Equipment information management method, terminal equipment and storage medium

By receiving and verifying the equipment SN, flexible processes and linkages of device management are realized, and the problems of lack of flexibility and error handling in the existing technology are solved, and user experience and management efficiency are improved.

CN119065539APending Publication Date: 2024-12-03XIAMEN MILESIGHT IOT CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411113109.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-06-06
Filing Date
2024-08-14
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The existing equipment management solutions lack flexibility and cannot meet the personalized needs of different users. The lack of error handling mechanism and incomplete equipment linkages lead to user operation difficulties and inefficiency.

Method used

By receiving the device SN, compliance and repeatability verification are carried out, qualified SN is cached, data requests are sent to the server, and device list is filled to realize the flexible process of adding, modifying and deleting devices, and device linkage is realized through mapping tables to provide errors Marking and error notification.

Benefits of technology

It provides flexible equipment management solutions to meet personalized needs, improves user experience and operation accuracy, realizes automatic merger and linkage between devices, and improves management efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119065539A_ABST
    Figure CN119065539A_ABST
Patent Text Reader

Abstract

The invention relates to an equipment information management method, terminal equipment and a storage medium, and the method comprises the steps: receiving an input equipment SN, adding a corresponding number of empty equipment entries in an equipment list according to the number, and updating an equipment list window at the same time; caching all qualified SNs, sending an equipment data acquisition request to a server, filling the cached SNs into newly added empty equipment entries, and updating an equipment list window; after receiving the equipment data returned by the server, filling other equipment data related fields in the newly added empty equipment entry, and updating the equipment list window; and filling the product list with the new SN, and updating a product list window. According to the invention, a flexible equipment management scheme is provided, the user is allowed to perform customization according to own requirements, and personalized requirements of different users are met.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of equipment management, and in particular to an equipment information management method, terminal equipment and storage medium. Background Art

[0002] At present, there are some equipment information management solutions in the field of equipment management, but there are the following problems:

[0003] (1) Lack of flexibility: The existing solutions have fixed and non-customizable processes for operations such as adding, modifying, and deleting devices, and cannot meet the personalized needs of different users.

[0004] (2) Lack of error handling mechanism: The existing solutions do not provide effective error reporting and prompting functions when device input errors or data anomalies occur, which causes inconvenience to users.

[0005] (3) Imperfect device linkage: In the existing solution, the linkage operations between devices are relatively independent, and it is impossible to automatically merge and associate devices. Summary of the invention

[0006] In order to solve the above problems, the present invention proposes a device information management method, a terminal device and a storage medium.

[0007] The specific plan is as follows:

[0008] A device information management method comprises the following steps:

[0009] S1: receiving the input device SN, and adding a corresponding number of empty device entries to the device list according to the number of the input device SNs, and updating the device list window for displaying the device list on the display page;

[0010] S2: Check the compliance and duplication of all input SNs, and take the compliant and non-duplicate SNs as qualified SNs;

[0011] S3: Cache all qualified SNs, send device data acquisition requests corresponding to all qualified SNs to the server, and fill the cached qualified SNs into the fields corresponding to the SNs in the newly added empty device entries in the device list, and update the content of the device list displayed in the device list window;

[0012] S4: after receiving the device data returned by the server, fill other device data related fields in the newly added empty device entry in the device list based on the device data, and update the content of the device list displayed in the device list window;

[0013] S5: for each received device data, determine whether the corresponding product model exists in the product list. If so, add the SN corresponding to the device data to the mapping table corresponding to the product model in the product list; otherwise, add the mapping table corresponding to the product model to the product list; the mapping relationship between the product model and the SN is stored in the mapping table;

[0014] S6: updating a product list window for displaying a product list on a display page.

[0015] Furthermore, the method of receiving the input device SN is: receiving the SN information directly input in the add device window of the display page, when the input SN information includes multiple SNs, the multiple SNs are separated by separators.

[0016] Furthermore, when completing the SN information input in the add device window for input insertion, first query the current device balance that can be added to determine whether the number of SNs to be inserted exceeds the device balance. If it exceeds, only the number of SNs that can be added in the inserted data will be intercepted, and a prompt will be issued that the number exceeds the limit.

[0017] Furthermore, the method for receiving the input device SN is: input the SN information by clicking the Add button in the display page. When the Add button is clicked, a new empty device entry is added to the device list. At this time, after the device list in the device list window is updated, a row corresponding to the empty device entry is added. The input of the device SN is achieved by entering a device SN in the field corresponding to the SN in the row corresponding to the newly added empty device entry.

