Relay communication method and related equipment

Abstract

The embodiment of the invention provides a communication method and related equipment. The method comprises the following steps: network management equipment sends a pre-configured cell set to an IAB host accessed to a backhaul integrated IAB node, wherein the pre-configured cell set comprises cell information of one or more cells. Receiving first cell information from the IAB node; the first cell information is determined by the IAB host of the IAB node for the IAB node from the pre-configured cell set, so that configuration updating of the corresponding IAB node can be completed.

Description

[0001] This application is a divisional application. The application number of the original application is 202011150220.4, the filing date of the original application is October 23, 2020, and the entire content of the original application is incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technologies, and more particularly, to a relay communication method and related devices. Background Art

[0003] The concepts of a Central Unit (CU) and a Distributed Unit (DU) are introduced in the fifth generation (5G) of communication. A base station, such as a next-generation node B (gNB), can be divided into a gNB-CU and at least one gNB-DU connected to the gNB-CU according to protocol layers. The gNB-DU may include functions of the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and the Physical (PHY) layer. The CU may include functions of the Packet Data Convergence Protocol (PDCP) layer, the Service Data Adaptation Protocol (SDAP) layer, and the Radio Resource Control (RRC) layer. The gNB-CU and the gNB-DU are connected by a wired connection and communicate through the F1 interface.

[0004] The existing network planning and deployment are responsible by the network management equipment in the network. For the base stations with the CU-DU separation architecture, such as gNB, the topological relationship between the gNB-CU and the gNB-DU is determined by the network management equipment, and the network management equipment configures the gNB-CU and the gNB-DU respectively. For example, the network management equipment sends configuration information to the gNB-DU. The configuration information may include: gNB-DU identifier (gNB-DU ID), gNB-DU name (gNB-DU Name), identifier of the base station to which the gNB-DU belongs (gNBID), base station identifier length of the base station to which the gNB-DU belongs (gNB ID length), Internet Protocol (IP) address of the DU side corresponding to the F1 interface (i.e., the local IP address of the gNB-DU on the F1 interface), IP address of the CU side corresponding to the F1 interface (i.e., the peer IP address of the gNB-DU on the F1 interface, which is also the local IP address of the gNB-CU on the F1 interface because the peer of the gNB-DU on the F1 interface is the gNB-CU), cell local identifier (cellLocalId), public land mobile network identifier list (PLMN IdList), single network slice selection assistance information list (sNSSAI List), physical cell identifier (PCI), tracking area code (TAC), uplink and downlink frequency points, frequency of synchronization signal and physical broadcast channel block (SSB), SSB period, SSB carrier spacing, SSB offset, SSB duration.

[0005] In an Integrated Access and Backhaul (IAB) network, the Cell Identity of the cell served by an IAB node includes a first base station identifier, and the cell served by the IAB host to which the IAB node is connected includes a second base station identifier. The normal operation of the IAB network generally requires ensuring that the first base station identifier is equal to the second base station identifier. After the IAB node is connected to the IAB host, for the terminals served by the IAB node, the cell served by the IAB node can be considered as the cell served by the IAB host.

[0006] To ensure the normal routing of data, the IP address of the IAB node and the IP address of the IAB host DU to which the IAB node is connected need to belong to the same network segment or have the same network prefix.

[0007] However, since the connection between the IAB-DU and the Donor-CU is wireless, the IAB node can randomly choose to connect to different IAB hosts or switch between different IAB hosts, which results in the network management device being unable to timely obtain the topology information in the current IAB network (such as the IAB host information to which the IAB node is connected), and thus unable to provide accurate configuration information for the IAB nodes in the IAB network. Summary of the Invention

[0008] In view of this, the present application provides a communication method and related devices, which can enable the network management device to provide accurate configuration information for the IAB nodes in the IAB network.

[0009] In a first aspect, the present application provides a communication method, which may include: the network management device receives first information from an Integrated Access and Backhaul IAB node; the network management device generates first configuration information for the IAB node according to the first information; the network management device sends the first configuration information to the IAB node. Through this method, exemplary beneficial effects include: enabling the IAB nodes in the IAB network to obtain accurate configuration information and ensuring the operation of the IAB network.

[0010] In a feasible design, the first information includes: the cell information of the cell to which the IAB node is connected, and / or the base station identifier of the IAB host of the IAB node. Through this design, exemplary beneficial effects include: enabling the network management device to obtain the IAB host information of the IAB node and generating appropriate configuration information for the IAB according to the IAB host information.

[0011] In a feasible design, the cell information includes at least one of the following: cell identifier, cell global identifier, physical cell identifier.

[0012] In a feasible design, the first information includes the location information or neighbor cell information of the IAB node. Through this design, exemplary beneficial effects include enabling the network management device to obtain the IAB host information around the IAB node and generating a corresponding set of appropriate configuration information for each candidate IAB host, facilitating the IAB node to make a suitable autonomous selection.

[0013] In a feasible design, the first configuration information includes X pieces of configuration information, and the X pieces of configuration information respectively correspond to X candidate IAB hosts, where X is a positive integer; the network management device receives the third configuration information from the IAB node or the index corresponding to the third configuration information, and the third configuration information is determined by the IAB node according to the first configuration information, and the third configuration information has a corresponding relationship with the IAB host selected by the IAB node. Through this design, exemplary beneficial effects include enabling the network management device and the IAB node to align the configuration information autonomously selected by the IAB node. Interacting with the configuration information autonomously selected by the IAB node through the index can save signaling overhead.

[0014] In a feasible design, the first configuration information includes at least one of the following: the local Internet Protocol (IP) address of the IAB node on the F1 interface, the peer IP address of the IAB node on the F1 interface, and the cell information of the cell served by the IAB node; where the local end of the F1 interface is the distributed unit (DU) end of the IAB node, and the peer end of the F1 interface is the centralized unit (CU) end of the IAB host of the IAB node. Through this design, exemplary beneficial effects include ensuring that the IP address of the IAB node and the IP address of the DU of the IAB host belong to the same network segment or have the same network prefix. And ensuring that the cell identifier of the cell served by the IAB node includes the base station identifier of the IAB host.

[0015] In a feasible design, the network management device generates the first configuration information of the IAB node according to the first information, including: the network management device determines the IAB host of the IAB node according to the first information; the network management device generates the first configuration information according to the IAB host.

[0016] In a feasible design, the network management device generates the first configuration information according to the IAB host, including: the network management device determines the local IP address of the IAB node on the F1 interface according to the DU of the IAB host; and / or, the network management device determines the cell information of the cell served by the IAB node according to the CU of the IAB host. Through this design, exemplary beneficial effects include ensuring that the cell identifier of the cell served by the IAB node includes the base station identifier of the IAB host.

[0017] In a feasible design, when the first configuration information does not include the local IP address of the IAB node on the F1 interface, it includes: the network management device also sends first indication information to the IAB node, where the first indication information is used to indicate the type of IP address that the IAB node requests from the IAB host; or, the first indication information is used to indicate the prefix of the IP address that the IAB node requests from the IAB host; or, the first indication information is used to indicate that the IAB node requests X IP addresses from the IAB host; or, the first indication information is used to indicate that the IAB node requests Y IP addresses for the F1-C interface or F1-C service from the IAB host; or, the first indication information is used to indicate that the IAB node requests Z IP addresses for the F1-U interface or F1-U service from the IAB host; or, the first indication information is used to indicate the prefix of the IP address for the F1-C interface or F1-C service that the IAB node requests from the IAB host; or, the first indication information is used to indicate the prefix of the IP address for the F1-U interface or F1-U service that the IAB node requests from the IAB host; X, Y, and Z are positive integers, the F1-C interface is the control plane interface of the F1 interface, and the F1-U interface is the user plane interface of the F1 interface. Through this design, exemplary beneficial effects include: it can enable the IAB node to request appropriate IP address information from the IAB host under the unified control of the network management device.

[0018] In a feasible design, the network management device sends a pre-configured cell set to the target IAB host of the IAB node; the network management device receives cell information from the IAB node; the cell information is determined by the target IAB host of the IAB node from the pre-configured cell set for the IAB node. Through this design, exemplary beneficial effects include: it can enable the IAB node to obtain cell configuration information more quickly in the scenario of switching the IAB host.

[0019] In a feasible design, the network management device receives second indication information from the IAB node; the network management device determines, according to the second indication information, that the physical cell identifier (PCI) of the IAB node remains unchanged. Through this design, exemplary beneficial effects include: avoiding the update of the PCI during the IAB node handover process, reducing the impact on the communication between the IAB node and its child nodes, improving communication efficiency, and enhancing the user experience.

[0020] In a feasible design, the network management device receives third indication information from the IAB node; the network management device determines, according to the third indication information, whether the IAB node is an IAB node. Through this design, exemplary beneficial effects include: it can enable the network management device to timely understand the situation of the IAB node and achieve the control of the IAB node.

[0021] In a feasible design, the network management device receives fourth indication information from the IAB node, and the fourth indication information includes the status of the cell served by the IAB node; wherein, the status of the cell served by the IAB node includes: the cell is closed or the cell is in the discontinuous transmission (DTX) state; the network management device determines the status of the cell served by the IAB node according to the fourth indication information. Through this design, exemplary beneficial effects include: enabling the network management device to timely understand the situation of the IAB node and realizing the control of the IAB node.

[0022] In a feasible design, when the status of the cell served by the IAB node is that the cell is in the DTX state, the fourth indication information further includes: the synchronization signal block (SSB) information of the cell served by the IAB node.

[0023] In a second aspect, the present application provides a communication method, which may include: the integrated access and backhaul (IAB) node sends first information to a network management device; the IAB node receives first configuration information from the network management device.

[0024] In a feasible design, the first information includes: the cell information of the cell accessed by the IAB node, and / or, the base station identifier of the IAB host of the IAB node.

[0025] In a feasible design, the cell information includes at least one of the following: cell identifier, cell global identifier, physical cell identifier.

[0026] In a feasible design, the first information includes: the location information or neighbor cell information of the IAB node.

[0027] In a feasible design, the first configuration information includes X configuration information, and the X configuration information respectively corresponds to X candidate IAB hosts, where X is a positive integer; the method further includes: the IAB node selects an IAB host; the IAB node determines the configuration information corresponding to the IAB host in the first configuration information as the third configuration information; the IAB node sends the third configuration information or the index corresponding to the third configuration information to the network management device.

[0028] In a feasible design, the first configuration information includes at least one of the following: the local Internet protocol (IP) address of the IAB node on the F1 interface, the peer IP address of the IAB node on the F1 interface, the cell information of the cell served by the IAB node; wherein, the local end of the F1 interface is the distributed unit (DU) end of the IAB node, and the peer end of the F1 interface is the centralized unit (CU) end of the IAB host of the IAB node.

[0029] In a feasible design, when the first configuration information does not include the local IP address of the IAB node on the F1 interface, it includes: the IAB node also receives first indication information from the network management device, where the first indication information is used to indicate the type of IP address that the IAB node requests from the IAB host; or, the first indication information is used to indicate the prefix of the IP address that the IAB node requests from the IAB host; or, the first indication information is used to indicate that the IAB node requests X IP addresses from the IAB host; or, the first indication information is used to indicate that the IAB node requests Y IP addresses for the F1-C interface or F1-C service from the IAB host; or, the first indication information is used to indicate that the IAB node requests Z IP addresses for the F1-U interface or F1-U service from the IAB host; or, the first indication information is used to indicate the prefix of the IP address for the F1-C interface or F1-C service that the IAB node requests from the IAB host; or, the first indication information is used to indicate the prefix of the IP address for the F1-U interface or F1-U service that the IAB node requests from the IAB host; X, Y, and Z are positive integers, the F1-C interface is the control plane interface of the F1 interface, and the F1-U interface is the user plane interface of the F1 interface.

