A multi-screen cooperative control method for war readiness shift

Abstract

The application discloses a kind of multi-screen cooperative control methods for war readiness shift, belong to multi-screen linkage technical field.The application is grouped to screen and is configured to report page, establishes the association of each report page and each screen group, then according to the configuration information of report page and the operation instruction sent by report end realizes the cooperative control of multiple screens;The application uniformly configures screen device and the display content of device in report end, more convenient, safe;The application designs screen grouping strategy, under the premise of guaranteeing that multiple report pages are simultaneously displayed by split screen at the same time, the efficiency of configuration is significantly improved;The application provides page preloading mechanism, and controlled screen pre-caches page content according to report page order, even in the case that page content is too large or short network jitter occurs, the fluency of report can still be guaranteed.

Description

Technical Field

[0001] The present invention relates to the field of multi-screen linkage technology, and more specifically to a multi-screen collaborative control method for combat readiness handover. Background Art

[0002] Combat readiness handover is a very important task in daily duty. The combat readiness duty situation of one day, one week or one month is reported to the superiors, cooperative units and the next duty team in the form of a report. The report content includes situation introduction (text), statistical charts, system screenshots and situation information such as air situation, sea situation, command and communication presented by the duty system. Normally, a report requires a main reporter and multiple duty personnel to work together to display the relevant content on the large screen by manually switching the signal source. The above method has high requirements for personnel coordination, and it is often the case that the screen switching is not timely or even errors occur.

[0003] To address this frequently occurring situation, Chinese patent application "CN117008862A: A Multi-screen Linkage Data Display Method, Apparatus, Equipment, and Storage Medium" provides a multi-screen linkage data display method, apparatus, equipment, and storage medium for use in a multi-screen linkage data display system. The method involves establishing connections between the gateway layer and the master control terminal, and between the gateway layer and the controlled terminals, and saving the connection information. When the master control terminal switches scene pages, it generates a scene switching instruction and controls multiple controlled terminals to access the scene homepage. When multiple controlled terminals need to display business data, the data is retrieved and displayed from the server based on the connection information.

[0004] However, if the data to be displayed is too large or there is network jitter, the controlled terminal screen will experience delays, affecting the display effect. In addition, the above patent configures linkage codes for each controlled terminal to bring the controlled terminal under the control of the master terminal. When there are many controlled terminals, the configuration work will be very complicated.

[0005] Therefore, how to provide a multi-screen collaborative control method for combat readiness handover scenarios, connect the splicing screens and projectors on the walls of the duty environment, the lifting screens on the conference tables, and the monitors on the duty seats and other devices together to work together, and simply and smoothly realize the synchronous playback, split-screen display and interactive control of the content, and improve the quality and efficiency of combat readiness handover is a problem that technical personnel in this field urgently need to solve. Summary of the Invention

[0006] In view of this, the purpose of the present invention is to provide a multi-screen collaborative control method for combat readiness handover.

[0007] In order to achieve the above object, the present invention adopts the following technical solutions:

[0008] A multi-screen collaborative control method for combat readiness handover includes the following steps:

[0009] S1: Grouping the screens according to the combat readiness handover report requirements to obtain a number of screen groups; wherein the screens in the same screen group display the same report page; and the screens in different screen groups display the same or different report pages;

[0010] S2: Configure each report page and establish the association between each report page and each screen group;

[0011] S3: The reporting terminal checks whether all screens are ready. If they are, the shift report task is started. The reporting terminal automatically generates a start playback operation instruction and sends it to the collaborative server;

[0012] The collaborative server sends the start-play operation instruction to all screens;

[0013] After receiving the start-play operation instruction, each screen transfers the screen control right to the reporting terminal; and automatically downloads the configuration information of all reporting pages associated with the screen group to which it belongs; and preloads the page content according to the configuration information;

[0014] S4: The reporting terminal sends the real-time page operation instructions to the collaborative server;

[0015] The collaborative server sends the page operation instruction to the designated screen group in the page operation instruction;

[0016] After receiving the page operation instruction, each screen in the designated screen group performs the page operation behavior corresponding to the page operation instruction;

[0017] S5: Repeat S4 until the reporting end completes the shift report, and then execute S6;

[0018] S6: The reporting terminal automatically generates a stop playback operation instruction and sends it to the collaborative server;

[0019] The collaborative server sends the stop playback operation instruction to all screens;

[0020] After receiving the stop playback operation instruction, each screen takes back the screen control right and displays the screen content before the shift report.

