WO2020000807A1

WO2020000807A1 - Service processing method, service system, call management system and service processing system

Info

Publication number: WO2020000807A1
Application number: PCT/CN2018/111493
Authority: WO
Inventors: 晏湘涛
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-06-28
Filing date: 2018-10-23
Publication date: 2020-01-02
Also published as: CN109246071A

Abstract

The embodiments of the present application relate to the technical field of communications, and provided therein are a service processing method, a service system, a call management system and a service processing system. The service processing method provided in the embodiments of the present application comprises: receiving a service request of a user; determining whether the service request requires scheduling a related system; when determined that the service request requires scheduling a related system, forwarding the service request; when the service request does not require scheduling a related system, carrying out service logic processing according to the service request to obtain a processing result; and feeding the processing result back to the user. The technical solution of the present application may reduce or even prevent a situation in which every thread of a current service system becomes congested or a JVM memory even overflows during a large concurrent request.

Description

Business processing method, business system, call management system and business processing system

This application claims the priority of a Chinese patent application filed on June 28, 2018 with the Chinese Patent Office, application number 201810690525.0, and the invention name as "Business Processing Method, Business System, Call Management System, and Business Processing System", its entire content Incorporated by reference in this application.

Technical field

The present application relates to the field of communication technologies, and in particular, to a service processing method, a service system, a call management system, and a service processing system.

Background technique

In the large-scale enterprise information technology system or Internet large-scale system architecture, based on the requirements of system scalability and stability, it is often necessary to deploy large-scale systems into a distributed multi-system architecture. In a distributed multi-system architecture, based on the requirements of business logic, different application systems need to implement remote interface call communication based on Remote Procedure Call Protocol (RPC). When a user initiates a business request for a function point on a business system and requires the cooperation of one or more associated systems, the business system needs to make an RPC call to the associated system.

However, the aforementioned RPC calls to the associated system are often synchronized in the local JVM (Java Virtual Machine). Therefore, once the service of the associated system fails and cannot return the processing result, the business system can only wait for the timeout. , Will cause the current thread to be suspended, waiting, and the processing result cannot be fed back to the user. The user often re-initiates the request at this time, and the associated system can no longer provide services at this time. It is easy to cause the threads of the current business system to be blocked or even the JVM memory overflow during a large concurrent request, resulting in a functional point of the business system The failure caused the entire business system to be unusable.

Application content

The embodiments of the present application provide a business processing method, a business system, a call management system, and a business processing system, which can reduce or even avoid the situation that the threads of the current business system are completely blocked or even the JVM memory overflows during large concurrent requests.

In a first aspect, an embodiment of the present application provides a service processing method. The service processing method includes: receiving a user's service request; determining whether the service request needs to call an associated system; and when the service request needs to call an associated system, The service request is forwarded; when the service request does not need to call an associated system, business logic processing is performed according to the service request to obtain a processing result; and the processing result is fed back to the user.

In a second aspect, an embodiment of the present application provides a service system. The service system includes: a receiving module configured to receive a user's service request; and a first RPC interface configured to, when the service request needs to call an associated system, The service request is forwarded; a service judgment module is configured to determine whether the service request needs to call an associated system according to the service request; a service processing module is used to determine the service request according to the service when the associated system does not need to call the associated system. Requesting business logic processing to obtain a processing result; a first feedback module, configured to feedback the processing result to the user.

In a third aspect, an embodiment of the present application provides a service processing method. The service processing method includes: receiving a forwarded service request; invoking a corresponding associated system according to the service request; receiving a processing result from the associated system; and sending a request to a user. The processing result is fed back.

According to a fourth aspect, an embodiment of the present application provides a call management system. The call management system includes: a second RPC interface for receiving a forwarded service request and receiving a processing result from an associated system; and a calling module for The above-mentioned service request calls the corresponding associated system; the second feedback module is used to feed back the processing result to the user.

In a fifth aspect, an embodiment of the present application provides a service processing system. The service processing system includes the service system described above, the call management system described in any one of the foregoing, and at least one associated system.

