A human-computer interaction method and system suitable for a plan market application scenario

Abstract

The application discloses a kind of man-machine interaction method and system suitable for plan market application scene, comprising: according to the configuration data request of editing information;Determine whether data request is general data request or application data request, if general data request, by platform unified query service module directly response, the data transmission of response is shown to man-machine cloud terminal;If it is application data request, then judge service scheduling mode is request message distribution mode or request service calling mode, according to the corresponding request message, it is data query function or picture number or command line calling function, according to the function of judging response result, return to man-machine request scheduling service module, again by man-machine request scheduling service module return to man-machine cloud terminal and show.Occupation: under the guarantee that man-machine back-end service can respond to different data type request of front end, the target of lightweight client, picture display editing flexibility and expansion is realized.

Description

Technical Field

[0001] This invention relates to a human-computer interaction method and system adapted to planned market application scenarios, belonging to the field of human-computer interaction technology for scheduling automation systems. Background Technology

[0002] To adapt to the integrated operation characteristics of modern power grids, automated dispatch control systems for dispatching applications have emerged. Human-machine cloud terminals, serving as tools for dispatchers to browse power grid-related information, are a crucial component of the new system. They can access information such as the overall network basic model, real-time operating conditions, analytical decision results, and statistical data, providing dispatchers with a user-friendly human-machine interaction method. Planning and market-based scenarios primarily involve developing optimized operation plans covering the entire lifecycle—yearly, monthly, weekly, day-ahead, and intraday—based on load and renewable energy forecasts. Their human-machine interaction requirements include the ability to visualize initial planning data, unit and tie-line planning results, and planned power flow distribution, as well as the ability to flexibly and conveniently edit planning strategies, basic data, and planning results, including single-point, batch, and graphical modifications.

[0003] Existing human-computer interaction mechanisms in scheduling automation systems are ineffective at displaying planning data across different periods in planned market application scenarios. Furthermore, they suffer from high front-end and back-end coupling, resulting in bloated and inflexible clients that cannot support flexible editing, display, and expansion of various data types, and place high demands on the configuration of the display terminal. Therefore, designing a human-computer interaction mechanism that adapts to the visualization requirements of planned market application scenarios—namely, a lightweight client and flexible display and editing—is particularly important. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to overcome the defects of the prior art and provide a human-computer interaction method and system that is suitable for planned market application scenarios, so that the client and the server can focus on their respective business needs, with high cohesion and low coupling, and better realize the division of labor and communication and cooperation.

[0005] To address the aforementioned technical problems, this invention provides a human-computer interaction method adapted to planned market application scenarios, comprising:

[0006] Input editing information through the human-machine cloud terminal, and configure data requests based on the editing information;

[0007] The human-machine interface server determines whether the data request is a general data request or an application data request.

[0008] If it is a general data request, the unified query service module of the human-machine server platform will respond directly and transmit the response data to the human-machine cloud terminal for display.

[0009] If it is an application data request, it is parsed by the human-machine request scheduling service module of the human-machine server. Based on the parsing result, it determines whether the service scheduling method is request message distribution or request service invocation. Based on the determination result, it generates a corresponding request message and submits it to the human-machine request application service module of the human-machine server. The human-machine request application service module determines whether it is a data query function, screen data setting, or command line invocation function based on the corresponding request message. Based on the determination of the function, it generates a response result and returns it to the human-machine request scheduling service module. Finally, the human-machine request scheduling service module returns it to the human-machine cloud terminal for display.

[0010] Furthermore, the request message distribution method is to broadcast the application data request through the message bus. The broadcast message transmission data method is the protobuf protocol. The screen setting or command line call function adopts the request message distribution method. After the human-machine request application service module listens for the broadcast data request, it responds and returns the processing result.

[0011] The requested service invocation method involves making targeted service invocations through the service bus based on the data type of the application data request. The data interaction method between services is the protobuf protocol. The functions of horizontal table query, sensitivity query, and tree structure data query adopt the requested service invocation method. After receiving the data request transmitted through the service bus, the human-machine request application service module performs response processing and returns the processing result.

[0012] Furthermore, the data types of the application data requests include:

[0013] A horizontal table query is a request type for retrieving load, renewable energy forecasts, power generation plans, unit regulation ranges, and tie-line plans within a certain time range.

[0014] Screen data setting refers to the request type for modifying data on the human-machine interface of the human-machine cloud terminal and saving it to the database;

[0015] Command line invocation refers to the request type used by the human-machine interface of a human-machine cloud terminal to invoke terminal commands in the background.

[0016] Sensitivity query is a request type for querying sensitivity data of cross-sections, lines, transformers, and generator sets.

[0017] Tree structure query is a request type for querying tree graph structure data.

[0018] A human-computer interaction system adapted to planned market application scenarios includes:

[0019] The input module is used to input editing information through the human-machine cloud terminal and configure data requests based on the editing information;

[0020] The determination module is used to determine whether a data request is a general data request or an application data request through the human-machine interface server.

[0021] If it is a general data request, the unified query service module of the human-machine server platform will respond directly and transmit the response data to the human-machine cloud terminal for display.

[0022] If it is an application data request, it is parsed by the human-machine request scheduling service module of the human-machine server. Based on the parsing result, it determines whether the service scheduling method is request message distribution or request service invocation. Based on the determination result, it generates a corresponding request message and submits it to the human-machine request application service module of the human-machine server. The human-machine request application service module determines whether it is a data query function, screen data setting, or command line invocation function based on the corresponding request message. Based on the determination of the function, it generates a response result and returns it to the human-machine request scheduling service module. Finally, the human-machine request scheduling service module returns it to the human-machine cloud terminal for display.

[0023] Furthermore, the determining module includes:

[0024] The broadcast communication module is used to determine the request message distribution method, which is to broadcast the application data request through the message bus. The broadcast message transmission data method is the protobuf protocol. The screen setting or command line call function adopts the request message distribution method. After the human-machine request application service module listens for the broadcast data request, it performs response processing and returns the processing result.

[0025] The bus communication module is used to determine the service call method based on the data type of the application data request and to make a targeted service call through the service bus. The data interaction method between services is the protobuf protocol. The horizontal table query, sensitivity query and tree structure data query functions adopt the aforementioned service call method. After receiving the data request transmitted through the service bus, the human-machine request application service module performs response processing and returns the processing result.

[0026] Furthermore, the determining module includes a data type determining module, used to determine the data type of the application data request as follows:

[0027] A horizontal table query indicates a request type for retrieving load, renewable energy forecasts, power generation plans, unit regulation ranges, and tie-line plans within a certain time range.

[0028] The "screen setting" option indicates the request type for modifying data on the human-machine interface of the human-machine cloud terminal and saving it to the database.

[0029] Command line call indicates the type of request from the human-machine interface of the human-machine cloud terminal to call terminal commands in the background;

[0030] Sensitivity query indicates the type of request for sensitivity data of cross-sections, lines, transformers, and generator sets.

[0031] Tree structure query indicates the type of request that queries tree graph structure data.

[0032] The beneficial effects achieved by this invention are as follows:

[0033] This invention is based on a microservice-based client / server architecture. Following the principle of lightweight client design, the client only handles data requests and display, while data querying and request processing are handled by the backend service. To accommodate both general and application-specific data requests from the frontend interface, the corresponding backend service is divided into a unified platform query service and a human-computer request application service. While ensuring that the human-computer backend service can respond to different data type requests from the frontend, the invention achieves the goals of a lightweight client, flexible and scalable screen display and editing. Attached Figure Description

[0034] Figure 1 This is a diagram of the existing human-computer interaction architecture.

[0035] Figure 2 This is a diagram illustrating the human-computer interaction mechanism architecture for planned market application scenarios of the present invention.

[0036] Figure 3 This is a diagram illustrating the JSON message format.

[0037] Figure 4 This is a schematic diagram of the request message format for a protobuf message;

[0038] Figure 5 This is a schematic diagram of the protobuf response message format;

[0039] Figure 6 This is a diagram illustrating the JSON response message format. Detailed Implementation

[0040] The present invention will be further described below with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and should not be used to limit the scope of protection of the present invention.

[0041] like Figure 1 As shown, the human-computer interaction backend service provides unified services to the human-computer client through a service bus and a message bus. It also interacts with modules such as data access interfaces and platform management, providing a general human-computer interaction mechanism. Within the scheduling automation system, the human-computer interaction service serves as the platform's unified query service. However, based on the visualization requirements of planned market scenarios, this service cannot meet all data display and editing needs.

