Method, apparatus, device and medium for remote authorization in business transactions

Abstract

The present disclosure provides a method for remote authorization in business transactions, which can be applied to the financial field. The method includes: receiving M remote authorization requests; in response to each of the received remote authorization requests, creating a remote authorization node corresponding to the remote authorization request; within a predetermined time after each of the remote authorization nodes is created, monitoring the status update information of the remote authorization node; wherein the status update information includes one of authorization passed, authorization failed, or authorization timeout; and in response to monitoring the status update information of each of the remote authorization nodes, feeding back the status update information to the requester of the remote authorization request corresponding to the remote authorization node to respond to the remote authorization request. The present disclosure also provides an apparatus, device, storage medium, and program product for remote authorization in business transactions.

Description

Technical Field

[0001] The present disclosure relates to the field of cloud computing and can be used in the financial field. More specifically, it relates to a method, apparatus, device, medium and program product for remote authorization in business transactions. Background Art

[0002] In the business transactions of enterprises, permission approval requirements are usually set for some unconventional or sensitive businesses. When ordinary business personnel handle these businesses, they often need to apply for professional review and authorization, and can continue to execute the business after the authorization is passed. For example, in banking business, when tellers handle large transactions, frozen account transactions, or re-review business transactions, they need to be authorized by higher authority levels or more professional personnel. At present, this authorization is usually completed through the on-site authorization mode. In the on-site authorization mode, when business personnel handle business transactions that require authorization, they will ask professionals with approval authority on site, and then the professionals will review and handle them on site. However, this mode requires both business personnel and professionals to be on site, which places too high requirements on the location and time of both parties. Summary of the invention

[0003] In view of the above problems, the present disclosure provides methods, devices, equipment, media and program products for remote authorization in business transactions that can be processed remotely and in real time online, at least overcoming the defect of strict restrictions on the locations of both parties in the on-site authorization mode requirements.

[0004] In a first aspect of an embodiment of the present disclosure, a method for remote authorization in a business transaction is provided. The method comprises: receiving M remote authorization requests, wherein the M remote authorization requests are respectively from M requesting parties, and M is an integer greater than or equal to 1; in response to each received remote authorization request, creating a remote authorization node corresponding to the remote authorization request; wherein the remote authorization node is used to provide one of the N authorized parties with an entry for authorization review of the remote authorization request, and record the authorization result to update the state of the remote authorization node, wherein N is an integer greater than or equal to 1; within a predetermined time after each remote authorization node is created, monitoring the state update information of the remote authorization node; wherein the state update information includes one of authorization passed, authorization failed, or authorization timed out; and in response to monitoring the state update information of each remote authorization node, feeding back the state update information to the requesting party of the remote authorization request corresponding to the remote authorization node to respond to the remote authorization request.

[0005] According to an embodiment of the present disclosure, the method also includes: receiving at least one authorization query request, wherein each of the authorization query request comes from one of the N authorizers; in response to the authorization query request, sending a record to be authorized to the authorizer that sent the authorization query request, wherein the record to be authorized includes information of at least one remote authorization node; based on the authorizer's selection operation on the remote authorization node in the record to be authorized, feeding back to the authorizer the remote authorization request corresponding to the selected remote authorization node; obtaining authorization result information obtained by the authorizer through an authorization review of the remote authorization request; and using the authorization result information to update the status of the remote authorization node selected by the authorizer.

[0006] According to an embodiment of the present disclosure, the creating a remote authorization node corresponding to the remote authorization request includes: using zookeeper to create the remote authorization node.

[0007] According to an embodiment of the present disclosure, the remote authorization node includes a remote authorization request node and a remote authorization response node. The remote authorization request node is used to provide one of the N authorized parties with an entry for authorization review of the remote authorization request; and the remote authorization response node is used to record the authorization result to update the status of the remote authorization node.

[0008] According to an embodiment of the present disclosure, before monitoring the status update information of the remote authorization node, the method further includes: registering a listener with each of the remote authorization nodes, the listener being used to monitor the status update information of the remote authorization node.

[0009] According to an embodiment of the present disclosure, the method further includes: in response to each remote authorization request received, obtaining transaction record information corresponding to the remote authorization request; wherein, the authorization review of the remote authorization request includes performing an authorization review on the transaction record information corresponding to the remote authorization request.

[0010] According to an embodiment of the present disclosure, the obtaining of the transaction record information corresponding to the remote authorization request includes: obtaining transaction page information corresponding to the remote authorization request in a client of the requester of the remote authorization request.

[0011] According to an embodiment of the present disclosure, the obtaining of the transaction record information corresponding to the remote authorization request further includes: storing the transaction page information in a database that communicates with the remote authorization node in HTML format.

[0012] According to an embodiment of the present disclosure, after feeding back the status update information to the requester of the remote authorization request corresponding to the remote authorization node, the method further includes: deleting the remote authorization node.

[0013] In a second aspect of the embodiments of the present disclosure, a device for remote authorization in business transactions is provided. The device includes a first receiving module, a creation module, a monitoring module, and a response module. The first receiving module is used to receive M remote authorization requests, wherein the M remote authorization requests are respectively from M requesting parties, and M is an integer greater than or equal to 1. The creation module is used to create a remote authorization node corresponding to the remote authorization request in response to each received remote authorization request; wherein the remote authorization node is used to provide one of the N authorized parties with an entry for authorization review of the remote authorization request, and record the authorization result to update the state of the remote authorization node, wherein N is an integer greater than or equal to 1. The monitoring module is used to monitor the status update information of the remote authorization node within a predetermined time after each remote authorization node is created; wherein the status update information includes one of authorization passed, authorization failed, or authorization timed out. The response module is used to respond to the status update information of each remote authorization node monitored, and feedback the status update information to the requesting party of the remote authorization request corresponding to the remote authorization node to respond to the remote authorization request.

[0014] According to an embodiment of the present disclosure, the device also includes a second receiving module, a record sending module, an audit interaction module, a result acquisition module and a node update module. The second receiving module is used to receive at least one authorization query request, wherein each of the authorization query requests comes from one of the N authorized parties. The record sending module is used to send a record to be authorized to the authorized party that sent the authorization query request in response to the authorization query request, and the record to be authorized includes information of at least one remote authorization node. The audit interaction module is used to feedback the remote authorization request corresponding to the selected remote authorization node to the authorized party based on the authorized party's selection operation on the remote authorization node in the record to be authorized. The result acquisition module is used to obtain the authorization result information obtained by the authorized party performing an authorization audit on the remote authorization request. The node update module is used to update the status of the remote authorization node selected by the authorized party using the authorization result information.

[0015] According to an embodiment of the present disclosure, the device further comprises a monitoring registration module. The monitoring registration module is used to register a listener with each remote authorization node before monitoring the status update information of the remote authorization node, and the listener is used to monitor the status update information of the remote authorization node.

[0016] According to an embodiment of the present disclosure, the device further comprises a transaction information acquisition module. The transaction information acquisition module is used to respond to each received remote authorization request and acquire transaction record information corresponding to the remote authorization request. The performing authorization review on the remote authorization request comprises performing authorization review on the transaction record information corresponding to the remote authorization request.

[0017] According to an embodiment of the present disclosure, the transaction information acquisition module is specifically used to acquire transaction page information corresponding to the remote authorization request in the client of the requester of the remote authorization request.

[0018] According to an embodiment of the present disclosure, the transaction information acquisition module is further used to store the transaction page information in a database that communicates with the remote authorization node in HTML format.

[0019] According to an embodiment of the present disclosure, the device further comprises a node deletion module. The node deletion module is used to delete the remote authorization node after feeding back the status update information to the requester of the remote authorization request corresponding to the remote authorization node.

[0020] In a third aspect of the embodiments of the present disclosure, an electronic device is provided. The electronic device includes one or more processors and one or more memories. The one or more memories are used to store one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors execute the above method.

[0021] According to a fourth aspect of the embodiments of the present disclosure, there is also provided a computer-readable storage medium on which executable instructions are stored, and when the instructions are executed by a processor, the processor executes the above method.

[0022] According to a fifth aspect of the embodiments of the present disclosure, a computer program product is provided, including a computer program, which implements the above method when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The above contents and other purposes, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0024] Figure 1 The application scenario diagram schematically shows the method, apparatus, device, medium and program product for remote authorization in business transactions according to the embodiments of the present disclosure;

[0025] Figure 2 A flowchart of a method for remote authorization in a business transaction according to an embodiment of the present disclosure is schematically shown;

[0026] Figure 3 A flowchart of a method for remote authorization in a business transaction according to another embodiment of the present disclosure is schematically shown;

[0027] Figure 4 A flowchart of a method for remote authorization in a business transaction according to yet another embodiment of the present disclosure is schematically shown;

[0028] Figure 5 A conceptual diagram of a process for remote authorization in a business transaction according to an embodiment of the present disclosure is schematically shown;

[0029] Figure 6 A flowchart of three-party interaction in a method for remote authorization in a business transaction according to an embodiment of the present disclosure is schematically shown;

[0030] Figure 7 A block diagram schematically shows an apparatus for remote authorization in a business transaction according to an embodiment of the present disclosure; and

[0031] Figure 8 A block diagram of an electronic device suitable for implementing a method for remote authorization in a business transaction according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0032] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0033] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0034] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0035] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0036] The disclosed embodiment provides a method, apparatus, device, medium and program product for remote authorization in business transactions that can be processed remotely and in real time online. The method includes first receiving M remote authorization requests, wherein the M remote authorization requests are respectively from M requesting parties, and M is an integer greater than or equal to 1. Then, in response to each remote authorization request received, a remote authorization node corresponding to the remote authorization request is created, wherein the remote authorization node is used to provide one of the N authorized parties with an entry for authorization review of the remote authorization request, and record the authorization result to update the state of the remote authorization node, wherein N is an integer greater than or equal to 1. Next, within a predetermined time after each remote authorization node is created, the state update information of the remote authorization node is monitored, wherein the state update information includes one of authorization passed, authorization failed or authorization timed out. Finally, in response to the state update information of each remote authorization node monitored, the state update information is fed back to the requesting party of the remote authorization request corresponding to the remote authorization node to respond to the remote authorization request.

[0037] In this way, after initiating a remote authorization request, within a certain period of time, either the authorization request is authorized, and the requester can continue the transaction; or the remote authorization request is not authorized, and the requester stops the transaction; or if no authorization result is received regarding the authorization request within a predetermined period of time, the authorization times out and the transaction ends. If the transaction needs to be re-approved after the authorization times out, the requester needs to re-initiate the authorization request and process it online in real time. It can be seen that according to the embodiments of the present disclosure, for each business transaction that requires authorization, feedback results can be given through real-time online processing. On the one hand, both business personnel and professionals can be free from geographical restrictions in business processing, and the workplace is more flexible. On the other hand, it can also avoid the anxiety caused by the requester being in a completely passive state after the authorization request is submitted.

[0038] It should be noted that the methods, devices, equipment, media and program products for remote authorization in business transactions determined in the embodiments of the present disclosure can be used in the financial field, and can also be used in any field other than the financial field. The present disclosure does not limit the application field.

[0039] Figure 1The application scenario diagram of the method, apparatus, device, medium and program product for remote authorization in business transactions according to an embodiment of the present disclosure is schematically shown.

[0040] like Figure 1 As shown, the application scenario 100 according to this embodiment may include at least one requesting client 101 , an authorization system 102 , and at least one authorizing client 103 .

[0041] At least one requesting client 101 can communicate with the authorization system 102. The requesting party can use the requesting party client 101 to input business transaction information, submit a remote authorization request to the authorization system 102 through operations in the requesting party client 101, and wait online for authorization approval, authorization failure, or authorization timeout information fed back by the authorization system 102 within a fixed time, and determine whether to continue the transaction, stop the transaction, or end the transaction accordingly. The requesting party is a user on the requesting party client 101, for example, a business person who logs in through an account on the requesting party client 101, or a robot software using the requesting party client 101.

[0042] At least one authorizer client 103 can communicate with the authorization system 102. The authorizer can use one authorizer client 103 to obtain the pending authorization records that need to be authorized and reviewed by itself from the authorization system 102, and determine whether the authorization is passed by reviewing each pending authorization transaction in the pending authorization record, and feedback the authorization result to the authorization system 102. The authorizer is a user on the authorizer client 101, for example, a professional who logs in to the authorizer client 101 through an account, or a robot software using the authorizer client 101.

[0043] The authorization system 102 may be composed of one or more servers. The authorization system 102 may execute the method for remote authorization in business transactions of the embodiment of the present disclosure, manage the received authorization requests, and give corresponding response information for an authorization request within a fixed time period, regardless of whether the authorization result fed back by the authorizer is received, so as to end the online authorization processing flow.

[0044] It should be noted that the method for remote authorization in business transactions provided in the embodiments of the present disclosure can generally be executed by the authorization system 102. Accordingly, the apparatus, device, medium and program product for remote authorization in business transactions provided in the embodiments of the present disclosure can generally be set in the authorization system 102.

[0045] It should be understood that Figure 1The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0046] The following will be based on Figure 1 The scene described by Figure 2 to Figure 6 A method for remote authorization in a business transaction according to a disclosed embodiment is described in detail.

[0047] Figure 2 The flowchart of the method for remote authorization in business transactions according to an embodiment of the present disclosure is schematically shown.

[0048] like Figure 2 As shown, the method for remote authorization in business transactions of this embodiment may include operations S210 to S240.

[0049] In operation S210, M remote authorization requests are received, wherein the M remote authorization requests are respectively from M requesters, and M is an integer greater than or equal to 1. For example, in the application scenario 100, the authorization system 102 can receive a remote authorization request sent by at least one requester client 101. According to one embodiment of the present disclosure, each requester client 101 can be limited to only send one remote authorization request within a time period. For example, after sending the remote authorization request, the requester client 101 can be set to enter an online waiting state (for example, locking the current page, etc.), and before the remote authorization request is responded to, the requester client 101 cannot initiate a new remote authorization request.

[0050] In operation S220, in response to each remote authorization request received, a remote authorization node corresponding to the remote authorization request is created. The remote authorization node is used to provide one of the N authorized parties with an entry for authorization review of the remote authorization request, and to record the authorization result to update the state of the remote authorization node, where N is an integer greater than or equal to 1. For example, the remote authorization node can be created according to the agreed rules to ensure that the node will not be repeated. For example, according to the principle that a requesting party can only send one remote authorization request for the same business transaction in each time period, the remote authorization node is encoded according to the request time, business personnel information, transaction information, etc.

[0051] According to an embodiment of the present disclosure, remote authorization requests are managed through a remote authorization node in the authorization system 102. For example, the authorization system 102 can provide the authorized party with entry information such as information summaries, links or paths for viewing remote authorization requests through the remote authorization node, and record the authorization result of the authorized party in the remote authorization node. The authorization system 102 enables the requester and the authorized party to share a storage model through the remote authorization node, and associates the received remote authorization request with the authorization result of the authorization review of the remote authorization request, thereby making the authorization system 102 applicable to scenarios where multiple requesters and multiple authorized parties work together.

[0052] In one embodiment, zookeeper can be used to create a remote authorization node. For example, the authorization system 102 can be deployed with Zookeeper and a database. Zookeeper can create a remote authorization node for the received remote authorization request, and use the remote authorization node to record the key information of the remote authorization request and the information of the received authorization result, with a small amount of data. The detailed request information in the remote authorization request or the business transaction information associated therewith can be stored in the database for verification and use by the authorized party.

[0053] According to one embodiment of the present disclosure, the remote authorization node may include a remote authorization request node and a remote authorization response node. The remote authorization request node is used to provide one of the N authorized parties with an entry for authorization review of the remote authorization request, and the remote authorization response node is used to record the authorization result to update the status of the remote authorization node. For example, the remote authorization request node may store authorization information such as business personnel information, transaction code, authorization type, etc. The remote authorization response node may store authorization result information such as authorization passed or authorization failed, etc.

[0054] In operation S230, within a predetermined time period after each remote authorization node is created, status update information of the remote authorization node is monitored, wherein the status update information includes one of authorization passed, authorization failed, or authorization timed out.

[0055] When the remote authorization node receives the authorization result fed back by the authorizer within the predetermined time period, the state of the remote authorization node may be updated to the authorization result information, such as authorization passed or authorization failed.

[0056] When the end time of the predetermined time is reached, if the remote authorization node has not received the authorization result information of authorization passed or authorization failed, in one embodiment, the state of the remote authorization node can be updated to authorization timeout.

[0057] When the remote authorization node includes a remote authorization request node and a remote authorization response node in operation S230, in one embodiment, only the status update information of the remote authorization response node may be monitored.

[0058] In operation S240, in response to monitoring the status update information of each remote authorization node, the status update information is fed back to the requester of the remote authorization request corresponding to the remote authorization node to respond to the remote authorization request. Thus, for each business that needs authorization, a feedback result can be given through real-time online processing, thereby completing the online processing of the remote authorization request within a fixed time.

[0059] Figure 3 The flowchart of a method for remote authorization in a business transaction according to another embodiment of the present disclosure is schematically shown.

[0060] like Figure 3 As shown, the method for remote authorization in business transactions according to this embodiment may further include operations S320, S330, and S350 in addition to operations S210 to S240.

[0061] First, in operation S210, M remote authorization requests are received, wherein the M remote authorization requests come from M requesting parties respectively, and M is an integer greater than or equal to 1.

[0062] Next, in operation S320, in response to each received remote authorization request, the transaction record information corresponding to the remote authorization request is obtained. Meanwhile, in operation S220, in response to each received remote authorization request, a remote authorization node corresponding to the remote authorization request is created.

[0063] Since the transaction record information of the transaction when the requesting party initiated the remote authorization request can be obtained for each remote authorization request in operation S320, when the authorizing party conducts an authorization review of the remote authorization request, the transaction record information can be provided to the authorizing party for detailed review.

[0064] The transaction record information obtained in operation S320 may be, for example, the transaction page information corresponding to the remote authorization request in the client of the requester of the remote authorization request. For example, after the authorization system 102 receives the remote authorization request, it intercepts the image of the page where the transaction information is input in the client 101 of the requester, or reads the code and other information of the page where the transaction information is input in the client 101 of the requester. Then, the transaction page information may be further stored in the database communicating with the remote authorization node in the form of html. In this way, when the authorized party queries the detailed information of the remote authorization request corresponding to the node through the remote authorization node, the transaction page information in html format may be found from the database. Storing the transaction page information in the form of html facilitates the network transmission of the transaction page information on the one hand, and facilitates opening the transaction page information through a browser in the client 103 of the authorized party on the other hand, so as to make the authorized party see the page information that is almost completely consistent with the transaction page information displayed in the client 101 of the requester, so that the requester and the authorized party can see almost the same transaction page interface, achieving an effect similar to the on-site audit mode, and improving the accuracy of the authorization audit.

[0065] Then, in operation S330, a listener is registered with each remote authorization node, and the listener is used to monitor the status update information of the remote authorization node. For example, when using zookeeper to create a remote authorization node, a PathChildrenCacheListener can be registered for each remote authorization node (such as when distinguishing between remote authorization request nodes and remote authorization response nodes, only remote response nodes can be registered), and the status update information of the corresponding node can be monitored through the PathChildrenCacheListener.

[0066] Next, in operation S230, the state update information of the remote authorization node may be monitored within a predetermined time period using a listener (eg, PathChildrenCacheListener) registered for each remote authorization node.

[0067] Then, in operation S240, in response to monitoring the status update information of each remote authorization node, the status update information is fed back to the requester of the remote authorization request corresponding to the remote authorization node, so as to respond to the remote authorization request.

[0068] Thereafter, in operation S350, the remote authorization node is deleted. In this way, not only the online processing of the remote authorization request is completed within a predetermined time period, but also the corresponding remote authorization node is deleted to release memory space.

[0069] It should be noted that in Figure 3 Operations S210 to S240 are consistent with the above description. Please refer to the above content for detailed information.

[0070] Figure 4 The flowchart of a method for remote authorization in a business transaction according to yet another embodiment of the present disclosure is schematically shown.

[0071] like Figure 4 As shown, according to another embodiment of the present disclosure, the method for remote authorization in business transactions includes Figure 2 or Figure 3 In addition to the method flow shown, operations S410 to S450 may also be included. Figure 4 The illustrated process involves the interaction process between the authorization system 102 and the authorization party.

[0072] First, in operation S410, at least one authorization query request is received, wherein each authorization query request comes from one of the N authorizers. In some embodiments, before operation S410, after a remote authorization node is created in the authorization system 102, authorization reminder information can be sent to the authorizer who authorizes the transaction based on the information of the transaction involved in the remote authorization node, so as to remind the authorizer to conduct authorization review in time.

[0073] Then, in operation S420, in response to the authorization query request, a record to be authorized is sent to the authorizer that sent the authorization query request, and the record to be authorized includes information of at least one remote authorization node. For example, the authorization system 102 can summarize the information of the remote authorization nodes involved in the transaction for which the authorizer has the authorization review qualification into a record to be authorized, and send it to the authorizer, based on the authorization qualification information of the authorizer in the authorization query request.

[0074] Next, in operation S430, based on the authorizer's selection operation on the remote authorization node in the authorization record, the remote authorization request corresponding to the selected remote authorization node is fed back to the authorizer. For example, after the authorizer selects the information of a certain remote authorization node, the detailed information of the remote authorization request corresponding to the remote authorization node (for example, transaction page information) can be sent from the database to the authorizer for the authorizer's review.

[0075] Then, in operation S440, the authorization result information obtained by the authorizer through the authorization review of the remote authorization request is obtained. After the authorizer performs the authorization approval or rejection operation in the interface of the authorizer client 103, the authorization system 102 can obtain the corresponding authorization result information.

[0076] Then, in operation S450, the state of the remote authorization node selected by the authorizer is updated using the authorization result information. Then, in operation S240, a response message may be sent to the requester of the remote authorization request corresponding to the remote authorization node to end the online processing of the remote authorization request.

[0077] In addition, if the authorized party does not perform the authorization pass or reject operation within a predetermined time after the remote authorization node is created, the authorization system 102 can determine that the status of the remote authorization node is an authorization timeout according to the above description, and then end the online waiting processing process of the remote authorization request corresponding to the remote authorization node through operation S240.

[0078] Figure 5 The figure schematically shows a conceptual flow chart of remote authorization in business transactions according to an embodiment of the present disclosure.

[0079] Figure 5 An example of the application process concept of the solution of the embodiment of the present disclosure in the bank authorization business and risk control business is illustrated, wherein the requester 501 is, for example, a front-end teller who logs in to the authorization system 102 through the requester client 101. The authorizer 503 can be, for example, an authorization teller who logs in to the authorization system 102 through the authorizer client 103. Among them, the shared storage model of the zookeeper service is used in the authorization system 102 to achieve the collaboration between the requester 501 and the authorizer 503. For example, for a remote authorization request, the zookeeper service creates a Zookeeper node 502. The authorizer 503 can store the authorization result of the remote authorization request in the Zookeeper node 502, and the requester 501 can obtain the response information of the authorization passed, the authorization failed or the authorization timed out from the Zookeeper node 502.

[0080] Specifically, in operation S51, the requester 501 determines whether to keep in touch with the Zookeeper node 502. If so, in operation S52, the requester 501 publishes the screen of the transaction page information applied for authorization, the identity verification result, the business image and other information to the Zookeeper node 502, and monitors the status update information of the Zookeeper node 502 by registering a listener with the Zookeeper node 502.

[0081] Next, in operation S53 , the authorizer 503 obtains the list of Zookeeper nodes that can be authorized for review (ie, the list to be authorized), and in operation S54 , after completing the authorization, submits the authorization result to the Zookeeper node 502 and updates the authorization data on the Zookeeper node 502 .

[0082] Then in operation S55, when the data on the Zookeeper node 502 changes, the Zookeeper node 502 sends status update information to the requester 501 that monitors this information. After the requester 501 receives the status update information, the authorization system 102 automatically deletes the node data on the Zookeeper.

[0083] According to the embodiments of the present disclosure, online processing can be implemented based on the Zookeeper data publish / subscribe function and the processing results (authorization passed, authorization failed, or authorization timed out) can be received in real time without the requesting party passively querying to obtain the authorization result, thereby reducing the anxiety caused by uncertainty when the passive authorization party is processing.

[0084] Figure 6 The following schematically shows a three-party interaction flow chart in a method for remote authorization in a business transaction according to an embodiment of the present disclosure. It should be noted that: Figure 6 What is shown is only an application example of the solution of the present disclosure and does not constitute a limitation to the present disclosure.

[0085] like Figure 6 As shown, when the requester uses the requester client 101 to process a large transaction, the requester first inputs the business in the business input page (S1 and S2), then the authorization page pops up on the business input page (S3), and then the requester submits the remote authorization (S4). When the requester submits the remote authorization, a remote authorization request will be sent to the authorization system 102 (S5); at the same time, the transaction of the requester client 101 is grayed out and locked (S6), and the response result is waited online.

[0086] After receiving the remote authorization request, the authorization system 102 obtains the transaction page information from the requesting client 101 (S7), records it in the form of HTML to the remote authorization application form, and stores it in the database (S8). At the same time, zookeeper is used to create a remote authorization node (S9). The remote authorization node may include a remote authorization request node and a remote authorization response node. The remote authorization node can be created according to the agreed rules to ensure that the node will not be repeated. The remote authorization request node can store authorization information such as teller, transaction code, authorization type, etc. The remote authorization request response node stores the authorization results: authorization passed and authorization failed. As a result, the amount of data that can be stored in the remote authorization node is small, and detailed data related to the transaction can be obtained by querying the database. At the same time, the status update information of the remote authorization node is monitored through PathChildrenCacheListener (S10).

[0087] The authorizer can use the interaction between the authorizer client 103 and the authorization system 102 to perform business authorization. For example, the authorizer can log in to the authorization system 102 through the authorizer client 103, and the remote authorization query interface (S11) can be displayed in the authorizer client 103. Then the authorizer can click to query in the remote authorization query interface (S12). Next, through the interaction with the authorization system 102 (S13 and S14), the authorized records to be authorized are obtained and displayed (S15). The authorized records are, for example, the list information of the remote authorization request node on zookeeper. The authorizer can query the remote authorization application form in the authorizer client 103 according to the authorized records, select the transaction content corresponding to the node to be reviewed, and then complete the transaction authorization approval after reviewing the transaction page information (S16~S19). At this time, the authorization system 102 updates the authorization result under the zookeeper remote authorization response node directory (S20).

[0088] After PathChildrenCacheListener listens to the authorization result, the authorization system 102 sends the authorization result and displays it on the transaction page of the requesting client (S21). If the authorization is passed, the transaction page is restored and the transaction process continues to run; if the authorization is not passed, the transaction stops (S23). At the same time, the authorization system 102 deletes the zookeeper-related authorization node information (S22).

[0089] In addition, if the online waiting time of the requester exceeds the predetermined time after submitting the remote authorization request (S5), the authorization system 102 will send authorization timeout information to the requester client 101 (S21), end the transaction, and delete the created remote authorization node (S22) accordingly. If the transaction is to be authorized again, it is necessary to re-initiate the request review process for the transaction.

[0090] Based on the methods and methods for remote authorization in business transactions provided in the above embodiments, the present disclosure also provides a device for remote authorization in business transactions. Figure 7 The device is described in detail.

[0091] Figure 7 The block diagram of the apparatus 700 for remote authorization in business transactions according to an embodiment of the present disclosure is schematically shown. According to an embodiment of the present disclosure, the apparatus 700 can be arranged in the authorization system 102 to implement the reference Figure 2 to Figure 6 A method for remote authorization in a business transaction is described.

[0092] like Figure 7As shown, according to some embodiments of the present disclosure, the system 700 for remote authorization in business transactions includes a first receiving module 710 , a creating module 720 , a monitoring module 730 and a responding module 740 .

[0093] The first receiving module 710 may, for example, perform operation S210 to receive M remote authorization requests, where the M remote authorization requests come from M requesting parties respectively, and M is an integer greater than or equal to 1.

[0094] The creation module 720 can, for example, perform operation S220, which is used to create a remote authorization node corresponding to the remote authorization request in response to each remote authorization request received; wherein the remote authorization node is used to provide one of the N authorized parties with an entry for authorization review of the remote authorization request, and to record the authorization result to update the status of the remote authorization node, wherein N is an integer greater than or equal to 1.

[0095] The monitoring module 730 may, for example, perform operation S230 to monitor the status update information of the remote authorization node within a predetermined period of time after each remote authorization node is created; wherein the status update information includes one of authorization passed, authorization failed, or authorization timed out.

[0096] The response module 740 may, for example, perform operation S240 to, in response to monitoring status update information of each remote authorization node, feed back the status update information to the requester of the remote authorization request corresponding to the remote authorization node, so as to respond to the remote authorization request.

[0097] According to some other embodiments of the present disclosure, the device 700 may further include a monitoring registration module 750 , a transaction information acquisition module 760 , and a node deletion module 770 .

[0098] The monitoring registration module 750 may, for example, perform operation S330 to register a listener with each remote authorization node before monitoring the status update information of the remote authorization node, where the listener is used to monitor the status update information of the remote authorization node.

[0099] The transaction information acquisition module 760 can, for example, perform operation S320 to obtain transaction record information corresponding to the remote authorization request in response to each received remote authorization request. The authorization review of the remote authorization request includes the authorization review of the transaction record information corresponding to the remote authorization request. In one embodiment, the transaction information acquisition module 760 can be used to obtain the transaction page information corresponding to the remote authorization request in the client of the requester of the remote authorization request. In another embodiment, the transaction information acquisition module 760 can also be used to store the transaction page information in the form of html in a database that communicates with the remote authorization node.

[0100] The node deletion module 770 may, for example, perform operation S350 to delete the remote authorization node after feeding back the status update information to the requester of the remote authorization request corresponding to the remote authorization node.

[0101] According to some further embodiments of the present disclosure, the device 700 may further include a second receiving module 780 , a record sending module 790 , an audit interaction module 7100 , a result acquisition module 7110 and a node update module 7120 .

[0102] The second receiving module 780 may, for example, perform operation S410 to receive at least one authorization query request, wherein each authorization query request comes from one of the N authorizing parties.

[0103] The record sending module 790 may, for example, perform operation S420 to send, in response to the authorization query request, a record to be authorized to the authorizer that sent the authorization query request, where the record to be authorized includes information of at least one remote authorization node.

[0104] The audit interaction module 7100 may, for example, perform operation S430 to feed back to the authorizer a remote authorization request corresponding to the selected remote authorization node based on the authorizer's selection operation on the remote authorization node in the authorization record.

[0105] The result acquisition module 7110 may, for example, execute operation S440 to obtain authorization result information obtained by the authorizer through authorization review of the remote authorization request.

[0106] The node updating module 7120 may, for example, perform operation S450 to update the status of the remote authorization node selected by the authorizer using the authorization result information.

[0107] According to an embodiment of the present disclosure, any multiple modules among the first receiving module 710, the creating module 720, the monitoring module 730, the responding module 740, the monitoring registration module 750, the transaction information obtaining module 760, the node deleting module 770, the second receiving module 780, the record sending module 790, the audit interaction module 7100, the result obtaining module 7110 and the node updating module 7120 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first receiving module 710, the creation module 720, the listening module 730, the response module 740, the listening registration module 750, the transaction information acquisition module 760, the node deletion module 770, the second receiving module 780, the record sending module 790, the audit interaction module 7100, the result acquisition module 7110 and the node update module 7120 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging circuits, or can be implemented in any one of the three implementation methods of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the first receiving module 710, the creation module 720, the listening module 730, the response module 740, the listening registration module 750, the transaction information acquisition module 760, the node deletion module 770, the second receiving module 780, the record sending module 790, the audit interaction module 7100, the result acquisition module 7110 and the node update module 7120 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is executed.

[0108] Figure 8 A block diagram of an electronic device 800 suitable for implementing a method for remote authorization in a business transaction according to an embodiment of the present disclosure is schematically shown.

[0109] like Figure 8As shown, the electronic device 800 according to an embodiment of the present disclosure includes a processor 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 to a random access memory (RAM) 803. The processor 801 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 801 may also include an onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0110] In RAM 803, various programs and data required for the operation of electronic device 800 are stored. Processor 801, ROM 802 and RAM 803 are connected to each other via bus 804. Processor 801 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 802 and / or RAM 803. It should be noted that the program can also be stored in one or more memories other than ROM 802 and RAM 803. Processor 801 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0111] According to an embodiment of the present disclosure, the electronic device 800 may further include an input / output (I / O) interface 805, which is also connected to the bus 804. The electronic device 800 may further include one or more of the following components connected to the I / O interface 805: an input portion 806 including a keyboard, a mouse, etc.; an output portion 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 808 including a hard disk, etc.; and a communication portion 809 including a network interface card such as a LAN card, a modem, etc. The communication portion 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage portion 808 as needed.

[0112] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0113] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 802 and / or RAM 803 described above and / or one or more memories other than ROM 802 and RAM 803.

[0114] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method provided by the embodiment of the present disclosure.

[0115] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 801. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0116] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 809, and / or installed from a removable medium 811. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0117] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the processor 801, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0118] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0119] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0120] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0121] The embodiments of the present disclosure are described above. However, these embodiments are only for the purpose of illustration and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for remote authorization in a business transaction, comprising: Receiving M remote authorization requests, wherein the M remote authorization requests are respectively from M requesting parties, and M is an integer greater than or equal to 1; wherein each requesting party enters an online waiting state after sending a remote authorization request, and does not initiate a new remote authorization request before the remote authorization request is responded to; In response to each of the received remote authorization requests, create a remote authorization node corresponding to the remote authorization request; wherein the remote authorization node is used to provide one of the N authorizers with an entry for authorization review of the remote authorization request, and record the authorization result to update the state of the remote authorization node, wherein N is an integer greater than or equal to 1; Within a predetermined time period after each remote authorization node is created, monitoring the status update information of the remote authorization node; wherein the status update information includes one of authorization passed, authorization failed, or authorization timed out; and In response to monitoring the status update information of each remote authorization node, feeding back the status update information to the requester of the remote authorization request corresponding to the remote authorization node, so as to respond to the remote authorization request; Wherein, in response to each received remote authorization request, creating a remote authorization node corresponding to the remote authorization request includes: encoding the remote authorization node according to the request time, business personnel information and transaction information of the remote authorization request.

2. The method according to claim 1, wherein: The method further comprises: receiving at least one authorization query request, wherein each of the authorization query requests comes from one of the N authorizing parties; In response to the authorization query request, sending a record to be authorized to the authorizer that sent the authorization query request, wherein the record to be authorized includes information of at least one remote authorization node; Based on the selection operation of the authorizer on the remote authorization node in the record to be authorized, feeding back to the authorizer the remote authorization request corresponding to the selected remote authorization node; Obtaining authorization result information obtained by the authorizer through authorization review of the remote authorization request; and The authorization result information is used to update the status of the remote authorization node selected by the authorizer.

3. The method according to claim 2, wherein: The creating of the remote authorization node corresponding to the remote authorization request comprises: Use Zookeeper to create the remote authorization node.

4. The method according to claim 1, wherein: The remote authorization node includes a remote authorization request node and a remote authorization response node; wherein, The remote authorization request node is used to provide one of the N authorizers with an entry for performing authorization review on the remote authorization request; and The remote authorization response node is used to record the authorization result to update the state of the remote authorization node.

5. The method according to claim 1, wherein: Before monitoring the status update information of the remote authorization node, the method further includes: A listener is registered with each of the remote authorization nodes, where the listener is used to listen to the status update information of the remote authorization node.

6. The method according to any one of claims 1 to 5, wherein: The method further comprises: In response to each received remote authorization request, obtaining transaction record information corresponding to the remote authorization request; The performing authorization review on the remote authorization request includes performing authorization review on the transaction record information corresponding to the remote authorization request.

7. The method according to claim 6, wherein: The acquiring of the transaction record information corresponding to the remote authorization request includes: Acquire transaction page information corresponding to the remote authorization request in the client of the requester of the remote authorization request.

8. The method according to claim 7, wherein: The acquiring of the transaction record information corresponding to the remote authorization request further includes: The transaction page information is stored in HTML format in a database that communicates with the remote authorization node.

9. The method according to claim 1, wherein: After feeding back the status update information to the requester of the remote authorization request corresponding to the remote authorization node, the method further includes: The remote authorization node is deleted.

10. An apparatus for remote authorization in a business transaction, comprising: A first receiving module is configured to receive M remote authorization requests, wherein the M remote authorization requests are respectively from M requesting parties, and M is an integer greater than or equal to 1; wherein each requesting party enters an online waiting state after sending a remote authorization request, and does not initiate a new remote authorization request before the remote authorization request is responded to; A creation module, configured to create a remote authorization node corresponding to each remote authorization request in response to each received remote authorization request; wherein the remote authorization node is used to provide one of the N authorized parties with an entry for authorization review of the remote authorization request, and record the authorization result to update the state of the remote authorization node, wherein N is an integer greater than or equal to 1; wherein the creation module is specifically configured to: encode the remote authorization node according to the request time, business personnel information and transaction information of the remote authorization request; A monitoring module, used to monitor the status update information of each remote authorization node within a predetermined time after the creation of each remote authorization node; wherein the status update information includes one of authorization passed, authorization failed or authorization timed out; A response module is used for responding to the state update information of each remote authorization node monitored, feeding back the state update information to the requester of the remote authorization request corresponding to the remote authorization node, so as to respond to the remote authorization request.

11. An electronic device, comprising: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 9.

Images