Cooperative processing method and system of equipment resources, electronic equipment and storage medium
Through the collaborative processing methods and systems of equipment resources, a collaborative relationship is established, and equipment model construction, data sharing and model sharing are realized, which solves the problem of low equipment management performance in the existing technology, and improves the management performance and resource utilization efficiency of industrial equipment. .
Patent Information
- Application Number
- CN202411111231.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-13
- Publication Date
- 2024-12-10
AI Technical Summary
The existing equipment management operation and maintenance system cannot effectively manage the resources of industrial equipment, resulting in low management performance and lack of openness, which cannot meet the collaborative needs between equipment suppliers and users.
Provide a collaborative processing method and system for device resources. By establishing a collaborative relationship, users can select collaborative users in the collaborative relationship establishment interface to complete collaborative processing of device resources, including device model construction, data sharing and model sharing, and enhance device resources Openness.
The management performance of industrial equipment is improved, the openness of equipment resources is enhanced through collaborative processing, and the collaborative management between equipment suppliers and users is supported, which improves the operation and maintenance efficiency and resource utilization of equipment.
Smart Images

Figure CN119107050A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of device management, and in particular to a method, system, electronic device and storage medium for collaborative processing of device resources. Background Art
[0002] The existing equipment management and operation system is mainly aimed at the internal management of equipment by equipment suppliers or equipment users, and realizes the storage and query of equipment operation and maintenance related data within the enterprise.
[0003] In fact, most management scenarios of industrial equipment require value-added services from equipment suppliers and support from equipment resources of other equipment-using companies. However, the existing equipment management and operation systems can only manage equipment resources within the enterprise. The equipment resources are not open enough, resulting in low management performance of industrial equipment. Summary of the invention
[0004] In view of this, the purpose of the present application is to provide a collaborative processing method, system, electronic device and storage medium for device resources, which can collaboratively process device resources of users with collaborative relationships, thereby managing the equipment, increasing the openness of device resources, and improving the management performance of industrial equipment.
[0005] In a first aspect, an embodiment of the present application provides a method for collaboratively processing device resources, the method comprising:
[0006] In response to a collaborative user identifier selected by the relationship establishment user in the collaborative relationship establishment interface, sending a collaborative relationship establishment request of the relationship establishment user to the collaborative user corresponding to the collaborative user identifier, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishment user;
[0007] After the collaborative user confirms, the corresponding storage relationship establishment user identifier, collaborative user identifier, and collaborative relationship identifier are stored to establish a collaborative relationship between the relationship establishment user and the collaborative user; the collaborative relationship identifier is randomly assigned and is different from other collaborative relationship identifiers;
[0008] In response to the co-processing type and co-processing user selected by the target user in the device resource co-processing interface, the device resource co-processing operation corresponding to the co-processing type is completed according to the device resources of the target user and / or the device resources of the co-processing user; a collaborative relationship exists between the target user and the co-processing user.
[0009] In a possible implementation, if the collaborative processing type is a device model building type, in response to the collaborative processing type and the collaborative processing user selected by the target user in the device resource collaborative processing interface, the device resource collaborative processing operation corresponding to the collaborative processing type is completed according to the device resources of the target user and / or the device resources of the collaborative processing user, including:
[0010] Acquire data cleaning information and device model building information input by the target user, and the target device data identifier selected from the device data identifiers corresponding to the collaborative processing user;
[0011] The data cleaning information and the target device data identifier are sent to the collaborative processing user, so that the collaborative processing user cleans the data corresponding to the target device data identifier according to the data cleaning information;
[0012] Receive the target device data of cleaning completion sent by the collaborative processing user;
[0013] Build a device model for the target user based on the device model building information and the target device data.
[0014] In a possible implementation, obtaining device model building information input by a target user includes:
[0015] In response to a device analysis model building request initiated by a target user on a device model building interface, all deep learning framework identifiers are displayed on the device model building interface, so that the target user can select a target deep learning framework identifier from all deep learning framework identifiers;
[0016] Obtain the model input information and model output information entered by the target user in the device model building interface.
[0017] In a possible implementation, before building a device model for a target user based on the device model building information and the target device data, the method further includes:
[0018] A container service is created for a target user to build a device model for the target user based on the container service, the device model building information, and the target device data.
[0019] In a possible implementation, if the collaborative processing type is a device data sharing type, in response to the collaborative processing type and the collaborative processing user selected by the target user in the device resource collaborative processing interface, the device resource collaborative processing operation corresponding to the collaborative processing type is completed according to the device resources of the target user and / or the device resources of the collaborative processing user, including:
[0020] In response to the target user selecting the device data to be shared on the device data sharing interface, displaying all the collaborative relationship identifiers corresponding to the target user on the device data sharing interface, so that the target user selects a first collaborative relationship identifier from all the collaborative relationship identifiers;
[0021] The device data to be shared is shared with users corresponding to the first collaborative relationship identifier except the target user.
[0022] In a possible implementation, if the collaborative processing type is a device model sharing type, in response to the collaborative processing type and the collaborative processing user selected by the target user in the device resource collaborative processing interface, the device resource collaborative processing operation corresponding to the collaborative processing type is completed according to the device resources of the target user and / or the device resources of the collaborative processing user, including:
[0023] In response to the target user selecting a device model to be shared on the device model sharing interface, displaying all collaborative relationship identifiers corresponding to the target user on the device model sharing interface, so that the target user selects a second collaborative relationship identifier from all collaborative relationship identifiers;
[0024] The device model to be shared is shared with users corresponding to the second collaborative relationship identifier except the target user.
[0025] In a second aspect, an embodiment of the present application further provides a collaborative processing system for device resources, the collaborative processing system for device resources comprising:
[0026] A response module, configured to respond to a collaborative user identifier selected by the relationship establishment user on the collaborative relationship establishment interface and send a collaborative relationship establishment request of the relationship establishment user to the collaborative user corresponding to the collaborative user identifier, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishment user;
[0027] The establishment module is used to establish the identification of the establishment user, the collaborative user identification, and the collaborative relationship identification corresponding to the storage relationship after the collaborative user confirmation is completed, so as to establish the collaborative relationship between the establishment user and the collaborative user; the collaborative relationship identification is randomly assigned and is different from other collaborative relationship identifications;
[0028] The response module is also used to respond to the collaborative processing type and collaborative processing user selected by the target user in the device resource collaborative processing interface, and complete the device resource collaborative processing operation corresponding to the collaborative processing type according to the device resources of the target user and / or the device resources of the collaborative processing user; a collaborative relationship exists between the target user and the collaborative processing user.
[0029] In a possible implementation, the response module is specifically configured to obtain data cleaning information and device model building information input by the target user, and a target device data identifier selected from the device data identifiers corresponding to the collaborative processing user, if the collaborative processing type is a device model building type;
[0030] The data cleaning information and the target device data identifier are sent to the collaborative processing user, so that the collaborative processing user cleans the data corresponding to the target device data identifier according to the data cleaning information;
[0031] Receive the target device data of cleaning completion sent by the collaborative processing user;
[0032] Build a device model for the target user based on the device model building information and the target device data.
[0033] In the third aspect, an embodiment of the present application also provides an electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, when the electronic device is running, the processor and the storage medium communicate through the bus, and the processor executes the machine-readable instructions to perform the steps of the collaborative processing method of device resources as described in any one of the first aspects.
[0034] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the collaborative processing method of device resources as described in any one of the first aspects are executed.
[0035] The embodiment of the present application provides a method, system, electronic device and storage medium for collaborative processing of equipment resources, the method comprising: in response to the collaborative user identifier selected by the relationship establishment user in the collaborative relationship establishment interface, sending a collaborative relationship establishment request of the relationship establishment user to the collaborative user corresponding to the collaborative user identifier, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishment user; after the collaborative user confirms, the identifier of the relationship establishment user, the collaborative user identifier and the collaborative relationship identifier are stored correspondingly to establish a collaborative relationship between the relationship establishment user and the collaborative user; in response to the collaborative processing type and the collaborative processing user selected by the target user in the equipment resource collaborative processing interface, according to the equipment resources of the target user and / or the equipment resources of the collaborative processing user, the equipment resource collaborative processing operation corresponding to the collaborative processing type is completed. The present application can complete the collaborative processing of equipment resources for the equipment resources of users with collaborative relationships, thereby managing the equipment, increasing the openness of equipment resources, and improving the management performance of industrial equipment. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0037] Figure 1 A flowchart of a method for collaboratively processing device resources provided by an embodiment of the present application is shown;
[0038] Figure 2 A flowchart of another method for collaborative processing of device resources provided in an embodiment of the present application is shown;
[0039] Figure 3 A flowchart of another method for collaborative processing of device resources provided in an embodiment of the present application is shown;
[0040] Figure 4 A flowchart of another method for collaborative processing of device resources provided in an embodiment of the present application is shown;
[0041] Figure 5 A flowchart of collaborative processing of device resources provided by an embodiment of the present application is shown;
[0042] Figure 6 A schematic diagram of the structure of a collaborative system of device resources provided in an embodiment of the present application is shown;
[0043] Figure 7 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION
[0044] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.
[0045] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.
[0046] In order to enable those skilled in the art to use the content of this application, the following implementation is provided in conjunction with the specific application scenario "device management field". For those skilled in the art, the general principles defined herein can be applied to other embodiments and application scenarios without departing from the spirit and scope of this application. Although this application is mainly described around the "device management field", it should be understood that this is only an exemplary embodiment.
[0047] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.
[0048] The following is a detailed description of a method for collaborative processing of device resources provided in an embodiment of the present application.
[0049] Reference Figure 1 As shown, it is a flow chart of a collaborative processing method of device resources provided in an embodiment of the present application. The specific execution process of the collaborative method of device resources is as follows:
[0050] S101. In response to a collaborative user identifier selected by a relationship establishing user in a collaborative relationship establishing interface, a collaborative relationship establishing request of the relationship establishing user is sent to a collaborative user corresponding to the collaborative user identifier, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishing user.
[0051] S102: After the collaborative user has confirmed, the identification of the user establishing the relationship, the collaborative user identification, and the collaborative relationship identification are stored accordingly to establish a collaborative relationship between the relationship establishing user and the collaborative user.
[0052] S103. In response to the co-processing type and co-processing user selected by the target user in the device resource co-processing interface, the device resource co-processing operation corresponding to the co-processing type is completed according to the device resources of the target user and / or the device resources of the co-processing user.
[0053] The embodiment of the present application provides a collaborative method for equipment resources, the method comprising: in response to the collaborative user identifier selected by the relationship establishment user in the collaborative relationship establishment interface, sending a collaborative relationship establishment request of the relationship establishment user to the collaborative user corresponding to the collaborative user identifier, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishment user; after the collaborative user confirmation is completed, the identifier of the relationship establishment user, the collaborative user identifier, and the collaborative relationship identifier are stored correspondingly to establish a collaborative relationship between the relationship establishment user and the collaborative user; in response to the collaborative processing type and the collaborative processing user selected by the target user in the equipment resource collaborative processing interface, according to the equipment resources of the target user and / or the equipment resources of the collaborative processing user, the equipment resource collaborative processing operation corresponding to the collaborative processing type is completed. The present application can complete the collaborative processing of equipment resources for the equipment resources of users with collaborative relationships, thereby managing the equipment, increasing the openness of equipment resources, and improving the management performance of industrial equipment.
[0054] The following is a description of the exemplary steps of the present application embodiment:
[0055] S101. In response to a collaborative user identifier selected by a relationship establishing user in a collaborative relationship establishing interface, a collaborative relationship establishing request of the relationship establishing user is sent to a collaborative user corresponding to the collaborative user identifier, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishing user.
[0056] In the implementation manner of the present application, the relationship establishing user can be a device user or a device supplier. The collaborative user corresponding to the collaborative user identifier can be a device user or a device supplier. The collaborative user can confirm the establishment of a collaborative relationship with the relationship establishing user (i.e., agree to establish a collaborative relationship with the target user), or refuse to establish a collaborative relationship with the relationship establishing user. If the collaborative user refuses to establish a collaborative relationship with the relationship establishing user or the collaborative user's confirmation instruction is not received within a preset time, the establishment of the collaborative relationship between the relationship establishing user and the collaborative user is stopped; and a collaborative relationship establishment failure reminder is sent to the relationship establishing user.
[0057] Specifically, in response to a collaborative relationship establishment request initiated by the relationship establishment user in the collaborative relationship establishment interface, other user identifiers except the relationship establishment user are displayed in the collaborative relationship establishment interface, so that the relationship establishment user selects a collaborative user identifier from other user identifiers.
[0058] Here, the collaborative relationship establishment request may carry a collaborative user screening condition input by the relationship establishment user; the collaborative user screening condition is used to screen out collaborative user identifiers displayed for the relationship establishment user in the collaborative relationship establishment interface. If the collaborative relationship establishment request contains the collaborative user screening condition, other user identifiers that meet the collaborative user screening condition are displayed in the collaborative relationship establishment interface, so that the relationship establishment user can select the collaborative user identifier from other user identifiers.
[0059] Among them, the relationship-building user can customize the collaborative user screening conditions, reduce the number of other user identifiers displayed in the collaborative relationship-building interface, and improve selection efficiency and user experience.
[0060] S102: After the collaborative user has confirmed, the identification of the user establishing the relationship, the collaborative user identification, and the collaborative relationship identification are stored accordingly to establish a collaborative relationship between the relationship establishing user and the collaborative user.
[0061] In the implementation mode of the present application, after receiving the confirmation instruction of the collaborative user within the preset time period (i.e., after the collaborative user confirms), the corresponding storage relationship establishment user identifier, collaborative user identifier, and collaborative relationship identifier are used to establish a collaborative relationship between the relationship establishment user and the collaborative user; wherein the collaborative relationship identifier is randomly assigned and is different from other collaborative relationship identifiers. There is a specific collaborative relationship between the collaborative users and the relationship establishment users corresponding to the same collaborative relationship identifier, and the users with collaborative relationships can collaborate on device resources with each other; device resources include device data and device models.
[0062] Furthermore, after the relationship-building user establishes a collaborative relationship, the relationship-building user can authorize the permissions of the collaborative user corresponding to the established collaborative relationship, and can also view all collaborative user identifiers, add and delete collaborative users corresponding to the established collaborative relationship, etc. In addition, the users corresponding to the collaborative relationship can also conduct message conversations, and the conversations support text, pictures and voice content.
[0063] S103. In response to the co-processing type and co-processing user selected by the target user in the device resource co-processing interface, the device resource co-processing operation corresponding to the co-processing type is completed according to the device resources of the target user and / or the device resources of the co-processing user.
[0064] In the implementation manner of the present application, the target user can be a device user or a device supplier. The collaborative processing type includes a device model building type, a device data sharing type, and a device model sharing type. Different collaborative processing types correspond to different device resource collaborative processing operations. Among them, there is a collaborative relationship between the target user and the collaborative processing user. The device resource collaborative processing interface includes a device model building interface, a device data sharing interface, and a device model sharing interface.
[0065] Specifically, if the collaborative processing type is a device model building type, the data cleaning information and device model building information input by the target user, as well as the target device data identifier selected from the device data identifier corresponding to the collaborative processing user, are obtained; the data cleaning information and the target device data identifier are sent to the collaborative processing user, so that the collaborative processing user cleans the data corresponding to the target device data identifier according to the data cleaning information; the cleaned target device data sent by the collaborative processing user is received; and a device model is built for the target user based on the device model building information and the target device data.
[0066] Specifically, if the collaborative processing type is a device data sharing type, then in response to the target user selecting the device data to be shared in the device data sharing interface, all collaborative relationship identifiers corresponding to the target user will be displayed in the device data sharing interface, so that the target user can select the first collaborative relationship identifier from all collaborative relationship identifiers; and the device data to be shared will be shared with users other than the target user corresponding to the first collaborative relationship identifier.
[0067] Specifically, if the collaborative processing type is a device model sharing type, then in response to the target user selecting the device model to be shared in the device model sharing interface, all collaborative relationship identifiers corresponding to the target user will be displayed in the device model sharing interface, so that the target user can select a second collaborative relationship identifier from all collaborative relationship identifiers; and the device model to be shared will be shared with users other than the target user corresponding to the second collaborative relationship identifier.
[0068] Reference Figure 2 As shown, it is a flowchart of another method for collaborative processing of device resources provided in an embodiment of the present application. The exemplary steps of the embodiment of the present application are described below:
[0069] S201. Acquire data cleaning information and device model building information input by a target user, and a target device data identifier selected from device data identifiers corresponding to collaborative processing users.
[0070] In an implementation manner of the present application, the device data contains at least one data field; the data cleaning information is used to limit the form and content of the data shared by collaborative processing users, and may specifically include the data format (such as the arrangement order of multiple data segments), data segment identifier, data segment length, etc.
[0071] For example, the device specification data corresponding to the target device data identifier includes device size, device model, and device name. The arrangement order of the data segments in the data cleaning information can be: device model, device size, and the data segment identifier can include the device model identifier and the device size identifier.
[0072] Equipment models can include equipment 3D models, equipment analysis models, equipment simulation analysis models, equipment control models, etc. Among them, the equipment 3D model is a three-dimensional, solid model; the equipment analysis model refers to a deep learning model, which can be used to detect faults, determine equipment operating parameters, etc.; the equipment simulation analysis model is a model made for studying simulation equipment, which can be a physical model or a mathematical model, and can be used for thermal analysis of equipment, etc.; the equipment control model is a model that can control real equipment based on the input equipment operating parameters.
[0073] Here, different equipment models correspond to different equipment model construction information; the equipment model construction information contains the model attribute information required to build the model. The equipment model construction information of the equipment three-dimensional model may include the size of the three-dimensional model, the position of the three-dimensional model and the equipment identification constructed by the model, etc.; the equipment model construction information of the equipment analysis model may include the model's deep learning framework, model input information, model output information, model objective function (representing the final optimization goal of model training), the identification of the equipment analyzed by the model, etc.; the equipment model construction information of the equipment simulation analysis model may include initial conditions (referring to the numerical settings of each model variable or parameter at the beginning of the simulation), working condition settings and the identification of the equipment simulated by the model, etc.; the equipment model construction information of the equipment control model may include the identification of the equipment controlled by the model, etc.
[0074] Here, each device has a unique identification code (ie, device identification), and the device model, device data, and device service interface associated with it are all encoded based on this unique identification code.
[0075] In addition, in addition to obtaining the target device data identifier selected from the device data identifiers corresponding to the collaborative processing user, the target device data identifier selected from the device data identifiers of the target user may also be obtained.
[0076] Here, each user has a private space (that is, other users cannot view or obtain it) and a public space (that is, other users can view or obtain it, and the other users who can view or obtain it can be set by the user himself). The device data identifier corresponding to the collaborative processing user refers to the data stored in the public space by the collaborative processing user;
[0077] Specifically, obtaining device model building information input by the target user includes: in response to a device analysis model building request initiated by the target user in the device model building interface, displaying all deep learning framework identifiers in the device model building interface so that the target user can select a target deep learning framework identifier from all deep learning framework identifiers; and obtaining model input information and model output information input by the target user in the device model building interface.
[0078] In the implementation manner of the present application, the device analysis model construction request means that the model that the target user needs to build is a device analysis model. The target deep learning framework includes learning frameworks such as TensorFlow, Caffe, and PyTorch. In addition to obtaining the model input information and model output information entered by the target user in the device model construction interface, the model objective function entered by the target user in the device model construction interface and the device identifier analyzed by the model can also be obtained.
[0079] In addition, further, if the acquired device model construction information is the device model construction information of the device analysis model, then before building the device model for the target user based on the device model construction information and the target device data, the method also includes: creating a container service for the target user to build a device model for the target user based on the container service, the device model construction information and the target device data.
[0080] Here, Container Service is a cloud computing service designed to simplify the deployment, management and expansion of containerized applications. It provides a reliable platform that enables developers to build, package and run applications more easily without having to pay attention to the underlying infrastructure and complex container orchestration work; Allocating container services means allocating processor resources such as CPU and GPU to target users for the construction of device analysis models.
[0081] Specifically, obtaining the target user input device model construction information includes: responding to the device three-dimensional model construction request initiated by the target user in the device model construction interface, obtaining the size of the three-dimensional model input by the target user in the device model construction interface, the position of the three-dimensional model and the device identification of the model constructed, etc.
[0082] Specifically, obtaining the target user input device model construction information includes: responding to the device three-dimensional model construction request initiated by the target user in the device model construction interface, obtaining the size of the three-dimensional model input by the target user in the device model construction interface, the position of the three-dimensional model and the device identification of the model constructed, etc.
[0083] Specifically, obtaining the target user input device model building information includes: responding to the device simulation analysis model building request initiated by the target user in the device model building interface, obtaining the initial conditions, working condition settings and device identification simulated by the model input by the target user in the device model building interface.
[0084] Specifically, obtaining the target user input device model building information includes: responding to a device control model building request initiated by the target user in the device model building interface, obtaining the device identifier controlled by the model input by the target user in the device model building interface, etc.
[0085] S202: Send the data cleaning information and the target device data identifier to the collaborative processing user, so that the collaborative processing user cleans the data corresponding to the target device data identifier according to the data cleaning information.
[0086] For example, the device specification data corresponding to the target device data identifier includes device size, device model, and device name. The arrangement order of the data segments in the data cleaning information can be: device model, device size, and the data segment identifier can include device model identifier and device size identifier. The shared user should remove the device name in the device specification data and arrange it in the order of device model and device size. For example, for a piece of data A, the device model of data A is HJK, the device size is 35*34*67, and the name is Q, then the cleaned data A should be HJK35*34*67.
[0087] S203: Receive the cleaning completed target device data sent by the collaborative processing user.
[0088] S204: Build a device model for the target user based on the device model building information and the target device data.
[0089] In the implementation mode of the present application, the constructed device model should meet the device model construction information; and different device models have different corresponding construction steps. The construction steps of the device three-dimensional model can be planning, modeling, material and texture addition, lighting setting, animation, rendering and adjustment, and post-processing, etc., or the existing three-dimensional modeling software Unity can be used directly. The construction steps of the device analysis model can be data collection, feature extraction and selection, model training, testing and evaluation, and possible optimization, etc. The construction steps of the device simulation analysis model can be determining the state variables, the initial conditions of the model and the estimation of the parameters, selecting the time change method of the model, determining the probability distribution of each main random variable and the generation method of uniform random numbers, drawing the logical relationship flow chart between the entities in each subsystem, and describing how the state variables change over time in mathematical form, etc.
[0090] Furthermore, if the device model built by the target user is a device analysis model, after the model is built, it is also necessary to stop the container service used to build the model to release the computing resources CPU and GPU.
[0091] Reference Figure 3 As shown, it is a flow chart of another device resource collaboration method provided in an embodiment of the present application. The exemplary steps of the embodiment of the present application are described below:
[0092] S301. In response to a target user selecting device data to be shared in a device data sharing interface, all collaborative relationship identifiers corresponding to the target user are displayed in the device data sharing interface, so that the target user selects a first collaborative relationship identifier from all collaborative relationship identifiers.
[0093] In the implementation manner of the present application, the equipment data may include equipment specification data, equipment operation data, equipment failure data, equipment model operation data, etc.
[0094] S302: Share the device data to be shared with users corresponding to the first collaborative relationship identifier except the target user.
[0095] Here, sharing the device data to be shared with users other than the target user corresponding to the first collaborative relationship identifier does not directly send the device data to be shared to other users, but stores the device data to be shared in the public space of the target user, so that other users can view or obtain the device data to be shared when they need to use it (including but not limited to device model construction), avoiding other users from storing too much invalid device data and reducing storage space. When viewing device data, two-dimensional data can be displayed in the form of icons.
[0096] In addition, in addition to the above-mentioned method in which the target user shares device data with other users by selecting a collaborative relationship identifier, the device data to be shared can also be shared with users who meet the device access permissions and have a collaborative relationship in response to the target user selecting the device data to be shared and entering the device access permissions in the device data sharing interface.
[0097] Furthermore, sharing the device data to be shared with users other than the target user corresponding to the first collaborative relationship identifier, or sharing the device data to be shared with users who meet the device access rights and have a collaborative relationship includes: performing blockchain authentication on the device data to be shared; after the blockchain authentication is passed, sharing the device data to be shared with users other than the target user corresponding to the first collaborative relationship identifier, or sharing the device data to be shared with users who meet the device access rights and have a collaborative relationship.
[0098] Here, blockchain authentication is a method of using blockchain technology for identity authentication and security confirmation. This authentication method involves writing device data directly into the blockchain, using its tamper-proof and distributed characteristics to improve the security and reliability of identity authentication. For example, by writing device data into the blockchain, the identity of the device can be securely confirmed without relying on the traditional centralized digital certificate authentication center (CA), thereby improving efficiency and security.
[0099] Furthermore, the embodiments of the present application also provide a device data access method, which sets different access methods for historical device data and real-time device data. Specifically: for historical device data, a file or database of historical device data imported by a target user in a historical device data upload interface is received; the historical device data in the file or database is stored in the device data list of the target user. For real-time device data, the real-time device data of the target user is received according to the MQTT topic set by the target user; the real-time device data is stored in the device data list of the target user; wherein the content of the MQTT topic set by the target user corresponds to the field in the device data list.
[0100] In the implementation mode of the present application, the device data is stored in the target user's private space by default after access (i.e. other users cannot view or obtain it). It can only be stored in the target user's public space (i.e. other users can view or obtain it) when the target user actively shares it.
[0101] Here, MQTT topic is a very important concept in the MQTT protocol, which is used to classify and filter messages. MQTT messages are classified by topic. Clients can publish messages to specific topics or subscribe to one or more topics to receive related messages. MQTT topics have the following characteristics: 1. Hierarchical structure: MQTT topics can use " / " as a hierarchical separator to build a hierarchical topic tree. This hierarchical structure makes the management and classification of topics more flexible and convenient. For example, the topic " / home / livingroom / temperature" represents the temperature information of the living room in a home environment. 2. Wildcard: The MQTT protocol supports two wildcards for matching topics. Single-level wildcard (+): matches a topic name of one level. For example, the topic " / home / + / temperature" can match " / home / livingroom / temperature" and " / home / bedroom / temperature", etc. Multi-level wildcard (#): matches topic names of any level. For example, the topic " / home / #" can match all topics starting with " / home / ", such as " / home / livingroom / temperature", " / home / bedroom / humidity". 3. Name specification: The topic name should be kept as short and clear as possible. It is recommended to use ASCII characters and avoid spaces and special characters. At the same time, the topic name is case-sensitive, so " / HOME" and " / home" will be considered as two different topics. 4. System topic: The MQTT protocol also defines some special system topics for transmitting system-level messages and control information. For example, topics with the prefix "$SYS / " are used by the MQTT broker (Broker) to publish its internal status information. In MQTT applications, the correct design and use of topics are crucial to the implementation of message publishing, subscription, and filtering. By reasonably constructing the topic tree and using wildcards, flexible message routing and efficient resource utilization can be achieved.
[0102] The embodiment of the present application provides another collaborative processing method for device resources, which enables the target user to actively share device data with other users with collaborative relationships, so as to increase the openness of the device data and improve the management performance of industrial equipment.
[0103] Reference Figure 4 As shown, it is a flowchart of another method for collaborative processing of device resources provided in an embodiment of the present application. The exemplary steps of the embodiment of the present application are described below:
[0104] S401. In response to a target user selecting a device model to be shared in a device model sharing interface, all collaborative relationship identifiers corresponding to the target user are displayed in the device model sharing interface, so that the target user selects a second collaborative relationship identifier from all collaborative relationship identifiers.
[0105] In the implementation manner of the present application, the device model may include a three-dimensional device model, a device analysis model, a device simulation analysis model, a device control model, etc.
[0106] S402: Share the device model to be shared with users corresponding to the second collaborative relationship identifier except the target user.
[0107] Here, sharing the device model to be shared with users other than the target user corresponding to the second collaborative relationship identifier does not mean directly sending the device model to be shared to other users, but means storing the interface or model file of the device model to be shared in the public space of the target user, so that other users can view or obtain the device model to be shared when they need to use it (including but not limited to device model construction), avoiding other users from storing too many invalid device models and reducing storage space. Here, the embodiment of the present application can display a three-dimensional model.
[0108] Furthermore, sharing the device model to be shared with users other than the target user corresponding to the second collaborative relationship identifier includes: performing blockchain authentication on the device model to be shared; and sharing the device model to be shared with users other than the target user corresponding to the second collaborative relationship identifier after the blockchain authentication is passed.
[0109] Here, an embodiment of the present application provides another collaborative processing method for device resources, which enables the target user to actively share the device model with other users with a sharing relationship, so as to increase the openness of the device model and improve the management performance of industrial equipment.
[0110] like Figure 5 As shown, it is a collaborative processing flow chart of device resources provided in an embodiment of the present application, wherein, after the initiator creates a collaborative project, it invites multiple collaborators to participate in the collaborative project, that is, the initiator and the collaborators establish a system relationship. The initiator and the collaborators create the managed devices in their respective resource management and collect the data resources and model resources of the device. The initiator and the collaborators can also upload their respective data resources and model resources to the chain (i.e., blockchain authentication). After successful authentication, the data resources and model resources are shared, and then the application scenarios of the resources are constructed and published so that both the initiator and the collaborators can use the shared data resources and model resources. In addition, the initiator and the collaborators can also perform intelligent analysis (i.e., build a device model), reference the data resources shared by the initiator and the collaborators, and use the data resources for model construction training, and publish the intelligent model resources after the training is completed.
[0111] Scenario example: A scenario where an equipment supplier collaborates with multiple equipment users to perform predictive maintenance on equipment. The equipment supplier initiates a collaborative relationship and shares equipment 3D models and equipment simulation analysis models, etc. Equipment users share data and models such as real-time data on equipment operating status and historical equipment failures. Multiple parties collaborate to build equipment predictive maintenance applications in a collaborative working environment to guide equipment users to perform predictive maintenance on equipment, improve equipment utilization, and reduce equipment maintenance cycles and costs. After multiple parties jointly build and train an equipment status prediction model (the specific functions of the equipment analysis model are conformal) and share the model with users in the collaborative relationship, the equipment supplier and equipment user in the collaborative relationship can call the model to analyze private data and share the analysis results for updating the equipment status prediction model in the collaborative environment.
[0112] Based on the same inventive concept, the embodiment of the present application also provides a collaborative processing system for device resources corresponding to the collaborative processing method for device resources. Since the principle of solving the problem by the system in the embodiment of the present application is similar to the collaborative processing method for device resources in the embodiment of the present application, the implementation of the system can refer to the implementation of the method, and the repeated parts will not be repeated.
[0113] Reference Figure 6 FIG. 1 is a schematic diagram of a collaborative processing system for device resources provided in an embodiment of the present application. The collaborative processing system for device resources includes:
[0114] A response module 601 is used for sending a collaborative relationship establishment request of the relationship establishment user to the collaborative user corresponding to the collaborative user identifier in response to the collaborative user identifier selected by the relationship establishment user in the collaborative relationship establishment interface, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishment user;
[0115] Establishing module 602, used for storing the identifier of the relationship establishing user, the collaborative user identifier, and the collaborative relationship identifier correspondingly after the collaborative user confirms, so as to establish a collaborative relationship between the relationship establishing user and the collaborative user; the collaborative relationship identifier is randomly assigned and is different from other collaborative relationship identifiers;
[0116] Response module 601 is also used to respond to the collaborative processing type and collaborative processing user selected by the target user in the device resource collaborative processing interface, and complete the device resource collaborative processing operation corresponding to the collaborative processing type according to the device resources of the target user and / or the device resources of the collaborative processing user; a collaborative relationship exists between the target user and the collaborative processing user.
[0117] In a possible implementation, the response module is specifically used to obtain data cleaning information and device model building information input by the target user, and a target device data identifier selected from the device data identifier corresponding to the collaborative processing user, if the collaborative processing type is a device model building type; send the data cleaning information and the target device data identifier to the collaborative processing user, so that the collaborative processing user cleans the data corresponding to the target device data identifier according to the data cleaning information; receive the cleaned target device data sent by the collaborative processing user; and build a device model for the target user based on the device model building information and the target device data.
[0118] In a possible implementation manner, the response module is further configured to:
[0119] In response to a device analysis model building request initiated by the target user on the device model building interface, all deep learning framework identifiers are displayed on the device model building interface, so that the target user can select a target deep learning framework identifier from all deep learning framework identifiers;
[0120] The model input information and model output information input by the target user in the device model building interface are obtained.
[0121] In a possible implementation, the response module is further used to create a container service for the target user before building a device model for the target user based on the device model building information and the target device data, so as to build a device model for the target user based on the container service, the device model building information and the target device data.
[0122] In one possible implementation, the response module is specifically used to display all collaborative relationship identifiers corresponding to the target user in the device data sharing interface in response to the target user selecting the device data to be shared in the device data sharing interface if the collaborative processing type is a device data sharing type, so that the target user can select a first collaborative relationship identifier from all collaborative relationship identifiers; and share the device data to be shared with users other than the target user corresponding to the first collaborative relationship identifier.
[0123] In a possible implementation, the response module is specifically used to display all collaborative relationship identifiers corresponding to the target user in the device model sharing interface in response to the target user selecting the device model to be shared in the device model sharing interface if the collaborative processing type is a device model sharing type, so that the target user can select a second collaborative relationship identifier from all collaborative relationship identifiers; and share the device model to be shared with users other than the target user corresponding to the second collaborative relationship identifier.
[0124] The embodiment of the present application provides a collaborative processing system for equipment resources, which includes: a response module 601, which is used to respond to the collaborative user identifier selected by the relationship establishment user in the collaborative relationship establishment interface, and send a collaborative relationship establishment request of the relationship establishment user to the collaborative user corresponding to the collaborative user identifier, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishment user; an establishment module 602, which is used to store the identifier of the relationship establishment user, the collaborative user identifier, and the collaborative relationship identifier correspondingly after the collaborative user confirms, so as to establish a collaborative relationship between the relationship establishment user and the collaborative user; the response module 601 is also used to respond to the collaborative processing type and collaborative processing user selected by the target user in the equipment resource collaborative processing interface, and complete the equipment resource collaborative processing operation corresponding to the collaborative processing type according to the equipment resources of the target user and / or the equipment resources of the collaborative processing user. The present application can complete the collaborative processing of equipment resources for the equipment resources of users with collaborative relationships, thereby managing the equipment, increasing the openness of equipment resources, and improving the management performance of industrial equipment.
[0125] like Figure 7 As shown, an electronic device 700 provided in an embodiment of the present application includes: a processor 701, a memory 702 and a bus, the memory 702 stores machine-readable instructions executable by the processor 701, when the electronic device is running, the processor 701 and the memory 702 communicate through the bus, and the processor 701 executes the machine-readable instructions to perform the steps of the collaborative processing method of device resources as mentioned above.
[0126] Specifically, the above-mentioned memory 702 and processor 701 can be general-purpose memories and processors, which are not specifically limited here. When the processor 701 runs the computer program stored in the memory 702, it can execute the above-mentioned collaborative processing method of device resources.
[0127] Corresponding to the above-mentioned collaborative processing method of device resources, an embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned collaborative processing method of device resources are executed.
[0128] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the method embodiment, and will not be repeated in this application. In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.
[0129] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0130] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0131] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, 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, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the information processing method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.
[0132] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A method for collaborative processing of device resources, characterized in that: The method comprises: In response to a collaborative user identifier selected by the relationship establishment user in the collaborative relationship establishment interface, sending a collaborative relationship establishment request of the relationship establishment user to the collaborative user corresponding to the collaborative user identifier, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishment user; After the collaborative user confirms, the identifier of the relationship-establishing user, the collaborative user identifier, and the collaborative relationship identifier are stored accordingly to establish a collaborative relationship between the relationship-establishing user and the collaborative user; the collaborative relationship identifier is randomly assigned and is different from other collaborative relationship identifiers; In response to the co-processing type and co-processing user selected by the target user in the device resource co-processing interface, the device resource co-processing operation corresponding to the co-processing type is completed according to the device resources of the target user and / or the device resources of the co-processing user; a collaborative relationship exists between the target user and the co-processing user.
2. The collaborative processing method of device resources according to claim 1, characterized in that: If the collaborative processing type is a device model building type, in response to the collaborative processing type and the collaborative processing user selected by the target user in the device resource collaborative processing interface, the device resource collaborative processing operation corresponding to the collaborative processing type is completed according to the device resources of the target user and / or the device resources of the collaborative processing user, including: Acquire data cleaning information and device model building information input by a target user, and a target device data identifier selected from the device data identifiers corresponding to the collaborative processing user; Sending the data cleaning information and the target device data identifier to the collaborative processing user, so that the collaborative processing user cleans the data corresponding to the target device data identifier according to the data cleaning information; Receiving the target device data of cleaning completion sent by the collaborative processing user; A device model is constructed for the target user based on the device model construction information and the target device data.
3. The collaborative processing method of device resources according to claim 2, characterized in that: Obtain device model building information input by the target user, including: In response to a device analysis model building request initiated by the target user on the device model building interface, all deep learning framework identifiers are displayed on the device model building interface, so that the target user can select a target deep learning framework identifier from all deep learning framework identifiers; The model input information and model output information input by the target user in the device model building interface are obtained.
4. The collaborative processing method of device resources according to claim 3, characterized in that: Before constructing a device model for the target user based on the device model construction information and the target device data, the method further includes: A container service is created for the target user to build a device model for the target user based on the container service, the device model building information and the target device data.
5. The collaborative processing method of device resources according to claim 1, characterized in that: If the collaborative processing type is a device data sharing type, in response to the collaborative processing type and the collaborative processing user selected by the target user in the device resource collaborative processing interface, the device resource collaborative processing operation corresponding to the collaborative processing type is completed according to the device resources of the target user and / or the device resources of the collaborative processing user, including: In response to the target user selecting the device data to be shared on the device data sharing interface, displaying all the collaborative relationship identifiers corresponding to the target user on the device data sharing interface, so that the target user selects a first collaborative relationship identifier from all the collaborative relationship identifiers; The device data to be shared is shared with users corresponding to the first collaborative relationship identifier except the target user.
6. The collaborative processing method of device resources according to claim 1, characterized in that: If the collaborative processing type is a device model sharing type, in response to the collaborative processing type and the collaborative processing user selected by the target user in the device resource collaborative processing interface, the device resource collaborative processing operation corresponding to the collaborative processing type is completed according to the device resources of the target user and / or the device resources of the collaborative processing user, including: In response to a target user selecting a device model to be shared on a device model sharing interface, displaying all collaborative relationship identifiers corresponding to the target user on the device model sharing interface, so that the target user selects a second collaborative relationship identifier from all collaborative relationship identifiers; The device model to be shared is shared with users corresponding to the second collaborative relationship identifier except the target user.
7. A collaborative processing system for device resources, characterized in that: The collaborative processing system of the device resources includes: A response module, configured to respond to a collaborative user identifier selected by a relationship establishment user in a collaborative relationship establishment interface, and send a collaborative relationship establishment request of the relationship establishment user to the collaborative user corresponding to the collaborative user identifier, so that the collaborative user confirms to establish a collaborative relationship with the relationship establishment user; An establishment module, used for storing the identifier of the relationship establishment user, the collaborative user identifier, and the collaborative relationship identifier correspondingly after the collaborative user confirms the relationship, so as to establish a collaborative relationship between the relationship establishment user and the collaborative user; the collaborative relationship identifier is randomly assigned and is different from other collaborative relationship identifiers; The response module is also used to respond to the collaborative processing type and collaborative processing user selected by the target user in the device resource collaborative processing interface, and complete the device resource collaborative processing operation corresponding to the collaborative processing type according to the device resources of the target user and / or the device resources of the collaborative processing user; a collaborative relationship exists between the target user and the collaborative processing user.
8. The collaborative processing system of device resources according to claim 7, characterized in that: The response module is specifically used for: If the collaborative processing type is a device model building type, obtaining data cleaning information and device model building information input by the target user, and a target device data identifier selected from the device data identifier corresponding to the collaborative processing user; Sending the data cleaning information and the target device data identifier to the collaborative processing user, so that the collaborative processing user cleans the data corresponding to the target device data identifier according to the data cleaning information; Receiving the target device data of cleaning completion sent by the collaborative processing user; A device model is constructed for the target user based on the device model construction information and the target device data.
9. An electronic device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the storage medium communicate via the bus, and the processor executes the machine-readable instructions to perform the steps of the collaborative processing method of device resources as described in any one of claims 1 to 6.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for collaborative processing of device resources according to any one of claims 1 to 6 are executed.
