Fault management method and apparatus

Abstract

The present application discloses a fault management method and apparatus. The method comprises: receiving a first request, wherein the first request is used for requesting to perform fault management on a first service; acquiring data in response to the first request, wherein the data includes at least one of performance data, historical fault data and sensing data of the first service; and performing fault management on the first service on the basis of the data, wherein the first service is an Internet of Things service capable of ambient energy harvesting, for example, an ambient Internet of Things (AIoT) service. The Method clarifies a fault management solution related to AIoT services, which can improve AIoT service experience.

Description

A fault management method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510125289.8, filed on January 26, 2025, entitled "A Fault Management Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a fault management method and apparatus. Background Technology

[0004] The 3rd Generation Partnership Project (3GPP) defines the Ambient Internet of Things (A-IoT) technology. AIoT technology refers to the technology where terminal devices, lacking or with limited energy storage capabilities, harvest energy from the environment for communication. This harvested energy includes radio waves, light, motion, heat, or other suitable forms of energy. Services transmitted based on AIoT technology are called AIoT services. AIoT services involve multiple devices or network entities, including terminal devices, base stations, core network elements, and third-party platforms. Therefore, AIoT services are susceptible to various sources of failure, which can cause the AIoT system to fail to provide the expected service.

[0005] Existing technologies do not yet address fault management related to AIoT businesses. Summary of the Invention

[0006] This application provides a fault management method and apparatus, which clarifies a fault management scheme related to AIoT services and can improve the AIoT service experience.

[0007] Firstly, a fault management method is provided, which can be executed by a first network element or a chip in the first network element. Taking the method being executed by the first network element as an example, the method includes: receiving a first request, the first request being used to request fault management of a first service; responding to the first request, collecting data, the data including at least one of performance data, historical fault data, or sensor data of the first service; and performing fault management of the first service based on the data; wherein the first service is an environmentally powered Internet of Things (IoT) service, such as an AIoT service.

[0008] This application embodiment clarifies a fault management scheme related to AIoT services, which can realize fault management of AIoT services, thereby improving the AIoT service experience.

[0009] In one possible design, the first request includes first information, or the first network element is configured with first information, which is used to indicate the data collection rules. Accordingly, data collection includes: collecting data based on the first information.

[0010] In this way, the first network element can collect data according to the collection rules, so that the collected data can accurately characterize the features of AIoT services, thereby enabling fault management of AIoT services.

[0011] In one possible design, the data satisfies at least one of the following:

[0012] The data corresponds to the first time frame.

[0013] The data corresponds to the area within the first area;

[0014] The business type corresponding to the data is the first business type;

[0015] The terminal type corresponding to the data is the first terminal type.

[0016] Of course, the above is just an example, and the actual situation is not limited to this.

[0017] This can narrow the scope of data collection and reduce the amount of data collected, which helps to obtain more accurate fault management results.

[0018] In one possible design, the first information is used to indicate at least one of the following:

[0019] The time corresponding to the data (i.e., indicating which time period the data needs to be collected, such as the first time range);

[0020] The area corresponding to the data (i.e., indicating which areas need to generate data, such as the first area);

[0021] The business type corresponding to the data (i.e., indicating which business types of data need to be collected, such as the first business type);

[0022] The terminal type corresponding to the data (i.e., indicating which terminal types of data need to be collected, such as the first terminal type).

[0023] Of course, the above is just an example, and the actual situation is not limited to this.

[0024] This clarifies the scope of data collection, reduces the amount of data collected, and helps to obtain more accurate fault management results.

[0025] In one possible design, the data includes performance data for the primary service, which includes one or more of the following:

[0026] The number of requests for the first service;

[0027] The success rate of the first business;

[0028] The failure rate of the first business;

[0029] The read rate of the first service;

[0030] Write speed of the first service;

[0031] The accuracy rate of the first business;

[0032] Alarm information for the first service;

[0033] The number of terminals connected to the first service.

[0034] Of course, the above is just an example, and the actual situation is not limited to this.

[0035] In one possible design, the data may include performance data of the first service. In this case, the first information is used to indicate that the performance data includes one or more of the following:

[0036] The number of requests for the first service;

[0037] The success rate of the first business;

[0038] The failure rate of the first business;

[0039] The read rate of the first service;

[0040] Write speed of the first service;

[0041] The accuracy rate of the first business;

[0042] Alarm information for the first service;

[0043] The number of terminals connected to the first service.

[0044] Of course, the above is just an example, and the actual situation is not limited to this.

[0045] In this way, when it is necessary to collect network-side performance data for the primary service, the specific data collection target can be clearly defined, reducing the amount of data collected and helping to obtain more accurate fault management results.

[0046] In one possible design, in a scenario where network-side performance data of a first service is collected, data collection based on first information may include: sending a second request to a second network element, the second request including second information used to determine the performance data of the first service, the second network element being used to manage network performance; and receiving the performance data of the first service from the second network element. Optionally, sending the second request to the second network element may be based on the first information, where the second information is determined based on the first information.

[0047] In this way, network-side performance data of the first service can be obtained from the second network element, which is a simple and reliable method.

[0048] In one possible design, the data includes performance data of the first service, which includes one or more of the following: the signal reception quality of the terminal corresponding to the first service, the battery level of the terminal corresponding to the first service, or the number of times the terminal corresponding to the first service accesses the network.

[0049] In one possible design, the performance data satisfies at least one of the following:

[0050] The terminal location corresponding to the performance data is within the first location range;

[0051] The terminal identifier corresponding to the performance data is the first terminal identifier.

[0052] This allows for a further narrowing of the data collection scope and a reduction in the amount of data collected, which helps to obtain more accurate fault management results.

[0053] In one possible design, the data may include performance data of a first service, and the first information is used to indicate at least one of the following:

[0054] Performance data includes one or more of the following: the signal reception quality of the terminal corresponding to the first service, the battery level of the terminal corresponding to the first service, or the number of times the terminal corresponding to the first service accesses the network.

[0055] The terminal location corresponding to the performance data, such as the first location range;

[0056] The terminal identifier corresponding to the performance data, such as the first terminal identifier.

[0057] Of course, the above is just an example, and the actual situation is not limited to this.

[0058] In this way, when it is necessary to collect performance data on the terminal side of the primary service, the specific data collection target can be clearly defined, the amount of data collected can be reduced, and more accurate fault management results can be obtained.

[0059] In one possible design, in a scenario where performance data of the first service is collected from the terminal side, collecting data based on the first information may include: sending a third request to a third network element, the third request including third information used to determine the performance data of the first service, and the third network element used to manage terminal performance; and receiving the performance data of the first service from the third network element. Optionally, sending the third request to the third network element may be based on the first information, where the third information is determined based on the first information.

[0060] In this way, it is possible to obtain the terminal-side performance data of the first service from the third network element, which is a simple and reliable method.

[0061] In one possible design, the data includes historical fault data of the first service; the historical fault data includes one or more of the following: fault frequency, fault time, or fault area.

[0062] In one possible design, the historical fault data satisfies the following condition: the fault type corresponding to the historical fault data is the first fault type.

[0063] This allows for a further narrowing of the data collection scope and a reduction in the amount of data collected, which helps to obtain more accurate fault management results.

[0064] In one possible design, the data may include historical fault data of the first service; the first information is used to indicate at least one of the following: the fault type corresponding to the historical fault data, such as the first fault type; the historical fault data includes one or more of the following: fault frequency, fault time, or fault area.

[0065] In this way, when it is necessary to collect historical fault data for the primary service, the specific data collection objects (such as one or more of the fault frequency, fault time, or fault area) can be clearly defined, the data collection scope can be further refined (such as what type of fault data to collect historical fault data), and the amount of data collected can be further reduced, which helps to obtain more accurate fault management results.

[0066] In one possible design, in a scenario where historical fault data of the first service is collected, data collection based on the first information may include: sending a fourth request to a fourth network element, the fourth request including fourth information used to determine the historical fault data of the first service, and the fourth network element used to manage faults; and receiving the historical fault data of the first service from the fourth network element. Optionally, sending the fourth request to the fourth network element may be based on the first information, where the fourth information is determined based on the first information.

[0067] In this way, historical fault data of the first service can be obtained from the fourth network element, which is a simple and reliable method.

[0068] In one possible design, the data includes sensor data of the first service; the sensor data satisfies the following: the parameter type of the sensor data is the first parameter type.

[0069] This allows for a further narrowing of the data collection scope and a reduction in the amount of data collected, which helps to obtain more accurate fault management results.

[0070] In one possible design, the data may include sensor data of a first service; the first information is used to indicate the type of parameters contained in the sensor data, such as a first parameter type.

[0071] In this way, when it is necessary to collect sensor data for the primary service, the specific data collection object (such as parameter type) can be clearly defined, further reducing the amount of data collected and helping to obtain more accurate fault management results.

[0072] In one possible design, in the scenario of collecting sensor data for the first service, collecting data based on the first information may include: sending a fifth network request to a fifth network element, the fifth network request including fifth information used to determine the sensor data for the first service, and the fifth network element used to manage the sensor data; and receiving the sensor data for the first service from the fifth network element. Optionally, sending the fifth network request to the fifth network element may be based on the first information, whereby the fifth network information is determined based on the first information.

[0073] In this way, it is possible to obtain the sensor data of the first service from the fifth network element, which is simple and reliable.

[0074] In one possible design, fault management of services based on data may include: performing one or more of the following on the first service: fault prediction, fault location, or fault elimination based on data.

[0075] Of course, the above fault management methods are just examples, and are not limited to these in practice.

[0076] In one possible design, the result of fault prediction includes one or more of the following: fault time, fault probability, fault type, fault service type, or fault equipment information of the first service.

[0077] Of course, the above fault management methods are just examples, and are not limited to these in practice.

[0078] In one possible design, performing fault prediction on the first service based on data may include: processing the data using at least one of the following technologies: artificial intelligence (AI) / machine learning (ML), network digital twin (NDT), AI agent, world model, and MDA, to obtain fault management results.

[0079] This can improve the efficiency and accuracy of obtaining fault management results.

[0080] Secondly, a fault management method is provided. This method can be executed by a second network element or a chip in the second network element. The second network element is used to manage network performance. Taking the method being executed by the second network element as an example, the method includes: receiving a second request, the second request including second information, the second information being used to determine the performance data of a first service, the first service being an environmentally powered Internet of Things (IoT) service; obtaining the performance data of the first service according to the second request; and sending the performance data of the first service, the performance data of the first service being used for fault management of the first service.

[0081] In one possible design, the performance data satisfies at least one of the following:

[0082] The time frame corresponding to the performance data is within the first time range;

[0083] The region corresponding to the performance data is within the first region;

[0084] The business type corresponding to the performance data is the first business type;

[0085] The terminal type corresponding to the performance data is the first terminal type.

[0086] Of course, the above is just an example, and the actual situation is not limited to this.

[0087] In one possible design, the performance data includes one or more of the following:

[0088] The number of requests for the first service;

[0089] The success rate of the first business;

[0090] The failure rate of the first business;

[0091] The read rate of the first service;

[0092] Write speed of the first service;

[0093] The accuracy rate of the first business;

[0094] Alarm information for the first service;

[0095] The number of terminals connected to the first service.

[0096] Of course, the above is just an example, and the actual situation is not limited to this.

[0097] In one possible design, the second information is used to indicate at least one of the following:

[0098] The time corresponding to the performance data;

[0099] The region corresponding to the performance data;

[0100] The business type corresponding to the performance data;

[0101] The terminal type corresponding to the performance data.

[0102] The number of requests for the first service;

[0103] The success rate of the first business;

[0104] The failure rate of the first business;

[0105] The read rate of the first service;

[0106] Write speed of the first service;

[0107] The accuracy rate of the first business;

[0108] Alarm information for the first service;

[0109] The number of terminals connected to the first service.

[0110] Thirdly, a fault management method is provided. This method can be executed by a third network element or a chip in the third network element. The third network element is used to manage terminal performance. Taking the method being executed by the third network element as an example, the method includes: receiving a third request, the third request including third information, the third information being used to determine the performance data of a first service, the first service being an environmentally powered IoT service; obtaining the performance data of the first service according to the third request; sending the performance data of the first service, the performance data of the first service being used for fault management of the first service.

[0111] In one possible design, the performance data includes one or more of the following: the signal reception quality of the terminal corresponding to the first service, the battery level of the terminal corresponding to the first service, or the number of times the terminal corresponding to the first service accesses the network.

[0112] In one possible design, the performance data satisfies at least one of the following:

[0113] The terminal location corresponding to the performance data is within the first location range;

[0114] The terminal identifier corresponding to the performance data is the first terminal identifier.

[0115] In one possible design, the third information is used to indicate at least one of the following:

[0116] The time corresponding to the performance data;

[0117] The region corresponding to the performance data;

[0118] The business type corresponding to the performance data;

[0119] The terminal type corresponding to the performance data;

[0120] Performance data includes one or more of the following: the signal reception quality of the terminal corresponding to the first service, the battery level of the terminal corresponding to the first service, or the number of times the terminal corresponding to the first service accesses the network.

[0121] The terminal location corresponding to the performance data;

[0122] The terminal identifier corresponding to the performance data.

[0123] Fourthly, a fault management method is provided. This method can be executed by a fourth network element or a chip within the fourth network element. The fourth network element is used to manage faults. Taking the method being executed by the fourth network element as an example, the method includes: receiving a fourth request, the fourth request including fourth information, the fourth information being used to determine historical fault data of a first service, the first service being an environmentally powered IoT service; obtaining historical fault data of the first service according to the fourth request; and sending the historical fault data of the first service, the historical fault data of the first service being used for fault management of the first service.

[0124] In one possible design, historical fault data includes one or more of the following: fault frequency, fault time, or fault region.

[0125] In one possible design, the historical fault data satisfies the following condition: the fault type corresponding to the historical fault data is the first fault type.

[0126] In one possible design, the fourth piece of information is used to indicate at least one of the following:

[0127] The time corresponding to historical fault data;

[0128] The area corresponding to historical fault data;

[0129] The business type corresponding to historical fault data;

[0130] Terminal types corresponding to historical fault data;

[0131] Fault types corresponding to historical fault data;

[0132] Historical fault data includes one or more of the following: fault frequency, fault time, or fault area.

[0133] Fifthly, a fault management method is provided. This method can be executed by a fifth network element or a chip within the fifth network element. The fifth network element is used to manage sensor data. Taking the method being executed by the fifth network element as an example, the method includes: receiving a fifth request, the fifth request including fifth information, the fifth information being used to determine the sensor data of a first service, the first service being an environmentally powered IoT service; obtaining the sensor data of the first service according to the fifth request; and sending the sensor data of the first service, the sensor data of the first service being used for fault management of the first service.

[0134] In one possible design, the sensor data satisfies the following condition: the parameter type of the sensor data is the first parameter type.

[0135] In one possible design, the fifth piece of information is used to indicate at least one of the following:

[0136] The time corresponding to the sensor data;

[0137] The area corresponding to the sensor data;

[0138] The business type corresponding to the sensor data;

[0139] The terminal type corresponding to the sensor data;

[0140] The types of parameters included in the sensor data.

[0141] Sixthly, a fault management method is provided, which can be executed by a sixth network element or a chip in the sixth network element. Taking the method being executed by the sixth network element as an example, the method includes: sending a first request, the first request being used to request fault management for a first service, the first service being an environmentally powered Internet of Things service; and receiving the fault management result of the first service.

[0142] In one possible design, the first request includes first information, which is used to indicate the data collection rules.

[0143] In one possible design, the first information is used to indicate at least one of the following:

[0144] The time corresponding to the data (i.e., indicating which time period's data needs to be collected);

[0145] The area corresponding to the data (i.e., indicating which areas' data needs to be collected);

[0146] The business type corresponding to the data (i.e., indicating which business types of data need to be collected);

[0147] The terminal type corresponding to the data (i.e., indicating which terminal types of data need to be collected).

[0148] In one possible design, the data may include performance data of the first service. In this case, the first information is used to indicate that the performance data includes one or more of the following:

[0149] The number of requests for the first service;

[0150] The success rate of the first business;

[0151] The failure rate of the first business;

[0152] The read rate of the first service;

[0153] Write speed of the first service;

[0154] The accuracy rate of the first business;

[0155] Alarm information for the first service;

[0156] The number of terminals connected to the first service.

[0157] In one possible design, the data may include performance data of a first service, and the first information is used to indicate at least one of the following:

[0158] Performance data includes one or more of the following: signal reception quality of the terminal corresponding to the first service, battery level of the terminal corresponding to the first service, or number of accesses by the terminal corresponding to the first service.

[0159] The terminal location corresponding to the performance data;

[0160] The terminal identifier corresponding to the performance data.

[0161] In one possible design, the data may include historical fault data of the first service; the first information is used to indicate at least one of the following: the fault type corresponding to the historical fault data; the historical fault data includes one or more of the following: fault frequency, fault time, or fault area.

[0162] In one possible design, the data may include sensor data of a first service; the first information is used to indicate the type of parameters contained in the sensor data.

[0163] In one possible design, fault management includes one or more of the following: fault prediction, fault location, or fault elimination.

[0164] In one possible design, the result of fault prediction includes one or more of the following: fault time, fault probability, fault type, fault service type, or fault equipment information of the first service.

[0165] In a seventh aspect, a fault management apparatus is provided, comprising a module, unit, or technical means for performing the method described in the first aspect or any possible design of the first aspect.

[0166] For example, a fault management device may include:

[0167] The transceiver unit is used to receive a first request, which requests fault management for a first service; in response to the first request, it collects data, which includes at least one of the performance data, historical fault data, or sensor data of the first service.

[0168] The processing unit is used to perform fault management on the first service based on data; wherein the first service is an environmentally powered Internet of Things service, such as an AIoT service.

[0169] Eighthly, a fault management apparatus is provided, comprising a module, unit, or technical means for performing the method as described in the second aspect or any possible design of the second aspect.

[0170] For example, a fault management device may include:

[0171] The transceiver unit is used to receive a second request, which includes second information. The second information is used to determine the performance data of the first service, which is an environmentally powered Internet of Things (IoT) service.

[0172] The processing unit is used to obtain the performance data of the first service according to the second request;

[0173] The transceiver unit is also used to send performance data of the first service, which is used for fault management of the first service.

[0174] Ninth aspect, a fault management apparatus is provided, including modules, units or technical means for performing the methods described in the third aspect or any possible design of the third aspect.

[0175] For example, a fault management device may include:

[0176] The transceiver unit is used to receive a third request, which includes third information. The third information is used to determine the performance data of the first service, which is an environmentally powered Internet of Things service.

[0177] The processing unit is used to obtain the performance data of the first service based on the third request;

[0178] The transceiver unit is also used to send performance data of the first service, which is used for fault management of the first service.

[0179] In a tenth aspect, a fault management apparatus is provided, comprising a module, unit, or technical means for performing the method described in the fourth aspect or any possible design of the fourth aspect.

[0180] For example, a fault management device may include:

[0181] The transceiver unit is used to receive a fourth request, which includes fourth information. The fourth information is used to determine the historical fault data of the first service, which is an environmentally powered Internet of Things service.

[0182] The processing unit obtains historical fault data of the first service based on the fourth request;

[0183] The transceiver unit is also used to send historical fault data of the first service, which is used for fault management of the first service.

[0184] Eleventhly, a fault management apparatus is provided, comprising a module, unit, or technical means for performing the method described in the fifth aspect or any possible design of the fifth aspect.

[0185] For example, a fault management device may include:

[0186] The transceiver unit is used to receive the fifth request, which includes the fifth information. The fifth information is used to determine the sensor data of the first service, which is an environmentally powered Internet of Things service.

[0187] The processing unit is used to obtain the sensor data of the first service according to the fifth request;

[0188] The transceiver unit is also used to send sensor data of the first service, which is used for fault management of the first service.

[0189] In a twelfth aspect, a fault management apparatus is provided, comprising a module, unit, or technical means for performing the method described in the sixth aspect or any possible design of the sixth aspect.

[0190] For example, a fault management device may include:

[0191] The transceiver unit is used to send a first request, which requests fault management for a first service, which is an environmentally powered IoT service; and to receive the fault management results of the first service.

[0192] In a thirteenth aspect, a fault management apparatus is provided, comprising at least one processor; and a communication interface communicatively connected to the at least one processor; wherein the at least one processor executes instructions stored in a memory to cause the method described in the first aspect or any possible design of the first aspect to be executed, or to cause the method described in the second aspect or any possible design of the second aspect to be executed, or to cause the method described in the third aspect or any possible design of the third aspect to be executed, or to cause the method described in the fourth aspect or any possible design of the fourth aspect to be executed, or to cause the method described in the fifth aspect or any possible design of the fifth aspect to be executed, or to cause the method described in the sixth aspect or any possible design of the sixth aspect to be executed.

[0193] Fourteenth aspect: A computer-readable storage medium storing a computer program or instructions that, when executed by a fault management device, cause the method described in the first aspect or any possible design of the first aspect to be executed, or cause the method described in the second aspect or any possible design of the second aspect to be executed, or cause the method described in the third aspect or any possible design of the third aspect to be executed, or cause the method described in the fourth aspect or any possible design of the fourth aspect to be executed, or cause the method described in the fifth aspect or any possible design of the fifth aspect to be executed, or cause the method described in the sixth aspect or any possible design of the sixth aspect to be executed.

[0194] In a fifteenth aspect, a computer program product is provided, the computer program product storing instructions that, when run on a computer, cause the method described in the first aspect or any possible design of the first aspect to be executed, or cause the method described in the second aspect or any possible design of the second aspect to be executed, or cause the method described in the third aspect or any possible design of the third aspect to be executed, or cause the method described in the fourth aspect or any possible design of the fourth aspect to be executed, or cause the method described in the fifth aspect or any possible design of the fifth aspect to be executed, or cause the method described in the sixth aspect or any possible design of the sixth aspect to be executed.

[0195] In a sixteenth aspect, a communication system is provided, comprising the fault management apparatus described in at least one of the seventh to twelfth aspects.

[0196] The specific designs and technical effects of aspects two through sixteen above can be referred to the corresponding designs and technical effects in aspect one, and will not be repeated here. Attached Figure Description

[0197] Figure 1 is a schematic diagram of the architecture of a communication system that can be applied to an embodiment of this application;

[0198] Figures 2A to 2C are schematic diagrams of several possible management architectures provided in the embodiments of this application;

[0199] Figure 3 is a flowchart of a fault management method provided in an embodiment of this application;

[0200] Figures 4A to 4D are flowcharts of several data acquisition methods provided in the embodiments of this application;

[0201] Figures 5A to 5D are flowcharts of several specific fault management methods provided in the embodiments of this application;

[0202] Figure 6 is a structural schematic diagram of a fault management device provided in an embodiment of this application;

[0203] Figure 7 is a structural schematic diagram of a fault management device provided in an embodiment of this application. Detailed Implementation

[0204] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0205] 1. Ambient power (AMP):

[0206] Also known as AMP technology, it refers to the technology by which devices communicate by harvesting energy from different sources in the environment (such as radio waves, light, motion, heat, or other suitable energy sources).

[0207] It is understandable that terms such as environmental energy or AMP are merely exemplary names, and other naming methods may be used for this technology in specific implementations.

[0208] 2. Ambient Internet of Things (A-IoT or AIoT):

[0209] The Internet of Things (IoT) that can be powered by the environment is called the environmental IoT, such as the IoT based on AMP technology (also known as AMP IoT).

[0210] Terminal devices that can be powered by the environment can be called AIoT terminal devices, such as terminal devices that use AMP technology for communication.

[0211] Services that can be powered by the environment can be called AIoT services, or services transmitted in AIoT services can be called AIoT services, such as services transmitted using AMP technology.

[0212] In some embodiments, AIoT may also be referred to as an AIoT system (it is understood that an AIoT system may include non-AIoT terminal devices, such as ordinary active devices).

[0213] It is understandable that terms such as Environmental Internet of Things, A-IoT, or AIoT are merely exemplary names, and other naming methods may be used for this technology in specific implementations.

[0214] 3. Terminal equipment:

[0215] Terminal devices, also known as terminals, user equipment (UE), mobile stations, mobile terminals, etc., can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminal devices.

[0216] In this embodiment, the terminal device can also be a terminal device in an IoT system (i.e., an IoT device). IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. As an example, this embodiment can be applied to an AIoT system, where the terminal device can be an AIoT terminal device, also known as an AIoT terminal, AIoT device, etc. An AIoT terminal device can obtain energy from the environment and communicate with network devices, intermediate nodes, auxiliary nodes, or another terminal device.

[0217] 4. Network element:

[0218] It usually refers to the basic functional unit that constitutes a network. For example, it is an entity that can perform specific network functions, has specific functions and interfaces, and can independently complete certain network tasks or work in conjunction with other network elements to achieve complex network functions.

[0219] It is understood that in the embodiments of this application, a "network element" can exist as a standalone physical entity or be integrated into a physical entity with other functions. In specific implementations, a "network element" can also be referred to as a "network entity," "network function," "device," or "apparatus," etc. Regardless of the terminology used, they all have equivalent meanings and functions within the overall architecture, operating principle, and scope of protection of the technical solution. They can be substituted for each other without affecting the integrity and feasibility of the technical solution, so as to more comprehensively reflect the diverse implementation methods of this patented technology.

[0220] 5. Radio Access Network (RAN):

[0221] Also known as an access network, the radio access network is responsible for connecting user terminal equipment to the core network, enabling users to access the network. A radio access network includes at least one access network device.

[0222] Access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system; it can also be a module or unit that performs some of the functions of a base station, for example, a central unit (CU) or a distributed unit (DU). Access network equipment can be a macro base station, a micro base station, an indoor station, a relay node, or a donor node, etc. The embodiments of this application do not limit the specific technology or equipment form used in the access network equipment. In the embodiments of this application, a base station is used as an example of an access network equipment for description.

[0223] In one possible scenario, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be configured separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0224] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN or open RAN or ORAN) system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0225] It is understood that base stations and terminal equipment can be fixed in location or mobile. Base stations and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of base stations and terminal equipment.

[0226] The roles of base stations and terminal devices can be relative. For example, a helicopter (or drone) can be configured as a mobile base station. For terminal devices accessing the wireless access network via the helicopter (or drone), the helicopter (or drone) is a base station; however, for the base station accessed by the helicopter (or drone), the helicopter (or drone) is a terminal device. That is, the helicopter (or drone) and the base station communicate via a wireless air interface protocol. Of course, the helicopter (or drone) and the base station can also communicate via an interface protocol between base stations. In this case, the helicopter (or drone) is also a base station relative to the base station.

[0227] Communication between base stations and terminal devices, between base stations, and between terminal devices can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0228] In practical applications, access network equipment can also be called access network element, access network device, or access network, etc., without restriction.

[0229] 6. Core Network (CN): This is the core part of the network, responsible for critical functions such as high-speed data transmission and switching. The core network includes one or more core network elements, such as:

[0230] Session management function (SMF) network element: mainly used for session management, allocation and management of network protocol (IP) addresses of terminal devices, selection of manageable user equipment plane functions, policy control, or terminal points of charging function interfaces, and downlink data notification, etc.

[0231] Access and mobility management function (AMF) network elements: mainly used for mobility management and access management, such as the mobility management entity (MME) function in 4G communication networks or the AMF network element in 5G networks.

[0232] Policy control function (PCF) network elements: A unified policy framework used to guide network behavior, providing policy rule information to control plane functional network elements (such as AMF, SMF, etc.).

[0233] UDM network elements are used to handle user identification, subscription, access authentication, registration, or mobility management, etc.

[0234] Application function (AF) network elements: used for data routing affected by applications, accessing network open functions, or interacting with policy frameworks for policy control, etc.

[0235] UPF network elements are used for packet routing and forwarding, or for quality of service (QoS) processing of user plane data.

[0236] Network exposure function (NEF) network elements: used to securely expose services and capabilities provided by 3GPP network functions to the outside world.

[0237] Network repository function (NRF) network elements: used to store network function entities and their service description information, as well as support service discovery, network element entity discovery and other functions.

[0238] Data network (DN): A data network that provides business services to users. Generally, clients reside on terminal devices, while servers reside on the data network. A data network can be a private network, such as a local area network (LAN), an external network not controlled by the operator, such as the internet, or a proprietary network jointly deployed by operators, such as a network providing Internet Protocol (IP) Multimedia Core Network Subsystem (IMS) services. It can be understood that when a data network is an external network not controlled by the operator (such as the internet), it can be considered not part of the core network.

[0239] It is understandable that different network elements can be independent physical devices or integrated into the same physical device, without any restrictions.

[0240] 7. Domain: Refers to a specific area or functional module, usually an independent part or subsystem of a network. For example, according to the operator (or equipment vendor), a network can be divided into at least one domain. Devices (or network elements or entities) in the same domain correspond to the same operator (or equipment vendor), while devices (or network elements or entities) in different domains correspond to different operators (or equipment vendors).

[0241] In practice, the access network and core network can be divided into separate domains. For example, the domain in the RAN is called the RAN domain, and the domain in the core network is called the CN domain.

[0242] 8. Operations administration and maintenance (OAM) systems are a set of processes, activities, tools, and standards for operating, managing, and maintaining any system, typically applicable to telecommunications, computer networks, and computer hardware.

[0243] 9. In the embodiments of this application, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and / or c means: a exists alone, b exists alone, c exists alone, a and b exist simultaneously, b and c exist simultaneously, a and c exist simultaneously, or a, b and c exist simultaneously, where a, b, and c can be single or multiple.

[0244] The ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority or importance of multiple objects.

[0245] The above explanations are merely examples and do not constitute a limitation on these terms.

[0246] The following describes the application scenarios of the embodiments of this application.

[0247] The embodiments of this application can be applied to AIoT systems or systems that include AIoT, such as Internet of Things (IoT) systems, vehicle-to-X (V2X) systems, narrowband Internet of Things (NB-IoT) systems, etc.

[0248] The embodiments of this application can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring. For example, the embodiments of this application can be applied to devices in vehicle networking systems, or to IoT nodes and sensors in IoT systems, or to smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0249] The embodiments of this application can also be applied to LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, worldwide interoperability for microwave access (WiMAX) communication systems, long term evolution (LTE) systems, 5G communication systems, future communication systems, etc. Furthermore, the embodiments of this application can also be applied to wireless local area network systems that support IEEE 802.11ax (mobile hotspot (Wi-Fi) 6) / 802.11be (Wi-Fi 7) / 802.11bn ((Wi-Fi 68) / Wi-Fi (artificial intelligence, AI) / millimeter wave / UWB or sensing.

[0250] For example, Figure 1 is a schematic diagram of the architecture of a communication system that can be applied to an embodiment of this application. The communication system includes a wireless access network 100, a core network 200, and an operations administration and maintenance (OAM) system 300.

[0251] The radio access network 100 is primarily responsible for connecting user terminal equipment to the core network 200, enabling the terminal equipment to access the network. The radio access network 100 includes at least one access network device (or access network element or access network entity, such as a base station) and at least one terminal device. The core network 200 includes at least one core network device (or core network element). It should be understood that the access network in Figure 1 is based on the ORAN architecture, but is not limited to this in practice.

[0252] It's understandable that when the terminal device is an AIoT terminal device, it can function as a tag, and the base station can function as a reader, performing operations on the AIoT terminal device (such as inventory, sensing, tracking, or tag reading and writing). Therefore, in an AIoT scenario, the AIoT terminal device can also be called a tag, and the base station can also be called a reader.

[0253] The core network 200 is the core of the network, responsible for critical functions such as high-speed data transmission and switching. Core network 200 includes network elements such as SMF, AMF, PCF, UDM, AF, UPF, NEF, NRF, and the data network (DN). It can be understood that when the data network is an external network not controlled by the operator (such as the Internet), it can be considered not to belong to the core network.

[0254] The OAM system 300 is the network management plane of the communication system. It can operate independently of the user plane and control plane, and can interact with the access network and core network, and is responsible for the network management of the access network and core network.

[0255] In one possible implementation, the network can be divided into one or more domains. Based on this domain classification, network management can be categorized into two types: single-domain management and cross-domain management. Single-domain management refers to the management of a single domain; the system that performs single-domain management can be called a single-domain management system (or single-domain manager, etc.), and a specific implementation of a single-domain management system is, for example, an element management system (EMS). Cross-domain management refers to the management of multiple different domains; the system that performs cross-domain management can be called a cross-domain management system (or cross-domain manager, etc.), and a specific implementation of a cross-domain management system is, for example, a network management system (EMS).

[0256] For example, EMS manages equipment (or network elements) from the same operator (or equipment vendor), while NMS manages equipment (or network elements) from different operators (or equipment vendors). NMS can also handle interactions with third-party entities. Third-party entities refer to entities other than terminal equipment and operator network equipment, such as third-party servers located on the Internet.

[0257] In practical implementation, EMS can be further subdivided into EMS-RAN, which manages the RAN domain, and EMS-CN, which manages the CN domain. NMS or EMS, etc., can be physical devices or virtual machines, without restriction.

[0258] The network management plane can include producers and consumers. Consumers are the requesters, initiating service requests related to network management (such as AIoT-related service requests). Producers receive service requests, process them, obtain results, and then return the results to the requesters. Producers can also be referred to as manufacturers, producers, service providers, service providers, or service parties, while consumers can be referred to as consumers, service users, customers, or users, among other names.

[0259] See Figures 2A to 2C for illustrations of several possible management structures:

[0260] Figure 2A illustrates two possible three-tier management architectures. The three tiers are the cross-domain layer, the single-domain layer, and the device-on-user (UE) layer. The cross-domain layer is primarily responsible for cross-domain management; for example, the cross-domain layer could be the NMS. The single-domain layer is primarily responsible for single-domain management; for example, the single-domain layer could be the EMS. The consumer can reside on the NMS or on a third-party entity, and is used to initiate fault management-related requests (such as fault prediction requests). The producer resides in a single RAN domain. The producer receives requests from the consumer, collects and processes data according to the requests, and returns the processing results to the consumer.

[0261] A single-domain layer includes one or more network elements for performing network management within a single domain. These elements may include minimum drive tests (MDT), fault management (FM), performance management (PM), or an AIoT monitoring module. Specifically, the MDT manages performance data on the terminal side, FM manages faults (e.g., storing alarm information and historical fault data), the PM manages performance data on the network side (e.g., base stations, core network elements), and the AIoT monitoring module collects and manages sensor data acquired by the terminal. Optionally, the single-domain layer may also include the managed network element (or entity or device), such as a base station.

[0262] The cross-domain layer includes one or more network elements for performing network management on different domains. For example, it can uniformly manage FM, PM, etc. in different domains. It may also include configuration management, which is used to store the configuration data of each network element and device in the network.

[0263] The terminal device layer includes one or more terminal devices, such as AIoT terminal devices.

[0264] Figure 2B illustrates a possible two-tier management architecture. Compared to a three-tier management architecture, it lacks a single-domain layer, or rather, the functionality of the single-domain layer is integrated into the cross-domain layer, which can uniformly manage the network across various domains. The Consumer can reside as a third-party entity, while the Producer, MDT, PM, FM, AIoT monitoring module, etc., all reside in the cross-domain layer.

[0265] Of course, besides the three-tier and two-tier management architectures, other architectures are also possible. For example, Figure 2C shows an ORAN-based management architecture. The consumer resides in a third-party entity, while the producer, MDT, PM, FM, and AIoT monitoring module are all located within the ORAN device. The ORAN device can be, for example, a non-real-time access network intelligent controller (RIC). The non-real-time RIC is part of the ORAN architecture and is responsible for all orchestration and management of RAN components, as well as automated monitoring and control of RAN components in RAN management scenarios where execution time requirements are not high (e.g., greater than 1 second).

[0266] It is understood that in practical applications, the above network architectures may also include other network elements, and this application does not limit this.

[0267] It should be noted that the names of the network elements in this application are merely examples, and this application does not preclude the possibility of using other names for the network elements in the future, or the merging of functions between the network elements. With the evolution of technology, any device or network element capable of implementing the functions of the aforementioned network elements is within the scope of protection of this application.

[0268] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0269] The following describes the technical features involved in the embodiments of this application.

