CN114430428B - Client interface unifying method, service system, storage medium and electronic equipment - Google Patents
Client interface unifying method, service system, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN114430428B CN114430428B CN202210340842.6A CN202210340842A CN114430428B CN 114430428 B CN114430428 B CN 114430428B CN 202210340842 A CN202210340842 A CN 202210340842A CN 114430428 B CN114430428 B CN 114430428B
- Authority
- CN
- China
- Prior art keywords
- request
- client
- requester
- data
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a client interface unifying method, a service system, a storage medium and electronic equipment, which can obtain routing data sent by a server aiming at a request of a requester through a client; checking the state of the user according to the state requirement of a preset functional module; if the user states are verified to be passed, corresponding service data is formed according to the routing data, and the service data comprises: module identification of the functional module and data required by the functional module; calling the function module through the unified interface according to the module identification of the function module, and inputting data required by the function module into the function module to execute corresponding service processing so as to obtain a corresponding processing result, wherein one unified interface corresponds to a plurality of function modules; and the client sends the processing result to the requester. The invention can call a plurality of functional modules through one unified interface, thereby reducing the number of interfaces, avoiding exposing the interfaces and being safe and reliable.
Description
Technical Field
The present invention relates to the field of data transmission, and in particular, to a method for unifying client interfaces, a service system, a storage medium, and an electronic device.
Background
At present, a third-party (requester) page is generally loaded in a browser of a client, and the client needs to directly expose an interface to the third-party page, which is neither safe nor convenient to manage.
There are two main problems: 1. a third party needs to call a plurality of functional modules, so that a client needs to expose a plurality of interfaces, and more interfaces are not beneficial to management; 2. the third party is not well managed, a plurality of interfaces are directly exposed, and potential safety hazards easily exist.
Disclosure of Invention
In view of the above, the present invention provides a client interface unifying method, a service system, a storage medium, and an electronic device that overcome or at least partially solve the above problems.
In a first aspect, a method for unifying client interfaces is applied to a service system, and the system includes: a server, a client and a requester;
the method comprises the following steps:
the client obtains routing data sent by the server aiming at the request of the requester, wherein the routing data at least carries a user identifier of a user initiating the request and a module identifier of a function module related to the request;
the client checks the state of the user according to a preset state requirement of the functional module, wherein the state requirement is as follows: when the functional module responds to the request, aiming at the state requirement of the user;
if the user state passes the verification, the client forms corresponding service data according to the routing data, wherein the service data comprises: module identification of the functional module and data required by the functional module;
the client calls the functional modules through unified interfaces according to the module identifiers of the functional modules, and inputs data required by the functional modules into the functional modules to execute corresponding service processing so as to obtain corresponding processing results, wherein one unified interface corresponds to a plurality of functional modules;
and the client side sends the processing result to the requester.
With reference to the first aspect, in some optional implementations, before the client obtains the routing data that the server sends for the request of the requester, the method further includes:
the server side obtains a request sent by the requester, wherein the request carries corresponding request information;
and the server performs decryption operation, signature verification operation and authentication operation on the request, and if the decryption operation, the signature verification operation and the authentication operation all pass, the routing data is formed and sent to the client.
With reference to the previous embodiment, in some optional embodiments, the performing, by the server, a decryption operation, a signature verification operation, and an authentication operation on the request, and if the decryption operation, the signature verification operation, and the authentication operation all pass, forming the routing data and sending the routing data to the client, includes:
the server side decrypts the request to obtain the request information, wherein the request information comprises: the authentication information calculated by the requester and the parameter information related to the authentication information;
the server side calculates to obtain current verification information according to parameter information related to the verification information through a pre-established rule;
the server compares the current verification information with the verification information calculated by the requester so as to perform the signature verification operation;
if the current verification information is consistent with the verification information calculated by the requester, determining whether the requester has the authority to call the function module related to the request so as to perform the authentication operation;
and if the authentication operation is passed, forming the routing data and sending the routing data to the client.
With reference to the first aspect, in some optional implementations, the forming, by the client, corresponding service data according to the routing data includes:
and the client splices all data in the routing data used by the corresponding functional module according to a pre-established data processing rule, thereby forming the service data.
With reference to the first aspect, in some optional implementations, the sending, by the client, the processing result to the requester includes:
and the client packages the processing result according to a preset format and sends the processing result to the requester after encryption operation and signature adding operation.
In a second aspect, a service system includes: a server, a client and a requester;
the client includes a routing module, the routing module including: the system comprises a routing data acquisition unit, a state verification unit, a service data forming unit, a service processing unit and a result sending unit;
the route data obtaining unit is configured to obtain route data sent by the server in response to the request of the requester, where the route data carries at least a user identifier of a user initiating the request and a module identifier of a function module involved in the request;
the state checking unit is configured to check the state of the user according to a preset state requirement of the functional module, where the state requirement is: when the functional module responds to the request, aiming at the state requirement of the user;
the service data forming unit is configured to form corresponding service data according to the routing data if the user status is verified to pass, where the service data includes: module identification of the functional module and data required by the functional module;
the service processing unit is used for calling the functional modules through unified interfaces according to the module identifiers of the functional modules and inputting data required by the functional modules into the functional modules to execute corresponding service processing so as to obtain corresponding processing results, wherein one unified interface corresponds to a plurality of functional modules;
and the result sending unit is used for sending the processing result to the requester.
With reference to the second aspect, in some optional embodiments, the server further includes: a request obtaining unit and a routing data forming unit;
the request obtaining unit is configured to obtain a request sent by the requester before the client obtains the routing data, which is sent by the server and is for the request of the requester, where the request carries corresponding request information;
and the routing data forming unit is used for performing decryption operation, signature verification operation and authentication operation on the request, and if the decryption operation, the signature verification operation and the authentication operation pass, the routing data is formed and sent to the client.
In combination with the previous embodiment, in some optional embodiments, the route data forming unit includes: the decryption subunit, the verification information calculation subunit, the signature verification subunit, the authentication subunit and the routing data forming subunit;
the decryption subunit is configured to perform a decryption operation on the request to obtain the request information, where the request information includes: the authentication information calculated by the requester and the parameter information related to the authentication information;
the verification information calculation subunit is used for calculating current verification information according to the parameter information related to the verification information through a pre-established rule;
the signature verification subunit is used for comparing the current verification information with the verification information calculated by the requester so as to perform the signature verification operation;
the authentication subunit is configured to determine whether the requester has an authority to invoke the function module related to the request to perform the authentication operation if the current verification information is consistent with the verification information calculated by the requester;
and the routing data forming subunit is used for forming the routing data and sending the routing data to the client if the authentication operation passes.
In a third aspect, a computer readable storage medium has a program stored thereon, which when executed by a processor implements the client interface unification method of any of the above.
In a fourth aspect, an electronic device comprises at least one processor, and at least one memory, bus, connected to the processor; the processor and the memory complete mutual communication through the bus; the processor is configured to call program instructions in the memory to perform any of the client interface unified methods described above.
By means of the technical scheme, the client interface unifying method, the service system, the storage medium and the electronic device provided by the invention can obtain the routing data sent by the server aiming at the request of the requester through the client, wherein the routing data at least carries the user identification of the user initiating the request and the module identification of the function module related to the request; the client checks the state of the user according to a preset state requirement of the functional module, wherein the state requirement is as follows: when the functional module responds to the request, aiming at the state requirement of the user; if the user state passes the verification, the client forms corresponding service data according to the routing data, wherein the service data comprises: module identification of the functional module and data required by the functional module; the client calls the functional modules through unified interfaces according to the module identifiers of the functional modules, and inputs data required by the functional modules into the functional modules to execute corresponding service processing so as to obtain corresponding processing results, wherein one unified interface corresponds to a plurality of functional modules; and the client side sends the processing result to the requester. Therefore, the invention can call a plurality of functional modules through one unified interface, thereby reducing the number of interfaces, avoiding exposing the interfaces, and being safe and reliable.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flow chart illustrating a method for client interface unification provided by the present invention;
FIG. 2 is a schematic structural diagram of a service system provided by the present invention;
fig. 3 shows a schematic structural diagram of an electronic device provided by the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The invention provides a client interface unifying method, which is applied to a service system, and the system comprises: a server, a client and a requester;
as shown in fig. 1, the method includes: s100, S200, S300, S400, and S500;
s100, the client side obtains routing data sent by the server side according to the request of the requester;
wherein, the routing data at least carries the user identification of the user who initiates the request and the module identification of the function module related to the request;
alternatively, the present invention may be applied to systems in the banking field. The client can be understood as application software installed in a mobile terminal (a mobile phone, a computer and the like) of a client. The server can be understood as a network server and an application server which are communicated with the client.
The merchant as a bank also has a corresponding client, but generally, the client of the merchant is embedded in the app of the bank in a web page form, and the requester can be understood as the web page of the merchant. The web page terminal of the merchant calls an interface of the client terminal to interact with the server terminal, processes the information, performs processes such as face recognition, networking check, photo and model acquisition, verification and the like, and then returns the result to the web page terminal of the merchant.
Alternatively, the routing data may be understood as: information indicating which flows the client needs to perform. For example, if the OCR function needs to be executed, the routing data indicates that the client needs to invoke the "authentication" function first, so as to allow the client to take a picture or scan the id card.
Optionally, the raw data here refers to a request of a requester of the merchant. For example, the raw data indicates "what kind of information is requested by the merchant, what authentication information is carried", and the like. The original data may be sent to the interface module of the server through the same interface (e.g., JS interface) set in the client, which is not limited in the present invention.
Optionally, the JS interface refers to a JavaScript interface provided by the client, and is implemented by the client and provided in Webview.
For example, the client calls a JS interface when logging in UI interaction on a page by using the 'panning of the merchant' function, and informs the server of the user number and the mobile phone number of the client needing authorization to log in at present through the JS interface so that the server performs corresponding processing.
For another example, when the function is called, for example, the "social security card area" calling interface tells the server that the "face recognition" function needs to be used, and the name and the identification number of the client (the whole message is a ciphertext) are uploaded, so that the server performs corresponding processing.
Optionally, the user mentioned in the present invention may correspond to a customer, and the user identifier may be a name, a mobile phone number, an identification number, and the like. The module identification of the functional module to which the request relates can be understood as: the client is the module identification of the function module required to be called for the request of the corresponding merchant. Of course, the routing data may carry other information or data besides the user identifier and the module identifier, which is not limited in the present invention.
Optionally, in combination with the embodiment shown in fig. 1, in some optional embodiments, before S100, the method further includes: step 1.1 and step 1.2;
step 1.1, the server side obtains a request sent by the requester, wherein the request carries corresponding request information;
optionally, the request information mentioned here can be understood as the specific information in the original data, and the present invention is not limited to this.
And step 1.2, the server side carries out decryption operation, signature verification operation and authentication operation on the request, if the decryption operation, the signature verification operation and the authentication operation pass, the routing data is formed and sent to the client side.
Optionally, in practice, sensitive information of the client amount to be verified needs to be protected, and interception and tampering in the process are prevented. Therefore, the client needs to encrypt the request when sending the request, and the corresponding server needs to decrypt the request after receiving the request.
Optionally, specific service parameters of different functional modules are different. But in general, it generally comprises: merchant number, function number, signature verification information (verification information calculated by self splicing of the merchant) and service parameters (such as OCR information). The label checking process comprises the following steps: and splicing the merchant number, the function number, the service parameter and the timestamp together, and calculating an abstract value according to the merchant-side key. And the server side carries out splicing calculation comparison in the same way. If the contents are the same, the contents are not tampered, and the authentication operation is continued; if the difference is not the same, the content is indicated to be in a problem, and the service can be refused.
Optionally, after the service end decrypts the transaction, the service end may execute a corresponding authentication operation, thereby determining whether the merchant has an authority to invoke the function module, if so, continuing the transaction, and if not, rejecting the service.
In combination with the previous embodiment, in certain alternative embodiments, the step 1.2 comprises: step 2.1, step 2.2, step 2.3, step 2.4 and step 2.5;
step 2.1, the server decrypts the request to obtain the request information, wherein the request information includes: the authentication information calculated by the requester and the parameter information related to the authentication information;
optionally, the parameter information related to the verification information may include: merchant number, function number, service parameter, timestamp and other information.
Step 2.2, the server calculates to obtain the current verification information according to the parameter information related to the verification information through a pre-established rule;
optionally, the rule for the server to calculate the current verification information is consistent with the rule for the requester to calculate the verification information, which is not limited in the present invention.
Step 2.3, the server compares the current verification information with the verification information calculated by the requester so as to perform the signature verification operation;
optionally, as described above, when the requester sends the request, the requester calculates the verification information using the same rule, and sends the verification information and the parameter information related to the verification information to the server. And the server receives the parameter information related to the verification information and also calculates the current verification information by using the same rule. If the parameter information is not tampered in the transmission process, the current verification information calculated by the server side and the verification information calculated by the requester side are consistent, and if the parameter information is not consistent, the parameter information is tampered in the transmission process, namely, the verification tag does not pass.
Step 2.4, if the current verification information is consistent with the verification information calculated by the requester, determining whether the requester has the authority to call the function module related to the request so as to perform the authentication operation;
optionally, as mentioned above, the authentication operation is to determine whether the requesting party has the right to invoke the function module involved in the request. Namely, whether the merchant has the authority to call the corresponding function module is determined. For example, the background configuration data is checked according to the user identification, and whether the function module can be called is judged.
Optionally, the authentication operation may be performed after the result of the signature verification operation is "pass", or may be performed in parallel with the signature verification operation. That is, the signature verification operation and the authentication operation are executed independently, and it is not necessary to use a certain one as a premise, which is not limited by the present invention.
And 2.5, if the authentication operation is passed, forming the routing data and sending the routing data to the client.
Optionally, if both the signature verification operation and the authentication operation pass, the request information may be sorted and processed to form corresponding routing data, which is not limited in the present invention.
S200, the client checks the state of the user according to the preset state requirement of the functional module;
wherein the status requirements are: when the functional module responds to the request, aiming at the state requirement of the user;
optionally, the status requirements of different functional modules are different. For example, the payment module requires that the client has external transfer authority, and the function of checking personal transaction details requires that the client is in a login state. Various state requirements such as "checking external transfer authority", "checking client state (whether a user is a section)", "checking whether login is performed", "checking whether storage authority is opened", "checking whether camera authority is opened" and "checking whether an account is bound" can be provided, and the setting is specifically performed according to the requirements of different functional modules.
S300, if the user state is verified to pass, the client forms corresponding service data according to the routing data, wherein the service data comprises: module identification of the functional module and data required by the functional module;
optionally, as mentioned above, the status requirements of different functional modules are different, and one functional module may have multiple status requirements in multiple aspects at the same time. Therefore, only when the user state is checked to pass, the client forms corresponding service data according to the routing data.
Optionally, the service data may be understood as: and data of specific services required by the corresponding functional module. If the function of 'face recognition without customer information' is aimed at, the customer information is not stored in the bank, and the name and identity card number is sent by the merchant in an encrypted manner. However, the action data, storage location, execution number, and the like required in the functional module need to be generated and synchronized by the server to the client, and processed by the client.
Optionally, the present invention may strip the routing data first, and then check the state of the user. Stripping the routing data can be understood as: the routing data is processed into data usable by the corresponding functional module. If the routing data sent to the client by the server side is provided with a calling face recognition module, data verification with the name xxx and the identification number xxx is used, the client peels the information and processes the information into a name: xxx, identification number: xxx ", and the corresponding service data is formed subsequently according to the stripped data, which is not limited in the present invention.
For example, with reference to the embodiment shown in fig. 1, in some optional embodiments, the forming, by the client in S300, corresponding service data according to the routing data includes: and the client splices all data in the routing data used by the corresponding functional module according to a pre-established data processing rule, thereby forming the service data.
Optionally, the module identifier of the functional module may correspond to the functional meaning, that is, the present invention may also set a corresponding function identifier for each function, and replace the module identifier of the functional module with the function identifier, which is not limited in the present invention.
S400, the client calls the functional modules through unified interfaces according to the module identifiers of the functional modules, and inputs data required by the functional modules into the functional modules to execute corresponding service processing so as to obtain corresponding processing results, wherein one unified interface corresponds to a plurality of functional modules;
optionally, the interface module of the client may call a corresponding function as a unified interface. For example, clicking the "upload icon" on a settings page in current instant messaging software would enter the "select picture" (take a picture or select a gallery of pictures) function. Similarly, if the UI on the web page of the merchant is face recognition, the UI is transmitted to the module identifier and data of the face recognition module through the corresponding unified interface, so as to call the corresponding function module.
Optionally, after the functional modules execute the respective services, the functional modules may generate corresponding service processing results. For example, after the face recognition module recognizes a face shot by the camera, a corresponding recognition result may be generated, which is not limited in the present invention.
Optionally, the present invention may unify the interfaces to call different function modules, without requiring too many interfaces or exposing the interfaces to the requesting party, and has certain security and reliability.
S500, the client side sends the processing result to the request side.
Optionally, as described above, the initial request is initiated by the web page of the requesting party, so that the result should be finally returned to the requesting party, so that the requesting party displays the corresponding processing result, which is not limited in the present invention.
Optionally, the processing results returned by different functional modules are different. For example, the "no customer information face recognition" function returns information such as "this customer face recognition passes" to the merchant. The function of identification card identification returns the content of the identification card, such as name, sex, birth year and month, issuing organ and identification card number.
Optionally, the client may directly send the processing result to the requesting party, or may send the processing result to the requesting party after performing a certain processing. For example, in connection with the embodiment shown in fig. 1, in some alternative embodiments, the S500 includes: and the client packages the processing result according to a preset format and sends the processing result to the requester after encryption operation and signature adding operation.
Optionally, in order to protect the client's information from interception and to prevent tampering. The tagging operation may be performed first. That is, the return code, the return information, the service information, the timestamp, and the like in the processing result are concatenated, and the digest value is calculated by the key and added to the message.
Optionally, the encryption operation is performed after the signing operation is performed. I.e. the entire message is encrypted using the public key.
Alternatively, the encryption operation and the decryption operation of the present invention may be based on the SM4 algorithm, and the corresponding keys are distributed, which is not limited by the present invention.
As shown in fig. 2, the present invention provides a service system including: a server 1000, a client 2000, and a requestor 3000;
the client 2000 includes a routing module 100, and the routing module 100 includes: a routing data obtaining unit 110, a state checking unit 120, a service data forming unit 130, a service processing unit 140 and a result transmitting unit 150;
the routing data obtaining unit 110 is configured to obtain routing data sent by the server 1000 for the request of the requestor 3000, where the routing data carries at least a user identifier of a user initiating the request and a module identifier of a function module involved in the request;
the state checking unit 120 is configured to check the state of the user according to a preset state requirement of the functional module, where the state requirement is: when the functional module responds to the request, aiming at the state requirement of the user;
the service data forming unit 130 is configured to form corresponding service data according to the routing data if the user status is verified to pass, where the service data includes: module identification of the functional module and data required by the functional module;
the service processing unit 140 is configured to call the functional module through a unified interface according to the module identifier of the functional module, and input data required by the functional module to execute corresponding service processing, so as to obtain a corresponding processing result, where one unified interface corresponds to multiple functional modules;
the result sending unit 150 is configured to send the processing result to the requester 3000.
In some optional embodiments, in combination with the embodiment shown in fig. 2, the server 1000 further includes: a request obtaining unit and a route data forming unit;
the request obtaining unit is configured to obtain the request sent by the requester 3000 before the client 2000 obtains the routing data, which is sent by the server 1000 for the request of the requester 3000, where the request carries corresponding request information;
the routing data forming unit is configured to perform decryption operation, signature verification operation, and authentication operation on the request, and if the decryption operation, the signature verification operation, and the authentication operation all pass, form the routing data and send the routing data to the client 2000.
In combination with the previous embodiment, in some optional embodiments, the route data forming unit includes: the decryption subunit, the verification information calculation subunit, the signature verification subunit, the authentication subunit and the routing data forming subunit;
the decryption subunit is configured to perform a decryption operation on the request to obtain the request information, where the request information includes: authentication information calculated by the requester 3000 and parameter information related to the authentication information;
the verification information calculation subunit is used for calculating current verification information according to the parameter information related to the verification information through a pre-established rule;
the signature verification subunit is configured to compare the current verification information with the verification information calculated by the requester 3000, so as to perform the signature verification operation;
the authentication subunit is configured to determine whether the requester 3000 has an authority to invoke the function module related to the request to perform the authentication operation if the current verification information is consistent with the verification information calculated by the requester 3000;
the routing data forming subunit is configured to form the routing data and send the routing data to the client 2000 if the authentication operation passes.
With reference to the embodiment shown in fig. 2, in some optional embodiments, the performing, by the service data forming unit 130, the client 2000 to form corresponding service data according to the routing data specifically includes: a service data forming subunit;
and the service data forming subunit is used for splicing all data in the routing data used by the corresponding functional module according to a pre-established data processing rule so as to form the service data.
In some optional embodiments, in combination with the embodiment shown in fig. 2, the result sending unit 150 includes: a result transmitting subunit;
the result sending subunit is configured to package the processing result according to a preset format, and send the processing result to the requester 3000 after performing an encryption operation and a signing operation.
The present invention provides a computer-readable storage medium having a program stored thereon, which when executed by a processor implements the client interface unifying method of any of the above.
As shown in fig. 3, the present invention provides an electronic device 70, wherein the electronic device 70 comprises at least one processor 701, at least one memory 702 connected to the processor 701, and a bus 703; the processor 701 and the memory 702 complete communication with each other through the bus 703; the processor 701 is configured to call the program instructions in the memory 702 to execute any one of the client interface unified methods described above.
In this application, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (10)
1. A method for unifying client interfaces is applied to a service system, and the system comprises: a server, a client and a requester;
the method comprises the following steps:
the client obtains routing data sent by the server aiming at the request of the requester, wherein the routing data at least carries a user identifier of a user initiating the request and a module identifier of a function module related to the request;
the client checks the state of the user according to a preset state requirement of the functional module, wherein the state requirement is as follows: when the functional module responds to the request, aiming at the state requirement of the user;
if the user state passes the verification, the client forms corresponding service data according to the routing data, wherein the service data comprises: module identification of the functional module and data required by the functional module;
the client calls the functional modules through unified interfaces according to the module identifiers of the functional modules, and inputs data required by the functional modules into the functional modules to execute corresponding service processing so as to obtain corresponding processing results, wherein one unified interface corresponds to a plurality of functional modules;
and the client side sends the processing result to the requester.
2. The method according to claim 1, wherein before the client obtains the routing data sent by the server for the request of the requester, the method further comprises:
the server side obtains a request sent by the requester, wherein the request carries corresponding request information;
and the server performs decryption operation, signature verification operation and authentication operation on the request, and if the decryption operation, the signature verification operation and the authentication operation all pass, the routing data is formed and sent to the client.
3. The method of claim 2, wherein the server performs a decryption operation, a signature verification operation, and an authentication operation on the request, and if the decryption operation, the signature verification operation, and the authentication operation all pass, the server forms the routing data and sends the routing data to the client, including:
the server side decrypts the request to obtain the request information, wherein the request information comprises: the authentication information calculated by the requester and the parameter information related to the authentication information;
the server side calculates to obtain current verification information according to parameter information related to the verification information through a pre-established rule;
the server compares the current verification information with the verification information calculated by the requester to perform the signature verification operation;
if the current verification information is consistent with the verification information calculated by the requester, determining whether the requester has the authority to call the function module related to the request so as to perform the authentication operation;
and if the authentication operation passes, forming the routing data and sending the routing data to the client.
4. The method of claim 1, wherein the client forms corresponding service data according to the routing data, and the method comprises:
and the client splices all data in the routing data used by the corresponding functional module according to a pre-established data processing rule, thereby forming the service data.
5. The method of claim 1, wherein the client sends the processing result to the requester, and wherein the sending comprises:
and the client packages the processing result according to a preset format and sends the processing result to the requester after encryption operation and signature adding operation.
6. A service system, comprising: a server, a client and a requester;
the client includes a routing module, the routing module including: the system comprises a routing data obtaining unit, a state checking unit, a service data forming unit, a service processing unit and a result sending unit;
the route data obtaining unit is configured to obtain route data sent by the server in response to the request of the requester, where the route data carries at least a user identifier of a user initiating the request and a module identifier of a function module involved in the request;
the state checking unit is configured to check the state of the user according to a preset state requirement of the functional module, where the state requirement is: when the functional module responds to the request, aiming at the state requirement of the user;
the service data forming unit is configured to form corresponding service data according to the routing data if the user status is verified to pass, where the service data includes: module identification of the functional module and data required by the functional module;
the service processing unit is used for calling the functional modules through unified interfaces according to the module identifiers of the functional modules and inputting data required by the functional modules into the functional modules to execute corresponding service processing so as to obtain corresponding processing results, wherein one unified interface corresponds to a plurality of functional modules;
and the result sending unit is used for sending the processing result to the requester.
7. The system of claim 6, wherein the server further comprises: a request obtaining unit and a route data forming unit;
the request obtaining unit is configured to obtain a request sent by the requester before the client obtains the routing data that is sent by the server for the request of the requester, where the request carries corresponding request information;
and the routing data forming unit is used for performing decryption operation, signature verification operation and authentication operation on the request, and if the decryption operation, the signature verification operation and the authentication operation pass, the routing data is formed and sent to the client.
8. The system according to claim 7, wherein the route data forming unit comprises: the decryption subunit, the verification information calculation subunit, the signature verification subunit, the authentication subunit and the routing data forming subunit;
the decryption subunit is configured to perform a decryption operation on the request to obtain the request information, where the request information includes: the authentication information calculated by the requester and the parameter information related to the authentication information;
the verification information calculation subunit is used for calculating current verification information according to the parameter information related to the verification information through a pre-established rule;
the signature verification subunit is used for comparing the current verification information with the verification information calculated by the requester so as to perform the signature verification operation;
the authentication subunit is configured to determine whether the requester has an authority to invoke the function module related to the request to perform the authentication operation if the current verification information is consistent with the verification information calculated by the requester;
and the routing data forming subunit is used for forming the routing data and sending the routing data to the client if the authentication operation passes.
9. A computer-readable storage medium on which a program is stored, the program, when executed by a processor, implementing the client interface unifying method according to any one of claims 1 to 5.
10. An electronic device comprising at least one processor, and at least one memory, bus connected to the processor; the processor and the memory complete mutual communication through the bus; the processor is configured to invoke program instructions in the memory to perform the client interface unified method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210340842.6A CN114430428B (en) | 2022-04-02 | 2022-04-02 | Client interface unifying method, service system, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210340842.6A CN114430428B (en) | 2022-04-02 | 2022-04-02 | Client interface unifying method, service system, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114430428A CN114430428A (en) | 2022-05-03 |
| CN114430428B true CN114430428B (en) | 2022-07-05 |
Family
ID=81314256
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210340842.6A Active CN114430428B (en) | 2022-04-02 | 2022-04-02 | Client interface unifying method, service system, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114430428B (en) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102387075B (en) * | 2011-10-18 | 2014-07-09 | 成都康赛信息技术有限公司 | Dynamic service routing method and device for enterprise service bus |
| RU2011154492A (en) * | 2011-12-30 | 2013-07-27 | Май Партнерс Анд Глобал Старс Инвестментс (Мп&Гси) Лтд | SYSTEM OF PAYMENT OF ELECTRONIC CHECKS AND METHODS OF ISSUE, TRANSFER OF PAYMENT AND VERIFICATION OF ELECTRONIC CHECKS |
| CN110830493B (en) * | 2019-11-14 | 2022-02-25 | 北京京航计算通讯研究所 | Single sign-on implementation method based on intelligent enterprise portal |
| CN112184222B (en) * | 2020-05-29 | 2022-09-30 | 支付宝(杭州)信息技术有限公司 | Service processing method, device and equipment based on block chain |
| CN112702402A (en) * | 2020-12-16 | 2021-04-23 | 普元信息技术股份有限公司 | System, method, device, processor and storage medium for realizing government affair information resource sharing and exchange based on block chain technology |
-
2022
- 2022-04-02 CN CN202210340842.6A patent/CN114430428B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN114430428A (en) | 2022-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11283797B2 (en) | Authenticating a user device associated with a user to communicate via a wireless network in a secure web-based environment | |
| CN108200050B (en) | Single sign-on server, method and computer readable storage medium | |
| US10142114B2 (en) | ID system and program, and ID method | |
| US9648013B2 (en) | Systems, methods and devices for performing passcode authentication | |
| US20140244451A1 (en) | E-commerce transaction verification system and method | |
| CN111488596A (en) | Data processing permission verification method and device, electronic equipment and storage medium | |
| CN109347865B (en) | User data authentication and evidence storage method and system based on block chain technology | |
| KR20210095705A (en) | Techniques for securely performing offline authentication | |
| EP3151180A1 (en) | Identification method and system | |
| WO2024109551A1 (en) | Digital payment processing method and apparatus, and device, system and medium | |
| KR102116587B1 (en) | Method and system using a cyber id to provide secure transactions | |
| CN111062059B (en) | Method and device for service processing | |
| CN112819675A (en) | Banking affair flow control method and device | |
| CN114430428B (en) | Client interface unifying method, service system, storage medium and electronic equipment | |
| CN110544087A (en) | Mobile payment method, device, equipment and computer readable storage medium | |
| TWI618008B (en) | Transaction fee negotiation for currency remittance | |
| CN115482132A (en) | Data processing method and device for electronic contract based on block chain and server | |
| JP7461241B2 (en) | Customer information management server and customer information management method | |
| CN110365646B (en) | Method and device for associating entity to first server | |
| CN109191116B (en) | Resource management method and system and payment management method and system | |
| JP2022120314A (en) | Personal information management device, terminal and terminal program | |
| CN112000713A (en) | Data processing method, device, equipment and medium | |
| EP4250207B1 (en) | Devices, methods and a system for secure electronic payment transactions | |
| CN110750808B (en) | Bill processing method and device and storage medium device | |
| KR101232581B1 (en) | Payment processing system and control method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |