Method, apparatus and system for disconnecting F1 connection
Patent Information
- Application Number
- JP2023526430
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-10-30
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2040-10-30
AI Technical Summary
In the context of 3GPP Rel-16 IAB, there is a lack of optimization for tearing down source F1 connections during Inter-donor-CU handovers, leading to resource wastage and potential terminal service interruptions due to untimely or premature release of connections.
The method involves determining and sending a first message to IAB nodes to release F1 connections with the source IAB donor-CU, utilizing various communication protocols and associations to ensure timely and reliable disconnection, including IP encapsulation and timer-based mechanisms.
This approach ensures timely release of F1 connections, preventing resource wastage and service interruptions, thereby enhancing the reliability and efficiency of IAB communication.
Smart Images

Figure 0007578818000001 
Figure 0007578818000002 
Figure 0007578818000003
Abstract
Description
[Technical field]
[0001] The present application relates to the field of communications, and in particular to a method and apparatus, and system for releasing an F1 connection. [Background technology]
[0002] In 3GPP (3rd Generation Partnership Project) Rel-15 (Release-15) New Radio (NR), a gNB (next generation node base station) may use a CU (Central Unit)-DU (Distributed Unit) split architecture. Specifically, a gNB includes one gNB-CU and one or more gNB-DUs.
[0003] Two types of nodes are introduced in 3GPP Rel-15 IAB (Integrated Access and Backhaul): IAB node (called IAB node) and IAB donor (called IAB donor node or donor IAB node). The IAB donor can be a gNB.
[0004] Mobility refers to the handover of a UE (User Equipment) from one cell to another, and therefore may also be referred to generally as handover. In this application, the general term handover is used.
[0005] 3GPP Rel-16 IAB only considers Intra-donor-CU handover scenarios instead of Inter-donor-CU handover scenarios, and does not disclose an optimization solution for releasing the source F1 connection between an IAB node and a source IAB donor-CU in an Inter-donor-CU handover scenario. Summary of the Invention [Means for solving the problem]
[0006] The embodiments of the present application provide a method and apparatus, and a system for releasing an F1 connection, so that an IAB node (including a handover IAB node and a downstream IAB node of the handover IAB node) can determine that the CU of the donor node connected to the IAB node changes based on the instruction of the source IAB donor. Thus, the IAB node can release the F1 connection in a timely manner. This avoids the waste of resources caused by the F1 connection not being released in a timely manner, or the interruption of terminal service caused by the F1 connection being released early but a new F1 connection not being set up, thereby improving the reliability of releasing the F1 connection and ensuring the IAB communication performance.
[0007] According to a first aspect, an embodiment of the present application provides a method for releasing an F1 connection. The method is used for an integrated access and backhaul IAB node. The method includes: receiving a first message from a source IAB donor node, the first message indicating that a central unit CU of an IAB donor node connected to the IAB node is changing; disconnecting the F1 connection of the source IAB donor node to the CU according to the first message; Including, The source IAB donor node is an IAB donor node that is connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes.
[0008] The F1 connection between an IAB node and a CU of a source IAB donor node may be referred to as a source F1 connection.
[0009] In a possible embodiment, the first message includes first information, and the first information indicates that a CU of an IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs.
[0010] In a possible embodiment, the first message is an F1 Application Protocol F1AP message.
[0011] In a possible embodiment, the step of receiving a first message from the source IAB donor node includes: receiving a first message from the source IAB donor node via the target IAB donor node; Including, The target IAB donor node is an IAB donor node that is connected to the IAB node after the CU of the IAB donor node connected to the IAB node has changed.
[0012] In a possible embodiment, the step of receiving a first message from the source IAB donor node via the target IAB donor node includes: setting up a first TNL association with the source IAB donor node based on an IP address assigned to the IAB node by the target IAB donor node; receiving a first message from the source IAB donor node via the target IAB donor node based on the first TNL association; Includes.
[0013] In a possible embodiment, the first message further includes second information, where the second information includes an IP address assigned to the IAB node by the source IAB donor node and / or an identifier of a CU of the source IAB donor node.
[0014] In a possible embodiment, the step of receiving a first message from the source IAB donor node via the target IAB donor node includes: setting up a second TNL association with the source IAB donor node based on an IP address assigned to the IAB node by the source IAB donor node; receiving a first message from the source IAB donor node via the target IAB donor node based on the second TNL association; Includes.
[0015] In a possible embodiment, the first message includes an inner IP header and an outer IP header, where the IP address of the IAB node included in the inner IP header corresponds to a source IAB donor node, and the IP address of the IAB node included in the outer IP header corresponds to a target IAB donor node.
[0016] In a possible embodiment, the step of releasing the F1 connection of the source IAB donor node to the CU in accordance with the first message includes: starting a timer; disconnecting the F1 connection of the source IAB donor node to the CU after the timer expires; Includes.
[0017] In a possible embodiment, the first message further comprises information regarding the duration of the timer.
[0018] According to a second aspect, an embodiment of the present application provides a method for releasing an F1 connection. The method is used for a source integrated access and backhaul IAB donor node. The method includes: determining a first message, the first message indicating a change in a central unit CU of an IAB donor node connected to the IAB node; sending a first message to the IAB node to release an F1 connection between the IAB node and the CU of the source IAB donor node; Including, The source IAB donor node is an IAB donor node that is connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes.
[0019] In a possible embodiment, the first message includes first information, and the first information indicates that a CU of an IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs.
[0020] In a possible embodiment, the first message is an F1 Application Protocol F1AP message.
[0021] In a possible embodiment, the step of sending the first message to the IAB node comprises: Sending a first message to the IAB node via the target IAB donor node. Including, The target IAB donor node is an IAB donor node that is connected to the IAB node after the CU of the IAB donor node connected to the IAB node has changed.
[0022] In a possible embodiment, the step of transmitting the first message to the IAB node via the target IAB donor node comprises: setting up a first TNL association with an IAB node, the first TNL association corresponding to an IP address assigned to the IAB node by the target IAB donor node; sending a first message to the IAB node via the target IAB donor node based on the first TNL association; Includes.
[0023] In a possible embodiment, the first message further includes second information, where the second information includes an IP address assigned to the IAB node by the source IAB donor node and / or an identifier of a CU of the source IAB donor node.
[0024] In a possible embodiment, the step of transmitting the first message to the IAB node via the target IAB donor node comprises: setting up a second TNL association with the IAB node, the second TNL association corresponding to an IP address assigned to the IAB node by the source IAB donor node; sending the first message to the IAB node via the target IAB donor node based on the second TNL association; Includes.
[0025] In a possible embodiment, the method comprises the steps of: sending an IP address assigned to the IAB node by the source IAB donor node to a CU of the target IAB donor node, where the IP address assigned to the IAB node by the source IAB donor node is used to determine a mapping relationship; Further comprising: A mapping relationship is a correspondence between an IP address assigned to an IAB node by a source IAB donor node and a Backhaul Adaptation Protocol (BAP) address assigned to an IAB node by a target IAB donor node.
[0026] In a possible embodiment, the first message includes an inner IP header and an outer IP header, where the IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and the IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node.
[0027] In a possible embodiment, the first message further comprises information regarding the duration of the timer.
[0028] According to a third aspect, an embodiment of the present application provides an apparatus for releasing an F1 connection. The apparatus is used in an integrated access and backhaul IAB node. The apparatus includes: a receiving module configured to receive a first message from a source IAB donor node, the first message indicating a change in a central unit CU of an IAB donor node connected to the IAB node; a disconnection module configured to disconnect the F1 connection of the source IAB donor node to the CU according to the first message; Including, The source IAB donor node is an IAB donor node that is connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes.
[0029] According to a fourth aspect, an embodiment of the present application provides an apparatus for releasing an F1 connection. The apparatus is used in a source integrated access and backhaul IAB donor node. The apparatus includes: a determining module configured to determine a first message, the first message indicating that a CU of an IAB donor node connected to the IAB node is to change; a sending module configured to send a first message to the IAB node to release an F1 connection between the IAB node and the CU of the source IAB donor node; Including, The source IAB donor node is an IAB donor node that is connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes.
[0030] According to a fifth aspect, an embodiment of the present application provides a communications device, the communications device including a processor coupled to a memory configured to store computer instructions, the processor configured to execute the computer instructions to perform the method according to the first aspect.
[0031] According to a sixth aspect, an embodiment of the present application provides a communications device, the communications device including a processor coupled to a memory configured to store computer instructions, the processor configured to execute the computer instructions to perform the method according to the second aspect.
[0032] According to a seventh aspect, an embodiment of the present application provides a communication system. The communication system includes two or more of an IAB node, a source IAB donor node, and a target IAB donor node. The IAB node is configured to perform the method according to the first aspect, and the source IAB donor node is configured to perform the method according to the second aspect.
[0033] According to an eighth aspect, an embodiment of the present application provides a computer storage medium, the computer storage medium comprising computer instructions, the computer instructions, when executed, causing a method according to the first aspect to be performed.
[0034] According to a ninth aspect, an embodiment of the present application provides a computer storage medium, the computer storage medium comprising computer instructions, the computer instructions, when executed, causing a method according to the second aspect to be performed.
[0035] According to a tenth aspect, an embodiment of the present application provides an apparatus. The apparatus is configured to execute the method according to the first and second aspects. The embodiment of the present application provides a method, an apparatus, and a system for releasing an F1 connection. A first message is determined, the first message indicates that a CU of an IAB donor node connected to the IAB node is changed, and the first message is sent to the IAB node. In this manner, the IAB node releases the F1 connection to the CU of the source IAB donor node according to the first message. Thus, the IAB node releases the source F1 connection in a timely manner based on the instruction of the source IAB donor. This avoids the waste of resources caused by the F1 connection not being released in a timely manner, or the communication interruption caused by the F1 connection being released early, thereby improving the reliability and efficiency of releasing the source F1 connection. [Brief description of the drawings]
[0036] [Figure 1] 1 is a schematic diagram of a CU-DU division structure. [Diagram 2] A schematic diagram of a control plane protocol stack in a CU-DU split structure. [Diagram 3] 1 is a schematic diagram of a user plane protocol stack in a CU-DU split structure. [Figure 4] FIG. 1 is a schematic diagram of a two-hop data backhaul scenario. [Diagram 5] FIG. 1 is a schematic diagram of a control plane protocol stack for two-hop data backhaul. [Figure 6] FIG. 1 is a schematic diagram of a user plane protocol stack for two-hop data backhaul. [Figure 7] FIG. 1 is a schematic diagram of an Intra-CU handover scenario. [Figure 8] FIG. 1 is a schematic diagram of an Intra-CU handover procedure. [Figure 9] FIG. 2 is a schematic diagram of an Inter-CU handover scenario according to an embodiment of the present application; [Figure 10]FIG. 13 is a schematic diagram of another Inter-CU handover scenario according to an embodiment of the present application; [Figure 11] FIG. 13 is a schematic diagram of yet another Inter-CU handover scenario according to an embodiment of the present application; [Figure 12] FIG. 2 is a schematic diagram of a method for releasing an F1 connection according to an embodiment of the present application; [Figure 13] FIG. 2 is a schematic diagram of a method for releasing an F1 connection according to an embodiment of the present application; [Figure 14] FIG. 2 is a schematic diagram of a protocol stack architecture according to an embodiment of the present application; [Figure 15] FIG. 2 is a schematic diagram of a method for releasing an F1 connection according to an embodiment of the present application; [Figure 16] FIG. 2 is a schematic diagram of a protocol stack architecture according to an embodiment of the present application; [Figure 17] FIG. 2 is a schematic diagram of a method for releasing an F1 connection according to an embodiment of the present application; [Figure 18] 4 is a schematic flowchart of a method for releasing an F1 connection according to an embodiment of the present application; [Figure 19] 4 is a schematic flowchart of a method for releasing an F1 connection according to an embodiment of the present application; [Figure 20] FIG. 2 is a schematic diagram of the structure of an apparatus for releasing an F1 connection according to an embodiment of the present application; [Figure 21] FIG. 2 is a schematic diagram of the structure of an apparatus for releasing an F1 connection according to an embodiment of the present application; [Figure 22] 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present application; [Figure 23] 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0037] The following describes the technical solutions of the embodiments in the present application with reference to the accompanying drawings. Obviously, the described embodiments are only some, but not all, of the embodiments of the present application.
[0038] In the description herein, the phrases "one embodiment" or "some embodiments" and the like indicate that one or more embodiments of the present application include a particular feature, structure, or characteristic that is described with reference to the embodiment. Thus, statements such as "in one embodiment," "in some embodiments," "in some other embodiments," and "in other embodiments" appearing in different places in the specification do not necessarily mean to refer to the same embodiment. Instead, unless specifically emphasized otherwise, these statements mean "one or more, but not all, embodiments."
[0039] In the description of this specification, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. In this specification, "and / or" describes only the association relationship between associated objects and represents that three relationships may exist. For example, A and / or B may represent the following three cases: only A exists, both A and B exist, and only B exists. In addition, in the description of the embodiments of this application, "multiple" means two or more.
[0040] In the description herein, the terms "first" and "second" are for descriptive purposes only and should not be understood as an indication or implication of relative importance or an implicit indication of the number of technical features depicted. Thus, a feature qualified by "first" or "second" may explicitly or implicitly include one or more features. The terms "including," "having," and variations thereof all mean "including but not limited to," unless specifically emphasized otherwise.
[0041] In 3GPP Rel-15 NR, the gNB may use a CU-DU split architecture. Specifically, the gNB includes one gNB-CU and one or more gNB-DUs. As shown in Figure 1, one gNB-DU can be connected to only one gNB-CU. In addition, the gNB-CU is connected to the gNB-DU via an F1 interface, and the gNB-CU is connected to the 5GC via an NG interface.
[0042] A gNB may be a node that provides NR (New Radio) user plane and control plane transmission to a UE (User equipment), and contains one or more cells. A gNB is connected to a 5GC (5G Core) network via an NG interface and to another gNB via an Xn interface. The Xn-C interface is used for control plane signaling transmission between two gNBs, and the Xn-U interface is used for user plane data transmission between two gNBs. The interface between a gNB and a UE is called a Uu interface.
[0043] The gNB-CU may be a logical node including the RRC (Radio Resource Control) layer, the SDAP (Service Data Adaptation Protocol) layer, and the PDCP (Packet Data Convergence Protocol) layer of a gNB, or including the RRC layer and the PDCP layer of an en-gNB, and is configured to control one or more gNB-DUs.
[0044] A gNB-DU (Distributed Unit) can be a logical node that includes the RLC (Radio Link Control), MAC (Media Access Control), and PHY (Physical) layers of a gNB or en-gNB. One gNB-DU supports one or more cells, but one cell can belong to only one gNB-DU.
[0045] The UE accesses the gNB-CU through the gNB-DU. Specifically, the UE's peer PHY / MAC / RLC layer functions are located in the gNB-DU, and the UE's peer PDCP / SDAP / RRC layer functions are located in the gNB-CU.
[0046] As shown in Figure 2, for the CP (Control Plane), in the UL (Uplink) direction, the gNB-DU encapsulates the RRC message generated by the UE into an F1AP (F1 Application Protocol) message of the F1 interface, and sends the F1AP message to the gNB-CU. In the DL (Downlink) direction, the gNB-CU encapsulates the RRC message into an F1AP message and sends the F1AP message to the gNB-DU, and the gNB-DU extracts the RRC message from the F1AP message, maps the RRC message to a SRB (Signaling Radio Bearer) corresponding to the Uu interface, and sends the SRB to the UE. The SRB can be SRB0 / SRB1 / SRB2, etc.
[0047] As shown in Figure 3, for UP (User Plane), in the UL direction, the gNB-DU maps the UE's data packets received from the DRB (Data Radio Bearer) on the Uu interface to the corresponding GTP (General packet radio service Tunneling Protocol) tunnel, and sends the GTP tunnel to the gNB-CU. In the DL direction, the gNB-CU maps the UE's data packets to the corresponding GTP tunnel, and sends the GTP tunnel to the gNB-DU, and the gNB-DU extracts the UE's data packets from the GTP tunnel, maps the UE's data packets to the DRB corresponding to the Uu interface, and sends the DRB to the UE.
[0048] Two types of nodes are introduced in 3GPP Rel-15 IAB: IAB node (referred to as IAB node) and IAB donor (referred to as IAB donor node or donor IAB node). The IAB donor may be a gNB.
[0049] As shown in Figure 4, a two-hop data backhaul scenario is used as an example. Backhaul is called BH for short. The IAB network uses a CU-DU split architecture. In other words, the IAB donor includes two parts: IAB donor-CU (called donor-CU for short) and IAB donor-DU (called donor-DU for short), and the IAB node includes two parts: IAB node-MT (called IAB-MT for short) and IAB node-DU (called IAB-DU for short). The IAB node-MT (Mobile Terminal) can also be called IAB node-UE (called IAB-UE for short).
[0050] In the case of an IAB donor, the functions of the donor-DU are similar to those of the gNB-DU, and the functions of the donor-CU are similar to those of the gNB-CU.
[0051] For an IAB node, the function of the IAB-DU is similar to that of the gNB-DU, and the IAB-DU is configured to provide access services to a child node of the IAB-DU. The child node of the IAB-DU may be a UE or another IAB node. The IAB-MT has the function of a UE and is configured to provide data backhaul to a child node of the co-site IAB-DU (i.e., the IAB-DU and IAB-MT belong to the same IAB node).
[0052] In addition, IAB nodes can be further classified into access IAB nodes and intermediate IAB nodes. Specifically, an IAB node accessed by a UE is called an access IAB node, and an IAB node on the path between an access IAB node and an IAB donor is called an intermediate IAB node. For example, as shown in FIG. 4, a UE accesses IAB node2. IAB node2 is called the access IAB node of the UE (or the parent node of the UE), the UE is called the child node of IAB node2, and the link between the UE and IAB node2 is called an access link. IAB node1 is called an intermediate IAB node. The parent node of IAB node1 is the IAB donor (the child node of IAB donor is IAB node1). The child node of IAB node1 is IAB node2 (the parent node of IAB node2 is IAB node1). The links between IAB node1 and IAB node2 and the links between IAB node1 and IAB donor are all called backhaul links. The UE's peer PHY, MAC, and RLC layers are located in the access IAB node (i.e., IAB2-DU), and the UE's peer PDCP, SDAP, and RRC layers are located in the donor-CU. Both IAB nodes use an L2 data forwarding architecture. The following shows the specific user plane protocol stack and the specific control plane protocol stack.
[0053] Figure 5 shows the control plane protocol stack for two-hop data backhaul. An F1 interface is established between the access IAB node (i.e., IAB2-DU) and the IAB donor (i.e., donor-CU). Specifically, if the IAB donor uses a CP-UP split architecture, an F1-C interface is established between the IAB2-DU and the donor CU-CP. The UE's RRC message is encapsulated into an F1AP message on the F1-C interface for transmission.
[0054] Figure 6 shows the user plane protocol stack for two-hop data backhaul. When the IAB donor uses the CP-UP split architecture, an F1-U interface is established between the IAB2-DU and the donor CU-UP, and a GTP tunnel per UE bearer is established on the F1-U interface. In other words, each UE DRB established on the interface between the UE and IAB2-DU corresponds to a separate GTP tunnel on the interface between the IAB2-DU and the donor CU-UP.
[0055] Mobility refers to the handover of a UE from one cell to another. Therefore, mobility can also be generally referred to as handover or migration, which are collectively referred to as handover in this application.
[0056] In 3GPP Rel-16 IAB, only the Intra-donor-CU handover scenario is considered, and the Inter-donor-CU handover scenario is not considered.
[0057] Intra-donor-CU handover refers to handover within the same donor-CU. Inter-donor-CU handover refers to handover between different donor-CUs. That is, during an Intra-donor-CU handover, the donor-CU remains the same and the handover is performed within the donor-CU. During an Inter-donor-CU handover, the donor-CU changes.
[0058] As shown in Figure 7, in an Intra-donor-CU handover scenario, an example in which an IAB node directly connected to an IAB donor is handed over is used for explanation. The handed over IAB node may be called a handover IAB node or a migration IAB node, which are collectively referred to as handover IAB nodes in this application.
[0059] This scenario can also be extended to a multi-hop scenario, where there is at least one other IAB node between the handover IAB node and the IAB donor.
[0060] The handover IAB node includes two parts: IAB-MT and IAB-DU. In this embodiment, the IAB-MT of the handover IAB node is collectively referred to as the handover IAB-MT, and the IAB-DU of the handover IAB node is collectively referred to as the handover IAB-DU. The downstream node of the handover IAB node includes the child node, the grandchild node (the child node of the child node), and the descendant node of the grandchild node, etc. of the handover IAB node. The downstream node may be another IAB node or a UE.
[0061] Similar to the UE, before the IAB-MT handover, the IAB-MT is connected to the source IAB donor, i.e., connected to the IAB donor-CU via IAB donor-DU1. After the IAB-MT handover, the IAB-MT is connected to the target IAB donor, i.e., connected to the IAB donor-CU via IAB donor-DU2.
[0062] Since the IAB donor-CU remains unchanged before and after the IAB-MT handover, the F1 connection between the IAB-DU and the IAB donor-CU remains unchanged.
[0063] The IP address (Internet Protocol Address) of the IAB-DU is assigned by the IAB donor-DU. That is, the IP address of the IAB-DU and the IP address of the IAB donor-DU belong to the same network segment or have the same network prefix. Therefore, when the IAB donor-DU changes, the IP address of the IAB-DU changes.
[0064] Figure 8 is a schematic diagram of an IAB Intra-donor-CU handover procedure. A multi-hop scenario (there is at least one other IAB node between the handover IAB node and the IAB donor-DU) is used as an example. The source route is the transmission path between the source parent node and the source IAB donor-DU. The target route is the transmission path between the target parent node and the target IAB donor-DU. The handover procedure is specifically as follows:
[0065] 8-1: The handover IAB-MT sends an RRC message (ie, a MeasurementReport message) to the IAB-DU of the source parent node. The MeasurementReport message is a measurement report message.
[0066] 8-2: The IAB-DU of the source parent node sends an F1AP message (ie, a UL RRC Message Transfer message) to the IAB donor-CU, and the message carries a Measurement Report message. The UL RRC Message Transfer message is a UL RRC message transfer message.
[0067] 8-3: The IAB donor-CU sends an F1AP message (i.e., a UE Context Setup Request message) to the IAB-DU of the target parent node of the handover IAB node to set up context information of the handover IAB-MT on the target parent node. The UE Context Setup Request message is a UE context setup request message.
[0068] 8-4: The IAB-DU of the target parent node sends an F1AP message (ie, a UE Context Setup Response message) to the IAB donor-CU in response. The UE Context Setup Response message is a UE context setup response message.
[0069] 8-5: The IAB donor-CU sends an F1AP message (ie, a UE Context Modification Request message) to the IAB-DU of the source parent node, which carries an RRC Reconfiguration message. The UE Context Modification Request message is a UE context modification request message. The RRC Reconfiguration message is an RRC reconfiguration message.
[0070] The RRCReconfiguration message includes the configuration of the default BH RLC channel (default bearer) and default BAP routing ID (default route) used by the handover IAB-MT to carry UL F1-C / non-F1 services on the target path. The F1-C services refer to UE-associated F1AP messages and Non-UE associated F1AP messages, and the non-F1 services refer to application layer messages established by IPsec (Internet Protocol Security), SCTP (Stream Control Transmission Protocol) association, or OAM (Operation Administration and Maintenance) services, etc.
[0071] When the IAB donor-DU changes, the RRCReconfiguration message may further include the IP address assigned to the handover IAB node (or handover IAB-DU) by the target IAB donor-DU.
[0072] 8-6: The IAB-DU of the source parent node forwards the received RRCReconfiguration message to the handover IAB-MT.
[0073] 8-7: The IAB-DU of the source parent node sends an F1AP message (ie, a UE Context Modification Response message) to the IAB donor-CU in response. The UE Context Modification Response message is a UE context modification response message.
[0074] 8-8: Handover The IAB-MT initiates a random access procedure to the IAB-DU of the target parent node.
[0075] 8-9: The handover IAB-MT sends an RRCReconfigurationComplete message to the IAB-DU of the target parent node. The RRCReconfigurationComplete message is an RRC reconfiguration completion message.
[0076] 8-10: The IAB-DU of the target parent node sends a UL RRC Message Transfer message to the IAB donor-CU. This message carries the RRCReconfigurationComplete message.
[0077] 8-11: The IAB donor-CU configures the corresponding BH RLC channel and BAP route configuration for the target path of the handover IAB node, and configures DL bearer mapping on the target IAB donor-DU for the handover IAB node. This configuration process may be performed in advance, for example, immediately after step (8-3).
[0078] 8-12: The F1-C connection is updated with the new IP address of the handover IAB-DU, and the IAB donor-CU updates the UL BH information associated with each GTP tunnel to the handover IAB node, i.e., all F1-U tunnels are updated with the new IP address of the handover IAB-DU.
[0079] 8-13: The IAB donor-CU sends an F1AP message (ie, a UE Context Release Command message) to the IAB-DU of the source parent node. The UE Context Release Command message is a UE context release request message.
[0080] 8-14: The IAB-DU of the source parent node releases the context of the handover IAB-MT and sends a F1AP message (UE Context Release Complete message) to the IAB donor-CU in response. The UE Context Release Complete message is a UE context release completion message.
[0081] 8-15: The IAB donor-CU releases the BH RLC channel and BAP route configuration information on the source route between the source parent node and the source IAB donor-DU.
[0082] In an Intra-donor-CU handover scenario, it may be known that the F1 connection between the handover IAB-DU and the IAB donor-CU remains unchanged, and similarly, the F1 connection between a downstream node (e.g., another IAB node) of the handover IAB node and the IAB donor-CU also remains unchanged. In other words, the handover IAB node, or a child IAB node of the handover IAB node, etc., does not need to release the F1 connection to the IAB donor-CU.
[0083] However, the Inter-donor-CU handover scenario is also a typical handover scenario. In this scenario, the IAB donor-CU changes, and as a result, the F1 connection to the handover IAB-DU changes (in the current standard, one DU can be connected to one CU to set up one F1 connection). Specifically, before the handover, the handover IAB-DU sets up an F1 connection to the source IAB donor-CU. After the handover, the handover IAB-DU needs to set up an F1 connection to the target IAB donor-CU and release the F1 connection to the source IAB donor-CU. Similarly, the F1 connection between the downstream node (e.g., another IAB node) of the handover IAB node and the IAB donor-CU also changes. Specifically, the downstream node needs to release the F1 connection to the source IAB donor-CU.
[0084] Therefore, the present application provides a method and apparatus, and a system for releasing an F1 connection, to solve the problem of an IAB node releasing an F1 connection to a source IAB donor-CU in an Inter-donor-CU handover scenario. The IAB nodes include a handover IAB node and a downstream IAB node of the handover IAB node.
[0085] The application scenarios of this application mainly include:
[0086] Before the IAB-MT handover, the handover IAB-MT is connected to the source IAB donor-CU (e.g., IAB donor-CU1 in FIG. 9) via the source IAB donor-DU (e.g., IAB donor-DU1 in FIG. 9). After the IAB-MT handover, the handover IAB-MT is connected to the target IAB donor-CU (e.g., IAB donor-CU2 in FIG. 9) via the target IAB donor-DU (e.g., IAB donor-DU2 in FIG. 9).
[0087] The downstream node of the handover IAB node may be a UE or another IAB node.
[0088] The above scenario can be further expanded. Specifically, there is at least one other IAB node between the handover IAB node and the IAB donor-DU. As shown in Figure 10, before the handover, IAB node1 and IAB node2 are other IAB nodes (which may be called intermediate IAB nodes) between the handover IAB node and the source IAB donor-DU (e.g., IAB donor-DU1 in Figure 10), and IAB node3 and IAB node4 are other IAB nodes (which may be called intermediate IAB nodes) between the handover IAB node and the target IAB donor-DU (e.g., IAB donor-DU2 in Figure 10).
[0089] In addition, the above scenario can be further expanded, specifically including the following two cases (examples), as shown in Figure 11:
[0090] Case 1: Before handover, the handover IAB-MT is directly connected to the source IAB donor-DU. After handover, the handover IAB-MT is connected to the target IAB donor-DU via at least one other IAB node.
[0091] Case 2: Before handover, the handover IAB-MT is connected to the source IAB donor-DU via at least one other IAB node. After handover, the handover IAB-MT is directly connected to the target IAB donor-DU.
[0092] In all of the above handover scenarios, the path between the handover IAB-MT and the source IAB donor-CU (e.g., IAB donor-CU1 in Figures 9 to 11) is called the source path (i.e., Source Path), and the path between the handover IAB-MT and the target IAB donor-CU (e.g., IAB donor-CU2 in Figures 9 to 11) is called the target path (i.e., Target Path). Alternatively, the path between the handover IAB-MT and the source IAB donor-DU (e.g., IAB donor-DU1 in Figures 9 to 11) is called the source path, and the path between the handover IAB-MT and the target IAB donor-DU (e.g., IAB donor-DU2 in Figures 9 to 11) is called the target path.
[0093] The network elements in this application include an IAB node and an IAB donor. The IAB node includes an IAB node-DU (abbreviated as IAB-DU) and an IAB node-MT (abbreviated as IAB-MT). The IAB donor includes an IAB donor-CU (abbreviated as Donor-CU) and an IAB donor-DU (abbreviated as Donor-DU).
[0094] In the case of the IAB donor, the function of the donor-DU is similar to that of the gNB-DU, and the donor-DU mainly performs the functions of the L1 and L2 protocol stacks, including the functions of the PHY layer, MAC layer, and RLC layer. The function of the donor-CU is similar to that of the gNB-CU, and the donor-CU mainly performs the functions of the PDCP layer, SDAP layer, and RRC layer.
[0095] For IAB nodes, the function of the IAB-DU is similar to that of the gNB-DU, and the IAB-DU is configured to provide access services to child nodes of the IAB-DU. The child nodes of the IAB-DU may be UEs or other IAB nodes. The IAB-MT has the function of a UE and is configured to provide data backhaul to child nodes of the co-site IAB-DU.
[0096] In the following, a description is provided using a specific embodiment.
[0097] If RAN (Radio Access Network) sharing (specifically, one RAN device is shared by different operators) is not considered, one DU can be connected to only one CU. In an Inter-donor-CU handover scenario, an IAB donor connected to an IAB node is handed over from a source IAB donor to a target IAB donor. Thus, the IAB node needs to set up an F1 connection to the target IAB donor and delete / release the F1 connection to the source IAB donor. The IAB nodes include the handover IAB node and downstream IAB nodes of the handover IAB node (e.g., a child node, a grandchild node, or a descendant node of a grandchild node).
[0098] The present application will be described using the handover scenario of Figure 9 as an example. The solutions provided in the present application are also applicable to the handover scenarios of Figures 10 and 11.
[0099] In the IAB scenario, the IAB node includes IAB-MT and IAB-DU, and the source IAB donor includes source IAB donor-DU and source IAB donor-CU. When an IAB node deletes / releases an F1 connection to a source IAB donor, it means that the IAB-DU deletes / releases an F1 connection to a source IAB donor-CU. Here, the F1 connection between the IAB-DU and the source IAB donor-CU is called a source F1 connection. Specifically, the following several solutions are included:
[0100] Solution 1: The source IAB donor explicitly indicates to the IAB node to remove / disconnect the source F1 connection.
[0101] In a possible embodiment, scheme 1, The source IAB donor may indicate to the IAB node via the target IAB donor to delete / release the source F1 connection.
[0102] As shown in Figure 12, after the IAB-MT handover is completed, for example, after the source IAB donor-CU receives a UE Context Release message sent by the target IAB donor, the source IAB donor-CU sends an F1AP message to the IAB-DU via the target IAB donor. After receiving the message, the IAB-DU deletes / releases the source F1 connection. The F1AP message may be an F1AP message, for example, an F1 Removal Request message, or may be a newly defined F1AP message.
[0103] Optionally, the F1AP message may carry indication information 1. The indication information 1 indicates that the donor-CU is changed / updated or that an inter-CU is handed over, which causes the IAB-DU to subsequently trigger the setup of an F1 connection to the target IAB donor-CU.
[0104] In order to assist the target IAB donor in performing correct routing and / or bearer mapping for F1AP messages sent by the source IAB donor-CU to the IAB-DU, before the source IAB donor-CU indicates to the IAB-DU via the target IAB donor to remove / release the source F1 connection, the target IAB donor-CU sends to the source IAB donor-CU the mapping relationship between the UE-associated (User equipment-associated) F1AP type indication and the DSCP (Differentiated Services Code Point) / flow label and / or the mapping relationship between the Non-UE-associated F1AP type indication and the DSCP / flow label. Specifically, the target IAB donor-CU sends the following information to the source IAB donor-CU: Send one or both of an F1AP type indication and a DSCP / flow label, where the F1AP type indication includes a UE-associated F1AP type indication and / or a Non-UE-associated F1AP type indication, and the F1AP type indication corresponds to the DSCP / flow label.
[0105] The source IAB donor-CU indicates to the IAB-DU to delete / release the source F1 connection via the target IAB donor. Specifically, the F1AP message sent by the source IAB donor-CU to the IAB-DU is encapsulated in an IP packet and routed to the IAB-DU via the target IAB donor-DU. Some specific implementations include the following:
[0106] Method 1-1: A newly set up TNL (Transport Network Layer), that is, a first TNL association, is used.
[0107] Specifically, the F1AP message is sent based on the newly set up TNL association between the IAB-DU and the source IAB donor-CU.
[0108] In method 1-1, when the IAB-DU obtains the IP address assigned to the IAB-DU by the target IAB donor, the IAB-DU newly sets up a TNL association with the source IAB donor-CU, i.e., the IP address corresponding to the newly set up TNL association includes the IP address of the source IAB donor-CU and the IP address assigned to the IAB node by the target IAB donor.
[0109] It should be noted that in this application, the IP address assigned to the IAB node by the IAB donor is used by the IAB-DU.
[0110] Optionally, after receiving the F1AP message sent by the source IAB donor-CU based on the newly set up TNL association, the F1AP message may further carry the indication information 2, as shown in FIG. 13, to enable the IAB-DU to delete the F1 connection between the IAB-DU and the source IAB donor-CU. The indication information 2 may implicitly or explicitly indicate to delete the source F1 connection. For example, the indication information 2 may be an IP address assigned to the IAB node by the source IAB donor, an identifier of the source IAB donor-CU (e.g., source IAB donor-CU name), or indication information indicating (explicitly indicating) to delete the source F1 connection. The IAB-DU deletes the F1 connection corresponding to the indication information based on the indication information 2. In addition, a protocol stack architecture corresponding to the above-mentioned method 1-1 is shown in FIG. 14.
[0111] Method 1-2: The old TNL (i.e., the second TNL association) is used.
[0112] Specifically, the F1AP message is sent based on the old TNL association between the IAB-DU and the source IAB donor-CU.
[0113] In method 1-2, the IP addresses corresponding to the old TNL association set up between the IAB-DU and the source IAB donor-CU include the IP address of the source IAB donor-CU and the IP address assigned to the IAB node by the source IAB donor.
[0114] As shown in FIG. 15, in order to enable the target IAB donor-DU to perform corresponding routing and bearer mapping based on the IP packets received from the source IAB donor-CU, the source IAB donor-CU needs to send the IP address assigned to the IAB node by the source IAB donor to the target IAB donor-CU, and the target IAB donor-CU configures a mapping relationship between the IP address assigned to the IAB node by the source IAB donor and the BAP address assigned to the IAB node by the target IAB donor-CU, and sends the mapping relationship to the target IAB donor-DU. Specifically, the target IAB donor-CU sends the IP address assigned to the IAB node by the source IAB donor and the BAP address assigned to the IAB node by the target IAB donor-CU to the target IAB donor-DU, and there is a correspondence relationship between the IP address assigned to the IAB node by the source IAB donor and the BAP address assigned to the IAB node by the target IAB donor-CU. In addition, the protocol stack architecture corresponding to the above-mentioned method 1-2 is the same as the protocol stack architecture corresponding to the above-mentioned method 1-1.
[0115] Scheme 1-3: An IP-in-IP transmission scheme is used, that is, IP encapsulation is performed twice.
[0116] As shown in Figure 16, IP encapsulation is performed twice for the F1AP message sent by the source IAB donor-CU to the IAB-DU. Downlink data transmission is used as an example. During the first IP (called outer IP for ease of explanation) encapsulation, the destination IP address is the IP address assigned to the IAB node by the source IAB donor, and the source IP address is the IP address of the source IAB donor-CU. During the second IP (called inner IP for ease of explanation) encapsulation, the destination IP address is the IP address assigned to the IAB node by the target IAB donor, and the source address is the IP address of the source IAB donor-CU.
[0117] In order to allow the source IAB donor-CU to know the IP address assigned to the IAB node by the target IAB donor, the target IAB donor-CU needs to send the IP address assigned to the IAB node by the target IAB donor to the source IAB donor-CU.
[0118] In another possible embodiment, scheme 2, The source IAB donor may directly indicate to the IAB node to delete / release the source F1 connection via the source route. As shown in FIG. 17, before the IAB-MT receives the handover command (or before the handover is executed), the source IAB donor-CU sends an F1AP message to the IAB-DU. After receiving the message, the IAB-DU deletes / releases the source F1 connection. The F1AP message may be an F1AP message, for example, an F1 Removal Request message, or a newly defined F1AP message. Optionally, the F1AP message may further carry an indication information 1. The indication information 1 indicates that the donor-CU is changed / updated or that an inter-CU is handed over, which causes the IAB-DU to subsequently trigger the setup of an F1 connection to the target IAB donor-CU.
[0119] Solution 2: Implicitly tell the IAB node to remove / disconnect the source F1 connection.
[0120] In a possible embodiment, after the IAB-MT receives the handover command (i.e., when the RRC reconfiguration message carries the ReconfigurationWithSync parameter), the IAB-MT notifies the IAB-DU via the internal interface, which causes the IAB-DU to automatically delete / release the source F1 connection.
[0121] In a possible embodiment, after the IAB-DU receives the new configuration or after the new configuration of the IAB-DU is activated, the IAB-DU automatically deletes / releases the source F1 connection. The new configuration is the configuration of the IAB-DU connected to the target IAB donor and includes at least one of the following information: a new cell identity (e.g., Cell identity or CGI (Cell Global Identity)) of the cell of the IAB-DU connected to the target IAB donor, and a system broadcast message of the cell of the IAB-DU. Optionally, the IAB-DU may obtain the new configuration from the OAM server or the IAB-DU may obtain the new configuration from the target IAB donor.
[0122] In a possible embodiment, the source IAB donor or the target IAB donor configures a timer in the IAB node. After the timer expires, the IAB-DU automatically deletes / releases the source F1 connection. Specifically, there are several possibilities for the IAB node to start the timer, including when the IAB-MT receives a handover command or when the IAB-DU receives a new configuration, the IAB node starts the timer, and the IAB-DU automatically deletes / releases the source F1 connection after the timer expires.
[0123] Next, Figure 18 is a schematic flowchart of a method for releasing an F1 connection according to an embodiment of the present application. The method for releasing an F1 connection may be used for a source IAB donor node. The source IAB donor node includes a source donor-CU and a source donor-DU, for example, an IAB donor-CU1 and an IAB donor-DU1 in any of the Inter-CU handover scenarios of Figures 9 to 11. As shown in Figure 18, the method for releasing an F1 connection may include the following steps.
[0124] S181: Determine a first message, where the first message indicates that a CU of an IAB donor node connected to an IAB node is changed.
[0125] Specifically, the source IAB donor node may be an IAB donor node connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes.
[0126] The IAB node may be a handover IAB node or a downstream node of the handover IAB node. The downstream node of the handover IAB node may include a child node, a grandchild node (a child node of a child node), and a descendant node of a grandchild node, etc. of the handover IAB node. In addition, the downstream node may be another IAB node or a UE. The source IAB donor node may perform a handover decision based on the measurement result reported by the handover IAB node to determine whether the handover IAB node needs to be handed over from the source IAB donor node to the target IAB donor node. Thus, the source IAB donor node may determine whether the CU of the IAB donor node connected to the IAB node changes based on the decision result.
[0127] In one embodiment, the message name of the first message may implicitly indicate that the CU of the IAB donor node connected to the IAB node is changed. For example, the first message is an F1 Removal Request message or a newly defined message (e.g., F1 Release Request message).
[0128] In another embodiment, the information carried in the first message explicitly or implicitly indicates that the CU of the IAB donor node connected to the IAB node changes. For example, the first message includes first information, and the first information indicates that the CU of the IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs. For example, the first information may be the indication information 1 shown in FIG. 12.
[0129] In another embodiment, the first message may be an F1AP message. The F1AP message may be an F1AP message, for example, an F1 Removal Request message, or may be a newly defined F1AP message. Optionally, the F1AP message may carry first information, and the first information indicates that a CU of an IAB donor node connected to an IAB node changes or an inter-donor CU handover occurs.
[0130] In another embodiment, the first message may be a handover command generated by the target IAB donor node (i.e., the RRC reconfiguration message carries the ReconfigurationWithSync parameter). The handover command carries first information, where the first information indicates that a CU of the IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs.
[0131] In another embodiment, the first message may be a message for configuring configuration information of the DU of the IAB node connected to the target IAB donor node. The configuration information may include a new cell identity (e.g., Cell identity or CGI) of the cell of the IAB-DU connected to the target IAB donor, and / or a system broadcast message of the cell of the IAB-DU. The configuration information may implicitly indicate that the CU of the IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs. Optionally, the configuration information may be provided by an OAM server or by the target IAB donor node.
[0132] In another embodiment, the first message may further include information about the duration of the timer. The duration of the timer may be configured by the source IAB donor node, or may be configured by the target IAB donor node, or may be pre-specified in the communication protocol. Specifically, after receiving the first message, the IAB node starts a timer, and then releases the F1 connection to the CU of the source IAB donor node after the timer expires. In this way, the IAB node reserves a certain processing time before releasing the F1 connection, which can improve the reliability of releasing the F1 connection.
[0133] S182: Send a first message to the IAB node to release the F1 connection between the IAB node and the CU of the source IAB donor node.
[0134] Specifically, an F1 connection between an IAB node and a CU of a source IAB donor node may be referred to as a source F1 connection for short, and an F1 connection between an IAB node and a CU of a target IAB donor node may be referred to as a target F1 connection for short.
[0135] In one embodiment, the source IAB donor may send a first message to the IAB node via the source route. For example, before the IAB node is handed over from the source route to the target route, the source IAB donor may send a first message to the IAB node via the source route. For example, as shown in Figure 17, before the IAB-MT receives the handover command (or before the handover is executed), the source IAB donor-CU sends an F1AP message to the IAB-DU. After receiving the message, the IAB-DU deletes / releases the source F1 connection.
[0136] In another embodiment, the source IAB donor node may send the first message to the IAB node via the target IAB donor node. For example, after the IAB node is handed over from the source path to the target path, the source IAB donor node may send the first message to the IAB node via the target IAB donor node.
[0137] The target IAB donor node may be an IAB donor node connected to the IAB node after the CU of the IAB donor node connected to the IAB node has changed, for example, IAB donor-CU2 and IAB donor-DU2 in any of the Inter-CU handover scenarios of Figures 9 to 11. In this application, the source IAB donor node transmits the first message to the IAB node via the target IAB donor node specifically means that the source IAB donor node transmits the first message to the IAB node via the target IAB donor-DU (IAB donor-DU2 in any of the Inter-CU handover scenarios of Figures 9 to 11). In other words, the first message is transmitted without passing through the target IAB donor-CU (IAB donor-CU2 in any of the Inter-CU handover scenarios of Figures 9 to 11).
[0138] It should be understood that the source IAB donor node may initially route the first message to the target IAB donor node using a wired connection, and the target IAB donor node may further route and forward the first message to the IAB node via the target path after receiving the first message.
[0139] The source path may be a transmission path between a source parent node and a source IAB donor-CU, and the target path may be a transmission path between a target parent node and a target IAB donor-CU. For example, in FIG. 9 to FIG. 11, the path between the handover IAB-MT and IAB donor-CU1 is called the source path (i.e., Source Path), and the path between the handover IAB-MT and IAB donor-CU2 is called the target path (i.e., Target Path). Alternatively, the source path may be a transmission path between a source parent node and a source IAB donor-DU, and the target path may be a transmission path between a target parent node and a target IAB donor-DU. For example, in FIG. 9 to FIG. 11, the path between the handover IAB-MT and IAB donor-DU1 is called the source path (i.e., Source Path), and the path between the handover IAB-MT and IAB donor-DU2 is called the target path (i.e., Target Path).
[0140] For example, as shown in Figure 12, after the IAB-MT handover is completed, for example, after the source IAB donor-CU receives a UE Context Release message sent by the target IAB donor, the source IAB donor-CU sends an F1AP message to the IAB-DU via the target IAB donor. After receiving the message, the IAB-DU deletes / releases the source F1 connection. The F1AP message may be an F1AP message, for example, an F1 Removal Request message, or may be a newly defined F1AP message.
[0141] From the above embodiment, it can be known that a first message is determined, the first message indicates that the CU of the IAB donor node connected to the IAB node is changed, and the first message is sent to the IAB node. In this way, the IAB node can release the F1 connection to the CU of the source IAB donor node according to the first message. Therefore, the IAB node releases the F1 connection in a timely manner based on the instruction of the source IAB donor. This avoids the waste of resources caused by the F1 connection not being released in a timely manner, or the interruption of terminal service caused by the F1 connection being released early but a new F1 connection not being set up, thereby improving the reliability of releasing the F1 connection and ensuring the IAB communication performance.
[0142] Further, in one embodiment, when sending a first message to the IAB node via the target IAB donor node, the source IAB donor node may set up a first TNL association with the IAB node, the first TNL association corresponding to an IP address assigned to the IAB node by the target IAB donor node, and then send the first message to the IAB node via the target IAB donor node based on the first TNL association.
[0143] Specifically, on the IAB node side, the IAB node may set up a first TNL association with the source IAB donor based on the IP address assigned by the target IAB donor. In other words, the first TNL association is triggered by the IAB node and set up to the source IAB donor node. For a specific implementation process, please refer to the newly set up TNL in the above method 1-1.
[0144] Optionally, the first message sent based on the first TNL association may further include second information. The second information includes an IP address assigned to the IAB node by the source IAB donor node and / or an identifier of a CU of the source IAB donor node, or the second information includes instruction information explicitly indicating to the IAB node to delete the source F1 connection. For example, the second information may be instruction information 2 shown in FIG. 13.
[0145] In another embodiment, when sending a first message to the IAB node via the target IAB donor node, the source IAB donor node may send the first message by setting up a second TNL association with the IAB node, the second TNL association corresponding to an IP address assigned to the IAB node by the source IAB donor node, and then send the first message to the IAB node via the target IAB donor node based on the second TNL association.
[0146] Specifically, the second TNL association is triggered by the IAB node and set up to the source IAB donor node. For a specific implementation process, please refer to the old TNL of the above-mentioned method 1-2. It should be noted that when the IAB node first accesses the source IAB donor node, before setting up the source F1 connection to the source IAB donor node, the IAB node may set up a second TNL association with the source IAB donor node based on the IP address assigned to the IAB node by the source IAB donor node. When the IAB node performs a handover, the source IAB donor node may send a first message to the IAB node through the target IAB donor node based on the set up second TNL association.
[0147] Optionally, before sending the first message to the IAB node through the target IAB donor node based on the second TNL association, the source IAB donor may further send an IP address assigned to the IAB node by the source IAB donor node to the CU of the target IAB donor node, and the IP address assigned to the IAB node by the source IAB donor node is for determining a mapping relationship, where the mapping relationship is a correspondence relationship between the IP address assigned to the IAB node by the source IAB donor node and the BAP address assigned to the IAB node by the target IAB donor node. For example, the mapping relationship may be the mapping relationship shown in FIG. 15.
[0148] In another embodiment, when the source IAB donor sends a first message to the IAB node through the target IAB donor node, the first message may include an inner IP header and an outer IP header, the IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and the IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node. For a specific implementation process, please refer to the IP-in-IP transmission method of the above-mentioned method 1-3, specifically, the source IAB donor performs IP encapsulation twice on the first message.
[0149] It should be understood that the inner layer here refers to the second IP encapsulation process, and the outer layer refers to the first IP encapsulation process. Optionally, the IP address of the IAB node included in the inner layer may be the IP address assigned by the target IAB donor node, and the IP address of the IAB node included in the outer layer may be the IP address assigned by the source IAB donor node. For example, as shown in Figure 16, IP encapsulation is performed twice for the F1AP message sent by the source IAB donor-CU to the IAB-DU. Downlink data transmission is used as an example. During the first IP encapsulation, the destination IP address is the IP address assigned to the IAB node by the source IAB donor, and the source IP address is the IP address of the source IAB donor-CU. During the second IP encapsulation, the destination IP address is the IP address assigned to the IAB node by the target IAB donor, and the source address is the IP address of the source IAB donor-CU.
[0150] From the above embodiment, it can be known that when sending a first message to an IAB node through a target IAB donor node, the source IAB donor can send the first message to the IAB node using multiple implementations, such as the first TNL association, the second TNL association, and an IP-in-IP transmission manner, i.e., two times IP encapsulation, etc. This increases the diversity of the manner of sending the first message and meets the individual requirements of different communication functions.
[0151] Figure 19 is a schematic flowchart of a method for releasing an F1 connection according to an embodiment of the present application. The method for releasing an F1 connection may be used for an IAB node. The IAB node includes an IAB-MT and an IAB-DU, for example, an IAB-MT and an IAB-DU in any of the Inter-CU handover scenarios of Figures 9 to 11. As shown in Figure 19, the method for releasing an F1 connection may include the following steps.
[0152] S191: Receive a first message from a source IAB donor node, where the first message indicates that a CU of an IAB donor node connected to the IAB node changes.
[0153] Specifically, the source IAB donor node may be an IAB donor node connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes.
[0154] The IAB node may be a handover IAB node or a downstream node of the handover IAB node. The downstream node of the handover IAB node may include a child node of the handover IAB node, a grandchild node (a child node of a child node), and a descendant node of the grandchild node, etc. In addition, the downstream node may be another IAB node or a UE.
[0155] Regarding the first message: In one embodiment, the message name of the first message may implicitly indicate that the CU of the IAB donor node connected to the IAB node is changed. For example, the first message is an F1 Removal Request message or a newly defined message (e.g., an F1 Release Request message).
[0156] In another embodiment, the information carried in the first message explicitly or implicitly indicates that the CU of the IAB donor node connected to the IAB node changes. For example, the first message includes first information, and the first information indicates that the CU of the IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs. For example, the first information may be the indication information 1 shown in FIG. 12.
[0157] In another embodiment, the first message may be an F1AP message. The F1AP message may be an F1AP message, for example, an F1 Removal Request message, or may be a newly defined F1AP message. Optionally, the F1AP message may carry first information, and the first information indicates that a CU of an IAB donor node connected to an IAB node changes or an inter-donor CU handover occurs.
[0158] In another embodiment, the first message may be a handover command generated by the target IAB donor node (i.e., the RRC reconfiguration message carries the ReconfigurationWithSync parameter). The handover command carries first information, where the first information indicates that a CU of the IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs.
[0159] In another embodiment, the first message may be a message for configuring configuration information of the DU of the IAB node connected to the target IAB donor node. The configuration information may include a new cell identity (e.g., Cell identity or CGI) of the cell of the IAB-DU connected to the target IAB donor, and / or a system broadcast message of the cell of the IAB-DU. The configuration information may implicitly indicate that the CU of the IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs. Optionally, the configuration information may be provided by an OAM server or by the target IAB donor node.
[0160] Reception method: In one embodiment, the IAB node may receive a first message from the source IAB donor node via the source route. For example, before the IAB node is handed over from the source route to the target route, the IAB node may receive a first message from the source IAB donor node via the source route. For example, as shown in Figure 17, before the IAB-MT receives the handover command (or before the handover is executed), the source IAB donor-CU sends an F1AP message to the IAB-DU. After receiving the message, the IAB-DU deletes / releases the source F1 connection.
[0161] In another embodiment, the IAB node may receive the first message from the source IAB donor node via the target IAB donor node. For example, after the IAB node is handed over from the source path to the target path, the IAB node may receive the first message from the source IAB donor node via the target IAB donor node.
[0162] The target IAB donor node may be an IAB donor node connected to the IAB node after the CU of the IAB donor node connected to the IAB node has changed. For example, the target IAB donor node is IAB donor-CU2 and IAB donor-DU2 in any of the Inter-CU handover scenarios in Figures 9 to 11. In this application, the source IAB donor node sends a first message to the IAB node through the target IAB donor node specifically means that the source IAB donor node sends the first message to the IAB node through the target IAB donor-DU (IAB donor-DU2 in any of the Inter-CU handover scenarios in Figures 9 to 11). In other words, the first message is sent without passing through the target IAB donor-CU (IAB donor-CU2 in any of the Inter-CU handover scenarios in Figures 9 to 11).
[0163] It should be understood that the source IAB donor node may initially route the first message to the target IAB donor node using a wired connection, and the target IAB donor node may further route and forward the first message to the IAB node via the target path after receiving the first message, such that the IAB node may receive the first message from the source IAB donor node via the target IAB donor node.
[0164] The source path may be a transmission path between a source parent node and a source IAB donor-CU, and the target path may be a transmission path between a target parent node and a target IAB donor-CU. For example, in FIG. 9 to FIG. 11, the path between the handover IAB-MT and IAB donor-CU1 is called the source path (i.e., Source Path), and the path between the handover IAB-MT and IAB donor-CU2 is called the target path (i.e., Target Path). Alternatively, the source path may be a transmission path between a source parent node and a source IAB donor-DU, and the target path may be a transmission path between a target parent node and a target IAB donor-DU. For example, in FIG. 9 to FIG. 11, the path between the handover IAB-MT and IAB donor-DU1 is called the source path (i.e., Source Path), and the path between the handover IAB-MT and IAB donor-DU2 is called the target path (i.e., Target Path).
[0165] For example, as shown in Figure 12, after the IAB-MT handover is completed, for example, after the source IAB donor-CU receives a UE Context Release message sent by the target IAB donor, the source IAB donor-CU sends an F1AP message to the IAB-DU via the target IAB donor. After receiving the message, the IAB-DU deletes / releases the source F1 connection. The F1AP message may be an F1AP message, for example, an F1 Removal Request message, or may be a newly defined F1AP message.
[0166] S192: Release the F1 connection to the CU of the source IAB donor node according to the first message.
[0167] Specifically, after receiving the first message, the IAB node may choose to immediately disconnect the F1 connection of the source IAB donor node to the CU, or may choose to disconnect the F1 connection of the source IAB donor node to the CU after a certain time delay based on the actual situation.
[0168] In one embodiment, the IAB node may start a timer and release the F1 connection to the CU of the source IAB donor node after the timer expires. In this way, the IAB node reserves a certain processing time before releasing the source F1 connection, which improves the reliability of releasing the source F1 connection. The duration of the timer may be configured by the source IAB donor node, or may be configured by the target IAB donor node, or may be pre-specified in the communication protocol.
[0169] In another embodiment, the first message includes information about the duration of the timer. In this way, the IAB node can obtain the duration of the timer according to the first message, then start the corresponding timer based on the duration, and release the F1 connection of the source IAB donor node to the CU after the corresponding timer expires.
[0170] From the above embodiment, it can be known that the first message sent by the source IAB donor node is received, the first message indicates that the CU of the IAB donor node connected to the IAB node is changed, and the F1 connection to the CU of the source IAB donor node is released according to the first message. Therefore, the IAB node releases the F1 connection in a timely manner based on the instruction of the source IAB donor. This avoids the waste of resources caused by the F1 connection not being released in a timely manner, or the interruption of terminal service caused by the F1 connection being released early but not setting up a new F1 connection, thereby improving the reliability of releasing the F1 connection and ensuring the IAB communication performance.
[0171] Further, in one embodiment, when receiving a first message from the source IAB donor node via the target IAB donor node, the IAB node may set up a first TNL association with the source IAB donor node based on an IP address assigned to the IAB node by the target IAB donor node, and then receive the first message from the source IAB donor node via the target IAB donor node based on the first TNL association.
[0172] Specifically, on the IAB node side, the IAB node may set up a first TNL association with the source IAB donor based on the IP address assigned by the target IAB donor. In other words, the first TNL association is triggered by the IAB node and set up to the source IAB donor node. For a specific implementation process, please refer to the newly set up TNL in the above method 1-1.
[0173] Optionally, the first message received based on the first TNL association may further include second information. The second information may include an IP address assigned to the IAB node by the source IAB donor node and / or an identifier of a CU of the source IAB donor node, or the second information may include instruction information explicitly indicating to the IAB node to delete the source F1 connection. For example, the second information may be instruction information 2 shown in FIG. 13.
[0174] In another embodiment, when receiving the first message from the source IAB donor node via the target IAB donor node, the IAB node may set up a second TNL association with the source IAB donor node based on an IP address assigned to the IAB node by the source IAB donor node, and receive the first message from the source IAB donor node via the target IAB donor node based on the second TNL association.
[0175] Specifically, the second TNL association is triggered by the IAB node and set up to the source IAB donor node. For a specific implementation process, please refer to the old TNL of the above-mentioned method 1-2. It should be noted that when the IAB node first accesses the source IAB donor node, before setting up the source F1 connection to the source IAB donor node, the IAB node may set up a second TNL association with the source IAB donor node based on the IP address assigned to the IAB node by the source IAB donor node. When the IAB node performs a handover, the source IAB donor node may send a first message to the IAB node through the target IAB donor node based on the set up second TNL association.
[0176] In another embodiment, when the IAB node receives the first message from the source IAB donor node through the target IAB donor node, the first message may include an inner IP header and an outer IP header, the IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and the IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node. For a specific implementation process, please refer to the IP-in-IP transmission method of the above-mentioned method 1-3, specifically, the source IAB donor node performs IP encapsulation twice on the first message.
[0177] It should be understood that the inner layer here refers to the second IP encapsulation process, and the outer layer refers to the first IP encapsulation process. Optionally, the IP address of the IAB node included in the inner layer may be the IP address assigned by the target IAB donor node, and the IP address of the IAB node included in the outer layer may be the IP address assigned by the source IAB donor node. For example, as shown in Figure 16, IP encapsulation is performed twice for the F1AP message sent by the source IAB donor-CU to the IAB-DU. Downlink data transmission is used as an example. During the first IP encapsulation, the destination IP address is the IP address assigned to the IAB node by the source IAB donor, and the source IP address is the IP address of the source IAB donor-CU. During the second IP encapsulation, the destination IP address is the IP address assigned to the IAB node by the target IAB donor, and the source address is the IP address of the source IAB donor-CU.
[0178] From the above embodiment, it can be known that when receiving the first message from the source IAB donor node through the target IAB donor node, the IAB node can receive the first message from the source IAB donor node using multiple implementations, such as the first TNL association, the second TNL association, and the IP-in-IP transmission manner, i.e., two IP encapsulation, etc. This increases the diversity of the manner of receiving the first message and meets the individual requirements of different communication functions.
[0179] 20 is a schematic diagram of the structure of an apparatus for releasing an F1 connection according to an embodiment of the present application. The apparatus for releasing an F1 connection may be used in a source IAB donor node. The source IAB donor node includes a source donor-CU and a source donor-DU, for example, an IAB donor-CU1 and an IAB donor-DU1 in any of the Inter-CU handover scenarios of FIG. 9 to FIG. 11. As shown in FIG. 20, the apparatus for releasing an F1 connection includes: A determination module 201 configured to determine a first message, the first message indicating that a CU of an IAB donor node connected to the IAB node is to change; a sending module 202 configured to send a first message to the IAB node to release an F1 connection between the IAB node and the CU of the source IAB donor node; It may include, The source IAB donor node is an IAB donor node that is connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes.
[0180] Specifically, the source IAB donor node may be an IAB donor node connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes. The IAB node may be a handover IAB node or a downstream node of the handover IAB node. The downstream node of the handover IAB node may include a child node, a grandchild node (a child node of a child node), and a descendant node of a grandchild node, etc. of the handover IAB node. In addition, the downstream node may be another IAB node or a UE. The source IAB donor node may perform a handover decision based on the measurement result reported by the handover IAB node to determine whether the handover IAB node needs to be handed over from the source IAB donor node to the target IAB donor node. Thus, the source IAB donor node may determine whether the CU of the IAB donor node connected to the IAB node changes based on the decision result. In one embodiment, the message name of the first message may implicitly indicate that the CU of the IAB donor node connected to the IAB node changes. For example, the first message is an F1 Removal Request message (an existing F1AP message) or a newly defined message (eg, an F1 Release Request message).
[0181] In a possible embodiment, the first message includes first information, and the first information indicates that a CU of an IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs.
[0182] Specifically, the information carried in the first message explicitly or implicitly indicates that a CU of an IAB donor node connected to the IAB node changes. For example, the first message includes first information, and the first information indicates that a CU of an IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs. For example, the first information may be indication information 1 shown in FIG. 12.
[0183] In a possible embodiment, the first message is an F1 Application Protocol F1AP message.
[0184] Specifically, the F1AP message may be an F1AP message, such as an F1 Removal Request message, or may be a newly defined F1AP message. Optionally, the F1AP message may carry first information, where the first information indicates that a CU of an IAB donor node connected to an IAB node changes or an inter-donor CU handover occurs.
[0185] In a possible embodiment, the transmission module 202 includes: a sending submodule configured to send a first message to the IAB node via the target IAB donor node; Including, The target IAB donor node is an IAB donor node connected to the IAB node after the CU of the IAB donor node connected to the IAB node has changed. For example, the target IAB donor node is IAB donor-CU2 and IAB donor-DU2 in any of the Inter-CU handover scenarios in Figures 9 to 11. In this application, the source IAB donor node sends a first message to the IAB node through the target IAB donor node specifically means that the source IAB donor node sends the first message to the IAB node through the target IAB donor-DU (IAB donor-DU2 in any of the Inter-CU handover scenarios in Figures 9 to 11). In other words, the first message is sent without passing through the target IAB donor-CU (IAB donor-CU2 in any of the Inter-CU handover scenarios in Figures 9 to 11).
[0186] It should be understood that the source IAB donor node may initially route the first message to the target IAB donor node using a wired connection, and the target IAB donor node may further route and forward the first message to the IAB node via the target path after receiving the first message.
[0187] In a possible embodiment, the sending sub-module comprises: a first association unit configured to set up a first TNL association with the IAB node based on an IP address assigned to the IAB node by the target IAB donor node; a first sending unit configured to send a first message to the IAB node via the target IAB donor node based on the first TNL association; Includes.
[0188] Specifically, on the IAB node side, the IAB node may set up a first TNL association with the source IAB donor based on the IP address assigned by the target IAB donor. In other words, the first TNL association is triggered by the IAB node and set up to the source IAB donor node. For a specific implementation process, please refer to the newly set up TNL in the above method 1-1.
[0189] In a possible embodiment, the first message further includes second information, where the second information includes an IP address assigned to the IAB node by the source IAB donor node and / or an identifier of a CU of the source IAB donor node.
[0190] Specifically, the first message sent based on the first TNL association may further include second information. The second information may include an IP address assigned to the IAB node by the source IAB donor node and / or an identifier of a CU of the source IAB donor node, or the second information may include instruction information explicitly indicating to the IAB node to delete the source F1 connection. For example, the second information may be instruction information 2 shown in FIG. 13.
[0191] In a possible embodiment, the sending sub-module comprises: a second association unit configured to set up a second TNL association with the IAB donor node based on an IP address assigned to the IAB node by the source IAB donor node; a second sending unit configured to send the first message to the IAB node via the target IAB donor node based on the second TNL association; Includes.
[0192] Specifically, the second TNL association is triggered by the IAB node and set up to the source IAB donor node. For a specific implementation process, please refer to the old TNL of the above-mentioned method 1-2. It should be noted that when the IAB node first accesses the source IAB donor node, before setting up the source F1 connection to the source IAB donor node, the IAB node may set up a second TNL association with the source IAB donor node based on the IP address assigned to the IAB node by the source IAB donor node. When the IAB node performs a handover, the source IAB donor node may send a first message to the IAB node through the target IAB donor node based on the set up second TNL association.
[0193] In a possible embodiment, the sending sub-module comprises: a third sending unit configured to send an IP address assigned to the IAB node by the source IAB donor node to the CU of the target IAB donor node, where the IP address assigned to the IAB node by the source IAB donor node is used to determine a mapping relationship; The mapping relationship is a correspondence relationship between the IP address assigned to the IAB node by the source IAB donor node and the backhaul adaptation protocol (BAP) address assigned to the IAB node by the target IAB donor node. Further includes:
[0194] Specifically, before sending the first message to the IAB node via the target IAB donor node based on the second TNL association, the source IAB donor may further send an IP address assigned to the IAB node by the source IAB donor node to the CU of the target IAB donor node.
[0195] In a possible embodiment, the first message includes an inner IP header and an outer IP header, where the IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and the IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node.
[0196] It should be understood that the inner layer here refers to the second IP encapsulation process, and the outer layer refers to the first IP encapsulation process. Optionally, the IP address of the IAB node included in the inner layer may be the IP address assigned by the target IAB donor node, and the IP address of the IAB node included in the outer layer may be the IP address assigned by the source IAB donor node. For example, as shown in Figure 16, IP encapsulation is performed twice for the F1AP message sent by the source IAB donor-CU to the IAB-DU. Downlink data transmission is used as an example. During the first IP encapsulation, the destination IP address is the IP address assigned to the IAB node by the source IAB donor, and the source IP address is the IP address of the source IAB donor-CU. During the second IP encapsulation, the destination IP address is the IP address assigned to the IAB node by the target IAB donor, and the source address is the IP address of the source IAB donor-CU.
[0197] In a possible embodiment, the first message further comprises information regarding the duration of the timer.
[0198] Specifically, the duration of the timer may be configured by the source IAB donor node, or may be configured by the target IAB donor node, or may be pre-specified in the communication protocol. Specifically, after receiving the first message, the IAB node starts a timer, and then releases the F1 connection to the CU of the source IAB donor node after the timer expires. In this way, the IAB node reserves a certain processing time before releasing the F1 connection, which can improve the reliability of releasing the F1 connection.
[0199] It should be understood that the present apparatus is configured to execute the method for releasing F1 connection at the source IAB donor node side in the above embodiment. The implementation principle and technical effect of the corresponding program modules in the present apparatus are similar to those described in the method for releasing F1 connection at the source IAB donor node side. For the operation process of the present apparatus, please refer to the corresponding process in the method for releasing F1 connection at the source IAB donor node side. Details will not be described again here.
[0200] 21 is a schematic diagram of the structure of an apparatus for releasing an F1 connection according to an embodiment of the present application. The apparatus for releasing an F1 connection may be used in an IAB node. The IAB node includes an IAB-MT and an IAB-DU, for example, an IAB-MT and an IAB-DU in any of the Inter-CU handover scenarios of FIG. 9 to FIG. 11. As shown in FIG. 21, the apparatus for releasing an F1 connection includes: A receiving module 211 configured to receive a first message from a source IAB donor node, the first message indicating that a CU of an IAB donor node connected to the IAB node is changing; a disconnection module 212 configured to disconnect the F1 connection of the source IAB donor node to the CU according to the first message; It may include, The source IAB donor node is an IAB donor node that is connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes.
[0201] Specifically, the source IAB donor node may be an IAB donor node connected to the IAB node before the CU of the IAB donor node connected to the IAB node changes. The IAB node may be a handover IAB node or a downstream node of the handover IAB node. The downstream node of the handover IAB node may include a child node, a grandchild node (a child node of a child node), and a descendant node of a grandchild node, etc. of the handover IAB node. In addition, the downstream node may be another IAB node or a UE. In one embodiment, the message name of the first message may implicitly indicate that the CU of the IAB donor node connected to the IAB node changes. For example, the first message is an F1 Removal Request message (an existing F1AP message) or a newly defined message (e.g., an F1 Release Request message).
[0202] In a possible embodiment, the first message includes first information, and the first information indicates that a CU of an IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs.
[0203] Specifically, the information carried in the first message explicitly or implicitly indicates that a CU of an IAB donor node connected to the IAB node changes. For example, the first message includes first information, and the first information indicates that a CU of an IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs. For example, the first information may be indication information 1 shown in FIG. 12.
[0204] In a possible embodiment, the first message is an F1AP message.
[0205] Specifically, the F1AP message may be an F1AP message, such as an F1 Removal Request message, or may be a newly defined F1AP message. Optionally, the F1AP message may carry first information, where the first information indicates that a CU of an IAB donor node connected to an IAB node changes or an inter-donor CU handover occurs. In a possible embodiment, the receiving module 211: a receiving submodule configured to receive a first message from the source IAB donor node via the target IAB donor node; Including, The target IAB donor node is an IAB donor node connected to the IAB node after the CU of the IAB donor node connected to the IAB node has changed. For example, the target IAB donor node is IAB donor-CU2 and IAB donor-DU2 in any of the Inter-CU handover scenarios in Figures 9 to 11. In this application, the source IAB donor node sends a first message to the IAB node through the target IAB donor node specifically means that the source IAB donor node sends the first message to the IAB node through the target IAB donor-DU (IAB donor-DU2 in any of the Inter-CU handover scenarios in Figures 9 to 11). In other words, the first message is sent without passing through the target IAB donor-CU (IAB donor-CU2 in any of the Inter-CU handover scenarios in Figures 9 to 11).
[0206] It should be understood that the source IAB donor node may initially route the first message to the target IAB donor node using a wired connection, and the target IAB donor node may further route and forward the first message to the IAB node via the target path after receiving the first message, such that the IAB node may receive the first message from the source IAB donor node via the target IAB donor node.
[0207] In a possible embodiment, the receiving sub-module comprises: a first setup unit configured to setup a first TNL association with a source IAB donor node based on an IP address assigned to the IAB node by a target IAB donor node; a first receiving unit configured to receive a first message from the source IAB donor node via the target IAB donor node based on the first TNL association; Includes.
[0208] Specifically, on the IAB node side, the IAB node may set up a first TNL association with the source IAB donor based on the IP address assigned by the target IAB donor. In other words, the first TNL association is triggered by the IAB node and set up to the source IAB donor node. For a specific implementation process, please refer to the newly set up TNL in the above method 1-1.
[0209] In a possible embodiment, the first message further includes second information, where the second information includes an IP address assigned to the IAB node by the source IAB donor node and / or an identifier of a CU of the source IAB donor node.
[0210] Specifically, the first message received based on the first TNL association may further include second information. The second information may include an IP address assigned to the IAB node by the source IAB donor node and / or an identifier of a CU of the source IAB donor node, or the second information may include instruction information explicitly indicating to the IAB node to delete the source F1 connection. For example, the second information may be instruction information 2 shown in FIG. 13.
[0211] In a possible embodiment, the receiving sub-module comprises: a second setup unit configured to setup a second TNL association with the source IAB donor node based on an IP address assigned to the IAB node by the source IAB donor node; a second receiving unit configured to receive a first message from the source IAB donor node via the target IAB donor node based on the second TNL association; Includes.
[0212] The second TNL association is triggered by the IAB node and set up to the source IAB donor node. For a specific implementation process, please refer to the old TNL of the above-mentioned method 1-2. It should be noted that when the IAB node first accesses the source IAB donor node, before setting up the source F1 connection to the source IAB donor node, the IAB node may set up a second TNL association with the source IAB donor node based on the IP address assigned to the IAB node by the source IAB donor node. When the IAB node performs a handover, the source IAB donor node may send a first message to the IAB node through the target IAB donor node based on the set up second TNL association.
[0213] In a possible embodiment, the first message includes an inner IP header and an outer IP header, where the IP address of the IAB node included in the inner IP header corresponds to a source IAB donor node, and the IP address of the IAB node included in the outer IP header corresponds to a target IAB donor node.
[0214] It should be understood that the inner layer here refers to the second IP encapsulation process, and the outer layer refers to the first IP encapsulation process. Optionally, the IP address of the IAB node included in the inner layer may be the IP address assigned by the target IAB donor node, and the IP address of the IAB node included in the outer layer may be the IP address assigned by the source IAB donor node. For example, as shown in Figure 16, IP encapsulation is performed twice for the F1AP message sent by the source IAB donor-CU to the IAB-DU. Downlink data transmission is used as an example. During the first IP encapsulation, the destination IP address is the IP address assigned to the IAB node by the source IAB donor, and the source IP address is the IP address of the source IAB donor-CU. During the second IP encapsulation, the destination IP address is the IP address assigned to the IAB node by the target IAB donor, and the source address is the IP address of the source IAB donor-CU.
[0215] In a possible embodiment, the release module 212 includes: a start submodule configured to start a timer; a disconnection submodule configured to disconnect the F1 connection of the source IAB donor node to the CU after the timer expires; Includes.
[0216] Specifically, the IAB node may start a timer and release the F1 connection to the CU of the source IAB donor node after the timer expires. In this way, the IAB node ensures a certain processing time before releasing the source F1 connection, which improves the reliability of releasing the source F1 connection. The duration of the timer may be configured by the source IAB donor node, or may be configured by the target IAB donor node, or may be pre-specified in the communication protocol.
[0217] In a possible embodiment, the first message further comprises information regarding the duration of the timer.
[0218] It should be understood that the IAB node may obtain the duration of the timer according to the first message, then start the corresponding timer based on the duration, and release the F1 connection to the CU of the source IAB donor node after the corresponding timer expires. It should be understood that the present apparatus is configured to execute the method for releasing the F1 connection at the IAB donor side in the above embodiment. The implementation principle and technical effect of the corresponding program modules in the present apparatus are similar to those described in the method for releasing the F1 connection at the IAB donor side. For the operation process of the present apparatus, please refer to the corresponding process in the method for releasing the F1 connection at the IAB donor side. Details will not be described again here.
[0219] FIG. 22 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device may be an IAB donor node (e.g., a source donor node or a target donor node in the embodiment of the present application) and may implement the function of the IAB donor node in the embodiment of the above-mentioned method. Alternatively, the communication device may be an IAB node and may implement the function of the IAB node in the embodiment of the above-mentioned method. For ease of explanation, FIG. 22 shows the main components of the communication device. As shown in FIG. 22, the following are as follows:
[0220] The communication device includes at least one processor 711, at least one memory 712, at least one transceiver 713, at least one network interface 714, and one or more antennas 715. The processor 711, the memory 712, the transceiver 713, and the network interface 714 are connected to each other, for example, via a bus. In this embodiment of the present application, the connection may include various types of interfaces, transmission lines, or buses, etc. This is not limited in this embodiment. The antenna 715 is connected to the transceiver 713. The network interface 714 is configured to allow the communication device to be connected to another network device via a communication link.
[0221] The processor 711 is primarily configured to process communication protocols and communication data, control the entire node, execute software programs, and process data of the software programs.
[0222] In an optional embodiment, the processor may include a baseband processor and a central processing unit. The baseband processor is mainly configured to process communication protocols and communication data. The central processing unit is mainly configured to control the entire terminal device, execute software programs, and process data of the software programs. Alternatively, the processor may integrate the functions of the baseband processor and the central processing unit. Those skilled in the art may understand that the baseband processor and the central processing unit may be processors independent of each other and are interconnected by a technology such as a bus. Those skilled in the art may understand that a node may include multiple baseband processors to accommodate different network standards, and a node may include multiple central processing units to enhance the processing capabilities of the node. The components of the node may be connected via various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be incorporated in the processor or may be stored in the memory in the form of a software program. The processor executes the software program to perform the baseband processing function.
[0223] The memory 712 is mainly configured to store software programs and data. The memory 712 may exist independently and be connected to the processor 711. Optionally, the memory 712 and the processor 711 may be integrated together, for example, integrated on a single chip, i.e., an on-chip memory, or the memory 712 is an independent storage element. This is not limited in this embodiment of the present application. The memory 712 can store program codes for executing the technical solutions in the embodiments of the present application, and the processor 711 controls the execution. Various types of computer program codes that are executed may also be considered as drivers of the processor 711.
[0224] The transceiver 713 may be configured to perform conversion between baseband signals and radio frequency signals and process the radio frequency signals. The transceiver 713 may be connected to an antenna 715. The transceiver 713 includes a transmitter (Tx) and a receiver (Rx). Specifically, the one or more antennas 715 may receive the radio frequency signals. The receiver Rx of the transceiver 713 receives the radio frequency signals from the antenna, converts the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provides the digital baseband signals or digital intermediate frequency signals to the processor 711, which is configured to further process, e.g., demodulate and decode, the digital baseband signals or digital intermediate frequency signals. In addition, the transmitter Tx of the transceiver 713 is configured to receive the modulated digital baseband signals or modulated digital intermediate frequency signals from the processor 711, converts the modulated digital baseband signals or modulated digital intermediate frequency signals into radio frequency signals, and transmits the radio frequency signals via the one or more antennas 715. Specifically, the receiver Rx may selectively perform one or more levels of frequency downmixing processing and analog-digital conversion processing on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal. The sequence of the frequency downmixing processing and the analog-digital conversion processing is adjustable. The transmitter Tx may selectively perform one or more levels of frequency upmixing processing and digital-analog conversion processing on the modulated digital baseband signal or the modulated digital intermediate frequency signal to obtain a radio frequency signal. The sequence of the frequency upmixing processing and the digital-analog conversion processing is adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as a digital signal. Optionally, the transmitter Tx and the receiver Rx may be implemented by different physical structures / circuits or may be implemented by the same physical structure / circuit, in other words, the transmitter Tx and the receiver Rx may be inherited together.
[0225] The transceiver may also be referred to as a transceiver unit, a transceiver device, or the like. Optionally, a component in the transceiver unit configured to perform a receiving function may be considered a receiving unit, and a component in the transceiver unit configured to perform a transmitting function may be considered a transmitting unit. That is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit may also be referred to as a receiver, an input port, a receiving circuit, or the like. The transmitting unit may also be referred to as a transmitter, a transmitting circuit, or the like. Alternatively, the Tx, Rx, and the antenna may be combined into a transceiver.
[0226] In FIG. 22, when the communication device is a source IAB donor node, the source IAB donor node may communicate with the target IAB donor node through a network interface to complete the reception and transmission of information and / or messages between the source IAB donor node and the target IAB donor node in the embodiment of the present application, and the source IAB donor node may communicate with the IAB node through a transceiver and an antenna to complete the transmission and reception of information and / or messages between the source IAB donor node and the IAB node in the embodiment of the present application. When the communication device is an IAB node, the IAB node may communicate with the source IAB donor node or the target IAB donor node through a transceiver and an antenna to complete the reception and transmission of information and / or messages between the IAB node and the source IAB donor node or the target IAB donor node. For specific information and / or specific messages, please refer to the contents of the preceding embodiment. Details will not be described again here.
[0227] FIG. 23 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device may be an IAB donor node (e.g., a source donor node or a target donor node in the embodiment of the present application) and may implement the function of the IAB donor node in the embodiment of the above-mentioned method. The communication device may be in a CU-DU split architecture. As shown in FIG. 23, the communication device may include one or more DUs 1101 and one or more CUs 1102. The DU 1101 may include at least one antenna 11011, at least one radio frequency unit 11012, at least one processor 11013, and at least one memory 11014. The DU 1101 is mainly configured to receive and transmit radio frequency signals, perform conversion between radio frequency signals and baseband signals, and perform some baseband processing. The CU 1102 may include at least one processor 11022 and at least one memory 11021. The CU 1102 and the DU 1101 may communicate with each other via an interface. The control plane interface may be F1-C, and the user plane interface may be F1-U.
[0228] The CU1102 is mainly configured to perform baseband processing and control the base station, etc. The DU1101 and the CU1102 may be physically located together, or may be physically located separately, i.e., in a distributed base station. The CU1102 is the control center of the base station, and may also be called a processing unit, and is mainly configured to complete baseband processing functions. For example, the CU1102 may be configured to control the communication device to perform the operation procedures in the above-mentioned method embodiments.
[0229] Specifically, the baseband processing in the CU and the DU may be divided based on the protocol layer of the wireless network. For details, see above.
[0230] In an example, the CU 1102 may include one or more boards. The multiple boards may jointly support a radio access network of a single access standard (e.g., a 5G network) or may separately support radio access networks of different access standards (such as an LTE network, a 5G network, or another access network). The memory 11021 and the processor 11022 may provide functionality to one or more boards. In other words, the memory and the processor may be independently located on each board, or the multiple boards may share the same memory and the same processor. In addition, the necessary circuits may be further configured on each board. The DU 1101 may include one or more boards. The multiple boards may jointly support a radio access network of a single access standard (e.g., a 5G network) or may separately support radio access networks of different access standards (such as an LTE network, a 5G network, or another access network). The memory 11014 and the processor 11013 may provide functionality to one or more boards. In other words, the memory and processor may be independently located on each board, or multiple boards may share the same memory and the same processor. In addition, necessary circuitry may be further configured on each board.
[0231] Optionally, the CU 1102 may perform transmission to an IAB node via the DU 1101. The CU 1102 may be connected to another communication device via an interface. The CU 1102 may receive data and / or messages from another communication device (e.g., a CU of another communication device) via the interface, or may transmit data and / or messages to another communication device via the interface.
[0232] For example, when the communication device is a source donor node, the CU1102 may send and receive messages and / or information through the interface between the CU1102 and the target donor node, and may send and receive messages and / or information between the IAB node and the DU1101. When the communication device is a target donor node, the CU1102 may send and receive messages and / or information through the interface between the CU1102 and the source donor node, and may send and receive messages and / or information between the IAB node and the DU1101. For specific information and / or specific messages, please refer to the contents of the preceding embodiments. Details will not be described again here.
[0233] An embodiment of the present application further provides a communication system including two or more of a source IAB donor node, a target IAB donor node, and an IAB node, wherein the source IAB donor node may perform a method for releasing an F1 connection at the source IAB donor node side, and the IAB node may perform a method for releasing an F1 connection at the IAB node side.
[0234] An embodiment of the present application further provides a computer storage medium, the computer storage medium including computer instructions, when executed in a source IAB donor node, the source IAB donor node can perform a method for releasing an F1 connection at the source IAB donor node side.
[0235] An embodiment of the present application further provides a computer storage medium, the computer storage medium including computer instructions, when executed in an IAB node, the IAB node can perform a method for releasing an F1 connection at the IAB node side.
[0236] It may be noted that the processor in the embodiments of the present application may be a central processing unit (CPU), another general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic component, a transistor logic device, a hardware component, or a combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.
[0237] The method steps in the embodiments of the present application may be implemented by hardware or by a processor by executing software instructions. The software instructions may include corresponding software modules. The software modules may be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a removable hard disk, a CD-ROM, or any other form of storage medium known in the art. For example, the storage medium is coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may alternatively be a component of the processor. The processor and the storage medium may be located in an ASIC.
[0238] All or part of the above-mentioned embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or another programmable device. The computer instructions may be stored in or transmitted using a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) manner or wireless (e.g., infrared, radio, or microwave) manner. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device, such as a server or data center, that incorporates one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).
[0239] It can be understood that various numbers in the embodiments of the present application are merely used for distinction to simplify the description, and are not used to limit the scope of the embodiments of the present application. [Explanation of symbols]
[0240] 201 Decision Module 202 Transmitting Module 211 Receiver module 212 Release Module 711 Processor 712 Memory 713 Transceiver 714 Network Interface 715 Antenna 1101DU 1102 CU 11011 Antenna 11012 Radio Frequency Unit 11013 Processor 11014 Memory 11021 Memory 11022 processor
Claims
1. 1. A method for releasing an F1 connection, the method being used for an integrated access and backhaul (IAB) node, the method comprising: receiving a first message from a source IAB donor node, the first message indicating that a central unit (CU) of an IAB donor node connected to the IAB node is changing; releasing the F1 connection of the source IAB donor node to the CU according to the first message; Including, The source IAB donor node is an IAB donor node connected to the IAB node before a CU of the IAB donor node connected to the IAB node is changed; The step of receiving a first message from a source IAB donor node includes: receiving the first message from the source IAB donor node via a target IAB donor node; Including, The target IAB donor node is an IAB donor node connected to the IAB node after a CU of the IAB donor node connected to the IAB node has changed; The method of claim 1, wherein the first message includes an inner IP header and an outer IP header, an IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and an IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node.
2. A method for releasing an F1 connection, the method being used for an integrated access and backhaul (IAB) node, the method comprising: receiving a first message from a source IAB donor node, the first message indicating that a central unit (CU) of an IAB donor node connected to the IAB node is changing; releasing the F1 connection of the source IAB donor node to the CU according to the first message; Including, The source IAB donor node is an IAB donor node connected to the IAB node before a CU of the IAB donor node connected to the IAB node is changed; The first message includes first information, and the first information indicates that a CU of the IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs; The step of receiving a first message from a source IAB donor node includes: receiving the first message from the source IAB donor node via a target IAB donor node; Including, The target IAB donor node is an IAB donor node connected to the IAB node after a CU of the IAB donor node connected to the IAB node has changed; The method of claim 1, wherein the first message includes an inner IP header and an outer IP header, an IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and an IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node.
3. 1. A method for releasing an F1 connection, the method being used for a source integrated access and backhaul (IAB) donor node, the method comprising: determining a first message, the first message indicating a change in a central unit (CU) of an IAB donor node connected to the IAB node; sending the first message to the IAB node to release an F1 connection between the IAB node and a CU of the source IAB donor node; Including, The source IAB donor node is an IAB donor node connected to the IAB node before a CU of the IAB donor node connected to the IAB node is changed; The step of transmitting the first message to the IAB node comprises: sending the first message to the IAB node via a target IAB donor node; Including, The target IAB donor node is an IAB donor node connected to the IAB node after a CU of the IAB donor node connected to the IAB node has changed; The method of claim 1, wherein the first message includes an inner IP header and an outer IP header, an IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and an IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node.
4. A method for terminating an F1 connection, the method being used for a source integrated access and backhaul (IAB) donor node, the method comprising: determining a first message, the first message indicating a change in a central unit (CU) of an IAB donor node connected to the IAB node; sending the first message to the IAB node to release an F1 connection between the IAB node and a CU of the source IAB donor node; Including, The source IAB donor node is an IAB donor node connected to the IAB node before a CU of the IAB donor node connected to the IAB node is changed; The first message includes first information, and the first information indicates that a CU of the IAB donor node connected to the IAB node changes or an inter-donor CU handover occurs; The step of transmitting the first message to the IAB node comprises: sending the first message to the IAB node via a target IAB donor node; Including, The target IAB donor node is an IAB donor node connected to the IAB node after a CU of the IAB donor node connected to the IAB node has changed; The method of claim 1, wherein the first message includes an inner IP header and an outer IP header, an IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and an IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node.
5. 1. An apparatus for releasing an F1 connection, the apparatus being used in an integrated access and backhaul (IAB) node, the apparatus comprising: a receiving module configured to receive a first message from a source IAB donor node, the first message indicating that a central unit (CU) of an IAB donor node connected to the IAB node is changing; a disconnection module configured to disconnect an F1 connection of the source IAB donor node to a CU according to the first message; Equipped with The source IAB donor node is an IAB donor node connected to the IAB node before a CU of the IAB donor node connected to the IAB node is changed; The receiving module includes: further configured to receive the first message from the source IAB donor node via a target IAB donor node; The target IAB donor node is an IAB donor node connected to the IAB node after a CU of the IAB donor node connected to the IAB node has changed; the first message includes an inner IP header and an outer IP header, the IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and the IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node; Device.
6. 1. An apparatus for releasing an F1 connection, the apparatus being used in a source integrated access and backhaul (IAB) donor node, the apparatus comprising: a determining module configured to determine a first message, the first message indicating a change in a central unit (CU) of an IAB donor node connected to an IAB node; a sending module configured to send the first message to the IAB node to release an F1 connection between the IAB node and a CU of the source IAB donor node; Equipped with The source IAB donor node is an IAB donor node connected to the IAB node before a CU of the IAB donor node connected to the IAB node is changed; The transmitting module includes: and further configured to transmit the first message to the IAB node via a target IAB donor node; The target IAB donor node is an IAB donor node connected to the IAB node after a CU of the IAB donor node connected to the IAB node has changed; The first message includes an inner IP header and an outer IP header, an IP address of the IAB node included in the inner IP header corresponds to the target IAB donor node, and an IP address of the IAB node included in the outer IP header corresponds to the source IAB donor node.
7. A communication device, the communication device comprising a processor, the processor coupled to a memory; the memory is configured to store computer instructions; 3. A communications device, the processor being configured to execute the computer instructions to perform the method of claim 1 or 2.
8. A communication device, the communication device comprising a processor, the processor coupled to a memory; the memory is configured to store computer instructions; 5. A communications device, wherein the processor is configured to execute the computer instructions to perform the method of claim 3 or 4.
9. 5. A communication system comprising an integrated access and backhaul (IAB) node and a source IAB donor node, the IAB node configured to perform the method of claim 1 or 2, and the source IAB donor node configured to perform the method of claim 3 or 4.
10. 3. A computer storage medium comprising computer instructions which, when executed, perform the method of claim 1 or 2.
11. 5. A computer storage medium comprising computer instructions which, when executed, perform the method of claim 3 or 4.
12. A computer program comprising computer program instructions, which when executed by a communication device enable said communication device to carry out the method according to claim 1 or 2.
13. A computer program comprising computer program instructions, which when executed by a communication device enable said communication device to carry out the method according to claim 3 or 4.
Citation Information
Patent Citations
Connection establishment method and device, set access backhaul node and storage medium
CN111093286A