[0021] Preferably, the configuration information of the report page includes: page identification, page serial number, page type, page address, page display and screen group number;

[0022] The page identifier represents a unique identifier for distinguishing each report page; wherein, the page identifier is represented by a UUID;

[0023] The page serial number indicates the reporting order of each report page; wherein, during the shift report process, the report pages with the same serial number at the same time are displayed simultaneously on different screens;

[0024] The page type indicates the type of the report page; wherein the page type includes text, page, picture, and audio and video;

[0025] The page address represents the URL address corresponding to the report page;

[0026] The page display indicates screen display properties; wherein the page display includes whether it is full screen, width, height, left margin, and top margin;

[0027] The screen group number indicates the group number of the screen group on which the report page needs to be displayed.

[0028] Preferably, the start play operation instruction, the page operation instruction and the stop play operation instruction all include an operation screen group number, an operation type, an operation page identifier and an event;

[0029] The operation screen group number is used to specify the screen group that receives the operation instruction; wherein, the operation screen group number is an array, and the elements in the array are the group numbers of the screen groups; when the array is empty, it means that the operation instruction is sent to all screens; when the array is not empty, it means that the operation instruction is sent to the screen group corresponding to the group number;

[0030] The operation type indicates the type of the operation instruction; wherein the operation type includes a start play operation instruction, a page operation instruction, and a stop play operation instruction;

[0031] The operation page identifier indicates the page identifier of the report page operated by the operation instruction; wherein, when the operation type is a start play operation instruction and a stop play operation instruction, it is meaningless; when the operation type is a page operation instruction, the operation page identifier indicates the page identifier of the report page operated by the page operation instruction;

[0032] The event is used to indicate a specific page operation behavior.

[0033] Preferably, the event includes an event type, a key combination, coordinates, a key, and a direction; wherein the event type includes a mouse event and a keyboard event; the key combination indicates whether the Ctrl, Alt, and Shift keys are pressed; the coordinates indicate the X coordinate and Y coordinate of the mouse; the key indicates the keyboard key and mouse key actually pressed; and the direction indicates the direction of the key.

[0034] Preferably, S3 specifically includes:

[0035] When each screen is started, the agent software embedded in the screen automatically sends screen-related information to the collaborative server; the screen-related information includes screen status and screen parameters;

[0036] The collaborative server receives the screen-related information and sends the screen-related information bound to the handover record to the reporting terminal. After the reporting terminal detects that all screens are ready, it prompts the reporting personnel to start the combat readiness handover report.

[0037] Preferably, S3 specifically further includes:

[0038] After receiving the start-play operation instruction, each screen automatically downloads the configuration information of all report pages associated with the screen group to which it belongs; and at the same time preloads the page content specified by the page address according to the page play sequence.

[0039] Preferably, the page operation instructions include page switching instructions and mouse and keyboard operation instructions.

[0040] Preferably, the screen parameters include the screen model, resolution, DPI and refresh rate.

[0041] Preferably, the entity formed by encapsulating the mouse operation and keyboard operation of the reporting end is sent to the corresponding screen according to the screen group number in the form of an event stream.

[0042] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the multi-screen collaborative control method for combat readiness handover described above is implemented.

[0043] It can be seen from the above technical solutions that, compared with the prior art, the present invention discloses a multi-screen collaborative control method for combat readiness handover, which can achieve the following beneficial technical effects:

[0044] 1) The present invention uniformly configures the screen device and the display content of the device at the reporting end, which is more convenient and safer;

[0045] 2) The present invention designs a screen grouping strategy, which significantly improves the configuration efficiency while ensuring that multiple report pages can be displayed simultaneously on the screen at the same time;

[0046] 3) The present invention provides a page preloading mechanism, and the controlled screen caches the page content in advance according to the report page order. Even if the page content is too large or there is a short network jitter, the smoothness of the report can still be guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0048] Figure 1 A flowchart of a multi-screen collaborative control method for combat readiness handover provided by the present invention;

[0049] Figure 2 A schematic diagram showing a key combination provided in an embodiment of the present invention using one byte;

[0050] Figure 3 A schematic diagram of an electronic device provided by the present invention. DETAILED DESCRIPTION

[0051] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0052] like Figure 1 As shown, the embodiment of the present invention discloses a multi-screen collaborative control method for combat readiness handover, including the following steps:

[0053] S1: Grouping the screens according to the combat readiness handover report requirements to obtain a number of screen groups; wherein the screens in the same screen group display the same report page; and the screens in different screen groups display the same or different report pages;

[0054] S2: Configure each report page and establish the association between each report page and each screen group;

[0055] S3: The reporting terminal checks whether all screens are ready. If they are, the shift report task is started. The reporting terminal automatically generates a start playback operation instruction and sends it to the collaborative server;

[0056] Furthermore, when each screen is started, the agent software embedded in the screen automatically sends screen-related information to the collaborative server; wherein the screen-related information includes screen status (the screen status includes normal, offline and fault) and screen parameters (the screen parameters include screen model, resolution, DPI and refresh rate);

[0057] The collaborative server receives the screen-related information and sends the screen-related information (screen status and screen parameters) bound to the handover record to the reporting terminal. After the reporting terminal detects that all screens are ready, it prompts the reporting personnel to start the combat readiness handover report.

[0058] The collaborative server sends the start-play operation instruction to all screens;

[0059] After receiving the start-play operation instruction, each screen transfers the screen control right to the reporting terminal; and automatically downloads the configuration information of all reporting pages associated with the screen group to which it belongs; and preloads the page content according to the configuration information;

[0060] Furthermore, after each screen receives the start playback operation instruction, it automatically downloads the configuration information of all reporting pages associated with the screen group to which it belongs; at the same time, it preloads the page content specified by the page address according to the page playback order (during the download process, the screen feeds back the download status to the reporting end through the collaborative server).

[0061] Furthermore, the configuration information of the report page includes: page identification (ID), page sequence number (Index), page type (Type), page address (Address), page display (Display) and screen group number (GroupNo);

[0062] The page identifier represents a unique identifier for distinguishing each report page; wherein, the page identifier is represented by a UUID;

[0063] The page serial number indicates the reporting order of each report page; wherein, during the shift report process, the report pages with the same serial number at the same time are displayed simultaneously on different screens;

[0064] The page type indicates the type of the report page; wherein the page type includes text (Text), page (Page), picture (Image) and audio and video (Video);

[0065] It can be understood that: Text means formatted text;

[0066] Page refers to the page of the software system that actually performs the duty task, such as an early warning system;

[0067] Image refers to images related to the shift handover, such as situational maps, system screenshots, etc.

[0068] Video refers to recorded audio and video files.

[0069] The page address represents the URL address corresponding to the report page;

[0070] It is understandable that: the report page is created by a page creation tool; each report page corresponds to a unique URL address (for example, http: / / ip:port / text / page-1), and the URL address is generated during the creation process of the report page.

[0071] The page display indicates screen display properties; wherein the page display includes whether it is full screen (FullScreen), width (Width), height (Height), left margin (Left), and top margin (Top);

[0072] The screen group number indicates the group number of the screen group on which the report page needs to be displayed.

[0073] It can be understood that: the screen group number is in array form, and the elements in the array are groups of screen groups. A reporting page can be displayed on multiple screen groups at the same time, and a screen group can only display the same page. When the screen starts, the implanted agent software automatically reports the screen status (including normal, offline and faulty) and screen parameters (including screen model, resolution, DPI, refresh rate, etc.). When specifying the screen to display on the reporting page, the reporter needs to refer to the screen parameter information to improve the effect of the shift report.

[0074] It is understandable that configuration information can be identified in JSON format. In a certain shift report, the configuration information of two report pages is as follows:

[0075]

[0076] GroupNo:[1,3] (indicates that the report page with ID 3e1ad7e6-a412-11ef-8275-5547dd713830 needs to display the screen groups with group numbers 1 and 3)

[0077]

[0078]

[0079] GroupNo:[1,2] (indicates that the report page with ID 4e41f928-a412-11ef-8275-5547dd713830 needs to display the screen groups with group numbers 1 and 2)

[0080] } ]

[0082] S4: The reporting terminal sends the real-time page operation instructions to the collaborative server;

[0083] It is understandable that if the reporting terminal switches the reporting page, or performs corresponding mouse and keyboard operations on the reporting page, the reporting terminal automatically generates corresponding page operation instructions.

[0084] The collaborative server sends the page operation instruction to the designated screen group in the page operation instruction;

[0085] After receiving the page operation instruction, each screen in the designated screen group performs the page operation behavior (such as page switching, mouse click, keyboard release, etc.) corresponding to the page operation instruction.

[0086] S5: Repeat S4 until the reporting end completes the shift report, and then execute S6;

[0087] S6: The reporting terminal automatically generates a stop playback operation instruction and sends it to the collaborative server;

[0088] The collaborative server sends the stop playback operation instruction to all screens;

[0089] After receiving the stop playback operation instruction, each screen takes back the screen control right and displays the screen content before the shift report.

[0090] Furthermore, the start play operation instruction, the page operation instruction and the stop play operation instruction each include an operation screen group number (GroupNo), an operation type (Type), an operation page identifier (PageId) and an event (Event);

[0091] The operation screen group number is used to specify the screen group that receives the operation instruction; wherein, the operation screen group number is an array, and the elements in the array are the group numbers of the screen groups; when the array is empty, it means that the operation instruction is sent to all screens; when the array is not empty, it means that the operation instruction is sent to the screen group corresponding to the group number;

[0092] The operation type indicates the type of the operation instruction; wherein the operation type includes a start play operation instruction, a page operation instruction, and a stop play operation instruction;

[0093] Furthermore, the page operation instructions include page switching instructions and mouse and keyboard operation instructions.

[0094] The start playback operation instruction, page switching instruction, mouse and keyboard operation instruction, and stop playback operation instruction in the operation instructions are represented by 0, 1, 2, and 3 respectively.

[0095] The operation page identifier indicates the page identifier of the report page operated by the operation instruction; wherein, when the operation type is a start play operation instruction and a stop play operation instruction, it is meaningless; when the operation type is a page operation instruction, the operation page identifier indicates the page identifier of the report page operated by the page operation instruction;

[0096] The event is used to represent a specific page operation behavior; the present invention encapsulates the entity formed by the mouse operation and keyboard operation of the reporting end, and sends it to the corresponding screen according to the screen group number in the form of an event stream.

[0097] Furthermore, the event includes an event type (Type), a combination key (ComposeKey), a coordinate (Coordinate), a key (Key) and a direction (Direction);

[0098] The event types include mouse events (MouseEvent) and keyboard events (KeyboardEvent); wherein, mouse events are represented by 0 and keyboard events are represented by 1.

[0099] The key combination indicates whether the Ctrl, Alt and Shift keys are pressed; it is represented by the last three digits of a byte, such as Figure 2 As shown, where X takes the value of 0 or 1, 0 indicates not pressed, and 1 indicates pressed.

[0100] The coordinates represent the X and Y coordinates of the mouse;

[0101] The keys represent the keyboard keys and mouse keys that are actually pressed; keyboard keys are represented by positive numbers, which are consistent with the ASCII codes of the corresponding keys; mouse keys are represented by negative numbers, -1 represents the left key, -2 represents the right key, -3 represents the middle key, and -4 represents the middle key scroll.

[0102] The direction represents the direction of the key; where 0 represents pressing, 1 represents releasing, 2 represents scrolling the middle mouse button up, and 3 represents scrolling the middle mouse button down.

[0103] It is understood that: the operation instructions can be identified in JSON format;

[0104] In a certain shift report, the page operation instructions are as follows:

[0105]

[0106] It can be understood that: when the operation instruction is a start play operation instruction: GroupNo: []; Type: 0; when the operation instruction is a stop play operation instruction: GroupNo: []; Type: 3.

[0107] The embodiment of the present invention also discloses a schematic diagram of the physical structure of an electronic device, such as Figure 3 As shown, the electronic device may include: a processor 301, a communication interface 302, a memory 303, and a communication bus 304, wherein the processor 301, the communication interface 302, and the memory 303 communicate with each other via the communication bus 304. The processor 301 can call the logic instructions in the memory 303 to execute the above-mentioned multi-screen collaborative control method for combat readiness handover.

[0108] In addition, the logic instructions in the above-mentioned memory 303 can be implemented in the form of a software functional unit and sold or used as an independent product, and can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the embodiment of the present invention. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0109] On the other hand, an embodiment of the present invention also provides a computer program product, which includes a computer program. The computer program can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the above-mentioned multi-screen collaborative control method for combat readiness handover.

[0110] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Reference can be made to the common and similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method description.