[0030] In a feasible design, the IAB node sends second information to the IAB host; the second information is used to request the type of IP address from the IAB host; or, the second information is used to request the prefix of the IP address from the IAB host; or, the second information is used to request X IP addresses from the IAB host; or, the second information is used to request Y IP addresses for the F1-C interface or F1-C service from the IAB host; or, the second information is used to request Z IP addresses for the F1-U interface or F1-U service from the IAB host; or, the second information is used to request the prefix of the IP address for the F1-C interface or F1-C service from the IAB host; or, the second information is used to request the prefix of the IP address for the F1-U interface or F1-U service from the IAB host; X, Y, and Z are positive integers, the F1-C interface is the control plane interface of the F1 interface, and the F1-U interface is the user plane interface of the F1 interface.

[0031] In a feasible design, the IAB node receives second configuration information from the IAB host; wherein, the second configuration information may include at least one of the following information: the IP address prefix assigned by the IAB host to the IAB node, the IP address assigned by the IAB host to the IAB node, the IP address assigned by the IAB host to the IAB node for the F1-C interface or F1-C service, the IP address assigned by the IAB host to the IAB node for the F1-U interface or F1-U service, the IP address prefix assigned by the IAB host to the IAB node for the F1-C interface or F1-C service, the IP address prefix assigned by the IAB host to the IAB node for the F1-U interface or F1-U service.

[0032] In a feasible design, the IAB node sends the second configuration information to the network management device. Through this design, exemplary beneficial effects include: enabling the alignment of the configuration information assigned by the IAB host node to the IAB node between the network management device and the IAB node.

[0033] In a feasible design, the IAB node sends second indication information to the network management device; wherein, the second indication information includes the location information of the IAB node and / or the information of the neighboring cells of the IAB node. Alternatively, the second indication information is used to indicate that the PCI of the cell served by the IAB node remains unchanged.

[0034] In a feasible design, the IAB node sends third indication information to the network management device; wherein, the third indication information is used to indicate whether the node is an IAB node.

[0035] In a feasible design, the IAB node sends fourth indication information to the network management device; wherein, the fourth indication information includes the status of the cell served by the IAB node; wherein, the status of the cell served by the IAB node includes: the cell is closed or the cell is in the discontinuous transmission (DTX) state.

[0036] In a feasible design, when the status of the cell served by the IAB node is in the DTX state, the fourth indication information further includes: the SSB information of the cell served by the IAB node.

[0037] In a third aspect, the present application provides a communication method, which is applied to a network management device. The method may include: sending a preconfigured cell set to the IAB host of the integrated access and backhaul IAB node, where the preconfigured cell set includes cell information of one or more cells. Receiving first cell information from the IAB node; the first cell information is determined by the IAB host of the IAB node from the preconfigured cell set for the IAB node.

[0038] In a feasible design, the cell information includes at least one of the following: cell identifier, cell global identifier, physical cell identifier.

[0039] In a feasible design, receive second indication information from an IAB node; according to the second indication information, determine that the physical cell identifier (PCI) of the IAB node remains unchanged.

[0040] In a feasible design, it includes: receive third indication information from a first node; according to the third indication information, determine that the first node is an IAB node or an IAB host.

[0041] In a feasible design, it includes: receive fourth indication information from an IAB node, where the fourth indication information includes the status of the cell served by the IAB node; wherein, the status of the cell served by the IAB node includes: the cell is closed or the cell is in a discontinuous reception (DTX) state; according to the fourth indication information, determine the status of the cell served by the IAB node.

[0042] In a feasible design, when the status of the cell served by the IAB node is in the DTX state, the fourth indication information further includes: the SSB information of the cell served by the IAB node.

[0043] In a fourth aspect, the present application provides a communication method, which is applied to an IAB node. The method may include: obtain first cell information, where the first cell information is determined by the IAB host of the IAB node from a pre-configured cell set for the IAB node, and the pre-configured cell set includes cell information of one or more cells. Send the first cell information to a network management device.

[0044] In a fifth aspect, the present application provides a device, which may include: at least one processor and an interface circuit. The program instructions involved are executed in the at least one processor so that the communication device implements the method and any of its designs in any one of the first aspect to the fourth aspect. The device may be a terminal device or a network device or a chip in any one of the method and any of its designs in any one of the first aspect to the fourth aspect. Optionally, the communication device may further include at least one memory, and the memory stores the program instructions involved.

[0045] In a sixth aspect, the present application provides a computer-readable storage medium, in which the program instructions involved are stored. When the program instructions involved are run, the communication device is enabled to implement the method and any of its designs in any one of the first aspect to the fourth aspect.

[0046] In a seventh aspect, the present application provides a computer program product, which includes program instructions involved. When the involved program instructions are executed, the method according to the first aspect and any of its designs is implemented.

[0047] In an eighth aspect, the present application provides a communication device, which is used to execute the method according to any one of the first aspect to the fourth aspect and any of its designs. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The drawings that may be included in the specification and form a part of the specification show exemplary embodiments, features, or aspects of the present application together with the specification, and are used to explain the principles of the present application. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0049] Figure 1 is a schematic diagram of a possible communication system of the present application;

[0050] Figure 2 is a schematic diagram of an IAB host provided by an embodiment of the present application;

[0051] Figure 3 is a schematic diagram of a control plane protocol stack in an IAB network provided by an embodiment of the present application;

[0052] Figure 4 is a schematic diagram of a user plane protocol stack in an IAB network provided by an embodiment of the present application;

[0053] Figure 5 is a schematic diagram of an IAB node handover provided by an embodiment of the present application;

[0054] Figure 6 is a schematic diagram of a communication method provided by an embodiment of the present application;

[0055] Figure 7 is a schematic diagram of a communication method provided by an embodiment of the present application;

[0056] Figure 8 is a schematic diagram of a communication method provided by an embodiment of the present application;

[0057] Figure 9 is a schematic diagram of a communication method provided by an embodiment of the present application;

[0058] Figure 10 is a schematic diagram of a communication method provided by an embodiment of the present application;

[0059] Figure 11 is a schematic diagram of a communication method provided by an embodiment of the present application;

[0060] Figure 12 is a schematic diagram of a communication method provided by an embodiment of the present application;

[0061] Figure 13 is a schematic diagram of a communication method provided by an embodiment of the present application;

[0062] Figure 14 is a schematic block diagram of a communication device provided by an embodiment of the present application;

[0063] Figure 15 is a schematic block diagram of a communication device provided by an embodiment of the present application;

[0064] Figure 16 is a schematic block diagram of a device provided by an embodiment of the present application. Detailed implementation manners

[0065] In the description of the present application, terms such as "first", "second", "operation 201", or "operation 202" are only used for the purpose of distinguishing descriptions and facilitating the context. Different sequence numbers do not have specific technical meanings in themselves, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying the execution order of operations.

[0066] The term "and / or" in the present application is merely a description of the association relationship of associated objects, indicating that three relationships can exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B can be singular or plural. In addition, the character " / " in this article indicates that the associated objects before and after are in an "or" relationship.

[0067] In the present application, "transmission" can include the following three situations: sending of data, receiving of data, or sending and receiving of data. In the present application, "data" can include service data and / or signaling data.

[0068] Each threshold, threshold value, offset value, or preset value of the user equipment in the present application can be configured by the network equipment, can also be stored in the user equipment when it leaves the factory, or can be defined or specified by standards. These thresholds, threshold values, offset values, or preset values can take the value of 0.

[0069] The term "comprising" or "having" and any variations thereof in the present application are intended to cover non-exclusive inclusion. For example, a process / method including a series of steps, or a system / product / device including a series of units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes / methods / products / devices.

[0070] The solution provided by the embodiments of the present application can be applicable to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th generation (5G) mobile communication system, or New Radio (NR) system, and other network systems that can be used to provide mobile communication services, etc. The present application does not make any limitations.

[0071] Compared with the fourth-generation mobile communication system, the fifth-generation mobile communication (5G) has put forward more stringent requirements for all network performance indicators. For example, the capacity index has increased by 1000 times, with wider coverage requirements, ultra-high reliability and ultra-low latency, etc. On the one hand, considering the rich high-frequency carrier frequency resources, in hot spots, in order to meet the ultra-high capacity requirements of 5G, it is becoming increasingly popular to use high-frequency small cells for networking. The propagation characteristics of high-frequency carriers are poor, severely attenuated by occlusion, and the coverage range is not wide. Therefore, a large number of small cells need to be densely deployed. Correspondingly, the cost of providing fiber backhaul for these densely deployed small cells is very high and the construction difficulty is great. Therefore, an economical and convenient backhaul solution is required. On the other hand, from the perspective of wide coverage requirements, when providing network coverage in some remote areas, the deployment of optical fibers is difficult and costly, and a flexible and convenient access and backhaul solution also needs to be designed. The integrated access and backhaul (IAB) technology provides an idea for solving the above two problems: both its access link and backhaul link adopt wireless transmission solutions, avoiding fiber deployment. In the IAB network, the relay node RN (RN, Relay Node) or the IAB node (IAB node) can provide wireless access services for the user equipment (UE, User equipment). The service data of the UE is transmitted by the IAB node through the wireless backhaul link to the host node (IAB donor) or the host base station (DgNB, Donor gNodeB). Using IAB nodes can enable the sharing of antennas for access and backhaul, reducing the number of antennas of the base station.

[0072] The embodiments of the present application will be described below in conjunction with the accompanying drawings. Features or contents marked with dashed lines in the drawings can be understood as optional operations or optional structures of the embodiments of the present application.

[0073] Figure 1The user equipment in [the scenario] can be an access terminal device, user unit, user station, mobile station, mobile unit, remote station, remote terminal device, mobile device, user terminal device, wireless terminal device, user agent, or user device, etc. It can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), a handheld device with wireless communication function, a computing device, other processing devices connected to a wireless modem, in-vehicle device, wearable device (such as smart watch, smart bracelet, etc.), and can also be smart furniture or home appliances, a terminal device in a 5G network, a terminal device in a future evolved public land mobile network (PLMN), or a vehicle device in a vehicle to everything (V2X) network, customer premises equipment (CPE), etc. The present application does not limit the specific implementation form of the user equipment.

[0074] Figure 1 The IAB node in [the scenario] can be composed of an MT (mobile termination, abbreviated as IAB-MT in the context of mobile terminal) and a DU (distributed unit, abbreviated as IAB-DU). Among them, when the IAB node faces its parent node, it can be regarded as a terminal device, that is, in the role of the MT; when the IAB node faces its child nodes (the child nodes may be another IAB node or an ordinary UE), it can be regarded as a network device, that is, in the role of the DU.

[0075] Figure 1 The IAB donor in [the scenario] can be a donor base station, and the IAB donor can be abbreviated as DgNB (i.e., donor gNodeB) in a 5G network. The IAB donor can be a complete entity, or can exist in a form separated into a centralized unit (CU) (abbreviated as Donor-CU or gNB-CU in this application) and a distributed unit (DU) (abbreviated as Donor-DU or gNB-DU in this application), such as Figure 2As shown, the IAB host can be a gNB located in a 5G radio access network (5G RAN). The IAB host can be composed of a gNB-CU and a gNB-DU. The gNB-CU and the gNB-DU are connected through an F1 interface, and the F1 interface can further include a control plane interface (F1-C) and a user plane interface (F1-U). The CU is connected to the core network through a next-generation (NG) interface. Among them, the gNB-CU or the Donor-CU can also exist in a form where the user plane (UP) (referred to as CU-UP in this application) and the control plane (CP) (referred to as CU-CP in this application) are separated, that is, the gNB-CU or the Donor-CU is composed of a CU-CP and a CU-UP. A gNB-CU can include a gNB-CU-CP and at least one gNB-CU-UP. Alternatively, a Donor-CU can include a Donor-CU-CP and at least one Donor-CU-UP.

[0076] Figure 1 The network management device in it can be an operation, administration and maintenance network element (OAM). The network management device can include an element management system (EMS) and a network management system (NMS). Figure 2 As shown, the network management device can be a functional network element located in a 5G core network (5G Core, 5GC). Alternatively, the network management device can also be a functional network element deployed in the backbone network behind the 5G core network, or the network management device can also be deployed in other locations. This application does not limit the specific deployment location of the network management device.

[0077] The IAB node is connected to the core network via the IAB host. For example, in a standalone (SA) 5G architecture, the IAB node is connected to the core network (5G core, referred to as 5GC) of the 5G network via the IAB host. In a dual-connectivity (DC) / multi-connectivity 5G architecture (e.g., non-standalone (NSA), or NR-NR DC scenario, etc.), on the main path, the IAB node can be connected to the evolved packet core (EPC) via an evolved NodeB (eNB), or can also be connected to the 5G core network via the IAB host.

[0078] To ensure the reliability of service transmission, the IAB network supports the networking of multi-hop IAB nodes and multi-connected IAB nodes. Therefore, there may be multiple transmission paths between the terminal and the IAB host. On a path, there is a definite hierarchical relationship between IAB nodes and between the IAB nodes and the IAB hosts connected to the IAB nodes. Each IAB node regards the node that provides backhaul services for it as the parent node. Correspondingly, each IAB node can be regarded as the child node of its parent node.

[0079] Exemplarily, see Figure 1 , the parent node of IAB node 1 is the IAB host, 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, and the parent node of IAB node 5 is IAB node 2. The uplink data packet of the terminal can be transmitted to the IAB host through one or more IAB nodes and then sent by the IAB host to the mobile gateway device (such as the user plane function (UPF) network element in the 5G network), and the downlink data packet will be received by the IAB host 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 IAB host, which are: terminal 1 → IAB node 4 → IAB node 3 → IAB node 1 → IAB host, terminal 1 → IAB node 4 → IAB node 2 → IAB node 1 → IAB host. There are three available paths for the transmission of data packets between terminal 2 and the IAB host, which are: terminal 2 → IAB node 4 → IAB node 3 → IAB node 1 → IAB host, terminal 2 → IAB node 4 → IAB node 2 → IAB node 1 → IAB host, terminal 2 → IAB node 5 → IAB node 2 → IAB node 1 → IAB host.

[0080] It can be understood that in the IAB network, a transmission path between the terminal and the IAB host 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 node. 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 the node that provides 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, see Figure 1, in the path "Terminal 1 → IAB Node 4 → IAB Node 3 → IAB Node 1 → IAB Host", 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 IAB Host through a wireless backhaul link.

[0081] Intermediate IAB nodes on the upstream path from an IAB node to the IAB host can all be referred to as the upstream nodes of the IAB node. For example Figure 1 IAB Node 1 and IAB Node 2 in [Example] can both be referred to as the upstream IAB nodes of IAB Node 5. Intermediate IAB nodes or access IAB nodes on the downstream path from an IAB node to a terminal can all be referred to as the downstream nodes of the IAB node. For example Figure 1 IAB Node 2, IAB Node 3, IAB Node 4, and IAB Node 5 in [Example] can all be referred to as the downstream nodes of IAB Node 1. Downstream nodes include child nodes, grandchild nodes (or called great-grandchild nodes) of child nodes, etc. Downstream nodes can be other IAB nodes or terminals. Exemplarily, Figure 1 Terminal 1 in [Example] can be referred to as the downstream node of IAB Node 4, IAB Node 4 and IAB Node 5 can be called the downstream nodes of IAB Node 1, and Terminal 1 and Terminal 2 can be called the downstream nodes of IAB Node 1.

[0082] The above IAB networking scenarios are only exemplary. In IAB scenarios combining multi-hop and multi-connection, there are more other possibilities for IAB networking scenarios. For example, an IAB host and IAB nodes under another IAB host form a dual connection to serve a terminal, etc., which will not be listed one by one here.

[0083] The access IAB node in the embodiments of the present application refers to the IAB node accessed by a terminal, and the intermediate IAB node refers to the IAB node that provides a wireless backhaul service for an IAB node (for example, an access IAB node or other intermediate IAB nodes). Exemplarily, see Figure 1 , in the path "Terminal 1 → IAB Node 4 → IAB Node 3 → IAB Node 1 → IAB Host", IAB Node 4 is the access IAB node, and IAB Node 3 and IAB Node 1 are intermediate IAB nodes. It should be noted that for a terminal accessing an IAB node, an 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 specifically an access IAB node or an intermediate IAB node is not fixed and needs to be determined according to the specific application scenario.

[0084] Figure 3and Figure 4 are respectively the schematic diagram of the control plane protocol stack and the user plane protocol stack in the IAB network provided by the embodiments of the present application. The following will be described in conjunction with Figure 3 and Figure 4 as follows.

[0085] For the control plane, as Figure 3 shown, a Uu interface is established between the terminal 1 and the IAB2-DU, and the peer protocol layers include the RLC layer, the MAC layer, and the PHY layer. An F1-C interface is established between the IAB2-DU and the IAB donor CU 1, and the peer protocol layers include the F1 application protocol (F1AP) layer and the stream control transmission protocol (SCTP) layer. The IAB donor DU 1 and the IAB donor CU 1 are connected by a wired connection, and the peer protocol layers include the internet protocol (IP) layer, L2, and L1. A BL is established between the IAB node 2 and the IAB node 3, between the IAB node 3 and the IAB node 1, and between the IAB node 1 and the IAB donor DU 1, and the peer protocol layers include the Backhaul Adaptation Protocol (BAP) layer, the RLC layer, the MAC layer, and the PHY layer. In addition, a peer RRC layer and PDCP layer are established between the terminal 1 and the IAB donor CU 1, and a peer IP layer is established between the IAB2-DU and the IAB donor DU 1.

[0086] It can be seen that compared with the control plane protocol stack of a single air interface, the DU accessing the IAB node in the IAB network realizes the functions of the gNB-DU of a single air interface (that is, the functions of establishing peer RLC layer, MAC layer, and PHY layer with the terminal, and establishing peer F1AP layer and SCTP layer with the CU). It can be understood that the DU accessing the IAB node in the IAB network realizes the functions of the gNB-DU of a single air interface; the IAB donor CU realizes the functions of the gNB-CU of a single air interface.

[0087] On the control plane, the RRC message is encapsulated and transmitted in the F1AP message between the access IAB node and the IAB donor CU. Specifically, in the uplink direction, the terminal 1 encapsulates the RRC message in a PDCP protocol data unit (PDU), and after being processed by the RLC layer, MAC layer, and PHY layer in sequence, it is sent to the IAB2-DU. After being processed by the PHY layer, MAC layer, and RLC layer in sequence, the IAB2-DU obtains the PDCP PDU, encapsulates the PDCP PDU in the F1AP message, and after being processed by the SCTP layer and IP layer in sequence, it obtains an IP packet. The IAB2-MT sends the IP packet to the IAB3-DU after being processed by the BAP layer, RLC layer, MAC layer, and PHY layer in sequence. After being processed by the PHY layer, MAC layer, RLC layer, and BAP layer in sequence, the IAB3-DU obtains an IP packet, and then the IAB3-MT sends the IP packet to the IAB1-DU using an operation similar to that of the IAB2-MT. Similarly, the IAB1-MT sends the IP packet to the IAB donor DU 1. After parsing the IP packet, the IAB donor DU 1 sends the IP packet to the IAB donor CU 1, and the IAB donor CU 1 obtains the RRC message after being processed by the SCTP layer, F1AP layer, and PDCP layer in sequence. The downlink direction is similar and will not be described here.

[0088] For the user plane, as Figure 4 shown, a Uu interface is established between the terminal 1 and the IAB2-DU, and the peer protocol layers include the RLC layer, MAC layer, and PHY layer. An F1-U interface is established between the IAB2-DU and the IAB donor CU 1, and the peer protocol layers include the GPRS tunnelling protocol for the user plane (GTP-U) layer and the user datagram protocol (UDP) layer. There is a wired connection between the IAB donor DU 1 and the IAB donor CU 1, and the peer protocol layers include the IP layer, L2, and L1. A BL is established between the IAB node 2 and the IAB node 3, between the IAB node 3 and the IAB node 1, and between the IAB node 1 and the IAB donor DU 1, and the peer protocol layers include the BAP layer, RLC layer, MAC layer, and PHY layer. In addition, a peer SDAP layer and PDCP layer are established between the terminal 1 and the IAB donor CU 1, and a peer IP layer is established between the IAB2-DU and the IAB donor DU 1.

[0089] It can be seen that compared with the user plane protocol stack of a single air interface, the DU of the IAB network's user plane protocol stack realizes some functions of the gNB-DU of the single air interface (i.e., the functions of establishing peer RLC layer, MAC layer, and PHY layer with the terminal, as well as the functions of establishing peer GTP-U layer and UDP layer with the IAB donor CU 1). It can be understood that the DU of the IAB access node realizes the functions of the gNB-DU of the single air interface; the IAB donor CU realizes the functions of the gNB-CU of the single air interface.

[0090] On the user plane, the PDCP data packet is transmitted encapsulated in the GTP-U tunnel between the access IAB node and the IAB donor CU. The GTP-U tunnel is established on the F1-U interface.

[0091] It should be noted that an IAB node may have one or more roles, and this IAB node can have the protocol stacks of these one or more roles; or, the IAB node can have a set of protocol stacks, and this protocol stack can use the protocol layers corresponding to different roles to process according to the different roles of the IAB node. The following takes the example that this IAB node has the protocol stacks of these one or more roles for explanation:

[0092] (1) Protocol stack of a general terminal

[0093] When an IAB node accesses the IAB network, it can act as the role of a general terminal. At this time, the MT of this IAB node has the protocol stack of a general terminal, such as Figure 3 and Figure 4 the protocol stack of terminal 1 in, that is, the RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer. Among them, on the control plane, the RRC message of the IAB node is transmitted encapsulated in the F1AP message between the parent node of the IAB node and the IAB donor CU; on the user plane, the PDCP data packet of the IAB node is transmitted encapsulated in the GTP-U tunnel between the parent node of the IAB node and the IAB donor CU.

[0094] In addition, after this IAB node accesses the IAB network, this IAB node can still act as the role of a general terminal. For example, it transmits its own uplink and / or downlink data packets (such as OAM data packets) to the IAB donor, and performs measurements through the RRC layer, etc.

[0095] (2) Protocol stack of an access IAB node

[0096] After an IAB node accesses the IAB network, this IAB node can provide access services for the terminal, thus acting as the role of an access IAB node. At this time, this IAB node has the protocol stack of an access IAB node, such asFigure 3 and Figure 4 the protocol stack of IAB node 2 in

[0097] In this case, there can be two sets of protocol stacks on the interface of this IAB node facing its parent node. One is the protocol stack of a common terminal, and the other is the protocol stack for providing backhaul services to the terminal (i.e., the protocol stack for accessing the IAB node). Optionally, the same protocol layers of the two sets of protocol stacks can be shared. For example, both sets of protocol stacks correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.

[0098] (3) Protocol stack of the intermediate IAB node

[0099] After the IAB node accesses the IAB network, this IAB node can act as the role of an intermediate IAB node. At this time, this IAB node has the protocol stack of the intermediate IAB node, such as Figure 3 and Figure 4 the protocol stack of IAB node 3 or IAB node 1 in

[0100] In this case, there can be two sets of protocol stacks on the interface of this IAB node facing its parent node. One is the protocol stack of a common terminal, and the other is the protocol stack for providing backhaul services to the sub-IAB node (i.e., the protocol stack of the intermediate IAB node). Optionally, the same protocol layers of the two sets of protocol stacks can be shared. For example, both sets of protocol stacks correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.

[0101] In addition, the IAB node can simultaneously assume the roles of an access IAB node and an intermediate IAB node. For example, the IAB node can be an access IAB node for some terminals and an intermediate IAB node for other terminals. At this time, this IAB node can have three sets of protocol stacks. One is the protocol stack for the above-mentioned common terminal, one is the protocol stack for the access IAB node, and one is the protocol stack for the intermediate IAB node. Optionally, the same protocol layers of the three sets of protocol stacks can be shared. For example, all three sets of protocol stacks correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.