[0018] Furthermore, the method of receiving the input device SN is: uploading the file recording the device SN to be input to the server by clicking the upload button in the display page; after receiving the file, the server parses it to extract all the SNs therein.

[0019] Furthermore, when the input device SN includes multiple ones, this implementation also includes deduplication of all the input SNs.

[0020] Furthermore, the non-compliant SN is marked as an error mark, and the error information of the SN is recorded, and the duplicate SN is marked as a duplicate mark; the device entries corresponding to the non-compliant and duplicate SNs are placed in front in the device list, and the device entries corresponding to the non-compliant and duplicate SNs are highlighted in the device list window of the display page.

[0021] Furthermore, the highlighting method is to mark the input box of the SN corresponding field in red, and when it is an unqualified SN, a red exclamation mark is added to the input box, and when the mouse moves to the red exclamation mark, an error information display window pops up, and the content of the error information display window displays the error information of the corresponding SN recorded.

[0022] A device information management terminal device comprises a processor, a memory and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method in an embodiment of the present invention when executing the computer program.

[0023] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described above in an embodiment of the present invention are implemented.

[0024] The present invention adopts the above technical solution, provides a flexible device management solution, allows users to customize according to their own needs, and meets the personalized needs of different users. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 Shown is a flow chart of a method according to a first embodiment of the present invention.

[0026] Figure 2 Shown is a schematic diagram of a display page in this embodiment.

[0027] Figure 3 The figure shows a schematic diagram of inputting SN information through the Add Device window in this embodiment.

[0028] Figure 4 Shown is a schematic diagram of a newly added empty device entry in this embodiment.

[0029] Figure 5 Shown is a schematic diagram showing the highlighting of non-compliant and duplicate SNs in this example.

[0030] Figure 6 The diagram shown is a schematic diagram of filling only the field corresponding to SN in this embodiment.

[0031] Figure 7 Shown is a schematic diagram of filling in the device data related fields in this embodiment. DETAILED DESCRIPTION

[0032] To further illustrate various embodiments, the present invention provides drawings. These drawings are part of the disclosure of the present invention, which are mainly used to illustrate the embodiments and can be used in conjunction with the relevant descriptions in the specification to explain the operating principles of the embodiments. With reference to these contents, ordinary technicians in this field should be able to understand other possible implementations and advantages of the present invention.

[0033] The present invention will now be further described with reference to the accompanying drawings and specific implementation methods.

[0034] Embodiment 1:

[0035] The embodiment of the present invention provides a device information management method, such as Figure 1 As shown, the method comprises the following steps:

[0036] S1: receiving the input device SN, and adding a corresponding number of empty device entries to the device list according to the number of the input device SNs, and updating the device list window for displaying the device list on the display page.

[0037] refer to Figure 2 In this embodiment, there are three ways to receive the input device SN:

[0038] The first is to receive the SN information directly input in the Add Device window of the display page. At this time, the SN information input in the window may include only one SN or multiple SNs, and the multiple SNs are separated by separators. When identifying the SN, multiple SNs can be distinguished by identifying the separators. In this embodiment, the separator is a line feed character. In other embodiments, those skilled in the art may also use other separators, which are not limited here.

[0039] Furthermore, since the number of devices that can be added is limited, when multiple SNs are input at one time through the first method, all SNs are input in the Add Device window before data insertion, such as Figure 3 As shown, after the SN input is completed, click the Fill in Device List button to insert data, which may cause the number of inserted data to exceed the quantity limit. In order to avoid exceeding the quantity limit, this embodiment also includes querying the current device surplus that can be added each time data is inserted, and judging whether the number of SNs to be inserted exceeds the device surplus. If it exceeds, only the number of SNs that can be added in the inserted data is intercepted, and a prompt that the number exceeds the limit is issued.

[0040] The second method is to enter SN information by clicking the Add button in the display page. When the Add button is clicked, an empty device entry is added to the device list. At this time, the device list in the device list window is updated and a row corresponding to the empty device entry is added, such as Figure 4 As shown. The user can input a device SN by entering a device SN in the field corresponding to the SN of the row corresponding to the newly added empty device entry. Since only one SN can be entered each time the Add button is clicked, when multiple SNs need to be entered, just click the Add button multiple times.

