Information acquisition method and apparatus, and server, device, storage medium and chip

Abstract

The present application relates to an information acquisition method and apparatus, and a server, a device, a storage medium and a chip. The method is applied to an offset state information collection server. The method comprises: receiving trigger information which is sent by a fault injection server, wherein the trigger information is determined on the basis of fault generation information which is sent by a device in a bearer network; and acquiring offset state information of the device on the basis of the trigger information, wherein the offset state information is generated by the device on the basis of state indication information of an adjacent time node. Using the present method can improve the timeliness of determining the blast radius of a fault on a bearer network.

Description

Information acquisition method, device, server, equipment, storage medium and chip

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims priority to Chinese patent application number 202311246898.6, filed on September 25, 2023, entitled “Information Acquisition Method, Apparatus, Server, Equipment, Storage Medium and Chip,” and the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates to the field of network security technology, and in particular to an information acquisition method, apparatus, server, device, storage medium, and chip. Background Art

[0004] As Internet Protocol (IP) bearer networks evolve towards cloud-network converged infrastructure, their logic becomes increasingly complex. Any random failure can potentially have a cascading impact on the IP bearer network. Therefore, chaos engineering can be used to inject various types of failures into the IP bearer network, thereby uncovering hidden risks and assessing reliability. However, before using chaos engineering to inject failures, it is necessary to predefine the corresponding blast radius so that the impact range can be controlled. The blast radius represents the extent of the failure's impact on the bearer network.

[0005] In traditional technology, the status information of the device into which the fault is injected is mainly obtained manually, and the explosion radius is determined based on the status information of the device. However, there is a problem in that the timeliness of determining the explosion radius in traditional technology is low.

[0006] Summary of the Invention

[0007] Embodiments of the present application provide an information acquisition method, apparatus, server, device, storage medium, and chip, which can improve the timeliness of determining the blast radius of a fault on a bearer network.

[0008] In a first aspect, an information acquisition method is provided, which is applied to an offset status information collection server, and the method includes:

[0009] Receiving trigger information sent by a fault injection server; the trigger information is determined based on fault generation information sent by a device in the bearer network;

[0010] The offset status information of the device is acquired according to the trigger information; the offset status information is generated by the device based on status indicator information of adjacent time nodes.

[0011] In one embodiment, the trigger information includes a fault group identifier injected into the device and time information when the device generates a fault based on the fault group identifier.

[0012] In one embodiment, obtaining the offset status information of the device according to the trigger information includes:

[0013] When the trigger information is received, a request information is sent to the device; the request information is used to instruct the device to collect and send offset status information;

[0014] receiving the offset status information sent by the device based on the request information;

[0015] In one embodiment, the request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

[0016] In one embodiment, the method further comprises:

[0017] The explosion radius of the bearer network is determined based on the offset status information.

[0018] In a second aspect, an information acquisition method is provided, which is applied to a fault injection server, and the method includes:

[0019] Send a trigger message to the offset status information collection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network, and the trigger information is used to instruct the offset status information collection server to obtain the offset status information of the device, and the offset status information is generated by the device based on the status indicator information of adjacent time nodes.

[0020] In one embodiment, the trigger information includes a fault group identifier injected into the device and time information when the device generates a fault based on the fault group identifier.

[0021] In one embodiment, the method further comprises:

[0022] A fault mapping table is sent to the device; the fault mapping table includes at least one of the following: a fault group identifier, fault description information, a fault generation configuration command, and current time information.

[0023] In one embodiment, sending the fault mapping table to the device includes:

[0024] The fault mapping table is sent to the device based on the identification number of the device.

[0025] In one embodiment, the method further comprises:

[0026] receiving fault generation information sent by the device;

[0027] The trigger information is determined according to the fault generation information.

[0028] In a third aspect, an information acquisition method is provided, which is applied to a device in a bearer network, and the method includes:

[0029] Receiving request information sent by the offset status information collection server; the request information is determined by the offset status information collection server based on trigger information sent by the fault injection server, and the trigger information is determined based on fault generation information sent by the device;

[0030] generating, according to the request information, offset state information of the device based on state indicator information of adjacent time nodes;

[0031] The offset status information is sent to the offset status information collection server.

[0032] In one embodiment, the trigger information includes a fault group identifier pre-injected into the device and time information when the device generates a fault based on the fault group identifier.

[0033] In one embodiment, the request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

[0034] In one embodiment, before receiving the request information sent by the offset status information collection server, the method further includes:

[0035] Receive the fault mapping table sent by the fault injection server;

[0036] determining fault generation information according to the fault mapping table;

[0037] The fault generation information is sent to the fault injection server.

[0038] In one embodiment, the fault mapping table includes at least one of the following items: a fault group identifier corresponding to the device, a fault generating configuration command, fault description information, and current time information.

[0039] In one embodiment, generating the offset status information of the device based on the status indicator information of adjacent time nodes according to the request information includes:

[0040] Determine the status indicator set, the time interval, and the time interval according to the request information;

[0041] Determine first status indicator information of an indicator in the status indicator set at a first time node;

[0042] Determining a second time node adjacent to the first time node according to the time interval and the time interval, and obtaining second status indicator information of the indicator at the second time node;

[0043] The offset state information is determined according to the first state indicator information and the second state indicator information.

[0044] In a fourth aspect, an information acquisition device is provided, which is applied to an offset state information collection server, and the device includes:

[0045] A first receiving module is configured to receive trigger information sent by a fault injection server; the trigger information is determined based on fault generation information sent by a device in the bearer network;

[0046] An acquisition module is configured to acquire offset status information of the device according to the trigger information; the offset status information is generated by the device based on status indicator information of adjacent time nodes.

[0047] In a fifth aspect, an information acquisition device is provided, which is applied to a fault injection server, and the device includes:

[0048] The first sending module is used to send trigger information to the offset status information collection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network, and the trigger information is used to instruct the offset status information collection server to obtain the offset status information of the device, and the offset status information is generated by the device based on the status indicator information of adjacent time nodes.

[0049] In a sixth aspect, an information acquisition device is provided, which is applied to a device in a bearer network, and the device includes:

[0050] a third receiving module, configured to receive request information sent by the offset status information collection server; the request information is determined by the offset status information collection server based on trigger information received from the fault injection server, and the trigger information is determined based on fault generation information sent by the device;

[0051] A generating module, configured to generate offset status information of the device based on the status indicator information of adjacent time nodes according to the request information;

[0052] The third sending module is configured to send the offset status information to the offset status information collection server.

[0053] In a seventh aspect, a server for collecting offset status information is provided, comprising: a receiver and a processor;

[0054] The receiver is configured to receive trigger information sent by a fault injection server; the trigger information is determined based on fault generation information sent by a device in the bearer network;

[0055] The processor is configured to obtain offset status information of the device according to the trigger information; the offset status information is generated by the device based on status indicator information of adjacent time nodes.

[0056] In an eighth aspect, a fault injection server is provided, comprising: a transmitter;

[0057] The transmitter is used to send trigger information to the offset status information collection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network, and the trigger information is used to instruct the offset status information collection server to obtain the offset status information of the device, and the offset status information is generated by the device based on the status indicator information of adjacent time nodes.

[0058] In a ninth aspect, a device in a bearer network is provided, comprising: a receiver, a processor, and a transmitter;

[0059] The receiver is configured to receive request information sent by the offset status information collection server; the request information is determined by the offset status information collection server based on trigger information received from the fault injection server, and the trigger information is determined based on fault generation information sent by the device;

[0060] The processor is configured to generate offset status information of the device based on status indicator information of adjacent time nodes according to the request information;

[0061] The transmitter is configured to send the offset status information to the offset status information collection server.

[0062] In a tenth aspect, an information acquisition system is provided, comprising the offset status information collection server of the seventh aspect, the fault injection server of the eighth aspect, and the device in the bearer network of the ninth aspect;

[0063] The offset status information collection server is configured to execute the steps of the method described in the first aspect above;

[0064] The fault injection server is used to execute the steps of the method described in the second aspect above;

[0065] The device in the bearer network is used to execute the steps of the method described in the third aspect above.

[0066] In the eleventh aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method described in the first, second and third aspects above is implemented.

[0067] In the twelfth aspect, a chip is provided, which includes a programmable logic circuit and / or program instructions, and when the chip is running, the methods described in the first, second and third aspects above are implemented.

[0068] In a thirteenth aspect, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the methods described in the first, second and third aspects above. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, serving to explain the principles of the present application. It is obvious that the drawings described below are merely some embodiments of the present application, and a person of ordinary skill in the art can derive other drawings based on these drawings without inventive effort. In the drawings:

[0070] FIG1 is a diagram showing an application environment of an information acquisition method according to an embodiment;

[0071] FIG2 is a schematic diagram of a flow chart of an information acquisition method in one embodiment;

[0072] FIG3 is a schematic flow chart of an information acquisition method in another embodiment;

[0073] FIG4 is a schematic flow chart of an information acquisition method in another embodiment;

[0074] FIG5 is a schematic flow chart of an information acquisition method in another embodiment;

[0075] FIG6 is a schematic flow chart of an information acquisition method in another embodiment;

[0076] FIG7 is a schematic flow chart of an information acquisition method in another embodiment;

[0077] FIG8 is a schematic diagram of an information acquisition method in one embodiment;

[0078] FIG9 is a structural block diagram of an information acquisition device according to an embodiment;

[0079] FIG10 is a structural block diagram of an information acquisition device according to another embodiment;

[0080] FIG11 is a structural block diagram of an information acquisition device according to another embodiment;

[0081] FIG12 is a structural block diagram of an information acquisition device according to another embodiment;

[0082] FIG13 is a structural block diagram of an information acquisition device according to another embodiment;

[0083] FIG14 is a structural block diagram of an information acquisition device according to another embodiment;

[0084] FIG15 is a diagram showing the internal structure of a server for collecting offset status information according to an embodiment;

[0085] FIG16 is a diagram showing the internal structure of a fault injection server according to another embodiment;

[0086] FIG17 is a diagram showing the internal structure of a device in a bearer network in another embodiment. DETAILED DESCRIPTION

[0087] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0088] FIG1 is a schematic diagram of an application scenario for information acquisition provided by an embodiment of the present application. As shown in FIG1 , the scenario includes an offset state information collection server 100, a fault injection server 200, and a device 300 in the bearer network. The offset state information collection server 100 transmits data with the fault injection server 200 and the device 300 in the bearer network respectively through the network, and the fault injection server 200 transmits data with the device 300 in the bearer network through the network. The fault injection server 200 is used to inject faults into the device 300 in the bearer network, and determines trigger information based on the fault generation information sent by the device 300 in the bearer network, and sends the trigger information to the offset state information collection server 100. The offset state information collection server 100 is used to generate request information based on the trigger information, and send the request information to the device 300 in the bearer network to receive the offset state information sent by the device 300 in the bearer network.

[0089] As IP bearer networks evolve towards their ultimate goal of becoming cloud-network converged infrastructures, they are becoming increasingly complex. For example, these networks require interconnection and resource sharing between virtual and real devices, interoperability between new and legacy network architectures and routing solutions, management of diverse cloud networks, and scaling and open-source cloud networks. Random failures can have cascading impacts on the IP bearer network. Therefore, proactive risk detection and reliability assessment of evolving IP bearer networks are crucial. Chaos engineering can effectively address these issues by randomly injecting various types of failures into the IP bearer network to identify and address potential risks. Before injecting a failure, chaos engineering requires pre-determining the blast radius that represents the impact of the failure on the bearer network, ensuring that the impact can be controlled.

[0090] In traditional technology, the size of the explosion radius is usually determined based on theoretical knowledge and historical experience of experts. However, the granularity of the explosion radius determined by this method is large and the accuracy is low. Alternatively, by injecting a fault into a device in the IP bearer network, such as a router, and manually logging into each device and typing in a fault generation command, after the fault is generated, the information collection server is manually controlled to obtain the operating status of each device, thereby determining the impact range of the injected fault on the bearer network based on the operating status of each device. However, for large-scale networks, this method requires manual injection of fault generation commands and manual control of the collection of device operating status, resulting in low efficiency in collecting device operating status, which leads to low efficiency in determining the explosion radius. Based on this, there is a problem in the traditional technology of low timeliness in determining the explosion radius of the fault on the bearer network.

[0091] Based on the above-mentioned traditional technology, an embodiment of the present application provides an information acquisition method, which receives trigger information sent by a fault injection server. Since the trigger information is determined based on the fault generation information sent by the device in the bearer network, the offset status information collection server can obtain the offset status information generated by the device based on the status indicator information of adjacent time nodes according to the trigger information. Compared with the traditional technology, there is no need to manually control the offset status information collection server to obtain the offset status information when the fault generation is determined. It can trigger the operation of obtaining the offset status information generated by the device according to the trigger information, thereby saving the time for obtaining the offset status information, improving the efficiency of obtaining the offset status information, and further improving the timeliness of determining the explosion radius of the fault on the bearer network based on the obtained offset status information.

[0092] It should be noted that the beneficial effects or technical problems solved by the embodiments of the present application are not limited to this one, but may also include other implicit or related problems. For details, please refer to the description of the following embodiments.

[0093] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0094] In one embodiment, as shown in FIG2 , a method for obtaining information is provided. The method is described by taking the method applied to the offset state information collection server in FIG1 as an example, and includes the following steps:

[0095] S201, receiving trigger information sent by a fault injection server; the trigger information is determined according to fault generation information sent by a device in the bearer network.

[0096] The fault injection server randomly injects various preset faults into devices in the bearer network through human control, thereby causing damage to the devices in the bearer network and testing the operating status of the devices under the preset fault conditions. Optionally, the fault injection server can be a server, or a terminal, etc. In this embodiment, after the preset fault is injected into the devices in the bearer network by the fault injection server, the devices in the bearer network will send fault generation information after the fault is generated. The trigger information can be generated by the fault injection server based on the fault generation information sent by the devices in the bearer network after receiving it. Optionally, the devices in the bearer network can include routers, storage devices, switches, servers, etc. As an optional implementation method, the bearer network can include one device or multiple devices, which is not limited in this embodiment. Therefore, the fault injection server can inject different faults into different devices according to actual needs, and the fault injection server can generate trigger information for different devices based on the different fault generation information received.

[0097] As an optional implementation, the trigger information may include the fault group identifier of the injected device and the time information when the device generates the fault based on the fault group identifier. The fault group identifier is identification information used to distinguish the fault type. It is understandable that different numbers can be used as identifiers for different faults, and the faults can be pre-classified into different fault groups based on the type of each fault. Faults corresponding to different fault group identifiers can be injected into different devices according to actual needs. Optionally, a fault group can include one fault, or a fault group can include multiple faults. Optionally, the fault injection server can inject one fault group into a device, or the fault injection server can inject multiple fault groups into a device.

[0098] It can be understood that when a device generates a fault, the device can record the identifier of the fault and the generation time of the fault, and determine the identifier of the fault, the fault group identifier corresponding to the fault, and the generation time of the fault as the fault generation information, and send the fault generation information to the fault injection server, so that the offset status information collection server can receive the trigger information generated by the fault injection server based on the fault generation information.

[0099] In this embodiment, the fault injection server can compare the corresponding fault in the received fault generation information with the fault of the injected device when receiving the fault generation information sent by the device, and determine whether the faults of all injected devices are generated based on the comparison results. If the faults of all injected devices are generated, the trigger information is determined based on the fault generation information. The determined trigger information may include the fault group identifier of the injected device and the time information when the device generates the fault based on the fault group identifier.

[0100] S202 , obtaining offset status information of the device according to the trigger information; the offset status information is generated by the device based on status indicator information of adjacent time nodes.

[0101] Among them, the offset state information refers to the difference information of the state indicator information corresponding to the device at different time nodes. According to the offset state information, the change in the operating state of the device into which the fault is injected can be determined. In this embodiment, the offset state information can be obtained by obtaining the state indicator information corresponding to the device at adjacent time nodes based on a preset state indicator, comparing the two sets of state indicator information, and determining it based on the comparison result. It is understandable that different faults may correspond to different state indicator information, and injecting different types of faults into the device may also affect different state information. Optionally, the state indicator information may include the throughput, storage capacity, utilization rate of the device, as well as information such as the delay, jitter, and packet loss of the device during data transmission.

[0102] In this embodiment, the offset status information collection server can respond to the trigger information when it receives the trigger information, thereby triggering the acquisition operation of the offset status information. Optionally, the offset status information collection server can send an acquisition message of the offset status information to the device in the bearer network through the network. When the device in the bearer network receives the acquisition message sent by the offset status information collection server, it can obtain the status indicator information corresponding to the device at adjacent time nodes according to the operating status of the device, obtain the offset status information based on the status indicator information of the adjacent time nodes, and send it to the offset status information collection server through the network, so that the offset status information collection server can obtain the offset status information of the device.

