Business processing methods, systems, management SDKs, clients, and electronic devices.

By introducing a management SDK, the problem of low efficiency in integrating multiple SDKs was solved, enabling efficient and flexible business processing workflows and reducing development difficulty and costs.

CN115237456BActive Publication Date: 2026-11-17JINGDONG TECH HLDG CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202210852645.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-20
Publication Date
2026-11-17
Estimated Expiration
2042-07-20

AI Technical Summary

Technical Problem

In existing technologies, the integration efficiency of applications with multiple SDKs is low. Business users need to understand the business processes and integration documentation of each SDK, resulting in high development and integration costs and making it difficult to achieve business processing.

Method used

By introducing a management SDK, configuration information can be obtained by receiving identification information from the business front end, and one or more atomic SDKs can be scheduled to realize business process orchestration and result processing, reducing the difficulty of business integration.

Benefits of technology

It improves SDK integration efficiency and reduces development costs. Business users only need to connect to the upper-level management SDK, simplifying the integration process and allowing for flexible responses to anti-counterfeiting strategies and configuration changes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115237456B_ABST
    Figure CN115237456B_ABST
Patent Text Reader

Abstract

This disclosure relates to a service processing method, system, management SDK, client, and electronic device, and pertains to the field of computer technology. The method includes: a management software development kit (SDK) receiving a service request sent by a service frontend, wherein the service request includes: service identification information; the management SDK obtaining service configuration information based on the service identification information, wherein the configuration information includes: parameters corresponding to one or more atomic SDKs and logical parameters of the service; the management SDK scheduling one or more atomic SDKs according to the configuration information; and the management SDK returning the service processing result to the service frontend.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a business processing method, system, management SDK, client, and electronic device. Background Technology

[0002] With the development of Internet technology, the services that terminal applications can provide are becoming increasingly rich, and multiple SDKs (Software Development Kits) can be integrated.

[0003] Currently, some scenarios can achieve the corresponding functions with only a single SDK, while others require multiple SDKs. For example, in scenarios involving user ID card and facial recognition verification, an ID card verification SDK and a facial recognition SDK are needed to verify the user's ID card and face respectively. For these scenarios, applications need to integrate multiple SDKs.

[0004] In related technologies, for one or more SDKs provided by a third party, the business application needs to understand the business process and integration documentation of each SDK to integrate it. If multiple SDKs need to be integrated, the business application needs to chain and process the results from these SDKs to obtain the final business processing result. Summary of the Invention

[0005] The inventors discovered that the concepts and parameters involved in the intelligent SDK are difficult to understand, the integration of the SDK by the business side is inefficient and requires a lot of development and integration costs, and it is very difficult for the business side to integrate the application with the third-party SDK to realize business processing.

[0006] One of the technical problems this disclosure aims to solve is: how to improve the efficiency of application-SDK integration and reduce the difficulty of application integration with SDK to implement business processing.

[0007] According to some embodiments of this disclosure, a service processing method is provided, comprising: a management software development kit (SDK) receiving a service request sent by a service frontend, wherein the service request includes: service identification information; the management SDK obtaining service configuration information based on the service identification information, wherein the configuration information includes: parameters corresponding to one or more atomic SDKs and logical parameters of the service; the management SDK scheduling one or more atomic SDKs based on the configuration information; and the management SDK returning the service processing result to the service frontend.

[0008] In some embodiments, the management SDK scheduling one or more atomic SDKs based on configuration information includes: the management SDK classifying and reorganizing the configuration information to obtain the parameters and business logic parameters corresponding to each atomic SDK; the management SDK performing logical processing based on the parameters and business logic parameters corresponding to each atomic SDK to obtain process data; the management SDK performing process orchestration based on the process data to obtain the business process; and the management SDK scheduling one or more atomic SDKs based on the business process.

[0009] In some embodiments, the business process includes: each step of the business operation and the information required for each step of the operation, wherein each step of the operation includes a scheduling operation for each atomic SDK, and the information required for the scheduling operation of each atomic SDK includes the parameters corresponding to the atomic SDK. The management SDK scheduling one or more atomic SDKs according to the business process includes: the management SDK executing each step of the business operation according to the business process; wherein, when the management SDK executes the scheduling operation of each atomic SDK, it wakes up the atomic SDK and sends the parameters corresponding to the atomic SDK to the atomic SDK.

[0010] In some embodiments, the parameters corresponding to one or more atomic SDKs include: anti-counterfeiting strategy parameters corresponding to each atomic SDK, which are used to enable each atomic SDK to perform anti-counterfeiting verification on the information input by the user according to the corresponding anti-counterfeiting strategy parameters.

[0011] In some embodiments, the service identification information includes at least one of the following: service name, service ID, and service key, and a token assigned to the service; before the management SDK obtains the service configuration information based on the service identification information, the method further includes: the management SDK searching for the stored token corresponding to the service based on at least one of the service name, service ID, and service key; the management SDK determining whether the service frontend has passed verification based on the comparison result between the stored token corresponding to the service and the token assigned to the service, and the validity period of the token corresponding to the service; and if the service frontend has passed verification, the management SDK obtaining the service configuration information based on the service identification information.

[0012] In some embodiments, before the management SDK obtains the configuration information of the service based on the service's identification information, the method further includes: the management SDK determining whether the service frontend has permission to call one or more modules related to the atomic SDK based on the service's identification information; and if the service frontend has permission to call one or more modules related to the atomic SDK, the management SDK executes the process of obtaining the configuration information of the service based on the service's identification information.

[0013] In some embodiments, before the management SDK obtains the service configuration information based on the service's identification information, the method further includes: the management SDK determining whether the user at the service front-end is using multi-signal login; and if the user at the service front-end is using single sign-on, the management SDK then obtains the service configuration information based on the service's identification information.

