CN112950314A

CN112950314A - Method, device, equipment and storage medium for determining ticket purchasing qualification

Info

Publication number: CN112950314A
Application number: CN202110219719.4A
Authority: CN
Inventors: 徐雪; 刘如梦
Original assignee: Tengjing Sports Culture Development Shanghai Co ltd
Current assignee: Tengjing Sports Culture Development Shanghai Co ltd
Priority date: 2021-02-26
Filing date: 2021-02-26
Publication date: 2021-06-11
Anticipated expiration: 2041-02-26
Also published as: CN112950314B

Abstract

The application provides a method, a device, equipment and a storage medium for determining ticket purchasing qualification, and belongs to the fields of Internet and computers. The method comprises the following steps: acquiring activity correlation operation information based on a target user account, and determining a credit score of the target user account; in response to the credit score satisfying the condition, determining that the target user account is eligible for ticket purchasing for the target event; and sending the first indication information to the client. In the implementation of the application, the ticket buying threshold is improved, the condition of ticket resale is avoided, a good ticket buying environment is provided for the user, the acquisition of the credit points has correlation with the target activity, the credit points can reflect the attention degree of the target user account to the target activity, the user with high attention degree to the target activity is guaranteed to have the ticket buying qualification, and the empty seat condition caused by ticket buying waste is avoided.

Description

Method, device, equipment and storage medium for determining ticket purchasing qualification

Technical Field

The embodiment of the application relates to the field of internet and computers, in particular to a method, a device, equipment and a storage medium for determining ticket purchasing qualification.

Background

At present, the holding times of electronic competitive events are more and more, and the number of people buying tickets on line is more and more. In the related art, when a user purchases an admission ticket of an electronic competitive event, the user can log in a ticketing website by using a login account to purchase the ticket.

However, in the above related art, the ticket can be purchased after the ticket station is registered, and the online ticket purchasing threshold is low, which easily causes a situation of excessive offline reverse ticket selling, and adversely affects the actual ticket purchasing environment.

Disclosure of Invention

The embodiment of the application provides a method, a device, equipment and a storage medium for determining ticket purchasing qualification, which can improve a ticket purchasing threshold and provide a good ticket purchasing environment for a user. The technical scheme is as follows:

according to an aspect of an embodiment of the present application, there is provided a method for determining purchase eligibility, the method including:

acquiring activity associated operation information based on a target user account, and determining credit points of the target user account, wherein the activity associated operation information refers to operation information related to target activities;

responsive to the credit score satisfying a condition, determining that the target user account qualifies for ticketing for the target event;

and sending first indication information to a client, wherein the first indication information is used for indicating that the target user account is qualified for ticket buying for the target activity.

According to an aspect of an embodiment of the present application, there is provided a credit point display method, including:

displaying an event ticket buying interface, wherein the event ticket buying interface comprises at least one event ticket buying inlet;

under the condition that the target user account is not bound with the associated account, displaying an account binding interface, wherein the account binding interface is used for authorizing and binding at least one associated account;

displaying credit points of the target user account under the condition that the binding of the target user account and the associated account is successful; and displaying a corresponding ticket buying control when the credit points meet the conditions.

According to an aspect of an embodiment of the present application, there is provided an apparatus for determining ticket purchasing qualification, the apparatus including:

the information acquisition module is used for acquiring activity associated operation information based on a target user account and determining credit points of the target user account, wherein the activity associated operation information is operation information related to target activities;

a qualification module to determine that the target user account is qualified for ticketing for the target event in response to the credit score satisfying a condition;

and the information sending module is used for sending first indication information to a client, wherein the first indication information is used for indicating that the target user account is qualified for ticket purchasing of the target event.

According to an aspect of an embodiment of the present application, there is provided a credit point display apparatus including:

the interface display module is used for displaying an event ticket buying interface, and the event ticket buying interface comprises at least one event ticket buying inlet;

the account display module is used for displaying an account binding interface under the condition that the target user account is not bound with the associated account, and the account binding interface is used for authorizing and binding at least one associated account;

the credit point display module is used for displaying the credit point of the target user account under the condition that the target user account is successfully bound with the associated account; and displaying a corresponding ticket buying control when the credit points meet the conditions.

The computer equipment comprises a terminal and a server;

according to an aspect of the embodiments of the present application, there is provided a computer device, including a processor and a memory, where at least one instruction, at least one program, a code set, or a set of instructions is stored in the memory, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by the processor to implement the above-mentioned method for determining ticket purchasing eligibility, or to implement the above-mentioned method for displaying credit points.

According to an aspect of embodiments of the present application, there is provided a computer-readable storage medium having at least one instruction, at least one program, a set of codes, or a set of instructions stored therein, which is loaded and executed by a processor to implement the above-mentioned method for determining ticket purchasing eligibility or to implement the above-mentioned method for displaying credit points.

According to an aspect of embodiments herein, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instruction from the computer readable storage medium, and the processor executes the computer instruction, so that the computer device executes the method for determining the ticket purchasing qualification or realizes the credit point display method.

The technical scheme provided by the embodiment of the application can have the following beneficial effects:

the ticket buying qualification of the target user account is detected through the credit integral of the target user account, and under the condition that the credit integral meets the condition, the target user account is determined to have the ticket buying qualification, the ticket buying threshold is improved, the situation of ticket resale is avoided, and a good ticket buying environment is provided for the user; moreover, the credit points are determined through operation information related to the target event, namely the acquisition of the credit points is related to the target event, so that the credit points can reflect the attention degree of the target user account to the target event, the user with high attention degree to the target event is ensured to have ticket buying qualification, and the empty seat condition caused by ticket buying waste is avoided.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of a ticketing system provided by one embodiment of the present application;

fig. 2 is a flowchart of a method for determining ticket-buying eligibility according to an embodiment of the present application;

fig. 3 is a flowchart of a method for determining ticket-buying eligibility according to another embodiment of the present application;

FIG. 4 illustrates a schematic view of a seat selection interface;

FIG. 5 illustrates a schematic diagram of an order payment interface;

fig. 6 is a schematic view exemplarily showing a flow of a determination manner of ticket purchase eligibility;

FIG. 7 is a flowchart of a credit point display method provided by an embodiment of the present application;

FIGS. 8 and 9 illustrate schematic views of an event ticketing interface;

FIG. 10 is a diagram illustrating an account binding interface;

FIGS. 11-12 illustrate schematic diagrams of a points presentation interface;

fig. 13 is a block diagram of a device for determining ticket-buying eligibility, provided in an embodiment of the present application;

fig. 14 is a block diagram of a ticket purchase qualification determining apparatus according to another embodiment of the present application;

FIG. 15 is a block diagram of a credit point display device according to an embodiment of the present application;

FIG. 16 is a block diagram of a credit interface display device provided in another embodiment of the present application;

FIG. 17 is a schematic diagram of a server architecture provided by one embodiment of the present application;

fig. 18 is a schematic diagram of a terminal structure according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Referring to fig. 1, a schematic diagram of a ticket purchasing system according to an embodiment of the present application is shown. The ticket purchasing system may include: a terminal 10 and a server 20.

The terminal 10 may be an electronic device such as a mobile phone, a tablet Computer, a game console, an electronic book reader, a multimedia playing device, a wearable device, a PC (Personal Computer), and the like. The terminal 10 may include a client having a ticket purchasing function. The ticket booking function may be a ticket booking function for a certain event alone, or a ticket booking function for different events, which is not limited in the embodiment of the present application. Alternatively, the client may be a client that needs to download an installed application, or may be a client of a point-to-point application.

The server 20 is used for providing background services for the terminal 10. The server 20 may be a server, a server cluster composed of a plurality of servers, or a cloud computing service center. Alternatively, the server 20 may be a background server to the clients described above. Illustratively, the server 20 is configured to perform qualification testing on the ticket-buying user to determine whether the ticket-buying user qualifies for ticket-buying. Optionally, the server 20 provides background services for clients in multiple terminals 10 simultaneously.

In the embodiment of the present application, the terminal 10 may further include other clients associated with the client. Alternatively, the server 20 determines whether the ticket-buying user of the terminal 10 is eligible for ticket-buying based on the user operation information recorded by the other client and the user operation recorded by the client when the eligibility of the ticket-buying user of the terminal 10 is detected. Of course, in actual operation, the server 20 may update the ticket purchasing qualification of the ticket purchasing user in real time according to actual situations.

Alternatively, the terminal 10 and the server 20 communicate with each other through the network 30. The technical solution of the present application will be described below with reference to several embodiments.

Referring to fig. 2, a flowchart of a method for determining ticket-buying eligibility according to an embodiment of the present application is shown. The method can be applied to the ticket purchasing system shown in fig. 1, for example, the execution subject of each step can be the server 20, and the method can comprise the following steps (201-203):

step 201, obtaining activity correlation operation information based on the target user account, and determining credit points of the target user account.

The target user account refers to the login account of the client. Optionally, the user logs in the client based on the target user account. In a possible implementation manner, the target user account is an account allocated to the user by a background server of the client when the user logs in the client for the first time. Illustratively, when the user logs in the client for the first time, the target user account is acquired through a registration operation. In another possible implementation, the target user account is an account allocated to the user by other clients associated with the client. Illustratively, the game application is associated with a social application, and the user logs in to the client of the game application using the login account of the client of the social application when logging in to the client of the game application.

In the embodiment of the application, when determining the credit score of the target user account, the server acquires the activity associated operation information of the target user account, and determines the credit score of the target user account based on the activity associated operation information. The activity-related operation information refers to operation information related to a target activity, and the target activity may be any online or offline activity, such as a game event, a painting exhibition, online shopping, and the like.

Optionally, the activity-related operation information includes information corresponding to a user operation executed by the user through the target user account; or, the activity-related operation information includes information corresponding to a user operation executed by the user through the target user account and/or the related account. Wherein the associated account refers to a user account associated with the target user account. Optionally, the target user account and the associated account have the same identification information, and the identification information is used to indicate the unique identity of the user. Illustratively, the associated account and the target user account have the same mobile phone number as the identification information; or the associated account and the target user account have the same identification number as the identification information; or the associated account and the target user account have the same social account as identification information; and so on.

In one possible implementation, the server acquires credit points of the target user account after receiving the point acquisition request from the client. The point acquisition request comprises identification information of a target user account. Optionally, after acquiring the point acquisition request, the server collects user operations recorded by acquiring the identification information based on the identification information in the point acquisition request, and further determines the activity-related operation information of the target user account. The user operation comprises user operation corresponding to a target user account and user operation corresponding to an associated account.

In another possible implementation, after determining that the binding between the target user account and the associated account is completed, the server obtains credit points of the target user account. Optionally, the server, upon receiving an account binding request from the client, binds the target user account with at least one associated account, where the associated account is used to obtain the activity associated operation information, and further, when the binding of the target user account with the at least one associated account is completed, the server determines the activity associated operation information of the target user account based on the user operation recorded by the target user account and the user operation recorded by the associated account. In a possible implementation manner, the account binding request includes identification information of an associated account and identification information of a target user account, and the server determines the associated account based on the identification information of the associated account and binds the associated account with the target user account; in another possible implementation manner, the account binding request includes identification information of a target user account, and the server searches for and obtains an associated account corresponding to the target user account based on the identification information of the target user account, and further binds the associated account with the target user account.

It should be noted that, in actual application, the binding time between the target user account and the associated account may be any time, for example, the target user account is bound to the associated account when being created, and the user is bound to the associated account only after triggering the account binding operation through the target user account, which is not limited in the embodiment of the present application.

Optionally, in this embodiment of the application, after the server obtains the credit point of the target user account, the server may update the credit point of the target user account in real time. Optionally, the server detects the identification information of the target user account in real time, acquires newly added activity associated operation information of the target user account after determining that the newly added activity associated operation information exists, acquires an integral change value of the target user account according to the newly added activity associated operation information, and updates the credit integral of the target user account based on the integral change value to obtain an updated credit integral.

The integral change value may be an integral increase value or an integral decrease value, which is not limited in the embodiment of the present application. Exemplarily, if the server detects that the user executes the check-in operation of the other client through the associated account, the point change value is determined to be a point increase value; and if the server detects that the user receives the report information of the accounts of other users through the target user account, determining the point change numerical value as a point reduction numerical value.

It should be noted that different activities may have different point rules according to different actual situations, and therefore, when the server updates the target user account, the server may only update the point change value caused by the general operation information. Then, when the credit score of the target user account aiming at a certain activity is obtained, the floating credit score can be determined according to the score rule of the activity on the basis of the updated offline credit score, and the credit score of the target user account is further determined according to the offline credit score and the floating credit score.

Step 202, in response to the credit score satisfying the condition, determining that the target user account is eligible for ticket buying for the target event.

In this embodiment, after acquiring the credit point of the target user account, the server determines whether the target user account is eligible for ticket purchase for the target event based on the credit point. Optionally, if the credit points meet the conditions, determining that the target user account is qualified for ticket buying for the target event; and if the credit points do not meet the conditions, determining that the target user account does not have the ticket purchasing qualification aiming at the target event. Wherein, the above condition refers to the condition for judging the ticket purchasing qualification of the target event.

Optionally, the conditions for different activities are different.

In practical application, the condition can be flexibly set and adjusted according to practical situations, which is not limited in the embodiment of the present application. For example, the above condition is that the credit point is greater than the threshold, the server compares the credit point with the threshold when judging the credit point, and if the credit point is greater than the threshold, it is determined that the target user account has the ticket-buying qualification for the target event; for another example, the above condition is that the rank corresponding to the credit score exceeds the target value, and when the server determines the credit score, the server determines the credit rank of the target user account based on the credit score, compares the credit rank with the target value, and if the credit rank exceeds the target value, determines that the target user account has the ticket-buying qualification for the target event.

Optionally, the above conditions for different target user accounts are different.

In one possible embodiment, the condition relates to a length of time that the target user account has been registered. Optionally, if the registered time length of the target user account is long, determining that the user corresponding to the target user account is an old user, and the difficulty of achieving the conditions is low; if the registered time of the target user account is short, determining that the user corresponding to the target user account is a new user, and because the attention degree of the new user for the target activity cannot be determined, under the condition, the difficulty of achieving the conditions is high.

Illustratively, after obtaining the credit points, the server obtains the registered time length of the target user account, and determines a point judgment threshold corresponding to the target user account based on the registered time length of the target user account, and if the credit points are greater than the point judgment threshold, determines that the target user account has a ticket-buying qualification for the target event. Wherein the registered duration and the integral judgment threshold are in a negative correlation relationship. That is, the longer the registered time period is, the smaller the integral determination threshold value is, and the shorter the registered time period is, the larger the integral determination threshold value is.

Of course, in practical applications, the above conditions can be flexibly set and adjusted according to practical situations. For example, in order to ensure the ticket purchasing experience of a new user, when determining that the registered duration of a target user account is less than a certain value, the server determines that a user corresponding to the target user account is a new user, then allocates a new credit acquisition activity to the target user account, and the new user temporarily acquires enough credit through the new credit acquisition activity in a short time, so as to ensure the ticket purchasing qualification of the new user. Illustratively, the new points obtaining activity may invite the old user to verify the identity of the new user, ask the new user questions related to the target activity, and so on.

In another possible embodiment, the condition relates to the credit score update frequency of the target user account number. Optionally, if the credit score of the target user account is updated more frequently, determining that the user corresponding to the target user account is more active, in which case, the difficulty of achieving the above condition is lower; and if the updating frequency of the credit points of the target user account is slower, determining that the user corresponding to the target user account is not active, wherein the difficulty of achieving the conditions is higher in the case.

Illustratively, after acquiring the credit points, the server acquires the credit point updating frequency of the target user account, determines a point judgment threshold corresponding to the target user account based on the credit point updating frequency of the target user account, and determines that the target user account has ticket-buying qualification for the target event if the credit points are greater than the point judgment threshold. Wherein the credit integration update frequency is in a negative correlation with the integration determination threshold. That is, the faster the credit integration update frequency, the smaller the integration determination threshold, and the slower the credit integration update frequency, the larger the integration determination threshold.

Step 203, sending the first indication information to the client.

In the embodiment of the application, after determining that the target user account is qualified for ticket buying for the target event, the server generates first indication information and sends the first indication information to the client. Wherein the first indication information is used for indicating that the target user account is qualified for ticket buying for the target event. Optionally, after receiving the first indication information, the client displays a corresponding ticket purchasing control in the interface, and the user enters a ticket purchasing process through a triggering operation for the ticket purchasing control.

Optionally, in this embodiment of the application, if the server determines that the target user account does not qualify for ticket purchasing for the target event through the credit points, second indication information is generated and sent to the client. Wherein the second indication information is used for indicating that the target user account does not have the ticket purchasing qualification aiming at the target event. Optionally, after receiving the second indication information, the client displays a corresponding point detail viewing control in the interface, and the user views the prompt information of the point acquisition mode through a trigger operation for the point detail viewing control.

In summary, in the technical solution provided in the embodiment of the present application, the ticket-buying qualification of the target user account is detected through the credit point of the target user account, and when the credit point meets the condition, it is determined that the target user account has the ticket-buying qualification, so that the ticket-buying threshold is increased, the occurrence of a ticket-resale situation is avoided, and a good ticket-buying environment is provided for the user; moreover, the credit points are determined through operation information related to the target event, namely the acquisition of the credit points is related to the target event, so that the credit points can reflect the attention degree of the target user account to the target event, the user with high attention degree to the target event is ensured to have ticket buying qualification, and the empty seat condition caused by ticket buying waste is avoided.

In addition, the integral judgment threshold value is determined according to the registration time of the target user account, namely the integral judgment condition is flexibly set according to the specific conditions of different target user accounts, so that the fairness and the rationality of ticket purchasing qualification verification are ensured.

Next, a manner of acquiring the credit points will be described. Optionally, the activity-related operation information includes general operation information and target operation information.

In an exemplary embodiment, the step 201 includes the following steps:

1. and acquiring the offline credit points of the target user account.

In the embodiment of the application, when determining to acquire the credit score of the target user account, the server acquires the offline credit score of the target user account. The offline credit integral is determined according to the general operation information of the target user account. Optionally, the common operations corresponding to different activities are the same, and the integration rules of different activities for the common operations are the same.

In a possible implementation manner, the general operation information includes binding operation information of the target user account. Optionally, when the server obtains the offline credit score, based on the identification information of the target user account, the server obtains binding operation information of the target user account, and determines the offline credit score from the target user account based on the binding operation information. The binding operation is a binding operation for the identification information and the target user account, and the identification information is used for indicating the unique identity of the user, such as an identification number, a mobile phone number and the like.

In another possible embodiment, the general operation information includes binding operation information and participation operation information for the associated activity. The associated activities are other activities related to the target activities, such as check-in activities of associated clients, associated game activities, ticket purchasing situations of the associated activities, and the like. Optionally, when the server obtains the offline credit score, based on the identification information of the target user account, obtaining binding operation information of the target user account and participation operation information of the target user account for the associated activities, further based on the binding operation information, determining a basic credit score of the target user account, based on the participation operation information, determining an additional credit score of the target user account, and determining the offline credit score of the target user account according to the basic credit score and the additional credit score. The server may obtain the offline credit points of the target user account in the manners of adding, subtracting, multiplying, dividing, averaging, weighting, averaging, and the like for the basic credit points and the additional credit points, which is not limited in this embodiment of the present application.

Optionally, in this embodiment of the present application, the offline credit points are credit points updated in real time.

2. And acquiring the floating credit points of the target user account aiming at the target activity.

In the embodiment of the application, when determining to acquire the credit score of the target user account, the server acquires the floating credit score of the target user account. Wherein, the floating credit integral is determined according to the target operation information of the target user account. Optionally, the target operations corresponding to different activities are different, and the integration rules of different activities for the target operations are different.

Optionally, when the server obtains the floating credit integration, the server obtains an integration rule corresponding to the target activity. Wherein, the integration rules corresponding to different activities are different. Further, the server determines target operation information of the target user account based on target operation contained in the point rule, and determines floating credit points of the target user account based on the point calculation rule contained in the point rule and in combination with the target operation information of the target user account.

3. And determining the credit point of the target user account according to the offline credit point and the floating credit point.

Optionally, after acquiring the offline credit point and the floating credit point, the server determines the credit point of the target user account according to the offline credit point and the floating credit point. Optionally, the server obtains the credit score of the target user account by means of addition, subtraction, multiplication, division, averaging, weighting, averaging and the like for the offline credit score and the floating credit score, which is not limited in this embodiment of the present application.

Referring to fig. 3, a flowchart of a method for determining ticket-buying eligibility according to another embodiment of the present application is shown. The method can be applied to the ticket purchasing system shown in FIG. 1, for example, the execution subject of each step can be the server 20, and the method can comprise the following steps (301-306):

step 301, obtaining activity association operation information based on the target user account, and determining credit points of the target user account.

Step 302, in response to the credit score satisfying the condition, determining that the target user account is eligible for ticket purchasing for the target event.

Step 303, sending the first indication information to the client.

The steps 301-.

At step 304, seat selection information for the target activity is received from the client.

Optionally, in this embodiment of the application, after receiving the first indication information, the client displays a corresponding ticket purchasing control in the interface, and the user enters a ticket purchasing process through a trigger operation for the ticket purchasing control. Further, the client generates seat selection information for the target activity after detecting a selection operation of the user for the seat, and receives the seat selection information to the server. Correspondingly, the server receives seat selection information for the target activity from the client.

Alternatively, the user may generate the seat selection information by a trigger operation for a certain seat in the seat selection interface. Illustratively, as shown in fig. 4, a plurality of seat selection controls 41 are included in the seat selection interface 40, and one seat selection control 41 corresponds to one seat, and after detecting a trigger operation for the seat selection control 41, the client generates seat selection information for the target activity and sends the seat selection information to the server. At this time, the seat selection information includes the selected seat number.

And 305, responding to the seat selection information and the credit points meeting the requirements, determining that seat selection of the target user account is successful, and sending order information to the client.

In this embodiment, after acquiring the seat selection information, the server determines the seat selection information and the credit points of the target user account, so as to determine whether the seat selection of the target user account is successful. Optionally, if the seat selection information and the credit points meet the requirements, determining that the seat selection of the target user account is successful; and if the seat selection information and the credit points do not meet the requirements, determining that the target user account selection fails.

The request is a credit point determination request for seat selection information. Optionally, in the embodiment of the present application, the credit score determination requirements for the seats in different areas are different. Illustratively, the aesthetic effect of the seat is positively correlated with the difficulty of achieving the requirement, i.e., the greater the aesthetic effect of the seat, the less the aesthetic effect of the seat, and the less the difficulty of achieving the requirement.

Optionally, after the server acquires the seat selection information, an integral threshold corresponding to the position distribution information is determined based on the position distribution information in the seat selection information, and further, the server compares the credit integral of the target user account with the integral threshold. If the credit score is larger than the score threshold value, determining that the selection of the account seat of the target user is successful; and if the credit score is smaller than the score threshold value, determining that the target user account fails to be selected. The position distribution information is used to indicate the area of the selected seat number, that is, the position distribution information can be used to describe the quality of the viewing effect of the selected seat.

In the embodiment of the application, the server generates order information after determining that the seat selection of the target user account is successful, and sends the order information to the client. The order information comprises the identification information of the target user account. Optionally, after receiving the order information, the client displays an order payment interface. Illustratively, as shown in fig. 5, the order payment interface 50 includes a name 51 of the target event, a holding location 52 of the target event, a holding time 53 of the target event, a selected seat number 54, identification information 55 of the target user account, an amount to be paid 56, a payment button 57, and the like.

In the embodiment of the application, after determining that seat selection of the target user account fails, the server generates failure prompt information and sends the failure prompt information to the client. Wherein, the failure prompt message is used for indicating that the seat selection of the account of the target user fails. Optionally, the failure prompt message includes a seat selection failure reason, and after receiving the failure prompt message, the client displays the seat selection failure reason to the user and reminds the user of re-selecting seats.

And step 306, binding the selected seat number with the identity information of the target user account under the condition that the order payment is determined to be successful.

In the embodiment of the application, after the server determines that the order payment is successful, the selected seat number is bound with the identification information of the target account. In one possible embodiment, the selected seat number is included in the seat selection information; in another possible embodiment, the selected seat number is sent to the server by a payment success message after the user has successfully paid. Optionally, the payment success information is generated and sent by the third party payment platform after determining that the user has successfully paid.

It should be noted that, in the embodiment of the present application, the ticket purchasing numbers corresponding to different target user accounts may be different. Optionally, the number of tickets purchased in the account of the target user is in positive correlation with the credit score, that is, the larger the credit score is, the larger the number of tickets purchased is, the smaller the credit score is, the smaller the number of tickets purchased is. Of course, in the embodiment of the present application, one ticket corresponds to only one piece of identification information.

In summary, in the technical scheme provided by the embodiment of the application, the point information is associated with the seat selection qualification, and the credit points can reflect the attention degree of the user to the target activity, so that the user who has high attention to the target activity can buy the front seat tickets, and the fairness of ticket buying is ensured.

In addition, referring to fig. 6, the user ticket purchasing process is fully described from the server side. After receiving the account binding request aiming at the target user account, the server determines the associated account of the target user account based on the identification information of the target user account, and binds the target user account and the associated account. And after the account is successfully bound, acquiring the offline credit score of the target user account, acquiring the floating credit score of the target user account according to the score rule corresponding to the target activity, and further determining the credit score of the target user account according to the offline credit score and the floating credit score. Further, if the credit score of the target user account is larger than the score judgment threshold value, determining that the target user account has the ticket buying qualification aiming at the target event, and sending first indication information to the client; and if the credit score of the target user account is smaller than the score judgment threshold value, determining that the target user account does not have the ticket purchasing qualification aiming at the target event, and sending second indication information to the client. Then, after the server detects the seat selection information, an integration threshold value corresponding to the credit integration is determined based on the seat selection information. Further, if the credit score of the target user account is larger than the score threshold value, determining that seat selection of the target user account is successful, and sending order information to the client; and if the credit score of the target user account is smaller than the score threshold value, determining that seat selection of the target user account fails, and sending seat selection failure information to the client. And then, under the condition that the payment of the order is determined to be completed, the server binds the identity identification information of the target user account with the selected seat number.

Please refer to fig. 7, which illustrates a flowchart of a credit point display method according to an embodiment of the present application. The method can be applied to the ticket purchasing system shown in fig. 1, for example, the execution subject of each step can be the terminal 10, and the method can include the following steps (701-703):

step 701, displaying an event ticket purchasing interface.

The event ticket buying interface comprises at least one event ticket buying inlet. In the embodiment of the application, before ticket booking, a user displays an event ticket booking interface by a client, and further, the user controls the user interface to display a corresponding ticket booking process through a ticket booking inlet in the event ticket booking interface.

In one possible implementation, the event ticket purchasing interface comprises a plurality of ticket purchasing entries corresponding to the events. Illustratively, as shown in fig. 8, the event ticket purchasing interface 80 includes first event information 81, a first event ticket purchasing entry 82, second event information 83, a second event ticket purchasing entry 84, third event information 85, and a third event ticket purchasing entry 86.

In another possible implementation, the event ticketing interface includes a plurality of ticketing entries for an event. Illustratively, as shown in fig. 9, the event ticket buying interface 90 includes a first ticket buying inlet 91, a second ticket buying inlet 92 and a third ticket buying inlet 93 of the target event. Wherein, the holding time of the target event corresponding to different ticket purchasing entrances is different.

Step 702, displaying an account binding interface under the condition that the target user account is not bound with the associated account.

The account binding interface is used for authorizing binding of at least one associated account. Wherein the associated account refers to a user account associated with the target user account. Optionally, the target user account and the associated account have the same identification information, and the identification information is used to indicate the unique identity of the user.

In the embodiment of the application, if the target user account is not bound to the associated account, an account binding interface is displayed. The account binding interface comprises at least one selection identifier of a next binding account. Optionally, after displaying the account binding interface, the client detects the account binding interface, and determines that the binding account is an associated account based on the selection operation of the binding account if the selection operation of the binding account is detected. Optionally, in this embodiment of the present application, one associated account includes more than one role identifier, and after determining the associated account, the client displays a selection control of multiple role identifiers corresponding to the associated account. The client determines that the target role identifier is a bound role identifier of the target user account according to the triggering operation of the selection control of the target role identifier, and determines that the target user account and the associated account are successfully bound under the condition that the target user account and the target role identifier are successfully bound.

Illustratively, as shown in FIG. 10, an account binding button 101 and a selection identifier 102 for a plurality of bound accounts are included in the account binding interface 10. After the user selects the binding account by clicking the selection identifier 102 of the binding account, the user clicks the account binding button 101, further, a plurality of role identifiers 103 corresponding to the selected binding account are displayed in the account binding interface 100, the user triggers and generates the account binding request by clicking the role identifiers 103, and the server binds the target user account and the selected binding account.

Step 703, displaying credit points of the target user account under the condition that the binding of the target user account and the associated account is successful; and, in case the credit points satisfy the conditions, displaying the corresponding ticket purchasing control.

In the embodiment of the application, the client displays the credit points of the target user account under the condition that the binding of the target user account and the associated account is successful; and, in case the credit points satisfy the conditions, displaying the corresponding ticket purchasing control. Wherein, the above condition refers to the condition for judging the ticket purchasing qualification of the target event. Illustratively, as shown in fig. 11, credit points 111 for the target user account and a ticketing control 112 are included in the points presentation interface 110.

Optionally, the ticket buying control is a ticket buying control for the target event, and the user enters a ticket buying process of the target event through the ticket buying control; or the ticket buying control is a ticket buying control for each event, and the user performs an event selection interface through the ticket buying control and enters a ticket buying flow of the target event after receiving a selection operation for the target event.

Certainly, under the condition that the target user account and the associated account are successfully bound, if the credit score does not meet the condition, the client displays the credit score of the target user account and simultaneously displays the corresponding score detail viewing control. Further, the client displays a credit point detail display interface when detecting the triggering operation of the point detail viewing control. The detail display interface of the credit points comprises at least one reminding icon for reminding the acquisition path of the credit points.

Illustratively, as shown in fig. 12, credit points 121 for the target user account number and a point detail view control 122 are included in the point presentation interface 120. After the user clicks the point detail viewing control 122, a reminder icon 123 is displayed in the point presentation interface. The reminding icon 123 includes a reminding icon corresponding to a general operation, a reminding icon for a participation operation of an associated activity, and a reminding icon for a target operation.

Of course, in practical applications, the point detail viewing control 113 may also be included in the point demonstration interface 110 in fig. 11.

In summary, in the technical scheme provided by the embodiment of the application, the credit points of the target user account are displayed in the user interface, so that the user can visually check the owned credit points, and the operation is simple and convenient.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Referring to fig. 13, a block diagram of a device for determining ticket-buying eligibility according to an embodiment of the present application is shown. The device has the function of realizing the method for determining the ticket purchasing qualification, and the function can be realized by hardware or hardware executing corresponding software. The device may be a server or may be provided in a server. The apparatus 1300 may include: an information acquisition module 1310, a qualification determination module 1320, and an information transmission module 1330.

The information obtaining module 1310 is configured to obtain activity-related operation information based on a target user account, where the activity-related operation information is operation information related to a target activity, and the determined credit point of the target user account.

An eligibility determination module 1320, configured to determine that the target user account is eligible for ticketing for the target event in response to the credit score satisfying a condition.

An information sending module 1330 configured to send, to the client, first indication information that indicates that the target user account is eligible for ticket buying for the target event.

In an exemplary embodiment, the activity-associated operation information includes general operation information and target operation information; the information obtaining module 1310 includes: the device comprises an offline acquisition unit, a floating acquisition unit and an integral acquisition unit.

The off-line acquisition unit is used for acquiring an off-line credit point of the target user account; the offline credit point is determined according to the general operation information of the target user account, and the general operations corresponding to different activities are the same.

A floating acquisition unit, configured to acquire a floating credit score of the target user account for the target activity; the floating credit point is determined according to the target operation information of the target user account, and the target operations corresponding to different activities are different.

And the credit acquisition unit is used for determining the credit score of the target user account according to the offline credit score and the floating credit score.

In an exemplary embodiment, the floating obtaining unit is configured to obtain an integration rule corresponding to the target activity; wherein, the integration rules corresponding to different activities are different; determining target operation information of the target user account based on target operation contained in the integration rule; and determining the floating credit point of the target user account number based on a point calculation rule contained in the point rule and by combining the target operation information of the target user account number.

In an exemplary embodiment, the offline acquisition unit is configured to acquire binding operation information of the target user account and participation operation information of the target user account for an associated activity; the general operation information comprises binding operation information and participation operation information aiming at associated activities, the binding operation is the binding operation aiming at the identity identification information and the target user account, and the associated activities are other activities related to the target activities; determining a basic credit point of the target user account based on the binding operation information; determining an additional credit point of the target user account based on the participation operation information; and determining the offline credit point of the target user account according to the basic credit point and the additional credit point.

In an exemplary embodiment, the qualification module 1320 is configured to obtain the registered duration of the target user account; determining an integral judgment threshold corresponding to the target user account based on the registered duration of the target user account; wherein the registered duration is in a negative correlation with the integral determination threshold; in response to the credit score being greater than the score determination threshold, determining that the target user account is eligible for ticketing for the target event.

In an exemplary embodiment, as shown in fig. 14, the apparatus 1300 further comprises: a change acquisition module 1340, and an information update module 1350.

The information obtaining module 1310 is further configured to obtain activity-related operation information newly added to the target user account.

The change obtaining module 1340 is configured to obtain the integral change value of the target user account according to the newly added activity-related operation information.

The information updating module 1350 is configured to update the credit score of the target user account based on the score change value, so as to obtain an updated credit score.

In an exemplary embodiment, as shown in fig. 14, the apparatus 1300 further comprises: an information receiving module 1360, an order sending module 1370, and an information binding module 1380.

An information receiving module 1360 to receive seat selection information for the target activity from the client.

The order sending module 1370 is configured to determine that seat selection of the target user account is successful in response to that the seat selection information and the credit score meet requirements, and send order information to the client, where the order information includes identification information of the target user account.

And an information binding module 1380, configured to bind the selected seat number with the identification information of the target user account if it is determined that the order payment is successful.

In an exemplary embodiment, as shown in fig. 14, the apparatus 1300 further comprises: account binding module 1390.

An account binding module 1390, configured to bind the target user account with at least one associated account in response to receiving an account binding request from the client; and the associated account is used for acquiring the activity associated operation information.

The information obtaining module 1310 is further configured to, when the binding between the target user account and at least one of the associated accounts is completed, perform the step of obtaining the credit points of the target user account determined based on the activity associated operation information of the target user account.

In summary, according to the technical scheme provided by the embodiment of the application, the ticket-buying qualification of the target user account is detected through the credit integral of the target user account, and under the condition that the credit integral meets the condition, the target user account is determined to have the ticket-buying qualification, so that the ticket-buying threshold is improved, the condition of selling tickets reversely is avoided, and a good ticket-buying environment is provided for the user; moreover, the credit points are determined through operation information related to the target event, namely the acquisition of the credit points is related to the target event, so that the credit points can reflect the attention degree of the target user account to the target event, the user with high attention degree to the target event is ensured to have ticket buying qualification, and the empty seat condition caused by ticket buying waste is avoided.

Referring to fig. 15, a block diagram of a credit point display device according to an embodiment of the present application is shown. The device has the function of realizing the credit point display method, and the function can be realized by hardware or by hardware executing corresponding software. The device may be a terminal or may be provided in a terminal. The apparatus 1500 may include: an interface display module 1510, an account number display module 1520, and an integration display module 1530.

The interface display module 1510 is configured to display an event ticket purchasing interface, where the event ticket purchasing interface includes at least one event ticket purchasing entry.

An account display module 1520, configured to display an account binding interface when the associated account is not bound to the target user account, where the account binding interface is used to authorize to bind at least one of the associated accounts.

The credit score display module 1530 is configured to display the credit score of the target user account if the target user account is successfully bound with the associated account; and displaying a corresponding ticket buying control when the credit points meet the conditions.

In an exemplary embodiment, as shown in fig. 16, the apparatus 1500 further comprises: an account selection module 1540, a role display module 1550, a role selection module 1560, and a result determination module 1570.

An account selecting module 1540, configured to determine that the bound account is the associated account in response to a selection operation for a bound account in the account binding interface.

A role display module 1550, configured to display a selection control of the plurality of role identifiers in response to the associated account including more than one role identifier; wherein, different role identifiers correspond to roles used by the associated account in different scenes.

A role selection module 1560, configured to respond to a trigger operation of the selection control for the target role identifier, and determine that the target role identifier is the bound role identifier of the target user account.

A result determining module 1570, configured to determine that the target user account and the associated account are successfully bound when the target user account and the target role identifier are successfully bound.

In an exemplary embodiment, the credit point display module 1530 is further configured to display the credit point of the target user account if the target user account is successfully bound to the associated account; and, in the event that the credit score does not satisfy the condition, displaying a corresponding score detail viewing control; in response to the triggering operation of the point detail viewing control, displaying a detail display interface of the credit points; the detail display interface of the credit points comprises at least one reminding icon for prompting the acquisition path of the credit points.

In summary, according to the technical scheme provided by the embodiment of the application, the credit points of the target user account are displayed in the user interface, so that the user can visually check the owned credit points, and the operation is simple and convenient.

Referring to fig. 17, a block diagram of a server according to an embodiment of the present application is shown. The server may be configured to implement the functions of the above-described ticket purchasing qualification determination method. Specifically, the method comprises the following steps:

the server 1700 includes a Central Processing Unit (CPU) 1701, a system Memory 1704 including a Random Access Memory (RAM) 1702 and a Read Only Memory (ROM) 1703, and a system bus 1705 connecting the system Memory 1704 and the CPU 1701. The server 1700 also includes a basic input/output system (I/O system) 1706 for facilitating the transfer of information between devices within the computer, and a mass storage device 1707 for storing an operating system 1713, application programs 1714, and other program modules 1715.

The basic input/output system 1706 includes a display 1708 for displaying information and an input device 1709 such as a mouse, keyboard, etc. for user input of information. Wherein a display 1708 and an input device 1709 are connected to the central processing unit 1701 via an input-output controller 1710 connected to the system bus 1705. The basic input/output system 1706 may also include an input/output controller 1710 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, the input-output controller 1710 may also provide output to a display screen, a printer, or other type of output device.

The mass storage device 1707 is connected to the central processing unit 1701 through a mass storage controller (not shown) connected to the system bus 1705. The mass storage device 1707 and its associated computer-readable media provide non-volatile storage for the server 1700. That is, the mass storage device 1707 may include a computer-readable medium (not shown) such as a hard disk or a CD-ROM (Compact disk Read-Only Memory) drive.

Without loss of generality, computer readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other solid state Memory technology, CD-ROM, DVD (Digital Video Disc) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that computer storage media is not limited to the foregoing. The system memory 1704 and mass storage device 1707 described above may be collectively referred to as memory.

According to various embodiments of the present application, the server 1700 may also operate with remote computers connected to a network through a network, such as the Internet. That is, the server 1700 may be connected to the network 1712 through the network interface unit 1711 connected to the system bus 1705, or may be connected to other types of networks or remote computer systems (not shown) using the network interface unit 1711.

The memory also includes a computer program stored in the memory and configured to be executed by the one or more processors to implement the above-described method of determining ticket purchasing eligibility.

Referring to fig. 18, a block diagram of a terminal 1800 according to an embodiment of the present application is shown. The terminal 1800 may be an electronic device such as a mobile phone, a tablet computer, a game console, an electronic book reader, a multimedia player, a wearable device, a PC, etc. The terminal is used for implementing the control method of the virtual object provided in the above embodiment. The terminal may be the terminal 10 in the game play environment of fig. 1. Specifically, the method comprises the following steps:

generally, the terminal 1800 includes: a processor 1801 and a memory 1802.

The processor 1801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 1801 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 1801 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1801 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing content required to be displayed on the display screen. In some embodiments, the processor 1801 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.

Memory 1802 may include one or more computer-readable storage media, which may be non-transitory. Memory 1802 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 1802 is used to store at least one instruction, at least one program, set of codes, or set of instructions configured to be executed by one or more processors to implement the credit point display method described above.

In some embodiments, the terminal 1800 may further optionally include: a peripheral interface 1803 and at least one peripheral. The processor 1801, memory 1802, and peripheral interface 1803 may be connected by a bus or signal line. Each peripheral device may be connected to the peripheral device interface 1803 by a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1804, display 1805, camera assembly 1806, audio circuitry 1807, positioning assembly 1808, and power supply 1809.

Those skilled in the art will appreciate that the configuration shown in fig. 18 is not intended to be limiting of terminal 1800 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.

In an exemplary embodiment, there is also provided a computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions which, when executed by a processor of a server, implements the method of determining ticket purchasing eligibility described above.

In an exemplary embodiment, there is also provided a computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions which, when executed by a processor of a terminal, implements the credit point display method described above.

Optionally, the computer-readable storage medium may include: ROM (Read Only Memory), RAM (Random Access Memory), SSD (Solid State drive), or optical disc. The Random Access Memory may include a ReRAM (resistive Random Access Memory) and a DRAM (Dynamic Random Access Memory).

In an exemplary embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer readable storage medium. The processor of the server reads the computer instruction from the computer readable storage medium, and executes the computer instruction, so that the server executes the method for determining the ticket purchasing qualification.

In an exemplary embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer readable storage medium. The processor of the terminal reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the terminal executes the credit point display method.

It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. In addition, the step numbers described herein only exemplarily show one possible execution sequence among the steps, and in some other embodiments, the steps may also be executed out of the numbering sequence, for example, two steps with different numbers are executed simultaneously, or two steps with different numbers are executed in a reverse order to the order shown in the figure, which is not limited by the embodiment of the present application.

The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method for determining ticket purchase eligibility, the method comprising:

2. The method of claim 1, wherein the activity-related operation information comprises general operation information and target operation information;

the acquiring of the credit point of the target user account determined based on the activity associated operation information of the target user account includes:

acquiring an offline credit score of the target user account; the offline credit point is determined according to the general operation information of the target user account, and the general operations corresponding to different activities are the same;

acquiring a floating credit score of the target user account aiming at the target activity; the floating credit score is determined according to target operation information of the target user account, and target operations corresponding to different activities are different;

and determining the credit score of the target user account according to the offline credit score and the floating credit score.

3. The method of claim 2, wherein the obtaining floating credit points for the target activity for the target user account comprises:

acquiring an integral rule corresponding to the target activity; wherein, the integration rules corresponding to different activities are different;

determining target operation information of the target user account based on target operation contained in the integration rule;

and determining the floating credit point of the target user account number based on a point calculation rule contained in the point rule and by combining the target operation information of the target user account number.

4. The method of claim 2, wherein said obtaining the offline credit score of the target user account comprises:

acquiring binding operation information of the target user account and participation operation information of the target user account aiming at the associated activities; the general operation information comprises binding operation information and participation operation information aiming at associated activities, the binding operation is the binding operation aiming at the identity identification information and the target user account, and the associated activities are other activities related to the target activities;

determining a basic credit point of the target user account based on the binding operation information;

determining an additional credit point of the target user account based on the participation operation information;

and determining the offline credit point of the target user account according to the basic credit point and the additional credit point.

5. The method of claim 1, wherein the determining that the target user account qualifies for ticketing for the target event comprises:

acquiring the registered duration of the target user account;

determining an integral judgment threshold corresponding to the target user account based on the registered duration of the target user account; wherein the registered duration is in a negative correlation with the integral determination threshold;

in response to the credit score being greater than the score determination threshold, determining that the target user account is eligible for ticketing for the target event.

6. The method according to any one of claims 1 to 5, wherein after obtaining the activity-related operation information based on the target user account and determining the credit score of the target user account, the method further comprises:

acquiring newly added activity associated operation information of the target user account;

acquiring the integral change value of the target user account according to the newly added activity associated operation information;

and updating the credit points of the target user account number based on the point change numerical value to obtain updated credit points.

7. The method according to any one of claims 1 to 5, wherein after sending the first indication information to the client, further comprising:

receiving seat selection information for the target activity from the client;

responding to the seat selection information and the credit score meeting requirements, determining that seat selection of the target user account is successful, and sending order information to the client, wherein the order information comprises identity identification information of the target user account;

and under the condition that the order payment is determined to be successful, binding the selected seat number with the identity identification information of the target user account.

8. The method of claim 7, wherein the determining that the target user account seating was successful in response to the seating selection information and the credit score meeting requirements comprises:

determining an integral threshold value corresponding to the position distribution information based on the position distribution information in the seat selection information, wherein the position distribution information is used for indicating the located area of the selected seat number;

and in response to the credit score being greater than the score threshold value, determining that the target user account seat selection is successful.

9. The method according to any one of claims 1 to 5, further comprising:

in response to receiving an account binding request from the client, binding the target user account with at least one associated account; wherein, the correlation account is used for acquiring the activity correlation operation information;

and under the condition that the binding of the target user account and at least one associated account is finished, executing the step of obtaining the credit points of the target user account determined based on the activity associated operation information of the target user account.

10. A credit point display method, the method comprising:

11. The method of claim 10, wherein after displaying the account binding interface, further comprising:

responding to the selection operation of the binding account in the account binding interface, and determining that the binding account is the associated account;

in response to the associated account including more than one role identification, displaying a selection control of the plurality of role identifications; wherein, different role identifiers correspond to roles used by the associated account in different scenes;

responding to the trigger operation of the selection control aiming at the target role identification, and determining that the target role identification is the binding role identification of the target user account;

and under the condition that the target user account is successfully bound with the target role identifier, determining that the target user account is successfully bound with the associated account.

12. The method of claim 10, further comprising:

displaying credit points of the target user account under the condition that the binding of the target user account and the associated account is successful; and, in the event that the credit score does not satisfy the condition, displaying a corresponding score detail viewing control;

in response to the triggering operation of the point detail viewing control, displaying a detail display interface of the credit points;

the detail display interface of the credit points comprises at least one reminding icon for prompting the acquisition path of the credit points.

13. An apparatus for determining ticket purchasing eligibility, the apparatus comprising:

14. A credit point display device, the device comprising:

15. A computer device comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by the processor to implement the method of determining ticketing eligibility as claimed in any one of claims 1 to 9, or to implement the method of displaying credit points as claimed in any one of claims 10 to 12.

16. A computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement the method of determining ticket claim 1 to 9 or to implement the method of displaying credit of any one of claims 10 to 12.