CN117575491A

CN117575491A - Approval processing method and device, storage medium and electronic equipment

Info

Publication number: CN117575491A
Application number: CN202311197306.6A
Authority: CN
Inventors: 李�灿
Original assignee: Chongqing Ant Consumer Finance Co ltd
Current assignee: Chongqing Ant Consumer Finance Co ltd
Priority date: 2023-09-15
Filing date: 2023-09-15
Publication date: 2024-02-20

Abstract

The specification discloses an approval processing method, an approval processing device, a storage medium and electronic equipment, wherein the method comprises the following steps: and monitoring the collaborative approval state of the approval node and the collaborative approval service to determine an abnormal approval node, and then determining an upstream processing unit corresponding to the abnormal approval node, so that request approval retry processing for the data transfer request is initiated based on the upstream processing unit on the abnormal approval node and the target collaborative approval service.

Description

Approval processing method and device, storage medium and electronic equipment

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to an approval processing method, an approval processing device, a storage medium, and an electronic device.

Background

In recent years, with the rapid development of information technology, people can conveniently borrow various data resources by using the internet. In the process of borrowing data resources, the approval of a lending mechanism is often required to pass, and the approval of the lending mechanism usually needs to rely on a plurality of system approval nodes, and the approval failure is caused by the abnormal occurrence of a single system approval node.

Disclosure of Invention

The specification provides an approval processing method, an approval processing device, a storage medium and electronic equipment, wherein the technical scheme is as follows:

In a first aspect, the present disclosure provides an approval processing method applied to a data transfer approval system, where the method includes:

responding to a data transfer request initiated by a user side, and calling an approval collaboration service to approve the data transfer request in sequence based on a plurality of approval nodes in the data transfer approval system;

monitoring a collaborative approval state corresponding to the approval collaborative service of the approval node in the process of requesting approval;

when the collaborative approval state is an approval abnormal state, determining an upstream processing unit of an abnormal approval node corresponding to the approval abnormal state;

and controlling the abnormal approval node and a target approval cooperative service to perform request approval batch retry processing on the data transfer request based on the upstream processing unit, wherein the target approval cooperative service is the approval cooperative service corresponding to the abnormal approval node.

In a second aspect, the present disclosure provides an approval processing apparatus for use in a data transfer approval system, the apparatus comprising:

the response module is suitable for responding to a data transfer request initiated by a user side, calling approval collaboration service based on a plurality of approval nodes in the data transfer approval system and approving the data transfer request in sequence;

The monitoring module is suitable for monitoring the collaborative approval state corresponding to the approval collaborative service of the approval node in the process of requesting approval;

the determining module is suitable for determining an upstream processing unit of an abnormal approval node corresponding to the approval abnormal state when the collaborative approval state is the approval abnormal state;

and the request approval retry module is suitable for controlling the abnormal approval node and the target approval cooperative service to carry out request approval retry processing on the data transfer request based on the upstream processing unit, wherein the target approval cooperative service is the approval cooperative service corresponding to the abnormal approval node.

In a third aspect, the present description provides a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the above-described method steps.

In a fourth aspect, the present description provides an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the above-mentioned method steps.

In a fifth aspect, the present description provides a computer program product storing at least one instruction for loading by a processor and performing the method steps of any one of the above.

The technical scheme provided by some embodiments of the present specification has the following beneficial effects: and after the abnormal approval node with the collaborative approval state corresponding to the approval collaborative service is determined, an upstream processing unit corresponding to the abnormal approval node is found, and request approval retry processing for a data transfer request is initiated on the basis of the upstream processing unit on the abnormal approval node and the target approval collaborative service, so that information interaction between the abnormal approval node and the corresponding target approval collaborative service is recovered through retry, and the abnormal approval node and the corresponding target approval collaborative service are recovered to be normal, thereby solving the technical problem that approval failure is caused by abnormality of a single system approval node.

Drawings

In order to more clearly illustrate the technical solutions of the present specification or the prior art, the following description will briefly introduce the drawings that are required to be used in the embodiments or the prior art descriptions, it is obvious that the drawings in the following description are only some embodiments of the present specification, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic view of a scenario of a data transfer approval system and a client provided in the present disclosure;

FIG. 2 is a flow diagram of an approval process according to one or more embodiments of the present disclosure;

FIG. 3 is a flow diagram of a downstream approval process in accordance with one or more embodiments of the present disclosure;

FIG. 4 is a schematic diagram of an approval processing apparatus according to one or more embodiments of the present disclosure;

FIG. 5 is a schematic diagram of an electronic device provided in the present specification;

FIG. 6 is a schematic diagram of the architecture of the operating system and user space provided herein;

FIG. 7 is an architecture diagram of the android operating system of FIG. 6;

FIG. 8 is an architecture diagram of the IOS operating system of FIG. 6.

Detailed Description

The following description of the embodiments of the present invention will be made apparent from, and elucidated with reference to, the drawings of the present specification, in which embodiments described are only some, but not all, embodiments of the present specification. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

In the description of the present specification, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In the description of the present specification, it should be noted that, unless expressly specified and limited otherwise, "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus. The specific meaning of the terms in this specification will be understood by those of ordinary skill in the art in the light of the specific circumstances. In addition, in the description of the present specification, unless otherwise indicated, "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

In the traditional data transfer approval process, one scheme is to extend the call timeout time for the dependent approval node when approving the approval. In this mode, situations in which the approving node database is slow to execute or there is a network delay can be avoided. However, this solution also has significant drawbacks. Firstly, prolonging the time length of the branch examination and approval can reduce the experience of the user; second, it is difficult to determine a reasonable timeout.

The other scheme is to shorten the call timeout time of the approval node, quickly fail when the system is abnormal, then take a default spam value corresponding to different data transfer scenes, for example, call timeout when the student transfers data, the approval can be failed by default, and call timeout when the white collar transfers data, the approval can be successful by default. In the mode, the reasonable default spam value for distinguishing different scenes is high in cost and difficult to maintain, and the branch approval is used for controlling the risk of data transfer, so that the risk of data transfer is improved by taking the spam value.

In order to solve the technical problems, the embodiment of the specification provides an approval processing method, which solves the problem that the whole data transfer approval process is terminated due to single dependent system service abnormality by increasing the self-healing retry capability of the system in the approval process, thereby failing the data transfer request.

The present specification is described in detail below with reference to specific examples.

Referring to fig. 1, fig. 1 is a schematic view of a data transfer approval system and a user side provided in the present disclosure. As shown in fig. 1, the data transfer approval system may at least include a service platform 100, and the user terminal may at least include a client cluster.

The client cluster may include at least one client, as shown in fig. 1, specifically including a client 1 corresponding to a user 1, a client 2 corresponding to a user 2, …, and a client n corresponding to a user n, where n is an integer greater than 0.

Each client in the client cluster may be a communication-enabled electronic device including, but not limited to: wearable devices, handheld devices, personal computers, tablet computers, vehicle-mounted devices, smart phones, computing devices, or other processing devices connected to a wireless modem, etc. Electronic devices in different networks may be called different names, for example: a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent or user equipment, a cellular telephone, a cordless telephone, a personal digital assistant (personal digital assistant, PDA), an electronic device in a 5G network or future evolution network, and the like.

The service platform 100 may be a separate server device, such as: rack-mounted, blade, tower-type, or cabinet-type server equipment, or hardware equipment with stronger computing capacity such as workstations, mainframe computers and the like is adopted; the server cluster may also be a server cluster formed by a plurality of servers, and each server in the server cluster may be formed in a symmetrical manner, wherein each server is functionally equivalent and functionally equivalent in a transaction link, and each server may independently provide services to the outside, and the independent provision of services may be understood as no assistance of another server is needed.

In one or more embodiments of the present disclosure, the service platform 100 may establish a communication connection with at least one client in the client cluster, and complete data interaction during the approval process based on the communication connection, such as online transaction data interaction, for example, the service platform 100 may implement content recommendation to the client based on a target neural network model obtained by the approval process method of the present disclosure; as another example, the service platform 100 may obtain training data, such as first training data, from a client.

It should be noted that, the service platform 100 establishes a communication connection with at least one client in the client cluster through a network for interactive communication, where the network may be a wireless network, or may be a wired network, where the wireless network includes, but is not limited to, a cellular network, a wireless local area network, an infrared network, or a bluetooth network, and the wired network includes, but is not limited to, an ethernet network, a universal serial bus (universal serial bus, USB), or a controller area network. In one or more embodiments of the specification, techniques and/or formats including HyperText Mark-up Language (HTML), extensible markup Language (Extensible Markup Language, XML), and the like are used to represent data exchanged over a network (e.g., target compression packages). All or some of the links may also be encrypted using conventional encryption techniques such as secure socket layer (Secure Socket Layer, SSL), transport layer security (Transport Layer Security, TLS), virtual private network (Virtual Private Network, VPN), internet protocol security (Internet Protocol Security, IPsec), and the like. In other embodiments, custom and/or dedicated data communication techniques may also be used in place of or in addition to the data communication techniques described above.

The embodiments of the data transfer approval system provided in the present disclosure and the approval processing methods in one or more embodiments belong to the same concept, and an execution subject corresponding to the approval processing methods related to one or more embodiments in the present disclosure may be the service platform 100 described above; the execution subject corresponding to the approval processing method in one or more embodiments of the specification may also be an electronic device corresponding to the client, which is specifically determined based on an actual application environment. The implementation process of the data transfer approval system embodiment may be described in detail in the following method embodiment, which is not described herein.

Based on the schematic view of the scenario shown in fig. 1, the following describes in detail an approval processing method provided in one or more embodiments of the present disclosure.

Referring to fig. 2, fig. 2 provides a flow diagram of an approval process method, which may be implemented by a computer program and may be executed on an approval processing device based on von neumann system, according to one or more embodiments of the present disclosure. The computer program may be integrated in the application or may run as a stand-alone tool class application. The approval processing device may be a service platform.

Specifically, the approval processing method is applied to a data transfer approval system, and comprises the following steps:

s202: and responding to the data transfer request initiated by the user terminal, and calling an approval collaboration service to approve the data transfer request in sequence based on a plurality of approval nodes in the data transfer approval system.

The user side initiates a data transfer request to the data transfer approval system, and after the data transfer approval system receives the data transfer request, the data transfer approval system can call the corresponding approval collaboration service based on a plurality of approval nodes in the data transfer approval system and approve the data transfer request according to the approval collaboration sequence.

The number of the plurality of approval nodes in the data transfer approval system can be two, three, four, etc. Each approval node has a corresponding approval collaboration service, which belongs to an external service compared with the data transfer approval system. The approval nodes interact with the corresponding approval cooperative service so as to realize the approval of the nodes on the data transfer request. For example, the approval node requests the corresponding approval cooperative service, when the request is successful and the target data of the data transfer request of the approval cooperative service is correctly taken, the target data is checked, and when the check is passed, the next approval node processing is performed.

When the data transfer request is to be sequentially examined based on the examination and approval cooperative service called by the examination and approval nodes in the data transfer and approval system, the data transfer request can be sequentially examined and approved based on the examination and approval cooperative service serial called by the examination and approval nodes in the data transfer and approval system, or the data transfer request can be sequentially examined and approved based on the examination and approval cooperative service parallel called by the examination and approval nodes in the data transfer and approval system. Here, it should be noted that, when a single approval node is abnormal and cannot be recovered during serial approval or parallel approval of the data transfer request, the whole approval process is terminated.

In one embodiment provided in the present specification, the data transfer approval system includes at least two of an organization contract check node, a credit agreement check node, a credit check node, a wind control authentication check node, and a data transfer scheme decision node.

The data transfer approval system can comprise any two, three, four or five of an organization contract check node, a credit agreement check node, a credit check node, a wind control authentication check node and a data transfer scheme decision node.

When the data transfer approval system can include an organization contract check node, a credit agreement check node, a credit check node, a wind control authentication check node and a data transfer scheme decision node, the data transfer approval system can perform serial approval on the data transfer request based on the nodes. At this time, the approval collaboration sequence may be:

the approval node requests corresponding approval cooperative service, when the request is successful and the target data of the approval cooperative service aiming at the data transfer request is correctly taken, the target data is checked, and when the check is passed, the next approval node processing is carried out

When the organization contract check node requests corresponding approval cooperative service, namely organization contract service, when the request is successful and the organization contract service is correctly taken into target data of the data transfer request, namely organization contract state, fund proportion and the like, the organization contract check node checks the target data, such as whether the organization contract state is valid, the fund proportion is correct and the like, and when the verification is passed, approval processing of the trust agreement check node is carried out.

The credit agreement check node requests corresponding approval cooperative service, namely credit agreement service, when the request is successful and the target data of the credit agreement service aiming at the data transfer request, namely the protocol state, is correctly taken, the credit agreement check node checks the target data, namely the verification of whether the protocol state is valid or not, and when the verification is passed, approval processing of the credit check node is carried out.

And requesting corresponding approval cooperative service by using the credit check node, namely using the credit service, checking the target data aiming at the data transfer request by using the credit service when the request is successful and the target data, namely the data transfer credit, is correctly obtained, checking the target data by using the credit check node, judging whether the data transfer credit is larger than or equal to the data transfer amount corresponding to the data transfer request, checking to pass when the data transfer credit is larger than or equal to the data transfer amount corresponding to the data transfer request, and performing approval processing of the wind control authentication check node after the checking is passed.

The wind control authentication check node requests corresponding approval cooperative service, namely wind control authentication service, when the request is successful and the wind control authentication service is correctly taken to target data of the data transfer request, namely safety wind control information, credit wind control information, historical behavior data and the like, the wind control authentication check node checks the target data, judges whether the safety wind control information, the credit wind control information, the historical behavior data and the like meet approval requirements, and when the request meets the approval requirements, the verification is passed, and after the verification is passed, approval processing of the data transfer scheme decision node is carried out.

The data transfer scheme decision node requests corresponding approval cooperative service, namely decision consultation service, when the request is successful and the decision consultation service is correctly taken to target data of the data transfer request, namely the organization information for providing borrowed data, the data transfer scheme decision node checks the target data, checks whether the organization information for providing the borrowed data meets the approval requirement or not, and when the data meets the approval requirement, the check is passed, the data transfer is carried out after the check is passed, and then the data transfer receipt is provided.

S204: and monitoring the collaborative approval state corresponding to the approval collaborative service of the approval node in the request approval process.

When the approval node approves the data transfer request, the collaborative approval state corresponding to the approval node and the approval collaborative service is monitored. Because the approval cooperative service belongs to external service, interaction jitter exists in the interaction process of the approval node and the approval cooperative service, so that the interaction is abnormal, and the whole approval process is possibly terminated. Therefore, the collaborative approval state corresponding to the approval collaborative service of the approval node can be monitored in the process of requesting the data transfer approval system to carry out approval.

S206: and when the collaborative approval state is an approval abnormal state, determining an upstream processing unit of an abnormal approval node corresponding to the approval abnormal state.

When the collaborative approval state is an approval abnormal state, an abnormal approval node corresponding to the approval abnormal state is determined, the abnormal approval node is identified and captured, and then an upstream processing unit corresponding to the abnormal approval node is determined. Here, the upstream processing unit includes, but is not limited to, an approval node upstream of the abnormal approval node and a receiving interface unit of the data transfer approval system for the data transfer request, where the receiving interface unit may receive the data transfer request and/or perform preprocessing before node approval on the received data transfer request.

S208: and controlling the abnormal approval node and the target approval cooperative service to perform request approval and retry processing on the data transfer request based on the upstream processing unit, wherein the target approval cooperative service is the approval cooperative service corresponding to the abnormal approval node.

After the abnormal approval node corresponding to the approval abnormal state and the upstream processing unit of the abnormal approval node are determined, the characteristic of short system jitter occurrence time and quick recovery are considered, so that when the abnormal approval node is abnormal, the abnormal approval node can be recovered through retry. System jitter refers to the fact that multiple components such as databases, networks, message centers, external services and the like are relied on in a system, and each component has a very small probability of failure in execution and usually has short time and very fast recovery.

Therefore, the data transfer request can be subjected to request approval retry processing based on the control of the abnormal approval node and the target approval cooperation service by the upstream processing unit, namely, the abnormal approval node and the target approval cooperation service receive and interactively process the data transfer request again. Here, the target approval cooperative service is an approval cooperative service corresponding to the abnormal approval node.

When the approval nodes in the data transfer approval system are 5, the overall approval failure probability is 0.05% according to the calculation of 0.01% of the jitter probability between each approval node and the approval cooperative service, and the approval success rate can be improved by 0.05% after optimization.

In the embodiment provided by the specification, the collaborative approval state corresponding to the approval collaborative service is monitored, the abnormal approval node with the collaborative approval state being the approval abnormal state is determined, then an upstream processing unit corresponding to the abnormal approval node is found, and the request approval retry processing for the data transfer request is initiated on the basis of the upstream processing unit for the abnormal approval node and the target approval collaborative service, so that the information interaction between the abnormal approval node and the corresponding target approval collaborative service is recovered through retry, and the abnormal approval node and the corresponding target approval collaborative service are recovered to be normal, so that the technical problem that the approval failure is caused by the occurrence of abnormality of the single system approval node is solved.

And when one of the approval nodes depends on the approval cooperative service to be abnormal, the short-term jitter can be quickly retried and recovered by the method, so that the stability of the system is ensured. The emergency possibility is increased, after the transaction is accepted synchronously, when the system has a short fault, the whole approval process is not stopped, and the fault is recovered in a relatively sufficient time before the whole approval process is stopped. The embodiment of the specification has no requirement on the overtime of the call and does not need to configure the spam values of different scenes; but when any node in the flow carries out abnormality, the upstream automatic initiation retry can be uniformly captured and driven, so that the system is recovered, and the approval flow is not blocked.

Of course, in other embodiments, the self-healing capability of automatic retry may also be supported inside the relying approval node, so that when the approval node is invoked by the branch approval, a deterministic approval result is necessarily returned, but the requirement on the approval node is higher.

In one embodiment provided in the present disclosure, monitoring, in S204, a co-approval state of an approval node corresponding to an approval co-service during a request approval includes:

and acquiring an approval collaborative execution result of the approval node in the request approval process, and determining a collaborative approval state of the approval node and the approval collaborative service based on the approval collaborative execution result.

In the process of request approval, after the approval node and the corresponding approval cooperation service perform approval processing on the data transfer request, when approval is abnormal or approval is normal, the approval node generates a corresponding approval cooperation execution result. Therefore, when the data transfer approval system is requested to carry out approval, an approval collaborative execution result of the approval node is obtained, and then, based on the approval collaborative execution result, a collaborative approval state of the approval node and the approval collaborative service is determined, namely, whether the collaborative approval state is an abnormal state or not.

And through monitoring the approval cooperative execution result of the approval node in the approval process, the cooperative approval state of the approval node and the approval cooperative service is obtained in real time, so that the intervention is performed in time when the cooperative approval state is abnormal.

In an embodiment provided in the present disclosure, determining a collaborative approval state of an approval node and an approval collaborative service based on an approval collaborative execution result in the above embodiment includes:

and determining the result of the approval co-execution as a target error code, and determining the co-approval state of the approval node and the approval co-service as an approval abnormal state.

In the process of requesting approval, after the approval node and the corresponding approval cooperation service thereof perform approval processing on the data transfer request, when the approval is abnormal, the approval node generates a corresponding target error code, after the approval node is identified to generate the target error code, the approval node and the approval cooperation service corresponding to the target error code are determined to be generated, and the cooperation approval state of the approval node and the approval cooperation service is determined to be the approval abnormal state.

The approval node and the approval cooperative service for approval of the abnormal state are identified by identifying the target error code generated by the approval node, so that the method provided by the specification can consider the existing approval protocol to realize the accurate identification of the approval node and the approval cooperative service for approval of the abnormal state.

In one embodiment provided in the present specification, the determining, in S206, an upstream processing unit of an exception approval node corresponding to an approval exception state includes:

And determining an approval coordination sequence aiming at the data transfer request, and determining an upstream processing unit corresponding to the abnormal approval node based on the approval coordination sequence.

And determining the approval collaborative sequence of each approval node and the receiving interface unit in the data transfer approval system for the data transfer request based on the dependency relationship between each approval node and the receiving interface unit in the data transfer approval system, namely, the approval sequence when the receiving interface unit and the approval node approve the data transfer request. After the approval coordination sequence aiming at the data transfer request is determined, the position of the abnormal approval node in the approval coordination sequence is determined, and the upstream processing unit corresponding to the abnormal approval node is determined based on the position of the abnormal approval node in the approval coordination sequence.

And determining an upstream processing unit corresponding to the abnormal approval node by determining an approval cooperation sequence aiming at the data transfer request in the data transfer approval system, so as to prepare for the subsequent initiation of request approval retry processing aiming at the data transfer request based on the upstream processing unit for the abnormal approval node and the target approval cooperation service.

In an embodiment provided in the present disclosure, the determining, in the above embodiment, an upstream processing unit corresponding to an abnormal approval node based on an approval coordination order includes:

If the abnormal approval node is the initial approval node, determining a receiving interface unit of the data transfer approval system aiming at the data transfer request, and determining the receiving interface unit as an upstream processing unit of the abnormal approval node;

if the abnormal approval node is not the initial approval node, acquiring an upstream approval node corresponding to the abnormal approval node based on the approval cooperation sequence, and determining the upstream approval node as an upstream processing unit of the abnormal approval node.

When the abnormal approval node is the initial approval node, the abnormal approval node is the approval node for approving the data transfer request in the first data transfer approval system, that is, no other approval node exists before the abnormal approval node. Thus, at this point, the receiving interface unit of the data transfer approval system for the data transfer request may be determined, and the receiving interface unit may receive the data transfer request and/or perform preprocessing before node approval on the received data transfer request. After determining the receiving interface unit, the receiving interface unit may be determined as an upstream processing unit of the exception approving node, so as to prepare for the subsequent initiation of a request approval retry process for the data transfer request based on the upstream processing unit for the exception approving node and the target approval collaboration service.

When the exception approving node is not the original approving node, i.e., there are other approving nodes before the exception approving node. Therefore, in this case, the upstream approval node corresponding to the abnormal approval node may be obtained based on the approval cooperation sequence, and the upstream approval node may be an upstream approval node adjacent to the abnormal approval node, or may be a non-adjacent upstream approval node before the abnormal approval node in the approval sequence. And determining the upstream approval node corresponding to the abnormal approval node as an upstream processing unit of the abnormal approval node.

By determining whether the abnormal approval node is an initial approval node or not, a proper receiving interface unit or an upstream approval node is selected as an upstream processing unit of the abnormal approval node, so that the embodiment of the specification can initiate request approval retry processing for a data transfer request based on the upstream processing unit to the abnormal approval node and a target approval cooperation service.

In one embodiment provided in the present disclosure, the step S208 of performing a request approval retry process on the data transfer request based on the upstream processing unit controlling the exception approval node and the target approval cooperation service includes:

And based on the abnormal approval node and the target approval cooperative service, performing request approval batch retry processing on the data transfer request.

After determining the abnormal approval node, sending the target error code generated by the abnormal approval node to an upstream processing unit, wherein the types of the target error code are various, different types of the target error code correspond to the abnormal type of the abnormal approval node, and the upstream processing unit carries out type identification on the target error code to obtain an identification result. Therefore, the data transfer request can be subjected to request approval retry processing based on the control of the abnormal approval node and the target approval cooperation service by the upstream processing unit, so that the abnormal approval node and the target approval cooperation service are restored to a normal state.

An approval retry instruction aiming at the data transfer request is sent to the abnormal approval node through the upstream processing unit, and the abnormal approval node is controlled to call a target approval cooperation service to carry out approval retry processing on the retry request based on the approval retry instruction; and/or the number of the groups of groups,

and transmitting an approval retry instruction aiming at the data transfer request to the target approval cooperative service through the upstream processing unit, and controlling a downstream approval node to call the downstream approval cooperative service to perform downstream approval processing on the data transfer request through the target approval cooperative service based on the approval retry instruction.

The upstream processing unit may send an approval retry instruction for the data transfer request to the abnormal approval node and/or the target approval cooperation service, and when the approval retry instruction for the data transfer request is only sent to the abnormal approval node, the abnormal approval node may be controlled to invoke the target approval cooperation service to perform an approval retry process on the retry request based on the approval retry instruction, that is, invoke the target approval cooperation service to perform a re-approval of the data transfer request again based on the abnormal approval node, so as to restore the abnormal approval node and the target approval cooperation service to a normal state.

When only an approval retry instruction for the data transfer request is sent to the target approval cooperative service, the downstream approval node can be directly controlled based on the target approval cooperative service to call the downstream approval cooperative service to perform downstream approval processing on the data transfer request, and at this time, the target approval cooperative service can also have the approval function of the abnormal approval node.

The upstream processing unit can also send approval retry instructions for the data transfer request to the abnormal approval node and the target approval cooperative service at the same time, and the data transfer request can be subjected to request approval retry processing based on the control of the abnormal approval node and the target approval cooperative service by the upstream processing unit through two paths.

Referring to fig. 3, fig. 3 is a schematic flow chart illustrating a downstream approval process according to one or more embodiments of the present disclosure. Specific:

in the above embodiment, an approval retry instruction for a data transfer request is sent to a target approval collaboration service through an upstream processing unit, and a downstream approval node is controlled to invoke a downstream approval collaboration service to perform downstream approval processing on the data transfer request based on the approval retry instruction through the target approval collaboration service, including:

s302: and sending an approval retry instruction aiming at the data transfer request to the target approval cooperative service through the upstream processing unit, and controlling the target approval cooperative service to perform target approval processing on the data transfer request through the approval retry instruction to obtain a target approval result.

After the upstream processing unit is determined, an approval retry instruction for the data transfer request is sent to a target approval cooperation service corresponding to the abnormal approval node based on the upstream processing unit, the target approval cooperation service is controlled to perform target approval processing on the data transfer request directly through the approval retry instruction, and a target approval result corresponding to the target approval processing is obtained. Here, the node approval problem when the abnormal approval node cannot be recovered is effectively solved. It should be noted that the objective approval collaboration service may have an approval function of an abnormal approval node.

S304: and the control target approval cooperation service sends the target approval result to at least one of the abnormal approval node and the downstream approval node so as to control the downstream approval node to call the downstream approval cooperation service to perform downstream approval processing on the data transfer request.

Because temporary interaction interruption possibility exists between the target approval cooperative service and the abnormal approval node, the target approval cooperative service can be controlled to send a target approval result to at least one of the abnormal approval node and the downstream approval node, information interaction between the target approval cooperative service and the abnormal approval node can be restored when the target approval cooperative service is controlled to send the target approval result to the abnormal approval node, the approval interruption caused by the fact that the information interaction between the target approval cooperative service and the abnormal approval node is not restored can be avoided when the target approval cooperative service is controlled to send the target approval result to the downstream approval node, and the target approval cooperative service and the abnormal approval node can be restored when the target approval cooperative service is controlled to send the target approval result to the abnormal approval node and the downstream approval node.

Referring to fig. 4, fig. 4 is a schematic structural diagram of an approval processing apparatus according to one or more embodiments of the present disclosure. The following describes in detail the approval processing device provided in the present specification with reference to fig. 4, where the approval processing device is applied to a data transfer approval system. It should be noted that, the approval processing apparatus shown in fig. 4 is used to execute the method of the embodiment shown in the foregoing description, and for convenience of explanation, only the portion relevant to the present description is shown, and specific technical details are not disclosed, please refer to the embodiment shown in the foregoing description.

Referring to fig. 4, a schematic structural diagram of an approval processing apparatus of the present specification is shown. The approval processing apparatus 1 may be implemented as all or part of a data transfer approval system by software, hardware or a combination of both. According to some embodiments, the approval processing apparatus 1 comprises a response module 11, a monitoring module 12, a determining module 13 and a request approval retry module 14, in particular for:

the response module 11 is suitable for responding to a data transfer request initiated by a user terminal, calling approval collaboration service based on a plurality of approval nodes in a data transfer approval system and approving the data transfer request in sequence;

The monitoring module 12 is adapted to monitor the collaborative approval state corresponding to the approval collaborative service of the approval node in the process of requesting approval;

the determining module 13 is adapted to determine an upstream processing unit of the abnormal approval node corresponding to the approval abnormal state when the collaborative approval state is the approval abnormal state;

the request approval retry module 14 is adapted to control the abnormal approval node and the target approval cooperation service to perform request approval retry processing on the data transfer request based on the upstream processing unit, where the target approval cooperation service is an approval cooperation service corresponding to the abnormal approval node.

In the embodiment provided in the present disclosure, by providing an approval processing apparatus 1, a collaborative approval state corresponding to an approval collaborative service of an approval node may be monitored, an abnormal approval node of the collaborative approval state is determined, and then an upstream processing unit corresponding to the abnormal approval node is found, and a request approval retry process for a data transfer request is initiated for the abnormal approval node and a target approval collaborative service based on the upstream processing unit, so that information interaction between the abnormal approval node and the corresponding target approval collaborative service is recovered through retry, so that the abnormal approval node and the corresponding target approval collaborative service recover to be normal, and a technical problem that an approval failure will be caused when an abnormality occurs in a single system approval node is solved.

Optionally, the monitoring module 12 is adapted to obtain an approval co-execution result of the approval node during the request approval process, and determine a co-approval status of the approval node and the approval co-service based on the approval co-execution result.

Optionally, the monitoring module 12 is adapted to determine that the result of the collaborative execution of the approval is a target error code, and determine that the collaborative approval state of the approval node and the collaborative approval service is an approval abnormal state.

Optionally, the determining module 13 is adapted to determine an approval co-order for the data transfer request, and determine the upstream processing unit corresponding to the abnormal approval node based on the approval co-order.

Optionally, the determining module 13 is adapted to determine a receiving interface unit of the data transfer approval system for the data transfer request if the abnormal approval node is the initial approval node, and determine the receiving interface unit as an upstream processing unit of the abnormal approval node;

Optionally, the request approval retry module 14 is adapted to send the target error code to the upstream processing unit based on the abnormal approval node, control the upstream processing unit to perform type recognition on the target error code to obtain a recognition result, determine that the recognition result is a system retry result, and perform request approval retry processing on the data transfer request based on the upstream processing unit control the abnormal approval node and the target approval cooperation service.

Optionally, the request approval retry module 14 is adapted to send an approval retry instruction for the data transfer request to the exception approval node through the upstream processing unit, and control the exception approval node to invoke the target approval collaboration service to perform the approval retry process on the retry request based on the approval retry instruction; and/or the number of the groups of groups,

Optionally, the request approval retry module 14 includes:

the processing sub-module is suitable for sending an approval retry instruction aiming at the data transfer request to the target approval cooperative service through the upstream processing unit, and controlling the target approval cooperative service to perform target approval processing on the data transfer request through the approval retry instruction to obtain a target approval result;

the control sub-module is suitable for controlling the target approval cooperation service to send the target approval result to at least one of the abnormal approval node and the downstream approval node so as to control the downstream approval node to call the downstream approval cooperation service to perform downstream approval processing on the data transfer request.

Optionally, the data transfer approval system comprises at least two of an organization contract check node, a credit agreement check node, a credit check node, a wind control authentication check node and a data transfer scheme decision node.

It should be noted that, when the approval processing apparatus provided in the foregoing embodiment performs the approval processing method, only the division of the foregoing functional modules is used as an example, and in practical application, the foregoing functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the approval processing device and the approval processing method provided in the foregoing embodiments belong to the same concept, which embody detailed implementation procedures in the method embodiments, and are not repeated here.

The foregoing description is provided for the purpose of illustration only and does not represent the advantages or disadvantages of the embodiments.

The present disclosure further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are adapted to be loaded by a processor and execute the approval processing method as shown in the embodiments of the present disclosure, and the specific execution process may refer to the specific description of the foregoing embodiments, which is not repeated herein.

The present disclosure further provides a computer program product, where at least one instruction is stored, where the at least one instruction is loaded by the processor and executed by the processor to perform the method for approval processing according to the foregoing embodiment, and a specific execution process may refer to a specific description of the foregoing embodiment, which is not repeated herein.

Referring to fig. 5, fig. 5 is a schematic structural diagram of an electronic device provided in the present disclosure. The electronic device in this specification may include one or more of the following: processor 110, memory 120, input device 130, output device 140, and bus 150. The processor 110, the memory 120, the input device 130, and the output device 140 may be connected by a bus 150.

Processor 110 may include one or more processing cores. The processor 110 utilizes various interfaces and lines to connect various portions of the overall electronic device, perform various functions of the electronic device 100, and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 120, and invoking data stored in the memory 120. Alternatively, the processor 110 may be implemented in at least one hardware form of digital signal processing (digital signal processing, DSP), field-programmable gate array (field-programmable gate array, FPGA), programmable logic array (programmable logic Array, PLA). The processor 110 may integrate one or a combination of several of a central processor (central processing unit, CPU), an image processor (graphics processing unit, GPU), and a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for being responsible for rendering and drawing of display content; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 110 and may be implemented solely by a single communication chip.

The memory 120 may include a random access memory (random Access Memory, RAM) or a read-only memory (ROM). Optionally, the memory 120 includes a non-transitory computer readable medium (non-transitory computer-readable storage medium). Memory 120 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 120 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, which may be an Android (Android) system, including an Android system-based deep development system, an IOS system developed by apple corporation, including an IOS system-based deep development system, or other systems, instructions for implementing at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments described below, and the like. The storage data area may also store data created by the electronic device in use, such as phonebooks, audiovisual data, chat log data, and the like.

Referring to FIG. 6, FIG. 6 is a schematic diagram of the operating system and user space provided herein. Memory 120 may be divided into an operating system space in which the operating system runs and a user space in which native and third party applications run. In order to ensure that different third party application programs can achieve better operation effects, the operating system allocates corresponding system resources for the different third party application programs. However, the requirements of different application scenarios in the same third party application program on system resources are different, for example, under the local resource loading scenario, the third party application program has higher requirement on the disk reading speed; in the animation rendering scene, the third party application program has higher requirements on the GPU performance. The operating system and the third party application program are mutually independent, and the operating system often cannot timely sense the current application scene of the third party application program, so that the operating system cannot perform targeted system resource adaptation according to the specific application scene of the third party application program.

In order to enable the operating system to distinguish specific application scenes of the third-party application program, data communication between the third-party application program and the operating system needs to be communicated, so that the operating system can acquire current scene information of the third-party application program at any time, and targeted system resource adaptation is performed based on the current scene.

Referring to fig. 7, fig. 7 is a diagram illustrating an architecture of the android operating system in fig. 6. Taking an operating system as an Android system as an example, as shown in fig. 7, a program and data stored in the memory 120 may be stored in the memory 120 with a Linux kernel layer 320, a system runtime library layer 340, an application framework layer 360 and an application layer 380, where the Linux kernel layer 320, the system runtime library layer 340 and the application framework layer 360 belong to an operating system space, and the application layer 380 belongs to a user space. The Linux kernel layer 320 provides the underlying drivers for various hardware of the electronic device, such as display drivers, audio drivers, camera drivers, bluetooth drivers, wi-Fi drivers, power management, and the like. The system runtime layer 340 provides the main feature support for the Android system through some C/c++ libraries. For example, the SQLite library provides support for databases, the OpenGL/ES library provides support for 3D graphics, the Webkit library provides support for browser kernels, and the like. Also provided in the system runtime library layer 340 is a An Zhuoyun runtime library (Android run) which provides mainly some core libraries that can allow developers to write Android applications using the Java language. The application framework layer 360 provides various APIs that may be used in building applications, which developers can also build their own applications by using, for example, campaign management, window management, view management, notification management, content provider, package management, call management, resource management, location management. At least one application program is running in the application layer 380, and these application programs may be native application programs of the operating system, such as a contact program, a short message program, a clock program, a camera application, etc.; and may also be a third party application developed by a third party developer, such as a game-like application, instant messaging program, photo beautification program, etc.

Taking an operating system as an IOS system as an example, the programs and data stored in the memory 120 are shown in fig. 8, the IOS system includes: core operating system layer 420 (Core OS layer), core service layer 440 (Core Services layer), media layer 460 (Media layer), and touchable layer 480 (Cocoa Touch Layer). The core operating system layer 420 includes an operating system kernel, drivers, and underlying program frameworks that provide more hardware-like functionality for use by the program frameworks at the core services layer 440. The core services layer 440 provides system services and/or program frameworks required by the application, such as a Foundation (Foundation) framework, an account framework, an advertisement framework, a data storage framework, a network connection framework, a geographic location framework, a sports framework, and the like. The media layer 460 provides an interface for applications related to audiovisual aspects, such as a graphics-image related interface, an audio technology related interface, a video technology related interface, an audio video transmission technology wireless play (AirPlay) interface, and so forth. The touchable layer 480 provides various commonly used interface-related frameworks for application development, with the touchable layer 480 being responsible for user touch interactions on the electronic device. Such as a local notification service, a remote push service, an advertisement framework, a game tool framework, a message User Interface (UI) framework, a User Interface UIKit framework, a map framework, and so forth.

Referring to FIG. 8, FIG. 8 is a block diagram of the IOS operating system of FIG. 6. Among the frameworks illustrated in fig. 8, frameworks related to most applications include, but are not limited to: the infrastructure in core services layer 440 and the UIKit framework in touchable layer 480. The infrastructure provides many basic object classes and data types, providing the most basic system services for all applications, independent of the UI. While the class provided by the UIKit framework is a basic UI class library for creating touch-based user interfaces, iOS applications can provide UIs based on the UIKit framework, so it provides the infrastructure for applications to build user interfaces, draw, process and user interaction events, respond to gestures, and so on.

The manner and principle of implementing data communication between the third party application program and the operating system in the IOS system may refer to the Android system, and this description is not repeated here.

The input device 130 is configured to receive input instructions or data, and the input device 130 includes, but is not limited to, a keyboard, a mouse, a camera, a microphone, or a touch device. The output device 140 is used to output instructions or data, and the output device 140 includes, but is not limited to, a display device, a speaker, and the like. In one example, the input device 130 and the output device 140 may be combined, and the input device 130 and the output device 140 are a touch display screen for receiving a touch operation thereon or thereabout by a user using a finger, a touch pen, or any other suitable object, and displaying a user interface of each application program. Touch display screens are typically provided on the front panel of an electronic device. The touch display screen may be designed as a full screen, a curved screen, or a contoured screen. The touch display screen can also be designed to be a combination of a full screen and a curved screen, and a combination of a special-shaped screen and a curved screen is not limited in this specification.

In addition, those skilled in the art will appreciate that the configuration of the electronic device shown in the above-described figures does not constitute a limitation of the electronic device, and the electronic device may include more or less components than illustrated, or may combine certain components, or may have a different arrangement of components. For example, the electronic device further includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a wireless fidelity (wireless fidelity, wiFi) module, a power supply, and a bluetooth module, which are not described herein.

In this specification, the execution subject of each step may be the electronic device described above. Optionally, the execution subject of each step is an operating system of the electronic device. The operating system may be an android system, an IOS system, or other operating systems, which is not limited in this specification.

The electronic device of the present specification may further have a display device mounted thereon, and the display device may be various devices capable of realizing a display function, for example: cathode ray tube displays (cathode ray tubedisplay, CR), light-emitting diode displays (light-emitting diode display, LED), electronic ink screens, liquid crystal displays (liquid crystal display, LCD), plasma display panels (plasma display panel, PDP), and the like. A user may utilize a display device on electronic device 101 to view displayed text, images, video, etc. The electronic device may be a smart phone, a tablet computer, a gaming device, an AR (Augmented Reality ) device, an automobile, a data storage device, an audio playing device, a video playing device, a notebook, a desktop computing device, a wearable device such as an electronic watch, electronic glasses, an electronic helmet, an electronic bracelet, an electronic necklace, an electronic article of clothing, etc.

In the electronic device shown in fig. 5, where the electronic device may be a terminal, the processor 110 may be configured to invoke the network optimization application stored in the memory 120 and to specifically perform the following operations:

responding to a data transfer request initiated by a user side, and calling an approval collaboration service to approve the data transfer request in sequence based on a plurality of approval nodes in a data transfer approval system;

monitoring a collaborative approval state corresponding to the approval node and the approval collaborative service in the request approval process;

and controlling the abnormal approval node and the target approval cooperative service to perform request approval and retry processing on the data transfer request based on the upstream processing unit, wherein the target approval cooperative service is the approval cooperative service corresponding to the abnormal approval node.

In one embodiment, the processor 110, when executing the co-approval status corresponding to the approval co-service of the approval node during the request approval, specifically executes the following steps:

In one embodiment, the processor 110, when executing the determination of the co-approval status of the approval node and the approval co-service based on the result of the approval co-execution, specifically executes the following steps:

In one embodiment, when executing the upstream processing unit of the exception approval node corresponding to the determined approval exception state, the processor 110 specifically executes the following steps:

In one embodiment, the processor 110, when executing the upstream processing unit corresponding to the abnormal approval node based on the approval coordination sequence, specifically executes the following steps:

In one embodiment, the processor 110 specifically performs the following steps when performing the request review retry process on the data transfer request based on the control of the exception approving node by the upstream processing unit and the target review collaboration service:

In one embodiment, when the processor 110 sends an approval retry instruction for the data transfer request to the target approval collaboration service through the upstream processing unit, and controls the downstream approval node to invoke the downstream approval collaboration service to perform the downstream approval process on the data transfer request through the target approval collaboration service based on the approval retry instruction, the following steps are specifically performed:

an approval retry instruction aiming at the data transfer request is sent to the target approval cooperative service through the upstream processing unit, and the target approval cooperative service is controlled to carry out target approval processing on the data transfer request through the approval retry instruction so as to obtain a target approval result;

and the control target approval cooperation service sends the target approval result to at least one of the abnormal approval node and the downstream approval node so as to control the downstream approval node to call the downstream approval cooperation service to perform downstream approval processing on the data transfer request.

In one embodiment, the data transfer approval system comprises at least two of an organization contract check node, a credit agreement check node, a credit check node, a wind control authentication check node and a data transfer scheme decision node.

Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory, a random access memory, or the like.

It should be noted that, information (including but not limited to user equipment information, user personal information, etc.), data (including but not limited to data for analysis, stored data, presented data, etc.), and signals according to the embodiments of the present disclosure are all authorized by the user or are fully authorized by the parties, and the collection, use, and processing of relevant data is required to comply with relevant laws and regulations and standards of relevant countries and regions. For example, object features, interactive behavior features, user information, and the like referred to in this specification are all acquired with sufficient authorization.

The foregoing disclosure is only illustrative of the preferred embodiments of the present invention and is not to be construed as limiting the scope of the claims, which follow the meaning of the claims of the present invention.

Claims

1. An approval processing method applied to a data transfer approval system, the method comprising:

2. The method of claim 1, wherein the monitoring, during the request approval, a collaborative approval state of the approval node corresponding to the approval collaborative service includes:

and acquiring an approval cooperative execution result of the approval node in the request approval process, and determining a cooperative approval state of the approval node and the approval cooperative service based on the approval cooperative execution result.

3. The method of claim 2, the determining, based on the approval co-execution result, a co-approval status of the approval node and the approval co-service, comprising:

4. The method according to claim 1, wherein the determining the upstream processing unit of the exception approval node corresponding to the approval exception state includes:

5. The method of claim 4, wherein the determining, based on the approval co-order, an upstream processing unit corresponding to the abnormal approval node includes:

if the abnormal approval node is an initial approval node, determining a receiving interface unit of the data transfer approval system aiming at the data transfer request, and determining the receiving interface unit as an upstream processing unit of the abnormal approval node;

if the abnormal approval node is not the initial approval node, acquiring the upstream approval node corresponding to the abnormal approval node based on the approval cooperation sequence, and determining the upstream approval node as an upstream processing unit of the abnormal approval node.

6. A method according to claim 3, said controlling, based on the upstream processing unit, the exception approving node and target approval co-service to request approval retry processing of the data transfer request, comprising:

And based on the abnormal approval node, sending the target error code to the upstream processing unit, controlling the upstream processing unit to conduct type recognition on the target error code to obtain a recognition result, determining that the recognition result is a system retry result, and based on the upstream processing unit, controlling the abnormal approval node and the target approval cooperative service to conduct request approval batch retry processing on the data transfer request.

7. The method of claim 1, the controlling, based on the upstream processing unit, the exception approving node and a target approval collaboration service to request approval retry processing of the data transfer request, comprising:

transmitting an approval retry instruction aiming at the data transfer request to the abnormal approval node through the upstream processing unit, and controlling the abnormal approval node to call a target approval cooperation service to perform approval retry processing on the retry request based on the approval retry instruction; and/or the number of the groups of groups,

and sending an approval retry instruction aiming at the data transfer request to the target approval cooperative service through the upstream processing unit, and controlling a downstream approval node to call the downstream approval cooperative service to carry out downstream approval processing on the data transfer request through the target approval cooperative service based on the approval retry instruction.

8. The method of claim 7, wherein the sending, by the upstream processing unit, an approval retry instruction for the data transfer request to the target approval collaboration service, controlling, by the target approval collaboration service, a downstream approval node to invoke a downstream approval collaboration service to perform downstream approval processing on the data transfer request based on the approval retry instruction, includes:

transmitting an approval retry instruction aiming at the data transfer request to the target approval cooperative service through the upstream processing unit, and controlling the target approval cooperative service to perform target approval processing on the data transfer request through the approval retry instruction to obtain a target approval result;

and controlling a target approval cooperation service to send the target approval result to at least one of the abnormal approval node and the downstream approval node so as to control the downstream approval node to call the downstream approval cooperation service to perform downstream approval processing on the data transfer request.

9. The method of claim 1, the data transfer approval system comprising at least two of an organization contract check node, a credit agreement check node, a credit check node, a wind control authentication check node, and a data transfer scheme decision node.

10. An approval processing device applied to a data transfer approval system, the device comprising:

11. A computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the method steps of any one of claims 1 to 9.

12. A computer program product storing at least one instruction for loading by a processor and performing the method steps of any one of claims 1 to 9.

13. An electronic device, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the method steps of any of claims 1-9.