[0270] The 3rd Generation Partnership Project (3GPP) has released Technical Specification (TS) 22.261, which defines the service requirements for 5G. Section 6.48 of this TS covers AIoT. TR 23.700-13 further discusses the network topology of AIoT. AIoT data differs from traditional terminal data, interacting through the control plane. The protocol stack and identity information (ID) involved are also defined separately. TR 22.840 proposes 43 AIoT use cases and corresponding parameters, introducing different AIoT use cases, such as inventory management for warehouses and sensor-based services for agricultural and livestock health monitoring. The parameters differ for different services. The following refers to AIoT services as AIoT services.

[0271] AIoT services involve terminals, base stations (or readers), core network elements, and third-party platforms. These services are susceptible to various sources of failure, which can cause the AIoT system to fail to provide the expected service. These and related failures require extensive troubleshooting. To reduce network and service downtime and performance degradation, it is necessary to implement fault management for AIoT services.

[0272] However, there is currently no fault management solution related to AIoT business.

[0273] In view of this, the technical solution of the embodiments of this application is provided to clarify the fault management scheme related to AIoT services, so as to realize fault management of AIoT services (such as fault prediction, fault location or fault elimination, etc., one or more), which can improve the AIoT service experience.

[0274] The method provided in the embodiments of this application is described below with reference to the accompanying drawings.

[0275] Referring to Figure 3, a fault management method provided in an embodiment of this application is shown, which includes the following steps S301 to S302:

[0276] S301, the sixth network element sends the first request, and the first network element receives the first request.

[0277] The first request is used to request (or instruct) fault management for the first service.

[0278] The first business is an IoT business that can be powered by the environment, or in other words, a business where terminal devices transmit energy based on the environment. For example, the first business is the AIoT business listed above. The definition of AIoT can be found in the terminology section above, and will not be repeated here. For ease of description, the following text will use AIoT as the example, and the terms "first business" and "AIoT business" are interchangeable.

[0279] The sixth network element can be any network element capable of initiating fault management for the first service. For example, the sixth network element can be the consumer mentioned above. The sixth network element can be located within the operator's network (e.g., at the cross-domain layer) or on a third-party entity (e.g., on a third-party server on the Internet), etc., without any restrictions.

[0280] The first network element can be any network element capable of performing fault management for the first service. For example, the first network element can be the producer mentioned above. In specific implementations, the first network element can be located in the cross-domain layer, enabling fault management for the first service in different domains, or it can be located in the single-domain layer, enabling fault management for the first service in a single domain. There are no restrictions, as shown in Figures 2A to 2C.

[0281] Fault management includes, but is not limited to, at least one of the following: fault location, fault troubleshooting, or fault prediction. Fault location refers to locating the location where a fault occurs, such as pinpointing a specific terminal device or network element. Fault troubleshooting refers to finding the cause of the fault and / or resolving it. Fault prediction refers to predicting potential future faults.

[0282] S302. In response to the first request, the first network element collects data and performs fault management on the first service based on the collected data.

[0283] In one possible implementation, the first request can be a new message type corresponding to the first service (or fault management of the first service). The first network element determines to perform fault management on the first service based on the message type of the first request. In another possible implementation, the first request can reuse an existing MDA request message, carrying first indication information to indicate fault management on the first service (or to indicate the first service). The first network element determines to perform fault management on the first service based on the first indication information in the first request. This application embodiment does not limit the specific message type of the first request.

[0284] In one possible implementation, fault management defaults to at least one of fault location, fault troubleshooting, or fault prediction, for example, fault prediction by default. In another possible implementation, the first request indicates the specific fault management type; for example, the first request carries second indication information indicating that fault management is specifically fault location, fault troubleshooting, or fault prediction. In yet another possible implementation, different types of messages correspond to different fault management types, and the message type corresponding to the first request indicates whether fault management is specifically fault location, fault troubleshooting, or fault prediction.

[0285] The first network element can collect data according to data collection rules. One possible implementation is that the collection rules can be default or pre-configured; for example, the first network element may be configured with first information, which indicates the data collection rules (e.g., the first information is the collection rule). Another possible implementation is that the collection rules can be indicated by other network elements, such as the sixth network element; for example, the first request may carry first information, which indicates the data collection rules (e.g., the first information is the collection rule). Of course, the above two implementations are merely examples, and this application does not limit the way the first network element obtains data collection rules.

[0286] In practical implementation, the data collection rules can include related content such as the collection scope and / or collection objects. The collection scope refers to the range within which the first network element collects data. The scope can have multiple dimensions, such as time range (i.e., which time periods to collect data from), spatial range (i.e., which regions to collect data from), service range (i.e., which service types to collect data from), and terminal range (i.e., which terminals to collect data from). The collection objects refer to the specific parameters included in the collected data.

[0287] To facilitate understanding, the following lists several possible data types and provides examples of the data collection rules for each type:

[0288] I. Performance data of the first business.

[0289] Performance data is data used to describe the performance of the first service, including but not limited to one or more of the following: network-side performance of the first service (i.e., the performance of the first service on the network side) and terminal-side performance of the first service (i.e., the performance of the first service on the terminal side).

[0290] 1. For network-side performance data, the collection scope may include one or more of the following:

[0291] 1) The time corresponding to the performance data, such as the first time range.

[0292] Time, for example, is the time when the performance data was generated; in other words, the first piece of information can indicate which time ranges of performance data were generated and which were collected.

[0293] 2) The region corresponding to the performance data, such as the first region;

[0294] This area can refer to either a geographic location or a network location; there are no restrictions.

[0295] In other words, the initial information can indicate which areas to collect data from.

[0296] 3) The business type corresponding to the performance data, such as the first business type;

[0297] The first business type can be a broad category, such as AIoT business; it can also be a further subdivided business type within AIoT business, such as inventory management business, sensing business, or tracking business under AIoT business, without any restrictions.

[0298] In other words, the first information can instruct the collection of performance data for the first service or the first information can instruct which specific service types within the first service to collect performance data for.

[0299] 4) The terminal type corresponding to the performance data, such as the first terminal type.

[0300] In other words, the first information can indicate which terminal types to collect the performance data of the first service.

[0301] For example, in some scenarios, terminal devices can be divided into two types: AIoT terminal devices and ordinary terminal devices. The first information can indicate the AIoT terminal type, indicating that the performance data of the first service is collected for the AIoT terminal type.

[0302] For example, in some scenarios, AIoT terminal devices can be divided into the following three types:

[0303] A. Type I terminal equipment (similar to passive tags): It has no energy storage, cannot generate signals independently, and uses backscattering to transmit signals;

[0304] B. Type II terminal equipment (similar to semi-passive tags): It has energy storage but cannot generate signals independently. It uses backscattering to transmit signals, and its stored energy can amplify the reflected signals.

[0305] C. Category 3 terminal equipment (similar to active tags): It has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0306] In other words, the first information can instruct the collection of performance data of the first service for one or more terminals, including first-class terminal devices, second-class terminal devices, or third-class terminal devices.

[0307] It is understandable that the above four examples are just examples, and there can be more or fewer in practice, without any limit.

[0308] Accordingly, the first information may indicate one or more of the following:

[0309] The time frame corresponding to the performance data, such as the first time range;

[0310] The region corresponding to the performance data, such as the first region;

[0311] The business type corresponding to the performance data, such as the first business type;

[0312] The terminal type corresponding to the performance data, such as the first terminal type.

[0313] It is understood that the first piece of information may include one or more pieces of information. Each of the above items may correspond to one piece of information, or each item may correspond to multiple pieces of information, and multiple items may correspond to one piece of information. This application does not impose specific limitations. For example, time and region may be indicated by one piece of information (i.e., one piece of information indicates both time and region), or they may be indicated by two pieces of information (i.e., one piece of information indicates time, and the other piece of information indicates region).

[0314] Correspondingly, the network-side performance data collected by the first network element meets one or more of the following criteria:

[0315] The time frame corresponding to the performance data is within the first time range;

[0316] The region corresponding to the performance data is within the first region;

[0317] The business type corresponding to the performance data is the first business type;

[0318] The terminal type corresponding to the performance data is the first terminal type.

[0319] Regarding network-side performance, the data collected may include one or more of the following (correspondingly, the first information may indicate one or more of the following, and the network-side performance data collected by the first network element may include one or more of the following):

[0320] 1) Number of requests for the first service;

[0321] 2) Success rate of the first business transaction;

[0322] 3) Failure rate of the first business;

[0323] 4) Read rate of the first service;

[0324] 5) Write speed of the first service;

[0325] 6) The accuracy rate of the first business transaction;

[0326] 7) Alarm information for the first service;

