CN109617860B - Real-name authentication method and device for account - Google Patents
Real-name authentication method and device for account Download PDFInfo
- Publication number
- CN109617860B CN109617860B CN201811377869.2A CN201811377869A CN109617860B CN 109617860 B CN109617860 B CN 109617860B CN 201811377869 A CN201811377869 A CN 201811377869A CN 109617860 B CN109617860 B CN 109617860B
- Authority
- CN
- China
- Prior art keywords
- real
- account
- name
- product
- identity information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/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
- 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/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4012—Verifying personal identification numbers [PIN]
Abstract
The embodiment of the application discloses a real-name authentication method and device for an account. The method comprises the following steps: receiving a request for purchasing a real-name product sent by a user through a terminal; verifying whether the identity information contained in the purchase information of the real-name products is consistent with the identity information corresponding to the account information used for purchasing the real-name products; if the product is consistent with the service life of the product, acquiring the service life of the product; and if the use state is used, confirming that the account is a real-name authentication account under the condition that the account is a non-real-name authentication account. By using the embodiment of the application, the purpose of real-name authentication of the non-real-name authentication account can be realized, or the real-name authentication account which is cheated and set by manual or system verification can be distinguished.
Description
The application is a divisional application of Chinese patent application with application number 201610021993.X and name of invention "real name authentication method and device of account" filed by the Chinese patent office in 2016, 01, month 13.
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for authenticating a real name of an account.
Background
With the continuous development of internet technology, the situation that user identity information is falsely used by others is continuously increased. If lawless persons use the identity information for fraudulent use to carry out illegal activities such as money washing and the like, the lawless persons can not be caught, and the lawless persons can also have great influence on normal users with the identity being falsely used.
Conventionally, in order to avoid such a situation, a method of performing real-name authentication on an account has been widely adopted for each Application (App). The real-name authentication is that it is necessary to confirm that the account issuer holds his own identity card for account opening, i.e. the person and the identity card are matched.
Some accounts are opened without real-name authentication. For example, only the identification card is uploaded, so that the account is a non-real-name authentication account.
For another example, some users cheat manual or system audit through disguise and the like, and open real-name authentication accounts successfully.
Disclosure of Invention
An embodiment of the present invention provides a method and an apparatus for authenticating a real name of an account, so as to solve the problems in the prior art.
In order to solve the above technical problem, the method and apparatus for authenticating a real name of an account provided in the embodiment of the present application are implemented as follows:
a method of real-name authentication of an account, comprising:
receiving a request for purchasing a real-name product sent by a user through a terminal;
verifying whether the identity information contained in the purchase information of the real-name products is consistent with the identity information corresponding to the account information used for purchasing the real-name products;
if the product is consistent with the service life of the product, acquiring the service life of the product;
and if the use state is used, confirming that the account is a real-name authentication account under the condition that the account is a non-real-name authentication account.
A method of real-name authentication of an account, comprising:
receiving a request for purchasing a real-name product sent by a user through a terminal;
verifying whether the identity information contained in the purchase information of the real-name products is consistent with the identity information corresponding to the account information used for purchasing the real-name products;
if the product is consistent with the service life of the product, acquiring the service life of the product;
and if the use state is used, promoting the real-name authentication level of the account under the condition that the account is a real-name authentication account.
An account real-name authentication device, comprising:
the receiving unit is used for receiving a request of purchasing a real-name product sent by a user through a terminal;
the verification unit is used for verifying whether the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product;
the acquiring unit is used for acquiring the use state of the product when the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product;
and the authentication unit is used for confirming that the account is a real-name authentication account when the account is a non-real-name authentication account when the use state is used.
An account real-name authentication device, comprising:
the receiving unit is used for receiving a request of purchasing a real-name product sent by a user through a terminal;
the verification unit is used for verifying whether the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product;
the acquiring unit is used for acquiring the use state of the product when the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product;
the judging unit is used for judging whether the account is a real-name authentication account or not when the using state is used;
and the promoting unit is used for promoting the real-name authentication level of the account under the condition that the account is a real-name authentication account when the using state is used.
According to the technical scheme provided by the embodiment of the application, when a user uses a real-name system product, a field worker needs to verify whether the identity information of the user is the user, when the identity information is the user, the use state of the product corresponding to the identity information is acquired as used, and the account can be confirmed to be a real-name authentication account under the condition that the account is a non-real-name authentication account; thus, the purpose of real-name authentication of the non-real-name authentication account is achieved. Or, in the case that the account is a real-name authentication account, the real-name authentication level of the account can be improved; in this way, for the account with confirmed real-name authentication, the real-name authentication of the account can be further performed in a mode of improving the real-name authentication level of the account, so that the account with confirmed real-name authentication which is manually or systematically checked and opened is distinguished.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.
FIG. 1 is a flow chart of a method for real-name authentication of an account provided in an embodiment of the present application;
FIG. 2 is a flowchart of a method for real-name authentication of an account provided in an embodiment of the present application;
FIG. 3 is a block diagram of an apparatus for real-name authentication of an account according to an embodiment of the present application;
fig. 4 is a block diagram of an account real-name authentication apparatus according to an embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without inventive step, shall fall within the scope of protection of the present application.
Fig. 1 is a flowchart of a real-name authentication method for an account provided in an embodiment of the present application. In this embodiment, the method for authenticating the real name of the account includes the following steps:
s110: and receiving a request sent by a user through the terminal for purchasing the real-name products.
The terminal includes a desktop computer, a laptop computer, a tablet computer, a smart phone, a handheld computer, a personal digital assistant ("PDA"), or any other wired or wireless processor-driven device.
The real-name system product can comprise a product which needs to verify identity information when a user uses the product, and the product comprises at least one of a train ticket, an airplane ticket and a hotel accommodation. The identity information may include an identification number.
In this embodiment, the user may use an application (e.g., pay for treasure, travel) on the terminal to purchase the real-name product. Generally, when a user purchases the real-name product, the user needs to provide identity information (such as an identification number) of the user; in this way, the server of the application program can receive a request sent by the user through the terminal to purchase the real-name product.
In the following, taking the scenario of train tickets as an example, the user can use an application on the terminal to purchase train tickets. Generally, when a user purchases a train ticket, identity information (such as an identification number) of a ticket purchaser needs to be provided; in this way, the server of the application program can receive a request sent by the user through the terminal to purchase the train ticket.
In the following, taking the scenario of airline tickets as an example, a user can purchase airline tickets using an application on a terminal. Generally, when a user purchases an airline ticket, identity information (such as an identification number) of a ticket purchaser needs to be provided; in this way, the server of the application program can receive a request for purchasing an airline ticket sent by the user through the terminal.
In the following, taking the hotel accommodation scenario as an example, the user may book the hotel accommodation using an application on the terminal. Generally, when a user reserves a hotel, identity information (such as an identification number) of a lodging person needs to be provided; in this way, the server of the application program can receive a request for reservation of hotel accommodations sent by the user through the terminal.
S120: and verifying whether the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product.
As described above, since the user needs to provide the identification information when purchasing the real-name product through the terminal, when the server of the application receives the request for purchasing the real-name product transmitted from the user through the terminal, the request includes the identification information included in the purchase information of the real-name product.
And the identity information corresponding to the account information comprises an identity card number.
In practical application, the user can purchase real-name products by himself or herself through the application program on the terminal, and can purchase real-name products by others. If the user is to help others to buy the real-name products, the used identity information is not the identity information of the user; in this way, the identity information included in the purchase information of the real-name product is the identity information of the non-user, and the identity information corresponding to the account information on the application program is the identity information of the user, so that the identity information in the purchase information of the real-name product is verified to be inconsistent with the identity information corresponding to the account information used for purchasing the real-name product, and in the case of inconsistency, the subsequent steps of the embodiment of the present invention do not need to be executed. If the user purchases a real-name system product for himself, the used identity information is identity information of the user; in this way, since the identity information included in the purchase information of the real-name product is the identity information of the user and the identity information corresponding to the account information on the application program is also the identity information of the user, it is verified that the identity information in the purchase information of the real-name product is identical to the identity information corresponding to the account information used for purchasing the real-name product, and the step S130 is executed.
S130: and if the product is consistent with the preset standard, acquiring the use state of the product.
When the server of the application program verifies that the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product, the server of the application program can further acquire the use state of the product. Generally, the usage status is divided into "unused" and "used"; after the real-name product is purchased successfully, the default use state of the product in the product server is 'unused', and when the product is used, the product server changes the use state of the product into 'used'.
In practical applications, when the user uses the real-name product, a worker in the field usually verifies the identity information of the user. For example, a user needs to present his/her identity card, and a worker in the field can verify whether the appearance of the user is consistent with the picture on the identity card, and also verify whether the information (e.g., identity card number) on the identity card is consistent with the identity information (e.g., identity card number) on the product used by the user. If the identity of the product is consistent with the identity of the product, the user can use the product through identity verification on site; and after the product is used, the use state of the product in the product server is changed to "used". If the two products are not consistent, the user cannot pass the identity verification on the spot, the staff on the spot refuses the user to use the product, and the use state of the product in the product server is still 'unused'.
The product server may be one server, or may be divided into a plurality of independent servers according to a specific scenario. In the above scenes of the medium train ticket, the air ticket and the hotel accommodation, the product server may be the same server, or three servers respectively correspond to the three scenes.
Still taking the scenario of the train ticket as an example, after the user successfully purchases the train ticket, the default usage status of the train ticket in the product server (in this scenario, the product server may be used to sell the train ticket) is "unused". When the train ticket is checked, the product server changes the use state of the train ticket into used. When the user uses the train ticket, the staff at the train station usually verifies the identity information of the user. For example, the user needs to present his identity card, and the staff in the field can verify whether the appearance of the user is consistent with the picture on the identity card, and also verify whether the information (such as the identity card number) on the identity card is consistent with the identity information (such as the identity card number) on the train ticket used by the user. If the two are consistent, the user can use the train ticket through the identity verification on site; and after checking the ticket, the use state of the train ticket in the product server is changed to 'used'. If the two are not consistent, the user can not pass the identity verification of the site, the staff in the site refuses the user to use the train ticket, and the use state of the train ticket in the product server is still 'unused'.
Still taking the scenario of the airline ticket as an example, after the user successfully purchases the airline ticket, the default usage state of the airline ticket in the product server (which may be used for selling the airline ticket in this scenario) is "unused". When the airplane ticket is checked, the product server changes the use state of the airplane ticket into used. When the user uses the airline ticket, typically, the identity of the user is verified by the airport staff. For example, the user needs to present his identity card, and the staff in the field can verify whether the appearance of the user is consistent with the picture on the identity card, and also verify whether the information (such as the identity card number) on the identity card is consistent with the identity information (such as the identity card number) on the airline ticket used by the user. If the identity of the users is consistent with the identity of the users, the users can use the airline tickets through identity verification on the spot; and the usage status of the airline ticket in the product server is changed to "used" after ticket checking. If the two are not consistent, the user can not pass the identity verification of the field, the staff in the field refuses the user to use the airline ticket, and the use state of the airline ticket in the product server is still 'unused'.
Still taking the hotel accommodation scenario as an example, after the user successfully reserves the hotel accommodation, the default usage status of the hotel accommodation in the product server (in this scenario, the product server may be used for reserving the hotel accommodation) is "unused", and after the user transacts the check-in procedure, the product server changes the usage status of the hotel accommodation to "used". When a user uses the hotel accommodation, the staff of the hotel can check the identity information of the user. For example, the user needs to present his/her identity card, and the staff in the field can verify whether the appearance of the user is consistent with the picture on the identity card, and also verify whether the information (such as the identity card number) on the identity card is consistent with the identity information (such as the identity card number) provided when the user reserves a hotel. If the identity is consistent, the user can pass the identity verification on site, so that the check-in procedure can be handled; and after the check-in procedure is transacted, the use status of the hotel accommodations in the product server is changed to "used". If the difference is not consistent, the user can not pass the identity verification on the spot, the staff on the spot refuses the user to handle the check-in procedure, and the use state of the hotel accommodations in the product server is still 'unused'.
Specifically, the step S130 may include:
and receiving the use state of the product corresponding to the identity information pushed by the product server.
Still taking the scene of the train ticket as an example, the server of the application program may receive the use state of the train ticket corresponding to the identity information pushed by the product server.
Still taking the scenario of the airline ticket as an example, the server of the application program may receive the usage state of the airline ticket corresponding to the identity information pushed by the product server.
Still taking the scene of the hotel accommodations as an example, the server of the application program may receive the use state of the hotel accommodations corresponding to the identity information pushed by the product server.
In this embodiment, since the user purchases the real-name product through the application program on the terminal, in order to provide the user with the use state of the real-name product purchased by the user, the real-name product server may push the use state of the real-name product purchased by the user to the server of the application program. Thus, the user can check the use state of the purchased real-name product through the application program on the terminal.
In other embodiments, the S130 step may include:
and inquiring the use state of the product corresponding to the identity information from the product server.
Still taking the scenario of the train ticket as an example, the server of the application program may query the product server for the use state of the train ticket corresponding to the identity information.
Still taking the scenario of the airline ticket as an example, the server of the application program may query the product server for the usage state of the airline ticket corresponding to the identity information.
Still taking the scenario of hotel accommodations as an example, the server of the application program may query the product server for the use state of the hotel accommodations corresponding to the identity information.
In this embodiment, since the user purchases the real-name product through the application program on the terminal, in order to provide the use state of the purchased real-name product to the user, the server of the application program may query, from the real-name product server, the use state of the product corresponding to the identity information. Thus, the user can check the use state of the purchased real-name product through the application program on the terminal.
S140: and if the use state is used, confirming that the account is a real-name authentication account under the condition that the account is a non-real-name authentication account.
In this embodiment, since the real-name product is purchased through the application program, the application program needs to be logged in to the account, and after the real-name product is purchased successfully, the corresponding relationship between the identity information and the account is recorded in the server of the application program.
If the use state is 'used', the user passes the on-site identity verification, and the identity information is proved to be the user, the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product, so that the account can be confirmed to be used by the user, and if the account is a non-real-name authentication account, the server of the application program can confirm that the account is a real-name authentication account.
If the use state is 'unused', the user is not approved by identity verification on site, or the user does not use the product on site; the server of the application program does not need to perform the subsequent steps of the embodiment.
According to the embodiment, when the user uses the real-name system product, the on-site staff needs to verify whether the identity information of the user is the user, and when the identity information is the user, the use state of the product corresponding to the identity information is acquired as used, so that the account corresponding to the identity information can be confirmed to be the real-name authentication account under the condition that the account is a non-real-name authentication account. Thus, the aim of real-name authentication of the non-real-name authentication account is fulfilled
In the embodiment of the present application, after the step S140, the following steps may be further included:
and pushing a notice for confirming that the account is the real-name authentication account to the terminal.
By the embodiment, after the server of the application program confirms that the account is the real-name authentication account, the notification for confirming that the account is the real-name authentication account can be pushed to the terminal. Therefore, the user can be informed in time, and the user experience is improved.
Fig. 2 is a flowchart of a real-name authentication method for an account provided in an embodiment of the present application. In this embodiment, the method for authenticating the real name of the account includes the following steps:
s210: and receiving a request sent by a user through the terminal for purchasing the real-name products.
The real-name system products comprise at least one of train tickets, air tickets and hotel accommodations. The step S210 is similar to the step S110 in the above embodiment, and is not described here again.
S220: and verifying whether the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product.
The step S220 is similar to the step S120 in the above embodiment, and is not described again here.
S230: and if the product is consistent with the preset standard, acquiring the use state of the product.
The acquiring the use state of the product specifically comprises:
receiving the use state of the product corresponding to the identity information pushed by the product server;
or inquiring the use state of the product corresponding to the identity information from the product server.
The step S230 is similar to the step S130 in the above embodiment, and is not described here again.
S240: and if the use state is used, promoting the real-name authentication level of the account under the condition that the account is a real-name authentication account.
In this embodiment, since the real-name product is purchased through the application program, the application program needs to be logged in to the account, and after the real-name product is purchased successfully, the corresponding relationship between the identity information and the account is recorded in the server of the application program.
The real-name authentication level can be different levels which are preset, for example, the real-name authentication level which does not pass the real-name authentication account is 1 level; the security level of the account of the identity recognition completed by the prior art is 2 level; the security level of the account of the identity recognition completed by the embodiment of the application is 3 level. A higher rank in this example indicates a more secure account.
If the use state is 'used', the user passes the on-site identity verification, and the identity information is proved to be the user, because the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product, the account can be confirmed to be used by the user, and if the account is a real-name authentication account, the server of the application program can improve the real-name authentication level of the account.
If the use state is 'unused', the user is not approved by identity verification on site, or the user does not use the product on site; the server of the application program does not need to perform the subsequent steps of the embodiment.
According to the embodiment, when the user uses the real-name system product, the on-site staff needs to verify whether the identity information of the user is the user, and when the identity information is the user, the use state of the product corresponding to the identity information is acquired as used, so that the real-name authentication level of the account can be improved under the condition that the account is a real-name authentication account. In this way, for the account with confirmed real-name authentication, the real-name authentication of the account can be further performed in a mode of improving the real-name authentication level of the account, so that the account with confirmed real-name authentication which is manually or systematically checked and opened is distinguished.
The embodiments of the present application also provide an apparatus, which can implement the above method steps, and the apparatus can be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, the logical device is formed by reading a corresponding computer program instruction into a memory by a Central Processing Unit (CPU) of a server to run.
Fig. 3 is a block diagram of an account real-name authentication apparatus according to an embodiment of the present disclosure. In this embodiment, the real-name authentication device for an account includes:
a receiving unit 310, configured to receive a request for purchasing a real-name product sent by a user through a terminal;
a verification unit 320, configured to verify whether identity information included in the purchase information of the real-name product is consistent with identity information corresponding to account information used for purchasing the real-name product;
an obtaining unit 330, configured to obtain a usage state of the product when the identity information included in the purchase information of the real-name product is consistent with account information corresponding to account information used for purchasing the real-name product;
an authentication unit 340, configured to, when the usage status is used, confirm that the account is a real-name authentication account if the account is a non-real-name authentication account.
Preferably, the obtaining unit 330 specifically includes:
the product server is used for pushing the identity information of the product to the real-name system product purchase information;
or, when the identity information included in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product, the product server is used for inquiring the use state of the product corresponding to the identity information.
Preferably, after the identifying unit 340, the method further includes:
and the pushing unit is used for pushing a notice for confirming that the account is the real-name authentication account to the terminal.
Preferably, the real-name products comprise at least one of train tickets, air tickets and hotel accommodations.
Fig. 4 is a block diagram of an account real-name authentication apparatus according to an embodiment of the present disclosure. In this embodiment, the device for authenticating the real name of the account includes:
a receiving unit 410, configured to receive a request for purchasing a real-name product sent by a user through a terminal;
a verification unit 420, configured to verify whether identity information included in the purchase information of the real-name product is consistent with identity information corresponding to account information used for purchasing the real-name product;
an obtaining unit 430, configured to obtain a use state of the product when the identity information included in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product;
the promoting unit 440 is configured to promote the real-name authentication level of the account when the account is a real-name authentication account when the usage status is used.
Preferably, the obtaining unit 430 specifically includes:
when the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product, receiving the use state of the product corresponding to the identity information pushed by the product server;
or, when the identity information included in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product, inquiring the use state of the product corresponding to the identity information from the product server.
Preferably, the real-name products comprise at least one of train tickets, air tickets and hotel accommodations.
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 (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 Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. 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.
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 magnetic 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.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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 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 (8)
1. A real-name authentication method of an account is characterized by comprising the following steps:
receiving a request for purchasing a real-name product sent by a user through a terminal;
verifying whether the identity information contained in the purchase information of the real-name products is consistent with the identity information corresponding to the account information used for purchasing the real-name products;
and if the real-name system products are consistent and the real-name system products are purchased successfully, confirming that the account is a real-name authentication account under the condition that the account is a non-real-name authentication account.
2. The method of claim 1, wherein the real-name products comprise at least one of train tickets, airline tickets, hotel accommodations.
3. A real-name authentication method of an account is characterized by comprising the following steps:
receiving a request for purchasing a real-name product sent by a user through a terminal;
verifying whether the identity information contained in the purchase information of the real-name products is consistent with the identity information corresponding to the account information used for purchasing the real-name products;
if the real-name authentication account is consistent with the real-name authentication account, and the real-name authentication level of the account is improved under the condition that the account is the real-name authentication account.
4. The method of claim 3, wherein the real-name products comprise at least one of train tickets, airline tickets, hotel accommodations.
5. An account real-name authentication device, comprising:
the receiving unit is used for receiving a request of purchasing a real-name product sent by a user through a terminal;
the verification unit is used for verifying whether the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product;
and an authentication unit configured to confirm that the account is a real-name authentication account if the account is a non-real-name authentication account if the identity information included in the purchase information of the real-name product matches the identity information corresponding to the account information used for purchasing the real-name product and the real-name product is purchased successfully.
6. The apparatus of claim 5, wherein the real-name products comprise at least one of train tickets, airline tickets, hotel accommodations.
7. An account real-name authentication device, comprising:
the receiving unit is used for receiving a request of purchasing a real-name product sent by a user through a terminal;
the verification unit is used for verifying whether the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product;
and the upgrading unit is used for upgrading the real-name authentication level of the account when the identity information contained in the purchase information of the real-name product is consistent with the identity information corresponding to the account information used for purchasing the real-name product and the real-name product is purchased successfully and the account is a real-name authentication account.
8. The apparatus of claim 7, wherein the real-name products comprise at least one of train tickets, airline tickets, hotel accommodations.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811377869.2A CN109617860B (en) | 2016-01-13 | 2016-01-13 | Real-name authentication method and device for account |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610021993.XA CN105577678B (en) | 2016-01-13 | 2016-01-13 | The real name identification method and device of account |
| CN201811377869.2A CN109617860B (en) | 2016-01-13 | 2016-01-13 | Real-name authentication method and device for account |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610021993.XA Division CN105577678B (en) | 2016-01-13 | 2016-01-13 | The real name identification method and device of account |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109617860A CN109617860A (en) | 2019-04-12 |
| CN109617860B true CN109617860B (en) | 2021-10-22 |
Family
ID=55887335
Family Applications (4)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811377869.2A Active CN109617860B (en) | 2016-01-13 | 2016-01-13 | Real-name authentication method and device for account |
| CN201811379030.2A Active CN109361691B (en) | 2016-01-13 | 2016-01-13 | Real-name authentication method and device for account |
| CN201610021993.XA Active CN105577678B (en) | 2016-01-13 | 2016-01-13 | The real name identification method and device of account |
| CN201811377896.XA Active CN109347860B (en) | 2016-01-13 | 2016-01-13 | Real-name authentication method and device for account |
Family Applications After (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811379030.2A Active CN109361691B (en) | 2016-01-13 | 2016-01-13 | Real-name authentication method and device for account |
| CN201610021993.XA Active CN105577678B (en) | 2016-01-13 | 2016-01-13 | The real name identification method and device of account |
| CN201811377896.XA Active CN109347860B (en) | 2016-01-13 | 2016-01-13 | Real-name authentication method and device for account |
Country Status (2)
| Country | Link |
|---|---|
| CN (4) | CN109617860B (en) |
| HK (1) | HK1224098A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109472607A (en) * | 2018-09-18 | 2019-03-15 | 深圳壹账通智能科技有限公司 | Product purchase request processing method, device, computer equipment and storage medium |
| CN110049005B (en) * | 2019-03-06 | 2021-06-01 | 厦门市易联众易惠科技有限公司 | Real-name authentication sharing processing method, system, equipment and readable medium |
| CN111049808A (en) * | 2019-11-26 | 2020-04-21 | 中国联合网络通信集团有限公司 | Real-name authentication method and device |
| CN116436655A (en) * | 2021-02-02 | 2023-07-14 | 支付宝(杭州)信息技术有限公司 | Account authentication method, device, equipment and medium |
| CN113283959B (en) * | 2021-05-12 | 2022-07-05 | 支付宝(杭州)信息技术有限公司 | Travel information pushing processing method, device, equipment and system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102004978A (en) * | 2010-12-02 | 2011-04-06 | 联动优势科技有限公司 | Secure real-name payment system and method |
| CN102045367A (en) * | 2011-01-10 | 2011-05-04 | 软库创投（北京）科技有限公司 | Registration method and authentication server of real-name authentication |
| CN102647430A (en) * | 2012-05-09 | 2012-08-22 | 司文 | Real-name certification system and method capable of hiding identity information |
| CN103269270A (en) * | 2013-04-25 | 2013-08-28 | 安徽杨凌科技有限公司 | Real-name authentication safe login method and system based on cell phone number |
| CN103854182A (en) * | 2012-11-30 | 2014-06-11 | 国泰世华商业银行股份有限公司 | Method for online shopping by real-name authentication |
| WO2014176748A1 (en) * | 2013-04-28 | 2014-11-06 | Tencent Technology (Shenzhen) Company Limited | Method, device, and system for accessing third party platforms via a messaging application |
| CN104378759A (en) * | 2014-12-04 | 2015-02-25 | 福建星网锐捷网络有限公司 | Users' real name authentication method and system |
Family Cites Families (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20020020051A (en) * | 2000-09-07 | 2002-03-14 | 전준호 | An electronic method of purchasing at volume discount from participating sites and mobile information services using an identity secure in-house credit account |
| EP1237327A3 (en) * | 2001-03-01 | 2003-07-02 | NTT Data Technology Corporation | Method and system for individual authentication and digital signature utilizing article having DNA based ID information mark |
| CN102271314B (en) * | 2010-06-07 | 2015-04-01 | 中兴通讯股份有限公司 | Method and system for realizing terminal communication and method for realizing terminal position update |
| CN102377635B (en) * | 2010-08-06 | 2014-01-01 | 北京乾唐视联网络科技有限公司 | Metropolitan area network communication method and communication system thereof |
| CN102376049A (en) * | 2010-08-27 | 2012-03-14 | 黄金富 | Cell phone payment confirmation system based on security verification and corresponding method thereof |
| CN102063740A (en) * | 2010-11-15 | 2011-05-18 | 北京交通大学 | Real-name railway ticket detecting system based on palm vein network characteristic authentication |
| JP5427825B2 (en) * | 2011-04-19 | 2014-02-26 | 株式会社日立製作所 | Kana system |
| CN102136160B (en) * | 2011-04-20 | 2013-05-08 | 铁道部运输局 | Electronic ticket system for railway |
| US9119067B2 (en) * | 2011-06-03 | 2015-08-25 | Apple Inc. | Embodiments of a system and method for securely managing multiple user handles across multiple data processing devices |
| CN102376206A (en) * | 2011-09-26 | 2012-03-14 | 无锡宇科万通科技有限公司 | Passenger ticket using reflective display screen |
| CN105376220B (en) * | 2011-11-30 | 2019-09-17 | 阿里巴巴集团控股有限公司 | A kind of service implementation method, system and server |
| CN102800131A (en) * | 2012-07-24 | 2012-11-28 | 中国铁道科学研究院电子计算技术研究所 | Ticket checking system for real-name train ticket system |
| CN103634120A (en) * | 2013-12-18 | 2014-03-12 | 上海市数字证书认证中心有限公司 | Method and system for real-name authentication based on face recognition |
| CN104182726A (en) * | 2014-02-25 | 2014-12-03 | 苏凯 | Real name authentication system based on face identification |
| CN105100029B (en) * | 2014-05-22 | 2018-10-30 | 阿里巴巴集团控股有限公司 | The method and apparatus that authentication is carried out to user |
| CN104113526A (en) * | 2014-06-04 | 2014-10-22 | 潘世杰 | Server, client and method for matching resource transactions |
| CN104021494B (en) * | 2014-06-23 | 2018-03-02 | 上海携程商务有限公司 | The operating system and operating method of cyber ordering system of real name product |
| CN104615852B (en) * | 2014-12-31 | 2018-04-27 | 浙江融创信息产业有限公司 | The method for order and the raising source service efficiency of registering for guarantee online booking |
| CN104717073B (en) * | 2015-03-19 | 2018-09-18 | 张文 | Personal information shared system and its personal information sharing method and identity identifying method |
-
2016
- 2016-01-13 CN CN201811377869.2A patent/CN109617860B/en active Active
- 2016-01-13 CN CN201811379030.2A patent/CN109361691B/en active Active
- 2016-01-13 CN CN201610021993.XA patent/CN105577678B/en active Active
- 2016-01-13 CN CN201811377896.XA patent/CN109347860B/en active Active
- 2016-10-24 HK HK16112187.0A patent/HK1224098A1/en unknown
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102004978A (en) * | 2010-12-02 | 2011-04-06 | 联动优势科技有限公司 | Secure real-name payment system and method |
| CN102045367A (en) * | 2011-01-10 | 2011-05-04 | 软库创投（北京）科技有限公司 | Registration method and authentication server of real-name authentication |
| CN102647430A (en) * | 2012-05-09 | 2012-08-22 | 司文 | Real-name certification system and method capable of hiding identity information |
| CN103854182A (en) * | 2012-11-30 | 2014-06-11 | 国泰世华商业银行股份有限公司 | Method for online shopping by real-name authentication |
| CN103269270A (en) * | 2013-04-25 | 2013-08-28 | 安徽杨凌科技有限公司 | Real-name authentication safe login method and system based on cell phone number |
| WO2014176748A1 (en) * | 2013-04-28 | 2014-11-06 | Tencent Technology (Shenzhen) Company Limited | Method, device, and system for accessing third party platforms via a messaging application |
| CN104378759A (en) * | 2014-12-04 | 2015-02-25 | 福建星网锐捷网络有限公司 | Users' real name authentication method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109617860A (en) | 2019-04-12 |
| CN109361691B (en) | 2021-07-20 |
| HK1224098A1 (en) | 2017-08-11 |
| CN109347860B (en) | 2021-08-24 |
| CN105577678B (en) | 2018-11-09 |
| CN109361691A (en) | 2019-02-19 |
| CN105577678A (en) | 2016-05-11 |
| CN109347860A (en) | 2019-02-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109617860B (en) | Real-name authentication method and device for account | |
| CN109064175B (en) | Account embezzlement risk prevention and control method and device | |
| CN107341702B (en) | Service processing method and device | |
| CA2934716C (en) | Payment container, method for creating, method for processing, corresponding devices and programs | |
| US11455612B2 (en) | Payment systems and methods for managing payment card use | |
| US11847633B1 (en) | Connected payment card systems and methods | |
| CN111985703B (en) | User identity state prediction method, device and equipment | |
| CN111784345B (en) | Payment processing method, device, equipment and system | |
| CN105659241A (en) | Confirming the identity of integrator applications | |
| CN110009335B (en) | Payment code generation method, payment code generation device, mobile payment method, mobile payment device and equipment | |
| RU2656960C2 (en) | Transport system user checking | |
| CN110992162A (en) | Resource processing method, device, equipment and system | |
| CN111738473B (en) | Processing method, device, equipment and system for ticket booking service | |
| US20220374896A1 (en) | Identity, Payment and Access Control System | |
| CN110619557B (en) | Fixed asset lease management method and device and electronic equipment | |
| US20180012223A1 (en) | Methods and computer systems for implementing a payment card network | |
| US20220058621A1 (en) | Methods and systems for facilitating managing of payments made using digital wallets | |
| US20180018648A1 (en) | Systems and methods for managing user accounts using a directory kiosk system | |
| US20210287194A1 (en) | Systems and methods for incentivizing the use of a payment mechanism | |
| CN113283894A (en) | Method, device and computer readable medium for payment based on medical insurance electronic certificate | |
| JP6439386B2 (en) | Storage medium management program, storage medium management method, and storage medium management apparatus | |
| KR20230023531A (en) | Method, system and non-transitory computer-readable recording medium for managing ticket transaction on blockchain network | |
| CN116521542A (en) | Method and device for service object unlimited, storage medium and electronic equipment | |
| CN114240423A (en) | Prepaid card fund protection method and device, electronic equipment and storage medium | |
| CN113450144A (en) | Method and device for executing service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200924 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200924 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |