Distributed business query engine system

Abstract

The invention provides a distributed service query engine system, which comprises an information query management subsystem configured to register query requirements; the file routing distribution system is connected with the information query management subsystem and is configured to export a request instruction file with routing information and distribute the request instruction file to a corresponding query scheduling execution system according to a network structure; the query scheduling execution system is connected with the file routing distribution system and is configured to receive the request instruction file, schedule different functional plug-ins to initiate query on corresponding services according to parameters carried by the request instruction file, and encapsulate an execution result into a return file with routing information; and the asynchronous notification system is configured to notify a query initiator to check the query result after the information query management subsystem receives the return file. According to the invention, various service systems can be integrated, real-time sharing and synchronization of information are realized, the production efficiency is improved, the operation cost is reduced, and the information accuracy is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of information management systems, and in particular to a distributed business query engine system. Background Art

[0002] In the current manufacturing industry, each business system is often independent and closed. This decentralized system architecture makes information flow extremely difficult. Especially in the production tracking of finished products (card level), due to the complexity of the production process, cross-regional nature and the interaction of multiple business systems, it becomes extremely difficult to obtain a full picture of the business.

[0003] Difficulty in information flow: The lack of effective data interfaces and communication mechanisms between business systems makes it impossible to share and synchronize key information in the production process in real time. Information transmission relies on manual operations, such as manual inquiries and email exchanges, which is not only inefficient but also prone to errors.

[0004] Low response efficiency and high cost: In order to obtain complete production tracking information, a lot of manpower and material resources are needed to query and integrate between different systems and regions. This manual intervention method not only increases operating costs, but also prolongs the time to obtain information and reduces production efficiency.

[0005] Large information errors: Due to poor information flow and manual intervention, production tracking data is prone to errors and omissions. These errors may accumulate and spread to subsequent production links, leading to product quality problems or deviations from production plans.

[0006] Information security issues: Information is stored in different systems or transmitted through unsafe means such as emails, which makes it vulnerable to security risks such as leakage and tampering. Once sensitive information is illegally obtained or abused, it may cause serious economic losses and reputation damage to the company.

[0007] In summary, the existing finished product (card-level) production tracking system has multiple drawbacks such as difficulty in information flow, low response efficiency, high cost, large information errors and information security issues. Summary of the invention

[0008] To solve the above problems, the present invention proposes an efficient and integrated distributed business query engine system, which can integrate various business systems, realize real-time information sharing and synchronization, improve production efficiency, reduce operating costs, and ensure information accuracy.

[0009] The present invention achieves the above-mentioned purpose through the following technical solutions:

[0010] A distributed business query engine system, comprising:

[0011] An information query management subsystem, configured to register query requirements, where the query requirements at least include query type, query conditions, execution time, and frequency;

[0012] A file routing and distribution system, communicatively connected to the information query management subsystem, configured to export a request instruction file with routing information and distribute the request instruction file to the corresponding query scheduling and execution system according to the network structure;

[0013] A query scheduling and execution system, communicatively connected to the file routing and distribution system, configured to receive the request instruction file, dispatch different function plugins according to the parameters carried in the request instruction file to initiate a query for the corresponding service, and after the query is completed, encapsulate the execution result into a return file with routing information;

[0014] An asynchronous notification system, communicatively connected to the information query management subsystem, configured to notify the query initiator to view the query result after the information query management subsystem receives the return file;

[0015] Wherein, during the process of distributing the query instruction file and receiving the return file, the file routing and distribution system performs encryption protection on the data.

[0016] According to a distributed service query engine system provided by the present invention, the information query management subsystem is further configured to:

[0017] Initiate a query request, generate query requirements according to user input or preset conditions;

[0018] Terminate a query request, abort the query according to user instructions or system rules during the query process or before the query result is returned;

[0019] Approve a query request, perform permission verification and approval process processing on the query request initiated by the user;

[0020] Track a query request, monitor the execution status and progress of the query request in real time or periodically;

[0021] Automatically expire a query request, for a query request with a set validity period, automatically mark it as expired or perform deletion processing after the validity period expires;

[0022] Delete a query request, delete the initiated or completed query request and its related information according to user instructions or system rules;

[0023] Initiate a query request periodically in cron format, automatically initiate query requirements periodically according to a preset cron expression.

[0024] According to a distributed service query engine system provided by the present invention, the file routing and distribution system further performs the following steps:

[0025] Regularly obtain query request instructions from the information query management subsystem, and generate a request instruction file containing routing information according to preset rules;

[0026] Distribute the generated request instruction file to the corresponding query scheduling execution system according to routing requirements to achieve the scheduling and execution of query tasks;

