CN111967764A

CN111967764A - Service access verification method and device and electronic equipment

Info

Publication number: CN111967764A
Application number: CN202010826329.9A
Authority: CN
Inventors: 谢奕斐
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-08-17
Filing date: 2020-08-17
Publication date: 2020-11-20

Abstract

The embodiment of the specification discloses a service admission verification method, a device and electronic equipment, which are used for receiving a service admission request, wherein the service admission request carries an identifier of a user; determining at least one item of information to be checked corresponding to the service to be admitted according to the service admission request; judging whether the historical verification information corresponding to the user identification contains the historical verification result of the information to be verified; if yes, determining the verification result of the information to be verified according to the historical verification result; and if not, checking the information to be checked. The technical scheme disclosed by the embodiment of the specification is beneficial to the service access verification in the compliance field, and the efficiency of the service access verification and the user experience can be improved.

Description

Service access verification method and device and electronic equipment

Technical Field

The embodiment of the specification relates to the technical field of computers, in particular to a service admission verification method, a service admission verification device and electronic equipment.

Background

With the development of internet and computer technologies, more and more services are moved to a network service platform for processing. When a user requests the service platform for the admission service, the user needs to submit relevant verification information to the service platform to prove that the user has the operation qualification of the service requested for the admission, and the service platform verifies the compliance of the operation qualification of the service requested for the user to operate by verifying the verification information submitted by the user.

In the prior art, generally, according to a service type of an admission service applied by a user, verification is performed on verification information required by the service type, and if the verification is passed, the user is approved to operate a service corresponding to the service type on a service platform.

Disclosure of Invention

In view of this, embodiments of the present disclosure provide a method and an apparatus for checking service admission, and an electronic device, so as to solve the problem that the same user needs to repeatedly check the same checking information when applying for different services on a service platform.

The embodiment of the specification adopts the following technical scheme:

an embodiment of the present specification provides a service admission verification method, including:

receiving a service access request, wherein the service access request carries an identifier of a user;

determining at least one item of information to be checked corresponding to the service to be admitted according to the service admission request;

judging whether the historical verification information corresponding to the user identification contains the historical verification result of the information to be verified;

if yes, determining the verification result of the information to be verified according to the historical verification result;

and if not, checking the information to be checked.

An embodiment of the present disclosure further provides a service admission verification apparatus, including:

the receiving module is used for receiving a service access request, wherein the service access request carries an identification of a user;

the determining module is used for determining to-be-checked information corresponding to at least one to-be-admitted service according to the service admission request;

the judging module is used for judging whether the historical verification information corresponding to the user identification contains the historical verification result of the information to be verified;

if yes, determining a verification result of the information to be verified according to the historical verification result;

and if not, checking the information to be checked.

Embodiments of the present specification further provide an electronic device, including at least one processor and a memory, where the memory stores programs and is configured to enable the at least one processor to execute the following steps:

and if not, checking the information to be checked.

The embodiment of the specification adopts at least one technical scheme which can achieve the following beneficial effects:

determining to-be-checked information corresponding to at least one to-be-checked service according to the service access request, judging whether historical check information corresponding to the user identification contains the historical check result of the to-be-checked information or not, if yes, directly determining the check result of the to-be-checked information according to the historical check result, and if not, checking the to-be-checked information.

When the information to be checked is checked, whether the historical checking information corresponding to the identification of the user contains the historical checking result of the checking information is judged in advance, so that when the information to be checked is checked, the checking result of the information to be checked can be directly determined without repeated checking, repeated checking of the repeated checking information by the server can be effectively avoided, and the service access checking efficiency is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the embodiments of the specification and are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the specification and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic flowchart of a service admission verification method according to an embodiment of the present disclosure;

fig. 2 is a schematic flow chart of a method for checking service admission according to an embodiment of the present disclosure;

fig. 3 is a flowchart of performing deduplication processing on repeated information to be checked in a service admission checking method provided in an embodiment of the present specification;

fig. 4 is a timing diagram of a method for checking service admission according to an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of a traffic admission checking apparatus according to an embodiment of the present disclosure.

Detailed Description