[0103] In the above-mentioned information acquisition method, the offset status information collection server receives the trigger information sent by the fault injection server. Since the trigger information is determined based on the fault generation information sent by the device in the bearer network, the offset status information collection server can obtain the offset status information generated by the device based on the status indicator information of adjacent time nodes according to the trigger information. Compared with traditional technologies, there is no need to manually control the offset status information collection server to obtain the offset status information when the fault generation is determined. It can trigger the operation of obtaining the offset status information generated by the device according to the trigger information, thereby saving the time for obtaining the offset status information, improving the efficiency of obtaining the offset status information, and further improving the timeliness of determining the explosion radius of the fault on the bearer network based on the obtained offset status information.

[0104] In the above scenario of obtaining the offset status information of the device based on the trigger information, the offset status information collection server can send a request message to the device upon receiving the trigger information, thereby obtaining the offset status information sent by the device. In one embodiment, as shown in FIG3 , the above S202 includes:

[0105] S301: When trigger information is received, a request message is sent to the device; the request message is used to instruct the device to collect and send offset status information.

[0106] Among them, the request information refers to the request information that the offset status information collection server sends to the device to obtain the offset status information, so that the device can collect the operating status of the corresponding device according to the request message when receiving the request information, obtain the offset status information according to the operating status of the device and send it to the offset status information collection server.

[0107] As an optional implementation, the request information may include at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

[0108] It should be noted that the operating status of the equipment affected by different faults may be different. Therefore, for different faults, it is necessary to collect status indicator information corresponding to different faults. In this embodiment, the corresponding indicator set identifier can be determined in advance based on the fault type of the injected device, so that the corresponding status indicator set identifier and the status indicator set corresponding to the device are sent to the device through the request message sent. For example, if the bearer network includes multiple devices, the status indicator set identifier corresponding to each device can be determined in advance based on the fault group injected into each device, so that the determined status indicator set identifier and the status indicator set corresponding to the status indicator set identifier are sent to the corresponding device through the request message.

[0109] It should be noted that in order to ensure the timeliness and effectiveness of the acquired offset status information, the time for the device to collect the offset status information can be limited. Therefore, the time interval for acquiring the offset status information and the time interval for acquiring the offset status information can be included in the request message. It is understandable that the corresponding time intervals and time intervals may also be different for different status indicator sets. Therefore, the corresponding preset time intervals and preset time intervals can be determined based on the status indicator set corresponding to each device. For example, if it is necessary to collect the offset status information of the injected fault device at night, the preset time interval can be set to 20:00-21:00, and the preset time interval can be set to 5s, so that the preset time interval and time interval can be sent to the corresponding device through the request message.

[0110] In this embodiment, the offset status information collection server can respond to the trigger information when it receives the trigger information, so that under the trigger of the trigger information, it can generate a request message according to the status indicator set identifier of the device, the status indicator set corresponding to the status indicator set identifier, the preset time interval corresponding to the status indicator set, and the preset time interval corresponding to the status indicator set, and send the request message to the device through the network, so as to receive the offset status information collected and sent by the device based on the request message. It should be noted that when the offset status information collection server receives the trigger information, it can generate a request message in real time based on the trigger information.

[0111] S302: Receive offset status information sent by the device based on the request information.

[0112] In this embodiment, the offset status information collection server can receive the offset status information sent by the device in the bearer network under the instruction of the request information, and collect the offset status information generated during the operation of the device. For example, if the status indicator set included in the request message includes the throughput of the device and the delay of data transmission, the preset time interval is 20:00-21:00, and the preset time interval is 5s, then the device can obtain the throughput and data transmission delay information of the device every 5s from 20:00 to 21:00 based on the request message, and calculate the difference between the throughput and data transmission delay information corresponding to two adjacent time nodes, and use the difference as the initial offset status information, thereby sending all the initial offset status information from 20:00 to 21:00 as offset status information to the offset status information collection server.

[0113] In this embodiment, when the offset status information collection server receives trigger information, it can trigger the offset status information collection server to send request information to the device, so that the device can collect and send offset status information according to the instructions of the request information. Since the offset status information collection server can trigger the sending of a request message for offset status information to the device according to the trigger information, it avoids manual control of the offset status information collection server sending a request message to increase the time for obtaining information, thereby saving the time for the receiving device to send the offset status information based on the request information, and improving the efficiency of obtaining the offset status information of the device.

[0114] Based on the above-mentioned acquisition of the device offset status information, in order to further ensure the impact of the device failure in the bearer network, the blast radius of the failure on the bearer network can also be determined based on the offset status information. In one embodiment, the above-mentioned method further includes: determining the blast radius of the bearer network based on the offset status information.

[0115] The explosion radius of the bearer network refers to the range of the impact on the bearer network caused by the equipment in the bearer network when a fault occurs. In this embodiment, the offset status information collection server can send the offset status information to the offset status information analysis module for analysis after receiving the offset status information, so as to obtain the range of the impact of the fault injected into the device on the bearer network based on the offset status information, that is, determine the explosion radius of the bearer network. It can be understood that if the offset status information indicates that the deviation of the operating state of the device after the fault is generated is greater, it means that the explosion radius is larger; if the offset status information indicates that the deviation of the operating state of the device after the fault is generated is smaller, it means that the explosion radius is smaller.

[0116] In this embodiment, the explosion radius of the bearer network is determined based on the offset status information. Since the offset status information is obtained after the offset status information collection server sends a request information to the device according to the trigger information, compared with the traditional technology, the offset status information can be obtained more quickly, and the efficiency of obtaining the offset status information is improved, thereby improving the timeliness of determining the explosion radius of the bearer network based on the offset status information.

[0117] In one embodiment, an information acquisition method is also provided, which is illustrated by taking the method applied to the fault injection server in Figure 1 as an example. The method includes: sending trigger information to the offset status information collection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network, and the trigger information is used to instruct the offset status information collection server to obtain the offset status information of the device, and the offset status information is generated by the device based on the status indicator information of adjacent time nodes.

[0118] Among them, the offset status information collection server is a device for collecting offset status information corresponding to the equipment of the bearer network. Optionally, the offset status information collection server can be a server, or the offset status information collection server can also be a terminal. In this embodiment, the trigger information can be that the fault injection server injects a preset fault into the equipment in the bearer network, thereby receiving the fault generation information sent by the equipment in the bearer network after the fault is generated, and is generated according to the fault generation information. Optionally, the equipment of the bearer network may include routers, storage devices, switches, servers, etc. The bearer network may include one device or multiple devices. This embodiment does not limit this. Therefore, the fault injection server can inject different faults into different devices according to actual needs, thereby determining the trigger information according to different fault generation information.

[0119] As an optional implementation, the trigger information may include the fault group identifier of the injected device and the time information when the device generates the fault based on the fault group identifier. The fault group identifier is identification information used to distinguish the fault type. It is understandable that different numbers can be used as identifiers for different faults, and the faults can be pre-classified into different fault groups according to their types. Faults corresponding to different fault group identifiers can be injected into different devices according to actual needs. Optionally, a fault group can include one fault, or a group leader group can include multiple faults. Optionally, the fault injection server can inject one fault group into a device, or the fault injection server can inject multiple fault groups into a device.

[0120] It can be understood that when a fault is generated in the device, the device can record the identifier of the fault and the generation time of the fault, and determine the identifier of the fault, the fault group identifier corresponding to the fault, and the generation time of the fault as the fault generation information, and send the fault generation information to the fault injection server. The fault injection server can determine the trigger information based on the received fault generation information and send the trigger information to the offset status information collection server.

[0121] In this embodiment, the fault injection server can compare the corresponding fault in the received fault generation information with the fault of the injected device when receiving the fault generation information sent by the device, and determine whether the faults of all injected devices are generated based on the comparison results. If the faults of all injected devices are generated, the trigger information is determined based on the fault generation information, and the trigger information is sent to the offset status information collection server, which can instruct the offset status information collection server to obtain the offset status information generated by the device based on the status indicator information of adjacent time nodes.

[0122] In the above-mentioned information acquisition method, the fault injection server can instruct the offset status information collection server to obtain the offset status information generated by the device based on the status indicator information of adjacent time nodes by sending trigger information determined according to the fault generation information sent by the device in the bearer network to the offset status information collection server. Since the offset status information collection server can be triggered to obtain the offset status information according to the trigger information, compared with traditional technologies, there is no need for manual control of the offset status information collection server to obtain the offset status information, which can save the time of obtaining the offset status information, thereby improving the timeliness of the explosion radius determined according to the offset status information.

[0123] In the scenario where the fault injection server determines trigger information based on fault generation information sent by a device in the bearer network, the fault injection server can inject the fault into the device by sending a fault mapping table to the device. In one embodiment, the method further includes: sending the fault mapping table to the device; the fault mapping table includes at least one of the following: a fault group identifier, fault description information, a fault generation configuration command, and current time information.

[0124] Among them, the fault mapping table can be used to represent the correspondence between fault groups and devices. Optionally, the fault group and the device can be a one-to-one relationship, or a many-to-one relationship. The correspondence between the fault group and the device can be set according to actual needs. In this embodiment, the fault mapping table can include a fault group identifier, fault description information, a fault generation configuration command, and current time information. Among them, the fault group identifier can be used to distinguish different types of faults. The fault description information can include the specific phenomenon, severity, and affected business scope corresponding to each fault. The fault generation configuration command refers to the generation program corresponding to each fault. By running the generation program, the corresponding fault can be generated. The current time information refers to the time when the fault injection server injects the fault into the device.

[0125] As an optional implementation, the fault injection server may send a fault mapping table to the device based on the identification number of the device.

[0126] In this embodiment, the corresponding relationship between the device identification and the fault mapping table corresponding to the device can be pre-stored in the fault injection server, so that the corresponding fault mapping table can be sent to the device according to the device identification number.

[0127] In this embodiment, by sending a fault mapping table to the device, the fault group identifier, fault description information, fault generation configuration command and previous time information can be sent to the device, so that the device can generate a corresponding fault according to the fault generation configuration command, and then collect the corresponding fault generation information after the fault is generated and send it to the fault injection server.

[0128] In the scenario of sending trigger information to the offset state information collection server, the fault injection server can determine the trigger information by receiving the fault generation information sent by the device, and then send the trigger information to the offset state information collection server. In one embodiment, as shown in FIG4 , the method further includes:

[0129] S401: Receive fault generation information sent by a device.

[0130] The fault generation information is determined based on the generated faults and the generation time of the generated faults after the device generates the fault information according to the fault generation configuration command. The fault generation information can be used to determine whether all the faults injected into the device have been generated and the generation time.

[0131] In this embodiment, the fault injection server may receive the fault generation information sent by the device when the device determines the fault generation information as the fault generation information based on the generation time corresponding to the fault, the identifier of the fault, and the fault group identifier corresponding to the fault.

[0132] S402: Determine trigger information according to the fault generation information.

[0133] In this embodiment, the fault injection server may determine trigger information based on the received fault generation information. Optionally, the determined trigger information may include the fault group identifier of the device injected by the fault injection server and the time information when the device generates the fault based on the fault group identifier.

[0134] As an optional implementation, the fault injection server can compare the corresponding fault in the received fault generation information with the fault of the injected device when receiving the fault generation information sent by the device, and determine whether the faults of all injected devices are generated based on the comparison results. If the faults of all injected devices are generated, the trigger information is determined based on the fault generation information.

[0135] In this embodiment, the fault injection server can determine the trigger information based on the fault generation information by receiving the fault generation information sent by the device. Since the fault generation information contains the generated fault and the shopping time, the fault injection server can accurately determine the trigger information based on the fault generation information, thereby improving the accuracy of the determined trigger information, and further improving the accuracy of the offset status information collection server triggered by the trigger information to collect the offset status information.

[0136] In one embodiment, as shown in FIG5 , a method for obtaining information is further provided. The method is described by taking the method applied to a device in the bearer network in FIG1 as an example, and includes the following steps:

[0137] S501, receiving request information sent by the offset status information collection server; the request information is determined by the offset status information collection server based on trigger information sent by the fault injection server, and the trigger information is determined based on fault generation information sent by the device.

[0138] The request information refers to the request information that the offset status information collection server sends to the device to obtain the offset status information. It should be noted that the operating status of the device affected by different faults may be different. Therefore, for different faults, it is necessary to collect status indicator information corresponding to different faults. The offset status information collection server can generate different request information based on different status indicator information and send the corresponding request information to the device. For example, if the bearer network includes multiple devices, the offset status information collection server needs to determine different status indicator information based on the fault group identifier in each device, generate different request information, and then send the corresponding request information to each device.

[0139] Among them, the trigger information can be determined by the fault injection server based on the fault generation information sent by the device. Optionally, the trigger information may include the fault group identifier of the device pre-injected and the time information when the device generates the fault based on the fault group identifier. The fault group identifier is identification information used to distinguish the fault type, and the time information of generating the fault refers to the time when the fault in the device is generated.

[0140] It can be understood that when the device receives a fault injected by a fault injection server, it can determine the generated fault identifier, the fault group identifier corresponding to the generated fault, and the generation time of the fault as fault generation information and send it to the fault injection server when the fault is generated. When the fault injection server determines that all injected faults are generated, it can determine the trigger information based on the fault generation information and send the trigger information to the offset status information collection server, so that the offset status information collection server can be triggered and generate request information, so that the device can receive the request information sent by the offset status information collection server.

[0141] In this embodiment, the device may receive the request information sent by the offset status information collection server when the offset status information collection server receives the trigger information, responds to the trigger information, and generates the request information according to the trigger information.

[0142] S502: Generate offset status information of the device based on the status indicator information of adjacent time nodes according to the request information.

[0143] Optionally, the request information may include at least one of the following items: the status indicator set identifier of the device, the status indicator set corresponding to the status indicator set identifier, the preset time interval corresponding to the status indicator set, and the preset time interval corresponding to the status indicator set. It can be understood that if any information in the request information is different, the offset status information generated by the device will also be different.

[0144] In this embodiment, the device can collect the status indicator information corresponding to adjacent time nodes after a time interval based on the status indicator set identifier and status indicator set in the request information, and calculate the difference between the status indicator information corresponding to the adjacent time nodes, and use the difference as the offset status information.

[0145] As an optional implementation, the difference between the status indicator information corresponding to any two adjacent time nodes within a time interval can be used as the initial offset status information, thereby generating the offset status information of the device from multiple initial offset status information within a preset time interval. For example, if the status indicator set included in the request message includes the throughput of the device and the delay of data transmission, the preset time interval is 20:00-21:00, and the preset time interval is 5s, then the device can obtain the throughput and data transmission delay information of the device every 5s from 20:00 to 21:00 based on the request message, and calculate the difference between the throughput and data transmission delay information corresponding to two adjacent time nodes, and use the difference as the initial offset status information, thereby using all the initial offset status information from 20:00 to 21:00 as the offset status information.

[0146] S503: Send the offset status information to the offset status information collection server.

[0147] In this embodiment, when the device generates the offset status information, it may send the generated offset status information to the offset status information collection server through the network.

[0148] In the above-mentioned information acquisition method, the device in the bearer network receives the request information sent by the offset status information collection server. Since the request information is determined by the offset status information collection server based on the trigger information sent by the received fault injection server, and the trigger information can quickly trigger the offset status information collection server to generate the request information, the time for the device to receive the request information is saved, so that the device can quickly generate the offset status information of the device based on the status indicator information of the adjacent time nodes, and send the offset status information to the offset status information collection server, thereby improving the efficiency of the offset status information collection server in obtaining the offset status information; in addition, since the trigger information is determined based on the fault generation information sent by the device, the determined trigger information can fully characterize the generation of the fault in the device.

[0149] In the scenario of receiving the request information sent by the offset status information collection server, the device needs to send the fault generation information to the fault injection server. The following describes the detailed process of the device sending the fault generation information to the fault injection server. In one embodiment, as shown in Figure 6, before S501, the method further includes:

[0150] S601: Receive a fault mapping table sent by a fault injection server.

[0151] Among them, the fault mapping table can be used to represent the correspondence between fault groups and devices. Optionally, the fault groups and devices can be a one-to-one relationship, or a many-to-one relationship. The correspondence between fault groups and devices can be set according to actual needs.

[0152] Optionally, the fault mapping table includes at least one of the following: a fault group identifier corresponding to the device, a fault generation configuration command, fault description information, and current time information. The fault group identifier can be used to distinguish different types of faults. The fault description information can include the specific phenomenon, severity, and affected business scope corresponding to each fault. The fault generation configuration command refers to the generation program corresponding to each fault, and running the generation program can generate the corresponding fault. The current time information refers to the time when the fault injection server injects the fault into the device.

[0153] In this embodiment, the device can receive a fault mapping table sent by a fault injection server according to the identification number of the device. Optionally, the fault mapping table received by the device may include a fault group identifier and a fault generation configuration command, fault description information, and current time information corresponding to the fault group identifier, indicating that the fault injection server injects a group of faults into the device; or, the fault mapping table received by the device may also include multiple fault group identifiers and a fault generation configuration command, fault description information, and current time information corresponding to each fault group identifier, indicating that the fault injection server injects multiple groups of faults into the device.

[0154] S602: Determine fault generation information according to the fault mapping table.

[0155] In this embodiment, the device can determine the injected fault based on the corresponding fault group identifier in the received fault mapping table, and generate the corresponding fault by running the fault generation configuration command, so that when a fault is generated, the fault generation information is determined based on the generation time of the generated fault, the identifier of the generated fault, and the identifier of the fault group to which the generated fault belongs.

[0156] S603: Send the fault generation information to the fault injection server.

[0157] In this embodiment, the device can send the determined fault generation information to the fault injection server through the network. Optionally, the device can send the fault generation information corresponding to each generated fault to the fault injection server when the fault is generated. Alternatively, the device can also send the fault generation information corresponding to all generated faults to the fault injection server when each fault in the corresponding fault group identifier is generated.

[0158] In this embodiment, the device in the bearer network can determine the fault generation information based on the fault mapping table sent by the fault injection server, and thus can send the fault generation information to the fault injection server. Since the fault generation information is generated based on the injected fault mapping table, there is no need to manually log in to the device to write a program to generate the fault, thereby improving the efficiency of fault generation.

[0159] The specific process of the device determining the offset state information according to the request information is described in detail below. In one embodiment, as shown in FIG7 , the above S502 includes:

[0160] S701: Determine a status indicator set, a time interval, and a time interval according to request information.

[0161] Among them, the status indicator set in the request information refers to the set of indicators corresponding to the fault group injected by each device. For example, when a fault is generated in the device, the throughput, utilization, storage capacity of the device during operation when the fault is generated, and the delay, jitter, packet loss and other status information of the device transmitting data can be collected. The collected status information is used as the information corresponding to the status indicator. The time interval and time interval in the request information can be set according to actual needs. For example, the time interval can be 0:00-06:00, and the time interval can be 5s.

[0162] In this embodiment, the device can parse the received request information to obtain the status indicator set, time interval, and time interval carried in the request information. It is understood that if the bearer network includes multiple devices and each device has a different fault type injected, the status indicator set included in the request information sent by the offset status information collection server to each device will also be different.

[0163] S702: Determine first status indicator information of an indicator in the status indicator set at a first time node.

[0164] Among them, the first time node refers to the moment when the device obtains the operating status of the device for the first time, and the first status indicator information refers to the operating status of the device obtained according to the status indicator set at the first time node. Optionally, if the status indicator set includes 1 indicator, the first status indicator information includes the status indicator information corresponding to the indicator; if the status indicator set includes 3 indicators, the first status indicator information includes the status indicator information corresponding to each of the 3 indicators.

[0165] In this embodiment, the device can determine the operating state that meets the indicators in the status indicator set from the operating state of the device corresponding to the first time node based on the indicators in the status indicator set, thereby determining the operating state that meets the indicators in the status indicator set as the first status indicator information.

[0166] S703: Determine a second time node adjacent to the first time node according to the time interval and the time interval, and obtain second state indicator information of the indicator at the second time node.

[0167] Among them, the second time node refers to the moment when the device obtains the first status indicator information and re-obtains the new operating status of the device after a time interval. The second status indicator information refers to the operating status of the device obtained according to the status indicator set at the second time node. It can be understood that the quantity and type of the second status indicator information are the same as those of the first status indicator information.

[0168] In this embodiment, after obtaining the first status indicator information, the device can re-obtain the operating status of the device corresponding to the second time node after a time interval, and determine the operating status that meets the indicators in the status indicator set, thereby determining the operating status that meets the indicators in the status indicator set as the second status indicator information.

[0169] It is understood that within a time interval, multiple time nodes can be determined based on the time interval. The device can then use the second time node as a new first time node, determine a new second time node based on the time interval, and obtain new second state indicator information for the indicator at the new second time node, thereby determining all indicator information within the time interval. For example, if the time interval is 08:00-09:00 and the time interval is 10 seconds, it can be determined that the time interval includes 10 time nodes, and thus 10 indicator information can be obtained.

[0170] S704: Determine offset state information according to the first state indicator information and the second state indicator information.

[0171] In this embodiment, the first status indicator information and the second status indicator information can be compared, and the comparison result can be determined as the offset status information. For example, if the indicator in the status indicator set is the utilization rate of the device, and the first status indicator information obtained is 60% and the second status indicator information is 55%, then the offset status information can be determined to be the utilization rate of the device is 5%.

[0172] Optionally, initial offset state information may be determined based on indicator information corresponding to every two adjacent time nodes, thereby determining the mean of each initial offset state information as the offset state information; or, the sum of each initial offset state information may be determined as the offset state information.

[0173] In this embodiment, the device determines the status indicator set, time interval and time interval according to the request information, and can determine the first status indicator information of the indicator in the status indicator set at the first time node, and determine the second time node adjacent to the first time node according to the time interval and time interval, and obtain the second status indicator information of the indicator at the second time node. Since the device can accurately determine the status indicator information corresponding to each time node according to the time interval, it can accurately determine the offset status information according to the first status indicator information and the second status indicator information, and then can accurately determine the explosion radius of the fault on the bearer network according to the offset status information, thereby improving the precision and accuracy of the determined explosion radius.

[0174] To facilitate understanding by those skilled in the art, the information acquisition method provided in this application is described in detail below with reference to FIG8 . FIG8 includes a fault injection server, an offset status information collection server, multiple devices in the bearer network, and an offset status information analysis module. The method may include:

[0175] S1. The fault injection server sends a fault mapping table to each device in the bearer network based on the device identification number. The fault mapping table includes at least one of the following items: fault group identifier, fault description information, fault generation configuration command, and current time information.

[0176] S2: Each device receives the fault mapping table sent by the fault injection server.

[0177] S3, each device determines fault generation information according to the fault mapping table.

[0178] S4, each device sends the fault generation information to the fault injection server.

[0179] S5. The fault injection server determines trigger information according to the fault generation information sent by each device in the bearer network.

[0180] S6: The fault injection server sends trigger information to the offset status information collection server.

[0181] S7. When the trigger information is received, the trigger offset status information collection server sends a request information to each device, and the request information includes at least one of the following: the status indicator set identifier of the device, the status indicator set corresponding to the status indicator set identifier, the preset time interval corresponding to the status indicator set, and the preset time interval corresponding to the status indicator set.

[0182] S8. Each device determines a state indicator set, a time interval, and a time interval according to the request information sent by the offset state information collection server.

[0183] S9, each device determines first status indicator information of an indicator in the status indicator set at a first time node.

[0184] S10 , each device determines a second time node adjacent to the first time node according to the time interval and the time interval, and obtains second status indicator information of the indicator at the second time node.

[0185] S11 , each device determines offset state information according to the first state indicator information and the second state indicator information.

[0186] S12: Each device sends the offset status information to the offset status information collection server.

[0187] S13, the offset status information collection server sends the received offset status information corresponding to each device to the offset status information analysis module.

[0188] S14: The offset status information analysis module determines the explosion radius of the bearer network based on the offset status information.

[0189] It should be noted that for the descriptions in S1-S15 above, reference can be made to the relevant descriptions in the above embodiments, and the effects are similar, so this embodiment will not be repeated here.

[0190] It should be understood that, although the various steps in the flowcharts of Figures 2-7 are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in Figures 2-7 may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0191] In one embodiment, as shown in FIG9 , an information acquisition device is provided, which is applied to an offset state information collection server and includes: a first receiving module 10 and an acquisition module 11 , wherein:

[0192] The first receiving module 10 is configured to receive trigger information sent by a fault injection server; the trigger information is determined according to fault generation information sent by a device in the bearer network.

[0193] Optionally, the trigger information includes a fault group identifier of the injection device and time information of when the device generates a fault based on the fault group identifier.

[0194] The acquisition module 11 is configured to acquire the offset state information of the device according to the trigger information; the offset state information is generated by the device based on the state indicator information of adjacent time nodes.

[0195] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0196] In one embodiment, as shown in FIG10 , the acquisition module 11 includes: a first sending unit 111 and a receiving unit 112 , wherein:

[0197] The first sending unit 111 is configured to send a request message to the device when trigger information is received; the request message is used to instruct the device to collect and send the offset status information.

[0198] Optionally, the request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

[0199] The receiving unit 112 is configured to receive the offset status information sent by the device based on the request information.

[0200] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0201] In one embodiment, referring to FIG. 10 , the apparatus further includes a first determining module 12 , wherein:

[0202] The first determining module 12 is configured to determine the explosion radius of the bearer network based on the offset state information.

[0203] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0204] In one embodiment, as shown in FIG11 , an information acquisition device is provided, which is applied to a fault injection server and includes: a first sending module 13 , wherein:

[0205] The first sending module 13 is used to send trigger information to the offset status information collection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network, and the trigger information is used to instruct the offset status information collection server to obtain the offset status information of the device. The offset status information is generated by the device based on the status indicator information of adjacent time nodes.

[0206] Optionally, the trigger information includes a fault group identifier of the injection device and time information of when the device generates a fault based on the fault group identifier.

[0207] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0208] In one embodiment, as shown in FIG12 , the apparatus further includes: a second sending module 14 , wherein:

[0209] The second sending module 14 is configured to send a fault mapping table to the device; the fault mapping table includes at least one of the following: a fault group identifier, fault description information, a fault generation configuration command, and current time information.

[0210] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0211] In one embodiment, referring to FIG. 12 , the second sending module 14 includes a second sending unit 141 , wherein:

[0212] The second sending unit 141 is configured to send the fault mapping table to the device based on the identification number of the device.

[0213] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0214] In one embodiment, referring to FIG. 12 , the apparatus further includes: a second receiving module 15 and a second determining module 16 , wherein:

[0215] The second receiving module 15 is used to receive fault generation information sent by the device;

[0216] The second determining module 16 is configured to determine trigger information according to the fault generation information.

[0217] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0218] In one embodiment, as shown in FIG13 , an information acquisition device is provided. The device applied to the bearer network includes: a third receiving module 17 , a generating module 18 , and a third sending module 19 , wherein:

[0219] The third receiving module 17 is used to receive the request information sent by the offset status information collection server; the request information is determined by the offset status information collection server based on the trigger information sent by the fault injection server, and the trigger information is determined based on the fault generation information sent by the device.

[0220] Optionally, the request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

[0221] Optionally, the trigger information includes a fault group identifier pre-injected into the device and time information when the device generates a fault based on the fault group identifier.

[0222] The generating module 18 is configured to generate the offset status information of the device based on the status indicator information of the adjacent time nodes according to the request information.

[0223] The third sending module 19 is configured to send the offset status information to the offset status information collection server.

[0224] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0225] In one embodiment, as shown in FIG14 , before receiving the request information sent by the offset state information collection server, the apparatus further includes a fourth receiving module 20, a third determining module 21, and a fourth sending module 22, wherein:

[0226] The fourth receiving module 20 is configured to receive the fault mapping table sent by the fault injection server.

[0227] Optionally, the fault mapping table includes at least one of the following items: a fault group identifier corresponding to the device, a fault generating configuration command, fault description information, and current time information.

[0228] The third determining module 21 is configured to determine fault generation information according to the fault mapping table.

[0229] The fourth sending module 22 is configured to send the fault generation information to the fault injection server.

[0230] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0231] In one embodiment, referring to FIG. 14 , the generating module 18 includes a first determining unit 181 , a second determining unit 182 , a third determining unit 183 , and a fourth determining unit 184 , wherein:

[0232] The first determining unit 181 is configured to determine a state indicator set, a time interval, and a time interval according to the request information.

[0233] The second determining unit 182 is configured to determine first state indicator information of an indicator in the state indicator set at a first time node.

[0234] The third determining unit 183 is configured to determine a second time node adjacent to the first time node according to the time interval and the time interval, and obtain second state indicator information of the indicator at the second time node.

[0235] The fourth determining unit 184 is configured to determine the offset state information according to the first state indicator information and the second state indicator information.

[0236] The information acquisition device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail here.

[0237] For the specific definition of the information acquisition device, please refer to the definition of the information acquisition method above and will not be repeated here. The various modules in the above-mentioned information acquisition device can be implemented in whole or in part by software, hardware, or a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software so that the processor can call and execute the operations corresponding to the above modules.

[0238] In one embodiment, an offset status information collection server is provided, see Figure 15. The terminal device 700 shown in Figure 15 includes: at least one processor 701, a memory 702, at least one network interface 704 and a user interface 703. The various components in the terminal device 700 are coupled together through a bus system 705. It can be understood that the bus system 705 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 705 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, various buses are labeled as bus systems 705 in Figure 15. In addition, in an embodiment of the present invention, a transceiver 706 is also included. The transceiver can be multiple components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium.

[0239] The user interface 703 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touchpad, or a touch screen).

[0240] It is understood that the memory 702 in the embodiment of the present invention can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 702 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0241] In some embodiments, the memory 702 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof: an operating system 7021 and application programs 7022 .

[0242] The operating system 7021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, for implementing various basic services and handling hardware-based tasks. Application programs 7022 include various application programs, such as a media player (MediaPlayer) and a browser (Browser), for implementing various application services. Programs implementing the methods of the embodiments of the present invention may be included in application programs 7022.

[0243] In an embodiment of the present invention, by calling the program or instructions stored in the memory 702, specifically, the program or instructions stored in the application 7022, the receiver is used to receive the trigger information sent by the fault injection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network; optionally, the trigger information includes the fault group identifier of the injected device and the time information of the device generating the fault based on the fault group identifier; the processor is used to obtain the offset status information of the device according to the trigger information; the offset status information is generated by the device based on the status indicator information of adjacent time nodes.

[0244] Some or all of the methods disclosed in the above embodiments of the present invention may also be applied to the processor 701, or implemented by the processor 701, or implemented by the processor 701 in conjunction with other components (e.g., a transceiver). The processor 701 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method may be performed by hardware integrated logic circuits in the processor 701 or by software instructions. The processor 701 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of the present invention may be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of the present invention may be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 702, and processor 701 reads the information in memory 702 and performs the steps of the above method in conjunction with its hardware.

[0245] It is understood that the embodiments described in the embodiments of the present invention can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSP devices, DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions of the present application, or a combination thereof.

[0246] For software implementation, the techniques of the embodiments of the present invention can be implemented through modules (e.g., procedures, functions, etc.) that perform the functions of the embodiments of the present invention. The software code can be stored in a memory and executed by the processor 701. The memory can be implemented in the processor 701 or external to the processor 701.

[0247] In one embodiment, a transmitter is used to send a request message to a device when a trigger message is received; the request message is used to instruct the device to collect and send offset status information; a receiver is used to receive the offset status information sent by the device based on the request message; optionally, the request message includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

[0248] In one embodiment, the processor is further configured to determine a blast radius of the bearer network based on the offset state information.

[0249] In one embodiment, a fault injection server is provided, see Figure 16. The terminal device 800 shown in Figure 16 includes: at least one processor 801, a memory 802, at least one network interface 804 and a user interface 803. The various components in the terminal device 800 are coupled together through a bus system 805. It can be understood that the bus system 805 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 805 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, various buses are labeled as bus systems 805 in Figure 16. In addition, in an embodiment of the present invention, a transceiver 806 is also included. The transceiver can be multiple components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium.

[0250] The user interface 803 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touchpad, or a touch screen).

[0251] It is understood that the memory 802 in the embodiment of the present invention can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 802 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0252] In some embodiments, the memory 802 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof: an operating system 8021 and application programs 8022 .

[0253] The operating system 8021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, for implementing various basic services and handling hardware-based tasks. Application programs 8022 include various application programs, such as a media player (MediaPlayer) and a browser (Browser), for implementing various application services. Programs implementing the methods of the embodiments of the present invention may be included in application programs 8022.

[0254] In an embodiment of the present invention, by calling the program or instructions stored in the memory 802, specifically, the program or instructions stored in the application 8022, the transmitter is used to send trigger information to the offset status information collection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network, and the trigger information is used to instruct the offset status information collection server to obtain the offset status information of the device, and the offset status information is generated by the device based on the status indicator information of the adjacent time nodes; optionally, the trigger information includes the fault group identifier of the injected device and the time information of the device generating the fault based on the fault group identifier.

[0255] Some or all of the methods disclosed in the above embodiments of the present invention may also be applied to processor 801, or implemented by processor 801, or implemented by processor 801 in conjunction with other components (e.g., a transceiver). Processor 801 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method may be performed by hardware integrated logic circuits or software instructions within processor 801. The above processor 801 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. The methods, steps, and logic block diagrams disclosed in the embodiments of the present invention may be implemented or executed. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of the present invention may be directly executed by a hardware decoding processor or by a combination of hardware and software modules within the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 802, and processor 801 reads information in memory 802 and, in conjunction with its hardware, completes the steps of the above method.

[0256] It is understood that the embodiments described in the embodiments of the present invention can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSP devices, DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions of the present application, or a combination thereof.

[0257] For software implementation, the techniques of the embodiments of the present invention can be implemented through modules (e.g., procedures, functions, etc.) that perform the functions of the embodiments of the present invention. The software code can be stored in a memory and executed by the processor 801. The memory can be implemented in the processor 801 or external to the processor 801.

[0258] In one embodiment, the transmitter is further configured to send a fault mapping table to the device; the fault mapping table includes at least one of the following: a fault group identifier, fault description information, a fault generation configuration command, and current time information.

[0259] In one embodiment, the transmitter is further configured to send the fault mapping table to the device based on the identification number of the device.

[0260] In one embodiment, the receiver is configured to receive fault generation information sent by a device; and the processor is configured to determine trigger information according to the fault generation information.

[0261] In one embodiment, a fault injection server is provided, see Figure 17. The terminal device 900 shown in Figure 17 includes: at least one processor 901, a memory 902, at least one network interface 904 and a user interface 903. The various components in the terminal device 900 are coupled together through a bus system 905. It can be understood that the bus system 905 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 905 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, various buses are labeled as bus systems 905 in Figure 17. In addition, in an embodiment of the present invention, a transceiver 906 is also included. The transceiver can be multiple components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium.

[0262] The user interface 903 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touchpad, or a touch screen).

[0263] It is understood that the memory 902 in the embodiment of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 902 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0264] In some embodiments, the memory 902 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof: an operating system 9021 and application programs 9022 .

[0265] The operating system 9021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, for implementing various basic services and handling hardware-based tasks. Application programs 9022 include various application programs, such as a media player (MediaPlayer) and a browser (Browser), for implementing various application services. Programs implementing the methods of the embodiments of the present invention may be included in application programs 9022.

[0266] In an embodiment of the present invention, by calling a program or instruction stored in the memory 902, specifically, it can be a program or instruction stored in the application 9022, wherein the receiver is used to receive the request information sent by the offset status information collection server; the request information is determined by the offset status information collection server based on the trigger information sent by the received fault injection server, and the trigger information is determined based on the fault generation information sent by the device; optionally, the request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set; optionally, the trigger information includes a fault group identifier pre-injected into the device and time information of the device generating the fault based on the fault group identifier; the processor is used to generate the offset status information of the device based on the status indicator information of adjacent time nodes according to the request information; the transmitter is used to send the offset status information to the offset status information collection server.

[0267] Some or all of the methods disclosed in the above embodiments of the present invention may also be applied to the processor 901, or implemented by the processor 901, or implemented by the processor 901 in conjunction with other components (e.g., a transceiver). The processor 901 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method may be performed by hardware integrated logic circuits in the processor 901 or by software instructions. The above processor 901 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of the present invention may be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of the present invention may be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 902, and processor 901 reads information in memory 902 and, in conjunction with its hardware, completes the steps of the above method.

[0268] It is understood that the embodiments described in the embodiments of the present invention can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSP devices, DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions of the present application, or a combination thereof.

[0269] For software implementation, the techniques of the embodiments of the present invention can be implemented through modules (e.g., procedures, functions, etc.) that perform the functions of the embodiments of the present invention. The software code can be stored in a memory and executed by the processor 901. The memory can be implemented in the processor 901 or external to the processor 901.

[0270] In one embodiment, a receiver is used to receive a fault mapping table sent by a fault injection server; optionally, the fault mapping table includes at least one of the following items: a fault group identifier corresponding to the device, a fault generation configuration command, fault description information, and current time information; a processor is used to determine fault generation information based on the fault mapping table; and a transmitter is used to send the fault generation information to the fault injection server.

[0271] In one embodiment, the processor is used to determine a status indicator set, a time interval, and a time interval based on the request information; the processor is also used to determine the first status indicator information of the indicator in the status indicator set at the first time node; the processor is also used to determine the second time node adjacent to the first time node according to the time interval and the time interval, and obtain the second status indicator information of the indicator at the second time node; the processor is also used to determine the offset status information based on the first status indicator information and the second status indicator information.

[0272] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0273] Receive trigger information sent by the fault injection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network;

[0274] Optionally, the trigger information includes a fault group identifier of the injected device and time information of when the device generates a fault based on the fault group identifier;

[0275] The device's offset status information is obtained based on the trigger information; the offset status information is generated by the device based on status indicator information of adjacent time nodes.

[0276] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0277] When a trigger message is received, a request message is sent to the device; the request message is used to instruct the device to collect and send offset status information;

[0278] receiving offset status information sent by the device based on the request information;

[0279] Optionally, the request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

[0280] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0281] The explosion radius of the bearer network is determined based on the offset status information.

[0282] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0283] Sending a trigger message to the offset status information collection server; the trigger message is determined based on the fault generation information sent by the device in the bearer network, and the trigger message is used to instruct the offset status information collection server to obtain the offset status information of the device, which is generated by the device based on the status indicator information of adjacent time nodes;

[0284] Optionally, the trigger information includes a fault group identifier of the injection device and time information of when the device generates a fault based on the fault group identifier.

[0285] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0286] Send a fault mapping table to the device; the fault mapping table includes at least one of the following: a fault group identifier, fault description information, a fault generation configuration command, and current time information.

[0287] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0288] A fault mapping table is sent to the device based on the device's identification number.

[0289] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0290] Receive fault generation information sent by the device;

[0291] Trigger information is determined based on the fault generation information.

[0292] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0293] Receiving a request message sent by the offset status information collection server; the request message is determined by the offset status information collection server based on the trigger information sent by the fault injection server, and the trigger information is determined based on the fault generation information sent by the device;

[0294] Optionally, the trigger information includes a fault group identifier pre-injected into the device and time information of when the device generates a fault based on the fault group identifier;

[0295] Optionally, the request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set;

[0296] Generate device offset status information based on the status indicator information of adjacent time nodes according to the request information;

[0297] The offset status information is sent to the offset status information collection server.

[0298] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0299] Receive the fault mapping table sent by the fault injection server;

[0300] Optionally, the fault mapping table includes at least one of the following: a fault group identifier corresponding to the device, a fault generating configuration command, fault description information, and current time information;

[0301] Determine fault generation information according to the fault mapping table;

[0302] Send fault generation information to the fault injection server.

[0303] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0304] Determine the status indicator set, time interval, and time interval based on the request information;

[0305] Determine first status indicator information of an indicator in the status indicator set at a first time node;

[0306] Determine a second time node adjacent to the first time node according to the time interval and the time interval, and obtain second state indicator information of the indicator at the second time node;

[0307] Determine offset state information according to the first state indicator information and the second state indicator information.

[0308] The present application also provides a computer program product comprising instructions, which, when executed on a computer, causes the computer to perform the following steps:

[0309] Receive trigger information sent by the fault injection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network;

[0310] Optionally, the trigger information includes a fault group identifier of the injected device and time information of when the device generates a fault based on the fault group identifier;

[0311] The device's offset status information is obtained based on the trigger information; the offset status information is generated by the device based on status indicator information of adjacent time nodes.

[0312] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0313] When a trigger message is received, a request message is sent to the device; the request message is used to instruct the device to collect and send offset status information;

[0314] receiving offset status information sent by the device based on the request information;

[0315] Optionally, the request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

[0316] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0317] The explosion radius of the bearer network is determined based on the offset status information.

