Equipment management method, computing equipment and computer readable storage medium
By obtaining device feature information and service provider attributes, determining matching rules to determine target service providers, the problem of inefficiency of traditional equipment management methods in complex environments is solved, and efficient adaptability and user experience improvement of equipment management are achieved.
Patent Information
- Application Number
- CN202411340515.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-25
- Publication Date
- 2024-12-31
AI Technical Summary
Traditional equipment management methods are difficult to adapt to different scenarios in complex environments, resulting in low management efficiency.
By obtaining the feature information of the target device, confirming the matching rules (exact match, feature match, broad match), determining the target service provider based on the feature information and the attribute information of the service provider, and generating work order information, updating the location information in real time to improve the device Management efficiency.
It realizes scenario adaptability and flexibility of device management, and improves the efficiency and user experience of device management.
Smart Images
Figure CN119232577A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a device management method, a computing device and a computer-readable storage medium. Background Art
[0002] With the rapid development of technology, the number of devices is increasing and the types are becoming more diverse.
[0003] Traditional manual management methods can no longer meet the needs of equipment management in complex environments. Specifically, existing equipment management methods cannot adapt to different scenarios when assigning service parties such as service engineers, resulting in low equipment management efficiency.
[0004] Therefore, there is an urgent need for a device management method that can improve the management efficiency of the device. Summary of the invention
[0005] The purpose of this application is to provide a device management method, a computing device and a readable storage medium, which can realize intuitive or convenient classification of programs, improve program management efficiency, and enhance user experience.
[0006] To achieve the above objectives:
[0007] In a first aspect, an embodiment of the present application provides a device management method, including:
[0008] Get the characteristic information of the target device;
[0009] Based on the feature information, determining a corresponding matching rule, wherein the matching rule includes at least one of a complete match, a feature match, and a broad match;
[0010] Based on the matching rule, according to the characteristic information and the attribute information of the service provider, a target service provider corresponding to the target device is confirmed.
[0011] In one embodiment, the characteristic information includes a device status; the step of confirming a corresponding matching rule based on the characteristic information includes at least one of the following: if the device status in the characteristic information is a preset status, confirming that the matching rule is the complete match; if the device status in the characteristic information is not the preset status, confirming that the matching rule is the characteristic match.
[0012] In one embodiment, based on the matching rule, according to the feature information and the attribute information of the service provider, the step of confirming the target service provider corresponding to the target device includes: based on the feature matching, matching according to the feature information and the attribute information of the service provider; if based on the feature matching, according to the feature information and the attribute information of the service provider, the target service provider is not matched, then updating the current matching rule to a broad match; based on the broad match, confirming the target service provider according to the feature information and the attribute information of the service provider.
[0013] In one embodiment, the matching rule includes feature matching; based on the matching rule, according to the feature information and the attribute information of the service provider, the step of confirming the target service provider corresponding to the target device includes: confirming the target feature in the feature information according to the preset feature in the feature information; based on the feature matching, confirming the target service provider according to the target feature and the attribute information of the service provider.
[0014] In one embodiment, the matching rule includes the feature matching; based on the matching rule, according to the feature information and the attribute information of the service provider, the step of confirming the target service provider corresponding to the target device includes: obtaining the user information corresponding to the target device; based on the feature matching, confirming the target service provider according to the feature information, the user information and the attribute information of the service provider.
[0015] In one embodiment, based on the feature matching, the step of confirming the target service provider according to the feature information, the user information and the attribute information of the service provider includes: confirming multiple service providers according to the user information and the attribute information of the service provider; based on the feature matching, confirming the target service provider from the multiple service providers according to the feature information.
[0016] In one embodiment, the method further includes: generating work order information of the target device according to at least one of feature information, contract information, and repair information of the target device.
[0017] In one embodiment, the method further includes: acquiring real-time location information of the target device; and sending the real-time location to a terminal corresponding to the target service provider.
[0018] In a second aspect, an embodiment of the present application provides a computing device, comprising: a processor and a memory storing a computer program, and when the processor runs the computer program, the above-mentioned device management method is implemented.
[0019] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the above-mentioned device management method is implemented.
[0020] The device management method, computing device and computer-readable storage medium provided by the embodiments of the present application include obtaining characteristic information of the target device; based on the characteristic information, confirming the corresponding matching rule, wherein the matching rule includes at least one of full match, characteristic match and broad match; based on the matching rule, confirming the target service provider corresponding to the target device according to the characteristic information and the attribute information of the service provider. The present application also provides a computing device and storage medium capable of implementing the above method. The present application can confirm the corresponding matching rule based on the characteristic information, and thus confirm the target service provider according to the characteristic information based on the confirmed matching rule. Therefore, the present application can adapt to different scenarios, thereby improving the efficiency of device management. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Figure 1 A schematic diagram of a flow chart of a device management method provided in a first embodiment of the present invention;
[0022] Figure 2 A flowchart of a device management method provided in the second embodiment of the present application;
[0023] Figure 3 A schematic diagram of a flow chart of a device management method provided in the third embodiment of the present application;
[0024] Figure 4 A schematic diagram of the structure of a computing device provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0025] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0026] It should be noted that, in this article, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.
[0027] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this article, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of..." or "when..." or "in response to determination". Furthermore, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising", "including" indicate that there are described features, steps, operations, elements, components, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and / or groups. The terms "or" and "and / or" used herein are interpreted as inclusive, or mean any one or any combination. Thus, “A, B, or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A, B, and C.” An exception to this definition will occur only when a combination of elements, functions, steps, or operations are inherently mutually exclusive in some manner.
[0028] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are displayed in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
[0029] It should be noted that, in this article, step codes such as S10, S11, etc. are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the sequence. When implementing the step, those skilled in the art may execute S11 first and then S10, etc., but these should all be within the scope of protection of this application.
[0030] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0031] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.
[0032] See also Figure 1 , is a device management method provided in an embodiment of the present application, and the device management method can be executed by a program management device provided in an embodiment of the present application, and the program management device can be implemented in software and / or hardware, such as a computing device such as a computer or a server. In one embodiment, the computing device includes a rule engine to implement the device management method, wherein the rule engine is developed from an inference engine and is a component embedded in an application program, which realizes the separation of business decisions from application program code and uses predefined semantic modules to write business decisions.
[0033] In this embodiment, the execution subject of the device management method is a computer as an example for description. The device management method provided in this embodiment includes:
[0034] Step S10: Acquire characteristic information of the target device.
[0035] The target device is any device that needs to be managed, such as engineering machinery that needs to be delivered, installed or maintained. The characteristic information may include but is not limited to at least one of the following: device status, device type, device model, second-hand identification of the device, and the region to which the device belongs.
[0036] In one embodiment, step S10: obtaining characteristic information of the target device may include: obtaining characteristic information of the target device from a relational database. A relational database refers to a database that uses a relational model to organize data, and stores data in the form of rows and columns to facilitate user understanding. A series of rows and columns of a relational database is called a table, and a group of tables constitutes a database.
[0037] Step S11: Based on the feature information, confirm the corresponding matching rule, wherein the matching rule includes at least one of complete matching, feature matching, and broad matching.
[0038] Among them, exact match, feature match, and broad match are three different matching rules.
[0039] In one embodiment, at least two of the full match, feature match, and broad match have different types or quantities or selection rules of target features selected from the feature information. For example, the full match is a matching rule that matches based only on one target feature in the feature information, such as the device status. Broad match is a matching rule that matches based only on another target feature in the feature information, such as the region to which the device belongs. Feature match is a matching rule that confirms one or more target features for matching based on preset features in the feature information, such as the device status. Specifically, when the preset features of feature match are different, the target features selected from the feature information for matching are also different. For example, when the device status is prototype shipment, the confirmed target features do not include the second-hand identification of the device. When the device status is device maintenance, the confirmed target features include the second-hand identification of the device.
[0040] In one embodiment, the matching logic and / or matching results of at least two of the full match, feature match, and broad match are different. Specifically, in one embodiment, based on the same feature information of the target device, when matching is performed through feature matching and full match respectively, the matched service providers are different. Specifically, in one embodiment, full match is a matching rule that can match a preset number of service providers according to feature information. For example, if the device status in the feature information is a return status, the matching rule is confirmed to be a full match to match the only return service engineer pre-stored in the database. Feature match is a matching rule that may or may not match a service provider according to feature information. Broad match is a matching rule that can match multiple service providers according to feature information. Among them, in one embodiment, full match and feature match can also be collectively referred to as exact match, that is, the number of service providers that can be matched is relatively small compared to broad match.
[0041] In one embodiment, the corresponding matching rule can be confirmed based on the device status, second-hand mark, etc. in the feature information. For example, if the device status in the feature information is a preset status, the matching rule is confirmed to be a complete match. If the device status is not a preset status, the matching rule is confirmed to be a feature match. The preset status is a status set by the user or the system, such as a return status.
[0042] Step S12: Based on the matching rules, according to the characteristic information and the attribute information of the service provider, the target service provider corresponding to the target device is confirmed.
[0043] The attributes of the service provider are information about the characteristics of the service provider, and may include, for example, at least one of the following: responsible area, position, service organization, product line, etc. Specifically, for example, the service provider may be, but not limited to, a service engineer, a service customer service staff, a service robot, a service terminal, etc. Specifically, in one embodiment, the attribute information of the service provider may be pre-stored in a non-relational database, but the present application is not limited thereto.
[0044] In one embodiment, the matching rule includes feature matching. Step S12, based on the matching rule, according to the feature information and the attribute information of the service provider, the step of confirming the target service provider corresponding to the target device may include: confirming the target feature in the feature information according to the preset feature in the feature information; based on feature matching, confirming the target service provider according to the target feature and the attribute information of the service provider. Among them, the preset feature can be, for example, the device status or other preset feature information. Among them, the target feature may include the preset feature or may not include the preset feature. The number of target features may be one or more (i.e., the features in the feature information are combined). Specifically, for example, when the device status is prototype shipment, the confirmed target feature does not include the second-hand identification of the device, and when the device status is device maintenance, the confirmed target feature includes the second-hand identification of the device. In this way, based on feature matching, according to the determined target feature and the attribute information of the service provider, the target service provider is confirmed, which can avoid unnecessary data processing, thereby further improving the efficiency of management.
[0045] In one embodiment, the matching rule includes feature matching. Step S12: Based on the matching rule, according to the feature information and the attribute information of the service provider, the target service provider corresponding to the target device is confirmed, including: obtaining user information corresponding to the target device; based on the feature matching, according to the feature information, the user information and the attribute information of the service provider, the target service provider is confirmed. The user information may include the user's attribute information such as the user's ID, the user's gender, the user's occupation, etc., and may also include the user's historical service information, the user's level, etc., and other user-related information.
[0046] Specifically, in one embodiment, based on feature matching, according to feature information, user information and attribute information of the service provider, the step of confirming the target service provider includes: confirming multiple service providers according to user information and attribute information of the service provider; based on feature matching, confirming the target service provider from multiple service providers according to feature information. Specifically, based on user information and attribute information of the service provider, the multiple service providers confirmed are service providers with the same features, such as multiple service engineers of the same service organization. For example, if the user information of the target device includes historical service information of service organization A, service providers a1, a2, and a3 in service organization A can be confirmed first, and service provider a1 can be selected as the target service provider from service providers a1, a2, and a3 based on the feature information.
[0047] The device management method of this embodiment includes obtaining feature information of the target device; based on the feature information, confirming the corresponding matching rule, wherein the matching rule includes at least one of a full match, a feature match, and a broad match; based on the matching rule, according to the feature information and the attribute information of the service provider, confirming the target service provider corresponding to the target device. Therefore, this example can confirm the corresponding matching rule based on the feature information, and then confirm the target service provider based on the feature information based on the confirmed matching rule, and can adapt to different scenarios, thereby improving the efficiency of device management.
[0048] Figure 2 This is a flow chart of a device management method provided in the second embodiment of the present application. Figure 2 As shown, the device management method of this embodiment includes:
[0049] Step S20, obtaining characteristic information of the target device;
[0050] Step S21, determining whether the device state in the characteristic information is a preset state;
[0051] If the device state is the preset state, proceed to step S22 to confirm that the matching rule is a complete match;
[0052] If the device state is not the preset state, proceed to step S23 to confirm that the matching rule is feature matching;
[0053] Step S24: Based on the confirmed matching rule, according to the characteristic information and the attribute information of the service provider, the target service provider corresponding to the target device is confirmed.
[0054] In one embodiment, step S24 may further include:
[0055] Step S25: If the target service provider is not matched, the target service provider is confirmed based on broad matching according to the feature information and the attribute information of the service provider.
[0056] Specifically, for example, the characteristic information of the target device includes the device status, second-hand mark, and region. It is determined whether the device status is a return status. If the device status is a return status, the matching rule is confirmed to be a complete match, so as to determine the target service provider as the return engineer A with the attribute of return according to the complete match. If the device status is not a return status but a prototype shipment, the matching rule is confirmed to be a feature match, and the device status and region in the feature information are confirmed to be the target features, and the target service provider is confirmed. If the target service provider is not matched according to the feature match, the matching rule is updated to a broad match to confirm the target service provider based on the region to which the target device belongs and the attribute information of the service provider. For example, if the region to which the target device belongs is XX, the service provider whose region is also XX in the attribute information of the service provider is confirmed as the target service provider. Among them, if there are multiple target service providers, multiple target service providers can be screened according to a random selection method or a user's selection instruction to obtain the final target service provider.
[0057] The device management method of this embodiment confirms the corresponding matching rules according to the device status, and when the target service provider is not matched based on complete matching or feature matching, it can obtain the target service provider based on broad matching, which can further improve the scenario adaptability and flexibility of device management, thereby further improving the efficiency of device management.
[0058] Figure 3 This is a flow chart of a device management method provided in the third embodiment of the present application. Figure 3 As shown, the device management method of this embodiment includes the following steps:
[0059] Step S30: Generate work order information of the target device according to at least one of the characteristic information, contract information, and repair information of the target device;
[0060] The work order information may be repair work order information, delivery work order information, maintenance work order information, etc. Specifically, in one embodiment, the work order information may be generated by a rule engine based on the feature information and the quality assurance information in the contract information.
[0061] In one implementation, the work order information may include information of a target service provider, such as a target service engineer.
[0062] Step S31, output work order information.
[0063] In one embodiment, the output method of the work order information can be determined according to the type of the work order information. For example, when the work order information is a maintenance work order, the work order information can be output regularly according to the maintenance time. When the work order information is a repair work order, the work order information is output in real time.
[0064] In one embodiment, the device management method may further include:
[0065] Step S32, obtaining real-time location information of the target device;
[0066] Step S33: Send the real-time location to the terminal corresponding to the target service provider.
[0067] In one implementation, the work order information and the real-time location information may be sent simultaneously to a terminal corresponding to the target service provider, so that the work order information and the real-time location signal are displayed on the terminal simultaneously.
[0068] Specifically, in one embodiment, when the terminal corresponding to the target service provider receives the real-time location information of the target device, the terminal of the target service provider can automatically start the navigation mode according to the service time in the work order information to improve service efficiency.
[0069] In this embodiment, the work order information of the target device is generated according to at least one of the characteristic information, contract information, and repair information of the target device, which can improve the accuracy of the work order information generation. Moreover, in one embodiment, the output method of the work order information can be determined according to the type of the work order information, such as regular output or real-time output, to improve the efficiency and timeliness of work order generation. In addition, in one embodiment, the real-time location information of the target device can be obtained, so that the terminal corresponding to the target service party can navigate according to the real-time location information, thereby further improving the efficiency of the service.
[0070] Based on the same inventive concept as the above embodiments, an embodiment of the present invention provides a computing device, such as Figure 4 As shown, the computing device includes: a processor 410 and a memory 411 storing a computer program; wherein, Figure 4 The processor 410 shown in the figure is not used to indicate that the number of the processor 410 is one, but is only used to indicate the positional relationship of the processor 410 relative to other devices. In actual applications, the number of the processor 410 may be one or more; similarly, Figure 4 The memory 411 shown in the figure has the same meaning, that is, it is only used to refer to the position relationship of the memory 411 relative to other devices. In practical applications, the number of memories 411 can be one or more. When the processor 410 runs the computer program, the device management method described above is implemented.
[0071] The computing device may also include: at least one network interface 412. The various components in the computing device are coupled together via a bus system 413. It is understood that the bus system 413 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 413 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, the bus system 413 is not used in the example above. Figure 4 Various buses are labeled as bus system 413.
[0072] The memory 411 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a ferromagnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM); the magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAM bus random access memory (DRRAM, Direct Rambus Random Access Memory).The memory 411 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memories.
[0073] The memory 411 in the embodiment of the present invention is used to store various types of data to support the operation of the computing device. Examples of these data include: any computer program used to operate on the computing device, such as an operating system and an application; contact data; phone book data; messages; pictures; videos, etc. Among them, the operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application program may include various applications, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. Here, the program that implements the method of the embodiment of the present invention may be included in the application program.
[0074] Based on the same inventive concept as the above-mentioned embodiment, this embodiment further provides a computer storage medium, in which a computer program is stored. The computer storage medium may be a ferromagnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM) or other memory; it may also be various devices including one or any combination of the above-mentioned memories, such as a mobile phone, a computer, a tablet device, a personal digital assistant, etc. When the computer program stored in the computer storage medium is executed by the processor, the above-mentioned device management method is implemented. For the specific steps implemented when the computer program is executed by the processor, please refer to Figure 1 The description of the illustrated embodiment will not be repeated here.
[0075] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0076] In this document, the terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion of elements other than those listed and may also include additional elements not expressly listed.
[0077] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.
Claims
1. A device management method, characterized in that: include: Get the characteristic information of the target device; Based on the feature information, determining a corresponding matching rule, wherein the matching rule includes at least one of a complete match, a feature match, and a broad match; Based on the matching rule, according to the characteristic information and the attribute information of the service provider, a target service provider corresponding to the target device is confirmed.
2. The method according to claim 1, characterized in that The characteristic information includes device status; The step of confirming the corresponding matching rule based on the feature information includes at least one of the following: If the device state in the characteristic information is a preset state, confirming that the matching rule is the complete match; If the device state in the feature information is not the preset state, the matching rule is confirmed to be the feature match.
3. The method according to claim 1 or 2, characterized in that: The step of confirming a target service provider corresponding to the target device based on the matching rule and the characteristic information and the attribute information of the service provider includes: Based on the feature matching, matching is performed according to the feature information and the attribute information of the service provider; If the target service provider is not matched based on the feature matching according to the feature information and the attribute information of the service provider, the current matching rule is updated to a broad match; Based on the broad match, the target service provider is confirmed according to the feature information and the attribute information of the service provider.
4. The method according to claim 1, characterized in that: The matching rules include feature matching; The step of confirming a target service provider corresponding to the target device based on the matching rule and the characteristic information and the attribute information of the service provider includes: According to the preset features in the feature information, confirm the target features in the feature information; Based on the feature matching, the target service provider is confirmed according to the target features and the attribute information of the service provider.
5. The method according to claim 1, characterized in that The matching rule includes the feature matching; The step of confirming a target service provider corresponding to the target device based on the matching rule and the characteristic information and the attribute information of the service provider includes: Obtaining user information corresponding to the target device; Based on the feature matching, the target service provider is confirmed according to the feature information, the user information and the attribute information of the service provider.
6. The method according to claim 5, characterized in that Based on the feature matching, the step of confirming the target service provider according to the feature information, the user information and the attribute information of the service provider includes: Confirming multiple service providers according to the user information and the attribute information of the service provider; Based on the feature matching, the target service provider is confirmed from among the multiple service providers according to the feature information.
7. The method according to claim 1, characterized in that The method further comprises: Work order information of the target device is generated according to at least one of the characteristic information, contract information, and repair information of the target device.
8. The method according to claim 1, characterized in that: The method further comprises: Obtaining real-time location information of the target device; The real-time location is sent to a terminal corresponding to the target service provider.
9. A computing device, characterized in that include: A processor and a memory storing a computer program, wherein when the processor runs the computer program, the device management method according to any one of claims 1 to 8 is implemented.
10. A computer-readable storage medium, characterized in that: A computer program is stored, and when the computer program is executed by a processor, the device management method according to any one of claims 1 to 8 is implemented.