CN117938857B - Synchronous management method and system for object model - Google Patents
Synchronous management method and system for object model Download PDFInfo
- Publication number
- CN117938857B CN117938857B CN202410325664.9A CN202410325664A CN117938857B CN 117938857 B CN117938857 B CN 117938857B CN 202410325664 A CN202410325664 A CN 202410325664A CN 117938857 B CN117938857 B CN 117938857B
- Authority
- CN
- China
- Prior art keywords
- object model
- terminal
- public cloud
- cloud
- encrypted
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 20
- 230000001360 synchronised effect Effects 0.000 title claims abstract description 17
- 238000000034 method Methods 0.000 claims abstract description 23
- 230000003993 interaction Effects 0.000 claims abstract description 11
- 238000012827 research and development Methods 0.000 claims description 15
- 238000005192 partition Methods 0.000 claims description 3
- 238000012795 verification Methods 0.000 claims description 3
- 238000011161 development Methods 0.000 description 32
- 230000006870 function Effects 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000003801 milling Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
Classifications
-
- 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/10—Protocols in which an application is distributed across nodes in the network
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- 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/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Computing Systems (AREA)
- Strategic Management (AREA)
- Computer Security & Cryptography (AREA)
- Tourism & Hospitality (AREA)
- Game Theory and Decision Science (AREA)
- Operations Research (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a synchronous management method and a synchronous management system for object models, wherein the method comprises the following steps: the public cloud acquires an encrypted to-be-checked object model uploaded by the first terminal; the public cloud determines a first object model list corresponding to the customized item according to interaction between the public cloud and the second terminal; the public cloud responds to a synchronization request sent by a third terminal, downloads and sends an encrypted target object model conforming to the synchronization request to the third terminal according to the first object model list; and the third terminal uploads the encrypted target object model to the private cloud. The application reduces the loss risk of enterprise assets.
Description
Technical Field
The application relates to the field of data processing, in particular to a synchronous management method and system of an object model.
Background
The object model is a data model defined by an internet of things (Internet of Things, abbreviated as IoT) platform for products, is an abstract of physical things of the physical world, and is a digital model for the digital world after digital description. Based on the common abstract feature, the object model may allow applications to no longer target individual product devices, but instead employ the same processing logic for the same class of devices. The object model mainly comprises four parts of an acquisition driving program, an acquisition attribute, a calculation attribute and an equipment state expression of the hardware acquisition gateway.
Some suppliers deposit hundreds of standard object models according to equipment brands, industry types and the like of different clients, different object models are needed to be selected on an IOT management platform according to different production equipment model types of the clients, and an object model library on the IOT management platform is needed to be uploaded and maintained by staff, but for the object model library maintenance of privately owned projects, embedded development engineers and on-site implementation engineers are maintained together, and part of implementation engineers can store the object models, so that the object models of the clients are easy to leak and are more confusing to manage. In addition, the proprietary object models can not be synchronously stored through public cloud, some object models customized by the project can be repeatedly created by different manufacturers but the object models of the same equipment, and the development and maintenance cost is high.
Disclosure of Invention
The application provides a synchronous management method and system of a physical model, namely the technical problems.
In a first aspect, the present application provides a method for synchronously managing object models, including the steps of:
the public cloud acquires an encrypted to-be-checked object model uploaded by the first terminal;
The public cloud determines a first object model list corresponding to the customized item according to interaction between the public cloud and the second terminal;
the public cloud responds to a synchronization request sent by a third terminal, downloads and sends an encrypted target object model conforming to the synchronization request to the third terminal according to the first object model list;
And the third terminal uploads the encrypted target object model to the private cloud.
In some embodiments, before the public cloud obtains the encrypted to-be-checked object model uploaded by the first terminal, the method includes:
The public cloud acquires input information sent by a fourth terminal; the input information comprises an equipment list corresponding to the customization project, an identity of a private cloud and a second object model list, wherein the second object model list comprises related information of a plurality of object models, and the object models comprise an existing object model and a new object model;
The public cloud creates corresponding research and development tasks according to the new object model;
And the public cloud sends the equipment list, the identity mark and the research and development task to the first terminal.
In some embodiments, the public cloud obtaining the encrypted to-be-checked object model uploaded by the first terminal includes:
the first terminal receives the research and development task and logs in an object model system deployed on the first terminal according to the research and development task so as to create the new object model on the object model system;
The first terminal encrypts the new object model according to a first preset encryption algorithm and a first preset secret key to obtain the encrypted object model to be checked;
And the first terminal sends the encrypted to-be-checked object model to the public cloud.
In some embodiments, the public cloud determining a first object model inventory corresponding to the customized item from interactions between itself and the second terminal includes:
The second terminal generates and sends selection information to the public cloud;
and the public cloud modifies object models in the second object model list according to the selection information to obtain the first object model list.
In some embodiments, further comprising:
The public cloud partitions the customization project into a plurality of subtasks.
In some embodiments, the first object model list includes a serial number and a storage address of an object model, and the downloading and transmitting, by the public cloud, the encrypted object model according to the first object model list and in accordance with the synchronization request to the third terminal in response to the synchronization request sent by the third terminal includes:
When the third terminal is disconnected with the private cloud and the input account information passes verification, the third terminal establishes connection with the public cloud, and generates and sends the synchronization request to the public cloud according to the research and development task;
The public cloud searches a storage address of the matched object model from the first object model list according to the synchronous request;
the public cloud invokes a corresponding target object model according to the storage address;
the public cloud encrypts the target object model according to a second preset encryption algorithm and a second preset secret key to obtain the encrypted target object model;
and the public cloud sends the encrypted object model to the third terminal.
In some embodiments, the uploading, by the third terminal, the encrypted object model to the private cloud includes:
the third terminal is disconnected with the public cloud and is connected with the private cloud corresponding to the customization project;
and the third terminal uploads the encrypted target object model to the private cloud.
In some embodiments, further comprising:
the third terminal receives feedback information sent by the private cloud;
the third terminal is disconnected with the private cloud and is connected with the public cloud, and the third terminal sends the feedback information to the public cloud.
In some embodiments, further comprising:
And after the third terminal determines that the third terminal is disconnected with the private cloud, formatting the third terminal.
In a second aspect, the present application further provides a synchronization management system of an object model, including: public cloud, private cloud, first terminal, second terminal and third terminal;
the public cloud is used for acquiring the encrypted to-be-checked object model uploaded by the first terminal;
the public cloud is further used for determining a first object model list corresponding to the customized item according to interaction between the public cloud and the second terminal;
the public cloud is further used for responding to a synchronization request sent by a third terminal, downloading and sending an encrypted target object model conforming to the synchronization request to the third terminal according to the first object model list;
and the third terminal is used for uploading the encrypted target object model to the private cloud.
According to the synchronous management method and system for the object model, the original log file is collected according to the target access address by acquiring the target access address corresponding to the acquisition task. And matching the original log file with a preset screening condition, and extracting equipment parameter data from the original log file according to a preset extraction mode. The preset extraction mode comprises any one or more of value taking, counting and four arithmetic operations. All object models are maintained on the IOT system of the public cloud, and an implementation engineer cannot store the object models and cannot easily leak the object models. The newly developed or specific equipment object model is created and stored on public cloud, other clients can conveniently reuse the newly developed or specific equipment object model after encountering the same equipment, repeated workload of development is reduced, development efficiency is improved, and development and maintenance costs are reduced. The localized customization project uses which object models, and the public cloud has flow records, so that the problems can be rapidly positioned and traced. Since the object model is also an asset, if it is not managed and can be copied and used at will, the loss of the enterprise asset can be caused. According to the method, only the object model in the first object model list passing the auditing can be encrypted and uploaded to the public cloud, and the auditing flow is increased to enable the export of the object control model, so that the loss risk of enterprise assets is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a method for synchronously managing object models according to an embodiment of the present application;
Fig. 2 is a schematic structural diagram of a synchronous management system of an object model according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to fall within the scope of the application.
In describing embodiments of the present application, it should be understood that the terms "first," "second," and "second" are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or number of features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more of the described features. In the description of the embodiments of the present application, the meaning of "plurality" is two or more, unless explicitly defined otherwise.
The following description is presented to enable any person skilled in the art to make and use the application. In the following description, details are set forth for purposes of explanation. It will be apparent to one of ordinary skill in the art that the present application may be practiced without these specific details. In other instances, well-known processes have not been described in detail in order to avoid unnecessarily obscuring the description of the embodiments of the application. Thus, the present application is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
Referring to fig. 1 and fig. 2, fig. 1 is a flow chart of a method for synchronously managing object models according to an embodiment of the present application. Fig. 2 is a schematic structural diagram of a synchronous management system of an object model according to an embodiment of the present application. It should be noted that although a logical order is shown in the flowchart shown in fig. 1, in some cases, the steps shown or described may be performed in an order different from that shown in the figures. As shown in fig. 1, the method for synchronously managing object models includes the steps of:
s100, the public cloud 100 acquires an encrypted to-be-checked object model uploaded by the first terminal 200;
S200, the public cloud 100 determines a first object model list corresponding to a customized item according to interaction between the public cloud 100 and the second terminal 300;
S300, the public cloud 100 responds to a synchronization request sent by a third terminal 400, downloads and sends an encrypted object model conforming to the synchronization request to the third terminal 400 according to the first object model list;
And S400, uploading the encrypted target object model to the private cloud 500 by the third terminal 400.
Specifically, the first terminal 200 is generally a terminal device used by a development engineer on a provider side (hereinafter, the embodiment is simply referred to as a service side for brevity of description) that provides the object model service, the second terminal 300 is generally a terminal device used by an auditor on the service side, and the third terminal 400 is generally a terminal device used by an implementation engineer on the service side.
Private cloud 500 is built for use solely by a particular customer, thus providing the most effective control over data, security, and quality of service. This particular customer owns the infrastructure and can control the manner in which cloud applications are deployed on this infrastructure. Private cloud 500 may be deployed within a firewall of an enterprise data center, or they may be deployed at a secure hosting site, with the core attribute of private cloud 500 being a proprietary resource. Public cloud 100 is a cloud deployment model controlled by a third party's cloud service provider for cloud service users and resources.
The encrypted to-be-inspected object model comprises the encrypted to-be-inspected object model, and the development engineer can firstly compress and package the plurality of to-be-inspected object models by using the first terminal 200, and encrypt the compressed and packaged plurality of to-be-inspected object models by using a first preset encryption algorithm and a first preset secret key. Of course, the plurality of object models to be inspected may be encrypted by directly using a first preset encryption algorithm and a first preset key to obtain a plurality of encrypted object models to be inspected, the plurality of object models to be inspected may be directly encrypted by directly using a first preset encryption algorithm and a plurality of first preset keys to obtain a plurality of encrypted object models to be inspected, or even the plurality of object models to be inspected may be directly encrypted by directly using a plurality of first preset encryption algorithms and a plurality of first preset keys to obtain a plurality of encrypted object models to be inspected, and then the first terminal 200 uploads the encrypted object models to be inspected to the public cloud 100.
It should be noted that, the first preset key may be generated by the public cloud 100 platform, and may be designed to correspond to one or more first preset keys according to a development engineer, or may correspond to one or more first preset keys by one first terminal 200.
After the public cloud 100 acquires the encrypted object model to be audited, which is transmitted by the development engineer through the first terminal 200, the auditor uses the second terminal 300 to perform information interaction with the public cloud 100, the auditor confirms whether the first object model list is matched with the customization project, if so, the first object model list can be uploaded to the public cloud 100, so that when the implementation engineer carries the third terminal 400 to the site of the client side, the implementation engineer uses the third terminal 400 to generate a login connection public cloud 100, the implementation engineer uses the third terminal 400 to generate and transmit a synchronization request corresponding to the customization project to the public cloud 100, so that the third terminal 400 can download the encrypted object model conforming to the synchronization request from the public cloud 100 according to the first object model list passing the audit, and then the third terminal 400 transmits the downloaded encrypted object model to the private cloud 500, and thus the private cloud 500 synchronizes the object model used by the same customization project, and thus, all the implementation engineers can not maintain the customization project on the third terminal 100, and the system can not directly maintain the customization project.
In some embodiments, before the public cloud 100 obtains the encrypted to-be-checked object model uploaded by the first terminal 200, the method includes:
the public cloud 100 obtains input information sent by the fourth terminal 600; the input information includes a device list corresponding to the customization project, an identity of the private cloud 500, and a second object model list, where the second object model list includes related information of a plurality of object models, and the plurality of object models includes an existing object model and a new object model;
the public cloud 100 creates corresponding research and development tasks according to the new object model;
the public cloud 100 sends the device list, the identity and the development task to the first terminal 200.
Specifically, the fourth terminal 600 is generally a product manager on the server side or a terminal device used by a project manager, when a contract is signed between the client side and the server side, and when a service side provides project support for the client side, that is, a new project is developed, the server side project manager uses the fourth terminal 600 to log in the public cloud 100 system to create a custom task, that is, the project manager uses the fourth terminal 600 to input or input a device list (including device brands and device models corresponding to a plurality of devices in the scope of the custom project) in an input box corresponding to the public cloud 100 system, device identification codes indicating device identities, etc.), the identity of the private cloud 500 for waiting for synchronization of object model information can be a MAC address, an IP address, HTTP, connection parameters (ports and user name passwords) of an MQTT interface, etc., the project manager uses the fourth terminal 600 to sign up or select a model of a current custom project to be used as a model to be checked to obtain a second model list, wherein the model to be checked includes the model of the current custom model (that is, a corresponding model is created by a user is applied to the first terminal 200 and a corresponding to a new model of the current custom model, and a corresponding development model is created by the user, and a corresponding to the first model is created by the terminal 200, and the current development model is created by the user is applied to the corresponding to the custom model is created by the user model.
For example, it is determined whether an existing object model in the object model database of public cloud 100 is capable of supporting all brand models of the device inventory in the customization project. For example, if there is an object model a in the object model database of the public cloud 100, which can adapt to the X, Y type of device in the device list, but does not support the Z type of device in the device list, then an object model B is developed to adapt to the Z type of device, so that the object model a is an existing object model, and the object model B is a new object model to be developed.
In some embodiments, the obtaining, by the public cloud 100, the encrypted to-be-checked object model uploaded by the first terminal 200 includes:
The first terminal 200 receives the research and development task and logs in to an object model system deployed on the first terminal 200 according to the research and development task to create the new object model on the object model system;
the first terminal 200 encrypts the new object model according to a first preset encryption algorithm and a first preset secret key to obtain the encrypted object model to be checked;
the first terminal 200 sends the encrypted to-be-checked object model to the public cloud 100.
Specifically, the object model is generally described by an english character string, and the format adopted by the equipment object model may be JSON, XML or custom format.
The development engineer may acquire image data of a large number of target objects, that is, devices that need to create object models, such as intelligent devices including air conditioners, televisions, refrigerators, and processing devices including milling machines and lathes on a production line. The first terminal 200 obtains basic information of the target object by performing image recognition on the image data, wherein the basic information includes, but is not limited to, any one or more of types, brands and models, and of course, the basic information may also include other information of the object to be created, and a recognition result may be set according to actual requirements. Then, the first terminal 200 extracts configuration information from the object database according to the basic information, and finally creates a new object model corresponding to the target object according to the configuration information object model. On the one hand, the object model can be automatically created by utilizing the image data in an image recognition mode, so that the object model is prevented from being created by adopting a code writing or manual dragging component, the development workload of development engineers is reduced, and the object model is intelligently created with high efficiency and low cost; on the other hand, since manual operation is not required, when there are a large number of object models to be created, the object models can be created automatically by mass image creation, and the efficiency of creating the object models can be greatly improved.
Of course, the first terminal 200 is pre-deployed with an object model system, and the development engineer may also log in to the object model system using the first terminal 200 to first create a blank object model on the object model system. Wherein the object model system refers to a third party application that provides object model creation services. Wherein, the blank model refers to the object model without description of functions. After creating the blank model, the first terminal 200 displays an attribute configuration parameter list to the development engineer, where at least one attribute configuration parameter is recorded in the attribute configuration parameter list, and each attribute configuration parameter corresponds to a function of the device. One attribute configuration parameter corresponds to a function that can be realized by the device, the attribute configuration parameter can be described by an english character string, and it can be in JSON, XML or custom format, etc., each attribute configuration parameter has a corresponding name, and the name briefly describes the function corresponding to the attribute configuration parameter. It is understood that object models are typically composed of at least one attribute configuration parameter. The attribute configuration parameters are uploaded and configured by a plurality of development engineers with registered account information in the object model system, namely, different development engineers comb at least one function according to a service scene and create attribute configuration parameters, and each attribute configuration parameter corresponds to one function. When the development engineer uses the first terminal 200, the object model system can be accessed to acquire and view each attribute configuration parameter for selection by the development engineer. The first terminal 200 acquires a selection operation of the development engineer for selecting at least one attribute configuration parameter from the attribute configuration parameter list. When the first terminal 200 detects that at least one attribute configuration parameter in the attribute configuration parameter list receives a setting operation (such as a click operation, a drag operation, etc.), it determines that a selection operation is acquired. The object model system deployed on the first terminal 200 responds to the selection operation to add the selected attribute configuration parameters to the blank object model to complete the creation of the object model. After the attribute configuration parameters required by the development engineer are added to the blank model, the first terminal 200 issues an instruction to complete creation. The first terminal 200 confirms that the equipment object model is created according to the instruction, and then the equipment object model can be used in the internet of things cloud platform.
After the first terminal 200 creates a new object model in the above manner, the first terminal 200 encrypts the new object model according to the first preset encryption algorithm and the first preset key to obtain the encrypted object model to be checked, and then the first action uploads the encrypted object model to be checked to the public cloud 100 for updating the object model database.
In some embodiments, the public cloud 100 determining a first object model list corresponding to a customized item according to interactions between itself and the second terminal 300 includes:
The second terminal 300 generates and transmits selection information to the public cloud 100;
and the public cloud 100 modifies object models in the second object model list according to the selection information to obtain the first object model list.
Specifically, the second terminal 300 is used by the auditor on the server side to check the second model list issued by the fourth terminal 600, and the auditor manually checks whether the object model in the second model list checked by the project manager is selected more, missed or misplaced, i.e. judges whether the object model in the second model list is matched with the equipment category in the customized project. Of course, the function of VLOOKUP, such as excel, of the second terminal 300 may also be automatically checked to verify whether the object model in the second object model list matches the device type corresponding to the device category in the custom item.
In summary, the second terminal 300 generates selection information according to the selection operation of the auditor, and the second terminal 300 sends the selection information to the public cloud 100, and the public cloud 100 selects information to modify the object model in the second object model list to obtain the first object model list. If the selection is missed, adding the missed object model to the second object model list according to the selection operation of the second terminal 300 to obtain a first object model list, if the selection is repeated, deleting the object model selected by the second terminal 300 in the second object model list to obtain a first object model list, and if the selection is wrong, deleting the wrong object model in the second object model list and adding the correct object model to obtain the first object model list.
In some embodiments, further comprising:
the public cloud 100 partitions the customization entries into a plurality of subtasks.
Specifically, public cloud 100 may divide the customization project into a plurality of subtasks, each part of the subtasks includes maintenance of at least one object model to be audited, part of the subtasks includes creation requirements of a new object model, part of the subtasks includes update or upgrade requirements of an existing object model, public cloud 100 may pre-store the type of art of the existing development engineer, divide the customization task according to the type of art of the existing development engineer, and assign the subtasks to appropriate development engineers.
In some embodiments, the first object model list includes a serial number and a storage address of an object model, and the public cloud 100, in response to a synchronization request sent by the third terminal 400, downloads and sends an encrypted object model that meets the synchronization request to the third terminal 400 according to the first object model list, including:
When the third terminal 400 is disconnected from the private cloud 500 and the input account information passes the verification, the third terminal 400 establishes a connection with the public cloud 100, and generates and sends the synchronization request to the public cloud 100 according to the development task;
The public cloud 100 searches a storage address of the matched object model from the first object model list according to the synchronization request;
the public cloud 100 invokes a corresponding target object model according to the storage address;
The public cloud 100 encrypts the object model according to a second preset encryption algorithm and a second preset key to obtain the encrypted object model;
The public cloud 100 sends the encrypted object model to the third terminal 400.
Specifically, before the implementation engineer logs in the public cloud 100 according to personal account information by using the third terminal 400, the third terminal 400 firstly queries Ping information of the third terminal 400, judges whether the third terminal 400 and the private cloud 500 are in a connection state according to the Ping information, if so, controls the third terminal 400 to disconnect itself from the private cloud 500, if so, controls itself to establish connection with the public cloud 100, uses the third terminal 400 to select development tasks associated with or governed by the implementation engineer, the third terminal 400 generates a corresponding synchronization request according to the development tasks attributed to the third terminal 400, the third terminal 400 sends the generated synchronization request to the public cloud 100, the public cloud 100 queries a first object model list according to a serial number of an object model included in the synchronization request after receiving the synchronization request sent by the third terminal 400, can determine a storage address of the object model to be downloaded, and then the public cloud 100 reads a target object model corresponding to the synchronization request according to the searched storage address, the public cloud 100 uses a second preset encryption algorithm and a second preset encryption target object model to encrypt the target object model, and then encrypts the target object model to the third terminal 400, and encrypts the target object model by the third terminal 400.
It should be noted that, the second preset key may be generated by the public cloud 100 platform, and may be designed to correspond to one or more second preset keys according to an item of the private cloud 500, or may correspond to one or more second preset keys by an implementation engineer, or correspond to one or more second preset keys by a synchronization device, that is, the third terminal 400.
In some embodiments, the uploading the encrypted object model to the private cloud 500 by the third terminal 400 includes:
The third terminal 400 disconnects from the public cloud 100 and establishes a connection with the private cloud 500 corresponding to the customization project;
the third terminal 400 uploads the encrypted object model to the private cloud 500.
Specifically, after receiving the encrypted target object model sent by the public cloud 100 and completing the synchronization operation of the target object model, the third terminal 400 disconnects itself from the public cloud, then, the third terminal 400 searches for the corresponding private cloud 500 according to the identity of the private cloud 500 in the above embodiment, so that the third terminal 400 establishes connection with the private cloud 500 corresponding to the current customization project according to the identity, and then, the third terminal 400 sends the encrypted target object model to the private cloud 500 to realize synchronization of the encrypted target object model to the private cloud 500.
In the embodiment of the present application, as long as the third terminal 400 can access the network of the private cloud 500, that is, the third terminal 400 successfully establishes a connection with the private cloud 500, the third terminal 400 can start the synchronization process of the encrypted object model. Of course, after the synchronization is completed, the implementation engineer may log into the IOT system of the private cloud 500 using the third terminal 400 to check whether the synchronization is successful. The synchronization operation may be repeated if the synchronization is unsuccessful, whereas the third terminal 400 may disconnect the private cloud 500 if the synchronization is successful.
In some embodiments, further comprising:
the third terminal 400 receives feedback information sent by the private cloud 500;
The third terminal 400 disconnects from the private cloud 500 and establishes a connection with the public cloud 100, and the third terminal 400 sends the feedback information to the public cloud.
Specifically, when the localized customization is allowed, after the customization is implemented, the private cloud 500 may send feedback information of the customization to the third terminal 400, where the feedback information includes implementation results, binding relationships, point table configuration and other information corresponding to the customization, and then the third terminal 400 synchronizes the feedback information to the public cloud 100 for archiving. In this way, if a problem occurs in the private cloud 500 of the customer site, the third terminal 400 may call the archive file corresponding to the private cloud 500 in the public cloud 100 to quickly restore. The point table refers to a data dictionary that needs to be collected by the third terminal 400 at the client side, and the point table includes address information of internal storage parameters of the device, which is generally configured by a staff at the client side.
In some embodiments, further comprising:
After determining that the third terminal 400 is disconnected from the private cloud 500, the third terminal performs formatting processing.
Specifically, the information security of a part of the client side is strict, and after the third terminal 400 accesses the intranet (i.e. establishes a connection with the private cloud 500), formatting is required before accessing the public network (i.e. establishes a connection with the public cloud 100) again. The formatting process includes performing data emptying on the third terminal 400, and is generally performed by a staff on the client side to delete all contents of the emptied hard disk and the U disk.
All object models of the application are maintained on the IOT system of the public cloud 100, and an implementation engineer cannot save the object models and is not easy to leak. The newly developed or specific equipment object model is created and stored on public cloud 100, other clients can conveniently reuse the newly developed or specific equipment object model after encountering the same equipment, the repeated workload of development is reduced, the development efficiency is improved, and the development and maintenance cost is reduced. The localized customization project uses which object models, and the public cloud 100 has flow records, so that the problems can be rapidly positioned and traced. Since the object model is also an asset, if it is not managed and can be copied and used at will, the loss of the enterprise asset can be caused. According to the application, only the object model in the first object model list passing the auditing can be encrypted and uploaded to the public cloud 100, and the auditing flow is added to enable the export of the object control model, so that the loss risk of enterprise assets is reduced.
In a second aspect, the present application further provides a synchronization management system of an object model, including: public cloud 100, private cloud 500, first terminal 200, second terminal 300, and third terminal 400;
the public cloud 100 is configured to obtain an encrypted to-be-checked object model uploaded by the first terminal 200;
the public cloud 100 is further configured to determine a first object model list corresponding to the customized item according to interaction between itself and the second terminal 300;
The public cloud 100 is further configured to respond to a synchronization request sent by a third terminal 400, download and send an encrypted object model conforming to the synchronization request to the third terminal 400 according to the first object model list;
The third terminal 400 is configured to upload the encrypted object model to the private cloud 500.
In the specific implementation, each unit may be implemented as an independent entity, or may be combined arbitrarily and implemented as the same entity or a plurality of entities, and each unit may refer to the foregoing method embodiment to implement processing demonstration of an application program, which is not described herein.
Those of ordinary skill in the art will appreciate that all or a portion of the steps of the various methods of the above embodiments may be performed by instructions, or by instructions controlling associated hardware, which may be stored on a computer-readable storage medium and loaded and executed by a processor to implement the above embodiments of the methods. Wherein the computer-readable storage medium may comprise: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments. It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process and the beneficial effects of the above-described synchronous management system for object model and its corresponding units may refer to the description of the synchronous management method for object model in the above embodiment, which is not repeated herein.
The above description is made in detail on a method and a system for synchronously managing object models provided by the embodiment of the present application, and specific examples are applied to describe the principles and implementations of the present application, and the description of the above embodiments is only used to help understand the method and the core idea of the present application; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in light of the ideas of the present application, the present description should not be construed as limiting the present application.
Claims (9)
1. The synchronous management method of the object model is characterized by comprising the following steps:
The public cloud acquires input information sent by a fourth terminal; the input information comprises an equipment list corresponding to a customized item, an identity of a private cloud and a second object model list, wherein the second object model list comprises related information of a plurality of object models, and the object models comprise an existing object model and a new object model;
The public cloud creates corresponding research and development tasks according to the new object model;
the public cloud sends the equipment list, the identity and the research and development task to a first terminal;
the public cloud acquires an encrypted to-be-checked object model uploaded by the first terminal;
The public cloud determines a first object model list corresponding to the customized item according to interaction between the public cloud and the second terminal;
the public cloud responds to a synchronization request sent by a third terminal, downloads and sends an encrypted target object model conforming to the synchronization request to the third terminal according to the first object model list;
And the third terminal uploads the encrypted target object model to the private cloud.
2. The method for synchronously managing object models according to claim 1, wherein the public cloud obtaining the encrypted to-be-checked object model uploaded by the first terminal comprises:
the first terminal receives the research and development task and logs in an object model system deployed on the first terminal according to the research and development task so as to create the new object model on the object model system;
The first terminal encrypts the new object model according to a first preset encryption algorithm and a first preset secret key to obtain the encrypted object model to be checked;
And the first terminal sends the encrypted to-be-checked object model to the public cloud.
3. The method of claim 2, wherein determining, by the public cloud, a first object model list corresponding to the customized item according to an interaction between the public cloud and the second terminal comprises:
The second terminal generates and sends selection information to the public cloud;
and the public cloud modifies object models in the second object model list according to the selection information to obtain the first object model list.
4. A method of synchronous management of object models according to claim 3, further comprising:
The public cloud partitions the customization project into a plurality of subtasks.
5. The method for synchronously managing object models according to claim 4, wherein the first object model list includes a serial number and a storage address of an object model, the public cloud responding to a synchronization request sent by a third terminal, downloading and sending an encrypted object model conforming to the synchronization request to the third terminal according to the first object model list includes:
When the third terminal is disconnected with the private cloud and the input account information passes verification, the third terminal establishes connection with the public cloud, and generates and sends the synchronization request to the public cloud according to the research and development task;
The public cloud searches a storage address of the matched object model from the first object model list according to the synchronous request;
the public cloud invokes a corresponding target object model according to the storage address;
the public cloud encrypts the target object model according to a second preset encryption algorithm and a second preset secret key to obtain the encrypted target object model;
and the public cloud sends the encrypted object model to the third terminal.
6. The method for synchronously managing object models according to claim 1, wherein the uploading the encrypted object model to the private cloud by the third terminal comprises:
the third terminal is disconnected with the public cloud and is connected with the private cloud corresponding to the customization project;
and the third terminal uploads the encrypted target object model to the private cloud.
7. The method for synchronous management of object models according to claim 1, further comprising:
the third terminal receives feedback information sent by the private cloud;
the third terminal is disconnected with the private cloud and is connected with the public cloud, and the third terminal sends the feedback information to the public cloud.
8. The synchronization management method of an object model according to claim 5 or 7, further comprising:
And after the third terminal determines that the third terminal is disconnected with the private cloud, formatting the third terminal.
9. A synchronous management system for object models, comprising: public cloud, private cloud, first terminal, second terminal, third terminal and fourth terminal;
The public cloud is used for acquiring input information sent by the fourth terminal, creating a corresponding research and development task according to a new object model, and sending an equipment list, an identity mark and the research and development task to the first terminal; the input information comprises an equipment list corresponding to a customized item, an identity of a private cloud and a second object model list, wherein the second object model list comprises related information of a plurality of object models, and the object models comprise an existing object model and a new object model;
the public cloud is further used for acquiring an encrypted to-be-checked object model uploaded by the first terminal;
the public cloud is further used for determining a first object model list corresponding to the customized item according to interaction between the public cloud and the second terminal;
the public cloud is further used for responding to a synchronization request sent by a third terminal, downloading and sending an encrypted target object model conforming to the synchronization request to the third terminal according to the first object model list;
and the third terminal is used for uploading the encrypted target object model to the private cloud.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410325664.9A CN117938857B (en) | 2024-03-21 | 2024-03-21 | Synchronous management method and system for object model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410325664.9A CN117938857B (en) | 2024-03-21 | 2024-03-21 | Synchronous management method and system for object model |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117938857A CN117938857A (en) | 2024-04-26 |
| CN117938857B true CN117938857B (en) | 2024-06-14 |
Family
ID=90756028
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410325664.9A Active CN117938857B (en) | 2024-03-21 | 2024-03-21 | Synchronous management method and system for object model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117938857B (en) |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101794222B1 (en) * | 2013-04-09 | 2017-11-07 | 사이트릭스 시스템스, 인크. | Providing a native desktop using cloud-synchronized data |
| US10867282B2 (en) * | 2015-11-06 | 2020-12-15 | Anguleris Technologies, Llc | Method and system for GPS enabled model and site interaction and collaboration for BIM and other design platforms |
| CN111324905A (en) * | 2020-02-17 | 2020-06-23 | 平安国际智慧城市科技股份有限公司 | Image data labeling method and device, computer equipment and storage medium |
| US11415969B2 (en) * | 2020-09-21 | 2022-08-16 | Rockwell Automation Technologies, Inc. | Connectivity to an industrial information hub |
| CN116781717A (en) * | 2022-03-11 | 2023-09-19 | 南京贝登医疗股份有限公司 | Method and system for synchronizing hybrid cloud data |
| CN115550463A (en) * | 2022-09-16 | 2022-12-30 | 深圳市润腾智慧科技有限公司 | Cross-cloud Internet of things platform data processing method and device and related equipment |
| CN116489170A (en) * | 2023-04-06 | 2023-07-25 | 无锡拓速网络科技有限公司 | Cloud platform-based source data synchronization method, system and medium |
| CN117499465A (en) * | 2023-10-27 | 2024-02-02 | 中信银行股份有限公司 | Cloud platform Internet of things access method and system based on Internet of things configuration |
| CN117579651A (en) * | 2023-11-03 | 2024-02-20 | 北京智芯微电子科技有限公司 | Internet of things system |
-
2024
- 2024-03-21 CN CN202410325664.9A patent/CN117938857B/en active Active
Non-Patent Citations (2)
| Title |
|---|
| 基于阿里云物联网平台的自动气象站设计;黄娇郁;唐海;;湖北农业科学;20200910(第17期);全文 * |
| 工业云平台的建设与应用实践;杨维明;刘爱军;齐建军;黄松波;;中华纸业;20131023(第20期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117938857A (en) | 2024-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101399729B (en) | Management system and method for file download and upload | |
| CN108989066A (en) | device management method and device | |
| KR102080156B1 (en) | Auto Recharge System, Method and Server | |
| CN111596932B (en) | Mirror image file generation method and device and computer readable storage medium | |
| CN111327613B (en) | Distributed service authority control method and device and computer readable storage medium | |
| CN111580833A (en) | Application updating method and system, local management agent device and cloud server | |
| CN113971191A (en) | Data import method and device and computer readable storage medium | |
| CN117938857B (en) | Synchronous management method and system for object model | |
| CN112130864A (en) | Deployment method and deployment device of private cloud platform service software | |
| CN105844171B (en) | Method and device for file synchronization control | |
| WO2024041035A1 (en) | Machine learning model management method and device, model management platform, and storage medium | |
| CN115567596B (en) | Cloud service resource deployment method, device, equipment and storage medium | |
| EP4130982B1 (en) | Network-based solution module deployment platform | |
| CN114675872B (en) | Data processing method, device, equipment and storage medium for application program | |
| US11757976B2 (en) | Unified application management for heterogeneous application delivery | |
| CN113986423A (en) | Bullet frame display method and system, storage medium and terminal equipment | |
| CN112804291B (en) | Remote equipment auditing method, device and system | |
| CN117435215A (en) | Development environment deployment method, system, computer device and storage medium | |
| EP4224808A1 (en) | Device upgrade control method and apparatus, and computer device and storage medium | |
| CN113535328B (en) | Application instance control method, device, equipment and storage medium | |
| CN116684282B (en) | Method and device for initializing newly-added cloud server and computer equipment | |
| US20240176631A1 (en) | Wizard based gateway onboarding to cloud | |
| CN118427159B (en) | Pre-training model file management method, program product, device and medium | |
| CN113127419B (en) | File detection method, device, computer equipment and storage medium | |
| CN112231109B (en) | Buffer resource management system, method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |