A method and system for screening and processing abnormal equipment based on a third-party business platform

Abstract

A method and system for screening and processing abnormal devices based on a third-party business platform, characterized in that the method includes step 1, extracting the device information of all devices from the local business platform and generating a local device list, and extracting the device information of all devices from the third-party business platform and generating a list of all devices; step 2, after sequentially extracting the device codes in the local device list, traversing the device codes in all device lists to perform a search and comparison, and recording the abnormal devices in the abnormal device list; step 3, based on the result of the first search and comparison, extracting the device names of the devices that failed to match, traversing the device names in all device lists to perform a second search and comparison, and recording the abnormal devices in the abnormal device list; step 4, recording the devices that failed to match successfully in the second search and comparison, and using manual methods to achieve information changes. The method of the present invention is simple, fast, accurate and without omissions.

Description

Technical Field

[0001] The present invention relates to the field of network operation and maintenance, and more specifically, to a method and system for screening and processing abnormal devices based on a third-party service platform. Background Art

[0002] At present, the model of building and integrating new business platforms based on third-party business platform interfaces has been increasingly widely used. By accessing the equipment and data content of third-party business platforms, the workload of local development and the need for local operation and maintenance management can be greatly reduced.

[0003] However, since local services need to call multiple data from different third-party service platforms, it is difficult to synchronize information when the local service platform maintains the equipment from the third-party service platform. For example, in the monitoring system set up in the power plant area, the local service platform of the power plant needs to call third-party monitoring platforms provided by multiple different manufacturers to obtain the monitoring equipment resources under its jurisdiction. At the same time, the local service platform can also obtain the video stream data provided by the third-party monitoring platform through monitoring resources. However, in the actual application process, due to the problem that the local service platform and the equipment information in the third-party service platform cannot be fully synchronized, the local service platform often encounters resource call exceptions and unsuccessful resource calls in the process of the control server calling the monitoring resources of the manufacturer's security monitoring platform.

[0004] In addition, in the prior art, local business platforms are usually unable to automatically find the root cause of the above abnormal problems, and therefore are unable to automatically repair the faults in a timely manner, and can only manually troubleshoot through regular operation and maintenance. This not only reduces the stability and anti-interference of the system in the local business platform, but also increases the difficulty, efficiency and timeliness of troubleshooting, making it difficult to improve the intelligence level of the local business platform.

[0005] Therefore, there is an urgent need for an abnormal device screening and processing method and system based on a third-party business platform. Summary of the invention

[0006] In order to solve the deficiencies in the prior art, the purpose of the present invention is to provide a method and system for screening and processing abnormal devices based on a third-party business platform, by extracting the device codes and device names of the devices in the local business platform and the third-party business platform, and performing multiple retrieval and comparison on the device list, thereby screening out abnormal devices.

[0007] The present invention adopts the following technical solution.

[0008] The first aspect of the present invention relates to a method for screening and processing abnormal devices based on a third-party business platform, wherein the method comprises the following steps: step 1, extracting device information of all devices from a local business platform and generating a local device list, and extracting device information of all devices from a third-party business platform and generating a list of all devices; step 2, after sequentially extracting device codes in the local device list, traversing device codes in all device lists to perform a search and comparison, and recording abnormal devices in the abnormal device list; step 3, based on the result of the first search and comparison, extracting device names of devices that failed to match, traversing device names in all device lists to perform a second search and comparison, and recording abnormal devices in the abnormal device list; step 4, recording devices that failed to match successfully in the second search and comparison, and manually changing information.

[0009] Preferably, the device information of all devices extracted from the third-party business platform includes the device code, device name and device area address assigned by the third-party business platform; the device information of all devices extracted from the local business platform includes the device number and device area organization assigned by the local business platform, as well as the device code, device name and device area address from the third-party business platform.

[0010] Preferably, a retrieval and comparison includes: step 2.1, extracting the device codes in the local device list in turn, and traversing the device codes in all device lists based on the device codes in each local device list; step 2.2, when the device codes in all device lists are found to match the device codes in the local device list, sending a play request to the device and executing the play function based on the play address fed back by the device; step 2.3, if the play function can be executed based on the device play address, it is determined that the device is a normal device, otherwise it is an abnormal device, until the retrieval and comparison of the device codes in all local device lists are completed.

[0011] Preferably, after determining that each device is a normal device, the corresponding record of each device in the device list is deleted.

[0012] Preferably, if the playback function cannot be performed based on the device playback address, the device is determined to be an abnormal device and the device is recorded in an abnormal list.

[0013] Preferably, when no matching device code in all device lists is found based on the device code in the local device list, a secondary search and comparison is performed on the device.

[0014] Preferably, the abnormal device list includes the device number, device code, device name, device area address, device area organization and device playback address of the device.

[0015] Preferably, the secondary retrieval and comparison includes: step 3.1, based on the result of the primary retrieval and comparison, extracting the device name of the device from the local device list, and traversing the device names in all device lists; step 3.2, when the device name of the device is found to match the device name in all device lists, determining that the current device is a normal device, otherwise it is an abnormal device; step 3.3, based on the device code of the current device recorded in the third-party business platform, modifying the device code of the current device in the local business platform.

[0016] Preferably, the device name in the abnormal device list matches the device name in the list of all devices in particular: the device name in the abnormal device list matches the only device name in the list of all devices.

[0017] Preferably, when the device name in the abnormal device list is retrieved to match more than one device name in the all device list, more than one device is manually detected based on the current device information in the abnormal device list, and the duplicate device name is modified based on the manual detection result.

[0018] Preferably, device area addresses of more than one device are extracted, and a manual inspection work order is generated based on the device area addresses.

[0019] The second aspect of the present invention relates to an abnormal equipment screening and processing system based on a third-party business platform. In the system, a local business platform is communicated with one or more third-party business platforms, and an abnormal equipment screening and processing method based on a third-party business platform as described in the first aspect of the present invention is implemented.

[0020] The beneficial effect of the present invention is that, compared with the prior art, the abnormal device screening and processing method and system based on the third-party business platform in the present invention can extract the device code and device name of the device in the local business platform and the third-party business platform, and perform multiple searches and comparisons on the device list, thereby screening out abnormal devices. The method in the present invention is simple, has a fast data processing speed, does not cause huge pressure on the server, and can accurately detect abnormal devices without omission, and accurately locate the cause of the abnormality.

[0021] The beneficial effects of the present invention also include:

[0022] 1. The method of the present invention can gradually narrow down the scope of abnormal devices through multiple retrieval and comparison, and can find some abnormal situations in which incorrect device information records often appear in the platform only based on the automatic retrieval and comparison process, and solve such abnormal situations, thereby greatly reducing the workload of manual maintenance and reducing the trouble of secondary development of the platform.

[0023] 2. The method of the present invention can reversely modify the device code through the device name, thereby eliminating the problem of device information not being able to correspond due to the device code reset. In this way, interference can be effectively eliminated, so that manual inspection work orders can be more accurately and targetedly issued to the equipment that really needs to be repaired.

[0024] 3. The method of the present invention replaces the operating method that needs to update a large amount of data in a timely manner when the local business platform and the third-party business platform are in a data connection mode, so that even if the data in the local business platform is not updated frequently, the normal operation of the local business platform business can be guaranteed, reducing the amount of invalid data transmission and network traffic, and alleviating the communication burden and the burden of server processing data.

[0025] 4. The method of the present invention can use the system to automatically find abnormalities, and timely discover and repair abnormal problems. The system can set up scheduled tasks as needed to regularly find and repair abnormal situations, thereby ensuring the timeliness and flexibility of the method and improving the stability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 A schematic diagram of the steps of a method for screening and processing abnormal devices based on a third-party business platform of the present invention;

[0027] Figure 2 It is a schematic diagram of a search and comparison in a method for screening and processing abnormal devices based on a third-party business platform of the present invention;

[0028] Figure 3 The present invention is a flowchart of abnormal device screening in an embodiment of an abnormal device screening and processing method based on a third-party business platform. DETAILED DESCRIPTION

[0029] The present application is further described below in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and cannot be used to limit the protection scope of the present application.

[0030] Figure 1 FIG. 1 is a flow chart of the steps of a method for screening and processing abnormal devices based on a third-party business platform of the present invention. Figure 1 As shown, a method for screening and processing abnormal devices based on a third-party business platform, wherein the method includes steps 1 to 4.

[0031] Step 1: extract device information of all devices from the local service platform and generate a local device list, and extract device information of all devices from the third-party service platform and generate a list of all devices.

[0032] It is understandable that the local service platform and the third-party service platform can be connected in a one-to-one or one-to-many manner. That is, the local service platform can collect device information and device-related data from one or more third-party service platforms according to the actual situation of the devices and data it integrates.

[0033] In one embodiment of the present invention, the local business platform may be a business platform for implementing power plant security monitoring, and therefore, the platform may be connected to one or more vendor platforms that provide security monitoring equipment. Usually, the local business platform cannot realize more functional development based on the security monitoring function, and therefore, multiple functions can be realized by simply accessing the device information, device status data, etc. provided by the vendor platform. For example, in the present invention, the local business platform can control security equipment from different manufacturers by accessing the vendor platforms of multiple security monitoring equipment, and obtain the video information sent back by these monitoring equipment.

[0034] In addition, the devices from multiple third-party business platforms that can be controlled by the local business platform can be specifically placed in multiple different power plants. The specific location is not limited. There may be a certain distance between the power plants. Each power plant can also be divided into multiple different areas according to the different operating requirements of the power plant. The local business platform can comprehensively control the equipment from multiple power plants and multiple power plant areas.

[0035] This method requires the local business platform to update the data information from the third-party business platform in real time, otherwise it will cause the data in the local business platform and the third-party business platform to be out of sync. When the data is out of sync, the local business platform may not be able to control the device whose device information has been changed, or it may not be able to collect relevant data from the device.

[0036] However, the network traffic and server computing cost of real-time updating of data information of third-party business platforms to prevent abnormal data collection or device control are too high. This method is unnecessary, especially for business platforms that do not need to frequently modify device attributes or basic device information.

[0037] Therefore, the present invention provides a simpler method for synchronizing device information between platforms, that is, a method for screening and processing abnormal devices.

[0038] First, the relevant information of all the registered devices that have been recorded before can be extracted from the local service platform.

[0039] Preferably, the device information of all devices extracted from the third-party business platform includes the device code, device name and device area address assigned by the third-party business platform; the device information of all devices extracted from the local business platform includes the device number and device area organization assigned by the local business platform, as well as the device code, device name and device area address from the third-party business platform.

[0040] Table 1 is a table of relevant information of a monitoring device in the present invention. As shown in Table 1, the information of the device includes device number, device code, device name, device area address and area organization.

[0041]

[0042] Table 1. Related information table of a monitoring device in the present invention

[0043] It is understandable that the device code (Code) in the present invention can be a code shared by a security monitoring platform from a third-party manufacturer, which is constructed by means of UUID (Universally Unique Identifier). Specifically, UUID enables all elements in a distributed system to have unique identification information without the need to formulate identification information through the control of a central control terminal. Since UUID enables each machine device to generate a unique string of numbers in the same time and space, the uniqueness of the device identity is ensured. In the prior art, UUID can be a string of 128-bit numbers, identified in hexadecimal form, and 32 characters can be combined in the form of 8-4-4-4-12. Among them, the 13th to 16th characters can be used to identify the version of UUID, and the 17th to 20th characters can be used to identify different variables. It should be noted that in the present invention, multiple different third-party manufacturers create device codes through a UUID method, that is, multiple manufacturers' security monitoring platforms share a UUID encoding method, so the device code (Code) in the present invention is uniquely determined and will not have duplication problems with the codes of other devices.

[0044] In addition, the device name (Name) is generated by the third-party business platform through manual input. Depending on the business and the type of equipment, the device name may have different naming rules. The naming rule may be based on the needs and pre-determined by the equipment manufacturer or equipment user. For example, in one embodiment of the present invention, the device name may be composed of a power plant installation location and a 4-digit number. The power plant installation location may be the power plant equipment in which the monitoring device is installed, and the number may be used to distinguish monitoring devices installed on the same power plant equipment according to actual conditions.

[0045] Similarly, the equipment area address (Address) can be used to characterize that the equipment is placed in different areas of the power plant. For example, the steam turbine area of ​​unit #1 shown in Table 1. Specifically, since the main function of the equipment name (Name) is to distinguish different equipment and thus give the equipment a specified name, in actual applications, the power plant installation location used in the equipment name (Name) can be implemented in an abbreviated form or in various forms that maintenance personnel can understand. Generally speaking, the equipment area address (Address) needs to be specific to the actual area and actual location of each device.

[0046] It should be noted that, according to the cooperation model between the power plant and the third-party manufacturer, although the maintenance method of the equipment name and equipment area address is actually input and maintained in the manufacturer's security monitoring platform, the operators who perform the maintenance are specifically staff from each power plant. In other words, in order to facilitate the manufacturer's security to control and maintain the automated mode of equipment in the power plant, save the manpower consumed in the construction of the manufacturer's security monitoring platform in the power plant, and avoid technical limitations, each manufacturer provides maintenance rights for the corresponding equipment. Therefore, power plant personnel can use the manufacturer's security monitoring platform provided by multiple different manufacturers to maintain the equipment in the power plant. Therefore, the method in the present invention is essentially based on this cooperation model, which realizes the convenient connection between the power plant platform and multiple third-party business platforms, and achieves the best effect of adapting to the cooperation model between manufacturers and power plants.

[0047] In the present invention, the third-party service platform is only responsible for generating the device code, device name and device area address of each device. Other device information such as device number and device area organization is allocated by the local service platform when the device registers or logs in to the local service platform.

[0048] Similar to the device code (Code), the device number (InstnseID) in the present invention is also generated using UUID technology. Unlike the device code assigned by the third-party service platform, the device number in the present invention is assigned by the local service platform using UUID technology. Therefore, since devices from different third-party service platforms will have a unique UUID number after logging into the local service platform or being recognized by the local service platform for the first time, the device number (InstnseID) can be used as a unique identification mark to confirm the identity of the device.

[0049] In addition, to facilitate the management and maintenance of the equipment, the local business platform can assign an equipment area organization (Org) code according to which power plant the current equipment is placed. The code may include the name of the power plant or the number of the power plant. Through this data item, you can know which power plant the equipment is used by. It should be noted that the equipment area organization in the present invention is used to record the organization where the equipment is located, such as the name of the organization of a specific power plant. In contrast, the equipment area address mentioned above will be specific to the area in the power plant where the equipment is located or the location on the equipment. In addition, the equipment area organization (Org) is generated by the power plant business platform. The equipment area address is first entered in the manufacturer's security monitoring platform.

[0050] In the present invention, when a device has logged into the local service platform or is first identified by the local service platform, the information assigned to the current device by the third-party service platform, such as the device code, device name, and device area address, can be collected. Therefore, each device recorded in the local service platform database can include the contents of all the data items shown in Table 1.

[0051] In the present invention, in order to realize the screening of abnormal devices, the device codes of all devices can be extracted from the local business platform to generate the first temporary list list1. Then, through the local business platform, all third-party business platforms are called, so that the third-party business platforms can summarize the information of all related devices connected to them that they can identify. Thus, each third-party business platform will send a device list of all devices to the local business platform. The local business platform summarizes these lists and generates a second temporary list list2.

[0052] According to the contents of the first and second temporary lists formed in the above process, abnormal devices can be screened out. Specifically, the screening process for abnormal devices will be performed in step 2.

[0053] Step 2, after sequentially extracting the device codes in the local device list, traverse the device codes in all device lists to perform a search and comparison, and record the abnormal devices in the abnormal device list.

