CN113032036B - Service data processing method, device, system, computer equipment and storage medium - Google Patents

Service data processing method, device, system, computer equipment and storage medium Download PDF

Info

Publication number
CN113032036B
CN113032036B CN202110147723.4A CN202110147723A CN113032036B CN 113032036 B CN113032036 B CN 113032036B CN 202110147723 A CN202110147723 A CN 202110147723A CN 113032036 B CN113032036 B CN 113032036B
Authority
CN
China
Prior art keywords
target
program logic
logic layer
state information
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110147723.4A
Other languages
Chinese (zh)
Other versions
CN113032036A (en
Inventor
秦勤
蒲茂阳
王健
袁珍珍
姚兵
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN202110147723.4A priority Critical patent/CN113032036B/en
Publication of CN113032036A publication Critical patent/CN113032036A/en
Application granted granted Critical
Publication of CN113032036B publication Critical patent/CN113032036B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G06F9/4451—User profiles; Roaming
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/62—Uninstallation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates

Abstract

The application relates to a business data processing method, a business data processing device, a business data processing system, a computer device and a storage medium. The method comprises the following steps: acquiring a target service request; the target service request carries a target user identifier; acquiring local program logic layer state information corresponding to a target user identifier locally, and acquiring reference program logic layer state information corresponding to the target user identifier from a target docking server; updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification; screening to obtain the state information of the logic layer of the target program based on the state information of the logic layer of the local program and the updated state in the state information of the logic layer of the reference program; and processing the target service request through the target program logic layer corresponding to the state information of the target program logic layer to obtain a service processing result. The method can ensure the orderliness of service processing.

Description

Service data processing method, device, system, computer equipment and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a system, a computer device, and a storage medium for processing service data.
Background
With the development of computer technology, users can handle many services on line. In order to process the service requests initiated by a large number of users, a plurality of service servers are deployed, and the service requests initiated by the users can be randomly distributed to a certain service server for processing. The service server stores configuration files, the configuration files are used for determining program logic layers for processing service requests, and each service request needs to be processed through the corresponding program logic layer.
Conventionally, the update of the configuration file between the plurality of service servers is not synchronized. Therefore, if the program logic layer corresponding to the service request depends on the configuration file on the service server, the service request corresponding to the same user is sometimes processed on one program logic layer and sometimes processed on the other program logic layer, which results in confusion in processing the service request.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a service data processing method, device, system, computer device, and storage medium capable of guaranteeing the ordering of service processing.
A method for processing service data, the method comprising:
acquiring a target service request; the target service request carries a target user identifier;
acquiring local program logic layer state information corresponding to a target user identifier locally, and acquiring reference program logic layer state information corresponding to the target user identifier from a target docking server; updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification;
screening to obtain the state information of the logic layer of the target program based on the state information of the logic layer of the local program and the updated state in the state information of the logic layer of the reference program;
and processing the target service request through the target program logic layer corresponding to the state information of the target program logic layer to obtain a service processing result.
A traffic data processing apparatus, the apparatus comprising:
the service request acquisition module is used for acquiring a target service request; the target service request carries a target user identifier;
the program logic layer state information acquisition module is used for locally acquiring local program logic layer state information corresponding to the target user identification and acquiring reference program logic layer state information corresponding to the target user identification from the target docking server; updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification;
the target program logic layer state information determining module is used for screening and obtaining target program logic layer state information based on the updating state in the local program logic layer state information and the reference program logic layer state information;
and the service processing module is used for processing the target service request through the target program logic layer corresponding to the state information of the target program logic layer to obtain a service processing result.
In one embodiment, the target docking server serves a plurality of candidate service servers, and each service request carrying the target user identifier is randomly allocated to any one of the candidate service servers for processing.
In one embodiment, the program logic layer state information acquisition module is further configured to locally acquire a program logic layer state information configuration file; the program logic layer state information configuration file comprises user identification configuration information corresponding to various program logic layer states respectively; determining the state of a local program logic layer corresponding to the target user identification based on the matching result of the target user identification and the configuration information of each user identification; the local program logic layer state information is obtained based on the current version of the program logic layer state information configuration file and the local program logic layer state.
In one embodiment, the program logic layer state information obtaining module is further configured to perform mapping processing on the target user identifier to obtain a target user mapping identifier; determining a target docking server from each candidate docking server based on a matching result of the target user mapping identifier and a user mapping identifier range corresponding to a plurality of candidate docking servers; and determining the state information of the logic layer of the reference program from the state information of the logic layer of the candidate program corresponding to each candidate user identifier in the target docking server based on the matching result of the target user identifier and each candidate user identifier in the target docking server.
In one embodiment, the update status includes a status version, and the target program logic layer status information determining module is further configured to filter, from the local program logic layer status information and the reference program logic layer status information, program logic layer status information corresponding to a latest status version as target program logic layer status information.
In one embodiment, the apparatus further comprises:
the program logic layer state information updating module is used for generating a program logic layer state information updating request according to the target user identifier and the local program logic layer state information when the state version of the local program logic layer state information is updated; and sending the program logic layer state information updating request to the target docking server so that the target docking server updates the reference program logic layer state information into the local program logic layer state information according to the program logic layer state information updating request.
In one embodiment, the service processing module is further configured to query a request status of a historical service request corresponding to the target user identifier; when the request state of at least one historical service request is unfinished, processing a target service request through a processing program logic layer to obtain a service processing result; and when the request states of all historical service requests are finished, processing the target service requests through the target program logic layer to obtain service processing results.
In one embodiment, when the target program logic layer is a general program logic layer, the service processing module is further configured to obtain a general service processing logic from the general program logic layer; and processing the target service request based on the general service processing logic to obtain a service processing result.
In one embodiment, the target service request carries a target service identifier, when the target program logic layer is a dedicated program logic layer, the dedicated program logic layer stores candidate service processing logics corresponding to a plurality of candidate service identifiers, respectively, and the service processing module is further configured to obtain the target service processing logic corresponding to the target service identifier from the dedicated program logic layer; and processing the target service request based on the target service processing logic to obtain the service processing result.
In one embodiment, the current service processing logic includes a general service processing logic or a target service processing logic, and the service processing module is further configured to obtain historical service processing statistical information corresponding to the target user identifier from the processing program logic layer when the processing program logic layer is inconsistent with the target program logic layer; and sending the historical service processing statistical information to a target program logic layer so that the target program logic layer processes the target service request based on the historical service processing statistical information and the current service processing logic to obtain a service processing result.
In one embodiment, the service processing module is further configured to obtain target service information from the target service request; obtaining target service processing statistical information based on the historical service processing statistical information and the target service information; acquiring standard service processing statistical information, and determining reference service information based on the standard service processing statistical information and the target service processing statistical information; and obtaining a service processing result based on the target service information and the reference service information.
A business data processing system, characterized in that, the system includes a target business server and a target docking server;
the target service server is used for acquiring a target service request, wherein the target service request carries a target user identifier, locally acquiring local program logic layer state information corresponding to the target user identifier, generating a program logic layer state information query request corresponding to the target service request, and sending the program logic layer state information query request to the target docking server;
the target docking server is used for locally acquiring the reference program logic layer state information corresponding to the target user identification according to the program logic layer state information query request and returning the reference program logic layer state information to the processing server; updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification;
the target service server is further configured to obtain target program logic layer state information by screening based on the update state in the local program logic layer state information and the reference program logic layer state information, and process the target service request through a target program logic layer corresponding to the target program logic layer state information to obtain a service processing result.
In one embodiment, the system comprises a plurality of candidate service servers, wherein a target server serves each candidate service server, and each service request carrying a target user identifier is randomly allocated to any one of the candidate service servers for processing.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
acquiring a target service request; the target service request carries a target user identifier;
acquiring local program logic layer state information corresponding to a target user identifier locally, and acquiring reference program logic layer state information corresponding to the target user identifier from a target docking server; updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification;
screening to obtain the state information of the logic layer of the target program based on the state information of the logic layer of the local program and the updated state in the state information of the logic layer of the reference program;
and processing the target service request through the target program logic layer corresponding to the state information of the target program logic layer to obtain a service processing result.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
acquiring a target service request; the target service request carries a target user identifier;
acquiring local program logic layer state information corresponding to a target user identifier locally, and acquiring reference program logic layer state information corresponding to the target user identifier from a target docking server; updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification;
screening to obtain the state information of the logic layer of the target program based on the state information of the logic layer of the local program and the updated state in the state information of the logic layer of the reference program;
and processing the target service request through the target program logic layer corresponding to the state information of the target program logic layer to obtain a service processing result.
The service data processing method, the device, the system, the computer equipment and the storage medium acquire the target service request; the target service request carries a target user identifier, local program logic layer state information corresponding to the target user identifier is obtained locally, reference program logic layer state information corresponding to the target user identifier is obtained from a target docking server, the reference program logic layer state information is updated according to a processing program logic layer corresponding to an adjacent historical service request, the adjacent historical service request carries the target user identifier, the target program logic layer state information is obtained through screening based on the update states in the local program logic layer state information and the reference program logic layer state information, and the target service request is processed through the target program logic layer corresponding to the target program logic layer state information to obtain a service processing result. Thus, each time the target service server obtains a service request, the target service server queries the local and target docking servers for a target program logic layer for processing the current service request. The method determines the state information of the logic layer of the target program through the comparison of the state information of the logic layer of the local program and the state information of the logic layer of the reference program, can ensure that once a certain user initiates a service request at a certain time, if the state information of the logic layer of the program is changed, all subsequent service requests are uniformly subject to the latest state information of the logic layer of the target program after the change, avoid the problem that the logic layer of the program for processing the service request is continuously changed due to the fact that a configuration file is published among a plurality of service servers in a sequential order, and ensure the orderliness of service processing.
Drawings
FIG. 1 is a diagram of an application environment of a method for processing service data in one embodiment;
FIG. 2 is a block chain system diagram in accordance with an embodiment;
FIG. 3 is a flow chart illustrating a method for processing service data according to an embodiment;
FIG. 4 is a flowchart illustrating a process of locally obtaining state information of a local program logic layer corresponding to a target user identifier in one embodiment;
FIG. 5 is a flowchart illustrating an embodiment of obtaining reference program logic layer state information corresponding to a target user identifier from a target docking server;
FIG. 6 is a block diagram of a business data processing system in accordance with one embodiment;
FIG. 7A is a block diagram of a business data processing system in accordance with another embodiment;
FIG. 7B is a block diagram of a business data processing system in accordance with yet another embodiment;
fig. 8 is a schematic flow chart of a service data processing method in another embodiment;
FIG. 9 is a block diagram of a business data processing apparatus in one embodiment;
FIG. 10 is a block diagram showing the construction of a service data processing apparatus according to an embodiment;
FIG. 11 is a diagram illustrating an internal structure of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The service data processing method provided by the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 communicates with the target service server 104 through a network. The service request sent by the terminal can be randomly distributed to any one candidate service server, and the candidate service server for acquiring the service request is taken as a target service server. The target traffic server 104 communicates with the target docking server 106 over a network. Each candidate service server may communicate with the target docking server. The terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and both the service server and the docking server may be implemented by an independent server or a server cluster composed of a plurality of servers.
The system related to the embodiment of the invention can be a distributed system formed by connecting a client, a plurality of nodes (any form of computing equipment in an access network, such as a server and a user terminal) through a network communication mode. A user may initiate a service request through a client. The nodes may include a traffic server and a docking server. The service server may be used to process service requests and the docking server may be used to provide relevant data to the service server, for example, with reference to program logic layer state information. The service server and the docking server may be plural.
Taking a distributed system as an example of a blockchain system, referring To fig. 2, fig. 2 is an optional structural schematic diagram of the distributed system 100 applied To the blockchain system, which is formed by a plurality of nodes (computing devices in any form in an access network, such as servers and user terminals) and clients, and a Peer-To-Peer (P2P, Peer To Peer) network is formed between the nodes, and the P2P Protocol is an application layer Protocol operating on a Transmission Control Protocol (TCP). In a distributed system, any machine, such as a server or a terminal, can join to become a node, and the node comprises a hardware layer, a middle layer, an operating system layer and an application layer.
Referring to the functions of each node in the blockchain system shown in fig. 2, the functions involved include:
1) routing, a basic function that a node has, is used to support communication between nodes.
Besides the routing function, the node may also have the following functions:
2) the application is used for being deployed in a block chain, realizing specific services according to actual service requirements, recording data related to the realization functions to form recording data, carrying a digital signature in the recording data to represent a source of task data, and sending the recording data to other nodes in the block chain system, so that the other nodes add the recording data to a temporary block when the source and integrity of the recording data are verified successfully.
For example, the services implemented by the application include:
2.1) wallet, for providing the function of transaction of electronic money, including initiating transaction (i.e. sending the transaction record of current transaction to other nodes in the blockchain system, after the other nodes are successfully verified, storing the record data of transaction in the temporary blocks of the blockchain as the response of confirming the transaction is valid; of course, the wallet also supports the querying of the remaining electronic money in the electronic money address;
and 2.2) sharing the account book, wherein the shared account book is used for providing functions of operations such as storage, query and modification of account data, record data of the operations on the account data are sent to other nodes in the block chain system, and after the other nodes verify the validity, the record data are stored in a temporary block as a response for acknowledging that the account data are valid, and confirmation can be sent to the node initiating the operations.
2.3) Intelligent contracts, computerized agreements, which can enforce the terms of a contract, implemented by codes deployed on a shared ledger for execution when certain conditions are met, for completing automated transactions according to actual business requirement codes, such as querying the logistics status of goods purchased by a buyer, transferring the buyer's electronic money to the merchant's address after the buyer signs for the goods; of course, smart contracts are not limited to executing contracts for trading, but may also execute contracts that process received information.
3) And the Block chain comprises a series of blocks (blocks) which are mutually connected according to the generated chronological order, new blocks cannot be removed once being added into the Block chain, and recorded data submitted by nodes in the Block chain system are recorded in the blocks.
In one embodiment, as shown in fig. 3, a service data processing method is provided, which is described by taking the application of the method to the target service server in fig. 1 as an example, and includes the following steps:
step S302, obtaining a target service request; the target service request carries a target user identifier.
Wherein the service request is a request for triggering service processing. For example, in a social payment service, a service request may be used to request transfer of a virtual resource from one electronic account to another. The target service request refers to a service request currently received by the target service server. The service request carries a user identifier, which is an identifier used for uniquely identifying a triggering user of the service request, and may specifically include a character string of at least one character of letters, numbers, and symbols. For example, an instant communication number, mobile communication number, social network account number, etc. of the user is triggered. The target user identifier refers to a user identifier corresponding to a trigger user of the target service request.
Specifically, a user may trigger a target service request at a terminal, and the terminal sends the target service request to a target service server, so that the target service server processes the target service request. For example, user a sends a red packet to user B in the instant messaging application of the terminal, which may trigger a red packet service request.
Step S304, local program logic layer state information corresponding to the target user identification is obtained locally, and reference program logic layer state information corresponding to the target user identification is obtained from the target docking server; and updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification.
Wherein, the program logic layer state information refers to the state information of the program logic layer for processing the service request. The program logic layer state information includes a program logic layer state and an update state. The program logic layer includes a general program logic layer and a special program logic layer. The program logic layer states include a state from the dedicated program logic layer grayscale to the general program logic layer and a state from the general program logic layer back to the dedicated program logic layer. The general program logic layer mainly comprises general and basic program logic codes among a plurality of services. The special program logic layer mainly comprises program logic codes special for each service and program logic codes related to service logic and service flows. For example, in the P2P social payment scenario, four specific services are involved, namely red envelope, face-to-face collection, P2P transfer, and AA collection. P2P social payments refer to virtual resource transfers that occur from individual user to individual user. Logic code for payments (e.g., transfers, withdrawals, refunds, etc.) for various services may be stored in a common program logic layer, as payments are logic common to various services that require virtual resources to be transferred between electronic accounts. The general program logic layer can specifically comprise a payment interface, a transfer interface and the like. While the specific business logic of red envelope, face-to-face collection, P2P transfer, AA collection is different. For example, in a red packet service process, the receiving side does not receive the virtual resource packet within a preset time, the virtual resource corresponding to the red packet is returned to the sending side, and the program logic code dedicated to the red packet service can be stored in the dedicated program logic layer. In the recharging scene, the specific services of telephone fee recharging, flow recharging, game currency recharging and the like are involved. Logic code for payment in each transaction may be stored in a common program logic layer. The program logic code associated with the business processes of the respective business may be stored in a dedicated layer of program logic. For example, program logic codes related to business processes, such as telephone bill ordering, bill inquiry, charging success notification and the like in the telephone fee charging business can be stored in a special program logic layer. In the authority management scene, the method relates to specific services such as data consulting authority, data downloading authority, data uploading authority and data modifying authority, and logic codes related to authority searching in each service can be stored in a general program logic layer. The specific implementation logic for each privilege may be stored in a dedicated program logic layer. It will be appreciated that program logic code having the same functionality may also exist between services in a dedicated program logic layer. For example, in the P2P social payment scenario, the calculation and collection of the commission fees is carried out by the respective services themselves in charge. In the permission management scenario, permission modification is implemented by each service in charge of itself. Program logic code having the same function exists between the dedicated program logic layer and the general-purpose program logic layer. For example, in the P2P social payment scenario, the calculation and collection of the commission fees may be implemented at either a dedicated or a general purpose program logic level.
The local program logic layer state information refers to program logic layer state information which is inquired locally in the target service server, and the reference program logic layer state information refers to program logic layer state information which is inquired in the target docking server. The target docking server stores program logic layer state information corresponding to a plurality of user identifications respectively.
The adjacent historical service request and the target service request both carry target user identification, namely the adjacent historical service request and the target service request are triggered by the same user. The adjacent historical service request refers to a service request triggered by a triggering user corresponding to the target service request at a historical time, and is a last service request corresponding to the target service request, namely the adjacent historical service request is a historical service request which is triggered by the user before the target service request is triggered. When the service server receives a service request each time, the service server inquires program logic layer state information in the local and corresponding docking servers, and selects a program logic layer corresponding to the newer program logic layer state information to process the service request, and the docking server also updates and stores the newer program logic layer state information in the local. Therefore, the reference program logic layer state information stored in the target docking server is updated according to the processing program logic layer corresponding to the adjacent historical service request. The program logic layer corresponding to the reference program logic layer state information stored in the target docking server is necessarily the handler logic layer corresponding to the adjacent historical service request. The handler logic layer refers to a program logic layer that handles adjacent historical service requests.
Specifically, after acquiring the target service request, the target service server may locally acquire the local program logic layer state information corresponding to the target user identifier, and acquire the reference program logic layer state information corresponding to the target user identifier from the target docking server. The target service server may specifically generate a program logic layer state information query request carrying the target user identifier, and send the program logic layer state information query request to the target docking server, so that the target docking server locally obtains, according to the program logic layer state information query request, reference program logic layer state information corresponding to the target user identifier, and returns the reference program logic layer state information.
In one embodiment, the target business server stores program logic layer state information in the form of a configuration file. The configuration file comprises user identification configuration information corresponding to various program logic layer states respectively. For example, when the user identification includes an "ABC" character, the corresponding program logic layer state is a state from the application specific program logic layer grayscale to the general program logic layer. The target docking server stores program logic layer state information in the unit of user identification. For example, the program logic layer state corresponding to the user identifier 1 is a state from the dedicated program logic layer gray scale to the general program logic layer.
In one embodiment, the target docking server serves a plurality of candidate service servers, and each service request carrying the target user identifier is randomly allocated to any one of the candidate service servers for processing.
Specifically, the target docking server serves a plurality of candidate service servers, each of which may be in data communication with the target docking server. After a user triggers a target service request at a terminal, the target service request is randomly distributed to any one candidate service server for processing, and the candidate service server receiving the target service request is used as the target service server.
In one embodiment, the target docking server is a centralized docking server. All reference program logic layer state information corresponding to the user identification is stored on the centralized docking server.
In one embodiment, to relieve the storage pressure of the docking server, multiple candidate docking servers may be set up. And each candidate docking server respectively stores reference program logic layer state information corresponding to part of user identifications. After receiving the target user identifier, the target service server may determine a target docking server corresponding to the target user identifier from each candidate docking server, and obtain the reference program logic layer state information corresponding to the target user identifier from the target docking server.
In one embodiment, when the local program logic layer state information is updated, the local program logic layer state information is updated into the target docking server in time to replace the reference program logic layer state information.
Step S306, based on the updating state in the local program logic layer state information and the reference program logic layer state information, the target program logic layer state information is obtained through screening.
Wherein the update status is an update time for determining the program logic layer status information. The update status may specifically include information such as update time, status version, etc.
Specifically, the target service server may screen out newer program logic layer state information from the local program logic layer state information and the reference program logic layer state information as the target program logic layer state information based on the updated state in the local program logic layer state information and the reference program logic layer state information. For example, the program logic layer state information updated at the update time is taken as the target program logic layer state information. And taking the state information of the program logic layer with the updated state version as the state information of the target program logic layer.
Step S308, the target service request is processed through the target program logic layer corresponding to the state information of the target program logic layer, and a service processing result is obtained.
The target program logic layer refers to a program logic layer for processing a target service request. And if the program logic layer state in the target program logic layer state information is from the gray level of the special program logic layer to the gray level of the general program logic layer, the corresponding target program logic layer is the general program logic layer. And if the program logic layer state in the target program logic layer state information is from the general program logic layer to the special program logic layer, the corresponding target program logic layer is the special program logic layer.
Specifically, after the state information of the target program logic layer is determined, the target service server may process the target service request through the target program logic layer corresponding to the state information of the target program logic layer, so as to obtain a service processing result. The service processing result may be an intermediate processing result corresponding to the target service request, and the intermediate processing result is further processed subsequently to obtain the target processing result. For example, when the target service request is a red envelope service request, the processing of the target service request through the target program logic layer may specifically be calculating a total amount to be paid by a user initiating the red envelope, where the total amount includes a red envelope amount triggered by the user and a commission fee correspondingly generated. The result of the transaction may be a commission and a total amount. Subsequently, the total amount may be transferred from the electronic account of the user initiating the red envelope to the intermediate account, and when the user receiving the red envelope receives the red envelope, the amount of the red envelope is transferred from the intermediate account to the electronic account of the user receiving the red envelope, and the commission fee is transferred from the intermediate account to the commission fee account.
Because the service user amount is usually massive, if a new program logic code is to be online on the general program logic layer to replace a redundant program logic code with the same function among all services in the special program logic layer, in order to ensure that the range of influence is controllable, user gray levels can be selected, namely, under the condition that the current network running condition is not expected or other adverse consequences are caused according to the user gray levels, the consequences which are not expected are limited to the controllable range as much as possible, and the rolling back is carried out in time. Specifically, the gray level service can be utilized to control that only a few users' service requests in a controllable range are switched at a time and processed through a new program logic code, and then whether the running condition, the running logic and the running result of the program logic code meet expectations or not is observed. If no problems are identified, the new program logic code can be re-grayed to more users and observed by further modifying the profile of the grayscale service.
For example, in the conventional method, the old charging scheme of the credit card commission is that the calculation of the commission is realized by each specific service, and is completed by a special program logic layer, which is completely transparent to a general program logic layer, and the general program logic layer does not sense the existence of the commission. The old charging scheme may also be referred to as service side charging and the dedicated program logic layer may also be referred to as service side. The new charging mode of the credit card commission fee is to move the calculation and charging of the commission fee from the special program logic layer to the general program logic layer. The logic of charging the commission fee is not realized by each service, but is moved to the general program logic layer to be completed uniformly, and the service logic of each service is not inserted into a series of logic related to the commission fee separately. The new charging scheme may also be referred to as wallet-side charging and the generic program logic layer may also be referred to as wallet-side. However, the change of the configuration file among the plurality of service servers is a process, for example, at a certain time point, the configuration file of the service server a may have been upgraded to a new version, but the service server B is still an old version, and the configuration file of the service server B is still an old version for a period of time. If it is determined whether the service side charging or the wallet side charging is performed directly according to the configuration file local to the service server, a problem in service logic may occur. For example, a service request initiated by a user may be first distributed to the service server a with a newer profile version, and it is determined that the user has been charged by the wallet side, and the commission charge is calculated by the wallet side. However, there may be another service request of the user, which happens to be allocated to the service server B of the old version profile, and the user is not grayed to the wallet side in the profile of the service server B, that is, it is determined that the user should adopt the service side charging. Therefore, problems easily occur, once a certain user switches from the old version charging scheme to the new version charging scheme at a certain time, the new version charging scheme is adopted subsequently, the first request is switched to the new version charging scheme, the second request is used for charging the old version, and therefore the data stored by the service side and the wallet side are inconsistent and data disorder occurs.
However, the service data processing method of the present application can avoid the above problems. When the target service server receives the target service request, the target service server compares the state information of the local program logic layer with the state information of the reference program logic layer, takes the updated state information of the program logic layer as the state information of the target program logic layer, and processes the target service request through the target program logic layer corresponding to the state information of the target program logic layer. When a service request 1 initiated by a user is firstly distributed to a service server A with a newer configuration file version, the user is judged to be charged by the wallet side in gray scale, and the commission charge is calculated and charged by the wallet side. The target docking server stores the state information of the program logic layer corresponding to the user in time, namely the state from the business side charging gray level to the wallet side charging and the corresponding version information. When the next service request 2 of the service request 1 is distributed to the service server B of the old version configuration file, the user can still be judged to be charged to the wallet side through the local program logic layer state information and the reference program logic layer state information, and the commission charge is still calculated by the wallet side. Therefore, when a certain user initiates a service request at a certain time, if the state information of the program logic layer is changed, all subsequent service requests are uniformly subject to the latest state information of the target program logic layer after the change.
In the service data processing method, the target service request is acquired; the target service request carries a target user identifier, local program logic layer state information corresponding to the target user identifier is obtained locally, reference program logic layer state information corresponding to the target user identifier is obtained from a target docking server, the reference program logic layer state information is updated according to a processing program logic layer corresponding to an adjacent historical service request, the adjacent historical service request carries the target user identifier, the target program logic layer state information is obtained through screening based on the update states in the local program logic layer state information and the reference program logic layer state information, and the target service request is processed through the target program logic layer corresponding to the target program logic layer state information to obtain a service processing result. Thus, each time the target service server obtains a service request, the target service server queries the local and target docking servers for a target program logic layer for processing the current service request. The method determines the state information of the logic layer of the target program through the comparison of the state information of the logic layer of the local program and the state information of the logic layer of the reference program, can ensure that once a certain user initiates a service request at a certain time, if the state information of the logic layer of the program is changed, all subsequent service requests are uniformly subject to the latest state information of the logic layer of the target program after the change, avoid the problem that the logic layer of the program for processing the service request is continuously changed due to the fact that a configuration file is published among a plurality of service servers in a sequential order, and ensure the orderliness of service processing.
In one embodiment, as shown in fig. 4, obtaining the local program logic layer state information corresponding to the target user identifier locally includes:
step S402, acquiring a program logic layer state information configuration file locally; the program logic layer state information configuration file comprises user identification configuration information corresponding to various program logic layer states respectively.
The program logic layer state information configuration file is a configuration file for configuring the program logic layer state information. The program logic layer state information configuration file comprises user identification configuration information corresponding to various program logic layer states respectively. The program logic layer states include a state from the dedicated program logic layer grayscale to the general program logic layer and a state from the general program logic layer back to the dedicated program logic layer. The user identification configuration information is used for configuring a user identification cluster corresponding to any program logic layer state. For example, the user identification corresponding to the state from the dedicated program logic layer grayscale to the generic program logic layer is the user identification including the "A" character. The user identification configuration information supports configuration through flexible and complex rules, such as prefix and prefix matching, regular expression matching and the like. Because the amount of service users is large, the storage pressure of the target service server can be effectively reduced by configuring the program logic layer state information corresponding to the users through rules.
Step S404, determining the local program logic layer state corresponding to the target user identification based on the matching result of the target user identification and each user identification configuration information.
Step S406, obtaining the local program logic layer state information based on the current version of the program logic layer state information configuration file and the local program logic layer state.
Specifically, the target service server locally stores a program logic layer state information configuration file. After the target service server obtains the target service request carrying the target user identifier, the target service server may locally obtain a program logic layer state information configuration file, match the target user identifier with each user identifier configuration information, and use the program logic layer state corresponding to the user identifier configuration information successfully matched as the local program logic layer state corresponding to the target user identifier. Further, the configuration file can be updated, and in order to distinguish different configuration files, a version mechanism is introduced. When the configuration file is changed, the version of the configuration file needs to be modified correspondingly. The version of the configuration file may be represented by a string of at least one character selected from the group consisting of letters, numbers, and symbols. For example, when the configuration file is changed, the number of the version number is increased. The target business server may obtain local program logic layer state information based on the current version of the program logic layer state information configuration file and the local program logic layer state.
In this embodiment, the target service server locally stores the program logic layer state information corresponding to each user in the form of a program logic layer state information configuration file, which can reduce the storage pressure of the target service server.
In one embodiment, as shown in fig. 5, the obtaining of the reference program logic layer state information corresponding to the target user identifier from the target docking server includes:
step S502, mapping the target user identification to obtain the target user mapping identification.
Step S504, based on the matching result of the target user mapping identification and the user mapping identification range corresponding to the plurality of candidate docking servers, a target docking server is determined from each candidate docking server.
Specifically, in order to reduce the storage pressure of the docking server, a plurality of candidate docking servers may be provided, and different candidate docking servers store program logic layer state information corresponding to different user identifiers. Therefore, after the target service server receives the target service request, the target service server needs to determine the target docking server from the multiple candidate docking servers, and then obtain the reference program logic layer state information corresponding to the target user identifier from the target docking server. Different user mapping identifier ranges can be allocated to each candidate docking server in advance, and when a user mapping identifier obtained by mapping the user identifier falls into a certain user mapping identifier range, the program logic layer state information corresponding to the user identifier needs to be stored in the candidate docking server corresponding to the user mapping identifier range. Therefore, after the target service server obtains the target service request carrying the target user identifier, the target user identifier can be mapped to obtain the target user mapping identifier, and the target user mapping identifier is matched with the user mapping identifier ranges respectively corresponding to the candidate docking servers. When the target user identifier falls into a certain user mapping identifier range, the reference program logic layer state information corresponding to the target user identifier is stored in the candidate docking server corresponding to the user mapping identifier range, and the candidate docking server can be determined as the target docking server. The mapping process for the target user identifier may be hash calculation, normalization process, or the like for the target user identifier.
Step S506, based on the matching result between the target user identifier and each candidate user identifier in the target docking server, determining the reference program logic layer state information from the candidate program logic layer state information corresponding to each candidate user identifier in the target docking server.
Specifically, each candidate docking server stores candidate program logic layer state information corresponding to a plurality of candidate user identifiers, and the candidate docking server stores corresponding program logic layer state information in units of user identifiers. After the target docking server is determined, the target service server may match the target user identifier with each candidate user identifier in the target docking server, and use the candidate program logic layer state information corresponding to the candidate user identifier that is successfully matched as the reference program logic layer state information corresponding to the target user identifier, that is, search the reference program logic layer state information corresponding to the target user identifier in the target docking server.
In this embodiment, the state information of the program logic layer corresponding to a large number of users is stored in a distributed manner, which can reduce the storage pressure of the docking server and improve the security of data.
In one embodiment, the update status includes a status version, and the filtering to obtain the target program logic layer status information based on the update status in the local program logic layer status information and the reference program logic layer status information includes: and screening out the program logic layer state information corresponding to the latest state version from the local program logic layer state information and the reference program logic layer state information as the target program logic layer state information.
Specifically, because a version mechanism is introduced into the configuration file, the version of the configuration file may be used as the state version of the program logic layer state corresponding to each piece of user identification configuration information in the configuration file, and the state version may be used as the update state of the program logic layer state information. Therefore, the step of screening the target program logic layer state information based on the updated state in the local program logic layer state information and the reference program logic layer state information may specifically be to screen out the program logic layer state information corresponding to the latest state version from the local program logic layer state information and the reference program logic layer state information as the target program logic layer state information. For example, the version number of the configuration file of the target service server is 3, and the local program logic layer state corresponding to the target user identifier is determined to be the state from the special program logic layer gray scale to the general program logic layer from the configuration file, so that the local program logic layer state information includes the version number 3 and the state from the special program logic layer gray scale to the general program logic layer. The reference program logic layer state information includes a version number 2 and a state of rollback from the general program logic layer to the special program logic layer. According to the comparison of the version numbers, the state version update of the local program logic layer state information can be determined, so that the local program logic layer state information is used as the target program logic layer state information, and the target program logic layer corresponding to the target program logic layer state information is the general program logic layer.
In this embodiment, the state information of the logic layer of the target program can be quickly determined based on the comparison result of the state versions.
In one embodiment, the method further comprises: when the state version of the local program logic layer state information is updated, generating a program logic layer state information updating request according to the target user identification and the local program logic layer state information; and sending the program logic layer state information updating request to the target docking server so that the target docking server updates the reference program logic layer state information into the local program logic layer state information according to the program logic layer state information updating request.
Wherein the program logic layer state information update request is for requesting to update the program logic layer state information on the target docking server.
Specifically, when comparing the local program logic layer state information with the reference program logic layer state information, if the state version of the local program logic layer state information is updated, the updated program logic layer state information needs to be updated to the target docking server synchronously, so that the target docking server can store the latest or newer program logic layer state information all the time. Therefore, when the state version of the local program logic layer state information is updated, the target service server may generate a program logic layer state information update request according to the target user identifier and the local program logic layer state information, and send the program logic layer state information update request to the target docking server. And after the target docking server receives the program logic layer state information updating request, the target docking server updates the reference program logic layer state information corresponding to the target user identification into the local program logic layer state information.
In this embodiment, when the state version of the local program logic layer state information is updated, the reference program logic layer state information on the target docking server is updated in time, so that it can be ensured that the latest program logic layer state information is always used as the target program logic layer state information when a new service request is processed, thereby ensuring the ordering of data processing.
In one embodiment, processing the target service request through a target program logic layer corresponding to the target program logic layer state information to obtain a service processing result includes: inquiring the request state of the historical service request corresponding to the target user identification; when the request state of at least one historical service request is unfinished, processing a target service request through a processing program logic layer to obtain a service processing result; and when the request states of all historical service requests are finished, processing the target service requests through the target program logic layer to obtain service processing results.
Wherein, the historical service request refers to a service request triggered before the target service request. The request status of the historical service request includes completed and not completed.
Specifically, the target service server may query a request status of the historical service request corresponding to the target user identifier. When the request state of at least one historical service request is incomplete, in order to prevent the data disorder caused by the fact that the incomplete historical service request and the target service request are processed at different program logic layers at the same time, no matter which program logic layer the target program logic layer corresponding to the state information of the target program logic layer is, the target service request is processed through the processing program logic layer, and a service processing result is obtained. That is, when the request status of at least one historical service request is incomplete, the switching of the program logic layer is not allowed. When the request states of all historical service requests are finished, the target service requests can be processed through the target program logic layer at the moment, and service processing results are obtained.
For example, in the P2P social payment scenario, historical service requests initiated by users are all processed on the service side. However, when the user initiates a new service request, the query is that it should be grayed from the service side to the wallet side. If there is some fund in transit, for example, the red packet which is not received by the receiver in the overdue time limit of the red packet, in order to avoid the inconsistency of the exemption limit of the monthly exemption renewal fee of the user recorded by the subsequent service side and the wallet side, the service request is not allowed to go from the service side gray level to the wallet side, the service request is still processed by the service side, and the commission charge is calculated by using the service side charging scheme.
In this embodiment, only when the request states of all the historical service requests are completed, the target service request is processed through the target program logic layer to obtain a service processing result, so that the accuracy of the service processing result can be effectively guaranteed.
In one embodiment, when the target program logic layer is a general program logic layer, processing the target service request through the target program logic layer corresponding to the state information of the target program logic layer to obtain a service processing result, including: acquiring a general service processing logic from a general program logic layer; and processing the target service request based on the general service processing logic to obtain a service processing result.
Specifically, the general program logic layer mainly comprises general and basic program logic codes among a plurality of services. When processing the service request, if the target program logic layer is a generic program logic layer, the target service server may obtain a generic service processing logic from the generic program logic layer, and process the target service request based on the generic service processing logic to obtain a service processing result.
In one embodiment, the method for processing the target service request by the target program logic layer corresponding to the state information of the target program logic layer includes: acquiring a target service processing logic corresponding to the target service identifier from the special program logic layer; and processing the target service request based on the target service processing logic to obtain a service processing result.
Specifically, the dedicated program logic layer mainly includes program logic codes dedicated to each service, and program logic codes related to service logic and service flow. The special program logic layer stores candidate service processing logics corresponding to a plurality of candidate service identifications respectively. When processing a service request, if the target program logic layer is a dedicated program logic layer, the target service server may obtain, from the dedicated program logic layer, a target service processing logic corresponding to a target service identifier carried in the target service request, and process the target service request based on the target service processing logic to obtain a service processing result.
For example, in the P2P social payment scenario, the calculation of the commission is typically done on the business side, completely transparent to the wallet side, which is completely unaware of the commission. Developers currently develop new program logic codes, and move the logic of calculating and charging the commission fees from the business side to the wallet side for completion, so that the logic of charging the commission fees is not realized by each business, but is moved to the wallet side for unified completion. The service side no longer needs to insert a sequence of handling fee related logics separately in each service. However, the new program logic code needs to be subjected to a small-scale promotion test to be widely promoted and applied. Therefore, the current commission charging can be realized on the service side and also on the wallet side. And when the target program logic layer is a general program logic layer, namely the wallet side, processing the target service request through general service processing logic in the wallet side to obtain a service processing result. And when the target program logic layer is a special program logic layer, namely a service side, the target service request is processed through the target service processing logic of the specific service in the service side to obtain a service processing result.
In one embodiment, the current service processing logic includes a general service processing logic or a target service processing logic, and the processing of the target service request based on the current service processing logic to obtain the service processing result includes: when the processing program logic layer is not consistent with the target program logic layer, acquiring historical service processing statistical information corresponding to the target user identification from the processing program logic layer; and sending the historical service processing statistical information to a target program logic layer so that the target program logic layer processes the target service request based on the historical service processing statistical information and the current service processing logic to obtain a service processing result.
The historical service processing statistical information is statistical information obtained by counting the service information of the historical service request.
Specifically, the target program logic layer may comprehensively consider historical business processing statistics when processing business requests. Because different program logic layers are isolated during data processing, when the processing program logic layer is not consistent with the target program logic layer, that is, when the processing target service request is different from the program logic layer corresponding to the previous historical service request, the target service server can acquire the historical service processing statistical information corresponding to the target user identifier from the processing program logic layer and send the historical service processing statistical information to the target program logic layer. The target service server can process the target service request based on the historical service processing statistical information and the current service processing logic in the target program logic layer to obtain an accurate service processing result. Furthermore, historical business processing statistical information can be updated based on the business processing result. Correspondingly, when the processing program logic layer is consistent with the target program logic layer, the target service server can directly acquire the historical service processing statistical information corresponding to the target user identifier in the target program logic layer, and process the target service request based on the historical service processing statistical information and the current service processing logic to obtain an accurate service processing result.
In this embodiment, when the processing program logic layer is not consistent with the target program logic layer, the historical service processing statistical information corresponding to the target user identifier is obtained from the processing program logic layer, and the historical service processing statistical information is sent to the target program logic layer, so that the target program logic layer processes the target service request based on the historical service processing statistical information and the current service processing logic to obtain a service processing result. Therefore, the accuracy of the service processing result can be guaranteed.
In one embodiment, sending the historical service processing statistics information to the target processing layer, so that the target processing layer processes the target service request based on the historical service processing statistics information and the current service processing logic to obtain a service processing result, includes: acquiring target service information from the target service request; obtaining target service processing statistical information based on the historical service processing statistical information and the target service information; acquiring standard service processing statistical information, and determining reference service information based on the standard service processing statistical information and the target service processing statistical information; and obtaining a service processing result based on the target service information and the reference service information.
The target service information refers to the request content of the target service request. For example, in a P2P social payment scenario, when the target service request is a red-envelope service request, the target service information may be a share of the virtual resource requested to be placed in the red envelope. When the target service request is a P2P transfer service request, the target service information may be a virtual resource share that requests transfer to the recipient. The target service processing statistical information is statistical information obtained by counting the service information of the historical service request and the target service request. The standard service processing statistical information refers to a preset service information limit which can be consumed at will. The reference association information refers to additionally generated service information.
Specifically, when a service request is processed each time, the service information may be counted to obtain service processing statistical information, that is, the consumed service information amount may be counted to obtain service processing statistical information. When the target service request is processed, that is, when the current service request is processed, the target service server may obtain the target service information from the target service request, and count the historical service processing statistical information and the target service information to obtain the target service processing statistical information. Furthermore, the target service server may obtain the standard service processing statistical information, compare the standard service processing statistical information with the target service processing statistical information, and determine service processing related information according to the comparison result. And when the target service processing statistical information is smaller than the standard service processing statistical information, the standard service processing statistical information is not completely consumed, and the reference service information is absent. When the historical service processing statistical information is greater than the standard service processing statistical information, indicating that the standard service processing statistical information is completely consumed in the historical time, the reference service information can be calculated based on the target service information. Specifically, the target service information may be used as service association information, a service processing factor corresponding to the service association information is obtained, and the reference service information is obtained based on the service association information and the service processing factor. When the historical service processing statistical information is less than the standard service processing statistical information but the target service processing statistical information is greater than the standard service processing statistical information, it is indicated that the standard service processing statistical information is completely consumed at the current time, and at this time, the reference service information may be calculated based on the target service processing statistical information and the standard service processing statistical information. Specifically, the difference between the target service processing statistical information and the standard service processing statistical information is used as service related information, a service processing factor corresponding to the service related information is obtained, and reference service information is obtained based on the service related information and the service processing factor. And finally, obtaining a service processing result based on the target service information and the reference service information. The service related information refers to a part of service information which needs to be consumed additionally in the target service information. The service processing factor refers to a consumption factor and a consumption weight corresponding to the service associated information.
For example, in the P2P social payment scenario, the target service request is a red envelope service request. The share of the virtual resource that has been transferred in the current month, i.e., the virtual resource exemption line that has been consumed in the current month, can be obtained based on historical service requests. The current share of the virtual resources to be transferred can be obtained from the target service request, the share of the virtual resources to be transferred and the corresponding consumption factor of the part of the current share of the virtual resources to be transferred, which needs to generate additional virtual resource segmentation, can be calculated based on the current share of the virtual resources to be transferred, the share of the virtual resources transferred in the current month and the exemptable limit of the virtual resources in the current month, and the current share of the additional virtual resources to be transferred is obtained through weighting calculation. And further, a service processing result of the red packet service request can be obtained based on the current to-be-transferred virtual resource share and the current additional transferred virtual resource share.
In the embodiment, target service information is acquired from a target service request, target service processing statistical information is acquired based on historical service processing statistical information and the target service information, standard service processing statistical information is acquired, and reference service information is determined based on the standard service processing statistical information and the target service processing statistical information; and obtaining a service processing result based on the target service information and the reference service information. Thus, an accurate service processing result can be calculated.
In one embodiment, as shown in FIG. 6, a business data processing system is provided that includes a target business server 602 and a target docking server 604.
And the target service server is used for acquiring a target service request, wherein the target service request carries a target user identifier, locally acquiring local program logic layer state information corresponding to the target user identifier, generating a program logic layer state information query request corresponding to the target service request, and sending the program logic layer state information query request to the target docking server.
The target docking server is used for locally acquiring the reference program logic layer state information corresponding to the target user identification according to the program logic layer state information query request and returning the reference program logic layer state information to the processing server; and updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification.
The target service server is further configured to obtain target program logic layer state information by screening based on the update state in the local program logic layer state information and the reference program logic layer state information, and process the target service request through a target program logic layer corresponding to the target program logic layer state information to obtain a service processing result.
In one embodiment, the system comprises a plurality of candidate service servers, the target server serves each candidate service server, and each service request carrying the target user identifier is randomly allocated to any one of the candidate service servers for processing.
Referring to FIG. 7A, a business data processing system includes terminals, a cluster of candidate business servers, and a centralized target docking server. The terminal may be at least one. The cluster of candidate business servers includes a plurality of candidate business servers. And the target service request sent by the terminal is randomly distributed to any one candidate service server in the candidate service server cluster for processing. The candidate service server which acquires the target service request is used as a target service server, the target service server can locally acquire local program logic layer state information corresponding to a target user identifier, reference program logic layer state information corresponding to the target user identifier is acquired from a centralized target docking server, the target program logic layer state information is obtained by screening based on the update states in the local program logic layer state information and the reference program logic layer state information, and the target service request is processed through the target program logic layer corresponding to the target program logic layer state information to obtain a service processing result.
Referring to fig. 7B, the service data processing system includes a terminal, a candidate service server cluster, and a candidate docking server cluster. The terminal may be at least one. The candidate business server cluster comprises a plurality of candidate business servers, and the candidate docking server cluster comprises a plurality of candidate docking servers. And the target service request sent by the terminal is randomly distributed to any one candidate service server in the candidate service server cluster for processing. And taking the candidate service server which acquires the target service request as a target service server, wherein the target service server can locally acquire the local program logic layer state information corresponding to the target user identification. The target service server may determine a target docking server corresponding to the target user identifier from the candidate docking server cluster. And acquiring reference program logic layer state information corresponding to the target user identification from the target docking server, screening to obtain target program logic layer state information based on the local program logic layer state information and the update state in the reference program logic layer state information, and processing the target service request through the target program logic layer corresponding to the target program logic layer state information to obtain a service processing result.
The specific data processing process after the target service server receives the target service request may refer to the methods described in the embodiments of the service data processing method, and details are not described here.
In the service data processing system, the target service server acquires the target service request, the target service request carries the target user identifier, local program logic layer state information corresponding to the target user identifier is locally acquired, a program logic layer state information query request corresponding to the target service request is generated, and the program logic layer state information query request is sent to the target docking server. The target docking server locally acquires reference program logic layer state information corresponding to the target user identification according to the program logic layer state information query request, and returns the reference program logic layer state information to the processing server; and updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification. And the target service server screens the state information of the logic layer of the target program based on the updated state in the state information of the logic layer of the local program and the state information of the logic layer of the reference program to obtain the state information of the logic layer of the target program, and processes the target service request through the logic layer of the target program corresponding to the state information of the logic layer of the target program to obtain a service processing result. Thus, each time the target service server obtains a service request, the target service server queries the local and target docking servers for a target program logic layer for processing the current service request. The state information of the logic layer of the target program is determined by comparing the state information of the logic layer of the local program with the state information of the logic layer of the reference program, so that once a certain user initiates a service request at a certain time, if the state information of the logic layer of the program is changed, all subsequent service requests are uniformly subject to the latest state information of the logic layer of the target program after the change, and the problem that the logic layer of the program for processing the service request is continuously changed due to the fact that a configuration file is published among a plurality of service servers and has a sequence is solved.
The application also provides an application scenario applying the service data processing method. Specifically, the application of the service data processing method in the application scenario is as follows:
in the P2P social payment application scenario, the servers for business processing can be divided into a wallet side and a business side on the internal software architecture, i.e., a generic program logic layer and a specific program logic layer. The wallet side focuses on some basic logic common to the implementation of various services, such as account transfers, cash withdrawals, refunds, etc. The service side focuses on the logic on some service flows at the application level, which is specific to each specific service. For example, the specific logic of red envelope and transfer is different, and they are different from the business logic of face-to-face collection and AA collection.
Schemes for charging commission fees for social payment credit cards include business-side billing and wallet-side billing. The service side charging means that the calculation of the handling fee is realized by each specific service (such as red envelope, transfer account, face-to-face collection and the like), the wallet side charging means that the calculation of the handling fee is uniformly completed by the wallet side, and each service of the service side does not need to separately insert a series of logic related to the handling fee. The specific logic of the charging of the handling fee is to modify the amount of the order price to be the original amount plus the handling fee, and the additional handling fee needs to be calculated. In addition, the transfer of the commission to the commission revenue account may be separately charged by the business side or the wallet side. In the traditional method, the business side is mainly adopted for charging, the wallet side is completely transparent, and the wallet side does not sense the existence of the handling fee at all. At present, developers firstly develop wallet side charging, in order to ensure stable and accurate operation of the wallet side charging, a gray level service is designed on a service server, and a small number of users in a controllable range are controlled to adopt the wallet side charging each time. On the basis of not influencing and not using the existing service and the current network user in operation, online smooth gray level switching between the charging at the wallet side and the charging at the service side by taking a single user as a dimension is supported, and the online smooth gray level switching comprises the steps of supporting the charging upgrade of the commission fee (from the charging gray level at the service side to the charging at the wallet side) and the rollback of the charging scheme of the commission fee (from the charging rollback at the wallet side to the charging at the service side) of the single user in any sequence. Whether the wallet side charging or the service side charging is imperceptible to the user, completely transparent to the user, and implemented by the service server.
Referring to fig. 8, fig. 8 is a timing diagram of a service data processing method.
1. And acquiring a target service request, wherein the target service request carries a target user identifier.
Specifically, the target service request sent by the terminal may be obtained by a grayscale service in the target service server.
2. And locally acquiring the state information of the logic layer of the local program corresponding to the target user identification.
The target service server may obtain the local program logic layer state information from the local configuration file. The profile may comprise a grey white list from the business side charging grey scale to the wallet side charging, i.e. the profile is configured with subscriber identity configuration information from the business side charging grey scale to the wallet side charging. The configuration file supports a variety of matching rules, such as suffix matching, regular expression matching, and the like. The local program logic layer state information comprises a local program logic layer state and a version number corresponding to the configuration file.
3. And querying the state information of the logic layer of the reference program corresponding to the target user identification.
Specifically, the docking service in the target service server may send a program logic layer state information query request to the target docking server. And the target docking server locally acquires the reference program logic layer state information corresponding to the target user identification according to the program logic layer state information query request and returns the reference program logic layer state information to the target service server. The reference program logic layer state information comprises a reference program logic layer state and a corresponding version number.
4. And screening the state information of the logic layer of the target program from the state information of the logic layer of the local program and the state information of the logic layer of the reference program.
Specifically, the state information of the logic layer of the target program can be screened out by the gray level service in the target business server. Once the configuration file released by the developer is changed, the version number of the configuration file needs to be increased. Therefore, the program logic layer state information with a larger version number value can be screened from the local program logic layer state information and the reference program logic layer state information as the target program logic layer state information. And when the value of the version number of the local program logic layer state information is smaller, ignoring the local configuration and taking the reference program logic layer state information as the target program logic layer state information. And when the value of the version number of the local program logic layer state information is larger, taking the local program logic layer state information as the target program logic layer state information.
5. And inquiring the funds in transit.
Whether the in-transit funds exist can be specifically inquired through an in-transit fund inquiry service or a corresponding in-transit fund inquiry function. When the request status of the historical service request is incomplete, it may be determined that there is currently funds in transit. If the user currently has funds in transit (which are common in red envelope and P2P transfers, such as red envelope and transfers that are not received by the recipient within the expiration time of the red envelope and transfers), the user is not allowed to greyscale from the business side to the wallet side and back from the wallet side to the business side in order to avoid inconsistent exempt credits recorded by the business side and the wallet side for the user's monthly exemptions. The in-transit funds inquiry service may send the in-transit funds inquiry results to a grayscale service.
6. Processing target service requests
The target service request may specifically be processed by a service processing service. The gray scale service may send the target program logic layer state information and in-transit fund query results to a business processing service. Further, when there is an in-transit fund, the target service request is processed through the processing program logic layer corresponding to the adjacent historical service request. And when no in-transit fund exists, processing the target service request through the target program logic layer corresponding to the state information of the target program logic layer.
For example, the handler logic layer corresponding to the adjacent historical service request is the service side. And the object program logic layer corresponding to the object program logic layer state information is the wallet side. When there is an in-transit fund, the target service request is still processed through the service side. When there is no in-transit funds, then the target service request is processed through the wallet side.
7. And returning a service processing result.
The business processing service of the target business server can return a business processing result to the terminal, for example, the amount of the price marked by the order is modified to be the original amount plus the commission charge. Furthermore, besides accessing the gray level service to obtain the state information of the target program logic layer, each business itself needs to be used in the business process logic in the whole life cycle of the business payment order (from ordering to completing collection and payment, or refund), and stores the state information of the target program logic layer of the user by the business itself, and executes different processing logics (such as commission charge billing, commission charge, exemption credit amount verification of the commission charge in the month, and the like) in the whole life cycle of the business order according to the state information of the target program logic layer corresponding to the target program logic layer.
For example, the target program logical layer corresponding to the target program logical layer state information is the wallet side. Then the calculation of the commission may be done at the wallet side. However, in the whole process from the sending to the receiving of the red packet, the red packet needs to be processed according to the red packet service flow processing logic of the service side. For example, if the recipient does not receive the red envelope within the expiration time of the red envelope, the money for the red envelope is returned to the sender's electronic account.
8. When the local program logic layer state information is updated, the reference program logic layer state information on the target docking server is updated.
When the value of the version number of the local program logic layer state information is larger, the reference program logic layer state information in the target docking server needs to be refreshed synchronously to be the current latest version. Therefore, the target business server can generate a program logic layer state information updating request and send the program logic layer state information updating request to the target docking server through the docking service. The program logic layer state information updating request carries a target user identifier and corresponding local program logic layer state information. And after receiving the program logic layer state information updating request, the target docking server updates the reference program logic layer state information corresponding to the target user identification into the local program logic layer state information.
It can be understood that the design scheme of the grayscale service can be easily migrated to other wallet-side application services, such as cross-border remittance, life payment, telephone fee recharging and the like, at a very low cost, and the robustness and maintainability of the wallet service can be effectively ensured.
In this embodiment, it is ensured that, when a certain user initiates any service request (for example, red envelope, transfer, face-to-face collection, AA collection) at a certain time, if the program logic layer state information is changed (whether from the business side gray scale to the wallet side or from the wallet side back to the business side), all subsequent service requests are not affected by the order in which configuration files are issued among a plurality of service servers, based on the latest program logic layer state information after the change. The service data processing method of the embodiment supports online smooth gray scale switching of the P2P social payment service handling fee charging scheme, can support continuous service with granularity as fine as a single user, and does not affect smooth upgrade and rollback between new and old charging schemes under the condition of current network user experience.
The application also provides an application scenario applying the service data processing method. Specifically, the application of the service data processing method in the application scenario is as follows:
in the context of rights management, a server for business processing may be divided into a generic program logic layer and a dedicated program logic layer on an internal software architecture. The general program logic layer focuses on some basic logic common to implementing various rights services, such as rights lookup. The application-specific logic layer focuses on the logic specific to each particular entitlement service, on some of the service flows at the application level. For example, the specific rights implementation logic for having the reference rights and having the download rights is different.
The permission modification schemes include a general program logic layer modification scheme and a special program logic layer modification scheme. The modification of the special program logic layer means that the modification of the authority is realized by each specific authority service, the modification of the general program logic layer means that the modification of the authority is uniformly completed by the general program logic layer, and each authority service of the special program logic layer does not need to be independently inserted into a series of logics related to the authority modification. The modification of the authority can specifically be adding the data uploading authority for the user and deleting the data modification authority for the user. The gray scale service is designed on the service server, and a few users in a controllable range are controlled at a time to adopt one permission modification scheme. On the basis of not influencing and not using the existing service and the existing network users in operation, the online smooth gray level switching between the general program logic layer modification scheme and the special program logic layer modification scheme which take a single user as a dimension is supported, and the method comprises the steps of supporting the multiple random times of the single user, upgrading the authority modification scheme in random sequence (from the gray level of the special program logic layer modification scheme to the general program logic layer modification scheme) and rolling back the authority modification scheme (from the general program logic layer modification scheme to the special program logic layer modification scheme).
And the terminal sends a target permission modification request which carries a target user identifier corresponding to the user sending the request. And after receiving the target permission modification request, the target service server locally acquires the local program logic layer state information corresponding to the target user identification, and acquires the reference program logic layer state information corresponding to the target user identification from the target docking server. And when the state information of the local program logic layer is updated, processing the target permission modification request through the program logic layer corresponding to the state information of the local program logic layer. And the state information of the local program logic layer is synchronously updated to the target docking server, so that the latest program logic layer state information is ensured to be stored in the target docking server at any time. And when the state information of the reference program logic layer is updated, ignoring the state information of the local program logic layer, and processing the target permission modification request through the program logic layer corresponding to the state information of the reference program logic layer. By the design, when a user initiates an authority modification request of any authority service at a certain time, if the authority modification scheme corresponding to the user is changed (whether the gray level of the special program logic layer modification scheme is changed to the general program logic layer modification scheme or the general program logic layer modification scheme is rolled back to the special program logic layer modification scheme), the logic of the authority modification is uniformly based on the latest authority modification scheme after the change for all the subsequent authority modification requests, the influence of the order of issuing the configuration file between a plurality of service servers which possibly exists is avoided, and the orderliness of service processing is guaranteed.
It should be understood that although the various steps in the flow charts of fig. 2-8 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-8 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 9, a service data processing apparatus is provided, where the apparatus may adopt a software module or a hardware module, or a combination of the two modules, as a part of a computer device, and the apparatus specifically includes: a service request obtaining module 902, a program logic layer state information obtaining module 904, an object program logic layer state information determining module 906 and a service processing module 908, wherein:
a service request obtaining module 902, configured to obtain a target service request; the target service request carries a target user identifier.
A program logic layer state information obtaining module 904, configured to locally obtain local program logic layer state information corresponding to the target user identifier, and obtain reference program logic layer state information corresponding to the target user identifier from the target docking server; and updating the state information of the reference program logic layer according to the processing program logic layer corresponding to the adjacent historical service request, wherein the adjacent historical service request carries the target user identification.
And the target program logic layer state information determining module 906 is configured to obtain target program logic layer state information by screening based on the update states in the local program logic layer state information and the reference program logic layer state information.
The service processing module 908 is configured to process the target service request through the target program logic layer corresponding to the target program logic layer state information, so as to obtain a service processing result.
In one embodiment, the target docking server serves a plurality of candidate service servers, and each service request carrying the target user identifier is randomly allocated to any one of the candidate service servers for processing.
In one embodiment, the program logic layer state information acquisition module is further configured to locally acquire a program logic layer state information configuration file; the program logic layer state information configuration file comprises user identification configuration information corresponding to various program logic layer states respectively; determining the state of a local program logic layer corresponding to the target user identification based on the matching result of the target user identification and the configuration information of each user identification; the local program logic layer state information is obtained based on the current version of the program logic layer state information configuration file and the local program logic layer state.
In one embodiment, the program logic layer state information obtaining module is further configured to perform mapping processing on the target user identifier to obtain a target user mapping identifier; determining a target docking server from each candidate docking server based on a matching result of the target user mapping identifier and a user mapping identifier range corresponding to a plurality of candidate docking servers; and determining the state information of the logic layer of the reference program from the state information of the logic layer of the candidate program corresponding to each candidate user identifier in the target docking server based on the matching result of the target user identifier and each candidate user identifier in the target docking server.
In one embodiment, the update status includes a status version, and the target program logic layer status information determining module is further configured to filter, from the local program logic layer status information and the reference program logic layer status information, program logic layer status information corresponding to a latest status version as target program logic layer status information.
In one embodiment, as shown in fig. 10, the apparatus further comprises:
a program logic layer state information updating module 910, configured to generate a program logic layer state information updating request according to the target user identifier and the local program logic layer state information when the state version of the local program logic layer state information is updated; and sending the program logic layer state information updating request to the target docking server so that the target docking server updates the reference program logic layer state information into the local program logic layer state information according to the program logic layer state information updating request.
In one embodiment, the service processing module is further configured to query a request status of a historical service request corresponding to the target user identifier; when the request state of at least one historical service request is unfinished, processing a target service request through a processing program logic layer to obtain a service processing result; and when the request states of all historical service requests are finished, processing the target service requests through the target program logic layer to obtain service processing results.
In one embodiment, when the target program logic layer is a general program logic layer, the service processing module is further configured to obtain a general service processing logic from the general program logic layer; and processing the target service request based on the general service processing logic to obtain a service processing result.
In one embodiment, the target service request carries a target service identifier, when the target program logic layer is a dedicated program logic layer, the dedicated program logic layer stores candidate service processing logics corresponding to a plurality of candidate service identifiers, respectively, and the service processing module is further configured to obtain the target service processing logic corresponding to the target service identifier from the dedicated program logic layer; and processing the target service request based on the target service processing logic to obtain the service processing result.
In one embodiment, the current service processing logic includes a general service processing logic or a target service processing logic, and the service processing module is further configured to obtain historical service processing statistical information corresponding to the target user identifier from the processing program logic layer when the processing program logic layer is inconsistent with the target program logic layer; and sending the historical service processing statistical information to a target program logic layer so that the target program logic layer processes the target service request based on the historical service processing statistical information and the current service processing logic to obtain a service processing result.
In one embodiment, the service processing module is further configured to obtain target service information from the target service request; obtaining target service processing statistical information based on the historical service processing statistical information and the target service information; acquiring standard service processing statistical information, and determining reference service information based on the standard service processing statistical information and the target service processing statistical information; and obtaining a service processing result based on the target service information and the reference service information.
For specific limitations of the service data processing apparatus, reference may be made to the above limitations of the service data processing method, which is not described herein again. The modules in the business data processing device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 11. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer equipment is used for storing data such as program logic layer state information, program logic layer state configuration files, service processing results and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a business data processing method.
Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.
In an embodiment, a computer-readable storage medium is provided, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer-readable storage medium. The computer instructions are read by a processor of a computer device from a computer-readable storage medium, and the computer instructions are executed by the processor to cause the computer device to perform the steps in the above-mentioned method embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (25)

1. A method for processing service data, the method comprising:
acquiring a target service request; the target service request carries a target user identifier;
locally acquiring local program logic layer state information corresponding to the target user identification, and acquiring reference program logic layer state information corresponding to the target user identification from a target docking server; the state information of the reference program logic layer is updated according to a processing program logic layer corresponding to an adjacent historical service request, the adjacent historical service request carries the target user identifier, and the state information of the local program logic layer is obtained based on the local program logic layer state corresponding to the target user identifier in a locally obtained program logic layer state information configuration file and the current version of the program logic layer state information configuration file;
screening to obtain target program logic layer state information based on the update state in the local program logic layer state information and the reference program logic layer state information;
and processing the target service request through the target program logic layer corresponding to the state information of the target program logic layer to obtain a service processing result.
2. The method according to claim 1, wherein the target docking server serves a plurality of candidate service servers, and each service request carrying the target user identifier is randomly allocated to any one of the candidate service servers for processing.
3. The method of claim 1, wherein the locally obtaining the local program logic layer state information corresponding to the target user identifier comprises:
acquiring a program logic layer state information configuration file locally; the program logic layer state information configuration file comprises user identification configuration information corresponding to various program logic layer states respectively;
determining the state of a local program logic layer corresponding to the target user identification based on the matching result of the target user identification and the configuration information of each user identification;
and obtaining the local program logic layer state information based on the current version of the program logic layer state information configuration file and the local program logic layer state.
4. The method of claim 1, wherein the obtaining the reference program logic layer state information corresponding to the target user identifier from the target docking server comprises:
mapping the target user identification to obtain a target user mapping identification;
determining the target docking server from each candidate docking server based on a matching result of the target user mapping identifier and a user mapping identifier range corresponding to a plurality of candidate docking servers;
and determining the reference program logic layer state information from the candidate program logic layer state information corresponding to each candidate user identifier in the target docking server based on the matching result of the target user identifier and each candidate user identifier in the target docking server.
5. The method of claim 1, wherein the update status comprises a status version, and wherein filtering target program logic layer status information based on the update status in the local program logic layer status information and the reference program logic layer status information comprises:
and screening out the program logic layer state information corresponding to the latest state version from the local program logic layer state information and the reference program logic layer state information as the target program logic layer state information.
6. The method of claim 5, further comprising:
when the state version of the local program logic layer state information is updated, generating a program logic layer state information updating request according to the target user identification and the local program logic layer state information;
and sending the program logic layer state information updating request to the target docking server so that the target docking server updates the reference program logic layer state information into the local program logic layer state information according to the program logic layer state information updating request.
7. The method according to claim 1, wherein the processing the target service request through the target program logic layer corresponding to the target program logic layer state information to obtain a service processing result includes:
inquiring the request state of the historical service request corresponding to the target user identification;
when the request state of at least one historical service request is unfinished, processing the target service request through the processing program logic layer to obtain a service processing result;
and when the request states of all historical service requests are finished, processing the target service request through the target program logic layer to obtain a service processing result.
8. The method according to claim 1, wherein when the target program logic layer is a general program logic layer, the processing the target service request through the target program logic layer corresponding to the target program logic layer state information to obtain a service processing result includes:
acquiring a general service processing logic from the general program logic layer;
and processing the target service request based on the general service processing logic to obtain the service processing result.
9. The method according to claim 1, wherein the target service request carries a target service identifier, and when the target program logic layer is a dedicated program logic layer, the dedicated program logic layer stores candidate service processing logics corresponding to a plurality of candidate service identifiers, respectively, and the target service request is processed by the target program logic layer corresponding to the target program logic layer state information to obtain a service processing result, including:
acquiring a target service processing logic corresponding to the target service identifier from the special program logic layer;
and processing the target service request based on the target service processing logic to obtain the service processing result.
10. The method according to any one of claims 8 or 9, wherein the current service processing logic includes a general service processing logic or a target service processing logic, and the obtaining the service processing result based on the processing of the target service request by the current service processing logic includes:
when the processing program logic layer is not consistent with the target program logic layer, acquiring historical service processing statistical information corresponding to the target user identification from the processing program logic layer;
and sending the historical service processing statistical information to the target program logic layer so that the target program logic layer processes the target service request based on the historical service processing statistical information and the current service processing logic to obtain the service processing result.
11. The method of claim 10, wherein the sending the historical business process statistics to the target program logic layer to enable the target program logic layer to process the target business request based on the historical business process statistics and the current business process logic to obtain the business process result comprises:
acquiring target service information from the target service request;
obtaining target service processing statistical information based on the historical service processing statistical information and the target service information;
acquiring standard service processing statistical information, and determining reference service information based on the standard service processing statistical information and the target service processing statistical information;
and obtaining the service processing result based on the target service information and the reference service information.
12. A service data processing apparatus, characterized in that the apparatus comprises:
the service request acquisition module is used for acquiring a target service request; the target service request carries a target user identifier;
a program logic layer state information acquisition module, configured to locally acquire local program logic layer state information corresponding to the target user identifier, and acquire reference program logic layer state information corresponding to the target user identifier from a target docking server; the state information of the reference program logic layer is updated according to a processing program logic layer corresponding to an adjacent historical service request, the adjacent historical service request carries the target user identifier, and the state information of the local program logic layer is obtained based on the local program logic layer state corresponding to the target user identifier in a locally obtained program logic layer state information configuration file and the current version of the program logic layer state information configuration file;
the target program logic layer state information determining module is used for screening to obtain target program logic layer state information based on the updating state in the local program logic layer state information and the reference program logic layer state information;
and the service processing module is used for processing the target service request through the target program logic layer corresponding to the state information of the target program logic layer to obtain a service processing result.
13. The apparatus according to claim 12, wherein the target docking server serves a plurality of candidate service servers, and each service request carrying the target user identifier is randomly allocated to any one of the candidate service servers for processing.
14. The apparatus of claim 12, wherein the program logic layer state information obtaining module is further configured to locally obtain a program logic layer state information configuration file, the program logic layer state information configuration file includes user identifier configuration information corresponding to a plurality of program logic layer states, the local program logic layer state corresponding to the target user identifier is determined based on a matching result of the target user identifier and each user identifier configuration information, and the local program logic layer state information is obtained based on a current version of the program logic layer state information configuration file and the local program logic layer state.
15. The apparatus of claim 12, wherein the program logic layer status information obtaining module is further configured to perform mapping processing on the target user identifier to obtain a target user mapping identifier, determine the target docking server from each candidate docking server based on a matching result between the target user mapping identifier and a user mapping identifier range corresponding to a plurality of candidate docking servers, and determine the reference program logic layer status information from the candidate program logic layer status information corresponding to each candidate user identifier in the target docking server based on a matching result between the target user identifier and each candidate user identifier in the target docking server.
16. The apparatus of claim 12, wherein the updated state comprises a state version, and wherein the target program logic layer state information determining module is further configured to filter out program logic layer state information corresponding to a latest state version from the local program logic layer state information and the reference program logic layer state information as the target program logic layer state information.
17. The apparatus of claim 16, further comprising:
and the program logic layer state information updating module is used for generating a program logic layer state information updating request according to the target user identifier and the local program logic layer state information when the state version of the local program logic layer state information is updated, and sending the program logic layer state information updating request to the target docking server so that the target docking server updates the reference program logic layer state information into the local program logic layer state information according to the program logic layer state information updating request.
18. The apparatus according to claim 12, wherein the service processing module is further configured to query a request status of a historical service request corresponding to the target subscriber identity, process the target service request through the processing program logic layer to obtain a service processing result when the request status of at least one historical service request is incomplete, and process the target service request through the target program logic layer to obtain a service processing result when the request status of all historical service requests is complete.
19. The apparatus according to claim 12, wherein when the target program logic layer is a generic program logic layer, the service processing module is further configured to obtain a generic service processing logic from the generic program logic layer, and process the target service request based on the generic service processing logic to obtain the service processing result.
20. The apparatus according to claim 12, wherein the target service request carries a target service identifier, and when the target program logic layer is a dedicated program logic layer, the dedicated program logic layer stores candidate service processing logics corresponding to a plurality of candidate service identifiers, respectively, and the service processing module is further configured to obtain the target service processing logic corresponding to the target service identifier from the dedicated program logic layer, and process the target service request based on the target service processing logic to obtain the service processing result.
21. The apparatus according to any one of claims 19 or 20, wherein the current service processing logic includes a general service processing logic or a target service processing logic, and the service processing module is further configured to, when the processing program logic layer is inconsistent with the target program logic layer, obtain historical service processing statistical information corresponding to the target user identifier from the processing program logic layer, and send the historical service processing statistical information to the target program logic layer, so that the target program logic layer processes the target service request based on the historical service processing statistical information and the current service processing logic to obtain the service processing result.
22. The apparatus of claim 21, wherein the service processing module is further configured to obtain target service information from the target service request, obtain target service processing statistics based on the historical service processing statistics and the target service information, obtain standard service processing statistics, determine reference service information based on the standard service processing statistics and the target service processing statistics, and obtain the service processing result based on the target service information and the reference service information.
23. A business data processing system, characterized in that, the system includes a target business server and a target docking server;
the target service server is used for acquiring a target service request, wherein the target service request carries a target user identifier, locally acquires local program logic layer state information corresponding to the target user identifier, generates a program logic layer state information query request corresponding to the target service request, and sends the program logic layer state information query request to the target docking server, and the local program logic layer state information is acquired based on the local program logic layer state corresponding to the target user identifier in a locally acquired program logic layer state information configuration file and the current version of the program logic layer state information configuration file;
the target docking server is used for locally acquiring the reference program logic layer state information corresponding to the target user identifier according to the program logic layer state information query request and returning the reference program logic layer state information to the target service server; the state information of the reference program logic layer is updated according to a processing program logic layer corresponding to an adjacent historical service request, and the adjacent historical service request carries the target user identification;
the target service server is further configured to obtain target program logic layer state information by screening based on the update state in the local program logic layer state information and the reference program logic layer state information, and process the target service request through a target program logic layer corresponding to the target program logic layer state information to obtain a service processing result.
24. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor realizes the steps of the method of any one of claims 1 to 11 when executing the computer program.
25. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 11.
CN202110147723.4A 2021-02-03 2021-02-03 Service data processing method, device, system, computer equipment and storage medium Active CN113032036B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110147723.4A CN113032036B (en) 2021-02-03 2021-02-03 Service data processing method, device, system, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110147723.4A CN113032036B (en) 2021-02-03 2021-02-03 Service data processing method, device, system, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113032036A CN113032036A (en) 2021-06-25
CN113032036B true CN113032036B (en) 2022-04-26

Family

ID=76459844

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110147723.4A Active CN113032036B (en) 2021-02-03 2021-02-03 Service data processing method, device, system, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113032036B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114462903B (en) * 2022-04-14 2022-07-05 四川省大数据中心 Water, electricity and gas business applying system

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651703A (en) * 2008-08-14 2010-02-17 北京摩软科技有限公司 Method and system for initiating business request to server by mobile terminal
CN109639636B (en) * 2018-11-06 2021-04-02 创新先进技术有限公司 Service data forwarding method, service data processing method, service data forwarding device, service data processing device and electronic equipment
CN110147934A (en) * 2019-04-17 2019-08-20 深圳壹账通智能科技有限公司 Service request processing method, device, computer equipment and storage medium
CN110189013A (en) * 2019-05-23 2019-08-30 上海上湖信息技术有限公司 A kind of determination method, apparatus, equipment and the medium of operation flow
CN110245194A (en) * 2019-06-24 2019-09-17 北京奇艺世纪科技有限公司 Service data updating method, server and server cluster
CN110597837B (en) * 2019-09-19 2024-05-03 腾讯科技（深圳）有限公司 Service data processing method, device, storage medium and computer equipment
CN110782240B (en) * 2019-10-12 2022-09-09 未鲲(上海)科技服务有限公司 Business data processing method and device, computer equipment and storage medium

Also Published As

Publication number Publication date
CN113032036A (en) 2021-06-25

Similar Documents

Publication Publication Date Title
US10986177B2 (en) Systems and methods of self-forking blockchain protocol
WO2020192272A1 (en) Blockchain-based transfer method and system, computing device and storage medium
US11593321B2 (en) Systems and methods of self-administered protocols on a blockchain platform
US11978056B2 (en) Systems and methods for using shared databases for managing supplemental payment sources
US20230283473A1 (en) Computer-implemented systems and methods relating to a binary blockchain comprising a pair of coupled blockchains
CN111309745B (en) Virtual resource processing method and device, electronic equipment and storage medium
US20220036350A1 (en) Cross-border resource transfer authenticity verification method, device and electronic equipment
CN107358524B (en) Method for leveling funds among multiple account management lines in same currency
CN110046900B (en) Invoice revocation method and device based on block chain and electronic equipment
CN110852870A (en) Virtual resource transfer method, device, equipment and readable storage medium
CN110851531B (en) Cooperative edge computing method, block chain and cooperative edge computing system
WO2020088130A1 (en) Blockchain-based property execution method and system
CN113032036B (en) Service data processing method, device, system, computer equipment and storage medium
CN109614263B (en) Disaster tolerance data processing method, device and system
TWI736608B (en) Method and device for facilitating expansion of payment subject
CN111681053A (en) Receiving and paying chain construction method and device, computer equipment and readable storage medium
CN111680995A (en) Payment chain construction method and device, computer equipment and readable storage medium
JP7478240B2 (en) Escrow transaction method and system using smart contract on blockchain
CN113177772A (en) Service data processing method, device and system
CN110599347A (en) Bill processing method, device, computer readable storage medium and computer equipment
US20230244859A1 (en) System and method for automatically sharing verified user information across remote systems
KR100816298B1 (en) Method for Storing the Group Card
CN114328708A (en) Charging method, device and storage medium
CN113269627A (en) Accounting processing method and device
CN117764728A (en) Method, device, equipment and storage medium for cross-contract calling of blockchain

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40045885

Country of ref document: HK

GR01 Patent grant
GR01 Patent grant