WO2018218411A1 - 验证方法及设备 - Google Patents

验证方法及设备 Download PDF

Info

Publication number
WO2018218411A1
WO2018218411A1 PCT/CN2017/086292 CN2017086292W WO2018218411A1 WO 2018218411 A1 WO2018218411 A1 WO 2018218411A1 CN 2017086292 W CN2017086292 W CN 2017086292W WO 2018218411 A1 WO2018218411 A1 WO 2018218411A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
verification
identification information
user equipment
user
Prior art date
Application number
PCT/CN2017/086292
Other languages
English (en)
French (fr)
Inventor
袁冰松
余伟铬
庄琼鹰
罗昌明
Original Assignee
深圳来电科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳来电科技有限公司 filed Critical 深圳来电科技有限公司
Priority to PCT/CN2017/086292 priority Critical patent/WO2018218411A1/zh
Publication of WO2018218411A1 publication Critical patent/WO2018218411A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present disclosure relates to a verification method and apparatus.
  • the present disclosure relates to an authentication method and apparatus for providing a service for verification.
  • a dynamic code is a pseudo-random code generated according to a special algorithm, which is usually dynamically changed at intervals. Because of the high security of dynamic code, it is widely used in many fields such as online banking, online games, and telecommunications. At present, the dynamic code forms mainly include mobile phone passwords, hardware tokens, and mobile phone tokens.
  • the implementation of dynamic code mainly depends on time, so a so-called dynamic code verification method for time synchronization verification is proposed.
  • the device and the background server are internally written with the same algorithm, and the device side generates a dynamic code according to the time change of the device side according to the algorithm, and inputs the generated dynamic code into the server.
  • the server After receiving the input dynamic code, the server also generates a dynamic code according to the server side time variation according to the same algorithm. The server compares the two. If the two are the same, the verification is successful and the server tells the device that the verification is successful.
  • Another method for verifying dynamic code is that the server sends the dynamic code to the user's mobile phone, and then the user inputs the dynamic code into the device, and the device submits the input dynamic code to the server for verification. If the verification is successful, the verification is successful. And the server informs the device that the verification is successful and notifies the device to provide the service.
  • the present disclosure is presented to provide an improved verification method and apparatus.
  • a method for a first device comprising: generating identification information based on information related to a usage status of the first device; outputting the identification information for the user device to acquire the identification information Receiving first verification information from the user equipment or user; and verifying the received first verification information by using second verification information corresponding to the identification information.
  • a method for a user equipment comprising obtaining a base of a first device output Identification information generated from information related to usage status of the first device; transmitting the identification information to the second device; receiving verification information generated from the second device using the identification information; and outputting the verification Information for verification by the first device.
  • a method for a second device comprising: receiving identification information from a user device, the identification information being based on information related to usage status of the first device; Generating verification information; and transmitting the verification information to the user equipment.
  • a method comprising: a first device generating identification information, the identification information including information related to a usage status of the first device; the user device acquiring the identification information from the first device, and Transmitting the identification information to the second device; the second device generating the first verification information by using the received identification information, and transmitting the first verification information to the user equipment; a verification information; and the first device verifies the first verification information based on the second verification information corresponding to the generated identification information.
  • a first device comprising: a generating unit configured to generate identification information based on information related to usage status of the first device; for outputting the identification information for acquisition by a user device An output unit of the identification information; a receiving unit for receiving first verification information from the user equipment or user; and for using the second verification information corresponding to the identification information, the first verification received The verification unit for the information to be verified.
  • a user equipment comprising: an obtaining unit for acquiring identification information generated by the first device based on information related to usage status of the first device; and transmitting the identification information to a transmitting unit of the second device; a receiving unit for receiving the verification information generated by the second device from the identification information, and an output for outputting the verification information for verification by the first device unit.
  • a second device comprising: a receiving unit for receiving identification information from a user equipment, the identification information being based on information related to a usage status of the first device; a generating unit that generates the verification information by the identification information; and a transmitting unit that transmits the verification information to the user equipment.
  • an apparatus comprising one or more processors, and one or more memories storing instructions that, when executed by the one or more processors, cause the device to implement The method described earlier.
  • a non-transitory storage device that stores instructions that, when executed by a processor, cause implementation in accordance with the methods previously described.
  • FIG. 1 is an exemplary flow chart of a verification operation in accordance with one embodiment of the present disclosure.
  • FIG. 2 is a flow chart of an exemplary method for a first device, in accordance with one embodiment of the present disclosure.
  • FIG. 3 is an exemplary block diagram of a first device in accordance with one embodiment of the present disclosure.
  • FIG. 4 is a flow chart of an exemplary method for a user equipment, in accordance with one embodiment of the present disclosure.
  • FIG. 5 is an exemplary block diagram of a user equipment in accordance with one embodiment of the present disclosure.
  • FIG. 6 is a flowchart of an exemplary method for a second device, in accordance with one embodiment of the present disclosure.
  • FIG. 7 is an exemplary block diagram of a second device in accordance with one embodiment of the present disclosure.
  • Figure 8 is a diagrammatic view of an exemplary charging device in accordance with one embodiment.
  • Figure 9 illustrates a construction of an exemplary charging device in accordance with one embodiment.
  • Figure 10 illustrates a construction of an exemplary charging device in accordance with one embodiment.
  • Figure 11 illustrates a verification charging flow of an exemplary charging device in accordance with one embodiment.
  • FIG. 12 is a block diagram of an example structure of a device in which embodiments of the present disclosure may be implemented.
  • dynamic code generation and verification often require correct time synchronization between the device providing the service and the server to synchronize the dynamic codes on both sides. Inaccurate component timing can cause the hardware dynamic code to be out of sync with the server's dynamic code, resulting in verification failure.
  • the device and server side often need to maintain a communication connection through the network, so that the server can perform verification and instruct the device to provide service when the verification is successful. If communication problems occur between the device and the server, it will prevent the verification from proceeding normally.
  • the present disclosure proposes an improved authentication scheme that can successfully implement authentication without relying on timing synchronization of devices and servers and communication between devices and servers.
  • this technical solution can be advantageously applied in particular to dynamic code verification.
  • FIG. 1 exemplarily shows an exemplary flowchart of a verification operation flow of one embodiment of the present disclosure.
  • the first device may correspond to a device-related device providing the service, which may correspond to a different device according to a specific application, such as a shared vehicle, a shared charging device, a security device, and the like.
  • the user equipment may be a user's mobile terminal device, such as a smart phone, tablet, etc., which may also correspond to other types of devices as long as it can intervene between the first device and the second device to intervene as described in the present disclosure.
  • a specific type of identification information and verification information can be used.
  • the second device may be, for example, a background server, but the second device may also correspond to various other devices as long as it can determine the authentication information from the received identification information or transmit the verification information to the user device.
  • the first device generates identification information (S101), and outputs the identification information for acquisition by the user device (S102).
  • the user equipment acquires the identification information (S103), and transmits the identification information to the second device (S104).
  • the second device receives the identification information (S105), and generates verification information (S106). Then, the second device transmits the verification information to the user device (S107).
  • the user device acquires the verification information (S108), and outputs the verification information for acquisition by the first device (S109).
  • the first device receives the verification information (S110), and verifies the received verification information (S111). According to an embodiment, the first device may verify the received verification information by using the second verification information corresponding to the identification information.
  • the verification is implemented by the user equipment transferring information between the first device and the second device, and direct communication does not occur between the first device and the second device.
  • the identification information may be generated by the first device based on information related to usage conditions of the first device.
  • the form of the generated identification information may be, for example, a two-dimensional code, a barcode, a pattern code, or a combination of numbers, English, or the like.
  • the identification information may be generated, for example, by processing information related to the usage status of the first device according to a preset algorithm preset in the first device.
  • the identification information may include information related to usage status of the first device.
  • the information related to the usage status of the first device may be, for example, at least one of status information of the device itself, related information of the user device/user using the first device.
  • the status information of the first device itself may include the status of the service that the first device may provide (eg, whether the service is also available, how many services are still available, etc.), fault/abnormal conditions, previous usage conditions (eg, , time, number of times, etc.) and so on.
  • the status information of the first device itself may vary depending on the type of the first device, such as the power information of the charging device, the mileage information of the shared vehicle, and the like.
  • the information related to the usage status of the first device may further include Identification information of the user equipment of a device, related identification information of the user, such as a user identity card number, a barcode, a retina, a fingerprint, facial information, and the like.
  • the first device may further comprise means for collecting information related to the usage status of the first device.
  • the apparatus can include a detection component that detects an operational status of the first device to obtain information, which can be implemented in the form of hardware, software, firmware, or the like.
  • the component can include scanning means for scanning user identity information.
  • the generation of the identification information may for example also be based on identity information (ID information) of the first device.
  • ID information identity information
  • the first device may package/encrypt the identity information of the first device, the information related to the usage status of the first device, and the verification code into a specific form of dynamic information, such as a two-dimensional code.
  • identification information such as a two-dimensional code.
  • the verification code may be a random code generated according to, for example, a random code generation algorithm.
  • the verification code can also be in other forms and generated by other algorithms known in the art. This packing/encryption can be implemented by data packing/encryption algorithms/circuits known in the art and will not be described in detail herein.
  • the first device may generate a specific form of information, such as a two-dimensional code or the like, as the identification information according to the identity identification information of the first device and the information related to the usage status of the first device.
  • the identification information may be generated by an identification information generation algorithm known in the art, such as a two-dimensional code generation algorithm for generating a two-dimensional code/dynamic two-dimensional code for generating a pattern code of a pattern code/dynamic pattern code. Generate algorithms and more. It will not be described in detail here.
  • the identification information may be dynamically generated and, for example, may vary dynamically according to time, dynamically change for each generation, or dynamically according to information related to usage conditions of the first device.
  • the identification information generation may be periodically generated by the first device and displayed on the display screen of the first device for acquisition by the user equipment.
  • the identification information may be generated by the first device in response to the user's request, for example, the user requests the service via a physical or virtual button on the first device, and in response to the request, the first device may generate the identification information. After the identification information is generated, it can be displayed by the first device for acquisition by the user equipment.
  • the information related to the usage status of the first device may be collected periodically by the first device or may be acquired when the user requests to generate the identification information.
  • the first device may always generate the identification information for the user equipment to scan and transmit to the second device, so that the second device can know the state of the first device in time, and the second device can also The status of the first device is notified to the user in time, so that the user can also easily understand the status of the first device.
  • the generation of the identification information may further consider whether the information related to the usage status of the first device satisfies a predetermined condition, if the information related to the usage status of the first device does not satisfy the predetermined condition, No identification information is generated.
  • the predetermined condition may include, for example, whether it is lower than a minimum threshold at which a predetermined device can provide a service, and if it is below the threshold, the service cannot be provided.
  • the predetermined condition may include whether the user identity information is authenticated. and many more.
  • the first device may output the prompt information, so that the user equipment can more intuitively understand the state of the first device, and the user can also report the report to the server.
  • the first device is a device providing a service
  • the first device if the current state of the first device is capable of providing a service, the first device generates identification information. If the current state of the first device cannot provide the service, the first device does not generate the identification information, but displays the prompt information.
  • the generation of the identification information may also depend on the identity information of the user equipment/user.
  • the first device is a security device that needs to authenticate the user identity
  • the identification information is generated.
  • the first device also Instead of generating identification information, a prompt message is generated to inform the user.
  • the identification information can be directly notified to the user device, for example, directly to the user device, instead of Display, which further enhances security.
  • the identification information may be automatically changed every once in a period of time, for example, 1 minute, 5 minutes, etc., if the first device still does not obtain the input verification information or the verification is unsuccessful within the period of time, the identification information also changes, and then needs to be changed. Re-verify. This can further improve security.
  • the first device After the first device generates the identification information, the first device will output the identification information for the user equipment to acquire.
  • the first device may display the identification information through its display component for acquisition by the user device or the user.
  • the first device may also output the identification information to the user equipment or the user by other means, for example, by means of media printing, sound output, etc., to the user equipment or the user without displaying. If the first device can communicate with the user device, the first device can also send the identification information to the user device by means of communication.
  • the user device may acquire the identification information in various manners and transmit it to the second device through communication between the user device and the second device.
  • the user equipment may have a device such as a scanner, a camera, etc., and the user may call the device on the user device to scan the identification information displayed by the first device (for example, may be a two-dimensional code, a barcode, a pattern).
  • the code is obtained to obtain the information, and the identification information is transmitted to the second device by communication between the user equipment and the second device.
  • the user can also manually input the information into the user equipment, and send the identification information to the second device via communication of the user equipment with the second device.
  • the user device may also receive the identification information from the first device by means of communication.
  • the acquisition and transfer of the identification information may be performed by calling a single application implemented on the user device, such as a dedicated APP or a third party APP, or may also be performed by separately calling different applications. According to one embodiment, these operations can also be implemented by means of specific circuits installed on the user equipment.
  • the user equipment may simultaneously transmit the identity information of the user equipment for the second device to perform authentication while transmitting the identification information.
  • the second device may generate and send the verification information when the user equipment is authorized. Otherwise, the second device may send a prompt message to the user equipment, prompting the user equipment to use the device, or prompting the user equipment to obtain authorization.
  • the second device may receive the identification information transmitted from the user device by communicating with the user device.
  • the second device may receive the identification information through an application corresponding to the application on the user device, or may also receive the identification information through a general purpose or dedicated receiving circuit on the second device.
  • the receipt of the identification information can also be accomplished by other means known in the art and will not be described in detail herein.
  • the second device After receiving the identification information from the user device, the second device will generate the verification information based on the identification information.
  • the second device invokes an algorithm preset in the second device to process the received identification information to obtain verification information.
  • the form of the generated verification information may also be a two-dimensional code, a barcode, a pattern code, or a combination of numbers, English, and the like.
  • the form and generation of the verification information may also be different accordingly.
  • the manner in which the verification information is generated in the second device corresponds to a manner of determining the verification information corresponding to the identification information preset in the first device, for example, the algorithms used are the same of. This will be described more specifically later in conjunction with the progress of the verification.
  • the generation of the first verification information may also depend on the information related to the user device.
  • the second device may further determine whether to generate verification information according to the usage of the first device by the user equipment, for example, if the second device determines, according to the identity identification information of the user device, that the user equipment is already in use. A device no longer generates verification information and sends a report to the user device. This is especially the case, for example, when each user device can only use one first device.
  • verification information is generated to provide verification information, but the second The device records the identity information of the user equipment in association with the identity information of the first device used by the user equipment for subsequent processing.
  • the second device may further determine whether to generate verification information according to the previous status information of the user equipment/user.
  • the second device can know whether the user equipment is still using other first equipment, the previous credit rating status, whether the debt is owed, and the like, and thus can determine whether to allow the user to use the information according to the information of the user equipment.
  • a device or allow the user to try a predetermined time. If the user is not allowed to use, the verification information is not generated, and the related prompt information is presented to the user, for example, cannot be used, prompting the user to pay the fee, and then using it.
  • the second device After generating the verification information, the second device transmits the generated verification information to the user equipment.
  • the second device may transmit the authentication information to the user device by communicating with the user device.
  • the second device may transmit the authentication information through an application corresponding to the application on the user device, or may also transmit the verification information through a general purpose or dedicated transmission circuit on the second device.
  • the second device generates the first verification information and sends the first verification information to the user equipment, indicating that the second device authorizes or agrees to the user's use of the first device.
  • the transfer of the authentication information by the second device can also be accomplished by other means known in the art, here Will not be described in detail.
  • the user equipment can receive the verification information transmitted from the second device by communicating with the second device.
  • the user equipment may receive the authentication information, for example, via an application on the user equipment, or may also receive the verification information via a general purpose or dedicated receiving circuit on the user equipment.
  • the application receiving the verification information on the user equipment may be the same application as the application transmitting the identification information on the user equipment, although the two may be different.
  • the user equipment may output the verification information for acquisition by the first device.
  • the user equipment may display the verification information to be acquired by the first device scan.
  • the user may manually input the verification information displayed on the user device to the first device.
  • the user device can invoke a single application implemented on the user device, such as a dedicated APP or a third party APP, or a specific circuit to transmit the authentication information. Give the first device without displaying it.
  • a single application implemented on the user device such as a dedicated APP or a third party APP, or a specific circuit to transmit the authentication information.
  • the acquisition and transmission of the identification information at the user device and the acquisition and transmission of the verification information can be implemented by calling a public application or a common circuit. It can also be implemented by separate programs or circuits.
  • the authentication information input by the user may be received by an input device of the first device (eg, may be a keyboard, a touch screen, a button, etc.).
  • an input device of the first device eg, may be a keyboard, a touch screen, a button, etc.
  • the verification information can be manually entered by the user into the first device.
  • the verification information may be obtained from the user equipment by an acquisition device (eg, may be a scanner or the like) of the first device.
  • an acquisition device eg, may be a scanner or the like
  • the authentication information transmitted by the user device can be received by the acquiring device of the first device (eg, a receiving module in the communication module, etc.).
  • the first device is verified
  • the first device After receiving the verification information output by the user equipment, the first device will verify it. According to an embodiment, the first device may verify the received verification information by using the second verification information corresponding to the identification information. For convenience of description, the received verification information is hereinafter referred to as first verification information.
  • the first device generates second verification information according to a preset algorithm, wherein The algorithm for generating the verification information is unique to each of the first devices.
  • the second device generates the first verification information by using the same or corresponding algorithm, and the algorithm is only loaded onto the second device.
  • the form and generation of the verification information may also be different accordingly.
  • the first device may adopt a specific generation algorithm to package/encrypt the identity information of the first device, the information related to the usage status of the first device, and the verification code into a specific form of information, such as two. Dimensional code, etc., as identification information.
  • the verification code can be encrypted by the first device using a specific encryption algorithm.
  • the second verification information generated by the first device may be the verification code.
  • the identification information can be dynamic.
  • the algorithm for generating the verification code, the packing/encryption algorithm may be some commonly used algorithms, and thus will not be described in detail.
  • the second device may first separate the identity identification information of the first device and the information about the usage status of the first device from the received identification information by using a decapsulation/decryption algorithm. And the encrypted verification code, and then the decryption algorithm corresponding to the first device is invoked to decrypt the encrypted verification code, so that the decrypted verification code is used as the first verification information to be provided to the user equipment.
  • the second device may also encrypt/package the first verification information by using a predetermined encryption algorithm, so that the verification information is more safely transmitted back to the first device.
  • the verification code may remain unchanged during the verification process until the verification succeeds or after a predetermined number of verifications; or may be a dynamically generated verification code that changes once every certain time.
  • the second device may also directly invoke an algorithm corresponding to the first device to generate a verification code for verification by the first device.
  • the first device may generate a specific form of information, such as a two-dimensional code or the like, by using a preset generation algorithm according to the identity identification information of the first device and information related to the usage status of the first device, As identification information.
  • the first device may generate a verification code as the verification information according to the information related to the usage status of the first device by using a specific algorithm, or encrypt the information related to the usage status of the first device as the verification information by using a specific encryption algorithm. .
  • the second device may first separate the identity identification information of the first device and the information related to the usage status of the first device from the identification information, and then invoke the corresponding device.
  • the algorithm generates a verification code as the verification information as the verification information to provide to the user equipment according to the information related to the usage status of the first device, or decrypts the information related to the usage status of the first device to provide the verification information to the user equipment.
  • both the identification information and the verification information are generated based on information related to the usage status of the first device.
  • both effective information transmission and dynamic verification can be realized at the same time, so that the amount of information transmitted can be relatively small, but still provide sufficient information, and security can be Guaranteed.
  • the first and second verification information are typically in the same form, such as a two-dimensional code or a combination of numbers or letters, so the verification by the first device typically compares whether the two are consistent.
  • other known methods can also be used for verification. If the verification is successful, it indicates that the first device can know that the second device authorizes or agrees to the user's use of the first device. If the verification is unsuccessful, it indicates that the first device still cannot know whether the second device authorizes or agrees to the user's use of the first device.
  • the second verification information can be generated at any time prior to verification.
  • the second verification information may be generated by the first device while generating the identification information and pre-cached, or may be generated based on the pre-cached identification information when the first device receives the first verification information. Since the first device and the second device theoretically calculate the same identification information using the same algorithm, the first verification information and the second verification information are theoretically identical. Therefore, if the two are consistent, it means that the second verification information is obtained from the correct second device based on the correct identification information, so the first device considers the verification successful and provides the service to the user equipment. It should be understood that the agreement referred to herein is not exactly the same, but rather that the difference between the two can be considered to be the same as long as it is within a certain redundancy error range.
  • the first device considers that the verification is unsuccessful, thereby repeating the above process until The verification is successful.
  • the verification information is dynamically changed at intervals, considering the delay that may occur during the verification process, there may be a situation in which the verification information of the first device has changed when the verification information of the second device is received. , which causes the two to fail to match.
  • the first device side may save both the old local authentication information and the new local authentication information at a certain time after the change time interval, for example, 10 seconds, and only receive the first time in this time. If the verification information of the two devices matches one of the two, the verification can still be considered successful.
  • the first device no longer generates identification information until the user of the user device stops using the first device.
  • the operating information of the user equipment may be recorded in the first device, and The operation information of the user equipment is reported to the server.
  • the communication is not related to the verification work, so the workload and performance requirements are not high, and the cost can be reduced to some extent.
  • FIG. 2 shows a flow chart of a method for a first device in accordance with the present disclosure.
  • step S201 identification information is generated.
  • step S202 the identification information is outputted for the user equipment to acquire the identification information.
  • step S203 the first verification information is received from the user equipment or the user.
  • step S204 the received first verification information is verified by using the second verification information corresponding to the identification information.
  • the steps S201, S202, S203 and S204 can be implemented in a manner similar to S101, S102, S110 and S111 described above, and will not be described in detail herein.
  • Figure 3 shows a schematic block diagram of a first device.
  • the various units shown in FIG. 3 may implement the method steps described above with respect to FIG. 2 and can be implemented in various manners, such as in hardware, firmware, software modules, and the like.
  • the units may be implemented integrally in any manner, such as by a single circuit or device, or may be implemented separately.
  • the first device 300 includes a generating unit 301 for generating identification information, an output unit 302 for outputting the identification information for the user device, a receiving unit 303 for receiving the first verification information, and The second verification information corresponding to the identification information, and the verification unit 304 that verifies the received first verification information.
  • the generating unit and the verifying unit may be circuits in the first device, and may include at least one of an arithmetic circuit, a comparison circuit, an addition circuit, a subtraction circuit, an encryption circuit, a decryption circuit, and the like, for example, Implemented on printed circuit boards, FPGAs, ASICs, etc.
  • the generating unit and the verifying unit may be implemented by a single component in the first device, such as an MCU, CPU, etc., or separately.
  • the output unit may include a display unit that displays the identification information, such as a liquid crystal display or the like.
  • the receiving unit may comprise means for receiving a user manually inputting the verification information, For example, a keyboard, a touch screen displaying a virtual keyboard, and the like.
  • the receiving unit may comprise means for scanning authentication information provided by the user equipment, such as a scanner, camera or the like that scans the verification information displayed by the user equipment.
  • the receiving unit may correspond to a receiving circuit in the communication module.
  • the device 300 may further comprise means for generating second verification information, which may be implemented in a similar manner to the generation unit described above.
  • the unit may be included in the generating unit or the verifying unit, or implemented separately.
  • FIG. 4 shows a flow chart of a method for a user equipment in accordance with an embodiment of the present disclosure.
  • the first device and the second device may indicate the same meanings as described above, and will not be described in detail herein.
  • step S401 the identification information output by the first device is acquired, and the identification information is generated based on information related to the usage status of the first device.
  • step S402 the identification information is transmitted to the second device.
  • step S403 receiving verification information generated by the identification information from the second device
  • step S404 the verification information is outputted for verification by the first device.
  • Figure 5 shows a schematic block diagram of a user equipment.
  • the various units shown in FIG. 5 may implement the method steps described above with respect to FIG. 4 and can be implemented in various manners, such as hardware, firmware, software modules, and the like.
  • the units may be implemented integrally, for example, by a single circuit or device, or may be implemented separately.
  • the user device may have an acquisition unit 501 for acquiring identification information from the first device, such as a scanning device or the like for scanning the display of the first device, and a device for the user to input the identification information of the first unit into the user device.
  • the acquisition unit may correspond to a receiving circuit in the communication module.
  • the user equipment 500 may further include a transmitting unit 502 for transmitting the identification information generated by the first device to the second device, and a receiving unit 503 for receiving the verification information generated from the second device according to the identification information. .
  • both the transmitting unit and the receiving unit can be implemented by running stored and installed applications (such as mobile phone APPs) on the processor of the user device, or by related circuitry on the user device.
  • stored and installed applications such as mobile phone APPs
  • the user equipment may also have an output unit 501 that outputs authentication information, such as a display unit, or a transmission circuit that communicates authentication information to the communication module of the first device if the user device can communicate with the first device.
  • an output unit 501 that outputs authentication information, such as a display unit, or a transmission circuit that communicates authentication information to the communication module of the first device if the user device can communicate with the first device.
  • FIG. 6 shows a flow chart of a method for a second device in accordance with the present disclosure.
  • the first device and the user device may indicate the same meanings as described above, and will not be described in detail herein.
  • step S601 identification information from the user equipment is received, the identification information being based on information related to the usage status of the first device.
  • step S602 verification information is generated based on the identification information.
  • step S6503 the verification information is transmitted to the user equipment.
  • steps S601, S602, and S603 can be implemented in a manner similar to S105, S106, and S107 described above, and will not be described in detail herein.
  • Fig. 7 shows a schematic block diagram of a second device.
  • the various units shown in Figure 7 can implement the method steps described above with respect to Figure 6, and can be implemented in various ways, such as hardware, firmware, software modules, and the like.
  • the units may be implemented integrally, for example, by a single circuit or device, or may be implemented separately.
  • the second device 700 may include a receiving unit 701 for receiving identification information from the user device, the identification information including information related to usage status of the first device, and a generating unit 702 for generating verification information according to the identification information. And a transmitting unit 703 for transmitting the verification information to the user equipment.
  • the generating unit can be implemented as the generating unit in the aforementioned first device. According to an embodiment, both the receiving unit and the transmitting unit are achievable by a communication transceiver circuit in the second device. According to an embodiment, the generating unit may be implemented by an application installed on the second device or by a related circuit on the second device.
  • the first device itself does not require any direct communication with the second device (eg, a server), particularly with respect to direct communication of identification information and authentication information. Therefore, even if the network communication between the device itself and the server is not good, the identification information and the verification information can be successfully transmitted between the device and the server through the user device, and the verification of the dynamic code is not affected. In this way, the networking requirements of the device are greatly reduced, and the device may not even need it. Setting the network communication module will reduce the manufacturing cost of the device to some extent.
  • the generated identification information includes information related to the usage status of the device providing the service, so that the server can also learn the verification while implementing the verification through a single information transmission process.
  • the use of the device eliminates the need to communicate directly with the device, thereby simplifying the communication process by combining the verification process with the information transfer.
  • the foregoing workflow mainly relates to a verification operation process of starting a service phase.
  • the first device may generate the identification information again, and the user device transmits the identification information to the second device, so that the second device can understand that the device is used.
  • the status information of the first device, the usage record of the user device, and the like without directly communicating with the first device.
  • the information provided in the above operational flow can also be used to charge for the service.
  • the user again uploads the identification information of the first device to the second device at this time.
  • the second device can use the difference between the two uploads to complete the cost accounting.
  • This method can be called a post-paid method.
  • the second device may perform charging based on the time difference between the two accesses.
  • the identification information generated by the first device is generated based on some basic information, and the basic information may include some information associated with the fee settlement, the basic transmission in two transmissions may be utilized. The difference between the information is used for billing.
  • the second device may reserve a predetermined time after the user equipment accesses the second device in consideration of a possible authentication failure or the like, during which no charge is made. If the new verification code is no longer obtained from the user equipment after the predetermined time is exceeded, the user equipment is considered to have successfully obtained the service of the first device, and the previously stored access time/state information of the first device is used as the charging basis. If the user equipment retransmits the identification information to the second device within the predetermined time, the second device updates the previously stored access time/status information of the first device to the current access time/status information of the first device. And repeat the above operation.
  • This predetermined time may be determined in consideration of the time when the server transmits the verification code to the user equipment, the user equipment inputs the verification code into the first device, and the first device performs the verification operation, and the like, and is generally longer than the sum of these times.
  • a so-called prepaid method can be employed.
  • users can start at the service
  • the service is prepaid in advance to purchase a predetermined amount/scheduled length of time, and after the start of the service, when the predetermined amount/scheduled time is reached, the first device no longer provides the service, and the service ends.
  • the first device is not required to generate the identification information again and the identification information is transmitted through the user device.
  • the user subscription service information corresponding to the user prepaid may be communicated back to the first device along with the verification information generated by the second device, and the first device may provide the service according to the service information. If a failure occurs during the verification process that requires re-authentication, the user's subscription information is also resent to the first device during the re-authentication process.
  • the user may receive a prepaid prompt of the second device and pay for the purchase of a predetermined amount/predetermined length of time when the identification information is transmitted to the second device.
  • prepaid can also be done at other times before the service begins.
  • the novel dynamic code verification scheme described in the present disclosure does not need to rely on accurate time for generating a verification code in the implementation process, so that even after the device is completely powered off, the implementation of the verification scheme is not affected.
  • the device does not directly communicate with the second device, but relies on the user device of the user to complete the process of communicating with the second device, so the device itself does not need to have a network communication module. There are certain advantages in equipment manufacturing costs.
  • identification information by the generation and transmission of identification information, several convenient functions can be simultaneously realized by a single communication.
  • the server can provide the corresponding verification code for the first device, the server can also conveniently know the state information of the first device without directly communicating with the device and, for example.
  • the status information is used to perform server-side operations.
  • the user's operation is not complicated, and the security and reliability of the communication are greatly improved.
  • the verification management component in the charging device may correspond to the aforementioned first device
  • the backend server corresponds to the aforementioned second device.
  • the more common charging devices on the market include relatively fixed charging devices, such as charging piles, desktop charging devices, and the like, and charging devices for self-renting mobile power.
  • the entire service process of these charging devices usually rely on communication between the charging device and the backend server.
  • the back-end server sends an instruction to the charging device to confirm the charging start.
  • the device sends an end command to the server, and the server settles the fee with the user according to the usage time or the related power consumption.
  • the service process is completed.
  • the charging device Because the entire service process relies on communication between the charging device and the server, the charging device often needs to install a network communication module to establish network communication with the server. This makes it difficult to reduce the production difficulty and manufacturing cost of the charging device, and there may be a certain safety risk.
  • the present example proposes an improved charging device that utilizes a dynamic code to control the charging process in which the network communication module is removed, so that the production difficulty and manufacturing cost of the device are greatly reduced. Moreover, in the case that the charging device and the server do not need to communicate directly, the charging process can still be guaranteed, and the server can also timely and accurately understand the dynamic status information of the charging device.
  • the charging device may include components such as a control component, an output component, an input component, a charging service component, and the like, wherein the control component is interconnected with the output component, the input component, the charging service component, and the like, respectively.
  • the control component is interconnected with the output component, the input component, the charging service component, and the like, respectively.
  • other well-known components such as a power supply are not described in detail.
  • the foregoing first device may correspond at least to a control component, an input component and an output component, which are collectively referred to as a verification management component.
  • control components can be implemented in a variety of ways, such as conventional processors programmed to perform the functions described above, integral components including discrete devices for implementing the above-described functions, decentralized components, and the like.
  • the control component can be implemented as a processor such as a CPU, a microprocessor such as an MCU, a printed circuit board, or the like.
  • the control component can be implemented as a main control PCB board.
  • the control component dynamically generates an identification code, such as a two-dimensional code, the identification information described above, upon user request or periodically and automatically based on some basic information of the charging device.
  • the basic information of the charging device includes, but is not limited to, the number of the device, the remaining power of the device, the running status of the device, and the duration of the previous user.
  • the control component may also have verification information generated from the input component for verification and the charging device itself Verification function to verify that the information is consistent. These verification information can be generated according to a specific algorithm as described above.
  • the generation of the identification information and the verification information in the control component may be implemented by a specific circuit, for example, may include at least one of an arithmetic circuit, a comparison circuit, an addition circuit, a subtraction circuit, an encryption circuit, a decryption circuit, and the like.
  • a specific circuit for example, may include at least one of an arithmetic circuit, a comparison circuit, an addition circuit, a subtraction circuit, an encryption circuit, a decryption circuit, and the like.
  • it can be implemented by an integrated circuit, an FPGA, an ASIC, or the like that implements a specific algorithm function.
  • the verification function may also be implemented by a specific circuit, such as an integrated circuit, an FPGA, an ASIC, or the like that implements a specific function, or may be implemented by a comparison circuit, a comparator, or the like.
  • the output component such as the display component
  • the identification code generated by the control component is displayed for the user to scan for input or manually input to the user device, such as the user's mobile handset.
  • the display components can also take different forms.
  • the identification code is a two-dimensional code, so the display component configured by the charging device is a color display.
  • the display component can also be a digital display.
  • the output component can also be in other forms as long as the identification code or working condition can be provided to the user.
  • the output member can be a display member such as a display screen.
  • the input component is configured to receive authentication information from the background server input by the user/user device.
  • the control unit is electrically connected to the input unit and receives the verification code information input through the input unit.
  • the form of the input component can also be varied.
  • the input component used by the device is a tact switch, as shown in Figure 10, the different switches correspond to different numbers, using different numbers to form different verification codes.
  • the input component can also include keys, characters, and the like, as shown in FIG.
  • the verification code may be in the form of a two-dimensional code, a barcode, a pattern code, etc.
  • the input component may be a scanner, and the user only needs to provide the verification code for the input component to scan, and the verification code input is completed.
  • the input component can also be in other forms as long as the verification code can be provided to the charging device.
  • the charging service component is a component that the device provides a charging service to the user.
  • the operating state of the component is controlled by the control component.
  • the control component confirms that the verification code input by the user is valid, the control component issues an instruction to the charging service component, and the charging service component starts to provide the charging service.
  • the control unit issues an instruction to the charging service unit to stop providing the charging service.
  • the charging service component is at least one charging interface/charging line, and the user uses the data cable to connect the charging interface to the mobile device.
  • the control component instructs the charging service component to start working, that is, instructing the charging interface to power up and begin charging the mobile device.
  • the control unit commands charging service
  • the command charging interface is powered off and the charging of the mobile device is stopped.
  • the identification code generated by the charging device mainly contains the status information of the charging device itself.
  • the charging service component can also be in the form of a charging module, such as a receiving device that houses at least one mobile power source.
  • the control component controls the charging service component to start working, that is, controls the charging module to send the mobile power for the user to use.
  • the control unit controls the charging module to absorb the mobile power into the charging module to recharge the mobile power.
  • the identification code generated by the charging device includes status information related to the used mobile power source in addition to the status information of the charging device.
  • the control component may control the charging service component to provide or end the charging service by the driving component.
  • the driving component may electrify or de-energize the charging interface according to control of the control component, such as a switching component; in the case where the charging service component is a mobile power source, the driving component may be Control of the control unit to handle the mobile power source, such as a receiving device that houses a mobile power source or a drive device for the receiving device.
  • the drive member may be integral with the control member or may be integral with the charging service member.
  • the charging device may also include a fuselage component, and other functional components are mounted within the fuselage component, the fuselage component protecting each functional component.
  • the fuselage is the support component of the whole machine equipment, and other functional components are installed on the fuselage.
  • the fuselage components may include a casing (eg, a left casing and a right casing), a base (left and right base), a light panel, etc., and a built-in battery core that supplies power to the charging service component may be housed in the machine.
  • the body is injection molded and the material is ABS engineering plastic.
  • other materials and other manufacturing processes can also be used to manufacture the fuselage, for example, using a sheet metal material to manufacture a metal body by a process such as bending.
  • the charging device may also include other components for driving, indicating, decorating, aesthetically pleasing, etc., which will not be described in detail.
  • the control component of the charging device dynamically generates an identification code according to the request or timing according to the information of the device, and calls a preset algorithm to calculate the identification code, obtains a verification code (verification code A), and outputs an identification code, for example, the generated The identification code is projected onto the display unit.
  • the above-described algorithm for generating the identification code and for generating the verification code is preloaded into the charging device, for example during manufacturing, wherein the algorithm for generating the verification code is unique to each charging device. The corresponding algorithm is only loaded into the backend server.
  • the user can enter the identification code and upload it to the server through a dedicated APP on the user device or other third party APP.
  • the user can manually input the identification information, or the identification information can be scanned by the camera of the user device and the information can be uploaded.
  • the backend server interprets the identification code and obtains the information contained in the two-dimensional identification code.
  • the backend server calls the corresponding algorithm according to the device code in the two-dimensional identification code to calculate the two-dimensional identification code, obtains the verification code (the verification code B), and sends the verification code B back to the user equipment.
  • the background server can record other information contained in the identifier in the server. For example, the server may know the identification information and the power amount information of the charging device included in the identification information, and store the two in association as a usage record of the charging device.
  • the user inputs the verification code B to the charging device through the input unit of the charging device.
  • the charging device checks whether the verification code B is consistent with the verification code A calculated by the device itself, and if it is consistent, it is considered that the charging service component is controlled to start the charging service by verification. If the verification results of the two verification codes are inconsistent, the verification cannot be passed, and the above process needs to be repeated to continue the verification until the verification is passed.
  • the verification code A may not be generated when the charging device identification code is generated, but may be generated based on the previously buffered identification code after the verification code B is input.
  • FIG. 11 illustrates a verification charging flow in accordance with one embodiment of the present disclosure, wherein the incoming call treasure corresponds to the charging device described in the present disclosure.
  • the caller dynamically generates a two-dimensional code according to the power, the password factor, the abnormal code, the battery capacity, the number of cycles, the last used time, and the like (S1101), and displays the two-dimensional code.
  • the user scans the two-dimensional code (S1102) with the mobile phone, so that the two-dimensional code can be transmitted to the user's mobile phone through encrypted data transmission (ciphertext) (S1103), and then the user transmits the ciphertext to the server through the mobile phone (S1104). ).
  • the server After receiving the ciphertext, the server can calculate the password based on the ciphertext (S1105), and transmit the calculated password back to the user side (S1106). After receiving the password, the user enters a password in the incoming keypad (S1107).
  • the caller uses the dynamically generated two-dimensional code to verify the entered password (S1108), and in the case where the verification passes, the power line can output a current, so that the user can charge (S1109).
  • charging of the user device can also be billed through a similar workflow as described above.
  • the post-paid mode described above may be employed, wherein, at the end of charging, the user again obtains the identification code of the charging device and provides it to the server, and the server passes the letter of the identification code that is input twice.
  • the interest is compared to account for the user's usage fee. For example, when the user equipment is disconnected from the charging interface, or when the user returns the mobile power to the charging module, the charging device considers that the charging service is over and generates an identification code again.
  • the server can also inform the user of the cost of accounting, and provide other expressions, such as thank you for using, welcome to use next time.
  • the server can also provide other expressions first, and then calculate and provide fees later.
  • the server may request the user equipment to provide the identification information, and the server does not start accounting. cost.
  • the prepaid mode described above may be employed, for example, the user may prepay to purchase a predetermined amount of charging time before charging starts, and after verification, the control unit issues an instruction to the charging service unit, so that When the charging interface is powered, the user can connect the charging device and the mobile device through the charging cable to start charging the mobile device. While the charging service component starts to provide the charging service, the control component starts timing. When the preset time is reached, the control component controls the charging service component to stop supplying power, and the charging service is stopped.
  • a charging service component as a charging interface can adopt a post-paid and pre-paid mode
  • a charging service component as a mobile power source generally adopts a post-paid mode
  • the charging device of the present disclosure can successfully complete the charging of the user equipment by relying on the dynamic code in the whole operation, and the charging device does not need to directly communicate with the server in the process, so that the communication module in the charging device can be omitted. , thereby greatly simplifying the manufacture of the charging device and reducing the cost of the charging device.
  • the charging device can incorporate a variety of basic information into the identification code.
  • the basic information of the device is simultaneously transmitted to the back-end server, and the back-end server performs information according to the information uploaded by the two-dimensional code.
  • Cost accounting and equipment status update, maintenance personnel can view the running status of each device through the server background, perform targeted device maintenance, and the server does not need to communicate directly with the charging device.
  • the identification code can be dynamically generated, changing at regular intervals, and its security and reliability are also significantly higher than the fixed identification code.
  • the verification management module on the shared vehicle capable of generating information and verifying information may correspond to the aforementioned first device, and the module may have a display Screen, and can know the relevant state information of the shared vehicle, for example, fault information of the vehicle, mileage information of the vehicle, location information of the vehicle, etc., and the back-end server corresponds to the aforementioned second device.
  • the implementation of the technical solution of the present application in the shared vehicle will be described below by taking the mileage information of the vehicle as an example.
  • the first device of the shared vehicle is capable of generating an identification barcode or a two-dimensional code based on the bicycle code and the travel scale of the information travel calculation table, the identification code changing once every interval.
  • the mobile phone APP scans the barcode and uploads the identification code to the server.
  • the server calculates the verification code according to the barcode using a preset algorithm, and feeds the verification code back to the client APP.
  • the user inputs the verification code into the shared vehicle, and the CPU checks the verification code input by the user with the verification code calculated by the CPU, and automatically cancels the verification result for the user to use.
  • the barcode is scanned again by the APP, and the barcode is uploaded to the server, and the server calculates the corresponding rental fee according to the time interval of the two barcode uploads and the travel information of the travel calculation table included in the barcode. And collect the rent.
  • the GPS module can also be installed on the shared vehicle, and the GPS positioning information is also used as a basic information.
  • the identification code also includes the GPS positioning information, and the GPS information is uploaded to the user when the user uploads the identification code.
  • the server makes a record.
  • the security access device may correspond to the foregoing first device, the device may have a display screen, and the identity information of the user who wishes to use the access device may be known, and the back server corresponds to the foregoing second device.
  • the access control device In operation, when the user wishes to use the full access control, the access control device requires the user to input user identity information, such as the user inputting the user ID number, barcode, etc. or scanning the camera's retina, fingerprint, facial information, etc. by the access device's camera. .
  • the access control device is capable of generating an identification barcode or a two-dimensional code according to the code of the access control device and the above-mentioned user identity information, the identification code is changed once every interval, and displayed on the display component of the access control device.
  • the user scans the barcode with the mobile phone APP and uploads the identification code to the server.
  • the server calculates the verification code according to the barcode using a preset algorithm, and feeds the verification code back to the client APP.
  • the user inputs the verification code into the access control device, and the CPU checks the verification code input by the user with the verification code calculated by the CPU, and automatically unlocks the verification result for the user to enter and exit.
  • the methods and apparatus of the present disclosure may be implemented in a number of ways.
  • the methods and apparatus of the present disclosure may be implemented in software, hardware, firmware or any combination of software, hardware, firmware.
  • the above-described sequence of steps for the method is for illustrative purposes only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless otherwise specifically stated.
  • each of the above units may be implemented as a separate physical entity, or may be implemented by a single entity (eg, a processor (CPU or DSP, etc.), an integrated circuit, etc.).
  • the processing circuit may refer to various implementations of digital circuitry, analog circuitry, or mixed signal (combination of analog and digital) circuitry that perform functions in a computing system.
  • Processing circuitry may include, for example, circuitry such as an integrated circuit (IC), an application specific integrated circuit (ASIC), a portion or circuit of a separate processor core, an entire processor core, a separate processor, such as a field programmable gate array (FPGA) Programmable hardware device, and/or system including multiple processors.
  • IC integrated circuit
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • FIG. 12 is a block diagram showing an example structure of a device that can be employed in an embodiment of the present disclosure.
  • the central processing unit (CPU) 1801 functions as a data processing unit that performs various types of processing based on programs stored on a read only memory (ROM) 1802 or a storage unit 1808. For example, the CPU 1801 performs operations based on the foregoing.
  • a random access memory (RAM) 1803 stores programs, data, and the like executed by the CPU 1801.
  • the CPU 1801, the ROM 1802, and the RAM 1803 are connected to each other via a bus 1804.
  • the CPU 1801 is connected to the input and output interface 1805 via a bus 1804, and an input unit 1806 composed of various switches, a keyboard, a mouse, a microphone, and the like, and an output unit 1807 composed of a display, a speaker, and the like are connected to the input and output interface 1805.
  • the CPU 1801 executes various types of processing in response to an instruction input from the input unit 1806, and outputs the processing result to the output unit 1807.
  • the storage unit 1808 connected to the input and output interface 1805 is constituted by, for example, a hard disk, and stores thereon programs and various types of data executed by the CPU 1801.
  • the communication unit 1809 communicates with an external device via a network such as the Internet or a local area network. It should be understood that in the hardware configuration of the first device, the communication unit may be omitted.
  • the drive 1810 connected to the input and output interface 1805 drives a removable medium 1811 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory (for example, a memory card), and acquires each of the contents such as content and key information recorded thereon.
  • a removable medium 1811 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory (for example, a memory card), and acquires each of the contents such as content and key information recorded thereon.
  • Class data for example, a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory (for example, a memory card).
  • the present disclosure may also be embodied as programs recorded in a storage medium, the programs including machine readable instructions for implementing a method in accordance with the present disclosure. Accordingly, the present disclosure also covers a storage medium storing a program for executing a method according to the present disclosure.
  • the storage medium may be a non-volatile storage medium, and examples thereof may include a magnetic disk (including a floppy disk (registered trademark)), an optical disk (including a compact disk read only memory (CD-ROM) and a digital versatile disk (DVD)), and a magneto-optical disk (including Mini disk (MD) (registered trademark), semiconductor memory, memory card, memory stick, etc.
  • machine-executable instructions in the storage medium and the program product according to the embodiments of the present disclosure may also be configured to perform the method corresponding to the apparatus embodiment described above, and thus the content not described in detail herein may refer to the previous corresponding position. The description is not repeated here.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种验证方法和设备，所述验证方法包括第一设备生成识别信息，所述识别信息基于与第一设备的使用状况相关的信息；用户设备从第一设备获取所述识别信息，并将所述识别信息传送至第二设备；所述第二设备利用接收到的识别信息生成第一验证信息，并将所述第一验证信息发送给所述用户设备；所述用户设备输出所述第一验证信息；以及所述第一设备基于与所生成的识别信息对应的第二验证信息，对所述第一验证信息进行验证。

Description

验证方法及设备 技术领域
本公开涉及一种验证方法及设备。特别地，本公开涉及针对提供服务进行验证的验证方法和设备。
背景技术
服务验证应用于非常广阔的领域。目前常用的用于验证的码包括静态码和动态码。
静态码是相对固定的，因此容易遭到破解。动态码是一种根据专门算法所产生的伪随机码，其通常是每隔一段时间而动态变化。因为动态码的安全性较高，被广泛应用于网银、网游、电信等诸多领域。目前动态码的形式主要有手机密码、硬件令牌、手机令牌等多种形式。
在常规动态码应用中，动态码的实现主要是依赖于时间而进行变化，因此提出了一种所谓的时间同步验证的动态码验证方式。其中，设备和后台服务器内部被预先写入相同的算法，设备侧根据该算法生成依据设备侧的时间变化的动态码，将所产生动态码输入服务器。在接收到所输入的动态码之后，服务器也根据该相同的算法产生依据服务器侧时间变化的动态码。服务器将这两者进行比较。如果两者相同，则代表验证成功，并且服务器告知设备验证成功。
另外一种动态码的验证方式是由服务器将动态码发送至用户手机，再由用户将动态码输入设备，设备将输入的动态码提交到服务器进行验证，如果核对成功，则代表验证成功。并且服务器告知设备验证成功，通知设备提供服务。
发明内容
本公开被提出以旨在提供一种改进的验证方法和设备。
根据一个方面，提供了一种用于第一设备的方法，包括：基于与所述第一设备的使用状况相关的信息生成识别信息；输出所述识别信息，以供用户设备获取所述识别信息；从所述用户设备或用户接收第一验证信息；以及利用与所述识别信息对应的第二验证信息，对所接收到的第一验证信息进行验证。
根据另一个方面，提供了一种用于用户设备的方法，包括获取第一设备输出的基 于与第一设备的使用状况相关的信息生成的识别信息；将所述识别信息传送至第二设备；接收来自所述第二设备的利用所述识别信息生成的验证信息；以及输出所述验证信息，以供所述第一设备进行验证。
根据另一个方面，提供了一种用于第二设备的方法，包括：接收来自用户设备的识别信息，所述识别信息是基于与第一设备的使用状况相关的信息的；根据所述识别信息生成验证信息；以及向用户设备发送所述验证信息。
根据另一个方面，提供了一种方法，包括：第一设备生成识别信息，所述识别信息包括与第一设备的使用状况相关的信息；用户设备从第一设备获取所述识别信息，并将所述识别信息传送至第二设备；所述第二设备利用接收到的识别信息生成第一验证信息，并将所述第一验证信息发送给所述用户设备；所述用户设备输出所述第一验证信息；以及所述第一设备基于与所生成的识别信息对应的第二验证信息，对所述第一验证信息进行验证。
根据另一个方面，提供了一种第一设备，包括：用于基于与所述第一设备的使用状况相关的信息生成识别信息的生成单元；用于输出所述识别信息，以供用户设备获取所述识别信息的输出单元；用于从所述用户设备或用户接收第一验证信息的接收单元；以及用于利用与所述识别信息对应的第二验证信息，对所接收到的第一验证信息进行验证的验证单元。
根据另一个方面，提供了一种用户设备，包括：用于获取第一设备输出的基于与第一设备的使用状况相关的信息生成的识别信息的获取单元；用于将所述识别信息传送至第二设备的传送单元；用于接收来自所述第二设备的利用所述识别信息生成的验证信息的接收单元，以及用于输出所述验证信息，以供所述第一设备进行验证的输出单元。
根据另一个方面，提供了一种第二设备，包括：用于接收来自用户设备的识别信息的接收单元，所述识别信息是基于与第一设备的使用状况相关的信息的；用于根据所述识别信息生成验证信息的生成单元；以及用于向用户设备发送所述验证信息的发送单元。
根据另一个方面，提供了一种设备，包括一个或多个处理器，以及一个或多个存储器，存储有指令，所述指令在由所述一个或多个处理器执行时使得所述设备实现在先所述的方法。
根据另一个方面，提供了一种非暂态存储设备，存储有指令，所述指令在由处理器执行时使得实现根据在前所述的方法。
通过以下参照附图对本公开的示例性实施例的详细描述，本公开的其它特征及其优点将会变得清楚。
附图说明
构成说明书的一部分的附图描述了本公开的实施例，并且连同说明书一起用于解释本公开的原理。
参照附图，根据下面的详细描述，可以更加清楚地理解本公开，其中：
图1为根据本公开的一个实施例的验证操作的示例性流程图。
图2为根据本公开的一个实施例的用于第一设备的示例性方法的流程图。
图3为根据本公开的一个实施例的第一设备的示例性框图。
图4为根据本公开的一个实施例的用于用户设备的示例性方法的流程图。
图5为根据本公开的一个实施例的用户设备的示例性框图。
图6为根据本公开的一个实施例的用于第二设备的示例性方法的流程图。
图7为根据本公开的一个实施例的第二设备的示例性框图。
图8为根据一个实施例的示例性的充电设备的概略图。
图9示出了根据一个实施例的示例性的充电设备的构造。
图10示出了根据一个实施例的示例性的充电设备的构造。
图11示出了根据一个实施例的示例性的充电设备的验证充电流程。
图12为在其中可以实施本公开的实施例的设备的示例结构的框图
具体实施方式
现在将参照附图来详细描述本公开的各种示例性实施例。应注意到：除非另外具体说明，否则在这些实施例中阐述的部件和步骤的相对布置、数字表达式和数值不限制本公开的范围。
同时，应当明白，为了便于描述，附图中所示出的各个部分的尺寸并不是按照实际的比例关系绘制的。
以下对至少一个示例性实施例的描述实际上仅仅是说明性的，决不作为对本公开 及其应用或使用的任何限制。
对于相关领域普通技术人员已知的技术、方法和设备可能不作详细讨论，但在适当情况下，所述技术、方法和设备应当被视为授权说明书的一部分。
在这里示出和讨论的所有示例中，任何具体值应被解释为仅仅是示例性的，而不是作为限制。因此，示例性实施例的其它示例可以具有不同的值。
应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步讨论。
本公开的发明人发现，目前的动态码验证的实现形式均存在一定的使用限制，在实际使用中会存在某些不足的地方。
例如在前文所述的时间同步验证方式中，动态码的生成和验证往往需要提供服务的设备与服务器之间保持正确的时间同步以使得两侧的动态码同步，一旦遇到设备电量不足或计时部件计时不准确，则会导致硬件的动态码与服务器的动态码不同步，从而导致验证失败。
此外，在常规的动态码应用中，设备与服务器端往往需要通过网络保持通信连接，从而服务器能够进行验证并且在验证成功时指令设备提供服务。假如设备与服务器之间出现通信问题，会妨碍验证的正常进行。
针对目前动态码实现中所存在的这些问题，本公开提出一种改进的验证方案，该方案能够成功地实现验证，而不依赖于设备与服务器的计时同步以及设备与服务器之间的通信。特别地，该技术方案尤其可以有利地应用于动态码验证。
以下将参照附图对本公开的实施例进行详细描述。
图1示例性地示出了本公开的一个实施例的验证操作流程的示例性流程图。
第一设备可对应提供服务的装置相关的设备，其可以根据具体应用而对应于不同的设备，例如共享车辆、共享充电装置、安保装置等等相关的设备。
用户设备可以为用户的移动终端设备，如智能手机、平板电脑等等，其还可以对应于其它类型的设备，只要其可以在第一设备和第二设备之间居间传递本公开中所描述的特定类型的识别信息和验证信息即可。
第二设备例如可以是后台服务器，但是第二设备也可以对应于各种其它设备，只要其可以从所接收的识别信息确定验证信息或者将验证信息发送给用户设备即可。
参照图1来概述根据本公开的实施例的验证操作流程如下。
首先，第一设备生成识别信息(S101)，并且输出识别信息以供用户设备获取(S102)。
然后，用户设备获取识别信息(S103)，并且将识别信息传送至第二设备(S104)。
第二设备接收识别信息(S105)，并且生成验证信息(S106)。然后，第二设备将验证信息传递至用户设备(S107)。
用户设备获取验证信息(S108)，并且输出验证信息以供第一设备获取(S109)。
第一设备接收验证信息(S110)，并且对于所接收的验证信息进行验证(S111)。根据一种实施方式，第一设备可以利用与所述识别信息对应的第二验证信息，对所接收到的验证信息进行验证。
由此可见，在本公开的实施例中，通过用户设备在第一设备和第二设备之间居间传递信息来实现验证，而第一和第二设备之间不会发生直接通信。
以下将具体阐述上述操作流程的细节。在说明书的描述中，相同或相似的表述将具有相似的含义，将不再重复说明。应指出，以下描述的验证操作流程中的每一过程的操作以及实施方式仅仅是示例性的，其还可以通过其它等同方式来实施。
识别信息的生成
识别信息可以由第一设备基于与所述第一设备的使用状况相关的信息来生成。所生成的识别信息的形式例如可以是二维码、条形码、图案码或者是数字、英文组合等。
根据一种实施方式，所述识别信息可例如根据预先设置在第一设备中的预设算法对与所述第一设备的使用状况相关的信息进行处理而被生成。根据一种实施方式，所述识别信息可包括与所述第一设备的使用状况相关的信息。与所述第一设备的使用状况相关的信息例如可以是设备本身的状态信息、使用该第一设备的用户设备/用户的相关信息中的至少一个。
根据一种实现，第一设备本身的状态信息可以包括第一设备可提供的服务的状况(例如，还能否提供服务、还能提供多少服务等)、故障/异常状况、先前使用状况(例如，时间、次数等)等等。例如，第一设备本身的状态信息可依赖于第一设备的类型而不同，诸如充电装置的电量信息、共享车辆的里程信息等等。
作为示例，依赖于第一设备的使用情境，例如在第一设备为需要认证身份的安保设备，诸如门禁设备等时，与所述第一设备的使用状况相关的信息还可以包括使用第 一设备的用户设备的标识信息、用户的相关身份识别信息，例如用户身份证件号码、条形码、视网膜、指纹、脸部信息等等。
根据一种实施方式，第一设备还可包含用于采集与所述第一设备的使用状况相关的信息的装置。例如，该装置可以包括检测第一设备的工作状态以获取信息的检测部件，其可以通过硬件、软件或者固件等等形式来实现。该部件可以包括用于扫描用户身份信息的扫描装置。
根据一种实施方式，在存在不止一台第一设备的情况下，该识别信息的生成例如还可以基于第一设备的身份标识信息(ID信息)。
根据一种实施方式，第一设备可以将第一设备的身份标识信息、与第一设备的使用状况相关的信息、以及验证码，打包/加密为特定形式的动态信息，诸如二维码等，以作为识别信息。例如，该验证码可以是根据例如随机码生成算法生成的随机码。当然验证码还可为其它形式，并且按本领域已知的其它算法来生成。该打包/加密可以通过本领域已知的数据打包/加密算法/电路来实现，这里将不再详细描述。
根据另一种实施方式，第一设备可以根据第一设备的身份标识信息和与第一设备的使用状况相关的信息来生成特定形式的信息，诸如二维码等，以作为识别信息。例如，该识别信息可以通过本领域已知的识别信息生成算法来生成，例如用于生成二维码/动态二维码的二维码生成算法，用于生成图案码/动态图案码的图案码生成算法等等。这里将不再详细描述。
根据一种实施方式，该识别信息可以是动态生成的，并且例如可以根据时间而动态变化、对于每一次生成都动态变化、或者根据与所述第一设备的使用状况相关的信息而动态变化。
根据一种实施方式，识别信息生成可以是由第一设备定期生成，显示在第一设备的显示屏幕上以供用户设备获取。或者，识别信息可以由第一设备响应于用户的请求而生成，例如用户通过第一设备上的物理或虚拟按键来请求服务，响应于此请求，第一设备可以生成识别信息。识别信息生成之后，可由第一设备显示以供用户设备获取。
根据一种实施方式，与所述第一设备的使用状况相关的信息可以被第一设备定期地采集，或者在用户请求生成识别信息时被采集。
根据一种实施方式，第一设备可以始终都生成识别信息，以供用户设备扫描并传送给第二设备，从而第二设备能够及时地了解第一设备的状态，并且第二设备也能够 将第一设备的状况及时告知用户，从而用户也可以方便地了解第一设备的状况。
根据一种实施方式，识别信息的生成还可以考虑所述与第一设备的使用状况相关的信息是否满足预定条件，如果在所述与第一设备的使用状况相关的信息不满足预定条件，则不生成识别信息。例如，该预定条件可以包括例如是否低于预先设定的设备能提供服务的最低阈值，如果低于该阈值则无法提供服务。例如，该预定条件可以包括用户身份信息是否通过认证。等等。例如，在不生成识别信息的情况下，第一设备可以输出提示信息，以便用户设备可以更加直观地了解第一设备的状态，而且用户还可以将此上报给服务器。
例如，在第一设备是提供服务的设备的情况下，如果第一设备的当前状态能够提供服务，则第一设备生成识别信息。如果第一设备的当前状态不能提供服务，则第一设备不生成识别信息，而是显示提示信息。
根据一种实施方式，识别信息的生成还可以依赖于用户设备/用户的身份标识信息。在第一设备是需要认证用户身份的安保设备时，如果用户身份被认证为是授权用户，则生成识别信息，相反，如果用户身份无法被识别或者是不被授权的用户，则第一设备也不会生成识别信息，而是产生提示信息以告知用户。
根据一种实施方式，如果用户设备与第一设备之间可以通信，则在用户/用户设备的身份得到认证之后，可以将识别信息直接告知用户设备，例如直接发送到用户设备上，而不再显示，从而进一步提高了安全性。
识别信息可以是每隔一段时间，例如1分钟，5分钟等，自动变化的，如果在该段时间内第一设备仍没有得到输入的验证信息或者验证不成功，识别信息也会改变，继而需要重新验证。这样可以进一步提高安全性。
识别信息的输出
在第一设备生成识别信息之后，第一设备将输出该识别信息以供用户设备来获取。
根据一种实施方式，第一设备可以通过其显示部件显示识别信息以供用户设备或者用户获取。当然，第一设备也可通过其他方式来将识别信息进行输出而提供给用户设备或者用户，例如通过介质打印、声音输出等方式传递给用户设备或用户而无需显示。如果第一设备与用户设备之间能够进行通信，则第一设备也可以通过通信方式将识别信息发送给用户设备。
用户设备关于识别信息的获取和传送
在第一设备输出识别信息之后，用户设备可以以各种方式来获取该识别信息，并通过用户设备与第二设备之间的通信将其传送至第二设备。
根据一种实施方式，用户设备例如可具有扫描仪、摄像头等装置，并且用户可以通过用户设备上的应用程序调用该装置扫描第一设备显示的识别信息(例如可以是二维码、条形码、图案码等)以获取该信息，并通过用户设备与第二设备之间的通信将该识别信息发送至第二设备。
根据一种实施方式，如果识别信息是数字、英文等组合，用户也可以手动输入该信息到用户设备中，并经由用户设备与第二设备的通信将该识别信息发送至第二设备。
根据一种实施方式，如果第一设备与用户设备之间能够进行通信，则用户设备也可以通过通信方式从第一设备接收识别信息。
根据一种实施方式，识别信息的获取和传送可通过调用在用户设备上实现的单个应用程序，诸如专用APP或者第三方APP，来进行，或者也可以通过分别调用不同的应用程序来进行。根据一种实施方式，这些操作也可以借助于用户设备上安装的特定电路来实现。
根据一种实施方式，用户设备在传递识别信息的同时，还可以同时传递用户设备的身份信息，以供第二设备进行认证。第二设备可以认证用户设备得到授权的情况下生成并发送验证信息，否则第二设备可以向用户设备发出提示信息，提示用户设备无法使用本设备，或者提示用户设备需要获得授权。
识别信息的接收
根据一种实施方式，第二设备可通过与用户设备的通信来接收从用户设备传送的识别信息。例如，第二设备可以通过与用户设备上的应用程序相对应的应用程序来接收识别信息，或者也可以通过第二设备上的通用或专用接收电路来接收该识别信息。
识别信息的接收还可以通过本领域已知的其它方式来实现，这里将不再详细描述。
第二设备的验证信息的生成
在接收到来自用户设备的识别信息之后，第二设备将根据该识别信息来生成验证信息。
根据一种实施方式，第二设备例如调用预先设定在第二设备中的算法对所接收到的识别信息进行处理而得到验证信息。所生成的验证信息的形式也可以是二维码、条形码、图案码或者是数字、英文组合等。
取决于识别信息的形式，验证信息的形式和生成方式也可以相应地不同。根据一种实施方式，第二设备中生成验证信息的方式与在第一设备中预先设定的用于确定与识别信息对应的验证信息的方式是相对应的，例如它们所采用的算法是相同的。稍后将结合验证的进行来对于此进行更具体地描述。
除了来自第一设备的识别信息之外，第一验证信息的生成还可以依赖于用户设备相关的信息。
根据一种实施方式，第二设备还可以根据用户设备对第一设备的使用情况来确定是否生成验证信息，例如，如果第二设备根据所述用户设备的身份标识信息确定用户设备已经在使用第一设备，则不再生成验证信息，并且向用户设备发送报告。这种情况尤其例如适合于每个用户设备只能使用一个第一设备的情况。
在另一种实施方式中，在一个用户设备可以关联多个第一设备的情况下，即使用户设备已经在使用第一设备，仍生成验证信息以提供给验证信息，只是此时所述第二设备将用户设备的身份标识信息与用户设备所使用的第一设备的身份标识信息相关联地进行记录，以供后续处理。
根据一种实施方式，第二设备还可以根据用户设备/用户的先前状态信息来确定是否生成验证信息。
例如，第二设备可以了解到用户设备目前是否还在使用了其它的第一设备、先前的信用评级状态、是否欠费等等，并由此可以根据用户设备的信息来确定是否允许用户使用第一设备，或者允许用户试用预定的时间。如果不允许用户使用，则不生成验证信息，并且将相关提示信息呈现给用户，例如无法使用，提示用户缴费后再来使用等等。
第二设备的验证信息的传送
在生成验证信息之后，第二设备将所生成的验证信息传送给用户设备。
根据一种实施方式，第二设备可通过与用户设备的通信来向用户设备传送验证信息。例如，第二设备可以通过与用户设备上的应用程序相对应的应用程序来传送验证信息，或者也可以通过第二设备上的通用或专用传送电路来传送该验证信息。
根据一种实施方式，第二设备生成第一验证信息并向用户设备发送第一验证信息，表明第二设备授权或同意用户对第一设备的使用。
第二设备进行的验证信息的传送还可以通过本领域已知的其它方式来实现，这里 将不再详细描述。
用户设备关于验证信息的接收和传送
用户设备可通过与第二设备的通信来接收从第二设备传送的验证信息。根据一种实施方式，用户设备可以例如，通过用户设备上的应用程序来接收验证信息，或者也可以通过用户设备上的通用或专用接收电路来接收该验证信息。
根据一种实施方式，用户设备上接收验证信息的应用程序可以与用户设备上传送识别信息的应用程序是同一应用程序，当然这两者也可不同。
在接收到验证信息之后，用户设备可以输出该验证信息以供第一设备获取。根据一种实施方式，用户设备可以显示该验证信息以被第一设备扫描获取。根据一种实施方式，用户可以将用户设备上显示的验证信息手动输入到第一设备。
根据一种实施方式，在用户设备可以与第一设备通信的情况下，用户设备可以调用在用户设备上实现的单个应用程序，诸如专用APP或者第三方APP，或者特定的电路来将验证信息传送给第一设备，而不显示。
根据一种实施方式，在用户设备可以与第一设备通信的情况下，用户设备处的识别信息的获取和传送以及验证信息的获取和传送可通过调用公共的应用程序或者公共的电路来实现，也可以通过分离的程序或者电路来实现。
第一设备的验证信息的接收
根据一种实施方式，可以通过所述第一设备的输入装置(例如可以是键盘、触摸屏、按钮等等)接收用户输入的验证信息。例如，在数字或字母组合码的情况下，验证信息可由用户手动输入第一设备。
在另一种实施方式中，可通过所述第一设备的获取装置(例如可以是扫描仪等等)从用户设备获取所述验证信息。
在另一种实施方式中，在第一设备可以与用户设备通信的情况下，可以通过第一设备的获取装置(例如，通信模块中的接收模块等)来接收用户设备传送的验证信息。
第一设备进行验证
在接收到用户设备输出的验证信息之后，第一设备将对其进行验证。根据一种实施方式，第一设备可以利用与所述识别信息对应的第二验证信息，对所接收到的验证信息进行验证。为了便于描述，以下将所接收到的验证信息称为第一验证信息。
根据一种实施方式，第一设备根据预先设定的算法来生成第二验证信息，其中用 于生成验证信息的算法是每个第一设备特有的。而第二设备采用与之相同或相对应的算法来生成第一验证信息，该算法仅仅被装载到第二设备上。
取决于识别信息的形式，验证信息的形式和生成方式也可以相应地不同。
根据一种实施方式，第一设备可以采用特定生成算法来将第一设备的身份标识信息、与第一设备的使用状况相关的信息、以及验证码，打包/加密为特定形式的信息，诸如二维码等，以作为识别信息。其中该验证码可由第一设备利用特定的加密算法来加密。在此情况下，第一设备所生成的第二验证信息可以为该验证码。例如，该识别信息可以是动态的。这里，生成验证码的算法、打包/加密算法可以是目前常用的一些算法，因此将不再详细描述。
与此对应的，在第二设备侧，第二设备可以首先通过解包/解密算法来从所接收的识别信息中分离出第一设备的身份标识信息、与第一设备的使用状况相关的信息、以及加密的验证码，然后调用与第一设备相对应的解密算法来对加密的验证码进行解密，从而将解密得到的验证码作为第一验证信息以提供给用户设备。当然，第二设备也可以采用预定的加密算法对该第一验证信息进行加密/打包，以便该验证信息更安全地传递回第一设备。
在此实施方式中，验证码可以在验证过程中是保持不变的，直到验证成功或者经过预定次的验证之后；或者也可以是动态生成的验证码，其每隔一定时间就变化一次，此时第二设备也可以直接调用与第一设备对应的算法来生成验证码，以供第一设备验证。
根据一种实施方式，第一设备可以通过利用预先设定的生成算法根据第一设备的身份标识信息和与第一设备的使用状况相关的信息来生成特定形式的信息，诸如二维码等，以作为识别信息。并且，第一设备可以采用特定的算法根据与第一设备的使用状况相关的信息来生成验证码作为验证信息，或者采用特定的加密算法将与第一设备的使用状况相关的信息加密作为验证信息。
与此对应的，在第二设备侧，第二设备可以首先来从识别信息中分离出第一设备的身份标识信息和与第一设备的使用状况相关的信息，然后调用与第一设备相对应的算法来根据该与第一设备的使用状况相关的信息生成验证码作为验证信息以提供给用户设备，或者将与第一设备的使用状况相关的信息解密以作为验证信息提供给用户设备。
在此情况下，识别信息和验证信息都是基于与第一设备的使用状况相关的信息生成的。这样，通过主要传递与第一设备的使用状况相关的信息，可以同时实现有效信息传递以及动态验证两者，从而传输的信息量可以相对较小，但是仍能够提供足够的信息，并且安全性可以得到保证。
例如，第一和第二验证信息通常为相同形式，诸如二维码或者数字或字母组合码，因此第一设备进行的验证通常是比较这两者是否一致。当然也可以采用其他已知的方式来进行验证。如果验证成功，则表明第一设备能够获知第二设备授权或同意用户对第一设备的使用。如果验证不成功，则表明第一设备仍无法获知第二设备授权或同意用户对第一设备的使用。
第二验证信息可以在验证之前的任何时刻生成。根据一种实施方式，第二验证信息可以由第一设备在生成识别信息的同时生成并且预先缓存，或者可在第一设备接收到第一验证信息时，基于预先缓存的识别信息来生成。由于理论上第一设备与第二设备都是使用相同的算法对相同的识别信息进行计算，因此第一验证信息和第二验证信息理论上是一致的。因此，如果两者一致，则意味着第二验证信息是从正确的第二设备基于正确的识别信息而获得的，因此第一设备认为验证成功，并且为用户设备提供服务。应理解，此处所提及的一致并非是完全相同，而是指两者之间的差异只要在一定的冗余误差范围内即可认为是相同。
相反，如果例如可能由于信息传递过程中的干扰、篡改或识别信息实际并未传递到第二设备等等导致两个验证信息并不一致，则第一设备认为验证不成功，从而重复上述过程，直到验证成功为止。
在验证信息是每隔一段时间动态变化的情况下，考虑到验证过程中可能出现的延迟，可能存在如下状况，在接收到第二设备的验证信息时，第一设备本地的验证信息已经发生变化，从而导致两者无法匹配。针对此情况，第一设备侧可以在该变化时间间隔之后的一定时间，例如10秒内，同时保存旧的本地验证信息和新的本地验证信息两者，并且在此时间内只要接收到的第二设备的验证信息与这两者之一匹配，仍可认为验证成功。
根据一种实施方式，如果验证成功，则在用户设备的用户停止使用所述第一设备之前，第一设备不再产生识别信息。
根据一种实施方式，还可包括将用户设备的操作信息记录在第一设备内，并且定 期地将用户设备的操作信息上报至服务器。在此情况下，尽管用户设备仍可能与服务器通信，但是这种通信是与验证工作无关的，因此工作负荷和性能要求并不高，也能一定程度上降低成本。
以下将参照附图来进一步阐述根据本公开的实施例的在第一设备、第二设备以及用户设备各处实行的方法以及各设备的实施方式。
图2示出了根据本公开的用于第一设备的方法的流程图。
在步骤S201中，生成识别信息。
在步骤S202中，输出所述识别信息，以供用户设备获取所述识别信息。
在步骤S203中，从所述用户设备或用户接收第一验证信息。
在步骤S204中，利用与所述识别信息对应的第二验证信息，对所接收到的第一验证信息进行验证。
该步骤S201，S202，S203和S204可以分别以与前文所述的S101，S102，S110和S111相似的方式来实现，这里将不再进行具体描述。
图3示出了第一设备的示意性框图。图3中所示的各个单元可以实现上述参照图2描述的方法步骤，并且能够以各种方式，例如以硬件、固件、软件模块等来实现。例如，这些单元可以以任何方式集成地实现，例如由单个电路或者装置来实现，或者可以单独地实现。
第一设备300包括用于生成识别信息的生成单元301；用于输出识别信息，以供用户设备获取的输出单元302；用于接收第一验证信息的接收单元303；以及用于利用与所述识别信息对应的第二验证信息，对所接收到的第一验证信息进行验证的验证单元304。
根据一种实施方式，该生成单元和验证单元可以是第一设备中的电路，可以包括运算电路、比较电路、加法电路、减法电路、加密电路、解密电路等等中的至少一种，例如通过印刷电路板、FPGA、ASIC等实现。
根据一种实施方式，该生成单元和验证单元可以由第一设备中的单个部件，例如MCU、CPU等来实现，或者单独地实现。
根据一种实施方式，该输出单元可以包括显示所述识别信息的显示单元，例如液晶显示屏等。
根据一种实施方式，该接收单元可以包括用于接收用户手动输入验证信息的装置， 例如键盘，显示虚拟键盘的触摸屏等等。
根据一种实施方式，该接收单元可以包括扫描用户设备提供的验证信息的装置，例如扫描用户设备显示的验证信息的扫描仪、摄像头等。
根据一种实施方式，在用户设备可以与第一设备通信的情况下，该接收单元可以对应于通信模块中的接收电路。
根据一种实施方式，该设备300还可以包括用于生成第二验证信息的单元，该单元可以按与上述生成单元相似的方式来实现。根据实施方式，该单元可以包含在生成单元或者验证单元中，或者单独地实现。
图4示出了根据本公开的实施例的用于用户设备的方法的流程图。如上所述地，在以下的描述中，第一设备和第二设备可指示在前文描述相同的含义，这里将不再详细描述。
在步骤S401中，获取第一设备输出的识别信息，所述识别信息是基于与第一设备的使用状况相关的信息生成的。
在步骤S402中，将所述识别信息传送至第二设备。
在步骤S403中，接收来自所述第二设备的利用所述识别信息生成的验证信息；
在步骤S404中，输出所述验证信息，以供所述第一设备进行验证。
该步骤S401，S402，S403和S404可以分别以与前文所述的S103，S104，S108和S109相似的方式来实现，这里将不再进行具体描述。
图5示出了用户设备的示意性框图。图5中所示的各个单元可以实现上述参照图4描述的方法步骤，并且能够以各种方式，例如硬件、固件、软件模块等来实现。例如，这些单元可以集成在一起实现，例如由单个电路或者装置来实现，或者可以单独地实现。
该用户设备可具有用于从第一设备获取识别信息的获取单元501，例如用于扫描第一设备的显示的扫描装置等，以及供用户将第一单元的识别信息输入用户设备的装置。根据一种实施方式，在用户设备可以与第一设备通信的情况下，该获取单元可以对应于通信模块中的接收电路。
该用户设备500还可包括用于传送第一设备生成的识别信息至第二设备的传送单元502，以及用于接收来自所述第二设备的根据所述识别信息生成的验证信息的接收单元503。
根据一种实施方式，该传送单元和接收单元都可通过在用户设备的处理器上运行所存储和安装的应用程序(例如手机APP)来实现，也可由用户设备上的相关电路来实现。
该用户设备还可具有输出验证信息的输出单元501，例如可以是显示单元，或者在用户设备可以与第一设备通信的情况下将验证信息传递给第一设备的通信模块中的发送电路。
图6示出了根据本公开的用于第二设备的方法的流程图。如上所述地，该在以下的描述中，第一设备和用户设备可指示在前文描述相同的含义，这里将不再详细描述。
在步骤S601中，接收来自用户设备的识别信息，所述识别信息是基于与第一设备的使用状况相关的信息的。
在步骤S602中，根据所述识别信息生成验证信息。
在步骤S6503中，向用户设备发送所述验证信息。
该步骤S601，S602，S603可以分别以与前文所述的S105，S106，S107相似的方式来实现，这里将不再进行具体描述。
图7示出了第二设备的示意性框图。图7中所示的各个单元可以实现上述参照图6描述的方法步骤，并且能够以各种方式，例如硬件、固件、软件模块等来实现。例如，这些单元可以集成在一起实现，例如由单个电路或者装置来实现，或者可以单独地实现。
第二设备700可包括用于接收来自用户设备的识别信息的接收单元701，所述识别信息包括与第一设备的使用状况相关的信息；用于根据所述识别信息生成验证信息的生成单元702；以及用于向用户设备发送所述验证信息的发送单元703。
根据一种实施方式，该生成单元可以如前述第一设备中的生成单元那样实现。根据一种实施方式，接收单元和发送单元都可通过第二设备中的通信收发电路来实现。根据一种实施方式，生成单元可通过在第二设备上所安装的应用程序来实现，也可通过第二设备上的相关电路来实现。
根据本公开，该第一设备本身并不需要与第二设备(例如服务器)进行任何直接通信，特别是关于识别信息和验证信息的直接通信。因此即使设备本身与服务器的网络通讯不佳，识别信息以及验证信息也可通过用户设备在设备与服务器之间成功地传递，并不影响动态码的验证。这样，设备的联网需求大大降低，设备甚至可以不需要 设置网络通讯模块，一定程度上降低设备制造成本。
更进一步地，在本公开的方案中，所生成的识别信息包含有与提供服务的设备的使用状况相关的信息，这样通过单一信息传递过程，可以在实现验证的同时，服务器还可以了解到该设备的使用状况，无需与该设备直接通信，从而将验证过程和信息传输结合到一起，简化了通信过程。
此外，验证是由提供服务的设备发起并且在该设备处进行的，这样可有效地降低服务器处的工作负荷。
上述的工作流程主要涉及开始服务阶段的验证操作流程，在服务结束时，类似地，第一设备可再次生成识别信息，并且由用户设备传递至第二设备，从而第二设备可以了解设备使用结束时第一设备的状态信息，用户设备的使用记录等等，而无需与第一设备直接通信。
在实际应用中，还可利用上述操作流程中所提供的信息来对于服务进行计费。
根据一种实施方式，在停止服务后，用户再次将此时第一设备的识别信息上传第二设备。第二设备可利用两次上传之间的差异，完成费用核算。这种方式可以被称为后付费方式。
在一种简化方式中，例如，在用户设备两次接入第二设备时，第二设备可以基于两次接入之间的时间差异来进行计费。在另一种方式中，由于第一设备所生成的识别信息是以一些基本信息为基础而生成的，而这些基本信息可以包含一些与费用结算相关联的信息，因此可以利用两次传输中基本信息之间的差异来进行计费。
在此情况下，考虑到可能的验证失败等等，第二设备可以在用户设备接入第二设备之后保留预定的时间，在该预定时间内是不收费的。如果超过该预定时间仍不再从用户设备获得新的验证码，则认为用户设备成功获得了第一设备的服务，并且以先前存储的接入时间/第一设备的状态信息作为计费基础。如果在此预定时间内，用户设备重新传送识别信息给第二设备，则第二设备将先前存储的接入时间/第一设备的状态信息更新为当前的接入时间/第一设备的状态信息，并且重复上述操作。
此预定时间可以是考虑了服务器发送验证码至用户设备、用户设备将验证码输入第一设备并且第一设备进行验证操作所花费的时间等等来确定的，并且通常长于这些时间的总和。
根据一种实施方式，可以采用所谓的预付费方式。例如，用户可以在服务开始之 前预先付费以购买预定量/预定时间长度的服务，而服务开始之后，当到达该预定量/预定时间后，第一设备不再提供服务，服务结束。在此情况下，无需第一设备再次生成识别信息并且通过用户设备来传递识别信息。
根据一种实施方式，对应于用户预付费的用户预订服务信息可以连通第二设备生成的验证信息一起被传递回第一设备，第一设备可以按照该服务信息来提供服务。如果在验证过程中出现失败需要重新验证，则用户的预订信息也会在重新验证过程中被再次发送给第一设备。
根据一种实施方式，用户可以在传递识别信息给第二设备时，接收到第二设备的预付费提示而付费来购买预定量/预定时间长度的服务。当然，预付费还可以在服务开始之前的其它时间进行。
本公开所记载的这种新型动态码验证方案在实施过程中并不需要依赖准确的时间用于生成验证码，因此甚至在设备完全断电后再开机也不会影响该验证方案的实施。同时该方案中设备并不直接与第二设备通讯，而是依赖用户的用户设备完成与第二设备通讯的过程，因此设备本身并不需要具备网络通讯模块。在设备制造成本上具有一定优势。
此外，通过识别信息的生成和传递，可以通过单次通信来同时实现若干方便的功能。特别地，通过识别信息的生成和传递，在服务器能够为第一设备提供对应的验证码的同时，服务器还可以在不与设备直接通信的情况下方便地了解到第一设备的状态信息并例如利用该状态信息进行服务器端的操作。由此，用户的操作并不复杂，而且通信的安全性和可靠性大大提高。
以上描述的本公开的实施例可以广泛地应用于各种应用场景，例如充电设备，共享车辆，诸如共享车辆，安保设施等等。以下将针对示例性的应用场景来详细描述本公开的技术方案。
示例1
以下将以充电设备为例来详细描述本公开的技术方案的实施。其中充电设备中的至少验证管理部件可对应于前述的第一设备，后端服务器对应于前述的第二设备。
目前市面上比较常见的充电设备包括相对固定式的充电设备，例如充电桩、桌面式充电设备等；以及自助租借移动电源的充电设备。这些充电设备整个服务流程—— 包括充电开始、充电结束、费用结算等通常都依赖于充电设备与后端服务器之间的通讯来完成。在服务流程中，用户使用用户设备与后端服务器通讯确认身份、缴交押金完成后，后端服务器向充电设备发送指令，确认充电开始。当用户结束充电后，设备将结束指令发送至服务器，服务器根据使用时间或者耗费电量等相关依据与用户结算费用。用户通过电子支付完成费用结算后，服务流程即完成。
因为整个服务流程均依赖充电设备和服务器之间的通讯，因此充电设备往往需要安装网络通讯模块，与服务器之间建立网络通讯。这样会使得充电设备的生产难度和制造成本难以降低，而且还可能存在一定的安全风险。
然而，随着发展，充电设备，尤其是功能单一、系统简单的桌面式充电设备，越来越追求生产快、成本低。
对于此，本示例提出了改进的利用动态码控制充电流程的充电设备，其中的网络通信模块被去除，从而使得设备的生产难度以及制造成本都会大大下降。而且在充电设备与服务器无需直接通信的情况下，仍能保证充电流程的正常进行，且同时服务器也能够及时、准确地了解充电设备的动态状况信息。
以下将参照附图8-10来详细描述充电设备的构造。应指出，附图所示的充电设备的构造仅仅是说明性的，而非限制性的。
如图8所示，该充电设备可包括控制部件、输出部件、输入部件、充电服务部件等组成部分，其中，控制部件分别与输出部件、输入部件、充电服务部件等相互连接以进行交互。应理解，诸如供电电源之类的公知的其它部件未被详细描述。其中，前述的第一设备可至少对应于控制部件，输入部件和输出部件，这些都被总称为验证管理部件。
控制部件可被以多种方式实现，例如被编程以实现上述功能的常规处理器、包括分别用于实现上述功能的离散式器件的一体式部件，分散式部件等等。作为示例，该控制部件可实现为处理器诸如CPU、微处理器诸如MCU，印刷电路板等。如图10所示，控制部件可以实现为主控PCB板。
该控制部件应用户请求或者定期自动地根据充电设备的一些基本信息动态生成识别码，例如二维码，前文所述的识别信息。该充电设备的基本信息包括但不限于设备的编号、设备剩余电量、设备运行状况、上一位用户使用时长等信息。
该控制部件还可具有用于验证从输入部件获得的验证信息与充电设备自身产生的 验证信息是否一致的验证功能。这些验证信息可如前文所述地根据特定算法来产生。
根据一种实施方式，控制部件中的识别信息和验证信息的生成可由特定的电路来实现，例如可以包括运算电路、比较电路、加法电路、减法电路、加密电路、解密电路等等中的至少一种，例如可以由实现特定算法功能的集成电路、FPGA、ASIC等实现。根据一种实施方式，也可通过特定的电路来实现验证功能，例如实现特定功能的集成电路、FPGA、ASIC等实现，或者可由比较电路、比较器等实现。
输出部件，例如显示部件与控制部件电连接，将控制部件生成的识别码显示出来以供用户扫描输入或者手动输入用户设备，例如用户的移动手机。根据该识别码的类型不同，显示部件也可以采用不同的形式。在本例中，识别码为二维码，因此本充电设备所配置的显示部件为彩色显示屏。在实际应用中，如果识别码是数字形式，那么显示部件也可以是数字显示器。当然，输出部件还可以是其它形式，只要可以将识别码或工作状况提供给用户即可。如图9和10所示，输出部件可以是诸如显示屏的显示部件，
输入部件用于接收用户/用户设备输入的来自后台服务器的验证信息。控制部件与输入部件电连接，接收通过输入部件所输入的验证码信息。
依赖于输入的验证信息的类型，该输入部件的形式也可以是多样的。例如，在本例中设备所使用的输入部件是轻触开关，如图10所示，不同开关对应不同的数字，使用不同的数字组合成不同的验证码。当然该输入部件还可以包含字母、字符等按键，如图9所示。根据一种实施方式，验证码可以是二维码、条形码、图案码等形式，此时输入部件可以为扫描器，用户只需提供该验证码供该输入部件扫描，即可完成验证码的输入。当然，输入部件还可以是其它形式，只要可以将验证码提供给充电设备即可。
充电服务部件为设备向用户提供充电服务的部件。该部件的工作状态受控制部件的控制，控制部件在确认用户所输入的验证码有效，则向充电服务部件发出指令，充电服务部件开始提供充电服务。当服务时间完结后，控制部件即向充电服务部件发出指令，停止提供充电服务。
在本例中，充电服务部件为至少一个充电接口/充电线，用户使用数据线连接充电接口与移动设备。如图9和10所示。在验证通过之后，控制部件指令充电服务部件开始工作，即指令充电接口通电，开始向移动设备充电。当控制部件指令充电服务 部件停止工作时，即指令充电接口断电，停止向移动设备充电。在此情况下，充电设备生成的识别码主要包含的是充电设备本身的状态信息。
根据一种实施方式，充电服务部件也可以是充电模组的形式，诸如容纳有至少一个移动电源的容纳装置。在验证通过之后，控制部件控制充电服务部件开始工作，即控制充电模组送出移动电源供用户使用。当用户归还移动电源时，控制部件控制充电模组将移动电源吸纳进充电模组内重新对移动电源充电。在此情况下，充电设备生成的识别码除了包含充电设备的状态信息外，还会包含使用的移动电源相关的状态信息。
根据一种实施方式，控制部件可以通过驱动部件来控制充电服务部件提供或者结束充电服务。例如，在充电服务部件是充电接口的情况下，驱动部件可根据控制部件的控制来使得充电接口通电或者断电，诸如为开关部件；在充电服务部件是移动电源的情况下，驱动部件可根据控制部件的控制来吞吐移动电源，诸如为容纳一个移动电源的容纳装置或者该容纳装置的驱动装置。
该驱动部件可以与控制部件成一体，也可以与充电服务部件成一体。
充电设备还可以包括机身部件，其他功能部件均安装于机身部件内，机身部件对各个功能部件起保护作用。机身是整机设备的支撑部件，其他各功能部件安装于机身上。例如，机身部件可以包括机壳(例如，左机壳和右机壳)、底座(左底座和右底座)、灯板等，在为充电服务部件提供电源的内置电芯可以被容纳在机身部件内，并且与充电服务附件连接，如图9和10所示，在本例中，机身采用注塑成型，材料使用ABS工程塑料。在实际应用中，也可以使用其他材料和其他制造工艺制造机身，例如使用钣金材料通过折弯等工艺制造金属机身等。
充电设备还可以包括其它部件以用于驱动、指示、装饰、美观等作用，这些将不再详细描述。
以下将示例性地描述充电设备的示例性的工作流程。应指出，这里所描述的工作过程仅仅是示例性的，该工作过程还可以以如前文所描述的各过程的其它方式来实施。
充电设备的控制部件会根据请求或者定时地根据设备的信息动态生成识别码，并调用预设的算法对识别码进行计算，获得验证码(验证码A)并输出识别码，例如将所生成的识别码投射到显示部件上。上述的用于生成识别码和用于生成验证码的算法被预先装载到充电设备中，例如在制造期间，其中用于生成验证码的算法是每个充电设备特有的。而与之相对应的算法仅仅被装载到后台服务器中。
在用户希望充电时，用户可以通过用户设备上的专用APP或者其它第三方APP来输入识别码并且上传至服务器。取决于充电设备生成的识别码的形式，用户可以手动地输入该识别信息，或者可以通过用户设备的摄像头扫描该识别信息，并且上传信息。
后端服务器对识别码进行解读，获取二维识别码所包含的信息。其中，后端服务器根据二维识别码中的设备编码调用相应的算法对二维识别码进行计算，获得验证码(验证码B)，并且将验证码B发送回用户设备。此时，后台服务器可以将识别码所包含的其他信息记录在服务器内。例如，服务器可以获知该识别信息中所包含的充电设备的标识信息和电量信息，并且将这两者关联地存储以作为充电设备的使用记录。
用户通过充电设备的输入部件将验证码B输入充电设备。
充电设备核对该验证码B与设备本身计算的验证码A是否一致，一致则认为通过验证，控制充电服务部件开启充电服务。如果两个验证码核对结果不一致，则无法通过验证，需要重复上述过程以继续验证，直到通过验证为止。作为替代，验证码A也可以不在生成充电设备识别码时生成，而是在验证码B输入之后，基于先前缓存的识别码而生成。
图11示出了根据本公开的一个实施例的验证充电流程，其中所示的来电宝对应于本公开中所描述的充电设备。
来电宝根据电量、密码因子、异常代码、电池容量、循环次数、上次使用时长等动态生成二维码(S1101)，并且显示该二维码。用户利用手机扫一扫该二维码(S1102)，从而该二维码能够通过加密数据传输(密文)来传输到用户手机上(S1103)，然后用户通过手机对于服务器进行密文传输(S1104)。
在接收到密文之后，服务器根据密文可以计算出密码(S1105)，并且将所计算出的密码传送回用户侧(S1106)。在接收到密码之后，用户在来电宝键盘中输入密码(S1107)。
来电宝利用其中动态生成的二维码对于所输入的密码进行验证(S1108)，并且在验证通过的情况下，电源线可以输出电流，从而用户可以充电(S1109)。
如果充电设备以付费充电模式工作，则还可以通过类似的上述工作流程来对于用户设备的充电进行计费。
根据一种实施方式，可以采用前文所述的后付费模式，其中，在充电结束时，用户再次获得充电设备的识别码并提供给服务器，服务器通过将两次输入的识别码的信 息进行比较，从而核算用户的使用费用。例如，在用户设备与充电接口断开时，或者用户将移动电源归还到充电模组中时，充电设备认为充电服务结束，并且会再次生成识别码。
在实际应用中，在充电服务结束之后，服务器还可以将核算的费用告知用户，同时提供其他表述，例如感谢使用，欢迎下次使用等。当然，服务器也可以先提供其他表述，稍后再计算并提供费用。
在实际应用中，当用户设备在专用APP或者其它第三方APP上提交停止充电的请求时，如果用户设备此没有输入识别信息，则服务器会要求用户设备提供识别信息，而服务器并不会开始核算费用。
根据一种实施方式，可以采用前文所述的预付费模式，例如，用户在充电开始之前可以预先付费以购买预定量的充电时间，并且通过验证以后，控制部件会向充电服务部件发出指令，使充电接口通电，用户即可通过充电线连接充电设备和移动设备，开始给移动设备充电。充电服务部件开始提供充电服务的同时，控制部件开始计时，当到达预设时间后，控制部件即控制充电服务部件停止供电，该充电服务即停止。
通常，作为充电接口的充电服务部件可以采用后付费和前付费模式，而作为移动电源的充电服务部件通常主要采用后付费模式。
由上述描述可见，本公开的充电设备在整个运作中依靠动态码就可成功完成用户设备充电，而此过程中充电设备无需与服务器之间进行直接通信，这样充电设备中的通讯模块可以被省略，从而大大简化充电设备的制造，降低充电设备的成本。
而且，充电设备在识别码中可以融入很多各种基本信息，当用户扫描识别码的同时，等于将设备的这些基本信息同时传输给后端服务器，后端服务器根据二维码所上传的信息进行费用核算、设备状况更新，维护人员可以通过服务器后台查看各设备的运行状态，有针对性地进行设备维护，而服务器无需与充电设备直接通信。
而且，识别码可以是动态产生的，每隔一段时间就发生变化，其安全性和可靠性也明显高于固定识别码。
示例2
以下以共享车辆为例来描述本申请的技术方案的实施。其中共享车辆上的能够生成信息并且验证信息的验证管理模块可对应于前述的第一设备，该模块可以具有显示 屏，并且能够获知共享车辆的相关状态信息例如，车辆的故障信息，车辆的里程信息，车辆的位置信息等等，后端服务器对应于前述的第二设备。以下以车辆的里程信息为例来描述共享车辆中本申请的技术方案的实施。
在操作中，该共享车辆的第一设备能够根据单车编码和上述信息行程计算表的行程刻度生成一个识别条形码或二维码，该识别码每间隔一段时间变化一次。用户使用共享车辆的时候，用手机APP扫描该条形码，并将识别码上传服务器。服务器根据条形码利用预设算法计算出验证码，并将验证码反馈回客户APP。用户将验证码输入共享车辆，CPU将用户输入的验证码与CPU计算的验证码进行核对，核对结果一致则自动解锁，以供用户使用。当用户需要结束租借的时候，用APP再次扫描条形码，并将该条形码上传至服务器，服务器根据两次条形码上传的时间间隔以及条形码所包含的行程计算表的行程信息，核算出相应的租借费用，并收取租金。
除此之外，也可以在共享车辆上安装GPS模块，将GPS定位信息也作为一种基本信息，识别码将GPS定位信息也包含在内，用户上传识别码的时候将GPS信息一并上传至服务器进行记录。
示例3
以下以安全门禁设备为例来描述本申请的技术方案的实施。其中安全门禁设备可对应于前述的第一设备，该设备可以具有显示屏，并且能够获知希望使用门禁设备的用户的身份信息，后端服务器对应于前述的第二设备。
在操作中，在用户希望使用完全门禁时，门禁设备要求用户输入用户身份信息，例如用户输入用户身份证件号码、条形码等或者由门禁设备的摄像头扫描得到用户的视网膜、指纹、脸部信息等等。该门禁设备能够根据门禁设备的编码和上述用户身份信息生成一个识别条形码或二维码，该识别码每间隔一段时间变化一次，并且将其显示在门禁设备的显示部件上。
用户用手机APP扫描该条形码，并将识别码上传服务器。服务器根据条形码利用预设算法计算出验证码，并将验证码反馈回客户APP。用户将验证码输入门禁设备，CPU将用户输入的验证码与CPU计算的验证码进行核对，核对结果一致则自动解锁，以供用户出入。
应指出上文描述的示例仅仅是示例性的，本公开的技术方案仍可广泛地应用于其 它类型的需要进行验证的设备，诸如保险柜、各种自助服务设备等等，从本公开的描述可见，这些设备都无需安装通信模块，从而大大降低了成本，提高了生产率。
至此，已经详细描述了根据本公开的动态码验证方法和设备。为了避免遮蔽本公开的构思，没有描述本领域所公知的一些细节。本领域技术人员根据上面的描述，完全可以明白如何实施这里公开的技术方案。
可能以许多方式来实现本公开的方法和设备。例如，可通过软件、硬件、固件或者软件、硬件、固件的任何组合来实现本公开的方法和设备。用于所述方法的步骤的上述顺序仅是为了进行说明，本公开的方法的步骤不限于以上具体描述的顺序，除非以其它方式特别说明。
应注意，上述各个单元仅是根据其所实现的具体功能划分的逻辑模块，而不是用于限制具体的实现方式，例如可以以软件、硬件或者软硬件结合的方式来实现。在实际实现时，上述各个单元可被实现为独立的物理实体，或者也可由单个实体(例如，处理器(CPU或DSP等)、集成电路等)来实现。其中，处理电路可以指在计算系统中执行功能的数字电路系统、模拟电路系统或混合信号(模拟和数字的组合)电路系统的各种实现。处理电路可以包括例如诸如集成电路(IC)、专用集成电路(ASIC)这样的电路、单独处理器核心的部分或电路、整个处理器核心、单独的处理器、诸如现场可编程门阵列(FPGA)的可编程硬件设备、和/或包括多个处理器的系统。
另外，还应该指出的是，上述系列处理和设备也可以通过软件和/或固件实现。在通过软件和/或固件实现的情况下，从存储介质或网络向具有专用硬件结构的计算机安装构成该软件的程序，该计算机在安装有各种程序时，能够执行各种功能等等。图12是示出作为本公开的实施例中可采用的设备的示例结构的框图。
中央处理单元(CPU)1801起到基于存储在只读存储器(ROM)1802或存储单元1808上的程序执行各类处理的数据处理单元的作用。例如，CPU 1801执行基于前述操作。随机存取存储器(RAM)1803存储由CPU 1801执行的程序、数据等。CPU1801、ROM 1802和RAM 1803经由总线1804彼此相连。
CPU 1801经由总线1804连接至输入和输出接口1805，并且由各类开关、键盘、鼠标、麦克风等构成的输入单元1806和由显示器、扬声器等构成的输出单元1807连接至该输入和输出接口1805。例如，CPU 1801响应于从输入单元1806输入的指令执行各类处理，并将处理结果输出至输出单元1807。
连接至输入和输出接口1805的存储单元1808例如由硬盘构成，并且在其上存储由CPU 1801执行的程序以及各类数据。通信单元1809经由诸如因特网或局域网的网络与外部设备通信。应理解，在第一设备的硬件配置中，通信单元是可以省略的。
连接至输入和输出接口1805的驱动器1810驱动诸如磁盘、光盘、磁光盘或者半导体存储器(例如存储卡)的之类的可移除介质1811，并且获取其上记录的诸如内容和密钥信息的各类数据。
此外，在一些实施例中，还可将本公开实施为记录在存储介质中的程序，这些程序包括用于实现根据本公开的方法的机器可读指令。因而，本公开还覆盖存储用于执行根据本公开的方法的程序的存储介质。该存储介质可以是非易失性存储介质，其例子可包含磁盘(包含软盘(注册商标))、光盘(包含光盘只读存储器(CD-ROM)和数字通用盘(DVD))、磁光盘(包含迷你盘(MD)(注册商标))、半导体存储器、存储卡、存储棒等。
应当理解，根据本公开的实施例的存储介质和程序产品中的机器可执行指令还可以被配置为执行与上述装置实施例相对应的方法，因此在此未详细描述的内容可参考先前相应位置的描述，在此不再重复进行描述。
虽然已经通过示例对本公开的一些特定实施例进行了详细说明，但是本领域的技术人员应该理解，以上示例仅是为了进行说明，而不是为了限制本发明的范围。本领域的技术人员应该理解，可在不脱离本公开的范围和精神的情况下，对以上实施例进行修改。本发明的范围由所附权利要求来限定。

Claims (59)

  1. 一种用于第一设备的方法，包括：
    基于与所述第一设备的使用状况相关的信息生成识别信息；
    输出所述识别信息，以供用户设备获取所述识别信息；
    从所述用户设备或用户接收第一验证信息；以及
    利用与所述识别信息对应的第二验证信息，对所接收到的第一验证信息进行验证。
  2. 根据权利要求1所述的方法，其中，所述识别信息被所述用户设备获取，并被所述用户设备发送到第二设备。
  3. 根据权利要求1所述的方法，其中，所述第一验证信息是由所述第二设备利用所述识别信息产生并发送到所述用户设备的。
  4. 根据权利要求1所述的方法，其中，所述从所述用户设备或用户接收第一验证信息包括：通过所述第一设备的输入装置接收所述用户输入的所述第一验证信息。
  5. 根据权利要求1所述的方法，其中，所述从所述用户设备或用户接收第一验证信息包括：通过所述第一设备的获取装置从用户设备获取所述第一验证信息。
  6. 根据权利要求2或3所述的方法，所述第一设备与所述第二设备之间不进行关于所述识别信息和所述第一验证信息的直接通信。
  7. 根据权利要求1-5中任一项所述的方法，其中，所述第一设备具有显示单元，所述显示单元被配置用于显示所述识别信息。
  8. 根据权利要求1-5中任一项所述的方法，还包括：
    如果验证成功，则所述第一设备变为允许用户使用的状态。
  9. 根据权利要求1-5中任一项所述的方法，其中，所述第一设备是充电装置，所述与第一设备的使用状况相关的信息包括所述充电装置的电量信息、充电时间信息中的至少一个。
  10. 根据权利要求1-5中任一项所述的方法，其中，所述第一设备是用于容纳充电装置的容纳装置，所述与第一设备的使用状况相关的信息包括所述容纳装置的状态信息、所述容纳装置中所包含的可用充电装置的电量信息和充电时间信息中的至少一个。
  11. 根据权利要求1-5中任一项所述的方法，其中，所述第一设备是车辆，所述与第一设备的使用状况相关的信息包括所述车辆的位置信息和行驶距离信息中的至少一个。
  12. 根据权利要求2或3所述的方法，其中，所述识别信息还包括所述第一设备的身份标识信息、加密的验证码和第二设备地址信息中的至少一个，所述第二验证信息是所述验证码。
  13. 根据权利要求12所述的方法，其中，所述第一验证信息是经所述第二设备从所述识别信息解密得到的验证码。
  14. 根据权利要求2或3所述的方法，其中，所述第一验证信息是所述第二设备基于所接收到的识别信息中包含的所述与第一设备的使用状况相关的信息而被生成的，所述第二验证信息是所述第一设备基于所生成的识别信息中包含的所述与第一设备的使用状况相关的信息而被生成的。
  15. 根据权利要求1-5中任一项所述的方法，其中，如果验证成功，则在所述用户设备的用户停止使用所述第一设备之前不再产生识别信息。
  16. 根据权利要求1-5中任一项所述的方法，还包括：在所述与第一设备的使用 状况相关的信息不满足预定条件时，不生成识别信息。
  17. 根据权利要求1-6中任一项所述的方法，还包括：获取所述用户设备的身份标识信息以认证所述用户设备的身份；
    其中，响应于对所述用户设备的身份认证成功，生成所述识别信息。
  18. 根据权利要求2或3所述的方法，还包括将用户设备的操作信息记录在第一设备内，并且定期地将用户设备的操作信息上报至服务器。
  19. 一种用于用户设备的方法，包括：
    获取第一设备输出的基于与第一设备的使用状况相关的信息生成的识别信息；
    将所述识别信息传送至第二设备；
    接收来自所述第二设备的利用所述识别信息生成的验证信息；
    输出所述验证信息，以供所述第一设备进行验证。
  20. 根据权利要求19所述的方法，其中，获取第一设备输出的识别信息包括：通过所述用户设备的扫描装置，扫描所述第一设备显示的识别信息。
  21. 根据权利要求19所述的方法，其中，所述输出所述验证信息包括：显示所述验证信息。
  22. 根据权利要求19所述的方法，其中，所述第一设备是充电装置，所述与第一设备的使用状况相关的信息包括所述充电装置的电量信息和充电时间信息中的至少一个。
  23. 根据权利要求19所述的方法，其中，所述第一设备是用于容纳充电装置的容纳装置，所述与第一设备的使用状况相关的信息包括所述容纳装置中所包含的可用充电装置的电量信息和充电时间信息中的至少一个。
  24. 根据权利要求19所述的方法，其中，所述第一设备是车辆，所述与第一设备的使用状况相关的信息包括所述车辆的位置信息和行驶距离信息中的至少一个。
  25. 根据权利要求19所述的方法，其中，所述识别信息还包括所述第一设备的身份标识信息、加密的验证码和第二设备地址信息中的至少一个。
  26. 根据权利要求25所述的方法，其中，所述验证信息是经所述第二设备从所述识别信息解密得到的验证码。
  27. 根据权利要求19所述的方法，其中，所述验证信息是所述第二设备基于所接收到的识别信息所基于的所述与第一设备的使用状况相关的信息生成的。
  28. 一种用于第二设备的方法，包括：
    接收来自用户设备的识别信息，所述识别信息是基于与第一设备的使用状况相关的信息的；
    根据所述识别信息生成验证信息；以及
    向用户设备发送所述验证信息。
  29. 根据权利要求28所述的方法，其中，第一设备与第二设备之间不进行关于所述识别信息和所述验证信息的直接通信。
  30. 根据权利要求28所述的方法，其中，所述识别信息是由第一设备产生并且由用户设备获取的。
  31. 根据权利要求28所述的方法，其中，所述验证信息由用户设备或者用户提供给第一设备以供验证。
  32. 根据权利要求28所述的方法，其中，所述第一设备是充电装置，所述与第一设备的使用状况相关的信息包括所述充电装置的电量信息和充电时间信息中的至少 一个。
  33. 根据权利要求28所述的方法，其中，所述第一设备是用于容纳充电装置的容纳装置，所述与第一设备的使用状况相关的信息包括所述容纳装置中所包含的可用充电装置的电量信息和充电时间信息中的至少一个。
  34. 根据权利要求28所述的方法，其中，所述第一设备是车辆，所述与第一设备的使用状况相关的信息包括所述车辆的位置信息和行驶距离信息中的至少一个。
  35. 根据权利要求28所述的方法，其中，所述识别信息还包括所述第一设备的身份标识信息、加密的验证码、所述第二设备地址信息中的至少一个。
  36. 根据权利要求35所述的方法，其中，所述加密的验证码被所述第二设备解密以作为所述验证信息。
  37. 根据权利要求28所述的方法，其中，所述验证信息是所述第二设备基于所接收到的识别信息所基于的所述与第一设备的使用状况相关的信息而生成的。
  38. 根据权利要求28所述的方法，其中，所述第二设备根据用户设备两次传送识别信息至第二设备的与第一设备的使用状况相关的信息之间的差异来进行计费。
  39. 根据权利要求28所述的方法，还包括：
    获得来自所述用户设备的预付费信息，
    其中，第二设备产生的所述验证信息还包含所述预付费信息，以供第一设备在对所述验证信息验证成功后根据所述预付费信息为用户设备提供服务。
  40. 根据权利要求28所述的方法，还包括：
    获得来自所述用户设备的身份标识信息，
    其中，如果第二设备根据所述用户设备的身份标识信息已经确定用户设备已经在 使用第一设备，则不再生成验证信息，并且向用户设备报告。
  41. 根据权利要求28所述的方法，还包括：
    获得来自所述用户设备的身份标识信息，
    其中，所述第二设备将用户设备的身份标识信息与第一设备的身份标识信息相关联地进行记录。
  42. 根据权利要求28所述的方法，其中，所述第二设备根据识别信息中所包含的所述与第一设备的使用状况相关的信息来确定所述第一设备的工作状态，并向工作人员做出指示。
  43. 根据权利要求28所述的方法，还包括：
    对所述识别信息中所包含的所述第一设备的身份标识信息进行认证，并且
    根据所认证的所述第一设备的身份标识信息来采用对应的算法以产生验证信息。
  44. 根据权利要求43所述的方法，所述验证信息是通过采用所述对应的算法根据所述与第一设备的使用状况相关的信息来产生的。
  45. 一种方法，包括：
    第一设备基于与第一设备的使用状况相关的信息生成识别信息；
    用户设备从第一设备获取所述识别信息，并将所述识别信息传送至第二设备；
    所述第二设备利用接收到的识别信息生成第一验证信息，并将所述第一验证信息发送给所述用户设备；
    所述用户设备输出所述第一验证信息；以及
    所述第一设备基于与所生成的识别信息对应的第二验证信息，对所述第一验证信息进行验证。
  46. 根据权利要求45所述的方法，其中，第一设备与第二设备之间不进行关于所述识别信息和所述第一验证信息的直接通信。
  47. 一种第一设备，包括：
    用于基于与所述第一设备的使用状况相关的信息生成识别信息的生成单元；
    用于输出所述识别信息，以供用户设备获取所述识别信息的输出单元；
    用于从所述用户设备或用户接收第一验证信息的接收单元；以及
    用于利用与所述识别信息对应的第二验证信息，对所接收到的第一验证信息进行验证的验证单元。
  48. 根据权利要求47所述的第一设备，其中，所述输出单元是显示所述识别信息的显示单元。
  49. 根据权利要求48所述的第一设备，其中，所述接收电路包括接收中间设备的用户手动输入验证信息的电路。
  50. 根据权利要求48所述的第一设备，其中，所述接收电路包括扫描中间设备提供的验证信息的电路。
  51. 一种用户设备，包括：
    用于获取第一设备输出的基于与第一设备的使用状况相关的信息生成的识别信息的获取单元；
    用于将所述识别信息传送至第二设备的传送单元；
    用于接收来自所述第二设备的利用所述识别信息生成的验证信息的接收单元，以及；
    用于输出所述验证信息，以供所述第二设备进行验证的输出单元。
  52. 一种第二设备，包括：
    用于接收来自用户设备的识别信息的接收单元，所述识别信息是基于与第一设备的使用状况相关的信息的；
    用于根据所述识别信息生成验证信息的生成单元；以及
    用于向用户设备发送所述验证信息的发送单元。
  53. 一种设备，包括
    处理器，以及
    存储器，存储有指令，所述指令在由所述处理器执行时使得所述设备实现根据权利要求1-18中任一项所述的方法。
  54. 一种设备，包括
    处理器，以及
    存储器，存储有指令，所述指令在由所述处理器执行时使得所述设备实现根据权利要求19-27中任一项所述的方法。
  55. 一种设备，包括
    处理器，以及
    存储器，存储有指令，所述指令在由所述处理器执行时使得所述设备实现根据权利要求28-44中任一项所述的方法。
  56. 一种设备，包括
    一个或多个处理器，以及
    一个或多个存储器，存储有指令，所述指令在由所述一个或多个处理器执行时使得所述设备实现根据权利要求45所述的方法。
  57. 一种非暂态存储设备，存储有指令，所述指令在由处理器执行时使得实现根据在前权利要求1-18中任一项所述的方法。
  58. 一种非暂态存储设备，存储有指令，所述指令在由处理器执行时使得实现根据在前权利要求19-27中任一项所述的方法。
  59. 一种非暂态存储设备，存储有指令，所述指令在由处理器执行时使得实现根 据在前权利要求28-44中任一项所述的方法。
PCT/CN2017/086292 2017-05-27 2017-05-27 验证方法及设备 WO2018218411A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/086292 WO2018218411A1 (zh) 2017-05-27 2017-05-27 验证方法及设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/086292 WO2018218411A1 (zh) 2017-05-27 2017-05-27 验证方法及设备

Publications (1)

Publication Number Publication Date
WO2018218411A1 true WO2018218411A1 (zh) 2018-12-06

Family

ID=64454247

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/086292 WO2018218411A1 (zh) 2017-05-27 2017-05-27 验证方法及设备

Country Status (1)

Country Link
WO (1) WO2018218411A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111885135A (zh) * 2020-07-14 2020-11-03 浙江吉智新能源汽车科技有限公司 一种自动更换电池的系统及方法
CN113496403A (zh) * 2020-04-07 2021-10-12 国网电动汽车服务有限公司 一种充电身份信息校验系统及方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100306112A1 (en) * 2009-06-01 2010-12-02 Userstar Information System Co., Ltd. Online trading method and system with mechanism for verifying authenticity of a product
CN104464105A (zh) * 2014-12-15 2015-03-25 杭州行我行网络有限公司 基于手机app和蓝牙通信的自行车租还系统和方法
CN105072132A (zh) * 2015-08-27 2015-11-18 宇龙计算机通信科技(深圳)有限公司 验证方法、验证系统和通信设备
CN106355772A (zh) * 2016-10-12 2017-01-25 杭州行我行网络有限公司 一种自行车智能密码锁和系统及其操作方法
CN106447940A (zh) * 2016-10-17 2017-02-22 江苏宏溥科技有限公司 利用密码管理的公共自行车租赁系统与方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100306112A1 (en) * 2009-06-01 2010-12-02 Userstar Information System Co., Ltd. Online trading method and system with mechanism for verifying authenticity of a product
CN104464105A (zh) * 2014-12-15 2015-03-25 杭州行我行网络有限公司 基于手机app和蓝牙通信的自行车租还系统和方法
CN105072132A (zh) * 2015-08-27 2015-11-18 宇龙计算机通信科技(深圳)有限公司 验证方法、验证系统和通信设备
CN106355772A (zh) * 2016-10-12 2017-01-25 杭州行我行网络有限公司 一种自行车智能密码锁和系统及其操作方法
CN106447940A (zh) * 2016-10-17 2017-02-22 江苏宏溥科技有限公司 利用密码管理的公共自行车租赁系统与方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113496403A (zh) * 2020-04-07 2021-10-12 国网电动汽车服务有限公司 一种充电身份信息校验系统及方法
CN111885135A (zh) * 2020-07-14 2020-11-03 浙江吉智新能源汽车科技有限公司 一种自动更换电池的系统及方法

Similar Documents

Publication Publication Date Title
US11276051B2 (en) Systems and methods for convenient and secure mobile transactions
US8677467B2 (en) Method and apparatus in combination with a storage means for carrying out an authentication process for authenticating a subsequent transaction
WO2015161699A1 (zh) 数据安全交互方法和系统
KR100645401B1 (ko) 휴대폰에서의 시간동기 방식 오티피 발생장치와 방법
CN107392591B (zh) 行业卡的在线充值方法、系统及蓝牙读写装置
JP2013255415A (ja) 携帯電子機器用充電ステーションおよび関連システムと方法
CN111585971A (zh) 一种支持离线换电的身份确认方法和系统
WO2015161690A1 (zh) 数据安全交互方法和系统
CN103942687A (zh) 数据安全交互系统
CN104301110A (zh) 应用于智能终端的身份验证方法、身份验证设备和系统
CN107135227A (zh) 验证方法及设备
CN103942688A (zh) 数据安全交互系统
CN103942690A (zh) 数据安全交互系统
JP6092529B2 (ja) 電気移動体用充電システム及びそれに含まれるサーバ装置
JP2015537399A (ja) モバイル決済のためのアプリケーションシステム及びモバイル決済手段を提供する及び用いるための方法
CN103944729A (zh) 数据安全交互方法
WO2018218411A1 (zh) 验证方法及设备
CN103944735A (zh) 数据安全交互方法
CN207200310U (zh) 充电设备
TW201723948A (zh) 線下支付方法、終端設備、後臺支付裝置及線下支付系統
CN102264069B (zh) 基于通用引导架构的认证控制方法、装置及系统
KR101407737B1 (ko) Ｑｒ 코드를 이용한 스마트 기기의 금융 정보 처리 장치 및 그 방법
CN114448649B (zh) 一种数据流通方法、系统、存储介质及电子设备
CN103944911A (zh) 数据安全交互系统
CN116452198B (zh) 一种充电桩离线授权和计费方法及系统

Legal Events

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

Ref document number: 17911621

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 30/04/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17911621

Country of ref document: EP

Kind code of ref document: A1