A business processing method, apparatus, electronic device, and computer-readable medium

By receiving business processing requests, determining dimension identifiers and user identifiers, executing degradation logic to determine the target transaction type identifier, determining the target transaction authentication workflow, obtaining authentication result data, and processing business processing requests, the problem of high coupling between service identity management and business is solved, and the implementation difficulty and cost are reduced.

CN117041959BActive Publication Date: 2026-11-10CHINA CONSTRUCTION BANK +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311031749.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-08-16
Publication Date
2026-11-10
Estimated Expiration
2043-08-16

AI Technical Summary

Technical Problem

Existing service identity management is heavily coupled with business logic in distributed systems. Each service needs to associate multiple levels of rules with each transaction to further determine permissions, which makes implementation difficult and costly.

Method used

By receiving a business processing request, the system determines the dimension identifier and the user identifier, executes degradation logic based on the dimension identifier to determine the target transaction type identifier, determines the target transaction authentication workflow based on the target transaction type identifier and the user identifier, executes the target transaction authentication workflow, obtains authentication result data, and determines the request processing method to process the business processing request based on the authentication result data.

Benefits of technology

This reduces the difficulty of implementing service identity management and lowers the cost of service identity management during business processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117041959B_ABST
    Figure CN117041959B_ABST
Patent Text Reader

Abstract

This application discloses a business processing method, apparatus, electronic device, and computer-readable medium, relating to the field of computer technology. One specific implementation includes receiving a business processing request and determining the corresponding dimension identifier and user identifier; executing degradation logic based on the dimension identifier to determine a target transaction type identifier; determining a target transaction authentication workflow based on the target transaction type identifier and user identifier; executing the target transaction authentication workflow to obtain authentication result data; determining a request processing method based on the authentication result data; and processing the business processing request based on the request processing method. This reduces the difficulty of implementing service identity management and lowers the cost of service identity management during business processing.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a business processing method, apparatus, electronic device, and computer-readable medium. Background Technology

[0002] Currently, in distributed systems, traffic can be divided into north-south and east-west dimensions. North-south traffic authentication refers to traffic undergoing permission checks through a microservice gateway before being forwarded to the microservice. East-west traffic authentication refers to microservices calling each other through a registry center, where permission checks are performed at the service provider. Current service identity management is heavily coupled with business logic; each service needs to associate multiple levels of rules with the transaction for further permission checks, making implementation difficult and costly. Summary of the Invention

[0003] In view of this, embodiments of this application provide a business processing method, apparatus, electronic device, and computer-readable medium that can solve the problems of existing service identity management being severely coupled with business operations, requiring each service to associate multiple levels of rules for this transaction to further determine permissions, making implementation difficult and costly.

[0004] To achieve the above objectives, according to one aspect of an embodiment of this application, a business processing method is provided, comprising:

[0005] Receive business processing requests and determine the corresponding dimension identifier and user identifier;

[0006] Degradation logic is executed based on the dimension identifier to determine the target transaction type identifier;

[0007] Based on the target transaction type identifier and user identifier, determine the target transaction authentication workflow;

[0008] Execute the target transaction authentication workflow and obtain the authentication result data;

[0009] Based on the authentication results, determine the request processing method and process the business processing request accordingly.

[0010] Optionally, degradation logic is performed based on the dimension identifier to determine the target transaction type identifier, including:

[0011] Determine the dimension corresponding to the dimension identifier. In response to the dimension being a component dimension, execute the degradation logic from the component dimension to the transaction dimension to determine the target transaction type identifier in the transaction dimension.

[0012] Optionally, degradation logic is executed from the component dimension to the transaction dimension to determine the target transaction type identifier, including:

[0013] Execute the logic to retrieve the service identifier corresponding to the dimension identifier;

[0014] Based on the obtained service identifier, determine the target transaction type identifier.

[0015] Optionally, the target transaction authentication workflow is defined, including:

[0016] Determine the corresponding workflow list based on the target transaction type identifier;

[0017] Based on the user identifier, the user level is determined, and then the corresponding target transaction authentication workflow is determined from the workflow list according to the user level.

[0018] Optionally, the target transaction authentication workflow is executed, including:

[0019] Obtain the service dynamic identity token and its corresponding validity period;

[0020] The security encryption component is invoked to decrypt the service dynamic identity token, and then the legality is verified based on the decrypted data, the validity is verified based on the expiration date, and the permissions are verified based on the user identifier.

[0021] Optionally, before invoking the secure encryption component to decrypt the service dynamic identity token, the method further includes:

[0022] Obtain the service metadata corresponding to the business processing request, and then generate a service dynamic identity token based on the service metadata through a secure encryption component, and set the validity period of the service dynamic identity token.

[0023] Optionally, business processing requests are processed based on request processing methods, including:

[0024] In response to a request being processed as a pass request, the business processing request is sent to the target business processing node;

[0025] The response method is to intercept the request, which will then intercept the business processing request and return a request exception message.

[0026] In addition, this application also provides a business processing apparatus, including:

[0027] The receiving unit is configured to receive service processing requests and determine the corresponding dimension identifier and user identifier.

[0028] The transaction type identifier determination unit is configured to execute degradation logic based on the dimension identifier in order to determine the target transaction type identifier;

[0029] The workflow determination unit is configured to determine the target transaction authentication workflow based on the target transaction type identifier and the user identifier.

[0030] The execution unit is configured to execute the target transaction authentication workflow and obtain authentication result data.

[0031] The request processing unit is configured to determine the request processing method based on the authentication result data, and process the business processing request based on the request processing method.

[0032] Optionally, the transaction type identifier determination unit is further configured to:

[0033] Determine the dimension corresponding to the dimension identifier. In response to the dimension being a component dimension, execute the degradation logic from the component dimension to the transaction dimension to determine the target transaction type identifier in the transaction dimension.

[0034] Optionally, the transaction type identifier determination unit is further configured to:

[0035] Execute the logic to retrieve the service identifier corresponding to the dimension identifier;

[0036] Based on the obtained service identifier, determine the target transaction type identifier.

[0037] Optionally, the workflow determination unit is further configured to:

[0038] Determine the corresponding workflow list based on the target transaction type identifier;

[0039] Based on the user identifier, the user level is determined, and then the corresponding target transaction authentication workflow is determined from the workflow list according to the user level.

[0040] Optionally, the workflow determination unit is further configured to:

[0041] Obtain the service dynamic identity token and its corresponding validity period;

[0042] The security encryption component is invoked to decrypt the service dynamic identity token, and then the legality is verified based on the decrypted data, the validity is verified based on the expiration date, and the permissions are verified based on the user identifier.

[0043] Optionally, the workflow determination unit is further configured to:

[0044] Obtain the service metadata corresponding to the business processing request, and then generate a service dynamic identity token based on the service metadata through a secure encryption component, and set the validity period of the service dynamic identity token.

[0045] Optionally, the request processing unit is further configured to:

[0046] In response to a request being processed as a pass request, the business processing request is sent to the target business processing node;

[0047] The response method is to intercept the request, which will then intercept the business processing request and return a request exception message.

[0048] In addition, this application also provides a business processing electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, enable the one or more processors to implement the business processing method described above.

[0049] In addition, this application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the business processing method described above.

[0050] To achieve the above objectives, according to another aspect of the embodiments of this application, a computer program product is provided.

[0051] A computer program product according to an embodiment of this application includes a computer program that, when executed by a processor, implements the business processing method provided in the embodiment of this application.

[0052] One embodiment of the above invention has the following advantages or beneficial effects: This application receives a business processing request, determines the corresponding dimension identifier and user identifier; executes degradation logic based on the dimension identifier to determine the target transaction type identifier; determines the target transaction authentication workflow based on the target transaction type identifier and user identifier; executes the target transaction authentication workflow to obtain authentication result data; and determines the request processing method based on the authentication result data, and processes the business processing request based on the request processing method. This reduces the difficulty of implementing service identity management and lowers the service identity management cost during business processing.

[0053] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0054] The accompanying drawings are provided to better understand this application and do not constitute an undue limitation thereof. Wherein:

[0055] Figure 1 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application;

[0056] Figure 2 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application;

[0057] Figure 3 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application;

[0058] Figure 4 This is a schematic diagram of the main units of a service processing apparatus according to an embodiment of this application;

[0059] Figure 5 This is an exemplary system architecture diagram to which embodiments of this application can be applied;

[0060] Figure 6 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers in the embodiments of this application. Detailed Implementation

[0061] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These embodiments should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description. It should be noted that the collection, analysis, use, transmission, and storage of user personal information involved in the technical solutions of this application comply with relevant laws and regulations, are used for legitimate and reasonable purposes, are not shared, disclosed, or sold outside of these legitimate uses, and are subject to supervision and management by regulatory authorities. Necessary measures should be taken to prevent unauthorized access to such personal information data, ensure that personnel authorized to access personal information data comply with relevant laws and regulations, and ensure the security of user personal information. Once this user personal information data is no longer needed, the risk should be minimized by restricting or even prohibiting data collection and / or deleting the data.

[0062] When used, including in certain relevant applications, data is deidentified to protect user privacy, for example by removing specific identifiers, controlling the amount or specificity of stored data, controlling how data is stored, and / or other methods.

[0063] Figure 1 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application, as shown below. Figure 1 As shown, the business processing methods include:

[0064] Step S101: Receive the business processing request and determine the corresponding dimension identifier and user identifier.

[0065] In this embodiment, the execution entity of the business processing method (e.g., a server) can receive business processing requests via wired or wireless connections. A business processing request may be, for example, a transaction authentication request. Transaction authentication: In a distributed financial scenario, unified access control is implemented for calls between systems, and components, services, and transactions are classified and managed hierarchically through authentication rules. After receiving a business processing request, the execution entity can obtain the dimension identifier and user identifier carried in the request. Specifically, the dimension identifier can, for example, represent the transaction level requiring authentication, such as component-level, service-level, or transaction-level. Component-level authentication applies to all services and transactions under the component, service-level authentication applies to all transactions under the service, and transaction-level authentication applies only to the current transaction. The user identifier may be, for example, the ID or name of the user initiating the current business processing request; this embodiment does not specifically limit the user identifier.

[0066] Step S102: Execute downgrade logic based on dimension identifier to determine the target transaction type identifier.

[0067] In this application embodiment, JSON Web Token (JWT) is a network token technology that uses JSON format to transmit data. It is an open industry standard (RFC 7519) that defines a concise, self-contained protocol format for transmitting JSON objects between communicating parties. The transmitted information is digitally signed to be verifiable and trustworthy. It can be signed using the HMAC algorithm or RSA public / private key pairs to prevent content tampering. The business processing method in this application is based on the unified security encryption component SA, extending JWT to solve security issues such as service identity tampering and leakage. Furthermore, it preprocesses authentication rules at all levels, sinking component-level rules down to the service level, and service-level rules down to the transaction level to obtain specific transaction type identifiers.

[0068] The embodiments of this application can solve the problem of associating transaction requests with multi-level rules, and complete the steps of service identity token generation, service identity recognition and verification, and transaction permission judgment in a non-intrusive manner using plugins and agent.

[0069] Step S103: Determine the target transaction authentication workflow based on the target transaction type identifier and user identifier.

[0070] The executing entity can determine the corresponding workflow list based on the user identifier, and then match the target transaction type identifier with each workflow in the workflow list. The matching workflow can then be used as the target transaction authentication workflow.

[0071] Step S104: Execute the target transaction authentication workflow and obtain the authentication result data.

[0072] Specifically, the target transaction authentication workflow includes: obtaining the service dynamic identity token and its corresponding validity period; calling the security encryption component to decrypt the service dynamic identity token, and then performing legality verification based on the decrypted data, validity verification based on the validity period, and permission verification based on the user identifier.

[0073] Before calling the security encryption component to decrypt the service dynamic identity token, the business processing method also includes: obtaining the service metadata corresponding to the business processing request, then generating the service dynamic identity token through the security encryption component based on the service metadata, and setting the validity period of the service dynamic identity token.

[0074] For example, when issuing a service identity, a dynamic service identity token (Token) is generated using an encryption algorithm based on the service metadata, and an expiration date is set. Service identity verification: The dynamic service identity token is decrypted using a secure encryption component (SA) to verify the legitimacy and validity of the service identity. Specifically, during service identity generation, the SA component is used to extend the JWT to address the issues of token tampering and cracking. By obtaining the dynamic service identity token and its corresponding expiration date, it is possible to verify whether the token has expired based on the expiration date and whether the user has transaction permissions based on the user identifier. Specifically, the user identifier can be verified against a list of registered user identifiers to determine if the user identifier is in the list; if so, the permission verification passes; otherwise, the permission verification fails.

[0075] A dynamic service identity token is generated using an encryption algorithm based on service metadata, and its validity period can be set. The JWT is extended using the secure encryption component SA during service identity generation.

[0076] The authentication result data can correspond to whether the permission verification passed or failed.

[0077] Step S105: Determine the request processing method based on the authentication result data, and process the business processing request based on the request processing method.

[0078] Request processing methods can include blocking requests and allowing requests. When the authentication result data corresponds to a successful permission check, the corresponding request processing method is to allow the request; when the authentication result data corresponds to a failed permission check, the corresponding request processing method is to block the request. The business processing request is either allowed or blocked depending on the request processing method.

[0079] This embodiment receives a business processing request, determines the corresponding dimension identifier and user identifier, executes degradation logic based on the dimension identifier to determine the target transaction type identifier, determines the target transaction authentication workflow based on the target transaction type identifier and user identifier, executes the target transaction authentication workflow to obtain authentication result data, and determines the request processing method based on the authentication result data, and processes the business processing request based on the request processing method. This reduces the difficulty of implementing service identity management and lowers the service identity management cost during business processing.

[0080] Figure 2 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application, such as... Figure 2 As shown, the business processing methods include:

[0081] Step S201: Receive the business processing request and determine the corresponding dimension identifier and user identifier.

[0082] Step S202: Determine the dimension corresponding to the dimension identifier. In response to the dimension being a component dimension, execute the degradation logic from the component dimension to the transaction dimension to determine the target transaction type identifier in the transaction dimension.

[0083] The dimensions corresponding to the dimension identifier can include component dimensions, service dimensions, and transaction dimensions, with the dimensions decreasing in that order. When the dimension identifier corresponds to a component dimension, since the component dimension has lower-level service and transaction dimensions, it is possible to perform a downgrade from the component dimension to the service dimension, and then from the service dimension to the transaction dimension, in order to determine the corresponding target transaction type identifier.

[0084] Specifically, the degradation logic from the component dimension to the transaction dimension is executed to determine the target transaction type identifier, including: executing the logic to obtain the service identifier corresponding to the dimension identifier; and determining the target transaction type identifier based on the obtained service identifier.

[0085] A component identifier can correspond to multiple service identifiers. A service identifier can correspond to multiple target transaction type identifiers. One or more target transaction type identifiers can be obtained from the component identifier.

[0086] Step S203: Determine the target transaction authentication workflow based on the target transaction type identifier and user identifier.

[0087] The number of target transaction type identifiers can be one or more. The executing entity can determine the corresponding target transaction types based on the determined target transaction type identifiers, and then determine the target transaction authentication workflow corresponding to each target transaction type.

[0088] Step S204: Execute the target transaction authentication workflow and obtain the authentication result data.

[0089] After determining the authentication workflow for each target transaction, the executing entity can generate asynchronous tasks based on each target transaction authentication workflow, call the thread pool to execute the generated asynchronous tasks, and obtain authentication result data, thereby improving business processing efficiency and accuracy.

[0090] Step S205: Determine the request processing method based on the authentication result data, and process the business processing request based on the request processing method.

[0091] Based on the authentication results, which indicate whether permission verification passed or failed, the request processing method is determined, such as allowing or blocking the request. This reduces the difficulty of implementing service identity management and lowers the cost of service identity management during business processing.

[0092] Figure 3 This is a schematic diagram of the main flow of a business processing method according to an embodiment of this application, such as... Figure 3 As shown, the business processing methods include:

[0093] Step S301: Receive the business processing request and determine the corresponding dimension identifier and user identifier.

[0094] Step S302: Execute downgrade logic based on dimension identifier to determine the target transaction type identifier.

[0095] Dimensional identifiers can be used to characterize the transaction level that requires authentication, such as component level, service level, or transaction level. A component is a collection of aggregated services (such as a bank's core component managing fund account-related services, or a customer information component managing user information-related services), a service is a collection of similar interfaces (such as query services or modification services), and a transaction is a specific interface operation (such as a transfer operation or a balance query operation).

[0096] Step S303: Determine the corresponding workflow list based on the target transaction type identifier.

[0097] The target transaction type identifier can be, for example, zz (representing a transfer transaction) or cx (representing a query transaction). Each transaction type identifier can correspond to a specific workflow list. The workflow list can then include various workflows corresponding to different users.

[0098] Step S304: Based on the user identifier, determine the user level, and then determine the corresponding target transaction authentication workflow from the workflow list according to the user level.

[0099] After determining the workflow list, the executing entity can further identify the corresponding workflow based on the user level corresponding to the user identifier, and then use it as the target transaction authentication workflow. This makes the workflow used more accurate and improves the accuracy of business processing.

[0100] Step S305: Execute the target transaction authentication workflow and obtain the authentication result data.

[0101] Step S306: Determine the request processing method based on the authentication result data, and process the business processing request based on the request processing method.

[0102] Specifically, processing business processing requests based on request processing methods includes: in response to a request processing method of allowing a request, sending the business processing request to the target business processing node; in response to a request processing method of intercepting a request, intercepting the business processing request and returning request exception information.

[0103] The target processing node can be the work terminal corresponding to the offline business processing staff, or it can be a terminal for further review. This application embodiment does not specifically limit the target processing node. This application embodiment implements transaction authentication through a microservice gateway plugin and a microservice agent proxy method. No business modifications are required, it is transparent to the business, and reduces business coupling.

[0104] The execution entity in this embodiment can be configured with three modules: a service metadata management module, an authentication control center module, and an agent and gateway plugin. The authentication control center module relies on the service metadata module for configuring authentication rules; the agent and gateway plugin rely on the authentication control center module for obtaining and dynamically updating authentication rules. The service metadata management module is responsible for defining and managing service metadata in the distributed system, maintaining multi-level relationships between components, services, and transactions, and providing data support for dynamic service identity creation and authentication rule configuration. The authentication control center module is used for configuring authentication rules for microservice gateways and service providers, as well as distributing, changing, and pushing related data. The agent and gateway plugin are responsible for intercepting microservice transaction calls and completing service identity recognition, verification, and call permission judgment.

[0105] The authentication control center module retrieves all service metadata from the service metadata management module, performs filtering and screening operations, and displays it on the page. Users can configure and save authentication settings for service providers based on the service metadata information within the authentication control center module. Configuration can be done at any level, including components, services, and transactions. The final authentication rule data is then structurally transformed and persistently stored in the database. The authentication control center module distributes and synchronizes the stored authentication rule data to the gateway plugin and service providers, with the data cached in local memory. When a business processing request arrives, the gateway plugin and service provider (e.g., a proxy agent) preprocess the request, match the associated transaction authentication rules from the cache, further verify and identify the service consumer's service identity, and finally execute the authentication rule judgment, deciding whether to allow the request based on the authentication result.

[0106] In financial transaction scenarios, transaction authentication ensures the security of dynamic service identities, complying with financial-grade security standards. By defining unified authentication rules and preprocessing the rule data, a single transaction can be automatically associated with multiple levels (components, services, transactions) of business processing methods. The business processing methods in this embodiment are applied to the financial system in a loosely coupled and non-intrusive manner, transparent to the business, and with low integration costs. The business processing methods in this embodiment combine the unified security encryption component SA and JWT authentication to solve the problem of service identity tampering and leakage, meeting the security standards of financial scenarios. Simultaneously, the definition and preprocessing of authentication rules enable a single transaction to be automatically associated with relevant authentication methods; and these authentication methods support transaction authentication in a loosely coupled and non-intrusive manner.

[0107] Figure 4 This is a schematic diagram of the main units of a service processing apparatus according to an embodiment of this application. Figure 4 As shown, the business processing device 400 includes a receiving unit 401, a transaction type identifier determination unit 402, a workflow determination unit 403, an execution unit 404, and a request processing unit 405.

[0108] The receiving unit 401 is configured to receive service processing requests and determine the corresponding dimension identifier and user identifier.

[0109] The transaction type identifier determination unit 402 is configured to perform degradation logic based on the dimension identifier to determine the target transaction type identifier.

[0110] Workflow determination unit 403 is configured to determine the target transaction authentication workflow based on the target transaction type identifier and the user identifier.

[0111] Execution unit 404 is configured to execute the target transaction authentication workflow and obtain authentication result data.

[0112] The request processing unit 405 is configured to determine the request processing method based on the authentication result data, and process the business processing request based on the request processing method.

[0113] In some embodiments, the transaction type identifier determination unit 402 is further configured to: determine the dimension corresponding to the dimension identifier, and in response to the dimension being a component dimension, execute a degradation logic from the component dimension to the transaction dimension to determine the target transaction type identifier in the transaction dimension.

[0114] In some embodiments, the transaction type identifier determination unit 402 is further configured to: execute the logic of obtaining the service identifier corresponding to the dimension identifier; and determine the target transaction type identifier based on the obtained service identifier.

[0115] In some embodiments, the workflow determination unit 403 is further configured to: determine the corresponding workflow list based on the target transaction type identifier; determine the user level based on the user identifier; and then determine the corresponding target transaction authentication workflow from the workflow list based on the user level.

[0116] In some embodiments, the workflow determination unit 403 is further configured to: obtain a service dynamic identity token and its corresponding validity period; call a security encryption component to decrypt the service dynamic identity token, and then perform a legality check based on the decrypted data, a validity check based on the validity period, and a permission check based on the user identifier.

[0117] In some embodiments, the workflow determination unit 403 is further configured to: obtain service metadata corresponding to the business processing request, and then generate a service dynamic identity token based on the service metadata through a security encryption component, and set the validity period of the service dynamic identity token.

[0118] In some embodiments, the request processing unit 405 is further configured to: send a business processing request to the target business processing node in response to a request processing mode of allowing the request; and intercept the business processing request and return request exception information in response to a request processing mode of intercepting the request.

[0119] It should be noted that the business processing method and business processing device in this application are related in terms of specific implementation content, so repeated content will not be described again.

[0120] Figure 5 An exemplary system architecture 500 is shown that can be applied to the business processing method or business processing apparatus of the embodiments of this application.

[0121] like Figure 5As shown, system architecture 500 may include terminal devices 501, 502, and 503, a network 504, and a server 505. Network 504 serves as the medium for providing communication links between terminal devices 501, 502, and 503 and server 505. Network 504 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0122] Users can use terminal devices 501, 502, and 503 to interact with server 505 via network 504 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 501, 502, and 503, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0123] Terminal devices 501, 502, and 503 can be various electronic devices with business processing screens and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0124] Server 505 can be a server providing various services, such as a backend management server supporting business processing requests submitted by users using terminal devices 501, 502, and 503 (this is just an example). The backend management server can receive business processing requests, determine the corresponding dimension identifier and user identifier; execute degradation logic based on the dimension identifier to determine the target transaction type identifier; determine the target transaction authentication workflow based on the target transaction type identifier and user identifier; execute the target transaction authentication workflow and obtain authentication result data; and determine the request processing method based on the authentication result data, and process the business processing request accordingly. This reduces the difficulty of implementing service identity management and lowers the cost of service identity management during business processing.

[0125] It should be noted that the business processing method provided in this application embodiment is generally executed by server 505, and correspondingly, the business processing device is generally set in server 505.

[0126] It should be understood that Figure 5 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0127] The following is for reference. Figure 6 It shows a schematic diagram of the structure of a computer system 600 suitable for implementing a terminal device according to the embodiments of this application. Figure 6 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0128] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 602 or programs loaded from storage section 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the computer system 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0129] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0130] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs the functions defined above in the system of this application.

[0131] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. Computer-readable storage media can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0132] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0133] The units described in the embodiments of this application can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor may be described as including a receiving unit, a transaction type identifier determining unit, a workflow determining unit, an execution unit, and a request processing unit. The names of these units do not necessarily limit the specific unit itself.

[0134] In another aspect, this application also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to receive a business processing request, determine the corresponding dimension identifier and user identifier; execute degradation logic based on the dimension identifier to determine the target transaction type identifier; determine the target transaction authentication workflow based on the target transaction type identifier and user identifier; execute the target transaction authentication workflow to obtain authentication result data; determine the request processing method based on the authentication result data; and process the business processing request based on the request processing method.

[0135] The computer program product of this application includes a computer program that, when executed by a processor, implements the business processing method in the embodiments of this application.

[0136] The technical solution according to the embodiments of this application can reduce the difficulty of implementing service identity management and reduce the service identity management cost in the business process.

[0137] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A business processing method, characterized in that, include: Receive business processing requests and determine the corresponding dimension identifier and user identifier; Based on the dimension identifier, a downgrade logic is executed to determine the target transaction type identifier; Based on the target transaction type identifier and the user identifier, the target transaction authentication workflow is determined; Execute the target transaction authentication workflow and obtain the authentication result data; Based on the authentication result data, a request processing method is determined, and the business processing request is processed based on the request processing method.

2. The method according to claim 1, characterized in that, The step of performing degradation logic based on the dimension identifier to determine the target transaction type identifier includes: The dimension corresponding to the dimension identifier is determined. In response to the dimension being a component dimension, a degradation logic from the component dimension to the transaction dimension is executed to determine the target transaction type identifier in the transaction dimension.

3. The method according to claim 2, characterized in that, The execution of the degradation logic from the component dimension to the transaction dimension to determine the target transaction type identifier includes: Execute the logic to obtain the service identifier corresponding to the dimension identifier; Based on the obtained service identifier, the target transaction type identifier is determined.

4. The method according to claim 1, characterized in that, The workflow for determining the authentication of the target transaction includes: Based on the target transaction type identifier, determine the corresponding workflow list; Based on the user identifier, the user level is determined, and then the corresponding target transaction authentication workflow is determined from the workflow list according to the user level.

5. The method according to claim 1, characterized in that, The execution of the target transaction authentication workflow includes: Obtain the service dynamic identity token and its corresponding validity period; The security encryption component is invoked to decrypt the service dynamic identity token, and then the legality is verified based on the decrypted data, the validity is verified based on the validity period, and the permission is verified based on the user identifier.

6. The method according to claim 5, characterized in that, Before invoking the security encryption component to decrypt the service dynamic identity token, the method further includes: Obtain the service metadata corresponding to the business processing request, and then generate a service dynamic identity token based on the service metadata through a security encryption component, and set the validity period of the service dynamic identity token.

7. The method according to claim 1, characterized in that, The process of processing the business processing request based on the aforementioned request processing method includes: In response to the request processing method being a release request, the business processing request is sent to the target business processing node; In response to the request handling method being request interception, the business processing request is intercepted, and request exception information is returned.

8. A business processing device, characterized in that, include: The receiving unit is configured to receive service processing requests and determine the corresponding dimension identifier and user identifier. The transaction type identifier determination unit is configured to execute downgrade logic based on the dimension identifier to determine the target transaction type identifier; The workflow determination unit is configured to determine the target transaction authentication workflow based on the target transaction type identifier and the user identifier; The execution unit is configured to execute the target transaction authentication workflow and obtain authentication result data; The request processing unit is configured to determine the request processing method based on the authentication result data, and process the business processing request based on the request processing method.

9. The apparatus according to claim 8, characterized in that, The transaction type identifier determination unit is further configured to: The dimension corresponding to the dimension identifier is determined. In response to the dimension being a component dimension, a degradation logic from the component dimension to the transaction dimension is executed to determine the target transaction type identifier in the transaction dimension.

10. The apparatus according to claim 9, characterized in that, The transaction type identifier determination unit is further configured to: Execute the logic to obtain the service identifier corresponding to the dimension identifier; Based on the obtained service identifier, the target transaction type identifier is determined.

11. The apparatus according to claim 8, characterized in that, The workflow determination unit is further configured to: Based on the target transaction type identifier, determine the corresponding workflow list; Based on the user identifier, the user level is determined, and then the corresponding target transaction authentication workflow is determined from the workflow list according to the user level.

12. The apparatus according to claim 8, characterized in that, The workflow determination unit is further configured to: Obtain the service dynamic identity token and its corresponding validity period; The security encryption component is invoked to decrypt the service dynamic identity token, and then the legality is verified based on the decrypted data, the validity is verified based on the validity period, and the permission is verified based on the user identifier.

13. The apparatus according to claim 12, characterized in that, The workflow determination unit is further configured to: Obtain the service metadata corresponding to the business processing request, and then generate a service dynamic identity token based on the service metadata through a security encryption component, and set the validity period of the service dynamic identity token.

14. A business processing electronic device, characterized in that, include: One or more processors; Storage device 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 implement the method as described in any one of claims 1-7.

15. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-7.

16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-7.

Citation Information

Patent Citations

  • Method and device for realizing business downgrading

    CN107454138A

  • Service authentication method, device, equipment and system and storage medium

    CN111835789A