CN114595853A - Method, device, equipment and medium for sending and displaying graphic code data - Google Patents
Method, device, equipment and medium for sending and displaying graphic code data Download PDFInfo
- Publication number
- CN114595853A CN114595853A CN202210445337.8A CN202210445337A CN114595853A CN 114595853 A CN114595853 A CN 114595853A CN 202210445337 A CN202210445337 A CN 202210445337A CN 114595853 A CN114595853 A CN 114595853A
- Authority
- CN
- China
- Prior art keywords
- graphic code
- code data
- client
- account
- acquisition
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/36—User authentication by graphic or iconic representation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A90/00—Technologies having an indirect contribution to adaptation to climate change
- Y02A90/10—Information and communication technologies [ICT] supporting adaptation to climate change, e.g. for weather forecasting or climate simulation
Abstract
The embodiment of the specification provides a method, a device, equipment and a medium for sending and displaying graphic code data. The method can comprise the steps of receiving a request for acquiring the graphic code data sent by a client of a user account; the graphic code data is used for generating a graphic code; the graphical code represents validation data of acquisition eligibility for a specified resource; determining a target time of the user account for acquiring qualification of the specified resource and a request time corresponding to the acquisition request; under the condition that the time between the request time and the target time is within a specified duration range, generating graph code data; and sending the graphic code data to a client of the user account so that the client displays the graphic code represented by the graphic code data. By controlling the sending time of the graphic code data, the effect of enhancing the protection of the graphic code and the information protection expressed by the graphic code is achieved.
Description
Technical Field
The present disclosure relates to the field of computer internet technologies, and in particular, to a method, an apparatus, a device, and a storage medium for sending and displaying graphic code data.
Background
In real life, some users need to make a reservation to obtain a reservation certificate, and then go to the site actually, and check the identity by means of the obtained reservation certificate. Specifically, for example, the user may make a reservation to visit a museum, or may be vaccinated, or the like.
Please refer to fig. 1. For example, the supply of a nine-valent cervical cancer vaccine for women aged 16 to 26 years has attracted much attention in recent years, and even many people reflect that the vaccine has been queued for vaccination for more than half a year. The hospital can issue a certain amount of cervical cancer vaccine reservation resources on a network platform, and people who acquire the vaccination qualification go to the hospital to be vaccinated at a specified place at a specified time. The cervical cancer vaccine resource is in short supply, and a large number of people can contend for reservation qualification every time the hospital issues the cervical cancer vaccine reservation resource. The situation that the supply of the cervical cancer vaccine resource is short-pending causes the occurrence of the event that people resale the vaccine resource. The reseller robs the cervical cancer vaccination qualification issued by hospitals through various modes and then sells the cervical cancer vaccination qualification to common people at high price. The appearance of the reseller almost monopolizes the vaccine market, so that the common population cannot obtain fair cervical cancer vaccine inoculation qualification, and one part of people abandons the vaccination and one part of people spend high price to purchase the cervical cancer vaccine reservation qualification.
Please refer to fig. 2, fig. 3 and fig. 4. After the reseller acquires the inoculation qualification, the client used by the reseller can acquire a short message for successful reservation or a reservation platform displays that the reservation is successful. The reseller sends the short message of successful reservation or the screenshot of successful reservation displayed by the reservation platform to the high-price purchasing crowd to gain a profit. The purchasing crowd carries the short message with successful reservation or the reservation platform displays the screenshot with successful reservation to go to the appointed hospital, the doctor checks and sells the reservation code or the static graphic code on the short message or the screenshot, and the vaccine is inoculated after the check and the sale are successful. In the past, the common population cannot obtain the cervical cancer vaccine resources fairly and equitably, and the reseller obtains violence from the cervical cancer vaccine resources, disturbs the market and breaks the order of fair competition.
Disclosure of Invention
In view of the above, embodiments of the present disclosure are directed to providing a method, an apparatus, a device, and a storage medium for sending and displaying graphic code data, which may reduce the possibility of transferring a subscription certificate to some extent.
An embodiment of the present specification provides a method for sending pattern code data, including: receiving a request for acquiring graphic code data sent by a client of a user account; the graphic code data is used for generating a graphic code; the graphical code representing verification data of acquisition eligibility for a specified resource; determining a target time of the user account for acquiring qualification of the specified resource and a request time corresponding to the acquisition request; under the condition that the time between the request time and the target time is within a specified duration range, generating graph code data; and sending the graphic code data to a client of the user account so that the client displays the graphic code represented by the graphic code data.
An embodiment of the present specification provides a method for displaying a graphic code, including: obtaining an acquisition qualification for the specified resource; wherein the acquisition eligibility has a target time; displaying the graphic code corresponding to the acquisition qualification only when the current time and the target time are within a specified time range; wherein the graphic code carries verification data representing the acquisition eligibility.
An embodiment of the present specification provides a method for sending pattern code data, including: in the case of receiving an acquisition request for a specified resource sent by a client of a first account, allocating acquisition qualification for the specified resource to the first client; wherein the acquisition qualification is to be used as a credential to acquire the specified resource; under the condition that a starting instruction aiming at the first account and sent by a client side of a second account is received, generating graphic code data used for verifying the first account; wherein the start instruction represents permission to send graphic code data to the client of the first account; and sending the graphic code data to the client of the first account.
An embodiment of the present specification provides a method for sending pattern code data, including: determining a first account eligible for acquisition for a specified resource; sending a starting instruction aiming at the first account to a server; the starting instruction is used for instructing the server to send the graphic code data for verifying the first account to the client of the first account.
The embodiment of the present specification provides a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the method of the foregoing embodiment when executing the computer program.
The present specification embodiment proposes a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the method of the foregoing embodiment.
The embodiment of the specification realizes the control of the generation time of the graphic code by the way that the server determines that the graphic code data is generated under the condition that the time between the request time and the target time is within the specified time range. Thus, the graphic code is used as a certificate, and the graphic code also needs to be displayed within a specified time range from the target time. Thus, by controlling the possible presentation time of the graphic code, the possibility that the graphic code is transferred as a certificate is reduced.
Drawings
Fig. 1 is a schematic flow chart of the prior art provided in the present specification.
Fig. 2 is a schematic diagram of a page with successful reservation in the prior art provided in this specification.
Fig. 3 is a schematic diagram of an electronic device including a display interface in the prior art provided in the present specification.
Fig. 4 is a schematic diagram of an electronic device including a display interface in the prior art provided in the present specification.
Fig. 5 is a schematic diagram illustrating a reservation success page provided in an exemplary scenario of the present specification.
Fig. 6 is a schematic diagram illustrating a graphic code provided in an example scenario of the present specification.
Fig. 7 is a schematic diagram illustrating a graphic code provided in an example of a scenario of the present specification.
Fig. 8 is a schematic diagram illustrating a reservation success page provided in an exemplary scenario of the present specification.
Fig. 9 is a schematic diagram illustrating a list of reserved vaccines provided in an exemplary scenario of the present specification.
Fig. 10 is a schematic diagram illustrating a list of reserved vaccines provided in an exemplary scenario of the present specification.
Fig. 11 is a schematic diagram illustrating a graphic code provided in an example scenario of the present specification.
Fig. 12 is a schematic diagram illustrating a system for transmitting graphic code data according to an embodiment of the present disclosure.
Fig. 13 is a multi-terminal interaction diagram illustrating a method for transmitting graphic code data according to an embodiment of the present disclosure.
Fig. 14 is a flowchart illustrating a method of transmitting graphic code data according to an embodiment of the present specification.
Fig. 15 is a schematic view of an electronic device displaying reservation information according to an embodiment of the present disclosure.
Fig. 16 is a schematic diagram of an electronic device displaying a graphic code according to an embodiment of the present disclosure.
Fig. 17 is a flowchart illustrating a method for displaying a graphic code according to an embodiment of the present disclosure.
Fig. 18 is a schematic diagram illustrating a system for transmitting graphic code data according to an embodiment of the present disclosure.
Fig. 19 is a diagram illustrating a method for transmitting graphic code data according to an embodiment of the present specification.
Fig. 20 is a multi-terminal interactive view illustrating a method for transmitting graphic code data according to an embodiment of the present specification.
Fig. 21 is a multi-terminal interactive view illustrating a method for transmitting graphic code data according to an embodiment of the present specification.
Fig. 22 is a flowchart illustrating a method of transmitting graphic code data according to an embodiment of the present specification.
Fig. 23 is a schematic diagram showing a transmitting apparatus of graphic code data according to an embodiment of the present specification.
Fig. 24 is a schematic view illustrating a graphic code display device according to an embodiment of the present disclosure.
Fig. 25 is a schematic diagram showing a transmitting apparatus for graphic code data according to an embodiment of the present disclosure.
Fig. 26 is a schematic diagram showing a transmitting apparatus for graphic code data according to an embodiment of the present specification.
Fig. 27 is a functional diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
In order to make the technical solution of the present invention better understood, the technical solution of the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art without any inventive work based on the embodiments in the present specification belong to the protection scope of the present specification.
Please refer to fig. 5. The present specification provides an example of a scenario of a method for transmitting graphic code data. After a user reserves the cervical cancer vaccine on the platform, the user obtains the inoculation qualification. The user's client may present a graphical code comprising data representing the vaccination qualifications. The physician may verify eligibility for vaccination using a scan of the graphic code. In order to reduce the high price of buying the graphic code to other people after the reseller captures the graphic code, the display rule of the graphic code can be set, namely the graphic code can be displayed only 10 minutes before the appointment time. For example, the reserved inoculation time of the user can be 9 to 10, the client of the user can start to display the graphic code at 8 to 50 minutes, and the graphic code is not displayed at 8 to 50 minutes.
Please refer to fig. 6 and 7. After 8 points and 50 minutes, the client displays the graphic code, and the graphic code changes every 5 seconds. At the moment, if the reseller wants to sell the inoculation qualification, the reseller wants to intercept the graphic code and then send the graphic code to the buyer, and the buyer goes to the hospital for checking and selling to try to profit. Because the time for screenshot and sending for reimbursement is probably far longer than 5 seconds, the buyer can not use the screenshot graphic code to go for reimbursement in the hospital, and the reseller can not realize the profit again. And is helpful for maintaining fair and stable order.
Please refer to fig. 8. In another example scenario of a transmitting method of graphic code data provided in the present specification, a user has subscribed to a cervical cancer vaccine on a platform. The user scheduled a 9 o ' clock to 10 o ' clock, but the user wished to be vaccinated 8 o ' clock in the morning. Since the point 8 is less than 50 points, the user's client does not display the graphic code.
Please refer to fig. 9 and 10. After the user arrives at the hospital, the doctor can find the reservation information of the user in the system and can send a starting instruction to the server to instruct the client of the user to start displaying the graphic code. Thus, the verification process of the inoculation qualification of the user can be started in advance.
Please refer to fig. 11. And the doctor issues a starting instruction aiming at the user by operating the doctor client. The user's client may display the graphical code and change every 5 seconds. In this way, the doctor can check the inoculation qualification represented by the graphic code of the user client by the doctor client. Thus, the possibility of reselling the reservation certificate can be reduced. The above description is only exemplary of the present disclosure and should not be construed as limiting the present disclosure, and any modifications, equivalents and the like that are within the spirit and principle of the present disclosure are intended to be included within the scope of the present disclosure.
Please refer to fig. 12. The sending system of the graphic code data provided by the embodiment of the specification can comprise a client and a server. The client may be an electronic device with network access capabilities. Specifically, for example, the client may be a desktop computer, a tablet computer, a notebook computer, a smart phone, a digital assistant, a smart wearable device, a shopping guide terminal, a television, a smart speaker, a microphone, and the like. Wherein, wearable equipment of intelligence includes but not limited to intelligent bracelet, intelligent wrist-watch, intelligent glasses, intelligent helmet, intelligent necklace etc.. Alternatively, the client may be software capable of running in the electronic device. The server may be an electronic device having a certain arithmetic processing capability. Which may have a network communication module, a processor, memory, etc. Of course, the server may also refer to software running in the electronic device. The server may also be a distributed server, which may be a system with multiple processors, memory, network communication modules, etc. operating in coordination. Alternatively, the server may also be a server cluster formed by several servers. Or, with the development of scientific technology, the server can also be a new technical means capable of realizing the corresponding functions of the specification implementation mode. For example, it may be a new form of "server" implemented based on quantum computing.
Please refer to fig. 13 and 14. The embodiment of the specification provides a method for sending graphic code data. The transmission method of the graphic code data may be applied to a server. The method may include the following steps.
Step S110: receiving a request for acquiring graphic code data sent by a client of a user account; the graphic code data is used for generating a graphic code; the graphical code represents verification data of acquisition eligibility for a specified resource.
In this embodiment, the server receives the request for obtaining the graphic code data, which may indicate that the client requests to obtain the graphic code data. Specifically, the server may receive a request for obtaining the graphic code data through the service port. So that the server can correspond to a plurality of clients and respond to the acquisition requests of the graphic code data sent by the clients.
The graphic code may be a pattern containing a user account arranged according to a certain coding rule and representing the acquisition qualification for a specified resource. The graphic code is generated by the graphic code data. The server can convert user account information into the graphic code data recognized by the computer according to a certain coding rule, and the client can generate the graphic code according to the graphic code data. In some embodiments, the graphical code may include a two-dimensional code or a bar code, or the like. In some embodiments, the server may further generate a verification code according to an algorithm, and bind the verification code with the user account. Further, the verification code may be used as a part of the graphic code data in the process of generating the graphic code data.
The validation data may be used to verify that the user qualifies for a specified resource. Specifically, for example, the server may include a user account of the user and the verification code in the process of generating the graphic code data. Therefore, the timeliness of the verification data can be determined through the verification code, and the identity of the user can be verified through the user account. Of course, in some embodiments, the graphical code represented by the graphical code data may include only the verification code.
The specified resource may be a resource that the user wishes to obtain. Specifically, for example, the specified resource may be a scarce vaccine or a limited amount of commercial products. The acquisition qualification may be an assumed condition or identity that the user may possess the specified resource. For example, the acquisition eligibility may be the vaccination eligibility of a scarce vaccine or the purchase eligibility of a limited quantity of commercial products.
Since graphic codes are widely used in daily life, graphic codes can be used as carriers for authentication data. Specifically, the verification data specifying the acquisition eligibility of the resource may be represented by a graphic code. The server receives an acquisition request of the graphic code data sent by a client of the user account, which means that the user needs to call the graphic code to verify whether the user qualifies for acquisition.
Step S120: and determining the target time of the user account for acquiring qualification aiming at the specified resource and the request time corresponding to the acquisition request.
In this embodiment, when the user acquires the acquisition qualification of the specified resource, the target time may be bound for the acquisition qualification. I.e. the user may have said acquisition eligibility at the target time. Specifically, the target time may be in units of dates. For example, the target time may be 12 months and 25 days 2021. The target time may also be more accurate to hours, minutes or seconds. For example, the target time may be 12/25/8/2021, or 12/25/8/15/2021.
The request time corresponding to the acquisition request may be used to determine the time when the user operates the client to send the acquisition request. In some embodiments, the server may take the timestamp attached to the acquisition request as the request time. The server may also use the time when the acquisition request was received as the request time. The request time may be of the same granularity as the target time. Specifically, for example, the target time is in units of dates, and the request time is also in units of dates. The target time may be accurate to hours, minutes or seconds, and the requested time may be correspondingly accurate to hours, minutes or seconds. Of course, the request time may also be less granular than the target time. For example, the target time may be in minutes and the request time may be specific to seconds, or even smaller units.
Step S130: and under the condition that the time between the request time and the target time is within a specified time range, generating the graphic code data.
In this embodiment, a specified duration range may be preset as a constraint condition that can provide the graphic code data to the client. Namely, the time difference between the request time and the target time is within the range of the specified time length, the server generates the graphic code data. In some embodiments, after the target time is determined, a determined starting time at which the graphic code data may be generated may be derived from the target time and the specified time range. In this manner, the graphic code data may be generated after the request time exceeds the start time. Specifically, for example, when the target time is 2022 years, 1 month, 19 days, and 12 days, the specified time range is 1 hour, and if the time difference between the request time and the target time is greater than 1 hour, the graphic code data may not be generated. In the case where the time difference between the request time and the target time is less than or equal to 1 hour, the graphic code may be generated. Alternatively, the time of 1 month, 19 days, 11 of 2022 may be taken as the starting time based on the target time of 2022 year, 1 month, 19 days, 12 and the specified time range of 1 hour. After the request time exceeds 1 month, 19 months and 11 days of 2022, the graphic code data can be generated.
The generated graphic code data may be data that the server converts the user account information into data that can be recognized by a computer according to an encoding rule and is used for generating the graphic code. In some embodiments, the graphic code data may be generated by adopting a corresponding encoding rule according to a specific form of the graphic code. Specifically, for example, the graphic code data may be generated using a graphic code generation tool ZXing. Of course, the method for generating the graphic code is not limited to the above examples, and those skilled in the art can know the graphic code and the generating method, and all of them are covered in the protection scope of the present disclosure.
In order to reduce the high price of the graphic code after the graphic code is captured by the reverse seller, the graphic code data is generated only under the condition that the time between the request time and the target time is within a specified time range. Therefore, the time for the possible circulation of the graphic code is shortened, and the selling difficulty of the reseller is increased.
Step S140: and sending the graphic code data to a client of the user account so that the client displays the graphic code represented by the graphic code data.
In this embodiment, the sending of the graphic code data to the client of the user account may be that the server sends the graphic code data to the client of the user account. Specifically, for example, according to a network communication protocol, the server transmits the requested data in response to the acquisition request of the client.
The graphic code represented by the graphic code data displayed by the client side can be displayed on the client side by converting the graphic code data into the graphic code according to the drawing rule of the graphic code after the client side receives the graphic code data. Specifically, for example, the graphic code may be a two-dimensional code, and in this case, the client may have a positioning pattern area, a version information area, a formatting data area, an error correction area, and a graphic code data area, and the client displays a graphic at a specified position of the graphic code. Of course, the graphic code may be other graphic codes such as a bar code, and the graphic code may be generated according to the drawing rule of the corresponding graphic code.
The server sends the graphic code data to the client, after the client displays the graphic code, the user can see the graphic code at the client, and the graphic code can contain a user account and a verification code of the user so as to facilitate subsequent display or verification. Furthermore, when the verification is carried out, corresponding personnel can scan the image code by using the client and analyze the image code to obtain corresponding verification data. The verification data may comprise only a verification code. In some implementations, the validation data can include a validation code and a user account.
In the embodiment, the control on the generation time of the graphic code is realized by the way that the server determines that the graphic code data is generated under the condition that the time between the request time and the target time is within the specified time range. Thus, the graphic code is used as a certificate, and the graphic code also needs to be displayed within a specified time range from the target time. Thus, by controlling the possible presentation time of the graphical code, the possibility of the graphical code being transferred as a voucher is reduced.
In some embodiments, the sending method of the graphic code data may further include receiving a qualification acquisition request for a specified resource sent by a client of a user account; wherein the eligibility acquisition request represents a request to acquire eligibility for the specified resource at a target time; the qualification acquisition request is attached with a user account and a target time; storing a record of the user account and the target time corresponding to the specified resource; accordingly, determining a target time for the user account to qualify for the specified resource includes: determining a target time for the user account to qualify for the specified resource in accordance with the record.
The eligibility acquisition request for a specified resource may be that a user wishes to acquire the specified resource. The record for storing the user account and the target time corresponding to the specified resource may be a record for a server to record a corresponding relationship between the specified resource, the user account and the target time for subsequent verification and cancellation. Specifically, for example, a user wants to obtain a certain limited amount of goods, the platform opens a purchasing qualification of the limited amount of goods, the user triggers a control for reserving a purchase, selects a purchasing time and fills a user account of a purchaser, the client sends the purchasing limited amount of goods qualification, the purchasing time and the user account of the purchaser to the server, and the server stores the purchasing time corresponding to the purchasing limited amount of goods qualification and the user account of the purchaser in a background database for subsequent underwriting.
In some embodiments, the acquisition request is rejected if the time between the request and the target time is outside the specified duration range.
Please refer to fig. 15. The rejecting the obtaining request can be that the server does not execute the step of generating the graphic code data or execute the step of sending the graphic code data to the client of the account under the condition that the server judges that the time between the request time and the target time is out of the specified duration range.
In some cases, in order to reduce the spread of the graphic code, the server sets that the graphic code data is sent back only if the time between the request time and the target time is within the specified duration range. The client does not display the graphic code, so that the risk of spreading the graphic code can be reduced, the difficulty is increased for a reseller to sell the graphic code and the specified resource, and the possibility of fair competition is increased for the market of the specified resource.
In some embodiments, in the case that it is determined to reject the acquisition request, a prompt message indicating that the current time is not within the specified duration range may also be sent to the client of the user account. In this way, the user of the client can be informed of the reason why the graphic code cannot be presented. In some embodiments, the user of the client may also be prompted by a prompt message for when the graphical code may be presented.
In some embodiments, the method for transmitting graphic code data may further include: and after sending the graphic code data to the client of the user account, sending the regenerated graphic code data to the client of the user account at set interval duration.
In the present embodiment, by setting the specified time length range with respect to the target time, the possibility that the graphic code is sold over is reduced to some extent. On the basis, the graphic code data is updated by setting interval duration at intervals, so that the graphic code data displayed by the client is updated after the interval duration is set at intervals. Further increasing the difficulty of the reseller for reselling the graphic code.
Sending the regenerated graphic code data to the client of the user account at the set interval duration, wherein the timing can be started when the server sends the graphic code data, and the regenerated graphic code data is sent to the client by the server again after the preset duration is exceeded; or the client starts timing when receiving the graphic code, and sends a request for acquiring the graphic code data to the server again after the preset time length is exceeded, so that the server sends the regenerated graphic code data to the client again. In the present embodiment, in the process of regenerating the graphic code data by the server, the verification code is regenerated first, and the graphic code data is generated based on the newly generated verification code. Thus, the verification codes of different graphic code data are different. And the user information expressed by the graphic code data and the acquisition qualification of the specified resource are the same. Moreover, the set interval duration can be far smaller than the specified duration range, so that the graphic code displayed by the client can be changed more frequently. Specifically, the set interval duration may be several seconds. For example, the set interval duration may be less than or equal to 10 seconds, or the set interval duration may also be set to 3 seconds, 4 seconds, 5 seconds, 6 seconds, 7 seconds, or the like, which is not described in detail. Of course, in some cases, such as a network state where the network is slow, the set interval duration may be longer than 10 seconds.
On the client, the time length of the graphic code changes once every set interval. Scanning the graphic code exceeding the set interval duration may not obtain the acquisition qualification of the specified resource, may display that the graphic code is out of date, or may not be scannable. Through the change of the graphic code, difficulty is increased for the reseller to obtain benefits, and market order is better maintained.
In some embodiments, it is preferable that the set interval duration is less than or equal to 5 seconds.
In this embodiment, the reseller sends the screenshot of the graphic code to the buyer, and the buyer displays the graphic code to the seller of the specified resource to resell the specified resource, and the time required for reseller may be longer than 5 seconds. And setting the set interval duration to be less than 5 seconds, so that the circulation of the graphic code screenshot can be effectively reduced.
In some embodiments, sending the regenerated graphic code data to the client side when it is monitored that a screenshot operation occurs on the client side of the user account on an interface displaying the graphic code.
Please refer to fig. 16. And monitoring that the client of the user account generates screenshot operation on an interface for displaying the graphic code, wherein the screenshot operation can be notified to the server after the client executes a screenshot function. Or after executing the screenshot function, the client re-sends the acquisition request for acquiring qualification of the specified resource to the server. Alternatively, the client may recognize the stored picture, and when finding that the stored picture has a screenshot corresponding to the graphic code, the client may send a request for acquiring the graphic code data to the server again. Or, a buried point may be set at the client, and the server is notified to regenerate the graphic code data when the buried point detects that a screenshot event occurs in the section showing the graphic code at the client. In some embodiments, the client may be arranged to present the page for graphical code, not allowing screenshots. Specifically, for example, when a screenshot operation of a user is received, information that does not support the screenshot operation may be presented.
In some embodiments, after the step of transmitting the graphic code data to the client of the user account, the method for transmitting the graphic code data may further include: and under the condition that the duration of sending the graphic code data to the client exceeds the duration of a preset window, the regenerated graphic code data is not sent to the client of the user account any more. The transmitting method of the graphic code data may further include: after the graphic code data are sent to the client side of the user account, the sending time length exceeds the preset time length and the regenerated graphic code data are not sent to the client side of the user account any more; the preset window duration is used for restricting the duration of providing valid graphic code data to the client after receiving the acquisition request.
In some cases, the client may not verify for a longer period of time after presenting the graphical code. At this time, the server continuously updates the graphic code data according to the period of the set interval duration, which may cause a certain waste of resources.
In this embodiment, after the server starts sending the graphic code data to the client, the graphic code data may be maintained in a valid state and may continue to be regenerated. The server sends the regenerated graphic code data to the client so as to update the graphic code displayed by the client. The server may start timing after starting sending the graphic code data to the client. After the time reaches the preset window duration, if the server does not receive the verification and cancellation request of the client of the doctor all the time, or the graphic code of the client is not verified and cancelled all the time. The server may stop generating new graphic code data. Thus, certain computational power can be saved.
In some embodiments, the pre-window duration may be less than or equal to 1 minute. By the arrangement, the user can normally use the client-side display graphic code to verify the verification. And resource waste caused by long-time graphic code display of the client can be reduced.
Please refer to fig. 17. The embodiment of the specification provides a method for displaying a graphic code, which is convenient for protecting information of the graphic code. The method can be applied to a client. The method may include the following steps.
Step S210: obtaining an acquisition qualification for the specified resource; wherein the acquisition qualification has a target time.
Step S220: displaying the graphic code corresponding to the acquisition qualification only when the current time and the target time are within a specified duration range; wherein the graphic code carries verification data representing the acquisition eligibility.
In this embodiment, the user needs to reserve in advance to obtain the acquisition qualification, so that the user can acquire the specified resource at the selected target time. For example, a user wishing to travel to a hot spot that limits people flow may need to reserve tickets ahead and select a travel time at which to reach the spot to qualify for entry to the spot.
And when the user wants to display the graphic code, the control for displaying the graphic code is triggered, and the client sends a request for obtaining the graphic code data to the server and receives the graphic code data sent by the server. The client can display the graphic code according to the graphic code data. In some embodiments, the current time may refer to a time when the client sends the acquisition request, or a time when the acquisition request is generated. Of course, in some cases, the current time may also be the time when the server receives the acquisition request.
In this embodiment, in order to reduce the propagation of the graphic code and the acquisition qualification, the graphic code corresponding to the acquisition qualification may be displayed only when the time between the request time and the target time is within a specified time length range. The displaying of the graphic code corresponding to the acquisition qualification may be that the client receives the graphic code data corresponding to the acquisition qualification sent by the server only when the time between the current time and the target time is within a specified time range, or the server sends the graphic code data corresponding to the acquisition qualification. In some cases, after receiving the graphic code data sent by the server, the client may also determine that the time between the current time and the target time is not within the specified time range, and not display the graphic code represented by the graphic code data. And displaying the graphic code represented by the graphic code data under the condition that the client judges that the time between the current time and the target time is within the specified duration range. For example, the specified duration range may be 10 minutes, the target time is 12 minutes, the current time is 11 minutes, and 55 minutes, and the graphical code represented by the graphical code data is displayed by the client when the current time and the target time are within the specified duration range.
In some embodiments, the step of displaying the graphic code corresponding to the acquisition qualification only when the current time is within a specified time range from the target time includes: receiving graphic code data sent by a server at intervals of set interval duration; and updating the displayed graphic code according to the received graphic code data.
In order to prevent a reseller from obtaining qualification of the specified resource through screenshot and prevent other people from maliciously scanning the graphic code, the graphic code data sent by the server are received at set intervals, and the client displays the graphic code according to the graphic code data. Specifically, for example, the set interval duration is less than or equal to 5 seconds. The client side can send a request for acquiring the graphic code data to the server once after setting the interval time at intervals so as to acquire new graphic code data again, and update the displayed graphic code according to the new graphic code data.
In some embodiments, in the case that the time between the current time and the target time is not within the specified time range, the graphic code corresponding to the acquisition qualification is not displayed. Specifically, for example, the client may send a request for acquiring the graphic code data of the specified resource to the server; receiving the graphic code data sent by the server in a feedback way; and under the condition that the time between the current time and the target time is not within the specified duration range, not displaying the graphic code represented by the graphic code data.
In this embodiment, not displaying the graphic code corresponding to the acquisition qualification may include: and the server does not send the graphic code data, or the client does not display the graphic code corresponding to the graphic code data.
And the possibility of resale the graphic code and the acquisition qualification of the specified resource is reduced by controlling the time for displaying the graphic code on the client. For example, the specified duration range may be 10 minutes, the target time is 12 minutes, the current time is 11 minutes and 30 minutes, the current time and the target time are within the specified duration range, and the client displays the graphic code corresponding to the acquisition qualification.
Please refer to fig. 18, 19 and 20. Embodiments of the present description provide a method for sending graphic code data, which facilitates controlling sending of the graphic code data. The method may be applied to a server. The method may include the following steps.
Step S310: in the case of receiving an acquisition request for a specified resource sent by a client of a first account, allocating acquisition qualification for the specified resource to the first client; wherein the acquisition qualification is to be used as a credential to acquire the specified resource.
In this embodiment, the first account may be account information of the user. Specifically, the first account corresponds to the user. The first account may be used to represent the identity of the user. The first account may be information provided by the user when the user registers the system, or may be information allocated to the user by the system according to the set account information allocation rule. In some implementations, the first account may also be a user account of the user.
The server receives an acquisition request for a specified resource, which may represent a user of a client issuing the acquisition request, desiring to acquire an acquisition qualification for the specified resource. The server may assign acquisition eligibility for the specified resource to the first account. Of course, in some embodiments, the server may determine the amount of the specified resource and assign the first account to be eligible if the specified resource is sufficient.
The acquisition qualification may be used as a credential to acquire the specified resource. Specifically, the user corresponding to the first account may obtain the specified resource only when the client of the first account shows the obtaining qualification. Specifically, for example, the user corresponding to the first account reserves the entry qualification of entering the museum through the client. After the reservation is successful and the museum is reached, the voucher needs to be presented to enter the museum. Or, the user corresponding to the first account makes an appointment for vaccination through the client, and the user can be vaccinated only after the user arrives at the vaccination site and shows a certificate indicating successful appointment.
Step S320: under the condition that a starting instruction aiming at the first account and sent by a client side of a second account is received, generating graphic code data used for verifying the first account; wherein the start instruction represents permission to send graphical code data to a client of the first account.
In this embodiment, the client of the second account may be a client of a person having management authority for the specified resource. The server receives a starting instruction which is sent by the client side of the second account and is aimed at the first account, and the starting instruction can represent the acquisition qualification that a person with management authority aiming at a specified resource allows the first account to acquire the specified resource. The user represented by the first account, after acquiring the acquisition eligibility, may acquire the specified resource in accordance with the acquisition eligibility.
The start instruction may be understood as a computer instruction having a specified format. The initiating instruction may be accompanied by the first account. In this way, the server may determine, according to the start instruction, the first account to which the start instruction is directed. In this way, the server may generate the graphic code data and may send the graphic code data to the client of the first account. In this manner, the client of the first account may be enabled to expose the graphical code represented by the graphical code data. In this embodiment, the start instruction may be used to indicate that the server is allowed to send the graphic code data to the client of the first account. The server may generate the graphic code data first and then send the graphic code data to the client of the first account.
When the client of the second account sends the starting instruction aiming at the first account, the server sends the graphic code data to the client of the first account, so that the condition that the qualification for acquiring the specified resource is leaked can be reduced, and the pressure of generating the graphic code data by the server interface can also be relieved.
In some embodiments, the server may generate a verification code, and convert the verification code and the user account information into computer-recognizable graphic code data according to a coding rule to generate the graphic code. Of course, the server may only convert the verification code into computer recognizable data according to the encoding rule, so as to generate the graphic code data of the graphic code.
In some embodiments, the graphic code data may be generated by adopting a corresponding encoding rule according to a specific form of the graphic code. Specifically, for example, the graphic code data may be generated using a graphic code generation tool ZXing. Of course, the method for generating the graphic code is not limited to the above examples, and those skilled in the art can understand that the graphic code and the generating method are all covered by the protection scope of the present disclosure
Step S330: and sending the graphic code data to the client of the first account.
In this embodiment, the server sends the graphic code data to the client of the first account, and after the client of the first account displays the graphic code, the user of the second client may verify the acquisition qualification by scanning the graphic code. Specifically, for example, a user of a client of a first account has reserved a seat for a restaurant on the network, but intends to consume a day ahead. And under the condition that the user of the client of the second account allows the user of the first client to consume in advance, the client of the second account sends a starting instruction aiming at the first account, the client of the first account displays the reserved graphic code, and the client of the second account can verify the acquisition qualification of the client of the first account in a mode of verifying and canceling the graphic code.
Please refer to fig. 21 and 22. Embodiments of the present description provide a method for sending graphic code data, which facilitates controlling sending of the graphic code data. The method can be applied to a client. The method comprises the following steps.
Step S410: a first account is determined that is eligible for acquisition for a specified resource.
In this embodiment, the client may present account information that qualifies for a given resource. The user of the client may determine the first account from the presented account information. Alternatively, in some cases, the client may determine the first account in accordance with the entered data. Specifically, for example, the user indicated by the first account subscribes to vaccination and qualifies for vaccination, and the specified resource may be a vaccine.
In this embodiment, the nomenclature of the foregoing embodiments may be extended. The client of the second account may be the execution subject of this embodiment. The method for determining the first account may further include that the client of the first account displays the graphic code, and the client of the second account scans and analyzes the graphic code to obtain data contained in the graphic code. In this manner, the client of the second account may determine the first account from the data identified from the graphical code.
Step S420: sending a starting instruction aiming at the first account to a server; the starting instruction is used for instructing the server to send the graphic code data used for verifying the first account to the client side of the first account.
In this embodiment, the client of the second account sends the start instruction for the first account to the server. In this way, the server may generate and send the graphic code data to the client of the first account. After the first account receives the graphic code data, the graphic code can be displayed at the client of the first account for the client of the second account to verify and sell, so that the display times and time of the graphic code are reduced, the risk of leakage of the graphic code and the acquired resource is reduced, and the occupation amount of the calculation resource is also reduced.
Please refer to fig. 23. An embodiment of the present specification provides a transmitting apparatus for graphic code data, including: the device comprises a receiving module, a determining module, a generating module and a feedback module.
The receiving module is used for receiving an acquisition request of the graphic code data sent by a client of a user account; the graphic code data is used for generating a graphic code; the graphical code represents verification data of acquisition eligibility for a specified resource.
And the determining module is used for determining the target time of the acquisition qualification of the user account for the specified resource and the request time corresponding to the acquisition request.
And the generating module is used for generating the graphic code data under the condition that the time between the request time and the target time is within a specified duration range.
And the feedback module is used for sending the graphic code data to a client of the user account so that the client can display the graphic code represented by the graphic code data.
Please refer to fig. 24. The implementation mode of the specification provides a graphic code display device which comprises an obtaining module and a display module.
An acquisition module for acquiring an acquisition qualification for a specified resource; wherein the acquisition qualification has a target time.
The display module is used for displaying the graphic code corresponding to the acquisition qualification only when the current time and the target time are within a specified duration range; wherein the graphic code carries verification data representing the acquisition eligibility.
Please refer to fig. 25. The implementation mode of the description provides a sending device of graphic code data, which comprises an allocation module, a generation module and a sending module.
The allocation module is used for allocating acquisition qualification aiming at the specified resource for the first client under the condition of receiving an acquisition request aiming at the specified resource sent by the client of a first account; wherein the acquisition qualification is to be used as a credential to acquire the specified resource.
The generating module is used for generating graphic code data used for verifying the first account under the condition of receiving a starting instruction aiming at the first account and sent by a client side of a second account; wherein the start instruction indicates permission to send the graphic code data to the client of the first account.
And the sending module is used for sending the graphic code data to the client of the first account.
Please refer to fig. 26. The implementation mode of the specification provides a sending device of graphic code data, which comprises a determining module and a sending module.
A determination module that determines a first account eligible for acquisition for a specified resource;
the sending module is used for sending a starting instruction aiming at the first account to a server; the starting instruction is used for instructing the server to send the graphic code data for verifying the first account to the client of the first account.
The specific functions and effects of the sending device for the graphic code data and the display device for the graphic code data can be explained with reference to other embodiments in this specification, and are not described herein again. The various modules in the medical order processing apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
Please refer to fig. 27. In some embodiments, a computer device may be provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the method steps of any of the preceding embodiments when executing the computer program.
In some embodiments, a computer-readable storage medium may be provided, on which a computer program is stored, which when executed by a processor implements the method steps of any of the preceding embodiments.
In some embodiments, a computer device may be provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the method steps of any of the preceding embodiments when executing the computer program.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments may be implemented by hardware instructions of a computer program, which may be stored in a non-volatile computer-readable storage medium, and when executed, may include processes of the embodiments of the methods. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The description is made in a progressive manner among the embodiments of the present specification. The different embodiments focus on the different parts described compared to the other embodiments. After reading this specification, one skilled in the art can appreciate that many embodiments and many features disclosed in the embodiments can be combined in many different ways, and for the sake of brevity, all possible combinations of features in the embodiments are not described. However, as long as there is no contradiction between combinations of these technical features, the scope of the present specification should be considered as being described.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the present specification, the embodiments themselves are emphasized differently from the other embodiments, and the embodiments can be explained in contrast to each other. Any combination of the embodiments in the present specification by a person skilled in the art based on general technical common knowledge is covered in the disclosure of the present specification.
The above description is only an embodiment of the present disclosure, and is not intended to limit the scope of the claims of the present disclosure. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present application shall be included in the scope of the claims of the present application.
Claims (25)
1. A method for sending graphic code data is characterized by comprising the following steps:
receiving a request for acquiring graphic code data sent by a client of a user account; the graphic code data is used for generating a graphic code; the graphical code representing verification data of acquisition eligibility for a specified resource;
determining a target time of the user account for acquiring qualification of the specified resource and a request time corresponding to the acquisition request;
under the condition that the time between the request time and the target time is within a specified duration range, generating graph code data;
and sending the graphic code data to a client of the user account so that the client displays the graphic code represented by the graphic code data.
2. The method of claim 1, further comprising:
receiving a qualification acquisition request aiming at a specified resource sent by a client of a user account; wherein the eligibility acquisition request represents a request to acquire eligibility for the specified resource at a target time; the qualification acquisition request is attached with a user account and a target time;
storing a record of the user account and the target time corresponding to the specified resource;
accordingly, determining a target time for the user account to qualify for the specified resource includes: determining a target time for the user account to qualify for the specified resource in accordance with the record.
3. The method of claim 1, wherein the acquisition request is rejected if the requested time is outside the specified duration range from the target time.
4. The method of claim 3, wherein rejecting the acquisition request comprises: the step of generating the graphic code data is not performed; or, the step of sending the graphic code data to the client of the account is not executed.
5. The method of claim 3, further comprising:
and sending a prompt message indicating that the current time is not in the specified duration range to a client of the user account.
6. The method of claim 1, further comprising: and after sending the graphic code data to the client of the user account, sending the regenerated graphic code data to the client of the user account at set interval duration.
7. The method of claim 6, wherein the set interval duration is less than or equal to 5 seconds.
8. The method of claim 1, further comprising:
and sending the regenerated graphic code data to the client side under the condition that the client side of the user account is monitored to perform screenshot operation on the interface for displaying the graphic code.
9. The method of claim 6, wherein after the step of sending the graphic code data to a client of the user account, the method further comprises:
under the condition that the duration of sending the graphic code data to the client exceeds the duration of a preset window, the regenerated graphic code data are not sent to the client of the user account; the preset window duration is used for restricting the duration of providing valid graphic code data to the client after receiving the acquisition request.
10. The method of claim 9, wherein the preset window duration is less than or equal to 1 minute.
11. A method for displaying a graphic code is characterized by comprising the following steps:
obtaining an acquisition qualification for the specified resource; wherein the acquisition eligibility has a target time;
displaying the graphic code corresponding to the acquisition qualification only when the current time and the target time are within a specified duration range; wherein the graphic code carries verification data representing the acquisition eligibility.
12. The method according to claim 11, wherein the step of presenting the graphic code corresponding to the acquisition qualification only when the current time is within a specified time range from the target time comprises:
sending an acquisition request of the graphic code data aiming at the specified resource to a server; wherein, the request time corresponding to the acquisition request is taken as the current time;
and displaying the graphic code corresponding to the acquisition qualification only when the current time and the target time are within a specified time range.
13. The method according to claim 11, wherein the step of presenting the graphic code corresponding to the acquisition qualification only when the current time is within a specified time range from the target time comprises:
and receiving the graphic code data which is sent by the server and corresponds to the acquisition qualification under the condition that the current time and the target time are within a specified time range.
14. The method according to claim 11, wherein the step of presenting the graphic code corresponding to the acquisition qualification only when the current time is within a specified time range from the target time comprises:
receiving graphic code data sent by a server at intervals of set interval duration;
and updating the displayed graphic code according to the received graphic code data.
15. The method of claim 13, wherein the specified duration range is less than 5 seconds in duration.
16. The method of claim 11, further comprising: and under the condition that the current time and the target time are not within the specified time range, not displaying the graphic code corresponding to the acquisition qualification.
17. The method of claim 16, wherein the step of not presenting the graphical code corresponding to the acquisition qualification in case that the current time is not within the specified time duration from the target time comprises:
sending an acquisition request of the graphic code data aiming at the specified resource to a server;
receiving the graphic code data sent by the server;
and under the condition that the time between the current time and the target time is not within the specified duration range, not displaying the graphic code represented by the graphic code data.
18. A method for sending graphic code data is characterized by comprising the following steps:
in the case of receiving an acquisition request for a specified resource sent by a client of a first account, allocating acquisition qualification for the specified resource to the first client; wherein the acquisition qualification is to be used as a credential to acquire the specified resource;
under the condition that a starting instruction aiming at the first account and sent by a client side of a second account is received, generating graphic code data used for verifying the first account; wherein the start instruction represents permission to send graphic code data to the client of the first account;
and sending the graphic code data to the client of the first account.
19. A method for sending graphic code data is characterized by comprising the following steps:
determining a first account eligible for acquisition for a specified resource;
sending a starting instruction aiming at the first account to a server; the starting instruction is used for instructing the server to send the graphic code data for verifying the first account to the client of the first account.
20. A device for transmitting graphic code data, comprising:
the receiving module is used for receiving an acquisition request of the graphic code data sent by a client of a user account; the graphic code data is used for generating a graphic code; the graphical code representing verification data of acquisition eligibility for a specified resource;
the determining module is used for determining the target time of the acquisition qualification of the user account for the specified resource and the request time corresponding to the acquisition request;
the generating module is used for generating graphic code data under the condition that the time between the request time and the target time is within a specified duration range;
and the sending module is used for sending the graphic code data to a client of the user account so that the client can display the graphic code represented by the graphic code data.
21. A graphic code display device is characterized by comprising:
an acquisition module for acquiring an acquisition qualification for a specified resource; wherein the acquisition eligibility has a target time;
the display module is used for displaying the graphic code corresponding to the acquisition qualification only when the current time and the target time are within a specified duration range; wherein the graphic code carries verification data representing the acquisition eligibility.
22. A transmission apparatus of a graphic code, comprising:
the allocation module is used for allocating acquisition qualification aiming at the specified resource for the first client under the condition of receiving an acquisition request aiming at the specified resource sent by the client of the first account; wherein the acquisition qualification is to be used as a credential to acquire the specified resource;
the generating module is used for generating graphic code data used for verifying the first account under the condition of receiving a starting instruction aiming at the first account and sent by a client side of a second account; wherein the start instruction represents permission to send graphic code data to the client of the first account;
and the sending module is used for sending the graphic code data to the client of the first account.
23. A device for transmitting graphic code data, comprising:
a determination module that determines a first account eligible for acquisition for a specified resource;
the sending module is used for sending a starting instruction aiming at the first account to a server; the starting instruction is used for instructing the server to send the graphic code data for verifying the first account to the client of the first account.
24. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the method of any one of claims 1 to 19 when executing the computer program.
25. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method steps of any one of claims 1 to 19.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210445337.8A CN114595853B (en) | 2022-04-26 | 2022-04-26 | Method, device, equipment and medium for sending and displaying graphic code data |
| CN202211096172.4A CN115688946A (en) | 2022-04-26 | 2022-04-26 | Graphic code display method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210445337.8A CN114595853B (en) | 2022-04-26 | 2022-04-26 | Method, device, equipment and medium for sending and displaying graphic code data |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211096172.4A Division CN115688946A (en) | 2022-04-26 | 2022-04-26 | Graphic code display method, device, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114595853A true CN114595853A (en) | 2022-06-07 |
| CN114595853B CN114595853B (en) | 2022-09-06 |
Family
ID=81820591
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211096172.4A Pending CN115688946A (en) | 2022-04-26 | 2022-04-26 | Graphic code display method, device, equipment and medium |
| CN202210445337.8A Active CN114595853B (en) | 2022-04-26 | 2022-04-26 | Method, device, equipment and medium for sending and displaying graphic code data |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211096172.4A Pending CN115688946A (en) | 2022-04-26 | 2022-04-26 | Graphic code display method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN115688946A (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090089169A1 (en) * | 2007-09-28 | 2009-04-02 | Google Inc. | Event Based Serving |
| CN103136796A (en) * | 2011-11-23 | 2013-06-05 | 周增涛 | Method for preventing reselling ticket |
| CN106408291A (en) * | 2016-09-06 | 2017-02-15 | 深圳怡化电脑股份有限公司 | Cardless transaction method and system |
| CN107133680A (en) * | 2017-05-15 | 2017-09-05 | 泰康保险集团股份有限公司 | Reservation information processing method, user terminal and server |
| CN107578233A (en) * | 2017-08-23 | 2018-01-12 | 中国地质大学（武汉） | A kind of 2 D code information leakage prevention method, equipment and its storage device |
| CN107688933A (en) * | 2017-08-29 | 2018-02-13 | 腾讯科技（深圳）有限公司 | Resource transfers method, apparatus and storage medium |
| CN108681896A (en) * | 2018-03-29 | 2018-10-19 | 阿里巴巴集团控股有限公司 | Displaying, recognition methods and the device of Quick Response Code |
| CN112967793A (en) * | 2021-04-02 | 2021-06-15 | 北京声智科技有限公司 | Vaccination method, system, device, equipment and storage medium |
| CN113011769A (en) * | 2021-03-31 | 2021-06-22 | 建信金融科技有限责任公司 | Item reservation method and device |
| CN114078581A (en) * | 2021-10-15 | 2022-02-22 | 北京声智科技有限公司 | Health service reservation method, device, terminal, server and storage medium |
| CN114219112A (en) * | 2021-11-19 | 2022-03-22 | 北京声智科技有限公司 | Health service reservation method, device, server and storage medium |
-
2022
- 2022-04-26 CN CN202211096172.4A patent/CN115688946A/en active Pending
- 2022-04-26 CN CN202210445337.8A patent/CN114595853B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090089169A1 (en) * | 2007-09-28 | 2009-04-02 | Google Inc. | Event Based Serving |
| CN103136796A (en) * | 2011-11-23 | 2013-06-05 | 周增涛 | Method for preventing reselling ticket |
| CN106408291A (en) * | 2016-09-06 | 2017-02-15 | 深圳怡化电脑股份有限公司 | Cardless transaction method and system |
| CN107133680A (en) * | 2017-05-15 | 2017-09-05 | 泰康保险集团股份有限公司 | Reservation information processing method, user terminal and server |
| CN107578233A (en) * | 2017-08-23 | 2018-01-12 | 中国地质大学（武汉） | A kind of 2 D code information leakage prevention method, equipment and its storage device |
| CN107688933A (en) * | 2017-08-29 | 2018-02-13 | 腾讯科技（深圳）有限公司 | Resource transfers method, apparatus and storage medium |
| CN108681896A (en) * | 2018-03-29 | 2018-10-19 | 阿里巴巴集团控股有限公司 | Displaying, recognition methods and the device of Quick Response Code |
| CN113011769A (en) * | 2021-03-31 | 2021-06-22 | 建信金融科技有限责任公司 | Item reservation method and device |
| CN112967793A (en) * | 2021-04-02 | 2021-06-15 | 北京声智科技有限公司 | Vaccination method, system, device, equipment and storage medium |
| CN114078581A (en) * | 2021-10-15 | 2022-02-22 | 北京声智科技有限公司 | Health service reservation method, device, terminal, server and storage medium |
| CN114219112A (en) * | 2021-11-19 | 2022-03-22 | 北京声智科技有限公司 | Health service reservation method, device, server and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| SHUBHAM MISHRA: "Online Attendance Monitoring System Using QR Code (OAMS)", 《2021 2ND INTERNATIONAL CONFERENCE ON INTELLIGENT ENGINEERING AND MANAGEMENT (ICIEM)》 * |
| 吴建国等: "一种图形码编码方案的研究", 《计算机研究与发展》 * |
| 郑君等: "基于动态二维码的安全身份认证方案的研究", 《湖北理工学院学报》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114595853B (en) | 2022-09-06 |
| CN115688946A (en) | 2023-02-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20190268344A1 (en) | Data processing systems for fulfilling data subject access requests and related methods | |
| JP7216770B2 (en) | Ticketing Systems, Programs and Methods. | |
| US20180332162A1 (en) | Mobile application for personal safety | |
| US10152718B1 (en) | Agent initiated actions | |
| US20130253940A1 (en) | System and method for diagnosis involving crowdsourcing | |
| US7629891B1 (en) | Personal safety check-in and follow-up system and method | |
| US9444804B2 (en) | Dynamic security question generation | |
| US20130332207A1 (en) | System and method for intelligent management of appointment waiting list | |
| US20130204648A1 (en) | Management apparatus and management method | |
| US20140280617A1 (en) | Methods and Systems for Generating Social Media Messages | |
| US10601989B1 (en) | Agent controlled menu | |
| WO2019028411A1 (en) | Data processing systems for prioritizing data subject access requests for fulfillment and related methods | |
| US11954749B2 (en) | Legal event booking | |
| US20210374329A1 (en) | Systems and methods for providing writing assistance | |
| CN114595853B (en) | Method, device, equipment and medium for sending and displaying graphic code data | |
| CN105897762B (en) | Resource acquisition method and device | |
| CN111652634A (en) | Video excitation method, device and medium based on block chain | |
| CN111079195A (en) | Diagnosis appointment evidence storage method, device and medium based on block chain | |
| CN115829070A (en) | Library space reservation management method, system and storage medium | |
| US11328348B2 (en) | Obfuscated service provider identity during client selection | |
| CN112801458A (en) | Video conference application evaluation method, device, equipment and storage medium | |
| US20230245062A1 (en) | Devices, systems, and methods for blockchain-based inventory management | |
| TWI822932B (en) | Challenge support system, terminal device, method, program and information processing device | |
| JP2019083037A (en) | Ticket provision method, ticket provision device, and program for portable terminal | |
| US20170316384A1 (en) | Methods and systems for scheduling and managing manicure/pedicure appointments and payments |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |