Resource management method, control information transmission method and information configuration method

Abstract

The embodiment of the invention provides a resource management method, a control information transmission method and an information configuration method, and belongs to the technical field of communication. The resource management method can be executed by a first node and comprises the steps that a backhaul link resource management request is sent to a second node, and the resource management request comprises information related to backhaul link resources which the resource management request aims at; and receiving a first request response message returned by the second node based on the resource management request. Based on the scheme provided by the embodiment of the invention, the problem of backhaul link resource management between the concentration unit of the anchor node and the distribution unit of the anchor node or between the concentration unit of the anchor node (or the anchor node) and the relay node (or the distribution unit of the relay node) is solved, and the service of providing a user radio bearer for a user is better ensured.

Description

[0001] This application is a divisional application of the invention patent application with application number 201910741035.3, application date August 12, 2019, and invention name “Resource management method, control information transmission method, and information configuration method”. Technical Field

[0002] The present application relates to the field of communication technology, and in particular, to a resource management method, a control information transmission method, and an information configuration 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 was 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 shows 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 nodes, wherein users N1~Nx communicate with the anchor nodes through relay nodes 2 and 1, and users M1~My communicate with the anchor node through relay node 1.

[0004] The anchor node can 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 the F1 interface (see 3GPP TS38.473). The centralized unit includes the protocol stack of the service control plane and the protocol stack of the service user plane, wherein the protocol stack of the service control plane includes the radio resource control (RRC) protocol layer and the packet data convergence protocol (PDCP) layer, and the protocol stack of the service user plane includes the service data adaptation protocol (SDAP) layer and the PDCP layer; the distributed unit includes the protocol stack of the service control plane and the protocol stack of the service user plane, both of which include the radio link control (RLC) protocol layer, the medium access control (MAC) protocol layer and the physical layer (PHY, Physical).

