A data management method and device, electronic equipment, medium and product

Abstract

The application provides a data management method and device, electronic equipment, medium and product. According to an example of the application, the method can include: displaying an object model on a display interface, the object model being constructed by device data of a terminal device; in response to detecting a query operation on the object model, determining a visual control corresponding to the device data based on a preconfigured mapping relationship; and displaying the device data through the visual control, without manually searching and analyzing the device data through code or script, thereby realizing visual management of the device data and reducing the complexity of managing the device data of the terminal device.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and more particularly to a data management method, apparatus, electronic device, medium, and product. Background Technology

[0002] With the rapid advancement of information technology, the Internet of Things (IoT) has become a bridge connecting the physical and digital worlds, greatly promoting the popularization and application of terminal devices. Within the IoT ecosystem, the dramatic increase in the types and numbers of terminal devices will significantly enhance the level of automation and intelligence in IoT ecosystem scenarios.

[0003] However, the number of terminal devices is growing explosively, and each device generates a large amount of data, which greatly increases the complexity of device management. Summary of the Invention

[0004] To overcome the problems existing in related technologies, this application provides a data management method, apparatus, electronic device, medium, and product.

[0005] According to a first aspect of any embodiment of this application, a data management method is provided, the method comprising:

[0006] The object model is displayed on the display interface. The object model is constructed by the device data of the terminal device.

[0007] In response to the detection of a query operation for the object model, the visualization control corresponding to the device data is determined based on a pre-configured mapping relationship;

[0008] The device data is displayed through the visual control.

[0009] According to a second aspect of any embodiment of this application, a data management method for digital paintings is provided, wherein object model management is performed on a display device distinct from a terminal device, the terminal device being used to display the digital paintings; the method includes:

[0010] A model of an object is displayed on the display interface of the display device. The model of the object is constructed based on device data of the terminal device. The device data includes at least one of the following: device attributes, event attributes, and service attributes related to the digital painting.

[0011] In response to the detection of a query operation for the object model, the device data is displayed through a visualization control corresponding to the device data based on a pre-configured mapping relationship.

[0012] According to a third aspect of any embodiment of this application, a data management apparatus is provided, the apparatus comprising:

[0013] The object model display module is used to display the object model on the display interface. The object model is constructed by using the device data of the terminal device.

[0014] The control determination module is used to determine the visual control corresponding to the device data based on a pre-configured mapping relationship in response to the detection of a query operation for the object model.

[0015] The data display module is used to display the device data through the visualization control.

[0016] According to a fourth aspect of any embodiment of this application, a data management device for digital paintings is provided, which manages object models on a display device distinct from a terminal device, wherein the terminal device is used to display digital paintings; the device includes:

[0017] The first display module is used to display an object model on the display interface of the display device. The object model is constructed based on device data of the terminal device. The device data includes at least one of the following: device attributes, event attributes, and service attributes related to the digital painting.

[0018] The second display module is used to respond to the detection of a query operation for the object model and display the device data through a visualization control corresponding to the device data based on a pre-configured mapping relationship.

[0019] According to a fifth aspect of any embodiment of this application, an electronic device is provided, comprising:

[0020] processor;

[0021] Memory used to store processor-executable instructions;

[0022] The processor executes the executable instructions to implement the method described in any embodiment of this application.

[0023] According to a sixth aspect of any embodiment of the present application, a computer-readable storage medium is provided having computer instructions stored thereon that, when executed by a processor, implement the method described in any of the embodiments of the present application described above.

[0024] According to a seventh aspect of any embodiment of this application, a computer program product is provided, having a computer program / instructions stored thereon, which, when executed by a processor, implement the method described in any of the embodiments of this application described above.

[0025] The technical solution provided in this application may include the following beneficial effects:

[0026] As can be seen from the above embodiments, by displaying the object model on the display interface, the object model can abstractly reflect the terminal. In response to the detection of a query operation on the object model, based on the pre-configured mapping relationship, the corresponding visual control for the device data is determined. Through the visual control, the device data can be displayed intuitively, without the need to manually search and parse the device data through code or scripts, thereby realizing the visual management of device data and reducing the complexity of managing the device data of terminal devices.

[0027] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0028] The accompanying drawings, which are incorporated in and form part of this application, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0029] Figure 1 This is a flowchart illustrating a data management method according to an exemplary embodiment of this application;

[0030] Figure 2 This is a schematic diagram illustrating a display interface according to an exemplary embodiment of this application;

[0031] Figure 3 This is a schematic diagram illustrating a visual centralized control page according to an exemplary embodiment of this application;

[0032] Figure 4 This is a flowchart illustrating a data management method for digital paintings according to an exemplary embodiment of this application;

[0033] Figure 5 This is a schematic diagram illustrating a device data management interface according to an exemplary embodiment of this application;

[0034] Figure 6 This is a schematic diagram illustrating a newly created device attribute according to an exemplary embodiment of this application;

[0035] Figure 7 This is a schematic diagram illustrating a newly created event according to an exemplary embodiment of this application;

[0036] Figure 8 This is a schematic diagram illustrating a newly created event attribute according to an exemplary embodiment of this application;

[0037] Figure 9 This is a schematic diagram illustrating a newly created service according to an exemplary embodiment of this application;

[0038] Figure 10This is a schematic diagram illustrating input attributes for creating a new service according to an exemplary embodiment of this application;

[0039] Figure 11 This is a schematic diagram illustrating the output attributes of a newly created service according to an exemplary embodiment of this application;

[0040] Figure 12 This is a schematic diagram illustrating a visual control configuration interface according to an exemplary embodiment of this application;

[0041] Figure 13 This is an interactive diagram illustrating a method for adjusting device data according to an exemplary embodiment of this application;

[0042] Figure 14 This is a schematic diagram illustrating the structure of a first Internet of Things system according to an exemplary embodiment of this application;

[0043] Figure 15 This is an interactive diagram illustrating another method for adjusting device data according to an exemplary embodiment of this application;

[0044] Figure 16 This is a schematic diagram illustrating the structure of a second Internet of Things system according to an exemplary embodiment of this application;

[0045] Figure 17 This is a flowchart illustrating another method for adjusting device data according to an exemplary embodiment of this application;

[0046] Figure 18 This is a schematic diagram of the structure of an electronic device according to an exemplary embodiment of this application;

[0047] Figure 19 This is a block diagram illustrating a data management device according to an exemplary embodiment of this application;

[0048] Figure 20 This is a block diagram of a data management device for digital paintings according to an exemplary embodiment of this application. Detailed Implementation

[0049] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0050] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0051] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0052] Currently, the number of terminal devices is growing explosively, leading to a significant increase in the complexity of managing device data.

[0053] To address the aforementioned problems, this application proposes a data management method. The following embodiments are provided to further illustrate this application:

[0054] Please see Figure 1 , Figure 1 This is a flowchart illustrating a data management method according to an exemplary embodiment of this application. This data management method can be applied to an Internet of Things (IoT) platform, which is a platform for monitoring, configuring, and managing terminal devices and possesses powerful data processing and storage capabilities. The method may include the following steps:

[0055] Step 102: Display the object model on the display interface. The object model is constructed from the device data of the terminal device.

[0056] In this step, the IoT platform displays the created object models on its interface using formats such as a device list and device tree. The display interface is the visual interface through which users interact with the IoT platform, showcasing the object models corresponding to the terminal devices, receiving user input, and providing feedback on operation results.

[0057] The terminal device can be a smart home device such as a smart light bulb, smart socket, or smart camera; it can also be an industrial IoT device such as a sensor or controller; or it can be a wearable device such as a smartwatch or smart bracelet. This application does not limit the specific devices in this regard.

[0058] An object model is a data model of a terminal device. It is an abstract representation of the terminal device, used to describe its attributes, functions, events, services, and other characteristics and capabilities. The object model is the foundation for terminal device management and data interaction. Device data refers to various information generated by the terminal device during operation, such as sensor readings, device status, and event logs.

[0059] Please see Figure 2 , Figure 2 A schematic diagram of a display interface is shown. For example, the display interface can show created object models 1, 2, 3, 4, 5, and 6. The interface can also display the serial number, device number, device name, and online status of each object model. The display interface can also provide functions such as querying, grouping, sorting, registering, deleting, and downloading keys for the object models.

[0060] Among them, the device number is a unique identifier for each terminal device. The online status can include online and offline. When displaying the online status, the display interface can also show the time since the terminal device last went online.

[0061] The display interface can also show device information for each object model, including device type, network type, last online data, enabled status, activated status, device tags, and device grouping. The interface can also display summary information such as the total number of terminal devices, the total number of online devices, the total number of offline devices, and the total number of inactive devices.

[0062] Step 104: In response to the detection of a query operation for the object model, determine the visualization control corresponding to the device data based on the pre-configured mapping relationship.

[0063] In this step, the IoT platform can monitor user operations and detect whether the user triggers a query request for the object model through interactions such as clicking, selecting, or inputting. Upon detecting a query operation for the object model, the IoT platform determines the corresponding visual control for the device data based on pre-configured mapping relationships.

[0064] The query operation refers to the user's action of viewing the device data corresponding to the object model. Visual controls are the visual elements corresponding to the device data, used to display the device data, receive user input, or perform specific operations; examples include text boxes, buttons, and charts.

[0065] There is a pre-configured mapping relationship between device data and visual controls. This mapping relationship is the correspondence between device data and visual controls, and is used to flexibly define the display format of device data.

[0066] Users can pre-configure the most suitable visualization controls for device data according to actual needs, customize the display of device data, and more easily adapt to different device types and visualization requirements. Furthermore, even if the terminal device or device data is updated, the mapping relationship between the device data and the visualization controls can be easily adjusted to avoid affecting other terminal devices, which helps to improve the stability of data management.

[0067] Step 106: Display device data using visual controls.

[0068] In this step, the IoT platform displays device data through defined visual controls by redirecting pages and popping up prompts, enabling users to intuitively understand the status and information of the terminal device.

[0069] In one embodiment, device data may include at least one of the following: device attributes, event attributes, and service attributes. Specifically, device attributes reflect the current state of the terminal device, event attributes reflect the specific conditions that triggered the event, and service attributes reflect at least one of the following: the method of invoking a service performed by the terminal device and the result of that invoking.

[0070] Please continue reading. Figure 2 Taking the query operation as clicking the visual control button 20 as an example, the IoT platform detects that the user clicked the visual control button 20 and jumps to the visual control page.

[0071] Please see Figure 3 , Figure 3 A schematic diagram of a visual control page is shown. Taking device attributes such as volume, playback mode, carousel duration, and playback order as an example, the IoT platform displays the volume, playback mode, carousel duration, and playback order through slider controls on the visual control page.

[0072] Taking the power warning threshold as an example, the IoT platform displays the power warning threshold through a slider control on the visual control page. When the power of the terminal device is lower than the power warning threshold, a low power warning event is triggered.

[0073] Taking the service attributes as packet address and result code as an example, the IoT platform displays the packet address of the Over-The-Air (OTA) upgrade service through a text box control on the visual control page, and displays the result code of the OTA upgrade service through a radio button.

[0074] In the visual centralized control page, users can also configure whether to automatically refresh and display the latest device data for device attributes, event attributes, and service attributes. After the user sets automatic refresh, the IoT platform can periodically obtain device data from terminal devices, or the terminal devices can periodically report device data. Users can also customize the automatic refresh interval to adapt to different business needs.

[0075] The visual centralized control page can also display the desktop and command terminal of the terminal devices, enabling remote control of the terminal devices, which can greatly improve the efficiency and convenience of managing and maintaining terminal devices.

[0076] As mentioned above, visually displaying device attributes can intuitively reflect the current status of the terminal, making it easy to quickly view and manage the terminal's operation. Visually displaying event attributes helps users to view and manage the specific conditions that trigger events on the terminal in a timely manner, making it easier for users to better manage the terminal's behavior and avoid unnecessary triggering or missing important events. Visually displaying service attributes allows users to easily view and manage at least one of the service's invocation method and invocation result, enabling rapid optimization and improvement of the service.

[0077] The data management method in this embodiment displays an object model on a display interface. The object model abstractly reflects the terminal. In response to the detection of a query operation on the object model, a visual control corresponding to the device data is determined based on a pre-configured mapping relationship. Through the visual control, the device data can be displayed intuitively without the need to manually search and parse the device data through code or scripts. This allows for a more intuitive display of device attributes, realizing visual management of device data and reducing the complexity of managing device data for terminal devices. At the same time, by displaying the complex structure and dynamic data of the object model on the visual interface, complex device data becomes intuitive and easy to understand. Users do not need to directly define and modify device data in JavaScript Object Notation (JSON) format, reducing the learning cost of users for the underlying data structure and thus improving the user-friendliness when viewing and managing terminal devices.

[0078] In one embodiment, for terminal devices displaying digital artworks such as 3D picture frames, Western oil paintings, Eastern ink paintings, and Eastern calligraphy, the display technology of these devices focuses on presenting artistic effects and requires special pixel structures and display partition management, rather than the direct display of data information. Therefore, directly managing the data of the object model on the terminal device may interfere with or damage its artistic effect.

[0079] For example, a 3D photo frame device (hereinafter referred to as a photo frame device) may employ complex pixel arrangement and display partitioning technology to ensure that the 3D effect of the 3D photo frame can be obtained from multiple viewing angles; a Western oil painting simulation screen requires special display technology to simulate the color layers and texture details of traditional oil paintings; an Eastern ink painting dynamic display screen requires special display technology to simulate the flow and diffusion effects of ink; and an Eastern calligraphy scrolling screen requires special display technology to precisely control the scrolling speed and layout of the text.

[0080] To ensure the image quality of digital paintings, the terminal device does not have a touch layer, meaning users cannot directly operate or view data by touching the screen, thus limiting the feasibility of direct data management on the terminal device.

[0081] Furthermore, from an economic perspective, the screens of terminal devices that display digital artworks were originally designed to showcase high-quality digital artworks, rather than as general-purpose data display devices, and are not suitable for displaying information such as text, numbers, and charts.

[0082] For example, picture frame devices require the creation of special video source data from multiple viewpoints to ensure a 3D effect. These specific requirements for the data source not only increase the complexity of content creation but also raise screen costs. Using the screen to display ordinary text, numbers, and charts not only fails to fully leverage its artistic display advantages but also results in poor data presentation due to limitations in screen characteristics and display technology.

[0083] Given the unique characteristics of this type of terminal device, in order to manage it visually, the IoT platform can be applied to display devices that are separate from the terminal devices, focusing on data management of object models on the display devices, without being limited by the display technology and data format of the terminal devices.

[0084] Please see Figure 4 , Figure 4 This is a flowchart illustrating a data management method for digital paintings according to an exemplary embodiment of this application. The method can be executed on a display device distinct from a terminal device, where object model management is performed. The method may include the following steps:

[0085] Step 402: Display the object model on the display interface of the display device. The object model is constructed based on the device data of the terminal. The device data includes at least one of the following: device attributes, event attributes, and service attributes related to the digital painting.

[0086] In this step, the IoT platform can perform data management tasks on a display device separate from the terminal device. The terminal device is an electronic device used to display digital artwork, such as a high-definition display screen or a digital picture frame.

[0087] The IoT platform can display the created object model on the display interface of the display device. The object model is constructed based on the device data associated with the terminal device. The device data can cover multiple aspects closely related to the digital painting, and can include at least one of the following: device attributes, event attributes, and service attributes related to the digital painting.

[0088] Among them, device attributes related to digital paintings, such as the resolution, brightness, and color mode of the terminal device's display screen, directly affect the display effect of digital paintings.

[0089] Event attributes related to digital paintings, such as changes in digital paintings, switching of playback modes, and fault alarms, can reflect the dynamic changes of digital paintings in real time during the display process, helping users to discover and handle abnormal situations in a timely manner.

[0090] Service attributes related to digital artworks include: remote updates, scheduled playback, and integration with other electronic devices. These service attributes provide users with a wealth of operational options, enhancing the flexibility and interactivity of digital artwork displays.

[0091] On the display interface, the IoT platform also provides rich interactive functions for terminal devices, such as querying, grouping, sorting, registering, and deleting object models, as well as downloading keys. These interactive functions enable users to easily manage device data related to digital paintings, improving the efficiency and convenience of data management.

[0092] Step 404: In response to the detection of a query operation for the object model, display the device data through the visualization control corresponding to the device data based on the pre-configured mapping relationship.

[0093] In this step, the IoT platform can monitor user actions in real time, detecting whether the user triggers a query request for the object model on the display device through interactions such as clicking, selecting, or inputting. Upon detecting a query operation for the object model, the IoT platform determines the corresponding visual control for the device data based on a pre-configured mapping relationship, and displays the device data corresponding to the terminal device through this visual control.

[0094] For example, when a user wants to query the current display parameters of a digital painting on a terminal device, the IoT platform will find the corresponding visual control (such as a text box or slider) based on the mapping relationship and display the parameters on the display interface using the visual control. As another example, when a user wants to understand the playback history or fault records of a digital painting, the IoT platform will also display this device data through configured visual controls.

[0095] The data management method for digital paintings in this embodiment displays an object model on the display interface of a display device. In response to the detection of a query operation on the object model, based on a pre-configured mapping relationship, the method displays device attributes, event attributes, and service attributes related to the digital painting through visual controls corresponding to the device data. This allows users to intuitively view and manage the device data of the terminal device through a visual interface and controls on a display device separate from the terminal device. This improves the convenience and efficiency of data management while avoiding interference or damage to the artistic effect of the digital painting during data management on the terminal device, ensuring the high-quality display of the digital painting.

[0096] In one embodiment, during the object model management process, on the Internet of Things platform, users can manage device data according to their actual needs.

[0097] For example, management operations can be adding device data for new terminal devices, such as adding device attributes, event attributes, and service attributes to new terminal devices; they can also be adding device data corresponding to new device types, such as defining a completely new set of device data for a new device type; or they can be modifying device data corresponding to existing object models, such as adjusting the attribute range, event triggering conditions, or service call methods of existing terminal devices, and so on.

[0098] The IoT platform updates the device data in response to detected user management operations. It can dynamically configure matching visual controls for the updated device data; for example, the type of control can be determined based on the nature of the updated device data and display requirements. Furthermore, the size, color, font, and other attributes of the visual controls can be configured.

[0099] A new mapping relationship is dynamically constructed based on the updated device data and the matching visual controls. Based on this new mapping relationship, the updated device data is displayed using the matching visual controls.

[0100] As described above, by responding to the detection of management operations on device data, the device data is updated. Based on the updated device data and the matching visualization controls, a new mapping relationship is constructed. Based on the new mapping relationship, the updated device data is displayed. The IoT platform can dynamically configure matching visualization controls for the updated device data during runtime, realizing dynamic configuration and updating of the mapping relationship. This allows the IoT platform to quickly adapt to changes in device data. Whether it is adding a new device type, adding a new terminal device, or modifying device data, it can respond and update the device data and display method in real time, ensuring the accuracy of device data and avoiding data misalignment or visualization control failure.