[0027] Regularly obtain a request return file containing routing information from the query scheduling execution system, where the content of the request return file can be encrypted and protected;

[0028] Distribute the obtained request return file back to the information query management subsystem according to routing requirements.

[0029] According to a distributed service query engine system provided by the present invention, the step of regularly obtaining query request instructions from the information query management subsystem and generating a request instruction file containing routing information includes:

[0030] Receive query request instructions from the information query management subsystem regularly according to a predetermined time interval or trigger condition;

[0031] Parse the received query request instructions, and extract necessary query parameters and information;

[0032] According to preset rules and algorithms, combine the extracted query parameters and information to generate a request instruction file containing routing information, where the routing information is used to indicate which query scheduling execution system the query request should be distributed to;

[0033] Store the generated request instruction file in a specified location or directly pass it to the corresponding distribution module for subsequent distribution to the corresponding query scheduling execution system according to routing requirements.

[0034] According to a distributed service query engine system provided by the present invention, the preset rules include the steps of parsing request instruction parameters to generate a request instruction file containing routing information, specifically:

[0035] Deeply parse the query request instructions received from the information query management subsystem, and extract the target area and target node information for query distribution routing, as well as the service type and related access parameters;

[0036] Determine the specific routing path of the query scheduling execution system to which the query request should be distributed according to the extracted target area and target node information;

[0037] Generate a request instruction file that combines the service type and relevant access parameters and includes the routing path, service identifier, and access interface information, where the access interface information includes at least the access information of the database instance or the docking methods of the WinAPI interface and WebAPI interface provided by the application;

[0038] Store or encapsulate the generated request instruction file in a preset format and structure so that the subsequent distribution module can accurately identify and distribute it to the corresponding query scheduling execution system according to the routing requirements.

[0039] According to a distributed service query engine system provided by the present invention, before the file routing and distribution system distributes the request return file back to the information query management subsystem, it is also configured to encrypt and protect the content of the request return file. The specific implementation includes:

[0040] Select the AES encryption algorithm as the standard algorithm for data encryption;

[0041] Generate an AES encryption key, which is managed through a secure storage mechanism;

[0042] Perform AES encryption processing on the content of the request return file, and use the AES encryption algorithm to convert the plaintext data into ciphertext data;

[0043] Encapsulate the encrypted request return file in a predetermined format, including at least adding file header information to identify the encryption method and key ID;

[0044] When the file routing and distribution system distributes the encrypted request return file back to the information query management subsystem, it is transmitted through the SSL / TLS secure communication protocol;

[0045] After receiving the encrypted request return file, the information query management subsystem uses the pre-stored AES decryption key and the corresponding AES decryption algorithm to decrypt the ciphertext data to restore the original query result data for the query initiator to view.

[0046] According to a distributed service query engine system provided by the present invention, when the file routing and distribution system uses the AES encryption algorithm to convert the plaintext data of the request return file into ciphertext data, it includes the following steps:

[0047] Key expansion step: According to the selected AES encryption key length, expand the initial encryption key to generate a series of sub-keys for different encryption rounds;

[0048] Initial vector IV generation step: Generate a random and unique initial vector IV, which is independent of the encryption key and is used to ensure that even the same plaintext data will generate different ciphertexts when encrypted multiple times; the IV is stored or transmitted together with the ciphertext for use during decryption;

[0049] Plaintext data block encryption step: Divide the plaintext data into blocks according to the block size specified by the AES algorithm. If the length of the plaintext data is not an integer multiple of the block size, padding processing is performed; for each plaintext data block, perform multiple rounds of encryption operations using the sub-keys generated by the key expansion step and the initial vector IV; after a predetermined number of rounds of encryption operations, obtain the corresponding ciphertext data block; combine all the encrypted ciphertext data blocks in the encryption order to form the complete ciphertext data; encapsulate the ciphertext data and the initial vector IV in a predetermined format for subsequent transmission and distribution.

[0050] According to a distributed service query engine system provided by the present invention, the query scheduling execution system specifically executes the following steps:

[0051] Timed acquisition step: The query scheduling execution system regularly obtains the requests to be executed and their corresponding request parameters from the request queue in the management database according to the preset time order and priority rules;

[0052] Function plug-in loading step: According to the obtained request parameters, the query scheduling execution system dynamically loads the function plug-ins that match the request parameters; the function plug-ins are executable program modules used to implement the specific functions or operations specified by the requests;

[0053] Interface call step: After loading the function plug-ins, the query scheduling execution system calls the interfaces corresponding to the request parameters and passes the request parameters to the function plug-ins to trigger the execution of the function plug-ins;

[0054] Execution result return step: After the function plug-ins are executed, execution results are generated; the query scheduling execution system receives the execution results returned by the function plug-ins and stores the execution results in the management database.

[0055] According to a distributed service query engine system provided by the present invention, when the query scheduling execution system regularly obtains the requests to be executed and their corresponding request parameters from the request queue in the management database, the following strategy is specifically adopted:

[0056] Priority determination step: The query scheduling execution system determines the priority of each request in the request queue in the management database according to the preset priority rules; the priority rules at least include factors such as the initiation method of the request, the type of the request, and the importance of the request;

[0057] Time sequence consideration step: When the priorities are the same, the query scheduling execution system further determines the execution order according to the time sequence of the requests; that is, for requests with the same priority, the earlier initiated request is preferentially executed.

[0058] Step of obtaining requests to be executed: According to the results of the priority determination step and the time sequence consideration step, the query scheduling execution system selects the request with the highest priority and the earliest time sequence from the request queue as the request to be executed, and obtains the request parameters corresponding to this request.

[0059] According to a distributed service query engine system provided by the present invention, when the query scheduling execution system executes a request, the following steps are specifically executed to implement dynamic loading and execution of function plugins:

[0060] Plugin identification step: Parse the query request parameters to identify the function plugin identifier contained therein and the key information required to call this function plugin.

[0061] Plugin loading step: According to the identified function plugin identifier, dynamically load the function plugin that matches the request parameters; the function plugin at least includes a function plugin filesniffer based on the existence of the target file, function plugins provided by external service webapis such as webapiquery, and a plugin dbquery based on business database queries, etc.

[0062] Interface call preparation step: After loading the function plugin, according to the key information in the request parameters and in combination with the self-configuration of the function plugin, prepare the interface parameters required to call the function plugin.

[0063] Plugin execution step: Through the execution engine, call the corresponding interface of the function plugin, and pass the prepared interface parameters to the function plugin to trigger the execution of the function plugin.

[0064] Response result return step: After the function plugin finishes execution, generate a response result; the query scheduling execution system receives the response result returned by the function plugin, formats and processes the response result according to a preset specification, and then stores the processed response result in the management database or returns it to the request initiator.

[0065] Thus, compared with the prior art, the present invention has the following beneficial effects:

[0066] The present invention registers query requirements through a query management system and exports query instructions to different regions and business systems using a file interaction and distribution system. This mechanism enables the originally scattered and independent business systems to quickly respond to query requests and achieve rapid information integration. The design of a unified query interface enables enterprise customer service or relevant personnel to easily obtain production tracking information across systems and regions, greatly improving the efficiency and accuracy of information query.

[0067] The system architecture of the present invention has good scalability and can easily adapt to the development and changes of enterprise business. When adding new business systems or query requirements, only simple configuration in the query management system is required to seamlessly access the entire information management process. This low-coupling and lightweight information integration method makes the system more flexible and able to quickly respond to market demands and business changes.

[0068] The present invention ensures the transmission security of query instructions and return results through the collaborative work of a file interaction and distribution system and a scheduling and execution system. All data transmissions are encrypted, effectively preventing the risks of information leakage and tampering. At the same time, the system uniformly manages query results, providing a unified and secure information storage and access mechanism, further enhancing the security and reliability of data.

[0069] Compared with the traditional manual query method, the present invention realizes the automation and intelligence of the query process. The scheduling and execution system can automatically complete the scheduling and execution of query tasks, greatly shortening the query time and improving the query efficiency. At the same time, since the system reduces the manual intervention links, it reduces the uncertainty and error rate caused by human factors, making the query results more stable and consistent.

[0070] The present invention can support query requirements of different business types. Whether it is finished product production tracking, inventory query, or logistics information query, etc., it can quickly and accurately obtain through a unified query interface. This diverse business support ability enables the present invention to be widely applied in various business fields of enterprises and provides strong support for the efficient operation of enterprises.

[0071] In summary, through an integrated information management system, the present invention realizes the rapid integration and unified query of information, improves the scalability and flexibility of the system, enhances the security and reliability of data, increases the efficiency and stability of query, and meets diverse business needs.

[0072] The following further elaborates on the present invention in detail in conjunction with the accompanying drawings and specific implementation manners. Description of the Drawings

[0073] Figure 1 It is an application architecture diagram of an embodiment of a distributed business query engine system of the present invention.

[0074] Figure 2 It is a schematic diagram of the principles of the information query management subsystem and the file routing and distribution system in an embodiment of a distributed service query engine system of the present invention.

[0075] Figure 3 It is a schematic diagram of the principles of the query scheduling and execution system in an embodiment of a distributed service query engine system of the present invention.

[0076] Figure 4 It is a schematic diagram of the system deployment of an embodiment of a distributed service query engine system of the present invention Detailed implementation manners

[0077] To make the objectives, technical solutions and advantages of the present invention clearer, the technical solutions in the present invention will be clearly and completely described below with reference to the accompanying drawings in the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art without making creative efforts based on the embodiments in the present invention belong to the scope of protection of the present invention.

[0078] Reference to "embodiment" herein means that a specific feature, structure or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The phrase appears in various places in the specification and does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

[0079] See Figures 1 to 4 , this embodiment provides a distributed service query engine system, including:

[0080] An information query management subsystem configured to register query requirements, where the query requirements include at least a query type, query conditions, execution time, and frequency.

[0081] A file routing and distribution system communicatively connected to the information query management subsystem, configured to export a request instruction file with routing information and distribute the request instruction file to the corresponding query scheduling and execution system according to the network structure.

[0082] A query scheduling and execution system communicatively connected to the file routing and distribution system, configured to receive the request instruction file, schedule different function plugins to initiate a query for the corresponding service according to the parameters carried in the request instruction file, and encapsulate the execution result into a return file with routing information after the query is completed.

[0083] An asynchronous notification system, communicatively connected to the information query management subsystem, is configured to notify the query initiator to view the query result after the information query management subsystem receives the returned file.

[0084] Among them, during the process of distributing the query instruction file and receiving the returned file, the file routing and distribution system encrypts and protects the data.

[0085] Among them, the functions of the information query management subsystem include: the salesman submits query requirements (query type, conditions, time, frequency, etc.); the salesman views the query results (finally, the query results under all routes will be aggregated); the salesman manages the query requests and results.

[0086] In this embodiment, the information query management subsystem is further configured to:

[0087] Initiate a query request, generate a query requirement according to user input or preset conditions;

[0088] Terminate the query request, abort the query according to user instructions or system rules during the query process or before the query result is returned;

[0089] Approve the query request, perform permission verification and approval process processing on the query request initiated by the user;

[0090] Track the query request, monitor the execution status and progress of the query request in real time or regularly;

[0091] Automatically expire the query request, for the query request set with a validity period, automatically mark it as expired or delete it after the validity period expires;

[0092] Delete the query request, delete the initiated or completed query request and its related information according to user instructions or system rules;

[0093] Initiate a query request periodically in cron format, and automatically initiate a query requirement periodically according to the preset cron expression.

[0094] In this embodiment, the file routing and distribution system also performs the following steps:

[0095] Regularly obtain the query request instruction from the information query management subsystem, and generate a request instruction file containing routing information according to preset rules; among them, according to the template selected when submitting the query and the response parameter instance, generate a file with a routing in the file name. For example, MCSX2EPIS_1_RQ_4000_9_88B25AB6D66147EBA3DB369F321CA0BB_1(1)_20230314144923575.JSON.

[0096] Distribute the generated request instruction file to the corresponding query scheduling execution system according to the routing requirements to achieve the scheduling and execution of query tasks;

[0097] Regularly obtain the request return file containing routing information from the query scheduling execution system, where the content of the request return file can be encrypted and protected;

[0098] Distribute the obtained request return file back to the information query management subsystem according to the routing requirements.

[0099] In this embodiment, regularly obtain query request instructions from the information query management subsystem and generate a request instruction file containing routing information according to preset rules, including:

[0100] Receive query request instructions from the information query management subsystem regularly at a predetermined time interval or trigger condition;

[0101] Parse the received query request instructions to extract necessary query parameters and information;

[0102] According to preset rules and algorithms, combine the extracted query parameters and information to generate a request instruction file containing routing information, where the routing information is used to indicate which query scheduling execution system the query request should be distributed to;

[0103] Store the generated request instruction file in a specified location or directly pass it to the corresponding distribution module for subsequent distribution to the corresponding query scheduling execution system according to the routing requirements.

[0104] In this embodiment, the preset rules include the steps of parsing request instruction parameters to generate a request instruction file containing routing information, specifically:

[0105] Deeply parse the query request instructions received from the information query management subsystem to extract the target area and target node information for query distribution routing, as well as the service type and related access parameters;

[0106] Determine the specific routing path of the query scheduling execution system to which the query request should be distributed according to the extracted target area and target node information;

[0107] Combine the service type and related access parameters to generate a request instruction file containing the routing path, service identifier, and access interface information, where the access interface information includes at least the access information of the database instance or the docking method of the WinAPI interface and WebAPI interface provided by the application;

