Method and apparatus for identity management

Abstract

The present application provides a method and apparatus for identity management. The method includes: a first host node receiving first indication information sent by a first node, where the first indication information is used to indicate that the first node can be used to provide a wireless backhaul service; the first host node sending a first identity to the first node, where the first identity is used to uniquely identify the first node in a wireless backhaul link within the service range of the first host node. The method and apparatus for identity management in the present application can enable a data packet to perform routing during the air interface transmission process in an IAB network, improving the data transmission efficiency in the IAB network.

Description

[0001] This application is a divisional application of the original Chinese application filed with the National Intellectual Property Administration on February 15, 2019, with the application number "201910117983.X". The original application is incorporated herein by reference in its entirety for all purposes relevant to this divisional application. Technical Field

[0002] This application relates to the field of communications, and more particularly, to a method and apparatus for identifier management. Background Art

[0003] In a network including integrated access and backhaul (IAB) nodes, there are multiple transmission links in the transmission path between a user equipment (UE) and an IAB donor (also referred to as a donor node or a donor gNB), 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. When a data packet is transmitted between the UE and the IAB donor, it needs to pass through multiple intermediate nodes. Both the donor node and the IAB node need to perform routing selection to determine the next-hop node and then forward the packet. The routing selection needs to be based on the routing information carried in the data packet. For downlink transmission, the identifier of the IAB node can be used as the routing information during the transmission of the data packet on the wireless backhaul link. Although the IAB node can obtain a Cell Radio Network Temporary Identifier (C-RNTI) from its parent node, this identifier information is only used to uniquely identify the IAB node within the cell served by the parent node, and this identifier information cannot be used to address the IAB node on the wireless backhaul link within the service range of the donor node. Therefore, how to adopt an effective method for managing the identifier of the IAB node has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a method and apparatus for identifier management, which can reduce the routing overhead during the air interface transmission in the IAB network, thereby improving the data transmission efficiency 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, where the first indication information is used to indicate that the first node can be used to provide a wireless backhaul service; the first host node sends a first identity to the first node, and the first identity is used to uniquely identify the first node in a wireless backhaul link within the service range of the first host node.

[0006] In combination with the first aspect, in some implementation manners of the first aspect, the first identity includes the identity of the first host node and identity information specific to the first node.

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

[0008] In combination with the first aspect, in some implementation manners of the first aspect, the method further includes: the first host node sends the first identity to a second node, and the second node is the parent node of the first node.

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

[0010] In combination with the first aspect, in some implementation manners of the first aspect, the first host node includes a distributed unit DU and a central unit CU, and the method further includes: the distributed unit DU receives first configuration information sent by the central unit CU; the first configuration information includes the identity of the first node and the IP layer identity of the first node.

[0011] Optionally, the first configuration information further includes the identity 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 on Donor DU.

[0013] In combination with the first aspect, in some implementation manners of the first aspect, the first host node includes a distributed unit DU and a central unit CU, and the central unit CU includes a control plane CU-CP and a user plane CU-UP; the method further includes: CU-CP obtains the IP layer identity of the first node, and CU-CP sends the IP layer identity of the first node to the CU-UP.

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

[0015] In combination with the first aspect, in some implementations of the first aspect, the method further includes: a first host node sending first request information to a second host node, where the first request information is used to request the first node to switch to the second host node; the first host node receiving a second identifier sent by the second host node; and the first host node sending the second identifier to the first node, where the second identifier is used to identify the first node in the routing of a wireless backhaul link.

[0016] In an embodiment of the present application, when the topology of the IAB network is updated, or when the CU connected to the IAB node changes, that is, IAB node #1 undergoes a handover, after the handover, IAB node #1 will be connected to the target CU. The target CU receives the handover request information sent by the source CU, allocates a new adaptation layer identifier for 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 IAB node #1, where the source CU is the host node connected to IAB node #1 before the handover.

[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 for the first node.

[0018] In combination with the first aspect, in some implementations of the first aspect, a distributed unit (DU) receives a first data packet sent by a centralized unit (CU), where the first data packet includes an IP layer identifier and data of a first node; the DU sends a second data packet to the first node, where 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 identifier management is provided, including: a first node sending first indication information to a first host node, where the first indication information is used to indicate that the first node can be used to provide wireless backhaul services; the first node receiving a first identifier sent by the host node, where the first identifier is used to uniquely identify the first node in a wireless backhaul link within the 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 identifier 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 the parent node of the first node.

[0022] In combination with the second aspect, in some implementations of the second aspect, when the first node switches from the first host node to the second host node, the method further 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 identifier management is provided, including: a receiving unit, configured to receive first indication information sent by a first node, where the first indication information is used to indicate that the first node can be used to provide wireless backhaul services; a sending unit, configured to send a first identifier to the first node, and 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.

[0024] In combination with the third aspect, in some implementations of the third aspect, the first identifier includes an identifier of the first host node and identifier 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, and the second node is the parent node of the first node.

[0026] In combination with the third aspect, in some 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 configured 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 some implementations of the third aspect, the distributed unit DU is specifically configured to: receive a first data packet sent by the centralized unit CU, where the first data packet contains the IP layer identifier and data of the first node; send a second data packet to the first node, and the second data packet contains the IP layer identifier of the first node, the first identifier, and the data.

[0028] In combination with the third aspect, in some 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 configured 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 some implementations of the third aspect, the sending unit is further configured to send first request information to a second host node, where the first request information is used to request the first node to switch to the second host node; the receiving unit is further configured to receive a second identifier sent by the second host node; the sending unit is further configured to send the second identifier to the first node, where the second identifier is used to uniquely identify the first node in a wireless backhaul link within the service range of the second host node.

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

[0031] In combination with the fourth aspect, in some implementations of the fourth aspect, the first identifier includes an identifier of the first host node and identifier 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 configured 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 some implementations of the fourth aspect, when the first node switches from the first host node to the second host node, the receiving unit is further configured to receive a second identifier sent by the first host node, where the second identifier is used to uniquely identify the first node in a wireless backhaul link within the service range of the second host node.

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

[0035] In a sixth aspect, the present application provides a chip system, including: a processor, configured to execute the method described in the first aspect or the second aspect above.

[0036] In a seventh aspect, the present application provides a communication device, including: a processor, where the processor is coupled to a memory, and the memory is 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 the network device to implement the above functions. Description of the Drawings

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

[0039] Figure 2 It is a schematic diagram of the topological structure of the IAB network provided in the embodiments of the present application.

[0040] Figure 3 It shows the protocol stack architectures of the intermediate IAB node and the access IAB node.

[0041] Figure 4 It shows the protocol stacks of each node in the multi-hop IAB network in the present application.

[0042] Figure 5 It is a schematic interaction diagram of an identifier management method provided in the embodiments of the present application.

[0043] Figure 6 It is a schematic diagram of the identifier information allocated by the host node CU for the IAB node.

[0044] Figure 7 It is a schematic interaction diagram of another identifier management method provided in the embodiments of the present application.

[0045] Figure 8 It is a schematic interaction diagram of yet another identifier management method provided in the embodiments of the present application.

[0046] Figure 9 It is a schematic flowchart of packet routing selection provided in the embodiments of the present application.

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

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

[0049] Figure 12 It is a schematic structural diagram of a communication device provided in the embodiments of the present application.

[0050] Figure 13 It is a schematic structural diagram of another communication device provided in the embodiments of the present application. Detailed Embodiments

[0051] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application.

[0052] In the description of the present application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B. "And / or" in this text is merely an association relationship describing associated objects, indicating that there can be three relationships. For example, A and / or B may mean: A exists alone, A and B exist simultaneously, and B exists alone. Also, in the description of the present application, unless otherwise specified, "a plurality of" means two or more than two. Additionally, for the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and "first", "second", etc. do not necessarily mean 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 interchanged with "network". OFDMA systems 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) uses new versions of E-UTRA in long term evolution (LTE) and various versions evolved from LTE. The 5th-generation (5G) communication system using new radio (NR) is the next-generation communication system under research. In addition, the communication system can also be applicable to future-oriented communication technologies, and all are applicable to the technical solutions provided by the embodiments of the present application.

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

[0055] The terminal in the embodiments of this 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, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device (which may also be referred to as a wearable intelligent 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 a wireless backhaul service for a node (such as a terminal) that wirelessly accesses the wireless backhaul node. Among them, the wireless backhaul service refers to the data and / or signaling backhaul service provided through a wireless backhaul link.

[0057] The system architecture and business scenarios described in the embodiments of this application are used to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art will know that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems. In the embodiments of this application, the method provided is described by taking its application in the NR system or 5G network as an example. However, it should be noted that the method provided by the embodiments of this application can also be applied to other networks. For example, it can be applied in an evolved packet system (EPS) network (that is, the so-called fourth-generation (4G) network). Correspondingly, when the method provided by the embodiments of this application is applied in the EPS network, the network nodes executing the method provided by the embodiments of this application can be replaced with the network nodes in the EPS network. For example, when the method provided by the embodiments of this application is applied in the 5G network or NR system, the wireless backhaul node in the following text can be the wireless backhaul node in the 5G network. Exemplarily, the wireless backhaul node in the 5G network can be called an IAB node. Of course, it can also have other names, and the embodiments of this application do not make specific limitations in this regard. When the method provided by the embodiments of this application is applied in the EPS network, the wireless backhaul node in the following text can be the wireless backhaul node in the EPS network. Exemplarily, the wireless backhaul node in the EPS network can 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 the future network, and the usage of network data will also continue to climb. In order to accommodate more and more terminals and the rapidly growing usage of network data in the market, higher requirements are currently placed on the capacity of the 5G network. In hotspots, to meet the ultra-high capacity requirements of 5G, it has become increasingly popular to use high-frequency small cells for networking. High-frequency carrier waves have poor propagation characteristics, are severely attenuated by obstacles, and have a limited coverage range. Therefore, a large number of small cells need to be densely deployed in hotspots. These small cells can be IAB nodes.

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

[0060] In a network containing IAB nodes (hereinafter referred to as the IAB network), the IAB nodes can provide wireless access services for terminals and connect to a donor node through a wireless backhaul link to transmit user service data. Exemplarily, the donor node can be a donor base station. In a 5G network, the donor node can be abbreviated as an IAB donor or a DgNB (i.e., donor gNodeB). The donor node can be a complete entity or a separated form of a centralized unit (CU) (abbreviated as Donor-CU or simply CU in this article) and a distributed unit (DU) (abbreviated as Donor-DU in this article), that is, the donor node is composed of Donor-CU and Donor-DU. In the embodiments of this application and in the drawings, the method provided by the embodiments of this application is exemplarily described by taking the donor node being composed of Donor-CU and Donor-DU as an example.

[0061] Among them, Donor-CU can also be in a separated form of a User plane (UP) (abbreviated as CU-UP in this article) and a Control plane (CP) (abbreviated as CU-CP in this article), that is, Donor-CU is composed of CU-CP and CU-UP.

[0062] The IAB nodes are connected to the core network through a wired link via the donor node. For example, in a stand-alone 5G architecture, the IAB nodes are connected to the core network (5G core, 5GC) of the 5G network through a wired link via the donor node. In a non-stand-alone 5G architecture, the IAB nodes are connected to the evolved packet core (EPC) via the evolved NodeB (eNB) in the control plane and are connected to the EPC via the donor node and the eNB in the user plane.

[0063] To ensure the reliability of service transmission, the IAB network supports multi-hop IAB nodes and multi-connected IAB nodes to form a network. Therefore, there may be multiple transmission paths between the terminal and the donor node. On one path, there is a definite hierarchical relationship between IAB nodes and between an IAB node and the donor node serving the IAB node. Each IAB node regards the node providing backhaul service for it as its parent node. Correspondingly, each IAB node can be regarded as the child node of its parent node.

[0064] Exemplarily, see Figure 1, the parent node of IAB node 1 is the host node. IAB node 1 is in turn the parent node of IAB node 2 and IAB node 3. Both IAB node 2 and IAB node 3 are the parent nodes of IAB node 4. The parent node of IAB node 5 is IAB node 3. The uplink data packets 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 a 5G network). The downlink data packets 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 data packet transmission between terminal 1 and the host node, namely: terminal 1 → IAB node 4 → IAB node 3 → IAB node 1 → host node, 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, terminal 2 → IAB node 5 → IAB node 2 → IAB node 1 → host node.

[0065] It can be understood that in the IAB network, one transmission path between the terminal and the host node can include one or more IAB nodes. Each IAB node needs to maintain a wireless backhaul link facing the parent node and also needs to maintain a wireless link with the child nodes. If an IAB node is the node accessed by the terminal, the link between this IAB node and the child node (i.e., the terminal) is a wireless access link. If an IAB node is a node providing backhaul services for other IAB nodes, the link between this IAB node and the child node (i.e., other IAB nodes) is a wireless backhaul link. Exemplarily, refer to Figure 1 , in the path "terminal 1 → IAB node 4 → IAB node 3 → IAB node 1 → host node". Terminal 1 accesses IAB node 4 through a wireless access link, IAB node 4 accesses IAB node 3 through a wireless backhaul link, IAB node 3 accesses IAB node 1 through a wireless backhaul link, and IAB node 1 accesses the host node through a wireless backhaul link.

[0066] Exemplarily, the IAB node can be a device such as a customer premises equipment (CPE), a residential gateway (RG), etc. In this case, the method provided in the embodiments of the present application can also be applied to the scenario of home access.

[0067] The above IAB networking scenario is only exemplary. In the IAB scenario combining multi-hop and multi-connection, there are more other possibilities for the IAB networking scenario. For example, a dual connection formed by a host node and an IAB node under another host node serves the terminal, etc., which will not be enumerated one by one here.

[0068] To make the embodiments of this application clearer, the following provides a unified introduction to some content and concepts related to the embodiments of this application here.

[0069] 1. Link, the previous hop node of a node, the next hop node of a node, the ingress link of a node, and the egress link of a node

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

[0071] The previous hop node of a node: It refers to the node that is the last to receive a data packet before this node in the path containing this node.

[0072] The next hop node of a node: It refers to the node that is the first to receive a data packet after this node in the path containing this node.

[0073] The ingress link of a node: It refers to the link between this node and the previous hop node of this node, and can also be called the previous hop link of the node.

[0074] The egress link of a node: It refers to the link between this node and the next hop node of this node, and can also be called the next hop link of the node.

[0075] 2. Access IAB node, intermediate IAB node

[0076] In the embodiments of this application, the access IAB node refers to the IAB node accessed by the terminal, and the intermediate IAB node refers to the IAB node that provides wireless backhaul services for other IAB nodes (for example, access IAB nodes or other intermediate IAB nodes).

[0077] Exemplarily, refer to Figure 1 , in the path "Terminal 1 → IAB Node 4 → IAB Node 3 → IAB Node 1 → Host Node", IAB Node 4 is an 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 for a terminal accessing an IAB node, the IAB node is an access IAB node. For a terminal 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 needs to be determined according to the specific application scenario.

[0079] 3. Composition of IAB Node

[0080] An IAB node can have the role of a mobile terminal (MT) and the role of a DU. When the 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 the IAB node faces its child nodes (the child nodes may be terminals or the terminal parts of other IAB nodes), 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 is composed of an MT part and a DU part. An IAB node can establish a backhaul connection with at least one of its parent nodes through the MT part. The DU part of an IAB node can provide access services for terminals or the MT parts of other IAB nodes.

[0081] Exemplarily, see Figure 2 , the terminal is connected to the host node through IAB node 2 and IAB node 1. Among them, both IAB node 1 and IAB node 2 include a DU part and an MT part. The DU part of IAB node 2 provides access services for the terminal. The DU part of IAB node 1 provides access services for the MT part of IAB node 2. Donor-DU provides access services for the MT part of IAB node 1.

[0082] 4. Protocol Stack Architectures of Intermediate IAB Node, Access IAB Node, Donor-DU, Donor-CU, and Terminal

[0083] The protocol stacks of the intermediate IAB node in the user plane and the control plane are 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 the DU part of the intermediate IAB node may also share the Adapt layer, for example Figure 3 (b).

[0084] The protocol stacks of the access IAB node in the user plane and the control plane are different. Please refer to Figure 3 (c) and Figure 3 (d) respectively.

[0085] Exemplarily, based on Figure 3 the example shown, the user plane protocol stack architectures of each node can be referred to Figure 4(a), the control plane protocol stack architecture of each node can be referred to Figure 4 (b). Among them, Figure 4 In Figure 4 , the MT part and DU part of the intermediate IAB node do not share the Adapt layer as an example for drawing. Among them, Figures 3 to 4 The meanings of each protocol layer in Figures 3 to 4 are as follows: 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, Layer 2 (L2), Layer 1 (L1), 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. 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. Exemplarily, the L1 layer can be the physical layer in the OSI reference model.

[0086] It should be noted that Figure 4 In Figure 4 , the host node is composed of Donor-DU and Donor-CU as an example for drawing. Therefore, Figure 4 The protocol layers of Donor-DU and Donor-CU are shown in Figure 4 . If the host node is a fully functional entity, the host node only needs to retain the protocol stack of the interfaces of Donor-DU and Donor-CU to external nodes, and there is no need for the protocol layer on the internal interface between Donor-DU and Donor-CU.

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

[0088] 5. F1 Interface, Protocol Layers of F1 Interface

[0089] Among them, the F1 interface refers to the logical interface between the DU part of the IAB node and the host node (or Donor-CU or Donor-DU). The F1 interface can also be called the F1* interface, and it supports the user plane and the control plane. The protocol layers of the F1 interface refer to the communication protocol layers on the F1 interface.

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

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

[0092] Embodiment 1

[0093] Figure 5 Shows a schematic interaction diagram of an identity management method according to an embodiment of the present application. Refer to Figure 5 , the IAB Donor can allocate identities to IAB Node #1. The IAB donor base station has a wired connection to the core network, and IAB Node #1 is connected to the IAB donor base station through a wireless backhaul link, so that the UE served by IAB Node #1 can be connected to the core network.

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

[0095] During the startup process, IAB Node #1 accesses the network as an MT through its parent node. After or during the network access process, IAB Node #1 can send Indication Information #1 to the host node, indicating that it is an IAB node and can be used to provide wireless access and wireless backhaul services. For example, IAB Node #1 carries the indication information in the RRC message sent to the IAB Donor, and this indication information is used to indicate that IAB Node #1 is an integrated access and backhaul node and can be used to 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, IAB Node #1 sends Indication Information #1 to the CU through the host DU.

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

[0098] The host node can obtain the identification information #E1 of IAB Node #1 by receiving the identification information #E1 of IAB Node #1 from a core network element; or, the way for the host node to obtain the identification information #E1 of IAB Node #1 can also be: the host node IAB Donor receives the indication information sent by IAB Node #1, determines that IAB Node #1 is an integrated access and backhaul node, and the host node assigns the identification information #E1 to IAB Node #1, and this identification information #E1 is used to uniquely identify IAB Node #1 on the wireless backhaul link within the scope served by the host node.

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

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

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

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

[0103] For example, the host node may send the identification information #E1 to the MT part of IAB node #1 through an RRC message, or the CU may send the identification information #E1 to the DU part of 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 embodiments of the present application may also be understood as being replaced by the CU. Optionally, if the CU includes a CU-CP and a CU-UP, the host node in the embodiments of the present application may also be understood as being replaced by the CU-CP.

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

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

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

[0108] When the CU is in the form of separation between the control plane (CP) and the user plane (UP), the CU in step S504 can also be understood as being replaced by the CU-CP.

[0109] When the host node is in the form of separation between the CU and the DU, data needs to be forwarded by the Donor DU between the CU and the IAB node #1. Therefore, the CU will send the configuration information #S1 to route-configure the Donor DU. Since the routing of data packets between the CU and the Donor DU uses the IP layer, and the Donor DU uses the adaptation layer for routing 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 the IAB node #1 and the IP layer identifier of the IAB node #1. Thus, the Donor DU can maintain the correspondence between the adaptation layer identifier #E1 and the IP layer identifier of the IAB node #1, facilitating the Donor DU to add the adaptation layer identifier #E1 of the IAB node #1 to the downlink data packet #D1 with the IP layer destination address being the IP layer identifier of the IAB node #1 in the IP layer, so as to route the downlink data packet #D1 during wireless backhaul link transmission. The CU configures the identifier of the next-hop node to the IAB node #1 for the Donor DU, enabling the Donor DU to select an appropriate next-hop node for the data packet sent to the IAB node #1.

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

[0111] In an alternative embodiment, as Figure 5 shown, the method provided by the embodiment of the present application further includes:

[0112] In S505, send the identifier information #E1 to the parent node of the IAB node #1.

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

[0114] Situation 1, the host node sends the identifier information #E1 of the IAB node #1 to the parent node of the IAB node #1.

[0115] Situation 2, the IAB node #1 sends the identifier information #E1 of the IAB node #1 to the parent node of the IAB node #1.

[0116] For example Figure 5Among them, IAB node #2 is the parent node of IAB node #1. Therefore, exemplarily, for case 1, the host node can send the identification information #E1 of IAB node #1 to the MT part of IAB node #2 through an RRC message; alternatively, the host node can send the identification information #E1 of IAB node #1 to the DU part of IAB node #2 through an F1AP message. Exemplarily, for case 2, IAB node #1 can send the identification information #E1 to IAB node #2 through a control element of the MAC layer.

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

[0118] Through the method shown in the embodiments of the present application, an IAB node can obtain the identification information in the wireless backhaul link within the service range of the host node, and this identification information can be used as the routing information of the data packet in the wireless backhaul link, so the routing problem of the data packet in the wireless backhaul link can be solved.

[0119] Figure 6 Shows a schematic diagram of the identification information allocated by the host node for the IAB node.

[0120] In the embodiments of the present application, the host node can allocate the identification information #E1 for the IAB node, and this 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. As a possible example, this identification information #E1 includes the identification of the host node (prefix information specific to the host node), and the identification information specific to the IAB node #1.

[0121] Embodiment 2

[0122] Figure 7 Shows a schematic interaction diagram of another identification management method provided by the present application.

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

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

[0125] At 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 an F1AP message.

[0127] At S703, the CU sends the 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 can send the configuration information #S2 through an RRC message to the IAB node #1 (for example, an RRC message sent to the MT part of the IAB node #1); or, the CU sends the configuration information #S2 through an F1AP message to the IAB node #1 (for example, an F1AP message sent to the DU part of the IAB node #1).

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

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

[0131] Embodiment III

[0132] Figure 8 Shows a schematic interaction diagram of another identifier management method provided by the present application. Refer to 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 a management network element in the core network.

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

[0134] The IAB node #1 obtains the identifier information #E1 from a management network element in the core network. The identifier 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 identifications: the IP address obtained by the IAB node from the OAM; or, the cell identification served by the DU part of the IAB node, specifically, it can be the global cell identification in the 4G network (E-UTRAN Cell Global Identifier, E-UTRAN), or the global cell identification in the 5G NR network (NR cell global identifier, NCGI), etc.; or, the identification assigned by the core network element AMF / MME to the MT part of the IAB node, for example, various temporary user identities (Temporary Mobile Subscriber Identity, TMSI), or globally unique temporary identities (Globally Unique Temporary UE Identity, GUTI), such as MME-TMSI, 5G-TMSI, 4G-GUTI, 5G-GUTI, etc.; or, the identification pre-configured in the IAB node #1, for example, the international mobile subscriber identification number (International Mobile Subscriber Identification Number, IMSI), subscription permanent identifier (Subscription Permanent Identifier, SUPI), subscription concealed identifier (Subscription Concealed Identifier, SUCI), international mobile equipment identity (International Mobile Equipment Identity, IMEI), permanent equipment identifier (Permanent Equipment Identifier, PEI), etc. of the MT part.

[0136] At S802, the IAB node #1 sends the 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 contains 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 contains the identification information #E1 of the IAB node #1.

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

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

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

[0141] Step S803 can specifically be understood with reference to step S504 and will not be elaborated here.

[0142] In an alternative embodiment, as Figure 8 shown, the method provided by the embodiments of the present application further includes:

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

[0144] There are two different cases for S804, which are introduced separately below.

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

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

[0147] Step S804 can specifically be understood with reference to step S505 and will not be elaborated here.

[0148] Embodiment 4

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

[0150] At S901, the Donor DU receives a data packet #D1, and the data packet #D1 includes the IP layer identification of a target IAB node (such as IAB node #1).

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

[0152] At S903, the Donor DU determines the next-hop node (such as IAB node #2). Specifically, the donor DU can determine the next-hop node according to the received configuration information #S1.

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

[0154] In S904, send the data packet #D1 added with the identification information #E1 to the next-hop node of Donor Du.

[0155] Embodiment Five

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

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

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

[0159] Among them, the CU-CP can assign an IP layer identification to IAB node #1, or the CU-CP can obtain the IP layer identification of IAB node #1. The way for the CU-CP to obtain the IP layer identification of IAB node #1 can be to receive the IP layer identification of IAB node #1 sent from the core network element, or receive the IP layer identification of IAB node #1 sent by IAB node #1.

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

[0161] Among them, the IP layer identification in the embodiment of the present invention can be, for example, an IPv4 address or an IPv6 address.

[0162] Exemplarily, the way for the CU-CP to obtain the IP layer identification of IAB node #1 can be: the CU-CP assigns an IP layer identification to IAB node #1; or,

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

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

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

[0166] In the embodiment of the present application, after the CU-CP sends the IP layer identifier of IAB node #1 to the CU-UP, the CU-UP can use the IP layer identifier of IAB node #1 and add it to the data packet that needs to be sent to IAB node #1, which is convenient for the CU-UP and the donor DU to perform IP layer routing of the data packet.

[0167] Embodiment Six

[0168] Figure 11 Fig. shows a schematic interaction diagram of an IAB node switching between different host nodes.

[0169] See 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 on the wireless backhaul link needs to be changed.

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

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

[0172] In S1102, host node #2 assigns identification information #E4 to IAB node #1.

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

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

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

[0176] For example, the source host node #1 carries the identification information #E4 of IAB node #1 in the handover command sent to 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 embodiments of the present application can also be understood as being replaced by the CU. Optionally, if the CU includes a CU-CP and a CU-UP, the host node in the embodiments of the present application can also be understood as being replaced by the CU-CP.

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

[0179] See Figure 12 , Figure 12 is a schematic structural diagram of a network device 1000 provided by the present application. The network device 1000 is used to implement the functions of the host node in the method embodiments. As Figure 12 shown, the network device 1000 includes an antenna 1101, a radio frequency device 1102, and a baseband device 1103. The antenna 1101 is connected to the radio frequency device 1102. The baseband device 1103 may include one or more processing units 11031. In addition, the baseband device 1103 may further include a storage unit 11032 and a communication interface 11033. The storage unit 11032 is used to store programs and data. The communication interface 11033 is used to interact with the radio frequency device 1102. The communication interface 11033 may be an input / output interface or an input / output circuit.

[0180] The network device 1000 in the device embodiments of the present application may correspond to the host node in the method embodiments, 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 embodiments.

[0181] For example, the radio frequency device 1102 receives the indication information sent by the IAB node #1 through the antenna 1101, and 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 the identification information through the antenna 1101 to the IAB node #1, and the identification information includes the identification information of the IAB node #1 and the identification information of the host base station, and the identification information is used to identify the IAB node #1 in the wireless backhaul link served by the host base station.

[0182] For another example, the radio frequency device 1102 sends the 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 assigned by the host base station to the parent node.

[0183] For another example, the host base station includes a distributed unit (DU) and a central unit (CU). The DU receives the configuration information sent by the 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. Here, IAB node #3 is a child node of the host base station.

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

[0185] For another example, the CU obtains the adaptation layer identifier #D1 of the donor DU. The CU sends the adaptation layer identifier #D1 to the donor DU and sends configuration information #S2 to IAB node #1. Here, the configuration information #S2 contains the adaptation layer identifier #D1 of the donor DU. Alternatively, the configuration information #S2 may further include the identifier of the next-hop node for the uplink transmission from IAB node #1 to the donor DU. Thus, when IAB node #1 sends uplink data to the host node, it can perform route selection according to the configuration information #S2.

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

[0187] For another example, the host base station includes a distributed unit (DU) and a central 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 IAB node #1 and send the IP layer identifier of IAB node #1 to the CU-UP.

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

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

[0190] In one implementation, the units for implementing the above steps in the host base station can be implemented in the form of a processing unit scheduler. For example, the processing unit 11031 calls the program stored in the storage unit 11032 to execute the method executed by the host base station in the above method embodiments. The storage unit 11032 can be an on-chip storage unit on the same chip as the processing unit 11031, or a storage element on a different chip from the processing unit 11031, that is, an off-chip storage unit.

[0191] See Figure 13 , Figure 13 is a schematic structural diagram of a network device 2000 provided by the present application. The network device 2000 is used to implement the functions of the IAB node #1 in the method embodiments. As Figure 13 shown, the network device 2000 includes an antenna 2101, a radio frequency device 2102, and a baseband device 2103. The antenna 2101 is connected to the radio frequency device 2102. The baseband device 2103 may include one or more processing units 21031. In addition, the baseband device 2103 may further include a storage unit 21032 and a communication interface 21033. The storage unit 21032 is used to store programs and data. The communication interface 21033 is used to interact with the radio frequency device 2102. The communication interface 21033 may be an input / output interface or an input / output circuit.

[0192] The network device 2000 in the device embodiment of the present application can 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] Exemplarily, the IAB node #1 accesses the network as an MT identity during the startup process. After accessing the network, or during the process of accessing the network, the IAB node #1 can send indication information #1 to the host node, indicating 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 host base station through the 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 the identification information sent by the host base station through the antenna 2101. This identification information includes the identification information of the IAB node #1 and the identification information of the host base station, and this identification information is used to identify the IAB node #1 in the wireless backhaul link served by the host base station.

[0195] For another example, the radio frequency device 2102 sends the 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 to the parent node the identification information #E1 assigned by the host base station for the IAB node #1.

[0196] For another example, when the IAB node #1 switches from the host base station #1 to the host base station #2, the IAB node #1 receives the identification information #E4 sent by the host base station #1, and the identification information #E4 is used to identify the IAB node #1 in the radio backhaul link served by the 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 host base station #1 through the antenna 2101.

[0198] In the above device embodiments, the device 2000 described may be a chip on the baseband device 2103, and the chip includes at least one processing unit and an interface circuit. Among them, the processing element is used to execute each step of any method executed by the above IAB node #1, and the interface circuit is used to communicate with other devices.

[0199] In one implementation, the units for implementing each step in the above method by the IAB node #1 may be implemented in the form of a processing unit scheduler. For example, the processing unit 21031 calls the program stored in the storage unit 21032 to execute the method executed by the IAB node #1 in the above method embodiments. The storage unit 21032 may be an on-chip storage unit on the same chip as the processing unit 21031, that is, an on-chip storage unit, or a storage element on a different chip from the processing unit 21031, that is, an off-chip storage unit.

[0200] In addition, the present application provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions run on a computer, the computer is made to execute the corresponding operations and / or processes executed 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 runs on a computer, the computer is made to execute the method for identity management in the embodiments of the present application or the corresponding operations and / or processes executed by the IAB node or the host node in any method embodiment.

[0202] The present application further provides a chip, including a processor. The processor is configured to call and run a computer program stored in a memory to perform the corresponding operations and / or processes of the identity management method in the embodiments of the present application executed by an IAB node or a host node.

[0203] Optionally, the chip further includes a memory, and the memory is connected to the processor. The processor is configured to read and execute the 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 configured 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, which may specifically include an input interface and an output interface. Alternatively, the communication interface may be an input / output circuit, which may specifically include an input circuit and an output circuit.

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

[0207] In 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 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 allocate the control and signal processing functions of the terminal device or the network device among these devices according to their respective functions. In addition, the processor may have the function of operating one or more software programs, and the software programs may be stored in the memory. The functions of the processor may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0208] The memory can 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. It can also be 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.), magnetic disk storage media, or other magnetic storage devices. Or it can also be any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, etc.

[0209] In the embodiments of the present application, "and / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent the situation where A exists alone, A and B exist simultaneously, or B exists alone. Where A and B can be singular or plural.

[0210] Those of ordinary skill in the art can realize that the units of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods for each specific application to implement the described functions.

[0211] In several embodiments provided in the present 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 merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there can be other division methods. 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 displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical, or other form.

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

[0213] In addition, each functional unit in various embodiments of the present application may be integrated into one processing unit, may exist separately as individual physical units, or two or more units may be integrated into one unit.

[0214] If the above-mentioned function is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, may be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0215] As described above, the above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for identifier management, applied to an IAB system including an integrated access and backhaul IAB node and a first host node, characterized in that, the method includes: The central unit CU obtains the adaptation layer identifier assigned to the distributed unit DU, where the CU and the DU are included in the first host node; The CU sends an F1AP message to the DU, where the F1AP message sent by the CU includes the adaptation layer identifier assigned to the DU.

2. The method according to claim 1, characterized in that, the method further includes: The CU receives an RRC message sent by the IAB node, and the RRC message includes the IP address of the IAB node.

3. The method according to claim 1 or 2, characterized in that, the method further includes: The CU receives an F1AP message sent by the IAB node, and the F1AP message sent by the IAB node includes the adaptation layer identifier of the IAB node.

4. The method according to claim 1 or 2, characterized in that, the method further includes: The CU sends first configuration information to the DU, and the first configuration information includes the adaptation layer identifier of the IAB node and the IP address of the IAB node.

5. The method according to claim 1 or 2, characterized in that, the method further includes: The CU sends the adaptation layer identifier assigned to the DU to the IAB node.

6. The method according to claim 1 or 2, characterized in that, the method further includes: The CU sends the identifier of the next-hop node for the uplink transmission from the IAB node to the DU to the IAB node.

7. A method for identifier management, applied to an IAB system including an integrated access and backhaul IAB node and a first host node, characterized in that, the method further includes: The distributed unit DU receives an F1AP message sent by the central unit CU, where the F1AP message sent by the CU includes the adaptation layer identifier assigned by the CU to the DU, and the CU and the DU are included in the first host node; The DU performs data routing according to the adaptation layer identifier assigned by the CU to the DU.

8. The method according to claim 7, characterized in that, the method further includes: The DU receives the first configuration information sent by the CU, and the first configuration information includes the adaptation layer identifier of the IAB node and the IP address of the IAB node; According to the first configuration information, when the DU receives a downlink data packet with the target IP address being the IP address of the IAB node, the DU adds the adaptation layer identifier of the IAB node to the downlink data packet and sends the downlink data packet to the next-hop node.

9. A method for identifier management, applied to an IAB system including an integrated access and backhaul IAB node and a first host node, characterized in that, includes: The IAB node receives the IP address of the IAB node sent by the OAM system; The IAB node sends an RRC message to a Centralized Unit (CU), where the RRC message contains the IP address of the IAB node; The IAB node receives an adaptation layer identifier allocated for a Distributed Unit (DU) sent by the CU.

10. The method according to claim 9, wherein, it further includes: The IAB node sends an F1AP message to the CU, and the F1AP message sent by the IAB node includes the adaptation layer identifier of the IAB node.

11. The method according to claim 9, wherein, it further includes: The IAB node sends first indication information to the CU, and the first indication information indicates that the IAB node can be used to provide a wireless backhaul service; The IAB node receives the adaptation layer identifier of the IAB node sent by the CU.

12. The method according to any one of claims 9 - 11, wherein, the method further includes: The IAB node receives an identifier of a next-hop node for an uplink transmission from the IAB node to the DU from the CU.

13. A communication device, wherein, it includes a processor and a memory storing computer instructions, and the computer instructions are executed by the processor to cause the communication device to execute the method according to any one of claims 1 - 12.

14. A computer-readable storage medium, wherein, the computer-readable storage medium stores computer instructions, and when the computer instructions run on a computer, the computer is caused to execute the method according to any one of claims 1 - 12.

15. A chip, wherein, it includes a processor, and the processor is used to read a computer program to execute the method according to any one of claims 1 - 12.

16. A communication system, wherein, it includes: a CU for executing the method according to any one of claims 1 - 6 and a DU for executing the method according to claim 7 or 8.

17. The communication system according to claim 16, wherein, it further includes an IAB node for executing the method according to any one of claims 9 - 12.

Images