Communication method and apparatus

Abstract

Embodiments of the present application relate to the technical field of communications, and provide a communication method and apparatus. A second device determines a new radio cell identifier (NCI) list of an integrated access and backhaul (IAB) node; the second device sends the NCI list of the IAB node to a first device; the first device determines an NCI of the IAB node on the basis of the NCI list; and the first device sends the NCI of the IAB node to the second device. The method reuses a network function management service architecture and provides a configuration transmission process for configuring the cell identifier of the IAB node. According to the method, the problem of the NCI conflict caused by the mobility of the IAB node can be avoided, accurate transmission of an IAB node service is ensured, and the user experience can be improved.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on August 11, 2023, with application number 202311019597.X and application name “A Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0004] To reduce fiber deployment and lower deployment costs, the fifth-generation (5G) mobile communication system introduced integrated access and backhaul (IAB) network technology. An IAB node consists of a mobile termination (MT) and a distributed unit (DU). When facing its parent node, an IAB node acts as a user device (MT). When facing its child nodes (which can be another IAB node or regular user equipment (UE)), it acts as a network device providing backhaul services to the child nodes, acting as a DU.

[0005] IAB nodes (IAB-MTs) can obtain OAM services from operation, administration, and maintenance (OAM) entities through protocol data unit (PDU) sessions with core network entities. IAB nodes can also obtain OAM services directly from OAM entities through Internet Protocol (IP) backhaul links. To ensure accurate transmission of OAM services and a good user experience, cell identifiers can be configured for different IAB nodes. However, the specific methods for configuring cell identifiers for IAB nodes and how to report cell identifiers to OAM have not yet been determined.

[0006] Summary of the Invention

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

