Information transmission method, device and system

Abstract

The invention provides an information transmission method, device and system. The user experience can be improved. The first network management device receives the information of the network node sent by the second network management device, wherein the information of the network node comprises the information of the first access and return integrated IAB node; and the first network management equipment configures the information of the network node.

Description

[0001] This application is a divisional application of the invention application filed on July 30, 2020, with Chinese application number 202010751732.X and title "Method, Apparatus and System for Information Transmission". Technical Field

[0002] This application relates to the field of communications, and more specifically, to a method, apparatus, and system for information transmission. Background Technology

[0003] Compared to fourth-generation mobile communication systems, fifth-generation mobile networks (5G) impose more stringent requirements on all aspects of network performance. For example, they demand a 1000-fold increase in capacity, wider coverage, and ultra-high reliability and ultra-low latency. Given the abundance of high-frequency carrier resources, the use of high-frequency small cell networks is becoming increasingly popular in hotspot areas to meet the ultra-high capacity demands of 5G. However, high-frequency carriers have poor propagation characteristics, suffer severe attenuation due to obstruction, and have limited coverage, thus requiring a large-scale, dense deployment of small cells. Providing fiber optic backhaul for these numerous, densely deployed small cells is costly and difficult to implement, especially in remote areas.

[0004] Integrated access and backhaul (IAB) technology offers a solution to the aforementioned problems. Both its access link and backhaul link utilize wireless transmission schemes, avoiding the need for fiber optic deployment. In an IAB network, a relay node (RN), also known as an IAB node, provides wireless access services to user equipment (UE). UE service transmissions are handled by the IAB node, which connects to the IAB donor node via a wireless backhaul link. The donor node is also called the donor gnodeB (DgNB).

[0005] Currently, IAB nodes can obtain Operation, Administration and Maintenance (OAM) services from the OAM entity through Protocol Data Unit (PDU) sessions between the IAB node and the core network entity. However, the standard does not specifically define how to obtain these services from the network management device side. Summary of the Invention

[0006] This application provides a method, apparatus, and system for information transmission that can enhance the user experience.

[0007] In a first aspect, a method for information transmission is provided, comprising: a first network management device receiving information from a network node of a second network management device, wherein the information of the network node includes information of a first access backhaul integrated IAB node; and the first network management device configuring the information of the network node.

[0008] Based on the above technical solution, the first network management device receives information about the first IAB node sent by the second network management device, and configures the first IAB node according to the information of the first IAB node, which can ensure the execution of the first IAB node's services and thus improve the user experience.

[0009] In one possible implementation, the method further includes: the first network management device sending information of the first IAB node to the network node.

[0010] In one possible implementation, the information of the first IAB node is the capability information of the first IAB node.

[0011] In one possible implementation, the method further includes: the first network management device sending information of the first IAB node to the network node, causing the network node to send information of the first IAB node to the first IAB node.

[0012] In one possible implementation, the network node sends information of the first IAB node to the first IAB node, including: the network node sends the information of the first IAB node through a transmission link between the network node and the first IAB node, the transmission link being provided by a Protocol Data Unit (PDU) session of the first IAB node.

[0013] In one possible implementation, the information of the first IAB node includes at least one of the following: the identifier of the first IAB node, the length of the identifier of the first IAB node, the name of the first IAB node, the identifier of the Public Land Mobile Network (PLMN) to which the first IAB node belongs, the cell identifier of the first IAB node, the Absolute Radio Frequency Channel Number (ARFCN) of the first IAB node, the Cell Search Synchronization Signal (SSB) of the first IAB node, the Bandwidth Part (BWP) of the first IAB node, the cell status of the first IAB node, the management status of the first IAB node, the Internet Protocol (IP) address of the first IAB node, the IP address of the host node of the first IAB node, or the identifier of the host node of the first IAB node.

[0014] In one possible implementation, the method further includes:

[0015] The first network management device sends first information to the second network management device, the first information being used to obtain information about the first IAB node.

[0016] In one possible implementation, the first network management device is a management service producer, a wireless automation engine (MAE), or a network element management system (EMS); the second network management device is a management service consumer or a network management system (NMS).

[0017] Secondly, a method for information transmission is provided, comprising: a second network management device determining information about a network node, wherein the information about the network node includes information about a first integrated access backhaul (IAB) node; and the second network management device sending the information about the network node to a first network management device.

[0018] In one possible implementation, the information of the first IAB node includes at least one of the following: the identifier of the first IAB node, the length of the identifier of the first IAB node, the name of the first IAB node, the identifier of the Public Land Mobile Network (PLMN) to which the first IAB node belongs, the cell identifier of the first IAB node, the Absolute Radio Frequency Channel Number (ARFCN) of the first IAB node, the Cell Search Synchronization Signal (SSB) of the first IAB node, the Bandwidth Part (BWP) of the first IAB node, the cell status of the first IAB node, the management status of the first IAB node, the Internet Protocol (IP) address of the first IAB node, the IP address of the host node of the first IAB node, or the identifier of the host node of the first IAB node.

[0019] In one possible implementation, the method further includes: the second network management device receiving first information sent by the first network management device, the first information being used to obtain information about the first IAB node.

[0020] In one possible implementation, the first network management device is a management service producer, a wireless automation engine (MAE), or a network element management system (EMS); the second network management device is a management service consumer or a network management system (NMS).

[0021] Thirdly, a method for information transmission is provided, comprising: a first network management device acquiring management data of a network node, wherein the management data of the network node includes management data of a first integrated access backhaul (IAB) node; the first network management device sending the management data of the network node to a second network management device, wherein the management data includes fault information and / or performance information.

[0022] Based on the above technical solution, the first network management device obtains the fault information and / or performance information of the network node and sends the fault information and / or performance information of the network node to the second network management device, which can ensure the execution of the services of the first IAB node and thus improve the user experience.

[0023] In one possible implementation, the method further includes: the first network management device receiving a subscription request message from the second network management device, the subscription request message including second indication information, the second indication information being used to obtain management data of the first IAB node.

[0024] In one possible implementation, the first network management device sends the management data of the network node to the second network management device, including: the first network management device sending the management data of the network node to the second network management device through a data stream connection.

[0025] In one possible implementation, before the first network management device acquires the management data of the network node, the method further includes: the first network management device sending a data stream connection establishment request message to the second network management device; and the first network management device receiving a data stream connection establishment success response message sent by the second network management device.

[0026] In one possible implementation, the method further includes: the first network management device sending an interruption data stream connection indication message to the second network management device.

[0027] In one possible implementation, the second indication information includes the identifier of the first IAB node.

[0028] In one possible implementation, the first network management device is a management service producer, a wireless automation engine (MAE), or a network element management system (EMS); the second network management device is a management service consumer or a network management system (NMS).

[0029] Fourthly, a method for information transmission is provided, comprising: a second network management device receiving management data of a network node sent by a first network management device, wherein the management data of the network node includes management data of a first integrated access backhaul (IAB) node, and wherein the management data includes fault information and / or performance information.

[0030] In one possible implementation, the method further includes: the second network management device sending a subscription request message to the first network management device, the subscription request message including second indication information, the second indication information being used to obtain management data of the first IAB node.

[0031] In one possible implementation, before the second network management device receives management data of the network node sent by the first network management device, the method further includes: the second network management device receiving a data stream connection establishment request message sent by the first network management device; the second network management device establishing a data stream connection with the first network management device according to the data stream connection establishment request message; and the second network management device sending a data stream connection establishment success response message to the first network management device through the data stream connection.

[0032] In one possible implementation, the method further includes: the second network management device receiving interrupted data stream connection indication information sent by the first network management device; and the second network management device terminating the data stream connection with the first network management device according to the interrupted data stream connection indication information.

[0033] In one possible implementation, the second indication information includes the identifier of the first IAB node.

[0034] In one possible implementation, the first network management device is a management service producer, a wireless automation engine (MAE), or a network element management system (EMS); the second network management device is a management service consumer or a network management system (NMS).

[0035] Fifthly, a communication system is provided, comprising: a first network management device and a second network management device, wherein the second network management device is configured to send information of network nodes to the first network management device.

[0036] In one possible implementation, the second network management device is further configured to determine information about network nodes, including information about the first access backhaul (IAB) node.

[0037] In one possible implementation, the second network management device is further configured to receive first information sent by the first network management device, the first information being used to obtain information about the first IAB node.

[0038] A sixth aspect provides a communication system comprising: a first network management device and a second network management device, wherein the second network management device is configured to receive management data of network nodes sent by the first network management device, wherein the management data includes fault information and / or performance information.

[0039] In one possible implementation, the second network management device is further configured to send a subscription request message to the first network management device, the subscription request message including second indication information, the second indication information being used to obtain management data of the first access backhaul integrated IAB node.

[0040] In one possible implementation, the second network management device is further configured to: receive a data stream connection establishment request message sent by the first network management device, establish a data stream connection with the first network management device according to the data stream connection establishment request message, and send a data stream connection establishment success response message to the first network management device through the data stream connection.

[0041] In one possible implementation, the second network management device is specifically used to: receive the performance information of the network node sent by the first network management device through the data stream connection.

[0042] In a seventh aspect, a communication device is provided for performing the methods of the first to fourth aspects or any possible implementation thereof.

[0043] Eighthly, a communication device is provided, comprising: a processor, a memory, and an interface, wherein the memory is used to store computer code or instructions, the interface is used for communication, and the processor is used to invoke and execute the computer code or instructions in the memory, such as the methods in the first to fourth aspects or any possible implementations of the first to fourth aspects.

[0044] Ninth aspect, a computer-readable storage medium is provided, the computer-readable medium storing a computer program; when the computer program is run on a computer, it causes the computer to perform the method of the first aspect or any possible implementation thereof.

[0045] In a tenth aspect, a computer-readable storage medium is provided, the computer-readable medium storing a computer program; when the computer program is run on a computer, it causes the computer to perform the method of the second aspect or any possible implementation thereof.

[0046] Eleventhly, a computer-readable storage medium is provided, the computer-readable medium storing a computer program; when the computer program is run on a computer, it causes the computer to perform the method of the third aspect or any possible implementation of the third aspect.

[0047] In a twelfth aspect, a computer-readable storage medium is provided, the computer-readable medium storing a computer program; when the computer program is run on a computer, it causes the computer to perform the methods of the fourth aspect or any possible implementation thereof. Attached Figure Description

[0048] Figure 1 This is a schematic diagram of a wireless relay scenario according to an embodiment of this application.

[0049] Figure 2 This is a schematic diagram of the network architecture applicable to IAB nodes in an embodiment of this application.

[0050] Figure 3 This is a schematic block diagram of a communication system 300 according to an embodiment of this application.

[0051] Figure 4 This is an example diagram illustrating how MnF in this application simultaneously plays the roles of both a management service producer and a management service consumer.

[0052] Figure 5 This is a schematic diagram of a service-oriented management architecture according to an embodiment of this application.

[0053] Figure 6 This is a schematic flowchart illustrating an information transmission method according to an embodiment of this application.

[0054] Figure 7 This is a schematic diagram illustrating the relationship between different objects of the IOC in an embodiment of this application.

[0055] Figure 8 This is a schematic diagram showing the connection between the IAB node and gNB-CU via the IOC EP_F1C and EP_F1U interfaces in an embodiment of this application.

[0056] Figure 9 This is an interactive schematic diagram illustrating another information transmission method according to an embodiment of this application.

[0057] Figure 10 This is an interactive schematic diagram illustrating another information transmission method according to an embodiment of this application.

[0058] Figure 11 This is an interactive schematic diagram illustrating another information transmission method according to an embodiment of this application.

[0059] Figure 12 This is an interactive schematic diagram illustrating another information transmission method according to an embodiment of this application.

[0060] Figure 13 This is a schematic block diagram of a communication device 1300 according to an embodiment of this application.

[0061] Figure 14 This is a schematic block diagram of another communication device 1400 according to an embodiment of this application.

[0062] Figure 15 This is a schematic block diagram of another communication device 1500 according to an embodiment of this application.

[0063] Figure 16 This is a schematic block diagram of another communication device 1600 according to an embodiment of this application.

[0064] Figure 17 This is a schematic block diagram of another communication device according to an embodiment of this application. Detailed Implementation

[0065] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0066] The embodiments of this application can be applied to various communication systems, such as wireless local area network (WLAN), narrow band internet of things (NB-IoT), global system for mobile communications (GSM), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division-synchronization code division multiple access (TD-SCDMA), long term evolution (LTE), satellite communication, 5th generation (5G) systems, or new communication systems that will emerge in the future.

[0067] The terminal devices involved in the embodiments of this application may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. The terminal may be a mobile station (MS), subscriber unit, user equipment (UE), cellular phone, smartphone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem, handset, laptop computer, machine-type communication (MTC) terminal, etc.

[0068] Compared to fourth-generation mobile communication systems, fifth-generation mobile networks (5G) impose more stringent requirements on all aspects of network performance. For example, they demand a 1000-fold increase in capacity, wider coverage, and ultra-high reliability and ultra-low latency. Given the abundance of high-frequency carrier resources, the use of high-frequency small cell networks is becoming increasingly popular in hotspot areas to meet the ultra-high capacity demands of 5G. However, high-frequency carriers have poor propagation characteristics, suffer severe attenuation due to obstruction, and have limited coverage, thus requiring a large-scale, dense deployment of small cells. Providing fiber optic backhaul for these numerous, densely deployed small cells is costly and difficult to implement, especially in remote areas.

[0069] Integrated access and backhaul (IAB) technology offers a solution to the above problems. Both its access link and backhaul link utilize wireless transmission, avoiding the need for fiber optic deployment. For example... Figure 1The diagram illustrates a wireless relay scenario. In an IAB network, a relay node (RN), also known as an IAB node, provides wireless access services to user equipment (UE). UE service transmissions are handled by the IAB node, which connects to the IAB host node (donor node) via a wireless backhaul link. The host node is also called the host base station (donor gnodeB, DgNB). An IAB node can function as both a mobile terminal (MT) and a distributed unit (DU). When an IAB node faces its parent node, it is considered a terminal device (MT), where the parent node may be the host base station. When an IAB node faces its child node, it is considered a network device (DU), where the child node may be another IAB node or a regular UE. The host base station can be an access network element with full base station functionality, and can be an access network element with separate centralized unit (CU) and distributed unit configurations. For ease of description, the centralized unit of the host base station is abbreviated as donor CU or simply CU, and the distributed unit of the host base station is abbreviated as donor DU or simply DU. The donor CU may also have a separate control plane (CP) and user plane (UP) configuration; for example, a CU may consist of one CU-CP and one or more CU-UPs. The host base station connects to the core network elements serving the UE, such as connecting to the 5G core network, and provides radio backhaul functionality for IAB nodes.

[0070] Currently, IAB nodes can obtain Operation, Administration, and Maintenance (OAM) services from the OAM entity through Protocol Data Unit (PDU) sessions between the IAB node and the core network entity. The transmission connection between the IAB node and its OAM entity uses the IP protocol and is provided by the IAB-MTs PDU session over the 5G network. Alternatively, when the IAB-MT uses EN-DC, it is provided by the IAB-MTs PDN connection over the LTE network. However, the standard does not define the specific transmission on the network management equipment side, nor does it specify how the new 5G Quality of Service (5QI) indicator is defined. Additionally, IAB nodes can directly obtain OAM services from the OAM entity via the backhaul link, but the specific transmission method is not reflected in the protocol.

[0071] OAM services include: receiving commands, such as operation information commands related to fault management (FM), configuration management (CM), and performance management (PM); configuration data; software downloads, such as those for device software upgrades; alarms; and performance indicator information. Alarms generate high-priority traffic bursts, but do not require real-time transmission. Configuration data sent by the OAM entity to the IAB node also generates small bursts of traffic, with a lower priority than alarms, but is still sensitive to latency.

[0072] For ease of understanding of the embodiments of this application, as follows: Figure 2 The diagram illustrates a network architecture suitable for IAB nodes. The IAB host node (IAB-Donor gNB) is a base station that provides services to IAB nodes via wireless connection. An IAB-Donor gNB consists of an IAB-Donor-CU and one or more IAB-Donor-DUs. With gNB-CU-CP and gNB-CU-UP separated, the IAB-donor gNB can consist of one IAB-donor-CU-CP, multiple IAB-donor-CU-UPs, and multiple IAB-donor-DUs.

[0073] like Figure 3 As shown, a communication system 300 provided in an embodiment of this application is presented. The communication system 300 includes: a first network management device 310 and a second network management device 320.

[0074] In one implementation, the second network management device is used to send network node information to the first network management device. The first network management device is used to receive network node information from the second network management device, the network node information including information of the first access backhaul integrated IAB node; the first network management device is also used to configure the network node information.

[0075] Optionally, the second network management device is also used to determine information about network nodes, including information about the first IAB node.

[0076] Optionally, the first network management device is further configured to send first information to the second network management device, the first information being used to obtain information about the first IAB node.

[0077] Optionally, the second network management device is also used to receive the first information sent by the first network management device.

[0078] Optionally, the first network management device is also used to send information of the first IAB node to the network node.

[0079] Optionally, the first network management device is further configured to send the information of the first IAB node to a network node, so that the network node sends the information of the first IAB node to the first IAB node.

[0080] In another implementation:

[0081] The first network management device is used to acquire management data of network nodes, including management data of the first integrated access backhaul (IAB) node; the first network management device is also used to send the management data of the network node to the second network management device, wherein the management data includes fault information and / or performance information.