[0102] It should be noted that Figure 3 and Figure 4 have been introduced by taking the IAB network as an example. Figure 3 and Figure 4 The content of Figure 3 also applies to relay networks other than the IAB network. The control plane protocol stack architecture of this relay network can refer to Figure 4 . Figure 3 and Figure 4The IAB nodes in it can be replaced by relays. For example, IAB node 2 can be replaced by relay node 2, IAB node 3 can be replaced by relay node 3, IAB node 1 can be replaced by relay node 1, and IAB donor 1 can be replaced by host node 1. The host node has a CU and a DU protocol stack, and the rest of the content is the same as that in Figure 3 and Figure 4 described in, and specifically, reference can be made to Figure 3 and Figure 4 for the description, which will not be elaborated here.

[0103] As Figure 5 shown, the IAB nodes in the IAB network can be switched. The switch of an IAB node from a source IAB host to a target IAB host can be called an inter-IAB host switch, or an inter-donor CU migration. The switch of an IAB node from a source IAB parent node to a target IAB parent node without changing the IAB host can be called a switch within the IAB host, or an intra-donor CU migration. The IAB switch scenarios described in this application can include inter-donor CU migrating and / or intra-donor CU migrating.

[0104] In this application, the MT of an IAB node can be abbreviated as IAB-MT, the DU of an IAB node can be abbreviated as IAB-DU, the CU of an IAB host can be abbreviated as Donor-CU, and the DU of an IAB host can be abbreviated as Donor-DU.

[0105] In this application, the cells served by an IAB node can include the cells served by the DU of the IAB node or the cells deployed by the DU of the IAB node. The cells accessed by an IAB node can include the cells accessed by the MT of the IAB node or the serving cell where the MT of the IAB node is located.

[0106] In this application, the IAB host connected to an IAB node can be abbreviated as the IAB host of the IAB node. The cells served by the IAB host of the IAB node can include the cells served by the DU of the IAB host or the cells deployed by the DU of the IAB host. Among them, the IAB node can directly access the IAB host, or the IAB node can be connected to the IAB host through other IAB nodes. In this application, the local end of the IAB node at the F1 interface can refer to the DU end of the IAB node, and the peer end of the IAB node at the F1 interface can refer to the CU end of the IAB host of the IAB node.

[0107] Figure 6 The following shows a communication method according to an embodiment of the present application. The communication method 200 includes:

[0108] Operation 201: The IAB node sends a first piece of information to the network management device.

[0109] Exemplarily, before the IAB node sends the first piece of information to the network management device, the IAB-MT may first initiate an attach process to establish a protocol data unit session (PDU session) with a core network device (such as a user plane function (UPF)) through the IAB host. Among them, the established PDU session can be regarded as a data transmission channel, and the IAB node sends the first piece of information to the network management device through this channel. Specifically, it can be that the IAB-DU sends the first piece of information to the network management device through the data transmission channel established by the IAB-MT. The first piece of information can be carried in a configuration request message and is used to request the network management device to generate corresponding configurations for the IAB node (or the IAB-DU).

[0110] Optionally, before the IAB node sends the first piece of information to the network management device, the IAB node may have just switched from the source IAB host to the target IAB host and established a data transmission channel with the core network device through the target IAB host. The IAB node sends the first piece of information to the network management device through this data transmission channel. The first piece of information can be carried in a configuration update request message and is used to request the network management device to update corresponding configurations for the IAB node (or the IAB-DU).

[0111] The first piece of information may include at least one of the following: cell information of the cell accessed by the IAB node, and the base station identifier (gNB ID) of the IAB host of the IAB node. Among them, the cell information may include at least one of the following: physical cell identifier, cell identifier, and cell global identification (CGI). The cell identifier is composed of a base station identifier and a cell local identifier. The cell global identification is composed of a public land mobile network identifier (PLMNId), a base station identifier, and a cell local identifier (cellLocalId).

[0112] Optionally, in the scenario of handover, i.e., when the IAB node hands over from the source IAB host to the target IAB host, the IAB node sends the first information to the network management device through the target IAB host to request configuration update. Among them, the first information may further include the identification information of the IAB node. Specifically, it may be the identification of the IAB-DU (IAB-DU ID), and / or the name of the IAB-DU (IAB-DU Name). Exemplarily, the network management device may find the original configuration of the cell served by the IAB-DU according to the identification information of the IAB node and perform an update on the original configuration.

[0113] Operation 202: The network management device generates the first configuration information of the IAB node according to the first information.

[0114] After receiving the first information, the network management device learns the IAB host of the IAB node and generates the first configuration information for the IAB node. Specifically, the first configuration information may be generated for the IAB-DU.

[0115] The first configuration information includes at least one of the following parameters: the local IP address of the IAB node on the F1 interface, the peer IP address of the IAB node on the F1 interface, the identification of the base station to which the IAB node belongs, gNB ID, the identification information of the IAB-DU (such as DU ID or DU Name), gNB ID length, cellLocalId, PLMNIdList, sNSSAIList, PCI, serving cell bandwidth, TAC, uplink and downlink frequency points, SSB frequency, SSB period, SSB carrier spacing, SSB Offset, SSB Duration, and the cell information of the cell served by the IAB node.

[0116] In this application, the cell information of the cell served by the IAB node may include at least one of the following: PCI, cell identity (CellIdentity), CGI. Among them, the cell identity is composed of gNB Id + cellLocalId. The cell global identity CGI is composed of PLMNId + gNB Id + cellLocalId.

[0117] In this application, the IP address type may include IPv4 and / or IPv6 types. The peer IP address of the IAB node on the F1 interface includes at least one of the following: the CU-side address corresponding to the F1 interface (for example, the IP address of the Donor-CU, or the IP address of the Donor-CU-CP, or the IP address of the Donor-CU-UP). For example, considering the CP-UP separation architecture, the CU-side address corresponding to the F1-C interface is the IP address of the Donor-CU-CP, and the CU-side address corresponding to the F1-U interface is the IP address of the Donor-CU-UP.

[0118] In the IAB network, it is generally required that the IP address of the IAB node and the IP address of the IAB host of the IAB node belong to the same network segment or have the same network prefix to ensure the normal progress of data routing. In addition, it is generally also required that the base station identifier included in the cell identifier of the cell served by the IAB node be the same as the base station identifier of the IAB host of the IAB node.

[0119] In the embodiments of this application, in order to save signaling overhead, various configuration information can be indicated by defining an index value. For example, if the different configuration information sent by the network management device to the IAB node corresponds one-to-one with a configuration index, then through the interaction of the index value, the other party can know which configuration information is being sent down or reported. The corresponding relationship can be shown in Table 1 below:

[0120] Table 1:

[0121] Configuration Index Configuration Information 0 Parameters 1, 2, … 1 Parameters 1’, 2’, … …… ……

[0122] Exemplarily, the network management device can determine the IAB host of the IAB node according to the first information. For example, the network management device can determine the Donor-CU of the IAB node, and / or the Donor-DU, according to the first information.

[0123] Exemplarily, the network management device determines the Donor-CU of the IAB node according to the first information. Specifically, considering that the Donor-CU corresponds to a unique base station identifier, and a base station identifier also uniquely identifies a Donor-CU. The network management device can determine the Donor-CU of the IAB node according to the cell information of the cell accessed by the IAB node included in the first information. For example: when the cell information is CellIdentity or CGI, the network management device can determine the IAB host (or Donor-CU) of the IAB node according to the base station identifier included in the cell identifier.

[0124] Exemplarily, the network management device determines the Donor-DU of the IAB node according to the first information. Specifically, it can be: Considering that after each IAB node accesses the network, the network management device will configure the cell information of the cell served by the IAB node for the IAB node. That is to say, since the cell information of the cell served by each IAB node in the IAB network is configured by the network management device, the network management device can internally store the topological relationship of the IAB network. For example, the topological relationship can be the corresponding relationship between the cell information of the cell served by each IAB node in the IAB network and the cell information of the cell served by the Donor-DU. Or, the topological relationship can be the corresponding relationship between the cell information of the cell served by the IAB node and the Donor-DU. The network management device can determine the Donor-DU of the IAB node according to the topological relationship and the first information.

[0125] Exemplarily, when the parent node of the IAB node is the IAB host, since the cell information of the cell served by the Donor-DU is configured by the network management device, the network management device stores the corresponding relationship between the cell information of the cell served by the Donor-DU and the Donor-DU. Correspondingly, the network management device can determine the Donor-DU of the IAB node according to the cell information of the cell accessed by the IAB node included in the first information (that is, including the cell information of the cell served by the Donor-DU) and the stored corresponding relationship.

[0126] After the network management device determines the Donor-CU, and / or, Donor-DU of the IAB node, the network management device can further generate first configuration information for the IAB node according to the Donor-CU, and / or, Donor-DU.

[0127] For example, after the network management device determines the Donor-CU of the IAB node, it can configure the cell identifier of the cell served by the IAB node for the IAB node, so as to ensure that the base station identifier included in the cell identifier of the cell served by the IAB node is the same as the base station identifier of the IAB host of the IAB node. Another example, after the network management device determines the Donor-DU of the IAB node, the network management device can allocate the local IP address of the F1 interface for the IAB node, so that the IP address of the IAB node and the IP address of the Donor-DU belong to the same network segment or have the same network prefix.

[0128] Operation 203: The network management device sends the first configuration information to the IAB node.

[0129] The first configuration information can be carried in a configuration response message for responding to the configuration request message sent by the IAB node.

[0130] Exemplarily, after receiving the first configuration information, the IAB node triggers a process of establishing an F1 interface (F1-Setup) with the corresponding IAB host, for establishing the F1 interface between the IAB node and the corresponding IAB host. Specifically, after receiving the first configuration information sent by the network management device, the IAB-DU triggers a process of establishing an F1 interface with the Donor-CU, for establishing the F1 interface between the IAB-DU and the Donor-CU.

[0131] Optionally, if the first configuration information does not include the IP address information of the IAB node (for example, does not include the local IP address of the IAB node on the F1 interface, or the peer IP address of the IAB node on the F1 interface), this embodiment may further include the following further operations 204-206;

[0132] Optionally, the network management device may instruct the IAB node to request the corresponding IP address information from the IAB host. Exemplarily, the network management device may send a first indication message to the IAB node. The first indication message may be sent as a separate message, or may be carried in the above first configuration information and sent.

[0133] The first indication message may include at least one of the following information: indicating the type of IP address for the IAB node to request from the IAB host (for example, requesting an IPv4 type IP address from the IAB host, and / or, requesting an IPv6 type IP address from the IAB host), indicating the IAB node to request an IP address or a prefix of an IP address from the IAB host, indicating the number of IP addresses for the IAB node to request from the IAB host, indicating the number of IP addresses for the IAB node to request for the F1-C interface or F1-C service from the IAB host, indicating the number of IP addresses for the IAB node to request for the F1-U interface or F1-U service from the IAB host, indicating the IP address prefix for the IAB node to request for the F1-C interface or F1-C service from the IAB host, indicating the IP address prefix for the IAB node to request for the F1-U interface or F1-U service from the IAB host.

[0134] When the IAB node receives the first indication message, this embodiment may further include the following further operations 204-206.

[0135] Operation 204: The IAB node sends a second message to the IAB host.

[0136] The second piece of information is used to request the IAB host of the IAB node to allocate corresponding IP address information for the IAB node. Specifically, the IAB-MT sends an RRC message to the Donor-CU, and the second piece of information is carried in the RRC message, so that the Donor-CU can allocate corresponding IP address information for the IAB node according to the second piece of information. Alternatively, the Donor-CU sends an F1AP message to the Donor-DU, and the second piece of information is carried in the F1AP message, so that the Donor-DU can allocate corresponding IP address information for the IAB node according to the second piece of information.

[0137] Exemplarily, the information included in the second piece of information may refer to the content of the above-mentioned first indication information. For example, the second piece of information includes at least one of the following pieces of information: the type indicating that the IAB node requests an IP address from the IAB host, the IP address or IP address prefix indicating that the IAB node requests from the IAB host, the number of IP addresses indicating that the IAB node requests from the IAB host, the number of IP addresses indicating that the IAB node requests for the F1-C interface or F1-C service from the IAB host, the number of IP addresses indicating that the IAB node requests for the F1-U interface or F1-U service from the IAB host, the IP address prefix indicating that the IAB node requests for the F1-C interface or F1-C service from the IAB host, the IP address prefix indicating that the IAB node requests for the F1-U interface or F1-U service from the IAB host.

[0138] Operation 205: The IAB host sends second configuration information to the IAB node.

[0139] After receiving the second piece of information from the IAB node, the IAB host can allocate corresponding IP address information for the IAB node according to the second piece of information, and send the allocated IP address information to the IAB node carried in the second configuration information.

[0140] Optionally, during the handover process, when the IAB node switches from the source IAB host to the target IAB host, the target IAB host allocates a corresponding IP address or IP prefix for the IAB node, and carries the allocated IP address or IP prefix in the second configuration information and sends it to the IAB node through the handover command message generated by the target IAB node. Specifically, the target Donor-CU generates a handover command message, and the second configuration information is carried in the message. The target Donor-CU sends the generated handover command message to the IAB-MT through the source Donor-CU, so that the IAB-MT can send it to the IAB-DU through the internal interface.

[0141] Among them, the second configuration information may include at least one of the following information: the IP address prefix allocated by the IAB host for the IAB node, the IP address allocated by the IAB host for the IAB node, the IP address allocated by the IAB host for the IAB node for the F1-C interface / F1-C service, the IP address allocated by the IAB host for the IAB node for the F1-U interface / F1-U service, the IP address prefix allocated by the IAB host for the IAB node for the F1-C interface / F1-C service, the IP address prefix allocated by the IAB host for the IAB node for the F1-U interface / F1-U service.

[0142] Operation 206: The IAB node sends the second configuration information to the network management device.

[0143] After the IAB node receives the IP address information allocated by the IAB host, it carries the IP address information allocated by the IAB host in the second configuration information and sends it to the network management device. Specifically, the second configuration information may include at least one of the following information: the IP address prefix allocated by the IAB host for the IAB node, the IP address allocated by the IAB host for the IAB node, the IP address allocated by the IAB host for the IAB node for the F1-C interface / F1-C service, the IP address allocated by the IAB host for the IAB node for the F1-U interface / F1-U service, the IP address prefix allocated by the IAB host for the IAB node for the F1-C interface / F1-C service, the IP address prefix allocated by the IAB host for the IAB node for the F1-U interface / F1-U service.

[0144] Optionally, in addition to the IP address or IP prefix allocated by the IAB host for the IAB node, the second configuration information may further include at least one of the following other information: the identification information of the IAB-DU (for example: the ID of the IAB-DU, or the name of the IAB-DU), the peer IP address of the IAB node on the F1 interface (i.e., the IP address of the Donor-CU). Exemplarily, the network management device may find the original configuration of the cell served by the IAB-DU according to the identification information of the IAB node and update it on the original configuration.

[0145] Operation 206 is an optional operation, that is, when the IAB node obtains the IP address information, it may also choose not to send it to the network management device.

[0146] Operation 206 may also be replaced by: the IAB host sends the second configuration information to the network management device. That is to say, when the IAB host allocates the corresponding IP address information for the IAB node, it may also send the second configuration information to the network management device. In this way, the IAB node does not need to send the second configuration information to the network management device.

[0147] Operation 204-205 in the embodiments of the present application can form an embodiment alone. That is, once the IAB node determines that the received first configuration information does not include the IP address information of the IAB node, or after the IAB node receives the above first indication information, the IAB node can execute steps 204-205 to obtain the IP address information of the IAB node. Operation 206 is an optional operation, that is, when the IAB node obtains the IP address information, it can also choose not to send it to the network management device.

[0148] This embodiment mainly solves the problem of how the network management device learns the IAB host information (including: Donor-DU and / or Donor-CU) of the IAB node during the initial network access process or the handover process of the IAB node, so that the network management device can configure the IAB node in a timely and accurate manner. In this embodiment, the IAB node sends the cell information of the cell to which the IAB node is connected to the network management device, so that the network management device learns the IAB host of the IAB node, and thus allocates the corresponding cell identifier and / or IP address information to the IAB node; alternatively, the network management device can use an implicit method (the first configuration information does not include the IP address information of the IAB node) or an explicit method (the first configuration information includes the first indication information) to instruct the IAB node to request the corresponding IP address information from the IAB host. Through this embodiment, the IAB node can obtain the corresponding configuration information, ensuring the normal operation of the IAB node.

[0149] Figure 7 The following shows a communication method according to an embodiment of the present application. The communication method 200B includes:

[0150] Operation 201B: The network management device sends the first indication information to the IAB node.

[0151] Optionally, the network management device can instruct the IAB node to request the corresponding IP address information from the IAB host. Exemplarily, the network management device can send the first indication information to the IAB node.

[0152] The first indication information may include at least one of the following types of information: indicating the type of IP address requested by the IAB node from the IAB host (e.g., requesting an IPv4 type IP address from the IAB host, and / or requesting an IPv6 type IP address from the IAB host), indicating that the IAB node requests an IP address or a prefix of an IP address from the IAB host, indicating the number of IP addresses requested by the IAB node from the IAB host, indicating the number of IP addresses requested by the IAB node from the IAB host for the F1-C interface or F1-C service, indicating the number of IP addresses requested by the IAB node from the IAB host for the F1-U interface or F1-U service, indicating the IP address prefix requested by the IAB node from the IAB host for the F1-C interface or F1-C service, and indicating the IP address prefix requested by the IAB node from the IAB host for the F1-U interface or F1-U service.

[0153] Operation 202B: The IAB node sends second information to the IAB host.

[0154] The second information is used to request the IAB host of the IAB node to allocate corresponding IP address information for the IAB node. Specifically, the IAB-MT sends an RRC message to the Donor-CU, and the second information is carried in the RRC message, so that the Donor-CU allocates corresponding IP address information for the IAB node according to the second information. Alternatively, the Donor-CU sends an F1AP message to the Donor-DU, and the second information is carried in the F1AP message, so that the Donor-DU allocates corresponding IP address information for the IAB node according to the second information.

[0155] Exemplarily, the information included in the second information may refer to the content of the above first indication information. For example, the second information includes at least one of the following types of information: indicating the type of IP address requested by the IAB node from the IAB host, indicating that the IAB node requests an IP address or a prefix of an IP address from the IAB host, indicating the number of IP addresses requested by the IAB node from the IAB host, indicating the number of IP addresses requested by the IAB node from the IAB host for the F1-C interface or F1-C service, indicating the number of IP addresses requested by the IAB node from the IAB host for the F1-U interface or F1-U service, indicating the IP address prefix requested by the IAB node from the IAB host for the F1-C interface or F1-C service, and indicating the IP address prefix requested by the IAB node from the IAB host for the F1-U interface or F1-U service.

[0156] Operation 203B: The IAB host sends second configuration information to the IAB node.

[0157] After receiving the second information from the IAB node, the IAB host can, according to the second information, allocate corresponding IP address information for the IAB node, and carry the allocated IP address information in the second configuration information and send it to the IAB node.

[0158] Optionally, during the handover process, when the IAB node is handed over from the source IAB host to the target IAB host, the target IAB host allocates a corresponding IP address or IP prefix for the IAB node, and carries the allocated IP address or IP prefix in the second configuration information, and sends it to the IAB node through the handover command message generated by the target IAB node. Specifically, the target Donor-CU generates a handover command message, which carries the second configuration information, and the target Donor-CU sends the generated handover command message to the IAB-MT through the source Donor-CU, so that the IAB-MT sends it to the IAB-DU through the internal interface.

[0159] The second configuration information may include at least one of the following information: the IP address prefix allocated by the IAB host for the IAB node, the IP address allocated by the IAB host for the IAB node, the IP address allocated by the IAB host for the IAB node for the F1-C interface / F1-C service, the IP address allocated by the IAB host for the IAB node for the F1-U interface / F1-U service, the IP address prefix allocated by the IAB host for the IAB node for the F1-C interface / F1-C service, the IP address prefix allocated by the IAB host for the IAB node for the F1-U interface / F1-U service.

[0160] Operation 204B: The IAB node sends the second configuration information to the network management device.

[0161] After receiving the IP address information allocated by the IAB host, the IAB node carries the IP address information allocated by the IAB host in the second configuration information and sends it to the network management device. Specifically, the second configuration information may include at least one of the following information: the IP address prefix allocated by the IAB host for the IAB node, the IP address allocated by the IAB host for the IAB node, the IP address allocated by the IAB host for the IAB node for the F1-C interface / F1-C service, the IP address allocated by the IAB host for the IAB node for the F1-U interface / F1-U service, the IP address prefix allocated by the IAB host for the IAB node for the F1-C interface / F1-C service, the IP address prefix allocated by the IAB host for the IAB node for the F1-U interface / F1-U service.

[0162] Optionally, in addition to the IP address or IP prefix allocated by the IAB host for the IAB node, the second configuration information may further include at least one of the following other information: the identification information of the IAB-DU (for example, the ID of the IAB-DU, or the name of the IAB-DU), and the peer IP address of the IAB node on the F1 interface (i.e., the IP address of the Donor-CU). Exemplarily, the network management device may find the original configuration of the cell served by the IAB-DU based on the identification information of the IAB node and update it on the original configuration.

[0163] Operation 204B is an optional operation, that is, when the IAB node obtains the IP address information, it may also choose not to send it to the network management device.

[0164] Operation 204B may also be replaced with: the IAB host sends the second configuration information to the network management device. That is, when the IAB host allocates the corresponding IP address information for the IAB node, it may also send the second configuration information to the network management device. In this way, the IAB node does not need to send the second configuration information to the network management device.

[0165] Figure 8 The following shows a communication method according to an embodiment of the present application. The communication method 300 includes:

[0166] Operation 301: The IAB node sends the first information to the network management device.

[0167] The first information includes the location information of the IAB node and / or the information of the neighboring cells of the IAB node. Among them, the location information of the IAB node refers to the geographical location information of the IAB node, such as the longitude and latitude information where the IAB node is located. The information of the neighboring cells of the IAB node refers to the cell identifiers of the neighboring cells measured by the IAB node and / or the geographical location information of the neighboring cells, etc.

[0168] Operation 302: The network management device generates the first configuration information of the IAB node according to the first information.

[0169] The network management device may first determine the candidate IAB hosts of the IAB node according to the first information. The candidate IAB hosts may be at least one IAB host around the IAB node.

[0170] Exemplarily, for each candidate IAB host, the network management device generates a corresponding set of configuration information. As shown in Table 2:

[0171] Table 2:

[0172] Candidate IAB Host 1 Configuration Information 1 Candidate IAB Host 2 Configuration Information 2 …… …… Candidate IAB Host X Configuration Information X

[0173] The network management device can include the configuration information corresponding to X (X is a positive integer) candidate IAB hosts in the first configuration information to generate the first configuration information of the IAB node. The configuration information corresponding to each candidate IAB host for the IAB node may include at least one of the following parameters: the local IP address of the IAB node on the F1 interface, the peer IP address of the IAB node on the F1 interface (i.e., the IP address of the Donor-CU), the base station identifier of the candidate IAB host, the DU identifier information of the IAB node (such as DU ID or DU Name), gNB ID length, cellLocalId, PLMNIdList, sNSSAIList, PCI, CGI, serving cell bandwidth, TAC, uplink and downlink frequency points, SSB frequency, SSB period, SSB carrier interval, SSB Offset, SSBDuration, the IP address of the security gateway, and the cell information of the cell served by the IAB node.

[0174] Operation 303: The network management device sends the first configuration information to the IAB node.

[0175] Operation 304: The IAB node determines the third configuration information according to the first configuration information.

[0176] The IAB node can select one from the candidate IAB hosts for access according to factors such as the access link quality. The IAB host selected by the IAB node can be called the target IAB host. For example, in the scenario where the IAB node initially accesses the network, the IAB node can use the IAB host it is about to access or has selected as the target IAB host. Or, in the scenario where the IAB node performs a handover, the IAB node can use the target IAB host for the handover as the target IAB host.

[0177] The IAB node determines the configuration information corresponding to the target IAB host from the first configuration information according to the selected target IAB host, and uses it as the third configuration information.

[0178] Exemplarily, the IAB node (or the IAB-MT of the IAB node) determines the configuration information corresponding to the target IAB host from the first configuration information according to the system information or broadcast information received from the parent node (such as the target IAB host or the IAB node connected to the target IAB host), and uses it as the third configuration information. For example, the IAB node can obtain the CGI of the cell served by the parent node from the system information or broadcast information, and thus determine the configuration information corresponding to the target IAB host from the first configuration information according to the CGI, and use it as the third configuration information.

[0179] Optionally, in the scenario where the IAB node performs a handover, the source IAB host may send fifth indication information to the IAB node. The fifth indication information includes at least one of the following: the base station identifier of the target IAB host, the IP address of the CU of the target IAB host, information for indicating a handover across the Donor-CU, and information for indicating a change in the IAB host. The fifth indication information may be carried in an RRC message (such as an RRC reconfiguration message) generated by the source IAB host, or carried in an F1AP message generated by the source IAB host.

[0180] When the fifth indication information includes the base station identifier of the target IAB host, the IAB node may determine, based on the base station identifier of the target IAB host, the configuration information corresponding to the target IAB host from the first configuration information, and use it as the third configuration information.

[0181] When the fifth indication information includes the IP address of the CU of the target IAB host, after determining the third configuration information, the IAB node triggers a procedure to establish an F1 interface with the CU of the target IAB host indicated by the IP address. The procedure for establishing the F1 interface may include reporting the determined third configuration information to the CU of the target IAB host. Optionally, the IAB node may also determine, based on the IP address, the configuration information corresponding to the target IAB host from the first configuration information, and use it as the third configuration information.

[0182] When the fifth indication information includes information for indicating a handover across the Donor-CU or information for indicating a change in the IAB host (or Donor-CU), the IAB node may learn that the IAB host (or Donor-CU) to which it is connected has changed, and thus needs to determine the configuration information corresponding to the target IAB host from the first configuration information, and use it as the third configuration information. That is to say, the fifth indication information may be used to trigger the IAB node to determine the configuration information corresponding to the target IAB host from the first configuration information, and use it as the third configuration information.

[0183] Exemplarily, after determining the third configuration information, the IAB node may initiate an F1 interface establishment (F1-Setup) procedure with the corresponding target IAB host to establish an F1 interface between the IAB node and the corresponding target IAB host. Specifically, after determining the third configuration information, the IAB-DU triggers a procedure to establish an F1 interface with the target Donor-CU to establish an F1 interface between the IAB-DU and the target Donor-CU. It can also be considered that the fifth indication information triggers the IAB node to initiate an F1 interface establishment (F1-Setup) procedure with the corresponding target IAB host to establish an F1 interface between the IAB node and the corresponding target IAB host.

[0184] Optionally, after determining the third configuration information, the IAB node may establish an IP security association with the security gateway according to the IP address of the security gateway. The security gateway is the security gateway on the path between the IAB node and the target IAB host.

[0185] The fifth indication information may be the source IAB

[0186] It should be noted that operations 303 to 304 may constitute a separate embodiment for the IAB node to obtain multiple configurations from the network management device and select the correct configuration from the multiple configurations. That is to say, the network management device does not necessarily generate the first configuration information according to operation 301.

[0187] If the IP address of the security gateway is not included in the first configuration information, the IAB node may send a request message to the target IAB host to request the IP address of the security gateway.

[0188] Operation 305: The IAB node sends the third configuration information to the network management device.

[0189] As an implementation, in order to save signaling overhead, if the configuration information corresponding to each candidate IAB host in the first configuration information corresponds to an index value, then in operation 305, the IAB node may send the index value corresponding to the third configuration information to the network management device.

[0190] Operation 305 is an optional operation, that is, the network management device may not need the third configuration information, or the network management device may also obtain the third configuration information through other means.

[0191] Optionally, if the IP address information of the IAB node (for example, the local IP address of the IAB node on the F1 interface) is not included in the first configuration information, this embodiment may further include the following operations 306-308;

[0192] Optionally, the network management device may instruct the IAB node to request the corresponding IP address information from the IAB host. Exemplarily, the network management device may send a first indication message to the IAB node. The first indication message may be sent as a separate message or carried in the above-mentioned first configuration information. When the IAB node receives the first indication message, this embodiment may further include the following operations 306-308.

[0193] The first indication information may include at least one of the following: the type indicating that the IAB node requests an IP address from the IAB host, the indication that the IAB node requests an IP address or a prefix of the IP address from the IAB host, the number of IP addresses indicating that the IAB node requests from the IAB host, the number of IP addresses indicating that the IAB node requests from the IAB host for the F1-C interface or F1-C service, the number of IP addresses indicating that the IAB node requests from the IAB host for the F1-U interface or F1-U service, the IP address prefix indicating that the IAB node requests from the IAB host for the F1-C interface or F1-C service, the IP address prefix indicating that the IAB node requests from the IAB host for the F1-U interface or F1-U service.

[0194] Operation 306: The IAB node sends the second information to the IAB host.

[0195] This operation may refer to Operation 204 and may include the optional operations of Operation 204, which will not be elaborated here.

[0196] Operation 307: The IAB host sends the second configuration information of the IAB node to the IAB node.

[0197] This operation may refer to Operation 205 and may include the optional operations of Operation 205, which will not be elaborated here.

[0198] Operation 308: The IAB node sends the second configuration information to the network management device.

[0199] This operation may refer to Operation 206 and may include the optional operations of Operation 206, which will not be elaborated here.

[0200] Operation 308 is an optional operation, that is, after the IAB node obtains the IP address information, it may also choose not to send it to the network management device.

[0201] Operation 308 may be merged with Operation 305, that is, the second configuration information and the third configuration information may be sent to the network management device together in Operation 308. Operation 305 may be omitted as an optional operation.

[0202] Operation 308 may also be replaced with: The IAB host sends the second configuration information to the network management device. That is, after the IAB host assigns the corresponding IP address information to the IAB node, it may also send the second configuration information to the network management device. In this way, the IAB node does not need to send the second configuration information to the network management device.

