Business data processing systems, methods, and cloud servers
By adopting a modular design for the business data processing system, the separation of the user display layer and the business logic layer is achieved, which solves the problems of high development costs and low design reuse rate, supports multi-terminal usage scenarios, and improves the maintainability and flexibility of the system.
Patent Information
- Application Number
- CN202311782574.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-22
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2043-12-22
AI Technical Summary
In existing technologies, enterprise solution design and quotation data processing systems have high development costs, low design reuse rates, and cannot meet the needs of multi-terminal usage scenarios.
A business data processing system is adopted, including a client, a request forwarding module, a business logic processing center, a data center, and a message center. The request forwarding module uniformly receives client requests, the business logic processing center performs logical processing, the data center accesses and processes data, and the message center performs push processing, thereby achieving separation between the user display layer and the business logic layer.
It reduces the workload of front-end development and design, improves the reusability of design solutions, supports multi-terminal usage scenarios, and enhances the maintainability and flexibility of the system through modular development.
Smart Images

Figure CN117793203B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data system technology, and more specifically, to a business data processing system, method, and cloud server. Background Technology
[0002] With the rapid development of technologies such as mobile internet, the Internet of Things, cloud computing, and artificial intelligence, having an efficient solution design and quotation data processing system is of great significance to the development of enterprises.
[0003] Currently, most processing systems related to solution design and quotation data integrate business logic with solution design. Users still use traditional data query statements to access data, and the processing systems are mostly developed across multiple platforms, resulting in low reusability of design solutions. This not only increases development costs and is not conducive to development and design, but also fails to meet the needs of users in multi-platform usage scenarios. Summary of the Invention
[0004] The purpose of this application is to provide a business data processing system, method, and cloud server to address the shortcomings of the prior art, thereby solving the problems of high development costs, low reusability of design schemes, and inability to meet the needs of users in multi-terminal scenarios.
[0005] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows:
[0006] In a first aspect, embodiments of this application provide a business data processing system, including a client, a request forwarding module, a business logic processing center, a data center, and a message center;
[0007] The request forwarding module is used to receive data requests sent by each of the clients and send each data request to the business logic processing center. The data request includes user identity and request parameters.
[0008] The business logic processing center includes a task center module. The task center module is used to initiate a business data access request to the data center, receive initial business data determined by the data center based on the user identity and request parameters in the business data access request, perform business logic processing on the initial business data to obtain target business data, and send the target business data to the message center.
[0009] The message center is used to push the target business data to each of the clients.
[0010] As one possible implementation, the request forwarding module includes a front-end forwarding module and a back-end forwarding module;
[0011] The front-end forwarding module is used to receive data requests sent by each client and forward each data request to the back-end forwarding module;
[0012] The backend forwarding module is used to verify the user's identity and request parameters, determine the access permissions, business domains and business processing logic of each client, and send each data request to the business logic processing center.
[0013] As one possible implementation, the business logic processing center includes a design drawing template configuration module, a solution center module, and a template configuration center;
[0014] The design template configuration module is used to generate multiple design templates according to design scenarios and business requirements;
[0015] The solution center module is used to generate business design solutions based on various design templates;
[0016] The template configuration center is used to adjust the parameter configuration of each design template, and to verify and summarize the business design schemes according to business dependency parameters and business standards.
[0017] As one possible implementation, the business logic processing center also includes a contract center module, which includes multiple online contract templates;
[0018] The contract center module is used to retrieve contract data corresponding to the business design scheme, generate a business contract based on the contract data, target business data, and online contract template, and determine quotation data based on the contract data. The online contract template is any one of the online contract templates that matches the current business design scheme.
[0019] As one possible implementation, the data center stores the full amount of basic business data as well as processed data that has been processed according to business domains, business scenarios, and business processing logic;
[0020] The data center is used to obtain the initial business data from the full business base data and the processed data according to the user identity and request parameters, and send the initial business data to the business logic processing center.
[0021] As one possible implementation, the business logic processing center also includes a monitoring module, which is used to perform risk prediction and monitoring alarms on the target business data, design schemes, business contracts and business processes.
[0022] As one possible implementation, the business logic processing center also includes a management module, which is used to perform role authentication on the user who initiates the business data access request and to manage the permissions of the authenticated user.
[0023] As one possible implementation, the business logic processing center also includes a display module, which is used to display the progress of the solution design, the progress of the business contract, and the business schedule.
[0024] Secondly, embodiments of this application provide a business data processing method, applied to the business data processing system described in any one of the first aspects, the method comprising:
[0025] The request forwarding module receives data requests sent by each client and sends each data request to the business logic processing center. The data request includes user identity and request parameters.
[0026] The task center module of the business logic processing center initiates a business data access request to the data center, receives initial business data determined by the data center based on the user identity and request parameters in the business data access request, performs business logic processing on the initial business data to obtain target business data, and sends the target business data to the message center.
[0027] The target business data is pushed to each client through the message center.
[0028] Thirdly, embodiments of this application provide a cloud server, on which a request forwarding module, a business logic processing center, a data center, and a message center, as described in any of the first aspects of the business data processing system, are deployed.
[0029] Fourthly, embodiments of this application provide a computer storage medium storing a computer program, which, when executed by a processor, performs the steps of the business data processing method as described in any of the second aspects above.
[0030] According to the business data processing system, method, and cloud server provided in this application, the business data processing system includes a client, a request forwarding module, a business logic processing center, a data center, and a message center, and the modules of the business data processing system are better decoupled. Since the data request formats of different client front-ends differ, the request forwarding module can unify the data requests from each client for back-end forwarding and invocation, thus enabling the business data processing system to be applied to multi-terminal usage scenarios. Furthermore, business logic processing is performed by the business logic processing center, data access and processing are handled by the data center, and push processing is performed by the message center, thereby achieving separation between the user display layer and the business logic layer. Based on this, business logic processing by the business logic processing center enables internal enterprise solution design and automatic quotation, which not only reduces the workload of front-end development and design but also facilitates modular development by developers, thereby improving the reusability of business design solutions. Attached Figure Description
[0031] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0032] Figure 1 This paper illustrates a schematic diagram of the architecture of a business data processing system provided in an embodiment of this application.
[0033] Figure 2 This illustration shows an architectural diagram of a business logic processing center provided in an embodiment of this application;
[0034] Figure 3 This illustration shows an abstract design diagram of a system database for acquiring, verifying, and executing basic and related information of a device module in a design scheme provided in an embodiment of this application.
[0035] Figure 4 This illustration shows an abstract design diagram of the system database for acquiring, verifying, and executing basic and related information of the device module in another design scheme provided in an embodiment of this application;
[0036] Figure 5 This paper illustrates a schematic diagram of the architecture of another business data processing system provided in an embodiment of this application.
[0037] Figure 6 A flowchart illustrating a business data processing method provided in an embodiment of this application is shown. Detailed Implementation
[0038] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.
[0039] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0040] To enable those skilled in the art to utilize the content of this application, and in conjunction with the specific application scenario of "enterprise internal solution design and quotation data management system," the following implementation method is provided. For those skilled in the art, the general principles defined herein can be applied to other embodiments and application scenarios without departing from the spirit and scope of this application. Although this application primarily describes a business data processing system, it should be understood that this is merely an exemplary embodiment.
[0041] It should be noted that the term "comprising," will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.
[0042] Currently, most systems related to enterprise internal solution design and quotation data management systems suffer from the following main problems during system development, maintenance, and use: First, data access still relies on traditional SQL statements, which is not conducive to system maintenance and performance improvement. Second, cross-platform development is costly and cannot meet the needs of users using multiple platforms. Third, the import cost of business solution design modules is high, and the complex intertwined dependencies result in low solution reusability.
[0043] To address the problems existing in the prior art, this application provides a business data processing system that can reduce the workload of development and design, improve the reusability of design schemes, and facilitate the modular development and maintenance by developers.
[0044] Figure 1 A schematic diagram of the architecture of a business data processing system provided in an embodiment of this application is shown. (Refer to...) Figure 1 As shown, the business data processing system includes a client 10, a request forwarding module 11, a business logic processing center 12, a data center 13, and a message center 14. The client 10 includes, but is not limited to, browsers, mobile apps, WeChat official accounts, and mini-programs. The client 10 can send data requests to the request forwarding module 11 and can also return target business data pushed by the message center to the user. The request forwarding module 11 receives data requests from multiple clients 10 and forwards them to the business logic processing center 12. The business logic processing center 12 includes a task center module 121, which requests data access from the data center 13 based on the data requests, i.e., initiates a business data access request to the data center 13. Correspondingly, the business logic processing center 12 receives the initial business data determined by the data center 13 based on the user identity and request parameters in the business data access request, performs business logic processing on the initial business data to obtain the target business data, and pushes the target business data to the message center 14. The message center 14 then pushes the target business data to each client 10.
[0045] Based on this, the business data processing system provided in this application embodiment can unify the data requests from various clients through a request forwarding module, enabling the backend to forward and call them, thus allowing the business data processing system to be applied to multi-terminal usage scenarios. Furthermore, business logic processing is performed through a business logic processing center, with data access and processing handled by the data center and push processing by the message center, thereby achieving separation between the user display layer and the business logic layer. On this basis, business logic processing through the business logic processing center enables internal enterprise solution design and automatic quotation, not only reducing the workload of front-end development and design but also facilitating modular development by developers, thereby improving the reusability of business design solutions.
[0046] As one possible implementation method, combined with Figure 1 and Figure 2 As shown, in addition to the task center module 121 mentioned above, the business logic processing center 12 also includes a design template configuration module 122, a solution center module 123, a template configuration center 124, a contract center module 125, a monitoring module 126, a management module 127, and a display module 128.
[0047] For example, the task center module 121 can also perform offline analysis and mining based on existing data such as plans, contracts, construction, and operation and maintenance, and provide real-time feedback of the analysis and mining results to the user and monitoring module 126.
[0048] Based on this, the task center module facilitates the management and tracking of data from various links within the business data processing system, enabling offline analysis and mining, and timely summary feedback to users.
[0049] For example, the design template configuration module 122 described above is used to generate multiple design templates according to design scenarios and business requirements. In other words, the design template configuration module 122 can configure various common design templates through a backend server and display them on a browser page. Specifically, it obtains and displays the upstream and downstream dependencies and parameter information of the design templates through reflection.
[0050] Based on this, the design template configuration module can quickly configure or import reusable design templates, customize configurations according to actual business scenarios to quickly generate business design solutions, and accurately generate quotation data based on current industry and supplier equipment quotation information. Based on the generated quotation data, it can quickly lock in the supplier's inventory and logistics delivery status, complete the visualization and rapid response of the entire call chain, and thus improve design efficiency and accuracy.
[0051] For example, the solution center module 123 is used to generate business design solutions based on various design templates. Specifically, the solution center module 123 can reuse design templates, or it can customize the business according to actual business needs, automatically generate usable design drawings, generate usable solutions based on the design drawings, and present the solution information in real time.
[0052] Based on this, the solution center module enables users to quickly generate solutions based on the reuse of design templates, reducing errors in solution design and generating implementable design solutions to improve production efficiency.
[0053] For example, the template configuration center 124 is used to adjust the parameter configuration of each design template, and to verify and summarize the business design schemes according to business dependency parameters and business standards. Specifically, the template configuration center 124 defines and configures the parameters of the design templates, and verifies the business design schemes according to business standards and business dependency parameters, such as the adaptation verification conditions of upstream and downstream equipment, equipment supplier inventory, quotations and logistics information, and summarizes and generates quotation data corresponding to the business design schemes.
[0054] For example, in combination Figure 3 and Figure 4As shown, the template configuration center 124 contains the following tables: model_define, model_base, model_para, model_data_result, model_rule_data, and model_rule_check. The relationships between the model_rule_data and model_rule_check tables are one-to-many, between the model_base and model_define tables, many-to-one between the model_base and model_para, and many-to-many between the model_base and model_data_result tables.
[0055] For example, the model definition table `model_define` includes multiple parameter configuration information, such as the model primary key `id`, model name `model_name`, model type `model_type`, and model provider `model_supplier`, etc., and the parameter configuration information can be dynamically expanded and maintained. Furthermore, the `model_define` table can also be used to further customize equipment information according to customer needs for internal enterprise users based on basic public equipment information.
[0056] For example, the model base table `model_base` includes the primary key `id`, the model definition primary key `model_define_id`, the model parameter primary key `model_para_id`, and the business domain `biz_type` to which the model belongs. The model parameter table `model_para` includes the parameter definition primary key `para_id`, the parameter name `para_name`, the parameter description `para_desc`, the parameter initialization example `para_demo`, the parameter type `para_type`, and the list of parameter value rules `para_value_rules`. The model data result table `model_data_result` includes the primary key `id`, the project primary key `project_id`, the model base primary key `model_base_id`, the model base result `model_base_result`, the creator `create_user`, and the modifier `update_user`.
[0057] For example, the model rule data table `model_rule_data` includes basic validation rules and validation parameter information. Validation mainly targets internal data validation, external supplier data validation, and adaptation, thereby ensuring that the current validation rules and data information are dynamically and effectively implemented in real time. For instance, the model rule data table `model_rule_data` includes the primary key `id`, rule name `rule_name`, rule key index `rule_key`, data record type `type`, rule execution body `rule_function`, rule type `rule_type`, rule parameter definition `rule_para_define`, return value type `result_type`, return value attribute `result_key`, and return value attribute type `result_key_type`.
[0058] For example, the model rule check table `model_rule_check` contains parameter options, parameter configuration relationships, dependencies, and rule check information within and between design templates, thereby ensuring the rationality and accuracy of the design diagrams and business design solutions. For instance, the `model_rule_check` table includes the primary key `id`, the model primary key `model_id`, the parent model primary key `model_parent_id`, the check expression `expression`, and the check key information `rule_keys`.
[0059] For external data, reflection is performed using the rule execution body `rule_function` and rule parameter definition `rule_para_define` in the aforementioned model rule data table `model_rule_data`. External data is also invoked via an external RPC protocol, and data validation is performed on the external data to derive external supplier model information and processing customization information. Specifically, by defining the interface `IModelItem` and defining the return value `JsonObject` of the implementation interface `IModelItem`, classes `InnerEngineItem` for retrieving internal data and `ItemEngineItem` for retrieving external data are derived.
[0060] Based on this, the template configuration center can enhance the effectiveness of data transmission while ensuring its security, so as to accurately obtain available equipment and suppliers based on business design solutions.
[0061] For example, the contract center module 125 is used to retrieve the contract data corresponding to the business design scheme, generate a business contract based on the contract data and the target online contract template, and determine the quotation data based on the contract data. The target online contract template is any one of multiple online contract templates, which can be easily signed, printed, and used for later retrieval and tracking.
[0062] Based on this, the contract center module allows users to quickly understand the contract content and reuse various contract templates to quickly generate contracts with corresponding design schemes, thereby rapidly generating valid contracts.
[0063] For example, the monitoring module 126 described above is used for risk prediction and monitoring alarms on target business data, design schemes, business contracts, and business processes. Specifically, users can use the monitoring module 126 to obtain new business data, design schemes, quotation data, and contract data in a timely manner, while also obtaining information such as the construction status and equipment status at the project site for real-time operation and maintenance, risk prediction, and monitoring alarms.
[0064] For example, the management module 127 described above is used to perform role authentication on users who initiate business data access requests, and to manage the permissions of users after role authentication. Specifically, the management module 127 includes a user module and a permission management module. The user module is specifically used to complete user role authentication through login and control user access to business data. The permission management module is specifically used to configure permission roles and manage the roles of users who have completed enterprise authentication.
[0065] For example, the display module 128 described above is used to display the progress of solution design, business contract progress, and business progress. Specifically, the display module 128 can display the progress of solution design in the business data processing system, the progress of contracts after the design solution is implemented, the progress and status of project construction, and the follow-up progress of customer work orders on the business large screen.
[0066] Therefore, the display module allows users to understand the project progress in a timely manner and to plan and improve the project.
[0067] As one possible implementation, such as Figure 5 As shown, the request forwarding module 11 specifically includes a front-end forwarding module 111 and a back-end forwarding module 112. Specifically, the front-end forwarding module 111 is used to receive data requests sent by each client 10 and forward each data request to the back-end forwarding module 112. The back-end forwarding module 112 verifies the user identity and request parameters contained in the data request, determines the access permissions, business domains and business processing logic of each client 10, and sends each data request to the business logic processing center 12.
[0068] For example, the aforementioned front-end forwarding module 111 is specifically a Node front-end. The reason why client 10 does not directly send data requests to back-end forwarding module 112, but instead has it forwarded by front-end forwarding module 111, is that the business data processing involves multiple clients, and the data request formats of each client's front end are different. The Node front-end is used to unify the data requests of each client 10 to the Node front-end for back-end calls. Furthermore, due to the different access permissions of different roles and the need for data security management, the Node front-end can also verify the user identity and request parameters in the data request, and then determine the route, business domain, and business processing logic corresponding to each data request based on the request parameters.
[0069] For example, the aforementioned backend forwarding module 112 is specifically a Spring Boot backend. It requests the business logic processing center 12 and sends a data request through the Spring Boot backend. Simultaneously, the Spring Boot backend can provide feedback to the Node frontend based on the context of the data request and the scenario. Here, the context refers to the parameters, processed data, and pending data involved in a complete call chain; the scenario refers to the type of operation performed on the current data request based on the parameters; and the result refers to the data returned by the Spring Boot backend to the Node frontend for rendering after processing.
[0070] In addition, since the data center 13 includes basic full data and processed data after processing according to business domain, business scenario and business processing logic, after receiving the business data access request initiated by the task center module 121, the data center 13 obtains the initial business data from the above-mentioned basic full data and processed data according to the user identity and request parameters in the business data access request.
[0071] It should be noted that the construction of the aforementioned business data processing system and the operation of its various modules rely on middleware, including MySQL database service, HBase distributed open-source database, RocketMQ message queue, and the MVC architecture based on software components. Specifically, in this embodiment of the business data processing system, the user display layer and business logic layer are separated. Data access and processing are unified in the data center. Real-time data access is available in MySQL, while offline data computation is performed in HBase, thus meeting all data usage scenarios. Data mining, analysis, and early warning are performed when machine resources are idle. Message notifications and other scenario outreach are handled by the message center, which is decoupled from the business logic processing center, improving the maintainability of the business data processing system. Furthermore, the reusability and customization capabilities of the solution templates, the upstream and downstream dependencies of the device components within the design solution, and the unified parameters are all located in the business logic processing center, facilitating rapid iteration by the development and design teams. Then, by interacting with multiple platforms through the Node frontend, the workload of front-end programming is reduced and the reusability of backend code is increased, which is conducive to the team's modular development and also enhances the maintainability of the program.
[0072] Based on this, the business data processing system according to the embodiments of this application has clear functions for each module, adopts the technology of front-end and back-end separation, the front-end focuses on rendering, the back-end focuses on business logic processing, and the data is processed through the data center. In the process of solution design, online templates can be copied or customized templates can be customized, and reuse can be achieved through corresponding configurations.
[0073] The following is in conjunction with the above. Figures 1 to 5 The content described in the business data processing system shown herein provides a detailed explanation of the business data processing method provided in the embodiments of this application.
[0074] Figure 6 This illustration shows a flowchart of a business data processing method provided in an embodiment of this application. The method is applied to the aforementioned business data processing system. (Refer to...) Figure 6 As shown, the specific execution process of this method includes:
[0075] S601: Receive data requests sent by each client through the request forwarding module, and send each data request to the business logic processing center. The data request includes user identity and request parameters.
[0076] As one possible implementation, multiple clients 10 send data requests to the front-end forwarding module 111 in the request forwarding module 11, that is, to the Node front-end. Then, the Node front-end forwards the data requests to the back-end forwarding module 112, that is, the Spring Boot back-end. The Spring Boot back-end requests the business logic processing center 12 to forward the data requests of each client 10 to the business logic processing center 12 for business logic processing.
[0077] Before forwarding data requests to the Spring Boot backend, the Node frontend can validate the user identity and request parameters in the data request to determine the access permissions of different clients and the data security management requirements. It also uses the request parameters to determine the business domain and business processing logic, obtains the validation results, and sends these results back to each client. Similarly, when the Spring Boot backend sends a request to the business logic processing center, it determines the operation type corresponding to the current data request based on the parameters and processing data in a complete call chain, and then sends the data used for rendering back to the Node frontend.
[0078] S602. The task center module of the business logic processing center initiates a business data access request to the data center, receives the initial business data determined by the data center based on the user identity and request parameters in the business data access request, performs business logic processing on the initial business data to obtain the target business data, and sends the target business data to the message center.
[0079] As one possible implementation, after receiving a data request from the Spring Boot backend, the business logic processing center 12 initiates a business data access request to the data center 13 through the task center module 121 included in the business logic processing center 12. The data center 13 stores basic full data and processed data. Based on the user identity and request parameters in the business data access request, the initial business data is obtained from the above-mentioned basic full data and processed data. Based on the design template configuration module 122, scheme center module 123, template configuration center 124, contract center module 125, monitoring module 126, management module 127 and display module 128 included in the business logic processing center 12, the initial business data is processed to obtain target business data including business design schemes and quotation data.
[0080] Specifically, after acquiring the initial business data, the business logic processing center 12 verifies the initial business data, mainly including data integrity and permission integrity checks, to ensure the accuracy and accessibility of the initial business data. Since multi-dimensional and multi-layered data may be required depending on the business scenario and verification rules, the initial business data determined based on user identity and request parameters is assembled, including operations such as combination, sorting, filtering, and basic calculations. Furthermore, based on the collaborative work of various modules within the business logic processing center 12, a business design scheme and quotation data are obtained, and a notification is sent to the message center 14, distributing the business design scheme and quotation data to the message center 14.
[0081] S603 pushes target business data to each client through the message center.
[0082] As one possible implementation, message center 14 can send target business data back to each client 10 via asynchronous messages. Using asynchronous messages can decouple the two parties involved in the interaction, and only requires the business logic processing center 12 and message center 14 to pre-agree on the message format.
[0083] Based on this, the business data processing method provided in the embodiments of this application, on the basis of a business data processing system developed based on Node front-end, Spring Boot back-end, database service MySQL, distributed open source database HBase, message queue RocketMQ and software component pattern MVC architecture, unifies data access to the data center, which facilitates data analysis and performance optimization, reduces programming workload and increases code reusability, facilitates modular development by the team, and also enhances the maintainability of the application.
[0084] This application also provides a cloud server, on which the request forwarding module, business logic processing center, data center and message center of the above-mentioned business data processing system are deployed.
[0085] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the business data processing method described above.
[0086] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some communication interfaces; the indirect coupling or communication connection of devices or modules can be electrical, mechanical, or other forms.
[0087] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.
[0088] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.
Claims
1. A business data processing system, characterized in that, It includes a client, a request forwarding module, a business logic processing center, a data center, and a message center; the data center stores the full amount of basic business data as well as processed data based on business domains, business scenarios, and business processing logic; The request forwarding module is used to receive data requests sent by each of the clients and send each data request to the business logic processing center. The data request includes user identity and request parameters. The business logic processing center includes a task center module. The task center module is used to initiate a business data access request to the data center, and receive initial business data determined by the data center from the full business basic data and the processed data based on the user identity and request parameters in the business data access request. The task center module performs business logic processing on the initial business data based on the design template configuration module, scheme center module, template configuration center, contract center module, monitoring module, management module and display module included in the business logic processing center to obtain target business data containing business design schemes and quotation data, and sends the target business data to the message center. The message center is used to push the target business data to each of the clients.
2. The system according to claim 1, characterized in that, The request forwarding module includes a front-end forwarding module and a back-end forwarding module; The front-end forwarding module is used to receive data requests sent by each client and forward each data request to the back-end forwarding module; The backend forwarding module is used to verify the user's identity and request parameters, determine the access permissions, business domains and business processing logic of each client, and send each data request to the business logic processing center.
3. The system according to claim 1, characterized in that, The business logic processing center includes a design drawing template configuration module, a solution center module, and a template configuration center; The design template configuration module is used to generate multiple design templates according to design scenarios and business requirements; The solution center module is used to generate business design solutions based on various design templates; The template configuration center is used to adjust the parameter configuration of each design template, and to verify and summarize the business design schemes according to business dependency parameters and business standards.
4. The system according to claim 1, characterized in that, The business logic processing center also includes a contract center module, which includes multiple online contract templates; The contract center module is used to retrieve the business design scheme to generate the corresponding contract data, and generate an online business contract based on the contract data, target business data and the online contract template corresponding to the scheme, and determine the quotation data according to the business contract data. The online contract template is any one of multiple online contract template libraries that matches the current business design scheme.
5. The system according to claim 1, characterized in that, The business logic processing center also includes a monitoring module, which is used to perform risk prediction and monitoring alarms on the target business data, design schemes, business contracts and business processes.
6. The system according to claim 1, characterized in that, The business logic processing center also includes a management module, which is used to perform role authentication on users who initiate the business data access request and to manage the permissions of users after role authentication.
7. The system according to claim 1, characterized in that, The business logic processing center also includes a display module, which is used to display the progress of the solution design, the progress of the business contract, and the business progress.
8. A business data processing method, characterized in that, The method, applied to the business data processing system according to any one of claims 1-7, comprises: The request forwarding module receives data requests sent by each client and sends each data request to the business logic processing center. The data request includes user identity and request parameters. The task center module of the business logic processing center initiates a business data access request to the data center. The data center stores the full basic business data and the processed data after processing according to the business domain, business scenario and business processing logic. It receives the initial business data determined by the data center from the full basic business data and the processed data based on the user identity and request parameters in the business data access request. Based on the design template configuration module, scheme center module, template configuration center, contract center module, monitoring module, management module and display module included in the business logic processing center, the initial business data is processed to obtain target business data containing business design scheme and quotation data. The target business data is then sent to the message center. The target business data is pushed to each client through the message center.
9. A cloud server, characterized in that, The cloud server is equipped with a request forwarding module, a business logic processing center, a data center, and a message center, as described in any one of claims 1-7, within the business data processing system.
Citation Information
Patent Citations
Internal business data system and processing method of enterprise
CN105701220A
Internet-based water treatment design method, device and equipment and storage medium
CN112162752A
