CN117834667A - Universal collaboration command interaction method, system, equipment and medium - Google Patents
Universal collaboration command interaction method, system, equipment and medium Download PDFInfo
- Publication number
- CN117834667A CN117834667A CN202311549003.6A CN202311549003A CN117834667A CN 117834667 A CN117834667 A CN 117834667A CN 202311549003 A CN202311549003 A CN 202311549003A CN 117834667 A CN117834667 A CN 117834667A
- Authority
- CN
- China
- Prior art keywords
- command
- collaboration
- confirmation
- user
- background server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 230000003993 interaction Effects 0.000 title claims abstract description 19
- 238000012790 confirmation Methods 0.000 claims abstract description 80
- 238000012545 processing Methods 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 8
- 238000010200 validation analysis Methods 0.000 claims 1
- 241000282326 Felis catus Species 0.000 description 11
- 238000004891 communication Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000007547 defect Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- RWSOTUBLDIXVET-UHFFFAOYSA-N Dihydrogen sulfide Chemical compound S RWSOTUBLDIXVET-UHFFFAOYSA-N 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention relates to a method, a system, equipment and a medium for interaction of universal collaboration commands, wherein the method comprises the following steps: s is S 1 Initializing a collaboration command list; s is S 2 Setting a command for cooperative confirmation of a specific user role on a front-end workstation by a user, and sending a corresponding manual operation message to a background server; s is S 3 The background server confirms the collaboration command and then sends a collaboration command request message to all front-end workstations; s is S 4 After receiving the message, all front-end workstations check whether the original command is sent by the local machine, if so, discarding the original command; s is S 5 All front-end workstations check whether the user role mask and the user role of the local login are matched, and if so, promptThe cooperative command needs to be confirmed; s is S 6 And after the front-end workstation confirms the user, replying a collaboration command confirmation command to the background server. Compared with the prior art, the method and the device have the advantages that the universal collaboration command based on the user roles can greatly reduce the operation risk caused by single user decision errors.
Description
Technical Field
The invention relates to the field of track traffic signal processing, in particular to a method, a system, equipment and a medium for interaction of universal collaboration commands.
Background
The rail transit is taken as an important component of urban public transportation, so that the travel efficiency can be effectively improved, urban congestion can be relieved, the air quality can be improved, and urban development can be promoted; meanwhile, the system is an important mark for measuring the construction level of an urban traffic infrastructure, and is very important as a signal control system of a brain center, and the operation safety, the transportation capacity and the operation efficiency of the rail traffic are closely related to the signal control system. The automation and intelligent degree of the signal control system are higher and higher, and the GOA4 unmanned technology with the highest automatic operation level is also increasingly applied to new lines.
In the daily operation process, even if a driver does not drive a line, manual intervention processing is needed in many scenes, and the correct processing and issuing of manual commands directly affect the operation safety and the operation efficiency of the system.
The common operation modes of manual commands at present are generally divided into the following categories:
1) The operator clicks the function button through the system menu or the mouse to select the command and then directly issues the command.
2) After clicking a function button selection command through a system menu or a mouse, an operator pops up a confirmation dialog box, and needs to input a password and send the password after system verification.
3) The operator interacts with the signal control system, and issues a command after confirming the operation twice.
These several operation modes are all that a single operator interacts with the system to issue commands, and for critical commands, if the operator makes a decision, the operation of the system may be seriously affected. For commands related to different systems, other modes of communication are needed, and then operators of the systems respectively issue the commands to influence the execution efficiency.
Therefore, there is a need to design a general collaborative command interaction method that overcomes the defect of possible decision errors of a single user and improves the execution efficiency.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provide a general collaborative command interaction method, a system, equipment and a medium, which can overcome the defect that a single user may have a decision error and have high execution efficiency.
The aim of the invention can be achieved by the following technical scheme:
according to a first aspect of the present invention, there is provided a universal collaboration command interaction method, the method comprising:
step S 1 Loading a collaboration command configuration file by a background server and all front-end workstations, and initializing a collaboration command list;
step S 2 Setting a first command requiring specific user role cooperation confirmation on a first front-end workstation by a first user, wherein the first front-end workstation sends a manual operation message containing a command type of the first command to the background server;
step S 3 The background server checks the collaboration command list according to the command type to confirm the collaboration command, and if the collaboration command is confirmed, the background server sends a collaboration command request message to all front-end workstations;
step S 4 After all front-end workstations receive the collaboration command request message, checking whether the original command is sent by the local machine, if so, directly discarding, otherwise, turning to step S 4 Further processing；
Step S 5 All front-end workstations check whether the user role mask is matched with the user role logged in by the local machine, if the roles are not matched, the message is directly discarded, otherwise, the cooperative command is prompted to be confirmed;
step S 6 And the front-end workstation with the collaboration command to be confirmed carries out user confirmation based on the confirmation mode of the current collaboration command, and replies the collaboration command confirmation command to the background server after the user confirmation, and the background server further processes the collaboration command confirmation command.
Preferably, the step S 1 The parameters in the collaboration command configuration list include command type, command name, centralized station number, device name, role mask of collaboration confirmation user and confirmation mode.
Preferably, the step S 3 Checking a collaboration command list according to the command type to confirm the collaboration command, wherein the method specifically comprises the following steps:
the cooperative confirmation is needed for the command type with the centralized station number and the equipment name empty;
for command types where the centralized station number and device name are not empty, only the commands of a particular device need to be cooperatively acknowledged.
Preferably, the step S 3 The collaboration command request message includes a role mask and a confirmation mode of a collaboration confirmation user corresponding to the first command.
Preferably, the step S 3 When the collaboration command request message is sent to all front-end workstations, starting timing, and when the confirmation message is not received within a set time, clearing the current collaboration command request message and recovering to a pre-operation state.
Preferably, the acknowledgement message is not received within a set time, the current collaboration command request message is cleared, and the state before operation is restored, specifically: and periodically polling to set a timeout condition of the collaboration command, and if the timeout condition exists, clearing the request state, updating the interface display and recovering to the pre-operation state.
Preferably, the step S 6 The confirmation mode of the collaboration command comprises direct confirmationThe mode and the confirmation mode of repeated operation are specifically as follows:
if the direct confirmation mode is adopted, the user needs to click on a confirmation dialog box to select acceptance or rejection; and if the repeated operation confirmation mode is adopted, prompting the user to repeatedly operate and issuing a command to be confirmed cooperatively.
Preferably, the step S 6 The background server further processes, specifically: if the confirmation result is refusal, directly discarding the command and clearing the request state; if the result of the confirmation is acceptance, continuing to process the command, and further sending a message to an external interface or notifying other modules.
Preferably, the step S 3 Further comprises: if the non-cooperative command is confirmed, the normal processing is finished after a prompt of successful operation is given.
According to a second aspect of the present invention, there is provided a universal collaboration command interaction system, the system comprising a background server and at least two front-end workstations, the background server and the front-end workstations performing universal collaboration command interactions using the method described above.
According to a third aspect of the present invention there is provided an electronic device comprising a memory and a processor, the memory having stored thereon a computer program, the processor implementing the method of any one of the above when executing the program.
According to a fourth aspect of the present invention, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the method of any one of the above.
Compared with the prior art, the invention has the following advantages:
1) The user role-based general collaboration command interaction method designed by the invention can be applied to key commands which can be issued only by a plurality of user collaboration confirmation, and overcomes the defect that a single user may have a decision error.
2) For the execution command requiring confirmation of different types of user roles, the front-end workstation can give an obvious prompt, so that a user can conveniently grasp the current system state in real time, the operation efficiency is improved, and good guarantee is provided for stable operation of project sites.
3) The method of the invention not only supports configuration of the command list to be confirmed in a unit of command type, but also supports the cooperative confirmation of only partial devices under the same command type, thus having strong universality and flexibility.
4) The command confirming party in the invention judges based on the user role mask, can support a plurality of roles to have confirming qualification, and flexibly adapt to different operation organization modes.
5) The invention also supports the reading of the configuration file when no cooperative command is required, and ensures the compatibility of the application system on each line.
Drawings
FIG. 1 is a flow chart of the method of the present invention;
FIG. 2 is a schematic diagram of collaborative command interaction in an embodiment;
FIG. 3 is a flowchart of a background server generating a collaboration command request;
FIG. 4 is a flow diagram of a front end workstation processing a collaboration request message in an embodiment;
fig. 5 is a flowchart of a background server processing a collaboration confirmation message in an embodiment.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
Example 1
As shown in fig. 1, this embodiment provides a general collaboration command interaction method, which includes:
an initialization stage:
step S 1 The back-end server CATS and all front-end workstations GPC load collaboration command configuration files, combine other according to collaboration command configurationInitializing a collaboration command list in a memory by conventional command data; the parameters in the collaboration command configuration list include a command type command_type, a command name command_name, a centralized station number rtu_id, a device name device_name, a role mask of a collaboration confirmation user ack_role_mask, and a confirmation mode ack_mode. When the centralized station number rtu_id and the device name device_name are empty, it means that this type of command needs to be cooperatively acknowledged; when the centralized station number rtu_id and the device name device_name are not empty, it means that this type of command only requires a cooperative acknowledgement for a command of a specific device.
In the operation stage, taking a background server and a plurality of front-end workstations as examples:
step S 2 A first User (User 1) sets a first command A which needs to be confirmed by the cooperation of a specific User role TC on a first front-end workstation GPC, and the first front-end workstation GPC sends a MANUAL-operation message MANUAL_DEVICE_OPER with the command type of the first command A to a background server CATS;
step S 3 And the background server CATS checks the collaboration COMMAND list according to the COMMAND type to confirm the collaboration COMMAND, if the collaboration COMMAND is confirmed to be a non-collaboration COMMAND, the normal processing is finished after a prompt of successful operation is given, if the collaboration COMMAND is confirmed, a collaboration COMMAND REQUEST COOPERATIVE_COMMAND_REQUEST message (comprising a role mask and a confirmation mode of a collaboration confirmation user corresponding to the first COMMAND) is sent to all front-end workstations GPC, meanwhile, timing is started, no confirmation message is received within a set time (configurable), the current collaboration COMMAND REQUEST message is cleared, the state before operation is restored, and the timeliness of the operation is ensured.
The method comprises the steps of checking a collaboration command list according to a command type to confirm the collaboration command, wherein the method comprises the following steps: the cooperative confirmation is needed for the command type with the centralized station number and the equipment name empty; for command types where the centralized station number and device name are not empty, only the commands of a particular device need to be cooperatively acknowledged.
Step S 4 After all front-end workstations receive the collaboration COMMAND REQUEST COOPERATIVE_COMMAND_REQUEST message, checking whether the original COMMAND is sent locally, if so, then directlyDiscarding (preventing confirmation directly by person handling the request), otherwise go to step S 4 Further processing;
step S 5 Checking whether the User role mask ack_user_type is matched with the User roles logged in by the front-end workstation or not, if the User roles are not matched, directly discarding the message, otherwise prompting that a collaboration command needs to be confirmed (for example, the role of the second User2 is TC and is logged in on the GPC of the second front-end workstation, and the roles are considered to be matched);
step S 6 And the front-end workstation with the COOPERATIVE COMMAND to be confirmed carries out user confirmation based on the confirmation mode of the current COOPERATIVE COMMAND, and after the user confirmation, the current front-end workstation GPC replies the COOPERATIVE COMMAND confirmation COMMAND GPC_AC_COOPERATIVE_COMMAND to the background server CATS, and the background server CATS further processes the COOPERATIVE COMMAND.
Specifically, the confirmation modes of the collaboration command include a direct confirmation mode and a repeated operation confirmation mode, and if the direct confirmation mode is adopted, the user needs to click on a confirmation dialog box to select to accept or reject; and if the repeated operation confirmation mode is adopted, prompting the user to repeatedly operate and issuing a command to be confirmed cooperatively.
If the confirmation result is REJECT, directly discarding the command and clearing the request state; if the result of the confirmation is acceptance of the ACCEPT, the command continues to be processed, and a message is further sent to an external interface or other modules are notified.
Next, the method of this embodiment will be described in detail using the example of setting station jump stop.
As shown in fig. 2, the collaboration command interaction method in this embodiment includes the following steps:
step S101, a background server CATS reads parameters configured in a configuration file, including a command type, a command name, a centralized station number, a device name, a role mask of a collaboration confirmation user and a confirmation mode, and does not need a collaboration command function without the configuration description;
step S102, a user sets the skip stop of a designated station at a front-end workstation GPC, and sends a message MANUAL_DEVICE_OPER to a background server CATS;
step S103, initializing reading configuration by a background server CATS, and judging whether station jump stop is defined as operation requiring cooperative confirmation after receiving a MANUAL_DEVICE_OPER message;
step S104, if yes, sending a station skip stop cooperative command request message to all front-end workstations GPC;
step S105, after all front-end workstations GPC receive the request message of the cooperative command, check whether the original command is sent by the machine at first, if yes, discard the command directly and do not process (prevent the personnel who directly operate the request from confirming);
step S106, if not sent by the local machine, further checking whether the user role mask ack_user_type is matched with the user role logged in by the local machine; if the roles do not match, the message is dropped directly. If the roles match (for example, the role of User2 is TC and is logged in on workstation 2), workstation 2 prompts that a collaboration command needs to be confirmed, an icon flashes on the interface, and an ACCEPT or REJECT is to be clicked for confirmation;
step S107, the front-end workstation sends a station skip stop cooperative command confirmation message to the background server CATS;
step S108, if the platform skip stop is operated according to the configuration not being the cooperation command during CATS processing of the background server, directly issuing the command to an external interface; if an acknowledgement message sent by the front end station GPC is received, the interface request state is cleared and a station hop stop command is sent to the external interface.
Fig. 3 is a flowchart of a background server generating a collaboration command request message in the present invention. Taking the following example of setting station jump stop, the following steps are described in detail with reference to fig. 3:
step S201, similar to step S101 of fig. 2;
step S202, a background server CATS receives a message about the station set skip stop sent by a workstation and analyzes a MANUAL_DEVICE_OPER;
step S203, the same as step S103 in fig. 2;
step S204, searching whether the device is set in the cached operation command (avoiding repeated operation), and if the operation is repeated, directly discarding the command;
step S205, if the operation is not repeated, a station skip stop operation command is added to the CmdBuff which is processed uniformly, timing is synchronized, and if the ACK is not received within a certain time, the command is cleared;
step S206, the server sets a cooperative command request zone bit according to the operated equipment, and synchronously updates the display of the workstation;
step S207, a station skip COOPERATIVE COMMAND request COOPERATIVE_COMMAND_REQUEST message is sent to the workstation.
Fig. 4 is a flowchart of the front-end workstation processing the collaboration request message in this embodiment. Taking the following example of setting station jump stop, the following steps are described in detail with reference to fig. 4:
step S301, a workstation monitors a collaboration command REQUEST COOPERATIVE_COMMAN D_REQUEST message in a message thread;
step S302, after receiving the message, the workstation analyzes the current message;
step S303, analyzing the message and checking the authority contained in the message and the workstation sending the collaboration command, if the current workstation has no authority or is the collaboration command sent by the current workstation, not processing the message;
step S304, after analyzing the collaboration command, storing the collaboration command into a collaboration command pool, and refreshing a collaboration command notification button to keep a flashing state;
step S305, when the user observes that the collaboration command button flashes, clicking the collaboration command notification button;
step S306, checking whether a collaboration command needs to be processed currently;
step S307, if the collaboration command needs to be processed, a collaboration command confirmation dialog box is popped up;
step S308, the user knows the currently processed collaboration command through the collaboration command dialog box, and clicks the confirmation after the confirmation is completed;
step S309, the user confirms whether the secondary operation confirmation is needed through the confirmation mode ack_mode in the collaboration command message;
step S310, if the secondary operation is confirmed, the user needs to transact the skip COMMAND again, the workstation judges that the current skip operation is the secondary operation of the collaboration COMMAND according to the collaboration COMMAND pool, and sends an ACK_COOPERATIVE_COMMAND message of the collaboration COMMAND confirmation COMMAND;
step S311, the user clicks the confirmation button of the collaboration COMMAND confirmation dialog box and then sends the collaboration COMMAND confirmation COMMAND ack_collaboration_command message without secondary operation confirmation.
Fig. 5 is a flowchart of a process of generating a collaboration command confirmation message by the background server in the present embodiment. The following steps are described in detail with reference to fig. 5, taking the setting of station jump stop as an example:
step S401, the same as step S101 in fig. 2;
step S402, periodically polling the overtime condition of the preset collaboration command in the CmdBuff, and if the overtime condition exists, clearing the request state, updating the interface display and clearing the CmdBuff cache;
step S403, receiving the ACK message sent by the GPC and analyzing the ACK message;
step S404, judging whether the cooperation command request of the device exists in CmdBuff, if not, directly discarding the message;
step S405, if yes, directly issuing a command to an external interface;
and S406, clearing the request state, updating the interface display, and clearing the CmdBuff cache.
Next, the embodiment also provides a general collaboration command interaction system, which comprises a background server and at least two front-end workstations, wherein the background server and the front-end workstations perform general collaboration command interaction by adopting the method. In addition, the system also supports the reading of configuration files when no cooperative command is required, and ensures the compatibility of the application system on each line.
The universal collaboration command based on the user roles can greatly reduce operation risks caused by single user decision errors. The system has the advantages that a complete operation is needed, different types of user roles are confirmed, meanwhile, a workstation interface gives an obvious prompt, a user can conveniently grasp the current system state in real time, the system operation efficiency is improved, and good guarantee is provided for stable operation of project sites.
The electronic device of the present invention includes a Central Processing Unit (CPU) that can perform various appropriate actions and processes according to computer program instructions stored in a Read Only Memory (ROM) or computer program instructions loaded from a storage unit into a Random Access Memory (RAM). In the RAM, various programs and data required for the operation of the device can also be stored. The CPU, ROM and RAM are connected to each other by a bus. An input/output (I/O) interface is also connected to the bus.
A plurality of components in a device are connected to an I/O interface, comprising: an input unit such as a keyboard, a mouse, etc.; an output unit such as various types of displays, speakers, and the like; a storage unit such as a magnetic disk, an optical disk, or the like; and communication units such as network cards, modems, wireless communication transceivers, and the like. The communication unit allows the device to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processing unit performs the various methods and processes described above, e.g., method S 1 ～S 6 S101 to S108, S201 to S207, S301 to S311, S401 to S406. For example, in some embodiments, method S 1 ～S 6 S101-S108, S201-S207, S301-S311, S401-S406 may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as a storage unit. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device via the ROM and/or the communication unit. When the computer program is loaded into RAM and executed by the CPU, the method S described above may be performed 1 ～S 6 One or more steps of S101 to S108, S201 to S207, S301 to S311, and S401 to S406. Alternatively, in other embodiments, the CPU may be configured to perform method S by any other suitable means (e.g., by means of firmware) 1 ～S 6 、S101～S108、S201～S207、S301～S311、S401～S406。
The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a load programmable logic device (CPLD), etc.
Program code for carrying out methods of the present invention may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.
Claims (12)
1. A method for universal collaboration command interaction, the method comprising:
step S 1 Loading a collaboration command configuration file by a background server and all front-end workstations, and initializing a collaboration command list;
step S 2 Setting a first command requiring specific user role cooperation confirmation on a first front-end workstation by a first user, wherein the first front-end workstation sends a manual operation message containing a command type of the first command to the background server;
step S 3 The background server checks the collaboration command list according to the command type to confirm the collaboration command, and if the collaboration command is confirmed, the background server sends a collaboration command request message to all front-end workstations;
step S 4 After all front-end workstations receive the collaboration command request message, checking whether the original command is sent by the local machine, if so, directly discarding, otherwise, turning to step S 4 Further processing;
step S 5 All front-end workstations check whether the user role mask is matched with the user role logged in by the local machine, if the roles are not matched, the message is directly discarded, otherwise, the cooperative command is prompted to be confirmed;
step S 6 And the front-end workstation with the collaboration command to be confirmed carries out user confirmation based on the confirmation mode of the current collaboration command, and replies the collaboration command confirmation command to the background server after the user confirmation, and the background server further processes the collaboration command confirmation command.
2. The method according to claim 1, wherein said step S 1 The parameters in the collaboration command configuration list include command type, command name, centralized station number, device name, and role of collaboration confirmation userMasking and validation means.
3. The method according to claim 2, wherein said step S 3 Checking a collaboration command list according to the command type to confirm the collaboration command, wherein the method specifically comprises the following steps:
the cooperative confirmation is needed for the command type with the centralized station number and the equipment name empty;
for command types where the centralized station number and device name are not empty, only the commands of a particular device need to be cooperatively acknowledged.
4. The method according to claim 2, wherein said step S 3 The collaboration command request message includes a role mask and a confirmation mode of a collaboration confirmation user corresponding to the first command.
5. The method according to claim 1, wherein said step S 3 When the collaboration command request message is sent to all front-end workstations, starting timing, and when the confirmation message is not received within a set time, clearing the current collaboration command request message and recovering to a pre-operation state.
6. The method for interaction of universal collaboration command as claimed in claim 5 wherein the acknowledgement message is not received within a set time, the current collaboration command request message is cleared and restored to the pre-operation state, specifically: and periodically polling to set a timeout condition of the collaboration command, and if the timeout condition exists, clearing the request state, updating the interface display and recovering to the pre-operation state.
7. The method according to claim 1, wherein said step S 6 The confirmation modes of the collaboration command include a direct confirmation mode and a repeated operation confirmation mode, and specifically include:
if the direct confirmation mode is adopted, the user needs to click on a confirmation dialog box to select acceptance or rejection; and if the repeated operation confirmation mode is adopted, prompting the user to repeatedly operate and issuing a command to be confirmed cooperatively.
8. The method according to claim 1, wherein said step S 6 The background server further processes, specifically: if the confirmation result is refusal, directly discarding the command and clearing the request state; if the result of the confirmation is acceptance, continuing to process the command, and further sending a message to an external interface or notifying other modules.
9. The method according to claim 1, wherein said step S 3 Further comprises: if the non-cooperative command is confirmed, the normal processing is finished after a prompt of successful operation is given.
10. A universal collaboration command interaction system comprising a background server and at least two front-end workstations, the background server and front-end workstations performing universal collaboration command interaction using the method of claim 1.
11. An electronic device comprising a memory and a processor, the memory having stored thereon a computer program, characterized in that the processor, when executing the program, implements the method according to any of claims 1-9.
12. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311549003.6A CN117834667A (en) | 2023-11-20 | 2023-11-20 | Universal collaboration command interaction method, system, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311549003.6A CN117834667A (en) | 2023-11-20 | 2023-11-20 | Universal collaboration command interaction method, system, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117834667A true CN117834667A (en) | 2024-04-05 |
Family
ID=90519819
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311549003.6A Pending CN117834667A (en) | 2023-11-20 | 2023-11-20 | Universal collaboration command interaction method, system, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117834667A (en) |
-
2023
- 2023-11-20 CN CN202311549003.6A patent/CN117834667A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108537897B (en) | Parking lot parking charge management method, server and storage medium | |
| CN103677946A (en) | Method and system for updating elevator device control programs | |
| CN110895606B (en) | Internal system management method and device suitable for newly-built account and storage medium | |
| WO2023109500A1 (en) | Train formation management method and apparatus, device, and medium | |
| CN111080390B (en) | Order information modification method, system, equipment and storage medium | |
| CN106056436A (en) | Data fallback method, device and system | |
| CN117834667A (en) | Universal collaboration command interaction method, system, equipment and medium | |
| CN112172876A (en) | Cross-station route arranging method and system for distributed self-discipline dispatching centralized station | |
| CN115865613A (en) | Basic environment fault processing method and device | |
| CN105790975A (en) | Service processing operation execution method and device | |
| CN115080775A (en) | Access control equipment face data storage method and device, server and storage medium | |
| CN111680279B (en) | Login verification method, device and system | |
| CN113162819A (en) | Joint debugging method and device for 10kV pole-mounted switch complete equipment and storage medium | |
| JP2002032101A (en) | Work management system for railway facility | |
| CN116996572B (en) | Proxy node balancing method, system, terminal and storage medium | |
| CN116238565A (en) | Method, equipment and medium for transmitting route forecast information to vehicle-mounted equipment by TSRS (traffic control system) | |
| CN116995671B (en) | Quick power failure maintenance method, device and equipment for power grid and storage medium | |
| CN116811966A (en) | Method and equipment for optimizing trigger time of subway train passenger-clearing broadcast signals | |
| CN113010225B (en) | Automatic loading method and system for configuration files of intelligent substation | |
| CN111338824B (en) | Gray release method and device, electronic equipment and storage medium | |
| CN115904764B (en) | Version management method and device for wireless block center | |
| CN112202604B (en) | Emergency configuration method, device and system of electric power monitoring safety system switch | |
| CN114291135B (en) | Switch safety control method, equipment and medium with multiple confirmation mechanisms | |
| CN116208491A (en) | Cloud resource configuration updating method, system, change node, electronic equipment and medium | |
| CN114331768A (en) | Automatic map-based vehicle distribution method and device for rail transit signal simulation training system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |