Communication method and device

Abstract

The embodiment of the invention provides a communication method and device, and relates to the technical field of communication. The second equipment determines a cell identifier NCI list of the access backhaul integrated IAB node, and the second equipment sends the NCI list of the IAB node to the first equipment; the first device determines the NCI of the IAB node according to the NCI list; and the first equipment sends the NCI of the IAB node to the second equipment. According to the mode, the network function management service architecture is multiplexed, the configuration transmission process configured with the IAB node cell identifier is given, the problem of NCI identifier conflict caused by IAB node mobility can be avoided through the mode, accurate transmission of IAB node services is ensured, and the user experience can be improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular, to a communication method and device. Background Art

[0002] In order to reduce the fiber deployment and reduce the deployment cost, the fifth-generation mobile communication system (5G) introduces the integrated access and backhaul (IAB) network technology. The IAB node can be composed of a mobile termination (MT) part and a distributed unit (DU) part. When the IAB node faces its parent node, it can be regarded as a user device, that is, the role of MT; when the IAB node faces its child node (the child node may be another IAB node, or an ordinary user equipment (UE)), it can be regarded as a network device that provides backhaul services for the child node, that is, as a DU role.

[0003] The IAB node (IAB-MT) can obtain OAM services from the operation, management and maintenance (OAM) entity through the protocol data unit (PDU) session with the core network entity. The IAB node can also directly obtain OAM services from the OAM entity through the Internet Protocol (IP) backhaul link. In order to ensure the accurate transmission of OAM services and the user experience, cell identifiers can be configured for different IAB nodes, but how to configure cell identifiers for IAB nodes and how to report cell identifiers to OAM have not yet been determined. Summary of the invention

[0004] The present application provides a communication method and a communication device, so as to determine the configuration of the IAB node cell identifier and the data transmission process in the case of an architecture that multiplexes the OAM service.

[0005] In a first aspect, the present application provides a communication method, which can be executed through the interaction of a first device and a second device, wherein the second device can be a cross-domain management function unit, such as OAM, network management system (network management system, NMS), management service producer (management service producer, MnSProducer), management service consumer (management service Consumer, MnS Consumer) and other devices, or a chip used to implement a cross-domain management function unit, or a cross-domain management device, and the first device is a domain management function unit, such as an element management system (element management system, EMS), a mobile broadband automation engine (mobile broadband automation engine, MAE), MnS Producer, MnS Consumer, an access network domain management function unit (radio access network domain management function, RAN-Domain-MnF), a core network domain management function unit (core network domain management function, CN-Domain-MnF) or a chip used to implement a domain management function unit, or a single domain management device; in addition, the first device can also be a network element device (such as a base station, a core network element, etc.), and the second device can also be a domain management network element. Of course, in actual application, other devices may also be involved in the interaction, which is not specifically limited here. Execution is as follows:

[0006] The second device determines a new radio cell identifier (NCI) list of the IAB node, the second device sends the NCI list of the IAB node to the first device, the first device determines the NCI of the IAB node according to the NCI list, and the first device sends the NCI of the IAB node to the second device.

[0007] After the present application determines the NCI list of the IAB node through the second device, the NCI list of the IAB node is transmitted to the first device. After the first device determines the NCI of the IAB node, the NCI of the IAB node is transmitted back to the second device. This method establishes a network resource model for the IAB node, reuses the network function management service architecture, and provides a configuration transmission process for configuring the IAB node cell identifier. This method can avoid the problem of NCI identifier conflict caused by the mobility of the IAB node, ensure the accurate transmission of the IAB node service, and improve the user experience.

[0008] In an optional manner, the first device selects the NCI of the IAB node from the NCI list.

[0009] This approach can avoid the NCI collision caused by IAB node movement and the subsequent F1 interface establishment failure caused by the first device selecting the NCI of the IAB node from the NCI list, and can ensure accurate transmission of IAB node services and improve user experience.

[0010] In an optional manner, the first device sends the NCI list to the IAB host base station; the IAB host base station selects the NCI of the IAB node from the NCI list; the IAB host base station sends the NCI of the IAB node to the first device; the first device receives the NCI of the IAB node from the IAB host base station.

[0011] This method can avoid the situation where NCI collision caused by IAB node movement and thus the failure of F1 interface establishment occurs by selecting the NCI of the IAB node from the NCI list through the IAB host base station, and can ensure the accurate transmission of IAB node services and improve user experience.

[0012] In an optional manner, the first device is a domain management functional unit, and the second device is a cross-domain management functional unit; wherein the domain management functional unit is an access network domain management functional unit, or a core network domain management functional unit.

[0013] In an optional manner, the first device is a core network domain management function unit, the IAB host base station sends the NCI of the IAB node to an access and mobility management function (AMF); the AMF sends the NCI of the IAB node to the first device; or, the IAB host base station sends the NCI of the IAB node to the IAB node; the IAB node sends the NCI of the IAB node to a user plane function (UPF); the UPF sends the NCI of the IAB node to the first device.

[0014] This method transmits the updated NCI of the IAB node to the cross-domain management functional unit through the IAB host base station through the core network node, reuses the transmission architecture of the existing OAM service, and ensures the update of the NCI of the IAB node in the cross-domain management functional unit.

[0015] In the second aspect, the present application provides a communication method, which can be executed through the interaction of a first device, a second device and a third device, wherein the second device can be a cross-domain management function unit, such as OAM, NMS, MnS Producer, MnS Consumer and other devices, or a chip for implementing a cross-domain management function unit, or a cross-domain management device, the first device is an access network domain management function unit, such as EMS, MAE, MnS Producer, MnS Consumer, RAN-Domain-MnF, CN-Domain-MnF or a chip for implementing a domain management function unit, or a single domain management device; the third device is a core network domain management function unit, such as CN-Domain-MnF or a chip for implementing a domain management function unit, or a single domain management device; in addition, the first device can also be a network element device (such as a base station), the second device can also be a domain management network element, and the third device is a network element device (such as a core network network element). Of course, in actual application, the interaction of other devices may also be involved, which is not specifically limited here. This application is not specifically limited here. Execute as follows:

[0016] The second device determines the NCI list of the IAB node, the second device sends the NCI list of the IAB node to the first device, the first device determines the NCI of the IAB node according to the NCI list, and the third device sends the NCI of the IAB node to the first device.

[0017] In an optional manner, the first device selects the NCI of the IAB node from the NCI list.

[0018] In an optional manner, the first device sends the NCI list to the IAB host base station; the IAB host base station selects the NCI of the IAB node from the NCI list; and the IAB host base station sends the NCI of the IAB node to the first device.

[0019] In an optional manner, the IAB host base station sends the NCI of the IAB node to the AMF; the AMF sends the NCI of the IAB node to the third device.

[0020] In an optional manner, before the third device sends the NCI of the IAB node to the second device, the IAB host base station sends the NCI of the IAB node to the IAB node; the IAB node sends the NCI of the IAB node to the UPF; and the UPF sends the NCI of the IAB node to the third device.

[0021] In an optional manner, the NCI includes: a base station identifier and a cell identifier.

[0022] In a third aspect, an embodiment of the present application provides a communication device, which may be a first device (such as the first device in the first aspect, the first device in the second aspect) or a chip disposed inside the first device, or may be a second device (such as the second device in the first aspect, the second device in the second aspect) or a chip disposed inside the second device. The communication device has the function of implementing any aspect of the first to second aspects above, for example, the communication device includes a module or unit or means corresponding to the steps involved in executing any aspect of the first to second aspects above, and the function or unit or means may be implemented by software, or by hardware, or may be implemented by hardware executing the corresponding software.

[0023] In one possible design, the communication device includes a processing unit and a transceiver unit, wherein the transceiver unit can be used to send and receive signals to realize communication between the communication device and other devices, for example, the transceiver unit is used to receive information from; the processing unit can be used to perform some internal operations of the communication device. The transceiver unit can be called an input-output unit, a communication unit, etc., and the transceiver unit can be a transceiver; the processing unit can be a processor. When the communication device is a module (such as a chip) in a communication device, the transceiver unit can be an input-output interface, an input-output circuit or an input-output pin, etc., and can also be called an interface, a communication interface or an interface circuit, etc.; the processing unit can be a processor, a processing circuit or a logic circuit, etc.

[0024] In another possible design, the communication device includes a processor and may also include a transceiver, the transceiver is used to send and receive signals, and the processor executes program instructions to complete the method in any possible design or implementation of the first aspect to the second aspect. The communication device may also include one or more memories, the memory is used to couple with the processor, and the memory can store the necessary computer programs or instructions for implementing the functions involved in any aspect of the first aspect to the second aspect. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first aspect to the second aspect.

[0025] In another possible design, the communication device includes a processor, which can be used to couple with a memory. The memory can store necessary computer programs or instructions for implementing the functions involved in any one of the first to second aspects. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first to second aspects.

[0026] In another possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design or implementation of the first to second aspects above.

[0027] It can be understood that in the third aspect above, the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. In addition, the above processors can be one or more, and the memories can be one or more. The memory can be integrated with the processor, or the memory can be separately set from the processor. In the specific implementation process, the memory can be integrated with the processor on the same chip, or can be set on different chips respectively. The embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.

[0028] In a fourth aspect, an embodiment of the present application provides a communication system, which includes the first device and the second device in the above-mentioned first aspect to the second aspect.

[0029] In a fifth aspect, the present application provides a chip system, which includes a processor and may also include a memory, for implementing the method described in any possible design of the first to fifth aspects above. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0030] In a sixth aspect, the present application also provides a computer-readable storage medium, in which computer-readable instructions are stored. When the computer-readable instructions are executed on a computer, the computer executes a method in any possible design of the first aspect to the second aspect.

[0031] In a seventh aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the methods of the various embodiments of the first to second aspects described above.

[0032] For the technical effects that can be achieved in the above-mentioned second to seventh aspects, please refer to the description of the technical effects that can be achieved by the corresponding possible design schemes in the above-mentioned first aspect, and this application will not repeat them here. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 A schematic diagram of an IAB networking scenario is shown;

[0034] Figure 2 A schematic diagram of an IAB network architecture is shown;

[0035] Figure 3 A schematic diagram of a service-oriented management architecture applicable to an embodiment of the present application is shown;

[0036] Figure 4 A schematic flow chart of a communication method is shown;

[0037] Figure 5 A schematic diagram of a process of configuring an NCI of an IAB node is shown;

[0038] Fig. 6A A schematic diagram of a model of a DU and a DU cell is shown;

[0039] Figure 6B A schematic diagram of a model of a DU and IAB node cell is shown;

[0040] Figure 7 A schematic diagram of a process of configuring an NCI of an IAB node is shown;

[0041] Figure 8 A schematic diagram of a process of configuring an NCI of an IAB node is shown;

[0042] Fig. 9 A schematic diagram of a process of configuring an NCI of an IAB node is shown;

[0043] Fig.10 A schematic diagram of a process of configuring an NCI of an IAB node is shown;

[0044] Fig.11 A schematic diagram of a process of configuring an NCI of an IAB node is shown;

[0045] Fig.12 A schematic structural diagram of a communication device is shown;

[0046] Fig.13 A schematic structural diagram of a communication device is shown;

[0047] Fig.14 A structural schematic diagram of a communication device is shown. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The specific operating method in the method embodiment can also be applied to the device embodiment or system embodiment. Among them, in the description of the present application, unless otherwise specified, the meaning of "multiple" is two or more. Therefore, the implementation of the device and the method can refer to each other, and the repetitions will not be repeated.

[0049] Multi-hop networking may be used in the IAB network. Taking into account the need for service transmission reliability, the IAB node can support dual connectivity (DC) or multi-connectivity to cope with abnormal situations that may occur in the backhaul link (for example, interruption or blockage of the wireless link and load fluctuations, etc.) to improve the reliability of transmission. Therefore, the IAB network can support multi-hop and multi-connection networking, and there may be multiple routing paths between the terminal device and the host base station. Among them, on one path, there is a definite hierarchical relationship between the IAB nodes, and between the IAB nodes and the host base station serving the IAB nodes. Each IAB node regards the node that provides backhaul services to it as a parent node, and accordingly, each IAB node can be regarded as a child node of its parent node.

[0050] It should be understood that the outage or blockage of the wireless link may lead to wireless link failure or congestion. For example, when there is a building obstructing the UE and the IAB host node, the wireless link between the UE and the IAB host node may be blocked. In the prior art, the main reasons for wireless link failure are when the physical layer indicates that there is a problem with the wireless link and it exceeds a certain duration or random access fails or the radio link layer control (radio link control, RLC) fails. It should be understood that there may be other reasons for wireless link failure, which are not limited in the embodiments of the present application. Wireless link congestion may refer to the amount of uplink or downlink cache data to be transmitted by a certain IAB node on a certain link exceeding a certain threshold.

[0051] The IAB node may include an MT part and a DU part. When the IAB node faces its parent node, it can be regarded as a terminal device accessing the parent node, that is, as an MT; when the IAB node faces its child node, it can be regarded as a network device providing backhaul services for the child node, that is, as a DU. The child node here may be another IAB node or a terminal device.

[0052] The IAB host node can be an access network element with complete base station functions, such as a host base station DgNB, or an access network element with a centralized unit (CU) and DU separated. The IAB host node is connected to the core network element (e.g., connected to the 5G core network) serving the terminal device and provides wireless backhaul functions for the IAB node. For ease of description, the centralized unit of the IAB host node is referred to as donor CU, and the distributed unit of the IAB host node is referred to as donor DU. The donor CU may also be in the form of a control plane (CP) and a user plane (UP) separated. For example, the CU may be composed of a CU-CP and one (or more) CU-UPs.

[0053] In the embodiment of the present application, the access IAB node refers to the IAB node accessed by the terminal device, that is, the IAB node that provides services for the terminal device. During the IAB uplink transmission process, the access IAB node transmits the uplink data packet sent by the terminal device to the target donor DU through one or more other IAB nodes, and the target donor DU then transmits the uplink data packet to the corresponding donor CU-UP. During the IAB downlink transmission process, if the data packet is sent to the terminal device, the donor CU-UP transmits the downlink data packet sent to the terminal device to the corresponding donor DU, and transmits it to the access IAB node corresponding to the terminal device through one or more other IAB nodes or through a direct backhaul link, and the access IAB node transmits the received downlink data packet to the terminal device; if the data packet is sent to a certain IAB node, the donor CU-UP transmits the downlink data packet sent to the IAB node to the corresponding donor DU, and transmits it to the parent node of the IAB node through one or more other IAB nodes or through a direct backhaul link, and the parent node of the IAB node then transmits the received downlink data packet to this IAB node.

[0054] It should be understood that during the IAB downlink transmission process, if the node where the data packet finally arrives (hereinafter referred to as the terminal node) is a terminal device, the target node is the access IAB node corresponding to the terminal device. If the terminal node is a certain IAB node, the target node is the parent node of the IAB node. During the IAB uplink transmission process, the terminal node is the donor CU-UP, and the target node is the donor DU corresponding to the donor CU-UP. Among them, the target node can also be called the target receiving node.

[0055] like Figure 1The figure shows a schematic diagram of the IAB networking scenario. Among them, the parent node of IAB node 1 is the IAB donor, IABnode 1 is the parent node of IAB node 2 and IAB node 3, IAB node 2 and IAB node 3 are both the parent nodes of IAB node 4, and the parent node of IAB node 5 is IAB node 2. The uplink data packet sent by UE1 can be transmitted to the IAB donor through one or more IAB nodes, and then sent by the IAB donor to the mobile gateway device (for example, the user plane functional unit in the 5G core network). The downlink data packet will be received by the IAB donor from the mobile gateway device and sent to UE1 through one or more IAB nodes. The same applies to UE2.

[0056] There are two available paths for data packet transmission between UE1 and IAB donor, including path 1: UE1→IABnode4→IAB node3→IAB node 1→IAB donor; path 2: UE1→IAB node4→IAB node2→IABnode 1→IAB donor.

[0057] Among them, IAB node4 is the access IAB node of UE1, in path 1, IAB node3 and IAB node 1 are intermediate IAB nodes, in path 2, IAB node2 and IAB node 1 are intermediate IAB nodes, and IAB donor is the target node.

[0058] There are three available paths for data transmission between UE2 and IAB donor, including path 3: UE2→IABnode4→IAB node3→IAB node 1→IAB donor; path 4: UE2→IAB node4→IAB node2→IABnode 1→IAB donor; path 5: UE2→IAB node5→IAB node2→IAB node 1→IAB donor.

[0059] Among them, in path 3, IAB node4 is the access IAB node of UE1, IAB node3 and IAB node 1 are intermediate IAB nodes, in path 4, IAB node4 is the access IAB node of UE1, IAB node2 and IAB node 1 are intermediate IAB nodes, in path 5, IAB node5 is the access IAB node of UE1, IAB node2 and IAB node 1 are intermediate IAB nodes. IAB donor is the target node.

[0060] It should be understood that Figure 1 The IAB networking scenario shown is merely exemplary. There are many other possibilities in the IAB network that supports multi-hop and multi-connection networking, which are not listed here one by one.

[0061] Figure 2 A schematic diagram of an IAB network architecture is shown, including an IAB network of a standalone (SA) network and an IAB network of a non-standalone (NSA) network. Figure 2 Taking IAB node1 and IAB node2 as examples, IAB donor can be further divided into DU and CU parts, and CU can be further divided into CU-CP and CU-UP parts. Figure 2 IAB donor1 and IAB donor2 are used as examples for explanation.

[0062] The DU part of each IAB node has an F1 interface with the IAB donor CU. The F1 interface includes a control plane and a user plane. The user plane is maintained between the IAB-DU and the IAB donor CU-UP, while the control plane is maintained between the IAB-DU and the IAB donor CU-CP. The F1 interface between the IAB-DU and the IAB donor CU is Figure 2 The UE and the DU of the IAB node are connected via the NR Uu interface, and the MT and DU in each IAB node are connected via the NR BH interface. The IAB donor CU-CP and the IAB donor CU-UP are connected via the E1 interface.