[0203] The IAB node in the embodiment of this application may be a handover IAB node (such as Figure 5The IAB node in ) can also be a downstream node of the switched IAB (such as Figure 5 a child node of the IAB node 3 in

[0204] In this embodiment, the IAB node sends the location information and / or neighbor cell information of the IAB to the network management device, so that the network management device can learn the candidate IAB hosts that can be accessed / allowed to be accessed around the IAB node, and thus configure the configuration information corresponding to each candidate IAB host for the IAB node and send it to the IAB node.

[0205] The IAB node can determine the corresponding configuration information from the first configuration information according to its target IAB host. The network management device can indicate the IAB node to request the allocation of the corresponding IP address information from the IAB host by an implicit method (the IP address information of the IAB node is not included in the first configuration information) or an explicit method (the first indication information is included in the first configuration information).

[0206] Through this embodiment, the IAB node can select a set of configuration information from multiple sets of configuration information sent by the network management device, and further, the IAB node and the network management device can align the configuration information selected by the IAB node, ensuring the normal operation of the IAB node.

[0207] Figure 9 The following shows a communication method according to an embodiment of the present application. The communication method 400 includes:

[0208] Operation 401: The network management device sends a cell set to the target IAB host.

[0209] Optionally, the network management device pre-sends a cell set to each IAB host node.

[0210] The cell set may include cell information of one or more cells. For example, it may be one or a combination of PCI, CGI, or CellIdentity.

[0211] This operation 401 is an optional operation. For example, if the target IAB host pre-stores the cell set internally, or the cell set is predefined by the protocol, then it may not be necessary to obtain the cell set through the interaction between the network management device and the IAB host. For another example, the target IAB host can generate the fourth configuration information of the IAB node according to the configuration information of the IAB node in S402. For still another example, the target IAB host can obtain information from other devices to generate the fourth configuration information of the IAB node, not necessarily from the network management device.

[0212] Operation 402: The source IAB host sends a handover request message to the target IAB host.

[0213] The handover request message includes the configuration information of the IAB node. The configuration information may include at least one of the following parameters: the local IP address of the IAB node on the F1 interface, gNB ID, the DU identification information of the IAB node (such as DU ID or DUName), gNB ID length, cellLocalId, PLMNIdList, sNSSAIList, PCI, CGI, serving cell bandwidth, TAC, uplink and downlink frequencies, SSB frequency, SSB period, SSB carrier spacing, SSB Offset, SSB Duration, and the cell information of the cell served by the IAB node.

[0214] Optionally, the configuration information may further include: an indication of whether the cell is activated. The indication information corresponds one-to-one with the cell information of the cell served by the IAB node, and is used to indicate whether the cell served by the IAB node is currently activated. The configuration information may be included in the handover request message and sent as the context information of the IAB node.

[0215] The source IAB host may send the handover request message to the target IAB host after receiving the measurement report of the IAB node.

[0216] Operation 403: The target IAB host generates the fourth configuration information of the IAB node according to the configuration information of the IAB node.

[0217] The fourth configuration information may also be referred to as the configuration information of the IAB node under the target IAB host. The fourth configuration information may include at least one of the following parameters: the cell information of the cell served by the IAB node, the local IP address of the IAB node on the F1 interface, the peer IP address of the IAB node on the F1 interface, where the F1 interface further includes the F1-C interface and / or the F1-U interface, the identification information of the IAB-DU (for example: the ID of the IAB-DU, or the name of the IAB-DU), the SSB information of the cell served by the IAB node, the system information of the cell served by the IAB node, the indication information of whether the cell served by the IAB node is activated, and the IP address of the security gateway.

[0218] Exemplarily, after receiving the configuration information of the IAB node sent by the source IAB host, the target IAB host selects new configuration information for the IAB node from the cell set stored locally, for example: allocating the cell identifier of the cell served by the IAB node, and / or allocating the IP address information of the IAB node, and including the selected new configuration information in the fourth configuration information.

[0219] Operation 404: The target IAB host sends the fourth configuration information to the source IAB host.

[0220] The fourth configuration information may be carried in the handover request response message sent by the target IAB host to the source IAB host. The fourth configuration information may exist in the form of a container in the handover request response message.

[0221] The fourth configuration information may be carried in the RRC message generated by the CU of the target IAB donor (for example: handover command message, also known as RRC reconfiguration message).

[0222] Optionally, the fourth configuration information may be carried in the F1AP message generated by the CU of the target IAB donor.

[0223] Operation 405: The source IAB host sends the fourth configuration information to the IAB node.

[0224] After obtaining the fourth configuration information, the source IAB host may not parse it and further transparently transmit it to the IAB node. The fourth configuration information may be carried in the handover command or reconfiguration message sent by the source IAB host to the IAB node. Specifically, the source Donor-CU may carry the fourth configuration information in an F1AP message and send it to the IAB-DU, or the source Donor-CU may carry the fourth configuration information in an RRC message and send it to the IAB-MT, and then the IAB-MT may send it to the IAB-DU through an internal interface.

[0225] Exemplarily, after the CU of the source IAB donor obtains the RRC message in Operation 404 from the CU of the target IAB donor, it forwards it to the MT of the IAB node, and then the MT of the IAB node forwards it to the DU of the IAB node through an internal interface.

[0226] Exemplarily, after the CU of the source IAB donor obtains the F1AP message in Operation 404 from the CU of the target IAB donor, it further encapsulates it in the RRC message generated by the CU of the source IAB donor and sends it to the MT of the IAB node, and the MT of the IAB node forwards it to the DU of the IAB node through an internal interface. Or, after the CU of the source IAB donor obtains the F1AP message from the CU of the target IAB donor, it further encapsulates it in the F1AP message generated by the CU of the source IAB donor and sends it to the DU of the IAB node.

[0227] Optionally, after receiving the fourth configuration information, the IAB node triggers a process of establishing an F1 interface (F1-Setup) with the target IAB host, for establishing the F1 interface between the IAB node and the target IAB host. Specifically, after receiving the fourth configuration information, the IAB-DU triggers a process of establishing an F1 interface with the target Donor-CU, for establishing the F1 interface between the IAB-DU and the target Donor-CU.

[0228] Optionally, after receiving the fourth configuration information, the IAB node may establish an IP security association with the security gateway according to the IP address of the security gateway in the fourth configuration information. The security gateway is the security gateway on the path between the IAB node and the target IAB host.

[0229] Operations 402 to 405 may constitute a separate embodiment for the IAB node to obtain the fourth configuration information from the target IAB host.

[0230] Operation 406: The IAB node sends the fourth configuration information to the network management device.

[0231] Operation 406 and the IAB node establishing the F1 interface with the target IAB host are not in a specific chronological order.

[0232] Operation 406 is an optional operation, that is, after the IAB node obtains the fourth configuration information, it may also choose not to send it to the network management device.

[0233] Operation 406 may also be replaced by: the target IAB host or the source IAB host sends the fourth configuration information to the network management device. That is to say, after the target IAB host or the source IAB host obtains the fourth configuration information, it may also send the fourth configuration information to the network management device. In this way, the IAB node does not need to send the fourth configuration information to the network management device.

[0234] The IAB node in the embodiment of the present application may be a handover IAB node (such as Figure 5 the IAB node 3 in Figure 5 ), or may be a downstream node of the handover IAB (such as

[0235] the child node of the IAB node 3 in

[0236] Figure 10 The following shows a communication method according to an embodiment of the present application. The communication method 500A includes:

[0237] Operation 501A: The IAB node sends second indication information to the network management device.

[0238] The second indication information includes the location information of the IAB node and / or the information of neighboring cells of the IAB node. Optionally, the second indication information may also be indication information for indicating that the physical cell identifier (PCI) of the cell served by the IAB node remains unchanged.

[0239] Exemplarily, the IAB node may send the second indication information to the network management device after switching to the target IAB host.

[0240] Exemplarily, the second indication information may be included in any message sent by the IAB node to the network management device in all the above embodiments, such as a configuration update request message, or other newly defined messages. The embodiments of the present application do not make limitations.

[0241] Operation 502A: The network management device determines whether the cell identifier of the IAB node remains unchanged.

[0242] The network management device can obtain the current location of the IAB node according to the second indication information, and determine whether the physical cell identifier (PCI) of the cell served by the IAB node remains unchanged or needs to be changed.

[0243] Figure 11 The following shows a communication method according to an embodiment of the present application. The communication method 500B includes:

[0244] Operation 501B: The IAB node sends second indication information to the IAB host of the IAB node.

[0245] The IAB node may send the second indication information to the target IAB host during the process of switching to the target IAB host. The IAB node may directly send the second indication information to the target IAB host, or the source IAB host may send the second indication information to the target IAB host.

[0246] The second indication information includes the location information of the IAB node and / or the information of neighboring cells of the IAB node. Optionally, the second indication information may be indication information for indicating that the PCI of the cell served by the IAB node remains unchanged.

[0247] Exemplarily, the second indication information may be included in any message sent by the IAB node to the target IAB host in all the above embodiments, such as a configuration update request message, or other newly defined messages. Or, the second indication information may also be included in the handover request message sent by the source IAB host to the target IAB host in the above embodiments. The embodiments of the present application do not make limitations.

[0248] Operation 502B: The IAB host determines whether the cell identifier of the IAB node remains unchanged.

[0249] The IAB host can, according to the second indication information, learn the current location of the IAB node and determine whether the physical cell identifier of the serving cell of the IAB node remains unchanged or needs to be changed.

[0250] Through this embodiment, updating the PCI during the IAB node handover process can be avoided, the impact on the communication between the IAB node and its child nodes can be reduced, the communication efficiency can be improved, and the user experience can be enhanced.

[0251] Figure 12 The following shows a communication method according to an embodiment of the present application. The communication method 600 includes:

[0252] Operation 601: The first node sends third indication information to the network management device.

[0253] The third indication information is used to indicate whether the first node is an IAB node or an IAB-DU, or an IAB host or a Donor-DU. Alternatively, the third indication information is used to indicate whether the first node is an IAB node or an IAB-DU. Alternatively, the third indication information is used to indicate whether the first node is an IAB host or a Donor-DU. Based on the received third indication information, the network management device can identify the IAB node / IAB-DU and / or the IAB host or the Donor-DU, and generate configuration information for the IAB-DU and / or the Donor-DU respectively.

[0254] Specifically, the third indication information can be an explicit indication or an implicit indication. Among them, the implicit indication means that the third indication information can be the identifier of the IAB node or the IAB host, for example: IAB-DU ID / name, or Donor-DU ID / name; or, the third indication information can also be any information that can identify the identity of the IAB node or the IAB host, for example: the identity identifier of the IAB-DU / Donor-DU.

[0255] Exemplarily, the third indication information can be included in any message sent by the IAB node to the network management device in all the above embodiments, such as in the configuration update request message or the configuration request message, or in other newly defined messages, which is not limited in this embodiment.

[0256] This embodiment mainly solves the problem of how the network management device learns whether the IAB node is an IAB host, so that the network management device can timely understand the situation of the IAB node and realize the control of the IAB node.

[0257] Figure 13The following shows a communication method according to an embodiment of the present application. The communication method 700 includes:

[0258] Operation 701: The IAB node sends fourth indication information to the network management device.

[0259] The fourth indication information is used to indicate the energy-saving status information of the IAB node.

[0260] Specifically, the IAB node includes an IAB-DU and an IAB-MT. The energy saving of the IAB node can be achieved in the following ways: The IAB-MT enters the inactive state, the IAB-DU closes the serving cell or the cell served by the IAB-DU enters the discontinuous transmission state, for example: the DTX state (discontinuous transmission). Among them, the cell served by the IAB-DU entering the DTX state means that the serving cell only sends public information such as system broadcasts, paging messages (Paging), and long-period SSBs, and does not perform data transmission.

[0261] Once the IAB-DU enters the energy-saving state, the IAB node needs to notify the network management device in a timely manner. For example, once the IAB-DU closes the serving cell or the serving cell of the IAB-DU enters the DTX state, the IAB node needs to notify the network management device in a timely manner. That is to say, the fourth indication information is used to indicate that the cell served by the IAB-DU is closed, and / or is used to indicate that the cell served by the IAB-DU enters the DTX state.

[0262] Optionally, when the cell served by the IAB-DU enters the DTX state, the fourth indication information may further include: the SSB information used by the IAB-DU in the DTX state, for example: the period of the SSB.

[0263] Exemplarily, the fourth indication information may be included in any message sent by the IAB node to the network management device in all the above embodiments, such as in a configuration update request message, or in other newly defined messages. This embodiment does not make any limitations.

[0264] Operation 702: The network management device determines the energy-saving status information of the IAB node according to the fourth indication information.

[0265] This embodiment mainly solves the problem of how the network management device learns about the cell status of the IAB node in the energy-saving state, so that the network management device can timely understand the situation of the IAB node and achieve the control of the IAB node.

[0266] Based on the above similar technical concepts, an embodiment of the present application provides a communication device, which can be a relay device, a network device, or a user equipment in any of the communication methods and any possible designs provided in the foregoing embodiments. The relay device, the network device, or the user equipment may be included in any of the communication methods provided in the foregoing embodiments, and may include at least one corresponding unit for performing the method steps, operations, or behaviors performed by the relay device, the network device, or the user equipment. Among them, the setting of the at least one unit may have a one-to-one correspondence with the method steps, operations, or behaviors performed by the relay device, the network device, or the user equipment.

[0267] Figure 14 It is a schematic block diagram of a communication device 800 provided by an embodiment of the present application. Next, in combination with Figure 14 This will specifically describe the structure and functions of the communication device 800. The communication device 800 may include: an acquisition module 800, configured to receive first information from an integrated access and backhaul (IAB) node; a processing module 802, configured to generate first configuration information of the IAB node according to the first information; a sending module 803, configured to send the first configuration information to the IAB node.

[0268] Optionally, the first information includes: cell information of the cell to which the IAB node is connected, and / or a base station identifier of the IAB host of the IAB node.

[0269] Optionally, the cell information includes at least one of the following: cell identifier, cell global identifier, physical cell identifier.

[0270] Optionally, the first information includes: location information or neighbor cell information of the IAB node.

[0271] Optionally, the first configuration information includes X configuration information, and the X configuration information respectively corresponds to X candidate IAB hosts, where X is a positive integer; the method further includes: the network management device receives third configuration information from the IAB node or an index corresponding to the third configuration information, and the third configuration information is determined by the IAB node according to the first configuration information, and the third configuration information has a corresponding relationship with the IAB host selected by the IAB node.

[0272] Optionally, the first configuration information includes at least one of the following: the local Internet protocol (IP) address of the IAB node on the F1 interface, the peer IP address of the IAB node on the F1 interface, cell information of the cell served by the IAB node; where the local end of the F1 interface is the distributed unit (DU) end of the IAB node, and the peer end of the F1 interface is the centralized unit (CU) end of the IAB host of the IAB node.

[0273] Optionally, the processing module 802 generates first configuration information for the IAB node according to the first information, including: the processing module 802 determines the IAB host of the IAB node according to the first information; the processing module 802 generates the first configuration information according to the IAB host.

[0274] Optionally, the processing module 802 generates the first configuration information according to the IAB host, including: the processing module 802 determines the local IP address of the IAB node on the F1 interface according to the DU of the IAB host; and / or, the processing module 802 determines the cell information of the cell served by the IAB node according to the CU of the IAB host.

[0275] Optionally, when the first configuration information does not include the local IP address of the IAB node on the F1 interface, it includes: the sending module 803 also sends first indication information to the IAB node, and the first indication information is used to indicate the type of IP address that the IAB node requests from the IAB host; or, the first indication information is used to indicate the prefix of the IP address that the IAB node requests from the IAB host; or, the first indication information is used to indicate that the IAB node requests X IP addresses from the IAB host; or, the first indication information is used to indicate that the IAB node requests Y IP addresses for the F1-C interface or F1-C service from the IAB host; or, the first indication information is used to indicate that the IAB node requests Z IP addresses for the F1-U interface or F1-U service from the IAB host; or, the first indication information is used to indicate the prefix of the IP address for the F1-C interface or F1-C service that the IAB node requests from the IAB host; or, the first indication information is used to indicate the prefix of the IP address for the F1-U interface or F1-U service that the IAB node requests from the IAB host; X, Y, and Z are positive integers, the F1-C interface is the control plane interface of the F1 interface, and the F1-U interface is the user plane interface of the F1 interface.

[0276] Optionally, the sending module 803 sends a pre-configured cell set to the target IAB host of the IAB node; the obtaining module 801 receives cell information from the IAB node; the cell information is determined by the target IAB host of the IAB node from the pre-configured cell set for the IAB node.

[0277] Optionally, the obtaining module 801 receives second indication information from the IAB node; the processing module 802 determines that the physical cell identifier PCI of the IAB node remains unchanged according to the second indication information.

[0278] Optionally, the obtaining module 801 receives third indication information from the IAB node; the processing module 802 determines, according to the third indication information, that the first node is an IAB node or an IAB host.

[0279] Optionally, the obtaining module 801 receives fourth indication information from the IAB node, where the fourth indication information includes the status of the cell served by the IAB node; wherein, the status of the cell served by the IAB node includes: the cell is closed or the cell is in a discontinuous reception (DTX) state; the processing module 802 determines the status of the cell served by the IAB node according to the fourth indication information.

[0280] Optionally, when the status of the cell served by the IAB node is in the DTX state, the fourth indication information further includes: the SSB information of the cell served by the IAB node.

[0281] Figure 15 It is a schematic block diagram of a communication device 900 provided in an embodiment of the present application. Below, in conjunction with Figure 15 , the structure and functions of the communication device 900 will be specifically described. The communication device 900 may include: a sending module 901, configured to send first information to a network management device; an obtaining module 902, configured to receive first configuration information from the network management device.

[0282] Optionally, the first information includes: cell information of the cell accessed by the IAB node, and / or, the base station identifier of the IAB host of the IAB node.

[0283] Optionally, the cell information includes at least one of the following: cell identifier, cell global identifier, physical cell identifier.

[0284] Optionally, the first information includes: the location information or neighbor cell information of the IAB node.

[0285] Optionally, the first configuration information includes X configuration information, and the X configuration information respectively corresponds to X candidate IAB hosts, where X is a positive integer; the method further includes: the IAB node selects an IAB host; the IAB node determines the configuration information corresponding to the IAB host in the first configuration information as the third configuration information; the IAB node sends the third configuration information or the index corresponding to the third configuration information to the network management device.

[0286] Optionally, the first configuration information includes at least one of the following: the local IP address of the IAB node on the F1 interface, the peer IP address of the IAB node on the F1 interface, and the cell information of the cell served by the IAB node. Wherein, the local end of the F1 interface is the distributed unit (DU) end of the IAB node, and the peer end of the F1 interface is the centralized unit (CU) end of the IAB host of the IAB node.

[0287] Optionally, when the first configuration information does not include the local IP address of the IAB node on the F1 interface, it includes: the obtaining module 902 also receives first indication information from a network management device, where the first indication information is used to indicate the type of IP address that the IAB node requests from the IAB host; or, the first indication information is used to indicate the prefix of the IP address that the IAB node requests from the IAB host; or, the first indication information is used to indicate that the IAB node requests X IP addresses from the IAB host; or, the first indication information is used to indicate that the IAB node requests Y IP addresses for the F1-C interface or F1-C service from the IAB host; or, the first indication information is used to indicate that the IAB node requests Z IP addresses for the F1-U interface or F1-U service from the IAB host; or, the first indication information is used to indicate the prefix of the IP address for the F1-C interface or F1-C service that the IAB node requests from the IAB host; or, the first indication information is used to indicate the prefix of the IP address for the F1-U interface or F1-U service that the IAB node requests from the IAB host. The X, Y, Z, M, and N are positive integers. The F1-C interface is the control plane interface of the F1 interface, and the F1-U interface is the user plane interface of the F1 interface.

[0288] Optionally, the sending module 901 is configured to send second information to the IAB host. The second information is used to request the type of IP address from the IAB host; or, the second information is used to request the IP address prefix from the IAB host; or, the second information is used to request X IP addresses from the IAB host; or, the second information is used to request Y IP addresses for the F1-C interface or F1-C service from the IAB host; or, the second information is used to request Z IP addresses for the F1-U interface or F1-U service from the IAB host; or, the second information is used to request the IP address prefix for the F1-C interface or F1-C service from the IAB host; or, the second information is used to request the IP address prefix for the F1-U interface or F1-U service from the IAB host; X, Y, and Z are positive integers, the F1-C interface is the control plane interface of the F1 interface, and the F1-U interface is the user plane interface of the F1 interface. The obtaining module 902 is configured to receive second configuration information from the IAB host; wherein, the second configuration information may include at least one of the following information: the IP address prefix allocated by the IAB host for the IAB node, the IP address allocated by the IAB host for the IAB node, the IP address for the F1-C interface or F1-C service allocated by the IAB host for the IAB node, the IP address for the F1-U interface or F1-U service allocated by the IAB host for the IAB node, the IP address prefix for the F1-C interface or F1-C service allocated by the IAB host for the IAB node, the IP address prefix for the F1-U interface or F1-U service allocated by the IAB host for the IAB node.

[0289] Optionally, the sending module 901 is further configured to send the second configuration information to the network management device.

[0290] Optionally, the sending module 901 is further configured to send second indication information to the network management device; wherein, the second indication information includes the location information of the IAB node and / or the information of the neighboring cells of the IAB node. Or, the second indication information is used to indicate that the PCI of the cell served by the IAB node remains unchanged.

[0291] Optionally, the sending module 901 is further configured to send third indication information to the network management device; wherein, the third indication information is used to indicate whether the node is an IAB node.

[0292] Optionally, the sending module 901 is further configured to send fourth indication information to the network management device; wherein, the fourth indication information includes the status of the cell served by the IAB node; wherein, the status of the cell served by the IAB node includes: the cell is closed or the cell is in the discontinuous reception DTX state.

[0293] Optionally, when the status of the cell served by the IAB node is that the cell is in the DTX state, the fourth indication information further includes: the SSB information of the cell served by the IAB node.

[0294] Based on the same inventive concept, an embodiment of the present application further provides an apparatus 1000. The structure and functions of the apparatus 1000 will be specifically described below in conjunction with the schematic block diagram of the apparatus 1000. Figure 16 The apparatus may include at least one processor 1001 and an interface circuit 1002. When the program instructions involved are executed in the at least one processor 1001, the apparatus 1000 can implement the communication method provided in any of the foregoing embodiments and any possible design thereof. The interface circuit 1002 can be used to receive program instructions and transmit them to the processor. Alternatively, the interface circuit 1002 can be used for the apparatus 1000 to communicate and interact with other communication devices, such as interacting control signaling and / or service data, etc. The interface circuit 1002 can be a code and / or data read / write interface circuit. Alternatively, the interface circuit 1002 can be a signal transmission interface circuit between a communication processor and a transceiver. Optionally, the communication apparatus 1000 may further include at least one memory 1003, and the memory 1003 can be used to store the required program instructions and / or data involved. Optionally, the apparatus 1000 may further include a power supply circuit 1004, and the power supply circuit 1004 can be used to supply power to the processor 1001. The power supply circuit 1004 can be located within the same chip as the processor 1001, or within another chip outside the chip where the processor 1001 is located. Optionally, the apparatus 1000 may further include a bus 1005, and various parts in the apparatus 1000 can be interconnected through the bus 1005.

[0295] It should be understood that the processor in the embodiment of the present application can be a central processing unit (CPU), and the processor can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, etc. The general-purpose processor can be a microprocessor, or the processor can also be any conventional processor, etc.

[0296] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), or direct rambus RAM (DR RAM).

[0297] The power supply circuit described in the embodiments of the present application includes, but is not limited to, at least one of the following: a power supply line, a power supply subsystem, a power management chip, a power consumption management processor, or a power consumption management control circuit.

[0298] The transceiver device, interface circuit, or transceiver in the embodiments of the present application may include a separate transmitter and / or a separate receiver, or may be an integrated transmitter and receiver. The transceiver device, interface circuit, or transceiver may operate under the instruction of the corresponding processor. Optionally, the transmitter may correspond to a transmitter in a physical device, and the receiver may correspond to a receiver in a physical device.

[0299] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the above division of each functional module is used as an example. In actual applications, the above functions may be allocated to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working processes of the systems, devices, and units described above may refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0300] In the embodiments of 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 modules or units is only a logical function division, and in actual implementation, there may 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 couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