In the prior art, when receiving a service admission request, a service platform usually performs service admission audit processing on services requested to be admitted by a user according to service types, and performs audit on check information corresponding to each service type. However, for the check information to be checked corresponding to different service types, there may be a repeated situation, that is, the same kind of check information may be used for the service admission check of different service types, in this situation, since the service admission check processes of the service types are mutually independent, the user needs to upload the same check information repeatedly according to different service types, and the service platform also needs to perform repeated check information check according to the service types, the check process of the service platform is complicated, the check efficiency is low, and the user experience is not high.

Therefore, embodiments of the present disclosure provide a method, an apparatus, and an electronic device for service admission verification, where information to be verified corresponding to at least one service to be admitted is determined according to a service admission request, and by determining whether historical verification information corresponding to a user identifier includes a historical verification result of the information to be verified, if so, the verification result of the information to be verified can be directly determined according to the historical verification result, and if not, the information to be verified is verified. Therefore, when the information to be checked is checked in the historical checking process, the checking result of the information to be checked can be directly determined without repeated checking, repeated checking of the repeated checking information by the server can be effectively avoided, and the service access checking efficiency is improved.

In order to make the objects, technical solutions and advantages of the present application more clear, the technical solutions of the present application will be clearly and completely described below with reference to the specific embodiments of the present specification and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step are within the scope of the present application.

The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.

Fig. 1 is a schematic flow chart of a method for checking service admission according to an embodiment of the present disclosure.

S101: and receiving a service admission request, wherein the service admission request carries an identification of a user.

In this embodiment, a user may refer to a merchant, an individual, or the like that requests to register a service to a service platform corresponding to a server, and the user may send a service admission request to the server through a terminal or a service platform website, or the like, to request to operate a corresponding service on the service platform. The identifier of the user may refer to information used for referring to the user, and may specifically be a user name, a nickname, a certificate number, and the like, which is not specifically limited herein.

The business platform needs to verify the qualification of the resident business requested by the user operation in order to ensure the safety and the compliance of the platform and the benefit of both sides of the transaction, so as to determine whether the user has the qualification for operating the business and whether the identity of the user is legal, and if the user passes the verification, the user can be allowed to reside in the business platform to operate the corresponding business.

Therefore, the service admission request sent by the user may carry service information requesting admission, where the service information may include at least one service to be admitted that the user requests admission, and may also include information to be verified that is required for service admission verification, and the like, and is not limited specifically herein.

S103: and determining at least one item of information to be checked corresponding to the service to be admitted according to the service admission request.

In the embodiment of the present specification, the information to be checked may be understood as information that needs to be checked when the service to be admitted is subjected to service admission auditing, and specifically may be at least one of an object to be checked, an identifier of the object to be checked, a checking relationship between at least two objects to be checked corresponding to one service to be admitted, and the like, which is not specifically limited herein.

The object to be verified may be a target certification object that needs to be verified when the service to be admitted is verified for service admission, specifically, the target certification object may be a copy, a picture, an original, and the like of a user identity document, a business license, and other documents, and is not limited specifically herein.

The identifier of the object to be verified may refer to identifier information mapping the object to be verified, for example, a serial number of the object to be verified, a certificate name, and the like, where the serial number of the object to be verified may be a serial number of the server according to a serial number rule inside the service platform, so as to facilitate query and storage.

For a service admission request of a service to be admitted, it may be required that the user has one kind of information to be checked, or may also have more than two pieces of information to be checked, and in the case that more than two pieces of information to be checked are required, the checking relationship between the pieces of information to be checked may be preset according to the service admission checking policy to be admitted, specifically at least one of parallel checking and one checking.

For example, for a service a to be admitted, when a service admission request is made, the information to be checked that needs to be provided by the user may be certificate X and certificate Y, if the checking relationship between certificate X and certificate Y is parallel checking, the user is required to provide certificate X and certificate Y, and only when both certificate X and certificate Y pass the checking, the service admission request for the service a to be admitted will pass through the user.

If the verification relation between the certificate X and the certificate Y is one verification, the user can select one certificate to upload and verify according to the self condition, and in this case, the user can pass the service access request of the service A to be accessed through the verification of one certificate.

Therefore, when performing service admission verification, the verification relationship between the information to be verified also needs to be considered.

As an application embodiment, determining to-be-checked information corresponding to at least one to-be-admitted service according to the service admission request may include:

and extracting the information to be verified from the service admission request.

In the embodiment of the present specification, a user may send, according to a service admission requirement and a requirement, to-be-checked information required for service admission check, that is, service information carried in a service admission request, while sending the service admission request. Therefore, the server can directly extract the information to be checked required by the service admission check from the service admission request.

In this case, the user may provide at least one of the to-be-verified object identifier and the to-be-verified object to the server according to the service admission requirement of the to-be-admitted service, and as a preferred embodiment, the user may provide the to-be-verified object identifier, so that after the server may determine the to-be-verified object identifier provided by the user, it is determined whether the to-be-verified object corresponding to the to-be-verified object identifier has been verified, and if so, the user may not upload the to-be-verified object corresponding to the to-be-verified object identifier, so as to avoid the user from repeatedly uploading repeated to-be-verified objects, and improve user experience.

As another application embodiment, determining to-be-checked information corresponding to at least one to-be-admitted service according to the service admission request may include:

and determining the information to be checked corresponding to the at least one service to be admitted according to the service admission checking strategy corresponding to the at least one service to be admitted.

In this embodiment of the present specification, the service information carried in the service admission request sent by the user may include at least one service to be admitted or a service type requested to be admitted by the user. In this case, the server is required to determine the to-be-checked information corresponding to the to-be-admitted service according to the service admission checking policy corresponding to at least one item of to-be-admitted service.

The service admission verification policy may be understood as a qualification verification relationship required for operating the service to be admitted, and may specifically include at least one of performing parallel verification and selecting verification on the information to be verified corresponding to the service to be admitted, which is not specifically limited herein.

Specifically, the server may determine at least one service to be admitted, which is requested to be admitted by the user, according to the service admission request sent by the user, so as to determine a service admission verification policy corresponding to each service to be admitted, and thus, may determine the information to be verified, which corresponds to each service to be admitted, and the verification relationship between the information to be verified according to the service admission verification policy.

In this case, the information to be checked determined by the server may be an object to be checked stored locally in the server, and the object to be checked may be uploaded by the user in advance and stored in the server, so that the server queries and extracts according to the requirement.

As a preferred embodiment, the information to be verified determined by the server may also be an identifier of the object to be verified, so that the server may first determine the identifier of the determined object to be verified, and if it is determined that the object to be verified corresponding to the identifier of the object to be verified is not verified, the server may then request the user to upload the corresponding object to be verified for verification, thereby avoiding the user from uploading repeated objects to be verified, and improving user experience.

As another application embodiment, if the to-be-checked information corresponding to at least two to-be-admitted services is determined according to the service admission request, the method may further include:

and according to the service access verification strategies corresponding to the at least two services to be accessed, carrying out duplication elimination processing on the information to be verified corresponding to the at least two services to be accessed, so that the residual information to be verified after processing does not contain repeated information to be verified, wherein the service access verification strategy comprises at least one of parallel verification and one verification of the information to be verified corresponding to the services to be accessed.

If the service admission request sent by the user includes at least two services to be admitted, and there may be a coincidence of information to be checked for different services to be admitted, in the embodiment of the present specification, when the server determines information to be checked corresponding to the at least two services to be admitted, the server may further perform deduplication processing on the information to be checked corresponding to the at least two services to be admitted, so that the remaining information to be checked after processing does not include repeated information to be checked, thus, the server may avoid performing checking on the repeated information to be checked, and the user may also avoid repeatedly uploading the same information to be checked for different services to be admitted.

The server can perform deduplication processing on the information to be checked corresponding to at least two services to be admitted by combining the checking relation between the information to be checked according to the service admission checking strategy corresponding to each service to be admitted, so that the remaining information to be checked after deduplication processing does not contain repeated information to be checked, and the service admission checking strategy corresponding to each service to be admitted can be met.

In a specific application scenario, if the to-be-checked information corresponding to the at least two services to be admitted respectively includes repeated to-be-checked information, the processing of the to-be-checked information corresponding to the at least two services to be admitted respectively may include at least one of the following manners:

if the service access verification strategies corresponding to the at least two services to be verified are the parallel verification, performing duplicate removal processing on the repeated information to be verified to obtain the remaining information to be verified;

if the service access verification strategies corresponding to the at least two services to be accessed are all the selected verification, determining the residual information to be verified according to the repeated information to be verified;

and if the service access verification strategies corresponding to the at least two services to be accessed comprise the parallel verification and the alternative verification, determining the residual information to be verified according to the information to be verified of the services to be accessed corresponding to the parallel verification.

In a specific application embodiment, the service admission verification policies corresponding to at least two services to be admitted may have the following combination situations:

all the checks are parallel checks, all the checks are alternative checks, and the checks comprise a parallel check and an alternative check.

For convenience of description, the check relation symbol of parallel check is &' to represent a sum relation; the check relationship symbol for one check is "|", which represents the relationship. The above symbols are merely specific application examples, and do not limit the scope of the embodiments in this specification.

If the service admission verification policies corresponding to at least two services to be admitted are both parallel verifications, for example, the service admission verification policy of the service a to be admitted is X & Y, and the service admission verification policy of the service B to be admitted is Y & Z.

In this case, since the user requests to admit the two services at the same time, and the two services to be admitted have the same information Y to be checked, the repeated information Y to be checked can be deduplicated, after merging and summarizing the information to be checked corresponding to the two services to be admitted, the server only needs to check the information X, Y, Z to be checked, and when all three kinds of information to be checked pass the check, the services a and B to be admitted can both pass the service admission check.

If the service admission verification policies corresponding to at least two services to be admitted are all selected, for example, the service admission verification policy of the service C to be admitted is X-Y, and the service admission verification policy of the service D to be admitted is X-P-Q.

In this case, since the service C to be admitted and the service D to be admitted only need to select one of the pieces of information to be checked corresponding to each of them for checking, and the two pieces of information to be admitted include the repeated information X to be checked, the remaining information to be checked of the two pieces of services to be admitted can be determined according to the repeated information X to be checked according to the principle of saving the checking process, that is, only the repeated information X to be checked needs to be checked, and if the checking is passed, it can be determined that the two pieces of services to be admitted both pass the service checking.

If the service admission verification policies corresponding to at least two services to be admitted include parallel verification and alternative verification, for example, the service admission verification policy of the service E to be admitted is X & P, and the service admission verification policy of the service F to be admitted is Y-P-M.

In this case, since the two services to be admitted both correspond to the same information P to be checked, the service F to be admitted only needs to perform one check, and the remaining information to be checked of the two services to be admitted can be determined according to the information X, P to be checked corresponding to the service E to be admitted according to the principle of saving the check process, that is, when the two information to be checked both pass the check, the two services to be admitted also pass the service admission check.

Further, the method may further include:

and after the rest information to be checked is checked, if the service access checking strategy is that the information to be checked corresponding to the selected service to be checked does not pass the check, checking other information to be checked of the service to be checked.

When the service admission checking strategy corresponding to at least two services to be admitted comprises one checking, the repeated information to be checked is used as the information to be checked selected by the service to be admitted of the one checking, and in this case, if the repeated information to be checked does not pass the checking and other information to be checked corresponding to the service to be admitted is possibly in compliance, the checking result of the service to be admitted is determined to be inaccurate only by the checking result of the repeated information to be checked.

In this case, the other information to be checked corresponding to the service to be admitted may be further checked. Continuing the above example, for the service F to be admitted, after the repeated information P to be checked is checked, if the information P to be checked does not pass the check, the other information Y and M to be checked of the service F to be admitted can be further checked, and when one of the information to be checked passes the check, it can be determined that the service F to be admitted passes the service admission check.

S105: and judging whether the historical verification information corresponding to the user identification contains the historical verification result of the information to be verified.

