Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Referring to FIG. 1, a flow 100 of one embodiment of a page generation method according to the present application is shown. The execution subject of the page generation method may be a server. The server may be hardware or software. When the server is hardware, it may be implemented as a distributed device cluster formed by multiple devices, or may be implemented as a single device. When the server is software, it may be implemented as a plurality of software or software modules, or may be implemented as a single software or software module. And is not particularly limited herein. The page generation method comprises the following steps:
step 101, in response to receiving a queuing information acquisition request sent by a client, determining a target store and a table type indicated by the queuing information acquisition request.
In this embodiment, the execution main body of the page generation method may receive a queuing information acquisition request sent by the client. The client may be any of various clients that can be communicatively connected to the execution main body. The queue information obtaining request may be used to obtain the queue time. The queue time may refer to the queue time for a certain type of table dining situation in a certain store. After acquiring the queuing information acquisition request, the execution subject may determine the target store and table type indicated by the queuing information acquisition request.
Here, different types of tables are generally able to accommodate different numbers of people. For example, a single-person table can only accommodate one person for dining, a double-person table can accommodate one or two persons for dining, and a four-person table can accommodate four or fewer persons for dining. In addition, the dividing manner of the table is not limited, for example, the table can be divided into small tables, middle tall tables, large tables and the like according to the number of people that can be accommodated.
In some scenarios, when a user visits a store, the user or store staff may obtain a queue ticket by entering the number of people to eat in the store terminal. The user can hold the queuing receipt and send a queuing information acquisition request to the execution main body by scanning the identifier in the queuing receipt. The identifier may be a one-dimensional code (such as a bar code), a two-dimensional code, or the like, or may be a character string composed of at least one of characters, letters, numbers, and special characters.
In other scenarios, when a user visits a store, the queuing may be done automatically by scanning the store's provided identifier for queuing with the client. Alternatively, queuing can be done automatically through a queuing function provided by store public numbers. After queuing, the corresponding queuing progress link or button can be clicked through the client to check the queuing progress. And when the user clicks the corresponding queuing progress link or key, the execution main body sends a queuing information acquisition request.
It should be noted that the client may also send the queuing information acquisition request in other scenarios, which is not described herein any more.
And 102, taking a table matched with the table type in the target store as a target table, and acquiring the dining information of the current dining user of the target table and the user behavior information of the queuing user in front of the target table.
In this embodiment, the execution subject may first set, as the target table, a table in the target store that matches the table type indicated by the queuing information acquisition request. For example, if the table type indicated by the queuing information acquisition request is a middle table and 10 middle tables are shared by the target store, the 10 middle tables may be respectively used as the target tables. Then, the dining information of the current dining user at the target table and the user behavior information of the users waiting to queue in front of the dining at the target table can be obtained.
Here, the dining information of the current dining user at the target table may include various information related to the user who is currently dining at the target table. When the number of the target tables is larger than 1, the current dining user of each target table can correspond to one group of dining information. As an example, the meal information may include, but is not limited to, at least one of: the current number of people having a meal, the actual time consumed by having a meal, the estimated time consumed by having a meal, the remaining time of having a meal and the like. Wherein, for each target table, the actual dining time of the current dining user of the target table is the time length from the time the current dining user is called to the number to the current time. The estimated time spent for dining is the estimated time from the current user for dining being called to the number to the end of dining. The remaining meal time is the duration from the current time to the end of the meal.
Here, the user queued in front of the target table is a user waiting for a meal at the target table and having a queuing order earlier than that of the current user (i.e., the user who sent the queuing information acquisition request through the client). The user behavior information may be information indicative of user behavior, which may include, but is not limited to, at least one of: a queuing information obtaining action, an ordering action in other stores, a meal ordering action, a payment action and the like. Accordingly, the user behavior information may include, but is not limited to, at least one of: queuing information acquisition time, ordering time at other stores, ordering time, payment time, etc.
And 103, determining the dining state of the current dining user of the target table platform based on the acquired dining information, and converting the dining state into first visual data.
In this embodiment, based on the acquired meal information, the execution body may first determine the meal status of the current meal user of the target table. Wherein, the dining status can be divided in advance according to the needs, for example, at least one of the following can be included but not limited: the meal is about to be finished and is in the middle of the meal. The meal status of the current meal user for each target table may then be translated into a set of first visual data. The first visualization data may include, but is not limited to, text, symbols, or graphics, among other visual data. For example, different meal states may be presented using different page elements or different styles of the same page element.
Determining the current dining status of the dining user at the target table based on the dining information may be performed in a variety of ways. As an example, the feature information may be first extracted from the dining information, and then input into a pre-trained dining state detection model, to obtain the dining state of the current dining user. The meal status detection model may be a model trained in advance by a machine learning method (e.g., a supervised learning method), and the model may be trained by using a classification model. The classification model may include, but is not limited to, convolutional neural networks, support vector machines, and the like.
It should be noted that, in addition to converting the dining status into the first visual data, the execution main body may also convert dining information (such as one or more of the current number of people having a meal, the actual time consumed for having a meal, the estimated time consumed for having a meal, the remaining time of having a meal, and the like) into the first visual data, so as to further enrich the content of the queuing page returned to the user.
In some optional implementations of this embodiment, the meal information may include the number of people having a meal currently and the actual time spent having a meal. As shown in fig. 2, the meal status can be determined through substeps S11 to substep S13 as follows:
and a substep S11 of acquiring historical data of the target store, and counting the average historical dining time when the number of historical dining people is the same as the current number of dining people based on the historical data.
Here, the historical data may include information such as the number of people having a historical meal and the time spent having a historical meal. The execution subject can count the average historical dining time when the historical dining number is the same as the current dining number based on the historical data. When the average historical dining time consumption corresponding to each historical dining person number is counted, the average value can be obtained by using the historical dining time consumption of a plurality of recent times (such as 5 times) so as to improve the real-time performance and the accuracy of the data.
It should be noted that, when the number of the target tables is greater than 1, the current number of dining people at each target table can be obtained. For example, there are 3 target tables, and the number of current diners is 2, 3, and 4, respectively. In this case, the average historical dining time when the number of historical dining people is 2 people, the average historical dining time when the number of historical dining people is 3 people, and the average historical dining time when the number of historical dining people is 4 people can be counted.
And a substep S12, estimating the dining residual time of the current dining user of the target table platform based on the average historical dining time and the actual dining time.
Here, the average historical dining time may be determined as an estimated dining time of the current dining user at the target table, and a difference between the estimated dining time and an actual dining time of the current dining user may be determined as a remaining dining time of the current dining user.
Continuing with the above example, for the target table a with the current number of people having a meal of 2, if the average historical meal consumption time of 2 people is 30 minutes, the estimated meal consumption time of the current meal user at the target table a is 30 minutes. If the actual meal consumption of the current meal user of the target table A is 10 minutes, the meal remaining time of the current meal user of the target table A is 20 minutes.
For the target table B with the current dinning number of 3, if the average historical dinning time of the historical dinning people with the historical dinning number of 3 is 45 minutes, the estimated dinning time of the current dinning user of the target table B is 45 minutes. If the actual dining time of the current dining user at the target table B is 30 minutes, the remaining dining time of the current dining user at the target table A is 15 minutes.
For the target table C with the current dinning people number of 4, if the average historical dinning time is 1 hour when the historical dinning people number is 4, the estimated dinning time of the current dinning user at the target table C is 1 hour. If the actual dining time of the current dining user at the target table C is 15 minutes, the remaining dining time of the current dining user at the target table A is 45 minutes.
And a substep S13 of determining the dining state of the current dining user of the target table platform based on the comparison of the dining remaining time and a preset threshold value.
Here, the meal status may include, but is not limited to, at least one of: the meal is about to be finished and is in the middle of the meal. As an example, if the remaining meal time is less than the first preset value and greater than zero, the meal status of the current meal user may be determined as the upcoming meal end status. The specific value of the first preset value can be set according to needs, for example, set to 15 minutes, and is not limited herein. If the remaining meal time is greater than or equal to the first preset value, the meal state of the current meal user can be determined as the in-meal state. If the remaining meal time is equal to zero and the user does not finish the meal, the remaining meal time can be updated to a second preset value, and the meal status of the current meal user is determined as the end-to-meal status. Specific values of the second preset value can be set according to needs, such as 15 minutes, 10 minutes, and the like, and are not limited herein.
It can be understood that when the meal remaining time is equal to zero, it means that the meal duration of the current meal user has reached the estimated meal duration but the meal is not finished, so that the meal remaining time needs to be prolonged, and since the estimated meal duration has been reached, it can be considered that the meal remaining time is closer to the real meal end time, so that the meal status can be determined as the meal ending status.
In some optional implementations of this embodiment, the executing subject may convert the meal status into the first visual data by:
the first step is to select a dining state display area in a queuing information page to be generated. For example, the queuing information page can be divided into an upper area and a lower area, and the lower area is used as a dining state display area.
And secondly, dividing the dining state display areas according to the number of the target table platforms to obtain dining state display sub-areas corresponding to the target table platforms. For example, there are 10 target tables, the meal status display area may be divided into 10 meal status display sub-areas. Each dining state display sub-area corresponds to one target table.
And thirdly, in the dining state display sub-area corresponding to each target table platform, creating a page element for indicating the dining state of the current dining user of the target table platform. And the display styles of the page elements corresponding to different dining states are different. For example, the icon may be used as a page element to indicate the meal status of the current meal user of the target table. If the dining state is that the dining is about to be finished, the display style of the icon can be set to be a first color; if the meal state is in meal, the display style of the icon can be set to be in a second color. Wherein the first eye color is different from the second color for easy user differentiation.
And 104, detecting the queuing state of the front queuing user based on the acquired user behavior information, and converting the queuing state into second visual data.
In this embodiment, based on the acquired user behavior information, the execution subject may first detect a queuing state of a user queued in front. The queuing state may be divided in advance according to needs, and for example, may include but is not limited to at least one of the following: and queuing in and out of queue. The queued state may then be converted to second visual data. The second visualization data may include, but is not limited to, text, symbols, or graphics, among other visual data. For example, different queuing states may be presented using different page elements or different styles of the same page element.
Determining the queuing status of the queued users ahead of the target table based on the user behavior information may be performed in a variety of ways. As an example, the characteristic information may be extracted from the user behavior information, and then input into a pre-trained queuing state detection model to obtain the queuing state of the user who is queuing ahead. The queuing state detection model may be a model obtained by pre-training through a machine learning method (e.g., a supervised learning method), and the model may be trained by using a classification model. The classification model may include, but is not limited to, a convolutional neural network, a support vector machine, and the like.
In some optional implementations of this embodiment, the user behavior information may include a time at which the queued user viewed the queuing information. As shown in fig. 2, the dequeued user among the forward queued users is determined by the following substeps S21 to substep S23:
and a substep S21 of acquiring historical data of the target store, and counting the average interval time from the last time of checking the queuing information to the leaving of the historical leaving user of the target store based on the historical data.
Here, the history dequeue user is a user who is called but has not eaten. The execution main body can count the interval duration from last time of looking up queuing information to dequeuing of a plurality of historical dequeuing users based on historical data, so that the interval durations are averaged to obtain the average interval duration.
Alternatively, the average interval duration may be determined by:
the method comprises the first step of extracting queuing starting time, called number time, last time for viewing queuing information and historical dining data information of at least one historical dequeuing user of the target store from the historical data. The historical meal data information may include, but is not limited to, the time to go to each store for meal, among other things.
Secondly, for each historical dequeue user, determining the time consumed by the historical dequeue user from queuing to dequeue based on the queuing start time, the called number time and the historical dining data of the historical dequeue user, and determining the time consumed by waiting from the queuing start time of the historical dequeue user to the time of viewing queuing information at the last time; and determining the interval duration from the last time of checking the queuing information to the dequeuing of the historical dequeuing user based on the dequeuing time and the waiting time. Here, the difference between the dequeue elapsed time and the wait elapsed time may be used as the time interval from the last time the historical dequeue user viewed the queuing information to dequeue.
In some scenarios, if the historical meal data information indicates that the historical dequeue user has not had meals in other stores during queuing, the interval duration between the queuing start time and the called number time of the historical dequeue user may be taken as the time spent dequeuing.
In other scenarios, if the historical dining data information indicates that the historical dequeuing user has a meal in another store during queuing, the time interval between the queuing start time of the historical dequeuing user and the dining time in another store may be taken as the time spent dequeuing.
And thirdly, determining the average value of the interval duration from the last time of checking the queuing information to the dequeuing of each historical dequeuing user to obtain the average interval duration.
And a substep S22, detecting the current interval duration from the last time of checking the queuing information by the front queuing user to the current time.
And a substep S23 of determining the queuing status of the queued users ahead of the target table based on the comparison of the average interval duration and the current interval duration.
Wherein the queuing state comprises at least one of: and queuing in and out of queue. For a certain current queuing user of the target table, if the average interval duration is longer than the current interval duration from the last time of the current queuing user for viewing the queuing information to the current time, the current queuing user can be considered to be in the queuing state. If the average interval duration is less than or equal to the current interval duration from the last time of viewing the queuing information by the current queuing user to the current time, the front queuing user can be considered to be in the dequeued state.
In some optional implementations of this embodiment, the executing body may further detect a queuing state of the user queued in front by: for each forward-queued user, in response to detecting that the forward-queued user has dining activity in other stores based on the user behavior information of the forward-queued user after the queuing start time of the forward-queued user and before the forward-queued user is called to a number, determining the queued state in forward queue as being out-of-queue. Wherein, whether the dining behavior exists can be determined by detecting the ordering behavior, the payment behavior and the like. For example, if a forward queuing user is detected to go to another store for ordering, the forward queuing user may be considered to have dining behavior in the other store, and the queuing state of the forward queuing user may be determined to be out of queue.
In some optional implementations of this embodiment, the execution subject may convert the queuing state into the second visualization data by:
and step one, counting the number of front queuing users of the target table, and counting the number of off-queue users among the front queuing users based on the queuing state.
And secondly, selecting a queuing state display area in a queuing information page to be generated, and adding text information containing the number of front queuing users and the number of off-queue users to the queuing state display area. For example, the queuing information page can be divided into an upper area and a lower area, and the upper area is used as a dining state display area. Therefore, the content of the queuing information page can be enriched.
And 105, generating a queuing information page based on the first visual data and the second visual data, and returning the queuing information page to the client.
In this embodiment, the execution subject may arrange the first visualization data and the second visualization data in different regions of the same page, so as to obtain a queuing information page. The queuing information page at this time includes information indicating the dining state of the current dining user at the target table, and also includes information indicating the queuing state of the queuing user at the front of the target table. After the queuing information page is returned to the client, the client can display the queuing information page, so that the user can know the relevant information of the current dining user of the table, and can know the relevant information of the queuing user in front. By browsing the multi-dimensional information, the wrong decision-making of the user due to less information can be avoided.
It should be noted that other information may also be included in the queue information page, and the number of target tables corresponding to each meal status may be included as an example. Taking the meal status as divided into an upcoming meal end and a meal, the queuing information may include "upcoming meal end: 10"," during meal: 20", etc. As yet another example, the queuing information page may also include, but is not limited to, at least one of: the method comprises the steps of estimating queuing time, estimated number calling time, table type, the number of target tables, the current number of dining users of the target tables, actual dining time, estimated dining time, dining remaining time and other information.
With continued reference to fig. 4, fig. 4 is a schematic diagram of an application scenario of the page generation method according to the present embodiment. In the application scenario of fig. 4, the user inputs the number of dining people in the store terminal, and the store terminal can select the middle table according to the number of dining people, so as to print out a queue receipt displaying the two-dimensional code. Then, the user scans the two-dimensional code in the queue ticket through a client application installed in the terminal device (such as a mobile phone), so that a queue information acquisition request is initiated.
Then, the server can obtain the dining information of the current dining user of the target table platform in the background, determine the dining state of the current dining user based on the dining information, and convert the dining state into first visual data. Such as the dining status (e.g. "end of meal", "in meal") of each target table (e.g. "middle table 1", "middle table 2", "middle table 3", "middle table 4", "middle table 5", etc.).
Meanwhile, the server can obtain the user behavior information of the front queuing user waiting for dining at the target table at the background, determine the queuing state of the front queuing user based on the user behavior information, and further convert the queuing state into second visual data. The second visual data can be embodied as the number of people queuing ahead, the number of people leaving behind in advance, and the like.
In addition, the server can also obtain some other information, such as "waiting table type", "middle table number", the number of tables corresponding to each dining state (such as "dining in the middle of a meal: 16", "about to finish the meal: 4", etc.), the "number of dining people", "consumed time for dining", "estimated consumed time", "remaining time" of the current dining user at each target table, etc., and convert the information into other visualized data (such as text data).
Finally, the server may generate a queuing information page as shown in fig. 5 based on the visualization data, and return the queuing information page to the client.
In some optional implementation manners of this embodiment, the execution main body may further collect, in real time, dining information of current dining users of table types of stores where target platforms (such as a food ordering platform, a group purchase platform, a comment platform, and the like) are located and user behavior information of users who queue ahead, and store the collected dining information and user behavior information in a database in real time. Thus, the latest data can be stored in real time to facilitate data statistics and analysis in real time when a request for queuing information is received. After receiving a queuing information acquisition request aiming at a target store and a target table sent by a client, firstly acquiring a store identifier of the target store and a type identifier of the target table; and then, taking the store identification and the type identification as keywords, and performing information query in a database based on the keywords to obtain the dining information of the current dining user at the target table in the target store and the user behavior information of the users queued in front of the target table. Therefore, the latest data can be utilized for data analysis, and the accuracy of the queuing information returned to the client is improved.
The method provided by the embodiment of the application can provide accurate and various information for the user according to the type of the table where the user needs to have a dinner, improves the richness and accuracy of the queuing information provided for the user, and is helpful for the user to make a reasonable decision whether to continue queuing.
With further reference to fig. 5, as an implementation of the method shown in the above-mentioned figures, the present application provides an embodiment of a page generating apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 1, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 5, the page generating apparatus 500 of the present embodiment includes: a determining unit 501 configured to determine, in response to receiving a queuing information acquisition request sent by a client, a target store and a table type indicated by the queuing information acquisition request; an obtaining unit 502 configured to obtain meal information of a current meal user at a target table and user behavior information of a queued user ahead of the target table, with a table in the target store matching the table type as the target table; a first conversion unit 503, configured to determine a dining status of the current dining user at the target table platform based on the obtained dining information, and convert the dining status into first visual data; a second conversion unit 504, configured to detect a queuing state of the queued user ahead based on the acquired user behavior information, and convert the queuing state into second visual data; a returning unit 505 configured to generate a queue information page based on the first visual data and the second visual data, and return the queue information page to the client.
In some optional implementations of this embodiment, the apparatus further includes: the acquisition unit is configured to acquire the dining information of current dining users of various table types of various shops parked in the target platform and the user behavior information of users queued in front in real time, and store the acquired dining information and the user behavior information into the database in real time. And, the obtaining unit 502 is further configured to: acquiring store identification of the target store and type identification of the target table; and taking the store identification and the type identification as keywords, and performing information query in the database based on the keywords to obtain the dining information of the current dining user at the target table in the target store and the user behavior information of the users queued in front of the target table.
In some optional implementation manners of this embodiment, the meal information includes the current number of people having a meal and actual consumed meal time; and, the first converting unit 503 is further configured to: acquiring historical data of the target store, and counting average historical dining time when the number of historical dining people is the same as the current number of dining people based on the historical data; estimating the meal remaining time of the current meal user of the target table platform based on the average historical meal consumption time and the actual meal consumption time; determining the dining state of the current dining user of the target table platform based on the comparison between the dining remaining time and a preset threshold value, wherein the dining state comprises at least one of the following: the meal is about to be finished and is in the middle of the meal.
In some optional implementations of the present embodiment, the first converting unit 503 is further configured to: selecting a dining state display area in a queuing information page to be generated; dividing the dining state display area according to the number of the target tables to obtain dining state display sub-areas corresponding to the target tables; and in the meal state display sub-area corresponding to each target table, creating page elements for indicating the meal state of the current meal user of the target table, wherein the display styles of the page elements corresponding to different meal states are different.
In some optional implementations of this embodiment, the user behavior information includes a time when the front queuing user views queuing information; and, the second conversion unit 504, further configured to: acquiring historical data of the target store, and counting the average interval duration from the last time of checking queuing information to the time of leaving by a historical user of the target store based on the historical data, wherein the historical user of leaving is a called user who has not eaten; detecting the current interval duration from the last time of checking the queuing information to the current time of the front queuing user; determining a queuing status of a queued user in front of the target table based on a comparison of the average interval duration and the current interval duration, wherein the queuing status comprises at least one of: in queue and out of queue.
In some optional implementations of this embodiment, the second conversion unit 504 is further configured to: for each forward-queued user, in response to detecting that the forward-queued user has dining activity in other stores based on the user behavior information of the forward-queued user after the queuing start time of the forward-queued user and before the forward-queued user is called to a number, determining the queued state in forward queue as being out-of-queue.
In some optional implementations of this embodiment, the second conversion unit 504 is further configured to: extracting queuing starting time, called number time, last time for checking queuing information and historical dining data information of at least one historical dequeuing user of the target store from the historical data; for each historical dequeuing user, determining dequeuing consumed time from the start of queuing to the dequeuing of the historical dequeuing user and determining waiting consumed time from the queuing start time to the last time of checking queuing information of the historical dequeuing user on the basis of the queuing start time, the called number time and the historical dining data of the historical dequeuing user; determining the interval duration from the last time of checking the queuing information to the dequeuing of the historical dequeuing user based on the dequeuing time and the waiting time; and determining the average value of the interval duration from the last time of looking up the queuing information to the dequeuing of each historical dequeuing user, and obtaining the average interval duration.
In some optional implementations of this embodiment, the second conversion unit 504 is further configured to: counting the number of queuing users in front of the target table, and counting the number of departing users in the queuing users in front based on the queuing state; and selecting a queuing state display area in a queuing information page to be generated, and adding text information containing the number of the front queuing users and the number of the off-queue users to the queuing state display area.
According to the device provided by the embodiment of the application, the queuing information acquisition request sent by the client is received, so that the target store and the table type indicated by the request are determined; then taking a table matched with the table type in the target store as a target table, and acquiring the dining information of the current dining user of the target table and the user behavior information of the queuing user in front of the target table; then, determining the dining state of the current dining user of the target table platform based on the acquired dining information, and converting the dining state into first visual data; then, based on the acquired user behavior information, detecting the queuing state of the front queuing user, and converting the queuing state into second visual data; and finally, generating a queuing information page based on the first visual data and the second visual data, and returning the queuing information page to the client. Therefore, the accurate and various information can be provided for the user according to the type of the table where the user needs to have a dinner, the richness and the accuracy of the queuing information provided for the user are improved, and the provided information is helpful for the user to make a reasonable decision whether to continue queuing.
The embodiment also provides a queuing system which comprises a client and a server. The client is used for sending a queuing information acquisition request to the server by identifying the identifier in the queuing receipt; the server is used for determining the types of the target stores and the tables indicated by the queuing information acquisition request; taking a table matched with the table type in the target store as a target table, and acquiring the dining information of the current dining user of the target table and the user behavior information of the queuing user in front of the target table; determining the dining state of the current dining user of the target table platform based on the acquired dining information, and converting the dining state into first visual data; detecting the queuing state of the front queuing user based on the acquired user behavior information, and converting the queuing state into second visual data; generating a queuing information page based on the first visual data and the second visual data, and returning the queuing information page to the client; and the client is also used for displaying the queuing information.
In some optional implementations of this embodiment, the system further includes: the acquisition device is used for acquiring the dining information of the current dining users of various table types of various shops staying in the target platform and the user behavior information of the users queuing ahead in real time, and storing the acquired dining information and the user behavior information into the database in real time. The server is further used for acquiring store identifiers of the target stores and type identifiers of the target table; and taking the store identification and the type identification as keywords, and performing information query in the database based on the keywords to obtain the dining information of the current dining user at the target table in the target store and the user behavior information of the users queued in front of the target table.
In some optional implementation manners of this embodiment, the meal information includes the current number of people having a meal and the actual time consumed for having a meal; the server is further used for acquiring historical data of the target store and counting the average historical dining time when the historical dining number is the same as the current dining number on the basis of the historical data; estimating the meal remaining time of the current meal user of the target table platform based on the average historical meal consumption time and the actual meal consumption time; determining the dining state of the current dining user of the target table platform based on the comparison between the dining remaining time and a preset threshold value, wherein the dining state comprises at least one of the following: the meal is about to be finished and is in the middle of the meal.
In some optional implementation manners of this embodiment, the server is further configured to select a dining state display area in the queuing information page to be generated; dividing the dining state display area according to the number of the target tables to obtain dining state display sub-areas corresponding to the target tables; and in the meal state display sub-area corresponding to each target table, creating page elements for indicating the meal state of the current meal user of the target table, wherein the display styles of the page elements corresponding to different meal states are different.
In some optional implementations of this embodiment, the user behavior information includes a time when the front queuing user views queuing information; the server is further configured to obtain historical data of the target store, and count average time intervals from last time of checking queuing information to time of a user leaving the target store based on the historical data, where the user leaving the target store is a called user who has not used a meal; detecting the current interval duration from the last time of checking the queuing information to the current time of the front queuing user; determining a queuing status of a queued user in front of the target table based on a comparison of the average interval duration and the current interval duration, wherein the queuing status comprises at least one of: and queuing in and out of queue.
In some optional implementations of this embodiment, the server is further configured to, for each front queued user, determine the queuing status of the front queue as out-of-queue in response to detecting that the front queued user has dining activity in other stores based on the user behavior information of the front queued user after the queuing start time of the front queued user and before the front queued user is called.
In some optional implementations of this embodiment, the server is further configured to extract, from the historical data, a queuing start time, a called number time, a last time of viewing queuing information, and historical dining data information of at least one historical dequeuing user of the target store; for each historical dequeue user, determining the time spent from the beginning of queuing to the dequeue of the historical dequeue user and the time spent waiting from the queuing start time of the historical dequeue user to the last time of checking queuing information based on the queuing start time, the called number time and the historical dining data of the historical dequeue user; determining the interval duration from the last time of checking the queuing information to the dequeuing of the historical dequeuing user based on the dequeuing time consumption and the waiting time consumption; and determining the average value of the interval duration from the last time of looking up the queuing information to the dequeuing of each historical dequeuing user, and obtaining the average interval duration.
In some optional implementation manners of this embodiment, the server is further configured to count the number of users who queue in front of the target table, and count the number of users who leave the queue among the users who queue in front based on the queuing state; and selecting a queuing state display area in a queuing information page to be generated, and adding text information containing the number of the front queuing users and the number of the off-queue users to the queuing state display area.
According to the information sending system provided by the embodiment of the application, the target store and table type indicated by the request are determined by receiving the queuing information acquisition request sent by the client; then taking a table matched with the table type in the target store as a target table, and acquiring the dining information of the current dining user of the target table and the user behavior information of the queuing users in front of the target table; then, based on the acquired dining information, determining the dining state of the current dining user of the target table platform, and converting the dining state into first visual data; then, based on the acquired user behavior information, detecting the queuing state of the front queuing user, and converting the queuing state into second visual data; and finally, generating a queuing information page based on the first visual data and the second visual data, and returning the queuing information page to the client. Therefore, the accurate and various information can be provided for the user according to the type of the table where the user needs to have a dinner, the richness and the accuracy of the queuing information provided for the user are improved, and the provided information is helpful for the user to make a reasonable decision whether to continue queuing.
Referring now to FIG. 6, shown is a block diagram of a computer system 600 suitable for use in implementing an electronic device of an embodiment of the present application. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the use range of the embodiment of the present application.
As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU) 601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the system 600 are also stored. The CPU601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Liquid Crystal Display (LCD) and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. A driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that the computer program read out therefrom is mounted in the storage section 608 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The computer program performs the above-described functions defined in the method of the present application when executed by a Central Processing Unit (CPU) 601. It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, where the names of these units do not in some cases constitute a limitation of the unit itself.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be present separately and not assembled into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: determining types of a target store and a table platform in response to receiving a queuing information acquisition request sent by a client; taking a table matched with the table type in a target store as a target table, and acquiring the dining information of the current dining user of the target table and the user behavior information of the queuing users in front of the target table; determining the dining state of the current dining user of the target table platform based on the acquired dining information, and converting the dining state into first visual data; detecting the queuing state of the front queuing user based on the acquired user behavior information, and converting the queuing state into second visual data; and generating a queuing information page based on the first visual data and the second visual data, and returning the queuing information page to the client.
The foregoing description is only exemplary of the preferred embodiments of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements in which any combination of the features described above or their equivalents does not depart from the spirit of the invention disclosed above. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.