Application supporting system

Abstract

The embodiment of the invention relates to an application support system, and the system comprises an application layer which receives a request from a front end or a user in a multi-user environment, and determines an application layer behavior corresponding to the user after big data processing; the system public service module provides at least one public component and service and comprises authority management, log auditing, a data access layer, task scheduling and a message queue; the authority management comprises the steps of defining different roles, allocating a specific authority to each role, verifying the identity of a user, determining that the user can access resources or execute operations according to the identity of the user, and recording the change history of the user authority; the log auditing comprises recording an operation log of an application program, recording error and abnormal information generated when the system runs, and recording a performance index of the system; and the bus service gateway interface is used for interacting with a plurality of systems through multiplexing, and during interaction, a plurality of data streams during data sending or receiving are in parallel on one TCP connection.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to an application support system. Background Art

[0002] With the development of information technology, enterprise-level applications are increasing day by day, and traditional single applications can no longer meet the needs of high concurrency and high availability. Although the existing application support system has solved these problems to a certain extent, it still has deficiencies in flexibility and scalability. Therefore, it is particularly important to have an application support system that can adapt to rapidly changing business needs and is easy to expand. Summary of the invention

[0003] The purpose of the present invention is to provide an application support system to solve the problems existing in the prior art in view of the defects existing in the prior art.

[0004] To achieve the above object, the present invention provides an application support system, comprising:

[0005] The application layer, in a multi-user environment, receives requests from the front end or users, determines the application layer behavior corresponding to the user, and parses and verifies the request; the request includes identity authentication, permission check, and data validity verification; after the request is verified, the underlying service layer or business logic layer is called to execute specific business; after the business logic is executed, response data that meets the expected format and protocol standards is constructed, and the constructed response data includes data format conversion, error handling, and response header settings;

[0006] The system public service module provides at least one public component and service, which includes permission management, log auditing, data access layer, task scheduling, message queue, cache management and security framework; the permission management includes defining different roles and assigning specific permissions to each role, verifying the identity of the user, determining the user's accessible resources or executable operations based on the user's identity, and recording the change history of user permissions; the log auditing includes recording the operation log of the application, recording the errors and exceptions that occur during system operation, recording the system's performance indicators, including response time and CPU usage, recording security-related information, and providing log analysis tools to diagnose problems and conduct audits; the data access layer is used to provide a unified data access interface and manage the database connection pool; the task scheduling is used to manage scheduled tasks and scheduled tasks; the security framework provides authentication and authorization;

[0007] The bus service gateway interface is used to interact with multiple systems through multiplexing. During the interaction, multiple data streams are sent or received in parallel on one TCP connection.

[0008] In a possible implementation, the application layer is further used to process runtime errors and record error logs; and generate standard error information.

[0009] In a possible implementation, the system further includes: a WEB interaction / presentation layer, which is used to display a user interface and interact with a user.

[0010] In a possible implementation, the application layer includes an enterprise user management platform;

[0011] The enterprise user management platform is used to maintain the enterprise's account information, manage online applications and track enterprise project information, and interact with project management online.

[0012] In a possible implementation, the application layer further: analyzes the source, content and historical behavior of the user request based on the context information of the user request, and determines a service instance to process the request.

[0013] In a possible implementation, the application layer is also used to dynamically adjust the cache strategy according to the request frequency of user requests and the update frequency of data; the cache strategy includes keeping the frequently requested data in the cache and removing the infrequently requested data from the cache.

[0014] In one possible implementation, the system public service module analyzes the historical execution data of the task through a machine learning algorithm, predicts the execution time and resource requirements of the task, and allocates the task to the optimal execution node.

[0015] In a possible implementation, the system public service module is used to perform distributed log aggregation and centrally manage logs of multiple nodes.

[0016] In a possible implementation, the bus service gateway interface is also used to adjust the sending rate according to network feedback traffic and an adaptive flow control algorithm; wherein the adaptive flow control algorithm includes TCP's slow start mechanism and congestion avoidance mechanism.

[0017] In one possible implementation, the bus service gateway interface is also used to define different priority tags for the first type of data and the second type of data, and to sort the data before sending; the priority of the first type of data is higher than the priority of the second type of data; wherein the first type of data is real-time data; and the second type of data is delay-insensitive data.

[0018] By applying the application support system provided by the embodiment of the present invention, it is possible to achieve integration and management of multiple systems and support multiple network interfaces, such as SMS, WeChat, payment, etc. In addition, functions such as permission management and log auditing are also provided to improve the security and maintainability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 A schematic diagram of the application support system structure provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0020] In order to make the purpose, technical scheme and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0021] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments.

[0022] Figure 1 The application support system structure diagram provided by the embodiment of the present invention is shown below. Figure 1 The technical solution of the present invention is described with a specific embodiment. The application support system includes an application layer 1, a system public service module 2 and a bus service gateway interface 3.

[0023] Application layer 1, in a multi-user environment, receives requests from the front end or user, determines the application layer behavior corresponding to the user, and parses and verifies the request; the request includes identity authentication, permission check, and data validity verification; after the request is verified, calls the underlying service layer or business logic layer to execute specific business; after the business logic is executed, constructs response data that meets the expected format and protocol standards, and the constructed response data includes data format conversion, error handling, and response header settings;

[0024] Specifically, the application layer 1 receives requests from the front end or users, and parses and verifies the requests. Request processing includes pre-processing steps such as identity authentication, permission checking, and data validity verification. After the request is verified, the application layer calls the underlying service layer or business logic layer to perform specific business operations. Among them, business operations include calling database operations, external service APIs, or other third-party services.

[0025] After the business logic is executed, the application layer constructs the response data. This process includes data format conversion, error handling, and setting of response headers. The response construction ensures that the final response sent to the user conforms to the expected format and protocol standards.

[0026] The application layer is also used to manage transaction boundaries to ensure that a series of operations either all succeed or all fail. Transaction management is critical to ensuring data consistency and integrity.

[0027] Application layer 1 is also used to handle runtime errors and record detailed logs for debugging and auditing. Error handling should be able to provide friendly error messages to users while protecting sensitive information of the system from being leaked.

[0028] Application layer 1 is also used for encryption, such as encrypted communications, prevention of SQL injection, XSS attacks, etc. Security also includes preventing unauthorized access and protecting user data privacy.

[0029] Application layer 1 can also include a caching mechanism to reduce the backend load and improve response speed. The use of asynchronous processing methods, such as message queues, can improve concurrent processing capabilities.

[0030] Application layer 1 is also used to provide RESTful APIs or other types of APIs for external systems to call, so that users can more easily integrate and use these APIs.

[0031] Furthermore, the application layer 1 of the present application has personalized configuration options in a multi-user environment, such as data access strategy, log level, performance monitoring threshold, etc. After receiving the configuration selection message from the user terminal, multiple configuration options are displayed so that each user can customize the behavior of the application layer according to their own needs. Therefore, this personalized configuration improves the flexibility and adaptability of the system.

[0032] Furthermore, the application layer 1 is also used to analyze the source, content and historical behavior of the user request based on the context information of the user request, and determine the service instance to process the request.

[0033] Specifically, based on the context information of the user request, the application layer dynamically selects the optimal service instance by analyzing the source, content and historical behavior of the user request in the context information, thereby improving the efficiency and response speed of request processing.

[0034] Furthermore, the application layer 1 is also used to dynamically adjust the cache strategy according to the request frequency of user requests and the update frequency of data; the cache strategy includes keeping the data with high frequency requests in the cache and removing the data with low frequency requests from the cache.

[0035] Specifically, the application layer 1 dynamically adjusts the cache strategy according to the request frequency and the data update frequency to optimize performance. The dynamic adjustment of the cache strategy includes but is not limited to automatically adjusting the cache expiration time and storage method to ensure that the data with high frequency requests is always in the cache, and the data with low frequency requests is removed from the cache in time.

[0036] Furthermore, the application layer 1 is used to perform fault tolerance through a multi-level error handling mechanism.