[0041] The third method is to upload the file recording the device SN to be input to the server by clicking the upload button in the display page. After receiving the file, the server parses it to extract all the SNs therein.

[0042] Furthermore, when the input device SN includes multiple ones, this implementation also includes deduplication of all the input SNs.

[0043] S2: Perform compliance and duplication checks on all input SNs, and take the compliant and non-duplicate SNs as qualified SNs.

[0044] When performing compliance verification, the number of digits in the SN and whether it is a number are usually verified. When performing duplication verification, the input SN is matched with the existing SNs in the device list. If they match, the input SN is determined to be a duplicate SN.

[0045] In this embodiment, the non-compliant (i.e., compliance check failed) SN is marked as error, and the repeated (i.e., repeat check failed) SN is marked as repeat. When the SN compliance check fails, the reasons for the failure may include multiple reasons (such as SN does not exist, format error, etc.), in order to facilitate users to understand the reasons, this embodiment also includes recording the error information of the SN when the SN compliance check fails.

[0046] In order to facilitate users to know which SNs they input are unqualified in time, in this embodiment, the device entries corresponding to the unqualified and duplicated SNs are preferably placed in front of the device list, and the device entries corresponding to the unqualified and duplicated SNs are highlighted in the device list window of the display page. In this embodiment, the highlighting method is to mark the input box of the SN corresponding field in red, and when it is an unqualified SN, a red exclamation mark is added to the input box. When the mouse moves to the red exclamation mark, an error information display window pops up, and the content of the error information display window displays the error information of the corresponding SN recorded, such as Figure 5 shown.

[0047] S3: Cache all qualified SNs, and send device data acquisition requests corresponding to all qualified SNs to the server. At the same time, fill the cached qualified SNs into the field corresponding to the SN in the newly added empty device entry in the device list, and update the content of the device list displayed in the device list window.

[0048] S4: After receiving the device data returned by the server, other device data related fields in the newly added empty device entry in the device list are filled based on the device data, and the content of the device list displayed in the device list window is updated.

[0049] Figure 6The schematic diagram is shown as filling the cached qualified SN into the field corresponding to the SN in the newly added empty device entry in the device list. Figure 7 The diagram shown is a schematic diagram of filling other device data related fields in a newly added empty device entry in the device list based on the device data.

[0050] After receiving the device data returned by the server, this embodiment performs compliance detection again. If the detection is non-compliant, it is marked as an error and error information is recorded at the same time.

[0051] S5: For each device data received, determine whether the corresponding product model exists in the product list. If so, add the SN corresponding to the device data to the mapping table corresponding to the product model in the product list; otherwise, add a mapping table corresponding to the product model to the product list; the mapping table stores the mapping relationship between the product model and the SN.

[0052] In this embodiment, each product model in the product list includes not only its corresponding mapping table, but also template information corresponding to the product model.

[0053] S6: updating a product list window for displaying a product list on a display page.

[0054] When the product list is displayed in the product list window, one product model corresponds to one row, and the corresponding fields include the configuration file of the model and template information.

[0055] Furthermore, each row of device entries in the device list window of the display page of this embodiment has a corresponding delete button. When the delete button is clicked, the data in the corresponding device list is first matched based on the SN in the SN corresponding field in the device entry, and then deleted. At the same time, the corresponding SN mapping relationship in the product list is matched for deletion. After deletion, it is determined whether the corresponding mapping table is empty. If so, the corresponding product information (i.e., the corresponding row in the table, including the mapping table and template information) is deleted.

[0056] The embodiments of the present invention have the following beneficial effects:

[0057] (1) It provides a flexible device management solution that allows users to customize it according to their own needs, including the process of adding, modifying, and deleting devices to meet the personalized needs of different users.

[0058] (2) Through strict device input verification and error information processing, it can effectively identify and mark device input errors or data anomalies, and provide error reporting and prompt functions to improve user experience and operation accuracy.

[0059] (3) By automatically merging devices of the same model, generating product sets and maintaining mapping tables, linkage between devices and convenient operation can be achieved, thereby improving the efficiency of device management.

[0060] Embodiment 2:

[0061] The present invention also provides a device information management terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps in the above method embodiment of embodiment 1 of the present invention when executing the computer program.