[0101] If a static binding method is used to build the mapping relationship, corresponding visual controls and display logic need to be developed for each device's data, which not only increases the development workload but also raises the platform's maintenance costs. Dynamic configuration allows for flexible mapping between device data and visual controls, reducing development and maintenance complexity and minimizing additional development work caused by device upgrades or replacements. Furthermore, since the mapping relationship is dynamically built based on actual changes in device data, there is no need to redeploy the program or manually adjust the code. This flexibility greatly improves data management efficiency and shortens the time lag between device data changes and visual interface updates.

[0102] The foregoing embodiments described how to achieve visual management of device data of a terminal device by displaying a visual display model and displaying device data through visual controls. The following embodiments will provide a more detailed description of the device data visualization process, which can be applied to any of the embodiments described above.

[0103] In one embodiment, please refer to Figure 5 , Figure 5 A schematic diagram of a device data management interface is shown. Taking device data as a device attribute as an example, the IoT platform can provide functions such as importing, adding, modifying, and deleting device attributes in the device data management interface. Users can configure data parameters such as data type, identifier, name, required attributes, read / write mode, change notification, reporting interval, and format requirements for device attributes in the device data management interface.

[0104] For example, the data parameters of the device data can be as shown in Table 1:

[0105] Table 1 Data Parameters of Equipment Data

[0106]

[0107] The data types can include integers (int), floating-point numbers (float), strings (string), enumerations (enum), booleans (bool), structures (struct), and arrays (array). Reporting modes can include recurring and on-demand modes; recurring modes indicate periodic or periodic reporting, while on-demand modes indicate reporting only when device data changes.

[0108] The read / write mode can include attribute reporting (r), attribute reading (r+), and attribute setting (w). Attribute reporting (r) means that the terminal device actively reports device data, attribute reading (r+) means that the IoT platform actively reads device data from the terminal device, and attribute setting (w) means that the device data can be visually adjusted.

[0109] Please see Figure 6 , Figure 6 This diagram illustrates the creation of a new device attribute. In response to a user's action to create a new device attribute, the IoT platform displays the basic and business parameters of the device attribute.

[0110] Users can input and set the volume identifier, name, required attributes, read / write mode, change notification, data type, and format requirements. When the data type is integer, the format requirements can include the value range and step size, as well as unit symbols and units. The IoT platform detects the user's trigger action on the "OK" button and obtains... Figure 5 The volume attribute in the device data management interface shown.

[0111] If the IoT platform has configured device data read / write modes, including attribute reporting, during the construction of the object model, then in Figure 6 In the interface for creating new device properties shown, the attribute reporting in read / write mode is selected by default. Figure 5 The device data management interface shown does not need to display attribute reporting (r).

[0112] Please see Figure 7 , Figure 7 The diagram illustrates the creation of a new event. In response to a user's action to create an event, the IoT platform displays the identifier, name, event type, and event attributes. The event type can include information, warning, and error.

[0113] Users can input and set the identifier, name, and event type for low battery events, and add, edit, and delete event attributes.

[0114] Please see Figure 8 , Figure 8 This diagram illustrates the creation of a new event attribute. The IoT platform detects a user's action on the "Add" button and displays the basic parameters of the event attribute. The user can input and set the identifier, name, data type, and format requirements for the battery warning threshold. The IoT platform detects a user's action on the "OK" button and obtains... Figure 7 The battery warning threshold is shown.

[0115] Please see Figure 9 , Figure 9 This diagram illustrates the creation of a new service. In response to a user's request to create a new service, the IoT platform displays the identifier, name, required attributes, and service attributes. The service attributes can include both input and output attributes.

[0116] Users can input and set the identifier, name, and required attributes of the OTA upgrade service, and add, edit, and delete input and output attributes.

[0117] Please see Figure 10 , Figure 10 This diagram illustrates the input attributes for creating a new service. The IoT platform detects a user's interaction with the "Add" button and displays the basic parameters of the input attribute. Users can input and set the identifier, name, data type, and format requirements for the packet address. When the data type is string, the format requirements can include the data length. The IoT platform detects a user's interaction with the "OK" button and obtains... Figure 8 The packet address shown.

[0118] Please see Figure 11 , Figure 11 This diagram illustrates the output attributes of a newly created service. The IoT platform detects a user's action on the "Add" button for the output attribute and displays its basic parameters. The user can input and set the identifier, name, data type, and format requirements for the result code. When the data type is an enum, the format requirements can include the enumeration value and its corresponding description. The IoT platform detects a user's action on the "Confirm" button and obtains... Figure 9 The result code is shown.

[0119] After configuring the device data parameters for the terminal device, the IoT platform can generate a JSON file to describe the object model. An example of a JSON file is shown below:

[0120]

[0121]

[0122]

[0123]

[0124] Here, category represents the device category of the terminal device, version represents the device version of the terminal device, properties represent device attributes, events represent event attributes, and services represent service attributes.

[0125] id represents the identifier, name represents the name, required represents the required attribute, accessMode represents the read / write mode, reportMode represents the reporting mode, interval represents the reporting interval, changeNotify represents the change notification, datatype represents the data type, specs represents the format requirements, min and max represent the data range, step represents the step size, unit represents the unit symbol, and unitName represents the percentage.

[0126] By generating JSON files, both the terminal device side and the business side on the IoT platform can clearly understand the data structure and business logic of the terminal device, allowing them to carry out their respective development work, reducing the time spent on communication in intermediate business processes, and improving the maintainability and scalability of their respective programs.

[0127] In one embodiment, after configuring the data parameters of the device data, the IoT platform can display control attributes such as control style, optional control type, constraint requirements, and whether to display each device data on the visual control configuration interface.

[0128] The IoT platform can, based on the binding relationship between the data type of device data and the control type, display a set of alternative control types corresponding to each device's data on a visual control configuration interface through a list of available control types. For example, the binding relationship between data type and control type can be shown in Table 2:

[0129] Table 2. Binding Relationship between Data Types and Control Types

[0130] Data types Control Type Integer (int) sliders, rotators, calendars, time pickers, text boxes, etc. Floating-point type (float) sliders, rotators, text boxes, etc. String Tags, hyperlinks, multiline text boxes, text boxes, etc. Enumeration (enum) Radio buttons, drop-down lists, text boxes, etc. Boolean (bool) Radio buttons, drop-down lists, text boxes, etc. Structure (struct) Lists, data tables, multi-line text boxes, text boxes, etc. Array Lists, data tables, multi-line text boxes, text boxes, etc.

[0131] Please see Figure 12 , Figure 12 A schematic diagram of a visual control configuration interface is shown. The interface can display control properties corresponding to volume, playback mode, carousel duration, playback order, battery warning threshold, packet address, and result code.

[0132] The volume data type is integer. The list of available control types corresponding to the volume data displays a set of alternative control types for each device, including sliders, rotators, calendars, time pickers, text boxes, etc.

[0133] The data type-control type binding relationship is the process of associating a specific data type with a series of applicable control types, used to intelligently recommend or restrict the control types that can represent device data. The alternative control type set is a predefined collection containing various visualization control types, which can be set and adjusted according to common data display needs, helping users select the most suitable control from multiple visualization methods for the current device data display requirements.

[0134] As described above, by displaying a set of alternative control types based on the binding relationship between the data type of the device data and the control type, and by automatically recommending suitable alternative control types based on the data type of the device data, compatibility issues between controls that do not match the control type and the device data can be avoided, thereby improving the configuration efficiency of visual controls and mapping relationships.

[0135] In one embodiment, a user can select a suitable target control type from a list of optional control types for each device data item. The IoT platform detects the target control type selected by the user from the set of optional control types and determines the visual control based on the target control type. A mapping relationship between the device data and the visual control is then configured based on the device data and the visual control.

[0136] The target control type is a control type selected from the set of candidate control types, and is chosen by the user based on the characteristics of the device data and display requirements.

[0137] Please continue reading. Figure 12 Users can select the target control type for the volume slider from a list of available control types. The IoT platform detects the slider selected by the user from the set of available control types and determines the visual control type of the slider.

[0138] Configure the mapping relationship between the volume control and the slider control, based on the volume and slider type. The current volume value can be mapped to the current value of the slider control. When the volume value changes, the position of the slider in the slider control will also be updated accordingly to reflect the new volume value.

[0139] As described above, by detecting the target control type selected by the user from the set of alternative control types, and determining the visual control based on the target control type, it is possible to ensure that the target control can flexibly adapt to the data format and display requirements of different devices, making the device data display more intuitive and easy to understand, and improving the user's ability to understand and analyze device data. Based on device data and visual controls, a mapping relationship can be configured. By providing a rich selection of alternative control types and flexible mapping relationship configuration, it is possible to better adapt to different device types and device data.

[0140] In one embodiment, when a user adds or edits device data, the IoT platform receives the format requirements set by the user for the device data. Based on these format requirements, the IoT platform determines the constraints for the visual controls.

[0141] Format requirements are the standards or regulations set for the format of device data input and storage, such as the range of device data values, step size, and length range. Constraint requirements are the specific restrictions set on visual controls based on the format requirements, such as the control's value range, step size, and input type.

[0142] Please continue reading. Figure 12The IoT platform can determine the value range and step size of the visual control based on the volume's value range and step size, and display the corresponding value range and step size of the visual control on the visual control configuration interface. For example, Figure 12 The specific configurations for each device's data are as follows:

[0143] 1)Volume

[0144] The volume data type is integer, the volume value range is 0-100, and the volume step is 10. The visual control can be a slider control, the slider control value range is 0-100, and the slider control step is 10.

[0145] 2) Playback Mode

[0146] The data type for playback mode is integer, the value range for playback mode is 1-5, and the step size for playback mode is 1. The visual control can be a slider control, the value range for slider control is 0-5, and the step size for slider control is 1.

[0147] 3) Carousel duration

[0148] The data type for the carousel duration is a string, and the data length for the carousel duration is 16. The visual control can be a text box control.

[0149] 4) Playback order

[0150] The data type for playback order is integer, the value range for playback order is 1-3, and the step size for playback order is 1. 1-3 can represent sequential playback, random playback, and single-track loop respectively. The visual control can be a slider control, the value range for slider control is 1-3, and the step size for slider control is 1.

[0151] 5) Battery warning threshold

[0152] The data type of the battery warning threshold is integer, the value range of the battery warning threshold is 0-100, and the step size of the battery warning threshold is 1. The visual control can be a slider control, the value range of the slider control is 0-100, and the step size of the slider control is 1.

[0153] 6) Package address

[0154] The data type of the packet address is a string, the data length of the packet address is 16, and the visual control can be a text box control.

[0155] 7) Result Code

[0156] The data type of the result code is an enumeration. The enumeration values ​​of the result code include 0, 1 and 2, where 0 indicates success, 1 indicates download failure and 2 indicates upgrade failure. The visual control can be a radio button control.

[0157] As described above, by receiving the user's format requirements for device data, the constraints of the visual control are determined according to the format requirements, ensuring that the device data displayed by the visual control not only conforms to the format requirements of the device data, but is also within a reasonable range, thereby improving the accuracy and usability of the visual control.

[0158] It is understood that the data parameters of device attributes, event attributes and service attributes shown above are only examples. The corresponding data parameters of device data can also be configured based on different terminal devices, as long as the method described in the embodiments of this application is implemented. The embodiments of this application do not limit this.

[0159] In one embodiment, when a user adds or edits device data, the IoT platform receives a visual configuration instruction from the user regarding the device data. After displaying the device data through a visual control, the platform detects adjustments made to the visual control and monitors the state changes of the visual control in real time. The visual configuration instruction reflects support for adjusting device data through the visual control.

[0160] New Figure 6 Taking the volume setting as an example, after the user selects the attribute setting (w) in the read / write mode, they confirm the creation of a new volume attribute, which can then be adjusted via visual controls. The IoT platform receives visual configuration instructions from the user regarding device data; please refer to [link / reference]. Figure 3 The visual control page shown displays the volume via a slider control and then detects whether the user has performed an adjustment operation on the slider control.

[0161] As described above, by receiving visual configuration instructions from users for device data and detecting adjustment operations for visual controls, users can flexibly configure whether to adjust device data through visual controls according to actual needs. For device data that needs to be adjusted frequently, users can choose to use visual controls to simplify data configuration operations. For device data that is not frequently adjusted, users can choose not to use controls to reduce interface complexity, thereby improving the efficiency and accuracy of the data management process.