[0082] The second network management device is used to receive management data of network nodes sent by the first network management device.

[0083] Optionally, the second network management device is further configured to send a subscription request message to the first network management device, the subscription request message including second indication information, the second indication information being used to obtain management data of the first access backhaul integrated IAB node.

[0084] Optionally, the first network management device is also used to receive subscription request messages from the second network management device.

[0085] Optionally, the first network management device is further configured to send a data stream connection establishment request message to the second network management device and receive a data stream connection establishment success response message sent by the second network management device.

[0086] Optionally, the second network management device is further configured to: receive a data stream connection establishment request message sent by the first network management device, establish a data stream connection with the first network management device according to the data stream connection establishment request message, and send a data stream connection establishment success response message to the first network management device through the data stream connection.

[0087] Optionally, the first network management device is also used to send management data of network nodes to the second network management device via a data stream connection.

[0088] Optionally, the second network management device is specifically used to: receive the performance information of the network node sent by the first network management device through the data stream connection.

[0089] The first network management device can be a management service producer, a management service consumer, a domain management function unit, a wireless automation engine (MBB automation engine, MAE), or an element management system (EMS); the second network management device can be a management service consumer, a management service producer, a cross-domain management function unit, or a network management system (NMS).

[0090] A management function (MnF) is a management entity defined by the 3rd Generation Partnership Project (3GPP). Its externally visible behaviors and interfaces are defined as management services. In a service-providing management architecture, the MnF acts as either a management service producer (MnS Producer) or a management service consumer (MnS Consumer). The management services produced by the MnF's management service producer may have multiple consumers. An MnF can consume multiple management services from one or more management service producers. For example... Figure 4 As shown, an example diagram is presented where MnF simultaneously plays the roles of both a managerial service producer and a managerial service consumer.

[0091] For example, the Management Service Consumer (MnS Consumer) can be a management entity such as a network management system (NMS), and the Management Service Producer (MnS Producer) can be a management entity such as an element management system (EMS) or a wireless automation engine (MBB automation engine (MAE). This application does not limit this.

[0092] Figure 5This is a schematic diagram of a service-oriented management architecture provided in an embodiment of this 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 network elements. It should be understood that the cross-domain management function can be a node such as an NMS, MnS Producer, or MnS Consumer, and the domain management function can be a node such as an EMS, MAE, MnS Producer, or MnS Consumer.

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

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

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

[0096] A business support system (BSS) is oriented towards communication services, providing functions and management services such as billing, settlement, accounting, customer service, sales, network monitoring, communication service lifecycle management, and service intent translation. The BSS can be an operator's operating system or a vertical OT system.

[0097] A cross-domain management function unit, also called a network management function (NMF), can be a network management system (NMS) or a network function management service consumer (NFMS_C), among other network management entities. The cross-domain management function unit provides one or more of the following management functions or services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization, and translation of network intents from communication service providers (Intent-CSPs).

[0098] The network referred to in the aforementioned management functions or services may include one or more network elements or sub-networks, or it may be a network slice. In other words, the network management function unit may be a network slice management function (NSMF), a management data analytical function (MDAF), a self-organization network function (SON Function), or an intent-driven management service (MnS).

[0099] Optionally, in certain deployment scenarios, the cross-domain management function 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, and translation of network intents (Intent-CSP) from service producers or network intents (intent from communication service consumer, Intent-CSC) from service consumers in the sub-network. Here, a sub-network consists of multiple smaller sub-networks, which can be network slice sub-networks.

[0100] A domain management function (MnF), also called a network management function (NMF) or network element management function, can be a network element management entity such as a wireless automation engine (MAE), an element management system (EMS), or a network function management service provider (NFMS_P).

[0101] The domain management function unit provides one or more of the following functions or management services: lifecycle management of subnetworks or network elements, deployment of subnetworks or network elements, fault management of subnetworks or network elements, performance management of subnetworks or network elements, assurance of subnetworks or network elements, optimization functions of subnetworks or network elements, and translation of intents from network operators (Intent-NOPs) of subnetworks or network elements. Here, a subnetwork includes one or more network elements. A subnetwork can also include other subnetworks, meaning one or more subnetworks can form a larger subnetwork.

[0102] Optionally, the subnet here can also be a network slice subnet. The domain management system can be a network slice subnet management function (NSSMF), a management data analytical function (Domain MDAF), a self-organizing network function (SON Function), or an IntentDriven MnS, etc.

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

[0104] Based on network type, domain management functions can be categorized into: Radio Access Network Domain Management Function (RAN-Domain-MnF), Core Network Domain Management Function (CN-Domain-MnF), and Transport Network Domain Management Function (TN-Domain-MnF). It's important to note that a domain management function unit can also be a domain network management system, managing one or more of the following: access network, core network, or transport network.

[0105] According to administrative regions, they can be classified as: regional management functional units of a certain area, such as Shanghai regional management functional unit, Beijing regional management functional unit, etc.

[0106] 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 gNB, eNB), central unit control plane (CUCP), central unit (CU), distribution unit (DU), and central unit user plane (CUUP).

[0107] Among them, network elements can provide one or more of the following management functions or services: network element lifecycle management, network element deployment, network element fault management, network element performance management, network element assurance, network element optimization functions, and network element intent translation, etc.

[0108] This application proposes an information transmission method to realize the transmission of OAM services and improve user experience. For example... Figure 6 The diagram shown illustrates a schematic flowchart of an information transmission method according to an embodiment of this application.

[0109] 610, The second network management device determines the information of the network node, the information of which includes the information of the first access backhaul integrated IAB node.

[0110] It should be understood that the information of the first IAB node is included in the management object of the network node. The management object of the network node can be the management object of the core network node or the management object of the base station. For example, the management object of the core network node can be AMFFunction IOC, UPFFunction IOC, etc., and the management object of the base station node can be ManagedElement IOC, gNBDUFunction IOC, gNBCUUPFunction IOC, gNBCUCPFunction IOC, NRcellCU IOC, NRcellDU IOC, NRcellRelation IOC, ENBFunction IOC, EUtranCell IOC, or EUtranRelation IOC, etc. Optionally, the management object of the base station can also be defined as IABnode IOC or IABnodecell IOC.

[0111] In one implementation, the second network management device can independently determine information about one or more network nodes, i.e., independently determine the information that needs to be sent to the first IAB node. For example, the second network management device determines information about one or more network nodes, including information about one or more IAB nodes. The second network management device sends the network node information to the first network management device. After the first network management device sends the network node information to the network nodes, the network nodes will configure the IAB node information according to the IAB node's network access status.

[0112] In another implementation, after the first IAB node accesses the network, the network node sends first information to the first network management device. The first network management device then forwards this first information to the second network management device. The second network management device determines the information of the first IAB node based on the first information and sends this information back to the first IAB node. Specifically, the first network management device can send first information to the second network management device, which is used to obtain the information of the first IAB node; the second network management device receives the first information sent by the first network management device. It should be understood that the first information sent by the first network management device to the second network management device can be carried in the information of the network node, that is, the first information can be carried in the management object of the network node.

[0113] It should be understood that the network nodes can be core network nodes or base station nodes. Core network nodes can be LTE core network nodes, such as MME and SGW, or 5G NR core network nodes such as AMF and UPF. Base station nodes can be gNB, en-gNB, ng-eNB, eNB, gNB-CU, gNB-DU, gNB-CU-CP, gNB-CU-UP, eNB cell, gNB cell, gNB-DU cell, or gNB-CU cell. Optionally, base station nodes can also be IAB nodes or IAB node cells. The first network management device can be a management service producer, a management service consumer, a domain management function unit, a wireless automation engine (MBBautomation engine, MAE), or an element management system (EMS). The second network management device can be a management service consumer, a management service producer, a cross-domain management function unit, or a network management system (NMS).

[0114] Optionally, the network node may also refer to its neighboring network nodes or its neighboring cells (or adjacent cells). Accordingly, the network node's information includes information about its neighboring network nodes or its neighboring cells. The information about the network node's neighboring cells can also be understood as information about the neighboring relationships between network nodes.

[0115] Optionally, the network node information includes information about core network nodes or base station nodes, such as one or more of the following: base station name, base station identifier, cell identifier (e.g., PCI, CGI, etc.), neighboring base station name, neighboring base station identifier, neighboring cell identifier (e.g., PCI, CGI, etc.), PLMN identifier, core network node name, core network node identifier, etc. This embodiment is not limited to these, but any information related to the configuration of core network nodes or base station nodes can be included, which will not be elaborated here.