In the embodiment of the present specification, the historical verification information corresponding to the identifier of the user may be understood as the information to be verified that the user has already verified and the historical verification result thereof, and specifically may include the information to be verified that the user has passed the verification and the information to be verified that the user has not passed the verification, and the server may store the historical verification information corresponding to the identifier of the user in a classified manner according to the verification condition, so that the user may query the stored historical verification information when requesting a new service to be admitted.

In the embodiment of the present specification, by determining whether the historical verification information corresponding to the identifier of the user includes the historical verification result of the to-be-verified information corresponding to the to-be-admitted service newly requested by the user, if the historical verification information exists, the verification result of the verified to-be-verified information can be directly extracted, so that repeated verification is avoided.

Further, for the information to be checked that is not checked in the history check information corresponding to the identifier of the user, for example, for the business license Y, in the history check process, the business license Y uploaded by the user is not checked to be compliant and not checked, and when the user requests a new business admission, a new business license Y' is uploaded.

As an application embodiment, the determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified may include:

when the service access request comprises at least two services to be accessed, acquiring historical verification information of information to be verified corresponding to the verified services to be accessed in the service access request;

and judging whether the historical verification information contains the historical verification result of the to-be-verified information corresponding to the appointed to-be-admitted service.

In this embodiment, when the service admission request sent by the user includes at least two services to be admitted, the verification result of the to-be-verified information corresponding to the verified to-be-admitted service may be used as the historical verification information corresponding to the identifier of the user.

Therefore, when the to-be-checked information corresponding to the appointed to-be-admitted service is checked, the historical checking information corresponding to the user identification can be obtained firstly, whether the to-be-checked information corresponding to the appointed to-be-admitted service is checked is determined by judging whether the to-be-checked information is contained in the historical checking information, and if yes, the historical checking result can be directly adopted. The specified traffic to be admitted may be the traffic to be admitted which is currently undergoing the verification.

As another application embodiment, the determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified may include:

and acquiring historical verification information corresponding to the user identification from a database.

In this embodiment of the present specification, the historical verification information corresponding to the identifier of the user may refer to historical verification information stored in a database, and may include historical verification information of an admitted service, verification information that fails to pass a verification, and the like, which is not limited herein.

S107: if yes, determining the verification result of the information to be verified according to the historical verification result.

In the embodiment of the present specification, when the historical verification information corresponding to the identifier of the user includes the historical verification result of the information to be verified, the verification result of the information to be verified can be directly determined according to the historical verification result, and the server does not need to verify the information to be verified any more.

As an application embodiment, after determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified, the method may further include:

and if the historical verification information contains the historical verification result of the information to be verified, returning the verification result of the information to be verified to the account corresponding to the user identifier.

Specifically, when the historical verification information includes the historical verification result of the information to be verified, the historical verification result may be returned to the account corresponding to the identifier of the user, so as to inform the user that the information to be verified has been verified before the verification of this time.

Further, if the information to be verified is passed through the verification in history, the user can be informed that the object to be verified corresponding to the information to be verified does not need to be uploaded, repeated uploading is avoided, and user experience is improved; if the information to be checked has not been checked in history, the user may be informed to upload a compliant object to be checked, for example, a business license for compliance to the relevant regulatory department.

S109: and if not, checking the information to be checked.

In this embodiment of the present specification, when the historical verification information corresponding to the identifier of the user does not include the verification result of the information to be verified, the server needs to verify the information to be verified.

As an application embodiment, the verifying the information to be verified may include:

sending an acquisition request for acquiring the object to be verified corresponding to the information to be verified to an account corresponding to the user identifier;

receiving at least one object to be verified uploaded by the account according to the acquisition request;

and checking the at least one object to be checked.

Specifically, after determining the information to be checked, the server may send an acquisition request for acquiring the object to be checked corresponding to the determined information to be checked to the account corresponding to the identifier of the user, so that the server screens the information to be checked, merges and summarizes the information to be checked, and then requires the user to upload the object to be checked, which may not only prevent the user from uploading repeated objects to be checked according to the requirements of different services to be admitted, but also prevent the server from repeatedly checking the repeated objects to be checked.

The account corresponding to the user identifier may refer to an account registered by the user on the service platform or the server, and the account is bound to the user identifier, so that the account registered by the user may be determined by the user identifier.

The embodiment of the present specification provides a service admission verification method, which determines to-be-verified information corresponding to at least one service to be admitted according to a service admission request, and determines whether historical verification information corresponding to a user identifier includes a historical verification result of the to-be-verified information, if so, the verification result of the to-be-verified information can be directly determined according to the historical verification result, and if not, the to-be-verified information is verified, so that the admission result of each service to be admitted can be determined according to the verification result of the to-be-verified information. Therefore, when the information to be checked is checked in the historical checking process, the checking result of the information to be checked can be directly determined without repeated checking, repeated checking of the repeated checking information by the server can be effectively avoided, and the service access checking efficiency is improved.

As shown in fig. 2, a schematic flow chart of a service admission verification method provided in the embodiment of the present specification is shown, in which a merchant is used as a specific user in the embodiment of the present specification.

S201: receiving a service admission request sent by a merchant through a terminal, wherein the service admission request carries at least two services to be admitted, which are requested to be admitted by the merchant.

S203: and extracting the information to be checked corresponding to the at least two services to be admitted from the service admission request.

In the embodiment of the present specification, the information to be verified may specifically be an identifier of an object to be verified corresponding to the object to be verified, and the identifier to be verified may be an identifier of the object to be verified corresponding to the object to be verified, which is provided by the merchant according to the service admission verification policy corresponding to the at least two services to be admitted and the qualification conditions possessed by the merchant.

S205: and carrying out duplication elimination treatment on the information to be checked corresponding to the at least two services to be admitted to obtain the residual information to be checked.

S207: and determining whether the historical verification information of the merchant contains the historical verification result of the residual information to be verified.

S209: and checking the information to be checked which is not contained in the historical checking information.

S211: and returning the verification result corresponding to the service admission request to the terminal.

In this embodiment of the present specification, returning the verification result to the terminal may refer to returning the verification result to an account corresponding to the identifier of the merchant on the terminal, so that the merchant may check the verification result through the account to determine an admission result of the service to be admitted, which is requested to be admitted by the merchant.

The verification result includes a historical verification result of the verified information to be verified, and the verification result of the information to be verified, which is not included in the historical verification information, in step S209.

As shown in fig. 3, in a service admission verification method provided in this embodiment of the present disclosure, a server performs deduplication processing on to-be-verified information corresponding to multiple to-be-admitted services requested in a service admission request.

S301: and the server receives a service admission request sent by the merchant through the terminal.

S303: and analyzing the service admission request, and determining the service to be admitted, which is requested to be admitted by the merchant.

In the embodiments of the present application, the to-be-admitted service requested by the merchant to be admitted includes a to-be-admitted service a, a to-be-admitted service B, a to-be-admitted service C, and a to-be-admitted service D.

S305: and determining the information to be checked corresponding to each service to be admitted.

In an embodiment of the present specification, the information to be verified is an identifier of an object to be verified corresponding to the object to be verified. The information to be verified corresponding to the service A to be admitted comprises a certificate X and a certificate Y, the information to be verified corresponding to the service B to be admitted comprises a certificate P, a certificate Q and a certificate X, the information to be verified corresponding to the service C to be admitted comprises the certificate P and the certificate Q, and the information to be verified corresponding to the service D to be admitted comprises the certificate Q.

S307: and determining the verification relation between the to-be-verified information corresponding to each to-be-admitted service.

In the embodiment of the present specification, the check relationship between the information to be checked corresponding to the service a to be admitted is X & Y, that is, parallel check; the checking relation between the information to be checked corresponding to the service B to be admitted is P-Q-X, namely selecting checking; the checking relation between the information to be checked corresponding to the service C to be admitted is P-Q, namely selecting checking; the service D to be admitted corresponds to a unique certificate Q.

S309: and carrying out duplication elimination treatment on each piece of information to be checked to obtain the rest information to be checked.

In the embodiment of the present specification, since the service a to be admitted and the service D to be admitted are not selected for verification, the certificate X, the certificate Y, and the certificate Q corresponding to the two services to be admitted need to be verified.