[0162] In one embodiment, please refer to Figure 13 , Figure 13 An interactive diagram illustrating a method for adjusting device data, which can be applied to a first Internet of Things (IoT) system, is shown. Please refer to [link / reference]. Figure 14 , Figure 14 A schematic diagram of the structure of a first Internet of Things (IoT) system is shown. Taking a picture frame device as an example, the first IoT system may include a picture frame device 1401 and a management terminal 1402.

[0163] An application for communicating with a management terminal 1402 can be deployed in the picture frame device 1401. The management terminal 1402 may include an Internet of Things (IoT) platform, and can communicate with the picture frame device 1401 through the application in the picture frame device 1401. The management terminal 1402 may be a display device different from the picture frame device 1401, or it may be other electronic devices; there is no limitation on this.

[0164] like Figure 13 As shown, the adjustment method may include the following steps:

[0165] Step 1302: The picture frame device reports device data to the management terminal.

[0166] In this step, the picture frame device 1401 responds to the control command sent by the management terminal 1402 and reports device data such as device attributes, event attributes and service attributes to the management terminal 1402 through the application.

[0167] Step 1304: The management terminal constructs an object model based on the device data.

[0168] In this step, the management terminal 1402 constructs an object model based on the received device data. The object model can represent the attributes, services, events, etc. of the picture frame device 1401. The picture frame device 1401 is then registered with the network for subsequent management and monitoring.

[0169] Step 1306: The management terminal receives the data parameters configured by the user for the device data.

[0170] In this step, the management terminal 1402 receives data parameters such as the data type, format requirements, and visual configuration instructions for the device data in order to create new device data.

[0171] Step 1308: The management end determines the visual control based on the target control type and format requirements.

[0172] In this step, the management terminal 1402 displays a set of candidate control types based on the binding relationship between the data type of the device data and the control type. It then detects the target control type selected by the user from this set and determines the visual control. Finally, it determines the constraints of the visual control based on the format requirements of the device data.

[0173] Step 1310: The management terminal configures the mapping relationship based on device data and visual controls.

[0174] In this step, the management terminal 1402 configures the mapping relationship between the device data and the defined visual controls.

[0175] Step 1312: The management terminal displays the object model on the display interface.

[0176] Step 1314: In response to the detection of a query operation, the management terminal displays device data through a defined visual control based on the mapping relationship.

[0177] In this step, the management terminal 1402 responds to the detection of a query operation for the object model, determines the visualization control corresponding to the device data based on the configured mapping relationship, and displays the device data through the determined visualization control.

[0178] Step 1316: The management terminal responds to the detection of an adjustment operation on the visual control and determines the adjustment parameters of the device data.

[0179] In this step, the user adjusts the device data using visual controls on the centralized control interface. The management terminal 1402, upon detecting the adjustment operation on the visual controls, determines the adjustment parameters for the device data.

[0180] Please continue reading. Figure 3 For example, when a user performs an adjustment operation such as dragging the volume slider control, the management terminal 1402, in response to detecting the adjustment operation on the slider control, determines the volume adjustment parameters based on the step size of the slider control.

[0181] Step 1318: The management terminal sends control commands to the picture frame device.

[0182] In this step, the management terminal 1402 sends control commands to the picture frame device. The control commands can carry adjustment parameters of the device data.

[0183] Step 1320: The picture frame equipment adjusts the equipment data.

[0184] In this step, the picture frame device receives the control command sent by the management terminal 1402 and adjusts the device data according to the adjustment parameters carried in the control command.

[0185] Step 1322: The picture frame device sends a confirmation message to the management terminal.

[0186] In this step, after the device data is successfully adjusted, the picture frame device sends a confirmation message to the management terminal 1402. The confirmation message is used to identify that the picture frame device has been adjusted to the new device data, and may include the adjusted device data value, identifier, etc.

[0187] Step 1324: Upon receiving the confirmation message, the management terminal displays the new device data.

[0188] In this step, the management terminal 1402 receives the confirmation message sent by the picture frame device 1401. In response to receiving the confirmation message returned by the picture frame device 1401, it updates the visual controls on the visual control interface to display the new device data. The user can immediately see that the adjustment operation has taken effect and the device data has been updated to the new device data.

[0189] As described above, by responding to the detection of an adjustment operation on the visual control, the adjustment parameters of the device data are determined, and a control command is sent to the terminal device to make the terminal device adjust the device data. In response to receiving a confirmation message from the terminal device, the new device data is displayed. Through standardized control commands and confirmation messages, the management and configuration of device data can be simplified, the synchronization and consistency of device data can be ensured, and the ease of use and reliability of data management can be improved.

[0190] In one embodiment, please refer to Figure 15 , Figure 15 An interactive diagram illustrating another method for adjusting device data, which can be applied to a second IoT system, is shown. Please refer to... Figure 16 , Figure 16 A schematic diagram of a second Internet of Things (IoT) system is shown, which may include a picture frame device 1601, a server 1602, and a management terminal 1603.

[0191] An application for communicating with the server 1602 can be deployed in the picture frame device 1601. The management terminal 1603 may include an Internet of Things (IoT) platform, and the management terminal 1603 can communicate with the server 1602 via a network connection.

[0192] like Figure 15 As shown, the adjustment method may include the following steps:

[0193] Step 1502: The picture frame device reports device data to the server.

[0194] In this step, the picture frame device 1601 reports device data such as device attributes, event attributes and service attributes of the picture frame device 1601 to the server 1602.

[0195] Step 1504: The server reports device data to the management terminal.

[0196] In this step, the server 1602 will store and forward the device data received from the picture frame device 1601, and report the device data to the management terminal 1603.

[0197] Step 1506: The management terminal constructs an object model based on the device data.

[0198] In this step, the management terminal 1603 constructs an object model based on the received device data and registers the picture frame device 1401 to the network for subsequent management and monitoring.

[0199] Step 1508: The management terminal receives the data parameters for device data configuration.

[0200] In this step, the management terminal 1603 receives data parameters from the user regarding the data type, format requirements, and visual configuration instructions for the device data configuration, in order to create new device data.

[0201] Step 1510: The management end determines the visual control based on the target control type and format requirements.

[0202] In this step, the management terminal 1603 determines the visual control configured for the device data based on the target control type and format requirements of the device data.

[0203] Step 1512: The management terminal configures the mapping relationship based on device data and visual controls.

[0204] In this step, the management terminal 1603 configures the mapping relationship between the device data and the defined visual controls.

[0205] Step 1514: The management terminal displays the object model on the display interface.

[0206] Step 1516: In response to the detection of the query operation, the management terminal displays the device data through a visual control based on the mapping relationship.

[0207] In this step, the management terminal responds to the detection of a query operation on the object model and displays device data through a defined visual control based on the configured mapping relationship.

[0208] Step 1518: The management terminal responds to the detection of an adjustment operation on the visual control and determines the adjustment parameters of the device data.

[0209] Step 1520: The management terminal sends control commands to the server.

[0210] In this step, the management terminal 1603 sends a control command to the server terminal 1602. The control command can carry adjustment parameters of the device data.

[0211] Step 1522: The server sends control commands to the picture frame device.

[0212] In this step, the server 1602 records and forwards the adjustment parameters of the device data and sends control commands to the picture frame device 1601.

[0213] Step 1524: The picture frame equipment adjusts the equipment data.

[0214] Step 1526: The picture frame device sends a confirmation message to the server.

[0215] In this step, the picture frame device 1601 sends a confirmation message carrying new device data to the server 1602.

[0216] Step 1528: The server calculates the actual adjustment value based on the original device data and the new device data.

[0217] In this step, the server 1602 calculates the actual adjustment value of the frame device 1601 for the device data based on the original device data before adjustment and the new device data after adjustment of the frame device 1601.

[0218] Step 1530: If the server determines that the actual adjustment value and the adjustment parameter are the same, it sends a confirmation message to the management terminal.

[0219] In this step, if the actual adjustment value and the adjustment parameter are the same, the server 1602 can determine that the device data adjustment is successful, forward the confirmation message, and send a confirmation message to the management terminal 1603.

[0220] Step 1532: Upon receiving the confirmation message, the management terminal displays the new device data.

[0221] In this step, the management terminal 1603 responds to the received confirmation message by updating the visual controls on the visual control interface to display the new device data.

[0222] As described above, by sending control commands to the server, the server forwards the control commands to the terminal devices. Upon confirming that the actual adjustment value and adjustment parameters of the device data are the same, the server returns a confirmation message received from the terminal devices to the management end. As an intermediary device, the server can centrally receive control commands from multiple management ends and uniformly manage and distribute them to the corresponding terminal devices. This helps simplify the network architecture, reduce potential security risks, lower management complexity, and facilitate system expansion and upgrades. Furthermore, by confirming that the actual adjustment value and adjustment parameters of the device data are the same before returning the confirmation message to the management end, the accuracy and reliability of the control command execution can be ensured.

[0223] In one embodiment, please refer to Figure 17 , Figure 17 A flowchart illustrating another method for adjusting device data is provided. Taking an IoT platform deployed on a picture frame device as an example, this adjustment method may include the following steps:

[0224] Step 1702: Obtain the object model corresponding to the picture frame device.

[0225] In this step, the picture frame device can obtain the object model corresponding to the picture frame device by sending a request for the object model to the management terminal or by pre-installing the object model in the picture frame device.

[0226] Step 1704: Receive data parameters from the user for device data configuration.

[0227] Step 1706: Determine the visual control based on the target control type and format requirements.

[0228] Step 1708: Configure the mapping relationship based on device data and visual controls.

[0229] Step 1710: Display the object model on the display interface.

[0230] Step 1712: In response to the detection of a query operation for the object model, determine the visualization control corresponding to the device data based on the pre-configured mapping relationship.

[0231] Step 1714: Display device data using visual controls.

[0232] Step 1716: In response to the detection of an adjustment operation for the visual control, determine the adjustment parameters of the device data.

[0233] Step 1718: Adjust the device data and display the new device data.

[0234] In this step, the picture frame device adjusts the device data, updates the visual controls on the visual control interface, and displays the new device data. The specific implementation process of configuring and visualizing the above-mentioned object model and device data can be found in the corresponding steps of the above method, and will not be repeated here.

[0235] Figure 18 This is a schematic diagram illustrating the structure of an electronic device according to an exemplary embodiment of this application. The electronic device may be, for example, a mobile phone, computer, digital broadcasting terminal device, messaging device, game console, tablet device, personal digital assistant, server, smart home appliance, in-vehicle system, etc. (Reference) Figure 18At the hardware level, the electronic device includes a processor 1802, an internal bus 1804, a network interface 1806, memory 1808, and non-volatile memory 1810, and may also include other hardware required for business operations. The processor 1802 reads the corresponding computer program from the non-volatile memory 1810 into the memory 1808 and then runs it, forming a data management device / digital artwork data management device at the logical level. Of course, in addition to software implementation, this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to individual logic units, but can also be hardware or logic devices.

[0236] Figure 19 This is a block diagram illustrating a data management device according to an exemplary embodiment of this application. (Refer to...) Figure 19 The device may include: a physical model display module 1902, a control determination module 1904, and a data display module 1906, wherein:

[0237] The object model display module 1902 is used to display an object model on a display interface. The object model is constructed by using device data from a terminal device.

[0238] The control determination module 1904 is used to determine the visual control corresponding to the device data based on a pre-configured mapping relationship in response to detecting a query operation for the object model.

[0239] The data display module 1906 is used to display the device data through the visualization control.

[0240] In one example, the control determination module 1904, before determining the visual control corresponding to the device data based on a pre-configured mapping relationship in response to detecting a query operation for the object model, further includes: detecting the target control type selected by the user from a set of candidate control types; determining the visual control according to the target control type; and configuring the mapping relationship based on the device data and the visual control.

[0241] In one example, the control determination module 1904, before configuring the mapping relationship based on the device data and the visual control, further includes: displaying the set of alternative control types according to the binding relationship between the data type of the device data and the control type.

[0242] In one example, the control determination module 1904, before configuring the mapping relationship based on the device data and the visual control, further includes: receiving format requirements set by the user for the device data; and determining the constraint requirements of the visual control according to the format requirements.

[0243] In one example, the method is applied to a management terminal. The data display module 1906 is further configured to, in response to detecting an adjustment operation on the visualization control, determine adjustment parameters for the device data; send a control command to the terminal device to cause the terminal device to adjust the device data, the control command carrying the adjustment parameters; and, in response to receiving a confirmation message returned by the terminal device, display new device data, the confirmation message indicating that the terminal device has been adjusted to the new device data.