[0062] Further, as an executable solution, the device information management terminal device can be a computing device such as a desktop computer, a notebook, a PDA, etc. The device information management terminal device can include, but is not limited to, a processor and a memory. Those skilled in the art can understand that the composition structure of the above-mentioned device information management terminal device is only an example of the device information management terminal device, and does not constitute a limitation on the device information management terminal device. It can include more or less components than the above, or a combination of certain components, or different components. For example, the device information management terminal device can also include input and output devices, network access devices, buses, etc., and the embodiments of the present invention do not limit this.

[0063] Further, as an executable solution, the processor may be a central processing unit (CPU) or other general-purpose processors. The general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the device information management terminal device, and uses various interfaces and lines to connect various parts of the entire device information management terminal device.

[0064] The memory can be used to store the computer program and / or module, and the processor realizes various functions of the device information management terminal device by running or executing the computer program and / or module stored in the memory, and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system and at least one application required for a function; the data storage area can store data created according to the use of the mobile phone, etc. In addition, the memory can include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0065] The present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above method in the embodiment of the present invention are implemented.

[0066] If the module / unit integrated in the device information management terminal device is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory) and software distribution medium, etc.

[0067] Although the present invention has been specifically shown and described in conjunction with the preferred embodiments, it should be understood by those skilled in the art that various changes may be made to the present invention in form and details without departing from the spirit and scope of the present invention as defined by the appended claims, all of which are within the scope of protection of the present invention.

Claims

1. A device information management method, characterized in that: The following steps are involved: S1: receiving the input device SN, and adding a corresponding number of empty device entries to the device list according to the number of the input device SNs, and updating the device list window for displaying the device list on the display page; S2: Check the compliance and duplication of all input SNs, and take the compliant and non-duplicate SNs as qualified SNs; S3: Cache all qualified SNs, send device data acquisition requests corresponding to all qualified SNs to the server, and fill the cached qualified SNs into the fields corresponding to the SNs in the newly added empty device entries in the device list, and update the content of the device list displayed in the device list window; S4: after receiving the device data returned by the server, fill other device data related fields in the newly added empty device entry in the device list based on the device data, and update the content of the device list displayed in the device list window; S5: for each received device data, determine whether the corresponding product model exists in the product list. If so, add the SN corresponding to the device data to the mapping table corresponding to the product model in the product list; otherwise, add the mapping table corresponding to the product model to the product list; the mapping relationship between the product model and the SN is stored in the mapping table; S6: updating a product list window for displaying a product list on a display page.

2. The device information management method according to claim 1, characterized in that: The method of receiving the input device SN is: receiving the SN information directly input in the add device window of the display page, when the input SN information includes multiple SNs, the multiple SNs are separated by separators.

3. The device information management method according to claim 2, characterized in that: When completing the SN information input in the Add Device window for input insertion, first query the current device balance that can be added to determine whether the number of SNs to be inserted exceeds the device balance. If it exceeds, only the SNs that can be added in the inserted data will be intercepted, and a prompt will be issued that the number exceeds the limit.

4. The device information management method according to claim 1, characterized in that: The method for receiving the input device SN is: input the SN information by clicking the Add button in the display page. When the Add button is clicked, a new empty device entry is added to the device list. At this time, after the device list in the device list window is updated, a row corresponding to the empty device entry is added. The input of the device SN is achieved by entering a device SN in the field corresponding to the SN in the row corresponding to the newly added empty device entry.

5. The device information management method according to claim 1, characterized in that: The method of receiving the input device SN is: uploading the file recording the device SN to be input to the server by clicking the upload button in the display page; after receiving the file, the server parses it to extract all the SNs therein.

6. The device information management method according to claim 1, characterized in that: When the input device SN includes multiple ones, this implementation also includes deduplication of all the input SNs.

7. The device information management method according to claim 1, characterized in that: Also includes: Mark the non-compliant SN as an error mark and record the error information of the SN; mark the duplicate SN as a duplicate mark; The device entries corresponding to the non-compliant and duplicated SNs are placed in front in the device list, and the device entries corresponding to the non-compliant and duplicated SNs are highlighted in the device list window of the displayed page.

8. The device information management method according to claim 7, characterized in that: The highlighting method is to mark the input box of the SN corresponding field in red, and when it is an unqualified SN, a red exclamation mark is added to the input box. When the mouse moves to the red exclamation mark, an error information display window pops up, and the content of the error information display window displays the error information of the corresponding SN recorded.

9. A device information management terminal device, characterized in that: The method comprises a processor, a memory and a computer program stored in the memory and running on the processor, wherein the processor implements the steps of the method according to any one of claims 1 to 8 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.