A method and system for improving service dependency interface efficiency

Abstract

The present invention discloses a method and system for improving the efficiency of a service-dependent interface. When a client detects that a user is logged in, the client sends data acquisition requests to the server for different services, and acquires and stores third-party business data through the server. The client sends a business request containing the third-party business data associated with the business to the server, and the server performs business processing according to the third-party business data therein. The present invention does not require the server to acquire third-party business data from the third party each time the client makes a business request, nor does it require the server to cache the third-party data. In a high-concurrency scenario, the server only needs to care about the quality of its own service, thereby effectively improving system performance. In addition, since there is no other dependency during use, the availability of the system is greatly improved. At the same time, resource loss is small and implementation cost is low.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and system for improving the efficiency of a service dependent interface. Background Art

[0002] Microservices often use caching to improve service performance in high-concurrency scenarios, especially for interfaces that rely on external services. They often use distributed caching to improve interface performance while minimizing the impact of reduced external service quality.

[0003] When the traffic is not large, the system performance can be improved by providing data through a single cache service. When the traffic exceeds the performance bottleneck of a single cache, we often shard the cached data through clustering to speed up the access speed of the cache. For example, the IM (instant messaging) group service in the Central Education Cloud scenario currently has more than 30 million daily active users. Each request for the IM group service must rely on the user data provided by the user center service for business calculation and processing. Caching the data can greatly improve the performance of the group service. However, since the cache of a single machine cannot meet the needs of more than 30 million user data, sharding is used to increase the cache nodes to cache this data.

[0004] However, this server-side caching method has the following disadvantages:

[0005] 1. In terms of performance, although the service interface with external dependencies can improve access efficiency through caching, due to the problem of personalized data in external dependency data, it is impossible to form cache hotspots, which affects cache access efficiency;

[0006] 2. In terms of implementation, based on the sharding solution, developers not only need to focus on business logic, but also need to provide sharding rules to ensure cache access performance. Especially in terms of operation and maintenance, if additional nodes are needed, sharding rules need to be adjusted;

[0007] 3. In terms of availability, the introduction of the cache cluster will add an additional network element to the cache solution, which will inevitably lead to a decrease in availability. In addition, the service itself relies on a third party, and there are extremely high availability requirements for the quality of the third party. Summary of the invention

[0008] The technical problem to be solved by the present invention is to provide a method and system for improving the efficiency of service-dependent interfaces, thereby improving the performance and availability of the server more simply and effectively.

[0009] In order to solve the above technical problems, the technical solution adopted by the present invention is:

[0010] A method for improving the efficiency of a service dependency interface comprises the steps of:

[0011] S1. The client detects that the user is logged in, sends data acquisition requests to the server for different services, obtains third-party service data through the server and stores it;

[0012] S2. The client sends a service request including the third-party service data associated with the service to the server, and the server performs service processing according to the third-party service data.

[0013] In order to solve the above technical problems, another technical solution adopted by the present invention is:

[0014] A system for improving the efficiency of a service-dependent interface includes a client, wherein the client includes a first processor, a first memory, and a first computer program stored in the first memory and executable on the first processor, wherein the first processor implements the following steps when executing the first computer program:

[0015] S1. Detect user login, send data acquisition requests to the server for different services, obtain third-party service data through the server and store it;

[0016] S2. Send a service request including the third-party service data associated with the service to the server, and the server performs service processing according to the third-party service data therein.

[0017] The beneficial effects of the present invention are: a method and system for improving the efficiency of service-dependent interfaces of the present invention, in which the client obtains and stores third-party business data required for various businesses in advance, and attaches the corresponding third-party business data when a specific business request is subsequently initiated. The server does not need to obtain third-party business data from the third party each time the client makes a business request, nor does the server need to cache the third-party data. In a high-concurrency scenario, the server only needs to care about the quality of its own service, effectively improving system performance, and since there is no other dependency during use, the availability of the system is greatly improved. At the same time, resource loss is small and implementation cost is low. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A flow chart of a method for improving the efficiency of a service dependency interface according to an embodiment of the present invention;

[0019] Figure 2 A structural diagram of a system for improving the efficiency of service-dependent interfaces according to an embodiment of the present invention;

[0020] Figure 3 A timing diagram of an example of obtaining third-party business data in a method for improving the efficiency of a service-dependent interface according to an embodiment of the present invention;

[0021] Figure 4This is an example diagram of the architecture of a method for improving the efficiency of a service dependency interface according to an embodiment of the present invention;

[0022] Description of labels:

[0023] 1. A system for improving the efficiency of service-dependent interfaces; 2. Client; 3. Server; 4. First processor; 5. First memory; 6. Second processor; 7. Second memory. DETAILED DESCRIPTION

[0024] In order to explain the technical content, achieved objectives and effects of the present invention in detail, the following is an explanation in combination with the implementation modes and the accompanying drawings.

[0025] Please refer to Figure 1 , Figure 3 and Figure 4 , a method for improving the efficiency of a service dependency interface, comprising the steps of:

[0026] S1. The client detects that the user is logged in, sends data acquisition requests to the server for different services, obtains third-party service data through the server and stores it;

[0027] S2. The client sends a service request including the third-party service data associated with the service to the server, and the server performs service processing according to the third-party service data.

[0028] From the above description, it can be seen that the beneficial effects of the present invention are: a method and system for improving the efficiency of service-dependent interfaces of the present invention, in which the client obtains and stores third-party business data required for various businesses in advance, and attaches the corresponding third-party business data when subsequently initiating a specific business request. The server does not need to obtain third-party business data from the third party every time the client makes a business request, nor does the server need to cache the third-party data. In a high-concurrency scenario, the server only needs to care about the quality of its own service, effectively improving system performance, and since there is no other dependency during use, the availability of the system is greatly improved. At the same time, resource loss is small and the implementation cost is low.

[0029] Furthermore, the storage of the third-party business data in step S1 is specifically as follows:

[0030] The client creates and stores different business tokens for different business associations based on the third-party business data;

[0031] The step S2 comprises the steps of:

[0032] S21, the client sends a service request including the service token associated with the service to the server;

[0033] S22. The server obtains the third-party business data contained in the business token in the business request, and performs business processing according to the third-party business data.

[0034] From the above description, it can be seen that the third-party business data is stored and used in the form of a token. When in use, the token is generally stored in the request header of the request, which can effectively avoid modifying the original request body, distinguish client business data from third-party business data, and is more convenient to use.

[0035] Furthermore, the business token is obtained by concatenating the data part and the verification part;

[0036] The establishment of the business token is specifically as follows:

[0037] The client encodes the third-party business data for different businesses to obtain the data part of the business token, performs summary calculation on the data part, intercepts the content of the preset digits after the calculation result as the verification part of the business token, and splices them to obtain the business token;

[0038] The step S2 further comprises the steps of:

[0039] S211. The server obtains the business data in the business token, performs summary calculation on the business data, intercepts the content of the preset number of bits after the calculation result, and compares and verifies it with the verification part. If the verification passes, the token is deemed valid, the data part is decoded and the next step is entered. Otherwise, the token invalid information is returned.

[0040] From the above description, it can be seen that after encoding the third-party business data, it is necessary to perform summary calculation and splice it to form a token, so that after the server receives the token data, it can verify it to prevent data tampering and improve security.

[0041] Furthermore, the third-party business data includes data required for the business and the issuance time of the data required for the business, and the business processing is specifically performed according to the data required for the business;

[0042] The step S211 further includes the following steps:

[0043] S212. The server obtains the issuance time of the data required for the business in the business data, and determines whether the generation time of the data required for the business exceeds the preset time period based on the issuance time. If so, it is determined that the data required for the business is expired and invalid, and a token invalidation message is returned, otherwise, it proceeds to the next step.

[0044] From the above description, it can be seen that the third-party business data includes the data required for the business and the corresponding issuance time. The server also verifies the issuance time and considers the data with a long issuance time as expired to ensure that the business data is relatively timely and effective.

[0045] Furthermore, the step S1 is specifically as follows:

[0046] S11, the client detects that the user is logged in or the application is awakened, sends a token creation request to the server for different services, and calls the token creation interface of the server;

[0047] S12. The server creates an interface through the token, accesses the third-party interface specified by the service, obtains the third-party service data required by the service, and returns it to the client.

[0048] From the above description, it can be seen that when the user logs in or the application is awakened, the client obtains the third-party business data through the third-party interface of the server.

[0049] A system for improving the efficiency of a service-dependent interface includes a client, wherein the client includes a first processor, a first memory, and a first computer program stored in the first memory and executable on the first processor, wherein the first processor implements the following steps when executing the first computer program:

[0050] S1. Detect user login, send data acquisition requests to the server for different services, obtain third-party service data through the server and store it;

[0051] S2. Send a service request including the third-party service data associated with the service to the server, and the server performs service processing according to the third-party service data therein.

[0052] From the above description, it can be seen that the beneficial effects of the present invention are: a method and system for improving the efficiency of service-dependent interfaces of the present invention, in which the client obtains and stores third-party business data required for various businesses in advance, and attaches the corresponding third-party business data when subsequently initiating a specific business request. The server does not need to obtain third-party business data from the third party every time the client makes a business request, nor does the server need to cache the third-party data. In a high-concurrency scenario, the server only needs to care about the quality of its own service, effectively improving system performance, and since there is no other dependency during use, the availability of the system is greatly improved. At the same time, resource loss is small and the implementation cost is low.

[0053] Furthermore, a server is included, the server includes a second processor, a second memory, and a second computer program stored in the second memory and executable on the second processor, and when the first processor executes the first computer program, the step S1 of storing the third-party business data is specifically as follows:

[0054] According to the third-party business data, different business tokens are established and stored for different business associations;

[0055] The step S2 comprises the steps of:

[0056] S21, sending a service request including the service token associated with the service to the server;

[0057] When the second processor executes the second computer program, step S3 includes the steps of:

[0058] S22. Obtain the third-party service data contained in the service token in the service request, and perform service processing according to the third-party service data.

[0059] From the above description, it can be seen that the third-party business data is stored and used in the form of a token. When in use, the token is generally stored in the request header of the request, which can effectively avoid modifying the original request body, distinguish client business data from third-party business data, and is more convenient to use.

[0060] Furthermore, the business token is obtained by concatenating the data part and the verification part;

[0061] When the first processor executes the first computer program, the establishment of the service token is specifically as follows:

[0062] For different services, the third-party service data is encoded to obtain the data part of the service token, and the data part is digested and calculated, and the content of the preset digits after the calculation result is intercepted as the verification part of the service token, and the service token is obtained by splicing;

[0063] When the second processor executes the second computer program, step S3 further includes the steps of:

[0064] S211. Obtain the business data in the business token, perform summary calculation on the business data, intercept the content of the preset number of bits after the calculation result, and compare and verify it with the verification part. If the verification passes, the token is deemed valid, the data part is decoded and the next step is entered. Otherwise, the token invalid information is returned.

[0065] From the above description, it can be seen that after encoding the third-party business data, it is necessary to perform summary calculation and splice it to form a token, so that after the server receives the token data, it can verify it to prevent data tampering and improve security.

[0066] Furthermore, the third-party business data includes data required for the business and the issuance time of the data required for the business, and the business processing is specifically performed according to the data required for the business;

[0067] When the second processor executes the second computer program, the step S211 further includes the following steps:

[0068] S212. Obtain the issuance time of the business data required by the business data, and determine whether the generation time of the business data required by the business exceeds the preset time period based on the issuance time. If so, it is determined that the business data required by the business is expired and invalid, and a token invalidation message is returned, otherwise proceed to the next step.

[0069] From the above description, it can be seen that the third-party business data includes the data required for the business and the corresponding issuance time. The server also verifies the issuance time and considers the data with a long issuance time as expired to ensure that the business data is relatively timely and effective.

[0070] Further, when the first processor executes the first computer program, step S1 includes the steps of:

[0071] S11. When a user logs in or an application is started, a token creation request is sent to the server for different services, and the token creation interface of the server is called;

[0072] When the second processor executes the second computer program, step S1 comprises the steps of:

[0073] S12. Create an interface through the token, access the third-party interface specified by the service, obtain the third-party service data required by the service, and return it to the client.

[0074] From the above description, it can be seen that when the user logs in or the application is awakened, the client obtains the third-party business data through the third-party interface of the server.

[0075] The method and system of the present invention for improving the efficiency of service dependency interfaces are applicable to business scenarios where there is a dependency on third-party service data and the third-party business data does not change frequently, or the third-party business data changes frequently but temporary inconsistency of the third-party business data can be tolerated.

[0076] Please refer to Figure 1 and Figure 3, Embodiment 1 of the present invention is:

[0077] A method for improving the efficiency of a service dependency interface comprises the steps of:

[0078] S1. The client detects that the user is logged in, sends data acquisition requests to the server for different services, obtains third-party service data through the server and stores it;

[0079] The storage of the third-party business data in step S1 is specifically as follows:

[0080] The client creates and stores different business tokens for different business associations based on the third-party business data;

[0081] The step S1 comprises the steps of:

[0082] S11, the client detects that the user is logged in or the application is awakened, sends a token creation request to the server for different services, and calls the token creation interface of the server;

[0083] S12. The server creates an interface through the token, accesses the third-party interface specified by the service, obtains the third-party service data required by the service, and returns it to the client.

[0084] In this embodiment, when a user logs in or an application is invoked, the client calls the token creation interface of the server, which accesses the relevant third-party interface, obtains the required data, creates a business token and stores it.

[0085] like Figure 3 In the example shown, as a SaaS service, most interfaces of the group service rely on the organization ID (orgId) of the user center service and the tenant ID (tenantId) of the tenant service. The group service provides an interface for creating a business token. The interface uses the user ID (userId) to access these two interfaces to obtain the corresponding data (userData1, userData2). After the client obtains the token through the business token creation interface, it is stored locally.

[0086] S2. The client sends a service request including the third-party service data associated with the service to the server, and the server performs service processing according to the third-party service data therein;

[0087] The step S2 comprises the steps of:

[0088] S21, the client sends a service request including the service token associated with the service to the server;

[0089] S22. The server obtains the third-party business data contained in the business token in the business request, and performs business processing according to the third-party business data.

[0090] In this embodiment, when a request for a service is initiated next time, a business token is added to the http header parameter. For example, when a client related to a group service requests a group service again, a group-token is added to the request header, and its value is the corresponding business token value stored locally.

[0091] Please refer to Figure 1 , Figure 3 and Figure 4 , Embodiment 2 of the present invention is:

[0092] A method for improving the efficiency of a service-dependent interface, which differs from the first embodiment in that the service token is obtained by concatenating a data part and a verification part;

[0093] The establishment of the business token is specifically as follows:

[0094] The client encodes the third-party business data for different businesses to obtain the data part of the business token, performs summary calculation on the data part, intercepts the content of the preset number of digits after the calculation result as the verification part of the business token, and splices them to obtain the business token.

[0095] In this embodiment, the business token is generated from two parts, the first part of which is represented by the business data and the issuance time in a JSON structure, and then the JSON string is base64 encoded; the second part is the summary part, which is based on the base64 encoding result plus salt and then the summary is calculated, and the last 16 bits of the summary are intercepted to ensure the legitimacy of the first part of the data. For example:

[0096] In the group service, the business data is:

[0097] {

[0098] "user_id": 777,

[0099] "org_id": 481036337155,

[0100] "tenant_id":"aaa65g6",

[0101] "create_time":1665208676747

[0102] }

[0103] The string after base64 encoding is:

[0104] eyJleHBpcmVkX3RpbWUiOjE2NjUyMDg2NzY3NDcsIm9yZ19pZCI6NDgxMDM2MzM3MTU1LCJ0ZW5hbnRfaWQiOiJhYWE2NWc2IiwidXNlcl9pZCI6Nzc3fQ==

[0105] When the salt value is "#", the result of the summary calculation based on the national encryption algorithm SM3 is:

[0106] bb0ecf1e65573e9450faf401830195dee0d30dc04d0c1b2aa07efc7fdbab96af

[0107] The last 16 bits of the digest calculation result are intercepted and concatenated with the encoded string to obtain the final business token:

[0108] eyJleHBpcmVkX3RpbWUiOjE2NjUyMDg2NzY3NDcsIm9yZ19pZCI6NDgxMDM2MzM3MTU1LCJ0ZW5hbnRfaWQiOiJhYWE2NWc2IiwidXNlcl9pZCI6Nzc3fQ==a07efc7fdbab96af.

[0109] In this embodiment, the preset number of bits is 16 bits. In other equivalent embodiments, it can be adjusted according to actual needs.

[0110] The step S2 further comprises the steps of:

[0111] S211. The server obtains the business data in the business token, performs summary calculation on the business data, intercepts the content of the preset number of bits after the calculation result, and compares and verifies it with the verification part. If the verification passes, the token is deemed valid, the data part is decoded and the next step is entered. Otherwise, the token invalid information is returned.

[0112] In this embodiment, Figure 4 As shown, the business token needs to be verified. When the server receives a business request, it first obtains the business token from the request header, then performs digest verification, cuts off the last 16 digits, calculates the digest, and compares it with the last 16 digits cut off. If it passes, the character is decoded directly, otherwise the token is invalid.

[0113] The third-party business data includes data required for the business and the issuance time of the data required for the business, and the business processing is specifically performed according to the data required for the business;

[0114] The step S211 further includes the following steps:

[0115] S212. The server obtains the issuance time of the data required for the business in the business data, and determines whether the generation time of the data required for the business exceeds the preset time period based on the issuance time. If so, it is determined that the data required for the business is expired and invalid, and a token invalidation message is returned, otherwise, it proceeds to the next step.

[0116] In this embodiment, it is also necessary to determine the issuance time (creation time), which is the time for obtaining the third-party business data in this embodiment. In other equivalent embodiments, it can also be selected as the creation time of the business token. It is determined whether the issuance time (creation time) exceeds the preset time period. The preset time period is defined by the business service. In this embodiment, it is 6 hours. In other equivalent embodiments, it can be adjusted according to demand. If it is within the time range, the data required for the business in the business token is directly used for processing, thereby improving the interface performance. Otherwise, it expires and cannot be used.

[0117] Of course, in order to ensure the compatibility of the interface, if the request header does not contain a business-related token or the business token is invalid, the corresponding data will be obtained from each dependent third party for processing according to the original logic.

[0118] Please refer to Figure 2 , Embodiment 3 of the present invention is:

[0119] A system 1 for improving the efficiency of a service-dependent interface, characterized in that it includes a client 2 and a server 3, wherein the client includes a first processor 4, a first memory 5, and a first computer program stored in the first memory 5 and executable on the first processor 4, and the server 3 includes a second processor 6, a second memory 7, and a computer program stored in the second memory 7 and executable on the second processor 6, and when the first processor 4 executes the first computer program and the second processor 6 executes the second computer program, the steps in a method for improving the efficiency of a service-dependent interface in the above embodiment one or two are jointly implemented.

[0120] The main idea of ​​the present invention is that after logging in or calling up the application, the user creates a business token that relies on third-party business data, and brings this business token when accessing service-related interfaces, reducing the service's dependence on third-party requests, thereby improving the interface's response efficiency and service availability.

[0121] This patent proposes a solution to improve the performance of external service dependency interfaces. In the necessary path for user access (such as event processing after user login, application wake-up event processing), a business token is issued, and the token is based on the third-party dependent data and cache expiration time, and the result of base64 encoding and digest calculation (such as based on national encryption SM3) is spliced. Each time the client accesses an interface related to third-party dependency, it brings this token. The server first calculates and verifies the digest. After successful processing, it directly uses the third-party business data in the decoded token for business processing. In this way, the interface reduces calls to third-party services and greatly improves the access efficiency of the service.

[0122] To sum up, the present invention provides a method and system for improving the efficiency of service dependency interfaces, in which the client obtains and stores third-party business data required for various businesses in advance, and attaches the corresponding third-party business data when subsequently initiating a specific business request. The server does not need to obtain third-party business data from the third party each time the client makes a business request, nor does the server need to cache the third-party data. In a high-concurrency scenario, the server only needs to care about the quality of its own service, which effectively improves system performance. In addition, since there is no other dependency during use, the availability of the system is greatly improved. At the same time, resource loss is small and the implementation cost is low.

[0123] The effect that can be achieved:

[0124] 1. Data caching based on the client reduces external requests and improves the performance of external dependency-related interfaces;

[0125] 2. Lightweight, low resource consumption, the server only increases the CPU consumption of summary calculation;

[0126] 3. Low implementation cost, only adding token creation and verification functions;

[0127] 4. High O&M: Since the cache is on the client, you only need to care about the quality of the service in high-concurrency scenarios.

[0128] 5. High availability. Since there is no other dependency during use, the availability of the system is greatly improved.

[0129] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent transformations made using the contents of the present invention's specification and drawings, or directly or indirectly applied in related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for improving the efficiency of a service-dependent interface, characterized in that: Includes steps: S1. The client detects that the user is logged in, sends data acquisition requests to the server for different services, obtains third-party service data through the server and stores it; The step S1 comprises the steps of: S11, the client detects that the user logs in or the application is awakened, sends a token creation request to the server for different services, and calls the token creation interface of the server; S12. The server creates an interface through the token, accesses the third-party interface specified by the service, obtains the third-party service data required by the service, and returns it to the client; The storage of the third-party business data in step S1 is specifically as follows: The client creates and stores different business tokens for different business associations based on the third-party business data; S2. The client sends a service request including the third-party service data associated with the service to the server, and the server performs service processing according to the third-party service data therein; The step S2 comprises the steps of: S21, the client sends a service request including the service token associated with the service to the server; S22. The server obtains the third-party business data contained in the business token in the business request, and performs business processing according to the third-party business data.

2. A method for improving the efficiency of service-dependent interfaces according to claim 1, characterized in that: The business token is obtained by concatenating the data part and the verification part; The establishment of the business token is specifically as follows: The client encodes the third-party business data for different businesses to obtain the data part of the business token, performs summary calculation on the data part, intercepts the content of the preset digits after the calculation result as the verification part of the business token, and splices them to obtain the business token; The step S2 further comprises the steps of: S211. The server obtains the business data in the business token, performs summary calculation on the business data, intercepts the content of the preset number of bits after the calculation result, and compares and verifies it with the verification part. If the verification passes, the token is deemed valid, the data part is decoded and the next step is entered. Otherwise, the token invalid information is returned.

3. A method for improving service dependency interface efficiency according to claim 2, characterized in that: The third-party business data includes data required for the business and the issuance time of the data required for the business, and the business processing is specifically performed according to the data required for the business; The step S211 further includes the following steps: S212. The server obtains the issuance time of the data required for the business in the business data, and determines whether the generation time of the data required for the business exceeds the preset time period based on the issuance time. If so, it is determined that the data required for the business is expired and invalid, and a token invalidation message is returned, otherwise, it proceeds to the next step.

4. A system for improving the efficiency of service dependency interfaces, characterized in that: The method comprises a client, wherein the client comprises a first processor, a first memory, and a first computer program stored in the first memory and executable on the first processor, wherein the first processor implements the following steps when executing the first computer program: S1. Detect user login, send data acquisition requests to the server for different services, obtain third-party service data through the server and store it; The step S1 comprises the steps of: S11, the client detects that the user logs in or the application is awakened, sends a token creation request to the server for different services, and calls the token creation interface of the server; S12. The server creates an interface through the token, accesses the third-party interface specified by the service, obtains the third-party service data required by the service, and returns it to the client; The storage of the third-party business data in step S1 is specifically as follows: The client creates and stores different business tokens for different business associations based on the third-party business data; S2. Sending a service request including the third-party service data associated with the service to the server, and the server performs service processing according to the third-party service data therein; The step S2 comprises the steps of: S21, the client sends a service request including the service token associated with the service to the server; S22. The server obtains the third-party business data contained in the business token in the business request, and performs business processing according to the third-party business data.

5. A system for improving service dependency interface efficiency according to claim 4, characterized in that: The business token is obtained by concatenating the data part and the verification part; When the first processor executes the first computer program, the establishment of the service token is specifically as follows: For different services, the third-party service data is encoded to obtain the data part of the service token, and the data part is digested and calculated, and the content of the preset digits after the calculation result is intercepted as the verification part of the service token, and the service token is obtained by splicing; When the second processor executes the second computer program, step S3 further includes the steps of: S211. Obtain the business data in the business token, perform summary calculation on the business data, intercept the content of the preset number of bits after the calculation result, and compare and verify it with the verification part. If the verification passes, the token is deemed valid, the data part is decoded and the next step is entered. Otherwise, the token invalid information is returned.

6. A system for improving service dependency interface efficiency according to claim 5, characterized in that: The third-party business data includes data required for the business and the issuance time of the data required for the business, and the business processing is specifically performed according to the data required for the business; When the second processor executes the second computer program, the step S211 further includes the following steps: S212. Obtain the issuance time of the business data required by the business data, and determine whether the generation time of the business data required by the business exceeds the preset time period based on the issuance time. If so, it is determined that the business data required by the business is expired and invalid, and a token invalidation message is returned, otherwise proceed to the next step.

Images