WO2023226703A1 - 状态监控***、状态信息的更新方法及装置 - Google Patents
状态监控***、状态信息的更新方法及装置 Download PDFInfo
- Publication number
- WO2023226703A1 WO2023226703A1 PCT/CN2023/091889 CN2023091889W WO2023226703A1 WO 2023226703 A1 WO2023226703 A1 WO 2023226703A1 CN 2023091889 W CN2023091889 W CN 2023091889W WO 2023226703 A1 WO2023226703 A1 WO 2023226703A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- status information
- target
- target device
- status
- client
- Prior art date
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 199
- 238000000034 method Methods 0.000 title claims abstract description 78
- 230000008859 change Effects 0.000 claims abstract description 114
- 238000004519 manufacturing process Methods 0.000 claims abstract description 71
- 230000004044 response Effects 0.000 claims abstract description 65
- 238000003860 storage Methods 0.000 claims description 12
- 238000009434 installation Methods 0.000 claims description 6
- 230000001960 triggered effect Effects 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 3
- 230000003749 cleanliness Effects 0.000 abstract description 5
- 238000007726 management method Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 238000012423 maintenance Methods 0.000 description 7
- 101100113686 Clitocybe nebularis clt4 gene Proteins 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000002411 adverse Effects 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 230000004913 activation Effects 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000001934 delay Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 239000000428 dust Substances 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000012535 impurity Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/04—Processing captured monitoring data, e.g. for logfile generation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Definitions
- the present disclosure relates to the field of computer technology, and specifically, to a status monitoring system, a method and device for updating status information.
- embodiments of the present disclosure propose a status monitoring system, status information updating method and device to realize automatic monitoring of status information of production equipment, thereby solving deficiencies in related technologies.
- a method for updating status information including: in response to a status monitoring request initiated by a client for a target device, returning the current status information of the target device to the client, The client displays the current status information in the target monitoring interface; when a status change message for the target device is received, the changed status of the target device included in the status change message is The changed status information is sent to the client, so that the client updates the target monitoring interface according to the changed status information.
- the method further includes: querying the target layout file corresponding to the target device according to the identification information contained in the status monitoring request, and returning the target layout file to the client, so that the client can The device layout indicated by the target layout file displays the current status information.
- the method further includes: determining the target element corresponding to the target device in the target layout file, and replacing the element identification of the target element recorded in the target layout file with the device identification of the target device. ; Returning the target layout file to the client includes: returning the replaced target layout file to the client.
- the status monitoring request includes the identity information of the user who logged in to the client, and returning the current status information of the target device to the client includes: indicating that the user If it has the monitoring authority for the target device, the current status information of the target device is returned to the client.
- the current status information of the target device is obtained in the following manner: reading the current status information of the target device from a database associated with a manufacturing execution system, which is configured to respond to the target When the status information of the device changes, the status change message is initiated and the status information of the target device recorded in the database is updated.
- sending the changed status information of the target device after the change in the status change message to the client including:
- writing the changed status information contained in the status change message into the cache includes: if the status information of the target device has not been written in the cache, in the blank space of the cache The changed state information is written at the address; if the state information of the target device has been written in the cache, the changed state information is used to overwrite the written state information.
- writing the changed status information contained in the status change message into the cache includes: writing the changed status information into the cache according to a preset format.
- another method for updating status information including: in response to a status monitoring operation performed by a user on a target device, initiating a status monitoring request for the target device to the server, and The target monitoring interface displays the current status information of the target device returned by the server in response to the request; upon receiving the changed status information of the target device sent by the server, according to the change After the status information is updated, the target monitoring interface is updated.
- the status monitoring request includes identification information of the device
- the method further includes: receiving a target layout file corresponding to the target device queried by the server based on the identification information; Displaying the current status information in the monitoring interface includes: displaying the current status information in the target monitoring interface according to the device layout indicated by the target layout file.
- the device layout indicated by the target layout file includes at least one of the following: a device level to which the target device belongs, an installation location of the target device, and a connection method between the target device and other devices.
- the method further includes: in response to an indicator viewing operation performed by the user, collecting statistics on the operating indicators of the target device according to the device status of the target device; or, obtaining from the server the device statistics of the target device according to the device status of the target device.
- the operation indicators of the target device obtained by status statistics are displayed in the post-switch interface corresponding to the indicator viewing operation.
- the method further includes: in response to a status refresh operation performed by the user on the target device, The server initiates an update query request for the target device, so that the server returns the changed status information in response to the request.
- the method further includes: in response to the first switching operation performed by the user, determining a post-switching interface corresponding to the operation, where the post-switching interface includes a centralized monitoring interface or a monitoring interface of any device, wherein the centralized The monitoring interface is used to centrally display the status information of each device in the device set corresponding to the operation, and the monitoring interface of any device is used to display the status information of the device; to initiate to the server a response to the switched interface. Correspond to the update query request of the switched device, and display the changed status information of the switched device returned by the server in response to the request in the switched interface.
- the method further includes: in response to a second switching operation performed by the user, switching the target monitoring interface to a parameter configuration interface; in response to a parameter configuration operation performed by the user in the parameter configuration interface, displaying The parameters are configured accordingly, and the configured display parameters are used to display the status information of the corresponding device in the target monitoring interface and/or the monitoring interface of other devices.
- a status monitoring system including a client and a server, wherein the client is used to initiate a status monitoring request for a target device to the server, and monitor The interface displays the current status information of the target device returned by the server in response to the request; and, upon receiving the changed status information of the target device after the change sent by the server, according to The changed status information updates the target monitoring interface; the server is configured to respond to the status monitoring request and return the current status information to the client; and, upon receiving the target device In the case of a status change message, the changed status information contained in the status change message is sent to the client.
- a manufacturing execution system and a database are also included, wherein the database is used to store status information of the target equipment, and the status information is triggered and stored in the manufacturing execution system in response to changes in the status information of the target equipment.
- the manufacturing execution system further sends the status change message to the server in response to a change in the status information of the target device.
- a cache is also included.
- the cache is used to store post-change status information after the target device is changed.
- the post-change status information is written to the cache by the server in response to the status change message. .
- a device for updating status information includes one or more processors, and the processor is configured to: respond to a status monitoring request initiated by a client for a target device. , return the current status information of the target device to the client, so that the client displays the current status information in the target monitoring interface; in the case of receiving a status change message for the target device , sending the changed status information after the change of the target device included in the status change message to the client, so that the client updates the target monitoring interface according to the changed status information.
- the device includes one or more processors, and the processor is configured to: respond to status monitoring implemented by the user for the target device. Control operation, initiate a status monitoring request for the target device to the server, and display the current status information of the target device returned by the server in response to the request in the target monitoring interface; after receiving the request from the server If the changed status information of the target device is sent, the target monitoring interface is updated according to the changed status information.
- an electronic device including: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to implement the above first or second aspect the method described.
- a non-transitory computer-readable storage medium on which a computer program is stored, which implements the steps of the method described in the first or second aspect when executed by a processor.
- the client can respond to the status monitoring operation performed by the user on the target device and initiate a status monitoring request for the device to the server.
- the server may return the current status information of the device to the client in response to the request, so that the client displays the current status information in the target monitoring interface.
- the server may send the changed status information of the target device after the change contained in the message to the client, so that the server can change the status according to the changed status information of the target device.
- Status information updates the target monitoring interface.
- the current status information displayed by the client in the target monitoring interface is used to represent the status of the target device before the change, and the target monitoring interface updated based on the status information after the change is used to represent the new status of the device after the change.
- the server senses that the target device has changed (that is, receives the status change message)
- it can notify the client to automatically update the target monitoring interface accordingly
- on-site workers, operation and maintenance personnel, and managers can Users can accurately and timely learn the above changes in the target device by viewing the target monitoring interface.
- users can learn whether and what kind of changes have occurred in the target equipment through the target monitoring interface without going to the production environment to check on-site. This not only saves labor costs, but also effectively avoids possible interference to the production environment by personnel, that is, This avoids adverse effects on the cleanliness of the production environment and ensures product quality.
- Figure 1 is a schematic architectural diagram of a status monitoring system according to an embodiment of the present disclosure.
- FIG. 2 is a flowchart of a method for updating status information according to an embodiment of the present disclosure.
- FIG. 3 is a flowchart of another method for updating status information according to an embodiment of the present disclosure.
- Figure 4 is a schematic diagram of a target monitoring interface according to an embodiment of the present disclosure.
- Figure 5 is a schematic structural diagram of a node device according to an embodiment of the present disclosure.
- the status information update system of the present disclosure includes a client and a server, wherein the client is used to initiate a status monitoring request for a target device to the server, and display the server response in the target monitoring interface.
- the current status information of the target device returned by the request; and, in the case of receiving the changed status information of the target device after the change sent by the server, updating the changed status information according to the changed status information.
- the target monitoring interface; the server is configured to return the current status information to the client in response to the status monitoring request; and, in the case of receiving a status change message for the target device,
- the changed status information contained in the status change message is sent to the client.
- the system further includes a database, wherein the database is used to store status information of the target device, and the status information is triggered by the manufacturing execution system to be stored in the target device in response to a change in the status information of the target device.
- the manufacturing execution system further sends the status change message to the server in response to a change in the status information of the target device.
- the system further includes a cache, the cache being used to store post-change status information after the target device is changed, and the post-change status information is generated by the server in response to the status change message. Write to the cache.
- FIG 1 is a schematic architectural diagram of a status monitoring system according to an embodiment of the present disclosure. Each component of the condition monitoring system will be described below with reference to Figure 1 .
- the server 10 and its connected client 11, database (DB, DataBase) 12 and cache 13 constitute the status monitoring system described in this disclosure.
- the server 10 may be a server of the FMB (Factory Monitoring Board) platform, and the client 11 may be run on a terminal device used by users such as field workers, operation and maintenance personnel, or managers. Users can Log in to the FMB platform through the client to monitor the equipment status of the target equipment at the production site.
- the server can be a physical server including an independent host, or it can be a virtual server, cloud server, etc. hosted by a host cluster.
- the server 10 can include multiple functional modules, such as a message receiving module 101, a message reading module, etc. Fetch module 102, scheduled task module 103 and information query module 104. The specific functions of each module can be found in the following embodiments and will not be described again here.
- the terminal device can be a mobile phone, a tablet device, a notebook computer, a PDAs (Personal Digital Assistants), a wearable device (such as smart glasses, a smart watch, etc.), a VR (Virtual Reality, virtual reality) device, or an AR (Augmented Reality, augmented reality) devices, etc., this disclosure does not limit this.
- the client application can be pre-installed on the terminal device, so that the client can be started and run on the terminal device; of course, an online "client" such as HTML5 technology can also be used, and there is no need to install the client on the terminal device. The client can be obtained and run by installing the corresponding application on the device.
- the server 10 is also connected to a manufacturing execution system (MES, Manufacturing Execution System) 14 through a message queue 15.
- MES Manufacturing Execution System
- This system is connected to the production equipment 16 in the production environment.
- the system can be composed of multiple execution units, such as MES x and MES y as shown in the figure.
- the multiple execution units can correspond to different equipment objects, different production lines or different workshops in the production environment, such as MES x and MES y can correspond to workshop 1 and workshop 2 respectively, or can also correspond to production line 1 and production line 2 in a certain workshop, etc., which will not be described again.
- the target device described in this disclosure can be any production device connected to the manufacturing execution system 14 .
- the message queue 15 used to connect the manufacturing execution system and the server 10 can be the message middleware TIB Rendezvous, or can also use Kafka, RabbitMQ, ActiveMQ, etc., and the embodiment of the present disclosure is not limited to this.
- the manufacturing execution system 14 can also be connected to a database 12, which can be a local storage space or an external storage space of the manufacturing execution system 14, which is used to store production data and real equipment status generated during the operation of the manufacturing execution system 14. wait.
- the device information of any device stored in the database 12 can be divided into two categories: basic device information and device status information, where the basic device information can include device name, device identification, interface information, installation location, Function, brand, size, etc.; the equipment status information may include whether it is working (on or down), temperature, pressure, rotation speed, valve opening size, etc., which will not be described again.
- the cache 13 is used to store the status change message of any device received by the server 10 or the changed status information of the device extracted according to the status change message.
- the cache can be a Redis (Remote Dictionary Server) cache. Redis is an efficient memory-based storage system that enables the cache 13 to have high data caching efficiency.
- the manufacturing execution system 14 is not only connected to the production equipment 16, but can also be connected to detection equipment that cooperates with each production equipment, such as electronic switches, solenoid valves and other actuators, and sensors such as thermometers, pressure gauges, flow meters, etc., thereby manufacturing execution
- the system 14 can sense the equipment status of each production equipment in real time through the above detection equipment.
- manufacturing The execution system 14 can update the equipment status information of the target equipment recorded in the database 12 according to the change, so that the equipment status information of the target equipment is saved in the database 12 in real time - because the manufacturing execution system 14 will The database 12 mediator
- the stored device status information is updated in time, so the device status information of the target device read from the database 12 at any time can be used to represent the real device status of the target device at that time.
- the server 10 when receiving the status monitoring request initiated by the client 11 for the target device, the server 10 can read the device status information of the target device at the current moment from the database 12 and use it as the current status of the target device. The information is returned to the client 11 for display in the target monitoring interface. It can be seen that the current status information described in the embodiment of the present disclosure is the device status information of the target device read from the database 12 by the server 10 in response to the status monitoring request initiated by the client 11. In addition, upon receiving the status monitoring request, the server 10 can determine that the client 11 has a status monitoring requirement for the target device.
- the server 10 can register a message acquisition service for the target device with the message queue 15 , so as to obtain the status change message for the target device from the message queue 15; of course, the server 10 may not register the above service, but obtain the status change message for the target device by checking the messages in the message queue 15.
- the server 10 can directly send the changed status information contained in the message to the client 11; or, alternatively, The message or the changed status information can be stored in the cache 13 and sent to the client 11 at a fixed period or returned to the client 11 in response to an update query request initiated by the client 11, so that the client 11 can use the message.
- the status information updates the target monitoring interface.
- the above process of receiving the status change message can be performed by the message receiving module 101, and the process of reading and sending the changed status information can be performed by the message reading module 102.
- the scheduled task module 103 can be used to manage the execution frequency of various scheduled tasks in the status monitoring system.
- the scheduled tasks can include message reading tasks executed by the message reading module 102 and task query modules 104 Information query tasks performed.
- the message reading task is to read the stored status change message or changed status information from the cache 13 according to a fixed period
- the information query task is to read the target device's information from the database 12 according to a fixed period.
- the basic information such as the target layout file changes, please refer to the records in subsequent embodiments for the related processing of the target layout file, which will not be described here.
- the fixed period of the above message reading task should be smaller than the fixed period of the information query task.
- the current status information displayed by the client in the target monitoring interface is used to represent the status of the target device before the change, and the target monitoring interface updated according to the status information after the change is used
- the server senses that the target device has changed (that is, receives the status change message)
- it can notify the client to automatically update the target monitoring interface accordingly.
- on-site workers, operation and maintenance personnel, managers and other users can accurately and timely learn the above changes that have occurred in the target equipment by viewing the target monitoring interface.
- users can learn whether and what kind of changes have occurred in the target equipment through the target monitoring interface without going to the production environment to check on-site. This not only saves labor costs, but also effectively avoids possible interference to the production environment by personnel, that is, This avoids adverse effects on the cleanliness of the production environment and ensures product quality.
- FIG. 2 is a flowchart of a method for updating status information according to an embodiment of the present disclosure. As shown in Figure 2, this method is applied to the server side of the status monitoring system, and the method may include the following steps 202-204.
- Step 202 In response to the status monitoring request initiated by the client for the target device, return the current status information of the target device to the client, so that the client displays the current status information in the target monitoring interface.
- the server Before logging in to the client, the user needs to register his or her user account on the server.
- the server can create (i.e. register) different types of user accounts for different users based on the roles they play in the production process, and allocate corresponding account permissions to each type of account.
- the user account registered in the server may include at least one of the following: administrator account, operation and maintenance account, ordinary account, plan account, etc.
- the operation and maintenance personnel corresponding to the operation and maintenance account can have the permissions of equipment monitoring, machine management, group management, and billboard directory query; the ordinary production workers corresponding to the ordinary account can have the equipment monitoring and billboard directory of the equipment corresponding to their own jobs.
- the production planner corresponding to the planning account can have production scheduling permissions
- the administrator user corresponding to the administrator account can have system setting permissions, group management permissions, status dictionary query permissions, and physical location management permissions etc. for all operating rights of the condition monitoring system.
- the server can maintain a user permission list, which is used to record the permissions owned by the corresponding users of each user account that has completed registration.
- the client can determine the target device according to the default settings, such as determining the device last monitored by the user as the target device or the device that has recently changed as the target device; or, the user You can also specify a certain device to the client through a device selection operation. At this time, the client can determine the device as the target device in response to the operation. It can be understood that the target device determined in the above method is the monitoring object of the client at the current moment, so the client can initiate a status monitoring request for the target device to the server.
- the status monitoring request sent by any client it receives may include the identity information of the user who logged in to the client, such as the user account logged in by the client, the account nickname, etc.
- the server can determine whether the user account corresponding to the user has monitoring permissions for the target device based on the identity information, such as querying the permissions owned by the user account in the above user permissions list.
- the server may refuse to return the current status information of the target device to the server to prevent the user from monitoring the target beyond the limit. equipment.
- the server can also discard the status monitoring request, or return reminder information to the client, so that the client can remind the user or issue an alarm message or even temporarily freeze certain permissions of the user, which will not be described again.
- the server can only return the current status information of the device to the client used by users who have monitoring permissions for the target device, thereby achieving effective control over the monitoring permissions of the device and avoiding the possible consequences of over-limit monitoring. safety hazards.
- the manufacturing execution system in the status monitoring system can respond to changes in the status information of the target equipment and update the status information of the target equipment recorded in its associated database, so that the database always records all the status information of the target equipment.
- the latest status information of the target device it can be understood that the status information of the target device read from the database at any time can be regarded as the real status information of the device.
- the server can read the status information of the target device from the database and transfer the status information to the target device. The information is returned to the client as the current status information of the target device, so that the client displays the information in the target monitoring interface.
- any production equipment in the production environment is usually connected to other equipment according to a certain layout method (ie, equipment layout).
- the above equipment layout is usually recorded in the layout file corresponding to the production equipment.
- the target layout file corresponding to the target device can be used to indicate the device layout of the target device, such as the device hierarchy to which the target device belongs, the installation location of the target device, and the connection method between the target device and other devices. wait.
- the layout file of each device can be saved locally on the server or in the database.
- the corresponding layout file can be saved according to the identification information of the device (such as device ID) as an index, so that it can be queried based on the identification information of a certain device.
- the layout file for this device is usually connected to other equipment according to a certain layout method (ie, equipment layout).
- the above equipment layout is usually recorded in the layout file corresponding to the production equipment.
- the target layout file corresponding to the target device can be used to indicate the device layout of the target device, such as the device hierarchy to which the
- the server can return the target layout file corresponding to the target device to the client, so that it can display the target monitoring interface according to the device layout of the target device indicated by the target layout file. Displays current status information.
- the server can query the target layout file corresponding to the target device according to the identification information contained in the status monitoring request, and return the target layout file to the client, so that the client can follow the The device layout indicated by the target layout file displays the current status information.
- the target layout file may be associated with the current status information and returned to the client.
- the client when the client receives the target layout file and the current status information, it can determine the device layout of the target device indicated by it by parsing the target layout file, and follow the device layout in the target monitoring interface. Display the current status information. Specifically, the client can determine the device shape, size, orientation and other shape information of the target device by parsing the target layout file, thereby drawing a device graphic representing the target device in the target monitoring interface based on the external information, and then in The current status information of the target device is displayed at the corresponding position of the device graphic.
- the target layout file can be regarded as a "drawing" of the target device.
- the target layout file of the target device described in this disclosure may be a graphics file in the SVG (Scalable Vector Graphics) format (hereinafter referred to as the SVG file).
- the SVG file is a graphic file based on XML (Extensible Markup Language, Extensible Markup Language), which can be displayed clearly and without distortion on any screen resolution. Therefore, the SCG file is used as the target layout file of the target device, and the client Clear and distortion-free device graphics can be displayed, thereby ensuring the accuracy of the display of the current status information.
- the server can periodically check whether the target layout file has changed, and if a change occurs, the changed The target layout file is sent to the client so that the server can promptly layout the target according to the changed target.
- Bureau files display current status information.
- the scheduled task module 103 shown in FIG. 1 can set the information query module 104 to execute the information query task according to a fixed period, such as checking whether the target layout file saved in the database 12 is changed according to the period.
- the above fixed period can be set to be appropriately longer, such as 12 hours, 1 day, 1 month, 1 week, etc.
- the embodiments of the present disclosure do not This is not limited.
- the target layout file obtained by the server may contain at least one layout file, and any layout file may contain at least one file element.
- Any file element may correspond to multiple real devices in the production environment, that is, the file element may Reused by multiple real devices.
- the file element may be a basic unit that constitutes the layout file or a combination of multiple basic units. Any file element may correspond to a certain device or a certain functional module in the device.
- Device 1 and Device 2 are two devices of the same model deployed in different workshops, and their device layouts are the same but their device identifiers are different - obviously, Device 1 and Device 2 correspond to the same file element in the same layout file. S.
- the target device determined through the aforementioned method is Device 1
- the client displays the element identifier of file element S in the target monitoring interface
- the user may not be able to distinguish whether the identifier is used to characterize Device 1 or Device 2 in the production environment. , so it is impossible to determine whether the current status information of device 1 or the current status information of device 2 is displayed in the target monitoring interface.
- the server can determine the target element corresponding to the target device in the file, and replace the element identifier of the target element recorded in the target layout file with the The device identifier of the target device is obtained, and then the replaced target layout file is returned to the client. It can be understood that, after obtaining the replaced target layout file, the client can draw the device graphic of the target device in the target monitoring interface based on the external information obtained by parsing the file, and then draw the device graphic at the corresponding position of the device graphic. Displays the device identification of the target device and the current status information of the target device.
- the device identification of device 1 (instead of the element identification of file element S) can be displayed on the device graphic of device 1, so that users can intuitively view the current status information of the target device, avoid understanding obstacles, and help ensure the production process and status. Monitoring proceeds smoothly.
- Step 204 When a status change message for the target device is received, the changed status information of the target device after the change contained in the status change message is sent to the client for use by the client.
- the client updates the target monitoring interface according to the changed status information.
- the server may receive a status change message for the target device sent by the manufacturing execution system, which message contains the post-change status information after the target device has been changed. Thereafter, the server can send the message to the client so that it can update the target monitoring interface according to the information, that is, display the changed status information in the target monitoring interface.
- the changed status information can also be displayed by the server according to the device layout. It can be seen that the target layout file of the target device can Used to display the device information of the target device (the current status information and the changed status information).
- the server can send the changed status information to the client in various ways.
- the server in order to maximize the real-time performance of the device information displayed by the client, the server can extract the changed status information from the received status change message and send the information directly to the client, so that The client displays the changed status information to the user as soon as possible to avoid errors that may be caused by display delays.
- the server may also first change the status information in the status change message. After the change, the status information is written to the cache and read from the cache at the appropriate time to send to the client. For example, when receiving a status change message for the target device, the server may write the changed status information contained in the message into the cache.
- the server may write the changed status information into the cache according to a preset format. For example, for a target device containing 10 status parameters, when the changed status information contains the 1st to 4th status parameters, the server can write these four status parameters into the cache in sequence in a preset order. corresponds to the storage address of the target device.
- the server can write the changed status information at a blank address in the cache; and all the status information has been written in the cache.
- the server can use the changed status information to overwrite the written status information, thereby reducing the occupation of cache space by the changed status information and the amount of data that needs to be sent to the client.
- the server can send the changed status information stored in the cache to the client at a fixed period. For example, in any cycle, if the server receives the first data change message for the target device, it can write the post-change status information contained in the message into the cache; if it receives the first data change message for the same target device during this cycle, For the second status change message, the post-change status information in the second status change message can be used to overwrite the post-change status information already written in the cache (contained in the first status change message).
- the above fixed period can be set according to the actual situation, for example, it can be 1s, 50ms, 2s, 10s, etc.
- the fixed period can be smaller than the server's checking period for whether the target layout file is updated.
- the server can use the changed status information of the latter status change message to overwrite the changed status information of the previous status change message, ensuring that the changed status information of any device only occupies a fixed storage space in the cache, even if Even when status change messages increase dramatically, the cache space can be effectively controlled.
- the server can send the changed status information recorded in each cache (the status information after the latest change from the current moment) to the client for display, and trigger the start of the next cycle of status change message reception. and the process of writing changed status information into the cache.
- the server can also write the changed status information into the cache in the above data overwriting manner, and return the changed status recorded in the cache to the client in response to the update query request initiated by the client. information.
- the server returns the changed status information to the client only when it needs it. This further reduces the amount of data in the changed status information sent by the server to the client.
- the amount of changed status information that the client needs to display can be reduced, that is, the client's workload of updating the target monitoring interface can be reduced, which can help avoid client delays or freezes and other failures, thereby ensuring that users User experience for viewing changed status information.
- the server can delete the data from the cache or set an invalidation flag for it to reclaim the corresponding storage space and realize the cache. Efficient use of.
- FIG. 3 is a flowchart of another method for updating status information according to an embodiment of the present disclosure. As shown in Figure 3, this method is applied to the client of the status monitoring system, and the method may include the following steps 302-304.
- Step 302 In response to the status monitoring operation performed by the user on the target device, initiate a status monitoring request for the target device to the server, and display the target device returned by the server in response to the request in the target monitoring interface. current status information.
- the status monitoring request sent by the client to the server may include the identification information of the device, so that the server can query the target layout file corresponding to the target device based on the identification information, and convert the file Return to client.
- the client can display the current status information in the target monitoring interface according to the device layout indicated by the target layout file. For example, the client can parse the target layout file to obtain external information, draw a device graphic of the target device in the target monitoring interface based on the information, and then display the current status information in a targeted manner at the corresponding position of the graphic.
- the device layout indicated by the target layout file may include at least one of the following: a device level to which the target device belongs, an installation location of the target device, and a connection method between the target device and other devices.
- the menu bar 401 at the top of the interface displays functional options such as “Device Monitoring”, “Device Management”, “Device Grouping”, “Statistical Management” and “System Management”.
- “Device Monitoring” is triggered
- the graphic display box 403 and the information display box 404 can be displayed below.
- the tree structure box 402 on the left below includes options at different levels such as “type”, “factory” and “group”.
- “vacuum pump” is further displayed according to the equipment type.
- the status mark 4021 can be displayed in front of "CLT4" to visually indicate the current status of the device, such as whether it is currently in working or shutdown state, etc.
- the size, shape, color and other display parameters of the above status mark 4021 can use default values or The settings are customized by the user so that the user can understand what they refer to.
- the device graphics of the currently selected target device CLT4 can be displayed in the graphics display box 403 in the middle below.
- the shape, color, texture, lines and other target display parameters of the graphics can be used to represent the status information of CLT4.
- the device information of the target device CLT4 can be displayed in the information display box 404 on the right below, as described above. Prepare basic information, summarized status information, etc., which will not be described again.
- Step 304 Upon receiving the changed status information of the target device sent by the server, update the target monitoring interface according to the changed status information.
- the process of the client updating the target monitoring interface according to the changed status information is a process of updating the current status information displayed in the target monitoring interface to the newly received changed status information.
- the client when it receives the changed status information sent by the server, it can update the shape, color, texture, lines and other objects of the device graphics shown in the graphics display box 403 based on the information. Display parameters, and/or the status information displayed in the information display box 404 can also be updated.
- the embodiment of the present disclosure does not limit the specific update method of the target monitoring interface.
- the client can respond to the status monitoring operation performed by the user on the target device and initiate a status monitoring request for the device to the server.
- the server may return the current status information of the device to the client in response to the request, so that the client displays the current status information in the target monitoring interface.
- the server may send the changed status information of the target device after the change contained in the message to the client, so that the server can change the status according to the changed status information of the target device.
- Status information updates the target monitoring interface.
- the current status information displayed by the client in the target monitoring interface is used to represent the status of the target device before the change, and the target monitoring interface updated based on the status information after the change is used to represent the new status of the device after the change.
- the server senses that the target device has changed (that is, receives the status change message)
- it can notify the client to automatically update the target monitoring interface accordingly
- on-site workers, operation and maintenance personnel, and managers can Users can accurately and timely learn the above changes in the target device by viewing the target monitoring interface.
- users can learn whether and what kind of changes have occurred in the target equipment through the target monitoring interface without going to the production environment to check on-site. This not only saves labor costs, but also effectively avoids possible interference to the production environment by personnel, that is, This avoids adverse effects on the cleanliness of the production environment and ensures product quality.
- the user can also perform corresponding management operations on the target monitoring interface, which will be described below with reference to Figure 4.
- the client when the current status information or changed status information is displayed in the target monitoring interface, the user can perform a status refresh operation in the interface, such as clicking a shortcut key or as shown in Figure 1
- the above status refresh operation is implemented through the right-click menu in the graphic display box 403. Therefore, the client can initiate an update query request for the target device CLT4 to the server in response to this operation, so that the server returns the latest changed status information in response to the request.
- the changed status information returned by the server may be the changed status information of the target device read from the cache.
- the client after receiving the changed status information, the client can further update the target monitoring interface to display the information in the interface.
- the server can check whether the changed status information of the target device has been stored in the cache: if it is not stored, it indicates that it has been changed since the time of the last change. In the period up to the current moment, the target device has not changed here. At this time, there is no need to return the changed status information to the server. Instead, an empty message or other preset special messages can be returned; if it has been stored, it indicates that the target device The device has changed at least once within the above period of time, and the post-change status information stored at this time is the post-change status information after the latest change. At this time, the information can be read from the cache and sent to the client.
- the user in addition to viewing the status information of the target device in the target monitoring interface, the user can also view the status information of other devices.
- the user can perform a first switching operation in the target monitoring interface (such as triggering the "device grouping" function option in the menu bar 401 shown in Figure 4), and the client can determine its corresponding switched interface in response to the operation.
- the switched interface may be a centralized monitoring interface, which is used to centrally display the status information of each device in the device set corresponding to the operation, and the switched device corresponding to the interface is each device in the device set.
- the device collection may be a "type", "factory", “group” or other form of device collection, which is not limited in this embodiment of the disclosure.
- the switched interface may also be a monitoring interface of any device. The interface may be used to display the status information of any device, and the switched device corresponding to the interface is the any device.
- the client can initiate an update query request to the server for the post-switch device corresponding to the post-switch interface, and display in the post-switch interface the changes to the post-switch device returned by the server in response to the request.
- Post status information It can be understood that when the above-mentioned switching interface is a centralized monitoring interface, the user can perform batch and centralized monitoring of each device in the device set to improve monitoring efficiency; while after the above-mentioned switching interface is the monitoring of any device In the case of interface, users can monitor the status of the device in a targeted manner.
- the user in order to manage the display effect of status information, can configure corresponding display parameters.
- the user can perform a real-time second switching operation to switch the target monitoring interface to a parameter configuration interface.
- the user can trigger the "System Management" function option in the menu bar 401, thereby controlling the client to jump from the target monitoring interface shown in Figure 4 to the parameter configuration interface (not shown in the figure).
- the user can perform a parameter configuration operation in the parameter configuration interface, and the client can configure the display parameters accordingly in response to the operation.
- the above parameter configuration operation is to change the shape, color, texture, lines and other display parameters of a certain state, such as changing the downtime state from black to gray, changing the rotating part from circular to sector, etc.
- the display parameters after the above configuration is completed can be used to display the status information of the corresponding device in the target monitoring interface and/or the monitoring interface of other devices.
- the client can send the configured display parameters to the server, and the server can send them to other users corresponding to the user (such as ordinary user) client. Therefore, other users' clients can display device information in the target monitoring interface according to the display parameters after the above configuration is completed. In this way, administrator users can uniformly configure and change display parameters, which helps improve configuration efficiency.
- the user who performs the parameter configuration operation is an ordinary user. In this case, the client can store the configured display parameters locally. After that, the device information can be displayed in the target monitoring interface according to the above configured display parameters. Through this method, ordinary users can customize the configuration of display parameters so that the display effect of device information conforms to their own viewing habits.
- the user can view operating indicators of the target device.
- the user can perform an indicator viewing operation in the target monitoring interface, such as triggering the "Statistical Management" function option in the menu bar 401 shown in Figure 1 . Therefore, the client can respond to this operation and count the operating indicators of the target device according to the device status of the device; or obtain the operating indicators of the target device from the server, and the operating indicators are obtained by the server based on the device status of the target device.
- the client can display the running indicator in the post-switch interface corresponding to the indicator viewing operation.
- the above-mentioned switched interface may be the target monitoring interface, or may be an indicator statistics page jumped from the target monitoring interface, etc.; the above-mentioned statistical indicators may be activation rate (activation or utilization) within a preset period of time.
- the proportion of time that the equipment takes to create value within the time it can provide), status percentage statistics, equipment history and product history, etc., are not limited by the embodiments of the present disclosure.
- the client can display the statistical indicators of the target device to the user, so that the overall working condition of the target device can be easily and quickly known.
- the present disclosure also provides embodiments of a status information updating apparatus.
- An embodiment of the present disclosure proposes a device for updating status information.
- the device is used in applications.
- the device includes one or more processors, and the processor is configured to: respond to a status monitoring request initiated by a client for a target device. , return the current status information of the target device to the client, so that the client displays the current status information in the target monitoring interface; in the case of receiving a status change message for the target device , sending the changed status information after the change of the target device included in the status change message to the client, so that the client updates the target monitoring interface according to the changed status information.
- the processor is further configured to: query the target layout file corresponding to the target device according to the identification information contained in the status monitoring request, and return the target layout file to the client , displaying the current status information in the device layout indicated by the client according to the target layout file.
- the processor is further configured to: determine the target element corresponding to the target device in the target layout file, and replace the element identification of the target element recorded in the target layout file is the device identifier of the target device; return the replaced target layout file to the client.
- the status monitoring request includes the identity information of the user who logged in to the client, and the processor is further configured to: when the identity information indicates that the user has monitoring permissions for the target device In this case, the current status information of the target device is returned to the client.
- the processor is further configured to: read the current status information of the target device from a database associated with a manufacturing execution system, the manufacturing execution system being configured to respond to the status of the target device When the information changes, the status change message is initiated and the information of the target device recorded in the database is updated. status information.
- the processor is further configured to: upon receiving a status change message for the target device, write the changed status information contained in the status change message into the cache; according to a fixed Periodically sending the changed status information in the cache to the client; or, in response to an update query request initiated by the client, returning the changed status information recorded in the cache to the client.
- the processor is further configured to: write the changed status information at a blank address of the cache if the status information of the target device has not been written in the cache. ; When the status information of the target device has been written in the cache, use the changed status information to overwrite the written status information.
- the processor is further configured to write the changed status information into a cache according to a preset format.
- An embodiment of the present disclosure proposes another device for updating status information.
- the device includes one or more processors, and the processor is configured to: in response to a status monitoring operation performed by the user on the target device, initiate an update to the server to the server.
- the status monitoring request of the target device and display the current status information of the target device returned by the server in response to the request in the target monitoring interface; after receiving the change of the target device sent by the server
- the target monitoring interface is updated according to the post-change status information.
- the status monitoring request includes identification information of the device
- the processor is further configured to: receive the target layout file corresponding to the target device queried by the server based on the identification information. ; Display the current status information in the target monitoring interface according to the device layout indicated by the target layout file.
- the device layout indicated by the target layout file includes at least one of the following: a device hierarchy to which the target device belongs, an installation location of the target device, and a connection between the target device and other devices. Way.
- the processor is further configured to: in response to an indicator viewing operation performed by the user, collect statistics on the operating indicators of the target device according to the device status of the target device; or, to report the operation indicators to the server. Obtain the operation indicators of the target device obtained according to the statistics of the device status of the target device; display the operation indicators in the post-switch interface corresponding to the indicator viewing operation.
- the processor is further configured to: in response to a status refresh operation performed by the user on the target device, initiate an update query request for the target device to the server, so that the The server returns the changed status information in response to the request.
- the processor is further configured to: in response to the first switching operation performed by the user, determine a post-switch interface corresponding to the operation, where the post-switch interface includes a centralized monitoring interface or a user interface of any device.
- Monitoring interface wherein the centralized monitoring interface is used to collectively display each device set corresponding to the operation.
- the status information of the device, the monitoring interface of any device is used to display the status information of the device; initiate an update query request to the server for the switched device corresponding to the switched interface, and after the switch
- the changed status information of the switched device returned by the server in response to the request is displayed on the interface.
- the processor is further configured to: in response to a second switching operation performed by the user, switch the target monitoring interface to a parameter configuration interface; in response to the user's operation in the parameter configuration interface
- the parameter configuration operation implemented in configures the display parameters accordingly, and the configured display parameters are used to display the status information of the corresponding device in the target monitoring interface and/or the monitoring interface of other devices.
- An embodiment of the present disclosure also provides an electronic device, including: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to implement the update of status information described in any of the above embodiments method.
- Embodiments of the present disclosure also provide a non-transitory computer-readable storage medium on which a computer program is stored.
- the program is executed by a processor, the steps in the state information updating method described in any of the above embodiments are implemented.
- FIG. 5 is a schematic block diagram of a device 500 for data authentication or driving mode determination according to an embodiment of the present disclosure.
- the device 500 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, or the like.
- the device 500 may include one or more of the following components: a processing component 502, a memory 504, a power supply component 506, a multimedia component 508, an audio component 510, an input/output (I/O) interface 512, a sensor component 514, and communications component 516.
- Processing component 502 generally controls the overall operations of device 500, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
- the processing component 502 may include one or more processors 520 to execute instructions to complete all or part of the steps of the above method for updating status information.
- processing component 502 may include one or more modules that facilitate interaction between processing component 502 and other components.
- processing component 502 may include a multimedia module to facilitate interaction between multimedia component 508 and processing component 502.
- Memory 504 is configured to store various types of data to support operations at device 500 . Examples of such data include instructions for any application or method operating on device 500, contact data, phonebook data, messages, pictures, videos, etc.
- Memory 504 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
- SRAM static random access memory
- EEPROM electrically erasable programmable read-only memory
- EEPROM erasable programmable read-only memory
- EPROM Programmable read-only memory
- PROM programmable read-only memory
- ROM read-only memory
- magnetic memory flash memory, magnetic or optical disk.
- Power supply component 506 provides power to the various components of device 500 .
- Power supply component 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 500 .
- Multimedia component 508 includes a screen that provides an output interface between the device 500 and the user.
- the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
- the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide action.
- multimedia component 508 includes a front-facing camera and/or a rear-facing camera.
- the front camera and/or the rear camera may receive external multimedia data.
- Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
- Audio component 510 is configured to output and/or input audio signals.
- audio component 510 includes a microphone (MIC) configured to receive external audio signals when device 500 is in operating modes, such as call mode, recording mode, and speech recognition mode. The received audio signals may be further stored in memory 504 or sent via communication component 516 .
- audio component 510 also includes a speaker for outputting audio signals.
- the I/O interface 512 provides an interface between the processing component 502 and a peripheral interface module, which may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
- Sensor component 514 includes one or more sensors for providing various aspects of status assessment for device 500 .
- the sensor component 514 can detect the open/closed state of the device 500, the relative positioning of components, such as the display and keypad of the device 500, and the sensor component 514 can also detect a change in position of the device 500 or a component of the device 500. , the presence or absence of user contact with the device 500 , device 500 orientation or acceleration/deceleration and temperature changes of the device 500 .
- Sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
- Sensor assembly 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
- the sensor component 514 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
- Communication component 516 is configured to facilitate wired or wireless communication between apparatus 500 and other devices.
- the device 500 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G LTE, 6G NR, or a combination thereof.
- the communication component 516 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
- the communications component 516 also includes a near field communications (NFC) module to facilitate short-range communications.
- NFC near field communications
- the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
- RFID radio frequency identification
- IrDA infrared data association
- UWB ultra-wideband
- Bluetooth Bluetooth
- apparatus 500 may be implemented by one or more application specific integrated circuits (ASICs), Digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic components, implemented with To execute the update method of the above status information.
- ASICs application specific integrated circuits
- DSP Digital signal processor
- DSPD digital signal processing device
- PLD programmable logic device
- FPGA field programmable gate array
- controller microcontroller, microprocessor or other electronic components, implemented with To execute the update method of the above status information.
- a non-transitory computer-readable storage medium including instructions such as a memory 504 including instructions, is also provided, and the above instructions can be executed by the processor 520 of the device 500 to complete the above-mentioned updating method of status information.
- the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Data Mining & Analysis (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Testing And Monitoring For Control Systems (AREA)
- General Factory Administration (AREA)
Abstract
一种状态监控***、状态信息的更新方法及装置。所述方法包括:响应于客户端针对目标设备发起的状态监控请求,将所述目标设备的当前状态信息返回至所述客户端,以由所述客户端在目标监控界面中展示所述当前状态信息;在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述目标设备发生变更后的变更后状态信息发送至所述客户端,以由所述客户端根据所述变更后状态信息更新所述目标监控界面。该方法可以实现对设备状态的自动化监控以及状态信息的自动化更新,从而减少人员对生产环境的干扰,提升生产环境的洁净程度,保证产品质量。
Description
本公开涉及计算机技术领域,具体而言,涉及状态监控***、状态信息的更新方法及装置。
在工厂车间、流水线等生产环境中,工人需要获知各个生产设备的状态信息(包括运行与否、具体参数等)是否发生变化以及发生何种变化,以便进行生产。
在相关技术中,通常由工人去生产环境观察记录以获知上述状态信息及其变更。该方式不仅耗费人力,而且可能会向生产过程引入杂质,影响生产环境的洁净度,进而影响产品质量。
发明内容
有鉴于此,本公开的实施例提出了一种状态监控***、状态信息的更新方法及装置,以实现对生产设备的状态信息的自动化监控,从而解决相关技术中存在的不足。
根据本公开实施例的第一方面,提出一种状态信息的更新方法,包括:响应于客户端针对目标设备发起的状态监控请求,将所述目标设备的当前状态信息返回至所述客户端,以由所述客户端在目标监控界面中展示所述当前状态信息;在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述目标设备发生变更后的变更后状态信息发送至所述客户端,以由所述客户端根据所述变更后状态信息更新所述目标监控界面。
可选的,还包括:根据所述状态监控请求中包含的标识信息查询所述目标设备对应的目标布局文件,并将所述目标布局文件返回至所述客户端,以由所述客户端按照所述目标布局文件指示的设备布局展示所述当前状态信息。
可选的,还包括:确定所述目标布局文件中对应于所述目标设备的目标元素,并将所述目标布局文件中记录的所述目标元素的元素标识替换为所述目标设备的设备标识;所述将所述目标布局文件返回至所述客户端,包括:将替换后的所述目标布局文件返回至所述客户端。
可选的,所述状态监控请求中包含登录所述客户端的用户的身份信息,所述将所述目标设备的当前状态信息返回至所述客户端,包括:在所述身份信息表明所述用户拥有针对所述目标设备的监控权限的情况下,将所述目标设备的当前状态信息返回至所述客户端。
可选的,通过下述方式获取所述目标设备的当前状态信息:从制造执行***所关联的数据库中读取所述目标设备的当前状态信息,所述制造执行***用于响应于所述目标设备的状态信息发生变更,发起所述状态变更消息并更新所述数据库中记录的所述目标设备的状态信息。
可选的,所述在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述目标设备发生变更后的变更后状态信息发送至所述客户端,包括:在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息中包含的变更后状态信息写入缓存;按照固定周期向所述客户端发送所述缓存中的所述变更后状态信息;或者,响应于所述客户端发起的更新查询请求向所述客户端返回所述缓存中记录的所述变更后状态信息。
可选的,所述将所述状态变更消息中包含的变更后状态信息写入缓存,包括:在所述缓存中尚未写入所述目标设备的状态信息的情况下,在所述缓存的空白地址处写入所述变更后状态信息;在所述缓存中已写入所述目标设备的状态信息的情况下,使用所述变更后状态信息覆盖已写入的所述状态信息。
可选的,所述将所述状态变更消息中包含的变更后状态信息写入缓存,包括:按照预设格式将所述变更后状态信息写入缓存。
根据本公开实施例的第二方面,提出另一种状态信息的更新方法,包括:响应于用户针对目标设备实施的状态监控操作,向服务端发起针对所述目标设备的状态监控请求,并在目标监控界面中展示所述服务端响应于该请求返回的所述目标设备的当前状态信息;在接收到所述服务端发送的所述目标设备的变更后状态信息的情况下,根据所述变更后状态信息更新所述目标监控界面。
可选的,所述状态监控请求包含所述设备的标识信息,所述方法还包括:接收所述服务端根据所述标识信息查询到的所述目标设备对应的目标布局文件;所述在目标监控界面中展示所述当前状态信息,包括:在目标监控界面中按照所述目标布局文件指示的设备布局展示所述当前状态信息。
可选的,所述目标布局文件指示的设备布局包括下述至少之一:所述目标设备所属的设备层级、所述目标设备的安装位置、所述目标设备与其他设备之间的连接方式。
可选的,还包括:响应于所述用户实施的指标查看操作,根据所述目标设备的设备状态统计所述目标设备的运行指标;或者,向所述服务端获取根据所述目标设备的设备状态统计得到的所述目标设备的运行指标;在所述指标查看操作对应的切换后界面中展示所述运行指标。
可选的,还包括:响应于所述用户针对所述目标设备实施的状态刷新操作,向
所述服务端发起针对所述目标设备的更新查询请求,以使所述服务端响应于该请求返回所述变更后状态信息。
可选的,还包括:响应于所述用户实施的第一切换操作,确定该操作对应的切换后界面,所述切换后界面包括集中监控界面或者任一设备的监控界面,其中,所述集中监控界面用于集中展示所述操作对应的设备集合中各个设备的状态信息,所述任一设备的监控界面用于展示该设备的状态信息;向所述服务端发起针对所述切换后界面所对应切换后设备的更新查询请求,并在所述切换后界面中展示所述服务端响应于该请求返回的所述切换后设备的变更后状态信息。
可选的,还包括:响应于所述用户实施的第二切换操作,将所述目标监控界面切换为参数配置界面;响应于所述用户在所述参数配置界面中实施的参数配置操作对显示参数进行相应配置,配置完成的所述显示参数被用于在所述目标监控界面和/或其他设备的监控界面中显示相应设备的状态信息。
根据本公开实施例的第三方面,提出一种状态监控***,包括客户端和服务端,其中,所述客户端用于向所述服务端发起针对目标设备的状态监控请求,并在目标监控界面中展示所述服务端响应于该请求返回的所述目标设备的当前状态信息;以及,在接收到所述服务端发送的所述目标设备发生变更后的变更后状态信息的情况下,根据所述变更后状态信息更新所述目标监控界面;所述服务端用于响应于所述状态监控请求,向所述客户端返回所述当前状态信息;以及,在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述变更后状态信息发送至所述客户端。
可选的,还包括制造执行***和数据库,其中,所述数据库用于存储目标设备的状态信息,所述状态信息由制造执行***响应于所述目标设备的状态信息发生变更触发存储至所述数据库,所述制造执行***还响应于所述目标设备的状态信息发生变更向所述服务端发送所述状态变更消息。
可选的,还包括缓存,所述缓存用于存储所述目标设备发生变更后的变更后状态信息,所述变更后状态信息由所述服务端响应于所述状态变更消息写入所述缓存。
根据本公开实施例的第四方面,提出一种状态信息的更新装置,所述装置包括一个或多个处理器,所述处理器被配置为:响应于客户端针对目标设备发起的状态监控请求,将所述目标设备的当前状态信息返回至所述客户端,以由所述客户端在目标监控界面中展示所述当前状态信息;在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述目标设备发生变更后的变更后状态信息发送至所述客户端,以由所述客户端根据所述变更后状态信息更新所述目标监控界面。
根据本公开实施例的第五方面,提出另一种状态信息的更新装置,所述装置包括一个或多个处理器,所述处理器被配置为:响应于用户针对目标设备实施的状态监
控操作,向服务端发起针对所述目标设备的状态监控请求,并在目标监控界面中展示所述服务端响应于该请求返回的所述目标设备的当前状态信息;在接收到所述服务端发送的所述目标设备的变更后状态信息的情况下,根据所述变更后状态信息更新所述目标监控界面。
根据本公开实施例的第六方面,提出一种电子设备,包括:处理器;用于存储处理器可执行指令的存储器;其中,所述处理器被配置为实现上述第一方面或第二方面所述的方法。
根据本公开实施例的第七方面,提出一种非瞬态计算机可读存储介质,其上存储有计算机程序,该程序被处理器执行时实现上述第一方面或第二方面所述方法的步骤。
根据本公开的实施例,客户端可以响应于用户针对目标设备实施的状态监控操作,向服务端发起针对该设备的状态监控请求。服务端可以响应于该请求将该设备的当前状态信息返回至所述客户端,以由该客户端在目标监控界面中展示所述当前状态信息。进一步的,在接收到针对所述目标设备的状态变更消息的情况下,服务端可以将该消息包含的目标设备发生变更后的变更后状态信息发送至客户端,以由其根据所述变更后状态信息更新所述目标监控界面。
可见,客户端在目标监控界面中展示出的当前状态信息用于表征目标设备在发生变更前的状态,而根据变更后状态信息更新后的目标监控界面用于表征该设备发生变更后的新状态,通过该方式,服务端在感知到目标设备发生变更(即接收到所述状态变更消息)的情况下,可以通知该客户端相应地自动更新目标监控界面,现场工人、运维人员、管理人员等用户能够通过查看目标监控界面,准确、及时地获知目标设备所发生的上述变更。通过该方案,用户无需去生产环境现场查看即可通过目标监控界面获知目标设备是否发生变更以及发生何种变更,从而不仅节省了人力成本,而且有效避免了人员对生产环境可能产生的干扰,即避免了对生产环境的洁净度造成不利影响,从而保证产品质量。
应当理解的是,以上的一般描述和后文的细节描述仅是示例性和解释性的,并不能限制本公开。
为了更清楚地说明本公开实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简单的介绍,显而易见地,下面描述中的附图仅仅是本公开的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1是根据本公开实施例示出的一种状态监控***的架构示意图。
图2是根据本公开实施例示出的一种状态信息的更新方法的流程图。
图3是根据本公开实施例示出的另一种状态信息的更新方法的流程图。
图4是根据本公开实施例示出的一种目标监控界面的示意图。
图5是根据本公开实施例示出的一种节点设备的结构示意图。
下面将结合本公开实施例中的附图,对本公开实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本公开一部分实施例,而不是全部的实施例。基于本公开中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本公开保护的范围。
本公开所述的状态信息更新***包括客户端和服务端,其中,所述客户端用于向所述服务端发起针对目标设备的状态监控请求,并在目标监控界面中展示所述服务端响应于该请求返回的所述目标设备的当前状态信息;以及,在接收到所述服务端发送的所述目标设备发生变更后的变更后状态信息的情况下,根据所述变更后状态信息更新所述目标监控界面;所述服务端用于响应于所述状态监控请求,向所述客户端返回所述当前状态信息;以及,在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述变更后状态信息发送至所述客户端。
在一实施例中,所述***还包括数据库,其中,所述数据库用于存储目标设备的状态信息,所述状态信息由制造执行***响应于所述目标设备的状态信息发生变更触发存储至所述数据库,所述制造执行***还响应于所述目标设备的状态信息发生变更向所述服务端发送所述状态变更消息。
在一实施例中,所述***还包括缓存,所述缓存用于存储所述目标设备发生变更后的变更后状态信息,所述变更后状态信息由所述服务端响应于所述状态变更消息写入所述缓存。
图1是根据本公开实施例示出的一种状态监控***的架构示意图。下面结合图1对所述状态监控***的各个组成部分进行说明。如图1所示,服务端10及其所连接的客户端11、数据库(DB,DataBase)12和缓存13构成本公开所述的状态监控***。
所述服务端10可以是FMB(Factory Monitoring Board,工厂监控看板)平台的服务端,所述客户端11可以运行于现场工人、运维人员或管理人员等用户所使用的终端设备中,用户可以通过该客户端登录所述FMB平台,以对处于生产现场的目标设备的设备状态进行监控。其中,所述服务端可以为包含一独立主机的物理服务器,或者也可以为主机集群承载的虚拟服务器、云服务器等,该服务端10可以包括多个功能模块,如消息接收模块101、消息读取模块102、定时任务模块103和信息查询模块
104,各个模块的具体功能可参见下述实施例,此处暂不赘述。所述终端设备可以为手机、平板设备、笔记本电脑、掌上电脑(PDAs,Personal Digital Assistants)、可穿戴设备(如智能眼镜、智能手表等)、VR(Virtual Reality,虚拟现实)设备、AR(Augmented Reality,增强现实)设备等,本公开并不对此进行限制。所述客户端的应用程序可以被预先安装在终端设备上,使得该客户端可以在该终端设备上被启动并运行;当然,也可以使用诸如HTML5技术的在线“客户端”,此时无需在终端设备上安装相应的应用程序,即可获得并运行所述客户端。
所述服务端10还通过消息队列15连接有制造执行***(MES,Manufacturing Execution System)14,作为面向制造企业车间执行层的生产信息化管理***,该***连接有成产环境中的生产设备16。该***可以由多个执行单元构成,如图所示的MES x和MES y等,其中的多个执行单元可以分别对应于生产环境中的不同设备对象、不同生产线或不同车间等,如MES x和MES y可以分别对应于车间1和车间2,或者也可以分别对应于某一车间中的生产线1和生产线2等,不再赘述。其中,本公开所述的目标设备即可为制造执行***14所连接的任一生产设备。用于连接所述制造执行***与服务端10的消息队列15可以为消息中间件TIB Rendezvous,或者也可以采用Kafka、RabbitMQ、ActiveMQ等,本公开实施例并不对此进行限定。
所述制造执行***14还可以连接至数据库12,该数据库可以为制造执行***14的本地存储空间或者外接存储空间,其用于存储制造执行***14在运行过程中产生的生产数据、真实设备状态等。实际上,数据库12中所存储的任一设备的设备信息可以分为两类:设备基础信息和设备状态信息,其中,所述设备基础信息可以包括设备名称、设备标识、接口信息、安装位置、功能、品牌、大小等;所述设备状态信息可以包括是否在工作(开机还是宕机)、温度、压力、转速、阀门开口大小等,不再赘述。
所述缓存13用于存储服务端10接收到的任一设备的状态变更消息或者根据该状态变更消息提取出的该设备的变更后状态信息。具体的,该缓存可以为Redis(Remote Dictionary Server,远程字典服务器)缓存,Redis是一种基于内存的高效存储***,能够使缓存13具有较高的数据缓存效率。
下面对所述状态监控***的运行过程进行简要说明。制造执行***14不仅连接有所述生产设备16,还可以连接有与各个生产设备相互配合的检测设备,如电子开关、电磁阀等执行器以及温度计、压力表、流量计等传感器,从而制造执行***14可以通过上述检测设备实时感知各个生产设备的设备状态。在感知到目标设备(可以为任一生产设备)的设备状态发生变更(如设备启动或宕机、开关开启或闭合、温度升高或降低、流量增大或减小等)的情况下,制造执行***14可以根据所述变更对所述数据库12中记录的所述目标设备的设备状态信息进行更新,使得数据库12中实时保存所述目标设备的设备状态信息——因为制造执行***14会对所述数据库12中保
存的设备状态信息进行及时更新,所以任一时刻从数据库12中读取到的目标设备的设备状态信息,均可用于表征目标设备在该时刻的真实设备状态。
基于此,在接收到客户端11针对目标设备发起的状态监控请求的情况下,服务端10可以从数据库12中读取目标设备在当前时刻的设备状态信息,并将其作为目标设备的当前状态信息返回至客户端11用于在目标监控界面中展示。可见,本公开实施例所述的当前状态信息即为服务端10响应于客户端11发起的状态监控请求,从数据库12中读取到的目标设备的设备状态信息。另外,在接收到所述状态监控请求的情况下,服务端10即可确定客户端11存在针对目标设备的状态监控需求,此时服务端10可以向消息队列15注册针对目标设备的消息获取服务,以便此后从消息队列15处获取针对目标设备的状态变更消息;当然服务端10也可以不注册上述服务,而通过检查所述消息队列15中的消息以获取针对目标设备的状态变更消息。
在将所述当前状态信息返回至客户端11之后,若再次接收到针对目标设备的状态变更消息,则服务端10可以直接将该消息包含的变更后状态信息发送至客户端11;或者,也可以将该消息或所述变更后状态信息存储在缓存13中,并按照固定周期发送客户端11或者响应于客户端11发起的更新查询请求将其返回至客户端11,以便客户端11使用该变更后状态信息更新所述目标监控界面。其中,上述状态变更消息的接收过程可以由消息接收模块101执行,变更后状态信息的读取及发送过程可以由消息读取模块102执行。其中,所述定时任务模块103可以用于管理所述状态监控***中各类定时任务的执行频率,所述定时任务可以包括由消息读取模块102执行的消息读取任务和由任务查询模块104执行的信息查询任务。所述消息读取任务即为按照固定周期从所述缓存13中读取被存储的状态变更消息或变更后状态信息,所述信息查询任务即为按照固定周期从数据库12中读取目标设备的目标布局文件等基础信息是否发生变化,关于目标布局文件的相关处理可以参见后续实施例的记载,此处暂不赘述。其中,上述消息读取任务的固定周期应当小于所述信息查询任务的固定周期。
由上述针对所述状态监控***的介绍可见,客户端在目标监控界面中展示出的当前状态信息用于表征目标设备在发生变更前的状态,而根据变更后状态信息更新后的目标监控界面用于表征该设备发生变更后的新状态,通过该方式,服务端在感知到目标设备发生变更(即接收到所述状态变更消息)的情况下,可以通知该客户端相应的自动更新目标监控界面,现场工人、运维人员、管理人员等用户能够通过查看目标监控界面,准确、及时地获知目标设备所发生的上述变更。通过该方案,用户无需去生产环境现场查看即可通过目标监控界面获知目标设备是否发生变更以及发生何种变更,从而不仅节省了人力成本,而且有效避免了人员对生产环境可能产生的干扰,即避免了对生产环境的洁净度造成不利影响,从而保证产品质量。
下面结合图2~图4及其分别对应的实施例,对基于前述状态监控***实现的状态信息的更新方案进行详细说明。
图2是根据本公开实施例示出的一种状态信息的更新方法的流程图。如图2所述,该方法应用于状态监控***的服务端,该方法可以包括下述步骤202-204。
步骤202,响应于客户端针对目标设备发起的状态监控请求,将所述目标设备的当前状态信息返回至所述客户端,以由所述客户端在目标监控界面中展示所述当前状态信息。
在登录所述客户端之前,用户需要在所述服务端注册自身的用户账号。为实现对生产过程的有效管控,服务端可以根据用户在生产过程中所扮演的角色为不同用户创建(即注册)不同类型的用户账号,并为各类账户分别分配相应的账户权限。例如,所述服务端中注册的用户账号可以包括下述至少之一:管理员账户、运维账户、普通账户、计划账户等。其中,运维账户对应的运维人员可以拥有设备监控、机台管理、群组管理、看板目录查询等权限;普通账户对应的普通生产工人可以拥有自身工作岗位所对应设备的设备监控、看板目录查询、故障上报等权限;计划账户对应的生产计划人员可以拥有排产计划权限;而管理员账户对应的管理员用户可以拥有***设置权限、群组管理权限、状态字典查询权限、物理位置管理权限等针对状态监控***的全部操作权限。当然,不同账户的具体权限可以根据实际生产场景进行合理设置,本公开实施例并不对此进行限定。基于此,服务端可以维护用户权限列表,该列表用于记录已完成注册的各个用户账号所对应用户拥有的权限。
用户在客户端中登录用户账号完成后,客户端可以按照默认设置确定目标设备,如将该用户上次监控的设备确定为目标设备或者将最近发生变更的设备确定为目标设备等;或者,用户也可以通过设备选取操作向客户端指定某一设备,此时客户端可以响应于该操作将该设备确定为目标设备。可以理解的是,上述方式确定出的目标设备即为客户端在当前时刻的监控对象,因此客户端可以向服务端发起针对该目标设备的状态监控请求。
对于服务端而言,其接收到的任一客户端发送的状态监控请求中可以包含登录所述客户端的用户的身份信息,如客户端登录的用户账号、账号昵称等。服务端可以根据该身份信息判断该用户所对应用户账号是否拥有针对所述目标设备的监控权限,如在上述用户权限列表中查询所述用户账户所拥有的权限。进而,在所述身份信息表明所述用户不拥有针对所述目标设备的监控权限的情况下,服务端可以拒绝向其返回目标设备的当前状态信息,以避免所述用户超限监控所述目标设备。另外,服务端也可以丢弃所述状态监控请求,或者向客户端返回提醒信息,以便客户端提醒所述用户或者发出告警信息甚至暂时冻结所述用户的某些权限等,不再赘述。通过该方式,服务端可以仅向拥有针对目标设备的监控权限的用户所使用的客户端返回该设备的当前状态信息,从而实现对该设备监控权限的有效控制,避免了超限监控可能带来的安全隐患。
如前所述,状态监控***中的制造执行***可以响应于所述目标设备的状态信息发生变更,更新自身所关联的数据库中记录的所述目标设备的状态信息,从而使得该数据库始终记录所述目标设备的最新状态信息,可以理解的是,在任一时刻从该数据库中读取的目标设备的状态信息,均可视为该设备的真实状态信息。基于此,在接收到客户端发起的所述状态监控请求或者确定所述用户拥有针对目标设备的监控权限的情况下,服务端可以从所述数据库中读取目标设备的状态信息,并将该信息作为目标设备的当前状态信息返回至客户端,以由客户端在目标监控界面中展示该信息。
生产环境中的任一生产设备通常按照一定的布局方式(即设备布局)与其他设备相连接,上述设备布局通常记录于该生成设备对应的布局文件中。例如,目标设备所对应的目标布局文件可以用于指示目标设备的设备布局,如所述目标设备所属的设备层级、所述目标设备的安装位置、所述目标设备与其他设备之间的连接方式等。各个设备的布局文件可以保存于所述服务端本地或者所述数据库中,具体的,可以按照设备的标识信息(如设备ID)作为索引保存相应的布局文件,以便根据某一设备的标识信息查询该设备的布局文件。
基于此,为提升当前状态信息的可读性,服务端可以将目标设备对应的目标布局文件返回至所述客户端,以便其按照上述目标布局文件所指示的目标设备的设备布局在目标监控界面中展示当前状态信息。例如,服务端可以根据所述状态监控请求中包含的标识信息查询所述目标设备对应的目标布局文件,并将所述目标布局文件返回至所述客户端,以由所述客户端按照所述目标布局文件指示的设备布局展示所述当前状态信息。其中,所述目标布局文件可以与所述当前状态信息关联返回至客户端。相应的,客户端在接收到所述目标布局文件和当前状态信息的情况下,可以通过解析所述目标布局文件确定其所指示的目标设备的设备布局,并在目标监控界面中按照该设备布局展示所述当前状态信息。具体的,客户端可以通过解析所述目标布局文件确定目标设备的设备形状、大小、方位等外形信息,从而根据所述外部信息在目标监控界面中绘制用于表征目标设备的设备图形,进而在该设备图形的相应位置处展示目标设备的当前状态信息。
可见,所述目标布局文件可以视为所述目标设备的“图纸”。本公开所述目标设备的目标布局文件可以为SVG(Scalable Vector Graphics,可缩放矢量图形)格式的图形文件(下称SVG文件)。SVG文件是一种基于XML(Extensible Markup Language,可扩展标记语言)的图形文件,在任何分辨率的屏幕上均可清晰无失真的展示,因此使用SCG文件作为目标设备的目标布局文件,客户端可以展示出清晰无失真的设备图形,从而保证所述当前状态信息的展示准确性。
可以理解的是,目标设备的设备布局可能发生变更,为保证当前状态信息展示的准确性,服务端可以周期性检查所述目标布局文件是否发生变更,并在发生变更的情况下将变更后的目标布局文件发送至客户端,以便服务端及时根据变更后的目标布
局文件展示当前状态信息。例如,图1所示的定时任务模块103可以设置信息查询模块104按照固定周期执行信息查询任务,如按照该周期检查数据库12中保存的目标布局文件是否发生变更。当然,考虑到目标设备的设备布局在生产过程中通常并不会频繁变更,所以上述固定周期可以设置得适当长些,如12小时、1天、1月、1周等,本公开实施例并不对此进行限定。
服务端获取的到所述目标布局文件可以包含至少一个布局文件,任一布局文件中可能包含至少一个文件元素,任一文件元素可能对应于生产环境中的多个真实设备,即该文件元素可能被多个真实设备所复用。其中,所述文件元素可以为构成布局文件的基本单元或者多个基本单元的组合,任一文件元素可以对应于某一设备,也可以对应于该设备中的某一功能模块。例如,设备1和设备2为部署于不同车间中的两台同型号设备,且二者的设备布局相同而设备标识不同——显然,设备1和设备2对应于同一布局文件中的同一文件元素S。在通过前述方式确定的目标设备为设备1的情况下,若客户端在目标监控界面中展示文件元素S的元素标识,则用户可能无法区分该标识用于表征生产环境中的设备1还是设备2,从而无法确定目标监控界面中相应展示的是设备1的当前状态信息还是设备2的当前状态信息。
为避免展示和理解产生混乱,服务端在获取到的目标布局文件后,可以确定该文件中对应于目标设备的目标元素,并将所述目标布局文件中记录的目标元素的元素标识替换为所述目标设备的设备标识,然后将替换后的所述目标布局文件返回至所述客户端。可以理解的是,在获取到替换后的上述目标布局文件的情况下,客户端可以在目标监控界面中根据解析该文件得到的外部信息绘制目标设备的设备图形,然后在该设备图形的相应位置处展示目标设备的设备标识和目标设备的当前状态信息。如可以在设备1的设备图形上展示其设备标识(而非文件元素S的元素标识),使得用户可以直观的查看目标设备的当前状态信息,避免产生理解障碍,有助于保证生产过程和状态监控的顺利进行。
步骤204,在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述目标设备发生变更后的变更后状态信息发送至所述客户端,以由所述客户端根据所述变更后状态信息更新所述目标监控界面。
在将当前状态信息返回至客户端展示之后,服务端可能会收到制造执行***发送的针对目标设备的状态变更消息,该消息包含所述目标设备发生变更后的变更后状态信息。此后,服务端可以将该消息发送至客户端,以便其根据该信息更新所述目标监控界面,即在所述目标监控界面中展示所述变更后状态信息。其中,在当前状态信息被服务端按照目标布局文件指示的设备布局进行展示的情况下,所述变更后状态信息同样可以被服务端按照该设备布局进行展示,可见,目标设备的目标布局文件可以用于展示目标设备的设备信息(所述当前状态信息和变更后状态信息)。
其中,服务端可以通过多种方式向客户端发送所述变更后状态信息。在一实施例中,为尽量提升客户端所展示设备信息的实时性,服务端可以从接收到的状态变更消息中提取所述变更后状态信息,并将该信息直接发送至客户端,以使客户端尽快向用户展示变更后的变更后状态信息,避免展示延迟可能造成的错误发生。
在另一实施例中,鉴于目标设备可能在短时间内发生多次变更而用户往往并不需要一一查看每次变更后的变更后状态信息,所以服务端也可以先将状态变更消息中的变更后状态信息写入缓存,并在合适的时机从缓存中读出以发送至客户端。例如,在接收到针对所述目标设备的状态变更消息的情况下,服务端可以将该消息中包含的变更后状态信息写入缓存。其中,服务端可以按照预设格式将所述变更后状态信息写入缓存。如对于包含10个状态参数的目标设备,服务端可以在所述变更后状态信息中包含第1~4个状态参数的情况下,将这四个状态参数按照预设顺序依次写入所述缓存中对应于目标设备的存储地址处。示例性的,可以采用key_value键值对的方式写入所述变更后状态信息,如{key=设备ID;Value=温度1/压力1/温度2/流量1/转速1/压力2/转速3},不再赘述。
另外,在所述缓存中尚未写入所述目标设备的状态信息的情况下,服务端可以在该缓存的空白地址处写入所述变更后状态信息;而在所述缓存中已写入所述目标设备的状态信息的情况下,服务端可以使用所述变更后状态信息覆盖已写入的所述状态信息,从而减少变更后状态信息对缓存空间的占用和需要发送至客户端的数据量。
在此之后,服务端可以按照固定周期向客户端发送缓存中存储的所述变更后状态信息。例如在任一周期内,服务端若接收到针对目标设备的首个数据变更消息,则可以将该消息中包含的额变更后状态信息写入缓存;若在该周期内接收到针对同一目标设备的第二个状态变更消息,则可以使用第二个状态变更消息中的变更后状态信息覆盖缓存中已经写入的(首个状态变更消息包含的)变更后状态信息。其中,上述固定周期可以根据实际情况进行设置,如可以为1s、50ms、2s、10s等,该固定周期可以小于服务端对目标布局文件是否更新的检查周期。
通过该方式,服务端可以使用后一状态变更消息的变更后状态信息覆盖前一状态变更消息的变更后状态信息,保证任一设备的变更后状态信息仅在缓存中占据固定的存储空间,即便在状态变更消息急剧增多的情况下也能够实现对缓存空间实现有效控制。当然,在当前周期结束时刻,服务端可以将各个缓存中记录的变更后状态信息(距离当前时刻最近一次变更后的状态信息)发送至客户端展示,并触发开始下一周期的状态变更消息接收和变更后状态信息写入缓存的过程。
或者,服务端也可以按照上述数据覆盖的方式将变更后状态信息写入缓存,并响应于所述客户端发起的更新查询请求向所述客户端返回所述缓存中记录的所述变更后状态信息。通过该方式,服务端仅在客户端需要时才向其返回变更后状态信息,从
而进一步减少了服务端向客户端发送的变更后状态信息的数据量。通过上述数据覆盖的方式,可以减少客户端需要展示的变更后状态信息的数量,即减少客户端更新目标监控界面的工作量,有助于避免客户端发生延迟或卡顿等故障,从而保证用户查看变更后状态信息的用户体验。
另外,服务端在读取缓存中写入的任一设备的变更后状态信息之后,可以将该数据从所述缓存中删除,或者为其设置失效标识,以便回收相应的存储空间,实现缓存的高效利用。
图3是根据本公开实施例示出的另一种状态信息的更新方法的流程图。如图3所述,该方法应用于状态监控***的客户端,该方法可以包括下述步骤302-304。
步骤302,响应于用户针对目标设备实施的状态监控操作,向服务端发起针对所述目标设备的状态监控请求,并在目标监控界面中展示所述服务端响应于该请求返回的所述目标设备的当前状态信息。
如前所述,客户端向服务端发送的所述状态监控请求可以包含所述设备的标识信息,从而服务端可以根据所述标识信息查询所述目标设备对应的目标布局文件,并将该文件返回至客户端。此时,客户端可以在目标监控界面中按照所述目标布局文件指示的设备布局展示所述当前状态信息。例如,客户端可以解析所述目标布局文件获取外部信息,并根据该信息在目标监控界面中绘制目标设备的设备图形,然后在该图形的相应位置处针对性的展示所述当前状态信息。
其中,所述目标布局文件指示的设备布局可以包括下述至少之一:所述目标设备所属的设备层级、所述目标设备的安装位置、所述目标设备与其他设备之间的连接方式。
如图4所示,界面顶部的菜单栏401中展示有“设备监控”、“设备管理”、“设备分组”、“统计管理”和“***管理”等功能选项,在“设备监控”被触发的情况下,下方可以展示树状结构框402、图形展示框403和信息展示框404。
其中,下方左侧的树状结构框402中,包括“类型”、“工厂”和“分组”等不同层级的可选项,在“类型”选项被触发的情况下,进一步按照设备类型展示“真空泵”、“切割机”和“造粒机”等设备类型,并按照设备标识展示旋风除尘器“CLT4”。“CLT4”前方可以展示状态标识4021,以用于直观表明该设备的当前状态,如当前时刻处于工作状态还是停机状态等,上述状态标识4021的大小、形状、颜色等展示参数可以采用默认值或者由用户自定义设置,以便于用户理解其所指代的含义。
下方中部的图形展示框403中可以展示当前被选中的目标设备CLT4的设备图形,该图形的形状、颜色、纹理、线条等目标显示参数均可以用于表征CLT4的状态信息。下方右侧的信息展示框404中可以展示目标设备CLT4的设备信息,如前述设
备基本信息、汇总后的状态信息等,不再赘述。
步骤304,在接收到所述服务端发送的所述目标设备的变更后状态信息的情况下,根据所述变更后状态信息更新所述目标监控界面。
可以理解的是,客户端根据所述变更后状态信息更新目标监控界面的过程,即为将目标监控界面中展示的当前状态信息更新为新接收到的变更后状态信息的过程。例如在图1所示场景下,在客户端接收到服务端发送的变更后状态信息的情况下,可以根据该信息更新图形展示框403中所示设备图形的形状、颜色、纹理、线条等目标显示参数,和/或也可以更新信息展示框404中所展示的状态信息等,本公开实施例对于目标监控界面的具体更新方式并不进行限定。
通过上述实施例,客户端可以响应于用户针对目标设备实施的状态监控操作,向服务端发起针对该设备的状态监控请求。服务端可以响应于该请求将该设备的当前状态信息返回至所述客户端,以由该客户端在目标监控界面中展示所述当前状态信息。进一步的,在接收到针对所述目标设备的状态变更消息的情况下,服务端可以将该消息包含的目标设备发生变更后的变更后状态信息发送至客户端,以由其根据所述变更后状态信息更新所述目标监控界面。
可见,客户端在目标监控界面中展示出的当前状态信息用于表征目标设备在发生变更前的状态,而根据变更后状态信息更新后的目标监控界面用于表征该设备发生变更后的新状态,通过该方式,服务端在感知到目标设备发生变更(即接收到所述状态变更消息)的情况下,可以通知该客户端相应得自动更新目标监控界面,现场工人、运维人员、管理人员等用户能够通过查看目标监控界面,准确、及时地获知目标设备所发生的上述变更。通过该方案,用户无需去生产环境现场查看即可通过目标监控界面获知目标设备是否发生变更以及发生何种变更,从而不仅节省了人力成本,而且有效避免了人员对生产环境可能产生的干扰,即避免了对生产环境的洁净度造成不利影响,从而保证产品质量。
实际上,用户还可以针对所述目标监控界面进行相应的管理操作,下面结合图4进行说明。
在一实施例中,在目标监控界面中展示有所述当前状态信息或变更后状态信息的情况下,用户可以在该界面中实施状态刷新操作,如可以点击快捷键的方式或者在图1所示图形展示框403中通过右键菜单的方式实施上述状态刷新操作。从而,客户端可以响应于该操作向所述服务端发起针对目标设备CLT4的更新查询请求,以使所述服务端响应于该请求返回最新的变更后状态信息。如前述实施例可知,服务端返回的所述变更后状态信息可以是其从缓存中读取的目标设备的变更后状态信息。相应的,客户端可以在接收到所述变更后状态信息后进一步更新所述目标监控界面,以在该界面中展示该信息。
当然,在接收到客户端发起的所述更新查询请求的情况下,服务端可以检查所述缓存中是否已经存储有目标设备的变更后状态信息:若未存储,则表明从上次变更的时刻至当前时刻的一段时间内,目标设备并未在此发生变更,此时自然无需向服务端返回变更后状态信息,而可以返回空消息或者预设的其他特殊消息;若已存储,则表明目标设备在上述一段时间内发生了至少一次变更,而此时存储的变更后状态信息即为最近一次变更后的变更后状态信息,此时可以从缓存中读取该信息并发送至客户端。
在一实施例中,用户除了在目标监控界面中查看目标设备的状态信息之外,也可以查看其他设备的状态信息。例如,用户可以在目标监控界面中实施第一切换操作(如在图4所示菜单栏401中触发“设备分组”功能选项),而客户端可以响应于该操作确定其对应的切换后界面。其中,所述切换后界面可以为集中监控界面,该界面用于集中展示所述操作对应的设备集合中各个设备的状态信息,该界面对应的切换后设备为所述设备集合中的各个设备。其中,所述设备集合可以为“类型”、“工厂”、“分组”或者其他形式的设备集合,本公开实施例并不对此进行限定。或者,所述切换后界面也可以为任一设备的监控界面,该界面可以用于展示所述任一设备的状态信息,该界面对应的切换后设备即为所述任一设备。
进一步的,客户端可以向服务端发起针对切换后界面所对应切换后设备的更新查询请求,并在所述切换后界面中展示所述服务端响应于该请求返回的所述切换后设备的变更后状态信息。可以理解的是,在上述切换后界面为集中监控界面的情况下,用户可以对所述设备集合中各个设备进行批量、集中监控,提升监控效率;而在上述切换后界面为任一设备的监控界面的情况下,用户可以针对性的监控该设备的状态。
在一实施例中,为了管理状态信息的展示效果,用户可以配置相应的显示参数。例如,用户可以实施实时第二切换操作,以将所述目标监控界面切换为参数配置界面。如图4所示,用于可以触发菜单栏401中的“***管理”功能选项,从而控制客户端由图4所示的目标监控界面跳转至参数配置界面(图中并未示出)。进而,用户可以在参数配置界面中实施参数配置操作,客户端可以响应于该操作对显示参数进行相应配置。上述参数配置操作是更改某一状态的形状、颜色、纹理、线条等显示参数,如将宕机状态由黑色修改为灰色,将转动部件由圆形修改为扇形等。上述配置完成后的所述显示参数可以被用于在所述目标监控界面和/或其他设备的监控界面中显示相应设备的状态信息。
需要说明的是,若实施所述参数配置操作的用户为管理员用户,则客户端可以将配置后的显示参数发送至服务端,并由该服务端发送至该用户所对应其他用户(如普通用户)的客户端。从而其他用户的客户端可以按照上述配置完成后的显示参数在目标监控界面中展示设备信息。通过该方式,管理员用户可以实现对显示参数的统一配置和更改,有助于提升配置效率。而在实施所述参数配置操作的用户为普通用户的
情况下,客户端可以将配置后的显示参数存储在本地,在此之后,即可按照上述配置完成后的显示参数在目标监控界面中展示设备信息。通过该方式,普通用户可以自定义配置显示参数,以便设备信息的显示效果符合自身的查看习惯。
在一实施例中,用户可以查看目标设备的运行指标。例如,用户可以在所述目标监控界面中实施指标查看操作,如在图1所示菜单栏401中触发“统计管理”功能选项。从而客户端可以响应于该操作,根据目标设备的设备状态统计该设备的运行指标;或者向服务端获取目标设备的运行指标,该运行指标由服务端根据目标设备的设备状态统计得到。进而,客户端可以在所述指标查看操作对应的切换后界面中展示所述运行指标。其中,上述切换后界面可以为所述目标监控界面,或者也可以为从目标监控界面跳转的指标统计页面等;上述统计指标可以为预设时长内的稼动率(activation或utilization,是指设备在所能提供的时间内为了创造价值而占用的时间所占的比重)、状态百分比统计、设备履历和产品履历等,本公开实施例并不对此进行限定。通过该方式,客户端可以向用户展示目标设备的统计指标,以便简便快速的获知目标设备的整体工况。
与前述的状态信息的更新方法的实施例相对应,本公开还提供了状态信息的更新装置的实施例。
本公开实施例提出一种状态信息的更新装置,所述装置应用于,所述装置包括一个或多个处理器,所述处理器被配置为:响应于客户端针对目标设备发起的状态监控请求,将所述目标设备的当前状态信息返回至所述客户端,以由所述客户端在目标监控界面中展示所述当前状态信息;在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述目标设备发生变更后的变更后状态信息发送至所述客户端,以由所述客户端根据所述变更后状态信息更新所述目标监控界面。
在一个实施例中,所述处理器还被配置为:根据所述状态监控请求中包含的标识信息查询所述目标设备对应的目标布局文件,并将所述目标布局文件返回至所述客户端,以由所述客户端按照所述目标布局文件指示的设备布局展示所述当前状态信息。
在一个实施例中,所述处理器还被配置为:确定所述目标布局文件中对应于所述目标设备的目标元素,并将所述目标布局文件中记录的所述目标元素的元素标识替换为所述目标设备的设备标识;将替换后的所述目标布局文件返回至所述客户端。
在一个实施例中,所述状态监控请求中包含登录所述客户端的用户的身份信息,所述处理器还被配置为:在所述身份信息表明所述用户拥有针对所述目标设备的监控权限的情况下,将所述目标设备的当前状态信息返回至所述客户端。
在一个实施例中,所述处理器还被配置为:从制造执行***所关联的数据库中读取所述目标设备的当前状态信息,所述制造执行***用于响应于所述目标设备的状态信息发生变更,发起所述状态变更消息并更新所述数据库中记录的所述目标设备的
状态信息。
在一个实施例中,所述处理器还被配置为:在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息中包含的变更后状态信息写入缓存;按照固定周期向所述客户端发送所述缓存中的所述变更后状态信息;或者,响应于所述客户端发起的更新查询请求向所述客户端返回所述缓存中记录的所述变更后状态信息。
在一个实施例中,所述处理器还被配置为:在所述缓存中尚未写入所述目标设备的状态信息的情况下,在所述缓存的空白地址处写入所述变更后状态信息;在所述缓存中已写入所述目标设备的状态信息的情况下,使用所述变更后状态信息覆盖已写入的所述状态信息。
在一个实施例中,所述处理器还被配置为:按照预设格式将所述变更后状态信息写入缓存。
本公开实施例提出另一种状态信息的更新装置,所述装置包括一个或多个处理器,所述处理器被配置为:响应于用户针对目标设备实施的状态监控操作,向服务端发起针对所述目标设备的状态监控请求,并在目标监控界面中展示所述服务端响应于该请求返回的所述目标设备的当前状态信息;在接收到所述服务端发送的所述目标设备的变更后状态信息的情况下,根据所述变更后状态信息更新所述目标监控界面。
在一个实施例中,所述状态监控请求包含所述设备的标识信息,所述处理器还被配置为:接收所述服务端根据所述标识信息查询到的所述目标设备对应的目标布局文件;在目标监控界面中按照所述目标布局文件指示的设备布局展示所述当前状态信息。
在一个实施例中,所述目标布局文件指示的设备布局包括下述至少之一:所述目标设备所属的设备层级、所述目标设备的安装位置、所述目标设备与其他设备之间的连接方式。
在一个实施例中,所述处理器还被配置为:响应于所述用户实施的指标查看操作,根据所述目标设备的设备状态统计所述目标设备的运行指标;或者,向所述服务端获取根据所述目标设备的设备状态统计得到的所述目标设备的运行指标;在所述指标查看操作对应的切换后界面中展示所述运行指标。
在一个实施例中,所述处理器还被配置为:响应于所述用户针对所述目标设备实施的状态刷新操作,向所述服务端发起针对所述目标设备的更新查询请求,以使所述服务端响应于该请求返回所述变更后状态信息。
在一个实施例中,所述处理器还被配置为:响应于所述用户实施的第一切换操作,确定该操作对应的切换后界面,所述切换后界面包括集中监控界面或者任一设备的监控界面,其中,所述集中监控界面用于集中展示所述操作对应的设备集合中各个
设备的状态信息,所述任一设备的监控界面用于展示该设备的状态信息;向所述服务端发起针对所述切换后界面所对应切换后设备的更新查询请求,并在所述切换后界面中展示所述服务端响应于该请求返回的所述切换后设备的变更后状态信息。
在一个实施例中,所述处理器还被配置为:响应于所述用户实施的第二切换操作,将所述目标监控界面切换为参数配置界面;响应于所述用户在所述参数配置界面中实施的参数配置操作对显示参数进行相应配置,配置完成的所述显示参数被用于在所述目标监控界面和/或其他设备的监控界面中显示相应设备的状态信息。
本公开的实施例还提出一种电子设备,包括:处理器;用于存储处理器可执行指令的存储器;其中,所述处理器被配置为实现上述任一实施例所述的状态信息的更新方法。
本公开的实施例还提出一种非瞬态计算机可读存储介质,其上存储有计算机程序,该程序被处理器执行时实现上述任一实施例所述的状态信息的更新方法中的步骤。
关于上述实施例中的装置,其中各个模块执行操作的具体方式已经在相关方法的实施例中进行了详细描述,此处将不做详细阐述说明。
图5是根据本公开的实施例示出的一种用于数据存证或者驾驶模式的确定的装置500的示意框图。例如,装置500可以是移动电话,计算机,数字广播终端,消息收发设备,游戏控制台,平板设备,医疗设备,健身设备,个人数字助理等。
参照图5,装置500可以包括以下一个或多个组件:处理组件502,存储器504,电源组件506,多媒体组件508,音频组件510,输入/输出(I/O)的接口512,传感器组件514,以及通信组件516。
处理组件502通常控制装置500的整体操作,诸如与显示,电话呼叫,数据通信,相机操作和记录操作相关联的操作。处理组件502可以包括一个或多个处理器520来执行指令,以完成上述状态信息的更新方法的全部或部分步骤。此外,处理组件502可以包括一个或多个模块,便于处理组件502和其他组件之间的交互。例如,处理组件502可以包括多媒体模块,以方便多媒体组件508和处理组件502之间的交互。
存储器504被配置为存储各种类型的数据以支持在装置500的操作。这些数据的示例包括用于在装置500上操作的任何应用程序或方法的指令,联系人数据,电话簿数据,消息,图片,视频等。存储器504可以由任何类型的易失性或非易失性存储设备或者它们的组合实现,如静态随机存取存储器(SRAM),电可擦除可编程只读存储器(EEPROM),可擦除可编程只读存储器(EPROM),可编程只读存储器(PROM),只读存储器(ROM),磁存储器,快闪存储器,磁盘或光盘。
电源组件506为装置500的各种组件提供电力。电源组件506可以包括电源管理***,一个或多个电源,及其他与为装置500生成、管理和分配电力相关联的组件。
多媒体组件508包括在所述装置500和用户之间的提供一个输出接口的屏幕。在一些实施例中,屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板,屏幕可以被实现为触摸屏,以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界,而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中,多媒体组件508包括一个前置摄像头和/或后置摄像头。当装置500处于操作模式,如拍摄模式或视频模式时,前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜***或具有焦距和光学变焦能力。
音频组件510被配置为输出和/或输入音频信号。例如,音频组件510包括一个麦克风(MIC),当装置500处于操作模式,如呼叫模式、记录模式和语音识别模式时,麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器504或经由通信组件516发送。在一些实施例中,音频组件510还包括一个扬声器,用于输出音频信号。
I/O接口512为处理组件502和***接口模块之间提供接口,上述***接口模块可以是键盘,点击轮,按钮等。这些按钮可包括但不限于:主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件514包括一个或多个传感器,用于为装置500提供各个方面的状态评估。例如,传感器组件514可以检测到装置500的打开/关闭状态,组件的相对定位,例如所述组件为装置500的显示器和小键盘,传感器组件514还可以检测装置500或装置500一个组件的位置改变,用户与装置500接触的存在或不存在,装置500方位或加速/减速和装置500的温度变化。传感器组件514可以包括接近传感器,被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件514还可以包括光传感器,如CMOS或CCD图像传感器,用于在成像应用中使用。在一些实施例中,该传感器组件514还可以包括加速度传感器,陀螺仪传感器,磁传感器,压力传感器或温度传感器。
通信组件516被配置为便于装置500和其他设备之间有线或无线方式的通信。装置500可以接入基于通信标准的无线网络,如WiFi,2G或3G,4G LTE、6G NR或它们的组合。在一个示例性实施例中,通信组件516经由广播信道接收来自外部广播管理***的广播信号或广播相关信息。在一个示例性实施例中,所述通信组件516还包括近场通信(NFC)模块,以促进短程通信。例如,在NFC模块可基于射频识别(RFID)技术,红外数据协会(IrDA)技术,超宽带(UWB)技术,蓝牙(BT)技术和其他技术来实现。
在示例性实施例中,装置500可以被一个或多个应用专用集成电路(ASIC)、
数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现,用于执行上述状态信息的更新方法。
在示例性实施例中,还提供了一种包括指令的非瞬态计算机可读存储介质,例如包括指令的存储器504,上述指令可由装置500的处理器520执行以完成上述状态信息的更新方法。例如,所述非瞬态计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的实施例后,将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化,这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的,本公开的真正范围和精神由下面的权利要求指出。
应当理解的是,本公开并不局限于上面已经描述并在附图中示出的精确结构,并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
需要说明的是,在本文中,诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来,而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本公开实施例所提供的方法和装置进行了详细介绍,本文中应用了具体个例对本公开的原理及实施方式进行了阐述,以上实施例的说明只是用于帮助理解本公开的方法及其核心思想;同时,对于本领域的一般技术人员,依据本公开的思想,在具体实施方式及应用范围上均会有改变之处,综上所述,本公开内容不应理解为对本公开的限制。
Claims (22)
- 一种状态信息的更新方法,包括:响应于客户端针对目标设备发起的状态监控请求,将所述目标设备的当前状态信息返回至所述客户端,以由所述客户端在目标监控界面中展示所述当前状态信息;在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述目标设备发生变更后的变更后状态信息发送至所述客户端,以由所述客户端根据所述变更后状态信息更新所述目标监控界面。
- 根据权利要求1所述的方法,还包括:根据所述状态监控请求中包含的标识信息查询所述目标设备对应的目标布局文件,并将所述目标布局文件返回至所述客户端,以由所述客户端按照所述目标布局文件指示的设备布局展示所述当前状态信息。
- 根据权利要求2所述的方法,还包括:确定所述目标布局文件中对应于所述目标设备的目标元素,并将所述目标布局文件中记录的所述目标元素的元素标识替换为所述目标设备的设备标识;所述将所述目标布局文件返回至所述客户端,包括:将替换后的所述目标布局文件返回至所述客户端。
- 根据权利要求1所述的方法,所述状态监控请求中包含登录所述客户端的用户的身份信息,所述将所述目标设备的当前状态信息返回至所述客户端,包括:在所述身份信息表明所述用户拥有针对所述目标设备的监控权限的情况下,将所述目标设备的当前状态信息返回至所述客户端。
- 根据权利要求1所述的方法,通过下述方式获取所述目标设备的当前状态信息:从制造执行***所关联的数据库中读取所述目标设备的当前状态信息,所述制造执行***用于响应于所述目标设备的状态信息发生变更,发起所述状态变更消息并更新所述数据库中记录的所述目标设备的状态信息。
- 根据权利要求1所述的方法,所述在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述目标设备发生变更后的变更后状态信息发送至所述客户端,包括:在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息中包含的变更后状态信息写入缓存;按照固定周期向所述客户端发送所述缓存中的所述变更后状态信息;或者,响应于所述客户端发起的更新查询请求向所述客户端返回所述缓存中记录的所述变更后状态信息。
- 根据权利要求6所述的方法,所述将所述状态变更消息中包含的变更后状态信息写入缓存,包括:在所述缓存中尚未写入所述目标设备的状态信息的情况下,在所述缓存的空白地 址处写入所述变更后状态信息;在所述缓存中已写入所述目标设备的状态信息的情况下,使用所述变更后状态信息覆盖已写入的所述状态信息。
- 根据权利要求6所述的方法,所述将所述状态变更消息中包含的变更后状态信息写入缓存,包括:按照预设格式将所述变更后状态信息写入缓存。
- 一种状态信息的更新方法,包括:响应于用户针对目标设备实施的状态监控操作,向服务端发起针对所述目标设备的状态监控请求,并在目标监控界面中展示所述服务端响应于该请求返回的所述目标设备的当前状态信息;在接收到所述服务端发送的所述目标设备的变更后状态信息的情况下,根据所述变更后状态信息更新所述目标监控界面。
- 根据权利要求9所述的方法,所述状态监控请求包含所述设备的标识信息,所述方法还包括:接收所述服务端根据所述标识信息查询到的所述目标设备对应的目标布局文件;所述在目标监控界面中展示所述当前状态信息,包括:在目标监控界面中按照所述目标布局文件指示的设备布局展示所述当前状态信息。
- 根据权利要求10所述的方法,所述目标布局文件指示的设备布局包括下述至少之一:所述目标设备所属的设备层级、所述目标设备的安装位置、所述目标设备与其他设备之间的连接方式。
- 根据权利要求9所述的方法,还包括:响应于所述用户实施的指标查看操作,根据所述目标设备的设备状态统计所述目标设备的运行指标;或者,向所述服务端获取根据所述目标设备的设备状态统计得到的所述目标设备的运行指标;在所述指标查看操作对应的切换后界面中展示所述运行指标。
- 根据权利要求9所述的方法,还包括:响应于所述用户针对所述目标设备实施的状态刷新操作,向所述服务端发起针对所述目标设备的更新查询请求,以使所述服务端响应于该请求返回所述变更后状态信息。
- 根据权利要求9所述的方法,还包括:响应于所述用户实施的第一切换操作,确定该操作对应的切换后界面,所述切换后界面包括集中监控界面或者任一设备的监控界面,其中,所述集中监控界面用于集中展示所述操作对应的设备集合中各个设备的状态信息,所述任一设备的监控界面用于展示该设备的状态信息;向所述服务端发起针对所述切换后界面所对应切换后设备的更新查询请求,并在 所述切换后界面中展示所述服务端响应于该请求返回的所述切换后设备的变更后状态信息。
- 根据权利要求9所述的方法,还包括:响应于所述用户实施的第二切换操作,将所述目标监控界面切换为参数配置界面;响应于所述用户在所述参数配置界面中实施的参数配置操作对显示参数进行相应配置,配置完成的所述显示参数被用于在所述目标监控界面和/或其他设备的监控界面中显示相应设备的状态信息。
- 一种状态监控***,包括客户端和服务端,其中,所述客户端用于向所述服务端发起针对目标设备的状态监控请求,并在目标监控界面中展示所述服务端响应于该请求返回的所述目标设备的当前状态信息;以及,在接收到所述服务端发送的所述目标设备发生变更后的变更后状态信息的情况下,根据所述变更后状态信息更新所述目标监控界面;所述服务端用于响应于所述状态监控请求,向所述客户端返回所述当前状态信息;以及,在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述变更后状态信息发送至所述客户端。
- 根据权利要求16所述的***,还包括数据库,其中,所述数据库用于存储目标设备的状态信息,所述状态信息由制造执行***响应于所述目标设备的状态信息发生变更触发存储至所述数据库,所述制造执行***还响应于所述目标设备的状态信息发生变更向所述服务端发送所述状态变更消息。
- 根据权利要求16所述的***,还包括缓存,所述缓存用于存储所述目标设备发生变更后的变更后状态信息,所述变更后状态信息由所述服务端响应于所述状态变更消息写入所述缓存。
- 一种状态信息的更新装置,所述装置包括一个或多个处理器,所述处理器被配置为:响应于客户端针对目标设备发起的状态监控请求,将所述目标设备的当前状态信息返回至所述客户端,以由所述客户端在目标监控界面中展示所述当前状态信息;在接收到针对所述目标设备的状态变更消息的情况下,将所述状态变更消息包含的所述目标设备发生变更后的变更后状态信息发送至所述客户端,以由所述客户端根据所述变更后状态信息更新所述目标监控界面。
- 一种状态信息的更新装置,所述装置包括一个或多个处理器,所述处理器被配置为:响应于用户针对目标设备实施的状态监控操作,向服务端发起针对所述目标设备的状态监控请求,并在目标监控界面中展示所述服务端响应于该请求返回的所述目标设备的当前状态信息;在接收到所述服务端发送的所述目标设备的变更后状态信息的情况下,根据所述变更后状态信息更新所述目标监控界面。
- 一种电子设备,包括:处理器;用于存储处理器可执行指令的存储器;其中,所述处理器被配置为实现权利要求1至15中任一项所述的方法。
- 一种非瞬态计算机可读存储介质,其上存储有计算机程序,该程序被处理器执行时实现权利要求1至15中任一项所述的方法中的步骤。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210583685.1A CN114915567B (zh) | 2022-05-25 | 2022-05-25 | 状态监控***、状态信息的更新方法及装置 |
CN202210583685.1 | 2022-05-25 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023226703A1 true WO2023226703A1 (zh) | 2023-11-30 |
Family
ID=82768779
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2023/091889 WO2023226703A1 (zh) | 2022-05-25 | 2023-04-28 | 状态监控***、状态信息的更新方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN114915567B (zh) |
WO (1) | WO2023226703A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117834815A (zh) * | 2024-01-03 | 2024-04-05 | 荟普智能装备(深圳)有限公司 | 设备状态监控方法、装置、设备及存储介质 |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114915567B (zh) * | 2022-05-25 | 2024-05-10 | 京东方科技集团股份有限公司 | 状态监控***、状态信息的更新方法及装置 |
CN115063123A (zh) * | 2022-08-17 | 2022-09-16 | 歌尔股份有限公司 | 智能制造方法、***及电子设备 |
CN116071028B (zh) * | 2023-03-07 | 2023-06-02 | 徐工汉云技术股份有限公司 | 设备监控流程图生成方法、装置、电子设备和存储介质 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105867931A (zh) * | 2016-04-07 | 2016-08-17 | 北京橙鑫数据科技有限公司 | 信息展示界面的变更方法和装置 |
JP2018055329A (ja) * | 2016-09-28 | 2018-04-05 | アズビル株式会社 | 製造管理システム |
CN107888458A (zh) * | 2017-12-11 | 2018-04-06 | 北京小米移动软件有限公司 | 智能设备状态处理方法及装置 |
CN109213564A (zh) * | 2018-10-22 | 2019-01-15 | 珠海格力电器股份有限公司 | 智能家居控制界面调整方法、装置、智能终端和介质 |
CN112600920A (zh) * | 2020-12-14 | 2021-04-02 | 广州新科佳都科技有限公司 | 一种基于云平台的线网综合监控方法及*** |
CN114915567A (zh) * | 2022-05-25 | 2022-08-16 | 京东方科技集团股份有限公司 | 状态监控***、状态信息的更新方法及装置 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104468778B (zh) * | 2014-12-08 | 2017-12-15 | 广东工业大学 | 一种基于云服务的云制造执行***及其制造执行方法 |
CN108093206A (zh) * | 2016-11-21 | 2018-05-29 | 北京视联动力国际信息技术有限公司 | 一种资源监控方法及*** |
CN108363435A (zh) * | 2017-12-28 | 2018-08-03 | 杭州电子科技大学 | 一种猪舍环境远程监控***及方法 |
CN111478965A (zh) * | 2020-04-07 | 2020-07-31 | 四川虹美智能科技有限公司 | 设备影子的处理方法、装置和*** |
-
2022
- 2022-05-25 CN CN202210583685.1A patent/CN114915567B/zh active Active
-
2023
- 2023-04-28 WO PCT/CN2023/091889 patent/WO2023226703A1/zh unknown
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105867931A (zh) * | 2016-04-07 | 2016-08-17 | 北京橙鑫数据科技有限公司 | 信息展示界面的变更方法和装置 |
JP2018055329A (ja) * | 2016-09-28 | 2018-04-05 | アズビル株式会社 | 製造管理システム |
CN107888458A (zh) * | 2017-12-11 | 2018-04-06 | 北京小米移动软件有限公司 | 智能设备状态处理方法及装置 |
CN109213564A (zh) * | 2018-10-22 | 2019-01-15 | 珠海格力电器股份有限公司 | 智能家居控制界面调整方法、装置、智能终端和介质 |
CN112600920A (zh) * | 2020-12-14 | 2021-04-02 | 广州新科佳都科技有限公司 | 一种基于云平台的线网综合监控方法及*** |
CN114915567A (zh) * | 2022-05-25 | 2022-08-16 | 京东方科技集团股份有限公司 | 状态监控***、状态信息的更新方法及装置 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117834815A (zh) * | 2024-01-03 | 2024-04-05 | 荟普智能装备(深圳)有限公司 | 设备状态监控方法、装置、设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN114915567A (zh) | 2022-08-16 |
CN114915567B (zh) | 2024-05-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2023226703A1 (zh) | 状态监控***、状态信息的更新方法及装置 | |
CN111917918B (zh) | 基于增强现实的事件提醒管理方法、装置以及存储介质 | |
CN110109598A (zh) | 一种动画交互实现方法、装置及电子设备 | |
EP3232323B1 (en) | Method and apparatus for displaying status information of application | |
CN112379976A (zh) | 一种事件处理方法、装置、移动终端及存储介质 | |
CN111800454A (zh) | 一种可视化数据展示***及可视化页面投屏方法 | |
CN111459381A (zh) | 信息展示方法、电子设备及存储介质 | |
CN106528284B (zh) | 应用程序配置方法、装置及终端设备 | |
CN112528185A (zh) | 评论信息展示方法、装置、服务器、终端 | |
CN114328629A (zh) | 数据缓存方法、装置、电子设备及存储介质 | |
CN106021072A (zh) | 信息显示方法及装置 | |
CN114661811A (zh) | 数据展示方法、装置、电子设备及存储介质 | |
US20210132855A1 (en) | Method and device for detecting slow node and computer-readable storage medium | |
CN110768843B (zh) | 网络问题分析方法、装置、终端及存储介质 | |
CN112286611A (zh) | 图标显示方法、装置和电子设备 | |
CN112153218A (zh) | 页面显示方法、装置、可穿戴设备及存储介质 | |
CN115604132A (zh) | 服务器的远程控制方法、装置、电子设备和可读存储介质 | |
CN108012258A (zh) | 虚拟sim卡的数据流量管理方法、装置、终端及服务器 | |
CN115509872A (zh) | 一种客户端行为数据采集方法及装置 | |
CN105744324B (zh) | 一种组件管理的方法和装置 | |
CN114866640B (zh) | 触控面板失灵通信方法和相关装置 | |
CN101841761B (zh) | 用于移动通信网络的www内容发布方法、运营方法及*** | |
US11853540B2 (en) | Method for interface control, electronic device and storage medium | |
EP4060592A1 (en) | Method and system for acquiring content, user terminal, and content server | |
CN112988200A (zh) | 一种控件状态更新方法、装置、设备和存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23810776 Country of ref document: EP Kind code of ref document: A1 |