[0014] In some embodiments, the identification information of a service includes: a token assigned to the service, and the management SDK obtains the service configuration information based on the service identification information by: the management SDK pulling the service configuration information from the management server based on the token.

[0015] In some embodiments, the identification information of the service includes: a token assigned to the service. The method further includes: a management server receiving a token acquisition request sent by a service server, wherein the token acquisition request is sent by the service front-end to the service server and includes at least one of: service name, service ID, and service key; the management server generating a token assigned to the service based on at least one of the service name, service ID, and service key; and the management server sending the token assigned to the service to the service front-end through the service server.

[0016] In some embodiments, the identification information of the service includes: a token assigned to the service. The method further includes: a management server receiving a result verification request sent by a service server, wherein the result verification request includes the processing result of the service received by the service front end and the token assigned to the service; the management server searching for the stored processing result of the service based on the token assigned to the service; and the management server generating a result verification response based on the comparison result between the stored processing result of the service and the processing result of the service received by the service front end, and sending it to the service server.

[0017] In some embodiments, the method further includes: in response to a change request for the anti-counterfeiting capabilities of one or more atomic SDKs, a management server receives an anti-counterfeiting policy change request, wherein the anti-counterfeiting policy change request includes the changed anti-counterfeiting policy parameters of one or more atomic SDKs; and the management server saves the changed anti-counterfeiting policy parameters of one or more atomic SDKs as parameters corresponding to one or more atomic SDKs.

[0018] In some embodiments, one or more atomic SDKs include at least one of the following: ID card verification SDK and biometric information verification SDK.

[0019] According to some other embodiments of this disclosure, a management software development kit is provided, comprising: a receiving unit for receiving a service request sent by a business software development kit (SDK), wherein the service request includes: service identification information; an obtaining unit for obtaining service configuration information based on the service identification information, wherein the configuration information includes: parameters corresponding to one or more atomic SDKs and logical parameters of the service; a scheduling unit for scheduling one or more atomic SDKs based on the configuration information; and a sending unit for returning the processing result of the service to the service front end.

[0020] According to some other embodiments of this disclosure, a client is provided, including: a management SDK of any of the foregoing embodiments, a plurality of atomic SDKs, and a service front-end; the service front-end is used to send service requests to the management SDK and receive the processing results of the services sent by the management SDK; each atomic SDK is used to process services in response to the scheduling of the management SDK.

[0021] According to further embodiments of this disclosure, a service processing system is provided, including: a client of any of the foregoing embodiments; and a management server; the management server is configured to receive a token acquisition request sent by a service server, wherein the token acquisition request is sent by a service frontend to the service server and includes at least one of: service name, service ID, and service key; generate a token allocated to the service based on at least one of the service name, service ID, and service key; and send the token allocated to the service to the service frontend through the service server.

[0022] In some embodiments, the management server is configured to receive a result verification request sent by the business server, wherein the result verification request includes the processing result of the business received by the business front-end and the token assigned to the business; search for the stored processing result of the business based on the token assigned to the business; generate a result verification response based on the comparison result between the stored processing result of the business and the processing result of the business received by the business front-end, and send it to the business server.

[0023] In some embodiments, the management server is used to respond to the change requirements of the anti-counterfeiting capabilities of one or more atomic SDKs by receiving an anti-counterfeiting policy change request, wherein the anti-counterfeiting policy change request includes the changed anti-counterfeiting policy parameters of one or more atomic SDKs; and saves the changed anti-counterfeiting policy parameters of one or more atomic SDKs as parameters corresponding to one or more atomic SDKs.

[0024] According to further embodiments of this disclosure, an electronic device is provided, including: a processor; and a memory coupled to the processor for storing instructions, which, when executed by the processor, cause the processor to perform a processing method of a service as described in any of the foregoing embodiments.

[0025] According to further embodiments of the present disclosure, a non-transitory computer-readable storage medium is provided, on which a computer program is stored, wherein when the program is executed by a processor, it implements the processing method of the business of any of the foregoing embodiments.

[0026] In this disclosed solution, a management SDK connects to the business frontend of the business party. The business requests sent by the business frontend carry business identification information. Based on this identification information, the management SDK can obtain the business configuration information and schedule one or more atomic SDKs. The management SDK then returns the processing result to the business frontend. This disclosure implements a solution for business processing based on a two-layer SDK architecture. The business application only needs to connect to the upper-layer management SDK. The business frontend and management SDK only need to exchange simple parameters such as business identification information. Therefore, integrating the management SDK is more efficient and simpler than integrating atomic SDKs. The business party does not need to understand the scheduling methods, required parameters, or chaining mechanisms of the lower-layer atomic SDKs; it only needs to send the business identification information to the management SDK to obtain the processing result. The management SDK automatically and flexibly schedules the lower-layer atomic SDKs based on business needs, reducing the difficulty for the business application to integrate with the SDKs for business processing.

[0027] Other features and advantages of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 The present disclosure illustrates a flowchart of a service processing method according to some embodiments of the present disclosure.

[0030] Figure 2 A schematic diagram of the architecture of a two-layer SDK according to some embodiments of this disclosure is shown.

[0031] Figure 3 The following are schematic flowcharts illustrating service processing methods according to other embodiments of this disclosure.

[0032] Figure 4 A schematic diagram illustrating the structure of the management SDK of some embodiments of this disclosure is shown.

[0033] Figure 5 A schematic diagram of the client structure is shown for some embodiments of this disclosure.

[0034] Figure 6 A schematic diagram of the structure of a service processing system according to some embodiments of this disclosure is shown.

[0035] Figure 7 A schematic diagram of the structure of an electronic device according to some embodiments of the present disclosure is shown.

[0036] Figure 8 Schematic diagrams of the structure of electronic devices according to other embodiments of the present disclosure are shown. Detailed Implementation

[0037] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0038] This disclosure provides a method for processing business operations, which will be described below in conjunction with... Figures 1-3 describe.

[0039] Figure 1 Flowcharts are shown for some embodiments of the processing methods disclosed herein. Figure 1 As shown, the method of this embodiment includes steps S102 to S108.

[0040] In step S102, the management SDK receives service requests sent by the service frontend.

[0041] The business frontend may include a business SDK or a business application. In response to a business request, the business frontend can send a business request to the management SDK. For example, in response to user registration, which requires ID card and facial verification, the business frontend initiates a business request. In some embodiments, the business request includes: business identification information, which includes at least one of the following: business name, business ID, and business key. The business ID may be assigned to the business frontend by the management SDK. The business key may be a parameter defined by the management SDK, which, along with the business name and business ID, can serve as an authorization parameter and identification information for the business.

[0042] In step S104, the management SDK obtains the service configuration information based on the service's identification information.

[0043] The configuration information of a service can be pre-stored on the management server and associated with the service's identification information. The management SDK retrieves the service's configuration information from the management server based on the service's identification information.

[0044] In some embodiments, the configuration information includes: parameters corresponding to one or more atomic SDKs and logical parameters of the business. The parameters corresponding to one or more atomic SDKs are the parameters required for scheduling each atomic SDK, and the logical parameters of the business are used to represent the logical relationship between the scheduling of each atomic SDK, as well as the processing logic of the results returned by each atomic SDK, etc. The configuration information of the business can be pre-configured according to the needs of the business party. For example, for ID card and face verification businesses, the parameters corresponding to the ID card verification SDK and face verification SDK, as well as the logical parameters of the business, can be pre-configured.

[0045] In some embodiments, the parameters corresponding to one or more atomic SDKs include: anti-spoofing strategy parameters corresponding to each atomic SDK, which are used to enable each atomic SDK to perform anti-spoofing verification on the user input information according to the corresponding anti-spoofing strategy parameters. For example, when verifying face, the anti-spoofing strategy parameters may include the frequency of opening and closing eyes, the angle range of nodding and shaking the head, blurring, frame selection frequency, etc.

[0046] If business users integrate the various atomic SDKs, the anti-counterfeiting policy parameters will be hardcoded into the application. Changing these parameters requires redeploying the entire application, a complex and time-consuming process. Furthermore, if the anti-counterfeiting policy is compromised, timely remediation is impossible. By configuring the business settings on the management server side, and having the management SDK retrieve the configuration information upon receiving a business request, the anti-counterfeiting policy parameters do not need to be hardcoded into the application and can be changed at any time according to security requirements.

[0047] In some embodiments, in response to a change request for the anti-counterfeiting capabilities of one or more atomic SDKs, the management server receives an anti-counterfeiting policy change request. The anti-counterfeiting policy change request includes the modified anti-counterfeiting policy parameters for one or more atomic SDKs. The management server saves the modified anti-counterfeiting policy parameters for one or more atomic SDKs as parameters corresponding to those atomic SDKs. The anti-counterfeiting policy change request can be initiated by a business entity or triggered by an attack, and is not limited to the examples given.

[0048] Furthermore, other configuration information can be changed at any time. For example, parameters from the ID card verification SDK can be changed to those from the voice verification SDK, allowing subsequent calls to the voice verification SDK for business processing. Similarly, business logic parameters can be changed as needed. In some embodiments, the management server receives a configuration information change request, which includes the modified configuration information, including the modified parameters of one or more atomic SDKs and / or the modified business logic parameters. The management server saves the modified configuration information. The configuration information change request can be generated based on the needs of the business party.

[0049] In step S106, the management SDK schedules one or more atomic SDKs according to the configuration information.

[0050] In some embodiments, the management SDK categorizes and reorganizes the configuration information to obtain the parameters and business logic parameters corresponding to each atomic SDK; the management SDK performs logical processing based on the parameters and business logic parameters corresponding to each atomic SDK to obtain process data; the management SDK orchestrates the process based on the process data to obtain the business process; and the management SDK schedules one or more atomic SDKs according to the business process.

[0051] In some embodiments, the business process includes: each step of the business operation and the information required for each step, wherein each step includes the scheduling operation of each atomic SDK, and may also include generating the processing result of the business, processing the result returned by each atomic SDK, etc. The information required for the scheduling operation of each atomic SDK includes the parameters corresponding to that atomic SDK. The management SDK executes each step of the business operation according to the business process; when executing the scheduling operation of each atomic SDK, the management SDK invokes that atomic SDK and sends the parameters corresponding to that atomic SDK to that atomic SDK.

[0052] Some operations require information generated from the previous operation. Therefore, the management SDK can also perform the next operation based on the information generated from the previous operation. In some embodiments, the management SDK determines the next operation and the parameters corresponding to the atomic SDK of the next operation based on the business logic parameters and the results of the atomic SDK in the previous operation. This information serves as the process data for the next step. The next process is then orchestrated based on this process data, and the above process is repeated until the process ends. If the next operation does not involve the results of the atomic SDK of the previous operation or the parameters corresponding to the atomic SDK, this information is empty, and the process can be orchestrated directly based on the business logic parameters.

[0053] The parameters sent to the atomic SDK can also include anti-spoofing strategy parameters corresponding to the atomic SDK. The atomic SDK performs anti-spoofing verification on the information entered by the user based on the anti-spoofing strategy parameters. For example, the face verification SDK determines whether a face is a fake face (e.g., video, photo, etc.) based on the frequency of opening and closing eyes, the angle range of nodding and shaking the head, blurriness, frame selection frequency, etc.

[0054] like Figure 2 The diagram shown illustrates the architecture of some embodiments of the two-layer SDK disclosed herein. The two-layer SDK architecture includes a management SDK and multiple atomic SDKs. The business front-end interfaces with the management SDK, can invoke the management SDK, and receive the processing results returned by the management SDK. The atomic SDKs are invisible to the business front-end. The number and types of atomic SDKs can be flexibly added or removed by third parties, and the business side does not need to perform additional development work for these atomic SDKs.

[0055] The management SDK can include a configuration management layer, a protocol data conversion layer, and a process orchestration layer. Information can be exchanged between the management SDK and the individual atomic SDKs via a routing component. The management SDK can schedule the individual atomic SDKs according to business needs, and the individual atomic SDKs can send their results back to the management SDK.

[0056] The configuration management layer categorizes, splits, and reorganizes configuration information to obtain parameters corresponding to each atomic SDK and business logic parameters. Since configuration information transmitted via interfaces forms a chain of data, it needs to be categorized, split, and reorganized to obtain different types of parameters. For example, configuration information can be broken down into small data objects using a key-value pair.

[0057] The protocol data conversion layer receives the reconstructed configuration data above and the result data from the atomic SDK below. Based on the configuration data and the underlying atomic SDK's processing data, logical processing is performed to obtain the next step's workflow data.

[0058] The process orchestration layer obtains the next step's process data from the protocol data conversion layer, and then executes the next step of the process. For example, it can invoke an atomic SDK, or output business results upon completion of orchestration.

[0059] In step S108, the management SDK returns the processing result of the business to the business front end.

[0060] The processing result of a business application can be generated based on the results of each atomic SDK. If the processing result can be directly and easily generated from the results returned by each atomic SDK, then the management SDK can directly generate the processing result and return it to the business front-end. Alternatively, each atomic SDK can send its result to the management server, which will then generate the processing result and send it back to the management SDK.

[0061] When multiple atomic SDKs need to be scheduled, the results returned by each atomic SDK can be further processed to generate the final business processing result. For example, the ID card verification SDK returns an ID card image, and the face verification SDK returns a face image. By comparing the ID card image and the face image, it can be determined that the user holding the ID card and the user currently operating belong to the same user.

[0062] In the above embodiment, the management SDK connects to the business frontend of the business party. The business request sent by the business frontend carries the business identification information. The management SDK can obtain the business configuration information based on the business identification information, and realize the scheduling of one or more atomic SDKs. The management SDK returns the processing result of the business to the business frontend. The above embodiment implements a solution for business processing based on a two-layer SDK. The business application only needs to connect to the upper-layer management SDK. The business frontend and the management SDK only need to pass simple parameters such as the business identification information. Therefore, the efficiency of accessing the management SDK is higher and the access is simpler than that of the atomic SDKs. The business party does not need to know the scheduling method, required parameters, or how to perform chaining of the lower-layer atomic SDKs. It only needs to send the business identification information to the management SDK to obtain the processing result of the business. The management SDK automatically and flexibly implements the scheduling of the lower-layer atomic SDKs based on the business needs, reducing the difficulty for the business application to connect to the SDK to realize business processing.

[0063] The following is combined Figure 3 Some other embodiments of the processing methods described in this disclosure are described.

[0064] Figure 3 Flowcharts are shown for some other embodiments of the processing methods disclosed herein. For example... Figure 3 As shown, the method of this embodiment includes steps S302 to S324.

[0065] In step S302, the business front end sends a token acquisition request to the business server.

[0066] A token acquisition request may include, for example, at least one of the following: business name, business ID, and business key. The business frontend can send the token acquisition request using HTTP (Hypertext Transfer Protocol).

[0067] In step S304, the service server sends a token acquisition request to the management server.

[0068] The business server can send a token acquisition request to the management server through the JSF interface.

[0069] In step S306, the management server generates a token to be assigned to the service based on at least one of the service name, service ID, and service key.

[0070] The management server can generate tokens according to preset rules. For example, it can encode at least one of the three essential business elements (business name, business ID, and business key) according to a preset encoding method to generate a token assigned to the business. The token has a corresponding validity period and can be used to verify the legitimacy of the business.

[0071] In step S308, the management server sends the token assigned to the service to the service front end through the service server.

[0072] Instead of the business front-end interacting directly with the management server to pass tokens, the security of token transmission can be improved. By storing the tokens on the business server, if the token is tampered with when it is sent to the business front-end, the business front-end can retrieve the token from the business server again without having to obtain it from the management server.

[0073] In step S310, the business front-end sends a business request to the management SDK.

[0074] A business request may include, for example, at least one of the following: business name, business ID, and business key, as well as a token assigned to the business.

[0075] In step S312, the management SDK verifies the business front-end. If the verification passes, step S314 is executed; otherwise, step S313 is executed.

[0076] The management SDK can verify the legitimacy of the business frontend, the permissions of the business frontend to call one or more atomic SDK-related modules, multi-point login, and parameters passed by the business frontend. For example, when a business request includes multiple items such as business name, business ID, and business key, the SDK can verify the correspondence between these multiple items based on the stored mapping between business name, business ID, and business key. If they match, the verification passes; otherwise, the verification fails. For example, the management SDK can look up the stored token corresponding to the business based on at least one of the business name, business ID, and business key. Based on the comparison between the stored token and the token allocated to the business, and the validity period of the token corresponding to the business, the SDK determines whether the business frontend verification passes. If they match and the token is within its validity period, the verification passes; otherwise, the verification fails.

[0077] For example, the management SDK determines whether the business frontend has permission to call one or more atomic SDK-related modules based on the business's identification information. The management SDK can store the mapping between business identification information and module call permissions. It checks whether the business frontend has permission to call one or more atomic SDK-related modules based on the business's identification information; if so, the verification passes; otherwise, the verification fails. The one or more atomic SDK-related modules can be modules on the terminal. For example, when performing ID card verification or face verification, it is necessary to determine whether the business frontend has permission to call the camera module.

[0078] For example, the management SDK determines whether the user on the business frontend is using multi-sign-on; if so, the verification passes; otherwise, it fails. Similarly, the management SDK determines whether the parameters (business requests) sent by the business frontend conform to a preset format; if so, the verification passes; otherwise, it fails.

[0079] In step S313, the management SDK returns a service failure message to the service frontend.

[0080] In step S314, the management SDK obtains the service configuration information from the management server based on the service's identification information.

[0081] The management SDK can retrieve the service configuration information from the management server based on the token.

[0082] In step S316, the management SDK schedules one or more atomic SDKs according to the configuration information (the figure shows the case of scheduling multiple atomic SDKs).

[0083] When the management SDK sends parameters corresponding to each atomic SDK to each atomic SDK, it can send the service identification information to each atomic SDK.

[0084] In step S318, one or more atomic SDKs send the results to the management server.

[0085] Each atomic SDK sends the corresponding results and business identification information to the management server.

[0086] In step S320, the management server generates the processing results of the service based on the results of each atomic SDK.

[0087] In step S322, the management server sends the processing result of the service to the management SDK.

[0088] The management server can return the processing results of the business to the management SDK through the atomic SDK, or it can send them directly to the management SDK.

[0089] In step S324, the management SDK returns the processing result of the business to the business front end.

[0090] The processing results of a service may be tampered with or attacked during the process of being sent to the service front-end. Verification of the processing results can improve security. In some embodiments, the management server receives a result verification request from the service server, wherein the result verification request includes the processing result received by the service front-end and the token assigned to the service; the management server retrieves the stored processing result based on the token assigned to the service; the management server generates a result verification response based on the comparison between the stored processing result and the processing result received by the service front-end, and sends it to the service server. Alternatively, the management server may directly return the stored processing result to the service server for comparison and verification.

[0091] The method described above reduces the integration cost between business users and third-party SDKs, improving efficiency and convenience. Business users are not concerned with how to schedule atomic SDKs, how to set parameters, or anti-counterfeiting strategies. They only care about the combinations needed to implement their business logic. The business frontend connects to the management SDK, passing the business's identification information as input parameters, and ultimately receives the business's processing result. Business users can change configuration information and delete or add anti-counterfeiting strategies to change the security level at any time. If an attack is detected, a re-release is not required; anti-counterfeiting strategies can be immediately changed, employing multiple combinations and dimensions to prevent attacks and ensure business security, allowing more time for subsequent iterations and fixes. The business frontend connects to the upper-layer management SDK, which in turn depends on the lower-layer atomic SDKs, which are unknown to the business user. The management SDK can flexibly extend atomic SDKs without the business user's awareness; they only need to modify configuration information to use new atomic SDK functionalities.

[0092] In some embodiments, one or more atomic SDKs include at least one of the following: an ID card verification SDK and a biometric verification SDK. The ID card verification SDK can be an SDK that verifies identity by taking a photo of the ID card with a camera, or an SDK that verifies identity by reading the ID card chip information via NFC (Near Field Communication), and is not limited to the examples given. The biometric verification SDK includes, for example, a face verification SDK, an iris verification SDK, or a fingerprint verification SDK, and is not limited to the examples given. One or more atomic SDKs may also include other SDKs for verifying user identity, not limited to the examples given above.

[0093] The following example illustrates some applications of this disclosure, using a scenario where business needs require ID verification and facial recognition to complete registration.

[0094] Business applications require ID card anti-counterfeiting capabilities and ID card OCR (Optical Character Recognition) capabilities, as well as facial anti-counterfeiting capabilities and facial recognition capabilities (ID card anti-counterfeiting and OCR recognition can only determine the authenticity of the ID card, while facial anti-counterfeiting and recognition can only identify the current person. Only by comparing the facial image on the ID card with the collected facial image can the business being processed by the person on the ID card be determined).

[0095] When a business requests registration via ID card verification and facial recognition, the management SDK or server can assign a business ID to the business and configure it according to their needs. For example, it can be configured as a visual algorithm ID card service based on the business's strictness level, and anti-counterfeiting strategies can be configured, such as enabling flash anti-counterfeiting capabilities. Based on the business's requirements, anti-counterfeiting strategy parameters (e.g., angle, light intensity, missing edge / corner threshold, handheld status, etc.) can be configured.

[0096] The management server can be further configured to perform face SDK verification. Based on business requirements, including security and user experience, the server can configure a combination of silent and animated actions (such as nodding, shaking, opening and closing eyes, and opening and closing the mouth) and a combined resolution hook anti-spoofing strategy. In addition to face recognition configuration information, anti-spoofing strategy parameters (e.g., frequency of eye opening and closing, angle range of nodding and shaking, blurriness, frame selection frequency, etc.) can be configured in advance and stored on the management server.

[0097] The business frontend obtains a token from the management server via the management SDK based on the three business elements (business ID, business name, and business key). The management server generates a token using a specific algorithm. Tokens have an expiration time. After obtaining the token, the business frontend sends a business request to invoke the management SDK, with the assigned three business elements plus the token as input parameters. The management SDK retrieves configuration information using the three business elements and the token, thus obtaining all the parameters of the aforementioned configuration. These parameters are then sent to the configuration management layer for configuration splitting, reorganization, etc., so that they can be scheduled and used by the process orchestration layer and protocol data conversion layer.

[0098] The protocol data conversion layer first generates process data based on the configuration information, triggering the process orchestration layer to determine the business process. The process orchestration layer first invokes the ID card verification SDK and sends the corresponding parameters to the ID card verification SDK. The ID card verification SDK performs anti-counterfeiting based on anti-counterfeiting strategy parameters, selects frames, and sends the selected front and back images of the ID card, along with the three elements and a token, to the management server for OCR recognition of the ID card information. At the same time, it verifies the authenticity of the name and number on the ID card online.

[0099] After the ID card verification result is obtained, the management server associates all data from this process with the token and stores it in the database, while simultaneously returning the successful recognition result to the ID card SDK. The ID card SDK sends the result to the management SDK. The management SDK, based on the ID card verification result and the business process, determines the next step. If single ID card verification is configured, it will be orchestrated to directly output the final business processing result to the business front end. However, in this business, the next step is face verification. The process orchestration layer invokes the face verification SDK and sends the relevant parameters, three elements, and the token to the face verification SDK. If a counterfeit prevention strategy of silent + open / closed eyes + resolution HOOK is configured, the face verification SDK detects a face, prompts the user to open / close their eyes, and performs actions according to the prompts to prevent re-photographing, etc. Finally, it changes the resolution to prevent the program from being HOOKed for face scanning. After passing the anti-counterfeiting frame selection, the face image data is obtained, combined with the three elements and the token, and sent to the management server. It is then compared with the face image obtained from the real ID card to confirm that the cardholder and the current operator are the same person.

[0100] After successful verification, all data in this process is associated with the token. The management server retains the data in a legal and compliant manner and returns the result to the face verification SDK. The face verification SDK returns the result to the management SDK. The management SDK determines the final result based on the business process and the face verification result. Then, the business processing result is returned to the business front end, which also includes the token of the entire process.

[0101] The business side can use the results for real-time display on the front end. However, because front-end data is vulnerable to attack, the process loop is not yet complete. The business side needs to return the results to the business server. The business server then uses the token to query the management server to verify whether the processing results stored on the management server are consistent with the results received by the front end. If they are consistent, the entire process is complete and the results are reliable. The business side can then notify the business front end to proceed to the next step based on the query results.

[0102] The two-layer SDK disclosed herein can be flexibly configured according to business needs, both in terms of business logic and atomic SDKs. Once the configuration is determined, other tasks are handled by the configuration management layer, protocol data conversion layer, and process orchestration layer of the management SDK, which perform cyclical orchestration and finally output the results.

[0103] This disclosure also provides a management software development kit, which is described below in conjunction with... Figure 4 Describe it.

[0104] Figure 4 This is a structural diagram of some embodiments of the management SDK disclosed herein. Figure 4 As shown, the management SDK 40 in this embodiment includes: a receiving unit 410, an acquisition unit 420, a scheduling unit 430, and a sending unit 440.

[0105] The receiving unit 410 is used to receive service requests sent by the business software development kit (SDK), wherein the service request includes: service identification information.

[0106] The acquisition unit 420 is used to acquire the configuration information of the service based on the service's identification information, wherein the configuration information includes: parameters corresponding to one or more atomic SDKs and logical parameters of the service.

[0107] In some embodiments, the identification information of the service includes: a token assigned to the service, and the acquisition unit 420 is used to retrieve the configuration information of the service from the management server based on the token.

[0108] The scheduling unit 430 is used to schedule one or more atomic SDKs according to the configuration information.

[0109] In some embodiments, the scheduling unit 430 is used to classify and reorganize the configuration information to obtain parameters corresponding to each atomic SDK and logical parameters of the service; perform logical processing based on the parameters corresponding to each atomic SDK and the logical parameters of the service to obtain process data; perform process orchestration based on the process data to obtain the process of the service; and schedule one or more atomic SDKs according to the process of the service. The configuration management layer, protocol data conversion layer, and process orchestration layer in the foregoing embodiments can be set in the scheduling unit 430.

[0110] In some embodiments, the service flow includes: each step of the service operation and the information required for each step of the operation, wherein each step of the operation includes a scheduling operation for each atomic SDK, and the information required for the scheduling operation of each atomic SDK includes the parameters corresponding to the atomic SDK. The scheduling unit 430 is used to execute each step of the service operation according to the service flow; wherein, when executing the scheduling operation of each atomic SDK, the scheduling unit 430 is used to wake up the atomic SDK and send the parameters corresponding to the atomic SDK to the atomic SDK.

[0111] In some embodiments, the parameters corresponding to the one or more atomic SDKs include: anti-counterfeiting strategy parameters corresponding to each atomic SDK, which are used to enable each atomic SDK to perform anti-counterfeiting verification on the information input by the user according to the corresponding anti-counterfeiting strategy parameters.

[0112] The sending unit 440 is used to return the processing result of the service to the service front end.

[0113] In some embodiments, the management SDK further includes: a verification unit 450, configured to determine whether the service frontend has permission to call modules related to the one or more atomic SDKs based on the service's identification information; and, if the service frontend has permission to call modules related to the one or more atomic SDKs, trigger the acquisition unit 420 to acquire the service's configuration information based on the service's identification information.

[0114] In some embodiments, the verification unit 450 is further configured to determine whether the user of the service front-end is a multi-signal login; if the user of the service front-end is a single sign-on login, the configuration information of the service is obtained based on the service's identification information.

[0115] In some embodiments, the identification information of the service includes at least one of a service name, a service ID, and a service key, as well as a token assigned to the service; the verification unit 450 is further configured to look up the stored token corresponding to the service based on at least one of the service name, service ID, and service key; determine whether the service front-end has passed verification based on the comparison result between the stored token corresponding to the service and the token assigned to the service, and the validity period of the token corresponding to the service; if the service front-end has passed verification, trigger the acquisition unit 420 to acquire the configuration information of the service based on the identification information of the service.

[0116] This disclosure also provides a client, which is described below in conjunction with... Figure 5 Describe it.

[0117] Figure 5This is a structural diagram of some embodiments of the client disclosed herein. For example... Figure 5 As shown, the client 50 in this embodiment includes: a management SDK 40, multiple atomic SDKs 52, and a business front-end 54.

[0118] The service front-end 54 is used to send service requests to the management SDK 40 and receive the processing results of the services sent by the management SDK 40. The service front-end 54 can execute the methods executed by the service front-end in any of the foregoing embodiments, which will not be described in detail here.

[0119] Each atomic SDK 52 is used to process services in response to the scheduling of the management SDK 40. Each atomic SDK 52 can execute the methods executed by the atomic SDK in any of the foregoing embodiments, which will not be described in detail here.

[0120] The client may include a processor; and a memory coupled to the processor, the memory being used to store a management SDK, multiple atomic SDKs, and a business front-end program, which, when executed by the processor, causes the processor to execute the method performed by the management SDK, atomic SDKs, and business front-end in any of the foregoing embodiments, thereby implementing the functions of the management SDK, atomic SDKs, and business front-end.

[0121] This disclosure also provides a business processing system, which is described below in conjunction with... Figure 6 Describe it.

[0122] Figure 6 This is a structural diagram of some embodiments of the processing system for the services disclosed herein. For example... Figure 6 As shown, the system 6 of this embodiment includes: a client 50 of any of the foregoing embodiments; and a management server 62.

[0123] The management server 62 is used to receive a token acquisition request sent by the business server, wherein the token acquisition request is sent by the business front-end to the business server and includes at least one of the following: business name, business ID, and business key; generate a token allocated to the business based on at least one of the business name, business ID, and business key; and send the token allocated to the business to the business front-end through the business server.

[0124] In some embodiments, the management server 62 is configured to receive a result verification request sent by the service server, wherein the result verification request includes the processing result of the service received by the service front-end and the token allocated to the service; search for the stored processing result of the service based on the token allocated to the service; generate a result verification response based on the comparison result between the stored processing result of the service and the processing result of the service received by the service front-end, and send it to the service server.

[0125] The management server 62 is used to respond to the change requirements of the anti-counterfeiting capabilities of one or more atomic SDKs by receiving an anti-counterfeiting strategy change request, wherein the anti-counterfeiting strategy change request includes the changed anti-counterfeiting strategy parameters of the one or more atomic SDKs; and the changed anti-counterfeiting strategy parameters of the one or more atomic SDKs are saved as parameters corresponding to the one or more atomic SDKs.

[0126] The management server 62 is also used to execute the methods performed by the management server 62 in any of the foregoing embodiments, which will not be described again here.

[0127] The electronic devices in the embodiments of this disclosure can each be implemented by various computing devices or computer systems, as described below. Figure 7 as well as Figure 8 Describe it.

[0128] Figure 7 This is a structural diagram of some embodiments of the electronic device disclosed herein. For example... Figure 7 As shown, the electronic device 70 of this embodiment includes a memory 710 and a processor 720 coupled to the memory 710. The processor 720 is configured to execute processing methods of any of the embodiments of this disclosure based on instructions stored in the memory 710.

[0129] The memory 710 may include, for example, system memory, fixed non-volatile storage media, etc. The system memory may store, for example, an operating system, application programs, a boot loader, a database, and other programs.

[0130] Figure 8 These are structural diagrams of some other embodiments of the electronic device disclosed herein. For example... Figure 8 As shown, the electronic device 80 of this embodiment includes a memory 810 and a processor 820, which are similar to the memory 710 and processor 720, respectively. It may also include an input / output interface 830, a network interface 840, a storage interface 850, etc. These interfaces 830, 840, 850, and the memory 810 and processor 820 can be connected, for example, via a bus 860. The input / output interface 830 provides a connection interface for input / output devices such as a display, mouse, keyboard, and touchscreen. The network interface 840 provides a connection interface for various networked devices, such as connecting to a database server or cloud storage server. The storage interface 850 provides a connection interface for external storage devices such as SD cards and USB flash drives.

[0131] It should be noted that the acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with relevant laws and regulations and do not violate public order and good morals.

[0132] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0133] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0134] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0135] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0136] The above description is only a preferred embodiment of this disclosure and is not intended to limit this disclosure. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this disclosure should be included within the protection scope of this disclosure.

Claims

1. A business processing method, comprising: The management software development kit (SDK) receives business requests sent by the business frontend, wherein the business request includes: business identification information; The management SDK obtains the configuration information of the service based on the service's identification information. The configuration information includes: parameters corresponding to one or more atomic SDKs and logical parameters of the service. The logical parameters of the service are used to represent the logical relationship between the scheduling of each atomic SDK and the processing logic of the results returned by each atomic SDK. The management SDK schedules one or more atomic SDKs according to the configuration information, including: the management SDK classifies and reorganizes the configuration information to obtain parameters corresponding to each atomic SDK and logical parameters of the business; the management SDK performs logical processing according to the parameters corresponding to each atomic SDK and the logical parameters of the business to obtain process data; the management SDK performs process orchestration according to the process data to obtain the process of the business; and the management SDK schedules one or more atomic SDKs according to the process of the business. The management SDK returns the processing result of the business to the business front-end.

2. The processing method according to claim 1, wherein, The business process includes: each step of the business operation and the information required for each step, wherein each step includes a scheduling operation for each atomic SDK, and the information required for the scheduling operation of each atomic SDK includes the parameters corresponding to that atomic SDK. The management SDK scheduling one or more atomic SDKs according to the business process includes: The management SDK executes each step of the business process according to the business flow. Specifically, when the management SDK performs the scheduling operation for each atomic SDK, it wakes up the atomic SDK and sends the parameters corresponding to the atomic SDK to the atomic SDK.

3. The processing method according to claim 1, wherein, The parameters corresponding to the one or more atomic SDKs include: anti-counterfeiting strategy parameters corresponding to each atomic SDK, which are used to enable each atomic SDK to perform anti-counterfeiting verification on the information input by the user according to the corresponding anti-counterfeiting strategy parameters.

4. The processing method according to claim 1, wherein, The identification information of the service includes at least one of the following: service name, service ID, and service key, as well as the token assigned to the service; Before the management SDK obtains the configuration information of the service based on the service's identification information, it also includes: The management SDK searches for the token corresponding to the stored service based on at least one of the service name, service ID, and service key. The management SDK determines whether the front-end of the service has passed verification based on the comparison result between the token corresponding to the service stored in the database and the token allocated to the service, as well as the validity period of the token corresponding to the service. If the management SDK passes the verification at the business front end, it retrieves the configuration information of the business based on the business's identification information.

5. The processing method according to claim 1, wherein, Before the management SDK obtains the configuration information of the service based on the service's identification information, it also includes: The management SDK determines whether the business frontend has permission to call the modules related to the one or more atomic SDKs based on the business's identification information; When the management SDK has permission to call the modules related to one or more atomic SDKs at the business front end, it executes the process of obtaining the configuration information of the business based on the business's identification information.

6. The processing method according to claim 1, wherein, Before the management SDK obtains the configuration information of the service based on the service's identification information, it also includes: The management SDK determines whether the user of the business front-end is using multi-point login; When the user at the business front end is using single sign-on, the management SDK retrieves the configuration information of the business based on the business's identification information.

7. The processing method according to claim 1, wherein, The identification information of the service includes: a token assigned to the service; the management SDK obtains the configuration information of the service based on the identification information of the service, including: The management SDK retrieves the service configuration information from the management server based on the token.

8. The processing method according to claim 1, wherein, The identification information of the service includes: a token assigned to the service, and the method further includes: The management server receives a token acquisition request sent by the business server, wherein the token acquisition request is sent by the business front-end to the business server and includes at least one of the following: business name, business ID and business key; The management server generates the token assigned to the service based on at least one of the service name, service ID, and service key; The management server sends the token assigned to the service to the service front-end through the service server.

9. The processing method according to claim 1, wherein, The identification information of the service includes: a token assigned to the service, and the method further includes: The management server receives a result verification request sent by the business server, wherein the result verification request includes the processing result of the business received by the business front end and the token allocated to the business; The management server searches for the stored processing result of the service based on the token assigned to the service; The management server generates a result verification response based on the comparison between the stored processing result of the service and the processing result of the service received by the service front end, and sends it to the service server.

10. The processing method according to claim 3, further comprising: In response to a change request for the anti-counterfeiting capabilities of one or more atomic SDKs, the management server receives an anti-counterfeiting policy change request, wherein the anti-counterfeiting policy change request includes the changed anti-counterfeiting policy parameters of the one or more atomic SDKs. The management server saves the modified anti-counterfeiting strategy parameters of the one or more atomic SDKs as the parameters corresponding to the one or more atomic SDKs.

11. The processing method according to any one of claims 1-10, wherein, The one or more atomic SDKs include at least one of the following: ID card verification SDK and biometric information verification SDK.

12. A system for managing software development kits, comprising: The receiving unit is configured to receive a service request sent by the business software development kit (SDK), wherein the service request includes: service identification information; The acquisition unit is used to acquire the configuration information of the service based on the identification information of the service, wherein the configuration information includes: parameters corresponding to one or more atomic SDKs and logical parameters of the service, wherein the logical parameters of the service are used to represent the logical relationship between the scheduling of each atomic SDK and the processing logic of the results returned by each atomic SDK; A scheduling unit is configured to schedule one or more atomic SDKs according to the configuration information, comprising: a management SDK classifying and reorganizing the configuration information to obtain parameters corresponding to each atomic SDK and logical parameters of the service; the management SDK performing logical processing based on the parameters corresponding to each atomic SDK and the logical parameters of the service to obtain process data; the management SDK performing process orchestration based on the process data to obtain the process of the service; and the management SDK scheduling one or more atomic SDKs according to the process of the service. The sending unit is used to return the processing result of the service to the service front end.

13. A client, comprising: The system for managing software development kits as described in claim 12, comprising multiple atomic SDKs and a business front-end; The business front-end is used to send business requests to the management SDK system and receive the processing results of the business sent by the management SDK system; Each atomic SDK is used to process services in response to the scheduling of the system that manages the SDK.

14. A business processing system, comprising: The client described in claim 13; And management servers; The management server is used to receive a token acquisition request sent by the business server, wherein the token acquisition request is sent by the business frontend to the business server and includes at least one of the following: business name, business ID, and business key; generate a token allocated to the business based on at least one of the business name, business ID, and business key; and send the token allocated to the business to the business frontend through the business server.

15. The business processing system according to claim 14, wherein, The management server is used to receive a result verification request sent by the business server, wherein the result verification request includes the processing result of the business received by the business front end and the token allocated to the business; it searches for the stored processing result of the business based on the token allocated to the business; it generates a result verification response based on the comparison result between the stored processing result of the business and the processing result of the business received by the business front end, and sends it to the business server.

16. The business processing system according to claim 14, wherein, The management server is used to respond to the change requirements of the anti-counterfeiting capabilities of one or more atomic SDKs by receiving an anti-counterfeiting strategy change request, wherein the anti-counterfeiting strategy change request includes the changed anti-counterfeiting strategy parameters of the one or more atomic SDKs; and the changed anti-counterfeiting strategy parameters of the one or more atomic SDKs are saved as parameters corresponding to the one or more atomic SDKs.

17. An electronic device comprising: processor; as well as A memory coupled to the processor is used to store instructions that, when executed by the processor, cause the processor to perform the processing method of the service as described in any one of claims 1-11.

18. A non-transitory computer-readable storage medium having a computer program stored thereon, wherein, When executed by a processor, the program implements the steps of the method according to any one of claims 1-11.

Citation Information

Patent Citations

  • SDK access system and method

    CN107643954A

  • Data transmission method, device and system, computer equipment and readable storage medium

    CN111756737A

  • Resources providing method and device

    CN113934460A