[0054] Abnormal devices can be filtered out by comparing the first temporary list and the second temporary list extracted in step 1. In the present invention, the local service platform can set a scheduled task, so as to automatically start the retrieval and comparison of the device codes of all physical devices in the platform after the scheduled time arrives.

[0055] Specifically, the retrieval and comparison process can be performed in a multiple retrieval and comparison manner. The first retrieval and comparison can be performed on all devices. When abnormal devices are found, a second retrieval and comparison is performed on these devices. By continuously narrowing the scope through multiple retrieval and comparison, the information of abnormal devices is continuously modified to normal devices, thereby reducing the number of abnormal devices. Finally, the abnormal devices are locked in the part that can only be modified by manual detection, and the screening and processing of abnormal devices can be completed.

[0056] Figure 2 FIG. 1 is a schematic diagram of a search and comparison in a method for screening and processing abnormal devices based on a third-party business platform of the present invention. Figure 2 As shown, preferably, a retrieval comparison includes: step 2.1, extracting the device codes in the local device list in turn, and traversing the device codes in all device lists based on the device codes in each local device list; step 2.2, when the device codes in all device lists are found to match the device codes in the local device list, sending a play request to the device and executing the play function based on the play address fed back by the device; step 2.3, if the play function can be executed based on the device play address, it is determined that the device is a normal device, otherwise it is an abnormal device, until the retrieval comparison of the device codes in all local device lists is completed.

[0057] Specifically, the present invention can use a traversal method to extract the device code of a device from the first temporary list list1 one by one. Then, for this device code, it is compared one by one with all the data in the second temporary list list2. If it is found that the device code is consistent during the traversal of the second temporary list list2, it means that the corresponding device has been matched. At this time, the local service platform can issue a communication request to request the device in the third-party service platform to feedback the playback address of the device.

[0058] It should be noted that, in one embodiment of the present invention, the devices connected to the local business platform and the third-party business platform are all monitoring devices for realizing power plant monitoring. Therefore, these monitoring devices can use cameras to capture the environment inside the power plant and transmit the captured data back to the platform end for playback on the platform end. Therefore, when further confirming the identity of the device, the playback address of the device can be retrieved.

[0059] Of course, the devices connected to the local business platform and the third-party business platform are not limited to monitoring devices for power plant monitoring, but can also be other types of devices. Then, when further confirming the identity of the device, other similar methods can be used to confirm the device information. For example, if it is a mobile terminal device, identity confirmation can be achieved by sending short messages.

[0060] Next, since the playback address of the device is stored and recorded in the manufacturer's security monitoring platform, when the local business platform obtains the playback address of the device from the third-party business platform, the monitoring video can be played according to the playback address. In one embodiment of the present invention, the power plant business platform can be used as a local business platform to extract the device playback address from multiple manufacturer security monitoring platforms that are third-party business platforms by using the device encoding data item stored in the power plant business platform as a parameter, and using this parameter to obtain the playback address of the device in the manufacturer's security monitoring platform.

[0061] When normal playback can be performed according to the current playback address, it means that the local service platform can retrieve data from the current device normally. If the above steps can be achieved, it means that the retrieval comparison is successful and the current device can be excluded from abnormal devices. In this way, all data in the first temporary list list1 can be traversed to filter out all abnormal devices.

[0062] Preferably, after determining that each device is a normal device, the corresponding record of each device in the device list is deleted.

[0063] In this way, each time a normal device is found, the subsequent traversal calculation process will be simplified, for example, the workload of the subsequent primary search and comparison and the workload of the secondary search and comparison will be greatly reduced. In addition, in this way, abnormal devices can be further excluded. For example, although the device name is the same, but the device number is different, these normal devices can be excluded in the process of a single search and comparison.

[0064] Preferably, if the playback function cannot be performed based on the device playback address, the device is determined to be an abnormal device and the device is recorded in an abnormal list.