[0327] 8) Number of terminals connected to the first service.

[0328] It is understandable that the above 8 types are just examples, and there can be more or fewer in practice, without any limit.

[0329] It is understood that the first piece of information may include one or more pieces of information. Each of the above items may correspond to one piece of information, or each item may correspond to multiple pieces of information, and multiple pieces of information may correspond to one piece of information. This application does not impose specific limitations. For example, the read rate and write rate may be indicated by one piece of information (i.e., one piece of information indicates both read and write rates), or they may be indicated by two pieces of information (i.e., one piece of information indicates the read rate, and the other piece of information indicates the write rate).

[0330] In one possible example, the first network element collects network-side performance data for the first service, which could be obtained from the second network element. For example, referring to Figure 4A, after receiving the first request (i.e., S301), the first network element can perform the following:

[0331] S303A: The first network element sends the second request, and the second network element receives the second request;

[0332] The second network element is used to manage network performance; for example, the second network element can be the PM listed above.

[0333] The second request includes second information used to determine the performance data of the first service (network side). For example, the second information indicates the scope of collection, the objects to be collected, etc., of the performance data of the first service (network side), without limitation.

[0334] In a specific example, a first network element sends a second request based on first information. The second information is determined based on the first information, for example, the second information includes some or all of the content in the first information. For example, the second information is used to indicate one or more of the following:

[0335] The time corresponding to the performance data of the first business;

[0336] The region corresponding to the performance data of the first business;

[0337] The service type corresponding to the performance data of the first service;

[0338] The terminal type corresponding to the performance data of the first service;

[0339] The performance data of the first service includes at least one of the following: the number of requests to the first service, the success rate of the first service, the failure rate of the first service, the read rate of the first service, the write rate of the first service, the accuracy of the first service, the alarm information of the first service, or the number of terminals connected to the first service.

[0340] For a detailed explanation of the above information, please refer to the corresponding content above, which will not be repeated here.

[0341] Optionally, the first network element may also determine the second network element based on the first information (or the data to be collected).

[0342] S303B, the second network element obtains the network-side performance data of the first service according to the second request.

[0343] As an example, the second network element locally stores the network-side performance data of the first service, and the second network element reads the network-side performance data of the first service from its local storage based on the second information.

[0344] S303C and the second network element send network-side performance data of the first service, and the first network element receives the network-side performance data of the first service.

[0345] In practical applications, the first network element and the second network element can be integrated into one physical entity, or they can be integrated into different physical entities, without restriction. When the first network element and the second network element are integrated into one physical entity, the processes shown in S303A to S303C represent the interaction between functional modules within the device.

[0346] 2. For the performance data on the terminal side, the collection scope may include one or more of the following (correspondingly, the first information may indicate one or more of the following, and the performance data on the terminal side collected by the first network element satisfies one or more of the following):

[0347] 1) The time corresponding to the performance data;

[0348] 2) The region corresponding to the performance data;

[0349] 3) The business type corresponding to the performance data;

[0350] 4) The terminal type corresponding to the performance data.

[0351] The explanations for the above items are as described above and will not be repeated here. The scope of performance data collection on the terminal side can be the same as or different from the scope of performance data collection on the network side, without any restrictions.

[0352] 5) The terminal location corresponding to the performance data, such as the first location range;

[0353] The first location range is, for example, the location of one or more AIoT terminal devices.

[0354] 6) The terminal identifier corresponding to the performance data, such as the first terminal identifier.

[0355] The first terminal identifier is, for example, the identifier of one or more AIoT terminal devices.

[0356] It is understood that the first piece of information may include one or more pieces of information. Each of the above items may correspond to one piece of information, or each item may correspond to multiple pieces of information, and multiple items may correspond to one piece of information. This application does not impose any specific restrictions.

[0357] Regarding the performance of the terminal side, the data collected may include one or more of the following (correspondingly, the first information may indicate one or more of the following, and the performance data of the terminal side collected by the first network element may include one or more of the following):

[0358] 1) Signal reception quality of terminal equipment (such as reference signal receiving quality (RSRQ) measurement, signal to interference plus noise ratio (SINR) or reference signal receiving power (RSRP), etc.);

[0359] 2) The power level of the terminal equipment;

[0360] 3) Number of times the terminal device accesses the base station (or reader).

[0361] It is understandable that the above three are just examples, and there can be more or fewer in practice, without any limit.

[0362] It is understood that the first piece of information may include one or more pieces of information. Each of the above items may correspond to one piece of information, or each item may correspond to multiple pieces of information, and multiple items may correspond to one piece of information. This application does not impose any specific restrictions.

[0363] In one possible example, the first network element collects the performance data of the terminal side of the first service, which could be obtained from a third network element. For example, referring to Figure 4B, after receiving the first request (i.e., S301), the first network element can perform the following:

[0364] S304A: The first network element sends a third request, and the third network element receives the third request;

[0365] Among them, the third network element is used to manage terminal performance. For example, the third network element can be the MDT listed above.

[0366] The third request includes third information, which is used to determine the performance data of the first service (on the terminal side). For example, the third information indicates the scope of collection, the objects to be collected, etc., of the performance data of the first service (on the terminal side), without any restrictions.

[0367] In a specific example, the first network element sends a third request based on the first information, and the third information is determined based on the first information, for example, the third information includes part or all of the content of the first information. For example, the third information is used to indicate one or more of the following:

[0368] The time corresponding to the performance data;

[0369] The region corresponding to the performance data;

[0370] The business type corresponding to the performance data;

[0371] The terminal type corresponding to the performance data.

[0372] The terminal location corresponding to the performance data;

[0373] The terminal identifier corresponding to the performance data;

[0374] Performance data includes one or more of the following: signal reception quality of the terminal device, battery power of the terminal device, or number of times the terminal device accesses the network.

[0375] For a detailed explanation of the above information, please refer to the corresponding content above, which will not be repeated here.

[0376] Optionally, the first network element may also determine the third network element based on the first information (or the data to be collected).

[0377] S304B, the third network element obtains the terminal-side performance data of the first service based on the third request.

[0378] As an example, the third network element locally stores the performance data of the terminal side of the first service, and the third network element reads the performance data of the terminal side of the first service from the local storage based on the third information.

[0379] S304C and the third network element send the terminal-side performance data of the first service, and the first network element receives the terminal-side performance data of the first service.

[0380] In practical applications, the first network element and the third network element can be integrated into one physical entity, or they can be integrated into different physical entities, without restriction. When the first network element and the third network element are integrated into one physical entity, the processes shown in S304A to S304C represent the interaction between functional modules within the device.

[0381] In practical applications, the second and third network elements can be integrated into one physical entity or into different physical entities, without restriction.

[0382] In addition, in practical applications, it is also possible not to distinguish between network-side performance data and terminal-side performance data. For example, performance data can be either network-side performance data or terminal-side performance data by default, or performance data can include both network-side and terminal-side performance data by default.

[0383] Without distinguishing between network-side performance data and terminal-side performance data, some of the above information can be combined. For example, the first piece of information indicates a time range that simultaneously encompasses both network-side and terminal-side performance data. The first network element collects both network-side and terminal-side performance data within this time range. Similar variations can be applied to other information, which will not be described in detail here.

[0384] II. Historical fault data of the first service.

[0385] Historical fault data is used to describe the specific circumstances of faults that occurred in the history of the first business (i.e., in the past).

[0386] 1. For historical fault data, the collection scope may include one or more of the following (correspondingly, the first information may indicate one or more of the following, and the historical fault data collected by the first network element satisfies one or more of the following):

[0387] 1) The time corresponding to the historical fault data, such as the generation time of the historical fault data;

[0388] In other words, the first piece of information indicates which time ranges of historical fault data were generated and which data were collected.

[0389] 2) The area corresponding to historical fault data;

[0390] This area can refer to either a geographic location or a network location; there are no restrictions.

[0391] In other words, the first information indicates which areas to collect historical fault data, or the first information indicates which areas to collect data corresponding to historical faults that occurred.

[0392] 3) The service type corresponding to historical fault data;

[0393] Similarly, the business type can be a broad category, such as AIoT business; or it can be a further subdivision of AIoT business, such as inventory management business, sensing business, tracking business, etc., without any restrictions.

[0394] In other words, the first information indicates the collection of historical fault data for the first service or the first information indicates which specific service types within the first service should be included in the collection of historical fault data.

[0395] 4) Terminal types corresponding to historical fault data.

[0396] In other words, the first information indicates which terminal types are targeted for collecting historical fault data for the first service.

[0397] The scope of historical fault data collection as defined above may be the same as or different from the scope of performance data collection on the network side / terminal side, without restriction.

[0398] 5) Fault types corresponding to historical fault data, such as the first fault type;

[0399] In other words, the first piece of information indicates which types of historical fault data are being referenced. Fault types include, for example, network outages, AIoT device damage, read / write failures, disk storage failures, etc., without limitation.

[0400] It is understood that the first piece of information may include one or more pieces of information. Each of the above items may correspond to one piece of information, or each item may correspond to multiple pieces of information, and multiple items may correspond to one piece of information. This application does not impose any specific restrictions.

[0401] 2. For historical fault data, the collection objects may include one or more of the following (correspondingly, the first information may indicate one or more of the following, and the historical fault data collected by the first network element may include one or more of the following):

[0402] 1) Failure frequency;

[0403] For example, how many failures occur per day (or per hour, per minute, or per second).

[0404] 2) Downtime;

[0405] That is, the time when the failure occurred.

[0406] 3) Fault area;

[0407] The area where the fault occurs can be a geographical area or a network area, without restriction.

[0408] Optionally, fault types can also be included in the data collection. For example, network interruption, AIoT device damage, read / write failure, disk storage failure, etc., are not limited.

[0409] It is understood that the first piece of information may include one or more pieces of information. Each of the above items may correspond to one piece of information, or each item may correspond to multiple pieces of information, and multiple items may correspond to one piece of information. This application does not impose any specific restrictions.

[0410] In one possible example, the first network element collects historical fault data for the first service, which could be obtained from the fourth network element. For example, referring to Figure 4C, after receiving the first request (i.e., S301), the first network element can perform the following:

[0411] S305A: The first network element sends the fourth request, and the fourth network element receives the fourth request;

[0412] The fourth network element is used to manage faults; for example, the fourth network element can be the FM listed above.

[0413] The fourth request includes fourth information, which is used to determine the historical fault data of the first service. For example, the fourth information indicates the scope of collection, the objects to be collected, etc., of the historical fault data of the first service, without any restrictions.

[0414] In a specific example, the first network element sends a fourth request based on the first information. The fourth information is determined based on the first information, for example, the fourth information includes some or all of the content in the first information. For example, the fourth information is used to indicate one or more of the following:

[0415] The time corresponding to historical fault data;

[0416] The area corresponding to historical fault data;

[0417] The business type corresponding to historical fault data;

[0418] Terminal types corresponding to historical fault data;

[0419] Fault types corresponding to historical fault data;

[0420] Historical fault data includes one or more of the following: fault type, fault time, fault area, or fault type.

[0421] For a detailed explanation of the above information, please refer to the corresponding content above, which will not be repeated here.

[0422] Optionally, the first network element may also determine the fourth network element based on the first information (or the data to be collected).

[0423] S305B and the fourth network element obtain historical fault data of the first service based on the fourth request.

[0424] As an example, the fourth network element locally stores the historical fault data of the first service, and the fourth network element reads the historical fault data of the first service from the local storage according to the fourth information.

[0425] The S305C and the fourth network element send historical fault data of the first service, and the first network element receives historical fault data of the first service.

[0426] In practical applications, the first network element and the fourth network element can be integrated into one physical entity, or they can be integrated into different physical entities, without restriction. When the first network element and the fourth network element are integrated into one physical entity, the processes shown in S305A to S305C represent the interaction between functional modules within the device.

[0427] In practical applications, the fourth network element, such as the second and third network elements mentioned above, can be integrated into one physical entity or into different physical entities, without restriction.

[0428] III. Sensor data from the first service.

[0429] Sensor data refers to the data collected by sensors. Sensors can be a type of AIoT device, or in other words, AIoT devices include sensors (such as temperature sensors, humidity sensors, etc.).

[0430] 1. For sensor data, the acquisition range may include one or more of the following (correspondingly, the first information may indicate one or more of the following, and the sensor data acquired by the first network element satisfies one or more of the following):

[0431] 1) The time corresponding to the sensing data, such as the time when the sensing data was generated or the time when the sensor collected the sensing data;

[0432] 2) The area corresponding to the sensor data;

[0433] This area can refer to either a geographic location or a network location; there are no restrictions.

[0434] For example, the first information can indicate which areas to collect sensor data, or the first information can indicate which areas to collect sensor data collected by sensors.

[0435] 3) The service type corresponding to the sensor data;

[0436] Similarly, the business type can be a broad category, such as AIoT business; or it can be a further subdivision of AIoT business, such as inventory management business, sensing business, tracking business, etc., without any restrictions.

[0437] For example, the first information may be used to collect sensor data for the first service or the first information may be used to instruct the collection of sensor data for the sensor service within the first service.

[0438] 4) The type of terminal corresponding to the sensor data.

[0439] For example, the first information can indicate which terminal types are for which sensor data of the first service are collected, or the first information can indicate which terminal types are for which sensor data of the first service are collected.

[0440] It is understood that the range of sensor data collection defined above may be the same as or different from the range of performance data or historical fault data collection, without restriction.

[0441] The first piece of information may include one or more pieces of information. Each of the above items may correspond to one piece of information, or each item may correspond to multiple pieces of information, and multiple items may correspond to one piece of information. This application does not impose any specific restrictions.

[0442] 2. For sensor data, the acquisition object may include the parameter type contained in the sensor data, such as the first parameter type (correspondingly, the first information can indicate the first parameter type, and the parameter type of the sensor data acquired by the first network element is the first parameter type).

[0443] For example, if the first piece of information indicates temperature and humidity, then the sensor data that needs to be collected includes temperature and humidity.

[0444] In one possible example, the first network element collects the sensor data for the first service, which could be obtained from the fifth network element. For example, referring to Figure 4D, after receiving the first request (i.e., S301), the first network element can perform the following:

[0445] S306A, the first network element sends the fifth request, and the fifth network element receives the fifth request;

[0446] The fifth network element is used to manage sensor data. For example, the fifth network element can be the AIoT monitoring module listed above.

[0447] The fifth request includes fifth information, which is used to determine the sensor data of the first service. For example, the fifth information indicates the collection range, collection objects, etc. of the sensor data of the first service, without limitation.

[0448] In a specific example, the first network element sends a fifth request based on the first information. The fifth information is determined based on the first information, for example, the fifth information includes some or all of the content in the first information. For example, the fifth information is used to indicate one or more of the following:

[0449] The time corresponding to the sensor data;

[0450] The area corresponding to the sensor data;

[0451] The business type corresponding to the sensor data;

[0452] The terminal type corresponding to the sensor data;

[0453] The types of parameters included in the sensor data.

[0454] For a detailed explanation of the above information, please refer to the corresponding content above, which will not be repeated here.

[0455] Optionally, the first network element may also determine the fifth network element based on the first information (or the data that needs to be collected).

[0456] S306B, the fifth network element obtains the sensor data of the first service according to the fifth request.

[0457] As an example, the fifth network element locally stores the sensor data of the first service, and the fifth network element reads the sensor data of the first service from the local storage according to the fifth information.

[0458] The sensor data for the first service includes the values ​​of parameters corresponding to various sensor parameter types, such as temperature and humidity values. Optionally, the sensor data for the first service may also include the identifier of the terminal device corresponding to each parameter, to distinguish which parameter corresponds to which terminal device.

[0459] S306C and the fifth network element transmit the sensor data of the first service, and the first network element receives the sensor data of the first service.

[0460] In practical applications, the first network element and the fifth network element can be integrated into one physical entity, or they can be integrated into different physical entities, without restriction. When the first network element and the fifth network element are integrated into one physical entity, the processes shown in S306A to S306C represent the interaction between functional modules within the device.

[0461] In practical applications, the fifth network element, such as the second, third, and fourth network elements mentioned above, can be integrated into one physical entity or into different physical entities, without restriction.

[0462] Figures 4A to 4D above can be executed individually or in combination, depending on the content indicated by the first information, or in other words, on the data to be collected.

[0463] Optionally, when the data to be collected needs to be obtained from multiple different network elements (e.g., the second network element, the third network element, the fourth network element, and the fifth network element), the first network element can also arrange the steps for obtaining the data (e.g., arranging the order between S303A to S306A, S303B to S306B, S303C to S306C, and S303D to S306D).

[0464] It should be noted that the performance data, historical fault data, and sensor data listed above are merely some possible examples, and are not limited to these in practice. Furthermore, the methods for classifying or clustering the various types of data or information mentioned above are only examples, and other methods may be used in actual applications, which this application does not limit.

[0465] After collecting data, the first network element can perform fault management on the first service based on the collected data. Fault management includes, but is not limited to, one or more of the following: fault prediction, fault location, or fault elimination performed by the first network element based on the data. As an example, the first network element can use at least one of the following technologies to process the data: artificial intelligence (AI) / machine learning (ML), network digital twin (NDT), AI agent, world model, and MDA, to obtain fault management results. For example, taking fault prediction as an example, the result of fault prediction can include one or more of the following: fault time (i.e., the time when a fault may occur), fault probability (i.e., the probability of a fault occurring), fault type (i.e., the possible types of faults, such as AIoT device damage, read / write failure, inventory failure, etc.), fault service type (i.e., the type of service that may experience a fault, such as inventory service or read / write service, etc.), or fault device information (i.e., information about the device that may experience a fault, such as device location, device identifier, etc.).

[0466] The above solutions clarify the fault management solutions related to AIoT services. They can accurately characterize the features of AIoT services (such as read / write services and inventory management services, which are common in AIoT services but rare or absent in ordinary terminal services). They can achieve fault management for AIoT services (such as fault prediction, fault location, or fault troubleshooting, etc.), thereby improving the AIoT service experience.

[0467] In one possible design, the fault management of the first service in this application can be used as a type of fault management in management data analytics (MDA).

[0468] In 3GPP standards (such as TS28.104), the MDA (Multi-Demand Assistance) is defined. The functions of the MDA include fault management, but this fault management is for services of ordinary terminals and does not yet cover AIoT services. It can be understood that ordinary terminals refer to terminal devices that differ from AIoT terminal devices, such as those with energy storage capabilities or large energy storage capabilities. Ordinary terminals communicate based on their own stored energy (such as battery power).

[0469] Specifically, for ordinary terminal services, consumers can request MDA functions by sending MDA requests. Specifically, different request parameters can be included in the MDA request to request different MDA functions. After executing the corresponding function, the MDA will output the corresponding result.

[0470] For example, Table 1 shows several existing parameters for the MDA request:

[0471] Table 1 MDArequest Parameters

[0472] In Table 1, each row corresponds to a type of parameter (each type of parameter may include one or more specific parameters). M indicates: mandatory; CM indicates: conditional mandatory; F indicates: true; T indicates: false; O indicates: optional.

[0473] However, the above parameters are all general parameters applicable to ordinary terminals. There are no parameters related to AIoT services, so they cannot be used for AIoT terminal devices.

[0474] Therefore, in the specific implementation of this application, the first request can be a type of MDA request, such as adding one or more parameters to Table 1 to be applicable to fault management of AIoT services. The types of added parameters include, for example, AIoT services, AIoT service performance data, AIoT service sensor data, and AIoT service historical fault data, without specific limitations. The specific implementation of the added parameters can be referred to the relevant introduction to the first information above, and will not be repeated here.

[0475] Table 2 shows examples of MDA output parameters:

[0476] Table 2 MDA output parameters

[0477] For explanations of parameters M, F, T, O, etc. in Table 2, please refer to the relevant explanations in Table 1.

[0478] Wherein, mDAType indicates the output type of MDA. Different values ​​of mDAType indicate different MDA output types. Table 3 provides an explanation of mDAType:

[0479] Table 3 mDAType

[0480] However, there are currently no output types related to AIoT services (or fault management for AIoT services).

[0481] Therefore, in the specific implementation of this application, a new value can be defined in mDAType to indicate the output type related to AIoT services (or fault management of AIoT services).

[0482] For example, a first value can be added to indicate that the output type of MDA is the fault prediction result of AIoT services; a second value can be added to indicate that the output type of MDA is the fault location result of AIoT services; a third value can be added to indicate that the output type of MDA is the fault troubleshooting result of AIoT services, and so on. This application does not limit the specific value of mDAType used to indicate AIoT services.

[0483] The above design approach requires minimal changes to the standard and has strong applicability.

[0484] To better understand the technical solution of this application, several specific examples are listed below:

[0485] Referring to Figure 5A, which is a flowchart of a specific fault management method, the following steps are included:

[0486] S501A, the sixth network element sends a first request, the first network element receives the first request, the first request includes information A and information B;

[0487] Information A indicates that network-side performance data of the first service should be collected. Optionally, Information A may also specify the scope and objects of the collection of network-side performance data of the first service (see the relevant introduction above for details, which will not be repeated here).

[0488] Information B instructs the collection of historical fault data for the first service. Optionally, Information B also specifies the scope and objects of the historical fault data collection for the first service (see the relevant introduction above for details, which will not be repeated here).

[0489] Information A and information B here correspond to the first information above.

[0490] Optionally, information A and information B can share some information, such as collection time and collection area, that is, to indicate a unified time range and area range for all data to be collected.

[0491] S502A, the first network element arranges the data acquisition steps according to the first request;

[0492] For example, it is determined that network-side performance data of the first service is collected from the second network element and historical fault data of the first service is collected from the fourth network element. The specific data collection steps are as follows: S503A to S508A.

[0493] S503A: The first network element sends a second request to the second network element, and the second network element receives the second request, which includes information A.

[0494] Information A here corresponds to information 2 above.

[0495] S504A and the second network element determine the network-side performance data of the first service based on information A;

[0496] S505A: The second network element sends network-side performance data of the first service, and the first network element receives network-side performance data of the first service.

[0497] S506A: The first network element sends a fourth request to the fourth network element, and the fourth network element receives the fourth request, which includes information B.

[0498] Information B here corresponds to information four above.

[0499] S507A and the fourth network element determine the historical fault data of the first service based on information B;

[0500] S508A and the fourth network element send historical fault data of the first service, and the first network element receives historical fault data of the first service.