Furthermore, since the service B to be admitted and the service C to be admitted are both selected to be verified, and the service B to be admitted corresponds to the same certificate X as the service a to be admitted, the service B to be admitted corresponds to the same certificate Q as the service D to be admitted, and the service C to be admitted corresponds to the same certificate Q as the service D to be admitted, the information to be verified corresponding to the service a to be admitted and the service D to be admitted can satisfy the verification relationship between the service B to be admitted and the service C to be admitted.

In summary, after the deduplication processing is performed on the to-be-verified information corresponding to the four to-be-admitted services, the remaining to-be-verified information can be obtained as the license X, the license Y, and the license Q.

Furthermore, the remaining information to be verified may be compared with the historical verification information of the merchant and then determined to finally correspond to the service admission request, that is, the information to be verified that needs to be uploaded by the merchant, and the specific process flow of the step is as described in the above embodiment and is not described herein again.

Fig. 4 is a timing diagram of one preferred embodiment of a traffic admission verification method provided in the embodiments of the present specification.

S401: a user sends a service admission request to a server 4B through a user terminal 4A, wherein the service admission request carries at least one service requested by the user.

S403: and the server 4B determines at least one service type requested to be admitted by the user according to the service admission request.

S405: and the server 4B determines the information to be checked corresponding to each service type according to the service access checking strategy corresponding to each service type.

S407: the server 4B performs deduplication processing on each piece of information to be checked to obtain the remaining information to be checked.

S409: the server 4B sends the historical verification information acquisition request of the user to the database 4C, wherein the historical verification information acquisition request carries the identifier of the user.

S411: the database 4C returns the history verification information corresponding to the user identifier to the server 4B.

S413: and the server 4B judges whether the historical verification information contains the historical verification result of the residual information to be verified or not according to the received historical verification information. And determining the information to be checked corresponding to the service admission request according to the judgment result, namely the information to be checked which needs to be uploaded by the user.

S415: the server 4B sends an acquisition request for acquiring the object to be verified corresponding to the information to be verified to the user terminal 4A.

In this embodiment of the present specification, the obtaining request may further carry the determination result in step S413, so as to notify the user of the information to be verified that has been verified and the verification result thereof.

S417: and the user terminal 4A uploads the object to be verified corresponding to the acquisition request to the server 4B.

S419: the server 4B checks the object to be checked uploaded by the user terminal 4A to obtain a check result.

S421: the server 4B returns the check result to the user terminal 4A to inform the user of the admission result of the service requested to be admitted by the user.

S423: the server 4B stores the verification result in the database 4C as the updated historical verification information of the user.

Thus, when a user requests the server 4B to admit a new service type, the server 4B may query and acquire the historical verification information updated by the user by querying the database 4C, so as to perform judgment processing on the information to be verified corresponding to the current service admission request.

Fig. 5 is a schematic structural diagram of a service admission checking apparatus provided in an embodiment of the present specification based on the same inventive concept.

The receiving module 501 receives a service admission request, where the service admission request carries an identifier of a user;

a determining module 502, configured to determine, according to the service admission request, to-be-checked information corresponding to at least one to-be-admitted service;

the judging module 503 is configured to judge whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified;

if yes, the verification module 504 determines a verification result of the information to be verified according to the historical verification result;

and if not, checking the information to be checked.

Further, determining to-be-checked information corresponding to at least one to-be-admitted service according to the service admission request may include:

Further, if the to-be-checked information corresponding to at least two to-be-admitted services is determined according to the service admission request, the apparatus may further include:

Further, if the to-be-checked information corresponding to the at least two services to be admitted respectively includes repeated to-be-checked information, the processing of the to-be-checked information corresponding to the at least two services to be admitted respectively may include at least one of the following manners:

Further, the apparatus may further include:

Further, determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified may include:

Further, after determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified, the method may further include:

Further, the verifying the information to be verified may include:

and checking the at least one object to be checked.