[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 (such as 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 (such as 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 for serving the control plane, and a protocol stack including SDAP / PDCP / RLC / MAC / PHY used for serving 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 LTE (Long Term Evolution) / NR networks, user data is sent through a radio bearer (RB), which can be a data radio bearer (DRB) or a signaling radio bearer (SRB). Taking a data radio bearer (DRB) as an example, each user's data will be sent through one or more DRBs, and each DRB has a corresponding QoS (Quality of Service) parameter.

[0007] A new base station architecture is defined in the 5G network, that is, the base station includes a centralized unit (CU shown in the figure) and a distributed unit (DU shown in the figure), such as Figure 2As shown. In this base station architecture, when configuring DRB or SRB for a user, one way is that the centralized unit sends a request to establish, modify or release DRB / SRB to the distributed unit. The distributed unit will decide to accept or reject according to the wireless resource status and inform the centralized unit of the result. The centralized unit configures the user according to the result fed back by the distributed unit. Another way is that the distributed unit sends a request to modify or release DRB / SRB to the centralized unit. For a release request, the centralized unit can only accept it. For a modification request, the distributed unit cannot request to modify the QoS parameters of the DRB / SRB.

[0008] In non-IAB networks, that is, in existing networks, such as in the base station architecture of the above-mentioned 5G network, a user's DRB / SRB is served by the centralized unit and distributed unit of the base station, and the QoS requirements of a user's DRB / SRB are completed by the centralized unit and distributed unit of the base station. Therefore, the signaling interaction process performed by the existing technology only needs to be performed between the centralized unit and the distributed unit of the base station. The above method similar to the existing network will also be used in the IAB network. When configuring the user's DRB / SRB, the centralized unit of the anchor node will perform signaling interaction with the distributed unit of the relay node used to access the user (the signaling interaction can refer to the signaling interaction process between the centralized unit and the distributed unit of the base station in the existing network). However, in the IAB network, since a user's DRB / SRB may be served by multiple nodes, such as Figure 1 In the IAB network architecture shown in , the DRB / SRB of user N1 will be served by the centralized unit and the distributed unit in relay node 1, relay node 2 and anchor node. At this time, the interaction result between the centralized unit of the anchor node and the distributed unit of the relay node used to access the user cannot reflect the situation of the entire network. Therefore, the existing signaling interaction process cannot effectively coordinate the service of user wireless bearers (such as DRB / SRB) in the IAB network, which may cause the user wireless bearers that can be served by the IAB network to be rejected by the anchor node. Summary of the invention

[0009] 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: In a first aspect, an embodiment of the present application provides a resource management method, which is performed by a first node and includes: Sending a backhaul link resource management request to the second node, where the resource management request includes identification information of at least one user targeted by the resource management request and information related to the backhaul link resource targeted by the resource management request; A first request response message returned by the second node based on the resource management request is received.

[0010] In a second aspect, an embodiment of the present application provides a resource management method, which is performed by a second node and includes: receiving a backhaul link resource management request sent by the first node, where the resource management request includes information related to the backhaul link resource targeted by the resource management request; Request the first node to send a first request response message according to the resource management request.

[0011] In a third aspect, an embodiment of the present application provides a control information transmission method, which is performed by a fourth node, and the method includes: sending a data packet to a fifth node, the data packet including control information related to the user data; The fourth node and the fifth node are nodes in the IAB network.

[0012] In a fourth aspect, an embodiment of the present application provides a control information transmission method, which is performed by a fifth node, and the method includes: receiving a data packet sent by a fourth node, wherein the data packet includes control information related to the user data; Sending data packets based on control information; The fourth node and the fifth node are nodes in the IAB network.

[0013] In a fifth aspect, an embodiment of the present application provides an information configuration method, which is executed by a CU of an anchor node, and the method includes: Send a configuration request message for retransmission of the data packet or the last data packet to the DU of the anchor node; The receiving DU returns a configuration response message based on the configuration request message.

[0014] In a sixth aspect, an embodiment of the present application provides an information configuration method, which is executed by a DU of an anchor node, and the method includes: Receive a configuration request message of a retransmission data packet or a last data packet sent by the CU of the anchor node; The information configuration related to the retransmitted data packet or the last data packet is performed according to the configuration request information, and a configuration response message is sent to the CU of the anchor node.

[0015] In a seventh aspect, an embodiment of the present application provides a resource management device, which is arranged in a first node, and includes: A resource management request message sending module, configured to send a backhaul link resource management request to the second node, wherein the resource management request includes information related to the backhaul link resource targeted by the resource management request; The request response message receiving module is used to receive a first request response message returned by the second node based on the resource management request.

[0016] In an eighth aspect, an embodiment of the present application provides a resource management device, which is arranged in a second node and includes: A resource management request message receiving module, configured to receive a backhaul link resource management request sent by a first node, wherein the resource management request includes information related to the backhaul link resource targeted by the resource management request; The request response message sending module is used to request the first node to send a first request response message according to the resource management request.

[0017] In a ninth aspect, an embodiment of the present application provides a control information transmission device, which is arranged in a fourth node, and includes: a data packet sending module, configured to send a data packet to the fifth node, wherein the data packet includes control information related to the user data; The fourth node and the fifth node are nodes in the IAB network.

[0018] In a tenth aspect, an embodiment of the present application provides a control information transmission device, which is arranged in a fifth node, and includes: A data packet receiving module, used to receive a data packet sent by the fourth node, wherein the data packet includes control information related to the user data; A data packet sending module, used for sending data packets based on control information; The fourth node and the fifth node are nodes in the IAB network.

[0019] In an eleventh aspect, an embodiment of the present application provides an information configuration device, which is arranged in a CU of an anchor node, and includes: A configuration request message sending module, used for sending a configuration request message of a retransmitted data packet or a last data packet to the DU of the anchor node; The configuration response message receiving module is used to receive the configuration response message returned by the DU based on the configuration request message.

[0020] In a twelfth aspect, an embodiment of the present application provides an information configuration device, which is arranged in a DU of an anchor node, and includes: Configuration request message receiving module: used to receive the configuration request message of the retransmission data packet or the last data packet sent by the CU of the anchor node; Configuration response message sending module: used to configure information related to the retransmitted data packet or the last data packet according to the configuration request information, and send a configuration response message to the CU of the anchor node.

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

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

[0023] In the fifteenth aspect, an embodiment of the present application 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.

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

[0025] The technical solution provided by this application brings the following beneficial effects: The problem of how to manage user wireless bearers and / or return link channels between the CU of an anchor node and the DU of an anchor node, or between the CU of an anchor node (or an anchor node) and a relay node (or a distribution unit of a relay node) is solved, thereby avoiding the problem of directly abandoning the service for user wireless bearers because a node cannot meet the requirements for return link resources.

[0026] It solves the problem of how to transmit control information related to user data between the anchor node's DU (or anchor node) and the relay node, and between relay nodes, so that the intermediate reception can also obtain the above control information, thereby helping the node to better adjust the data scheduling strategy. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0028] Figure 1 A schematic diagram of the structure of an IAB network architecture is shown; Figure 2 A schematic diagram of the structure of a 5G base station is shown; Figure 3 A schematic diagram of a resource management method provided in an embodiment of the present application is shown; Figure 4 A schematic diagram of a signaling interaction process provided in an example of the present application is shown; Figure 5A schematic diagram of a signaling interaction process provided in another example of the present application is shown; Figure 6 A schematic diagram of a signaling interaction process provided in another example of the present application is shown; Figure 7 A schematic diagram of a signaling interaction process provided in another example of the present application is shown; Figure 8 A schematic diagram of a signaling interaction process provided in another example of the present application is shown; Fig. 9 A schematic diagram of a process of transmitting control information related to user data in an IAB network provided in an example of the present application is shown; Fig.10 A schematic diagram of a control information transmission method provided in an embodiment of the present application is shown; Fig.11 A schematic diagram of a flow chart of an information configuration method provided in an embodiment of the present application is shown; Fig.12 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

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

[0030] 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 intermediate elements. 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.

[0031] In the entire multi-hop network, Figure 1In 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.

[0032] In the IAB network, the relay node that the user accesses is the accessing IAB node. Figure 1 Relay node 2 is the access relay node for users N1~Nx, and relay node 1 is the access relay node for users M1~My. When configuring the user's DRB / SRB, the centralized unit of the anchor node will perform signaling interaction with the distributed unit of the access relay node (the signaling interaction can refer to the signaling interaction process between the centralized unit and the distributed unit of the base station in the existing network).

[0033] The difference between IAB network and single-hop network is that the user's DRB / SRB will be transmitted on the backhaul link. In order to realize the transmission of different DRB / SRBs for the same user or different DRB / SRBs for different users on the backhaul link, the concept of backhaul channel is also defined accordingly. On a backhaul link channel, the data of one user's DRB / SRB can be transmitted, the data of different DRB / SRBs for one user can be transmitted, and the data of different DRB / SRBs for different users can be transmitted. An example of a backhaul link channel is the backhaul link radio link control protocol layer channel, i.e., the Backhaul RLC channel. The entities at both ends of this channel are served by RLC / MAC / PHY services. Furthermore, it is possible to define a new protocol layer (such as an adaptation layer) on top of RLC. This backhaul link channel also has corresponding QoS parameters. One or more backhaul link channels will be established on the backhaul link to serve the user's DRB / SRB.

[0034] The technical personnel of the present application have found through research that there are at least the following three problems in the existing network technology that need to be improved.

[0035] 1. As described above, in an IAB network, a user's DRB / SRB may be served by multiple nodes (in a non-IAB network, i.e., an existing network, a user's DRB / SRB is served by the centralized unit and distributed unit of a base station), such as Figure 1 In the IAB network architecture shown in , the DRB / SRB of user N1 will be served by the centralized unit and the distributed unit in the relay node 1, relay node 2 and anchor node. In this way, the QoS requirements of a user's DRB / SRB are jointly completed by these nodes. However, the signaling interaction process performed by the prior art (such as the signaling interaction process between the centralized unit and the distributed unit of the base station) is only performed between the centralized unit of the anchor node and the distributed unit of the access relay node, and does not take into account the situation of other nodes serving the user. Therefore, the interaction result between the centralized unit of the anchor node and the distributed unit of the access relay node cannot reflect the situation of the entire network. In other words, when the distributed unit of the access relay node cannot accept the DRB / SRB of a certain user, it does not mean that the user's wireless bearer must not be served by the IAB network. In this way, the existing signaling interaction process cannot effectively coordinate the service of user wireless bearers (such as DRB / SRB) in the IAB network, which may cause the user's wireless bearer that can be served by the IAB network to be rejected by the anchor node.

[0036] For example, the QoS requirements of a user's DRB / SRB are met by multiple nodes. Take a DRB as an example, assuming that the delay requirement of the DRB from the centralized unit of the anchor node to the access relay node is 10ms. Figure 1 As an example, assume that the DRB needs to pass through the centralized unit of the anchor node to the access relay node: Anchor node distribution unit Relay Node 1 For access relay nodes, the set delay requirements are: the delay between the centralized unit of the anchor node and the distribution unit of the anchor node is 2ms, the delay between the distribution unit of the anchor node and relay node 1 is 6ms), and the delay between relay node 1 and the access relay node is 2ms. If relay node 1 and the access relay node cannot meet the 2ms requirement, this does not mean that the DRB of this user, i.e. UE (user equipment), cannot be served by these nodes, because the delay requirements between the nodes can be adjusted, such as adjusting the delay between the distribution unit of the anchor node and relay node 1 to 2ms, and adjusting the delay between relay node 1 and the access relay node to 6ms, so that the delay requirements of DRB can be met.

[0037] 2. In the IAB network, the backhaul channel is a special channel, which is different from the concept of DRB / SRB in the prior art. This channel is served by the distribution unit of the anchor node or the relay node. When configuring the backhaul channel, the distribution unit of the anchor node and the distribution unit of the relay node need to be configured according to the requirements of the backhaul channel (such as QoS requirements). The resources serving this channel are completely controlled by the distribution unit of the anchor node or the distribution unit of the relay node. According to the resource status of these nodes, these nodes can manage the backhaul link channels they serve (such as establishment, release, modification, etc.). However, such a signaling interaction process is not defined in the prior art, which makes it impossible for the distribution unit of the anchor node or the distribution unit of the relay node to manage the backhaul link channel.

[0038] 3. In the prior art, user data is sent between the user, the distributed unit of the base station and the centralized unit of the base station. In order to control data transmission well, in addition to sending user data, the centralized unit and the distributed unit of the base station also carry some control information, which is defined in TS38.425. However, in the IAB network, these control information will be exchanged between the centralized unit of the anchor node and the distributed unit of the access relay node through other nodes (such as the distributed unit of the anchor node and other relay nodes). During the transmission process, these other nodes may not be able to obtain these control information, resulting in the inability to control the transmission of user data based on these control information, thereby affecting the efficiency of user data transmission and may also affect information processing based on user data.

[0039] In order to solve at least one of the above technical problems in the prior art, an embodiment of the present application provides a resource management method, a control information transmission method, and an information configuration method.

[0040] The following first briefly describes the relevant technical terms that may be involved in the optional embodiments of the present application.

[0041] The user radio bearer involved in the embodiment of the present application may be a DRB, an SRB, or an E-RAB (Evolved Radio Access Bearer), which represents data for a user. The user radio bearer may be one or more different radio bearers belonging to one user, or one or more different radio bearers belonging to different users. For the QoS information involved in the embodiment of the present application, the QoS information defines information about at least one of the following QoS parameters: QoS Priority level; Packet Delay Budget; Packet Error Rate; 5QI (5G QoS Identifier) ​​value; QCI (QoS Class Identifier); Delay Critical Averaging Window; Maximum data burst volume; Allocation and Retention Priority; GBR (Guaranteed Bit Rate) QoS flow information, such as Maximum Flow Bit Rate Uplink / Downlink, Guaranteed Flow Bit Rate Uplink / Downlink, Maximum Packet Loss Rate Uplink / Downlink; GBR QoS information, such as E-RAB Maximum Bit Rate Uplink / Downlink, E-RAB guaranteed Bit Rate Uplink / Downlink; Reflective QoS Attribute.

[0042] The above-mentioned QoS information can be used to describe the QoS information of the user wireless bearer (such as the QoS information of DRB, and the QoS information of SRB), and can also be used to describe the QoS information of the return link channel. If the user wireless bearer (such as DRB and / or SRB) or the return link channel also contains multiple QoS flows, it can also be used to describe the QoS information of the QoS flow.

[0043] For the definition of the parameters in the above QoS information, please refer to 3GPP TS38.473 and 3GPP TS23.501.

[0044] In addition, it should be noted that in the embodiment of the present application, the signaling messages exchanged between two nodes can be exchanged through a wired link directly connecting the two nodes, or a wireless link between the two nodes, or can be exchanged after being forwarded by one or more nodes between the two nodes, and the link used when forwarding through one or more nodes can be a wired link or a wireless link.

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

[0046] One aspect of the present application provides a solution that can implement management of user bearer and backhaul link channel. The details are as follows: Figure 3 A schematic flow chart of a resource management method provided in an embodiment of the present application is shown. The method may be executed by a first node. As shown in the figure, the method may include: Step S110: sending a backhaul link resource management request to the second node, where the resource management request includes information related to the backhaul link resource targeted by the resource management request; Step S120: Receive a first request response message returned by the second node based on the resource management request.

[0047] It can be understood that the first node and the second node are both nodes in the IAB network.

[0048] The backhaul link resources may include at least one of a backhaul link channel and a user radio bearer, and the user radio bearer may be at least one of a user DRB, SRB and E-RAB.

[0049] For the information related to the return link resources targeted by the resource management request, specifically, if the targeted return link channel, that is, the return link resource is a return link channel, then the return link channel can be a newly created return link channel requested by the first node, or an existing return link channel requested to be modified by the first node, or a return link channel requested to be released by the first node; if it is targeted at a user wireless bearer, then the user wireless bearer can be a newly created wireless bearer requested by the first node, or an existing wireless bearer requested to be modified by the first node, or a wireless bearer requested to be released by the first node.

[0050] The resource management method provided in the embodiment of the present application realizes signaling interaction between different nodes in the IAB network. The first node and the second node interact based on the backhaul link resource management request and the corresponding request response message, so that different nodes in the IAB network can manage user wireless bearers and / or backhaul link channels, so that the interacting nodes can coordinate with each other to realize the configuration or adjustment of backhaul link resources (such as user wireless bearers, backhaul link channels) to better meet the needs of user wireless bearers and avoid directly giving up the service of user wireless bearers because one node cannot meet the needs.

[0051] It should be noted that the message name in the embodiment of the present application is only one optional example, but not the only one. Other message names may also be used, such as the message name of the above-mentioned return link resource management request. This message is used to identify that it is a message related to return link resource management (such as resource establishment, modification, release, etc.), and its name is not unique.

[0052] As an optional manner, the first node may be a centralized unit or an anchor node (including a centralized unit and a distributed unit anchor node) of an anchor node, and the second node may be a distributed unit or a relay node (or a distributed unit part of a relay node) of an anchor node.

[0053] As another optional manner, the first node may be a distribution unit or a relay node (or a distribution unit part of a relay node) of an anchor node, and the second node may be a centralized unit or an anchor node (including anchor nodes of centralized units and distribution units) of an anchor node.

[0054] Specifically, in an optional embodiment of the present application, the first node and the second node include any of the following: The first node is an anchor node, and the second node is a relay node or a DU of a relay node; The first node is a CU of an anchor node, and the second node is a DU of an anchor node, a relay node, or a DU of a relay node; The first node is a relay node or a DU of a relay node, and the second node is an anchor node or a CU of an anchor node; The first node is a DU of an anchor node, and the second node is a CU of an anchor node; Among them, if the first node is an anchor node or a CU of an anchor node, the resource management request is a first resource configuration request; if the first node is a relay node, a DU of a relay node or a DU of an anchor node, the resource management request is a first resource configuration modification request.

[0055] It should be noted that the relay node here may be an access relay node, a non-access relay node, or a relay node that serves as both a non-access relay node and an access relay node.

[0056] It can be understood that, for the user wireless bearer, the above-mentioned resource configuration request corresponds to the user wireless bearer configuration request, and the resource configuration modification request corresponds to the user wireless bearer configuration modification request; similarly, for the return link channel, the above-mentioned resource configuration request corresponds to the return link channel configuration request, and the resource configuration modification request corresponds to the return link channel configuration modification request.

[0057] As an example, Figure 4 A schematic diagram of a resource management method is shown in FIG. 1 . In this example, the first node may be an anchor node or a CU of an anchor node. When the first node is an anchor node, the second node may be a relay node or a DU of a relay node. When the first node is a CU of an anchor node, the second node may be a relay node or a DU of a relay node or a DU of an anchor node. Figure 4 As shown in , the resource management method in this example may include step 101 and step 102, which are specifically as follows: Step 101: The first node sends a configuration request message 101 (ie, a backhaul link resource management request in this example) to the second node; Step S102: the second node sends a configuration response message 102 (ie, a first request response message in this example) to the first node.

[0058] Among them, the above-mentioned configuration request message 101 and configuration response message 102 can be respectively the UEContext Setup / Modification Request (UE context configuration / modification request) and UE Context Setup / Modification Response / Failure (UE context configuration / modification response / failure) messages defined on the F1 interface, or they can be newly defined IAB node Context Setup / Modification Request (IAB node context configuration / modification request) and IAB node Context Setup / Modification Response / Failure (IAB node context configuration / modification response / failure) messages, or they can be other messages.

[0059] Based on the resource configuration request, the first node can provide the second node with relevant information (such as QoS information) of the return link resources (such as user wireless bearer, return link channel) that need to be met. At the same time, based on the request response information, the second node can provide the first node with reference information of the relevant information (such as QoS information) of the return link resources that it can meet according to its resource status. The reference information can help the first node adjust the parameters of the relevant information of the return link resources, and can help the first node and other nodes serving the user wireless bearer to make corresponding adjustments to the settings of the return link channel, so as to better meet the QoS requirements of the user wireless bearer, and avoid directly giving up the service to the user wireless bearer because a node cannot meet the QoS information provided by the first node.

[0060] As another example, Figure 5 , a schematic diagram of a resource management method is shown in FIG. 1 , in which the first node in the example may be a relay node or a DU of a relay node or a DU of an anchor node. When the first node is a relay node or a DU of a relay node, the second node may be an anchor node or a CU of an anchor node. When the first node is a DU of an anchor node, the second node may be a CU of an anchor node. Figure 5 As shown in , the resource management method in this example may include step 201 and step 202, which are specifically as follows: Step 201: The first node sends a configuration modification request message 201 (i.e., a backhaul link resource management request in this example) to the second node; Step S202: the second node sends a configuration modification response message 202 (ie, a first request response message in this example) to the first node.

[0061] Similarly, the above-mentioned configuration modification request message 201 and configuration modification response message 202 can be the UE Context Setup / Modification Required and UE Context Setup / ModificationConfirm / Refuse messages defined on the F1 interface, respectively, or they can be the newly defined IAB node Context Setup / ModificationRequired and IAB node Context Setup / Modification Confirm / Refuse messages, or they can be other messages.

[0062] Based on the resource configuration modification request, the first node can request to modify the relevant information (such as QoS information) of the user wireless bearer or return link channel according to its own resource status, and adjust the configuration of the first node when serving the user wireless bearer or return link channel, and the second node can decide whether to accept the modification requested by the first node according to the IAB network status. In addition, when the first node requests to release the user wireless bearer or return link channel, it provides the second node with the relevant information of the user wireless bearer or return link channel that it can satisfy, which can help the second node adjust the relevant information of the user wireless bearer or return link channel that the second node needs to satisfy according to the network status, and avoid the second node directly releasing the user wireless bearer or return link channel required to be released by the first node. In this way, it is possible to effectively provide services for user wireless bearers, without giving up the service of user wireless bearers because a node in the IAB network cannot meet the required QoS information.

[0063] In an optional embodiment of the present application, if the resource management request is a first resource configuration request, the information related to the backhaul link resource targeted by the resource management request includes at least one of the following information (the backhaul link resource targeted by the information related to the backhaul link resource may be a request to create, a request to modify, or a request to release): identification information of at least one user to which the resource management request is directed; Identification information of the backhaul link resource targeted by the resource management request; Information related to the QoS of the backhaul link resources serving the users; If the resource management request is a first resource configuration modification request, the information related to the backhaul link resource targeted by the resource management request includes at least one of the following information (the backhaul link resource targeted by the information related to the backhaul link resource may be a request to create, a request to modify, or a request to release): identification information of at least one user to which the resource management request is directed; Identification information of the backhaul link resource targeted by the resource management request; Information related to the QoS of the backhaul link resources requested to be modified.

[0064] The at least one user may include at least one of the following: UE, a relay node, a relay node other than the first node or the second node.

[0065] Among them, the identification information of at least one user targeted by the resource management request, that is, one or more identification information of at least one user targeted by the message (i.e., the resource management request), the identification information may include but is not limited to gNB-CU UE F1AP ID (5G base station centralized unit user F1AP (F1 Application Protocol, F1 application protocol) identifier), gNB-DU UE F1AP ID (5G base station distributed unit user F1AP identifier), C-RNTI (Cell Radio Network Temporary Identifier, cell radio network temporary identifier), etc. The user may be a user without relay function, such as an ordinary UE, or another relay node.

[0066] For the identification information of the return link resource targeted by the resource management request, specifically, if the return link resource is a return link channel, then the identification information is the identification information of the return link channel, specifically such as the ID of the return link channel; if the return link resource is a user wireless bearer, then the identification information is the identification information of the user wireless bearer, specifically such as a DRB ID or an SRB ID or an E-RAB ID.

[0067] In an optional embodiment of the present application, corresponding to the first resource configuration request, the above-mentioned information related to the QoS of the backhaul link resources serving the user may specifically include at least one of the following information (the parameters included in the following QoS information may refer to the QoS information described in the foregoing text of the present application): QoS information of backhaul link resources; QoS information of the backhaul link resources expected or requested to be met; QoS information of the backhaul link resources that are satisfied by the maximum expectation or maximum request; QoS information of the minimum expected or minimum requested backhaul link resources; Feedback indication information indicating information that the second node needs to feed back.

[0068] Each of the above information corresponding to the first resource configuration request is described below.

[0069] QoS information of return link resources: If it is for the return link channel, the QoS information may be generated by the first node according to the setting of the QoS parameters of the data served by the return link channel; if it is for the user wireless bearer, the QoS information may be generated by the first node according to the setting of the QoS parameters received from the core network, which represents the QoS requirements that the IAB network needs to meet when serving the user wireless bearer. This requirement needs to be met by the anchor node (or the centralized unit of the anchor node) and the user access relay node and all the nodes between the two nodes that serve the user wireless bearer. For details, please refer to the "DRB QoS" IE in TS38.473.

[0070] QoS information of the desired or requested return link resources (such as a return link channel or a user radio bearer): This information is the QoS requirement that the first node expects or requests the second node to meet when serving the return link channel or the user radio bearer. The "QoS information of the return link resources that is desired or requested to be met" may be the same as or different from the "QoS information of the return link resources".

[0071] QoS information of the maximum expected or requested return link resources (such as return link channels or user radio bearers): This information is the maximum QoS requirement that the first node expects or requests the second node to meet when serving the return link channel or user radio bearer. The "maximum expected or requested QoS information of the return link resources" may be the same as or different from the "QoS information of the return link resources" or the "QoS information of the return link resources expected or requested to be met".

[0072] The minimum QoS information of the backhaul link resources (such as the backhaul link channel or the user radio bearer) that is expected or requested to be satisfied, which is the minimum QoS requirement that the first node expects or requests the second node to meet when serving the backhaul link channel or the user radio bearer. The "minimum QoS information of the backhaul link resources that is expected or requested to be satisfied" may be the same as or different from the "QoS information of the backhaul link resources" or the "QoS information of the backhaul link resources that is expected or requested to be satisfied".

[0073] Feedback indication information indicating information that the second node needs to feedback: the indication information indicates the information that the second node needs to feedback. In one embodiment, for the backhaul link resource (backhaul link channel or user wireless bearer), the second node provides feedback according to the indication information after receiving the indication information. In another embodiment, for the backhaul link resource, if the second node cannot meet the above-mentioned "QoS information of the backhaul link resource" and / or "QoS information of the backhaul link resource expected or requested to be met" and / or "QoS information of the backhaul link resource that is maximum expected or requested to be met" and / or "QoS information of the backhaul link resource that is minimum expected or requested to be met", the second node provides feedback according to the indication information.

[0074] In an optional embodiment of the present application, the feedback indication information indicating the information that the second node needs to feedback may include at least one of the following information: Instruct the second node to feedback "QoS information of the maximum satisfiable backhaul link resources"; Instruct the second node to feedback "minimum satisfactory QoS information of backhaul link resources" The second node is instructed to feed back "QoS information of satisfactory backhaul link resources".

[0075] It should be noted that the term “satisfactory” involved in the embodiments of the present application can be interpreted as “admittable” or “acceptable”.

[0076] The above-mentioned "indication information indicating the information that the second node needs to feedback (i.e., feedback indication information)" is given for a backhaul link resource (such as a backhaul link channel or a user radio bearer), that is, the first node can choose whether to include the indication information in step S101 for each backhaul link resource. In another embodiment, the feedback indication information can be for the user, and as long as there is this indication information, the second node needs to feedback information according to the indication information for each backhaul link resource.

[0077] In an optional example of the present application, if the resource management request is a first resource configuration request, the first request response message also includes at least one of the following information: identification information of at least one user to which the first request response message is directed; information related to the backhaul link resources accommodated by the second node; information related to backhaul link resources not accommodated by the second node; Configuration information of the second node.

[0078] Each of the above-mentioned information in the first request response information corresponding to the first resource configuration request is explained below respectively.

[0079] Identification information of at least one user to which the first request response message is directed: that is, one or more identification information of the user to which the request response message is directed, such as gNB-CU UE F1AP ID, gNB-DU UE F1AP ID, C-RNTI. The user may be a user without relay function, such as a common UE, or another relay node.

[0080] The response information related to the backhaul link resources may specifically include one of the following information: Information related to the backhaul link resources (such as backhaul link channels or user radio bearers) accepted by the second node, if the accepted backhaul link information is step S101 ( Figure 4 If a newly created backhaul link resource is requested in step S101 in the example shown in , it indicates that the second node has accepted the newly created backhaul link resource; if the accepted backhaul link resource is the backhaul link resource requested to be modified in step S101, it indicates that the second node has accepted the modified backhaul link resource; if the accepted backhaul link resource is the backhaul link resource requested to be released in step S101, it indicates that the second node has accepted the request to release the backhaul link resource.

[0081] Information related to the return link resource not accepted by the second node: if the return link resource not accepted is the newly created return link resource requested in step S101, it indicates that the second node does not accept the newly created return link resource; if the return link resource not accepted is the return link resource requested to be modified in step S101, it indicates that the second node does not accept the modification of the return link resource; if the return link resource not accepted is the return link resource requested to be released in step S101, it indicates that the second node does not accept the request to release the return link resource.

[0082] The configuration information of the second node, i.e., the configuration information of the second node side generated by the second node, may include but is not limited to the configuration information of the RLC layer, and / or the configuration information of the logical channel, and / or the configuration information of the MAC layer, and / or the configuration information of the PHY layer, etc., and reference may be made to the Cell group configuration in TS38.331. The configuration information is related to the backhaul link channels (or user radio bearers) accepted and not accepted by the second node.

[0083] In an optional embodiment of the present application, the information related to the backhaul link resources accepted by the second node may include at least one of the following: Identification information of the backhaul link resource; Indication information used to indicate QoS information satisfied by the second connection node; QoS information satisfied by the second node; Information fed back based on the feedback indication information included in the first resource configuration request.

[0084] Specifically, the identification information of the above-mentioned backhaul link resources, if for a backhaul link channel, the identification information may be the ID of the backhaul link channel, or the logical channel ID serving the backhaul link channel; if for a user wireless bearer, the identification information may be a DRB ID or an SRB ID or an E-RAB ID.

[0085] Indication information indicating the QoS information (that is, the QoS requirement) satisfied by the second node: the indication information is used to indicate that the QoS information that can be satisfied by the second node is the QoS indicated by "QoS information of return link resources" and / or "QoS information of return link resources expected or requested to be satisfied" and / or "QoS information of return link resources that is maximum expected or requested to be satisfied" and / or "QoS information of return link resources that is minimum expected or requested to be satisfied".

[0086] QoS information satisfied by the second node: specifically, the QoS indicated by "QoS information of backhaul link resources" and / or "QoS information of satisfiable backhaul link resources" and / or "QoS information of maximum satisfiable backhaul link resources" and / or "QoS information of minimum satisfiable backhaul link resources", and / or other QoS information of backhaul link resources generated by the second node. Further, the information may be fed back according to the feedback indication information included in step S101.

[0087] In an optional embodiment of the present application, the information related to the backhaul link resources not accepted by the second node may include at least one of the following: Identification information of the backhaul link resource; Indication information used to indicate QoS information not satisfied by the second connection node; QoS information not satisfied by the second node; QoS information that can be satisfied by the second node; Information fed back based on the feedback indication information included in the first resource configuration request; The second node does not accept the reason information of the backhaul link.

[0088] Specifically, for the identification information of the return link resources, such as for the return link channel, it is the ID of the return link channel, or the logical channel ID serving the return link channel. For example, for the user wireless bearer, the identification information can be DRB ID or SRB ID or E-RAB ID.

[0089] For the indication information indicating the QoS information not satisfied by the second node: the indication information is used to indicate that the QoS information not satisfied by the second node may be the QoS indicated by "QoS information of return link resources" and / or "QoS information of return link resources expected or requested to be satisfied" and / or "QoS information of return link resources that is maximum expected or requested to be satisfied" and / or "QoS information of return link resources that is minimum expected or requested to be satisfied".

[0090] QoS information that can be satisfied by the second node: specifically, the QoS indicated by "QoS information of backhaul link resources" and / or "QoS information of satisfiable backhaul link resources" and / or "QoS information of maximum satisfiable backhaul link resources" and / or "QoS information of minimum satisfiable backhaul link resources", and / or other QoS information of backhaul link resources generated by the second node. Further, the information can be fed back according to the feedback indication information included in step S101.

[0091] Reason information about the second node not accepting the backhaul link, where the information indicates the specific reason why the second node does not accept the backhaul link, such as resource limitation. The reason information may also be used to indicate that one or more of the QoS parameters of the backhaul link cannot be met (such as QoS priority, delay budget of data packets, error rate of data packets, 5QI, QCI, delay importance indication, maximum data burst size, allocation reservation priority, GBR QoS flow information (such as maximum uplink / downlink flow rate, guaranteed uplink / downlink flow rate, maximum uplink / downlink packet loss rate), GBR QoS information (such as maximum uplink / downlink flow rate, guaranteed uplink / downlink flow rate), attributes of reflected QoS).

[0092] In an optional embodiment of the present application, corresponding to the first resource configuration modification request, the information related to the QoS of the backhaul link resource requested to be modified may include at least one of the following (the backhaul link resource targeted by the information may be requested to be newly created, requested to be modified, or requested to be released): Indication information indicating QoS information of the backhaul link resource that cannot be satisfied by the first node; QoS information of the backhaul link resources that cannot be satisfied by the first node; Reason information of the backhaul link that cannot be satisfied by the first node; Indication information indicating QoS information of the backhaul link resource that can be satisfied by the first node; QoS information of the backhaul link resources that can be satisfied by the first node; Configuration information of the first node.

[0093] Each of the above-mentioned information corresponding to the first resource configuration modification request is described below respectively.

[0094] Indication information indicating QoS information of the backhaul link resource that cannot be satisfied by the first node: the indication information used to indicate that the QoS that cannot be satisfied by the first node may be “QoS information of the backhaul link resource (such as the backhaul link channel or the user radio bearer)” and / or “QoS information of the backhaul link resource expected or requested to be satisfied” and / or “QoS information of the backhaul link resource that is maximum expected or requested to be satisfied” and / or “QoS information of the backhaul link resource that is minimum expected or requested to be satisfied”, wherein the “QoS information of the backhaul link resource” and / or “QoS information of the backhaul link resource that is expected or requested to be satisfied” and / or “QoS information of the backhaul link resource that is maximum expected or requested to be satisfied” and / or “QoS information of the backhaul link resource that is minimum expected or requested to be satisfied” may be the QoS information of the backhaul link resource that the second node satisfies in step S101 (corresponding to Figure 5 sent to the first node before step 201 in the above process.

[0095] QoS information of the return link resources that cannot be satisfied by the first node: Specifically, the unsatisfiable QoS information may be the QoS indicated by “QoS information of the return link resources” and / or “QoS information of the return link resources that is expected or requested to be satisfied” and / or “QoS information of the return link resources that is maximum expected or requested to be satisfied” and / or “QoS information of the return link resources that is minimum expected or requested to be satisfied” and / or other QoS information of the return link resources generated by the first node.

[0096] Reason information for the return link that cannot be satisfied by the first node, the information indicates the specific reason for the return link that cannot be satisfied by the first node, such as resource limitation, the reason information can also be used to indicate that one or more of the QoS parameters of the return link cannot be satisfied (such as QoS priority, delay budget of data packets, error rate of data packets, 5QI, QCI, delay importance indication, maximum data burst size, allocation reservation priority, GBR QoS flow information (such as maximum uplink / downlink flow rate, guaranteed uplink / downlink flow rate, maximum uplink / downlink packet loss rate), GBR QoS information (such as maximum uplink / downlink flow rate, guaranteed uplink / downlink flow rate), reflected QoS attributes).

[0097] Indication information indicating QoS information of the return link resources that can be satisfied by the first node: the indication information is used to indicate that the QoS that can be satisfied by the first node is the QoS indicated by "QoS information of the return link resources" and / or "QoS information of the return link resources that is expected or requested to be satisfied" and / or "QoS information of the return link resources that is maximum expected or requested to be satisfied" and / or "QoS information of the return link resources that is minimum expected or requested to be satisfied", where "QoS information of the return link resources" and / or "QoS information of the return link resources that is expected or requested to be satisfied" and / or "QoS information of the return link resources that is maximum expected or requested to be satisfied" and / or "QoS information of the return link resources that is minimum expected or requested to be satisfied" may be sent by the second node to the first node before step S101).

[0098] QoS information of the return link resources that can be satisfied by the first node, such as the QoS indicated by "QoS information of return link channel resources" and / or "QoS information of satisfyable return link resources" and / or "QoS information of maximum satisfyable return link resources" and / or "QoS information of minimum satisfyable return link resources" and / or other QoS information of the return link resources generated by the first node. Further, the information may be fed back based on the feedback indication information received from the second node before step S101. In one embodiment, the inclusion of the information may also implicitly indicate that the first node cannot satisfy the QoS information that the second node requires the first node to satisfy in other signaling interaction processes (which occur before step S101).

[0099] Configuration information of the first node: configuration information generated on the first node side, such as configuration information of the RLC layer, and / or configuration information of the logical channel, and / or configuration information of the MAC layer, and / or configuration information of the PHY layer, etc. For details, please refer to Cell group configuration in TS38.331. In one embodiment, the configuration information may be generated according to the return link channel (such as a return link channel or a user radio bearer) requested to be modified (or released or established) by the first node. In another embodiment, the configuration information may also be the configuration information on the first node side generated for the "QoS information of the return link resources that can be satisfied by the first node" for the above-mentioned return link information. In another embodiment, the first node may provide one or more of the above-mentioned configuration information to the second node, and for each configuration information, the first node indicates the one or more return link resources and the corresponding QoS information.

[0100] In an optional embodiment of the present application, if the resource management request is a first resource configuration modification request, the first request response message also includes at least one of the following: identification information of at least one user to which the first request response message is directed; information related to the backhaul link resources that the second node agrees to be modified; information related to the backhaul link resources that the second node disagrees with being modified; The first node configures the RRC message required by the user, such as the RRC Reconfiguration message; Indicates configuration information of the first node used when the first node configures a user.

[0101] The following describes various information that may be included in the first request response message, ie, the configuration modification response message, corresponding to the first resource configuration modification request.

[0102] Identification information of at least one user targeted by the first request response message: that is, one or more identification information of the user targeted by the message, such as gNB-CU UE F1AP ID, gNB-DU UE F1AP ID, C-RNTI. The user may be a user without relay function, such as a common UE, or another relay node.

[0103] Indicates the configuration information of the first node side used when the first node configures the user: such as the configuration information of the RLC layer, and / or the configuration information of the logical channel, and / or the configuration information of the MAC layer, and / or the configuration information of the PHY layer, etc. For details, please refer to the Cell group configuration in TS38.331. Figure 5 In step 201), the first node provides a plurality of configuration information to the second node, and the indication information may indicate which configuration information the first node uses when configuring the user.

[0104] In an optional embodiment of the present application, the information related to the backhaul link resources that the second node agrees to be modified includes (the "agree to be modified" means: if the first node requests new creation, the second node agrees to the new creation; if the first node requests modification, the second node agrees to the modification; if the first node requests release, the second node agrees to release): The second node agrees to modify the identification information of the backhaul link resource. In one embodiment, if the second node agrees to modify the identification information of the backhaul link resource (backhaul link channel or user radio bearer), the backhaul link resource indicated by the identification information of the backhaul link resource contained in the information will be newly created, modified or released. In another embodiment, if in step S101 (such as Figure 5 In the example shown in step 201 of FIG. 1 , the identification information of the backhaul link resource that is required to be newly created, modified, or released is not included in the response message (eg, Figure 5 In the message 202 in the response message, it can also indicate that the second node agrees to create, modify or release the backhaul link resource that is not included in the response message. If it agrees to create, modify or release, it means that it agrees to modify the first resource configuration request (such as Figure 5 The information provided in message 201) is modified.

[0105] In an optional embodiment of the present application, the information related to the backhaul link resource that the second node disagrees to be modified includes at least one of the following (the "disagree to be modified" means: if the first node requests new creation, the second node disagrees to the new creation; if the first node requests modification, the second node disagrees to the modification; if the first node requests release, the second node disagrees to the release): The second node disagrees with the modified identification information of the backhaul link resource; QoS information of the backhaul link resources that the first node needs to meet; Indication information used to indicate configuration information of the backhaul link resources required to be adopted by the first node.

[0106] In one embodiment, in the above process, if the first node sends a first resource configuration modification request message to the second node, the message includes information about the return link resource requested to be released, and provides the return link resource for the request to be released, and the first node provides information about the QoS of the return link resource that can be satisfied, and the first request response message fed back by the second node rejects the release request of the first node, it indicates that the first node can allocate resources for the return link resource according to the "QoS of the return link resource that can be satisfied" provided by it. If the first request response message fed back by the second node rejects the release request of the first node and provides "QoS information of the return link resource that needs to be satisfied", it indicates that the first node can allocate resources for the return link resource according to the "QoS of the return link resource that needs to be satisfied" provided by it.

[0107] In one embodiment, in the above process, if the first node sends a first resource configuration modification request message to the second node, the message includes information about the return link resources requested to be modified, and provides the return link resources for the request to be modified, the first node provides QoS-related information of the return link resources that can be satisfied, and the first request response message fed back by the second node rejects the modification request of the first node and provides "QoS information of the return link resources that need to be satisfied", it indicates that the first node can allocate resources for the return link resources according to the "QoS information of the return link resources that need to be satisfied" provided by it.

[0108] For the identification information of the return link resources that the second node does not agree to be modified, similarly, if it is for a return link channel, the identification information is the ID of the return link channel, or the logical channel ID serving the return link channel. If it is for a user wireless bearer, the identification information can be a DRB ID, an SRB ID, or an E-RAB ID.

[0109] The configuration information of the backhaul link resource to be used by the first node indicates the configuration information: the configuration information may include but is not limited to the configuration information of the RLC layer, and / or the configuration information of the logical channel, and / or the configuration information of the MAC layer, and / or the configuration information of the PHY layer, etc. For details, please refer to the indication information of the Cell group configuration in TS38.331. Figure 5 In step 201 shown in , if the first node provides the second node with multiple configuration information for serving the backhaul link resources, such as configuration information generated for "QoS information of the backhaul link resources", and / or, configuration information generated for "QoS information of satisfiable backhaul link resources", and / or, configuration information generated for "maximum satisfiable QoS information of backhaul link resources", and / or, configuration information generated for "minimum satisfiable QoS information of backhaul link resources", and / or configuration information generated for other QoS information of the backhaul link resources generated by the first node, the indication information can be used to indicate which of the above configuration information the first node should adopt.

[0110] In an optional embodiment of the present application, if the resource management request is a first resource configuration request, receiving a first request response message returned by the second node based on the resource management request includes: Receiving a second resource modification request sent by the second node based on the first resource configuration request; Sending a second request response message to the second node based on the second resource modification request; A first request response message is received, which is returned by the second node based on the second request response message and the first resource configuration request.

[0111] In an optional embodiment of the present application, if the resource management request is a first resource configuration modification request, receiving a first request response message returned by the second node based on the resource management request includes: Receiving a second resource configuration request sent by the second node based on the first resource configuration modification request; Returning a third request response message to the second node based on the second resource configuration request; A first request response message is received, which is returned by the second node based on the third request response message and the first resource configuration modification request.

[0112] In an actual system, the above two interaction processes provided in the above embodiments of the present application (the interaction process of the first node initiating a resource configuration request information to the second node (for the convenience of description, the process is referred to as the first process, such as Figure 4 ), and a process in which the first node initiates a resource configuration modification request to the second node (for ease of description, this process is referred to as the second process, as shown in Figure 5 The process shown in )) can be used in conjunction.

[0113] As an example, Figure 6 A schematic diagram of a resource configuration method used in two interactive process configurations is shown in FIG. As shown in the figure, in this example, the first process can be performed between the second process. Specifically, the resource configuration method can mainly include: Step 301: The first node sends a configuration modification request message 301 (such as a first resource configuration modification request) to the second node. For details of the request, see the first resource configuration modification request (such as Figure 5 message 201); Step 302: The second node sends a resource configuration request message 302 to the first node, which can refer to the first resource configuration request (such as Figure 4 101); Step 303: The first node sends a configuration response message 303 to the second node. For example, see the response message corresponding to the first resource configuration request message (eg Figure 4 102); Step 304: The second node sends a configuration modification response message 304 to the first node, which can refer to the first resource configuration modification response (such as Figure 5 message 202).

[0114] As an example, Figure 7 A schematic flow chart of another resource configuration method used in two interactive process configurations is shown in FIG. As shown in the figure, in this example, the second process can be performed between the first process. Specifically, the resource configuration method can mainly include: Step 401: The first node sends a configuration request message 401 to the second node. Figure 4 Message 101 shown in FIG.

[0115] Step 402: The second node sends a configuration modification request message 402 to the first node. Figure 5 Message 201 shown in; Step 403: The first node sends a configuration modification response message 403 to the second node. Figure 5 Message 202 shown in; Step 404: The second node sends a configuration response message 404 to the first node. Figure 4 Message 102 shown in .

[0116] In an optional embodiment of the present application, if the first node communicates with the second node through at least one third node, and the resource management request is a first resource configuration modification request, the first request response message is determined by the second node in the following manner: Sending a third resource configuration request to at least one third node based on the first resource configuration modification request; receiving a fourth request response message returned by the third node based on the third resource configuration request; A first request response message is determined according to the fourth request response information and the first resource configuration modification request.

[0117] In the IAB network, the user radio bearer is jointly served by multiple nodes. Therefore, when coordinating backhaul link resources such as a backhaul link channel or a user radio bearer, one or more other nodes (such as a third node, etc., which may be other relay nodes or distribution units of anchor nodes) may be involved. The following is an example in which the other node is the third node. For the case where there are multiple other nodes, the same can be applied.

[0118] As an example, Figure 8 A schematic flow chart of a resource management method when a first node interacts with a second node through a third node is shown. As shown in the figure, the method may include: Step 501: The first node sends a configuration modification request message 501 to the second node. Figure 5 Message 201 as shown in; Step 502: The second node sends a configuration request message 502 to the third node. Figure 4 Message 101 as shown in; Step 503: The third node sends a configuration response message 503 to the second node. Figure 4 Message 102 shown in; Step 504: The second node sends a configuration modification response message 504 to the first node. Figure 5 Message 202 shown in .

[0119] In this example, the above steps 502 and 503 are used to adjust the configuration of the second node and other nodes (such as the third node) to provide wireless bearer services for users. The adjustment is based on the information received in step 501. For example, step 501 provides QoS information of the return link channel or user wireless bearer that can be satisfied by the first node. In steps 502 and 503, the QoS information that needs to be satisfied when the third node serves the user wireless bearer is adjusted according to the information to better provide wireless bearer services for users.

[0120] It should be noted that for Figure 6 , Figure 7 or Figure 8 In the resource management method shown in , in each interactive process, except for the first step of the triggering node (the first node in the example) that triggers the start of the process, the current step of each node is based on the message received by the node, such as Figure 6 In step 302, the second node sends a message 302 to the first node. This step is based on the message 301 received by the second node. That is, the information carried in the message 302 is determined by the second node based on the message 301 received and the current resource configuration information of the second node.

[0121] Based on the resource configuration method provided in the embodiment of the present application, the nodes in the IAB network, i.e., the first node and the second node, can perform resource management of the user wireless bearer they serve and / or the return link channel that provides services for the user wireless bearer, such as configuration, resource allocation, and modification of the user wireless bearer and / or the return link channel. Through this method, the resource allocation of each node in the IAB network can be effectively coordinated to ensure that services are provided for the user wireless bearer.

[0122] In the prior art, when the CU and DU of a base station transmit user data, the CU will send control information related to the user data to the DU, such as information used to indicate whether the transmitted user data is a retransmitted data (see the Retransmission Flag field contained in the DLUSER DATA field in TS38.425), and the DU will also send some control information related to the user data to the CU, such as information used to indicate that the data packet sent by the DU to the CU is the last data packet for downlink status reporting (such as the Final Frame Indication field contained in the DL DATA DELIVERY STATUS field in TS38.425), such as information used to indicate the desired data rate for a user radio bearer (such as the Desired Data Rate field contained in the DL DATA DELIVERY STATUS field in TS38.425), which indicates the data rate at which the DU expects the CU to send data of the user radio bearer. The control information may also be information used to indicate the link status of the user served by the DU (such as the Cause field contained in the DL DATA DELIVERY STATUS field in TS38.425).

[0123] If the existing network method is used, in the IAB network, for a user radio bearer (such as DRB / SRB / E-RAB), the control information is exchanged between the CU of the anchor node and the access relay node of the user (that is, between non-intermediate nodes). During the interaction, the information will be forwarded through one or more intermediate nodes (such as the distribution unit of the anchor node and other relay nodes) between the CU of the anchor node and the access relay node of the user. Fig. 9 As shown, the control information will be forwarded through the distribution unit of the anchor node and the relay node 1. During the forwarding process, the control information is not forwarded to these intermediate nodes (such as Fig. 9 The distribution unit of the anchor node and the relay node 1) may be invisible, but these control information can help these intermediate nodes to forward data. In order to solve this problem, another aspect of the embodiment of the present application provides a method for sending control information related to user data in an IAB network. The details are as follows: The embodiment of the present application provides a control information transmission method, which can be executed by a fourth node, such as Fig.10 As shown, the method may mainly include: Sending a data packet (i.e., a data packet including control information related to the user data as shown in the figure) to the fifth node, where the data packet includes the control information related to the user data; The fourth node and the fifth node are nodes in the IAB network.

[0124] In an optional embodiment of the present application, the fourth node and the fifth node may be any two nodes communicating (directly or indirectly) in the IAB network, and may specifically be but not limited to intermediate nodes in the IAB network. It is understood that the intermediate node refers to neither the CU of the anchor node in the IAB network nor the node of the access relay node.

[0125] In an optional embodiment of the present application, the fourth node and the fifth node include any of the following: The fourth node and the fifth node are both relay nodes in the IAB network; One of the fourth node and the fifth node is a distribution unit of an anchor node in the IAB network, and the other is a relay node in the IAB network.

[0126] In an optional embodiment of the present application, the above data packet may include at least one of the following information: User’s data; Indicative information of identification information of the user to which the data packet belongs; Indicative information of identification information of the user radio bearer to which the data packet belongs; Indicative information of identification information of a backhaul link channel to which the data packet belongs; Indicative information of the path identification information of the path to which the data packet belongs; The destination receiving node to which the data packet belongs; The source sending node to which the data packet belongs; Indicative information of identification information of the relay node accessed by the user to which the data packet belongs; An indication of the type of data packet; Indicative information of a data rate that the fourth node expects the fifth node to use when sending data to the fourth node; Indication information related to a channel state when a distribution unit of the fourth node sends and receives data. In an optional embodiment of the present application, the indication information of the data packet type includes at least one of indication information used to indicate that the data packet is a retransmission data packet and indication information used to indicate that the data packet is the last data packet.

[0127] Each item of information that may be included in the above data packet is described below.

[0128] User data: such as PDCP PDU carrying user data; Indicative information of identification information of the user to which the data packet belongs: the indication information may be explicit or implicit, and specifically may include explicit or implicit identification information of the user to which the data packet belongs.

[0129] Indication information of identification information of the user radio bearer to which the data packet belongs: Similarly, the indication information may be implicit, and specifically may be explicit or implicit information including identification information of the user radio bearer to which the data packet belongs.

[0130] Indication information of identification information of the backhaul link channel to which the data packet belongs: the indication information may be explicit or implicit, and specifically may include explicit or implicit identification information of the backhaul link channel to which the data packet belongs.

[0131] Indicative information of the path identification information of the path to which the data packet belongs: the indication information may be explicit or implicit, and specifically may be explicit or implicit path identification information containing the path to which the data packet belongs. In one embodiment, the path indicated by the path identification information represents one or more nodes through which the user's data is sent from the CU of the anchor node to the access relay node of the user. In another embodiment, the path indicated by the path identification information represents one or more nodes through which the user's data is sent from the access relay node of the user to the CU of the anchor node.

[0132] Indicative information of identification information of the destination receiving node to which the data packet belongs, or indication information of identification information of the source sending node to which the data packet belongs, or indication information of identification information of the relay node to which the user to which the data packet belongs is connected: similarly, one or more of these indication information may be explicit or implicit, and specifically may be explicit or implicit identification information of the destination receiving node (or the source sending node to which the data packet belongs, or the relay node to which the user to which the data packet belongs) (such as the relay node / anchor node / centralized unit of the anchor node / distributed unit ID of the anchor node, identification information of the mobile terminal part of the relay node, identification information of the distributed unit part of the relay node, address information of the relay node / anchor node / centralized unit of the anchor node / distributed unit of the anchor node, such as IP address information, newly defined address information, and the newly defined address information may be allocated by the centralized unit of the anchor node).

[0133] Data packet type indication information: at least one of retransmission data packet indication information and last data packet indication information.

[0134] The retransmission indication information is data packet retransmission indication information, which indicates that the data packet is a retransmitted data packet.

[0135] Last data packet indication information: This information indicates that the data packet is the last data packet (or the last data packet containing a downlink status report (DL DATA DELIVERY STATUS) or the last data packet containing an uplink status report). In one embodiment, the indication information indicates that the data packet is the last data packet sent by the fourth node to the fifth node (or the last data packet containing a downlink status report or the last data packet containing an uplink status report).

[0136] In one embodiment, the indication information of the last data packet can be combined with the above-mentioned "indication information of the identification information of the user to which the data packet belongs" to indicate that the data packet is the last data packet of the user identified by the identification information of the user sent by the fourth node to the fifth node (or the last data packet containing a downlink status report, or the last data packet containing an uplink status report).

[0137] In another embodiment, the indication information of the last data packet can be combined with the above-mentioned "indication information of the identification information of the user wireless bearer to which the data packet belongs" to indicate that the data packet is the last data packet of the user wireless bearer identified by the identification information of the user wireless bearer sent by the fourth node to the fifth node (or the last data packet containing a downlink status report, or the last data packet containing an uplink status report).

[0138] In still another embodiment, the indication information of the last data packet may be combined with the above-mentioned "indication information of the identification information of the return link channel to which the data packet belongs" to indicate that the data packet is the last data packet (or the last data packet containing a downlink status report, or the last data packet containing an uplink status report) sent by the fourth node to the fifth node and belonging to the return link channel identified by the identification information.

[0139] In another embodiment, the indication information of the last data packet can be combined with the above-mentioned "identification information of the path to which the data packet belongs" to indicate that the data packet is the last data packet sent by the fourth node to the fifth node and belongs to the path identified by the identification information (or the last data packet containing a downlink status report, or the last data packet containing an uplink status report).

[0140] In another embodiment, the indication information of the last data packet can be combined with the above-mentioned "identification information of the destination receiving node to which the data packet belongs (or the source sending node to which it belongs, or the relay node accessed by the user)" to indicate that the data packet is the last data packet (or the last data packet containing a downlink status report, or the last data packet containing an uplink status report) sent by the fourth node to the fifth node and belonging to the node identified by the identification information.

[0141] Indicative information of the data rate that the fourth node expects the fifth node to use when sending data to the fourth node: that is, the indication information used to indicate the data rate that the fourth node expects the fifth node to use when sending data to the fourth node, and the indication information indicates the expected data sending rate. In one embodiment, the indication information indicates the data rate that the fourth node expects the fifth node to use when sending data to the fourth node.

[0142] In one embodiment, the indication information of the adopted data rate can be combined with the above-mentioned "identification information of the user to which the data packet belongs" to indicate that when the fifth node sends data belonging to the user identified by the identification information to the fourth node, the fourth node expects the fifth node to adopt the data rate.

[0143] In one embodiment, the indication information of the adopted data rate can be combined with the above-mentioned "identification information of the user wireless bearer to which the data packet belongs" to indicate that when the fifth node sends data belonging to the user wireless bearer identified by the identification information to the fourth node, the fourth node expects the data rate adopted by the fifth node.

[0144] In one embodiment, the indication information of the adopted data rate can be combined with the above-mentioned "identification information of the return link channel to which the data packet belongs" to indicate that when the fifth node sends data belonging to the return link channel identified by the identification information to the fourth node, the fourth node expects the fifth node to adopt the data rate.

[0145] In one embodiment, the indication information of the adopted data rate can be combined with the above-mentioned "identification information of the path to which the data packet belongs" to indicate that when the fifth node sends data belonging to the path identified by the identification information to the fourth node, the fourth node expects the fifth node to adopt the data rate; in one embodiment, the indication information can be combined with the above-mentioned "identification information of the destination receiving node to which the data packet belongs (or the source sending node to which it belongs, or the relay node accessed by the user)" to indicate that when the fifth node sends data belonging to the node identified by the identification information to the fourth node, the fourth node expects the fifth node to adopt the data rate.

[0146] Indication information related to the channel state when the distribution unit of the fourth node sends and receives data: that is, information related to the channel state when the distribution unit of the fourth node sends and receives data, such as indication information of radio link outage / resume, and / or indication information of uplink or downlink radio link outage / resume, etc. In one embodiment, the indication information related to the channel state can be combined with the above-mentioned "identification information of the user to which the data packet belongs" to indicate the user to which the state information is directed; in one embodiment, the indication information related to the channel state can be combined with the above-mentioned "identification information of the user wireless bearer to which the data packet belongs" to indicate the user wireless bearer to which the state information is directed; in one embodiment, the indication information related to the channel state can be combined with the above-mentioned "identification information of the return link channel to which the data packet belongs" to indicate the return link channel to which the state information is directed; in one embodiment, the indication information related to the channel state can be combined with the above-mentioned "identification information of the path to which the data packet belongs" to indicate the path to which the state information is directed; in one embodiment, the indication information related to the channel state can be combined with the above-mentioned "identification information of the destination receiving node to which the data packet belongs (or the source sending node to which it belongs, or the relay node accessed by the user to which it belongs)" to indicate the node to which the state information is directed.

[0147] In practical applications, the location of the control information in the data packet can be configured or set according to actual needs or predefined by protocol. As an optional method, the control information may be included in the header of the RLC layer of the data packet, or in the header of a newly defined protocol layer above the RLC layer (such as an adaptation layer, a bearer mapping layer, or other names), or in the header of the MAC layer, or in a physical layer signal. In addition, the control information may be included in a data packet with user data, or in a data packet without user data (such as an EndMarker data packet, which does not contain user data and is specifically used to send the control information).

[0148] In an embodiment of the present application, the above-mentioned data packet may be an uplink data packet or a downlink data packet. Among them, the downlink data packet refers to the data packet sent by the CU of the anchor node to the access relay node of the user, and the uplink data packet refers to the data packet sent by the access relay node of the user to the CU of the anchor node. The data packet containing control information related to user data sent by the fourth node to the fifth node may be an uplink data packet (the user data contained in the data packet is ultimately to be sent to the CU of the anchor node), or it may be a downlink data packet (the user data contained in the data packet is ultimately to be sent to the access relay node of the user, and then may be sent to the user by the access relay node). Furthermore, the data targeted by the above-mentioned data packet may be the data served by the distribution unit part of the fourth node, or the data served by the mobile terminal part of the fourth node, or the data served by the distribution unit part and the mobile terminal part of the fourth node.

[0149] Among them, for the above control information that can be included in the data packet, the fourth node may obtain the above information from other nodes, or the fourth node may determine the above information by itself.

[0150] When the fourth node is a relay node or a distributed unit of an anchor node, and the fifth node is a centralized unit of an anchor node, the control information may also be sent to the fifth node via control signaling (such as control signaling of an F1 interface). Specifically, in addition to the control information, the control signaling sent by the fourth node to the fifth node may optionally include at least one of information related to the data type and indication information of no data, specifically: Information related to the data type, including at least one of the following: Information indicating the identification information of the user to which it belongs; Indication information of the identification information of the user radio bearer to which it belongs; Indicative information of identification information of the backhaul link channel to which it belongs; Indicative information of the path identification information of the path to which it belongs; The destination receiving node; The source sending node to which it belongs; Indicative information of the identification information of the relay node to which the user belongs; Indication information of no data, the indication information is used to indicate that there is no data sent from the fourth node to the fifth node. Further, the data may be data of a specific type, and the data type targeted by the indication information may be the data type indicated by the above-mentioned “information related to the data type”. The indication information may be a separate information element (Information element) in the control signaling or an information element combined with the above-mentioned “information related to the data type”, and may also be included in the control signaling as a cause information (Cause). Further, the data targeted by the indication information may be data served by the distribution unit part of the fourth node, or data served by the mobile terminal part of the fourth node, or data served by the distribution unit part and the mobile terminal part of the fourth node.

[0151] In addition, the above-mentioned "information related to the data type" can be combined with the "indication information of no data" to indicate that there is no data indicated by the "information related to the data type", or to indicate that the fourth node does not have the data indicated by the "information related to the data type", or to indicate that the fourth node has no data indicated by the "information related to the data type" to send.

[0152] The above control signaling may be an existing UE Context Modification Required message, a UE Context Release Request message, other F1 signaling, or a newly defined control signaling.

[0153] Before the fourth node sends the control signaling to the fifth node, the fourth node may also receive a user data packet containing control information from other nodes, where the control information contains at least one of the following information: Indicative information of identification information of the user to which the data packet belongs; Indicative information of identification information of the user radio bearer to which the data packet belongs; Indicative information of identification information of a backhaul link channel to which the data packet belongs; Indicative information of the path identification information of the path to which the data packet belongs; The destination receiving node to which the data packet belongs; The source sending node to which the data packet belongs; Indicative information of identification information of the relay node accessed by the user to which the data packet belongs; An indication of the type of data packet; an indication of a data rate at which the other nodes expect the fourth node to send data to the other nodes; Indication information related to a channel state when a distribution unit of the fourth node sends and receives data.

[0154] Based on the control information transmission method provided in the embodiment of the present application, after the fifth node learns the above-mentioned control information sent by the fourth node, it can help the fifth node adjust the data packet scheduling decision. For example, when it is known that the data packet is a retransmitted data packet, the retransmitted data packet can be scheduled preferentially. When it is known that the data packet is the last data packet or when it is known that there is no data of a certain type on the node, the relevant resources can be released (such as releasing or modifying the return link channel serving this type of data, releasing or modifying the DRB or SRB serving this type of data). For another example, after knowing the link status of the DU of the fourth node when serving the user, it can decide whether to stop sending data to the fourth node. If the link status corresponding to the fourth node is interrupted, the fifth node can decide to stop sending data to the fourth node. If the link status corresponding to the fourth node is normal or replied, the fifth node can send data to the fourth node.

[0155] Through the control information transmission method provided in the embodiment of the present application, the relay node can also obtain control information related to the user data when sending user data, which can help the relay node adjust its data sending strategy and utilize resources more effectively.

[0156] For the above-mentioned data packet containing control information (which can be an uplink data packet or a downlink data packet), the indication information indicating that the data packet is a retransmitted data packet (or the last data packet), that is, the retransmission indication information (or the indication information of the last packet), may be sent from the CU of the anchor node, such as the CU of the anchor node sends it to the DU of the anchor node, and then the DU of the anchor node sends it to the fourth node, or it may also be sent from the CU of the anchor node to the DU of the anchor node, and then the DU of the anchor node sends it to other relay nodes, and then the other relay nodes send it to the fourth node. In order to complete the sending of the above-mentioned retransmission data packet indication information (or the indication information of the last packet), the existing mechanism may not guarantee that the node that sends the data packet to the fourth node can know whether a data packet is a retransmission data packet (or whether it is the last data packet). For example, for a downlink data packet sent by the CU of the anchor node to the DU of the anchor node, and then sent by the DU of the anchor node to the fourth node, it cannot be guaranteed that the DU of the anchor node can know whether a data packet is a retransmission data packet. This needs to be achieved through the configuration information between the CU of the anchor node and the DU of the anchor node; for another example, the data packet sent by the fourth node to the distribution unit of the anchor node is the last data packet, but the current mechanism cannot guarantee that the centralized unit of the anchor node can know that the data packet sent by the distribution unit of the anchor node is the last data packet. This also needs to be achieved through the configuration information between the CU of the anchor node and the DU of the anchor node. The specific configuration method may include but is not limited to at least one of the following methods: Method 1: By configuring a special GTP-U tunnel (GPRS Tunnel Protocol User) to indicate that the data packet sent in the tunnel is a retransmission data packet (or the last data packet), in this method, the GTP-U tunnel information of the sender and / or receiver, such as the GTP-U tunnel identifier (GTP-U TEID) and / or IP address) is used to indicate whether the GTP-U tunnel is the tunnel for sending the retransmission data packet (or the last data packet); Method 2: By configuring a special IP address to indicate that the packets containing the IP address are all retransmitted packets (or the last packet), the IP address information of the sender and / or receiver is used to indicate whether the packet containing the IP address is a retransmitted packet (or the last packet); Method 3: Indicate that the data packet is a retransmitted packet (or the last data packet) by configuring the information in the data packet header (such as the IP packet header).

[0157] In order to ensure that each node in the IAB network (such as the DU of the anchor node) can know whether a data packet that needs to be forwarded is a retransmitted data packet (or the last data packet), the embodiment of the present application further provides an information configuration method, which is executed by the CU of the anchor node, such as Fig.11 As shown, the method may include: Step 601: Send a configuration request message for a retransmission data packet or the last data packet to the distribution unit DU of the anchor node; Step 602: Receive a configuration response message returned by the DU of the anchor node based on the configuration request message.

[0158] In an optional embodiment of the present application, in order to implement any one of the above three methods 1 to 3, the configuration request message includes at least one of the following information: Information related to GPRS GTP-U tunnel; Information related to IP address; Information related to the packet header; Identification information of the user to which the data packet belongs; Identification information of the user radio bearer to which the data packet belongs; Path identification information of the path to which the data packet belongs; Identification information of the backhaul link channel to which the data packet belongs; The identification information or address information of the destination receiving node of the data packet (such as the access relay node of the user to which the data packet belongs); Identification information or address information of the source sending node of the data packet; The identification information or address information of the node to which the data packet belongs.

[0159] The information carried in the configuration request message indicates the relevant information used to transmit the retransmitted data packet (or the last data packet). After receiving the configuration request message, the DU of the anchor node can perform relevant configurations of the retransmitted data packet (or the last data packet) based on the information carried in the message. For example, the above-mentioned information related to the IP address can specifically indicate the relevant information of the IP address used to transmit the retransmitted data packet (or the last data packet).

[0160] It should be noted that, when there are multiple messages carried in the configuration message request, different messages can be used in combination to indicate the data packet for which the resource configuration of the retransmitted data packet (or the last data packet) is directed. For example, in an optional embodiment, the identification information of the user to which the data packet belongs and the information related to the IP address can be used in combination, and then the information related to the IP address used to transmit the retransmitted data packet (or the last data packet) of the user indicated by the identification information can be used.

[0161] In an optional embodiment of the present application, the information related to the GTP-U tunnel in the configuration request message includes at least one of the following information: Instruction information indicating the allocation of GTP-U tunnel information for receiving retransmitted data packets (or the last data packet); The CU of the anchor node sends the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The DU of the anchor node receives the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The DU of the anchor node sends the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The CU of the anchor node receives the GTP-U tunnel information of the retransmitted data packet (or the last data packet).

[0162] Among them, the GTP-U tunnel information of the above-mentioned retransmitted data packet (or the last data packet) may include but is not limited to information such as the TEID and / or IP address of the retransmitted data packet (or the last data packet). For example, for the GTP-U tunnel information of the anchor node's CU sending a retransmitted data packet (or the last data packet), the information may be the TEID of the anchor node's CU sending the retransmitted data packet (or the last data packet), or the IP address of the anchor node's CU sending the retransmitted data packet (or the last data packet), or the TEID and IP address of the anchor node's CU sending the retransmitted data packet (or the last data packet).

[0163] In an optional embodiment of the present application, the information related to the IP address in the configuration request message includes at least one of the following information: Instruction information indicating the IP address allocated to receive the retransmitted data packet (or the last data packet); The IP address to which the anchor node's CU sends the retransmitted data packet (or the last data packet); The IP address of the anchor node's DU that receives the retransmitted data packet (or the last data packet); The IP address to which the anchor node's CU sends the retransmitted data packet (or the last data packet); The IP address of the anchor node's DU that receives the retransmitted packet (or the last packet).

[0164] In an optional embodiment of the present application, the information related to the data packet header in the configuration request message includes at least one of the following information: Indicates the location of information in a data packet sent by the CU of the anchor node to the DU of the anchor node, which is used to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicating that when a data packet sent by the CU of the anchor node to the DU of the anchor node is a retransmitted data packet (or the last data packet), the content of the indication information contained in the retransmitted data packet (or the last data packet), for example, the content may be information set in the DSCP (Differentiated Services Code Point) and / or flow label field in the IP packet header to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicates the location of information in a data packet sent by the DU of the anchor node to the CU of the anchor node, which is used to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicates the content of the indication information contained in the data packet when the data packet sent by the DU of the anchor node to the CU of the anchor node is a retransmission data packet (or the last data packet), such as the information set in the DSCP / flow label field in the IP packet header to indicate that the data packet is a retransmission data packet (or the last data packet).

[0165] The configuration response message 602 corresponding to the configuration request information 601 is mainly used to confirm the information in step 601. It is clear to those skilled in the art that the configuration response message 602 corresponds to the configuration request information 601. The DU of the anchor node completes the configuration of the information related to the retransmitted data packet (or the last data packet) according to the configuration request information 601 received from the CU of the anchor node, and feeds back confirmation information to the CU of the anchor node. In an optional embodiment of the present application, the configuration response message may include at least one of the following information: Information related to GTP-U tunnel; Information related to IP address; Information related to the packet header; Identification information of the user to which the data packet belongs; Identification information of the user radio bearer to which the data packet belongs; Path identification information of the path to which the data packet belongs; Identification information of the backhaul link channel to which the data packet belongs; The identification information or address information of the destination receiving node of the data packet (such as the access relay node of the user to which the data packet belongs); Identification information or address information of the source sending node of the data packet; The identification information or address information of the node to which the data packet belongs.

[0166] In an optional embodiment of the present application, the information related to the GTP-U tunnel in the configuration response message includes at least one of the following information: The CU of the anchor node sends the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The DU of the anchor node receives the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The DU of the anchor node sends the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The CU of the anchor node receives the GTP-U tunnel information of the retransmitted data packet (or the last data packet).

[0167] In an optional embodiment of the present application, the information related to the IP address in the configuration response message includes at least one of the following information: The IP address to which the anchor node's CU sends the retransmitted data packet (or the last data packet); The IP address of the anchor node's DU that receives the retransmitted data packet (or the last data packet); The IP address to which the anchor node's CU sends the retransmitted data packet (or the last data packet); The IP address of the anchor node's DU that receives the retransmitted packet (or the last packet).

[0168] In an optional embodiment of the present application, the information related to the data packet header in the configuration response message includes at least one of the following information: Indicates the location of information in a data packet sent by the CU of the anchor node to the DU of the anchor node, which is used to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicates the content of indication information contained in the retransmitted data packet (or the last data packet) when the data packet sent by the CU of the anchor node to the DU of the anchor node is a retransmitted data packet (or the last data packet), such as the information set in the DSCP / flow label field in the IP packet header to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicates the location of information in a data packet sent by the DU of the anchor node to the CU of the anchor node, which is used to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicates the content of the indication information contained in the data packet when the data packet sent by the DU of the anchor node to the CU of the anchor node is a retransmission data packet (or the last data packet), such as the information set in the DSCP / flow label field in the IP packet header to indicate that the data packet is a retransmission data packet (or the last data packet).

[0169] Based on the configuration process of the information configuration method provided in the embodiment of the present application, the CU of the anchor node and / or the CU of the anchor node can know whether the data packet it receives is a retransmitted data packet (or the last data packet).

[0170] Based on Figure 3 Based on the same principle as the resource management method shown in , the embodiment of the present application further provides a resource management method, which can be specifically executed by the second node, and the method can specifically include: receiving a backhaul link resource management request sent by the first node, where the resource management request includes information related to the backhaul link resource targeted by the resource management request; Request the first node to send a first request response message according to the resource management request.

[0171] It is clear to those skilled in the art that this method is Figure 3 The method shown in the method has the same principle, but the method is described from a different execution subject side. Specifically, Figure 3 The resource management method shown in is described with the first node as the execution subject of the method, and this method is described with the second node as the execution subject of the method. Figure 4 In the example shown in Figure 3 The method shown is described with the sender of the configuration request message 101 as the execution subject, and the method is described with the receiving method of the configuration request message 101 as the execution subject. For a detailed description of the method, please refer to the above description of Figure 3 The corresponding description in the method shown in .

[0172] Optionally, the first node and the second node include any of the following: The first node is an anchor node, and the second node is a relay node or a DU of a relay node; The first node is a CU of an anchor node, and the second node is a DU of an anchor node, a relay node, or a DU of a relay node; The first node is a relay node or a DU of a relay node, and the second node is an anchor node or a CU of an anchor node; The first node is a DU of an anchor node, and the second node is a CU of an anchor node; Among them, if the first node is an anchor node or a CU of an anchor node, the resource management request is a first resource configuration request; if the first node is a relay node, a DU of a relay node or a DU of an anchor node, the resource management request is a first resource configuration modification request.

[0173] Optionally, the backhaul link resource includes at least one of a backhaul link channel and a user radio bearer; wherein the user radio bearer includes at least one of the following: DRB, SRB, E-RAB.

[0174] Optionally, if the resource management request is a first resource configuration request, the information related to the backhaul link resource targeted by the resource management request includes at least one of the following information: identification information of at least one user to which the resource management request is directed; Identification information of the backhaul link resource targeted by the resource management request; information related to QoS of backhaul link resources serving at least one user; If the resource management request is a first resource configuration modification request, the information related to the backhaul link resource targeted by the resource management request includes at least one of the following information: identification information of at least one user to which the resource management request is directed; Information related to the QoS of the backhaul link resources requested to be modified.

[0175] Optionally, the information related to the QoS of the backhaul link resources serving at least one user includes at least one of the following: QoS information of backhaul link resources; QoS information of the backhaul link resources expected or requested to be met; QoS information of the backhaul link resources that are satisfied by the maximum expectation or maximum request; QoS information of the minimum expected or minimum requested backhaul link resources; Feedback indication information indicating information that the second node needs to feed back; The information related to the QoS of the backhaul link resource requested to be modified includes at least one of the following: Indication information indicating QoS information of the backhaul link resource that cannot be satisfied by the first node; QoS information of the backhaul link resources that cannot be satisfied by the first node; Reason information of the backhaul link that cannot be satisfied by the first node; Indication information indicating QoS information of the backhaul link resource that can be satisfied by the first node; QoS information of the backhaul link resources that can be satisfied by the first node; Configuration information of the first node.

[0176] Optionally, if the resource management request is a first resource configuration request, the first request response message further includes at least one of the following information: identification information of at least one user to which the first request response information is directed; information related to the backhaul link resources accommodated by the second node; information related to backhaul link resources not accommodated by the second node; Configuration information of the second node.

[0177] Optionally, if the resource management request is a first resource configuration modification request, the first request response message also includes at least one of the following: identification information of at least one user to which the first request response message is directed; information related to the backhaul link resources that the second node agrees to be modified; information related to the backhaul link resources that the second node disagrees with being modified; The first node configures the RRC message required by the user; Indicates configuration information of the first node used when the first node configures a user.

[0178] Optionally, the information related to the backhaul link resources accepted by the second node includes at least one of the following: Identification information of the backhaul link resource; Indication information used to indicate QoS information satisfied by the second connection node; QoS information satisfied by the second node; Information fed back based on the feedback indication information included in the first resource configuration request; The information related to the backhaul link resources not accepted by the second node includes at least one of the following: Identification information of the backhaul link resource; Indication information used to indicate QoS information not satisfied by the second connection node; QoS information not satisfied by the second node; QoS information that can be satisfied by the second node; Information fed back based on the feedback indication information included in the first resource configuration request; Reason information of why the second node does not accept the backhaul link; The information related to the backhaul link resource that the second node agrees to be modified includes any one of the following: The second node agrees to the identification information of the backhaul link resource to be modified; The second node disagrees with the modified identification information of the backhaul link resource; The information related to the backhaul link resource that the second node disagrees with being modified includes at least one of the following: The second node disagrees with the modified identification information of the backhaul link resource; QoS information of the backhaul link resources that the first node needs to meet; Indication information used to indicate configuration information of the backhaul link resources required to be adopted by the first node.

[0179] Optionally, if the resource management request is a first resource configuration request, requesting the first node to send a first request response message according to the resource management request includes: Sending a second resource modification request to the first node based on the first resource configuration request; Receiving a second request response message sent by the first node based on the second resource modification request; A first request response message is returned based on the second request response message and the first resource configuration request.

[0180] Optionally, if the resource management request is a first resource configuration modification request, requesting the first node to send a first request response message according to the resource management request includes: Sending a second resource configuration request to the first node based on the first resource configuration modification request; Receiving a third request response message returned by the first node based on the second resource configuration request; A first request response message is sent to the first node based on the third request response message and the first resource configuration modification request.

[0181] Optionally, if the first node communicates with the second node through at least one third node, and the resource management request is a first resource configuration modification request, requesting the first node to send a first request response message according to the resource management request includes: Sending a third resource configuration request to at least one third node based on the first resource configuration modification request; receiving a fourth request response message returned by the third node based on the third resource configuration request; A first request response message is sent to the first node according to the fourth request response information and the first resource configuration modification request.

[0182] The optional at least one user includes at least one of the following: UE, a relay node, a relay node other than the first node or the second node.

[0183] Based on Fig.10 Based on the same principle as the method shown in , the embodiment of the present application further provides a control information transmission method, which can be performed by the fifth node. The method can specifically include: receiving a data packet sent by a fourth node, wherein the data packet includes control information related to the user data; Sending data packets based on control information; The fourth node and the fifth node are nodes in the IAB network.

[0184] Optionally, the fourth node and the fifth node include any of the following: The fourth node and the fifth node are both relay nodes in the IAB network; One of the fourth node and the fifth node is a distribution unit of an anchor node in the IAB network, and the other is a relay node in the IAB network.

[0185] Optionally, the data packet includes at least one of the following information: User’s data; Indicative information of identification information of the user to which the data packet belongs; Indicative information of identification information of the user radio bearer to which the data packet belongs; Indicative information of identification information of a backhaul link channel to which the data packet belongs; Indicative information of the path identification information of the path to which the data packet belongs; Indicative information of identification information of a destination receiving node to which the data packet belongs; Indicative information of identification information of the source sending node to which the data packet belongs; Indicative information of identification information of the relay node accessed by the user to which the data packet belongs; An indication of the type of data packet; Indicative information of a data rate that the fourth node expects the fifth node to use when sending data to the fourth node; Indication information related to a channel state when a distribution unit of the fourth node sends and receives data.

[0186] Optionally, the indication information of the data packet type includes at least one of indication information used to indicate that the data packet is a retransmission data packet and indication information used to indicate that the data packet is the last data packet.

[0187] It is clear to those skilled in the art that for a detailed description of the control information transmission method in the above-mentioned optional embodiments, reference can be made to the above description of Fig.10 Corresponding description of the control information transmission method shown in .

[0188] Based on Fig.11 Based on the same principle as the method shown in , the embodiment of the present application further provides an information configuration method, which can be specifically performed by the DU of the anchor node. The method may include: Receive a configuration request message of a retransmission data packet or a last data packet sent by the CU of the anchor node; The information configuration related to the retransmitted data packet or the last data packet is performed according to the configuration request information, and a configuration response message is sent to the CU of the anchor node.

[0189] Optionally, the configuration request message includes at least one of the following information: Information related to GTP-U tunnel; Information related to IP address; Information related to the packet header; Identification information of the user to which the data packet belongs; Identification information of the user radio bearer to which the data packet belongs; Path identification information of the path to which the data packet belongs; Identification information of the backhaul link channel to which the data packet belongs; The identification information or address information of the destination receiving node of the data packet; Identification information or address information of the source sending node of the data packet; The identification information or address information of the node to which the data packet belongs.

[0190] Optionally, the information related to the GTP-U tunnel in the configuration request message includes at least one of the following information: Instruction information for instructing allocation of GTP-U tunnel information for receiving a retransmitted data packet or a last data packet; The CU of the anchor node sends the GTP-U tunnel information of the retransmitted data packet or the last data packet; The DU of the anchor node receives the GTP-U tunnel information of the retransmitted data packet or the last data packet; The DU of the anchor node sends the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The CU of the anchor node receives the GTP-U tunnel information of the retransmitted data packet (or the last data packet).

[0191] Optionally, the information related to the IP address in the configuration request message includes at least one of the following information: Instruction information indicating the IP address allocated to receive the retransmitted data packet (or the last data packet); The IP address to which the anchor node's CU sends the retransmitted data packet (or the last data packet); The IP address of the anchor node's DU that receives the retransmitted data packet (or the last data packet); The IP address to which the anchor node's CU sends the retransmitted data packet (or the last data packet); The IP address of the anchor node's DU that receives the retransmitted packet (or the last packet).

[0192] Optionally, the information related to the data packet header in the configuration request message includes at least one of the following information: Indicates the location of information in a data packet sent by the CU of the anchor node to the DU of the anchor node, which is used to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicates the content of indication information included in the retransmitted data packet (or the last data packet) when the data packet sent by the CU of the anchor node to the DU of the anchor node is a retransmitted data packet (or the last data packet); Indicates the location of information in a data packet sent by the DU of the anchor node to the CU of the anchor node, which is used to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicates the content of the indication information contained in the data packet when the data packet sent by the DU of the anchor node to the CU of the anchor node is a retransmission data packet (or the last data packet).

[0193] Optionally, the configuration response message includes at least one of the following information: Information related to GTP-U tunnel; Information related to IP address; Information related to the packet header; Identification information of the user to which the data packet belongs; Identification information of the user radio bearer to which the data packet belongs; Path identification information of the path to which the data packet belongs; Identification information of the backhaul link channel to which the data packet belongs; The identification information or address information of the destination receiving node of the data packet; Identification information or address information of the source sending node of the data packet; The identification information or address information of the node to which the data packet belongs.

[0194] Optionally, the information related to the GTP-U tunnel in the configuration response message includes at least one of the following information: The CU of the anchor node sends the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The DU of the anchor node receives the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The DU of the anchor node sends the GTP-U tunnel information of the retransmitted data packet (or the last data packet); The CU of the anchor node receives the GTP-U tunnel information of the retransmitted data packet (or the last data packet).

[0195] Optionally, the information related to the IP address in the configuration response message includes at least one of the following information: The IP address to which the anchor node's CU sends the retransmitted data packet (or the last data packet); The IP address of the anchor node's DU that receives the retransmitted data packet (or the last data packet); The IP address to which the anchor node's CU sends the retransmitted data packet (or the last data packet); The IP address of the anchor node's DU that receives the retransmitted packet (or the last packet).

[0196] Optionally, the information related to the data packet header in the configuration response message includes at least one of the following information: Indicates the location of information in a data packet sent by the CU of the anchor node to the DU of the anchor node, which is used to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicates the content of indication information included in the retransmitted data packet (or the last data packet) when the data packet sent by the CU of the anchor node to the DU of the anchor node is a retransmitted data packet (or the last data packet); Indicates the location of information in a data packet sent by the DU of the anchor node to the CU of the anchor node, which is used to indicate that the data packet is a retransmitted data packet (or the last data packet); Indicates the content of the indication information contained in the data packet when the data packet sent by the DU of the anchor node to the CU of the anchor node is a retransmission data packet (or the last data packet).

[0197] An embodiment of the present application also provides an information interaction system, which includes at least one of the devices provided in the above embodiments of the present application.

[0198] An embodiment of the present application also provides a communication network system, which includes the above-mentioned information interaction system provided in the embodiment of the present application.

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

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

[0201] In an alternative embodiment, an electronic device is provided, such as Fig.12 As shown, Fig.12 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.

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

[0203] 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.12 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.

[0204] The memory 4003 may 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 these.

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

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

[0207] 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 first node in a wireless communication system, characterized in that The method comprises: Sending a first request message to the second node, wherein the first request message includes first information about backhaul link resources; receiving a second request message from the second node, the second request message including second information about backhaul link resources; Sending a second response message to the second node; A first response message is received from the second node.

2. The method according to claim 1, characterized in that The first information includes at least one of the following information: identification information of the user involved in the first request message; The identification information of the backhaul link resources involved in the first request message.

3. The method according to claim 1 or 2, characterized in that: The first response message includes identification information of the user involved.

4. The method according to claim 1, characterized in that: The second information includes at least one of the following information: identification information of the user involved in the second request message; identification information of the backhaul link resources involved in the second request message; Information related to the QoS of the backhaul link resources requested to be modified.

5. The method according to claim 1 or 4, characterized in that: The second response message includes at least one of the following: identification information of at least one user involved in the second response message; information related to the backhaul link resources that the second node agrees to modify; Information related to the backhaul link resources that the second node disagrees with modification.

6. A method performed by a second node in a wireless communication system, characterized in that The method comprises: receiving a first request message from a first node, wherein the first request message includes first information about a backhaul link resource; Sending a second request message to the first node, where the second request message includes second information about backhaul link resources; receiving a second response message from the first node; A first response message is sent to the first node.

7. The method according to claim 6, characterized in that The first information includes at least one of the following information: identification information of the user involved in the first request message; The identification information of the backhaul link resources involved in the first request message.

8. The method according to claim 6 or 7, characterized in that: The first response message includes identification information of the user involved.

9. The method according to claim 6, characterized in that The second information includes at least one of the following information: identification information of the user involved in the second request message; identification information of the backhaul link resources involved in the second request message; Information related to the QoS of the backhaul link resources requested to be modified.

10. The method according to claim 6 or 9, characterized in that: The second response message is at least one of the following: identification information of the user involved in the second response message; information related to the backhaul link resources that the second node agrees to modify; Information related to the backhaul link resources that the second node disagrees with modification.

11. A first node in a wireless communication system, characterized in that: The first node comprises: a transceiver for sending and receiving signals; and The controller is coupled to the transceiver and configured as: Sending a first request message to the second node, wherein the first request message includes first information about backhaul link resources; receiving a second request message from the second node, the second request message including second information about backhaul link resources; Sending a second response message to the second node; A first response message is received from the second node.

12. The first node according to claim 11, characterized in that: The first information includes at least one of the following information: identification information of the user involved in the first request message; The identification information of the backhaul link resources involved in the first request message.

13. The first node according to claim 11 or 12, characterized in that: The first response message includes identification information of the user involved.

14. The first node according to claim 11, characterized in that: The second information includes at least one of the following information: identification information of the user involved in the second request message; identification information of the backhaul link resources involved in the second request message; Information related to the QoS of the backhaul link resources requested to be modified.

15. The first node according to claim 11 or 14, characterized in that: The second response message includes at least one of the following: identification information of at least one user involved in the second response message; information related to the backhaul link resources that the second node agrees to modify; Information related to the backhaul link resources that the second node disagrees with modification.

16. A second node in a wireless communication system, characterized in that: The second node comprises: a transceiver for sending and receiving signals; and The controller is coupled to the transceiver and configured as: receiving a first request message from a first node, wherein the first request message includes first information about a backhaul link resource; Sending a second request message to the first node, where the second request message includes second information about backhaul link resources; receiving a second response message from the first node; A first response message is sent to the first node.

17. The second node according to claim 16, characterized in that: The first information includes at least one of the following information: identification information of the user involved in the first request message; The identification information of the backhaul link resources involved in the first request message.

18. The second node according to claim 16 or 17, characterized in that: The first response message includes identification information of the user involved.

19. The second node according to claim 16, characterized in that: The second information includes at least one of the following information: identification information of the user involved in the second request message; identification information of the backhaul link resources involved in the second request message; Information related to the QoS of the backhaul link resources requested to be modified.

20. The second node according to claim 16 or 19, characterized in that: The second response message is at least one of the following: identification information of the user involved in the second response message; information related to the backhaul link resources that the second node agrees to modify; Information related to the backhaul link resources that the second node disagrees with modification.

Images