[0501] It is understood that the above data collection steps are only examples and are not limited to these in practice.

[0502] S509A and the first network element perform fault prediction for the first service based on the network-side performance data and historical fault data of the first service, and output the corresponding fault prediction result for the first service.

[0503] For example, if the AIoT device corresponding to the first service experiences a significant drop in read / write speed within a reference time, and based on the historical fault data of the AIoT device, it is predicted that the AIoT device will fail after 2 hours, with the fault type being read / write failure.

[0504] For example, the first service is the inventory management service. The network-side performance data of the first service indicates that the accuracy of the inventory management service has decreased within the reference time. Combined with historical fault data, it is determined that the base station (reader) will fail within 1 hour, and the fault type is inventory management failure.

[0505] Of course, this is just an example, and the actual situation is not limited to this.

[0506] S510A: The first network element sends the fault prediction result corresponding to the first service, and the sixth network element receives the fault prediction result corresponding to the first service.

[0507] Figure 5A provides an example of a network-level fault prediction scheme for AIoT services: For network-level fault types specific to AIoT service scenarios, the first network element (such as the producer) obtains relevant data from relevant network elements (such as the second and fourth network elements) based on the request from the sixth network element (such as the consumer), which can predict network-level faults in AIoT services and improve the AIoT service experience.

[0508] Refer to Figure 5B, which is a flowchart of another specific fault management method, including the following steps:

[0509] S501B, the sixth network element sends a first request, the first network element receives the first request, the first request includes information C and information D;

[0510] Information C indicates the collection of performance data from the terminal side of the first service. Optionally, Information C also specifies the scope and objects of the collection of performance data from the terminal side of the first service (see the relevant introduction above for details, which will not be repeated here).

[0511] Information C indicates the collection of sensor data for the first service. Optionally, Information C also specifies the collection range and collection object of the sensor data for the first service (see the relevant introduction above for details, which will not be repeated here).

[0512] Information C and information D here correspond to the first information above.

[0513] Optionally, information C and information D can share some information, such as collection time and collection area, that is, to indicate a unified time range and area range for all data to be collected.

[0514] S502B, the first network element arranges the data acquisition steps according to the first request;

[0515] For example, it is determined that the performance data of the first service terminal side is collected from the third network element and the sensor data of the first service is collected from the fifth network element. The specific data collection steps are as follows: S503B to S508B.

[0516] S503B: The first network element sends a third request to the third network element, and the third network element receives the third request, which includes information C.

[0517] Information C here corresponds to the third piece of information above.

[0518] S504B, the third network element determines the terminal-side performance data of the first service based on the third information;

[0519] S505B, the third network element sends the terminal-side performance data of the first service, and the first network element receives the terminal-side performance data of the first service.

[0520] S506B: The first network element sends a fifth request to the fifth network element, and the fifth network element receives the fifth request, which includes information D.

[0521] Information D here corresponds to information five above.

[0522] S507B, the fifth network element determines the sensor data of the first service based on the fifth information;

[0523] S508B and the fifth network element send sensor data for the first service, and the first network element receives sensor data for the first service.

[0524] It is understood that the above data collection steps are only examples and are not limited to these in practice.

[0525] S509B and the first network element perform fault prediction for the first service based on the performance data and sensor data of the terminal side of the first service, and output the fault prediction result corresponding to the first service.

[0526] For example, the first service is the sensing service. The sensing data shows that the operating temperature of the AIoT terminal device is gradually rising and approaching the upper limit of the operating temperature. It can be predicted that the AIoT terminal device will malfunction in 10 minutes, and the malfunction type is damage to the AIoT terminal device.

[0527] For example, if the terminal type of the AIoT terminal device is a Class I terminal device and the primary service is inventory management, and the number of accesses by the AIoT terminal device decreases significantly within a reference time, and considering the power level of the AIoT terminal device, the possibility of power shortage for Class I terminal devices can be ruled out. It can be predicted that the Class I terminal device will fail within 1 hour, and the failure type will be read / write restricted.

[0528] Of course, this is just an example, and the actual situation is not limited to this.

[0529] S510B: The first network element sends the fault prediction result corresponding to the first service, and the sixth network element receives the fault prediction result corresponding to the first service.

[0530] Figure 5B provides an example of a scheme for predicting terminal-level faults in AIoT services: For terminal-level fault types specific to AIoT service scenarios, the first network element (such as the producer) obtains relevant data from relevant network elements (such as the third and fifth network elements) based on the request from the sixth network element (such as the consumer), which can predict terminal-level faults in AIoT services and improve the AIoT service experience.

[0531] Of course, Figures 5A to 5B above can also be implemented together, for example:

[0532] Refer to Figure 5C, which is a flowchart of another specific fault management method, including the following steps:

[0533] S501C and the sixth network element send a first request, and the first network element receives the first request. The first request includes information A, information B, information C, and information D.

[0534] The contents of information A, information B, information C, and information D are as described above and will not be repeated here.

[0535] Information A, information B, information C, and information D here correspond to the first information above.

[0536] Optionally, information A, information B, information C, and information D can share some information, such as collection time and collection area, that is, to indicate a unified time range and area range for all data to be collected.

[0537] S502C, the first network element arranges the data acquisition steps according to the first request;

[0538] For example, it is determined that network-side performance data of the first service will be collected from the second network element, historical fault data of the first service will be collected from the fourth network element, terminal-side performance data of the first service will be collected from the third network element, and sensor data of the first service will be collected from the fifth network element. The specific data collection steps are as follows: S503A to S508, A S503B to S508B.

[0539] S503A: The first network element sends a second request to the second network element, and the second network element receives the second request, which includes information A.

[0540] S504A and the second network element determine the network-side performance data of the first service based on information A;

[0541] S505A: The second network element sends network-side performance data of the first service, and the first network element receives network-side performance data of the first service.

[0542] S506A: The first network element sends a fourth request to the fourth network element, and the fourth network element receives the fourth request, which includes information B.

[0543] S507A and the fourth network element determine the historical fault data of the first service based on information B;

[0544] S508A and the fourth network element send historical fault data of the first service, and the first network element receives historical fault data of the first service.

[0545] S503B: The first network element sends a third request to the third network element, and the third network element receives the third request, which includes information C.

[0546] S504B, the third network element determines the terminal-side performance data of the first service based on the third information;

[0547] S505B, the third network element sends the terminal-side performance data of the first service, and the first network element receives the terminal-side performance data of the first service.

[0548] S506B: The first network element sends a fifth request to the fifth network element, and the fifth network element receives the fifth request, which includes information D.

[0549] S507B, the fifth network element determines the sensor data of the first service based on the fifth information;

[0550] S508B and the fifth network element send sensor data for the first service, and the first network element receives sensor data for the first service.

[0551] It is understood that the above data collection steps are only examples and are not limited to these in practice.

[0552] Based on the network-side performance data, terminal-side performance data, historical fault data, and sensor data of the first service, the S509C and the first network element perform fault prediction for the first service and output the corresponding fault prediction result for the first service.

[0553] S510C and the first network element send the fault prediction result corresponding to the first service, and the sixth network element receives the fault prediction result corresponding to the first service.

[0554] The example given in Figure 5C illustrates an overall prediction scheme for network-level and terminal-level faults in AIoT services, which can improve the AIoT service experience.

[0555] In addition, the first request may not carry the first information. The first network element has data collection rules configured locally by default, for example:

[0556] Refer to Figure 5D, which is a flowchart of another specific fault management method, including the following steps:

[0557] S501D and the sixth network element send the first request, and the first network element receives the first request;

[0558] S502D, the first network element arranges the data acquisition steps according to the first request;

[0559] For example, the first network element obtains information A, information B, information C, and information D from its local configuration, determines to collect network-side performance data of the first service from the second network element, collect historical fault data of the first service from the fourth network element, determine to collect terminal-side performance data of the first service from the third network element, and collect sensor data of the first service from the fifth network element. The specific data collection steps are, for example, S503A to S508, AS503B to S508B.

[0560] S503A: The first network element sends a second request to the second network element, and the second network element receives the second request, which includes information A.

[0561] S504A and the second network element determine the network-side performance data of the first service based on information A;

[0562] S505A: The second network element sends network-side performance data of the first service, and the first network element receives network-side performance data of the first service.

[0563] S506A: The first network element sends a fourth request to the fourth network element, and the fourth network element receives the fourth request, which includes information B.

[0564] S507A and the fourth network element determine the historical fault data of the first service based on information B;

[0565] S508A and the fourth network element send historical fault data of the first service, and the first network element receives historical fault data of the first service.

[0566] S503B: The first network element sends a third request to the third network element, and the third network element receives the third request, which includes information C.

[0567] S504B, the third network element determines the terminal-side performance data of the first service based on the third information;

[0568] S505B, the third network element sends the terminal-side performance data of the first service, and the first network element receives the terminal-side performance data of the first service.

[0569] S506B: The first network element sends a fifth request to the fifth network element, and the fifth network element receives the fifth request, which includes information D.

[0570] S507B, the fifth network element determines the sensor data of the first service based on the fifth information;

[0571] S508B and the fifth network element send sensor data for the first service, and the first network element receives sensor data for the first service.

[0572] It is understood that the above data collection steps are only examples and are not limited to these in practice.

[0573] Based on the network-side performance data, terminal-side performance data, historical fault data, and sensor data of the first service, the S509D and the first network element perform fault prediction for the first service and output the corresponding fault prediction result for the first service.

[0574] S510D and the first network element send the fault prediction result corresponding to the first service, and the sixth network element receives the fault prediction result corresponding to the first service.

[0575] The example shown in Figure 5D illustrates a comprehensive fault prediction scheme for network-level and terminal-level AIoT services, which can improve the AIoT service experience. Furthermore, it eliminates the need for a sixth network element to carry information indicating the data collection rules, thus saving signaling overhead.

[0576] It is understood that the above embodiments can be implemented individually or in combination.

[0577] The methods provided by the embodiments of this application have been described above with reference to the accompanying drawings. The apparatus provided by the embodiments of this application will be described below with reference to the accompanying drawings.

[0578] Figure 6 shows a schematic diagram of a fault management device provided in an embodiment of this application. The fault management device 600 can be one or more network elements or a circuit system of one or more network elements as described above, used to implement the method executed by the corresponding network element in the above method embodiments. For example, one such circuit system is a chip system.

[0579] The fault management device 600 includes at least one processor 601. The processor 601 can be used for internal processing within the device to implement certain control processing functions. Optionally, the processor 601 includes instructions. Optionally, the processor 601 can store data. Optionally, different processors can be independent devices, located in different physical locations, or located on different integrated circuits. Optionally, different processors can be integrated into one or more processors, for example, integrated onto one or more integrated circuits.

[0580] Optionally, the fault management device 600 includes one or more memories 603 for storing instructions. Optionally, the memories 603 may also store data. The processor and the memories may be configured separately or integrated together.

[0581] Optionally, the fault management device 600 includes a communication line 602 and at least one communication interface 604. Since the memory 603, communication line 602, and communication interface 604 are all optional, they are all represented by dashed lines in Figure 6.

[0582] Optionally, the fault management device 600 may further include a transceiver and / or an antenna. The transceiver can be used to send information to or receive information from other devices. The transceiver may be referred to as a transceiver unit, transceiver circuit, input / output interface, etc., and is used to realize the transmission and reception functions of the fault management device 600 via the antenna. Optionally, the transceiver includes a transmitter and a receiver. For example, the transmitter can be used to generate a radio frequency (RF) signal from a baseband signal, and the receiver can be used to convert the RF signal back into a baseband signal.