[0116] The information of the first IAB node includes one or more of the following: the identifier of the first IAB node, the length of the identifier of the first IAB node, the name of the first IAB node, the identifier of the public land mobile network (PLMN) to which the first IAB node belongs, the cell identifier of the first IAB node, the absolute radio frequency channel number (ARFCN) of the first IAB node, the cell search synchronization signal (SS / PBCH block, SSB) of the first IAB node, the bandwidth part (BWP) of the first IAB node, the cell status of the first IAB node (e.g., active, inactive), the management status of the first IAB node (e.g., locked, shutting down, unlocked), the Internet Protocol (IP) address of the first IAB node, the IP address of the host node (e.g., IAB-donor-CU) of the first IAB node, the identifier of the host node of the first IAB node, and the capability information of the first IAB node. It should be understood that the identifier of the first IAB node includes one or more of the local identifier (LocalcellID) or physical cell identifier (PMI) and tracking area identifier (TAC) of the first IAB node; the ARFCN of the first IAB node includes one or more of the downlink ARFCN, uplink ARFCN, and supplementary uplink ARFCN of the IAB node cell; the SSB of the first IAB node includes one or more of the SSB frequency, SSB period (SSBPeriodicity), SSB offset, SSB duration (SSBDuration), and SSB subcarrier spacing of the IAB node cell; and the bandwidth of the first IAB node includes one or more of the baseband uplink channel bandwidth (BSchannelBWUL) and baseband supplementary uplink channel bandwidth (BSchannelBWSUL) of the IAB node cell.

[0117] The IP address of the first IAB node can be an IPv4 address or an IPv6 address, which is the IP address used by the first IAB node for data interaction. The IP address of the host node of the first IAB node refers to the IP address of the host node (e.g., IAB-donor-CU) of the IAB node connected to the first IAB node through an interface (e.g., an F1 interface), which is also an IPv4 address or an IPv6 address, used by the first IAB node to interact with the host node of the IAB node through the interface. The identifier of the host node of the first IAB node is used to identify that the IP address is the host node of the IAB node. The IAB capability information is used to indicate whether the network node supports IAB functionality, or whether the network node supports IAB nodes, or whether the network node supports IAB node access. For example, IAB capabilities can be indicated using "is IAB Allowed" or "IAB Supported".

[0118] Optionally, the information of the first IAB node can also exist as a management object IOC, such as IAB nodeInformation IOC, which is associated with a network node, such as network node AMFIOC, UPF IOC, GNBCUCP IOC, or NRCellRelationIOC.

[0119] Optionally, the first information may include the identifier of the first IAB node, used to indicate the acquisition of information about the first IAB node. The identifier of the first IAB node may be identification information such as physical cell ID (PCI), cell global ID (CGI), or cell ID, which is not limited herein. For example, the first information may be IAB node indication information or IAB node configuration request indication information. The MAE sends the IAB node indication information or IAB node configuration request indication information to the NMS to indicate the acquisition of information about the first IAB node. This IAB node indication information or IAB node configuration request indication information can be sent through existing operations between the MAE and the NMS, or it can be sent through newly defined operations.

[0120] Optionally, the first information may also include identification information of the network node, indicating that the information of the first IAB node was configured through that network node. For example, the identification information of the network node may be an AMF ID or a UPF ID, etc.

[0121] Optionally, the first information indicates an IAB node, that is, it indicates that an IAB node has accessed the network. For example, the first information is IAB node indication information. The MAE sends the IAB node indication information to the NMS to indicate that the information of the first IAB node has been acquired. This IAB node indication information can be sent through existing operations between the MAE and the NMS, or it can be sent through newly defined operations. Specifically, optionally, after the first IAB node accesses the wireless network, the first IAB node can send an IAB node indication to the base station. This IAB node indication is used to indicate that the first IAB node has joined the network. The base station then sends the IAB node indication to the core network equipment, such as the access and mobility management function (AMF). The AMF then sends the IAB node indication to the network management equipment, which in turn sends the information of the first IAB node to the first IAB node.

[0122] Optionally, the first information may be an integrated access and backhaul node list (IAB node list) indication information, used to indicate that more than one first IAB node is connected to the wireless network. This IAB node list indication information is used to obtain information about multiple first IAB nodes.

[0123] Optionally, the first information can also exist as a management object IOC, such as an IAB node Indication IOC, which is associated with a network node, such as an AMF or UPF.

[0124] For example, as shown in Table 1, the addition of first information, such as an IABnode indication, to the AMF information object class (IOC) defined in the network resource management (NRM) model is illustrated. This could be called iABnodeIndication, or some other name.

[0125] Table 1 Examples of adding IAB node indications in AMF IOC

[0126]

[0127] M is mandatory, and CM is conditionally mandatory, meaning the iAB node indicator only exists in scenarios supported by the IAB feature. The other attributes besides the IAB node indicator are parameters already supported in existing technologies and will not be elaborated upon here.

[0128] For example, as shown in Table 2, information about adding the first IAB node to the UPF IOC defined in the NRM model is presented, for example, referred to as iABnodeInformation, or iABnodeConfiguration, or other names.

[0129] Table 2 shows examples of adding IAB node configuration in UPF IOC.

[0130]

[0131] M is mandatory, and CM is conditionally mandatory, meaning the iAB node indicator only exists in scenarios where the IAB feature is supported. The other attributes besides the IAB node configuration are parameters already supported in existing technologies and will not be elaborated upon here.

[0132] For example, as shown in Table 3, an NRM model is presented to determine the information of the first IAB node for the neighboring cells of a network node. The NRCellRelationIOC defined in the NRM model adds the information of the first IAB node. Here, the information of the first IAB node refers to the capabilities supported by the IAB function, such as being called isIABllowed, or other names.

[0133] Table 3 shows examples of the ability to add IAB feature support in NR Cell Relation IOC.

[0134]

[0135] M is mandatory, and CM is conditionally mandatory, meaning the isIABAllowed indicator only exists in scenarios supported by IAB features. The other attributes besides the isIABAllowed indicator are parameters already supported in existing technologies and will not be elaborated upon here.

[0136] For example, as shown in Tables 4 and 5, an NRM model is presented to determine the information of the first IAB node for a network node. The information of the first IAB node is added to the AMF IOC or MME IOC defined in the NRM model. Here, the information of the first IAB node refers to the network node's ability to support IAB, such as being called IAB supported, or other names.

[0137] Table 4 shows examples of the ability to add IAB functionality support in AMF IOC.

[0138]

[0139] M is mandatory, and CM is conditionally mandatory, meaning the IABsupported indicator only exists in scenarios where IAB features are supported. The other attributes besides the IABsupported indicator are parameters already supported in existing technologies and will not be elaborated upon here.

[0140] Table 5 shows examples of the ability to add IAB functionality support in the MME IOC.

[0141]

[0142] M is mandatory, and CM is conditionally mandatory, meaning the IABsupported indicator only exists in scenarios where IAB features are supported. The other attributes besides the IABsupported indicator are parameters already supported in existing technologies and will not be elaborated here; please refer to 3GPP TS 28.708 for details.

[0143] 620. The second network management device sends network node information to the first network management device, including the information of the first IAB node.

[0144] Specifically, after the second network management device determines that it will send information to the first IAB node or determines that the first IAB node has accessed the wireless network based on the received instruction information, it can send network node information to the first network management device.

[0145] It should be noted that the second network management device can send network node information to the first network management device through existing operations, such as create MOI operation, modify MOI Attributes operation, or delete MOI operation, or it can use newly defined operations. This embodiment does not limit this.

[0146] It should also be noted that the information of the network nodes can also be understood as network function-related requirements, which are the information model definitions of NRM. For example, the contents of Tables 1 and 2 are the information models of AMF IOC and UPF IOC defined by NRM.

[0147] 630, the first network management device receives information about a network node sent by the second network management device, the information of which includes information about the first IAB node.

[0148] 640, The first network management device configures the information of this network node.

[0149] It should be noted that the information configured by the first network management device for the network node includes the information configured by the first network management device for the first IAB node in the management object of the network node. The management object of the network node can be the management object of the core network node or the management object of the base station. For example, the management object of the core network node can be AMF Function IOC, UPF Function IOC, etc., and the management object of the base station node can be gNB DU Function IOC, gNB CU UP Function IOC, gNB CU CP Function IOC, NRcell CU IOC, NR cell DUIOC, NR cell Relation IOC, ENB Function IOC, EUtran Cell IOC, or EUtran Relation IOC, etc.; optionally, the base station node can also be an IAB node or an IAB node cell.

[0150] Optionally, when the network node in step 610 refers to an adjacent network node or a neighboring cell of the network node, it can also be understood that the first network management device configures the information of the first IAB node in the management object of the adjacent network node or the management object of the neighboring cell (e.g., the management object of the neighboring cell relationship). The management object of the adjacent network node can be a core network node or a base station node. For example, the management object of the core network node can be AMFFunction IOC, UPF Function IOC, etc., and the management object of the base station node can be gNB DU Function IOC, gNB CU UP Function IOC, gNB CU CP Function IOC, NR cell CU IOC, NR cell DU IOC, ENB Function IOC, etc. The management object of the neighboring cell of the network node can be the management object of the neighboring cell of the base station, such as NR cell Relation IOC, etc.