According to a sixth aspect, an embodiment of the present application provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the processor implements the method described in the first aspect. method.

In a seventh aspect, an embodiment of the present application provides a computer non-volatile readable storage medium, where the computer non-volatile readable storage medium includes a stored program, wherein the computer is controlled when the program runs. The device on which the volatile readable storage medium is located executes the method as described in the first aspect above.

According to an eighth aspect, an embodiment of the present application provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the processor implements the method described in the third aspect above. method.

In a ninth aspect, an embodiment of the present application provides a computer non-volatile readable storage medium, where the computer non-volatile readable storage medium includes a stored program, wherein the computer is controlled when the program runs. The device on which the volatile readable storage medium is located executes the method as described in the third aspect above.

The embodiments of the present application provide a business processing method, a business system, a call management system, and a business processing system. When the business processing method is applied to a business system, the business system receives a user's business request, and judges based on the user's business request. Does the business request need to call the associated system? Only when it is not necessary to call the associated system, it will be processed through its own business logic to obtain the processing result and feedback to the customer. When the associated system needs to be called, the business system will forward the user's business request To the call management system, the call management system will return the processing result to the customer. Therefore, during the implementation process, even if the service of the related system fails, the processing result cannot be returned. When the user re-initiates the request, the request will be forwarded by the business system. This can alleviate or even avoid the situation that the threads of the current business system are completely blocked or even the JVM memory overflows during large concurrent requests, so that the failure of one function point of the business system will not affect the other function points of the business system and will not cause The entire business system can use.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to explain the technical solutions in the embodiments of the present application or the prior art more clearly, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without paying creative labor.

FIG. 1 is a first flowchart of a service processing method according to an embodiment of the present application;

2 is a second flowchart of a service processing method according to an embodiment of the present application;

FIG. 3 is a flowchart of a security authentication and verification process according to an embodiment of the present application; FIG.

4 is a third flowchart of a service processing method according to an embodiment of the present application;

FIG. 5 is a first schematic diagram of a service system according to an embodiment of the present application; FIG.

FIG. 6 is a second schematic diagram of a service system according to an embodiment of the present application; FIG.

FIG. 7 is a third schematic diagram of a service system according to an embodiment of the present application;

8 is a first flowchart of another service processing method according to an embodiment of the present application;

9 is a second flowchart of another service processing method according to an embodiment of the present application;

FIG. 10 is a first schematic diagram of a call management system according to an embodiment of the present application; FIG.

11 is a second schematic diagram of a call management system provided by an embodiment of the present application;

FIG. 12 is a schematic diagram of a service processing system according to an embodiment of the present application; FIG.

FIG. 13 is a first schematic diagram of an interaction process between a service system, a call management system, and an associated system according to an embodiment of the present application; FIG.

FIG. 14 is a second schematic diagram of an interaction process of a service system, a call management system, and an associated system according to an embodiment of the present application.

detailed description

In order to make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments It is a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

It should be noted that, in the case of no conflict, various technical features in the embodiments of the present application may be combined with each other.

In a first aspect, an embodiment of the present application provides a service processing method, which is applicable to a service system. In one embodiment, as shown in FIG. 1, FIG. 1 is a service processing method provided by an embodiment of the present application. Flowchart 1 of this method includes:

Step 10: Receive a service request from a user;

Among them, a user's business request may be directed to one or more functional points of the business system. Business requests can be queries, business processing, storage, etc.

Step 11. Determine whether the service request needs to call the associated system. If so, go to step 12. If not, go to step 13 and step 14.

In the first example, the business request does not need to call the associated system, that is, the business system's own business logic can process the business request. In the second example, the business request only needs to call one or more associated systems. That is, the business request only needs to be processed by the business logic of one or more related systems, without the business logic of the business system. In the third example, the business request needs to be processed by the business logic of the business system, and it needs to be called The business logic of one or more associated systems is processed.

Among them, if it is determined that the service request meets the first example according to the user's service request, step 13 is performed, and the business system directly performs business logic processing to obtain the processing result; if the service request is determined according to the user's service request, the service request meets the second example. In the case of this example or the third example, step 12 is performed, and the service system forwards the user's service request.

Step 12. Forward the service request.

When it is determined that the service request needs to call the associated system, the service system forwards the user's service request, for example, to the call management system, so that the call management system processes the service request, obtains the processing result, and The processing result is fed back to the user.

Step 13: Perform business logic processing according to the service request to obtain a processing result.

When it is determined that the service request does not need to call the associated system, the service system directly performs service logic processing on the service request to obtain a processing result. When a business request corresponds to one business logic, only one business logic process is required. When a business request corresponds to multiple business logics, multiple business logic processes are required. For example, business request 1 only corresponds to business logic A1, and only business logic A1 needs to be processed; business request 2 corresponds to three business logics, business logic A2, business logic A3, and business logic A4, and business logic A2 needs to be processed separately , Business logic A3 processing and business logic A4 processing, the specific order of the three corresponds to the specific business request.

Step 14. Feedback the processing result to the user.

The business system performs business logic processing, and after obtaining the processing result, feeds back the processing result to the user.

The above business processing method has the following beneficial effects:

When the business processing method is applied to a business system, the business system receives the user's business request, and determines whether the business request needs to call the associated system based on the user's business request. Only when it does not need to call the associated system, it does so through its own business logic. Process, obtain the processing result and feedback to the customer, and when the associated system needs to be called, the business system forwards the user's business request to the call management system, and the call management system feeds back the processing result to the customer. Therefore, during the implementation process, Even if the service of the related system fails, the processing result cannot be returned. When the user re-initiates the request, the request will be forwarded by the business system, which can alleviate or even prevent the threads of the current business system from being blocked or even the JVM memory overflow during large concurrent requests The situation occurs so that the failure of one function point of the business system will not affect the other function points of the business system, and will not cause the entire business system to be unusable.

In another embodiment, as shown in FIG. 2, FIG. 2 is a second flowchart of a service processing method according to an embodiment of the present application. The service processing method includes:

Step 01: Perform security authentication check according to the user information and service request to determine whether the user has corresponding authority. If yes, go to step 10; if not, go to step 02 and step 03.

The user information includes, but is not limited to, one or more of a user's login account, login password, and the like. The above corresponding permissions are the permissions required by the user's business request.

Step 10. Receive a user's service request and user information.

Step 02: Reject the user's service request;

Step 03: Report an error to the user.

Step 12. Forward the service request and user information.

When it is determined that the business request needs to call the associated system, the business system forwards the user's business request and user information, for example, to the call management system, so that the call management system processes the service request, and the call management system also The security authentication check can be performed according to the user information to further confirm whether the user has the corresponding authority. If the management system is invoked to perform the security authentication verification based on the user information and business request, it is determined that the user does not have the appropriate authority, and the management system is refused to receive it. If the service request has the corresponding authority, the management system is called to process the service request, obtain the processing result, and feed the processing result back to the user.

Step 14. Feedback the processing result to the user.

Optionally, in step 01, the security authentication verification according to the user information and the service request may be specifically implemented by JWT (JSON Web Token) technology. As shown in FIG. 3, FIG. 3 is a security authentication verification provided by an embodiment of the present application. The flowchart of the process, the security certification verification process includes the following:

1. When the user logs in (for example, through the client), the account and password are used to authenticate to the business system. After the authentication is passed, the business system generates a token by using the held key. The user does not need to hold the key. The business system passes the secret. The key can be used to generate a Token. The Token generally contains the expiration time and the unique identifier of the user, such as the user ID. The business system returns the Token to the user.

2. The user saves the token returned by the business system.

3. The user makes a business request and carries a Token in the Authorization field of the Head, such as: Authorization: Bearer token.

4. The business system verifies the Token contained in the business request, and looks for the existence of the Token in Redis. The business system verifies the corresponding permissions by the user's unique identity obtained from the Token, and assigns this user's unique identity to the request parameters In the above, the above search is mainly to solve the problem of user cancellation, but the token is still within the time limit. If the token exists in Redis, it means that the user has been cancelled; if the token does not exist, the verification passes.