[0037] Specifically, the application layer 1 provides a multi-level error handling mechanism to ensure that errors are captured and handled at different levels, thereby improving the robustness of the system. Error handling mechanisms are set up at the application layer, service layer, and data layer to ensure that errors occurring at any level can be captured and handled in a timely manner.

[0038] Furthermore, in terms of hardware structure, the application layer includes an enterprise user management platform;

[0039] The enterprise user management platform is used to maintain the enterprise's account information, manage online applications and track enterprise project information, and interact with project management online.

[0040] Specifically, the enterprise user management platform can identify and classify abnormal status of enterprise accounts based on Bayesian networks and support vector machine models. Specifically, relevant data can be collected, including login logs, and then data cleaning can be performed to remove invalid data, fill missing values, standardize data formats, etc. to ensure data quality and consistency, and then useful features such as login time and geographic location can be extracted for subsequent model training. When training the model, determine the structure of the Bayesian network, that is, the dependencies between nodes (features). You can use score and search algorithms (such as K2 algorithm) or constrained basic algorithms (such as PC algorithm). When learning parameters: estimate the parameters in each conditional probability table. You can use maximum likelihood estimation or Bayesian estimation methods. When training with support vector machines, select appropriate kernel functions (such as linear kernels, polynomial kernels, RBF kernels) to handle nonlinear relationships. Parameter tuning: Use methods such as cross-validation to adjust hyperparameters (such as C and γ) to optimize the generalization ability of the model. Then, the model is integrated to integrate the results of the Bayesian network and support vector machine models. Voting, weighted average or other integration methods can be used to improve the accuracy and robustness of the prediction. Then, the performance of the model is evaluated using indicators such as accuracy, recall, F1 score, ROC curve, etc. Based on the evaluation results, the model parameters and feature selection are continuously adjusted to optimize the model performance. Finally, the trained model is deployed to the production environment to monitor the status of the enterprise account in real time. When the model detects an abnormal state, the early warning mechanism is immediately triggered to notify relevant personnel for further investigation and processing.

[0041] The system public service module 2 provides at least one public component and service, which includes permission management, log auditing, data access layer, task scheduling, message queue, cache management and security framework; the permission management includes defining different roles and assigning specific permissions to each role, verifying the identity of the user, determining the user's accessible resources or executable operations based on the user's identity, and recording the change history of user permissions; the log auditing includes recording the application's operation log, recording errors and exception information occurring during system operation, recording system performance indicators such as response time and CPU usage, recording security-related information, and providing log analysis tools to diagnose problems and conduct audits; the data access layer is used to provide a unified data access interface and manage database connection pools; the task scheduling is used to manage scheduled tasks and scheduled tasks; the security framework provides authentication and authorization.

[0042] Specifically, the system public service module 2 is an important part of the application support system, which provides a variety of common components and services to support the efficient operation of different applications. These components and services can be reused across multiple applications, thereby reducing the workload of repeated development and improving the overall stability and security of the system.

[0043] The following is a detailed expansion description of the system public service module 2:

[0044] The system public service module is used to verify the identity of users and ensure that only legitimate users can access system resources. It is also used to determine which resources users can access or which operations they can perform based on their roles and permissions. Different roles are defined and specific permissions are assigned to each role. Users manage user sessions to ensure session security and persistence. The change history of user permissions is recorded to facilitate auditing and tracking.

[0045] Among them, log audit includes recording the operation log of the application, including user operations, system operations, etc. Recording errors and exception information that occur when the system is running. Recording system performance indicators, such as response time, CPU usage, etc. Recording security-related information, such as login attempts, permission changes, etc. Providing log analysis tools to help diagnose problems and conduct audits.

[0046] Furthermore, the system public service module 2 is used to provide a unified data access interface, support multiple database types, support object-relational mapping, simplify data access code, manage database transactions, ensure data consistency and integrity, optimize database queries, improve data access performance, manage database connection pools, and improve connection utilization.

[0047] Furthermore, the system public service module 2 is used to perform scheduled tasks, such as data backup, report generation, etc. It supports scheduled tasks, such as cleaning up logs every night at midnight. It supports task execution based on event triggers. It provides a monitoring function for task execution status to ensure the normal operation of tasks.

[0048] Furthermore, the system public service module 2 is used to adjust the user's authority in real time according to business needs, and to dynamically manage the authority of managers according to roles, resources and operation granularity.

[0049] Specifically, the system's public service module 2 adjusts user permissions in real time according to business needs, and supports fine-grained permission control by role, resource, and operation. At the same time, the system also provides a history record and audit function for permission changes to ensure the transparency and traceability of permission management. It provides a dynamic permission management mechanism that supports fine-grained permission control and real-time updates.

[0050] Furthermore, the system public service module 2 uses distributed log aggregation technology to centrally manage logs from multiple nodes and provides powerful log analysis tools. It supports real-time log stream processing, log search and log statistics functions to help operation and maintenance personnel quickly discover and solve problems.

[0051] Furthermore, the system public service module 2 optimizes the task execution efficiency based on intelligent task scheduling based on machine learning algorithms. The historical execution data of tasks is analyzed through machine learning algorithms to predict the execution time and resource requirements of tasks, thereby intelligently allocating tasks to the optimal execution nodes. This intelligent scheduling mechanism significantly improves the execution efficiency of tasks and the resource utilization of the system.

[0052] Specifically, the system public service module 2 first collects the historical execution records of the task, including but not limited to the task type, input parameters, start time, end time, execution node information, resource consumption (such as CPU, memory, I / O), task results, etc. Invalid or erroneous data records are removed, missing values ​​are filled, and the data format is standardized. Useful features are extracted, such as the type and scale of the task, the performance indicators of the execution node, etc., for subsequent modeling.

[0053] Next, perform feature selection and model training. When selecting features, use correlation analysis, mutual information and other methods to select features that have a greater impact on task execution time and resource requirements. When selecting models, choose appropriate machine learning algorithms, such as linear regression, decision tree, random forest, support vector machine (SVM), neural network, etc. When training models, use historical data to train the model, evaluate the performance of the model through methods such as cross-validation, and adjust hyperparameters to optimize the model effect.

[0054] Next, we predict the execution time and resource requirements. When predicting the time, we use the trained model to predict the execution time of the new task. The input features may include task type, input parameters, task size, etc. When predicting resource requirements, we use the model to predict the resources required for the task, such as CPU usage, memory usage, disk I / O, etc.

[0055] Finally, the intelligent scheduling strategy is implemented. When selecting nodes, the most suitable node for executing the task is selected based on the predicted execution time and resource requirements. Factors to be considered include the current load of the node, the remaining resources, network latency, etc. When ensuring load balancing, ensure that the load of each node remains balanced after the task is assigned to avoid overloading some nodes while other nodes are idle. When making dynamic adjustments, during the task execution process, the node status and task progress are continuously monitored, and tasks are rescheduled when necessary to deal with emergencies.

[0056] Among them, when optimizing the task execution strategy, real-time monitoring and feedback can also be performed. Specifically, it includes: establishing a real-time monitoring system to collect various indicators during the task execution process, such as actual execution time, resource consumption, etc. Feedback the actual execution data to the model, continuously update and optimize the model, and improve the prediction accuracy. Detect abnormal situations during task execution through statistical methods or machine learning models, and take timely measures to solve them. Regularly evaluate the overall performance of the intelligent scheduling mechanism, including task execution efficiency, resource utilization, system throughput, etc. According to the evaluation results, continuously improve the feature selection, model training, scheduling strategy and other links to improve the overall performance of the system.

[0057] In one example, the execution records of all tasks in the past year are extracted from the database. The data is cleaned, missing values ​​are filled, and timestamps are standardized. Task type, input parameters, task scale, and execution node performance are selected as features through correlation analysis. The time prediction model and resource demand prediction model are trained using the random forest algorithm. The optimal execution node is selected based on the prediction results and the task is assigned. The task execution process is monitored and actual data is collected. The actual data is fed back to the model to continuously optimize the prediction accuracy and scheduling strategy.