[0244] In one example, the data display module 1906, before determining the adjustment parameters of the device data in response to detecting an adjustment operation on the visualization control, further includes: receiving a visual configuration indication for the device data, the visual configuration indication reflecting support for adjusting the device data through the visualization control; and detecting an adjustment operation on the visualization control.

[0245] In one example, the data display module 1906, when sending control instructions to the terminal device, includes: sending the control instructions to the server so that the server forwards the control instructions to the terminal device, and, if it is determined that the actual adjustment value of the device data is the same as the adjustment parameter, returning the confirmation message received from the terminal device to the management terminal.

[0246] In one example, the device data includes at least one of the following: device attributes, event attributes, and service attributes; wherein the device attributes are used to reflect the current state of the terminal device, the event attributes are used to reflect the specific conditions that trigger the event, and the service attributes are used to reflect at least one of the calling method and calling result of the terminal device executing the service.

[0247] Figure 20 This is a block diagram illustrating a data management device for a digital painting according to an exemplary embodiment of this application. (Refer to...) Figure 20 The device may include: a first display module 2002 and a second display module 2004, wherein:

[0248] The first display module 2002 is used to display an object model on the display interface of the display device. The object model is constructed based on device data of the terminal device. The device data includes at least one of the following: device attributes, event attributes, and service attributes related to the digital painting.

[0249] The second display module 2004 is used to respond to the detection of a query operation for the object model and display the device data through a visualization control corresponding to the device data based on a pre-configured mapping relationship.

[0250] In one example, the second display module 2004 is further configured to, in response to detecting a management operation on the device data during the object model management process, update the device data; construct a new mapping relationship based on the updated device data and a matching visualization control; and display the updated device data based on the new mapping relationship.

[0251] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0252] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0253] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions, such as a memory including instructions, is also provided, which can be executed by a processor of a data management device to implement the method as described in any of the above embodiments.

[0254] The non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc., and this application does not limit it.

[0255] In an exemplary embodiment, a computer program product including a computer program / instructions is also provided, which can be executed by a processor of a data management device to implement the method described in any of the above embodiments.

[0256] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0257] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention filed herein. This application is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and alterations can be made without departing from its scope. The scope of this application is limited only by the appended claims.

[0258] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A data management method, characterized in that, The method includes: The object model is displayed on the display interface. The object model is constructed by the device data of the terminal device. In response to the detection of a query operation for the object model, the visualization control corresponding to the device data is determined based on a pre-configured mapping relationship; The device data is displayed through the visual control.

2. The method according to claim 1, characterized in that, Before determining the visualization control corresponding to the device data based on a pre-configured mapping relationship in response to detecting a query operation for the object model, the method further includes: Detect the type of the target control selected by the user from the set of alternative control types; The visual control is determined based on the target control type; Configure the mapping relationship based on the device data and the visualization control.

3. The method according to claim 2, characterized in that, Before configuring the mapping relationship based on the device data and the visualization control, the method further includes: Based on the binding relationship between the data type of the device data and the control type, the set of alternative control types is displayed.

4. The method according to claim 2, characterized in that, Before configuring the mapping relationship based on the device data and the visualization control, the method further includes: Receive the user's format requirements for the device data; Based on the stated format requirements, determine the constraints of the visual control.

5. The method according to claim 1, characterized in that, The method is applied to the management terminal, and the method further includes: In response to detecting an adjustment operation on the visualization control, the adjustment parameters of the device data are determined; Send a control command to the terminal device to cause the terminal device to adjust the device data, wherein the control command carries the adjustment parameters; In response to receiving a confirmation message from the terminal device, new device data is displayed, wherein the confirmation message indicates that the terminal device has been adjusted to the new device data.

6. The method according to claim 5, characterized in that, Before determining the adjustment parameters of the device data in response to detecting an adjustment operation on the visualization control, the method further includes: Receive a visual configuration instruction for the device data, the visual configuration instruction being used to reflect support for adjusting the device data through the visual controls; Detect adjustments made to the visual control.

7. The method according to claim 5, characterized in that, Sending control commands to the terminal device includes: The control command is sent to the server so that the server forwards the control command to the terminal device. If the actual adjustment value of the device data is the same as the adjustment parameter, the server returns the confirmation message received from the terminal device to the management terminal.

8. The method according to claim 1, characterized in that, The device data includes at least one of the following: device attributes, event attributes, and service attributes; The device attributes reflect the current state of the terminal device, the event attributes reflect the specific conditions that trigger the event, and the service attributes reflect at least one of the calling method and the calling result of the service executed by the terminal device.

9. A data management method for digital paintings, characterized in that, The method involves managing object models on a display device distinct from a terminal device used to display digital artwork; the method includes: A model of an object is displayed on the display interface of the display device. The model of the object is constructed based on device data of the terminal device. The device data includes at least one of the following: device attributes, event attributes, and service attributes related to the digital painting. In response to the detection of a query operation for the object model, the device data is displayed through a visualization control corresponding to the device data based on a pre-configured mapping relationship.

10. The method according to claim 9, characterized in that, The method further includes: During the object model management process, the device data is updated in response to the detection of a management operation on the device data; Based on the updated device data and matching visual controls, construct a new mapping relationship; Based on the new mapping relationship, the updated device data is displayed.

11. A data management device, characterized in that, The device includes: The object model display module is used to display the object model on the display interface. The object model is constructed by using the device data of the terminal device. The control determination module is used to determine the visual control corresponding to the device data based on a pre-configured mapping relationship in response to the detection of a query operation for the object model. The data display module is used to display the device data through the visualization control.

12. A data management device for digital paintings, characterized in that, Object model management is performed on a display device distinct from a terminal device, wherein the terminal device is used to display digital artwork; the device includes: The first display module is used to display an object model on the display interface of the display device. The object model is constructed based on device data of the terminal device. The device data includes at least one of the following: device attributes, event attributes, and service attributes related to the digital painting. The second display module is used to respond to the detection of a query operation for the object model and display the device data through a visualization control corresponding to the device data based on a pre-configured mapping relationship.

13. An electronic device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor implements the method as described in any one of claims 1-10 by executing the executable instructions.

14. A computer-readable storage medium storing computer instructions thereon, characterized in that, When executed by the processor, this instruction implements the method as described in any one of claims 1-10.

15. A computer program product having a computer program / instructions stored thereon, characterized in that, When the computer program / instruction is executed by the processor, it implements the method as described in any one of claims 1-10.

Images