WO2019140790A1 - 业务跟踪方法、装置、终端设备及存储介质 - Google Patents

业务跟踪方法、装置、终端设备及存储介质 Download PDF

Info

Publication number
WO2019140790A1
WO2019140790A1 PCT/CN2018/081560 CN2018081560W WO2019140790A1 WO 2019140790 A1 WO2019140790 A1 WO 2019140790A1 CN 2018081560 W CN2018081560 W CN 2018081560W WO 2019140790 A1 WO2019140790 A1 WO 2019140790A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
verification code
verification
server
signature factor
Prior art date
Application number
PCT/CN2018/081560
Other languages
English (en)
French (fr)
Inventor
李波
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019140790A1 publication Critical patent/WO2019140790A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display
    • 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
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • 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
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a service tracking method, apparatus, terminal device, and storage medium.
  • the embodiment of the present application provides a service tracking method, device, terminal device, and storage medium, so as to solve the problem that each type of service can only verify the last received short message verification code and cause waste of resources.
  • the embodiment of the present application provides a service tracking method, including the following steps performed by a service server:
  • the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID;
  • the service information corresponding to the service ID is obtained, and the client is controlled to display the service information.
  • the embodiment of the present application provides a service tracking method, including the following steps performed by an authentication server:
  • the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID;
  • the verification result is sent to the service server, so that the client displays the business information when the verification result is passed.
  • the embodiment of the present application provides a service tracking device, including a service server, where the service server includes:
  • Receiving a verification code confirmation request module configured to receive a verification code confirmation request sent by the client, where the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID;
  • Sending a verification code confirmation request module configured to send a verification code confirmation request to the verification server
  • Receiving a verification result module configured to receive a verification result sent by the verification server, where the verification result is obtained based on a client verification code and a service verification code corresponding to the comparison signature factor;
  • the service information module is configured to obtain service information corresponding to the service ID when the verification result is passed, and control the client to display the service information.
  • the embodiment of the present application provides a service tracking apparatus, including an authentication server, where the verification server includes:
  • Receiving a verification code confirmation request module configured to receive a verification code confirmation request sent by the service server, where the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID;
  • Obtaining a service verification code module configured to query a database based on a signature factor, and obtain a service verification code stored in association;
  • Obtaining a verification result module configured to obtain a verification result by using a client verification code and a service verification code corresponding to the signature factor;
  • the verification result module is sent to send the verification result to the service server, so that the client displays the service information when the verification result is passed.
  • a fifth aspect of the present application provides a terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, when the processor executes the computer readable instructions Implement the following steps:
  • the service server receives the verification code confirmation request sent by the client, and the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID;
  • the service server sends a verification code confirmation request to the verification server
  • the service server receives the verification result sent by the verification server, and the verification result is obtained based on the client verification code and the service verification code corresponding to the comparison signature factor;
  • the service server obtains the service information corresponding to the service ID, and controls the client to display the service information.
  • a sixth aspect of the present application provides a terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, when the processor executes the computer readable instructions Implement the following steps:
  • the verification server receives the verification code confirmation request sent by the service server, and the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID;
  • the verification server queries the database based on the signature factor to obtain the service verification code of the associated storage;
  • the verification server obtains the verification result based on the client verification code and the service verification code corresponding to the signature factor;
  • the verification server sends the verification result to the service server, so that the client displays the business information when the verification result passes.
  • a seventh aspect of the present application provides one or more non-transitory readable storage mediums storing computer readable instructions, when executed by one or more processors, causing the one or more processes Perform the following steps:
  • the service server receives the verification code confirmation request sent by the client, and the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID;
  • the service server sends a verification code confirmation request to the verification server
  • the service server receives the verification result sent by the verification server, and the verification result is obtained based on the client verification code and the service verification code corresponding to the comparison signature factor;
  • the service server obtains the service information corresponding to the service ID, and controls the client to display the service information.
  • An eighth aspect of the present application provides one or more non-transitory readable storage mediums storing computer readable instructions, the computer readable instructions being executed by one or more processors such that the one or more processes Perform the following steps:
  • the verification server receives the verification code confirmation request sent by the service server, and the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID;
  • the verification server queries the database based on the signature factor to obtain the service verification code of the associated storage;
  • the verification server obtains the verification result based on the client verification code and the service verification code corresponding to the signature factor;
  • the verification server sends the verification result to the service server, so that the client displays the business information when the verification result passes.
  • the service server after the service server obtains the client verification code sent by the client, the service server sends the client verification code with the signature factor to the verification server for verification.
  • the service ID corresponding to the signature factor is obtained, so that the service information corresponding to the service ID is displayed to the client.
  • each service ID is matched with a corresponding signature factor, so that the client verification code sent from the client can trace the corresponding service information through the signature factor, thereby improving the use efficiency of the client verification code and saving the verification server.
  • FIG. 1 is a flowchart of a service tracking method in Embodiment 1 of the present application.
  • FIG. 2 is a schematic block diagram of a service tracking apparatus in Embodiment 2 of the present application.
  • FIG. 3 is a schematic diagram of a terminal device in Embodiment 4 of the present application.
  • the service tracking method includes the following steps performed by the service server:
  • the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID.
  • the verification result sent by the verification server is received, and the verification result is obtained based on the client verification code and the service verification code corresponding to the comparison signature factor.
  • the service information corresponding to the service ID is obtained, and the client is controlled to display the service information.
  • the service tracking method also includes the following steps performed by the verification server:
  • the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID.
  • the database is queried based on the signature factor, and the service verification code of the associated storage is obtained.
  • the verification result is obtained based on the client verification code and the service verification code corresponding to the signature factor.
  • the verification result is sent to the service server, so that the client displays the business information when the verification result is passed.
  • This embodiment is applied between a client, a personal terminal, a service server, and an authentication server that need to confirm service information through the Internet for realizing identity authentication.
  • a client is a service port that provides business information to a user, such as a web browser used by the World Wide Web, an email client when receiving an email, and various client software.
  • a service server is a server that displays business information to clients through various protocols.
  • the service server provides access to business information for use by clients, such as online video, online banking, and electronic maps.
  • Business service programs provided by business service providers, such as database services, email services, etc.
  • the client needs to work with the business server installed on the service provider side.
  • the client and the business server establish a network connection to ensure the normal operation of the service program.
  • the personal terminal is a software port or hardware device that is exclusive to each person, such as a personal instant messaging software interface, a mobile phone, and the like.
  • the personal terminal is identified by the user ID, that is, the user can locate the personal terminal by using the user ID.
  • the user ID is the mobile phone number
  • the QQ chat software the user ID is the QQ number.
  • the personal terminal can connect the terminal information sent by the various servers through the network, and is used to receive the service verification code sent by the verification server in this embodiment.
  • the verification server is a third-party service program that provides verification services, and is applied to the embodiment to verify the reliability of the client.
  • the authentication server provides a connection port to the service server through the third-party interface, and is used to undertake the verification service specified by the service server.
  • the client and the personal terminal can be integrated; when the authentication server is an authentication software port installed on the service server, the service server and the authentication server Can also be combined into one.
  • the execution body of this embodiment includes a service server and an authentication server.
  • the service tracking method includes the following steps:
  • the service server receives a verification code acquisition request sent by the client, where the verification code acquisition request includes a service ID and a user ID.
  • the verification code acquisition request is a request sent by the client to the service server for requesting the service server to allocate the service verification code.
  • the user ID is an identifier for identifying a user, including but not limited to a user-specific identification number such as a user's mobile phone number and a user's micro-signal.
  • the service ID is an identifier for identifying the service
  • the server obtains a request for each verification code according to the received one, and assigns a unique service ID to the verification code acquisition request for identifying the service to be applied for.
  • each of the verification code acquisition requests sent by the client is assigned a corresponding service ID, and different service information in multiple verification code acquisition requests sent by the same client can be distinguished to facilitate subsequent tracking.
  • the user ID facilitates the business server to determine the identity reliability of the client.
  • the service server generates a signature factor corresponding to the service ID based on the verification code acquisition request.
  • the signature factor is a unique record number set by the service server for each service information, that is, the signature factor and each service information are in a one-to-one relationship.
  • Each business information corresponds to a corresponding service ID, that is, the signature factor and the service ID are also one-to-one relationships.
  • the service ID can be used to obtain the corresponding service information. If the information is directly exchanged with the third party through the service ID, the information may be leaked to the client, causing unpredictable loss. Therefore, it is necessary to set a signature factor corresponding to the service ID, and use the signature factor to interact with the third party for tracking each business information.
  • each service information can be traced through the signature factor, which is safe and effective.
  • generating a signature factor corresponding to the service ID includes the following steps: processing the service ID based on the UUID algorithm, and generating a signature factor corresponding to the service ID.
  • UUID Universally Unique Identifier
  • OSF Open Software Foundation
  • UUID is guaranteed to be unique to all machines in the same time and space. According to the standard calculated by the OSF, the Ethernet card address, nanosecond time, chip ID code and many possible numbers are used.
  • the UUID consists of a combination of the following:
  • the current date and time, the first part of the UUID is related to time. If a UUID is generated after a few seconds after generating a UUID, the first part is different and the others are the same.
  • the standard UUID format is: xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxxxx (8-4-4-4-12), where each x is a hexadecimal number in the range 0-9 or a-f.
  • the uniqueness of the signature factor is greatly ensured, and each specific service ID corresponding to the signature factor can be traced back to the massive data.
  • the service tracking method further includes: storing the signature factor in association with the service ID.
  • the signature factor and the service ID are stored in association, so that the service server can quickly locate the service ID corresponding to the signature factor in the database according to the signature factor.
  • the service server generates a verification code generation request based on the signature factor, where the verification code generation request includes a signature factor and a user ID.
  • the verification code generation request is sent by the service server to the verification server, and is used to request the verification server to allocate a service verification code to the client.
  • the service verification code is generated based on the signature factor, and the service verification code needs to be sent to the personal terminal corresponding to the user ID. Therefore, the service server needs to add the user ID and the signature factor associated with the service ID to the verification code generation.
  • the verification code generation request is sent to the verification server.
  • the service ID and the service verification code are associated by the same signature factor, and the client can perform comparison when performing identity verification.
  • the client verification code sent by the client and the verification server are the same as the service verification code stored by the same signature factor, indicating that the client verification code sent by the same client can determine that the client is reliable, simple and convenient.
  • the service server sends a verification code generation request to the verification server, so that the verification server generates a service verification code based on the signature factor, and sends the service verification code to the personal terminal corresponding to the user ID.
  • the service server sends a verification code generation request to the verification server, so that the verification server generates a service verification code based on the signature factor, and sends the service verification code to the personal terminal corresponding to the user ID, and the user according to the received service verification code. , enter the client verification code to the client to authenticate the client.
  • the verification server generates a service verification code based on the signature factor, and sends the user ID to the client-specific personal terminal, so that the reliability of the identity authentication of the client can be ensured.
  • the service ID and the generated service verification code are simultaneously associated with the same signature factor, and the service verification code is formed into a one-to-one relationship with the service ID through the mapping of the signature factor, so that the subsequent verification by the service verification code can be accurately located. Go to the corresponding business ID.
  • the verification server receives the verification code generation request sent by the service server, and the verification code generation request includes a signature factor and a user ID.
  • the service server provides a user ID and a signature factor associated with the service ID in the verification code generation request, so that the verification server can generate the service verification code according to the signature factor when receiving the verification code generation request sent by the service server. And sending the generated service verification code to the corresponding personal terminal according to the user ID.
  • the verification server generates a corresponding service verification code based on the signature factor, and stores the service verification code in association with the signature factor.
  • the service verification code is applied to the embodiment, which may be a short message verification code.
  • the short message verification code can be set as the character verification code, and the candidate characters are first selected to consider the number and the English characters or both.
  • the numeric characters can be 0-9, and the English characters can be selected from 26 English letters. Among them, the length of the candidate character array can be increased considering that the English letters are case-sensitive.
  • the service verification code and the signature factor may be stored as a SESSION (session control) object for storing attributes and configuration information required for a specific user session.
  • SESSION session control
  • the characteristic of the SESSION object is that when the user jumps between the WEB pages of the application, the variables stored in the SESSION object will not be lost, but will persist throughout the user session.
  • One of the most common uses of SESSION objects is to store user preferences, such as business verification codes.
  • the comparison verification template is provided to the verification server by obtaining the service verification code, which is convenient for the verification server to make timely and correct judgments.
  • the corresponding service verification code is generated based on the signature factor, including: processing the signature factor based on the short message verification code interface and the preset short message verification code format, and generating a service verification code corresponding to the signature factor.
  • the verification server may be a short message platform, and the service verification code is applied to the short message verification code in the embodiment, and the short message verification code interface is a service interface reserved by the short message platform to the service server.
  • the preset SMS verification code format includes the expression form, length and generation algorithm of the verification code.
  • the SMS verification code can be set as the character verification code for the convenience of the customer operation, and the number and the English character or two are first considered when selecting the candidate character. Superimposed use.
  • the numeric characters can be 0-9, and the English characters can be selected from 26 English letters.
  • the length of the candidate character array can be increased considering that the English letters are case-sensitive.
  • the length of the short message verification code can be set to 6 digits, that is, three quarters of a byte (one digit occupies one eighth of a byte).
  • MD5 Message Digest Algorithm MD5, message digest algorithm fifth edition
  • MD5 belongs to a hash algorithm with high security performance. For the input of two different data, there will be an output value after the operation, but the obtained value is not reversible, and the original plaintext cannot be obtained.
  • the MD5 algorithm divides the input information by 512 digits in a grouping manner, and after standard processing, four 32-bit packets are obtained and sent to the target user's mobile phone. Because the entire MD5 algorithm is more rigorous, it greatly guarantees its security and is an excellent encryption algorithm.
  • the signature factor is processed by the short message verification code interface and the preset short message verification code format, and the short message verification code (ie, the service verification code) generated by the reliable algorithm ensures the service verification code received by the client. Security to avoid information leakage.
  • the verification server sends the service verification code to the personal terminal corresponding to the user ID.
  • the verification server sends the service verification code to the personal terminal corresponding to the user ID, and the service verification code received by the user through the personal terminal is used to perform identity verification based on the service verification code displayed by the personal terminal, which can effectively ensure The reliability and security of the client user identity.
  • the service server receives the verification code acquisition request initiated by the client, and assigns a unique signature factor to the service ID in the verification code acquisition request.
  • the service server assigns the task of generating the service verification code to the verification server for execution, and also sends the signature factor to the verification server.
  • the verification server will generate a personal terminal corresponding to the service verification code user ID based on the signature factor, so as to perform subsequent client verification code authentication.
  • the subsequent step can be clearly traced back to the service information corresponding to the corresponding service ID by the client verification code sent by the client; that is, if the client verifies After the code is verified, the customer verification code can implement a business information, which improves the efficiency of the client verification code.
  • the client may send a client verification code to the service server based on the service verification code, for verifying the reliability of the identity to the service server. Get the corresponding business information.
  • the service server receives the verification code confirmation request sent by the client, and the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID.
  • the verification code confirmation request is that the client initiates an acknowledgment identity reliability request to the service server by inputting the verification code information.
  • the client verification code is a verification code input by the user to the business service for authentication, and the client verification code can be a 6-digit SMS verification code.
  • the verification server sends the service verification code to the personal terminal, so that the user can obtain the service verification code through the personal terminal, the client can input a verification code confirmation request to the service server, and the verification code confirms the client verification code in the request.
  • the client initiates the verification code confirmation request to obtain a service information request. Therefore, the service server also allocates a signature factor for the service ID to distinguish each service information. Since the verification code confirmation request is used to verify whether the service information corresponding to the service ID is displayed to the client, the verification code confirmation request is required to carry the signature factor, so as to search for the service pre-allocated to the signature factor based on the signature factor. The verification code is compared with the client verification code to achieve identity verification.
  • the service server records the signature factor corresponding to the service ID, so that the subsequent step can accurately track and distinguish different service information by using the signature factor.
  • the service server sends a verification code confirmation request to the verification server.
  • the verification server is a server for verifying the correctness of the client authentication code input by the client.
  • the service server is dedicated to providing service information, and the user identity cannot be verified. Therefore, the service server needs to send the generated verification code confirmation request to the verification server, so that the verification server compares the service verification code pre-assigned to the client. Check whether the client's identity is consistent with the client's authentication code sent by the client.
  • the service server authenticates the client by sending a verification code confirmation request to the verification server, thereby implementing an explicit task division between the servers, that is, the service server is dedicated to providing service information, and the verification server is dedicated to the verification server. Authenticating the client increases the speed at which requests are processed.
  • the verification server receives the verification code confirmation request sent by the service server, and the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID.
  • the authentication server authenticates the client, it is required to obtain the client verification code and the signature factor provided in the verification code confirmation request.
  • the client verification code is the verification code that the user enters into the business service through the client for authentication.
  • the signature factor can be used to obtain a service verification code stored in the verification server corresponding to the signature factor, and only the verification code confirmation request provides the client verification code and the signature factor to determine the reliability of the client.
  • the verification server pre-stores the service verification code associated with the signature factor, and can quickly query and obtain the corresponding service verification code through the signature factor when the client is authenticated, so as to speed up the verification matching efficiency.
  • the verification server queries the database based on the signature factor, and obtains a service verification code stored in association with the signature factor.
  • the service verification code is a verification code for performing identity verification, which is generated in advance and stored in the verification server, and may be a short message verification code in this embodiment.
  • the short message verification code can be set as the character verification code, and the candidate characters are first considered to be numeric, English characters or both.
  • the numeric characters can be 0-9, and the English characters can be selected from 26 English letters.
  • the length of the candidate character array can be increased considering that the English letters are case-sensitive.
  • the database applied to this embodiment can create a SESSION (session control) object for storing attributes and configuration information required for a particular user session, such as a service verification code associated with a signature factor.
  • SESSION session control
  • attributes and configuration information required for a particular user session such as a service verification code associated with a signature factor.
  • the service verification code is obtained by using a signature factor to provide a comparison template to the verification server, which facilitates the verification server to make timely and correct judgments.
  • the verification server obtains the verification result based on the client verification code and the service verification code corresponding to the signature factor.
  • the verification result is a pass, indicating that the identity of the client is reliable and secure, and the client may be provided with Further service; otherwise, the verification result is not passed, and the identity of the client needs to be re-verified.
  • the verification server sends the verification result to the service server, so that the client displays the service information corresponding to the service ID when the verification result passes.
  • the general verification results include two types: verification pass and verification fail.
  • verification pass when the verification result is passed, the client verification code corresponding to the signature factor in the verification code confirmation request is the same as the service verification code; when the verification result is not passed, the signature in the verification code confirmation request is indicated.
  • the client verification code and the service verification code corresponding to the factor are different.
  • the verification server sends the verification result back to the service server in time, which facilitates the service server to timely provide action feedback to the client, thereby improving service processing efficiency.
  • the service server receives the verification result sent by the verification server, and the verification result is obtained based on the client verification code and the service verification code corresponding to the comparison signature factor.
  • the service server obtains the verification result provided by the verification server, and the verification result is obtained based on whether the client verification code and the service verification code corresponding to the comparison signature factor are consistent, that is, if the client verification code and the service verification code corresponding to the signature factor are the same , the verification result is passed; if the client verification code and the service verification code corresponding to the signature factor are not the same, the verification result is not passed.
  • the service server determines whether to provide service information to the client according to whether the verification result is passed. In this embodiment, the service server can provide corresponding feedback to the client in time based on the verification result of the verification server to the client identity verification, thereby improving the customer experience.
  • the service server obtains service information corresponding to the service ID when the verification result is passed, and controls the client to display the service information.
  • the service information is service information that the client requests to provide to the service server through the verification code confirmation request, and the service information can play video for the network video server, and the online bank provides the corresponding banking service or the electronic map to expand the map information.
  • the service server may be queried according to the service ID in the verification code confirmation request, and the service information corresponding to the service ID is obtained.
  • the service server traces back to the corresponding service information according to the service ID corresponding to the signature factor in the verification result. Because the signature factor corresponds to the client verification code and the service ID respectively, that is, the mapping relationship between the client verification code and the service ID is formed by the mapping of the signature factor, thereby improving the use efficiency of the client verification code.
  • the service server obtains the verification code confirmation request sent by the client, and sends the client verification code corresponding to the signature factor to the verification server for verification.
  • the verification server verifies the service verification code and the client verification code corresponding to the signature factor, and feeds back the verification result.
  • the service information corresponding to the service ID is obtained by the service server and displayed.
  • the client verification code sent from the client can trace the corresponding service verification code through the signature factor, and obtain the service ID when the verification is passed.
  • the corresponding service information improves the use efficiency of the client verification code, and saves the waste of resources caused by the verification server generating multiple service verification codes for the same service ID.
  • FIG. 2 is a schematic block diagram showing a service tracking device corresponding to the service tracking method in the first embodiment.
  • the service tracking device includes a service server 20 and an authentication server 10.
  • the service server 20 includes a receive verification code confirmation request module 21, a transmission verification code confirmation request module 22, a reception verification result module 23, and a display service information module 24.
  • the steps S21-S22 and S27-S28 corresponding to the service tracking method of the receiving verification code confirmation requesting module 21, the sending verification code confirmation requesting module 22, the receiving verification result module 23, and the display service information module 24 respectively correspond to the service tracking method in the embodiment.
  • the present embodiment will not be described in detail.
  • the receiving verification code confirmation requesting module 21 is configured to receive a verification code confirmation request sent by the client, where the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID.
  • the verification code confirmation request module 22 is configured to send the verification code confirmation request to the verification server.
  • the receiving verification result module 23 is configured to receive the verification result sent by the verification server, and the verification result is obtained based on the client verification code and the service verification code corresponding to the comparison signature factor.
  • the service information module 24 is configured to obtain service information corresponding to the service ID when the verification result is passed, and control the client to display the service information.
  • the service server 20 further includes a receiving verification code acquisition request module 25, a generation signature factor module 26, a generation verification code generation request module 27, and a transmission service verification code module 28.
  • the implementation functions of the received verification code acquisition requesting module 25, the generated signature generation module 26, the generated verification code generation request module 27, and the transmission service verification code module 28 respectively correspond to the steps S11 to S14 corresponding to the service tracking method in the embodiment, respectively. Avoiding the details, this embodiment will not be described in detail.
  • the receiving verification code acquisition requesting module 25 is configured to receive a verification code acquisition request sent by the client, where the verification code acquisition request includes a service ID and a user ID.
  • a signature factor module 26 is generated for generating a signature factor corresponding to the service ID based on the verification code acquisition request.
  • a verification code generation requesting module 27 is generated for generating a verification code generation request based on the signature factor, the verification code generation request including a signature factor and a user ID.
  • the verification code generation requesting module 28 is configured to send the verification code generation request to the verification server, so that the verification server generates the service verification code based on the signature factor, and sends the service verification code to the personal terminal corresponding to the user ID.
  • a signature factor module 26 is generated for processing the service ID based on the UUID algorithm to generate a signature factor corresponding to the service ID.
  • the signature factor module 26 is further configured to store the signature factor in association with the service ID.
  • the verification server 10 includes a receiving verification code confirmation request module 11, an acquisition service verification code module 12, an acquisition verification result module 13, and a transmission verification result module 14.
  • the implementation functions of the receiving verification code confirmation requesting module 11, the obtaining service verification code module 12, the obtaining verification result module 13 and the sending verification result module 14 correspond to the steps S23 to S26 corresponding to the service tracking method in the embodiment, in order to avoid redundancy, This embodiment will not be described in detail.
  • the receiving verification code confirmation requesting module 11 is configured to receive a verification code confirmation request sent by the service server, where the verification code confirmation request includes a client verification code and a signature factor, and the signature factor is related to the service ID.
  • the service verification code module 12 is configured to query the database based on the signature factor to obtain the service verification code stored in the association.
  • the verification result module 13 is configured to obtain the verification result based on the client verification code and the service verification code corresponding to the signature factor.
  • the verification result module 14 is configured to send the verification result to the service server, so that the client displays the service information when the verification result passes.
  • the verification server 10 further includes a verification verification code generation requesting module 15, a generation service verification code module 16, and a transmission service verification code module 17.
  • the implementation functions of the verification verification code generation requesting module 15 and the service verification code generation module 16 and the transmission service verification code module 17 correspond to the steps S15 to S17 corresponding to the service tracking method in the embodiment. To avoid redundancy, the embodiment is different. A detailed description.
  • the verification verification code generation requesting module 15 is configured to receive a verification code generation request sent by the service server, where the verification code generation request includes a signature factor and a user ID.
  • the service verification code module 16 is configured to generate a corresponding service verification code based on the signature factor, and store the service verification code in association with the signature factor.
  • the service verification code module 17 is configured to send the service verification code to the personal terminal corresponding to the user ID.
  • the service verification code module 16 is configured to process the signature factor based on the short message verification code interface and the preset short message verification code format, and generate a service verification code corresponding to the signature factor.
  • This embodiment provides one or more non-volatile readable storage media having computer readable instructions stored thereon.
  • the one or more non-volatile readable storage mediums storing computer readable instructions, when executed by one or more processors, causing one or more processors to perform the business tracking method of Embodiment 1 To avoid repetition, we will not repeat them here.
  • the computer readable instructions when executed by the processor, the functions of the modules/units in the service tracking device in Embodiment 2 are implemented. To avoid repetition, details are not described herein again.
  • non-volatile readable storage media storing computer readable instructions may comprise: any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a mobile hard drive, Disk, optical disk, computer memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signals, and telecommunications signals.
  • FIG. 3 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 30 of this embodiment includes a processor 31, a memory 32, and a computer readable instruction 33, such as a service tracking program, stored in the memory 32 and operable on the processor 31.
  • the processor 31 executes the computer readable instructions 33, the steps in the embodiments of the various service tracking methods described above are implemented, such as steps S11 through S28 shown in FIG.
  • the processor 31 implements the functions of the modules/units in the various apparatus embodiments described above when the computer readable instructions 33 are executed, such as the functions of the service server 20 and the authentication server 10, as shown in FIG.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Power Engineering (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请公开了一种业务跟踪方法、装置、终端设备及存储介质。该业务跟踪方法包括：接收客户端发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关；将验证码确认请求发送给验证服务器；接收验证服务器发送的验证结果，验证结果是基于对比签名因子对应的客户验证码和业务验证码得到的；在验证结果为通过时，获取与业务ID相对应的业务信息，并控制客户端显示业务信息。本申请通过给每个业务ID都匹配相应的签名因子，使得从客户端发送的客户验证码都可通过签名因子追溯相应的业务信息，提高了客户验证码的使用效率。

Description

业务跟踪方法、装置、终端设备及存储介质
本申请以2018年01月22日提交的申请号为201810058821.9，名称为“业务跟踪方法、装置、终端设备及存储介质”的中国发明申请为基础，并要求其优先权。
技术领域
本申请涉及通讯技术领域，尤其涉及一种业务跟踪方法、装置、终端设备及存储介质。
背景技术
当前很多通过互联网办理的业务，均需用户输入手机收到的短信验证码进行验证，以保证业务的顺利进行。用户通过一个手机号同时验证多项业务时(如同时验证多笔转账或多个页面登录时)，容易出现下述问题：多项业务都需要进行OTP(One-time Password，动态口令)认证，此时对于同种业务只有最后一次发送的短信验证码有效。即每类业务只能完成最后一笔收到短信验证码的业务操作，而之前发送的有关同类业务的短信验证码同时作废，造成了资源浪费。
发明内容
本申请实施例提供一种业务跟踪方法、装置、终端设备及存储介质，以解决每类业务只能验证最后收到的短信验证码而造成资源浪费的问题。
第一方面，本申请实施例提供一种业务跟踪方法，包括业务服务器执行的如下步骤：
接收客户端发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关；
将验证码确认请求发送给验证服务器；
接收验证服务器发送的验证结果，验证结果是基于对比签名因子对应的客户验证码和业务验证码得到的；
在验证结果为通过时，获取与业务ID相对应的业务信息，并控制客户端显示业务信息。
第二方面，本申请实施例提供一种业务跟踪方法，包括验证服务器执行的如下步骤：
接收业务服务器发送的验证码确认请求，验证码确认请求包括客户验证码和签名因 子，签名因子与业务ID相关；
基于签名因子查询数据库，获取关联存储的业务验证码；
基于签名因子对应的客户验证码和业务验证码，获取验证结果；
将验证结果发送给业务服务器，以使验证结果通过时客户端显示业务信息。
第三方面，本申请实施例提供一种业务跟踪装置，包括业务服务器，其中，业务服务器包括：
接收验证码确认请求模块，用于接收客户端发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关；
发送验证码确认请求模块，用于将验证码确认请求发送给验证服务器；
接收验证结果模块，用于接收验证服务器发送的验证结果，验证结果是基于对比签名因子对应的客户验证码和业务验证码得到的；
显示业务信息模块，用于在验证结果为通过时，获取与业务ID相对应的业务信息，并控制客户端显示业务信息。
第四方面，本申请实施例提供一种业务跟踪装置，包括验证服务器，其中，验证服务器包括：
接收验证码确认请求模块，用于接收业务服务器发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关；
获取业务验证码模块，用于基于签名因子查询数据库，获取关联存储的业务验证码；
获取验证结果模块，用于基于签名因子对应的客户验证码和业务验证码，获取验证结果；
发送验证结果模块，用于将验证结果发送给业务服务器，以使验证结果通过时客户端显示业务信息。
本申请第五方面提供一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
业务服务器接收客户端发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关；
业务服务器将验证码确认请求发送给验证服务器；
业务服务器接收验证服务器发送的验证结果，验证结果是基于对比签名因子对应的客户验证码和业务验证码得到的；
业务服务器在验证结果为通过时，获取与业务ID相对应的业务信息，并控制客户端显示业务信息。
本申请第六方面提供一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
验证服务器接收业务服务器发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关；
验证服务器基于签名因子查询数据库，获取关联存储的业务验证码；
验证服务器基于签名因子对应的客户验证码和业务验证码，获取验证结果；
验证服务器将验证结果发送给业务服务器，以使验证结果通过时客户端显示业务信息。
本申请第七方面提供一个或多个存储有计算机可读指令的非易失性可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
业务服务器接收客户端发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关；
业务服务器将验证码确认请求发送给验证服务器；
业务服务器接收验证服务器发送的验证结果，验证结果是基于对比签名因子对应的客户验证码和业务验证码得到的；
业务服务器在验证结果为通过时，获取与业务ID相对应的业务信息，并控制客户端显示业务信息。
本申请第八方面提供一个或多个存储有计算机可读指令的非易失性可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
验证服务器接收业务服务器发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关；
验证服务器基于签名因子查询数据库，获取关联存储的业务验证码；
验证服务器基于签名因子对应的客户验证码和业务验证码，获取验证结果；
验证服务器将验证结果发送给业务服务器，以使验证结果通过时客户端显示业务信息。
本申请实施例提供的业务跟踪方法、装置、终端设备及存储介质中，业务服务器获取客户端发送的客户验证码后，将带有签名因子的客户验证码发送给验证服务器进行验证。当该签名因子相对应的业务验证码和客户验证码通过验证，获取该签名因子对应的业务ID，以使该业务ID对应的业务信息显示给客户端。本实施例通过给每个业务ID都匹配相应的签名因子，使得从客户端发送的客户验证码都可通过签名因子追溯相应的业务信息，提高了客户验证码的使用效率，节省了验证服务器因针对同一个业务ID生成多个业务验证码造成的资源浪费。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例1中业务跟踪方法的一流程图；
图2是本申请实施例2中业务跟踪装置的一原理框图；
图3是本申请实施例4中终端设备的一示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
实施例1
该业务跟踪方法包括业务服务器执行的如下步骤：
接收客户端发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关。
将验证码确认请求发送给验证服务器。
接收验证服务器发送的验证结果，验证结果是基于对比签名因子对应的客户验证码和业务验证码得到的。
在验证结果为通过时，获取与业务ID相对应的业务信息，并控制客户端显示业务信 息。
该业务跟踪方法还包括验证服务器执行的如下步骤：
接收业务服务器发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关。
基于签名因子查询数据库，获取关联存储的业务验证码。
基于签名因子对应的客户验证码和业务验证码，获取验证结果。
将验证结果发送给业务服务器，以使验证结果通过时客户端显示业务信息。
本实施例应用在需要通过互联网确认业务信息，用于实现身份验证的交互的客户端、个人终端、业务服务器和验证服务器之间。
客户端是指与业务服务器相对应，为用户提供业务信息的服务端口，比如万维网使用的网页浏览器，收寄电子邮件时的电子邮件客户端，以及各种客户端软件等。
业务服务器是指通过各种协议把业务信息显示给客户端的服务器，业务服务器提供了访问业务信息的途径以供客户端使用，比如：网络视频、网上银行和电子地图等。由业务服务商提供的业务服务程序，比如数据库服务，电子邮件服务等。客户端需要与安装在业务服务商一侧的业务服务端互相配合运行。客户机和业务服务器之间通过建立网络连接，来保证服务程序的正常运行。
个人终端是每人专属的软件端口或者硬件设备，比如个人即时通讯软件界面、手机等。该个人终端是通过用户ID来进行标识的，也即他人可通过该用户ID定位到该个人终端，比如，对于手机来说用户ID就是手机号，对于QQ聊天软件，用户ID就是QQ号。个人终端可通过网络连接各种服务器发送的终端信息，本实施例中用于接收验证服务器发送的业务验证码。
验证服务器是提供验证业务的第三方服务程序，应用于本实施例，可以用于验证客户端的可靠性。验证服务器通过第三方接口给业务服务器提供连接端口，用于承接业务服务器指定的验证业务。
上述的四种终端中，当个人终端为客户端上安装的专属软件端口时，客户端和个人终端可以合并为一体；当验证服务器为业务服务器上安装的验证软件端口时，业务服务器和验证服务器也可以合并为一体。本实施例的执行主体包括业务服务器和验证服务器。
如图1所示，该业务跟踪方法包括如下步骤：
S11.业务服务器接收客户端发送的验证码获取请求，验证码获取请求包括业务ID和用户ID。
具体地，验证码获取请求是客户端向业务服务器发送的、用于向业务服务器申请分配业务验证码的请求。
用户ID是用于识别用户的标识，包括但不限于用户手机号、用户微信号等用户专属的标识号码。
业务ID是用于识别业务的标识，服务器根据接收到的每一验证码获取请求，给该验证码获取请求分配唯一的业务ID，用于识别其所要申请的业务。
本实施例中，通过给客户端发送的每一个验证码获取请求都分配一个对应的业务ID，可以将相同客户端发送的多个验证码获取请求中的不同业务信息都加以区分，便于后续跟踪各个业务信息。用户ID便于业务服务器对客户端的身份可靠性进行判定。
S12.业务服务器基于验证码获取请求，生成与业务ID相对应的签名因子。
具体地，签名因子是业务服务器为每项业务信息设定的唯一的一个记录号码，也即签名因子和每项业务信息都是一对一的关系。每项业务信息都对应一个相应的业务ID，也即签名因子和业务ID也是一对一的关系。
进一步地，通过业务ID可获取相应的业务信息，如果直接通过业务ID与第三方进行信息交互，有可能对客户端造成信息泄露，带来不可预估的损失。因此，需要再设置一个与业务ID相应的签名因子，通过签名因子与第三方进行信息交互用于追溯每一笔业务信息。
本实施例中，通过给业务ID生成相对应的唯一的签名因子，可以通过签名因子来追溯每一项业务信息，安全有效。
在一具体实施方式中，生成与业务ID相对应的签名因子，具体包括如下步骤：基于UUID算法对业务ID进行处理，生成与业务ID相对应的签名因子。
具体地，UUID(Universally Unique Identifier，通用唯一识别码)是一个软件建构的标准，也是被OSF(Open Software Foundation,开源软件基金会)的组织应用在分布式计算环境领域的一部分。UUID可以让分布式系统中的所有元素，都能有唯一的辨识资讯，而不需要透过中央控制端来做辨识资讯的指定。
UUID保证对在同一时空中的所有机器都是唯一的。按照OSF制定的标准计算，用到了以太网卡地址、纳秒级时间、芯片ID码和许多可能的数字。
UUID包括以下几部分的组合：
(1)当前日期和时间，UUID的第一个部分与时间有关，如果在生成一个UUID之后，过几秒又生成一个UUID，则第一个部分不同，其余相同。
(2)时钟序列。
(3)全局唯一的IEEE机器识别号，如果有网卡，从网卡MAC地址获得，没有网卡以其他方式获得。
标准的UUID格式为：xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx(8-4-4-4-12)，其中每个x是0-9或a-f范围内的一个十六进制的数字。
本实施例中，通过采用UUID算法生成签名因子，极大的保证了签名因子的唯一性，可在海量数据中追溯到每一笔与签名因子对应的具体的业务ID。
在生成与业务ID相对应的签名因子的步骤之后，该业务跟踪方法还包括：将签名因子与业务ID关联存储。将签名因子和业务ID进行关联存储，便于业务服务器根据签名因子在数据库中迅速定位于签名因子相对应的业务ID。
S13.业务服务器基于签名因子生成验证码生成请求，验证码生成请求包括签名因子和用户ID。
具体地，验证码生成请求是业务服务器发送给验证服务器的，用于请求验证服务器为客户端分配业务验证码的请求。因业务验证码是基于签名因子生成的，且需要将业务验证码发送给该用户ID对应的个人终端，因此，业务服务器需要将用户ID和关联有业务ID的签名因子，同时添加到验证码生成请求中，并将该验证码生成请求发送给验证服务器。
本实施例中通过相同的签名因子关联业务ID和业务验证码，可以在客户端进行身份验证时进行对比。例如，客户端发送的客户验证码和验证服务器基于相同签名因子存储的业务验证码相同，说明是相同客户端发送的客户验证码，进而可判定出客户端是可靠的，简单便捷。
S14.业务服务器将验证码生成请求发送给验证服务器，以使验证服务器基于签名因子生成业务验证码，并将业务验证码发送给与用户ID相对应的个人终端。
具体地，业务服务器将验证码生成请求发送给验证服务器，使得验证服务器基于签名因子生成业务验证码，将业务验证码发送给与用户ID相对应的个人终端后，用户根据接收到的业务验证码，向客户端输入客户验证码，用以对客户端进行身份验证。本实施例中，验证服务器基于签名因子生成业务验证码，并通过用户ID发送给客户端专有的个人终端，可以保证客户端进行身份认定的可靠性。
本实施例中，通过相同的签名因子同时关联业务ID和生成的业务验证码，将业务验证码通过签名因子的映射与业务ID形成一对一的关系，便于后续通过业务验证码可准确地定位到相应的业务ID。
S15.验证服务器接收业务服务器发送的验证码生成请求，验证码生成请求包括签名因子和用户ID。
具体地，业务服务器在验证码生成请求中提供用户ID和关联有业务ID的签名因子，以使验证服务器在接收业务服务器发送的验证码生成请求时，可根据签名因子用以生成业务验证码，并根据用户ID需要将生成的业务验证码发送给对应的个人终端。
S16.验证服务器基于签名因子，生成对应的业务验证码，并将业务验证码与签名因子关联存储。
具体地，业务验证码应用于本实施例可以是短信验证码。为了便于客户操作可将短信验证码设定为字符验证码，而且在选取候选字符时首先考虑数字和英文字符或者两者叠加使用。数字字符可取0-9，英文字符可选取26个英文字母，其中，考虑到英文字母有大小写，可增加候选字符数组长度。
本实施例中，可将业务验证码和签名因子关联存储为一个SESSION(会话控制)对象，用于存储特定用户会话所需的属性及配置信息。SESSION对象的特征是当用户在应用程序的WEB页之间跳转时，存储在SESSION对象中的变量将不会丢失，而是在整个用户会话中一直存在下去。SESSION对象最常见的一个用法就是存储用户的首选项，比如业务验证码。
本实施例中通过获取业务验证码给验证服务器提供对比范本，利于验证服务器作出及时正确的判断。
在一具体实施方式中，基于签名因子，生成对应的业务验证码，包括：基于短信验证码接口和预设短信验证码格式对签名因子进行处理，生成与签名因子相对应的业务验证码。
具体地，验证服务器可以为短信平台，业务验证码应用于本实施例可以设定为短信验证码，则短信验证码接口就是短信平台预留给业务服务器的服务接口。
预设短信验证码格式包括验证码的表达形式、长度和生成算法等，比如为了便于客户操作可将短信验证码设定为字符验证码，而且在选取候选字符时首先考虑数字和英文字符或者两者叠加使用。数字字符可取0-9，英文字符可选取26个英文字母，其中，考虑到英文字母有大小写，可增加候选字符数组长度。一般可将短信验证码的长度设为6位数，也即四分之三个字节(1位数占八分之一个字节)。
进一步地，短信验证码的生成算法需要确保发送给用户的每一个验证码都是安全完整的，同时保证用户的个人信息的安全，不被泄露。经过多年的研究发展，MD5(Message Digest Algorithm MD5，消息摘要算法第五版)算法渐渐成熟稳定被广泛应用于生成短信验证码。 MD5属于一种安全性能较高的散列型算法，对于输入的两种不同的数据，在操作后会有一个输出值，但是根据得到的数值并不可逆，不能得到原先的明文。
简单来说，MD5算法以分组的方式，用512位数对输入的信息进行划分，经过规范处理，得到四个三十二位的分组，再发送到目标用户的手机。因为整个MD5算法较为严谨，所以极大的保证了其安全性，是一种很优秀的加密算法。
本实施例中，通过短信验证码接口和预设短信验证码格式对签名因子进行处理，并通过可靠算法生成的短信验证码(即业务验证码)，可确保客户端接收到的业务验证码的安全性，避免信息泄露。
S17.验证服务器将业务验证码发送给与用户ID相对应的个人终端。
本实施例中，验证服务器通过将业务验证码发送给用户ID对应的的个人终端，用户通过个人终端接收到的业务验证码，以便基于个人终端显示的业务验证码进行身份验证，可以有效的保证客户端用户身份的可靠性和安全性。
本实施例提供的业务跟踪方法中，业务服务器接收客户端发起的验证码获取请求，给该验证码获取请求中的业务ID分配一唯一的签名因子。业务服务器将生成业务验证码的任务分配给验证服务器执行，并将签名因子同时也发送给验证服务器。验证服务器将基于签名因子生成业务验证码用户ID对应的个人终端，以便进行后续客户验证码的认证。
本实施例中通过给相同的签名因子映射唯一的业务ID并生成业务验证码，保证后续步骤可通过客户发送的客户验证码清晰地追溯到相应的业务ID对应的业务信息；也即如果客户验证码通过验证，该客户验证码即可对应实现一项业务信息，提高了客户验证码的使用效率。
步骤S17之后，即验证服务器将业务验证码发送给与用户ID相对应的个人终端之后，客户端基于该业务验证码可以向业务服务器发送客户验证码，用于向业务服务器验证身份的可靠性来获取相应的业务信息。
S21.业务服务器接收客户端发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关。
验证码确认请求是客户端通过输入验证码信息来向业务服务器发起确认身份可靠性请求。可以理解地，客户验证码就是用户通过客户端向业务服务输入的用于进行身份验证的验证码，该客户验证码可以是6位数字的短信验证码。在验证服务器将业务验证码发送给个人终端，以使用户可通过个人终端获取到业务验证码后，可以通过客户端向业务服务器输入验证码确认请求，该验证码确认请求中的客户验证码即为用户输入的验证码。
进一步地，客户端发起验证码确认请求是获取一项业务信息的请求，因此，业务服务器针对该业务ID同时会分配一个签名因子，用以区别每项业务信息。由于验证码确认请求是用于验证是否给客户端显示与业务ID相对应的业务信息，因此，需使验证码确认请求中携带签名因子，以便基于该签名因子查找预先分配给该签名因子的业务验证码，使其与客户验证码进行比对，从而实现身份确认。
本实施例中，业务服务器通过记录该业务ID对应的签名因子，利于后续步骤通过该签名因子准确地跟踪和区分不同的业务信息。
S22.业务服务器将验证码确认请求发送给验证服务器。
具体地，验证服务器是用来验证客户输入的客户验证码的正确性的服务器。而业务服务器专门用于提供业务信息，无法实现对用户身份的验证，因此业务服务器需将生成的验证码确认请求发送给验证服务器，以使验证服务器通过比对预先分配给该客户端的业务验证码和客户端发送的客户验证码是否一致，来确认客户端身份的可靠性。
本实施例中，业务服务器通过将验证码确认请求发送给验证服务器来对客户端进行身份验证，实现了服务器之间明确的任务分工，即业务服务器专门用于提供业务信息，验证服务器专门用于对客户端进行身份验证，提升了处理请求的速度。
S23.验证服务器接收业务服务器发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关。
具体地，验证服务器对客户端进行身份验证时，需要获取验证码确认请求中提供的客户验证码和签名因子。客户验证码就是用户通过客户端向业务服务输入的用于进行身份验证的验证码。签名因子可用以获取存储在验证服务器与该签名因子相对应的业务验证码，只有验证码确认请求提供这客户验证码和签名因子，才能对客户端的可靠性进行判定。
本实施例中，验证服务器预先存储有与签名因子关联的业务验证码，可以在客户端身份验证时，可通过该签名因子快速查询获取对应的业务验证码，以加快验证匹配效率。
S24.验证服务器基于签名因子查询数据库，获取与签名因子关联存储的业务验证码。
具体地，业务验证码是预先生成并存储在验证服务器中的用于进行身份验证的验证码，应用于本实施例可以是短信验证码。为了便于客户操作可将短信验证码设定为字符验证码，而且在选取候选字符时首先考虑数字、英文字符或者两者叠加使用。数字字符可取0-9，英文字符可选取26个英文字母，其中，考虑到英文字母有大小写，可增加候选字符数组长度。
应用于本实施例的数据库可以创建SESSION(会话控制)对象，用于存储特定用户会话 所需的属性及配置信息，如与签名因子相关联的业务验证码。这样，当用户在业务服务器提供的的WEB页面之间跳转时，存储在SESSION对象中的签名因子将不会丢失，而是在该用户会话中一直存在，直至客户端退出业务服务器。SESSION对象最常见的一个用法就是存储用户的首选项，比如业务验证码。
本实施例中通过签名因子获取业务验证码，以给验证服务器提供对比范本，利于验证服务器作出及时正确的判断。
S25.验证服务器基于签名因子对应的客户验证码和业务验证码，获取验证结果。
具体地，基于相同的签名因子，如果客户端发送的客户验证码和业务服务器存储的业务验证码一致，则其验证结果为通过，说明客户端的身份是可靠性安全的，可给该客户端提供进一步的服务；反之则其验证结果为不通过，需要对客户端的身份重新进行验证。
本实施例通过对比同一签名因子对应的客户验证码和业务验证码是否相同来判定客户端身份的安全性，便捷有效。
S26.验证服务器将验证结果发送给业务服务器，以使验证结果通过时客户端显示与业务ID相对应的业务信息。
具体地，一般验证结果都包括两种：验证通过和验证不通过。应用于本实施例为，当验证结果为通过时，表示验证码确认请求中的签名因子对应的客户验证码和业务验证码相同；当验证结果为不通过时，表示验证码确认请求中的签名因子对应的客户验证码和业务验证码不相同。
本实施例中，验证服务器及时将验证结果发回给业务服务器，利于业务服务器及时向客户端作出动作反馈，提高业务处理效率。
S27.业务服务器接收验证服务器发送的验证结果，验证结果是基于对比签名因子对应的客户验证码和业务验证码得到的。
具体地，业务服务器获取验证服务器提供的验证结果，该验证结果是基于对比签名因子对应的客户验证码和业务验证码是否一致时得到的，即若签名因子对应的客户验证码和业务验证码相同，则验证结果为通过；若签名因子对应的客户验证码和业务验证码不相同，则验证结果为不通过。业务服务器根据验证结果是否通过，决定是否给客户端提供业务信息。本实施例中，业务服务器基于验证服务器对客户端身份验证的验证结果，可及时对客户端提供相应的反馈，提高了客户体验。
S28.业务服务器在验证结果为通过时，获取与业务ID相对应的业务信息，并控制客户端显示业务信息。
具体地，业务信息是客户端通过验证码确认请求向业务服务器申请提供的业务信息，该业务信息可以为网络视频服务器播放视频，网上银行提供相应的银行业务或者电子地图展开地图信息等。具体地，可根据验证码确认请求中的业务ID查询业务服务器，获取与业务ID相对应的业务信息。
本实施例中，业务服务器在验证结果通过时，根据该验证结果中的签名因子对应的业务ID追溯到相应的业务信息。因该签名因子分别对应客户验证码和业务ID，也即通过签名因子的映射形成客户验证码和业务ID之间唯一对应的关系，提高了客户验证码的使用效率。
本实施例提供的业务跟踪方法，通过业务服务器获取客户端发送的验证码确认请求，将与签名因子对应的客户验证码发送给验证服务器进行验证。验证服务器对该签名因子相对应的业务验证码和客户验证码进行验证，并反馈验证结果。在验证结果为通过时，通过业务服务器获取与业务ID对应的业务信息并显示。本实施例中，通过给每个业务ID都匹配相应的签名因子，使得从客户端发送的客户验证码都可通过签名因子追溯相应的业务验证码，并在验证通过时，获取与业务ID相对应的业务信息，提高了客户验证码的使用效率，节省了验证服务器因针对同一个业务ID生成多个业务验证码造成的资源浪费。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
实施例2
图2示出与实施例1中业务跟踪方法一一对应的业务跟踪装置的原理框图。该业务跟踪装置包括业务服务器20和验证服务器10。如图2所示，该业务服务器20包括接收验证码确认请求模块21、发送验证码确认请求模块22、接收验证结果模块23和显示业务信息模块24。其中，接收验证码确认请求模块21、发送验证码确认请求模块22、接收验证结果模块23和显示业务信息模块24的实现功能与实施例中业务跟踪方法对应的步骤S21-S22、S27-S28分别对应，为避免赘述，本实施例不一一详述。
接收验证码确认请求模块21，用于接收客户端发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关。
发送验证码确认请求模块22，用于将验证码确认请求发送给验证服务器。
接收验证结果模块23，用于接收验证服务器发送的验证结果，验证结果是基于对比签名因子对应的客户验证码和业务验证码得到的。
显示业务信息模块24，用于在验证结果为通过时，获取与所述业务ID相对应的业务 信息，并控制客户端显示业务信息。
优选地，如图2所示，该业务服务器20还包括接收验证码获取请求模块25、生成签名因子模块26、生成验证码生成请求模块27和发送业务验证码模块28。其中，接收验证码获取请求模块25、生成签名因子模块26、生成验证码生成请求模块27和发送业务验证码模块28的实现功能与实施例中业务跟踪方法对应的步骤S11至S14分别对应，为避免赘述，本实施例不一一详述。
接收验证码获取请求模块25，用于接收客户端发送的验证码获取请求，验证码获取请求包括业务ID和用户ID。
生成签名因子模块26，用于基于验证码获取请求，生成与业务ID相对应的签名因子。
生成验证码生成请求模块27，用于基于签名因子生成验证码生成请求，验证码生成请求包括签名因子和用户ID。
发送验证码生成请求模块28，用于将验证码生成请求发送给验证服务器，以使验证服务器基于签名因子生成业务验证码，并将业务验证码发送给与用户ID相对应的个人终端。
优选地，生成签名因子模块26，用于基于UUID算法对所述业务ID进行处理，生成与所述业务ID相对应的签名因子。
生成签名因子模块26，还用于将所述签名因子与所述业务ID关联存储。
如图2所示，该验证服务器10包括接收验证码确认请求模块11、获取业务验证码模块12、获取验证结果模块13和发送验证结果模块14。其中，接收验证码确认请求模块11、获取业务验证码模块12、获取验证结果模块13和发送验证结果模块14的实现功能与实施例中业务跟踪方法对应的步骤S23至S26对应，为避免赘述，本实施例不一一详述。
接收验证码确认请求模块11，用于接收业务服务器发送的验证码确认请求，验证码确认请求包括客户验证码和签名因子，签名因子与业务ID相关。
获取业务验证码模块12，用于基于签名因子查询数据库，获取关联存储的业务验证码。
获取验证结果模块13，用于基于签名因子对应的客户验证码和业务验证码，获取验证结果。
发送验证结果模块14，用于将验证结果发送给业务服务器，以使验证结果通过时客户端显示业务信息。
优选地，如图2所示，该验证服务器10还包括验证验证码生成请求模块15、生成业 务验证码模块16和发送业务验证码模块17。其中，验证验证码生成请求模块15、生成业务验证码模块16和发送业务验证码模块17的实现功能与实施例中业务跟踪方法对应的步骤S15至S17对应，为避免赘述，本实施例不一一详述。
验证验证码生成请求模块15，用于接收业务服务器发送的验证码生成请求，验证码生成请求包括签名因子和用户ID。
生成业务验证码模块16，用于基于签名因子，生成对应的业务验证码，并将业务验证码与签名因子关联存储。
发送业务验证码模块17，用于将业务验证码发送给与用户ID相对应的个人终端。
优选地，生成业务验证码模块16，用于基于短信验证码接口和预设短信验证码格式对签名因子进行处理，生成与所述签名因子相对应的业务验证码。
实施例3
本实施例提供一个或多个存储有计算机可读指令的非易失性可读存储介质。该一个或多个存储有计算机可读指令的非易失性可读存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行实施例1中业务跟踪方法，为避免重复，这里不再赘述。或者，该计算机可读指令被处理器执行时实现实施例2中业务跟踪装置中各模块/单元的功能，为避免重复，这里不再赘述。
可以理解地，一个或多个存储有计算机可读指令的非易失性可读存储介质可以包括：能够携带所述计算机可读指令代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号和电信信号等。
实施例4
图3是本申请一实施例提供的终端设备的示意图。如图3所示，该实施例的终端设备30包括：处理器31、存储器32以及存储在存储器32中并可在处理器31上运行的计算机可读指令33，例如业务跟踪的程序。处理器31执行计算机可读指令33时实现上述各个业务跟踪方法实施例中的步骤，例如图1所示的步骤S11至S28。或者，处理器31执行计算机可读指令33时实现上述各装置实施例中各模块/单元的功能，例如图2所示，业务服务器20和验证服务器10的功能。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上 描述的全部或者部分功能。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种业务跟踪方法，其特征在于，包括业务服务器执行的如下步骤：
    接收客户端发送的验证码确认请求，所述验证码确认请求包括客户验证码和签名因子，所述签名因子与业务ID相关；
    将所述验证码确认请求发送给验证服务器；
    接收所述验证服务器发送的验证结果，所述验证结果是基于对比所述签名因子对应的客户验证码和业务验证码得到的；
    在验证结果为通过时，获取与所述业务ID相对应的业务信息，并控制所述客户端显示所述业务信息。
  2. 如权利要求1所述的业务跟踪方法，其特征在于，所述接收客户端发送的验证码确认请求的步骤之前，所述业务跟踪方法还包括：
    接收客户端发送的验证码获取请求，所述验证码获取请求包括业务ID和用户ID；
    基于验证码获取请求，生成与所述业务ID相对应的签名因子；
    基于所述签名因子生成验证码生成请求，所述验证码生成请求包括签名因子和用户ID；
    将所述验证码生成请求发送给验证服务器，以使所述验证服务器基于所述签名因子生成业务验证码，并将所述业务验证码发送给与所述用户ID相对应的个人终端。
  3. 如权利要求2所述的业务跟踪方法，其特征在于，所述生成与所述业务ID相对应的签名因子，包括：
    基于UUID算法对所述业务ID进行处理，生成与所述业务ID相对应的签名因子；
    在所述生成与所述业务ID相对应的签名因子的步骤之后，所述业务跟踪方法还包括：将所述签名因子与所述业务ID关联存储。
  4. 一种业务跟踪方法，其特征在于，包括验证服务器执行的如下步骤：
    接收业务服务器发送的验证码确认请求，所述验证码确认请求包括客户验证码和签名因子，所述签名因子与业务ID相关；
    基于签名因子查询数据库，获取与所述签名因子关联存储的业务验证码；
    基于所述签名因子对应的客户验证码和所述业务验证码，获取验证结果；
    将所述验证结果发送给所述业务服务器，以使验证结果通过时客户端显示与业务ID相对应的业务信息。
  5. 如权利要求4所述的业务跟踪方法，其特征在于，所述接收业务服务器发送的验证码确认请求的步骤之前，所述业务跟踪方法还包括：
    接收业务服务器发送的验证码生成请求，所述验证码生成请求包括签名因子和用户ID；
    基于所述签名因子，生成对应的业务验证码，并将所述业务验证码与所述签名因子关联存储；
    将所述业务验证码发送给与所述用户ID相对应的个人终端。
  6. 如权利要求5所述的业务跟踪方法，其特征在于，所述基于所述签名因子，生成对应的业务验证码，包括：
    基于短信验证码接口和预设短信验证码格式对签名因子进行处理，生成与所述签名因子相对应的业务验证码。
  7. 一种业务跟踪装置，其特征在于，包括业务服务器，所述业务服务器包括：
    接收验证码确认请求模块，用于接收客户端发送的验证码确认请求，所述验证码确认请求包括客户验证码和签名因子，所述签名因子与业务ID相关；
    发送验证码确认请求模块，用于将所述验证码确认请求发送给验证服务器；
    接收验证结果模块，用于接收所述验证服务器发送的验证结果，所述验证结果是基于对比所述签名因子对应的客户验证码和业务验证码得到的；
    显示业务信息模块，用于在验证结果为通过时，获取与所述业务ID相对应的业务信息，并控制所述客户端显示所述业务信息。
  8. 一种业务跟踪装置，其特征在于，包括验证服务器，所述验证服务器包括：
    接收验证码确认请求模块，用于接收业务服务器发送的验证码确认请求，所述验证码确认请求包括客户验证码和签名因子，所述签名因子与业务ID相关；
    获取业务验证码模块，用于基于签名因子查询数据库，获取与所述签名因子关联存储的业务验证码；
    获取验证结果模块，用于基于所述签名因子对应的客户验证码和所述业务验证码，获取验证结果；
    发送验证结果模块，用于将所述验证结果发送给所述业务服务器，以使验证结果通过时客户端显示与业务ID相对应的业务信息。
  9. 一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步 骤：
    业务服务器接收客户端发送的验证码确认请求，所述验证码确认请求包括客户验证码和签名因子，所述签名因子与业务ID相关；
    业务服务器将所述验证码确认请求发送给验证服务器；
    业务服务器接收所述验证服务器发送的验证结果，所述验证结果是基于对比所述签名因子对应的客户验证码和业务验证码得到的；
    业务服务器在验证结果为通过时，获取与所述业务ID相对应的业务信息，并控制所述客户端显示所述业务信息。
  10. 如权利要求9所述的终端设备，其特征在于，所述业务服务器接收客户端发送的验证码确认请求的步骤之前，所述处理器执行所述计算机可读指令时还实现如下步骤：
    业务服务器接收客户端发送的验证码获取请求，所述验证码获取请求包括业务ID和用户ID；
    业务服务器基于验证码获取请求，生成与所述业务ID相对应的签名因子；
    业务服务器基于所述签名因子生成验证码生成请求，所述验证码生成请求包括签名因子和用户ID；
    业务服务器将所述验证码生成请求发送给验证服务器，以使所述验证服务器基于所述签名因子生成业务验证码，并将所述业务验证码发送给与所述用户ID相对应的个人终端。
  11. 如权利要求10所述的终端设备，其特征在于，所述业务服务器生成与所述业务ID相对应的签名因子，包括：
    业务服务器基于UUID算法对所述业务ID进行处理，生成与所述业务ID相对应的签名因子；
    业务服务器在所述生成与所述业务ID相对应的签名因子的步骤之后，所述处理器执行所述计算机可读指令时还实现如下步骤：将所述签名因子与所述业务ID关联存储。
  12. 一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    验证服务器接收业务服务器发送的验证码确认请求，所述验证码确认请求包括客户验证码和签名因子，所述签名因子与业务ID相关；
    验证服务器基于签名因子查询数据库，获取与所述签名因子关联存储的业务验证码；
    验证服务器基于所述签名因子对应的客户验证码和所述业务验证码，获取验证结果；
    验证服务器将所述验证结果发送给所述业务服务器，以使验证结果通过时客户端显示与业务ID相对应的业务信息。
  13. 如权利要求12所述的终端设备，其特征在于，所述验证服务器接收业务服务器发送的验证码确认请求的步骤之前，所述处理器执行所述计算机可读指令时还实现如下步骤：
    验证服务器接收业务服务器发送的验证码生成请求，所述验证码生成请求包括签名因子和用户ID；
    验证服务器基于所述签名因子，生成对应的业务验证码，并将所述业务验证码与所述签名因子关联存储；
    验证服务器将所述业务验证码发送给与所述用户ID相对应的个人终端。
  14. 如权利要求13所述的终端设备，其特征在于，所述验证服务器基于所述签名因子，生成对应的业务验证码，包括：
    验证服务器基于短信验证码接口和预设短信验证码格式对签名因子进行处理，生成与所述签名因子相对应的业务验证码。
  15. 一个或多个存储有计算机可读指令的非易失性可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
    业务服务器接收客户端发送的验证码确认请求，所述验证码确认请求包括客户验证码和签名因子，所述签名因子与业务ID相关；
    业务服务器将所述验证码确认请求发送给验证服务器；
    业务服务器接收所述验证服务器发送的验证结果，所述验证结果是基于对比所述签名因子对应的客户验证码和业务验证码得到的；
    业务服务器在验证结果为通过时，获取与所述业务ID相对应的业务信息，并控制所述客户端显示所述业务信息。
  16. 如权利要求15所述的非易失性可读存储介质，其特征在于，所述业务服务器接收客户端发送的验证码确认请求的步骤之前，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器还执行如下步骤：
    业务服务器接收客户端发送的验证码获取请求，所述验证码获取请求包括业务ID和用户ID；
    业务服务器基于验证码获取请求，生成与所述业务ID相对应的签名因子；
    业务服务器基于所述签名因子生成验证码生成请求，所述验证码生成请求包括签名因 子和用户ID；
    业务服务器将所述验证码生成请求发送给验证服务器，以使所述验证服务器基于所述签名因子生成业务验证码，并将所述业务验证码发送给与所述用户ID相对应的个人终端。
  17. 如权利要求16所述的非易失性可读存储介质，其特征在于，所述业务服务器生成与所述业务ID相对应的签名因子，包括：
    业务服务器基于UUID算法对所述业务ID进行处理，生成与所述业务ID相对应的签名因子；
    在所述业务服务器生成与所述业务ID相对应的签名因子的步骤之后，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器还执行如下步骤：将所述签名因子与所述业务ID关联存储。
  18. 一个或多个存储有计算机可读指令的非易失性可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
    验证服务器接收业务服务器发送的验证码确认请求，所述验证码确认请求包括客户验证码和签名因子，所述签名因子与业务ID相关；
    验证服务器基于签名因子查询数据库，获取与所述签名因子关联存储的业务验证码；
    验证服务器基于所述签名因子对应的客户验证码和所述业务验证码，获取验证结果；
    验证服务器将所述验证结果发送给所述业务服务器，以使验证结果通过时客户端显示与业务ID相对应的业务信息。
  19. 如权利要求18所述的非易失性可读存储介质，其特征在于，所述验证服务器接收业务服务器发送的验证码确认请求的步骤之前，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器还执行如下步骤：
    验证服务器接收业务服务器发送的验证码生成请求，所述验证码生成请求包括签名因子和用户ID；
    验证服务器基于所述签名因子，生成对应的业务验证码，并将所述业务验证码与所述签名因子关联存储；
    验证服务器将所述业务验证码发送给与所述用户ID相对应的个人终端。
  20. 如权利要求19所述的非易失性可读存储介质，其特征在于，所述验证服务器基于所述签名因子，生成对应的业务验证码，包括：
    验证服务器基于短信验证码接口和预设短信验证码格式对签名因子进行处理，生成与所述签名因子相对应的业务验证码。
PCT/CN2018/081560 2018-01-22 2018-04-02 业务跟踪方法、装置、终端设备及存储介质 WO2019140790A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810058821.9A CN108418790A (zh) 2018-01-22 2018-01-22 业务跟踪方法、装置、终端设备及存储介质
CN201810058821.9 2018-01-22

Publications (1)

Publication Number Publication Date
WO2019140790A1 true WO2019140790A1 (zh) 2019-07-25

Family

ID=63125989

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081560 WO2019140790A1 (zh) 2018-01-22 2018-04-02 业务跟踪方法、装置、终端设备及存储介质

Country Status (2)

Country Link
CN (1) CN108418790A (zh)
WO (1) WO2019140790A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111914232A (zh) * 2020-07-28 2020-11-10 中国联合网络通信集团有限公司 业务处理方法及系统
CN114285582A (zh) * 2021-12-22 2022-04-05 中国电信股份有限公司 信息合法性的校验方法及装置、存储介质、电子设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110213229B (zh) * 2019-04-25 2021-09-14 平安科技（深圳）有限公司 身份认证方法、系统、计算机设备及存储介质
CN111475694B (zh) * 2020-03-18 2024-05-14 平安国际智慧城市科技股份有限公司 一种数据处理方法、装置、终端及存储介质
CN112800406B (zh) * 2021-01-21 2022-12-09 上海瀚之友信息技术服务有限公司 一种自定义加密信息传输方法及系统
CN113468515A (zh) * 2021-07-13 2021-10-01 富途网络科技(深圳)有限公司 用户身份验证方法、装置、电子设备以及存储介质
CN117134918A (zh) * 2023-07-20 2023-11-28 威艾特科技(深圳)有限公司 一种分布式数据签名校验方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050108360A1 (en) * 2003-11-13 2005-05-19 Samuel Zellner Method, system, and storage medium for validating users of communications services and messages transmitted
CN1859604A (zh) * 2006-05-29 2006-11-08 中国移动通信集团公司 业务请求发起流程的鉴权方法
US20130339248A1 (en) * 2012-06-18 2013-12-19 Ubipay, L.L.C. Ubiquitous purchase procurement apparatus
CN105046141A (zh) * 2015-06-12 2015-11-11 北京京东尚科信息技术有限公司 一种自适应的验证码设计方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050108360A1 (en) * 2003-11-13 2005-05-19 Samuel Zellner Method, system, and storage medium for validating users of communications services and messages transmitted
CN1859604A (zh) * 2006-05-29 2006-11-08 中国移动通信集团公司 业务请求发起流程的鉴权方法
US20130339248A1 (en) * 2012-06-18 2013-12-19 Ubipay, L.L.C. Ubiquitous purchase procurement apparatus
CN105046141A (zh) * 2015-06-12 2015-11-11 北京京东尚科信息技术有限公司 一种自适应的验证码设计方法及系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111914232A (zh) * 2020-07-28 2020-11-10 中国联合网络通信集团有限公司 业务处理方法及系统
CN111914232B (zh) * 2020-07-28 2023-05-09 中国联合网络通信集团有限公司 业务处理方法及系统
CN114285582A (zh) * 2021-12-22 2022-04-05 中国电信股份有限公司 信息合法性的校验方法及装置、存储介质、电子设备
CN114285582B (zh) * 2021-12-22 2024-04-05 中国电信股份有限公司 信息合法性的校验方法及装置、存储介质、电子设备

Also Published As

Publication number Publication date
CN108418790A (zh) 2018-08-17

Similar Documents

Publication Publication Date Title
WO2019140790A1 (zh) 业务跟踪方法、装置、终端设备及存储介质
US10554655B2 (en) Method and system for verifying an account operation
JP6877460B2 (ja) バイオメトリックアイデンティティを登録し、バイオメトリックアイデンティティを認証する方法及びデバイス
KR102493744B1 (ko) 생체 특징에 기초한 보안 검증 방법, 클라이언트 단말, 및 서버
JP6646341B2 (ja) ユーザを認証する方法及び装置、ウェアラブルデバイスを登録する方法及び装置
EP3092775B1 (en) Method and system for determining whether a terminal logging into a website is a mobile terminal
US20210234857A1 (en) Authentication system, authentication method, and application providing method
WO2018145605A1 (zh) 鉴权方法及服务器、访问控制装置
US9525679B2 (en) Sending session tokens through passive clients
US20180115547A1 (en) Edge protection for internal identity providers
WO2020140407A1 (zh) 基于云安全的云桌面登陆方法、装置、设备和存储介质
EP3206329B1 (en) Security check method, device, terminal and server
US20200196143A1 (en) Public key-based service authentication method and system
CN112491776B (zh) 安全认证方法及相关设备
JP2011215753A (ja) 認証システムおよび認証方法
WO2023093500A1 (zh) 一种访问验证方法及装置
CN114157434A (zh) 登录验证方法、装置、电子设备及存储介质
CN112929388B (zh) 网络身份跨设备应用快速认证方法和系统、用户代理设备
US8875244B1 (en) Method and apparatus for authenticating a user using dynamic client-side storage values
CN117336092A (zh) 一种客户端登录方法、装置、电子设备和存储介质
WO2023170653A1 (en) System and method for providing multi factor authorization to rdp services through a zero trust cloud environment
CN111984958A (zh) 一种支持vnc双因子的认证方法
US20230396618A1 (en) Token based identity verification and consent management
CN115618368A (zh) 接口访问方法、装置及设备
CN115017535A (zh) 云桌面操作系统的访问方法、装置、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18901715

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18901715

Country of ref document: EP

Kind code of ref document: A1