Identifier management method and device

Abstract

The invention provides an identifier management method and device, and the method comprises the steps that a first host node receives first indication information sent by a first node, and the first indication information is used for indicating that the first node can be used for providing a wireless backhaul service; and the first host node sends a first identifier to the first node, wherein the first identifier is used for uniquely identifying the first node in a wireless backhaul link within the service range of the first host node. According to the identifier management method and device provided by the invention, the data packet can be routed in the air interface transmission process in the IAB network, and the data transmission efficiency in the IAB network is improved.

Description

[0001] This application is a divisional application of the original Chinese application with an application date of February 15, 2019 and application number “202210865670.4”, wherein the original application is incorporated by reference into this divisional application. Technical Field

[0002] The present application relates to the field of communications, and more specifically, to a method and device for identity management. Background Art

[0003] In a network with integrated access and backhaul (IAB) nodes, the transmission path between the UE and the IAB donor (also known as a donor node or donor gNB) consists of multiple transmission links, including at least one wireless backhaul link and one wireless access link. The access link is the communication link between the UE and the IAB node, and the wireless backhaul link is the communication link between IAB nodes or between an IAB node and the donor node. Data packets transmitted between the UE and the IAB donor must pass through multiple intermediate nodes. Both the donor node and the IAB node need to route the data packets to determine the next hop node and then forward them. This routing selection is based on the routing information carried in the data packet. For downlink transmission, the IAB node identifier can serve as routing information for data packets during transmission on the wireless backhaul link. Although the IAB node can obtain the Cell Radio Network Temporary Identifier (C-RNTI) from the parent node, this identifier is only used to uniquely identify the IAB node within the cell served by the parent node. This identifier cannot be used to address the IAB node in the wireless backhaul link within the service range of the host node. Therefore, how to adopt an effective IAB node identifier management method has become an urgent problem to be solved. Summary of the Invention

[0004] The present application provides a method and apparatus for identity management, which can reduce routing overhead during air interface transmission in an IAB network, thereby improving the efficiency of data transmission in the IAB network.

[0005] In a first aspect, a method for identity management is provided, including: a first host node receives first indication information sent by a first node, the first indication information is used to indicate that the first node can be used to provide wireless backhaul services; the first host node sends a first identifier to the first node, the first identifier is used to uniquely identify the first node in a wireless backhaul link within a service range of the first host node.

[0006] In combination with the first aspect, in some implementations of the first aspect, the first identifier includes an identifier of the first host node and identification information specific to the first node.

[0007] Optionally, the first node may be an integrated access and backhaul (IAB) node or a relay node in an LTE system.

[0008] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the first host node sending the first identifier to a second node, where the second node is a parent node of the first node.

[0009] Optionally, the first identifier may be an adaptation layer identifier of the first node.

[0010] In combination with the first aspect, in certain implementations of the first aspect, the first host node includes a distributed unit DU and a centralized unit CU, and the method also includes: the distributed unit DU receives first configuration information sent by the centralized unit CU; the first configuration information includes the identifier of the first node and the IP layer identifier of the first node.

[0011] Optionally, the first configuration information further includes an identifier of a third node; the third node is a child node of the first host node.

[0012] That is, the host node Donor CU can perform routing configuration for Donor DU.

[0013] In combination with the first aspect, in certain implementations of the first aspect, the first host node includes a distributed unit DU and a centralized unit CU, and the centralized unit CU includes a control plane CU-CP and a user plane CU-UP; the method also includes: the CU-CP obtains the IP layer identifier of the first node, and the CU-CP sends the IP layer identifier of the first node to the CU-UP.

[0014] For example, the IP layer identifier of the first node may be the IPv4 address or IPv6 address of the first node.

[0015] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: the first host node sends a first request message to the second host node, the first request message is used to request the first node to switch to the second host node; the first host node receives a second identifier sent by the second host node; the first host node sends the second identifier to the first node, and the second identifier is used to identify the first node in the routing of the wireless backhaul link.

[0016] In an embodiment of the present application, when the topology of the IAB network is updated or the CU connected to the IAB node changes, that is, IAB node #1 is switched, after the switch, IAB node #1 will be connected to the target CU, the target CU receives the switching request information sent by the source CU, and assigns a new adaptation layer identifier to the IAB node #1. The target CU sends the adaptation layer identifier to the source CU, and the source CU sends the adaptation layer identifier to the IAB node #1, where the source CU is the host node connected to the IAB node #1 before the switch.

[0017] In combination with the first aspect, in some implementations of the first aspect, the first indication information is further used to instruct the first host node to allocate a first identifier to the first node.

[0018] In combination with the first aspect, in certain implementations of the first aspect, the distributed unit DU receives a first data packet sent by the centralized unit CU, wherein the first data packet includes the IP layer identifier and data of the first node; the DU sends a second data packet to the first node, wherein the second data packet includes the IP layer identifier of the first node, the first identifier and the data.

[0019] In a second aspect, a method for identity management is provided, including: a first node sends first indication information to a first host node, the first indication information being used to indicate that the first node can be used to provide wireless backhaul services; the first node receives a first identifier sent by the host node, the first identifier being used to uniquely identify the first node in a wireless backhaul link within a service range of the first host node.

[0020] In combination with the second aspect, in some implementations of the second aspect, the first identifier includes an identifier of the first host node and identification information specific to the first node.

[0021] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the first node sending the first identifier to a second node, where the second node is a parent node of the first node.

[0022] In combination with the second aspect, in certain implementations of the second aspect, when the first node switches from a first host node to a second host node, the method also includes: the first node receives a second identifier sent by the first host node, and the second identifier is used to uniquely identify the first node in the wireless backhaul link within the service range of the second host node.

[0023] In a third aspect, a device for identification management is provided, including: a receiving unit for receiving first indication information sent by a first node, the first indication information being used to indicate that the first node can be used to provide wireless backhaul services; a sending unit for sending a first identification to the first node, the first identification being used to uniquely identify the first node in a wireless backhaul link within the service range of the first host node.

[0024] In combination with the third aspect, in certain implementations of the third aspect, the first identifier includes an identifier of the first host node and identification information specific to the first node.

[0025] In combination with the third aspect, in some implementations of the third aspect, the sending unit is further configured to send the first identifier to a second node, where the second node is a parent node of the first node.

[0026] In combination with the third aspect, in certain implementations of the third aspect, the device is a host base station, and the host base station includes a distributed unit DU and a centralized unit CU; wherein the distributed unit DU is used to receive first configuration information sent by the centralized unit CU, and the first configuration information includes the first identifier and the IP layer identifier of the first node.

[0027] In combination with the third aspect, in certain implementations of the third aspect, the distributed unit DU is specifically used to: receive a first data packet sent by the centralized unit CU, the first data packet containing the IP layer identifier and data of the first node; and send a second data packet to the first node, the second data packet containing the IP layer identifier of the first node, the first identifier and the data.

[0028] In combination with the third aspect, in certain implementations of the third aspect, the device is a host base station, and the host base station includes a distributed unit DU and a centralized unit CU; wherein the centralized unit CU includes a control plane CU-CP and a user plane CU-UP; the CU-CP is specifically used to: obtain the IP layer identifier of the first node and send the IP layer identifier of the first node to the CU-UP.

[0029] In combination with the third aspect, in certain implementations of the third aspect, the sending unit is also used to send a first request message to the second host node, and the first request message is used to request the first node to switch to the second host node; the receiving unit is also used to receive a second identifier sent by the second host node; the sending unit is further used to send a second identifier to the first node, and the second identifier is used to uniquely identify the first node in the wireless backhaul link within the service range of the second host node.

[0030] In a fourth aspect, a device for identity management is provided, including: a sending unit for sending first indication information to a first host node, wherein the first indication information is used to indicate that the first node can be used to provide wireless backhaul services; a receiving unit for receiving a first identifier sent by the host node, wherein the first identifier is used to uniquely identify the first node in the wireless backhaul link within the service range of the first host node.

[0031] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first identifier includes an identifier of the first host node and identification information specific to the first node.

[0032] In combination with the fourth aspect, in some implementations of the fourth aspect, the sending unit is further used to send the first identifier to a second node, where the second node is a parent node of the first node.

[0033] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the first node switches from a first host node to a second host node, the receiving unit is also used to receive a second identifier sent by the first host node, and the second identifier is used to uniquely identify the first node in the wireless backhaul link within the service range of the second host node.

[0034] In a fifth aspect, the present application provides a storage medium having a computer program stored thereon, which implements the method described in the first or second aspect above when the computer program is executed by a processor.

[0035] In a sixth aspect, the present application provides a chip system, comprising: a processor for executing the method described in the first or second aspect above.

[0036] In the seventh aspect, the present application provides a communication device, comprising: a processor, the processor being coupled to a memory, the memory being used to store a program, and when the program is executed by the processor, the communication device implements the method described in the first aspect or the second aspect above.

[0037] The communication device may be, for example, a terminal, or a network device (such as a base station), or a chip, a chip system, or a processor that can support the terminal or network device to implement the above functions. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a schematic diagram applicable to the wireless relay scenario provided in the embodiment of the present application.

[0039] Figure 2 Schematic diagram of the topology of the IAB network provided in an embodiment of the present application.

[0040] Figure 3 The protocol stack architecture of the intermediate IAB node and the access IAB node is shown.

[0041] Figure 4 The diagram shows the protocol stacks of various nodes in the multi-hop IAB network of this application.

[0042] Figure 5 This is a schematic interactive diagram of an identification management method according to an embodiment of the present application.

[0043] Figure 6 This is a schematic diagram of identification information allocated by the host node CU to the IAB node.

[0044] Figure 7 It is a schematic interactive diagram of another identification management method according to an embodiment of the present application.

[0045] Figure 8 This is a schematic interactive diagram of another identification management method according to an embodiment of the present application.

[0046] Figure 9 This is a schematic flowchart of a data packet routing selection according to an embodiment of the present application.

[0047] Figure 10 This is a schematic diagram of the CU-CP sending the IAB node IP layer identifier to the CU-UP.

[0048] Figure 11 This is a schematic interaction diagram of IAB node switching between different CUs.

[0049] Figure 12 This is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0050] Figure 13 It is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0052] In the description of this application, unless otherwise specified, " / " means or, for example, A / B can mean A or B. "And / or" in this article is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. Moreover, in the description of this application, unless otherwise specified, "multiple" means two or more than two. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different.

[0053] The technical solutions of the embodiments of the present application can be applied to various communication systems. For example: orthogonal frequency-division multiple access (OFDMA), single carrier frequency-division multiple access (SC-FDMA) and other systems. The term "system" can be interchangeable with "network". The OFDMA system can implement wireless technologies such as evolved universal terrestrial radio access (E-UTRA) and ultra mobile broadband (UMB). E-UTRA is an evolved version of the universal mobile telecommunications system (UMTS). The 3rd Generation Partnership Project (3GPP) in the long term evolution (LTE) and various versions based on LTE evolution are new versions using E-UTRA. The fifth-generation (5G) communication system using the new radio (NR) is the next generation communication system under study. In addition, the communication system can also be applicable to future-oriented communication technologies, and is applicable to the technical solutions provided in the embodiments of this application.

[0054] The network elements involved in this application include terminals and wireless backhaul nodes.

[0055] The terminal in the embodiment of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device. The terminal may also be a station (ST) in a wireless local area network (WLAN), and may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device (also referred to as a wearable smart device). The terminal may also be a terminal in a next-generation communication system, for example, a terminal in 5G or a terminal in a future-evolved public land mobile network (PLMN).

[0056] The wireless backhaul node is used to provide wireless backhaul services to nodes (e.g., terminals) that wirelessly access the wireless backhaul node. The wireless backhaul service refers to data and / or signaling backhaul services provided via the wireless backhaul link.

[0057] The system architecture and service scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. It is known to those skilled in the art that with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems. In the embodiments of the present application, the method provided is applied to an NR system or a 5G network as an example. However, it should be noted that the method provided in the embodiments of the present application can also be applied to other networks, for example, it can be applied to an evolved packet system (EPS) network (commonly known as a fourth generation (4G) network). Accordingly, when the method provided in the embodiments of the present application is applied to an EPS network, the network node executing the method provided in the embodiments of the present application can be replaced with a network node in the EPS network. For example, when the method provided in the embodiments of the present application is applied to a 5G network or an NR system, the wireless backhaul node hereinafter may be a wireless backhaul node in the 5G network. For example, the wireless backhaul node in the 5G network may be referred to as an IAB node. Of course, it may also have other names, and the embodiments of the present application do not specifically limit this. When the method provided in the embodiment of the present application is applied in an EPS network, the wireless backhaul node mentioned below may be a wireless backhaul node in the EPS network. For example, the wireless backhaul node in the EPS network may be called a relay node (RN).

[0058] With the development of technologies such as virtual reality (VR), augmented reality (AR), and the Internet of Things, there will be more and more terminals in future networks, and network data usage will continue to rise. To accommodate the increasing number of terminals and the rapidly growing market for network data usage, higher requirements are currently being placed on the capacity of 5G networks. In hotspot areas, to meet the ultra-high capacity requirements of 5G, the use of high-frequency small base stations is becoming increasingly popular. High-frequency carriers have poor propagation characteristics, are severely attenuated by obstructions, and have a limited coverage range. Therefore, a large number of small base stations need to be densely deployed in hotspots. These small base stations can serve as IAB nodes.

[0059] In order to design flexible and convenient access and backhaul solutions, both the access link (AL) and the backhaul link (BL) in the IAB scenario adopt wireless transmission solutions.

[0060] In a network including an IAB node (hereinafter referred to as the IAB network), the IAB node can provide wireless access services for the terminal and connect to the donor node through a wireless backhaul link to transmit the user's business data. Exemplarily, the donor node can be a host base station. The host node can be referred to as an IAB donor or DgNB (i.e., donor gNodeB) in a 5G network. The host node can be a complete entity, or it can be a form in which a centralized unit (CU) (referred to as Donor-CU or CU in this article) and a distributed unit (DU) (referred to as Donor-DU in this article) are separated, that is, the host node is composed of Donor-CU and Donor-DU. In the embodiments of the present application and the accompanying drawings, the method provided in the embodiments of the present application is exemplified by taking the example of the host node consisting of Donor-CU and Donor-DU as an example.

[0061] Among them, the Donor-CU can also be a form in which the user plane (UP) (abbreviated as CU-UP in this article) and the control plane (CP) (abbreviated as CU-CP in this article) are separated, that is, the Donor-CU consists of the CU-CP and the CU-UP.

[0062] The IAB node is connected to the core network via a wired link via the host node. For example, in a standalone 5G architecture, the IAB node is connected to the 5G core (5GC) via a wired link via the host node. In a non-standalone 5G architecture, the IAB node is connected to the evolved packet core (EPC) via an evolved NodeB (eNB) on the control plane and to the EPC via the host node and eNB on the user plane.

[0063] To ensure reliable service transmission, the IAB network supports multi-hop and multi-connection IAB node networking. Therefore, multiple transmission paths may exist between a terminal and a host node. Within a path, IAB nodes maintain a defined hierarchical relationship between each other and between IAB nodes and the host node they serve. Each IAB node considers the node providing backhaul services to be its parent node. Accordingly, each IAB node can be considered a child of its parent node.

[0064] For example, see Figure 1, the parent node of IAB node 1 is the host node, and IAB node 1 is the parent node of IAB node 2 and IAB node 3. IAB node 2 and IAB node 3 are both the parent nodes of IAB node 4, and the parent node of IAB node 5 is IAB node 3. The uplink data packet of the terminal can be transmitted to the host node through one or more IAB nodes, and then sent by the host node to the mobile gateway device (such as the user plane function (UPF) network element in the 5G network). The downlink data packet will be received by the host node from the mobile gateway device and then sent to the terminal through one or more IAB nodes. There are two available paths for the transmission of data packets between terminal 1 and the host node, namely: terminal 1→IAB node 4→IAB node 3→IAB node 1→host node, and terminal 1→IAB node 4→IAB node 2→IAB node 1→host node. There are three available paths for data packet transmission between terminal 2 and the host node, namely: terminal 2 → IAB node 4 → IAB node 3 → IAB node 1 → host node, terminal 2 → IAB node 4 → IAB node 2 → IAB node 1 → host node, and terminal 2 → IAB node 5 → IAB node 2 → IAB node 1 → host node.

[0065] It is understandable that in an IAB network, a transmission path between a terminal and a host node may include one or more IAB nodes. Each IAB node needs to maintain a wireless backhaul link to the parent node, and also needs to maintain a wireless link to the child node. If an IAB node is a node accessed by a terminal, there is a wireless access link between the IAB node and the child node (i.e., the terminal). If an IAB node is a node that provides backhaul services to other IAB nodes, there is a wireless backhaul link between the IAB node and the child node (i.e., other IAB nodes). For example, see Figure 1 In the path "terminal 1 → IAB node 4 → IAB node 3 → IAB node 1 → host node", terminal 1 accesses IAB node 4 via a wireless access link, IAB node 4 accesses IAB node 3 via a wireless backhaul link, IAB node 3 accesses IAB node 1 via a wireless backhaul link, and IAB node 1 accesses the host node via a wireless backhaul link.

[0066] For example, the IAB node may be a customer premises equipment (CPE), a residential gateway (RG), etc. In this case, the method provided in the embodiment of the present application may also be applied to a home access scenario.

[0067] The above IAB networking scenarios are merely exemplary. In the IAB scenario combining multi-hop and multi-connection, there are many other possibilities for IAB networking scenarios, for example, a host node and an IAB node under another host node form a dual connection to serve the terminal, etc., which are not listed here one by one.

[0068] In order to make the embodiments of the present application clearer, some contents and concepts related to the embodiments of the present application are uniformly introduced here below.

[0069] 1. Link, the node's previous hop node, the node's next hop node, the node's ingress link (ingresslink), and the node's egress link (egress link)

[0070] Link: refers to the path between two adjacent nodes in a path.

[0071] The previous hop node of a node refers to the node that receives the data packet last before the node in the path containing the node.

[0072] The next hop node of a node refers to the first node that receives a data packet after the node in the path containing the node.

[0073] A node's ingress link refers to the link between the node and its previous-hop node, also known as the node's previous-hop link.

[0074] The node's egress link refers to the link between the node and its next-hop node, also known as the node's next-hop link.

[0075] 2. Access IAB nodes and intermediate IAB nodes

[0076] The access IAB node in the embodiment of the present application refers to the IAB node accessed by the terminal, and the intermediate IAB node refers to the IAB node that provides wireless backhaul services to other IAB nodes (eg, the access IAB node or other intermediate IAB nodes).

[0077] For example, see Figure 1 In the path "Terminal 1 → IAB Node 4 → IAB Node 3 → IAB Node 1 → Host Node", IAB Node 4 is the access IAB node, and IAB Node 3 and IAB Node 1 are intermediate IAB nodes. IAB Node 3 provides backhaul services for IAB Node 4, and IAB Node 1 provides backhaul services for IAB Node 3.

[0078] It should be noted that an IAB node is an access IAB node for terminals accessing it. For terminals accessing other IAB nodes, it is an intermediate IAB node. Therefore, whether an IAB node is an access IAB node or an intermediate IAB node is not fixed and depends on the specific application scenario.

[0079] 3. Composition of IAB nodes

[0080] An IAB node can have the role of a mobile terminal (MT) and the role of a DU. When an IAB node faces its parent node, it can be regarded as a terminal. At this time, the IAB node plays the role of an MT. When an IAB node faces its child node (the child node may be a terminal or the terminal part of another IAB node), it can be regarded as a network device. At this time, the IAB node plays the role of a DU. Therefore, it can be considered that an IAB node consists of an MT part and a DU part. An IAB node can establish a backhaul connection with at least one parent node of the IAB node through the MT part. The DU part of an IAB node can provide access services for the MT part of a terminal or another IAB node.

[0081] For example, see Figure 2 The terminal connects to the donor node through IAB node 2 and IAB node 1. Both IAB node 1 and IAB node 2 include a DU and a MT. The DU of IAB node 2 provides access services to the terminal. The DU of IAB node 1 provides access services to the MT of IAB node 2. The Donor-DU provides access services to the MT of IAB node 1.

[0082] 4. Protocol stack architecture of intermediate IAB nodes, access IAB nodes, Donor-DU, Donor-CU, and terminals

[0083] The protocol stack of the intermediate IAB node in the user plane and the control plane is the same. Among them, the MT part and the DU part of the intermediate IAB node may not share the Adapt layer, for example Figure 3 (a). The MT part and DU part of the intermediate IAB node can also share the Adapt layer, for example Figure 3 (b).

[0084] The protocol stacks for accessing IAB nodes on the user plane and control plane are different, see Figure 3 (c) and Figure 3 (d).

[0085] For example, based on Figure 3 For the example shown, the user plane protocol stack architecture of each node can be found in Figure 4(a), the control plane protocol stack architecture of each node can be found in Figure 4 (b). Among them, Figure 4 The diagram is drawn with the example that the MT part and DU part of the intermediate IAB node do not share the Adapt layer. Figures 3 and 4 The meanings of the various protocol layers are: packet data convergence protocol (PDCP) layer, general packet radio service tunneling protocol user plane (GTP-U) layer, user datagram protocol (UDP) layer, internet protocol (IP) layer, L2 layer (layer 2), L1 layer (layer 1), radio link control (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, radio resource control (RRC) layer, F1 application protocol (F1AP) layer, stream control transmission protocol (SCTP) layer. Among them, the L2 layer is the link layer, and exemplarily, the L2 layer can be the data link layer in the open systems interconnection (OSI) reference model. The L1 layer can be the physical layer, and exemplarily, the L1 layer can be the physical layer in the OSI reference model.

[0086] It should be noted that Figure 4 In the figure, we take the example of the host node consisting of Donor-DU and Donor-CU. Figure 4 The protocol layers of the Donor-DU and Donor-CU are shown in . If the host node is a fully functional entity, the host node only needs to retain the protocol stacks of the Donor-DU and Donor-CU interfaces to external nodes, and does not need the protocol layers on the internal interface between the Donor-DU and Donor-CU.

[0087] In addition, it should be noted that, regardless of the protocol stack architecture of the control plane or the protocol stack architecture of the user plane, when the Donor-DU is the proxy node of the F1 interface between the Donor-CU and the IAB node, the protocol stack architecture facing the IAB node in the Donor-DU, above the IP layer, also includes a UDP layer and a GTP-U layer that are respectively equivalent to the UDP layer and the GTP-U layer in the protocol stack architecture of the DU part accessing the IAB node.

[0088] 5. F1 interface, F1 interface protocol layer

[0089] The F1 interface is the logical interface between the DU portion of the IAB node and the donor node (or Donor-CU or Donor-DU). The F1 interface, also known as the F1* interface, supports both the user plane and the control plane. The protocol layer of the F1 interface refers to the communication protocol layer on the F1 interface.

[0090] Exemplarily, the user plane protocol layer of the F1 interface may include one or more of an IP layer, a UDP layer, and a GTP-U layer. Optionally, the user plane protocol layer of the F1 interface may also include a PDCP layer and / or an IP Security (IPsec) layer.

[0091] Exemplarily, the control plane protocol layer of the F1 interface may include one or more of an IP layer, an F1AP layer, and an SCTP layer. Optionally, the control plane protocol layer of the F1 interface further includes one or more of a PDCP layer, an IPsec layer, and a datagram transport layer security (DTLS) layer.

[0092] Example 1

[0093] Figure 5 A schematic interactive diagram of an identification management method according to an embodiment of the present application is shown. Figure 5 ,IAB Donor can assign an identity to IAB node #1. The IAB donor base station has a wired connection to the core network. IAB node #1 is connected to the IAB donor base station via a wireless backhaul link, thereby connecting the UE served by IAB node #1 to the core network.

[0094] In S501, IAB node #1 sends indication information #1 to the host node.

[0095] During startup, IAB node #1 accesses the network as a mobile operator (MT) through a parent node. After or during network access, IAB node #1 can send indication information #1 to the donor node, indicating that it is an IAB node and can provide wireless access and wireless backhaul services. For example, IAB node #1 can include indication information in an RRC message sent to an IAB donor, indicating that IAB node #1 is an integrated access and backhaul node and can provide wireless access and wireless backhaul services.

[0096] Optionally, if the host node includes a host CU (abbreviated as CU) and a host DU part, the IAB node #1 sends the indication information #1 to the CU via the host DU.

[0097] At S502, the host node obtains identification information #E1 of the IAB node #1.

[0098] The host node may obtain the identification information #E1 of the IAB node #1 by receiving the identification information #E1 of the IAB node #1 from a core network element. Alternatively, the host node may obtain the identification information #E1 of the IAB node #1 by receiving the indication information sent by the IAB node #1, determining that the IAB node #1 is an integrated access and backhaul node, and allocating the identification information #E1 to the IAB node #1. The identification information #E1 is used to uniquely identify the IAB node #1 on the wireless backhaul link within the service range of the host node.

[0099] As an example but not a limitation, the identification information #E1 is the adaptation layer identifier (adapt ID) of the IAB node. The adaptation layer identifier is unique within the service scope of the host node, that is, the adaptation layer identifiers of the IAB nodes served by the host node are different.

[0100] Optionally, the identification information #E1 includes the identification of the host node and identification information specific to the IAB node #1.

[0101] As an example and not a limitation, the identification information #E1 can also be any one of the following identifiers: the IP address assigned by OAM to IAB#1; or the cell identifier served by the DU part of the IAB node, which can specifically be the global cell identifier (E-UTRAN Cell Global Identifier, E-UTRAN) in the 4G network, or the global cell identifier (NR cell global identifier, NCGI) in the 5G NR network, etc.; or, the identifier assigned by the core network element AMF / MME to the MT part of the IAB node, for example, various types of temporary user identities (Temporary Mobile Subscriber Identity, TMSI), or globally unique temporary UE Identity (Globally Unique Temporary UE Identity, GUTI), such as MME-TMSI, 5G-TMSI, 4G-GUTI, 5G-GUTI, etc.

[0102] In S503, the host node sends identification information #E1 to the IAB node #1.

[0103] For example, the donor node may send the identification information #E1 to the MT part of the IAB node #1 through an RRC message, or the CU may send the identification information #E1 to the DU part of the IAB node #1 through an F1AP message.

[0104] It should be understood that if the host node includes a host CU (abbreviated as CU) and a host DU part, the host node in the embodiment of the present application can also be replaced by CU for understanding. Optionally, if the CU includes a CU-CP and a CU-UP, the host node in the embodiment of the present application can also be replaced by CU-CP for understanding.

[0105] In an optional embodiment, as Figure 5 As shown, if the host node includes a host CU (abbreviated as CU) and a host DU part, the method provided in the embodiment of the present application further includes:

[0106] In S504, the CU sends configuration information #S1 to the Donor DU. The configuration information #S1 includes identification information #E1 of the IAB node #1 and the IP layer identifier of the IAB node #1.

[0107] Optionally, the configuration information #S1 further includes identification information #E2 of the IAB node #2, where the IAB node #2 is a child node of the IAB node #1, that is, a next-hop node of the IAB node #1.

[0108] When the CU is in a form where the control plane (CP) and the user plane (UP) are separated, the CU in step S504 may also be replaced with CU-CP for further understanding.

[0109] When the host node is in a form where the CU and DU are separated, data needs to be forwarded between the CU and IAB node #1 through the Donor DU. Therefore, the CU will send configuration information #S1 to configure routing for the Donor DU. Since the IP layer is used to route data packets between the CU and the Donor DU, and the Donor DU uses the adaptation layer to route data packets in the backhaul link, the routing configuration information sent by the CU to the Donor DU includes the adaptation layer identifier #E1 of IAB node #1 and the IP layer identifier of IAB node #1. This allows the Donor DU to maintain the correspondence between the adaptation layer identifier #E1 of IAB node #1 and the IP layer identifier. This allows the donor DU to add the adaptation layer identifier #E1 of IAB node #1 to the downlink data packet #D1 when receiving the downlink data packet #D1 whose IP layer destination address is the IP layer identifier of IAB node #1, so that routing can be performed when the downlink data packet #D1 is transmitted over the wireless backhaul link. The CU configures the identifier of the next hop node to IAB node #1 for the donor DU, so that the donor DU can select an appropriate next hop node for the data packet sent to IAB node #1.

[0110] Optionally, the configuration information #S1 sent by the CU to the Donor DU may be included in the F1AP message sent by the CU to the Donor DU and transmitted via the peer F1AP protocol layer between the CU and the Donor DU.

[0111] In an optional embodiment, as Figure 5 As shown, the method provided in the embodiment of the present application also includes:

[0112] At S505, identification information #E1 is sent to the parent node of IAB node #1.

[0113] There are two different situations for S505, which are introduced below.

[0114] Case 1: The host node sends identification information #E1 of IAB node #1 to the parent node of IAB node #1.

[0115] Case 2: IAB node #1 sends identification information #E1 of IAB node #1 to the parent node of IAB node #1.

[0116] For example Figure 5In the example, IAB Node #2 is the parent node of IAB Node #1. Therefore, for scenario 1, the host node can send IAB Node #1's identification information #E1 to the MT portion of IAB Node #2 via an RRC message; alternatively, the host node can send IAB Node #1's identification information #E1 to the DU portion of IAB Node #2 via an F1AP message. For scenario 2, IAB Node #1 can send IAB Node #2's identification information #E1 via a MAC layer control element.

[0117] The parent node of IAB node #1 (such as Figure 5 IAB node #2 in the parent node may allocate identification information #E3 to IAB node #1. Identification information #E3 is used to identify IAB node #1 within the cell served by IAB node #2. Exemplarily, identification information #E3 may be a Cell Radio Network Temporary Identifier (C-RNTI) allocated by the parent node to the MT portion of IAB node #1. After step S505, IAB node #2 may maintain a correspondence between identification information #E1 of IAB node #1 and identification information #E3. When IAB node #2 determines to send data packet #D1 to IAB node #1 based on identification information #E1, it uses identification information #E3 to send data packet #D1 to IAB node #1 within the cell served by IAB node #2.

[0118] Through the method shown in the embodiment of the present application, the IAB node can obtain identification information in the wireless backhaul link within the service range of the host node. This identification information can be used as routing information for data packets in the wireless backhaul link, thereby solving the routing problem of data packets in the wireless backhaul link.

[0119] Figure 6 A schematic diagram showing identification information allocated by a host node to an IAB node is shown.

[0120] In an embodiment of the present application, the host node may assign identification information #E1 to the IAB node. This identification information #E1 is used to uniquely identify the IAB node #1 in a wireless backhaul link within the host node's service range. As one possible example, this identification information #E1 includes the host node's identifier (prefix information specific to the host node) and identification information specific to the IAB node #1.

[0121] Example 2

[0122] Figure 7 A schematic interactive diagram of another identification management method provided by the present application is shown.

[0123] In S701, the CU obtains the adaptation layer identifier #D1 of the donor DU.

[0124] For example, the CU may receive the adaptation layer identifier #D1 of the DU from a core network element, or the CU may allocate the adaptation layer identifier #D1 to the donor DU.

[0125] In S702, the CU sends the adaptation layer identifier #D1 to the donor DU.

[0126] For example, the CU sends the adaptation layer identifier #D1 to the donor DU through the F1AP message.

[0127] In S703, the CU sends configuration information #S2 to the IAB node #1, where the configuration information #S2 includes the adaptation layer identifier #D1 of the donor DU.

[0128] Exemplarily, the CU may send configuration information #S2 to the IAB node #1 via an RRC message (e.g., an RRC message sent to the MT part of the IAB node #1); or, the CU may send configuration information #S2 to the IAB node #1 via an F1AP message (e.g., an F1AP message sent to the DU part of the IAB node #1).

[0129] Optionally, the configuration information #S2 further includes an identifier of a next-hop node for uplink transmission from the IAB node #1 to the donor DU.

[0130] Therefore, when the IAB node #1 sends uplink data to the host node, it can add routing information according to the configuration information #S2 and perform route selection.

[0131] Example 3

[0132] Figure 8 A schematic interactive diagram of another identification management method provided by this application is shown. Figure 8 The adaptation layer identifier of the IAB node is configured by the network side, and the IAB node can obtain the identifier information from the management network element in the core network.

[0133] At S801, the IAB node #1 obtains identification information #E1 of the IAB node #1.

[0134] The IAB node #1 obtains identification information #E1 from the management network element in the core network. The identification information #E1 is used to uniquely identify the IAB node #1 in the wireless backhaul link within the service range of the host node.

[0135] The identification information #E1 can be any one of the following identifiers: the IP address obtained by the IAB node from the OAM; or the cell identifier served by the DU part of the IAB node, which can be the global cell identifier (E-UTRAN CellGlobal Identifier, E-UTRAN) in the 4G network, or the global cell identifier (NR cell global identifier, NCGI) in the 5G NR network; or the identifier allocated by the core network element AMF / MME to the MT part of the IAB node, for example, various types of temporary user identifiers (Temporary Mobile Subscriber Identity, TMSI), or globally unique temporary identifiers (Globally Unique Temporary UE Identity, GUTI), such as MME-TMSI, 5G-TMSI, 4G-GUTI, 5G-GUTI, etc.; or, an identifier pre-configured in the IAB node #1, for example, the International Mobile Subscriber Identification Number (IMSI) of the MT part, the Subscription Permanent Identifier (SUPI), the Subscription Hidden Identifier (SUPI) Concealed Identifier, SUCI), International Mobile Equipment Identity (IMEI), Permanent Equipment Identifier (PEI), etc.

[0136] At S802, the IAB node #1 sends identification information #E1 of the IAB node #1 to the host node.

[0137] Exemplarily, the MT part of the IAB node #1 sends an RRC message to the host node, which includes the identification information #E1 of the IAB node #1; or, the DU part of the IAB node #1 sends an F1AP message to the host node, which includes the identification information #E1 of the IAB node #1.

[0138] In an optional embodiment, as Figure 8 As shown, if the host node includes a host CU (abbreviated as CU) and a host DU, the method provided in the embodiment of the present application further includes:

[0139] In S803 , the CU sends configuration information # S1 to the Donor DU. The configuration information # S1 includes identification information # E1 of the IAB node # 1 and the IP layer identifier of the IAB node # 1 .

[0140] Optionally, the configuration information #S1 further includes identification information #E2 of the IAB node #2, where the IAB node #2 is a child node of the IAB node #1, that is, a next-hop node of the IAB node #1.

[0141] The details of step S803 can be understood by referring to step S504 and will not be described in detail.

[0142] In an optional embodiment, as Figure 8 As shown, the method provided in the embodiment of the present application also includes:

[0143] At S804, identification information #E1 is sent to the parent node of IAB node #1.

[0144] There are two different situations in S804, which are introduced below.

[0145] Case 1: The host node sends identification information #E1 of IAB node #1 to the parent node of IAB node #1.

[0146] Case 2: IAB node #1 sends identification information #E1 of IAB node #1 to the parent node of IAB node #1.

[0147] The details of step S804 can be understood by referring to step S505 and will not be described in detail.

[0148] Example 4

[0149] If the host node contains the host CU (abbreviated as CU) and the host DU part, Figure 9 A schematic flowchart of data packet routing selection according to an embodiment of the present application is shown.

[0150] At S901, the Donor DU receives a data packet #D1, which includes an IP layer identifier of a target IAB node (eg, IAB node #1).

[0151] At S902, identification information #E1 of target IAB node #1 is added to data packet #D1.

[0152] In S903, the donor DU determines the next hop node (for example, IAB node #2). Specifically, the donor DU determines the next hop node according to the received configuration information #S1.

[0153] In the embodiment of the present application, the configuration information #S1 includes identification information #E1 of the IAB node #1, the IP layer identifier of the IAB node #1, and the next hop node identifier.

[0154] At S904, the data packet #D1 with identification information #E1 added thereto is sent to the next hop node of Donor Du.

[0155] Example 5

[0156] Figure 10 The diagram shows a schematic diagram of the CU-CP sending the IP layer identifier of the IAB node to the CU-UP.

[0157] In an embodiment of the present application, the host node includes a Donor DU and a CU, wherein the centralized unit CU is divided into a CU-CP and a CU-UP, and the CU-CP can notify the CU-UP of the IP layer identifier of the IAB node #1.

[0158] As an example but not a limitation, routing can be performed between the CU-UP and the Donor DU via the IP layer, and the CU-CP can send the IP layer identifier of the IAB node #1 to the CU-UP via the E1 interface, where the E1 interface is the interface between the CU-CP and the CU-UP.

[0159] The CU-CP may allocate an IP layer identifier for the IAB node #1, or the CU-CP may obtain the IP layer identifier of the IAB node #1. The CU-CP may obtain the IP layer identifier of the IAB node #1 by receiving the IP layer identifier of the IAB node #1 sent from a core network element, or by receiving the IP layer identifier of the IAB node #1 sent by the IAB node #1.

[0160] At S1001 , the CU-CP obtains the IP layer identifier of the IAB node # 1 .

[0161] The IP layer identifier in the embodiment of the present invention may be, for example, an IPv4 address or an IPv6 address.

[0162] Exemplarily, the CU-CP acquires the IP layer identifier of the IAB node #1 in the following manner: the CU-CP allocates the IP layer identifier to the IAB node #1; or

[0163] IAB node #1 obtains the IP layer identifier from the core network element (such as OAM, PGW, or SMF), and IAB node #1 sends the IP layer identifier of IAB node #1 to CU-CP; or,

[0164] The core network element of the IAB node (eg, the mobility management function network element AMF) sends the IP layer identifier of the IAB node #1 to the CU-CP.

[0165] At S1002 , the CU-CP sends the IP layer identifier of the IAB node # 1 to the CU-UP.

[0166] In an embodiment of the present application, after the CU-CP sends the IP layer identifier of the IAB node #1 to the CU-UP, the CU-UP can use the IP layer identifier of the IAB node #1 and add it to the data packet that needs to be sent to the IAB node #1, so as to facilitate the IP layer routing of the data packet between the CU-UP and the donor DU.

[0167] Example 6

[0168] Figure 11 A schematic interaction diagram showing the switching of an IAB node between different host nodes is shown.

[0169] See also Figure 11 ,When the topology of the IAB network is updated, that is, IAB node #1 switches from the source ,host node to the target host node, the identification information used for ,routing in the wireless backhaul link needs to be changed.

[0170] In S1101 , host node #1 sends handover request information of IAB node #1 to host node #2.

[0171] Specifically, the source host node #1 sends a handover request message of the IAB node #1 to the target host node #2. The handover request message is used to request the IAB node #1 to connect to the host node #2.

[0172] At S1102, the host node #2 allocates identification information #E4 to the IAB node #1.

[0173] Specifically, the target host node #2 allocates an adaptation layer identifier #E4 to the IAB node #1. The identifier #E4 is used to uniquely identify the IAB node #1 in the wireless backhaul link within the service range of the host node #2.

[0174] At S1103 , the target host node # 2 sends identification information # E4 to the source host node # 1 .

[0175] At S1104, the source host node #1 sends identification information #E4 to the IAB node #1.

[0176] For example, the source host node #1 carries the identification information #E4 of the IAB node #1 in the handover command sent to the IAB node #1.

[0177] It should be understood that if the host node includes a host CU (abbreviated as CU) and a host DU part, the host node in the embodiment of the present application can also be replaced by CU for understanding. Optionally, if the CU includes a CU-CP and a CU-UP, the host node in the embodiment of the present application can also be replaced by CU-CP for understanding.

[0178] In an embodiment of the present application, when the IAB node pre-acquires identification information in the wireless backhaul link within the service range of the target host node during the switching process between different host nodes, the delay of the IAB node during the switching process between host nodes can be reduced.

[0179] See also Figure 12 , Figure 12 1 is a schematic diagram of the structure of a network device 1000 provided by this application. The network device 1000 is used to implement the function of the host node in the method embodiment. Figure 12 As shown, network device 1000 includes an antenna 1101, a radio frequency device 1102, and a baseband device 1103. Antenna 1101 is connected to radio frequency device 1102. Baseband device 1103 may include one or more processing units 11031. Baseband device 1103 may also include a storage unit 11032 and a communication interface 11033. Storage unit 11032 is used to store programs and data. Communication interface 11033 is used to exchange information with radio frequency device 1102. Communication interface 11033 may be an input / output interface or an input / output circuit.

[0180] The network device 1000 in the apparatus embodiment of the present application may correspond to the host node in the method embodiment, and the corresponding units included in the network device 1000 are used to execute the corresponding steps performed by the host node #1 in the method embodiment.

[0181] For example, the radio frequency device 1102 receives indication information sent by the IAB node #1 via the antenna 1101. The indication information is used to indicate that the IAB node #1 can be used to provide wireless backhaul services. The radio frequency device 1102 sends identification information to the IAB node #1 via the antenna 1101. The identification information includes the identification information of the IAB node #1 and the identification information of the donor base station. The identification information is used to identify the IAB node #1 in the wireless backhaul link served by the donor base station.

[0182] For another example, the radio frequency device 1102 sends identification information #E1 to the IAB node #2 through the antenna 1101, where the IAB node #2 is the parent node of the IAB node #1, that is, the IAB node #1 reports the identification information #E1 allocated by the host base station to the IAB node #1 to the parent node.

[0183] For another example, the host base station includes a distributed unit DU and a centralized unit CU, and the distributed unit DU receives configuration information sent by the centralized unit CU; the configuration information includes the adaptation layer identifier of IAB node #1, the IP layer identifier of IAB node #1, and the identification information of IAB node #3; wherein IAB node #3 is a child node of the host base station.

[0184] For another example, the donor base station includes a distributed unit (DU) and a centralized unit (CU). The distributed unit (DU) receives data packet #D1 sent by the centralized unit (CU). Data packet #D1 includes the IP layer identifier and data of IAB node #1. The DU sends data packet #D2 to the IAB node #1 based on configuration information #S101. The data packet #D2 includes the IP layer identifier, adaptation layer identifier, and data of IAB node #1.

[0185] For another example, the CU obtains the donor DU's adaptation layer identifier #D1, sends the adaptation layer identifier #D1 to the donor DU, and then sends configuration information #S2 to IAB node #1. Configuration information #S2 includes the donor DU's adaptation layer identifier #D1. Alternatively, configuration information #S2 may also include the identifier of the next-hop node for uplink transmission from IAB node #1 to the donor DU. Thus, when IAB node #1 sends uplink data to the donor node, it can select a route based on configuration information #S2.

[0186] Exemplarily, the CU may send configuration information #S2 to the IAB node #1 via an RRC message (e.g., an RRC message sent to the MT part of the IAB node #1); or, the CU may send configuration information #S2 to the IAB node #1 via an F1AP message (e.g., an F1AP message sent to the DU part of the IAB node #1).

[0187] For another example, the host base station includes a distributed unit DU and a centralized unit CU, the CU includes a control plane CU-CP and a user plane CU-UP, the CU-CP is used to obtain the IP layer identifier of the IAB node #1 and send the IP layer identifier of the IAB node #1 to the CU-UP.

[0188] For another example, when the IAB node #1 switches from the host base station #1 to the host base station #2, the host base station #1 sends a request message to the host base station #2, where the request message is used to request the IAB node #1 to switch to the host base station #2; the host base station #1 receives the identification information #E4 sent by the host base station #2; the host base station #1 sends the identification information #E4 to the host base station #2, where the identification information #E4 is used to identify the IAB node #1 in the wireless backhaul link served by the host base station #2.

[0189] Since the IAB node can obtain identification information in the wireless backhaul link within the service range of the host node, the identification information can be used as routing information for data packets in the wireless backhaul link, thereby solving the routing problem of data packets in the wireless backhaul link.

[0190] In one implementation, the unit that implements each step of the above method in the donor base station can be implemented in the form of a processing unit scheduling program. For example, the processing unit 11031 calls the program stored in the storage unit 11032 to execute the method performed by the donor base station in the above method embodiment. The storage unit 11032 can be on the same chip as the processing unit 11031, that is, an on-chip storage unit, or it can be a storage element on a different chip from the processing unit 11031, that is, an off-chip storage unit.

[0191] See also Figure 13 , Figure 13 2 is a schematic diagram of the structure of a network device 2000 provided by this application. The network device 2000 is used to implement the function of the IAB node #1 in the method embodiment. Figure 13 As shown, network device 2000 includes an antenna 2101, a radio frequency device 2102, and a baseband device 2103. Antenna 2101 is connected to radio frequency device 2102. Baseband device 2103 may include one or more processing units 21031. Furthermore, baseband device 2103 may include a storage unit 21032 and a communication interface 21033. Storage unit 21032 is used to store programs and data. Communication interface 21033 is used to exchange information with radio frequency device 2102. Communication interface 21033 may be an input / output interface or an input / output circuit.

[0192] The network device 2000 in the apparatus embodiment of the present application may correspond to the IAB node #1 in the method embodiment, and the corresponding units included in the network device 2000 are used to execute the corresponding steps executed by the IAB node #1 in the method embodiment.

[0193] For example, during the startup process, IAB node #1 accesses the network through the parent node as an MT. After accessing the network or during the process of accessing the network, IAB node #1 can send indication information #1 to the host node to indicate that it is an IAB node and can be used to provide wireless access and wireless backhaul services.

[0194] For example, the radio frequency device 2102 sends indication information to the donor base station via antenna 2101. This indication information can be used to indicate that the IAB node #1 can be used to provide wireless backhaul services. The radio frequency device 2102 receives identification information sent by the donor base station via antenna 2101. This identification information includes identification information of the IAB node #1 and identification information of the donor base station. This identification information is used to identify the IAB node #1 in the wireless backhaul link served by the donor base station.

[0195] For another example, the radio frequency device 2102 sends identification information #E1 to the IAB node #2 through the antenna 2101, where the IAB node #2 is the parent node of the IAB node #1, that is, the IAB node #1 reports the identification information #E1 allocated by the host base station to the IAB node #1 to the parent node.

[0196] For another example, when IAB node #1 switches from host base station #1 to host base station #2, IAB node #1 receives identification information #E4 sent by host base station #1, and identification information #E4 is used to identify IAB node #1 in the wireless backhaul link served by host base station #2.

[0197] For another example, the processing unit 21031 obtains the identification information #E1 of the IAB node #1, and the radio frequency device 2102 sends the identification information #E1 of the IAB node #1 to the donor base station #1 through the antenna 2101.

[0198] The device 2000 described in the above device embodiment may be a chip on the baseband device 2103, which includes at least one processing unit and an interface circuit. The processing unit is used to execute the steps of any of the methods performed by the above IAB node #1, and the interface circuit is used to communicate with other devices.

[0199] In one implementation, the unit that implements each step of the above method in IAB node #1 can be implemented in the form of a processing unit scheduler. For example, processing unit 21031 invokes a program stored in storage unit 21032 to execute the method performed by IAB node #1 in the above method embodiment. Storage unit 21032 can be on the same chip as processing unit 21031, i.e., an on-chip storage unit, or it can be a storage element on a different chip from processing unit 21031, i.e., an off-chip storage unit.

[0200] In addition, the present application provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the computer executes the corresponding operations and / or processes performed by the IAB node or the host node in any method embodiment.

[0201] The present application also provides a computer program product, which includes computer program code. When the computer program code is executed on a computer, the computer executes the method for identity management in an embodiment of the present application or the corresponding operations and / or processes performed by the IAB node or the host node in any method embodiment.

[0202] The present application also provides a chip including a processor configured to call and run a computer program stored in a memory to execute the corresponding operations and / or processes performed by the IAB node or the host node in the identity management method of an embodiment of the present application.

[0203] Optionally, the chip further includes a memory connected to the processor, and the processor is configured to read and execute a computer program in the memory.

[0204] Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive signals and / or data to be processed, and the processor obtains the signals and / or data from the communication interface and processes them.

[0205] Optionally, the communication interface may be an input / output interface, specifically including an input interface and an output interface. Alternatively, the communication interface may be an input / output circuit, specifically including an input circuit and an output circuit.

[0206] The memory and storage involved in the above embodiments may be physically independent units, or the memory may be integrated with the processor.

[0207] In each of the above embodiments, the processor may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the technical solution of the present application. For example, the processor may be a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, etc. The processor may distribute the control and signal processing functions of the terminal device or network device among these devices according to the respective functions of these devices. In addition, the processor may have the function of operating one or more software programs, and the software programs may be stored in a memory. The functions of the processor may be implemented by hardware, or may be implemented by executing corresponding software through hardware. The hardware or software includes one or more modules corresponding to the above functions.

[0208] The memory may be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0209] In the embodiments of the present application, "and / or" describes the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can represent the existence of A alone, the existence of A and B at the same time, or the existence of B alone. A and B can be singular or plural.

[0210] Those skilled in the art will appreciate that the units described in the various examples of the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application.

[0211] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0212] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0213] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0214] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0215] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for switching between host nodes in an integrated access and backhaul IAB system, characterized in that: include: Host node 1 sends a handover request message to host node 2, where the handover request message is used to request that IAB node 1 be handed over to host node 2. Host node 1 receives the adaptation layer identifier of IAB node 1 under host node 2 sent by host node 2; The host node 1 sends the adaptation layer identifier of the IAB node 1 under the host node 2 to the IAB node 1 .

2. The method according to claim 1, wherein The adaptation layer identifier of the IAB node 1 under the host node 2 is carried in the handover command sent by the host node 1 to the IAB node 1 .

3. A method for switching between host nodes in an IAB system, characterized in that: include: Host node 2 receives the handover request information sent by host node 1, where the handover request information is used to request handover of IAB node 1 to host node 2; Host node 2 allocates the adaptation layer identifier of IAB node 1 under host node 2 to the IAB node; The host node 2 sends the adaptation layer identifier of the IAB node 1 under the host node 2 to the host node 1 .

4. A communication device comprising a processor and a memory storing computer instructions, wherein: The computer instructions are executed by the processor to enable the communication device to perform the method according to any one of claims 1 to 3.

5. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 3.

6. A chip, characterized in that: The method comprises a processor configured to read a computer program from a computer program server to execute the method according to any one of claims 1 to 3.

7. A communication system comprising: A host node 1 for executing the method according to claim 1 or 2 and a host node 2 for executing the method according to claim 3.

Images