The embodiment of the present specification provides a service admission verification apparatus, where a server determines, according to a service admission request, to-be-verified information corresponding to at least one service to be admitted, and determines, by determining whether historical verification information corresponding to an identifier of a user includes a historical verification result of the to-be-verified information, if the historical verification information includes the historical verification result, the verification result of the to-be-verified information may be directly determined according to the historical verification result, and if the historical verification information does not include the historical verification result, the verification is performed on the to-be-verified information, and then the admission result of each service to be admitted may be determined according to the verification result of the to-be-verified information. Therefore, when the information to be checked is checked in the historical checking process, the checking result of the information to be checked can be directly determined without repeated checking, repeated checking of the repeated checking information by the server can be effectively avoided, and the service access checking efficiency is improved.

Based on the same inventive concept, embodiments of the present specification further provide an electronic device, including at least one processor and a memory, where the memory stores programs and is configured to be executed by the at least one processor to:

and if not, checking the information to be checked.

For other functions of the processor, reference may also be made to the contents described in the above embodiments, which are not described in detail herein.

Based on the same inventive concept, embodiments of the present specification further provide a computer-readable storage medium including a program for use in conjunction with an electronic device, the program being executable by a processor to perform the steps of:

and if not, checking the information to be checked.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (e.g., improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardbylangue (Hardware Description Language), vhjhdul, and the like, which are currently used in most popular languages. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that 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 like elements in a process, method, article, or apparatus that comprises the element.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are 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 above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A service admission verification method comprises the following steps:

and if not, checking the information to be checked.

2. The method according to claim 1, wherein determining the to-be-verified information corresponding to at least one to-be-admitted service according to the service admission request comprises:

3. The method according to claim 1, wherein determining the to-be-verified information corresponding to at least one to-be-admitted service according to the service admission request comprises:

4. The method according to claim 1, if the to-be-checked information corresponding to at least two services to be admitted is determined according to the service admission request, the method further comprises:

5. The method according to claim 4, wherein if the to-be-checked information corresponding to the at least two services to be admitted respectively includes repeated to-be-checked information, performing deduplication processing on the to-be-checked information corresponding to the at least two services to be admitted includes at least one of the following manners:

6. The method of claim 4, further comprising:

7. The method according to claim 1, wherein the step of determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified includes:

8. The method according to claim 1, wherein the step of determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified includes:

9. The method according to claim 1, after determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified, further comprising:

10. The method of claim 1, wherein verifying the information to be verified comprises:

and checking the at least one object to be checked.

11. A traffic admission verification apparatus comprising:

the judging module is used for judging whether the historical verification information corresponding to the user identification contains the historical verification result of the service access information to be verified;

and if not, checking the service access information to be checked.

12. The apparatus according to claim 11, wherein the determining, according to the service admission request, to-be-verified information corresponding to at least one service to be admitted comprises:

13. The apparatus according to claim 11, wherein the determining, according to the service admission request, to-be-verified information corresponding to at least one service to be admitted comprises:

14. The apparatus according to claim 11, if the to-be-verified information corresponding to at least two services to be admitted is determined according to the service admission request, the apparatus further comprises:

15. The apparatus according to claim 14, wherein if the to-be-checked information corresponding to the at least two services to be admitted respectively includes repeated to-be-checked information, the process of de-duplicating the to-be-checked information corresponding to the at least two services to be admitted includes at least one of the following manners:

16. The apparatus of claim 14, the apparatus further comprising:

17. The apparatus according to claim 11, wherein the determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified includes:

18. The apparatus according to claim 11, wherein the determining whether the historical verification information corresponding to the user identifier includes the historical verification result of the information to be verified includes:

19. The apparatus according to claim 11, after determining whether the historical verification result of the information to be verified is included in the historical verification information corresponding to the user identifier, further comprising:

20. The apparatus of claim 11, the verifying the information to be verified comprising:

and checking the at least one object to be checked.

21. An electronic device comprising at least one processor and a memory, the memory storing a program and configured for the at least one processor to perform the steps of:

judging whether the historical verification information corresponding to the user identification contains the historical verification result of the service access information to be verified;

and if not, checking the service access information to be checked.