[0151] Optionally, when step 620 involves performing the createMOI operation, the first network management device creates the object of the network node to be created before this step. For example, the network node object can be an AMF IOC, UPF IOC, etc.

[0152] Optionally, the first network management device sends a response message to the second network management device. The response message may include the identifier of the first network management device and / or the identifier of the network node object. The response message may use existing operations, such as the CreateMOI response, or it may use newly defined operations; this invention is not limited thereto.

[0153] Optionally, the first network management device sends the information of the first IAB node to the network node. The information of the first IAB node is the capability information of the first IAB node.

[0154] Optionally, the first network management device sends the information of the first IAB node to the network node, causing the network node to send the information of the first IAB node to the first IAB node. It should be understood that the network node can be a core network node or a base station node. The core network node can be an AMF, UPF, MME, SGW, etc., and the base station node can be a gNB, en-gNB, eNB, gNB-CU, gNB-DU, gNB-CU-CP, gNB-CUcell, gNB-DUcell, or gNB-CU-UP. The first network management device can be a management service producer, management service consumer, domain management function unit, wireless automation engine (MBBautomation engine, MAE), or element management system (EMS). The second network management device can be a management service consumer, management service producer, cross-domain management function unit, or network management system (NMS).

[0155] Optionally, the transmission link between the first IAB node and the network node is provided by the Protocol Data Unit (PDU) session of the first IAB node. It should be understood that the transmission link between the IAB-node and the first network management device or the second network management device uses IP and is provided by the IAB-MT's PDU session through the 5G network, or when the IAB-MT uses a multi-link architecture, it is provided by the IAB-MT's PDN connection through the LTE network.

[0156] Specifically, after receiving the information from the network node, the first network management device sends the information of the network node to the core network device, which can be a user plane function (UPF). The UPF then sends the information of the first IAB node to the base station, and the base station then sends the information of the first IAB node to the first IAB node.

[0157] In the technical solution provided in this application embodiment, the first network management device receives information about the first IAB node sent by the second network management device, and the first network management device configures the first IAB node according to the information of the first IAB node, which can ensure the execution of the first IAB node's services and thus improve the user experience.

[0158] For the transmission method where IAB nodes directly obtain OAM services from the OAM entity via the backhaul link, this application proposes another information transmission method. This application adds an IAB node functional object type, as shown in the following example:

[0159] The IAB node's network resource management (NRM) model defines information object classes (IOCs) such as IAB node functional objects and IAB node cell objects. The IAB node cell object is managed by the IAB node functional object, which in turn is managed by the IOC management entity (e.g., ManagedElement IOC). Figure 7 As shown, a diagram illustrating the relationships between different objects in the IOC is presented.

[0160] The IAB node's NRM transmission model (EPs) defines EP_F1C IOC and EP_F1U IOC as the interface between the IAB node and the gNB-CU. The gNB-CU can include gNB-CU-CP and gNB-CU-UP. The EP_F1C IOC and EP_F1U IOC include the local and remote IP addresses, such as the IP address of the IAB node and the IP address of the gNB-CU (e.g., the IAB donorCU). These IP addresses can be IPv4 or IPv6 addresses, and are determined by the second network management device. Figure 8 The diagram shows the connection between the IAB node and gNB-CU via the IOC EP_F1C and EP_F1U interfaces.

[0161] The following attributes are added for IAB nodes and IAB node cells. The attributes of an IAB node may include one or more of the following: IAB node ID, IAB node ID length, IAB node Name, and PLMNID. This embodiment of the application does not limit these attributes. The attributes of an IAB node cell may include one or more of the following: IAB node cell Local ID (e.g., CGI), PCI (Physical cell ID), TAC, ARFCN (absolute radiofrequency channel number, including uplink and downlink), SSB Frequency, SSB subcarrier spacing, SSB offset, and BWP information.

[0162] The aforementioned IAB node transmits data directly to the network management device via an IP backhaul link. This network management device can be either an MnS consumer or an MnS producer; this application does not limit the specific device. It should be noted that in this embodiment, the IAB node and IAB node cell can be modeled and configured independently, or they can be modeled and configured together. This explanation only uses independent modeling and configuration as an example.

[0163] In addition, this application defines a new 5QI. Among them, FM and CM services are both latency-sensitive services, and the priority of CM services may be lower than that of FM services; PM is a non-latency-sensitive service, which is generally reported in a period of 5 to 25 minutes, but the maximum burst volume needs to be limited, and its priority is the lowest.

[0164] Optionally, FM data can be classified into 5QI levels according to the following categories: hardware failures, software problems, functional faults, loss of some or all of the network element's specified capability due to overload situations, and communication failures between two network elements.

[0165] Optionally, PM data can be categorized into 5QI classes as follows: Network Function Performance Management (NF PM), Network Slice Subnet Instance Performance Management (NSSI PM), Network Slice Instance Performance Management (NSI PM), and Network Performance Management (NW PM).

[0166] Optionally, CM can classify 5QI based on basic configuration and software version updates. Basic configuration refers to one or more parameter configurations such as cell, base station, and slice. For example, cell configuration includes cell name, identifier, frequency point, etc.

[0167] 5G quality of service (QoS) characteristics related to 5QI include one or more of the following, but are not limited to:

[0168] (1) Resource type: guaranteed bit rate (GRB), GRB with severe latency, or non-GRB;

[0169] (2) Priority level;

[0170] (3) Packet delay budget, including the packet delay budget of the core network;

[0171] (4) Packet error rate;

[0172] (5) Averaging window, limited to GRB or GRB resource types with severe latency;

[0173] (6) Maximum data burst volume, limited to GRB resource types with severe latency.

[0174] As shown in Table 6, an example of the 5QI definition in an embodiment of this application is presented.

[0175] Table 6. An example of the 5QI definition.

[0176]

[0177] This application provides another method for information transmission, which optionally can be executed after method 600. The method includes:

[0178] The first network management device acquires management data from network nodes. This management data includes management data from the first integrated access backhaul (IAB) node. This management data can be fault information, performance information, or both. In other words, the first network management device can acquire fault information or performance information from the first IAB node, or it can acquire both fault information (or alarm information) and performance information from the first IAB node simultaneously.

[0179] It should be understood that network nodes can be core network nodes or base station nodes. Core network nodes can be nodes such as AMF, UPF, MME, and SGW, while base station nodes can be gNB, en-gNB, eNB, gNB-CU, gNB-DU, gNB-CU-CP, gNB-CUcell, gNB-DUcell, or gNB-CU-UP. The first network management device can be a management service producer, a management service consumer, a domain management function unit, a wireless automation engine (MBB automation engine, MAE), or an element management system (EMS). The second network management device can be a management service consumer, a management service producer, a cross-domain management function unit, or a network management system (NMS).

[0180] It should also be understood that the first network management device obtains the management data of the network node in order to prepare the data for the network node.

[0181] It should be noted that the first network management device may obtain the management data of the network node directly from the network node or through other means, and this application does not limit it here.

[0182] Specifically, the first network management device can obtain fault information and / or performance information of the first IAB node from the core network device, which can be a user plane function (UPF). The fault information and / or performance information of the first IAB node can be obtained by the UPF from the base station.

[0183] Optionally, before the first network management device acquires the management data of the network node, the second network management device may send a subscription request message to the first network management device, and the first network management device receives the subscription request message sent by the second network management device. Optionally, the subscription request message includes second indication information for indicating the acquisition of the management data of the first IAB node, and the first network management device acquires the management data of the network node according to the second indication information. Optionally, the second indication information may include the identifier of the first IAB node. Correspondingly, optionally, the second network management device may send a management data unsubscribe request message to the first network management device, and the unsubscribe request message includes third indication information for indicating the unsubscribe from the management data of the first IAB node.

[0184] It should be noted that the subscription request message can use existing operations, such as the subscribe operation, or a newly defined operation; this application does not impose any limitations on this. Similarly, the unsubscribe request message can use existing operations, such as the unsubscribe operation, or a newly defined operation; this application does not impose any limitations on this.

[0185] It should be understood that a subscription request message can be used only to subscribe to the fault information of the first IAB, or only to subscribe to the performance information of the first IAB, or to subscribe to both the fault information and performance information of the first IAB at the same time.

[0186] Optionally, before the first network management device acquires the management data of the network node, the second network management device may send an alarm information acquisition request message to the first network management device to acquire the fault information of the first IAB node. Optionally, the alarm information acquisition request message includes second indication information, used to indicate the acquisition of the fault information of the first IAB node, and the first network management device acquires the fault information of the network node according to the second indication information. Optionally, the second indication information may include the identifier of the first IAB node. It should be noted that the alarm information acquisition request message can use existing operations, such as the get alarm list operation, or newly defined operations; this application does not impose any limitations on this.