[0318] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0319] Sending a trigger message to the offset status information collection server; the trigger message is determined based on the fault generation information sent by the device in the bearer network, and the trigger message is used to instruct the offset status information collection server to obtain the offset status information of the device, which is generated by the device based on the status indicator information of adjacent time nodes;

[0320] Optionally, the trigger information includes a fault group identifier of the injection device and time information of when the device generates a fault based on the fault group identifier.

[0321] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0322] Send a fault mapping table to the device; the fault mapping table includes at least one of the following: a fault group identifier, fault description information, a fault generation configuration command, and current time information.

[0323] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0324] A fault mapping table is sent to the device based on the device's identification number.

[0325] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0326] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0327] Receive fault generation information sent by the device;

[0328] Trigger information is determined based on the fault generation information.

[0329] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0330] Receiving a request message sent by the offset status information collection server; the request message is determined by the offset status information collection server based on the trigger information sent by the fault injection server, and the trigger information is determined based on the fault generation information sent by the device;

[0331] Optionally, the trigger information includes a fault group identifier pre-injected into the device and time information of when the device generates a fault based on the fault group identifier;

[0332] Optionally, the request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set;

[0333] Generate device offset status information based on the status indicator information of adjacent time nodes according to the request information;

[0334] The offset status information is sent to the offset status information collection server.

[0335] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0336] Receive the fault mapping table sent by the fault injection server;

[0337] Optionally, the fault mapping table includes at least one of the following: a fault group identifier corresponding to the device, a fault generating configuration command, fault description information, and current time information;

[0338] Determine fault generation information according to the fault mapping table;

[0339] Send fault generation information to the fault injection server.

[0340] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0341] Determine the status indicator set, time interval, and time interval based on the request information;

[0342] Determine first status indicator information of an indicator in the status indicator set at a first time node;

[0343] Determine a second time node adjacent to the first time node according to the time interval and the time interval, and obtain second state indicator information of the indicator at the second time node;

[0344] Determine offset state information according to the first state indicator information and the second state indicator information.

[0345] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). Industrial Applicability

[0346] The present disclosure is applicable to the field of positioning and navigation technology, and is used to solve the problem of inaccurate location-based positioning in related technologies, so that the corrected initial positioning point can more accurately describe the position of the device to be positioned.

[0347] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0348] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. An information acquisition method, applied to an offset status information collection server, the method comprising: Receive trigger information sent by the fault injection server; The trigger information is determined according to the fault generation information sent by the equipment in the bearer network; The offset state information of the device is acquired according to the trigger information; the offset state information is generated by the device based on state indicator information of adjacent time nodes.

2. The method according to claim 1, wherein: The trigger information includes a fault group identifier injected into the device and time information when the device generates a fault based on the fault group identifier.

3. The method according to claim 2, wherein: The acquiring the offset state information of the device according to the trigger information includes: When the trigger information is received, a request information is sent to the device; the request information is used to instruct the device to collect and send the offset status information; receiving the offset status information sent by the device based on the request information.

4. The method according to claim 3, wherein: The request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

5. The method according to any one of claims 1 to 4, wherein: The method further comprises: A blast radius of the bearer network is determined based on the offset state information.

6. A method for obtaining information, wherein: Applied to a fault injection server, the method comprises: Send trigger information to the offset status information collection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network, and the trigger information is used to instruct the offset status information collection server to obtain the offset status information of the device, and the offset status information is generated by the device based on the status indicator information of adjacent time nodes.

7. The method according to claim 6, wherein: The trigger information includes a fault group identifier injected into the device and time information when the device generates a fault based on the fault group identifier.

8. The method according to claim 6, wherein: The method further comprises: Sending a fault mapping table to the device; the fault mapping table includes at least one of the following: Fault group ID, fault description information, fault generation configuration command, and current time information.

9. The method according to claim 8, wherein: The sending the fault mapping table to the device includes: The fault mapping table is sent to the device based on the identification number of the device.

10. The method according to any one of claims 6 to 9, wherein: The method further comprises: receiving fault generation information sent by the device; The trigger information is determined according to the fault generation information.

11. A method for obtaining information, wherein: Applied to a device in a bearer network, the method comprises: Receiving request information sent by the offset status information collection server; the request information is determined by the offset status information collection server according to trigger information sent by the received fault injection server, and the trigger information is determined according to the fault generation information sent by the device; According to the request information, generating the offset state information of the device based on the state indicator information of the adjacent time nodes; The offset state information is sent to the offset state information collection server.

12. The method according to claim 11, wherein: The trigger information includes a fault group identifier pre-injected into the device and time information when the device generates a fault based on the fault group identifier.

13. The method according to claim 11, wherein: The request information includes at least one of the following: a status indicator set identifier of the device, a status indicator set corresponding to the status indicator set identifier, a preset time interval corresponding to the status indicator set, and a preset time interval corresponding to the status indicator set.

14. The method according to claim 11, wherein: Before receiving the request information sent by the offset status information collection server, the method further includes: Receiving the fault mapping table sent by the fault injection server; Determine fault generation information according to the fault mapping table; The fault generation information is sent to the fault injection server.

15. The method according to claim 14, wherein: The fault mapping table includes at least one of the following items: a fault group identifier corresponding to the device, a fault generation configuration command, fault description information, and current time information.

16. The method according to claim 13, wherein: The step of generating the offset state information of the device based on the state indicator information of the adjacent time nodes according to the request information includes: Determine the status indicator set, the time interval and the time interval according to the request information; Determine first status indicator information of an indicator in the status indicator set at a first time node; Determine a second time node adjacent to the first time node according to the time interval and the time interval, and obtain second state indicator information of the indicator at the second time node; The offset state information is determined according to the first state indicator information and the second state indicator information.

17. An information acquisition device, wherein: Applied to a server for collecting offset status information, the device comprises: A first receiving module, configured to receive trigger information sent by a fault injection server; the trigger information is determined based on fault generation information sent by a device in the bearer network; An acquisition module is used to acquire the offset state information of the device according to the trigger information; the offset state information is generated by the device based on the state indicator information of adjacent time nodes.

18. An information acquisition device, wherein: Applied to a fault injection server, the device comprises: The first sending module is used to send trigger information to the offset status information collection server; the trigger information is determined based on the fault generation information sent by the device in the bearer network, and the trigger information is used to instruct the offset status information collection server to obtain the offset status information of the device, and the offset status information is generated by the device based on the status indicator information of adjacent time nodes.

19. An information acquisition device, wherein: A device applied to a bearer network, the device comprising: A third receiving module is used to receive request information sent by the offset state information collection server; the request information is determined by the offset state information collection server according to trigger information sent by the received fault injection server, and the trigger information is determined according to the fault generation information sent by the device; A generating module, configured to generate offset status information of the device based on status indicator information of adjacent time nodes according to the request information; The third sending module is used to send the offset state information to the offset state information collection server.

20. A server for collecting offset status information, wherein: include: Receiver and processor; The receiver is used to receive trigger information sent by the fault injection server; The trigger information is determined according to the fault generation information sent by the equipment in the bearer network; The processor is used to obtain the offset state information of the device according to the trigger information; the offset state information is generated by the device based on the state indicator information of adjacent time nodes.

21. A fault injection server, wherein: include: Transmitter; The transmitter is used to send trigger information to the offset status information collection server; The trigger information is determined based on fault generation information sent by a device in the bearer network, and the trigger information is used to instruct the offset status information collection server to obtain offset status information of the device, where the offset status information is generated by the device based on status indicator information of adjacent time nodes.

22. A device in a bearer network, wherein: include: Receivers, processors, and transmitters; The receiver is used to receive the request information sent by the offset status information collection server; The request information is determined by the offset status information collection server according to trigger information sent by the fault injection server, and the trigger information is determined according to the fault generation information sent by the device; The processor is configured to generate offset state information of the device based on the state indicator information of adjacent time nodes according to the request information; The transmitter is used to send the offset state information to the offset state information collection server.

23. An information acquisition system, wherein: The device comprises the offset status information collection server of claim 20, the fault injection server of claim 21 and the device in the bearer network of claim 22; The offset status information collection server is used to perform the steps of claims 1-5; The fault injection server is used to perform the steps of claims 6-10; The device in the bearer network is used to execute the steps of claims 11-16.

24. A computer-readable storage medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.

25. A chip, wherein: The chip comprises a programmable logic circuit and / or program instructions, and the steps of the method according to any one of claims 1 to 16 are implemented when the chip is executed.

26. A computer program product comprising a computer program, wherein: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.

Images