[0301] Those of ordinary skill in the art can realize that the units or algorithm operations of each example described in combination with the embodiments disclosed herein can be implemented by hardware, or by software, or by a combination of software and 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 to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0302] In the present application, "implemented by software" may refer to a processor reading and executing program instructions stored in a memory to implement the functions corresponding to the above-mentioned modules or units. Here, the processor refers to a processing circuit having the function of executing program instructions, including but not limited to at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., which are various processing circuits capable of running program instructions. In some other embodiments, the processor may further include circuits with other processing functions (such as hardware circuits for hardware acceleration, bus, and interface circuits, etc.). The processor may be presented in the form of an integrated chip. For example, it may be presented in the form of an integrated chip whose processing function only includes the function of executing software instructions, or it may also be presented in the form of an SoC (system on a chip). That is, on one chip, in addition to including a processing circuit capable of running program instructions (usually referred to as a "core"), it also includes other hardware circuits for implementing specific functions (of course, these hardware circuits can also be implemented separately based on ASIC or FPGA). Correspondingly, in addition to the function of executing software instructions, the processing function may also include various hardware acceleration functions (such as AI computing, encoding and decoding, compression and decompression, etc.).

[0303] In this application, "implemented by hardware" means that the functions of the above-mentioned modules or units are implemented by a hardware processing circuit that does not have the function of processing program instructions. The hardware processing circuit can be composed of discrete hardware components or can be an integrated circuit. To reduce power consumption and size, the form of an integrated circuit is usually used for implementation. The hardware processing circuit can include an ASIC or a PLD (programmable logic device); among them, the PLD can further include an FPGA, a CPLD (complex programmable logic device), etc. These hardware processing circuits can be a separately packaged semiconductor chip (such as packaged as an ASIC); or can be integrated with other circuits (such as a CPU, a DSP) and then packaged into a semiconductor chip. For example, multiple hardware circuits and a CPU can be formed on a silicon substrate and separately packaged into a chip. Such a chip is also called an SoC, or a circuit for implementing the FPGA function and a CPU can be formed on a silicon substrate and separately enclosed into a chip. Such a chip is also called an SoPC (system on a programmable chip).

[0304] It should be noted that when this application is implemented by software, hardware, or a combination of software and hardware, different software and hardware can be used, and it is not limited to using only one type of software or hardware. For example, one of the modules or units can be implemented using a CPU, and another module or unit can be implemented using a DSP. Similarly, when using hardware for implementation, one of the modules or units can be implemented using an ASIC, and another module or unit can be implemented using an FPGA. Of course, it is not limited that some or all of the modules or units are implemented using the same software (such as all through a CPU) or the same hardware (such as all through an ASIC). In addition, for those skilled in the art, it can be known that software is generally more flexible but has lower performance than hardware, while hardware is just the opposite. Therefore, those skilled in the art can choose software or hardware or a combination of both according to actual needs for implementation.

[0305] In the above embodiments, the descriptions of each embodiment have their own emphases. For the parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. The embodiments of this application can be combined, and some technical features in the embodiments can also be decoupled from the specific embodiments and combined with the existing technology to solve the technical problems involved in the embodiments of this application.

[0306] In the embodiments of the present application, the unit described as a separation component may or may not be physically separated. The component shown as a unit may or may not be a physical unit, that is, it may be located in one place or 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 the embodiments of the present application.

[0307] In addition, in each embodiment of the present application, the functional units may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0308] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or 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 may include several instructions to enable a computer device, such as a personal computer, a server, or a network device, or a processor to execute all or part of the operations of the methods described in the embodiments of the present application. The foregoing storage medium may include: various media that can store program codes such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs, or computer-readable storage media.

[0309] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application, and all of them should be covered by the protection scope of the present application.

Claims

1. A communication method, characterized in that, The communication method is applied to a network management device and includes: Sending a pre-configured cell set to an IAB host of an integrated access and backhaul IAB node, where the pre-configured cell set includes cell information of one or more cells; Receiving first cell information from the IAB node; the first cell information is determined by the IAB host of the IAB node from the pre-configured cell set for the IAB node.

2. The method according to claim 1, wherein The cell information includes at least one of the following: cell identifier, cell global identifier, physical cell identifier.

3. The method according to claim 1 or 2, characterized in that, It includes: Receiving second indication information from the IAB node; Determining, according to the second indication information, that the physical cell identifier PCI of the IAB node remains unchanged.

4. The method according to any one of claims 1 to 3, characterized in that It includes: Receiving third indication information from a first node; Determining, according to the third indication information, that the first node is an IAB node or an IAB host.

5. The method according to any one of claims 1-4, characterized in that, It includes: Receiving fourth indication information from the IAB node, where the fourth indication information includes the status of the cell served by the IAB node; wherein, the status of the cell served by the IAB node includes: cell shutdown or the cell being in a discontinuous reception DTX state; Determining, according to the fourth indication information, the status of the cell served by the IAB node.

6. The method according to claim 5, characterized in that, When the status of the cell served by the IAB node is the cell being in the DTX state, the fourth indication information further includes: the SSB information of the cell served by the IAB node.

7. A communication method, characterized in that, The communication method is applied to an IAB node and includes: Obtaining first cell information, where the first cell information is determined by the IAB host of the IAB node from a pre-configured cell set for the IAB node, and the pre-configured cell set includes cell information of one or more cells; Sending the first cell information to a network management device.

8. A communication device, characterized in that, It includes: At least one processor and an interface circuit, and the computer program involved is executed in the at least one processor so that the communication device executes the method according to any one of claims 1-7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores the computer program involved, and when the computer program involved runs, the method according to any one of claims 1-7 is executed.

10. A computer program product, characterized in that, The computer-readable storage medium stores the computer program involved, and when the computer program involved runs, the method according to any one of claims 1-7 is executed.

Images