WO2023088469A1 - Procédé et appareil de gestion de dispositif, dispositif électronique, support de stockage et produit-programme - Google Patents

Procédé et appareil de gestion de dispositif, dispositif électronique, support de stockage et produit-programme Download PDF

Info

Publication number
WO2023088469A1
WO2023088469A1 PCT/CN2022/133254 CN2022133254W WO2023088469A1 WO 2023088469 A1 WO2023088469 A1 WO 2023088469A1 CN 2022133254 W CN2022133254 W CN 2022133254W WO 2023088469 A1 WO2023088469 A1 WO 2023088469A1
Authority
WO
WIPO (PCT)
Prior art keywords
object model
model file
function
management
attribute information
Prior art date
Application number
PCT/CN2022/133254
Other languages
English (en)
Chinese (zh)
Inventor
黄王爵
邢佳
熊阅文
蒋文忠
Original Assignee
上海商汤智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 上海商汤智能科技有限公司 filed Critical 上海商汤智能科技有限公司
Publication of WO2023088469A1 publication Critical patent/WO2023088469A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/168—Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Definitions

  • the embodiment of the present disclosure is based on the Chinese patent application with the application number 202111408125.4, the application date is November 19, 2021, and the application name is "equipment management method, device, electronic equipment and storage medium", and the priority of the Chinese patent application is required Right, the entire content of this Chinese patent application is hereby incorporated into this disclosure as a reference.
  • the present disclosure relates to the technical field of computers, and in particular to a device management method, device, electronic device, storage medium and program product.
  • the way to realize remote control and management of multiple devices is usually to write the control logic on the management platform and the device terminal separately, and ensure that the functions of the management platform are consistent with those of the devices.
  • this method has disadvantages such as poor maintainability, error-prone, and high R&D costs, resulting in a high degree of strong dependence between the device and the management platform version, resulting in poor device management flexibility. .
  • An embodiment of the present disclosure provides a device management method applied to a device management platform, including:
  • the object model file is used to indicate the function information of the device and the attribute information corresponding to each function
  • the device is managed based on the packaged object model file.
  • the data interaction and update of the device, the device management platform, and the client are realized based on the object model file.
  • the management platform is enough, without rewriting the corresponding logic program of the device management platform, and the device is managed based on the encapsulated object model file, thereby reducing the coupling degree between the device and the device management platform, and improving the flexibility of device management sex.
  • the managing the device based on the packaged object model file includes:
  • sending the encapsulated object model file of the device to the client can make the function displayed by the client consistent with the device function, and reduce the coupling degree between the device and the device management platform, and improve the Flexibility in device management.
  • the managing the device based on the packaged object model file includes:
  • Analyzing the packaged object model file extracting target data indicating the function information and attribute information corresponding to each function;
  • the object model file of the device when sending the object model file of the device to the client, the object model file can be analyzed first to obtain the target data, and then the target data is sent to the client, which can improve the accuracy of extracting the target data, This ensures that the functions displayed by the client are consistent with the device functions.
  • the object model file includes an object model file defined by the device initialization or an object model file after the device is updated.
  • the object model file defined by device initialization or the object model file after device update is uploaded to the device management platform in real time, which can ensure that the device management platform obtains the function information of the device in real time, thereby ensuring that the functions displayed by the client can be compared with Device functionality remains the same.
  • the parsing the packaged object model file, and extracting the target data indicating the function information and the attribute information corresponding to each function includes:
  • the object model file is parsed to extract target data indicating the function information and attribute information corresponding to each function.
  • the object model file is analyzed based on the object model protocol version information and the object model file version information, which can improve the accuracy of extracting target data.
  • the sending the target data to the client includes:
  • the acquisition instruction is an instruction generated by the client in response to a request operation for the management page;
  • the target data is sent to the client.
  • the target data is sent to the client, which can save system resources, and can also make the functions displayed by the client consistent with the functions of the device.
  • the device includes a device information display interface; the method further includes:
  • receiving the modified attribute information sent by the device is beneficial for the device management platform to obtain the modified device function information in real time.
  • the attribute information includes at least one of parameter name, parameter type, control style and validation rule.
  • An embodiment of the present disclosure provides a device management method applied to a client, including:
  • the object model file is used to indicate the function information of the device and the attribute information corresponding to each function;
  • a management page of the device is displayed, and the content displayed on the management page includes function information of the device and attribute information corresponding to each function.
  • the data interaction and update between the device management platform and the client are realized based on the object model file.
  • the client only needs to receive the object model file of the device, and does not need to rewrite the corresponding logic program of the client , so that the functions displayed by the client can be consistent with the functions of the device, thereby reducing the degree of coupling between the device, the device management platform, and the client.
  • the method further includes:
  • the display of the management page of the device based on the object model file includes:
  • Analyzing the object model file extracting target data indicating the function information and attribute information corresponding to each function
  • a management page of the device is displayed, and the content displayed on the management page includes function information of the device and attribute information corresponding to each function.
  • the object model file is in a parsed state, and when the object model file is in an unresolved state, the object model file is parsed on the client side, so as to improve the accuracy of extracting target data, and then Ensure that the functions displayed by the client can be consistent with the device functions.
  • the method also includes:
  • the display of the management page of the device based on the object model file includes:
  • a management page of the device is displayed, and the content displayed on the management page includes function information of the device and attribute information corresponding to each function.
  • the target data is extracted and the management page of the device is displayed, which can improve the accuracy of the target data extraction, thereby ensuring that the functions displayed by the client can be maintained with the device functions. unanimous.
  • the displaying the management page of the device based on the target data includes:
  • the management page of the language environment is displayed, that is, it can be rendered flexibly according to the language environment of the client, which is beneficial to improve the multilingualism of the object model. Applicability in the scene.
  • the method also includes:
  • the attribute information of the device function can be modified through the management page, so as to realize the remote control and modification of the device, and then the device can be debugged more quickly.
  • An embodiment of the present disclosure provides a device management method applied to a device, including:
  • the object model file is generated
  • the object model file After the object model file is encapsulated, it is sent to the device management platform, so that the device management platform manages the device based on the object model file.
  • the data interaction and update between the device and the device management platform are realized based on the object model file.
  • the object model file of the device it is only necessary to send the object model file of the device to the device management platform That is, there is no need to rewrite the corresponding logic program of the device management platform, thereby reducing the degree of coupling between the device and the device management platform.
  • the device includes a device information display interface; the method further includes:
  • the updated object model file is packaged and then sent to the device management platform.
  • the updated object model file can be packaged and sent to the device management platform in real time, thereby ensuring the consistency of the device function information and the function information of the device management platform in real time.
  • An embodiment of the present disclosure also provides an equipment management device, the device includes:
  • the first receiving part is configured to receive the packaged object model file sent by the device, the object model file is used to indicate the function information of the device and the attribute information corresponding to each function;
  • the management part is configured to manage the device based on the packaged object model file.
  • the management part is also configured to:
  • the management part is also configured to:
  • Analyzing the packaged object model file extracting target data indicating the function information and attribute information corresponding to each function;
  • the object model file includes an object model file defined by the device initialization or an object model file after the device is updated.
  • the management part is also configured to:
  • the object model file is parsed to extract target data indicating the function information and attribute information corresponding to each function.
  • the management part is also configured to:
  • the acquisition instruction is an instruction generated by the client in response to a request operation for the management page;
  • the target data is sent to the client.
  • the attribute information includes at least one of parameter name, parameter type, control style and validation rule.
  • An embodiment of the present disclosure also provides an equipment management device, the device includes:
  • the second receiving part is configured to receive an object model file, the object model file is used to indicate the function information of the device and the attribute information corresponding to each function;
  • the display part is configured to display the management page of the device based on the object model file, and the content displayed on the management page includes function information of the device and attribute information corresponding to each function.
  • the display part is further configured as:
  • a management page of the device is displayed, and the content displayed on the management page includes function information of the device and attribute information corresponding to each function.
  • the display part is further configured as:
  • a management page of the device is displayed, and the content displayed on the management page includes function information of the device and attribute information corresponding to each function.
  • the display part is further configured as:
  • the device further includes a first modification part, and the first modification part is configured to:
  • An embodiment of the present disclosure also provides an equipment management device, the device includes:
  • the generation part is configured to generate a model file based on the function information of the device and the attribute information corresponding to each function;
  • the sending part is configured to encapsulate the object model file and send it to the device management platform, so that the device management platform manages the device based on the object model file.
  • the device includes a device information display interface; the apparatus further includes a second modifying part, and the second modifying part is configured to:
  • the send section is also configured to:
  • the updated object model file is packaged and then sent to the device management platform.
  • An embodiment of the present disclosure also provides an electronic device, including: a processor, a memory, and a bus, the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the The memories communicate through the bus, and the machine-readable instructions are executed by the processor to execute the steps of the device management method above.
  • An embodiment of the present disclosure further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above device management method are executed.
  • An embodiment of the present disclosure also provides a computer program product, including computer-readable codes.
  • the computer program product includes a computer program or an instruction, and when the computer program or instruction is run on an electronic device, the electronic device Execute the steps of the above device management method.
  • FIG. 1 is a schematic structural diagram of a device management system provided by an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a first device management method provided by an embodiment of the present disclosure
  • FIG. 3 is a flow chart of a method for managing equipment based on an object model file provided by an embodiment of the present disclosure
  • FIG. 4 is a flowchart of a method for sending target data to a client provided by an embodiment of the present disclosure
  • FIG. 5 is a flowchart of a second device management method provided by an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a management page provided by an embodiment of the present disclosure.
  • FIG. 7 is a flow chart of a method for displaying a management page of a device based on an object model file provided by an embodiment of the present disclosure
  • FIG. 8 is a flow chart of a method for displaying device management pages based on target data provided by an embodiment of the present disclosure
  • FIG. 9 is a schematic diagram of another management page provided by an embodiment of the present disclosure.
  • FIG. 10 is a flowchart of a third device management method provided by an embodiment of the present disclosure.
  • FIG. 11 is a flowchart of a fourth device management method provided by an embodiment of the present disclosure.
  • FIG. 12 is a flowchart of a fifth device management method provided by an embodiment of the present disclosure.
  • FIG. 13 is a schematic flowchart of interaction among a device, a device management device, and a client provided by an embodiment of the present disclosure
  • FIG. 14 is a schematic flowchart of another device, a device management device, and a client interaction provided by an embodiment of the present disclosure
  • FIG. 15 is a schematic structural diagram of a first device management device provided by an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a second device management device provided by an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of a third device management device provided by an embodiment of the present disclosure.
  • Fig. 18 is a schematic diagram of an electronic device provided by an embodiment of the present disclosure.
  • the face access control device and the face thermometer are devices with different functions, but both can be connected to the same device management platform, and the door sensor status and/or The access control function setting page, and the thermal imager connection status and/or temperature measurement function setting page of the face thermometer.
  • FIG. 1 is a schematic diagram of an architecture of a device management system provided by an embodiment of the present disclosure.
  • the device management system includes multiple devices (such as device 10 , device 20 , device 30 and device 40 ), a device management platform 100 and a client 200 .
  • multiple devices may be devices of the same type and different models, for example, multiple devices may be face access control devices or multiple devices may be face thermometers; of course, multiple devices may also be different types of devices , For example, multiple devices include both face access control devices and face thermometers.
  • the network may include various connection types, such as wires, wireless communication links, or fiber optic cables, among others.
  • the device management platform 100 may be a server, where the server may be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, and may also provide cloud services, cloud databases, cloud computing Cloud servers for basic cloud computing services such as cloud storage, big data and artificial intelligence platforms.
  • the client 200 may include various electronic devices, such as mobile phones, tablet computers, etc., which are not limited here.
  • the way to realize remote control and management of multiple devices is usually to write the control logic on the device management platform and the device terminal respectively, and ensure that the functions of the device management platform are consistent with the functions of the devices.
  • this method has disadvantages such as poor maintainability, error-prone, and high R&D costs, resulting in a high degree of strong dependence between the device and the management platform version.
  • an embodiment of the present disclosure provides a device management method applied to a device management platform, including: receiving a packaged object model file sent by a device, the object model file is used to indicate the function information of the device and Attribute information corresponding to each function; based on the packaged object model file, the device is managed.
  • the data interaction and update between the device and the device management platform are realized based on the object model file.
  • the object model file of the device it is only necessary to send the object model file of the device to the device management platform That is, there is no need to rewrite the corresponding logic program of the device management platform, and the device is managed based on the encapsulated object model file, thereby reducing the degree of coupling between the device and the device management platform.
  • FIG. 2 is a flow chart of the first device management method provided by an embodiment of the present disclosure.
  • the device management method may invoke computer-readable instructions stored in a memory through a processor. way to achieve.
  • the device management method provided by the embodiment of the present disclosure can be applied to the device management platform in Figure 1, including the following S101-S102:
  • S101 Receive a packaged object model file sent by a device, where the object model file is used to indicate function information of the device and attribute information corresponding to each function.
  • the packaging form of the packaged object model file is in the form of a JSON (JavaScript Object Notation) file, which is a lightweight data representation method.
  • JSON JavaScript Object Notation
  • the JSON file format adopts a key-value (key:value) method to record data, and the file is encapsulated in this way, making the file content more concise and intuitive, thereby facilitating the management of the object model file.
  • the object model file is used to indicate the function information of the device and the attribute information corresponding to each function.
  • the object model file is a collection of all function definitions of a type of product.
  • the object model file may be an object model file initially defined by the device; for example, it may be an object model file initially defined when the device accesses the device management platform for the first time.
  • the object model file can also be an updated object model file of the device; for example, the device update can be a device upgrade, for example, adding new device functions or updating device function versions, or artificially modifying device functions. This is not limited.
  • the attribute information corresponding to each function includes at least one of parameter name, parameter type, control style and verification rule.
  • the parameter name is the name of any attribute of the function.
  • the parameter name of the attribute information corresponding to the face recognition function can be a face recognition switch.
  • Parameter type refers to the data type corresponding to the parameter, for example, numeric type, string type or enumeration type, etc.
  • control style refers to the style displayed by this function, for example, drop-down box, button or radio box, etc.
  • check Rules refer to the validation rules for each attribute of the function.
  • the temperature measurement distance of the temperature measurement function of the face temperature measurement all-in-one machine can be set according to the usage scenario. If the system setting range of the temperature measurement distance is 1 to 3 meters, when the temperature measurement distance is artificially set, you can Automatically check whether the artificially set temperature measurement distance meets the range set by the system.
  • attribute information can be displayed or hidden in linkage.
  • attribute information such as body temperature detection threshold or body temperature detection distance can be displayed; when the body temperature detection function is turned off, the body temperature detection threshold or body temperature detection distance can be hidden and other attribute information.
  • the device is a device that establishes a communication connection with the device management platform.
  • the device may be one or more types of devices, for example, a face recognition access control machine and/or a face temperature measurement all-in-one machine.
  • the function information of the device is the function of the device, for example, for a face recognition access control machine, it has a face recognition function.
  • the attribute information corresponding to the face recognition function may be a face recognition distance, for example, the face recognition distance is 5 meters.
  • the function information of the device can be obtained based on the object model file, and then the device can be managed.
  • the encapsulated object model file when the device is managed based on the encapsulated object model file, the encapsulated object model file can be directly sent to the client, so that the client can
  • the packaged object model file displays the management page of the device, and the content displayed on the management page includes the function information of the device and the attribute information corresponding to each function.
  • the realization of the management of the device may include the following S1021-S1022:
  • the device management platform may first parse it to extract the target data.
  • the packaged object model file is a file in a fixed format, such as a JASON file, it is necessary to parse the file in this format to extract the function information and the corresponding
  • the key-value pair data of the attribute information is the format of (attribute:attribute value), that is, the format of (key:value).
  • the object model file carries object model protocol version information and object model file version information.
  • the object model protocol version information and object model can be File version information, parsing the object model file to extract target data indicating the function information and attribute information corresponding to each function.
  • the object model protocol version information is the version information of the analysis protocol corresponding to the object model file, that is, the object model files corresponding to different versions have different versions of the corresponding analysis protocols.
  • the object model file version information is the version of the object model file.
  • the object model file after the upgrade has different version information from the object model file before the upgrade.
  • the object model file further includes a product identifier, which is used to identify the product type of the device, for example, the product type of the device is a Camera camera or a SensePass Pro face recognition machine.
  • the target data needs to be sent to the client, so that the client can render and display based on the target data.
  • step S1022 when sending the target data to the client, as shown in FIG. 4, the following steps S10221-S10222 may be included:
  • the obtaining instruction refers to an instruction sent by the client to obtain the target data.
  • the device management platform since the device management platform is responsible for storing and analyzing object model files, when the user views the device information through the client, the device management platform will receive the acquisition instruction sent by the client in response to the request operation on the management page.
  • the request operation may be a click operation or a slide operation of the user on the management page, etc., which is not limited herein.
  • the target data of the device indicated by the obtaining instruction is sent to the client for rendering and displaying by the client.
  • FIG. 5 is a flowchart of a second device management method provided by an embodiment of the present disclosure.
  • the device management method may use a processor to invoke computer-readable instructions stored in a memory way to achieve.
  • the device management method provided by the embodiment of the present disclosure can be applied to the client in FIG. 1, including the following S401-S402:
  • S401 Receive an object model file, where the object model file is used to indicate device function information and attribute information corresponding to each function.
  • the client 200 may receive the object model file sent by the device management platform. It can be understood that the client may be a terminal such as a web browser, a computer (PC) client or a mobile phone, which is not limited here.
  • the client may be a terminal such as a web browser, a computer (PC) client or a mobile phone, which is not limited here.
  • the client 200 after receiving the object model file, the client 200 needs to display the management page of the device based on the object model file.
  • FIG. 6 is a schematic diagram of a management page provided by an embodiment of the present disclosure.
  • the device type of the current device is displayed on the management page, for example, the device type of the current device is a SensePass Pro face recognition machine, the device status of the current device is online, and the functions of the current device include Equipment setting function, access setting function, equipment information function, personnel information function and attendance setting function.
  • the function setting corresponding to the device setting function includes: enabling status, mode selection, verification mode, and video broadcasting, etc.
  • step S402 when displaying the management page of the device based on the object model file, as shown in FIG. 7 , the following steps S4021-S4024 may be included:
  • the object model file received by the client may be in a parsed state or in an unresolved state
  • the object model file after receiving the object model file, firstly, the object model file can be The status of the object is judged, and then the object model file is further processed according to the different status.
  • the target data may be directly extracted according to the parsed object model file.
  • the client since the object model file is in an unparsed state, the client first needs to parse the object model file.
  • the packaged form of the packaged object model file is in the form of a JSON (JavaScript Object Notation) file
  • the file in this form needs to be parsed to extract the function information and the corresponding function information of each function.
  • the key-value pair data of attribute information, the format of the key-value pair data is the format of (attribute: attribute value), that is, the format of (key: value).
  • the management page of the device can be displayed; wherein, the specific content of the management page can be Refer to the content described in step S402, which will not be repeated here.
  • step S4024 when displaying the management page of the device based on the target data, as shown in FIG. 8 , the following steps S40241-S40243 may be included:
  • the language used by the user of the client may be different, for example, multiple languages such as Chinese, English, French, or German. Then, in the case of displaying the management page of the device, it is first necessary to determine the locale of the management page to be displayed.
  • the client is a mobile phone, and the system language used by the mobile phone is English.
  • the management page is displayed through the mobile phone, it can be determined that the language environment of the management page to be displayed is English.
  • any object model file for any device corresponds to multiple language versions.
  • the client can determine the data matching the language environment from the target data.
  • the language environment is an English environment
  • the English version of the target data can be determined from the target data.
  • FIG. 9 is a schematic diagram of another management page provided by an embodiment of the present disclosure.
  • the data matching the language environment is target data in English
  • an English version management page can be displayed on the client. That is, the display format of the function information and attribute information displayed on the management page is in English.
  • FIG. 10 is a flowchart of a third device management method provided by an embodiment of the present disclosure. Different from the method in FIG. 5, the device management method further includes the following S403-S404:
  • the modifying operation may be a user's single-click operation, double-click operation, or slide operation on the management page, which is not limited herein.
  • the client can change the attribute information in response to the user's modification operation on the management page, that is, the user can remotely modify the device's Function settings or send remote control instructions to the device.
  • the client needs to send the modified attribute information to the device, so that the device adjusts the corresponding function.
  • the client may first send the changed attribute information to the device management platform for storage, and then the device management platform sends the changed attribute information to the device. That is to say, the client can dynamically load the information of the object model of the device. In this way, without upgrading the device management platform, the client can still access more products, so that the device, the device management platform, and the client's device The function information and the attribute information of the function are consistent.
  • FIG. 11 is a flowchart of a fourth device management method provided by an embodiment of the present disclosure.
  • the device management method may be implemented in a manner in which a processor invokes computer-readable instructions stored in a memory.
  • the device management method provided by the embodiment of the present disclosure can be applied to the device in FIG. 1 , including the following S901-S902:
  • an object model file will be automatically generated according to the function information of the device and the attribute information corresponding to each function.
  • S902. Encapsulate the object model file and send it to a device management platform, so that the device management platform manages the device based on the object model file.
  • the device may encapsulate the object model file in a preset format to make the file more concise and easier to parse and process.
  • the object model file is packaged into a JASON file format.
  • FIG. 12 is a flowchart of a fifth device management method provided by an embodiment of the present disclosure. Different from the method in FIG. 11, the device management method further includes the following S903-S904:
  • the device when the device performs system upgrade or artificially modifies the device function, in response to the modification instruction generated by the modification operation on the device information display interface, according to the modified device function information and function attribute information, the Modify the physical model file to generate an updated physical model file.
  • the updated object model file needs to be packaged and sent to the device management platform, so that the device management platform can update the object model file.
  • FIG. 13 is a schematic flowchart of interaction among a device, a device management apparatus, and a client provided by an embodiment of the present disclosure.
  • FIG. 13 shows the execution sequence of the method steps when the device 10 , the device management platform 100 and the client 200 interact. That is, for the device side, when the device 10 establishes a communication connection with the device management platform 100 for the first time, or after the device 10 communicates with the device management platform 100, and the device 10 performs a device update, the object model file needs to be sent to Device management platform. Then, the device management platform 100 receives the object model file, parses the object model file, extracts the target data, and sends the target data to the client 200 . The client 200 receives the target data and presents based on the target data. In addition, after the attribute information is modified through the management page of the client 200, the modified attribute information needs to be sent to the device, so that the device can perform function adjustment according to the modified attribute information.
  • An embodiment of the present disclosure provides a schematic flowchart of a method for interaction between a device, a device management platform, and a client. As shown in FIG. 14 , the method may include:
  • the device uploads the object model file to the device management platform
  • the equipment management platform saves the object model file
  • the equipment updates the object model status, obtains the updated object model file, and uploads the updated object model file to the equipment management platform;
  • the device management platform saves the updated object model file
  • the client sends a request for the object model file to the device management platform
  • the device management platform responds to the object model file request, and sends the updated object model file to the client;
  • the client performs rendering according to the object model file, obtains the management page of the device, and displays the management page of the device;
  • the client receives an instruction to modify the state of the object model, and responds to the modification instruction, changes the state of the object model, and obtains a modified object model file;
  • the client sends the changed object model file to the device management platform
  • the device management platform saves the changed object model file
  • the device management platform sends the changed object model file to the device
  • the device adjusts functions according to the changed object model file.
  • the device can send the object model file to the client through the management platform, and the client can also send the modified object model state to the device through the management platform after receiving the instruction to modify the state of the object model.
  • the function of the device is changed according to the modified state of the object model; in this way, the consistency of functions between the device, the device management platform and the client is improved.
  • the device can be managed based on the encapsulated object model file, which reduces the degree of coupling between the device and the device management platform and improves the flexibility of device management.
  • the writing order of each step does not mean a strict execution order and constitutes any limitation on the implementation process.
  • the specific execution order of each step should be based on its function and possible
  • the inner logic is OK.
  • the embodiment of the present disclosure also provides an equipment management device corresponding to the equipment management method. Since the problem-solving principle of the device in the embodiment of the present disclosure is similar to the above-mentioned equipment management method in the embodiment of the present disclosure, the implementation of the device You can refer to the implementation of the method, and the repetition will not be repeated.
  • FIG. 15 is a schematic structural diagram of a first device management device provided by an embodiment of the present disclosure.
  • the device management device 1000 includes: a first receiving part 1010 and a management part 1020; wherein,
  • the first receiving part 1010 receives the packaged object model file sent by the device, and the object model file is used to indicate the function information of the device and the attribute information corresponding to each function;
  • the management part 1020 is configured to manage the device based on the packaged object model file.
  • the management part 1020 is further configured to:
  • the management part 1020 is further configured to:
  • Analyzing the packaged object model file extracting target data indicating the function information and attribute information corresponding to each function;
  • the object model file includes an object model file defined by the device initialization or an object model file after the device is updated.
  • the management part 1020 is further configured to:
  • the object model file is parsed to extract the function information and the target data of the attribute information corresponding to each function.
  • the management part 1020 is further configured to:
  • the acquisition instruction is an instruction generated by the client in response to a request operation for the management page;
  • the target data is sent to the client.
  • the attribute information includes at least one of parameter name, parameter type, control style and validation rule.
  • FIG. 16 is a schematic structural diagram of a second device management device provided by an embodiment of the present disclosure.
  • the device management device 2000 includes: a second receiving part 2010 and a display part 2020; wherein,
  • the second receiving part 2010 is configured to receive an object model file, the object model file is used to indicate the function information of the device and the attribute information corresponding to each function;
  • the presentation part 2020 is configured to display the management page of the device based on the object model file, and the content displayed on the management page includes function information of the device and attribute information corresponding to each function.
  • the display part 2020 is further configured to:
  • a management page of the device is displayed, and the content displayed on the management page includes function information of the device and attribute information corresponding to each function.
  • the display part 2020 is further configured to:
  • a management page of the device is displayed, and the content displayed on the management page includes function information of the device and attribute information corresponding to each function.
  • the display part 2020 is further configured to:
  • a management page of the locale is displayed.
  • the device further includes a first modifying part 2030, and the first modifying part 2030 is configured to:
  • FIG. 17 is a schematic structural diagram of a third equipment management apparatus provided by an embodiment of the present disclosure.
  • the equipment management apparatus 3000 includes: a generating part 3010 and a sending part 3020; wherein,
  • the generating part 3010 is configured to generate an object model file based on the function information of the device and the attribute information corresponding to each function;
  • the sending part 3020 is configured to encapsulate the object model file and send it to the device management platform, so that the device management platform manages the device based on the object model file.
  • the device includes a device information display interface; the apparatus further includes a second modification part 3030, and the second modification part 3030 is configured to:
  • the sending part 3020 is also configured to:
  • the updated object model file is packaged and then sent to the device management platform.
  • a "part" may be a part of a circuit, a part of a processor, a part of a program or software, etc., of course it may also be a unit, a module or a non-modular one.
  • an embodiment of the present disclosure also provides an electronic device.
  • FIG. 18 it is a schematic structural diagram of an electronic device 4000 provided by an embodiment of the present disclosure, including a processor 4001 , a memory 4002 , and a bus 4003 .
  • the memory 4002 is used to store execution instructions, including the memory 40021 and the external memory 40022; the memory 40021 here is also called the internal memory, and is used to temporarily store the operation data in the processor 4001 and the data exchanged with the external memory 40022 such as the hard disk,
  • the processor 4001 exchanges data with the external memory 40022 through the memory 40021 .
  • the memory 4002 is specifically used to store application program codes executing the solution of the present application, and the execution is controlled by the processor 4001 . That is, when the electronic device 4000 is running, the processor 4001 communicates with the memory 4002 through the bus 4003, so that the processor 4001 executes the application program code stored in the memory 4002, and then executes the method in any one of the foregoing embodiments.
  • the processor 4001 may be an integrated circuit chip with signal processing capabilities.
  • the above-mentioned processor can be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC) , field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • memory 4002 can be, but not limited to, random access memory (Random Access Memory, RAM), read-only memory (Read Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), can Erasable Programmable Read-Only Memory (EPROM), Electric Erasable Programmable Read-Only Memory (EEPROM), etc.
  • RAM Random Access Memory
  • ROM read-only memory
  • PROM programmable read-only memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electric Erasable Programmable Read-Only Memory
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 800 .
  • the electronic device 800 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components.
  • the illustrated components can be realized in hardware, software or a combination of software and hardware.
  • Embodiments of the present disclosure further provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the device management method described in the foregoing method embodiments are executed.
  • the storage medium may be a volatile or non-volatile computer-readable storage medium.
  • Embodiments of the present disclosure also provide a computer program product, the computer program product carries a program code, and the instructions included in the program code can be used to execute the steps of the device management method described in the above method embodiment, for details, please refer to the above method The embodiment will not be repeated here.
  • the above-mentioned computer program product may be specifically implemented by means of hardware, software or a combination thereof.
  • the computer program product is embodied as a computer storage medium, and in another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (Software Development Kit, SDK), etc. wait.
  • a software development kit Software Development Kit, SDK
  • the disclosed system, terminal and method may be implemented in other ways.
  • the terminal embodiments described above are only illustrative.
  • the division of the units is only a logical function division.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some communication interfaces, or the indirect coupling or communication connection of units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium executable by a processor.
  • the technical solution of the present disclosure is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make an electronic device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in various embodiments of the present disclosure.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .
  • the data interaction and update of the device, the device management platform, and the client are realized based on the object model file.
  • the object model file of the device is sent to the device management platform without rewriting
  • the corresponding logic program of the device management platform reduces the degree of coupling between the device and the device management platform, and improves the flexibility of device management.

Abstract

L'invention concerne un procédé et un appareil de gestion de dispositif, un dispositif électronique et un support de stockage, qui sont appliqués à une plateforme de gestion de dispositif. Le procédé comprend les étapes consistant à : recevoir un fichier de modèle d'objet encapsulé, qui est envoyé par un dispositif, le fichier de modèle d'objet étant utilisé pour indiquer des informations de fonction du dispositif et des informations d'attribut correspondant à chaque fonction ; et à gérer le dispositif sur la base du fichier de modèle d'objet encapsulé.
PCT/CN2022/133254 2021-11-19 2022-11-21 Procédé et appareil de gestion de dispositif, dispositif électronique, support de stockage et produit-programme WO2023088469A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111408125.4A CN114036113A (zh) 2021-11-19 2021-11-19 设备管理方法、装置、电子设备及存储介质
CN202111408125.4 2021-11-19

Publications (1)

Publication Number Publication Date
WO2023088469A1 true WO2023088469A1 (fr) 2023-05-25

Family

ID=80145451

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/133254 WO2023088469A1 (fr) 2021-11-19 2022-11-21 Procédé et appareil de gestion de dispositif, dispositif électronique, support de stockage et produit-programme

Country Status (2)

Country Link
CN (1) CN114036113A (fr)
WO (1) WO2023088469A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114036113A (zh) * 2021-11-19 2022-02-11 深圳市商汤科技有限公司 设备管理方法、装置、电子设备及存储介质
CN114936062B (zh) * 2021-12-09 2024-01-30 腾讯科技（深圳）有限公司 一种设备自动调试的方法、装置、设备、系统及存储介质
CN116028580B (zh) * 2022-08-31 2023-10-20 荣耀终端有限公司 物模型管理方法、设备及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019143412A1 (fr) * 2018-01-19 2019-07-25 Umajin Inc. Kit de serveur configurable
CN111147586A (zh) * 2019-12-27 2020-05-12 腾讯科技（深圳）有限公司 设备端控制方法、装置和会议系统
CN111176528A (zh) * 2019-12-31 2020-05-19 欧普照明股份有限公司 一种控制方法、装置、电子设备及计算机可读存储介质
CN112994958A (zh) * 2021-05-17 2021-06-18 新华三技术有限公司 一种网络管理系统、方法、装置及电子设备
CN113572799A (zh) * 2020-04-29 2021-10-29 北京金山云网络技术有限公司 设备接入控制平台的方法、装置和服务器
CN114036113A (zh) * 2021-11-19 2022-02-11 深圳市商汤科技有限公司 设备管理方法、装置、电子设备及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019143412A1 (fr) * 2018-01-19 2019-07-25 Umajin Inc. Kit de serveur configurable
CN111147586A (zh) * 2019-12-27 2020-05-12 腾讯科技（深圳）有限公司 设备端控制方法、装置和会议系统
CN111176528A (zh) * 2019-12-31 2020-05-19 欧普照明股份有限公司 一种控制方法、装置、电子设备及计算机可读存储介质
CN113572799A (zh) * 2020-04-29 2021-10-29 北京金山云网络技术有限公司 设备接入控制平台的方法、装置和服务器
CN112994958A (zh) * 2021-05-17 2021-06-18 新华三技术有限公司 一种网络管理系统、方法、装置及电子设备
CN114036113A (zh) * 2021-11-19 2022-02-11 深圳市商汤科技有限公司 设备管理方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN114036113A (zh) 2022-02-11

Similar Documents

Publication Publication Date Title
WO2023088469A1 (fr) Procédé et appareil de gestion de dispositif, dispositif électronique, support de stockage et produit-programme
US10868866B2 (en) Cloud storage methods and systems
JP6755954B2 (ja) インターフェースデータの提示方法及び装置
US10545749B2 (en) System for cloud computing using web components
US10643023B2 (en) Programmatic native rendering of structured content
US9015657B2 (en) Systems and methods for developing and delivering platform adaptive web and native application content
US9355081B2 (en) Transforming HTML forms into mobile native forms
US20170010870A1 (en) Optimized retrieval of custom string resources
JP7358698B2 (ja) 語義表現モデルの訓練方法、装置、デバイス及び記憶媒体
JP6036100B2 (ja) ウェブ・ブラウザー画面の段階的な視覚的比較
TWI590157B (zh) 自客戶側應用程式之傳送資料壓縮序列化
US11842142B2 (en) Systems and methods for co-browsing
US10896036B2 (en) Auto mapping recommender
US20170289293A1 (en) Manipulation of browser dom on server
CN111651405A (zh) 配置文件管理方法、装置、设备及存储介质
US20160072927A1 (en) Odata enabled mobile software applications
US20210034357A1 (en) Software versioning for network connected devices
CN111357241A (zh) 使用自动化通用连接器封装将云应用程序集成到云服务代理平台中的系统和方法
US20150169533A1 (en) Server-less HTML Templates
JP4846832B2 (ja) Ｗｅｂページの表示方法、計算機システム及びプログラム
US20210303652A1 (en) Optimizing annotation reconciliation transactions on unstructured text content updates
WO2021129812A1 (fr) Procédé et système d'exécution d'application d'intelligence artificielle, et dispositif
CN113721910A (zh) 界面代码生成方法、装置、电子设备和计算机可读介质
CN113050921A (zh) 一种网页转换方法、装置、存储介质和计算机设备
US9680967B2 (en) Method of using application, gateway using the method, terminal using the method, and terminal system using the method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22894998

Country of ref document: EP

Kind code of ref document: A1