[0058] Furthermore, the system public service module 2 automatically selects the appropriate cache level according to the access frequency and importance of different data. High-frequency access data is preferentially stored in the memory cache, medium-frequency access data is stored in the distributed cache, and low-frequency access data is stored in the database cache. This multi-layer cache strategy effectively improves the data access speed and reduces the database load. Among them, the multi-layer cache strategy supports the combined use of memory cache, distributed cache and database cache.

[0059] Specifically, we first divide the cache level into memory cache, distributed cache, and database cache. Memory cache: used to store frequently accessed data, usually using memory databases such as Redis and Memcached. Distributed cache: used to store medium-frequency accessed data, and can use distributed cache systems such as Apache Ignite and Hazelcast. Database cache: used to store infrequently accessed data, usually a cache implemented at the database level, such as MySQL's query cache.

[0060] Then, determine the data access frequency and importance analysis. Record the access frequency and importance of each data item. You can use logs to record the time, data ID, access type, and other information of each data access. Regularly count the access frequency and importance of each data item. You can use batch jobs or real-time stream processing frameworks (such as Apache Spark, Flink) for statistics. Define the importance of data according to business rules, such as key business data, user personal information, etc. to determine the importance of data.

[0061] Next, execute the dynamic cache strategy. Dynamically select the appropriate cache level based on the access frequency and importance of the data. For frequently accessed data, store it in the memory cache to ensure the fastest access speed. For medium-frequency access data, store it in the distributed cache to balance access speed and resource consumption. For infrequently accessed data: store it in the database cache to reduce the occupancy of memory and distributed cache.

[0062] Finally, perform cache management. When data changes, update the corresponding cache level in time. Mechanisms such as cache penetration, cache breakdown, and cache avalanche can be used to ensure data consistency and reliability. Set a reasonable cache expiration time to avoid occupying cache resources for a long time. You can use strategies such as LRU (least recently used) or LFU (least frequently used) for cache elimination. Before system startup or peak hours, pre-load frequently accessed data into the memory cache to reduce the performance impact caused by cold start.

[0063] Furthermore, the system public service module 2 can perform multiple authentications, such as username / password, OAuth, OpenIDConnect, etc., and provide a fine-grained permission control mechanism. The system also uses encryption technology and security audit functions to ensure the security and integrity of user data.

[0064] The bus service gateway interface 3 is used to interact with multiple systems through multiplexing, and during the interaction, multiple data streams when sending or receiving data are parallelized on one TCP connection.

[0065] Among them, the bus service gateway interface 3 can be connected to various interfaces, such as SMS, WeChat, payment, environmental authentication, etc.

[0066] Furthermore, the bus service gateway interface 3 replaces the traditional text format (such as JSON) with a binary format. At the same time, a compression algorithm can be introduced to compress the message body to further reduce the amount of transmitted data, reduce the size of the data packet, and reduce the parsing overhead.

[0067] Furthermore, the bus service gateway interface 3 is the basic architecture of a high-performance serialization / deserialization library, including core interfaces and data structures, which serializes any data object into a byte stream and then deserializes the byte stream into the original data object.

[0068] Defines commonly used serialization formats, such as binary format, JSON, Protocol Buffers, etc. Supports the extension of custom data types. Use SIMD instruction sets to optimize performance. Modern processors support SIMD (Single Instruction Multiple Data) instruction sets, which can process multiple data points in a single instruction, thereby greatly improving performance. Common SIMD instruction sets include Intel's SSE, AVX, and ARM's NEON.

[0069] Furthermore, by learning from the multiplexing mechanism of HTTP / 2, multiple data streams are allowed to run in parallel on a TCP connection. This can effectively avoid the "head of line blocking" problem and improve concurrent processing capabilities. Multiple requests or responses can be transmitted simultaneously on a connection, reducing the time cost of establishing and disconnecting connections.

[0070] Specifically, each request or response is treated as an independent data stream. The data stream is divided into smaller units, called frames. Frame header: contains information such as frame type, length, and stream identifier. Frame data: actual data content. Reduce the amount of header information transmitted and improve transmission efficiency. The client and the server establish a TCP connection. Stream identifier: Each data stream has a unique identifier. Priority can be set for the data stream to ensure that critical data is transmitted first. The transmission rate of the data stream is controlled through the window update frame to avoid congestion.

[0071] In one example, the session is initialized first. The client sends an initial frame (such as setting the maximum frame size, the maximum number of concurrent streams, etc.), and the server replies with a confirmation frame. The client and server can send multiple data streams concurrently, and each data stream consists of multiple frames. Handling errors in a single data stream does not affect other data streams. Handling errors in the entire connection may require reestablishing the connection.

[0072] Furthermore, the bus service gateway interface 3 is also used to adjust the sending rate according to the network feedback traffic and the adaptive flow control algorithm; wherein the adaptive flow control algorithm includes the TCP slow start mechanism and congestion avoidance mechanism.

[0073] Among them, the slow start mechanism is: in the initial stage, the sending rate is increased rapidly until network congestion is detected. The congestion avoidance mechanism is: after detecting network congestion, the sending rate is gradually increased to avoid congestion again. The fast retransmission mechanism is: when three repeated ACKs are received, the lost data segment is immediately retransmitted. The fast recovery mechanism is: after fast retransmission, the sending rate is gradually increased to return to the level before congestion. In an example, the parameters are initialized first, the initial congestion window (Congestion Window, CWND): the initial value is set to 1 MSS (Maximum Segment Size). Initialize the slow start threshold (Slow Start Threshold, SSTHRESH): the initial value is set to a larger value, such as 64K. Initialize the receive window (Receiver Window, RWND): the maximum receive window of the receiver.

[0074] For the slow start mechanism, the congestion window is increased by 1 MSS for each ACK received. Check the congestion window: If the congestion window is greater than the slow start threshold, enter the congestion avoidance phase.

[0075] For the congestion avoidance mechanism, increase the congestion window: for each ACK received, increase the congestion window by 1 / CWND MSS. Check the congestion window: if the congestion window reaches the receiving window or the network congestion flag is triggered, reduce the congestion window.

[0076] For the fast retransmit mechanism, when three duplicate ACKs are received, the lost data segments are retransmitted immediately.

[0077] For the fast recovery mechanism, the slow start threshold is set to half of the congestion window, and then the congestion window is set to the slow start threshold and the congestion window continues to increase.

[0078] Then build a prediction model. Regularly collect network status information, such as RTT (Round-Trip Time), packet loss rate, bandwidth, etc. Use machine learning models (such as linear regression, decision tree, neural network, etc.) to predict future network status. According to the prediction results, adjust the sending rate in advance to avoid congestion.

[0079] Furthermore, the bus service gateway interface 3 is also used to define different priority labels for the first type of data and the second type of data, and to sort them before sending; the priority of the first type of data is higher than the priority of the second type of data; wherein the first type of data is real-time data; and the second type of data is delay-insensitive data.

[0080] Specifically, define priority tags, and define different priority tags for different types of data. Use a priority queue (such as a binary heap) to manage the data to be sent. Sort the data according to priority before sending. Determine the order in which the data is sent based on the priority tag.

[0081] In one example, different priority tags are defined for different types of data. For example: High priority: data with strong real-time requirements, such as voice and video streams. Medium priority: important but non-real-time data, such as online chat messages. Low priority: data with low delay sensitivity, such as file downloads. Then, use a priority queue to manage the data to be sent. The priority queue ensures that high-priority data is always processed first. Next, sort the data according to priority before sending. You can use the built-in priority queue data structure, or a custom sorting algorithm. Finally, determine the order in which the data is sent based on the priority tag. Ensure that high-priority data is sent first, and low-priority data is appropriately delayed.

[0082] Furthermore, the bus service gateway interface 3 is also used to perform zero copy through zero copy technology.

[0083] Specifically, in order to reduce the number of memory copies and reduce the system call overhead, the zero-copy feature of the operating system is used to pass data directly from the network buffer to the application without going through additional memory copy steps. For example, the sendfile() function in the Linux system implements this function.

[0084] Furthermore, the bus service gateway interface 3 is also used for forward error correction coding. The data block is encoded at the sending end to add redundant information; after the receiving end receives the data, even if part of the data is lost, the original data can be restored through the redundant information, avoiding unnecessary retransmission requests. The number of retransmissions caused by network packet loss is reduced, and the transmission efficiency is improved.

[0085] Therefore, an efficient data exchange protocol can be constructed for the bus service gateway interface, which can significantly improve the communication performance between different systems while reducing network latency and bandwidth consumption. Such a protocol is particularly suitable for high-concurrency, large-data transmission scenarios, such as cloud computing and the Internet of Things.

[0086] By applying the application support system provided by the embodiment of the present invention, it is possible to achieve integration and management of multiple systems and support multiple network interfaces, such as SMS, WeChat, payment, etc. In addition, functions such as permission management and log auditing are also provided to improve the security and maintainability of the system.

[0087] The professionals should further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to the function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0088] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0089] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. An application support system, characterized in that: The system comprises: The application layer, in a multi-user environment, receives requests from the front end or users, determines the application layer behavior corresponding to the user, and parses and verifies the request; the request includes identity authentication, permission check, and data validity verification; after the request is verified, the underlying service layer or business logic layer is called to execute specific business; after the business logic is executed, response data that meets the expected format and protocol standards is constructed, and the constructed response data includes data format conversion, error handling, and response header settings; The system public service module provides at least one public component and service, which includes permission management, log auditing, data access layer, task scheduling, message queue, cache management and security framework; the permission management includes defining different roles and assigning specific permissions to each role, verifying the identity of the user, determining the user's accessible resources or executable operations based on the user's identity, and recording the change history of user permissions; the log auditing includes recording the operation log of the application, recording the errors and exceptions that occur during system operation, recording the system's performance indicators, including response time and CPU usage, recording security-related information, and providing log analysis tools to diagnose problems and conduct audits; the data access layer is used to provide a unified data access interface and manage the database connection pool; the task scheduling is used to manage scheduled tasks and scheduled tasks; the security framework provides authentication and authorization; The bus service gateway interface is used to interact with multiple systems through multiplexing. During the interaction, multiple data streams are sent or received in parallel on one TCP connection.

2. The system according to claim 1, characterized in that The application layer is also used to process runtime errors and record error logs; and generate standard error information.

3. The system according to claim 1, characterized in that The system also includes: a WEB interaction / presentation layer, which is used to display the user interface and interact with the user.

4. The system according to claim 1, characterized in that The application layer includes an enterprise user management platform, which is used to maintain the enterprise's account information, manage online applications and tracking of enterprise project information, and interact with project management online.

5. The system according to claim 1, characterized in that The application layer also analyzes the source, content and historical behavior of the user request based on the context information of the user request, and determines a service instance to process the request.

6. The system according to claim 1, characterized in that The application layer is also used to dynamically adjust the cache strategy according to the request frequency of user requests and the update frequency of data; the cache strategy includes keeping the data with high frequency requests in the cache and removing the data with low frequency requests from the cache.

7. The system according to claim 1, characterized in that The system public service module analyzes the historical execution data of tasks through machine learning algorithms, predicts the execution time and resource requirements of tasks, and allocates tasks to the optimal execution nodes.

8. The system according to claim 1, characterized in that The system public service module is used to perform distributed log aggregation and centrally manage the logs of multiple nodes.

9. The system according to claim 1, characterized in that The bus service gateway interface is also used to adjust the sending rate according to the network feedback traffic and the adaptive flow control algorithm; wherein the adaptive flow control algorithm includes the TCP slow start mechanism and congestion avoidance mechanism.

10. The system according to claim 1, characterized in that The bus service gateway interface is also used to define different priority tags for the first type of data and the second type of data, and to sort the data before sending; the priority of the first type of data is higher than the priority of the second type of data; wherein the first type of data is real-time data; and the second type of data is delay-insensitive data.

Images