[0042] like Figure 2As shown, a human-computer interaction method adapted to planned market application scenarios first inherits the architecture of a general human-computer interaction mechanism. Based on the different data types displayed by the application, for data types that cannot be obtained by the platform's unified query service and certain specific functional requests, an application-layer human-computer interaction service is added to handle these requests. The overall design is as follows: Figure 2 As shown.

[0043] (1) When the human-computer interaction client refreshes the page in the browser, it submits a page data refresh request to the human-computer interaction server at the platform layer via a JSON message. However, when the editor is drawing the screen, the request parameters configured in the data source need to specify whether it is accessing the platform's unified query service or calling the application layer's human-computer interaction service, i.e., whether the data type is a general data request or an application data request.

[0044] (2) General data requests are directly responded to by the platform's unified query service. Application data requests are first submitted to the human-machine request scheduling service. After parsing the request message, the service performs necessary parameter verification, determines whether the service scheduling method is request message distribution or request service invocation based on the request type, and then submits the application layer human-machine request application service through protobuf message.

[0045] (3) The application layer human-machine request application service determines whether it is a data query function or other special function based on the request message parameters, and then returns the response result to the human-machine request scheduling service, which then returns it to the front-end interface.

[0046] (4) The request message distribution method broadcasts the data request through the message bus, while the request service call method makes a targeted service call through the service bus based on the request parameters.

[0047] Based on the type of application data query and special functional requirements, application data request types can be divided into: horizontal table query, screen data setting, command line call, sensitivity query, tree structure query, etc.

[0048] (1) Horizontal table lookup: The lookup table structure is as follows Figure 3 The data types shown primarily include load, renewable energy forecasts, power generation plans, and tie-line plans over a specific period. For example, within a single day, real-time power generation plans are displayed at 5-minute intervals, totaling 288 data points; while day-ahead power generation plans are displayed at 15-minute intervals, totaling 96 data points. Load and renewable energy forecast data are similar.

[0049] (2) Screen data setting: Modify data in the human-computer interface and save it to the database.

[0050] (3) Command line call: The human-machine interface enables the invocation of terminal commands in the background.

[0051] (4) Sensitivity query: Query the sensitivity data of equipment such as cross sections, lines and generator sets.

[0052] (5) Tree structure query: Query data with a tree graph structure. The tree structure data structure is as follows: Figure 4 As shown.

[0053] To ensure rational planning of backend services and improve service response efficiency and scalability, it is necessary to functionally divide frontend data requests according to business needs. The planning market-related human-machine request service functions are divided into general functions and service access functions. General functions refer to operation responses applied to various sub-scenarios within the planning market, such as setting data on screens and command-line calls; service access functions are applied to operation responses for specific business data, such as horizontal table queries, sensitivity data queries, tree structure queries, intelligent management of planned values, and economic model management.

[0054] The following is an implementation example of the present invention, illustrating the entire process of data request and response for the horizontal table query function. The following embodiments are only used to more clearly illustrate the technical solution of the present invention and should not be construed as limiting the scope of protection of the present invention.

[0055] When refreshing data, the browser on the human-machine interface client sends a request to the backend service of the human-machine interface in JSON format. The JSON message format is as follows: Figure 3 As shown,

[0056] Where op_type is the function number for horizontal table lookup; scn_name, scn_inst, sub_scn_name, and sub_scn_inst are application scenario parameters; table_no is the table number being queried; precision is the numerical precision; field_prefix is ​​a special domain name prefix; field_time is a special date domain name; and wheres are the search conditions, which include the primary key information of the table being queried.

[0057] To facilitate the differentiation of service types in the program, function numbers are used to distinguish different request types.

[0058] (1) 1~999: General function numbers, with message distribution (message bus) as the main scheduling method. For example, the function number for setting data on the main and backup machine screens is 1, and the function number for calling the command line host is 20.

[0059] (2) 1000~999999: Service access function number. The scheduling method is mainly based on service invocation. It is divided into service number and operation number. The lower 3 bits are the operation number and the rest are the service number. That is, the service number range is 1~999 and the operation number range is 0~999. For example, the function number of real-time database horizontal table query is 1000 and the function number of line to specified unit sensitivity query is 1100.

[0060] Since horizontal table lookups fall under the category of data request functions in planned market applications, the response is handled by the human-machine request scheduling service deployed on the human-machine server. The human-machine request scheduling service interacts with the human-machine request application service using protobuf messages, with the request message format as follows: Figure 4 As shown,

[0061] The human-machine request application service, deployed on the application server, processes data requests submitted by the human-machine request scheduling service, executes corresponding business operations, and feeds back the results to the human-machine request scheduling service. Considering the future increase in the types of human-machine application services and the issue of concurrent request processing, and to improve the service's scalability and flexibility, the human-machine request application service is divided into processing based on business characteristics. To avoid excessive programs, business processes are distinguished using command-line parameters (service tags), with each process handling a specific type of service request. Based on the application data request type, the human-machine request application service can be temporarily divided into basic services, sensitivity query services, economic model management services, and planned value management services, etc.

[0062] (1) Basic services: mainly handle screen operation or data query requests, including screen data setting, command line calls and horizontal table queries, etc.

[0063] (2) Sensitivity query service: Equipment sensitivity query related services

[0064] (3) Economic model management services: Operational services related to economic model management

[0065] (4) Planned Value Management Service: Operational services related to intelligent management of planned values

[0066] The protobuf response message format for human-machine requests to application services is as follows: Figure 5 As shown, after obtaining the response result, the human-machine request scheduling service sends it back to the client in JSON format. This serves as a bridge between the preceding and following steps in the entire data request and response process. The JSON response message format is as follows: Figure 6 As shown.

[0067] After acquiring the data, the human-machine client displays it visually according to the requirements. At this point, the human-machine interaction process for responding to a horizontal table query data request is complete.

[0068] Accordingly, the present invention also provides a human-computer interaction system adapted to planned market application scenarios, comprising:

[0069] The input module is used to input editing information through the human-machine cloud terminal and configure data requests based on the editing information;

[0070] The determination module is used to determine whether a data request is a general data request or an application data request through the human-machine interface server.

[0071] If it is a general data request, the unified query service module of the human-machine server platform will respond directly and transmit the response data to the human-machine cloud terminal for display.

[0072] If it is an application data request, it is parsed by the human-machine request scheduling service module of the human-machine server. Based on the parsing result, it determines whether the service scheduling method is request message distribution or request service invocation. Based on the determination result, it generates a corresponding request message and submits it to the human-machine request application service module of the human-machine server. The human-machine request application service module determines whether it is a data query function, screen data setting, or command line invocation function based on the corresponding request message. Based on the determination of the function, it generates a response result and returns it to the human-machine request scheduling service module. Finally, the human-machine request scheduling service module returns it to the human-machine cloud terminal for display.

[0073] Furthermore, the determining module includes:

[0074] The broadcast communication module is used to determine the request message distribution method, which is to broadcast the application data request through the message bus. The broadcast message transmission data method is the protobuf protocol. The screen setting or command line call function adopts the request message distribution method. After the human-machine request application service module listens for the broadcast data request, it performs response processing and returns the processing result.

[0075] The bus communication module is used to determine the service call method based on the data type of the application data request and to make a targeted service call through the service bus. The data interaction method between services is the protobuf protocol. The horizontal table query, sensitivity query and tree structure data query functions adopt the aforementioned service call method. After receiving the data request transmitted through the service bus, the human-machine request application service module performs response processing and returns the processing result.

[0076] Furthermore, the determining module includes a data type determining module, used to determine the data type of the application data request as follows:

[0077] A horizontal table query indicates a request type for retrieving load, renewable energy forecasts, power generation plans, unit regulation ranges, and tie-line plans within a certain time range.

[0078] The "screen setting" option indicates the request type for modifying data on the human-machine interface of the human-machine cloud terminal and saving it to the database.

[0079] Command line call indicates the type of request from the human-machine interface of the human-machine cloud terminal to call terminal commands in the background;

[0080] Sensitivity query indicates the type of request for sensitivity data of cross-sections, lines, transformers, and generator sets.

[0081] Tree structure query indicates the type of request that queries tree graph structure data.

[0082] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0083] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0084] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0085] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0086] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A human-computer interaction method adapted to planned market application scenarios, characterized in that, include: Input editing information through the human-machine cloud terminal, and configure data requests based on the editing information; The human-machine interface server determines whether the data request is a general data request or an application data request. If it is a general data request, the unified query service module of the human-machine server platform will respond directly and transmit the response data to the human-machine cloud terminal for display. If it is an application data request, it is parsed by the human-machine request scheduling service module of the human-machine server. Based on the parsing result, it determines whether the service scheduling method is the request message distribution method or the request service call method. Based on the determination result, it generates a corresponding request message and submits it to the human-machine request application service module of the human-machine server. The human-machine request application service module determines whether it is a data query function, a screen data setting function, or a command line call function based on the corresponding request message. Based on the determination of the function, it generates a response result and returns it to the human-machine request scheduling service module. Then, the human-machine request scheduling service module returns it to the human-machine cloud terminal for display. The request message distribution method is to broadcast application data requests through a message bus. The broadcast message transmission data method is the protobuf protocol. The screen setting or command line call function adopts the request message distribution method. After the human-machine request application service module listens for the broadcast data request, it responds and returns the processing result. The requested service invocation method involves making targeted service invocations through the service bus based on the data type of the application data request. The data interaction method between services is the protobuf protocol. The functions of horizontal table query, sensitivity query, and tree structure data query adopt the requested service invocation method. After receiving the data request transmitted through the service bus, the human-machine request application service module performs response processing and returns the processing result.

2. The human-computer interaction method for adapting to planned market application scenarios according to claim 1, characterized in that, The data types of the application data requests include: A horizontal table query is a request type for retrieving load, renewable energy forecasts, power generation plans, unit regulation ranges, and tie-line plans within a certain time range. Screen data setting refers to the request type for modifying data on the human-machine interface of the human-machine cloud terminal and saving it to the database; Command line invocation refers to the request type used by the human-machine interface of a human-machine cloud terminal to invoke terminal commands in the background. Sensitivity query is a request type for querying sensitivity data of cross-sections, lines, transformers, and generator sets. Tree structure query is a request type for querying tree graph structure data.

3. A human-computer interaction system adapted to planned market application scenarios, characterized in that, include: The input module is used to input editing information through the human-machine cloud terminal and configure data requests based on the editing information; The determination module is used to determine whether a data request is a general data request or an application data request through the human-machine interface server. If it is a general data request, the unified query service module of the human-machine server platform will respond directly and transmit the response data to the human-machine cloud terminal for display. If it is an application data request, it is parsed by the human-machine request scheduling service module of the human-machine server. Based on the parsing result, it determines whether the service scheduling method is the request message distribution method or the request service call method. Based on the determination result, it generates a corresponding request message and submits it to the human-machine request application service module of the human-machine server. The human-machine request application service module determines whether it is a data query function, a screen data setting function, or a command line call function based on the corresponding request message. Based on the determination of the function, it generates a response result and returns it to the human-machine request scheduling service module. Then, the human-machine request scheduling service module returns it to the human-machine cloud terminal for display. The determining module includes: The broadcast communication module is used to determine the request message distribution method, which is to broadcast the application data request through the message bus. The broadcast message transmission data method is the protobuf protocol. The screen setting or command line call function adopts the request message distribution method. After the human-machine request application service module listens for the broadcast data request, it performs response processing and returns the processing result. The bus communication module is used to determine the service call method based on the data type of the application data request and to make a targeted service call through the service bus. The data interaction method between services is the protobuf protocol. The horizontal table query, sensitivity query and tree structure data query functions adopt the aforementioned service call method. After receiving the data request transmitted through the service bus, the human-machine request application service module performs response processing and returns the processing result.

4. The human-computer interaction method for adapting to planned market application scenarios according to claim 3, characterized in that, The determining module includes a data type determining module, used to determine the data type of the application data request as follows: A horizontal table query indicates a request type for retrieving load, renewable energy forecasts, power generation plans, unit regulation ranges, and tie-line plans within a certain time range. The "screen setting" option indicates the request type for modifying data on the human-machine interface of the human-machine cloud terminal and saving it to the database. Command line call indicates the type of request from the human-machine interface of the human-machine cloud terminal to call terminal commands in the background; Sensitivity query indicates the type of request for sensitivity data of cross-sections, lines, transformers, and generator sets. Tree structure query indicates the type of request that queries tree graph structure data.

Images