[0008] 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 (NMS), management service producer (MnS Producer), management service consumer (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 an element management system (EMS), a mobile broadband automation engine (MAE), an MnS Producer, an MnS Consumer, an access network domain management function unit (RAN-Domain-MnF), a core network domain management function unit (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 network element, etc.), and the second device can also be a domain management network element. Of course, in actual applications, other devices may also be involved in the interaction, which is not specifically limited here. Execution is as follows:

[0009] The second device determines a new radio cell identifier (NCI) list of the IAB node, and 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 sends the NCI of the IAB node to the second device.

[0010] 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.

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

[0012] This approach can avoid NCI collision caused by IAB node movement and subsequent F1 interface establishment failure by the first device selecting the IAB node's NCI from the NCI list, thereby ensuring accurate transmission of IAB node services and improving user experience.

[0013] 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.

[0014] This method can avoid the NCI collision caused by IAB node movement and the subsequent failure of F1 interface establishment by selecting the NCI of the IAB node from the NCI list through the IAB host base station, thereby ensuring the accurate transmission of IAB node services and improving user experience.

[0015] 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.

[0016] 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 the 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 the user plane function (UPF); the UPF sends the NCI of the IAB node to the first device.

[0017] This method transmits the updated NCI of the IAB node to the cross-domain management functional unit through the IAB host base station via 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.

[0018] On 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:

[0019] The second device determines an NCI list of the IAB node, 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.

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

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

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

[0023] 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.

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

[0025] 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 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 of the above-mentioned first to second aspects. For example, the communication device includes a module or unit or means corresponding to the steps involved in any of the above-mentioned first to second aspects. The function or unit or means may be implemented by software, or by hardware, or the corresponding software implementation may be executed by hardware.

[0026] 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 achieve 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.

[0027] 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 to second aspects above. 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 of the first to second aspects above. 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 above.

[0028] In another possible design, the communication device includes a processor, which can be coupled to a memory. The memory can store the necessary computer programs or instructions for implementing the functions of any of the first and second aspects. The processor can execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the communication device implements the method of any possible design or implementation of the first and second aspects.

[0029] 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.

[0030] 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 and the processor can be set separately. 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.

[0031] 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 to second aspects.

[0032] 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 aspects 1 to 5. The chip system can be composed of a chip or can include a chip and other discrete devices.

[0033] 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 run on a computer, the computer executes a method in any possible design of the first aspect to the second aspect.

[0034] 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 above.

[0035] 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

[0036] FIG1 shows a schematic diagram of an IAB networking scenario;

[0037] FIG2 shows a schematic diagram of an IAB network architecture;

[0038] FIG3 shows a schematic diagram of a service-oriented management architecture applicable to an embodiment of the present application;

[0039] FIG4 shows a schematic flow chart of a communication method;

[0040] FIG5 shows a schematic flow chart of an NCl configuration method for an IAB node;

[0041] FIG6A shows a schematic diagram of a model of a DU and a DU cell;

[0042] FIG6B shows a schematic diagram of a model of a DU and IAB node cell;

[0043] FIG7 shows a schematic flow chart of a method for configuring NCl of an IAB node;

[0044] FIG8 shows a schematic flow chart of an NCl configuration method for an IAB node;

[0045] FIG9 shows a schematic flow chart of a method for configuring NCl of an IAB node;

[0046] FIG10 shows a schematic flow chart of a method for configuring NCI of an IAB node;

[0047] FIG11 shows a schematic flow chart of a method for configuring NCl of an IAB node;

[0048] FIG12 shows a schematic structural diagram of a communication device;

[0049] FIG13 shows a schematic structural diagram of a communication device;

[0050] FIG14 shows a schematic structural diagram of a communication device. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solutions and advantages of this application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The specific operating methods in the method embodiments can also be applied to the device embodiments or system embodiments. In the description of this application, unless otherwise specified, "multiple" means two or more. Therefore, the implementation of the device and method can refer to each other, and the repeated parts will not be repeated.

[0052] 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.

[0053] It should be understood that 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 time or random access fails or 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 cached data to be transmitted by a certain IAB node on a certain link exceeding a certain threshold.

[0054] An IAB node can include both an MT and a DU. When the IAB node faces its parent node, it can be considered a terminal device accessing the parent node, acting as an MT. When the IAB node faces its child node, it can be considered a network device providing backhaul services to the child node, acting as a DU. The child node can be another IAB node or a terminal device.

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

[0056] In the embodiments of the present application, an access IAB node refers to the IAB node accessed by a terminal device, i.e., the IAB node that provides services to the terminal device. During IAB uplink transmission, the access IAB node transmits the uplink data packet sent by the terminal device to the target donor DU via one or more other IAB nodes. The target donor DU then transmits the uplink data packet to the corresponding donor CU-UP. During IAB downlink transmission, 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. The downlink data packet is then transmitted to the access IAB node corresponding to the terminal device via one or more other IAB nodes or via a direct backhaul link. The access IAB node then transmits the received downlink data packet to the terminal device. If the data packet is sent to a specific IAB node, the donor CU-UP transmits the downlink data packet sent to the IAB node to the corresponding donor DU. The downlink data packet is then transmitted to the parent node of the IAB node via one or more other IAB nodes or via a direct backhaul link. The parent node of the IAB node then transmits the received downlink data packet to the specific IAB node.

[0057] It should be understood that during IAB downlink transmission, if the node at which the data packet ultimately arrives (hereinafter referred to as the terminating node) is a terminal device, the target node is the access IAB node corresponding to the terminal device. If the terminating node is an IAB node, the target node is the parent node of the IAB node. During IAB uplink transmission, the terminating node is the donor CU-UP, and the target node is the donor DU corresponding to the donor CU-UP. The target node can also be referred to as the target receiving node.

[0058] Figure 1 shows a schematic diagram of an IAB networking scenario. IAB node 1's parent node is the IAB donor, which is in turn the parent node of IAB node 2 and IAB node 3. Both IAB node 2 and IAB node 3 are the parent nodes of IAB node 4, and IAB node 5's parent node is IAB node 2. Uplink data packets sent by UE1 can be transmitted via one or more IAB nodes to the IAB donor, which then sends them to a mobile gateway device (e.g., the user plane functional unit in the 5G core network). Downlink data packets are received by the IAB donor from the mobile gateway device and then sent to UE1 via one or more IAB nodes. The same applies to UE2.

[0059] There are two available paths for data packet transmission between UE1 and the IAB donor: Path 1: UE1 → IAB node 4 → IAB node 3 → IAB node 1 → IAB donor; Path 2: UE1 → IAB node 4 → IAB node 2 → IAB node 1 → IAB donor.

[0060] 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. IAB donor is the target node.

[0061] There are three available paths for data transmission between UE2 and the IAB donor. Path 3: UE2 → IAB node 4 → IAB node 3 → IAB node 1 → IAB donor; Path 4: UE2 → IAB node 4 → IAB node 2 → IAB node 1 → IAB donor; and Path 5: UE2 → IAB node 5 → IAB node 2 → IAB node 1 → IAB donor.

[0062] In path 3, IAB node 4 is UE1's access IAB node, and IAB node 3 and IAB node 1 are intermediate IAB nodes. In path 4, IAB node 4 is UE1's access IAB node, and IAB node 2 and IAB node 1 are intermediate IAB nodes. In path 5, IAB node 5 is UE1's access IAB node, and IAB node 2 and IAB node 1 are intermediate IAB nodes. The IAB donor is the target node.

[0063] It should be understood that the IAB networking scenario shown in FIG1 is merely exemplary, and 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.

[0064] Figure 2 shows a schematic diagram of an IAB network architecture, including both standalone (SA) and non-standalone (NSA) IAB networks. Figure 2 uses IAB node 1 and IAB node 2 as examples. IAB donors can be further divided into DUs and CUs, and CUs can be further divided into CU-CPs and CU-UPs. Figure 2 uses IAB donor 1 and IAB donor 2 as examples.

[0065] Each IAB node's DU has an F1 interface with the IAB donor CU. This F1 interface consists of 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 not shown in Figure 2. The UE connects to the IAB node's DU via the NR Uu interface, while the MT in each IAB node connects to the DU via the NR BH interface. The IAB donor CU-CP connects to the IAB donor CU-UP via the E1 interface.

[0066] When the IAB node operates in SA mode, it can be connected to a single parent node or dually to 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, which can be connected to the 5G core network (5G core, 5GC), which is the dotted line part in the figure. The IAB-donor-CU-CP is connected to the control plane network elements (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 elements (such as the user plane function UPF) in the 5GC through the NG user plane interface (NG-U).

[0067] When the IAB node operates in NSA mode (or EN-DC mode), the IAB-donor-CU-UP can be connected to the EPC (for example, 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, and an X2 / Xn-C interface between the MeNB and the IAB-donor-CU-CP. 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 and the EPC are connected through the S1 interface user plane (S1-U).

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

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

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

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

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

[0073] Business support systems (BSSs) are oriented towards communications services and provide functions and management services such as billing, settlement, accounting, customer service, sales, network monitoring, communications service lifecycle management, and business intent translation. BSSs can be either carrier operations systems or vertical industry operations systems (OT systems).

[0074] The cross-domain management function unit, also called the network management function unit (NMF), can be a network management entity such as a network management system (NMS) or a network function management service consumer (NFMS_C). 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, and translation of service producer's network intent (intent from communication service provider, Intent-CSP).

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

[0076] Optionally, in certain 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 slicing sub-networks.

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

[0078] 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 of sub-networks or network elements, and translation of intents from network operators (Intent-NOPs) for sub-networks or network elements. A sub-network here includes one or more network elements. A sub-network may also include sub-networks, i.e., one or more sub-networks form a larger sub-network.

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

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

[0081] Based on network type, they can be divided into: radio access network domain management function (RAN-Domain-MnF), core network domain management function (CN-Domain-MnF), 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 that can manage one or more of the access network, core network, or transport network.

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

[0083] Network elements are entities that provide network services, including core network elements and access network elements. 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 function (NRF), and gateways. Access network elements include: base stations (such as gNBs and eNBs), central unit control plane (CUCP), central unit (CU), distributed unit (DU), and central unit user plane (CUUP).

[0084] NEs can provide one or more of the following management functions or services: NE lifecycle management, NE deployment, NE fault management, NE performance management, NE assurance, NE optimization, and NE intent translation. In practical applications, NEs can also provide services for IAB nodes and terminal devices.

[0085] The IAB-MT can obtain OAM services from the OAM entity through PDU sessions with core network entities. OAM services include receiving commands (such as operational messages related to FM, CM, and PM), configuration data, software downloads (e.g., for device software upgrades), alarms, and performance metrics. The transport connection between the IAB node and its OAM entity uses the IP protocol and is provided by the IAB-MT's PDU session over the 5G network, or, when the IAB-MT uses EN-DC, by the IAB-MT's PDN connection over the LTE network. The IAB node can also obtain OAM services from the OAM entity via an IP backhaul link. Within this IAB node architecture, the allocation of NCIs for IAB nodes is currently under discussion in the 3GPP standard. The IAB donor CU can allocate an NCI to the IAB node based on the NCI candidate list configured by the OAM for the IAB node. However, how to configure the IAB node's NCI and how to communicate this NCI to the OAM entity have not yet been discussed.

[0086] 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 IAB node's processing logic is that the IAB donor DU initiates the F1 establishment process with the CU, and exchanges NCI information. If the NCI of the IAB node conflicts with that of other IAB nodes under the current CU at this time, problems such as F1 establishment failure will occur.

[0087] In the related art, a 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 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 CU can be used to select the NCI to avoid NCI conflicts caused by IAB node mobility.

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

[0089] Candidate list of CelllocalID;

[0090] Candidate list of gNBID and celllocalID combinations (for mobile IABnodes).

[0091] 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.

[0092] 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 executing, the method can be executed through the interaction of 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, 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 4 takes the interaction between the first device and the second device as an example. Execution is as follows:

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

[0094] The above-mentioned second device 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.

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

[0096] Table 1

[0097] 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 example and will not be explained in detail here. Optionally, the candidate NCI list can also be a list composed 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. This is only an example and will not be explained in detail here.

[0098] 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, it sends the IAB node indication information 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 (i.e., the cross-domain management device) through the single-domain management device of the core network to indicate 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 to the instance of the UPF function (UPFFunction) object class, or the AMF node of the core network sends the indication information of IABnode to the NMS through the single-domain management device of the core network, that is, the indication information of IABnode needs to be added to the instance of the AMF function (AMFFunction) object class.

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

[0100] 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 IAB node indication information as being configured by the second device for the IAB node. This application does not specifically limit how to implement it.

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

[0102] Specifically, the first device may select the NCI of the IAB node from the candidate NCI list. For example, different NCIs may be selected from the candidate NCI list for the cells of IABnode1 and IABnode2 of CU1. This approach, in which the first device selects the NCI of the IAB node from the NCI list, can avoid NCI collisions caused by IAB node mobility and, consequently, F1 interface establishment failures. This ensures accurate transmission of IAB node services and improves the user experience.

[0103] 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 from 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. This application does not specifically limit how the first device determines the NCI of the IAB node.

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

[0105] 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-mentioned step 404 does not need to be performed.

[0106] 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.

[0107] To better illustrate the method of the present application, two specific embodiments are described below. In actual application, after interaction between the first device and the second device, an IAB node NCI can be selected from the IAB node NCI information list, and the IAB node NCI can be transmitted back to the second device via the first device. Alternatively, after interaction between the first device and the second device, an IAB node NCI can be selected from the IAB node NCI information list, and the IAB node NCI can be transmitted back to the second device via a third device. This application does not specifically limit the execution method, and the following embodiments 1 and 2 provide a detailed description.

[0108] Example 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.

[0109] Next, the second device is taken as the cross-domain management functional unit, and NMS is used as an example to illustrate. The first device is taken as the domain management functional unit, and the access network domain management functional unit RAN-Domain-MnF is used as an example to illustrate. The IAB host base station is taken as CU and IAB node as an example to illustrate. Of course, in actual application, 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 interface, or a northbound interface. The interface between RAN-Domain-MnF (or CN-Domain-MnF) and CU belongs to 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:

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

[0111] Refer to Figure 5 and execute as follows:

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

[0113] Specifically, the NMS determines the NCI list of the IAB node of the CU. The NCI list can be understood by referring to the introduction of FIG. 4 above, and will not be described in detail here.

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

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

[0116] Optionally, the NMS may further send indication information of the IAB node, where the indication information is used to indicate that the NCl list is used to configure the IAB node.

[0117] 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.

[0118] 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 IAB donor DU and the IAB node before the NMS can configure the information of the network node. In actual application, the NRM information model of the CU, IABnode, and IABnodecell 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 for the IABnodecell. This is not specifically limited in this application.

[0119] It should be noted that the CU can reuse the information model definition of the existing gNB-CU NRM, which can be referred to in 3GPP TS 28.541. This application will not go into details here.

[0120] 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.

[0121] The following is a brief introduction to the two different models mentioned above:

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

[0123] As shown in Figure 6A, 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 you can refer to 3GPP TS 28.541. This application does not limit the name definition. Figure 6A also shows that the ManagedElement IOC represents a communication device or entity in the communication network that provides support and / or services to users, and is used to communicate with the management entity through one or more management interfaces (directly or indirectly) to perform management control.

[0124] 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 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 the creation or update of the GNBDUFunction and NRDUCell, the RAN-Domain-MnF creates or updates the information of the GNBDUFunction and NRDUCell. For example, the information of GNBDUFunction is shown in Table 2 below. Other existing information of the GNBDUFunction IOC and the information in the NRDUCell IOC can be described in the existing 3GPP TS 28.541, which will not be repeated in this application. It should be noted that the IOC NRM model configuration information of the GNBDUFunction and NRDUCell can be sent simultaneously in one operation or in different operations, which is not limited in this application.

[0125] Table 2

[0126] 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, 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 the creation or update of 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, and this application will not repeat it here. For example, the information of the GNBCUCPFunction is shown in Table 3 below.

[0127] Table 3

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

[0129] As shown in Figure 6B, 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). Refer to the description of the ManagedElement IOC table in Figure 6A to understand the ManagedElement IOC in Figure 6B, which is not repeated here.

[0130] 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 GNBDUFunction IOC and IABNodeCell 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 the creation or update of the GNBDUFunction and IABNodeCell, the RAN-Domain-MnF creates or updates the information of the GNBDUFunction and IABNodeCell. For example, 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] Table 5

[0133] 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, 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 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, and will not be repeated here in this application. For example, the information of GNBCUCPFunction is shown in Table 6 below. The information of IABNodeCell is shown in Table 7 below.

[0134] Table 6

[0135] Table 7

[0136] It should also be noted that Tables 2-7 above are merely illustrative. In actual applications, each IOC may also include other attribute names, which are not specifically illustrated in this application. Furthermore, the RAN-Domain-MnF can obtain the NCI list of the IAB node by creating or updating IOC information. Specifically, in this embodiment, Figure 5 illustrates obtaining the NCI list of the IAB node using Model 1. In actual applications, Model 2 can also be used to obtain the NCI list of the IAB node. This is merely an illustrative example and does not constitute a limitation.

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

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

[0139] It should be noted that this step can be achieved through products and does not require standardization.

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

[0141] For example, the CU selects different NCIs, that is, non-conflicting NCIs, for the IAB node 1 and the IAB node 2 that it supports.

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

[0143] Step 505: The CU sends the NCI of the IAB node to the IAB node.

[0144] For example, FIG5 schematically illustrates that a CU sends the NCI of an IAB node 1 to the IAB node 1 and sends the NCI of an IAB node 2 to the IAB node 2.

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

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

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

[0148] 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.

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

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

[0151] 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.

[0152] Specifically, the NCI of IAB node 1 includes cellLocalId and gNBDUId. In the case where there are multiple IAB nodes, the NCI may be sent in a list or independently, which is not limited in this application.

[0153] When executing step 507, an existing notification operation, such as a change notification (Notification notifyMOIChanges), can be used to notify the NMS of the update of the NCI (cellLocalID or gNBID) in the IOC model of its gNBDUFunction, NRCellDU, or IABNodeCell. Alternatively, a newly defined operation, such as updating nCIListIABNode in Table 2, can be used to notify the NMS, which is not limited in this application.

[0154] Case 2: RAN-Domain-MnF selects the NCI of the IAB node and sends the selected NCI to the NMS

[0155] Refer to Figure 7 and execute as follows:

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

[0157] Specifically, the NMS determines the NCI list of the IAB node of the CU. The NCI list can be understood by referring to the introduction of FIG. 4 above, and will not be described in detail here.

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

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

[0160] Optionally, the NMS may further send indication information of the IAB node, where the indication information is used to indicate that the NCl list is used to configure the IAB node.

[0161] 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.

[0162] 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.

[0163] The above step 502 in FIG5 can be referred to for understanding, and will not be described in detail here. FIG7 uses the method of obtaining the NCI list of the IAB node using the second model as an example. Of course, in actual application, the method of the first model can also be used to obtain the NCI list of the IAB node. This is only an example and not a specific limitation.

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

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

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

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

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

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

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

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

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

[0173] 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.

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

[0175] 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.

[0176] 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.

[0177] When executing step 706, an existing notification operation, such as modifying the Notification notifyMOIChanges operation, can be used to notify the NMS of the update of the NCI (cellLocalID or gNBID) in the IOC model of its gNBDUFunction, NRCellDU, or IABNodeCell. Alternatively, a newly defined operation, such as updating nCIListIABNode in Table 2, can be used to notify the NMS, which is not limited in this application.

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

[0179] Refer to Figure 8 and execute as follows:

[0180] Step 801: The NMS determines the NCI of the IAB node of the CU.

[0181] For example, the NMS determines the NCI of the IAB node 1 and the NCI of the IAB node 2 of the CU 1 .

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

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

[0184] 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.

[0185] 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.

[0186] Optionally, the NMS may further 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.

[0187] This can be understood by referring to step 502 in FIG5 , and will not be described in detail here. However, in actual application, when step 802 is executed using a model, it is not necessary to transmit the information of nCIListIABNode and IABNodeIndication. This is only an example and not a limitation.

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

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

[0190] 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.

[0191] Example 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 returned to the second device through the third device

[0192] In actual application, the first device may also receive the NCI of the IAB node from the third device. The second device is 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 third device is the 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:

[0193] Case 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

[0194] Refer to Figure 9 and execute as follows:

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

[0196] Specifically, the NMS determines the NCI list of the IAB node of the IAB donor CU. The NCI list can be understood by referring to the introduction of FIG. 4 above, and will not be described in detail here. The details can be understood by referring to step 501, and will not be described in detail here.

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

[0198] Optionally, the NMS may further send indication information of the IAB node, where the indication information is used to indicate that the NCl list is used to configure the IAB node.

[0199] 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.

[0200] 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.

[0201] This can be understood by referring to step 502 in FIG. 5 , and will not be described in detail here.

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

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

[0204] For example, the CU selects different NCIs, that is, non-conflicting NCIs, for the IAB node 1 and the IAB node 2 that it supports.

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

[0206] Step 905: The CU sends the NCI of the IAB node to the IAB node.

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

[0208] Step 906: The CU sends the NCI of the IAB node to the AMF.

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

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

[0211] 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 IAB node belongs to.

[0212] Step 907: AMF sends the NCI of the IAB node to the CN-Domain-MnF.

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

[0214] The steps can be implemented through products, and the present invention will not elaborate on the specific implementation methods.

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

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

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

[0218] For example, the attributes in AMFFunction IOC are shown in Table 8 below. For other existing attributes in AMFFunction, reference may be made to the definitions in TS 28.541, which will not be described in detail in the present invention.

[0219] Table 8

[0220] 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.

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

[0222] Refer to Figure 10 and execute as follows:

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

[0224] Specifically, the NMS determines the NCI list of the IAB node of the IAB donor CU. The NCI list can be understood by referring to the introduction of FIG. 4 above, and will not be described in detail here. The details can be understood by referring to step 501, and will not be described in detail here.

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

[0226] Optionally, the NMS may further send indication information of the IAB node, where the indication information is used to indicate that the NCl list is used to configure the IAB node.

[0227] 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.

[0228] 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.

[0229] This can be understood by referring to step 502 in FIG. 5 , and will not be described in detail here.

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

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

[0232] For example, the CU selects different NCIs, that is, non-conflicting NCIs, for the IAB node 1 and the IAB node 2 that it supports.

[0233] 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.

[0234] Step 1005: The CU sends the NCI of the IAB node to the IAB node.

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

[0236] Step 1006: The IAB node sends the NCI of the IAB node to the UPF.

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

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

[0239] 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 IAB node belongs to.

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

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

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

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

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

[0245] For example, UPFFunction is shown in Table 9 below. For other existing attributes in UPFFunction, reference may be made to the definition in TS 28.541, which will not be described in detail in the present invention.

[0246] Table 9

[0247] 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.

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

[0249] Refer to Figure 11 and execute as follows:

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

[0251] Specifically, the NMS determines the NCI list of the IAB node of the IAB donor CU. The NCI list can be understood by referring to the introduction of FIG. 4 above, and will not be described in detail here. The details can be understood by referring to step 501, and will not be described in detail here.

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

[0253] Optionally, the NMS may further send indication information of the IAB node, where the indication information is used to indicate that the NCl list is used to configure the IAB node.

[0254] 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.

[0255] 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.

[0256] This can be understood by referring to step 502 in FIG. 5 , and will not be described in detail here.

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

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

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

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

[0261] For example, IAB node 1 selects the NCI of IAB node 1 from the NCI list of IAB nodes, and IAB node 2 selects the NCI of IAB node 2 from the NCI list of IAB nodes.

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

[0263] For example, IAB node 1 sends the NCI of IAB node 1 to UPF, and IAB node 2 sends the NCI of IAB node 2 to UPF.

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

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

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

[0267] 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.

[0268] 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 that performs each function. Those skilled in the art should easily appreciate 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 a hardware or computer software driven hardware manner 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 be beyond the scope of this application.

[0269] In the embodiments of the present application, the functional units of the device can be divided according to the above method examples. 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 software functional units.

[0270] In the case of adopting an integrated unit, Figure 12 shows a possible exemplary block diagram of the communication device involved in the embodiment of the present application. As shown in Figure 12, 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 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 used to perform receiving and sending operations respectively. 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 referred to as 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 referred to as 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 first device, the second device, the third device, etc. mentioned above.

[0271] In one embodiment, the communication apparatus 1200 is a first device, wherein the transceiver unit 1202 is configured to receive an NCI list of an IAB node from a second device; the processing unit 1201 is configured to determine the NCI of the IAB node based on the NCI list; and the transceiver unit 1202 is further configured to send the NCI of the IAB node to the second device.

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

[0273] 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.

[0274] 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 is an access network domain management functional unit or a core network domain management functional unit.

[0275] It should be noted that the first device is a core network domain management function 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.

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

[0277] Specifically, the processing unit 1201 is configured 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.

[0278] 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 the access network domain management function unit, the communication device is the cross-domain management function unit, and the third device is the core network domain management function unit.

[0279] As shown in Figure 13, this application also provides a communication device 1300. The communication device 1300 can be a chip or a chip system. The communication device can be located in the device involved in any of the above method embodiments, such as the first device or the second device, to perform the corresponding actions of the device.

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

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

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

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

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

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

[0286] Optionally, in actual applications, the communication device 1300 may or may not include a transceiver 1330, as illustrated by a dashed box in the figure. The communication device 1300 can exchange information with other devices via the transceiver 1330. The transceiver 1330 can be a circuit, a bus, a transceiver, or any other device capable of exchanging information.

[0287] 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.

[0288] The specific connection medium between the transceiver 1330, processor 1310, and memory 1320 is not limited in the embodiments of the present application. In FIG13 , the memory 1320, processor 1310, and transceiver 1330 are connected via a bus. The bus is represented by a bold line in FIG13 . The connection between other components is for illustrative purposes only and is not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, FIG13 uses only a single bold line, but this does not imply that there is only one bus or a single type of bus. In the embodiments 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, or a discrete hardware component, and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly executed by a hardware processor or by a combination of hardware and software modules within the processor.

[0289] In an 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 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 an 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.

[0290] Based on the above embodiments, referring to FIG14 , 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 receiving and sending steps of each device in any of the above method embodiments, and the logic circuit 1420 can be used to run code or instructions to execute the method executed by each device in any of the above embodiments, which will not be repeated.

[0291] Based on the above embodiments, embodiments of the present application further provide a computer-readable storage medium storing instructions that, when executed, cause the method executed by each device in any of the above method embodiments to be implemented, for example, causing the method executed by the first device or the second device in the embodiment shown in FIG4 to be implemented. The computer-readable storage medium may include various media capable of storing program code, such as a USB flash drive, a mobile hard drive, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

[0292] Based on the above embodiments, an embodiment of the present application provides a communication system, which includes the first device (e.g., RAN-Domain-MnF) and the 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.

[0293] In addition, the above-mentioned communication system may further include a terminal (eg, UE), which may perform data interaction with an access network device and a core network device to execute a related method in any of the above-mentioned method embodiments.

[0294] 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 take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, compact disc read-only memory (CD-ROM), optical storage, etc.) containing computer-usable program code.

[0295] 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 box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes 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 produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0296] These computer program instructions may also be stored in a computer-readable memory that can direct 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 a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0297] 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, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

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 19, 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