[0583] Processor 601 may include a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the present application.

[0584] Communication line 602 may include a path for transmitting information between the aforementioned components.

[0585] Communication interface 604 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), wired access network, etc.

[0586] The memory 603 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 603 may exist independently and be connected to the processor 601 via communication line 602. Alternatively, the memory 603 may be integrated with the processor 601.

[0587] The memory 603 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 601. The processor 601 executes the computer execution instructions stored in the memory 603, thereby implementing the steps performed by one or more network elements in the above embodiments.

[0588] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0589] In a specific implementation, as one example, processor 601 may include one or more CPUs, such as CPU0 and CPU1 in FIG6.

[0590] In a specific implementation, as one embodiment, the fault management device 600 may include multiple processors, such as processors 601 and 605 in FIG. 6. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0591] When the device shown in Figure 6 is a chip, such as a chip for a fault management device, the chip includes a processor 601 (and may also include a processor 605), a communication line 602, and a communication interface 604. Optionally, it may include a memory 603. Specifically, the communication interface 604 may be an input interface, pins, or circuits, etc. The memory 603 may be a register, cache, etc. The processor 601 and processor 605 may be a general-purpose CPU, microprocessor, ASIC, or one or more integrated circuits for controlling the execution of a program for controlling the fault management method of any of the above embodiments.

[0592] This application embodiment can divide the device into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. For example, when dividing the device into functional modules according to each function, Figure 7 is a schematic diagram of a fault management device. This device 700 can be one or more network elements involved in the above method embodiments, or a chip in one or more network elements. The device 700 includes a processing unit 702 and a transceiver unit 701.

[0593] It should be understood that the device 700 can be used to implement the steps performed by one or more network elements as described above. The relevant features can be referred to the embodiments shown in Figures 3, 4A to 4D, and 5A to 5D above, and will not be repeated here.

[0594] Optionally, the functions / implementation processes of the transceiver unit 701 and processing unit 702 in Figure 7 can be implemented by the processor 601 in Figure 6 calling computer execution instructions stored in memory 603. Alternatively, the functions / implementation processes of the processing unit 702 in Figure 7 can be implemented by the processor 601 in Figure 6 calling computer execution instructions stored in memory 603, and the functions / implementation processes of the transceiver unit 701 in Figure 7 can be implemented by the communication interface 604 in Figure 6.

[0595] Optionally, when the device 700 is a chip or circuit, the function / implementation process of the transceiver unit 701 can also be implemented through pins or circuits. Optionally, the transceiver unit 701 may include a transmitting unit and / or a receiving unit, whereby the transmitting unit implements the transmitting function and the receiving unit implements the receiving function; or, the transceiver unit 701 may be an integral module capable of implementing both transmitting and / or receiving functions. Optionally, the transceiver unit 701 can be implemented using a transceiver.

[0596] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the methods performed by one or more network elements in the aforementioned method embodiments. Thus, the functions described in the above embodiments can be implemented as software functional units and sold or used as independent products. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to it, or a part 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, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0597] This application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to perform the method executed by one or more network elements in any of the foregoing method embodiments.

[0598] This application also provides a fault management device, including a processor and an interface; the processor is used to execute the method performed by one or more network elements in any of the above method embodiments.

[0599] 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)).

[0600] 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 (DSP), 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 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.

[0601] 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 RAM, flash memory, ROM, erasable programmable read-only memory (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 the storage medium 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 disposed in an ASIC, which can be disposed in the terminal device. Optionally, the processor and storage medium can also be disposed in different components of the terminal device.

[0602] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0603] The contents of the various embodiments of this application can be referenced to each other. Unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0604] It is understood that in the embodiments of this application, one or more network elements may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples. In the embodiments of this application, other operations or variations of various operations may also be performed. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessary to execute all the operations in the embodiments of this application.

Claims

1. A fault management method characterized by, Applied to the first network element, the method includes: Receive a first request, the first request being used to request fault management for a first service, the first service being an IoT service that can be powered by the environment; In response to the first request, data is collected, including at least one of the performance data of the first service, historical fault data, or sensor data; fault management of the first service is performed based on the data.

2. The method of claim 1, wherein, The first request includes first information or the first network element is configured with first information, the first information being used to indicate the data collection rules; Data collection includes: collecting data based on the first information.

3. The method of claim 1 or 2, wherein, The data satisfies at least one of the following: The time corresponding to the data is within a first time range; The region corresponding to the data is within the first region; The business type corresponding to the data is the first business type; The terminal type corresponding to the data is the first terminal type.

4. The method according to any one of claims 1 to 3, characterized in that, The data includes performance data of the first service, and the performance data includes one or more of the following: The number of requests for the first service; The success rate of the first service; The failure rate of the first service; The read rate of the first service; The write rate of the first service; The accuracy rate of the first service; Alarm information for the first service; The number of terminals connected to the first service.

5. The method of claim 4, wherein, Data collected includes: A second request is sent to a second network element. The second request includes second information, which is used to determine the performance data of the first service. The second network element is used to manage network performance. Receive performance data of the first service from the second network element.

6. The method according to any one of claims 1 to 5, wherein, The data includes performance data of the first service, which includes one or more of the following: signal reception quality of the terminal corresponding to the first service, battery level of the terminal corresponding to the first service, or number of accesses by the terminal corresponding to the first service.

7. The method of claim 6, wherein, The performance data satisfies at least one of the following: The terminal location corresponding to the performance data is within the first location range; The terminal identifier corresponding to the performance data is the first terminal identifier.

8. The method of claim 6 or 7, wherein, Data collected includes: A third request is sent to a third network element, the third request including third information, the third information being used to determine the performance data of the first service, and the third network element being used to manage terminal performance; Receive performance data of the first service from the third network element.

9. The method according to any one of claims 1 to 8, wherein, The data includes historical fault data of the first service; the historical fault data includes one or more of the following: fault frequency, fault time, or fault region.

10. The method of claim 9, wherein, The historical fault data satisfies the following condition: the fault type corresponding to the historical fault data is the first fault type.

11. The method of claim 9 or 10, wherein, Data collected includes: A fourth request is sent to a fourth network element, the fourth request including fourth information, the fourth information being used to determine the historical fault data of the first service, and the fourth network element being used to manage faults; Receive historical fault data of the first service from the fourth network element.

12. The method of any one of claims 1-11, wherein, The data includes the sensor data of the first service; the sensor data satisfies the following condition: the parameter type of the sensor data is a first parameter type.

13. The method of claim 12, wherein, Data collected includes: Send a fifth network request to the fifth network element, the fifth network request including fifth information, the fifth information being used to determine the sensor data of the first service, and the fifth network element being used to manage the sensor data; Receive sensor data of the first service from the fifth network element.

14. The method of any one of claims 1-13, wherein, Fault management of the service based on the data includes: Based on the data, perform one or more of the following on the first service: fault prediction, fault location, or fault troubleshooting.

15. The method of claim 13, wherein, The result of the fault prediction includes one or more of the following: fault time, fault probability, fault type, fault service type, or fault equipment information of the first service.

16. The method of claim 14 or 15, wherein, Based on the data, perform fault prediction on the first service, including: The data is processed using at least one of the following techniques: Artificial Intelligence (AI / Machine Learning), Network Digital Twin (NDT), Artificial Intelligence Agent, World Model, and Management Data Analysis (MDA).

17. A fault management method characterized by, Applied to a second network element, which is used to manage network performance, the method includes: Receive a second request, the second request including second information, the second information being used to determine the performance data of the first service, the first service being an environmentally powered Internet of Things service; According to the second request, obtain the performance data of the first service, send the performance data of the first service, and use the performance data of the first service for fault management of the first service.

18. The method of claim 17, wherein, The performance data includes at least one of the following: The number of requests for the first service; The success rate of the first service; The failure rate of the first service; The read rate of the first service; The write rate of the first service; The accuracy rate of the first service; Alarm information for the first service; The number of terminals connected to the first service.

19. A fault management method characterized by, Applied to a third network element, the third network element being used to manage terminal performance, the method includes: Receive a third request, the third request including third information, the third information being used to determine the performance data of a first service, the first service being an environmentally powered Internet of Things service; According to the third request, the performance data of the first service is obtained and sent. The performance data of the first service is used for fault management of the first service.

20. The method of claim 19, wherein, The performance data includes one or more of the following: the signal reception quality of the terminal corresponding to the first service, the battery level of the terminal corresponding to the first service, or the number of times the terminal corresponding to the first service accesses the network.

21. A fault management method characterized by, Applied to a fourth network element, the fourth network element being used for fault management, the method includes: Receive a fourth request, which includes fourth information, which is used to determine the historical fault data of the first service, the first service being an IoT service that can be powered by the environment. According to the fourth request, the historical fault data of the first service is obtained and sent. The historical fault data of the first service is used for fault management of the first service.

22. The method of claim 21, wherein, The historical fault data includes one or more of the following: fault frequency, fault time, or fault region.

23. A fault management method characterized by, Applied to a fifth network element, which manages sensor data, the method includes: Receive a fifth request, which includes fifth information, which is used to determine the sensor data of the first service, which is an environmentally powered Internet of Things service. According to the fifth request, the sensor data of the first service is obtained and sent. The sensor data of the first service is used for fault management of the first service.

24. A fault management method characterized by, Applied to the sixth network element, the method includes: Send a first request, the first request being used to request fault management for a first service, the first service being an IoT service that can be powered by the environment; Receive the fault management results of the first service.

25. The method of claim 24, wherein, The fault management includes one or more of the following: fault prediction, fault location, or fault troubleshooting.

26. A fault management apparatus characterized by comprising: It includes modules for performing the method as described in any one of claims 1-16, or modules for performing the method as described in any one of claims 17-18, or modules for performing the method as described in any one of claims 19-20, or modules for performing the method as described in any one of claims 21-22, or modules for performing the method as described in claim 23, or modules for performing the method as described in any one of claims 24-25.

27. A fault management apparatus characterized by comprising: The method includes at least one processor; and a communication interface communicatively connected to the at least one processor; wherein the at least one processor executes instructions stored in a memory to cause the method as described in any one of claims 1-16 to be executed, or to cause the method as described in any one of claims 17-18 to be executed, or to cause the method as described in any one of claims 19-20 to be executed, or to cause the method as described in any one of claims 21-22 to be executed, or to cause the method as described in claim 23 to be executed, or to cause the method as described in any one of claims 24-25 to be executed.

28. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by the fault management device, cause the method described in any one of claims 1-16 to be executed, or the method described in any one of claims 17-18 to be executed, or the method described in any one of claims 19-20 to be executed, or the method described in any one of claims 21-22 to be executed, or the method described in claim 23 to be executed, or the method described in any one of claims 24-25 to be executed.

29. A computer program product, characterised in that, The computer program product stores instructions that, when executed on a computer, cause the method as described in any one of claims 1-16 to be executed, or the method as described in any one of claims 17-18 to be executed, or the method as described in any one of claims 19-20 to be executed, or the method as described in any one of claims 21-22 to be executed, or the method as described in claim 23 to be executed, or the method as described in any one of claims 24-25 to be executed.

Images