Equipment management method and device
By parsing and processing the parameters in the verification report and generating equipment management information, the problem of management errors caused by staff's regular screening of verification reports is solved, and intelligent and efficient equipment management is achieved.
Patent Information
- Application Number
- CN202510721672.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-30
- Publication Date
- 2025-09-12
AI Technical Summary
In the prior art, errors may occur during the periodic screening and verification of reports by staff, affecting the accuracy and efficiency of equipment management.
By obtaining the verification report in the compressed file, parsing the verification parameters according to the target parsing format, and using the preset functional modules to process these parameters to generate equipment management information, including verification distribution diagrams, historical summary information and expiration reminders.
It improves the accuracy and efficiency of equipment management, reduces human errors, and realizes intelligent management of equipment.
Smart Images
Figure CN120634012A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a device management method and apparatus. Background Art
[0002] Equipment inspection and verification involves testing the performance and quality of equipment to verify compliance with relevant regulations and standards. The purpose of inspection and verification is to ensure equipment safety and ensure its scientific management. Different types of equipment require different inspection and verification methods and objectives, and these inspections and verifications are conducted by qualified institutions or organizations.
[0003] Currently, verification reports are usually kept by staff and regularly screened to complete subsequent equipment management. However, errors may occur during the regular screening of verification reports by staff, thus affecting equipment management. Summary of the Invention
[0004] The present application provides a device management method and apparatus, which can improve the management capabilities of devices.
[0005] To achieve the above objectives, this application adopts the following technical solutions:
[0006] In a first aspect, the present application provides a device management method. In this method, a compressed file is obtained, comprising multiple verification reports. The verification reports indicate the verification status of a target device, with each target device corresponding to one verification report. Each verification report is parsed according to a target parsing format to obtain verification parameters within the verification report. The verification parameters are then processed based on a preset functional module to obtain device management information.
[0007] Based on the above technical solution, a compressed file is obtained, which includes multiple verification reports. The verification reports are used to indicate the verification status of the target device, with each target device corresponding to a verification report. For each verification report, the verification report is parsed according to the target parsing format to obtain the verification parameters in the verification report. In this way, the verification reports can be parsed in batches according to the target parsing format to obtain the verification parameters. The verification parameters can then be processed based on the preset functional modules to obtain device management information. In this way, the parsed verification parameters can be further utilized to facilitate device management.
[0008] In one possible implementation, the verification parameters include at least one of the following: the identification of the target device, the device type, the device description information, the current verification date, and the next verification date. The identification of the target device includes at least one of the following: the device tag number, the factory number, and the manufacturer; the current verification date is the verification date corresponding to the verification report.
[0009] In one possible implementation, the preset functional module is a verification date distribution module, which corresponds to the current verification date and the next verification date. The verification date distribution module generates a first verification distribution graph based on the current verification date. The first verification distribution graph indicates the distribution of each target device on the current verification date. The verification date distribution module generates a second verification distribution graph based on the next verification date. The second verification distribution graph indicates the distribution of each target device on the next verification date.
[0010] In one possible implementation, the preset functional module is a historical verification report viewing module, which corresponds to an identifier of a target device. The historical verification report viewing module obtains the identifier of a first device and, based on the identifier of the first device, determines a historical verification report corresponding to the first device from a database. The database stores historical verification reports for each target device, where the first device is any one of the multiple target devices. The historical verification report viewing module generates historical summary information for the first device based on the historical verification report corresponding to the first device.
[0011] In one possible implementation, the preset functional module is an expiration reminder module, which corresponds to the next verification date. The current date and the next verification date of each target device are obtained through the expiration reminder module. The second device is determined from multiple target devices based on the current date and the next verification date of each target device through the expiration reminder module, and the difference between the next verification date corresponding to the second device and the current date is less than a preset time threshold. The expiration reminder module generates an expiration reminder message, which is used to instruct the verification of the second device.
[0012] In one possible implementation, a template format for a validation report is obtained. Based on the validation report template format and multiple preset parsing formats, multiple format similarities are determined. The format similarity is the similarity between the validation report template format and the preset parsing formats, with each preset parsing format corresponding to one format similarity. Based on the multiple format similarities, a target parsing format is determined from the multiple preset parsing formats. The target parsing format is the preset parsing format corresponding to the greatest format similarity among the multiple format similarities. If the validation report is successfully parsed according to the target parsing format, validation parameters in the validation report are obtained.
[0013] In one possible implementation, if an exception occurs when parsing the validation report according to the target parsing format, the file format of the validation report is obtained. If the file format is a format that supports parsing, a parsing format generation requirement is generated. Based on the format generation requirement, a first parsing format is obtained, where the first parsing format matches the format of the validation report. The validation report is parsed according to the first parsing format to obtain validation parameters in the validation report.
[0014] In a possible implementation, the first parsed format is stored.
[0015] In a possible implementation, when the file format is a format that cannot be parsed, the format of the verification report is converted into a format that supports parsing.
[0016] In a second aspect, the present application provides a device management apparatus, the apparatus comprising:
[0017] The acquisition module is configured to obtain a compressed file containing multiple verification reports. The verification reports indicate the verification status of the target device, with each target device corresponding to one verification report. The processing module is configured to parse each verification report according to the target parsing format to obtain verification parameters contained in the verification report. The processing module is further configured to process the verification parameters based on the preset functional module to obtain device management information.
[0018] In a third aspect, the present application provides a device management device, which includes: a processor and a memory; the processor and the memory are coupled; the memory is used to store one or more programs, and the one or more programs include computer-executable instructions. When the device management device is running, the processor executes the computer-executable instructions stored in the memory to implement the method described in the first aspect and any possible implementation of the first aspect.
[0019] In a fourth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a computer, the computer executes the method described in the above-mentioned first aspect and any possible implementation of the first aspect.
[0020] In a fifth aspect, the present application provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run a computer program or instructions to implement the method described in the first aspect and any possible implementation of the first aspect.
[0021] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to execute the method described in the above-mentioned first aspect and any possible implementation of the first aspect.
[0022] In the above scheme, the technical problems that can be solved and the technical effects achieved by the equipment management device, computer, computer storage medium, chip or computer program product can be referred to the technical problems and technical effects solved by the above first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Figure 1 A flowchart of a device management method provided in an embodiment of the present application;
[0024] Figure 2 A flowchart of another device management method provided in an embodiment of the present application;
[0025] Figure 3 A schematic diagram of the structure of a device management device provided in an embodiment of the present application;
[0026] Figure 4 A schematic diagram of the structure of another device management device provided in an embodiment of the present application;
[0027] Figure 5 A conceptual partial view of a computer program product provided in an embodiment of the present application. DETAILED DESCRIPTION
[0028] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0029] Furthermore, the terms "including," "having," and any variations thereof, as used in the description of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or modules is not limited to the listed steps or modules, but may optionally include other steps or modules not listed, or may optionally include other steps or modules inherent to the process, method, product, or apparatus.
[0030] Additionally, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present concepts in a concrete manner.
[0031] like Figure 1 As shown, a device management method provided in an embodiment of the present application includes:
[0032] S101: Obtain a compressed file.
[0033] The compressed file includes multiple verification reports, which are used to indicate the inspection status of the target device. One target device corresponds to one verification report.
[0034] In a possible implementation, multiple verification reports may be obtained and then compressed to obtain a compressed file.
[0035] In another possible implementation, the compressed file may be uploaded through an upload tool.
[0036] S102. For each verification report, parse the verification report according to the target parsing format to obtain verification parameters in the verification report, thereby obtaining the verification parameters in each verification report.
[0037] In an embodiment of the present application, the verification parameters include at least one of the following: the identification of the target device, the device type, the device description information, the current verification date and the next verification date. The identification of the target device includes at least one of the following: the device position number, the factory number and the manufacturer; the current verification date is the verification date corresponding to the verification report.
[0038] In one possible implementation, each target resolution position in the verification report may be parsed according to a target resolution format to obtain verification parameters in the verification report, wherein the target resolution format includes multiple target resolution positions and preset parameters corresponding to each target resolution position.
[0039] It should be understood that the target resolution position refers to the position of the preset parameters in the verification report.
[0040] For example, if the verification report is a table file, the multiple target parsing locations may include: row 1, column 1, row 1, column 2, and row 1, column 3. The row 1, column 1 corresponds to the device ID, the row 1, column 2 corresponds to the current verification date, and the row 1, column 3 corresponds to the next verification date.
[0041] In this way, the corresponding verification parameters can be obtained according to the analytical position of each target.
[0042] Optionally, the verification parameters corresponding to the target resolution position in the verification report may be obtained according to the parameter format of the preset parameters corresponding to the target resolution position, where one target resolution position corresponds to one parameter format.
[0043] For example, the first row and the first column correspond to the equipment number, and the parameter format is a string format; the first row and the second column correspond to the current verification date, and the parameter format is a time format.
[0044] It should be understood that only when the parameter format of the verification parameter matches the parameter format corresponding to the target parsing position can the verification parameter corresponding to the target parsing position in the verification report be parsed and obtained.
[0045] In some embodiments, after obtaining the verification parameters, the verification parameters of the target resolution position may be stored according to a parameter format corresponding to the target resolution position.
[0046] In this way, the accuracy of the verification parameter format can be guaranteed and abnormalities in the data storage process can be avoided.
[0047] Optionally, the authentication parameters may be stored according to data encryption techniques.
[0048] Optionally, the verification report may be processed based on the data protection module to obtain a processed verification report.
[0049] Exemplarily, the data protection module may include: a data theft prevention module, an anti-screenshot module, and a watermark encryption module.
[0050] Optionally, the operation information of the verification parameters may be recorded and stored, such as the operator and the operation time.
[0051] S103: Process the verification parameters based on the preset function module to obtain device management information.
[0052] The device management information is information associated with the verification target device.
[0053] In the embodiment of the present application, a plurality of preset function modules may be included, and different preset function modules can perform different equipment verification management functions, wherein different preset function modules correspond to different verification parameters.
[0054] That is to say, different preset functional modules can obtain device management information through corresponding verification parameters.
[0055] It is understandable that since the preset function module only needs to use the corresponding verification parameters to obtain the corresponding device management information, the amount of data to be processed can be reduced, thereby improving processing efficiency.
[0056] Based on the above technical solution, a compressed file is obtained, which includes multiple verification reports. The verification reports are used to indicate the verification status of the target device, with each target device corresponding to a verification report. For each verification report, the verification report is parsed according to the target parsing format to obtain the verification parameters in the verification report. In this way, the verification reports can be parsed in batches according to the target parsing format to obtain the verification parameters. The verification parameters can then be processed based on the preset functional modules to obtain device management information. In this way, the parsed verification parameters can be further utilized to facilitate device management.
[0057] In some embodiments, the preset functional module is a verification date distribution module, and the verification date distribution module corresponds to the current verification date and the next verification date.
[0058] In this embodiment of the present application, the verification date distribution module generates a first verification distribution graph based on the current verification date. The first verification distribution graph indicates the distribution of each target device on the current verification date. The verification date distribution module generates a second verification distribution graph based on the next verification date. The second verification distribution graph indicates the distribution of each target device on the next verification date.
[0059] That is, the device management information may include the first verification distribution graph and the second verification distribution graph, thereby facilitating the review and statistics of the current date and the next verification date of each target device.
[0060] In some embodiments, the preset functional module is a historical verification report viewing module, and the historical verification report viewing module corresponds to the identifier of the target device.
[0061] In an embodiment of the present application, a historical verification report viewing module can obtain an identifier of a first device and, based on the identifier of the first device, determine a historical verification report corresponding to the first device from a database. The database stores historical verification reports for various target devices, where the first device is any one of the multiple target devices. The historical verification report viewing module can then generate historical summary information for the first device based on the historical verification report corresponding to the first device.
[0062] For example, if you need to find the historical verification report of device a, you can obtain the identification of device a (such as device number, factory number and manufacturer). Then, you can find the historical verification report of device a based on the identification of device a and summarize it into historical summary information.
[0063] It is understandable that the historical verification report viewing module allows users to intuitively view the historical verification report of the device, which helps users to have a more comprehensive understanding of the device.
[0064] In some embodiments, the preset functional module is a near-expiry reminder module, which corresponds to the next verification date.
[0065] In an embodiment of the present application, the expiration reminder module can be used to obtain the current date and the next verification date for each target device. Subsequently, the expiration reminder module determines a second device from the multiple target devices based on the current date and the next verification date for each target device, where the difference between the next verification date corresponding to the second device and the current date is less than a preset time threshold. The expiration reminder module then generates an expiration reminder message, which instructs the second device to be verified.
[0066] It should be understood that the embodiments of the present application do not limit the preset time threshold. For example, the preset time threshold can be 1 day, 2 days, 3 days, etc.
[0067] In this way, the user can be reminded to verify the second device which is approaching the next verification date, and generate a new verification report.
[0068] like Figure 2 As shown, another device management method provided by an embodiment of the present application, in which S102 may include:
[0069] S201. Obtain a template format of a verification report.
[0070] In a possible implementation, the parameter position of each verification parameter in the verification report may be obtained, and then a template format of the verification report may be generated based on the parameter position of each verification parameter.
[0071] For example, through identification, it can be determined that the equipment number is located in the first row and first column, the current verification date is located in the first row and second column, and the next verification date is located in the first row and third column.
[0072] In another possible implementation, a correspondence between multiple preset format identifiers and multiple preset template formats may be stored. The format identifier of the verification report may be obtained, and based on the format identifier of the verification report and the correspondence between the multiple preset format identifiers and the multiple preset template formats, the template format of the verification report may be determined from the multiple preset template formats.
[0073] S202: Determine multiple format similarities based on the template format of the verification report and multiple preset parsing formats.
[0074] The preset parsing format includes the parameter position of each verification parameter. The format similarity is the similarity between the template format of the verification report and the preset parsing format, and one preset parsing format corresponds to one format similarity.
[0075] In a possible implementation, for a preset parsing format, format similarity is determined based on the parameter position of each verification parameter in the template format of the verification report and the parameter position of each verification parameter in the preset parsing format.
[0076] For example, the format similarity may be determined based on the number of all parameter positions and the number of verification parameters located at the same parameter position.
[0077] For example, if the verification parameter 1 in the verification report template format is located at position 1, verification parameter 2 is located at position 2, verification parameter 3 is located at position 3, and verification parameter 4 is located at position 4. If, in the preset parsing format 1, verification parameter 1 is located at position 1, verification parameter 2 is located at position 2, verification parameter 3 is located at position 5, and verification parameter 4 is located at position 4, then the total number of parameter positions is 4, the number of verification parameters located at the same parameter position is 3, and the format similarity is 75%.
[0078] S203: Determine a target parsing format from a plurality of preset parsing formats based on the plurality of format similarities.
[0079] The target parsing format is a preset parsing format corresponding to the largest format similarity among the multiple format similarities.
[0080] S204: Determine whether the parsing of the verification report according to the target parsing format is successful.
[0081] In one possible implementation, if the parameter positions of each validation parameter in the validation report template format match the parameter positions of each validation parameter in the target parsing format, it can be determined that the parsing of the validation report according to the target parsing format is successful. If there are parameter positions in the target parsing format that do not match the parameter positions of the validation parameters in the validation report template format, it is determined that the parsing of the validation report according to the target parsing format is abnormal.
[0082] It should be understood that the presence of parameter positions in the target parsing format that do not match the parameter positions of the verification parameters in the template format of the verification report means that the verification parameters corresponding to the same parameter position in the target parsing format and the verification report are different.
[0083] In some embodiments, if the verification report is successfully parsed according to the target parsing format, S205 is executed.
[0084] S205. Obtain verification parameters in the verification report.
[0085] In the embodiment of the present application, when the verification report is parsed successfully according to the target parsing format, the verification parameters in the verification report are obtained.
[0086] Based on the above technical solution, a template format of the verification report is obtained. Based on the template format of the verification report and multiple preset parsing formats, multiple format similarities are determined. The format similarity is the similarity between the template format of the verification report and the preset parsing format, and one preset parsing format corresponds to one format similarity. In this way, based on the multiple format similarities, a target parsing format can be determined from multiple preset parsing formats. The target parsing format is the preset parsing format corresponding to the largest format similarity among the multiple format similarities. Then, if the verification report is successfully parsed according to the target parsing format, the verification parameters in the verification report can be obtained. In this way, the best template format can be selected from multiple preset parsing formats, and the verification parameters in the verification report can be obtained.
[0087] In some embodiments, if an exception occurs when parsing the validation report according to the target parsing format, the file format of the validation report is obtained. If the file format is a format that supports parsing, a parsing format generation requirement is generated, wherein the parsing format generation requirement is used to indicate the parameter location of each validation parameter in the validation report. Based on the format generation requirement, a first parsing format is obtained, and the first parsing format matches the format of the validation report. Then, the validation report is parsed according to the first parsing format to obtain the validation parameters in the validation report.
[0088] It should be understood that parsing anomalies may be caused by file format mismatch or parsing format mismatch. Therefore, it is possible to first determine whether the file format is a format that supports parsing, then generate parsing format generation requirements, and obtain the first parsing format, thereby obtaining verification parameters.
[0089] Optionally, a correspondence between the first parsing format and the format of the verification report may be stored.
[0090] Optionally, the parsing format generation requirement may be generated based on the parameter position of each verification parameter in the verification report. Alternatively, the parsing format generation requirement may be received from a user uploaded file.
[0091] In some embodiments, if the file format is a format that cannot be parsed, the format of the verification report is converted into a format that supports parsing.
[0092] For example, the formats that can be parsed may be Word format or Portable Document Format (PDF) format. The formats that cannot be parsed may be pictures, which can be converted into PDF format.
[0093] Optionally, when an exception occurs when parsing the verification report according to the target parsing format, exception information may be generated, where the exception information is used to indicate a reason for the exception in parsing the verification report.
[0094] In some embodiments, the device management apparatus is further deployed with an accessory tool. Other devices or systems can send a call request to the device management apparatus, the call request being used to instruct the device management apparatus to obtain device management information and / or verification parameters of each verification report by calling the accessory tool.
[0095] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. It is understandable that, in order to realize the above functions, the device management device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the device management method steps of each example described in the embodiment disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0096] The present application also provides a device management apparatus, which can be a mobile terminal or a computing device, a CPU in the mobile terminal, a management module in the mobile terminal for managing devices, or a client in the mobile terminal for managing devices.
[0097] The embodiment of the present application can divide the equipment management device into functional modules or functional units according to the above method example. For example, each functional module or functional unit can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules or functional units. Among them, the division of modules or units in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.
[0098] The embodiment of the present application provides a device management device. Figure 3 As shown, the device management apparatus may include: an acquisition module 301 and a processing module 302 .
[0099] Acquisition module 301 is configured to obtain a compressed file containing multiple verification reports. The verification reports indicate the verification status of the target device, with each target device corresponding to one verification report. Processing module 302 is configured to parse each verification report according to the target parsing format to obtain verification parameters contained in the verification report. Processing module 302 is further configured to process the verification parameters based on a preset functional module to obtain device management information.
[0100] In one possible implementation, the verification parameters include at least one of the following: the identification of the target device, the device type, the device description information, the current verification date, and the next verification date. The identification of the target device includes at least one of the following: the device tag number, the factory number, and the manufacturer; the current verification date is the verification date corresponding to the verification report.
[0101] In one possible implementation, the preset functional module is a verification date distribution module, which corresponds to the current verification date and the next verification date. Processing module 302 is further configured to generate, using the verification date distribution module, a first verification distribution graph based on the current verification date. The first verification distribution graph indicates the distribution of each target device on the current verification date. Processing module 302 is further configured to generate, using the verification date distribution module, a second verification distribution graph based on the next verification date. The second verification distribution graph indicates the distribution of each target device on the next verification date.
[0102] In one possible implementation, the preset functional module is a historical verification report viewing module, which corresponds to the target device's identifier. Processing module 302 is further configured to obtain the identifier of the first device through the historical verification report viewing module and, based on the identifier of the first device, determine a historical verification report corresponding to the first device from a database, the database storing historical verification reports for each target device, where the first device is any one of the multiple target devices. Processing module 302 is further configured to generate historical summary information for the first device using the historical verification report viewing module according to the historical verification report corresponding to the first device.
[0103] In one possible implementation, the preset functional module is an expiration reminder module, which corresponds to the next verification date. The processing module 302 is also used to obtain the current date and the next verification date of each target device through the expiration reminder module. The processing module 302 is also used to determine the second device from multiple target devices based on the current date and the next verification date of each target device through the expiration reminder module, and the difference between the next verification date corresponding to the second device and the current date is less than a preset time threshold. The processing module 302 is also used to generate an expiration reminder message through the expiration reminder module, and the expiration reminder message is used to instruct the verification of the second device.
[0104] In one possible implementation, the acquisition module 301 is further used to obtain the template format of the verification report. The processing module 302 is further used to determine multiple format similarities based on the template format of the verification report and multiple preset parsing formats. The format similarity is the similarity between the template format of the verification report and the preset parsing format, and one preset parsing format corresponds to one format similarity. The processing module 302 is further used to determine a target parsing format from multiple preset parsing formats based on the multiple format similarities. The target parsing format is the preset parsing format corresponding to the largest format similarity among the multiple format similarities. The processing module 302 is also used to obtain the verification parameters in the verification report when the verification report is successfully parsed according to the target parsing format.
[0105] In one possible implementation, processing module 302 is further configured to obtain the file format of the validation report if an exception occurs during parsing of the validation report according to the target parsing format. Processing module 302 is further configured to generate a parsing format generation requirement if the file format is a format that supports parsing. Processing module 302 is further configured to obtain a first parsing format based on the format generation requirement, where the first parsing format matches the format of the validation report. Processing module 302 is further configured to parse the validation report according to the first parsing format to obtain validation parameters in the validation report.
[0106] In a possible implementation, the processing module 302 is further configured to store the first parsed format.
[0107] In a possible implementation, the processing module 302 is further configured to convert the format of the verification report into a format that supports parsing when the file format is a format that cannot be parsed.
[0108] Figure 4 4 is a schematic diagram showing the structure of a device management apparatus according to an exemplary embodiment. The device management apparatus may include a processor 402, which is configured to execute application code to implement the device management method of the present application.
[0109] The processor 402 may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.
[0110] like Figure 4 As shown, the device management apparatus may further include a memory 403. The memory 403 is used to store application code for executing the solution of the present application, and the execution is controlled by the processor 402.
[0111] The memory 403 may be a read-only memory (ROM) or other static storage device capable of storing static information and instructions, a random access memory (RAM) or other dynamic storage device capable of storing information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and capable of being accessed by a computer, but is not limited thereto. The memory 403 may be independent and connected to the processor 402 via the bus 404. The memory 403 may also be integrated with the processor 402.
[0112] like Figure 4 As shown, the device management apparatus may further include a communication interface 401, wherein the communication interface 401, the processor 402, and the memory 403 may be coupled to each other, for example, via a bus 404. The communication interface 401 is used to exchange information with other devices, for example, to support information exchange between the device management apparatus and other devices.
[0113] It should be pointed out that Figure 4 The equipment structure shown in the figure does not constitute a limitation on the equipment management device, except Figure 4 In addition to the components shown, the equipment management device may include more or fewer components than shown, or combine certain components, or arrange the components differently.
[0114] In actual implementation, the functions implemented by the processing unit can be Figure 4 The processor 402 shown calls the program code in the memory 403 to implement it.
[0115] The present application also provides a computer-readable storage medium having instructions stored thereon. When the instructions in the computer-readable storage medium are executed by a processor of a computer device, the computer device is enabled to execute the device management method provided in the above-described embodiment. For example, the computer-readable storage medium may be a memory 403 including instructions, and the instructions may be executed by the processor 402 of the computer device to perform the above-described method. Alternatively, the computer-readable storage medium may be a non-transitory computer-readable storage medium, for example, a ROM, RAM, CD-ROM, magnetic tape, floppy disk, or optical data storage device.
[0116] Figure 5 A conceptual partial view of a computer program product provided by an embodiment of the present application is schematically shown. The computer program product includes a computer program for executing a computer process on a computing device.
[0117] In one embodiment, a computer program product is provided using a signal bearing medium 500. Signal bearing medium 500 may include one or more program instructions.
[0118] In some examples, the signal-bearing medium 500 may include a computer-readable medium 501, such as, but not limited to, a hard drive, a compact disk (CD), a digital video disk (DVD), a digital tape, a memory, a read-only memory (ROM), or a random access memory (RAM), and the like.
[0119] In some implementations, signal bearing medium 500 may include computer recordable medium 502 such as, but not limited to, memory, read / write (R / W) CD, R / W DVD, or the like.
[0120] In some embodiments, signal bearing medium 500 may include communication medium 503 such as, but not limited to, digital and / or analog communication media (eg, fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).
[0121] The signal bearing medium 500 may be conveyed by a wireless form of communication medium 503. The one or more program instructions may be, for example, computer executable instructions or logic implemented instructions.
[0122] In some examples, the device management apparatus may be configured to provide various operations, functions, or actions in response to one or more program instructions via computer-readable medium 501 , computer-recordable medium 502 , and / or communication medium 503 .
[0123] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.
[0124] It should be understood that in the several embodiments provided in this application, the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0125] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the classified units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0126] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0127] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all categories or parts of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all categories or partial steps of the methods of each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
[0128] The above are only specific embodiments of the present application, but the scope of protection of the present application is not limited thereto. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.
Claims
1. A device management method, characterized in that: The method comprises: Obtaining a compressed file, wherein the compressed file includes a plurality of verification reports, wherein the verification reports are used to indicate the inspection status of the target device, and each target device corresponds to one verification report; For each of the verification reports, the verification report is parsed according to a target parsing format to obtain verification parameters in the verification report, thereby obtaining verification parameters in each of the verification reports; The verification parameters are processed based on a preset function module to obtain device management information.
2. The method according to claim 1, characterized in that The verification parameters include at least one of the following: the identification of the target device, the device type, the device description information, the current verification date and the next verification date. The identification of the target device includes at least one of the following: the device position number, the factory number and the manufacturer; the current verification date is the verification date corresponding to the verification report.
3. The method according to claim 2, characterized in that The preset function module is a verification date distribution module, which corresponds to the current verification date and the next verification date; the verification parameters are processed based on the preset function module to obtain device management information, including: generating, by the verification date distribution module, a first verification distribution graph according to the current verification date, wherein the first verification distribution graph is used to indicate a distribution of each of the target devices on the current verification date; The verification date distribution module generates a second verification distribution graph according to the next verification date, and the second verification distribution graph indicates the distribution of each of the target devices on the next verification date.
4. The method according to claim 2, characterized in that The preset function module is a historical verification report viewing module, and the historical verification report viewing module corresponds to the identifier of the target device; the verification parameters are processed based on the preset function module to obtain device management information, including: Obtaining an identifier of a first device through the historical verification report viewing module, and determining a historical verification report corresponding to the first device from a database based on the identifier of the first device, the database storing historical verification reports of each of the target devices, the first device being any one of the plurality of target devices; The historical verification report viewing module generates historical summary information of the first device according to the historical verification report corresponding to the first device.
5. The method according to claim 2, characterized in that The preset function module is a near-expiry reminder module, which corresponds to the next verification date; the verification parameters are processed based on the preset function module to obtain device management information, including: Obtaining the current date and the next verification date of each target device through the upcoming reminder module; Determining, by the expiration reminder module, a second device from the plurality of target devices based on the current date and the next verification date of each target device, wherein the difference between the next verification date corresponding to the second device and the current date is less than a preset time threshold; A near-expiry reminder message is generated by the near-expiry reminder module, and the near-expiry reminder message is used to instruct the second device to be verified.
6. The method according to any one of claims 1 to 5, characterized in that The step of parsing the verification report according to the target parsing format to obtain verification parameters in the verification report includes: Obtaining a template format of the verification report; Determining, based on the template format of the verification report and a plurality of preset parsing formats, a plurality of format similarities, wherein the format similarities are similarities between the template format of the verification report and the preset parsing formats, and each preset parsing format corresponds to one format similarity; Based on the multiple format similarities, determining the target parsing format from the multiple preset parsing formats, the target parsing format being the preset parsing format corresponding to the largest format similarity among the multiple format similarities; When the verification report is parsed successfully according to the target parsing format, the verification parameters in the verification report are obtained.
7. The method according to claim 6, characterized in that The method further comprises: When parsing the verification report according to the target parsing format fails, obtaining the file format of the verification report; If the file format is a format that supports parsing, generating a parsing format generation requirement; Based on the format generation requirement, obtaining a first parsing format, wherein the first parsing format matches the format of the verification report; The verification report is parsed according to the first parsing format to obtain verification parameters in the verification report.
8. The method according to claim 7, characterized in that The method further comprises: The first parsed format is stored.
9. The method according to claim 7, characterized in that The method further comprises: In the case that the file format is a format that cannot be parsed, the format of the verification report is converted into a format that supports parsing.
10. A device management apparatus, characterized in that: include: processor and memory; The processor is coupled to the memory; The memory is used to store one or more programs, and one or more of the programs include computer-executable instructions. When the equipment management device is running, the processor executes the computer-executable instructions stored in the memory to enable the equipment management device to perform the method as described in any one of claims 1 to 9.