Identification code verification method, device, equipment and storage medium

Abstract

The present application provides a verification method, device, equipment and storage medium for an identification code certificate; the method includes: obtaining a first identification code certificate to be verified based on a request message sent by a terminal; verifying the first identification code certificate based on a discarding rule corresponding to the first identification code certificate to obtain a verification result; when the verification result indicates that the first identification code certificate needs to be discarded, deleting the first identification code certificate; generating a new first identification code certificate, and sending the new first identification code certificate to the terminal. In this way, the identification certificate can be verified to ensure that a correct and usable identification code is generated according to the identification code certificate.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a method, device, equipment and storage medium for verifying an identification code. Background Art

[0002] With the continuous development of mobile communication technology and the popularization of mobile payment, people can now solve various consumption related to food, clothing, housing and transportation without carrying cash. Taking travel as an example, users can take buses, subways and other means of transportation through the boarding code integrated in an application of the mobile terminal. Furthermore, when riding, users can show the boarding code, and the code scanning device carried in the vehicle can scan it to pay the fare.

[0003] The payment codes in various applications can be generated by obtaining the card certificate online, or by using the offline card certificate stored in the user terminal. However, since the offline card certificate is stored in the user terminal, if there is a problem with the offline card certificate or it has been abandoned, it not only occupies the storage space of the user terminal, but also requires the user to obtain the card certificate again and generate the payment code when using it, which is time-consuming and laborious. Summary of the invention

[0004] The embodiments of the present application provide a method, device and storage medium for verifying an identification code certificate, which can verify the identification certificate to ensure that a correct and usable identification code is generated according to the identification code certificate.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] The present application embodiment provides a method for verifying an identification code certificate, including:

[0007] Based on the request message sent by the terminal, obtaining a first identification code certificate to be verified;

[0008] Verifying the first identification code certificate based on a revocation rule corresponding to the first identification code certificate to obtain a verification result;

[0009] When the verification result indicates that the first identification code certificate needs to be discarded, deleting the first identification code certificate;

[0010] A new first identification code certificate is generated, and the new first identification code certificate is sent to the terminal.

[0011] The present application embodiment provides a verification device for an identification code certificate, including:

[0012] A first acquisition module, used to acquire a first identification code certificate to be verified based on a request message sent by a terminal;

[0013] A verification module, configured to verify the first identification code certificate based on a revocation rule corresponding to the first identification code certificate to obtain a verification result;

[0014] A deleting module, configured to delete the first identification code certificate when the verification result indicates that the first identification code certificate needs to be discarded;

[0015] The first generating module is used to generate a new first identification code certificate and send the new first identification code certificate to the terminal.

[0016] The present application embodiment provides a verification device for an identification code certificate, including:

[0017] A memory for storing executable instructions;

[0018] The processor is used to implement the method provided in the embodiment of the present application when executing the executable instructions stored in the memory.

[0019] An embodiment of the present application provides a storage medium storing executable instructions for causing a processor to execute and implement the method provided in the embodiment of the present application.

[0020] The embodiments of the present application have the following beneficial effects:

[0021] In the verification method of the identification code certificate provided in the embodiment of the present application, after the code issuing platform receives the request message sent by the terminal, it obtains the first identification code certificate to be verified, and verifies the first identification code certificate to determine whether the first identification code certificate needs to be discarded. When it is determined that the first identification code needs to be discarded, the first identification code certificate is deleted, and a new first identification code certificate is generated and sent to the terminal to ensure that the terminal generates a correct and valid second identification code based on the correct and valid new first identification code certificate, thereby improving payment efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1A A schematic diagram of the network architecture of the identification code verification method of the embodiment of the present application;

[0023] Figure 1B An optional structural diagram of an identification code certificate verification method provided in an embodiment of the present application applied to a blockchain system;

[0024] Figure 1C It is an optional schematic diagram of a block structure provided in an embodiment of the present application;

[0025] Figure 2 2 is a schematic diagram of the structure of the code issuing platform 200 provided in an embodiment of the present application;

[0026] Figure 3A schematic diagram of an implementation flow of a method for verifying an identification code provided in an embodiment of the present application;

[0027] Figure 4 A schematic diagram of another implementation flow of the identification code verification method provided in an embodiment of the present application;

[0028] Figure 5 A schematic diagram of another implementation flow of the method for verifying the identification code of the example implementation of this application;

[0029] Figure 6 A schematic diagram of an implementation flow of a method for verifying a boarding code certificate according to an embodiment of the present application;

[0030] Figure 7 This is another implementation flow chart of the method for verifying the boarding code certificate according to the embodiment of the present application. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of this application.

[0032] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0033] In the following description, the terms "first\second\third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0034] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0035] Before further describing the embodiments of the present application in detail, the nouns and terms involved in the embodiments of the present application are explained. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.

[0036] 1) Identification code: a code used to uniquely identify an entity in a certain type of data based on the classification of elements;

[0037] 2) Two-dimensional code: It is an identification code that uses a certain geometric figure to record data symbol information in black and white distributed in a plane (two-dimensional direction) according to a certain rule;

[0038] 3) Mini Programs: Web applications that can be run in installed applications. In other words, mini programs are applications that can be used without downloading.

[0039] 4) Ride code: a QR code that can be used to take buses and subways;

[0040] 5) Ride QR Code Mini Program: A mini program used to generate QR codes for taking buses and subways;

[0041] 6) Offline card certificate: The boarding code backend system generates an offline card certificate and sends it to the boarding code mini program. The boarding code mini program can use the card certificate to generate a boarding QR code locally offline for boarding.

[0042] The following describes an exemplary application of the apparatus for implementing the embodiment of the present application. The apparatus provided in the embodiment of the present application can be implemented as a terminal device. The following describes an exemplary application of the terminal device when the apparatus is implemented as a terminal device.

[0043] See also Figure 1A , Figure 1A This is a schematic diagram of the network architecture of the verification method of the identification code of the embodiment of the present application, such as Figure 1A As shown, the network architecture at least includes a user terminal 100, a code issuing platform 200, a network 300 and a scanning device 400. To support an exemplary application, the user terminal 100 and the scanning device 400 are respectively connected to the code issuing platform 200 through the network 300. The network 300 can be a wide area network or a local area network, or a combination of the two, and a wireless link is used to realize data transmission.

[0044] When the user opens the mini program or opens the electronic card to display the identification code through the user terminal 100, a verification request message or a certificate generation request can be sent to the code issuing platform 200 through the network 300. After receiving the corresponding request message, the code issuing platform 200 obtains the first identification code certificate to be verified, and calls the abandonment rule to determine whether the first identification code certificate needs to be abandoned. When it is determined that the first identification code certificate needs to be abandoned, the first identification code certificate is generated and sent to the user terminal 100. After receiving the first identification code certificate, the user terminal 100 generates and displays the first identification code based on the first identification code certificate, so that the scanning device 400 can scan the first identification code. The scanning device 400 sends the scanned information to the code issuing platform 200 for the code issuing platform 200 to deduct and settle the payment, and after the deduction, the deduction program message is sent to the user terminal 100.

[0045] The code issuing platform may be a payment application with a payment function or a backend server of an instant messaging application, or may be a third-party code issuing platform, which is not specifically limited in the embodiments of the present application.

[0046] The network architecture involved in the embodiment of the present application may also be a distributed system 101 of the blockchain system, see Figure 1B , Figure 1B An optional structural diagram of the identification code certificate verification method provided in the embodiment of the present application applied to a blockchain system, wherein the distributed system 101 can be a distributed node formed by multiple nodes 102 (any form of computing device in the access network, such as a server, a user terminal) and a client 103, and a peer-to-peer (P2P) network is formed between the nodes. The P2P protocol is an application layer protocol running on the Transmission Control Protocol (TCP) protocol. In a distributed system, any machine such as a server or a terminal can join and become a node, and the node includes a hardware layer, an intermediate layer, an operating system layer, and an application layer.

[0047] See also Figure 1B The functions of each node in the blockchain system shown include:

[0048] 1) Routing: a basic function of a node, used to support communication between nodes.

[0049] In addition to the routing function, the node can also have the following functions:

[0050] 2) Applications are deployed in the blockchain to implement specific businesses based on actual business needs, record data related to the implementation of functions to form record data, carry digital signatures in the record data to indicate the source of the task data, and send the record data to other nodes in the blockchain system for other nodes to add the record data to a temporary block when they successfully verify the source and integrity of the record data.

[0051] For example, the services implemented by the application include:

[0052] 2.1) Wallet, used to provide the function of conducting electronic currency transactions, including initiating transactions (i.e., sending the transaction record of the current transaction to other nodes in the blockchain system. After successful verification by other nodes, as a response to acknowledging the validity of the transaction, the transaction record data is stored in a temporary block of the blockchain; of course, the wallet also supports querying the remaining electronic currency in the electronic currency address.

[0053] 2.2) Shared ledger, which is used to provide functions such as storage, query and modification of account data. The record data of the operation on the account data is sent to other nodes in the blockchain system. After other nodes verify the validity, as a response to acknowledging the validity of the account data, the record data is stored in a temporary block, and a confirmation can also be sent to the node that initiated the operation.

[0054] 2.3) Smart contracts are computerized protocols that can execute the terms of a contract. They are implemented by deploying code on a shared ledger that is executed when certain conditions are met. The code is used to complete automated transactions based on actual business needs, such as querying the logistics status of the goods purchased by the buyer and transferring the buyer's electronic currency to the merchant's address after the buyer signs for the goods. Of course, smart contracts are not limited to executing contracts for transactions, but can also execute contracts for processing received information.

[0055] 3) Blockchain, including a series of blocks that are connected to each other in the order of their generation. Once a new block is added to the blockchain, it will not be removed. The block records the record data submitted by the nodes in the blockchain system.

[0056] 4) Consensus is a process in the blockchain network used to reach agreement on transactions in a block among multiple nodes involved. The agreed blocks will be appended to the end of the blockchain. The mechanisms for achieving consensus include Proof of Work (PoW), Proof of Stake (PoS), Delegated Proof-of-Stake (DPoS), Proof of Elapsed Time (PoET), etc.

[0057] See also Figure 1C , Figure 1C It is an optional schematic diagram of the block structure (Block Structure) provided in the embodiment of the present application. Each block includes the hash value of the transaction record stored in this block (the hash value of this block) and the hash value of the previous block. Each block is connected by the hash value to form a blockchain. In addition, the block can also include information such as the timestamp when the block was generated. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains relevant information for verifying the validity of its information (anti-counterfeiting) and generating the next block.

[0058] The device provided in the embodiments of the present application may be implemented in the form of hardware or a combination of hardware and software. Various exemplary implementations of the device provided in the embodiments of the present application are described below.

[0059] according to Figure 2 The exemplary structure of the code issuing platform 200 shown is foreseeable for other exemplary structures of the code issuing platform 200, so the structure described here should not be considered as limiting. For example, some components described below may be omitted, or components not described below may be added to meet the special needs of certain applications.

[0060] Figure 2 The code issuing platform 200 shown includes: at least one processor 210, a memory 240, at least one network interface 220 and a user interface 230. Each component in the code issuing platform 200 is coupled together through a bus system 250. It is understood that the bus system 250 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 250 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 250 is not described in detail. Figure 2 Various buses are labeled as bus system 250 .

[0061] The user interface 230 may include a display, a keyboard, a mouse, a touch pad, a touch screen, and the like.

[0062] The memory 240 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM). The volatile memory may be a random access memory (RAM). The memory 240 described in the embodiments of the present application is intended to include any suitable type of memory.

[0063] The memory 240 in the embodiment of the present application can store data to support the operation of the code issuing platform 200. Examples of such data include: any computer program used to operate on the code issuing platform 200, such as an operating system and an application program. Among them, the operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application program can include various application programs.

[0064] As an example of the method provided in the embodiment of the present application being implemented by software, the method provided in the embodiment of the present application can be directly embodied as a combination of software modules executed by the processor 210. The software module can be located in a storage medium, and the storage medium is located in the memory 240. The processor 210 reads the executable instructions included in the software module in the memory 240, and completes the method provided in the embodiment of the present application in combination with the necessary hardware (for example, including the processor 210 and other components connected to the bus 250).

[0065] As an example, the processor 210 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0066] The method for counting the page loading time provided in the embodiment of the present application will be explained in combination with the exemplary application and implementation of the terminal provided in the embodiment of the present application.

[0067] See also Figure 3 , Figure 3 A schematic diagram of an implementation flow of the identification code verification method provided in the embodiment of the present application will be combined with Figure 3 The steps shown are explained.

[0068] Step S101: acquiring a first identification code certificate to be verified based on a request message sent by a terminal.

[0069] Here, step S101 may be performed by a code issuing platform, which may be a payment application with a payment function or a backend server of an instant messaging application, or a third-party code issuing platform, which is not specifically limited in the embodiments of the present application.

[0070] The terminal may be a mobile smart terminal such as a mobile phone, a tablet computer, a smart wearable device, etc. The terminal at least includes a display screen to display the first identification code generated based on the first identification code certificate. Various applications (App, Application) may be installed in the terminal, such as social App, shopping App, ride App, etc.

[0071] The first identification code may be a QR code. In the embodiment of the present application, the first identification code certificate may be an offline identification code certificate, that is, the first identification code certificate is not generated online in real time. The first identification code certificate may include user information, certificate generation time, signature data, etc., wherein the user information may include information such as the user's ID number, name, user ID or user ID mask, and the signature data is data signed using the private key of the code issuing platform.

[0072] The request message may be a certificate generation request or a verification request message. When the terminal sends a certificate generation request, the request message may carry a certificate identifier of the certificate requested to be generated; when the terminal sends a verification request, the request message may carry a first identification code certificate, or may also carry relevant information of the first identification code certificate, such as the generation time, city, merchant, etc. of the first identification code certificate.

[0073] Step S102: verifying the first identification code certificate based on the revocation rule corresponding to the first identification code certificate to obtain a verification result.

[0074] Here, step S102 can be implemented by the code issuing platform. The code issuing platform verifies the first identification code certificate mainly to determine whether the first identification code certificate needs to be discarded. When implementing step S102, it can be based on the generation time of the first identification code certificate to determine whether the first identification code certificate is generated within the set discarding time range. When the generation time of the first identification code certificate is within the discarding time range, a verification result of verification failure can be obtained, which indicates that the first identification code certificate needs to be discarded, and step S103 is entered. When the generation time of the first identification code certificate is not within the discarding time range, a verification result of verification passing can be obtained, which indicates that the first identification code certificate is valid.

[0075] In some embodiments, the first identification code certificate may also be verified based on the user's historical consumption records to determine whether the user is a malicious user, thereby obtaining a verification result.

[0076] In some embodiments, before step S102, it is also necessary to obtain a discarding rule through the following steps: based on the identification information of the first identification code certificate, obtain a discarding rule corresponding to the first identification code certificate. Here, since the discarding time range and validity period of different identification code certificates are often different, different identification code certificates correspond to different discarding rules. Therefore, before verifying whether the first identification code certificate needs to be discarded, it is necessary to obtain the corresponding discarding rule based on the identification information of the first identification code certificate.

[0077] Step S103: when the verification result indicates that the first identification code certificate needs to be discarded, the first identification code certificate is deleted.

[0078] Here, step S103 can be implemented by the code issuing platform or by the terminal. When the first identification code certificate is an identification code certificate stored by the code issuing platform itself, when the verification result shows that the first identification code certificate needs to be discarded, the code issuing platform deletes the first identification code certificate and enters step S104; when the first identification code certificate is stored in the terminal, when the verification result shows that the first identification code certificate needs to be discarded, the code issuing platform sends a discard notification message to the terminal, and the terminal deletes the first identification code certificate and sends a certificate generation request to the code issuing platform again.

[0079] Step S104: Generate a new first identification code certificate, and send the new first identification code certificate to the terminal.

[0080] Here, step S104 may be implemented by the code issuing platform, and step S104 may be triggered and executed automatically after step S103, or may be executed based on receiving a certificate generation request sent by the terminal.

[0081] In some embodiments, after receiving the new first identification code certificate, the terminal generates a second identification code based on the new first identification code certificate, so as to perform a subsequent payment process based on the second identification code.

[0082] In the verification method of the identification code certificate provided in the embodiment of the present application, after the code issuing platform receives the request message sent by the terminal, it obtains the first identification code certificate to be verified, and verifies the first identification code certificate to determine whether the first identification code certificate needs to be discarded. When it is determined that the first identification code needs to be discarded, the first identification code certificate is deleted, and a new first identification code certificate is generated and sent to the terminal. This avoids the situation where the user finds that the scanning fails when scanning the code and needs to re-obtain the identification code certificate and generate an identification code. This not only simplifies the operation, but also ensures that the terminal can generate a correct and valid second identification code based on the correct and valid new first identification code certificate, thereby improving payment efficiency.

[0083] In some embodiments, Figure 3 The step S101 "obtaining the first identification code certificate to be verified based on the request message sent by the terminal" shown has the following two implementation methods based on different request messages:

[0084] The first implementation manner, when the first identification code certificate is cached in the terminal, the request message is a verification request message, and the verification request message carries the first identification code certificate, can be implemented by the following step S1011a:

[0085] Step S1011a: parse the verification request message and obtain the first identification code certificate carried in the verification request message.

[0086] The second implementation mode, when the first identification code certificate is not cached in the terminal, the request message is a certificate generation request, and the certificate generation request also carries a certificate identification requested to be generated, can be implemented by the following step 1011b:

[0087] Step S1011b: Based on the certificate identifier, determine whether the first identification code certificate corresponding to the certificate identifier is stored in the device.

[0088] Step S1012b: when the first identification code certificate is stored in the system, the system obtains the first identification code certificate to be verified from its own storage space.

[0089] Here, when implementing step S1011b, it is necessary to determine whether the corresponding first identification code certificate is stored in its own storage space according to the certificate identifier. When the corresponding first identification code certificate is stored in its own storage space, the first identification code certificate to be verified is obtained from its own storage space. In some embodiments, when there is no corresponding first identification code certificate in its own storage space, the code issuing platform generates the first identification code certificate based on the certificate identifier and sends the first identification code certificate to the terminal.

[0090] In some embodiments, when the request message in step S101 is a verification request message, and the verification request message carries the first identification code certificate, such as Figure 4 As shown, after step S102, the code issuing platform may further perform the following steps:

[0091] Step S21, determining whether the verification result indicates that the first identification code certificate needs to be discarded.

[0092] Here, when the verification result is that the verification is passed, it indicates that the first identification code certificate is valid, and step S24 is entered at this time to send a verification passed response message to the terminal to notify the terminal to generate a first identification code based on the first identification code certificate; when the verification result is that the verification is failed, it indicates that the first identification code certificate needs to be discarded, and step S22 is entered at this time.

[0093] Step S22: Send a verification failure response message to the terminal to notify the terminal to delete the first identification code certificate.

[0094] Here, when the request message in step S101 is a verification request message, Figure 3 Step S103 shown may be implemented through step S22, that is, when the request message received by the code issuing platform is a verification request message, deleting the first identification code certificate is performed by the terminal when the code issuing platform sends a verification failure response message to the terminal.

[0095] Step S23: receiving a certificate generation request sent by the terminal.

[0096] like Figure 4 As shown, after receiving the certificate generation request in step S23, the process proceeds to step S104 to generate a new first identification code certificate, and send the new first identification code certificate to the terminal.

[0097] Step S24: sending a verification success response message to the terminal to notify the terminal to generate a first identification code based on the first identification code certificate.

[0098] Here, after the terminal receives the response message of successful verification, it generates a first identification code based on the first identification code certificate, and presents the first identification code for the scanning device to scan the first identification code to implement the payment process. This ensures that the identification code presented by the terminal is correct and valid, thereby improving payment efficiency and user experience.

[0099] In some embodiments, the abandonment rule at least includes that the generation time of the first identification code certificate is within the abandonment time range, and correspondingly, Figure 3 Step S102 shown in the figure, "Based on the revocation rule corresponding to the first identification code certificate, verify the first identification code certificate to obtain a verification result" can be implemented through the following steps S1021a to S1023a, and relevant explanations are given below in combination with each step.

[0100] Step S1021a, obtaining the generation time of the first identification code certificate.

[0101] Step S1022a: Based on the revocation rule, obtain the revocation time range of the first identification code certificate.

[0102] Here, the abandonment time range of the first identification code certificate may be set by the administrator of the code issuing platform according to user complaint information of the first identification code certificate and alarm information of the code issuing platform.

[0103] Step S1023a: verify the first identification code based on the generation time and the abandonment time range to obtain a verification result.

[0104] Here, when the generation time is not within the abandonment time range, a verification result of verification passing is obtained; when the generation time is within the abandonment time range, a verification result of verification passing is obtained.

[0105] For example, when the generation time of the first identification code certificate is September 1, 2019, and the abolition time range of the first identification code certificate is from August 15, 2019 to August 30, 2019, then since September 1, 2019 is within the abolition time range from August 15, 2019 to August 30, 2019, a verification result of passed is obtained at this time.

[0106] In some embodiments, the abandonment rule may also include that the number of overdue payments of the user corresponding to the terminal identifier is greater than the number threshold, and the overdue amount of the user corresponding to the terminal identifier is higher than the amount threshold. Correspondingly, Figure 3 Step S102 shown in the figure, "Based on the revocation rule corresponding to the first identification code certificate, verify the first identification code certificate to obtain a verification result" can be implemented through the following steps S1021b to S1023b, and relevant explanations are given below in combination with each step.

[0107] Step S1021b: based on the terminal identifier, obtain the historical consumption record corresponding to the terminal identifier.

[0108] Here, the terminal identifier may be a user name of an App with a payment function logged in at the terminal, or an email address, phone number, etc. when registering on the payment App.

[0109] The historical consumption records corresponding to the terminal identification can be the historical consumption records of the merchant corresponding to the first identification code, or all historical consumption records corresponding to the terminal identification. For example, if the terminal identification is the user name of the payment app, and the merchant corresponding to the first identification code is Xi'an Metro, then the historical consumption records corresponding to the terminal identification can be all consumption records of riding Xi'an Metro corresponding to the terminal identification, or all consumption records paid using the terminal identification, which can be taxi consumption records, shopping consumption records, food consumption records, etc.

[0110] Historical consumption records may include information such as consumption time, payment time, and payment amount.

[0111] Step S1022b, determining the number of overdue payments and / or the overdue payment amount based on the historical consumption records.

[0112] Here, merchants can set a payment time range, for example, payment within two days after consumption, payment within 8 hours after consumption, etc. When the user does not pay within the payment time range set by the merchant, an overdue payment occurs, and the overdue payment amount and the number of overdue payments will be recorded.

[0113] When step S1022b is implemented, whether it is overdue can be determined based on the consumption time, payment time and payment time range in the historical consumption record. For example, the payment time range is 24 hours. A historical consumption record: consumption time is 17:00 on October 1, 2019, payment time is 12:00 on October 5, 2019, and consumption amount is 128 yuan. Then according to the consumption time and payment time, it can be concluded that the payment is overdue at this time, then the number of overdue payments will be increased by 1, and the current consumption amount will be added to the overdue consumption amount.

[0114] Step S1023b: Based on the number of overdue payments and / or the overdue payment amount, the first identification code certificate is verified to obtain a verification result.

[0115] Here, when step S1023b is implemented, the first identification code certificate can be verified only based on the number of overdue payments, wherein when the number of overdue payments exceeds the number threshold, a verification result of failed verification is obtained, and when the number of overdue payments does not exceed the number threshold, a verification result of passed verification is obtained.

[0116] When implementing step S1023b, the first identification code certificate can also be verified only based on the overdue payment amount. When the overdue payment amount exceeds the amount threshold, a verification result of failed verification is obtained; when the overdue payment amount does not exceed the amount threshold, a verification result of passed verification is obtained.

[0117] When implementing step S1023b, the first identification code certificate can also be verified based on the number of overdue payments and the overdue payment amount at the same time. When the number of overdue payments exceeds the number threshold or the overdue payment amount exceeds the amount threshold, a verification result of failed verification is obtained; when the number of overdue payments does not exceed the number threshold and the overdue payment amount does not exceed the amount threshold, a verification result of passed verification is obtained.

[0118] In some embodiments, the abandonment rule may also include that the generation time of the first identification code certificate is not within the prescribed validity period. Figure 3 Step S102 shown in the figure, "Based on the revocation rule corresponding to the first identification code certificate, verify the first identification code certificate to obtain a verification result" can be implemented through the following steps S1021c to S1023c, and relevant explanations are given below in combination with each step.

[0119] Step S1021c, obtaining the generation time of the first identification code certificate.

[0120] Step S1022c: based on the revocation rule, obtain the validity period information of the first identification code certificate.

[0121] Here, after the first identification code certificate is generated, the validity period information of the first identification code certificate can be determined based on the version information of the first identification code certificate. In some embodiments, the validity period information of the first identification code certificate can also be set by the administrator of the code issuing platform.

[0122] Step S1023c: verify the first identification code based on the generation time and the validity period information to obtain a verification result.

[0123] Here, when the generation time is within the range specified by the validity period information, a verification result of verification passing is obtained; when the generation time is not within the range specified by the validity period information, a verification result of verification failing is obtained.

[0124] For example, when the generation time of the first identification code certificate is September 1, 2019, and the validity period information of the first identification code certificate is from August 15, 2019 to October 15, 2019, then since September 1, 2019 is within the specified time range of the validity period from August 15, 2019 to October 15, 2019, the verification result of verification passing is obtained at this time.

[0125] In some embodiments, the abandonment rule may further include that the version number of the first identification code certificate is lower than the preset version number, and correspondingly, Figure 3 Step S102 shown in the figure, "Based on the revocation rule corresponding to the first identification code certificate, verify the first identification code certificate to obtain a verification result" can be implemented through the following steps S1021d to S1023d, and relevant explanations are given below in combination with each step.

[0126] Step S1021d: Obtain the version number of the first identification code certificate.

[0127] Step S1022d, obtaining a preset version number specified in the discarding rule.

[0128] Here, the preset version number may be set by the administrator of the code issuing platform, and further, may be set by the administrator according to user complaint information of the first identification code certificate and alarm information of the code issuing platform.

[0129] Step S1023d: verify the first identification code based on the version number of the first identification code certificate and the preset version number to obtain a verification result.

[0130] Here, when the version number of the first identification code certificate is higher than or equal to the preset version number, a verification result of verification passing is obtained, and when the version number of the first identification code certificate is lower than the preset version number, a verification result of verification failing is obtained.

[0131] For example, the preset version number is v5.2.1, and the version number of the first identification code certificate is v4.3.1. Since the version number of the first identification code certificate is lower than the preset version number, a verification result of failed verification is obtained.

[0132] It should be noted that, when implementing step S102, any one of the above methods may be adopted, or any combination of two or more of the above methods may be adopted.

[0133] In some embodiments, the discarding rule may also be updated by the following steps:

[0134] Step S31: receiving an edit operation on a discarding rule.

[0135] Here, the editing operation of the discarding rule may be adding a discarding rule, deleting a discarding rule, modifying a discarding rule, and the like.

[0136] Step S32: in response to the editing operation, updating the discarding rule.

[0137] Here, when implementing step S32, in response to the editing operation on the discarding rule, the original discarding rule before receiving the editing operation is added, deleted or modified to obtain the updated discarding rule.

[0138] Based on the above-mentioned embodiments, the present application further provides a method for verifying an identification code, which is applied to the network architecture shown in FIG. 1 . Figure 5 A schematic diagram of another implementation flow of the verification method of the example identification code for the present application is shown as follows: Figure 5 As shown, the method includes:

[0139] Step S501: The user terminal receives an operation of displaying a first identification code.

[0140] Here, in the embodiment of the present application, the first identification code is used as the boarding code for relevant description. When step S501 is implemented, the operation of displaying the first identification code can be the operation of opening the boarding code applet, and the boarding code applet can be a web program installed in a payment application, a map application, or an instant messaging application that can generate a boarding code. In some embodiments, the operation of displaying the first identification code can also be the operation of clicking on the electronic boarding card in the card bag in the payment application, or the operation of opening a dedicated boarding app to display the first identification code.

[0141] Step S502: The user terminal determines whether it has stored a first identification code certificate based on the operation.

[0142] Here, when the user terminal itself does not store the first identification code certificate, it proceeds to step S503 to send a certificate generation request to the code issuing platform; when the user terminal itself stores the first identification code certificate, it proceeds to step S505 to send a verification request to the code issuing platform.

[0143] Step S503: the user terminal sends a certificate generation request to the code issuing platform.

[0144] Here, the certificate generation request carries a terminal identifier.

[0145] Step S504: the code issuing platform determines whether it has stored the first identification code certificate.

[0146] Here, when the code issuing platform itself stores the first identification code certificate, the process proceeds to step S506; when the code issuing platform itself does not store the first identification code certificate, the process proceeds to step S510 to generate the first identification code certificate.

[0147] Step S505: The user terminal sends a verification request message to the code issuing platform.

[0148] Here, the signature verification request message carries the first identification code certificate and the terminal identification.

[0149] Step S506: the code issuing platform obtains the abandonment rule.

[0150] Here, the abandonment rules can be pre-set, for example, the generation time of the first identification code certificate can be within the abandonment time range, or the generation time of the first identification code certificate can be not within the time range specified by the validity period information, or the number of overdue payments in the consumption record corresponding to the terminal identification is not greater than the number threshold, the overdue payment amount is not greater than the amount threshold, and so on.

[0151] Step S507: the code issuing platform verifies the first identification code certificate based on the abandonment rule corresponding to the first identification code certificate to obtain a verification result.

[0152] Here, when step S507 is implemented, when it is determined that the first identification code certificate does not meet the conditions specified by the abandonment rules, a verification result of verification passing is obtained, which indicates that the first identification code certificate is valid; when it is determined that the first identification code certificate meets the conditions specified by the abandonment rules, a verification result of verification failing is obtained, which indicates that the first identification code certificate needs to be abandoned.

[0153] Step S508: The code issuing platform determines whether the first identification code certificate needs to be discarded based on the verification result.

[0154] Here, when it is determined that the first identification code certificate stored by the code issuing platform itself needs to be discarded, step S509 is entered; when it is determined that the first identification code certificate stored by the code issuing platform itself does not need to be discarded, step S511 is entered; when it is determined that the first identification code certificate stored by the user terminal needs to be discarded, step S509' is entered, and the code issuing platform sends a response message of verification failure to the user terminal to notify the user terminal to delete the first identification code certificate; when it is determined that the first identification code certificate stored by the code issuing platform itself does not need to be discarded, step S511' is entered.

[0155] Step S509: the code issuing platform deletes the first identification code certificate.

[0156] Step S509': the user terminal deletes the first identification code certificate based on the received verification failure response message, and sends a certificate generation request to the code issuing platform.

[0157] Step S510: The code issuing platform generates a new first identification code certificate.

[0158] Step S511: the code issuing platform sends the first identification code certificate to the user terminal.

[0159] Here, in step S511, the first identification code certificate sent by the code issuing platform to the user terminal is correct and valid, so that the first identification code that can be normally recognized by the scanning device can be generated.

[0160] Step S511', the code issuing platform sends a verification success response message to the user terminal.

[0161] Here, the code issuing platform sends a verification success response message to the user terminal to notify the terminal that the first identification code certificate is valid and the first identification code can be directly generated.

[0162] Step S512: The user terminal generates a first identification code based on the first identification code certificate, and displays the first identification code.

[0163] Here, the user terminal generates and displays the first identification code for scanning by the scanning device to perform the subsequent payment process.

[0164] Step S513: The scanning device scans the first identification code and obtains the scanned information.

[0165] Here, the scanned information may include payment information, user account information, etc.

[0166] Step S514: The scanning device sends the scanned information to the code issuing platform.

[0167] Step S515: the code issuing platform deducts fees based on the scanned information.

[0168] Here, the code issuing platform deducts and settles the user's account information based on the payment amount in the payment information.

[0169] Step S516: The code issuing platform sends the deduction success information to the user terminal.

[0170] Here, when the user account information is successfully deducted, the code issuing platform sends the deduction success information to the user terminal. In some embodiments, when the user account information is deducted unsuccessfully, the code issuing platform sends the deduction failure information to the user terminal. The code issuing platform can also send the deduction failure information to the scanning device. When the scanning device is a gate at a subway station, after receiving the deduction failure information, the scanning device can control the gate to close to prevent passengers from escaping.

[0171] In the verification method of the identification code certificate provided in the embodiment of the present application, no matter whether the first identification code certificate is stored in the user terminal or in the code issuing platform, before generating the first identification code based on the first identification code certificate, the code issuing platform will verify the first identification code certificate according to the abandonment rule to determine whether the first identification code certificate needs to be abandoned, and generate a new first identification code certificate, so as to generate a correct and valid first identification code to ensure that the subsequent payment process can be smoothly executed and improve payment efficiency.

[0172] The following is an explanation of an exemplary application of an embodiment of the present application in a practical application scenario.

[0173] In the embodiment of the present application, the identification code is taken as a boarding code as an example for explanation.

[0174] The user's mini program stores card certificates that can be used offline and are used to generate QR codes offline. The ride code backend (that is, the code issuing platform) also caches card certificates. When the user's mini program requests the generation of a card certificate, the ride code backend will give priority to returning the card certificate in its own cache. However, in some scenarios, it is necessary to promptly discard the card certificate cached in the ride code backend or the user's mini program, such as when the user is a high-risk user, when there is a problem with the cached offline card certificate that requires triggering the generation of a new card certificate, or when the offline card certificate requires a functional upgrade.

[0175] Figure 6 This is a schematic diagram of an implementation flow of the verification method of the boarding code certificate of the embodiment of the present application. Figure 6 In the method flow chart shown, the devices for information interaction include: user terminal and boarding code background, and the user terminal includes boarding code applet 661, and the boarding code background includes: boarding code card certificate management device 662, boarding code card certificate abandonment device 663, card certificate storage device 664, boarding code card certificate generation device 665, boarding code card certificate abandonment rule storage device 666, boarding code card certificate abandonment rule management platform 667. Figure 6 Each step is explained.

[0176] Step S601, the boarding code applet sends a generation request to the boarding code card certificate management device when the card certificate is not stored locally, or sends a judgment request to the boarding code card certificate management device when the card certificate is stored locally.

[0177] Here, if there is a card certificate on the mini program side, then every time the user opens the mini program, a judgment request will be initiated to the card certificate management device to determine whether the offline card certificate is invalid. At this time, after step S601, step S603 is directly entered.

[0178] Step S602, the boarding code card certificate management device queries the card certificate storage device whether there is an available cached card certificate.

[0179] Here, if the card certificate storage device has a card certificate, go to step S603; if the card certificate storage device does not store the corresponding card certificate, then go to step S605, the boarding code card certificate management background directly calls the card certificate generation device, and the generation device generates a new card certificate.

[0180] Step S603, the boarding code card certificate management device sends the card certificate to the boarding code card certificate discarding device.

[0181] Step S604: the card certificate revocation device reads the revocation rule to determine whether the cached card certificate has been revoked.

[0182] Here, if it is determined that the cached card certificate is discarded, step S605 is entered; if the cached card certificate is not discarded, the boarding code card certificate management device returns the certificate directly to the mini program end for use.

[0183] In the embodiment of the present application, if the card certificate discarding device determines that the card certificate requested by the boarding code applet needs to be discarded, a discarding instruction is sent back to the boarding code applet, and the boarding code applet deletes the offline card certificate cached locally, and again initiates a generation request to the boarding code card certificate management device to request the generation of a new card certificate, and executes step S602 and subsequent steps. At this time, if the boarding code card certificate management device determines that the card certificate cached in the card certificate storage device also hits the discarding rule, then the boarding code card certificate management device will not return the discarded cached card certificate to the boarding code applet, but will call the boarding code card certificate generation device, and finally generate a new card certificate and return it to the boarding code applet.

[0184] Step S605, the boarding code card certificate management device calls the boarding code card certificate generation device to generate a new card certificate.

[0185] Step S606, the boarding code card certificate generating device stores the newly generated card certificate into the card certificate storing device, and returns the new card certificate to the mini program for use.

[0186] Step S607: the card certificate revocation management platform adds, deletes, modifies and checks the revocation rules.

[0187] Figure 7 This is another implementation flow diagram of the method for verifying the boarding code certificate in the embodiment of the present application, such as Figure 7 As shown, the method includes:

[0188] Step S701, the user opens the ride code applet and determines whether the user has a card certificate stored.

[0189] Here, in the embodiment of the present application, if there is already a card certificate on the ride code mini program side, at this time for some reasons, such as the card certificate is at risk, or the card certificate needs to be upgraded, etc., it is necessary to discard the user's offline card certificate on the ride code mini program side in advance. When there is no card certificate, go to step S702.

[0190] When the ride code applet stores the card certificate, proceed to step S713.

[0191] Step S702, the boarding code applet sends an offline card certificate generation request to the boarding code card certificate management device.

[0192] Step S703, after receiving the request to generate an offline card certificate, the card certificate management device first requests the card certificate storage device to determine whether there is an available cached card certificate.

[0193] Step S704: the card certificate storage device determines whether there is an available cached card certificate.

[0194] Here, if there is an available card certificate in the card certificate storage device, the process proceeds to step S705, where the card certificate storage device sends the card certificate to the boarding code card certificate management device. If there is no available cached card certificate in the card certificate storage device, the process proceeds to step S709.

[0195] Step S705, the card certificate storage device sends the card certificate to the boarding code card certificate management device.

[0196] Step S706, the boarding code card certificate management device sends the card certificate to the boarding code card certificate revoking device to request the boarding code card certificate revoking device to determine whether the card certificate needs to be revoked.

[0197] Step S707, the boarding code card certificate discarding device reads the discarding rule from the boarding code card certificate discarding rule storage device to determine whether the cached card certificate needs to be discarded.

[0198] Abandonment rules can be added, deleted, modified and checked through the card certificate abandonment management platform.

[0199] Step S708: If the boarding code card certificate discarding device determines that the cached card certificate needs to be discarded, a notification message of discarding the card certificate is sent to the boarding code card certificate management device.

[0200] Step S709, the boarding code card certificate management device calls the boarding code card certificate generation device to generate a new card certificate.

[0201] Step S710, the boarding code card certificate generating device stores the newly generated card certificate in the card certificate storage device, and returns the new card certificate to the mini program for use.

[0202] Step S711: If the boarding code card certificate discarding device determines that the cached card certificate does not need to be discarded, a notification message that the card certificate is valid is sent to the boarding code card certificate management device.

[0203] Step S712: The boarding code card certificate management device directly returns the card certificate to the mini program end for use.

[0204] Step S713, the boarding code applet initiates a judgment request to the boarding code card certificate management device to determine whether the offline card certificate is invalid.

[0205] Here, the request parameters will carry the key information of the offline card certificate, such as the city merchant, the start time of the card certificate validity period, and the result time.

[0206] Step S714, the boarding code card certificate management device calls the boarding code card certificate revocation device to determine whether the card certificate needs to be revoked.

[0207] Step S715, the boarding code card certificate revocation device reads the revocation rule from the boarding code card certificate revocation rule storage device to determine whether the cached card certificate needs to be revoked.

[0208] Step S716: If the boarding code card certificate discarding device determines that the cached card certificate needs to be discarded, a notification message of discarding the card certificate is sent to the boarding code card certificate management device.

[0209] Step S717, the boarding code card certificate management device sends a cancellation instruction back to the boarding code mini program end.

[0210] Step S718, the ride code applet deletes the locally cached offline card certificate.

[0211] Here, after deleting the offline card certificate cached locally, the boarding code applet enters step S702 and initiates a generation request to the boarding code card certificate management device to request the generation of a new card certificate.

[0212] In the above-mentioned verification method of the boarding code certificate, the user's boarding code applet caches the card certificate with offline function. In some special scenarios, these cached card certificates need to be discarded in time, such as when the user is a high-risk user, when there is a problem with the user's offline cached card certificate and a new card certificate needs to be generated, or when the user's offline card certificate needs a functional upgrade. Through the convenient operation and management of the discarding rules of the boarding code card certificate discarding rule management platform, each time the user opens the applet for use, a card certificate discarding judgment request will be triggered. The request can be reasonably operated by the entire set of devices such as the boarding code card certificate management device, the boarding code card certificate discarding device, and the boarding code card certificate generation device, so that the offline card certificate of the user's applet can be discarded in time, and a new card certificate can be issued back to the applet to ensure the validity and correctness of the card certificate.

[0213] The following is a description of an exemplary structure of an identification code verification device 80 (hereinafter referred to as verification device) provided in an embodiment of the present application implemented as a software module. In some embodiments, for example, Figure 2 As shown, the software modules stored in the verification device 80 of the memory 240 may include:

[0214] A first acquisition module 81, configured to acquire a first identification code certificate to be verified based on a request message sent by a terminal;

[0215] A verification module 82, configured to verify the first identification code certificate based on a revocation rule corresponding to the first identification code certificate to obtain a verification result;

[0216] A deleting module 83, configured to delete the first identification code certificate when the verification result indicates that the first identification code certificate needs to be discarded;

[0217] The first generating module 84 is configured to generate a new first identification code certificate and send the new first identification code certificate to the terminal.

[0218] In some embodiments, when the request message is a verification request message, and the verification request message carries a first identification code certificate,

[0219] The first acquisition module 81 is further used for:

[0220] Parse the verification request message to obtain the first identification code certificate carried in the verification request message.

[0221] In some embodiments, the request message is a certificate generation request, and the certificate generation request carries a certificate identifier requested to be generated.

[0222] The first acquisition module 81 is further used for:

[0223] Based on the certificate identifier, determining whether a first identification code certificate corresponding to the certificate identifier is stored in the device;

[0224] When the first identification code certificate is stored in the system, the first identification code certificate to be verified is obtained from the storage space of the system.

[0225] In some embodiments, the verification device further comprises:

[0226] A third generating module, configured to generate a first identification code certificate based on the certificate identifier when the first identification code certificate is not stored in the module itself;

[0227] The third sending module is used to send the first identification code certificate to the terminal.

[0228] In some embodiments, the verification device further comprises:

[0229] A first sending module, configured to send a verification failure response message to the terminal when the verification result indicates that the first identification code certificate needs to be discarded, so as to notify the terminal to delete the first identification code certificate;

[0230] A first receiving module, used to receive a certificate generation request sent by a terminal;

[0231] The second generating module is used to generate a new first identification code certificate based on the certificate generation request, and send the new first identification code certificate to the terminal.

[0232] In some embodiments, the verification device further comprises:

[0233] The second sending module is configured to send a verification success response message to the terminal when the verification result indicates that the first identification code certificate is valid, so as to notify the terminal to generate a first identification code based on the first identification code certificate.

[0234] In some embodiments, the verification device further comprises:

[0235] The second acquisition module is used to acquire a discarding rule corresponding to the first identification code certificate based on the identification information of the first identification code certificate.

[0236] In some embodiments, the verification device further comprises:

[0237] A second receiving module, used for receiving an edit operation on a discarded rule;

[0238] An updating module is used to update the discarding rule in response to the editing operation.

[0239] In some embodiments, the verification module 82 is further configured to:

[0240] Obtaining the generation time of the first identification code certificate;

[0241] Based on the abandonment rule, obtaining an abandonment time range for the first identification code certificate;

[0242] The first identification code is verified based on the generation time and the abandonment time information, wherein when the generation time is within the abandonment time range, a verification result of failed verification is obtained; when the generation time is not within the abandonment time range, a verification result of passed verification is obtained.

[0243] In some embodiments, the verification module 82 is further configured to:

[0244] Obtaining historical consumption records corresponding to the terminal, and obtaining a number threshold and / or amount threshold based on a discarding rule;

[0245] Determine the number of overdue payments and / or the overdue payment amount based on the historical consumption records;

[0246] The first identification code certificate is verified based on the number of overdue payments and / or the overdue payment amount, wherein when the number of overdue payments exceeds a number threshold and / or the overdue payment amount exceeds an amount threshold, a verification result indicating that the verification failed is obtained.

[0247] In some embodiments, the verification module 82 is further configured to:

[0248] Obtaining the generation time of the first identification code certificate;

[0249] Based on the abandonment rule, obtaining validity period information of the first identification code certificate;

[0250] Based on the generation time and the validity period information, the first identification code is verified to obtain a verification result, wherein when the generation time is within the specified range of the validity period information, a verification result of passed verification is obtained; when the generation time is not within the specified range of the validity period information, a verification result of failed verification is obtained.

[0251] In some embodiments, the verification module 82 is further configured to:

[0252] Obtaining the version number of the first identification code certificate;

[0253] Obtaining a preset version number specified in the deprecation rule;

[0254] Based on the version number of the first identification code certificate and the preset version number, the first identification code is verified to obtain a verification result, wherein when the version number of the first identification code certificate is higher than or equal to the preset version number, a verification result of passed verification is obtained, and when the version number of the first identification code certificate is lower than the preset version number, a verification result of failed verification is obtained.

[0255] The embodiment of the present application provides a storage medium storing executable instructions, wherein the executable instructions are stored. When the executable instructions are executed by a processor, the processor will execute the method provided by the embodiment of the present application, for example, Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 The method shown.

[0256] In some embodiments, the storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EE PROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.

[0257] In some embodiments, executable instructions may be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.

[0258] As an example, executable instructions may, but need not, correspond to a file in a file system, may be stored as part of a file storing other programs or data, for example, in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (for example, files storing one or more modules, subroutines, or code portions).

[0259] By way of example, executable instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one site, or on multiple computing devices distributed across multiple sites and interconnected by a communication network.

[0260] The above is only an embodiment of the present application and is not intended to limit the protection scope of the present application. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A method for verifying a boarding code card certificate, characterized in that: include: Receiving a verification request message about the boarding code card certificate sent by the terminal, and acquiring the boarding code card certificate to be verified based on the verification request message, wherein the verification request message is generated and sent by the terminal in response to an operation of opening the boarding code when there is a boarding code card certificate cached locally in the terminal, and the boarding code card certificate is used by the terminal to generate a boarding code offline locally in the terminal, and the boarding code is used for scanning by a scanning device to make a boarding payment; Obtaining the discarding rule of the boarding code card certificate, and verifying the boarding code card certificate to be verified based on the discarding rule to obtain a verification result; When the verification result indicates that the to-be-verified boarding code card certificate needs to be discarded, a discard notification message is sent to the terminal to notify the terminal to delete the locally cached boarding code card certificate and then send a certificate generation request; Receiving a certificate generation request sent by the terminal, generating a new boarding code card certificate according to the certificate generation request, and sending the new boarding code card certificate to the terminal to instruct the terminal to generate a boarding code offline locally at the terminal according to the boarding code card certificate; When the verification result indicates that the boarding code card certificate to be verified is valid, a verification passed response message is sent to the terminal to notify the terminal to generate a boarding code offline locally at the terminal according to the boarding code card certificate.

2. The method according to claim 1, characterized in that The method further comprises: Receiving a certificate generation request sent by the terminal, wherein the certificate generation request is generated and sent by the terminal in response to an operation of opening the boarding code when there is no boarding code card certificate locally at the terminal, and the certificate generation request carries a certificate identifier requested to be generated; Based on the certificate identifier, determine whether the bus code card certificate corresponding to the certificate identifier is stored in the bus code card; When the corresponding boarding code card certificate is stored in itself, the boarding code card certificate is obtained from its own storage space, and the obtained boarding code card certificate is used as the boarding code card certificate to be verified using the discard rule for verification.

3. The method according to claim 2, characterized in that The method further comprises: When the corresponding boarding code card certificate is not stored in the system, a boarding code card certificate is generated based on the certificate identifier; The boarding code card certificate is sent to the terminal.

4. The method according to claim 1, characterized in that The discarding rules for obtaining the boarding code card certificate include: Based on the identification information of the boarding code card certificate to be verified, the discarding rule corresponding to the boarding code card certificate to be verified is obtained.

5. The method according to claim 1, characterized in that The method further comprises: receiving an edit operation on a discarded rule; In response to the editing operation, the discarding rule is updated.

6. The method according to any one of claims 1 to 5, characterized in that The step of verifying the to-be-verified boarding code card certificate based on the abandonment rule to obtain a verification result includes: Obtaining the generation time of the boarding code card certificate to be verified; Based on the abandonment rule, obtaining the abandonment time range of the boarding code card certificate to be verified; When the generation time is within the abandonment time range, obtaining a verification result indicating that the verification has failed; When the generation time is not within the abandonment time range, a verification result indicating that the verification is passed is obtained.

7. The method according to any one of claims 1 to 5, characterized in that The step of verifying the to-be-verified boarding code card certificate based on the abandonment rule to obtain a verification result includes: Obtaining historical consumption records corresponding to the terminal, and obtaining a number threshold and / or amount threshold based on a discarding rule; Determine the number of overdue payments and / or the overdue payment amount based on the historical consumption records; When the number of overdue payments exceeds the number threshold and / or the overdue payment amount exceeds the amount threshold, a verification result indicating that the verification has failed is obtained; When the number of overdue payments does not exceed the number threshold and / or the overdue payment amount does not exceed the amount threshold, a verification result of passed verification is obtained.

8. The method according to any one of claims 1 to 5, characterized in that The step of verifying the to-be-verified boarding code card certificate based on the abandonment rule to obtain a verification result includes: Obtaining the generation time of the boarding code card certificate to be verified; Based on the abandonment rule, obtaining the validity period information of the boarding code card certificate to be verified; When the generation time is within the range specified by the validity period information, a verification result of passing the verification is obtained; When the generation time is not within the specified range of the validity period information, a verification result indicating that the verification has failed is obtained.

9. The method according to any one of claims 1 to 5, characterized in that The step of verifying the to-be-verified boarding code card certificate based on the abandonment rule to obtain a verification result includes: Obtain the version number of the boarding code card certificate to be verified; Obtaining a preset version number specified in the deprecation rule; When the version number of the boarding code card certificate to be verified is higher than or equal to the preset version number, a verification result of verification passing is obtained; When the version number of the boarding code card certificate to be verified is lower than the preset version number, a verification result indicating that the verification failed is obtained.

10. A verification device for a boarding code card certificate, characterized in that: include: A first acquisition module is used to receive a verification request message about a boarding code card certificate sent by a terminal, and acquire the boarding code card certificate to be verified based on the verification request message. The verification request message is generated and sent by the terminal in response to an operation of opening a boarding code when there is a boarding code card certificate cached locally in the terminal. The boarding code card certificate is used by the terminal to generate a boarding code offline locally in the terminal, and the boarding code is used for scanning by a scanning device to make a boarding payment; A verification module, used for obtaining a discarding rule of the boarding code card certificate, and based on the discarding rule, verifying the boarding code card certificate to be verified to obtain a verification result; A deletion module, used for sending a discard notification message to the terminal when the verification result indicates that the boarding code card certificate to be verified needs to be discarded, so as to notify the terminal to delete the boarding code card certificate cached locally and then send a certificate generation request; A first generating module is used to receive a certificate generation request sent by the terminal, generate a new boarding code card certificate according to the certificate generation request, and send the new boarding code card certificate to the terminal to instruct the terminal to generate a boarding code locally offline at the terminal according to the boarding code card certificate; The first sending module is used to send a verification passed response message to the terminal when the verification result shows that the boarding code card certificate to be verified is valid, so as to notify the terminal to generate a boarding code offline locally at the terminal according to the boarding code card certificate.

11. The device according to claim 10, characterized in that The first acquisition module is further used to receive a certificate generation request sent by the terminal, wherein the certificate generation request is generated and sent by the terminal in response to an operation of opening the boarding code when there is no boarding code card certificate locally at the terminal, and the certificate generation request carries a certificate identifier requested to be generated; Based on the certificate identifier, determine whether the bus code card certificate corresponding to the certificate identifier is stored in the bus code card; When the corresponding boarding code card certificate is stored in itself, the boarding code card certificate is obtained from its own storage space, and the obtained boarding code card certificate is used as the boarding code card certificate to be verified using the discard rule for verification.

12. The device according to claim 11, characterized in that The first acquisition module is also used to generate a boarding code card certificate based on the certificate identifier when the corresponding boarding code card certificate is not stored in the first acquisition module; and send the boarding code card certificate to the terminal.

13. The device according to claim 10, characterized in that The verification module is also used to obtain the discarding rule corresponding to the boarding code card certificate to be verified based on the identification information of the boarding code card certificate to be verified.

14. The device according to claim 10, characterized in that The device also includes: The second acquisition module is used to receive an editing operation on a discarding rule; and update the discarding rule in response to the editing operation.

15. The device according to any one of claims 10 to 14, characterized in that The verification module is also used to obtain the generation time of the boarding code card certificate to be verified; based on the abandonment rule, obtain the abandonment time range of the boarding code card certificate to be verified; when the generation time is within the abandonment time range, obtain a verification result of failed verification; when the generation time is not within the abandonment time range, obtain a verification result of passed verification.

16. The device according to any one of claims 10 to 14, characterized in that The verification module is also used to obtain the historical consumption records corresponding to the terminal, and obtain the number threshold and / or amount threshold based on the abandonment rule; determine the number of overdue payments and / or the overdue payment amount according to the historical consumption records; when the number of overdue payments exceeds the number threshold and / or the overdue payment amount exceeds the amount threshold, a verification result of failed verification is obtained; when the number of overdue payments does not exceed the number threshold and / or the overdue payment amount does not exceed the amount threshold, a verification result of passed verification is obtained.

17. The device according to any one of claims 10 to 14, characterized in that The verification module is also used to obtain the generation time of the boarding code card certificate to be verified; based on the abandonment rule, obtain the validity information of the boarding code card certificate to be verified; when the generation time is within the specified range of the validity information, obtain a verification result of passed verification; when the generation time is not within the specified range of the validity information, obtain a verification result of failed verification.

18. The device according to any one of claims 10 to 14, characterized in that The verification module is further used to obtain the version number of the boarding code card certificate to be verified; obtain the preset version number specified in the abandonment rule; when the version number of the boarding code card certificate to be verified is higher than or equal to the preset version number, obtain a verification result of verification passing; When the version number of the boarding code card certificate to be verified is lower than the preset version number, a verification result indicating that the verification failed is obtained.

19. A verification device for a boarding code card certificate, characterized in that: include: A memory for storing executable instructions; A processor, configured to implement the method according to any one of claims 1 to 9 when executing the executable instructions stored in the memory.

20. A storage medium, characterized in that: Executable instructions are stored, which are used to cause a processor to execute and implement the method described in any one of claims 1 to 9.

Images