[0108] Store or encapsulate the generated request instruction file in a preset format and structure so that the subsequent distribution module can accurately identify and distribute it to the corresponding query scheduling execution system according to the routing requirements.

[0109] In this embodiment, before the file routing and distribution system returns the requested file to the information query and management subsystem, it is also configured to encrypt and protect the content of the requested file. The specific implementation includes:

[0110] Select the AES encryption algorithm as the standard algorithm for data encryption. This algorithm is widely recognized for its high security and wide applicability;

[0111] Generate an AES encryption key, which is managed through a secure storage mechanism to ensure that it cannot be obtained by unauthorized users;

[0112] Perform AES encryption processing on the content of the requested file. Use the AES encryption algorithm to convert the plaintext data into ciphertext data. This process involves steps such as key expansion, generation of the initial vector (IV), and block encryption of the plaintext data;

[0113] Encapsulate the encrypted requested file in a predetermined format, including at least adding file header information to identify the encryption method and key ID, etc.;

[0114] When the file routing and distribution system distributes the encrypted requested file back to the information query and management subsystem, it is transmitted through the SSL / TLS secure communication protocol to ensure the integrity and confidentiality of the data during transmission;

[0115] After receiving the encrypted requested file, the information query and management subsystem uses the pre-stored AES decryption key and the corresponding AES decryption algorithm to decrypt the ciphertext data to restore the original query result data for the query initiator to view.

[0116] In this embodiment, when the file routing and distribution system uses the AES encryption algorithm to convert the plaintext data of the requested file into ciphertext data, it includes the following steps:

[0117] Key expansion step: According to the selected AES encryption key length (such as 128 bits, 192 bits, or 256 bits), expand the initial encryption key to generate a series of sub-keys for different encryption rounds to ensure the complexity and security of the encryption process;

[0118] Initial vector IV generation step: Generate a random and unique initial vector IV. This IV is independent of the encryption key and is used to ensure that even the same plaintext data will produce different ciphertexts during multiple encryptions, enhancing the randomness and security of the encryption; The IV is stored or transmitted together with the ciphertext for use during decryption;

[0119] Steps for encrypting plaintext data in chunks: The plaintext data is divided into chunks according to the block size specified by the AES algorithm (e.g., 128 bits). If the length of the plaintext data is not an integer multiple of the block size, padding processing is performed.

[0120] For each plaintext data block, multiple rounds of encryption operations are performed using the subkeys generated by the key expansion step and the initial vector IV (used for the first encrypted block, and for subsequent blocks, the output of the previous encrypted block may be used as the IV, depending on the working mode of AES, such as CBC mode). Each round of encryption operation includes four basic transformation steps: byte substitution, row shift, column mixing, and round key addition.

[0121] After encryption operations for a predetermined number of rounds, the corresponding ciphertext data blocks are obtained. All the encrypted ciphertext data blocks are combined in the encryption order to form the complete ciphertext data. The ciphertext data and the initial vector IV are encapsulated in a predetermined format for subsequent transmission and distribution.

[0122] Through the above steps, the file routing and distribution system can securely and effectively convert the plaintext data of the requested return file into ciphertext data, ensuring the confidentiality of the data during transmission and storage.

[0123] In this embodiment, the query scheduling execution system specifically performs the following steps:

[0124] Timed acquisition step: The query scheduling execution system periodically obtains, from the request queue in the management database, the requests to be executed and their corresponding request parameters according to the preset time sequence and priority rules.

[0125] Function plug-in loading step: According to the obtained request parameters, the query scheduling execution system dynamically loads the function plug-ins that match the request parameters. The function plug-ins are executable program modules used to implement the specific functions or operations specified by the requests.

[0126] Interface call step: After loading the function plug-ins, the query scheduling execution system calls the interfaces corresponding to the request parameters and passes the request parameters to the function plug-ins to trigger the execution of the function plug-ins.

[0127] Execution result return step: After the function plug-ins are executed, execution results are generated. The query scheduling execution system receives the execution results returned by the function plug-ins and stores the execution results in the management database.

[0128] Through the above steps, the query scheduling execution system can efficiently manage and schedule the requests to be executed, dynamically load and execute the corresponding function plug-ins according to the request parameters, and timely feedback the execution results to the management database, thereby improving the flexibility and scalability of the system.

[0129] In this embodiment, when the query scheduling execution system periodically obtains the requests to be executed and their corresponding request parameters from the request queue in the management database, the following strategies are specifically adopted:

[0130] Priority determination step: The query scheduling execution system determines the priority of each request in the request queue in the management database according to the preset priority rules; the priority rules at least include factors such as the initiation method of the request (such as manual initiation by the customer service or system timing initiation), the type of the request, and the importance level of the request;

[0131] Time sequence consideration step: In the case of the same priority, the query scheduling execution system further determines the execution order according to the time sequence of the requests; that is, for requests with the same priority, the requests initiated earlier are executed first;

[0132] Step of obtaining the requests to be executed: According to the results of the priority determination step and the time sequence consideration step, the query scheduling execution system selects the request with the highest priority and the earliest time sequence from the request queue as the request to be executed, and obtains the request parameters corresponding to the request.

[0133] Through the above strategies, the query scheduling execution system can flexibly obtain the requests to be executed according to the priority and time sequence of the requests, ensure that high-priority requests can be processed in a timely manner, and at the same time maintain the orderliness and efficiency of system processing.

[0134] In this embodiment, when the query scheduling execution system executes a request, the following steps are specifically executed to implement the dynamic loading and execution of function plugins:

[0135] Plugin identification step: Analyze the query request parameters to identify the function plugin identifier and the key information required to call the function plugin contained therein;

[0136] Plugin loading step: Dynamically load the function plugin that matches the request parameters according to the identified function plugin identifier; the function plugins at least include the function plugin filesniffer based on the existence of the target file, the function plugins provided by the external business webapi such as webapiquery, and the plugin dbquery based on the business database query, etc.;

[0137] Interface call preparation step: After loading the function plugin, according to the key information in the request parameters and in combination with the self-configuration of the function plugin, prepare the interface parameters required to call the function plugin;

[0138] Plugin execution step: Through the execution engine, call the corresponding interface of the function plugin, and pass the prepared interface parameters to the function plugin to trigger the execution of the function plugin;

[0139] Response result return steps: After the function plugin finishes execution, a response result is generated; the query scheduling execution system receives the response result returned by the function plugin, formats and processes the response result according to preset specifications, and then stores the processed response result in the management database or returns it to the request initiator.

[0140] Through the above steps, the query scheduling execution system can flexibly load and execute corresponding function plugins according to query request parameters, implement diversified query processing functions, and return response results according to specifications, improving the scalability and processing efficiency of the system.

[0141] In summary, this embodiment provides a system for implementing distributed service asynchronous query based on files. The system includes a query management system, a file interaction and distribution system, an asynchronous notification system, a scheduling execution system, etc. The system registers query requirements through the query management system, exports query instructions for different regions and services through the file interaction and distribution system, and after reaching the service end through different routes or networks, the scheduling execution system completes scheduling and executes specific service queries and returns them. Then, it returns to the query management system through the file interaction and distribution system in the original way, and finally the asynchronous notification system notifies the initiator to view the results. It can provide low-coupling and lightweight information integration between enterprise customer service or relevant personnel and different internal business systems.

[0142] Specifically, by using a unified platform entry, the salesman submits key information for business queries (query type, conditions, execution time, frequency, etc.). After the system records it, it decomposes and generates a query request instruction file with a route, and according to the network structure, it reaches the system execution end. The execution end schedules different plugins to initiate queries for corresponding services according to the parameters carried in the request instruction file, and returns the execution results in the original way, and finally the system notifies the initiating salesman. The system has strong horizontal expansion ability and can meet the information query integration at different business development stages. The system encrypts and protects data during the query information exchange process.

[0143] Furthermore, in this embodiment, the query requirements are registered through the query management system, and the query instructions are exported to different regions and business systems by using the file interaction and distribution system. This mechanism enables the originally scattered and independent business systems to quickly respond to query requests and achieve rapid information integration. The design of a unified query interface enables enterprise customer service or relevant personnel to easily obtain production tracking information across systems and regions, greatly improving the efficiency and accuracy of information query.

[0144] Furthermore, the system architecture of this embodiment has good scalability and can easily adapt to the development and changes of enterprise business. When adding a new business system or query requirement, simply make a simple configuration in the query management system to seamlessly access the entire information management process. This low-coupling and lightweight information integration method makes the system more flexible and able to quickly respond to market demands and business changes.

[0145] Furthermore, through the collaborative work of the file interaction and distribution system and the scheduling and execution system in this embodiment, the transmission security of query instructions and return results is ensured. All data transmissions are encrypted, effectively preventing the risks of information leakage and tampering. At the same time, the system uniformly manages the query results and provides a unified and secure information storage and access mechanism, further enhancing the security and reliability of the data.

[0146] Furthermore, compared with the traditional manual query method, this embodiment realizes the automation and intelligence of the query process. The scheduling and execution system can automatically complete the scheduling and execution of query tasks, greatly shortening the query time and improving the query efficiency. At the same time, since the system reduces the manual intervention links and reduces the uncertainty and error rate caused by human factors, the query results are more stable and consistent.

[0147] Furthermore, this embodiment can support the query requirements of different business types. Whether it is finished product production tracking, inventory query, or logistics information query, etc., it can quickly and accurately obtain through a unified query interface. This diverse business support ability enables this embodiment to be widely applied to various business fields of the enterprise and provides strong support for the efficient operation of the enterprise.

[0148] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combinations of these technical features do not conflict, they should all be considered as within the scope described in this specification.

[0149] The above embodiments are only the preferred embodiments of the present invention and cannot be used to limit the scope of protection of the present invention. Any non-substantive changes and substitutions made by those skilled in the art based on the present invention belong to the scope of protection required by the present invention.

Claims

1. A distributed business query engine system, characterized in that: include: An information query management subsystem configured to register a query requirement, wherein the query requirement includes at least a query type, a query condition, an execution time and a frequency; A file routing distribution system, which is in communication connection with the information query management subsystem and is configured to export a request instruction file with routing information and distribute the request instruction file to a corresponding query scheduling execution system according to a network structure; A query scheduling execution system is connected to the file routing distribution system in communication, and is configured to receive the request instruction file, schedule different functional plug-ins to initiate queries for corresponding services according to the parameters carried in the request instruction file, and encapsulate the execution results into a return file with routing information after the query is completed; an asynchronous notification system, which is in communication connection with the information query management subsystem and is configured to notify the query initiator to view the query result after the information query management subsystem receives the return file; The file routing distribution system encrypts and protects data during the process of distributing query instruction files and receiving return files.

2. The system according to claim 1, characterized in that: The information query management subsystem is also configured as: Initiate a query request and generate query requirements based on user input or preset conditions; Terminate the query request, during the query process or before the query results are returned, according to user instructions or system rules; Approve query requests, perform permission verification and approval process on query requests initiated by users; Track query requests and monitor the execution status and progress of query requests in real time or periodically; Automatic expiration of query requests: for query requests with a set validity period, they will be automatically marked as expired or deleted after the validity period expires; Delete query requests and delete initiated or completed query requests and related information according to user instructions or system rules; Automatically initiate query requests regularly in cron format, and automatically initiate query requests periodically according to the preset cron expression.

3. The system according to claim 2, characterized in that The file routing distribution system further performs the following steps: Obtain query request instructions from the information query management subsystem at regular intervals, and generate a request instruction file containing routing information according to preset rules; Distribute the generated request instruction file to the corresponding query scheduling execution system according to the routing requirements to realize the scheduling and execution of query tasks; Obtaining a request return file containing routing information from a query scheduling execution system at a regular interval, wherein the content of the request return file may be encrypted and protected; The obtained request return file is distributed back to the information query management subsystem according to the routing requirements.

4. The system according to claim 3, characterized in that The method of obtaining a query request instruction from the information query management subsystem at a fixed time and generating a request instruction file containing routing information according to a preset rule includes: According to a predetermined time interval or trigger condition, regularly receiving a query request instruction from the information query management subsystem; Parse the received query request instruction and extract the necessary query parameters and information; According to preset rules and algorithms, combined with the extracted query parameters and information, a request instruction file containing routing information is generated, wherein the routing information is used to indicate to which query scheduling execution system the query request should be distributed; The generated request instruction file is stored in a specified location or directly passed to the corresponding distribution module so that it can be subsequently distributed to the corresponding query scheduling execution system according to routing requirements.

5. The system according to claim 4, characterized in that The preset rule includes the steps of parsing the request instruction parameters to generate a request instruction file containing routing information, specifically: Perform in-depth analysis on the query request instructions received from the information query management subsystem, extract the target area and target node information of the query distribution route, as well as the business type and related access parameters; Determine the specific routing path of the query scheduling execution system to which the query request should be distributed according to the extracted target area and target node information; In combination with the service type and related access parameters, a request instruction file including the routing path, service identifier and access interface information is generated, wherein the access interface information includes at least the access information of the database instance or the docking mode of the WinAPI interface and WebAPI interface provided by the application; The generated request instruction file is stored or encapsulated according to a preset format and structure so that the subsequent distribution module can accurately identify and distribute it to the corresponding query scheduling execution system according to routing requirements.