[0065] It is understandable that if the data of the device cannot be obtained normally according to the playback address of the current device, and the normal playback function cannot be performed, it can be judged that the current device is an abnormal device. The playback address is automatically assigned or generated by the manufacturer's security monitoring platform according to the characteristics of the device during the device's factory process, and is stored in the manufacturer's security monitoring platform. The specific method for obtaining it can adopt the commonly used methods in the prior art.

[0066] It should be noted that the device playback address in the present invention can automatically and synchronously update the device playback address after the system replaces or adds, deletes, or modifies the device code. That is to say, after the power plant business platform automatically changes the device code using the method in the present invention, it will use the new device code to obtain the new device playback address of the manufacturer's security platform, and the updated playback address is obtained.

[0067] If this happens, the device can be recorded in the exception list. Specifically, the exception list can be stored in the local business platform as a dynamically modifiable and editable data list, and can be dynamically added, deleted, and modified according to the retrieval and comparison. In the present invention, if it is found that although the first temporary list list1 and the second temporary list list2 have completely corresponding device codes, the transmission and playback of device data cannot be achieved, it means that the device itself may have an abnormality, such as device damage, etc., or there is a problem with the recording of device coding information in the local business platform or the third-party business platform. In this case, the original device information table in the local business platform database can be called according to the device number in the first temporary list list1, the device information can be collected therefrom, and the device can be added to the exception list.

[0068] Preferably, the abnormal device list includes the device number, device code, device name, device area address, device area organization and device playback address of the device.

[0069] Generally speaking, the structure of the exception list may be different from that of the first and second temporary lists. The exception list may include more specific equipment information. For example, the corresponding equipment number, equipment area organization and other information in the data table storing equipment information in the local power plant business platform can be called out and added to the exception list. In addition, the device name, equipment area address and equipment playback address of the corresponding equipment can also be obtained from the manufacturer's security monitoring platform. By maintaining the exception list in this way, the specific information of the equipment can be included in the finally generated exception list, which facilitates the generation and sending of equipment work orders to maintenance personnel.

[0070] Preferably, when no matching device code in all device lists is found based on the device code in the local device list, a secondary search and comparison is performed on the device record.

[0071] If the device code of a certain device in the first temporary list list1 does not find a matching device code in the second temporary list list2, a secondary search and comparison can be performed on such devices.

[0072] Step 3: based on the result of the first search and comparison, extract the device name of the device that failed to match, traverse the device names in the list of all devices to perform a second search and comparison, and record the abnormal device in the abnormal device list.

[0073] Since the extracted abnormal device list may also include devices that can be matched through other information, a secondary search and comparison is required. In actual practice, this situation often occurs. This is because when some equipment fails, the equipment needs to be repaired by a third-party business platform. During the maintenance process, the device will no longer exist on the third-party business platform. After the maintenance is completed, although it is the same device with the same device name, device address and other information, it will be returned to the same location in the power plant after the maintenance is completed to perform the same tasks as before, but when it is reloaded to the third-party business platform, the third-party business platform will reallocate a new UUID code for it.

[0074] When the device logs in to the third-party business platform with a new UUID code, the local business platform cannot recognize the update of the device. This may lead to the following situation. The local business platform will assign a new local business platform UUID, i.e., the device number, to the device based on the UUID code of the device. At the same time, the previous device number is shelved, and the corresponding device code is no longer valid. The correct video data can no longer be obtained based on the device number and device code, which causes problems on the business side of the local business platform. Since the device has a new device number and device code, if you want to complete the original business, you need to develop new code to change the way to retrieve the device information. This greatly increases the workload of the local business platform.

[0075] In the present invention, this trouble can be eliminated by secondary search and comparison. Preferably, the secondary search and comparison includes: step 3.1, based on the result of the primary search and comparison, extract the device name of the device from the local device list, and traverse the device names in all device lists; step 3.2, when the device name of the device is found to match the device name in all device lists, determine that the current device is a normal device, otherwise it is an abnormal device; step 3.3, based on the device code of the current device recorded in the third-party service platform, modify the device code of the current device in the local service platform.

[0076] In the present invention, a secondary search and comparison can be performed based on the result of the primary search and comparison, that is, the content in the abnormal device list, thereby greatly reducing the workload. Generally speaking, when the device described above is used again in the same location of the power plant after being returned to the factory for repair, the name and address of the device and other information are usually not changed. Therefore, the secondary search and comparison can be implemented based on information such as the device name and the device area address.

[0077] First, when a search and comparison fails, the device name of the current device can be extracted from the local device list according to the result, and the device name of the device is compared with the device names in the list of all devices.

[0078] When a matching device name is found, it means that although the device code has been modified, the device information in the local business platform and the device information in the third-party business platform can be matched based on the consistency of the device name. Therefore, the device code of the device recorded in the original database of the local business platform can be modified based on the device code in the third-party business platform. In this way, the device can be easily re-identified without modifying the upper-level business of the local business platform. The method is simple and low-cost, and can effectively modify the originally abnormal device into a normal device through automated means, reducing the complexity of manual detection. When the device code of the device is modified, or before or after it is modified, the device can be deleted from the list of abnormal devices.

[0079] Preferably, the device name in the abnormal device list matches the device name in the all device list specifically in that: the device name in the abnormal device list matches the only device name in the all device list.

[0080] It is understandable that, generally speaking, the device names artificially defined according to the naming rules should be different from each other, but there is also the possibility of duplicate names. Therefore, in order to eliminate this possibility, in the secondary search and comparison process, the condition for successful device name matching is strictly limited to that there can only be one device name in the third-party business platform that is consistent with the device name in the local business platform.

[0081] Preferably, when a device name in the abnormal device list is retrieved and matches more than one device name in the all device list, more than one device is manually detected based on current device information in the abnormal device list, and the duplicate device name is modified based on the manual detection result.

[0082] Preferably, performing manual inspection on more than one device further comprises:

[0083] The device area addresses of the more than one devices are extracted, and a manual inspection work order is generated based on the device area addresses.

[0084] Specifically, during the secondary search and comparison process, when multiple device names are found to match, a work order for manual inspection can be generated for the duplicated devices, allowing maintenance personnel to determine the specific problem on site. In order to provide maintenance personnel with the location of the equipment, the work order should at least include information on the equipment area address.

[0085] Step 4, record the devices that were not successfully matched in the secondary search and comparison, and use manual methods to change the information.

[0086] After receiving the manual inspection work order, the maintenance personnel will find the specific equipment according to the equipment area address, and after judging the specific problem, they will find the cause of the abnormal problem. According to the cause, they will determine whether the equipment needs to be repaired, or whether the abnormal problem can be solved by simply changing the equipment information. If the abnormal problem of the equipment can be solved by simply changing the equipment information, the information can be changed manually.

[0087] Figure 3 FIG. 1 is a flowchart of abnormal device screening in an embodiment of an abnormal device screening and processing method based on a third-party business platform of the present invention. Figure 3 As shown, the method of the present invention is generally divided into multiple steps. In multiple steps, two retrieval comparisons can be performed, and the information of abnormal devices can be determined according to specific circumstances. If there are still abnormal device records in the abnormal device list after completing the retrieval comparison process and all abnormal device screening processes, manual detection is required, otherwise all device abnormal problems can be solved without manual detection.

[0088] The second aspect of the present invention relates to an abnormal equipment screening and processing system based on a third-party business platform, wherein a local business platform is communicatively connected with one or more third-party business platforms, and an abnormal equipment screening and processing method based on a third-party business platform as described in the first aspect of the present invention is implemented.

[0089] The beneficial effect of the present invention is that, compared with the prior art, the abnormal device screening and processing method and system based on the third-party business platform in the present invention can extract the device code and device name of the device in the local business platform and the third-party business platform, and perform multiple searches and comparisons on the device list, thereby screening out abnormal devices. The method in the present invention is simple, has a fast data processing speed, does not cause huge pressure on the server, and can accurately detect abnormal devices without omission, and accurately locate the cause of the abnormality.

[0090] The applicant of the present invention has made a detailed explanation and description of the implementation examples of the present invention in conjunction with the drawings in the specification. However, those skilled in the art should understand that the above implementation examples are only preferred implementation schemes of the present invention, and the detailed description is only to help readers better understand the spirit of the present invention, but not to limit the scope of protection of the present invention. On the contrary, any improvements or modifications based on the inventive spirit of the present invention should fall within the scope of protection of the present invention.

Claims

1. A method for screening and processing abnormal devices based on a third-party business platform, characterized in that: The method comprises the following steps: Step 1: extract device information of all devices from the local service platform and generate a local device list, and extract device information of all devices from the third-party service platform and generate a list of all devices; Step 2, after sequentially extracting the device codes in the local device list, traverse the device codes in all the device lists to perform a search and comparison, and record the abnormal devices in the abnormal device list; The one-time search comparison includes: Step 2.1, extracting device codes in the local device list in turn, and traversing the device codes in all device lists based on each device code in the local device list; Step 2.2, when it is found that the device code in the list of all devices matches the device code in the local device list, a play request is sent to the device and a play function is executed based on the play address fed back by the device; Step 2.3, if the playback function can be performed based on the device playback address, the device is determined to be a normal device, otherwise it is an abnormal device, until the retrieval and comparison of device codes in all local device lists are completed; Step 3, based on the result of the first search and comparison, extract the device name of the device that failed to match, traverse the device names in the list of all devices to perform a second search and comparison, and record the abnormal device in the abnormal device list; The secondary search and comparison includes: Step 3.1, based on a search and comparison result, extract the device name of the device from the local device list, and traverse the device names in all device lists; Step 3.2, when the device name of the device is found to match the device name in the list of all devices, the current device is determined to be a normal device, otherwise it is an abnormal device; Step 3.3, based on the device code of the current device recorded in the third-party service platform, modify the device code of the current device in the local service platform; Step 4, record the devices that were not successfully matched in the secondary search and comparison, and use manual methods to change the information.

2. According to claim 1, a method for screening and processing abnormal devices based on a third-party business platform is characterized in that: The device information of all devices extracted from the third-party service platform includes the device code, device name and device area address assigned by the third-party service platform; The device information of all devices extracted from the local service platform includes the device number and device area organization assigned by the local service platform, and the device code, device name and device area address from the third-party service platform.

3. According to the method for screening and processing abnormal devices based on a third-party business platform as described in claim 1, it is characterized by: After determining that each device is a normal device, the corresponding record of each device in the list of all devices is deleted.

4. According to the method for screening and processing abnormal devices based on a third-party business platform as described in claim 1, it is characterized by: If the playback function cannot be performed based on the playback address of the device, it is determined that the device is an abnormal device and the device is recorded in an abnormal list.

5. According to the method for screening and processing abnormal devices based on a third-party business platform as described in claim 1, it is characterized by: When no matching device code in the list of all devices is found based on the device code in the local device list, a secondary search and comparison is performed on the device.

6. A method for screening and processing abnormal devices based on a third-party service platform according to claim 4 or 5, characterized in that: The abnormal device list includes the device number, device code, device name, device area address, device area organization and device playback address of the device.

7. According to the method for screening and processing abnormal devices based on a third-party business platform as described in claim 1, it is characterized by: The device names in the abnormal device list match the device names in the all device list specifically as follows: The device name in the abnormal device list matches the only device name in the all device list.

8. The method for screening and processing abnormal devices based on a third-party business platform according to claim 7, characterized in that: When the device name in the abnormal device list is retrieved to match more than one device name in the all device list, the more than one devices are manually detected based on the current device information in the abnormal device list, and the duplicate device name is modified based on the manual detection result.

9. The method for screening and processing abnormal devices based on a third-party business platform according to claim 8, characterized in that: The device area addresses of the more than one devices are extracted, and a manual inspection work order is generated based on the device area addresses.

10. An abnormal equipment screening and processing system based on a third-party business platform, characterized in that: In the system, a local business platform is communicatively connected with one or more third-party business platforms, and an abnormal device screening and processing method based on a third-party business platform as described in any one of claims 1-9 is implemented.

Images