[0187] Optionally, before the first network management device acquires the management data of the network node, it may also send a data stream connection establishment indication message to the second network device, and acquire the performance information of the first IAB node based on the received data stream connection establishment success response message from the second network management device. It should be understood that this data stream connection establishment success response message is used to indicate that a data stream connection has been established between the first and second network management devices. It should be noted that the data stream connection establishment indication message can use existing operations, such as the establishstreaming connection operation, or newly defined operations; this application does not impose any limitations on this.

[0188] Optionally, the first network management device may also acquire the management data of the network nodes independently. That is, even without receiving any instruction messages, the first network management device may independently acquire the fault information and / or performance information of the first IAB node. It should be noted that the fault information of the first IAB node includes: fault information type (e.g., "communication alarm," "processing error alarm," "environmental alarm," etc.), fault start time, or fault cause, etc. The fault information of the IAB node is not limited to these; any information related to the fault can be included. The performance information of the first IAB node includes packet transmission latency, radio resource utilization, throughput, or RRC connection count, etc. The performance information of the IAB node is not limited to these; any performance-related information can be included.

[0189] The first network management device sends management data of network nodes to the second network management device, wherein the management data of network nodes includes the management data of the first IAB node.

[0190] If the management data requested by the second network management device through the subscription request message is fault information, the first network management device responds to the request and sends the fault information to the second network management device. For example, the fault information of the first IAB node can be carried in the existing notifynewalarm operation, or the fault information of the changed first IAB node can be carried in the existing notifyChangeAlarm operation, or other newly defined operations can be used. This application embodiment does not limit this in any way.

[0191] If the management data requested by the second network management device through the subscription request message is performance information, the first network management device responds to the request and sends the information that the performance information is ready to the second network management device, thereby enabling the second network management device to obtain the performance information. For example, the first network management device can send an indication that the performance information of the first IAB node is ready to the second network management device through the existing notifyFileReady operation, or it can also send an indication that the performance information of the first IAB node is ready to the second network management device through other newly defined operations. This application embodiment does not limit this in any way.

[0192] If the management data obtained by the second network management device through the alarm information request message is fault information, the first network management device responds to the request and sends the fault information to the second network management device. For example, the fault information of the first IAB node can be added to the response (e.g., output) of the existing getalarmlist operation, or it can be done through other newly defined operations. This application embodiment does not limit this in any way.

[0193] like Figure 9 The diagram illustrates an interactive schematic of an information transmission method according to an embodiment of this application. The specific steps include:

[0194] 910. The second network management device sends a subscription request message to the first network management device, requesting to subscribe to the fault information or alarm information of the first IAB node.

[0195] Specifically, the subscription operation targets core network entities, such as UPF and AMF. Optionally, in an architecture where the IAB node directly transmits data with the network management device via an IP backhaul link, the subscription operation can also target the IAB node.

[0196] Optionally, the subscription request message includes second indication information, such as an IABnodeAlarm indication, for obtaining fault information or alarm information of the first IAB node. This embodiment uses obtaining fault information as an example.

[0197] 920. The first network management device obtains the fault information of the network nodes according to the subscription request message. The fault information of the network nodes includes the fault information of the first IAB node.

[0198] At 930, the first network management device sends fault information of the network node to the second network management device.

[0199] Specifically, the first network management device sends a notifynewalarm operation to the second network management device, and the notifynewalarm message carries the fault information of the first IAB node.

[0200] Optionally, the notification of a new alarm operation may also carry the identifier of the first IAB node. The identifier of the first IAB node may exist independently in the operation or be included in the second instruction information. This application does not limit this.

[0201] 940, the second network management device receives the fault information sent by the first network management device.

[0202] In another implementation, optionally, before the first network management device obtains the management data of the network node, the second network management device may also send a "get alarm list" message to the first network management device. This message is used to obtain fault information of the first IAB node. For example... Figure 10 The diagram illustrates an interaction diagram of another information transmission method according to an embodiment of this application. The specific steps include:

[0203] 1010, the second network management device sends a getalarmlist message to the first network management device. In this operation message, an IAB node alarm acquisition instruction can be added. The instruction is used to indicate the acquisition of fault information of the first IAB node.

[0204] Specifically, the object of the alarm list acquisition operation is a core network entity, such as UPF, AMF, etc. Optionally, in an architecture where the IAB node directly transmits data with the network management device via an IP backhaul link, the object of the subscription operation can also be the IAB node.

[0205] For example, add the IABnodealarm indicator to the Input parameter of getalarmlist, or add the IABnodealarm indicator to the existing alarmAckState attribute of Input. Add IABnode fault information, such as IABnodeAlarminformation, to the Output parameter of Getalarmlist. The content of this IABnodeAlarminformation information includes the fault information type (e.g., "communication alarm," "processing error alarm," "environment alarm," etc.), the fault start time, or the fault cause, etc. The IABnode fault information is not limited to these; any information related to the fault can be included.

[0206] 1020, the first network management device obtains the fault information of the network node according to the get alarm list message, which includes the fault information of the first IAB node.

[0207] 1030, the first network management device sends the fault information of the first IAB node to the second network management device by carrying the fault information of the first IAB node in the IAB alarm information list (IABalarminformationlist) message, or by sending it to the second network management device through other newly defined messages. This application embodiment does not limit this in any way.

[0208] 1040, the second network management device receives the fault information sent by the first network management device.

[0209] In another implementation, if the management data requested by the second network management device through the subscription request message is performance information, the first network management device can also send this performance information to the second network management device through existing messages. For example, the performance information of the first IAB node can be carried in an existing notify file ready message, or it can be sent to the second network management device through a newly defined message. Figure 11 The diagram illustrates an interaction diagram of another information transmission method according to an embodiment of this application. The specific steps include:

[0210] 1110, The second network management device sends a subscription request message to the first network management device, requesting to subscribe to performance information.

[0211] Optionally, the subscription request message includes second indication information, which is used to obtain the performance information of the first IAB node;

[0212] It should be understood that the object of the subscription operation is a core network entity, such as UPF, AMF, etc. Optionally, in an architecture where the IAB node directly transmits data with the network management device via an IP backhaul link, the object of the subscription operation can also be the IAB node.

[0213] 1120, the first network management device obtains the performance information of the network node based on the received subscription request message, the performance information of the network node including the performance information of the first IAB node.

[0214] 1130, the first network management device performs a response operation, sending a notifyfileready operation to the second network management device. The notifyfileready operation carries an indication that the performance information of the first IAB node is ready (e.g., IAB performance notification).

[0215] Optionally, the notification file preparation operation includes an identifier of the first IAB node, used to indicate which first IAB node's performance data is ready.

[0216] 1140, the second network management device receives performance information sent by the first network management device.

[0217] Optionally, before the first network management device obtains the management data of the network node, it may send a data stream connection establishment request message to the second network management device. This data stream connection establishment request message is used to obtain the performance information of the first IAB node. The second network management device establishes a data stream connection with the first network management device according to the data stream connection establishment request message and sends a data stream connection establishment success response message to the first network management device. This data stream connection establishment success response message is used to indicate that a data stream connection has been established between the first network management device and the second network management device. The first network management device sends the performance information of the first IAB node to the second network management device through the data stream connection.

[0218] Specifically, if the first network management device sends the performance information of the first IAB node to the second network management device through a data stream connection, the first network management device can send the performance information to the second network management device through existing messages. For example, the first network management device can carry the performance information of the first IAB node in an existing report stream data operation message, or send it to the second network management device through a newly defined message.

[0219] like Figure 12 The diagram illustrates an interaction diagram of another information transmission method according to an embodiment of this application. The specific steps include:

[0220] 1210, the first network management device sends a data stream connection establishment request message to the second network management device. The data stream connection establishment request message can use existing operations, such as the establishstreamingconnection operation, or newly defined operations, which are not limited herein.

[0221] 1220, the second network management device establishes a data stream connection with the first network management device based on the data stream connection establishment request message.

[0222] 1230, the second network management device sends a data stream connection establishment success response message to the first network management device. This data stream connection establishment success response message is used to indicate the status of establishing a data stream connection between the first network management device and the second network management device, such as successful establishment or establishment failure.

[0223] 1240, The first network management device obtains the performance information of the first IAB node.

[0224] 1250, the first network management device sends a report stream data operation message to the second network management device through the data stream connection. The report stream data operation message includes the performance information stream of the first IAB node.

[0225] It should be noted that the performance information stream of the first IAB node can be indicated using a stream ID, or other identification information.

[0226] Optionally, the report stream data operation message may also include the identifier of the IAB node, which is used by the second network management device to identify the performance information of the first IAB node.

[0227] It should be understood that report stream data messages can use existing operations, such as the reportstreamdata operation, or newly defined operations, which are not limited herein.