[0063] When the IAB node works in SA mode, the IAB node can be connected to one parent node or two parent nodes, where the two parent nodes can be controlled by the same IAB donor or by different IAB donors. The DU part of the IAB node can establish an F1 interface with an IAB donor, and the IAB donor can be connected to the 5G core network (5G core, 5GC), that is, the dotted part in the figure. The IAB-donor-CU-CP is connected to the control plane network element (such as the access and mobility management function AMF) in the 5GC through the NG control plane interface (NG-C), and the IAB-donor-CU-UP is connected to the user plane network element (such as the user plane function UPF) in the 5GC through the NG user plane interface (NG-U).

[0064] When the IAB node works in NSA mode (or EN-DC mode), the IAB-donor-CU-UP can be connected to the EPC (for example, connected to the serving gateway (SGW)) through the S1 user plane interface, there is an LTE Uu air interface connection between the MeNB and the MT of the IAB node, there is an X2 / Xn-C interface between the MeNB and the IAB-donor-CU-CP, and the MeNB is connected to the EPC through the S1 interface (including the S1 interface user plane and the S1 interface control plane). For example, the IAB-donor-CU-UP is connected to the EPC through the S1 interface user plane (S1-U).

[0065] Another possible scenario, Figure 2 The MeNB in ​​the 5G base station can also be replaced with a 5G gNB. Figure 2 The dotted LTE-Uu interface in the figure is replaced by the NR-Uu interface accordingly. The gNB can establish a user plane and / or control plane interface with the 5GC. The gNB and IAB-donor provide dual connection services for the IAB node. The gNB can act as the primary base station of the IAB node, or the secondary base station.

[0066] Figure 3 A schematic diagram of a service-oriented management architecture applicable to an embodiment of the present application is shown. The service-oriented management architecture includes a business support system (BSS), a cross-domain management function unit (CD-MnF), a domain management function unit (Domain-MnF) and a network element (element). It should be understood that the cross-domain management function unit can be a node such as OAM, NMS, MnS Producer, MnS Consumer, etc., and the domain management function unit can be a node such as EMS, MAE, MnS Producer, MnS Consumer, etc.

[0067] If the management service is a management service provided by a cross-domain management functional unit, then the cross-domain management functional unit is the management service producer, and the business support system is the management service consumer.

[0068] If the management service is a management service provided by a domain management functional unit, then the domain management functional unit is a management service producer, and the cross-domain management functional unit is a management service consumer.

[0069] When the management service is a management service provided by a network element, the network element is a management service producer, and the domain management functional unit is a management service consumer.

[0070] The business support system is oriented to communication services and is used to provide functions and management services such as billing, settlement, accounting, customer service, business, network monitoring, communication service life cycle management, and business intent translation. The business support system can be an operator's operating system or a vertical industry operating system (vertical OTsystem).

[0071] The cross-domain management function unit, also called the network management function unit (NMF), can be, for example, a network management entity such as a network management system (NMS), a network function management service consumer (NFMS_C), etc. The cross-domain management function unit provides one or more of the following management functions or management services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization functions, and translation of the network intent (intent from communication service provider, Intent-CSP) of the service producer, etc.

[0072] Among them, the network referred to in the above management function or management service may include one or more network elements or subnetworks, or a network slice. That is to say, the network management function unit may be a network slice management function unit (network slice management function, NSMF), or a cross-domain management data analytical function unit (management data analytical function, MDAF), or a cross-domain self-organization network function (SON Function) or a cross-domain intent management function unit (intentdriven management service, MnS).

[0073] Optionally, in some deployment scenarios, the cross-domain management functional unit can also provide sub-network lifecycle management, sub-network deployment, sub-network fault management, sub-network performance management, sub-network configuration management, sub-network assurance, sub-network optimization functions, sub-network service producer network intent (Intent-CSP) or sub-network service consumer network intent (intent from communication service consumer, Intent-CSC) translation, etc. The sub-network here consists of multiple small sub-networks, which can be network slice sub-networks.

[0074] Domain management function (Domain-MnF), also called network management function (NMF) or network element management function. For example, the domain management function can be a network element management entity such as a wireless automation engine (MBB automation engine, MAE), an element management system (element management system, EMS), or a network function management service provider (network function management service provider, NFMS_P).

[0075] The domain management functional unit provides one or more of the following functions or management services: lifecycle management of sub-networks or network elements, deployment of sub-networks or network elements, fault management of sub-networks or network elements, performance management of sub-networks or network elements, assurance of sub-networks or network elements, optimization functions of sub-networks or network elements, and translation of intent (intent from network operator, Intent-NOP) of sub-networks or network elements. The sub-network here includes one or more network elements. A sub-network may also include a sub-network, that is, one or more sub-networks form a larger sub-network.

[0076] Optionally, the subnetwork here can also be a network slice subnetwork. The domain management system can be a network slice subnet management function unit (network slice subnet management function, NSSMF), a domain management data analytical function unit (management data analytical function, Domain MDAF), a domain self-organization network function (self-organization network function, SON Function), a domain intent management function unit IntentDriven MnS, etc.

[0077] The domain management functional units can be classified as follows:

[0078] According to the network type, it can be divided into: access network domain management function unit (radio access network domain management function, RAN-Domain-MnF), core network domain management function unit (core network domain management function, CN-Domain-MnF), transport network domain management function unit (transport network domain management function, TN-Domain-MnF), etc. It should be noted that the domain management function unit can also be a domain network management system, which can manage one or more of the access network, core network or transport network;

[0079] According to the administrative region classification, it can be divided into: domain management functional units of a certain area, such as Shanghai domain management functional unit, Beijing domain management functional unit, etc.

[0080] Network elements are entities that provide network services, including core network elements and access network elements. Among them, core network elements include: access and mobility management function (AMF), session management function (SMF), policy control function (PCF), network data analytical function (NWDAF), network repository unit (NFRepository Function, NRF) and gateways. Access network elements include: base stations (such as gNB, eNB), central unit control plane (CUCP), central unit (CU), distributed unit (DU), central unit user plane (CUUP), etc.

[0081] Among them, the network element can provide one or more of the following management functions or management services: network element life cycle management, network element deployment, network element fault management, network element performance management, network element assurance, network element optimization function and network element intent translation, etc. Of course, in actual application, the network element can also provide services for IAB nodes and terminal devices.

[0082] IAB-MT can obtain OAM services from OAM entities through PDU sessions with core network entities. OAM services include: receiving commands (operation message commands related to FM, CM, PM, etc.), configuration data, software download (for example: for device software upgrade), alarms, and performance indicator information. The transmission connection between the IAB node and its OAM uses the IP protocol, which is provided by the IAB-MTs PDU session through the 5G network, or when the IAB-MT uses EN-DC, it is provided by the IAB-MTs PDN connection through the LTE network. The IAB node can also obtain OAM services from the OAM entity through the IP backhaul link. Under this IAB node architecture, the NCI allocation issue of the IAB node is being discussed in the 3GPP standard. The IAB donor CU can allocate NCI to the IAB node based on the NCI candidate list configured by OAM for the IAB node. However, how to configure the NCI of the IABnode and how to inform the OAM of the configured NCI have not yet been discussed.

[0083] In addition, for a mobile IAB node, when the IAB node moves and the IAB donor CU (hereinafter referred to as CU) serving the IAB node changes, the processing logic of the IAB node is that the IAB donor DU initiates the F1 establishment process to the CU, and exchanges NCI information. If at this time the NCI of the IAB node conflicts with that of other IAB nodes under the current CU, problems such as F1 establishment failure will occur.

[0084] In the related art, the mobile IAB node accesses the network as a UE, and its NCI can be assigned by the cross-domain network node (i.e., the cross-domain management function unit) by default. Since the mobile IAB node may belong to different cross-domain network nodes, the NCIs of the IAB nodes belonging to different cross-domain network nodes may be the same. Therefore, a candidate list of NCIs can be configured through the cross-domain network management function unit, and then the NCI can be selected by the CU to avoid NCI conflicts caused by the movement of the IAB node.

[0085] In addition, NCI is composed of gNBID (base station identifier) ​​and celllocalID (cell identifier), so there may be two types of NCI candidate lists:

[0086] Candidate list of CelllocalID;

[0087] Candidate list of gNBID and celllocalID combinations (for mobile IABnode).

[0088] It should be noted that the cell identifier here may refer to the cell identifier of the IAB node, or the identifier of the IAB node.

[0089] Based on this, the present application provides a communication method to clarify how to configure the NCI of the IABnode and how to inform the OAM of the configured NCI. When the method is executed, it can be executed through the interaction between the first device and the second device, wherein the second device can be a cross-domain management function unit, such as OAM, NMS, MnS Producer, MnS Consumer and other devices, or a chip for implementing a cross-domain management function unit, or a cross-domain management device, and the first device is a domain management function unit, such as EMS, MAE, MnS Producer, MnS Consumer, RAN-Domain-MnF, CN-Domain-MnF or a chip for implementing a domain management function unit, or a single domain management device; in addition, the first device can also be a network element device (such as a base station, a core network element, etc.), and the second device can also be a domain management network element. Of course, in actual application, the interaction of other devices may also be involved, which is not specifically limited here. Figure 4The interaction between the first device and the second device is used as an example to illustrate. The execution is as follows:

[0090] Step 401: The second device determines an NCI list of IAB nodes.

[0091] The second device mentioned above has a management function and can generally configure identification information for a network element node. Based on this, the second device can configure an NCI list for the IAB node.

[0092] For example, the second device determines candidate NCI lists of CU1 and CU2 respectively, as shown in Table 1 below, the candidate NCI list of CU1 includes NCI1 to NCI10, and the candidate NCI list of CU2 includes NCI11 to NCI20. The two IAB nodes under CU1 are IAB node1 and IAB node2, and the cells under IAB node1 and IAB node2 can select NCI from the candidate NCI list of CU1. The three IAB nodes under CU2 are IAB node3, IAB node4 and IAB node5, and the cells of IAB node3, IAB node4 and IAB node5 can select NCI from the candidate NCI list of CU2.

[0093] Table 1

[0094]

[0095] It should be noted that the candidate NCI list can be a list consisting of a base station identifier (e.g., gNBID) and a cell identifier (e.g., cellLocalID). For example, for the NCI candidate list of CU1, NCI1 is gNBID1, cellLocalID1, NCI2 is gNBID1, cellLocalID2, and NCI3 is gNBID1, cellLocalID3. For the NCI candidate list of CU2, NCI11 is gNBID2, cellLocalID1, NCI12 is gNBID2, cellLocalID2, and NCI13 is gNBID2, cellLocalID3. This is only an exemplary description and will not be explained one by one here. Optionally, the candidate NCI list may also be a list of cell identifiers. For example, for the candidate NCI list of CU1, NCI1 is cellLocalID1, NCI2 is cellLocalID2, and NCI3 is cellLocalID3. For the candidate NCI list of CU2, NCI11 is cellLocalID11, NCI12 is cellLocalID12, and NCI13 is cellLocalID13. These are merely illustrative and will not be described in detail here.

[0096] Optionally, before executing the above step 401, the second device needs to know that the IAB node has joined the network, that is, the IAB node (IAB-MT) has established a PDU session with the core network entity. Then, when the IAB node joins the network, it needs to send IAB node indication information to inform the second device that the node is an IAB node. Optionally, it can further indicate whether the node is a mobile IAB node or a non-mobile IAB node. Specifically, when the IAB node joins the network, the IAB node indication information is sent to the core network. After the core network receives the IAB node indication information, it sends the IAB node indication information to the second device (that is, the cross-domain management device) through the single-domain management device of the core network, indicating that the node is an IAB node. For example, the following two solutions can be adopted: the UPF node of the core network sends the indication information of IABnode to the second device through the single-domain management device of the core network, that is, the indication information of IABnode needs to be added in the instance of the UPF function (UPFFunction) object class, or the AMF node of the core network sends the indication information of IABnode to NMS through the single-domain management device of the core network, that is, the indication information of IABnode needs to be added in the instance of the AMF function (AMFFunction) object class.

[0097] Step 402: The second device sends the NCI list of IAB nodes to the first device.

[0098] It should be noted that the NCI list of the IAB node may be only an NCI list, which implicitly indicates that the NCI list belongs to the IAB node. Optionally, the second device may also send IAB node indication information, and the IAB node indication information is used to indicate that the NCI list is for use by the IAB node, that is, the NCI list is indicated by the indication information of the IAB node as configured by the second device for the IAB node. This application does not specifically limit how to implement it.

[0099] Step 403: The first device determines the NCI of the IAB node according to the NCI list.

[0100] Specifically, the first device may select the NCI of the IAB node from the candidate NCI list, for example, different NCIs may be selected for the cells of IABnode1 and IABnode2 of CU1 from the candidate NCI list. In this manner, the first device selects the NCI of the IAB node from the NCI list, which can avoid the NCI collision caused by the movement of the IAB node and the subsequent failure of establishing the F1 interface, and can ensure the accurate transmission of the IAB node service and improve the user experience.

[0101] Optionally, the first device may also send the NCI list to the base station (for example, gNB-CU, or CU), select the NCI of the IAB node through the base station, and then the first device determines it by receiving the NCI of the IAB node of the base station. This method selects the NCI of the IAB node from the NCI list by the IAB host base station, which can avoid the NCI collision caused by the movement of the IAB node and the failure of the F1 interface establishment, and can ensure the accurate transmission of the IAB node service and improve the user experience. It should be noted that the first device can receive the NCI of the IAB node directly from the base station, or the first device can receive the NCI of the IAB node from the base station through the core network AMF, or the first device can receive the NCI of the IAB node from the IAB node through the core network UPF. The present application does not specifically limit how the first device determines the NCI of the IAB node.

[0102] Step 404: The first device sends the NCI of the IAB node to the second device.

[0103] In addition, it should be noted that the second device can also directly determine the NCI of the IAB node. Then, after the second device sends the NCI of the IAB node to the first device, it is forwarded to the IAB host base station through the first device, and then the NCI of the IAB node is sent to the IAB node through the IAB host base station. The above step 404 does not need to be performed.

[0104] After the present application determines the NCI list of the IAB node through the second device, the NCI list of the IAB node is transmitted to the first device. After the first device determines the NCI of the IAB node, the NCI of the IAB node is transmitted back to the second device. This method establishes a network resource model for the IAB node, reuses the network function management service architecture, and provides a configuration transmission process for configuring the IAB node cell identifier. This method can avoid the problem of NCI identifier conflict caused by the mobility of the IAB node, ensure the accurate transmission of the IAB node service, and improve the user experience.

[0105] In order to better illustrate the method of the present application, two specific embodiments are used as follows. In actual application, based on the interaction between the first device and the second device, the IAB node NCI can be selected from the NCI information list of the IAB node, and the NCI of the IAB node can be transmitted back to the second device through the first device. Based on the interaction between the first device and the second device, the IAB node NCI can be selected from the NCI information list of the IAB node, and the IAB node NCI can be transmitted back to the second device through the third device. The present application does not specifically limit which method is executed, and is specifically introduced through the first and second embodiments.

[0106] Embodiment 1: After the interaction between the first device and the second device, the NCI of the IAB node is selected from the NCI information list of the IAB node, and the NCI of the IAB node is transmitted back to the second device through the first device

[0107] Next, the second device is taken as the cross-domain management function unit, and NMS is used as an example here to illustrate; the first device is the domain management function unit, and the access network domain management function unit RAN-Domain-MnF is used as an example here to illustrate; the IAB host base station is CU and IAB node are used as examples to illustrate. Of course, in actual applications, the number of IAB nodes may be multiple. This is only an example and does not limit the number of IAB nodes. The interface between NMS and RAN-Domain-MnF (or CN-Domain-MnF) is a standardized interface, generally referred to as a service-oriented interface, or a northbound interface. The interface between RAN-Domain-MnF (or CN-Domain-MnF) and CU belongs to the product implementation, generally referred to as a southbound interface, or a privatized interface. The interface between CU and IABnode is a standardized F1 interface. During specific execution, the following three different situations may be included, as follows:

[0108] Case 1 , CU selects the NCI of the IAB node and sends the selected NCI to the NMS via RAN-Domain-MnF

[0109] See also Figure 5 Execute as follows:

[0110] Step 501: The NMS determines the NCI list of the IAB node.

[0111] Specifically, the NMS determines the NCI list of the IAB node of the CU. Figure 4 The NCI list can be understood through the introduction, which is not repeated here.

[0112] For example, in a scenario with multiple CUs, the NMS needs to determine the NCI list of IAB nodes corresponding to the multiple CUs.

[0113] Step 502: The NMS sends the NCI list of IAB nodes to the RAN-Domain-MnF.

[0114] Optionally, the NMS may also send indication information of the IAB node, where the indication information is used to indicate that the NCI list is used to configure the IAB node.

[0115] It should be noted that the NMS also needs to send the identification information of the CU or the identification information of the base station to the RAN-Domain-MnF so that the RAN-Domain-MnF can identify which CU or base station the NCI list belongs to.

[0116] It should be noted that the candidate NCI list of the IAB node is defined by the information model of the network resource model (NRM) of the network function. That is, the RAN-Domain-MnF needs to pre-establish the models of the IABdonor DU and the IAB node to implement the information configuration of the network node by the NMS. In actual application, the NRM information model of the CU, IABnode and IAB nodecell can directly reuse the information model definition of the existing gNB-CU, gNB-DU and DU cell NRM, or the NRM information model of the IAB node can directly reuse the information model definition of the existing gNB-DU NRM, which is a newly defined NRM information model of the IABnodecell, and this application is not specifically limited here.

[0117] It should be noted that the CU can reuse the information model definition of the NRM of the existing gNB-CU, and the definition in 3GPP TS28.541 can be referred to. This application will not be repeated here.

[0118] It should also be noted that the CU here can be called gNB-CU or IAB-donor-CU, and this application does not limit this.

[0119] The following is a brief introduction to the two different models:

[0120] Model 1: The NRM information model of CU, IAB node and IAB node cell can directly reuse the information model definition of the existing NRM of gNB-CU, gNB-DU and DU cell

[0121] like Fig. 6A As shown, the IAB node reuses the definition of the object class (information object class, IOC) GNBDUFunction (DU function under GNB) (GNBDUFunction is 1 or more, and multiple are indicated by * in the figure), and the IABnode cell reuses the definition of NRCellDU IOC (DU cell under NR) (NRCellDU is 1 or more, and multiple are indicated by * in the figure). IOC has been defined in the existing protocol, and can be referred to 3GPP TS 28.541. This application does not limit the name definition. Fig. 6AAlso shown is a Managed Element (IOC), which represents a communication device or entity in a communication network that provides support and / or services to users and is used to communicate with a management entity through one or more management interfaces (directly or indirectly) to perform management control.

[0122] NMS determines the candidate NCI list information of the IAB node and / or the indication information of the IAB node, and NMS sends a message to RAN-Domain-MnF requesting to create or update the GNBDUFunction IOC and, the message includes the candidate NCI list of the IAB node and / or the indication information of the IAB node. After receiving the message requesting to create or update GNBDUFunction and NRDUCell, RAN-Domain-MnF creates or updates the information of GNBDUFunction and NRDUCell. Exemplarily, the information of GNBDUFunction is shown in Table 2 below. Other existing information of GNBDUFunction IOC and the information in NRDUCell IOC can be described in the existing 3GPP TS28.541, which will not be repeated in this application. It should be noted that the IOC NRM model configuration information of GNBDUFunction and NRDUCell can be sent simultaneously in one operation or in different operations, which is not limited in this application.

[0123] Table 2

[0124]

[0125] Optionally, the NMS determines the candidate NCI list information of the IAB node and / or the indication information of the IAB node, and the NMS sends a message to the RAN-Domain-MnF requesting to create or update the GNBCUCPFunction IOC, where the message includes the candidate NCI list of the IAB node and / or the indication information of the IAB node. After receiving the message requesting to create or update the GNBCUCPFunctionIOC, the RAN-Domain-MnF creates or updates the information of the GNBCUCPFunction IOC. Other existing information of the GNBCUCPFunction IOC can be described in the existing 3GPP TS 28.541, which will not be repeated in this application. By way of example, the information of the GNBCUCPFunction is shown in Table 3 below.

[0126] Table 3

[0127] Property Name Name Meaning ikB Base station identification gNBIdLength Base station identification length gNBCUName Name of the base station CU pL Public land mobile network logo nCIListIABNode IAB Node Candidate NCI List IABNodeIndication Instructions for IAB Nodes

[0128] Model 2: The NRM information model of IAB node can directly reuse the existing gNB-DU NRM information model definition to define the new NRM information model of IABnodecell

[0129] like Figure 6B As shown, the IAB node reuses the definition of GNBDUFunction (GNB DU function) (GNBDUFunction is one or more, and multiple are indicated by * in the figure), and the IABnode cell adopts the definition of IABNodeCell (IAB node cell) (IABnodeCell is one or more, and multiple are indicated by * in the figure). Fig. 6A To understand the description of the ManagedElement IOC table in Figure 6B The ManagedElement IOC in is not described here.

[0130] NMS determines the candidate NCI list information of the IAB node and / or the indication information of the IAB node, and NMS sends a message to RAN-Domain-MnF requesting to create or update the GNBDUFunction IOC and IABNodeCell IOC, and the message includes the candidate NCI list of the IAB node and / or the indication information of the IAB node. After receiving the message requesting to create or update GNBDUFunction and IABNodeCell, RAN-Domain-MnF creates or updates the information of GNBDUFunction and IABNodeCell. Exemplarily, the information of GNBDUFunction is shown in Table 4 below, and the IOC information of IABNodeCell is shown in Table 5 below. Other existing information of GNBDUFunction IOC can be described in the existing 3GPP TS 28.541, which will not be repeated in this application.

[0131] Table 4

[0132]

[0133] Table 5

[0134] Property Name Name Meaning cellLocalId Cell local identifier cellState Cell Status pLMNInfoList Public Land Mobile Network Information List nPNIdentityList Private network identifier list nR PCI Physical cell identification nRTAC Tracking area code arfcnDL Downlink frequency number arfcn Uplink frequency number

[0135] Optionally, the NMS determines the candidate NCI list information of the IAB node and / or the indication information of the IAB node, and the NMS sends a message to the RAN-Domain-MnF requesting the creation or update of the GNBCUCPFunction IOC and IABNodeCell IOC, wherein the message includes the candidate NCI list of the IAB node and / or the indication information of the IAB node. After receiving the message requesting the creation or update of the GNBCUCPFunction IOC and IABNodeCell IOC, the RAN-Domain-MnF creates or updates the information of the GNBCUCPFunction IOC and IABNodeCell IOC. Other existing information of the GNBCUCPFunction IOC can be described in the existing 3GPP TS 28.541, which will not be repeated in this application. For example, the information of GNBCUCPFunction is shown in Table 6 below. The information of the IABNodeCell is shown in Table 7 below.

[0136] Table 6

[0137] Property Name Name Meaning ikB Base station identification gNBIdLength Base station identification length gNBCUName Name of the base station CU pL Public land mobile network logo nCIListIABNode IAB Node Candidate NCI List IABNodeIndication Instructions for IAB Nodes

[0138] Table 7

[0139] Property Name Name Meaning cellLocalId Cell local identifier cellState Cell Status pLMNInfoList Public Land Mobile Network Information List nPNIdentityList Private network identifier list nR PCI Physical cell identification nRTAC Tracking area code arfcnDL Downlink frequency number arfcn Uplink frequency number

[0140] It should also be noted that the above Tables 2 to 7 are only exemplary. In actual application, each IOC may also include other attribute names, which are not specifically illustrated in this application. In addition, RAN-Domain-MnF can obtain the NCI list of the IAB node by creating or updating the IOC information. That is, in this embodiment, Figure 5 In the example of obtaining the NCI list of the IAB node by using the first model, of course, in actual application, the second model can also be used to obtain the NCI list of the IAB node. This is only an exemplary description and is not specifically limited.

[0141] Step 503: RAN-Domain-MnF sends the NCI list of IAB nodes to CU.

[0142] Optionally, in step 503, the RAN-Domain-MnF also sends the gNBDU identifier to the IAB donor CU.

[0143] It should be noted that this step can be achieved through products without the need for standardization.

[0144] Step 504: The CU selects an NCI for the IAB node it supports from the NCI list of the IAB nodes.

[0145] For example, the CU selects different NCIs, that is, non-conflicting NCIs, for the IAB node1 and IAB node2 that it supports.

[0146] It should be noted that the current IABnode may already have a preset NCI, and the CU reselects an NCI for the IABnode from the NCI list and configures it as the IABnode.

[0147] Step 505: CU sends the NCI of IABnode to IABnode.

[0148] For example, Figure 5 In the figure, it is schematically illustrated that CU sends the NCI of IAB node1 to IAB node1 and sends the NCI of IAB node2 to IABnode2.

[0149] It should be noted that the CU may send the NCI to the IAB node through an existing F1 interface message, or may also send the NCI through other new messages, which is not limited in the present application.

[0150] Step 506: The CU sends the NCI of the IAB node to the RAN-Domain-MnF.

[0151] For example, the CU sends the NCI of IAB node1 and the NCI of IAB node2 to the RAN-Domain-MnF.

[0152] It should be noted that, here it can also be understood that the CU sends the reconfigured NCI of the IABnode to the RAN-Domain-MnF.

[0153] Step 507: RAN-Domain-MnF sends the NCI of the IAB node to the NMS.

[0154] For example, RAN-Domain-MnF sends the NCI of IAB node1 and the NCI of IAB node2 to the NMS.

[0155] It should be noted that the RAN-Domain-MnF also needs to send the identification information of the CU corresponding to the IABnode to the NMS, so that the NMS can identify which CU node the IABnode is under.

[0156] Specifically, the NCI of IAB node1 includes cellLocalId and gNBDUId. In the case where there are multiple IABnode information, it can be sent in the form of a list or independently, which is not limited in this application.

[0157] When executing step 507, an existing notification operation may be performed, such as a change notification (NotificationnotifyMOIChanges) operation, that is, the NMS may be informed through a notification operation that the NCI (cellLocalID or gNBID) in the IOC model of its gNBDUFunction or NRCellDU or IABNodeCell has been updated. Alternatively, a newly defined operation may be performed, such as updating nCIListIABNode in Table 2 to notify the NMS, which is not limited in this application.

[0158] Case 2: RAN-Domain-MnF selects the NCI of the IAB node and sends the selected NCI to the NMS for reference. Figure 7 Execute as follows:

[0159] Step 701: The NMS determines the NCI list of the IAB node.

[0160] Specifically, the NMS determines the NCI list of the IAB node of the CU. Figure 4 The NCI list can be understood through the introduction, which is not repeated here.

[0161] For example, in a scenario with multiple CUs, the NMS needs to determine the NCI list of IAB nodes corresponding to the multiple CUs.

[0162] Step 702: The NMS sends the NCI list of IAB nodes to the RAN-Domain-MnF.

[0163] Optionally, the NMS may also send indication information of the IAB node, where the indication information is used to indicate that the NCI list is used to configure the IAB node.

[0164] It should be noted that the NMS also needs to send the identification information of the CU or the identification information of the base station to the RAN-Domain-MnF so that the RAN-Domain-MnF can identify which CU or base station the NCI list belongs to.

[0165] It should also be noted that the CU here can be called gNB-CU or IAB-donor-CU, and the present invention is not limited here.

[0166] Please refer to the above Figure 5 The step 502 in FIG. 1 is for reference only and will not be described in detail here. Figure 7 In the example of obtaining the NCI list of the IAB node by using the second model, of course, in actual application, the first model can also be used to obtain the NCI list of the IAB node. This is only an exemplary description and is not specifically limited.

[0167] Step 703: RAN-Domain-MnF selects the NCI of the IAB node from the NCI list of the IAB node.

[0168] For example, the RAN-Domain-MnF selects an NCI for the IABnode nodes supported by the CU managed by it, for example, different NCIs, that is, non-conflicting NCIs, are selected for the IAB node1 and IAB node2 under CU1.

[0169] It should be noted that the current IABnode may already have a preset NCI, and the RAN-Domain-MnF reselects an NCI for the IABnode from the NCI list and configures it as the IABnode.

[0170] Step 704: RAN-Domain-MnF sends the NCI of the IAB node to the CU.

[0171] For example, RAN-Domain-MnF sends the NCI of IABnode1 and the NCI of IABnode2 to CU.

[0172] Step 705: CU sends the NCI of IABnode to IABnode.

[0173] For example, the CU sends the NCI of IAB node1 to IAB node1, and sends the NCI of IAB node2 to IAB node2.

[0174] It should be noted that the CU may send the NCI to the IAB node through an existing F1 interface message, or may also send the NCI through other new messages, which is not limited in the present application.

[0175] Step 706: RAN-Domain-MnF sends the NCI of the IAB node to the NMS.

[0176] In actual application, the execution timing of step 706 and step 704 is not specifically limited. Step 706 can be executed before step 704 or simultaneously with step 704, which is not specifically limited here.

[0177] For example, the RAN-Domain-MnF sends the NCI of the IAB node1 of CU1 and the NCI of the IAB node2 to the RAN-Domain-MnF.

[0178] It should be noted that, here it can also be understood that the RAN-Domain-MnF sends the reconfigured NCI of the IABnode to the NMS.

[0179] It should also be noted that the RAN-Domain-MnF also needs to send the identification information of the CU corresponding to the IABnode to the NMS, so that the NMS can identify which CU node the IABnode belongs to.

[0180] When executing step 706, an existing notification operation may be performed, such as by changing the NotificationnotifyMOIChanges operation, that is, by notifying the NMS that the NCI (cellLocalID or gNBID) in the IOC model of its gNBDUFunction or NRCellDU or IABNodeCell has been updated. Alternatively, a newly defined operation may be performed, such as by updating nCIListIABNode in Table 2 to notify the NMS, which is not limited in this application.

[0181] Case 3: NMS selects the NCI of the IAB node

[0182] See also Figure 8 Execute as follows:

[0183] Step 801: The NMS determines the NCI of the IABnode of the CU.

[0184] For example, the NMS determines the NCI of the IAB node1 of CU1 and the NCI of the IAB node2.

[0185] Step 802: The NMS sends the NCI of the IAB node to the RAN-Domain-MnF.

[0186] For example, the NMS sends the NCI of the IAB node 1 and the NCI of the IAB node 2 to the RAN-Domain-MnF.

[0187] It should be noted that the NMS also needs to send the identification information of the CU or the identification information of the base station to the RAN-Domain-MnF so that the RAN-Domain-MnF can identify which CU or base station the NCI belongs to.

[0188] It should also be noted that the CU here can be called gNB-CU or IAB-donor-CU, and the present invention is not limited here.

[0189] Optionally, the NMS may also send indication information of the IAB node, where the indication information is used to indicate that the NCI is used to configure the IAB node.

[0190] Please refer to the above Figure 5However, in actual application, when the model is used for execution of step 802, there is no need to transmit the information of nCIListIABNode and IABNodeIndication, which is only illustrative and not specifically limited.

[0191] Step 803: RAN-Domain-MnF sends the NCI of the IAB node to the CU.

[0192] Step 804: The CU sends the NCI of the IAB node to the IAB node.

[0193] It should be noted that in an embodiment of the present application, the NMS and the CN-Domain-MnF may also transmit the NCI list of the IAB node or the NCI of the IAB node through the northbound interface, and the CN-Domain-MnF may send the NCI list of the IAB node or the NCI of the IAB node to the CU through the AMF or UPF.

[0194] Embodiment 2: After the interaction between the first device and the second device, the NCI of the IAB node is selected from the NCI information list of the IAB node, and the IAB node NCI is transmitted back to the second device through the third device

[0195] In actual application, the first device may also receive the NCI of the IAB node from the third device. The second device is a cross-domain management function unit, and NMS is used as an example here to illustrate; the first device is a domain management function unit, and the access network domain management function unit RAN-Domain-MnF is used as an example here to illustrate; the third device is a domain management function unit, and the core network domain management function unit CN-Domain-MnF is used as an example here to illustrate; the IAB host base station is illustrated by CU and IAB node. Of course, in actual application, the number of IAB nodes may be multiple, and this is only an example. Of course, in actual application, the number of IAB nodes may be multiple, and this is only an example, and the number of IAB nodes is not limited. In specific execution, the following three different situations are used as examples for illustration, as follows:

[0196] Situation 1: CU selects the NCI of the IAB node, CU sends the selected NCI to AMF, and AMF sends it to NMS via CN-Domain-MnF

[0197] See also Fig. 9 Execute as follows:

[0198] Step 901: The NMS determines the NCI list of the IAB node.

[0199] Specifically, the NMS determines the NCI list of the IAB node of the IAB donor CU. Figure 4 The NCI list can be understood by referring to the introduction of the NCI list, which will not be described in detail here. The specific understanding can be referred to step 501, which will not be described in detail here.

[0200] Step 902: The NMS sends the NCI list of IAB nodes to the RAN-Domain-MnF.

[0201] Optionally, the NMS may also send indication information of the IAB node, where the indication information is used to indicate that the NCI list is used to configure the IAB node.

[0202] It should be noted that the NMS also needs to send the identification information of the CU or the identification information of the base station to the RAN-Domain-MnF so that the RAN-Domain-MnF can identify which CU or base station the NCI list belongs to.

[0203] It should also be noted that the CU here can be called gNB-CU or IAB-donor-CU, and the present invention is not limited here.

[0204] Please refer to the above Figure 5 The step 502 in FIG. 1 is for reference only and will not be described in detail here.

[0205] Step 903: RAN-Domain-MnF sends the NCI list of IAB nodes to CU.

[0206] Step 904: The CU selects an NCI for the IAB node it supports from the NCI list of the IAB node.

[0207] For example, the CU selects different NCIs, that is, non-conflicting NCIs, for the IAB node1 and IAB node2 that it supports.

[0208] It should be noted that the current IABnode may already have a preset NCI, and the CU reselects an NCI for the IABnode from the NCI list and configures it as the IABnode.

[0209] Step 905: CU sends the NCI of IABnode to IABnode.

[0210] For example, the CU sends the NCI of IAB node1 to IAB node1, and sends the NCI of IAB node2 to IAB node2.

[0211] Step 906: CU sends the NCI of IABnode to AMF.

[0212] For example, CU1 sends the NCI of IAB node1 and the NCI of IAB node2 to AMF.

[0213] Specifically, it can be sent through an existing NG interface message, or through a newly defined message, which is not limited in this application.

[0214] It should be noted that the CU also needs to send the CU identifier or the base station identifier to the AMF so that the AMF can identify which CU the NCI of the IABnode belongs to.

[0215] Step 907: AMF sends the NCI of IABnode to CN-Domain-MnF.

[0216] For example, AMF sends the NCI of IABnode1 and the NCI of IAB node2 to CN-Domain-MnF.

[0217] The steps can be implemented through products, and the specific implementation method will not be described in detail in the present invention.

[0218] Step 908: CN-Domain-MnF sends the NCI of the IAB node to the NMS.

[0219] Specifically, the above step 908 can be implemented by adding the attribute of the IABnode information in the existing network management instance AMFFunction IOC.

[0220] It should be noted that the information of IABnode (IABnodeinformation attribute) includes the NCI (cellLocalId and / or gNBId) of IABnode, and optionally, may also include one or more of the gNB identifier (gNBId), DU identifier (gNBDUId), CU identifier (gNBCUId) and the like.

[0221] Exemplarily, the attributes in AMFFunction IOC are shown in Table 8 below. For other existing attributes in AMFFunction, reference may be made to the definition in TS28.541, which will not be described in detail in the present invention.

[0222] Table 8

[0223] Property Name Name Meaning pLMNInfoList Public Land Mobile Network Information List aMFIdentifier Access and mobility management function identifier iABnodeinformation IABnode Information

[0224] This method transmits the updated NCI of the IAB node to the cross-domain management functional unit through the core network node, reuses the transmission architecture of the existing OAM service, and ensures the update of the NCI of the IAB node in the cross-domain management functional unit.

[0225] Case 2: CU selects the NCI of the IAB node, the IAB node sends the selected NCI to UPF, and UPF sends it to NMS via CN-Domain-MnF

[0226] See also Fig.10 Execute as follows:

[0227] Step 1001: The NMS determines the NCI list of the IAB node.

[0228] Specifically, the NMS determines the NCI list of the IAB node of the IAB donor CU. Figure 4 The NCI list can be understood by referring to the introduction of the NCI list, which will not be described in detail here. The specific understanding can be referred to step 501, which will not be described in detail here.

[0229] Step 1002: The NMS sends the NCI list of IAB nodes to the RAN-Domain-MnF.

[0230] Optionally, the NMS may also send indication information of the IAB node, where the indication information is used to indicate that the NCI list is used to configure the IAB node.

[0231] It should be noted that the NMS also needs to send the identification information of the CU or the identification information of the base station to the RAN-Domain-MnF so that the RAN-Domain-MnF can identify which CU or base station the NCI list belongs to.

[0232] It should also be noted that the CU here can be called gNB-CU or IAB-donor-CU, and the present invention is not limited here.

[0233] Please refer to the above Figure 5 The step 502 in FIG. 1 is used for understanding and will not be described in detail here.

[0234] Step 1003: RAN-Domain-MnF sends the NCI list of IAB nodes to CU.

[0235] Step 1004: The CU selects an NCI for the IAB node it supports from the NCI list of the IAB nodes.

[0236] For example, the CU selects different NCIs, that is, non-conflicting NCIs, for the IAB node1 and IAB node2 that it supports.

[0237] It should be noted that the current IABnode may already have a preset NCI, and the CU reselects an NCI for the IABnode from the NCI list and configures it as the IABnode.

[0238] Step 1005, CU sends the NCI of IABnode to IABnode.

[0239] For example, CU sends the NCI of IAB node1 to IAB node1 and sends the NCI of IAB node2 to IAB node2.

[0240] Step 1006: IABnode sends the NCI of IABnode to UPF.

[0241] For example, CU1 sends the NCI of IAB node1 and the NCI of IAB node2 to UPF.

[0242] It should be noted that the CU can transfer the NCI to the UPF through the existing PDU session transmission method.

[0243] It should be noted that the CU also needs to send the CU identifier or the base station identifier to the UPF so that the UPF can identify which CU the NCI of the IABnode belongs to.

[0244] Step 1007: UPF sends the NCI of IABnode to CN-Domain-MnF.

[0245] For example, UPF sends the NCI of IABnode1 and the NCI of IAB node2 to CN-Domain-MnF. Specifically, the information may be packaged as data and sent through the data plane channel of the existing PDU session.

[0246] Step 1008: CN-Domain-MnF sends the NCI of the IAB node to the NMS.

[0247] Specifically, the above step 1008 can be implemented by adding the NCI attribute of IABnode in the existing network management instance UPFFunction.

[0248] It should be noted that the information of IABnode (IABnodeinformation attribute) includes the NCI (cellLocalId and / or gNBId) of IABnode, and optionally, may also include one or more of the gNB identifier (gNBId), DU identifier (gNBDUId), CU identifier (gNBCUId) and the like.

[0249] Exemplarily, UPFFunction is as shown in Table 9 below. For other existing attributes in UPFFunction, reference may be made to the definition in TS28.541, which will not be repeated in the present invention.

[0250] Table 9

[0251] Property Name Name Meaning pLMNInfoList Public Land Mobile Network Information List nRTAClist List of NR tracking area codes iABnodeinformation IABnode Information

[0252] This method transmits the updated NCI of the IAB node to the cross-domain management functional unit through the core network node, reuses the transmission architecture of the existing OAM service, and ensures the update of the NCI of the IAB node in the cross-domain management functional unit.

[0253] Case 3: The IAB node selects the NCI of the IAB node, and the IAB node sends the selected NCI to the UPF, which then sends it to the NMS via the CN-Domain-MnF.

[0254] See also Fig.11 Execute as follows:

[0255] Step 1101: The NMS determines the NCI list of the IAB node.

[0256] Specifically, the NMS determines the NCI list of the IAB node of the IAB donor CU. Figure 4 The NCI list can be understood by referring to the introduction of the NCI list, which will not be described in detail here. The specific understanding can be referred to step 501, which will not be described in detail here.

[0257] Step 1102: The NMS sends the NCI list of IAB nodes to the RAN-Domain-MnF.

[0258] Optionally, the NMS may also send indication information of the IAB node, where the indication information is used to indicate that the NCI list is used to configure the IAB node.

[0259] It should be noted that the NMS also needs to send the identification information of the CU or the identification information of the base station to the RAN-Domain-MnF so that the RAN-Domain-MnF can identify which CU or base station the NCI list belongs to.

[0260] It should also be noted that the CU here can be called gNB-CU or IAB-donor-CU, and the present invention is not limited here.

[0261] Please refer to the above Figure 5 The step 502 in FIG. 1 is used for understanding and will not be described in detail here.

[0262] Step 1103: RAN-Domain-MnF sends the NCI list of IAB nodes to CU.

[0263] Step 1104: The CU sends the NCI list of the IAB nodes to the IAB nodes it supports.

[0264] For example, CU1 sends the NCI list of IAB nodes to IAB node1 and IAB node2 respectively.

[0265] Step 1105: The IAB node selects the NCI of the IAB node from the NCI list of the IAB nodes.

[0266] For example, IAB node1 selects the NCI of IAB node1 from the NCI list of IAB nodes, and IAB node2 selects the NCI of IAB node2 from the NCI list of IAB nodes.

[0267] Step 1106: The IAB node sends the NCI of the IAB node to the UPF.

[0268] For example, IAB node1 sends the NCI of IAB node1 to UPF, and IAB node2 sends the NCI of IAB node2 to UPF.

[0269] Step 1107: UPF sends the NCI of the IAB node to the CN-Domain-MnF.

[0270] For example, UPF sends the NCI of IABnode1 and the NCI of IAB node2 to CN-Domain-MnF. Specifically, the information may be packaged as data and sent through the data plane channel of the existing PDU session.

[0271] Step 1108: CN-Domain-MnF sends the NCI of the IAB node to the NMS. This can be understood by referring to the description of the above step 1108, which will not be repeated here.

[0272] This method transmits the updated NCI of the IAB node to the cross-domain management functional unit through the core network node, reuses the transmission architecture of the existing OAM service, and ensures the update of the NCI of the IAB node in the cross-domain management functional unit.

[0273] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of device interaction. It is understandable that, in order to implement the above functions, each device may include a hardware structure and / or software module corresponding to each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.

[0274] The embodiment of the present application can divide the functional units of the device according to the above method example, for example, each functional unit can be divided according to each function, or two or more functions can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0275] In the case of an integrated unit, Fig.12 FIG. 1 shows a possible exemplary block diagram of a communication device involved in an embodiment of the present application. Fig.12 As shown, the communication device 1200 may include: a processing unit 1201 and a transceiver unit 1202. The processing unit 1201 is used to control and manage the actions of the communication device 1200. The transceiver unit 1202 is used to support the communication between the communication device 1200 and other devices. Optionally, the transceiver unit 1202 may include a receiving unit and / or a sending unit, which are respectively used to perform receiving and sending operations. Optionally, the communication device 1200 may also include a storage unit for storing program code and / or data of the communication device 1200. The transceiver unit may be called an input-output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor. When the communication device is a module (such as a chip) in a communication device, the transceiver unit may be an input-output interface, an input-output circuit or an input-output pin, etc., and may also be called an interface, a communication interface or an interface circuit, etc.; the processing unit may be a processor, a processing circuit or a logic circuit, etc. Specifically, the device may be the above-mentioned first device, second device, and third device, etc.

[0276] In one embodiment, the communication device 1200 is a first device, and its transceiver unit 1202 is used to receive the NCI list of the IAB node from the second device; the processing unit 1201 is used to determine the NCI of the IAB node according to the NCI list; the transceiver unit 1202 is also used to send the NCI of the IAB node to the second device.

[0277] Specifically, the processing unit 1201 may select the NCI of the IAB node from the NCI list.

[0278] Specifically, the transceiver unit 1202 may send the NCI list to the IAB donor base station; and receive the NCI of the IAB node from the IAB donor base station.

[0279] In actual application, the communication device may be a domain management functional unit, and the second device may be a cross-domain management functional unit; wherein the domain management functional unit may be an access network domain management functional unit or a core network domain management functional unit.

[0280] It should be noted that the first device is a core network domain management functional unit, and the transceiver unit 1202 can also receive the NCI of the IAB node sent from the IAB host base station through the AMF; or, receive the NCI of the IAB node sent from the IAB node through the UPF.

[0281] In one embodiment, the communication apparatus 1200 is a second device, wherein the processing unit 1201 is configured to determine a cell identifier NCI list of an IAB node; and the transceiver unit is configured to send the NCI list of the IAB node and receive the NCI of the IAB node.

[0282] Specifically, the processing unit 1201 is used to send the NCI list information of the IAB node to the first device; receive the NCI of the IAB node from the first device; wherein the first device is an access network domain management function unit or a core network domain management function unit, and the communication device is a cross-domain management function unit.

[0283] Specifically, the processing unit 1201 is used to send the NCI list information of the IAB node to the first device; receive the NCI of the IAB node from the third device; wherein the first device is an access domain management function unit, the communication device is a cross-domain management function unit, and the third device is a core domain management function unit.

[0284] like Fig.13 As shown, a communication device 1300 is also provided in the present application. The communication device 1300 may be a chip or a chip system. The communication device may be located in a device involved in any of the above method embodiments, such as a first device or a second device, to perform actions corresponding to the device.

[0285] Optionally, the chip system may consist of the chip, or may include the chip and other discrete devices.

[0286] The communication device 1300 includes a processor 1310 .

[0287] The processor 1310 is used to execute the computer program stored in the memory 1320 to implement the actions of each device in any of the above method embodiments.

[0288] The communication device 1300 may further include a memory 1320 for storing computer programs.

[0289] Optionally, the memory 1320 is coupled to the processor 1310. Coupling is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, for information exchange between devices, units or modules. Optionally, the memory 1320 is integrated with the processor 1310.

[0290] The processor 1310 and the memory 1320 may be one or more and are not limited.

[0291] Optionally, in practical applications, the communication device 1300 may include a transceiver 1330 or may not include the transceiver 1330, which is illustrated by a dotted box in the figure. The communication device 1300 may exchange information with other devices through the transceiver 1330. The transceiver 1330 may be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.

[0292] In a possible implementation, the communication device 1300 may be an access network device or a first core network device in the implementation of the above methods.

[0293] The specific connection medium between the transceiver 1330, the processor 1310 and the memory 1320 is not limited in the embodiment of the present application. Fig.13 The memory 1320, the processor 1310 and the transceiver 1330 are connected via a bus. Fig.13 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.13 Only one thick line is used to represent it, but it does not mean that there is only one bus or one type of bus. In the embodiment of the present application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor.

[0294] In the embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM). The memory may also be any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the embodiment of the present application may also be a circuit or any other device that can implement a storage function, for storing computer programs, program instructions and / or data.

[0295] Based on the above embodiments, see Fig.14 The embodiment of the present application also provides another communication device 1400, including: an interface circuit 1410 and a logic circuit 1420; the interface circuit 1410 can be understood as an input and output interface, which can be used to execute the sending and receiving steps of each device in any of the above method embodiments, and the logic circuit 1420 can be used to run codes or instructions to execute the method executed by each device in any of the above embodiments, which will not be repeated.

[0296] Based on the above embodiments, the embodiments of the present application further provide a computer-readable storage medium, which stores instructions. When the instructions are executed, the method executed by each device in any of the above method embodiments is implemented, for example, Figure 4 In the illustrated embodiment, the method executed by the first device or the second device is implemented. The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media that can store program codes.

[0297] Based on the above embodiments, an embodiment of the present application provides a communication system, which includes a first device (e.g., RAN-Domain-MnF) and a second device (e.g., NMS) mentioned in any of the above method embodiments, and can be used to execute the method executed by each device in any of the above method embodiments.

[0298] In addition, the above-mentioned communication system may also include a terminal (such as UE), which can execute the relevant method in any of the above-mentioned method embodiments by interacting with the access network device and the core network device.

[0299] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, compact disc read-only memory (CD-ROM), optical storage, etc.) containing computer-usable program codes.

[0300] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0301] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0302] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

Claims

1. A communication method, characterized in that: include: The first device receives a cell identifier NCI list of the first access and backhaul integrated IAB node from the second device; The first device determines the NCI of the IAB node according to the NCI list; The first device sends the NCI of the IAB node to the second device.

2. The method according to claim 1, characterized in that The first device determines the NCI of the IAB node according to the NCI list, including: The first device selects the NCI of the IAB node from the NCI list.

3. The method according to claim 1, characterized in that: The first device determines the NCI of the IAB node according to the NCI list, including: The first device sends the NCI list to the IAB host base station; The first device receives the NCI of the IAB node from the IAB donor base station.

4. The method according to any one of claims 1 to 3, characterized in that: The first device is a domain management functional unit, and the second device is a cross-domain management functional unit; wherein the domain management functional unit is an access network domain management functional unit or a core network domain management functional unit.

5. The method according to claim 3, characterized in that: The first device is a core network domain management function unit, and the first device receives the NCI of the IAB node from the IAB host base station, including: The first device receives the NCI of the IAB node sent by the IAB host base station through the access and mobility management function AMF; or, The first device receives the NCI of the IAB node sent by the IAB node through a user plane function UPF.

6. A communication method, characterized in that: include: The second device determines a cell identifier NCI list of the access backhaul integrated IAB node; The second device sends the NCI list of the IAB node; The second device receives the NCI of the IAB node.

7. The method according to claim 6, characterized in that The second device sends the NCI list of the IAB node, including: The second device sends the NCI list information of the IAB node to the first device; The second device receiving the NCI of the IAB node includes: The second device receives the NCI of the IAB node from the first device; Among them, the first device is an access domain management functional unit or a core domain management functional unit, and the second device is a cross-domain management functional unit.

8. The method according to claim 6, characterized in that The second device sends the NCI list of the IAB node, including: The second device sends the NCI list information of the IAB node to the first device; The second device receiving the NCI of the IAB node includes: The second device receives the NCI of the IAB node from a third device; Among them, the first device is an access domain management functional unit, the second device is a cross-domain management functional unit, and the third device is a core domain management functional unit.

9. A communication method, characterized in that: include: The second device determines a cell identifier NCI list of the access backhaul integrated IAB node; The second device sends the NCI list of the IAB nodes to the first device; The first device determines the NCI of the IAB node according to the NCI list; The first device sends the NCI of the IAB node to the second device.

10. The method according to claim 9, characterized in that The first device determines the NCI of the IAB node according to the NCI list, including: The first device selects the NCI of the IAB node from the NCI list.

11. The method according to claim 9, characterized in that The first device determines the NCI of the IAB node according to the NCI list, including: The first device sends the NCI list to the IAB host base station; The IAB host base station selects the NCI of the IAB node from the NCI list; The IAB donor base station sends the NCI of the IAB node to the first device.

12. The method according to any one of claims 9 to 11, characterized in that: The first device is a domain management functional unit, and the second device is a cross-domain management functional unit; wherein the domain management functional unit is an access network domain management functional unit or a core network domain management functional unit.

13. The method according to claim 11, characterized in that The first device is a core network domain management function unit, and the IAB host base station sends the NCI of the IAB node to the first device, including: The IAB host base station sends the NCI of the IAB node to the access and mobility management function AMF; The AMF sends the NCI of the IAB node to the first device.

14. The method according to claim 11, characterized in that The first device is a core network domain management function unit, and the IAB host base station sends the NCI of the IAB node to the first device, including: The IAB host base station sends the NCI of the IAB node to the IAB node; The IAB node sends the NCI of the IAB node to a user plane function UPF; The UPF sends the NCI of the IAB node to the first device.

15. A communication method, characterized in that: include: The second device determines a cell identifier NCI list of the access backhaul integrated IAB node; The second device sends the NCI list of the IAB nodes to the first device; The first device determines the NCI of the IAB node according to the NCI list; The third device sends the NCI of the IAB node to the second device.

16. The method according to claim 15, characterized in that The first device is an access network domain management functional unit, the second device is a cross-domain management functional unit, and the third device is a core network domain management functional unit.

17. The method according to claim 15 or 16, characterized in that The first device determines the NCI of the IAB node according to the NCI list, including: The first device selects the NCI of the IAB node from the NCI list.

18. The method according to claim 17, characterized in that The first device determines the NCI of the IAB node according to the NCI list, including: The first device sends the NCI list to the IAB host base station; The IAB host base station selects the NCI of the IAB node from the NCI list; The IAB donor base station sends the NCI of the IAB node to the first device.

19. The method according to claim 16, characterized in that Before the third device sends the NCI of the IAB node to the second device, the method further includes: The IAB host base station sends the NCI of the IAB node to the access and mobility management function AMF; The AMF sends the NCI of the IAB node to the third device.

20. The method according to claim 11, characterized in that Before the third device sends the NCI of the IAB node to the second device, the method further includes: The IAB host base station sends the NCI of the IAB node to the IAB node; The IAB node sends the NCI of the IAB node to a user plane function UPF; The UPF sends the NCI of the IAB node to the third device.

21. The method according to any one of claims 1 to 20, characterized in that: The NCI includes: a base station identifier and a cell identifier.

22. A communication device, characterized in that: include: A functional module for implementing the method according to any one of claims 1 to 21.

23. A communication device, characterized in that: include: at least one processor; The processor is coupled to a memory; The at least one processor is configured to execute a computer program or instruction so that the method according to any one of claims 1 to 21 is performed.

24. The communication device according to claim 23, characterized in that Also comprising at least one memory; The memory is used to store the computer program or instruction.

25. A chip system, characterized in that: The chip system comprises: a processing circuit; the processing circuit is coupled to a storage medium; The processing circuit is used to execute part or all of the computer programs or instructions in the storage medium, and when the part or all of the computer programs or instructions are executed, it is used to implement the method according to any one of claims 1 to 21.

26. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed by a computer, the method according to any one of claims 1 to 21 is executed.

27. A computer program product comprising a computer program or instructions, characterized in that When it is run on a computer, the method described in any one of claims 1 to 21 is executed.

Images