5. The business system processes the service request through the unique identifier of the user, and returns the processing result to the user.

Among them, when the user logs out, the business system saves the Token that is still within the time limit to Redis, sets the correct expiration time, and prompts the user that the logout is successful.

Optionally, as shown in FIG. 4, FIG. 4 is a third flowchart of a service processing method according to an embodiment of the present application. The service processing method further includes: after receiving a user's service request, and determining whether the service request is required Before calling the associated system, perform the following steps:

Step 101: Divide all business logic, and determine that the business logic of the associated system does not need to be called, and the business logic of the associated system that needs to be called.

For example, business system A contains n business logics, n is a positive integer greater than 1, such as 100, business logics A1 to Ax are business logics that do not need to call the associated system, and business logics Ax + 1 to An are those that need to call the association The business logic of the system, x is a positive integer greater than or equal to 1 and less than or equal to n, such as 90.

Step 102: Number each business logic that does not need to call the associated system.

For example, the business logics A1 to Ax that do not need to call the associated system are numbered RPC (A1) to RPC (Ax). The above numbering method is merely an example and is not limiting.

Step 103: Determine the associated system that needs to be invoked by each business logic of the associated system.

For example, the value of n is 100 and the value of x is 90. After step 103, it is determined that the associated systems to be invoked by business logic A91 to A100 are B, B, C, D, E, C, E, B, and D, E. The above is just an example and is not limited. Of course, different business logic can also call different associated systems.

Step 104: Number the business logic of the associated system that needs to be called according to the specific needs.

For example, after determining in Step 103 that the associated systems that need to be invoked by the business logic A91-A100 are B, B, C, D, E, C, E, B, D, E, respectively, the business logic A91-A100 are numbered as RPC (B1), RPC (B2), RPC (C1), RPC (D1), RPC (E1), RPC (C2), RPC (E2), RPC (B2), RPC (D2), and RPC (E3), The above numbering methods are merely examples and not limiting.

It should be noted that, taking the number RPC (B1) of the business logic A91 as an example, "B" means that the business logic A91 needs to call the associated system B, and "1" means that the business logic is the business system A's The first of all business logics (that is, the highest number) needs to call the business logic of the associated system B. Other similar descriptions are understood in the same manner as above, and will not be repeated one by one here.

It should be noted that a business request corresponds to one or more business logics, but each business logic corresponds to a system (business system or associated system). For example, business request 1 only corresponds to business logic A1, and business request 2 corresponds to 3 business logics, business logic A2, business logic A3, and business logic A4, business request 3 corresponds to 3 business logics, business logic A91, business logic A93, and business logic A94, and business request 4 corresponds to 3 business logics, business Logic A5, business logic A95, and business logic A96.

In the above steps, step 102 may be performed first, and then step 103 and step 104 may be performed, or step 103 and step 104 may be performed first, and then step 102 may be performed.

Correspondingly, step 13 is specifically to call the business logic of the corresponding number according to the service request to obtain the processing result.

In this embodiment, each business logic in the business system is numbered, and this number can be used to formulate an interface invocation strategy for processing business requests, which can more conveniently and quickly process business requests.

In a second aspect, an embodiment of the present application provides a service system. As shown in FIG. 5, FIG. 5 is a first schematic view of a service system provided by an embodiment of the present application. The service system includes a receiving module 51, a first RPC interface 52, The service judgment module 53, the service processing module 54, and the first feedback module 55. The receiving module 51 is used to receive a user's service request; the first RPC interface 52 is used to forward a service request when the service request needs to call the associated system; the service determination module 53 is used to determine whether the service request is required according to the service request Invoke the associated system; the business processing module 54 is configured to perform business logic processing according to the service request to obtain the processing result when the business request does not need to call the associated system; the first feedback module 55 is used to feedback the processing result to the user. The business system is applicable to the business processing method described in the first aspect. The specific contents of the business processing method in the first aspect are applicable to this business system.

Optionally, as shown in FIG. 6, FIG. 6 is a second schematic diagram of a service system provided in an embodiment of the present application. The service system further includes a first authentication module 56, and the first authentication module 56 is configured to receive user information and service requests. Perform security authentication check to determine whether the user has the corresponding authority. The receiving module 51 is specifically configured to receive the user's service request and user information when the user has the corresponding authority, and to refuse to receive the user's service request when the user does not have the corresponding authority; the first RPC interface 52 is specifically used to When the associated system is called, the user's service request and user information are forwarded; the first feedback module 55 is further configured to report an error to the user when the user's service request is rejected.

Optionally, as shown in FIG. 7, FIG. 7 is a third schematic diagram of a service system according to an embodiment of the present application. The service system further includes a service logic division module 57 and a numbering module 58. The service logic division module 57 is used for the service system. The business logic in the system is divided to obtain the business logic that does not need to call the associated system, and the business logic that needs to call the associated system. The numbering module 58 is used to number the business logic that does not need to call the associated system, and determine that the associated system needs to be called. Each business logic needs to call the associated system, and according to the specific needs of the associated system, the business logic that needs to call the associated system is numbered. Correspondingly, the service processing module 54 is specifically configured to call the service logic of the corresponding number according to the service request to obtain a processing result.

In a third aspect, an embodiment of the present application provides a service processing method, which is suitable for invoking a management system. In one embodiment, as shown in FIG. 8, FIG. 8 is another service provided by the embodiment of the present application. Flow chart 1 of the processing method. The service processing method includes:

Step 20: Receive the forwarded service request.

Specifically, when it is determined that the service request needs to call the associated system according to the user's service request, the service system forwards the user's service request, and the management system is called to receive the service request forwarded by the service system.

Step 21: Call the corresponding associated system according to the service request.

Specifically, the call management system is provided with a mapping relationship between a service request, business logic, and an associated system, and the call management system calls a corresponding associated system according to the service request and the above mapping relationship. For example, mapping relationship 1: Business request 3 corresponds to 3 business logics, business logic A91 (RPC (B1)), business logic A93 (RPC (C1)), and business logic A94 (RPC (D1)). The execution order of the three is RPC (B1)-> RPC (C1)-> RPC (D1), then call the management system to call related system B, related system C, and related system D in turn according to the mapping relationship; mapping relationship 2: service request 4 corresponds to 3 services Logic, business logic A5 (RPC (A5)), business logic A95 (RPC (E1)), and business logic A96 (RPC (C2)), the execution order of the three is RPC (A5)-> RPC (E1)-> RPC (C2), the call management system sequentially calls the business system A, the related system E, and the related system C according to the mapping relationship.

Step 22: Receive a processing result from the associated system.

Specifically, the management calling system receives a processing result from the associated system that was called last.

Step 23: feedback the processing result to the user.

The management invocation system feeds back the processing results to the user.

Optionally, as shown in FIG. 9, FIG. 9 is a second flowchart of another service processing method according to an embodiment of the present application. When a service system forwards a service request and user information, the foregoing service processing method further includes receiving a service. Before the request, step 201 is performed to perform security authentication verification based on the service request and user information to determine whether the user has the corresponding authority. When the user has the corresponding authority, perform step 20 to receive the forwarded service request. The user does not have the corresponding authority. When step 202 is executed, the forwarded service request is rejected. For the specific process of performing security authentication and verification based on the service request and user information in the service processing method of the third aspect, refer to related content in the service processing method of the first aspect, which will not be repeated here.

In a fourth aspect, an embodiment of the present application provides a call management system (rpcManager). As shown in FIG. 10, FIG. 10 is a schematic diagram of a call management system provided by an embodiment of the present application. The call management system includes a second RPC interface 1001. A calling module 1002 and a second feedback module 1003; a second RPC interface 1001 is used to receive a forwarded service request and receive a processing result from an associated system; a second feedback module 1003 is used to feedback a processing result to a user; a calling module 1002 is used to The business request calls the corresponding associated system.

Optionally, the calling module 1002 is specifically configured to call the corresponding associated system according to the mapping relationship between the service request, the business logic, and the associated system. The mapping relationship between the service request, the business logic, and the associated system may be stored in the calling module 1002.

Optionally, as shown in FIG. 11, FIG. 11 is a second schematic diagram of a call management system provided by an embodiment of the present application. The call management system further includes a second authentication module 1004 for performing security authentication calibration according to user information and service requests. Check to determine whether the user has the appropriate permissions. If the user has the corresponding authority, the second RPC interface 1001 receives the forwarded service request. If the user does not have the corresponding authority, the second RPC interface 1001 rejects the forwarded service request.

The call management system is applicable to the business processing method described in the third aspect, and the specific content of the business processing method in the third aspect is applicable to this call management system. The call management system can be implemented through a Java solution, a Node.Js solution or a Go language solution. In addition, the call management system can also provide complete functions such as authentication, threshold control, monitoring, and logging.

In a fifth aspect, an embodiment of the present application provides a service processing system. As shown in FIG. 12, FIG. 12 is a schematic diagram of a service processing system provided by an embodiment of the present application. The service processing system includes the service system 1201 and the call described above. A management system 1202 and at least one associated system 1203. The specific content of the service system 1201 and the call management system 1202 is described in the foregoing description, and details are not described herein again.

For example, as shown in FIG. 13 and FIG. 14, FIG. 13 is a schematic diagram 1 of interaction processes of a service system, a call management system, and an associated system according to an embodiment of the present application, and FIG. 14 is a service system, call, and the like provided by an embodiment of the present application. Schematic diagram of the interaction process between the management system and the associated system. The process of the business processing system processing the user's business request is as follows:

As shown in FIG. 13, the service system receives the user's service request, and the service system determines whether the service request needs to call the associated system. If it needs to be called, it forwards the user's service request to the call management system, and the call management system receives the service system forwarded Business request, and call the corresponding associated system according to the business request, the associated system performs business logic processing to obtain the processing result, the associated system sends the processing result to the call management system, the call management system receives the processing result from the related system, and feedbacks the processing to the user result.

As shown in FIG. 14, the business system receives the user's business request, and the business system determines whether the business request needs to call the associated system. If it is not required, the business system directly performs business logic processing according to the business request, obtains the processing result, and sends it to the user. Feedback processing results.

In a sixth aspect, the embodiment of the present application provides a specific application example, in which an agent inquires claim information (request for claim information is a business request) in a car insurance remote sale.

In the prior art, claim information is stored in hbase (that is, an associated system), but when a business system queries hbase's claim information, a thread of the business system hangs due to an exception in bhase. After the thread hangs, the query result cannot be obtained on the user interface. The user is eager to refresh the page and trigger a new query request again. The business system receives a new query request, uses a new thread to query hbase, hbase has no feedback, and the new thread hangs again. A large number of users repeatedly trigger new query requests, causing the business system threads to be exhausted, and the entire business system is unavailable, that is, to achieve such a non-core key function of the business system (that is, the function of querying claims information), and because of the association The exception of the system exhausted the threads of the business system, resulting in all functions of the entire business system being unavailable.

In the embodiment of the present application, since the non-core claim information query function needs to call the related system Hbase, when the business system receives a service request for querying the claim information, it forwards the business request to the call management system for processing, that is, to query the claim information. The functions are separated from the business system and handled by the newly established call management system, which not only can not affect the related functions of the business system when the abnormality of the related system Hbase occurs, and reduce the business system caused by the abnormality of the interface provided by the related system. The situation is dragged down, and the call management system is completely independent of the business system. It can use a different technology implementation system than the business system to achieve higher throughput and high concurrency support. It can provide claims query, which depends on the related system, to provide more functions. Stable and cost-effective service.

An embodiment of the present application further provides a computer device. The computer device includes a memory and a processor. The memory is used to store information including program instructions, the processor is used to control the execution of the program instructions, and the program instructions are implemented when the program instructions are loaded and executed by the processor. The business processing method of the first aspect.

An embodiment of the present application further provides a computer non-volatile readable storage medium, which controls a device where the computer non-volatile readable storage medium is located to execute the service processing method of the first aspect when a program is running.

An embodiment of the present application further provides a computer device. The computer device includes a memory and a processor. The memory is used to store information including program instructions, the processor is used to control the execution of the program instructions, and the program instructions are implemented when the program instructions are loaded and executed by the processor. The business processing method of the third aspect.

The embodiment of the present application further provides a computer non-volatile readable storage medium, which controls the device where the computer non-volatile readable storage medium is located to execute the service processing method of the third aspect when the program is running.

Finally, it should be noted that the above embodiments are only used to describe the technical solution of the present application, rather than limiting it. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features can be equivalently replaced; and these modifications or replacements do not deviate the essence of the corresponding technical solutions from the technical solutions of the embodiments of the present application. range.

Claims

A service processing method, comprising:

Receive user service requests;

Determining whether the service request needs to call an associated system;

When the service request needs to call an associated system, forwarding the service request;

When the service request does not need to call an associated system, perform business logic processing according to the service request to obtain a processing result;

Feedback the processing result to the user.
The service processing method according to claim 1, before the receiving a service request from a user, further comprising:

Perform security authentication check according to the user information and the service request, and determine whether the user has corresponding authority;

When determining that the user has corresponding authority, receiving the service request and the user information of the user, and when determining that the service request needs to call an associated system, forwarding the service request and the user information;

When it is determined that the user does not have corresponding authority, the service request of the user is rejected, and an error is reported to the user.
The service processing method according to claim 1 or 2, further comprising the following steps after the receiving a user's service request, before the determining whether the service request needs to call an associated system:

Divide all the business logic in the business system, and determine that the business logic of the associated system does not need to be called, and the business logic of the associated system needs to be called;

Number the business logic that does not need to call the associated system;

Determine the specific associated system that needs to be invoked for each business logic of the associated system;

Number the business logic that needs to call the associated system according to the specific system that needs to be called;

Wherein, performing the business logic processing according to the service request, and obtaining a processing result is: invoking the business logic of a corresponding number according to the service request to obtain the processing result.
A business system, which includes:

A receiving module for receiving a service request of a user;

A first RPC interface, configured to forward the service request when the service request needs to call an associated system;

A service judgment module, configured to determine whether a service request needs to call an associated system according to the service request;

A business processing module, configured to: when the business request does not need to call an associated system, perform business logic processing according to the business request to obtain a processing result;

A first feedback module, configured to feed back the processing result to the user.
A service processing method, comprising:

Receive forwarded service requests;

Calling a corresponding association system according to the service request;

Receiving a processing result from the associated system;

The processing result is fed back to the user.
The service processing method according to claim 5, further comprising the following steps before the receiving the forwarded service request:

Perform security authentication check according to the service request and user information, determine whether the user has corresponding authority, and receive the forwarded service request when the user has corresponding authority, and when the user does not have corresponding authority, Rejecting the business request.
A call management system, comprising:

A second RPC interface for receiving a forwarded service request and receiving a processing result from an associated system;

A calling module, configured to call a corresponding associated system according to the service request;

The second feedback module is used to feedback the processing result to the user.
The call management system according to claim 7, wherein the call module is configured to call a corresponding associated system according to a mapping relationship between a service request, business logic, and an associated system.
The call management system according to claim 7, further comprising a second authentication module, configured to perform security authentication verification according to the user information and the service request, and determine whether the user has corresponding authority.
A business processing system, comprising the business system according to claim 4, the call management system according to any one of claims 7 to 9, and at least one associated system.
A computer device includes a memory and a processor, the memory is used to store information including program instructions, the processor is used to control the execution of the program instructions, and the program instructions are loaded by the processor The following steps are implemented when executed:

Receive user service requests;

Determining whether the service request needs to call an associated system;

When the service request needs to call an associated system, forwarding the service request;

When the service request does not need to call an associated system, perform business logic processing according to the service request to obtain a processing result;

Feedback the processing result to the user.
The computer device according to claim 11, wherein, when the program instructions are loaded and executed by the processor, the following steps are further implemented:

Perform security authentication check according to the user information and the service request, and determine whether the user has corresponding authority;

When determining that the user has corresponding authority, receiving the service request and the user information of the user, and when determining that the service request needs to call an associated system, forwarding the service request and the user information;

When it is determined that the user does not have corresponding authority, the service request of the user is rejected, and an error is reported to the user.
The computer device according to claim 11 or 12, wherein when the program instructions are loaded and executed by the processor, the following steps are further implemented:

Divide all the business logic in the business system, and determine that the business logic of the associated system does not need to be called, and the business logic of the associated system needs to be called;

Number the business logic that does not need to call the associated system;

Determine the specific associated system that needs to be invoked for each business logic of the associated system;

Number the business logic that needs to call the associated system according to the specific system that needs to be called;

Wherein, performing the business logic processing according to the service request, and obtaining a processing result is: invoking the business logic of a corresponding number according to the service request to obtain the processing result.
A computer non-volatile readable storage medium, characterized in that, when the program is running, controlling a device where the computer non-volatile readable storage medium is located performs the following steps:

Receive user service requests;

Determining whether the service request needs to call an associated system;

When the service request needs to call an associated system, forwarding the service request;

When the service request does not need to call an associated system, perform business logic processing according to the service request to obtain a processing result;

Feedback the processing result to the user.
The computer non-volatile readable storage medium according to claim 14, wherein, when the program runs, controlling a device where the computer non-volatile readable storage medium is located further performs the following steps:

Perform security authentication check according to the user information and the service request, and determine whether the user has corresponding authority;

When determining that the user has corresponding authority, receiving the service request and the user information of the user, and when determining that the service request needs to call an associated system, forwarding the service request and the user information;

When it is determined that the user does not have corresponding authority, the service request of the user is rejected, and an error is reported to the user.
The computer non-volatile readable storage medium according to claim 14 or 15, wherein, when the program is running, controlling a device where the computer non-volatile readable storage medium is located further performs the following steps:

Divide all the business logic in the business system to determine that the business logic of the associated system does not need to be called, and the business logic of the associated system that needs to be called;

Number the business logic that does not need to call the associated system;

Determine the specific associated system that needs to be invoked for each business logic of the associated system;

Number the business logic that needs to call the associated system according to the specific system that needs to be called;

Wherein, performing the business logic processing according to the service request, and obtaining a processing result is: invoking the business logic of a corresponding number according to the service request to obtain the processing result.
A computer device includes a memory and a processor, the memory is used to store information including program instructions, the processor is used to control the execution of the program instructions, and the program instructions are loaded by the processor The following steps are implemented when executed:

Receive forwarded service requests;

Calling a corresponding association system according to the service request;

Receiving a processing result from the associated system;

The processing result is fed back to the user.
The computer device according to claim 17, wherein when the program instructions are loaded and executed by the processor, the following steps are further implemented:

Perform security authentication check according to the service request and user information, determine whether the user has corresponding authority, and receive the forwarded service request when the user has corresponding authority, and when the user does not have corresponding authority, Rejecting the business request.
A computer non-volatile readable storage medium, characterized in that, when the program is running, controlling a device where the computer non-volatile readable storage medium is located performs the following steps:

Receive forwarded service requests;

Calling a corresponding association system according to the service request;

Receiving a processing result from the associated system;

The processing result is fed back to the user.
The computer non-volatile readable storage medium according to claim 19, wherein, when the program runs, controlling a device where the computer non-volatile readable storage medium is located further performs the following steps:

Perform security authentication check according to the service request and user information, determine whether the user has corresponding authority, and receive the forwarded service request when the user has corresponding authority, and when the user does not have corresponding authority, Rejecting the business request.