[0228] Optionally, the first network management device can also add, update, or modify the performance data reporting flow information of the IAB node through operations such as addstreaminfo, updatestreaminfo, and deletestreaminfo. Optionally, the add, update, or modify operation may carry the identifier of the IAB node being added, updated, or modified.

[0229] Optionally, before the first network management device sends the data flow connection establishment instruction information to the second network management device, the second network management device may also send a create measurement job operation to the first network management device, instructing the first network management device to create a performance measurement job. For example, the create measurement job operation can be executed by the existing operation createMeasurementjob, or it can be executed by a newly defined operation; this application does not limit this. It should be noted that the operation object included in the create measurement job operation can be a core network entity, such as AMF or UPF. Optionally, in an architecture where the IAB node directly transmits data with the network management device via an IP backhaul link, the object of the subscription operation can also be the IAB node.

[0230] Optionally, if the first network management device no longer acquires the performance information of the first IAB node, or has completed acquiring it, the first network management device may also send a terminate streaming connection indication message to the second network management device. After receiving the terminate streaming connection indication message sent by the first network management device, the second network management device may terminate the data stream connection with the first network management device. 830, the second network management device receives management data of the network node sent by the first network management device. The management data of the network node includes the management data of the first access backhaul integrated IAB node, wherein the management data includes fault information and / or performance information.

[0231] In the technical solution provided in this application embodiment, the first network management device can obtain fault information and / or performance information of network nodes and send the fault information and / or performance information of network nodes to the second network management device, which can ensure the execution of services of the first IAB node and thus improve the user experience.

[0232] This application provides a communication device 1300, such as... Figure 13 The diagram shows a schematic block diagram of a communication device 1300 according to an embodiment of this application. This device can be applied to a first network management device, which can be a management service producer, a wireless automation engine (MAE), or a network element management system (EMS).

[0233] The device 1300 includes: a transceiver unit 1310, which is used to receive information about a network node sent by a second network management device, the information about the network node including information about a first access backhaul integrated IAB node.

[0234] Processing unit 1320 is used to configure information about network nodes.

[0235] Optionally, the transceiver unit 1310 is also configured to send the information of the first IAB node to the network node.

[0236] Optionally, the information of the first IAB node is the capability information of the first IAB node.

[0237] Optionally, the transceiver unit 1310 is further configured to send the information of the first IAB node to the network node, so that the network node sends the information of the first IAB node to the first IAB node.

[0238] Optionally, the network node sending information of the first IAB node to the first IAB node includes: the network node sending information of the first IAB node through a transmission link between the network node and the first IAB node, wherein the transmission link is provided by a Protocol Data Unit (PDU) session of the first IAB node.

[0239] Optionally, the transceiver unit 1310 is further configured to send first information to the second network management device, the first information being used to obtain information about the first IAB node.

[0240] Optionally, the information of the first IAB node includes at least one of the following: the identifier of the first IAB node, the length of the identifier of the first IAB node, the name of the first IAB node, the identifier of the Public Land Mobile Network (PLMN) of the first IAB node, the cell local identifier of the first IAB node, the physical cell identifier of the first IAB node, the absolute radio frequency channel number (ARFCN) of the first IAB node, the cell search synchronization signal (SSB) of the first IAB node, the bandwidth portion (BWP) of the first IAB node, the cell status of the first IAB node, the management status of the first IAB node, the Internet Protocol (IP) address of the first IAB node, the IP address of the host node of the first IAB node, or the identifier of the host node of the first IAB node.

[0241] Optionally, the second network management device can be a management service consumer or a network management system (NMS).

[0242] This application provides a communication device 1400, such as... Figure 14 The diagram illustrates a schematic block diagram of another communication device 1400 according to an embodiment of this application. This device can be applied to a second network management device, which can be a management service consumer or a network management system (NMS).

[0243] The device 1400 includes a processing unit 1410 and a transceiver unit 1420. The processing unit 1410 is used to determine information about a network node, including information about a first integrated access backhaul (IAB) node. The transceiver unit 1420 is used to send the network node information to a first network management device. Optionally, the transceiver unit 1420 is further used to receive first information sent by the first network management device, the first information being used to obtain information about the first IAB node. Optionally, the first network management device can be a management service producer, a wireless automation engine (MAE), or a network element management system (EMS).

[0244] This application provides a communication device 1500, such as... Figure 15 The diagram shows a schematic block diagram of another communication device 1500 according to an embodiment of this application. This device can be applied in a first network management device.

[0245] The device 1500 includes: an acquisition unit 1510 and a transceiver unit 1520. The acquisition unit 1510 is used to acquire management data of network nodes, including management data of a first access backhaul integrated IAB node. The transceiver unit 1520 is used to send management data of network nodes to a second network management device, wherein the management data includes fault information and / or performance information.

[0246] Optionally, the transceiver unit 1520 is further configured to receive a subscription request message from a second network management device, the subscription request message including second indication information, the second indication information being used to obtain management data of the first IAB node.

[0247] Optionally, the transceiver unit 1520 is specifically used to send fault information and / or performance information of network nodes to the second network management device via a data stream connection.

[0248] Optionally, the transceiver unit 1520 is also used to send a data stream connection establishment request message to the second network management device;

[0249] The transceiver unit 1520 is also used to receive a data stream connection establishment success response message sent by the second network management device.

[0250] Optionally, the transceiver unit 1520 is also used to send interrupted data stream connection indication information to the second network management device.

[0251] Optionally, the second indication information may include the identifier of the first IAB node.

[0252] This application provides a communication device 1600, such as... Figure 16The diagram shows a schematic block diagram of another communication device 1600 according to an embodiment of this application. This device can be applied to a second network management device.

[0253] The device 1600 includes a transceiver unit 1610 and a processing unit 1620, for receiving management data of network nodes sent by a first network management device. The management data of the network nodes includes management data of a first access backhaul integrated IAB node, and the management data includes fault information and / or performance information.

[0254] Optionally, the transceiver unit 1610 is further configured to send a subscription request message to the first network management device, the subscription request message including second indication information, the second indication information being used to obtain management data of the first IAB node.

[0255] Optionally, the transceiver unit 1610 is further configured to receive a data stream connection establishment request message sent by the first network management device, the data stream connection establishment request message being used to obtain performance information of the first IAB node; the processing unit 1620 is configured to establish a data stream connection with the first network management device according to the data stream connection establishment request message; the transceiver unit 1610 is further configured to send a data stream connection establishment success response message to the first network management device through the data stream connection, the data stream connection establishment success response message being used to indicate that a data stream connection has been established between the first network management device and the second network management device.

[0256] Optionally, the transceiver unit 1610 is specifically used to receive the performance information of the network node sent by the first network management device through the data stream connection.

[0257] Optionally, the transceiver unit 1610 is further configured to receive interrupted data stream connection indication information sent by the first network management device; and interrupt the data stream connection with the first network management device according to the interrupted data stream connection indication information.

[0258] Optionally, the second indication information may include the identifier of the first IAB node.

[0259] This application provides another schematic diagram of a communication device, used to implement the operation of the first network management device or the second network management device in the above embodiments. For example... Figure 17 As shown, the communication device includes a processor 1710 and an interface 1730. Optionally, the communication device also includes a memory 1720. The interface 1730 is used to enable communication with other devices.

[0260] The methods executed by the first network management device or the second network management device in the above embodiments can be implemented by the processor 1710 calling a program stored in memory (which can be memory 920 in the first network management device or the second network management device, or external memory). That is, the apparatus for the first network management device or the second network management device may include the processor 1710, which executes the methods executed by the first network management device or the second network management device in the above method embodiments by calling a program in memory. The processor here can be an integrated circuit with signal processing capabilities, such as a CPU. The apparatus for the first network management device or the second network management device can be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or one or more microprocessors (DSPs), or one or more FPGAs, or a combination of at least two of these integrated circuit forms. Alternatively, the above implementation methods can be combined.

[0261] Specifically, Figures 13 to 16 The functions / implementation processes of the transceiver unit, processing unit, and acquisition unit in the system can be understood through... Figure 17 The processor 1710 in the illustrated communication device calls computer-executable instructions stored in memory 1720 to implement the function. Alternatively, Figures 13 to 16 The functions / implementation processes of the processing unit and the acquisition unit in the middle can be obtained through Figure 17 The processor 1710 in the communication device shown calls computer execution instructions stored in memory 1720 to achieve this. Figures 13 to 16 The function / implementation process of the transceiver unit in the middle can be obtained through Figure 17 This is achieved through interface 1730 in the communication device shown.

[0262] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0263] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0264] The steps of the methods or algorithms described in the embodiments of this application can be directly embedded in hardware, software units executed by a processor, or a combination of both. The software units can be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be housed in an ASIC.