[0111] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A multi-screen collaborative control method for combat readiness handover, characterized in that: The following steps are involved: S1: Grouping the screens according to the combat readiness handover report requirements to obtain a number of screen groups; wherein the screens in the same screen group display the same report page; and the screens in different screen groups display the same or different report pages; S2: Configure each report page and establish the association between each report page and each screen group; S3: The reporting terminal checks whether all screens are ready. If they are, the shift report task is started. The reporting terminal automatically generates a start playback operation instruction and sends it to the collaborative server; The collaborative server sends the start-play operation instruction to all screens; After receiving the start-play operation instruction, each screen transfers the screen control right to the reporting terminal; and automatically downloads the configuration information of all reporting pages associated with the screen group to which it belongs; and preloads the page content according to the configuration information; The configuration information of the report page includes: page identification, page sequence number, page type, page address, page display and screen group number; The page identifier represents a unique identifier for distinguishing each report page; wherein, the page identifier is represented by a UUID; The page serial number indicates the reporting order of each report page; wherein, during the shift report process, the report pages with the same serial number are displayed simultaneously on different screens at the same time; The page type indicates the type of the report page; wherein the page type includes text, page, picture, and audio and video; The page address represents the URL address corresponding to the report page; The page display indicates screen display properties; wherein the page display includes whether it is full screen, width, height, left margin, and top margin; The screen group number indicates the group number of the screen group on which the report page needs to be displayed; S4: The reporting terminal sends the real-time page operation instructions to the collaborative server; The collaborative server sends the page operation instruction to the designated screen group in the page operation instruction; After receiving the page operation instruction, each screen in the designated screen group performs the page operation behavior corresponding to the page operation instruction; S5: Repeat S4 until the reporting end completes the shift report, and then execute S6; S6: The reporting terminal automatically generates a stop playback operation instruction and sends it to the collaborative server; The collaborative server sends the stop playback operation instruction to all screens; After receiving the stop playback operation instruction, each screen takes back the screen control right and displays the screen content before the shift report.

2. The multi-screen collaborative control method for combat readiness handover according to claim 1 is characterized in that: The start play operation instruction, the page operation instruction and the stop play operation instruction all include an operation screen group number, an operation type, an operation page identifier and an event; The operation screen group number is used to specify the screen group that receives the operation instruction; wherein, the operation screen group number is an array, and the elements in the array are the group numbers of the screen groups; when the array is empty, it means that the operation instruction is sent to all screens; when the array is not empty, it means that the operation instruction is sent to the screen group corresponding to the group number; The operation type indicates the type of the operation instruction; wherein the operation type includes a start play operation instruction, a page operation instruction, and a stop play operation instruction; The operation page identifier indicates the page identifier of the report page operated by the operation instruction; wherein, when the operation type is a start play operation instruction and a stop play operation instruction, it is meaningless; when the operation type is a page operation instruction, the operation page identifier indicates the page identifier of the report page operated by the page operation instruction; The event is used to indicate a specific page operation behavior.

3. The multi-screen collaborative control method for combat readiness handover according to claim 2 is characterized in that: The event includes an event type, a key combination, coordinates, a key, and a direction; wherein the event type includes a mouse event and a keyboard event; the key combination indicates whether the Ctrl, Alt, and Shift keys are pressed; the coordinates indicate the X coordinate and Y coordinate of the mouse; the key indicates the keyboard key and mouse button actually pressed; and the direction indicates the direction of the key.

4. The multi-screen collaborative control method for combat readiness handover according to claim 3 is characterized in that: S3 specifically includes: When each screen is started, the agent software embedded in the screen automatically sends screen-related information to the collaborative server; the screen-related information includes screen status and screen parameters; The collaborative server receives the screen-related information and sends the screen-related information bound to the handover record to the reporting terminal. After the reporting terminal detects that all screens are ready, it prompts the reporting personnel to start the combat readiness handover report.

5. The multi-screen collaborative control method for combat readiness handover according to claim 3 is characterized in that: S3 specifically includes: After receiving the start-play operation instruction, each screen automatically downloads the configuration information of all report pages associated with the screen group to which it belongs; and at the same time preloads the page content specified by the page address according to the page play sequence.

6. The multi-screen collaborative control method for combat readiness handover according to claim 2 is characterized in that: The page operation instructions include page switching instructions and mouse and keyboard operation instructions.

7. The multi-screen collaborative control method for combat readiness handover according to claim 4 is characterized in that: The screen parameters include the screen model, resolution, DPI and refresh rate.

8. The multi-screen collaborative control method for combat readiness handover according to claim 3 is characterized in that: The entity formed by encapsulating the mouse operations and keyboard operations of the reporting end is sent to the corresponding screen according to the screen group number in the form of an event stream.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the multi-screen collaborative control method for combat readiness handover according to any one of claims 1 to 8 is implemented.

Images