6. The system according to claim 5, characterized in that The file routing distribution system is also configured to encrypt and protect the content of the request return file before distributing the request return file back to the information query management subsystem. The specific implementation includes: Select AES encryption algorithm as the standard algorithm for data encryption; Generate AES encryption keys, which are managed through a secure storage mechanism; Perform AES encryption on the content of the file returned by the request, and use the AES encryption algorithm to convert the plaintext data into ciphertext data; Encapsulating the encrypted request return file in a predetermined format, including at least adding file header information to identify the encryption method and key ID; When the file routing distribution system distributes the encrypted request return file back to the information query management subsystem, it is transmitted through the SSL / TLS secure communication protocol; After receiving the encrypted request return file, the information query management subsystem uses the pre-stored AES decryption key and the corresponding AES decryption algorithm to decrypt the ciphertext data to restore the original query result data for the query initiator to view.

7. The system according to claim 6, characterized in that When the file routing distribution system uses the AES encryption algorithm to convert the plaintext data of the requested return file into ciphertext data, the following steps are included: Key expansion step: According to the selected AES encryption key length, the initial encryption key is expanded to generate a series of subkeys for different encryption rounds; Initial vector IV generation step: Generate a random and unique initial vector IV, which is independent of the encryption key and is used to ensure that even if the same plaintext data is encrypted multiple times, different ciphertexts will be generated; the IV is stored or transmitted together with the ciphertext for use in decryption; The steps of block encryption of plaintext data are as follows: the plaintext data is divided into blocks according to the block size specified by the AES algorithm. If the length of the plaintext data is not an integer multiple of the block size, padding is performed; for each plaintext data block, multiple rounds of encryption operations are performed using the subkey and initial vector IV generated in the key expansion step; after a predetermined number of rounds of encryption operations, the corresponding ciphertext data block is obtained; all encrypted ciphertext data blocks are combined in the encryption order to form complete ciphertext data; the ciphertext data and the initial vector IV are encapsulated in a predetermined format to facilitate subsequent transmission and distribution.

8. The system according to claim 1, characterized in that The query scheduling execution system specifically performs the following steps: Timing acquisition step: query the scheduling execution system to periodically obtain the requests to be executed and their corresponding request parameters from the request queue of the management database according to the preset time sequence and priority rules; Function plug-in loading step: query the scheduling execution system to dynamically load a function plug-in that matches the request parameters according to the acquired request parameters; the function plug-in is an executable program module used to implement the specific function or operation specified by the request; Interface calling step: After loading the function plug-in, query the interface corresponding to the scheduling execution system call request parameters, and pass the request parameters to the function plug-in to trigger the execution of the function plug-in; Execution result return step: after the function plug-in is executed, the execution result is generated; The query scheduling execution system receives the execution result returned by the function plug-in and stores the execution result in the management database.

9. The system according to claim 8, characterized in that When the query scheduling execution system obtains the to-be-executed request and its corresponding request parameter from the request queue of the management database at a regular interval, the system specifically includes: Priority determination step: the query scheduling execution system determines the priority of each request in the request queue in the management database according to a preset priority rule; the priority rule at least includes factors such as the initiation method of the request, the type of request, and the importance of the request; Time order consideration step: In the case of the same priority, the query scheduling execution system further determines the execution order according to the time order of the requests; that is, for requests with the same priority, the request initiated first will be executed first; Obtain the request to be executed step: According to the results of the priority determination step and the time sequence consideration step, the query scheduling execution system selects the request with the highest priority and the earliest time sequence from the request queue as the request to be executed, and obtains the request parameters corresponding to the request.

10. The system according to claim 8, characterized in that When executing a request, the query scheduling execution system specifically performs the following steps to dynamically load and execute the functional plug-in: Plug-in identification step: parsing the query request parameters, identifying the function plug-in identifier contained therein and the key information required to call the function plug-in; Plug-in loading step: dynamically load the function plug-in matching the request parameters according to the identified function plug-in identifier; The functional plug-ins at least include a function plug-in filesniffer based on the existence of the target file, a function plug-in such as webapiquery based on the provision of external business webapi, a plug-in dbquery based on business database query, etc.; Interface call preparation step: After loading the function plug-in, prepare the interface parameters required to call the function plug-in based on the key information in the request parameters and the function plug-in's own configuration; Plugin execution step: call the corresponding interface of the functional plug-in through the execution engine, pass the prepared interface parameters to the functional plug-in to trigger the execution of the functional plug-in; Response result return step: after the function plug-in is executed, a response result is generated; The query scheduling execution system receives the response result returned by the functional plug-in, formats and processes the response result according to the preset specification, and then stores the processed response result in the management database or returns it to the request initiator.

Images