[0265] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0266] In one or more exemplary designs, the functions described herein can be implemented in hardware, software, firmware, or any combination of these three. If implemented in software, these functions can be stored on a computer-readable medium or transmitted on a computer-readable medium in the form of one or more instructions or code. Computer-readable media includes computer storage media and communication media that facilitate the transfer of computer programs from one location to another. Storage media can be any available media accessible to a general-purpose or special-purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store program code in the form of instructions or data structures and other formats readable by a general-purpose or special-purpose computer or processor. Furthermore, any connection can be suitably defined as a computer-readable medium, for example, if the software is transmitted from a website, server, or other remote resource via a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL), or wirelessly, such as infrared, wireless, and microwave, it is also included in the definition of a computer-readable medium. The disks and discs mentioned include compressed disks, laser discs, optical discs, Digital Versatile Discs (DVDs), floppy disks, and Blu-ray discs. Disks typically copy data magnetically, while discs typically copy data optically using lasers. Combinations of these can also be contained in computer-readable media.

[0267] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0268] It should be understood that the aforementioned memory can be integrated into the processor, or the processor and memory can be integrated on the same chip, or they can be located on different chips and connected by an interface coupling. This application does not limit this.

[0269] This application also provides a computer-readable storage medium storing a computer program for implementing the methods in the above-described method embodiments. When the computer program is run on a computer, the computer can implement the methods in the above-described method embodiments.

[0270] Furthermore, the term "and / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. The term "at least one" in this application can represent "one" and "two or more." For example, at least one of A, B, and C can represent: A existing alone, B existing alone, C existing alone, A and B existing simultaneously, A and C existing simultaneously, C and B existing simultaneously, and A, B, and C existing simultaneously.

[0271] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0272] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0273] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0275] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0276] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A method for information transmission, characterized in that, include: The first network management device receives information from a network node of the second network management device, wherein the information of the network node includes information of the first integrated access backhaul (IAB) node. The first network management device configures the information of the network nodes.

2. The method according to claim 1, characterized in that, The network nodes are core network nodes or base station nodes.

3. The method according to claim 1 or 2, characterized in that, The first network management device configures the network node information, including: The first network management device configures the information of the first IAB node in the management object of the network node.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first network management device sends the information of the first IAB node to the network node.

5. The method according to any one of claims 1 to 4, characterized in that, The information of the first IAB node is the capability information of the first IAB node.

6. The method according to claim 5, characterized in that, The capability information of the first IAB node indicates whether the network node supports the access of the first IAB node.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The first network management device sends the information of the first IAB node to the network node, and the network node is used to send the information of the first IAB node to the first IAB node.

8. The method according to claim 7, characterized in that, The network node sends information from the first IAB node to the first IAB node, including: The network node sends information about the first IAB node through a transmission link between the network node and the first IAB node, and the transmission link is provided by the protocol data unit (PDU) session of the first IAB node.

9. The method according to claim 7 or 8, characterized in that, The information of the first IAB node includes at least one of the following: The identifier of the first IAB node, the length of the identifier of the first IAB node, the name of the first IAB node, the identifier of the Public Land Mobile Network (PLMN) to which the first IAB node belongs, the cell identifier of the first IAB node, the Absolute Radio Frequency Channel Number (ARFCN) of the first IAB node, the Cell Search Synchronization Signal (SSB) of the first IAB node, the Bandwidth Part (BWP) of the first IAB node, the cell status of the first IAB node, the management status of the first IAB node, the Internet Protocol (IP) address of the first IAB node, the IP address of the host node of the first IAB node, or the identifier of the host node of the first IAB node.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: The first network management device sends first information to the second network management device, the first information being used to obtain information about the first IAB node.

11. The method according to claim 10, characterized in that, The first information includes at least one of the following: The identifier of the first IAB node, the indication information of the first IAB node, or the configuration request indication information of the first IAB node.

12. The method according to any one of claims 1 to 11, characterized in that, The first network management device is a management service provider, a wireless automation engine (MAE), or a network element management system (EMS). The second network management device is a management service consumer or a network management system (NMS).

13. A method for transmitting information, characterized in that, include: The first network management device acquires management data of the network node, including management data of the first integrated access backhaul (IAB) node. The first network management device sends management data of the network node to the second network management device, wherein the management data includes fault information and / or performance information.

14. The method according to claim 13, characterized in that, The network nodes are core network nodes or base station nodes.

15. The method according to claim 13 or 14, characterized in that, The method further includes: The first network management device receives a subscription request message from the second network management device. The subscription request message includes second indication information, which is used to obtain management data of the first IAB node.

16. The method according to claim 15, characterized in that, The second indication information includes the identifier of the first IAB node.

17. The method according to any one of claims 13 to 16, characterized in that, The first network management device sends the management data of the network node to the second network management device, including: The first network management device sends the management data of the network node to the second network management device via a data stream connection.

18. The method according to claim 17, characterized in that, Before the first network management device acquires the management data of the network node, the method further includes: The first network management device sends a data stream connection establishment request message to the second network management device; The first network management device receives a data stream connection establishment success response message sent by the second network management device.

19. The method according to claim 17 or 18, characterized in that, The method further includes: The first network management device sends an interruption data stream connection indication message to the second network management device.

20. The method according to any one of claims 13 to 19, characterized in that, The first network management device is a management service provider, a wireless automation engine (MAE), or a network element management system (EMS). The second network management device is a management service consumer or a network management system (NMS).

21. A communication system, characterized in that, Including a first network management device and a second network management device, The first network management device is configured to perform the method as described in any one of claims 1 to 12. The second network management device is used to send information about network nodes to the first network management device.

22. The communication system according to claim 21, characterized in that, The second network management device is also used to determine information about network nodes, including information about the first integrated access backhaul (IAB) node.

23. The communication system according to claim 21 or 22, characterized in that, The second network management device is further configured to receive first information sent by the first network management device, wherein the first information is used to obtain information about the first IAB node.

24. A communication system, characterized in that, Including a first network management device and a second network management device, The first network management device is configured to perform the method as described in any one of claims 13 to 20. The second network management device is used to receive management data of network nodes sent by the first network management device, wherein the management data includes fault information and / or performance information.

25. The communication system according to claim 24, characterized in that, The second network management device is further configured to send a subscription request message to the first network management device, the subscription request message including second indication information, the second indication information being used to obtain management data of the first access backhaul integrated IAB node.

26. The communication system according to claim 24 or 25, characterized in that, The second network management device is further configured to receive a data stream connection establishment request message sent by the first network management device, establish a data stream connection with the first network management device according to the data stream connection establishment request message, and send a data stream connection establishment success response message to the first network management device through the data stream connection.

27. The communication system according to any one of claims 24 to 26, characterized in that, The second network management device is specifically used for: Receive the performance information of the network node sent by the first network management device through the data stream connection.

28. A communication method, characterized in that, include: The method as described in any one of claims 1 to 12, and, The second network management device sends network node information to the first network management device.

29. The communication method according to claim 28, characterized in that, The method further includes: The second network management device determines the information of the network node, which includes the information of the first integrated access backhaul (IAB) node.

30. The communication method according to claim 28 or 29, characterized in that, The method further includes: The second network management device receives first information sent by the first network management device, the first information being used to obtain information about the first IAB node.

31. A communication method, characterized in that, include: The method as described in any one of claims 13 to 20, and, The second network management device receives management data of network nodes sent by the first network management device, wherein the management data includes fault information and / or performance information.

32. The communication method according to claim 31, characterized in that, The method further includes: The second network management device sends a subscription request message to the first network management device. The subscription request message includes second indication information, which is used to obtain management data of the first integrated access backhaul (IAB) node.

33. The communication method according to claim 31 or 32, characterized in that, The method further includes: The second network management device receives a data stream connection establishment request message sent by the first network management device, establishes a data stream connection with the first network management device according to the data stream connection establishment request message, and sends a data stream connection establishment success response message to the first network management device through the data stream connection.

34. The communication method according to any one of claims 31 to 33, characterized in that, The second network management device receives management data of network nodes sent by the first network management device, including: The second network management device receives the performance information of the network node sent by the first network management device through the data stream connection.

35. A communication device, characterized in that, Includes units for performing the method as claimed in any one of claims 1 to 20 or any one of claims 28 to 34.

36. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program; when the computer program is run on a computer, it causes the computer to perform the method as claimed in any one of claims 1 to 20 or any one of claims 28 to 34.

37. A computer program product, characterized in that, The computer program product includes one or more computer instructions that, when loaded and executed on a computer, cause the method as claimed in any one of claims 1 to 20 or any one of claims 28 to 34 to be performed.

38. A communication device, characterized in that, include: A processor, a memory, and an interface, wherein the memory is used to store computer code or instructions, the interface is used for communication, and the processor is used to invoke and execute the computer code or instructions in the memory to implement the method as claimed in any one of claims 1 to 20 or any one of claims 28 to 34.

Images