WO2019242354A1 - 一种就餐业务处理方法及系统 - Google Patents

一种就餐业务处理方法及系统 Download PDF

Info

Publication number
WO2019242354A1
WO2019242354A1 PCT/CN2019/079165 CN2019079165W WO2019242354A1 WO 2019242354 A1 WO2019242354 A1 WO 2019242354A1 CN 2019079165 W CN2019079165 W CN 2019079165W WO 2019242354 A1 WO2019242354 A1 WO 2019242354A1
Authority
WO
WIPO (PCT)
Prior art keywords
reservation
user
client
merchant
information
Prior art date
Application number
PCT/CN2019/079165
Other languages
English (en)
French (fr)
Inventor
曹瑶瑶
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2019242354A1 publication Critical patent/WO2019242354A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/12—Hotels or restaurants

Definitions

  • the embodiments of the present specification relate to the field of Internet application technologies, and in particular, to a method and system for processing a dining service.
  • users can implement various business operations through various applications installed on the terminal. For example, when users need to eat, they can first browse merchant reviews and offers through applications such as word of mouth. Information, and then you can make a reservation and queue up before you arrive at the restaurant through the application to reserve seats. When you order, you can also scan the QR code of the merchant for self-service ordering based on the code scanning function of some applications. And check out through the payment app after eating.
  • the embodiments of the present specification provide a method and system for processing a dining service.
  • the technical solution is as follows:
  • a method for processing a dining service includes:
  • the user client sends the reservation reservation information input by the user to the merchant client after receiving the reservation reservation operation trigger;
  • the merchant client After receiving the reservation reservation information sent by the user client, the merchant client returns the reservation reservation result to the user client according to the reservation reservation information and the current seat information of the merchant;
  • the user client terminal displays the ordering operation interface after receiving the successful reservation reservation result returned by the merchant client; and after confirming that the user has finished ordering, sends the ordering information entered by the user to the merchant client;
  • the merchant client After receiving the order information sent by the user client, the merchant client displays the order processing operation interface; and after confirming that the merchant has completed the order, the generated order information is sent to the user client;
  • the user client terminal After receiving the order information sent by the merchant client, the user client terminal displays the settlement operation interface; and after receiving the triggering of the settlement operation, according to the received order information, settlement payment is made for this meal service.
  • a dining service processing method is provided and applied to a user client.
  • the method includes:
  • the settlement operation interface After receiving the order information sent by the merchant client, the settlement operation interface is displayed; after receiving the settlement operation trigger, according to the received order information, settlement payment is made for this meal service.
  • a dining service processing method is provided and applied to a merchant client.
  • the method includes:
  • a dining service processing system includes a user client and a merchant client;
  • the user client sends the reservation reservation information input by the user to the merchant client after receiving the reservation reservation operation trigger;
  • the merchant client After receiving the reservation reservation information sent by the user client, the merchant client returns the reservation reservation result to the user client according to the reservation reservation information and the current seat information of the merchant;
  • the user client terminal displays the ordering operation interface after receiving the successful reservation reservation result returned by the merchant client; and after confirming that the user has finished ordering, sends the ordering information entered by the user to the merchant client;
  • the merchant client After receiving the order information sent by the user client, the merchant client displays the order processing operation interface; and after confirming that the merchant has completed the order, the generated order information is sent to the user client;
  • the user client terminal After receiving the order information sent by the merchant client, the user client terminal displays the settlement operation interface; and after receiving the triggering of the settlement operation, according to the received order information, settlement payment is made for this meal service.
  • a dining service processing apparatus is provided and applied to a user client.
  • the apparatus includes:
  • the reservation reservation module is used to send the reservation reservation information input by the user to the merchant client after receiving the reservation reservation operation trigger, to instruct to return to the reservation reservation according to the reservation reservation information and the current seat information of the merchant. result;
  • the ordering module is used to display the ordering operation interface after receiving the successful reservation reservation result returned by the merchant client; and after confirming that the user has finished ordering, send the ordering information entered by the user to the merchant client;
  • the settlement payment module is used to display the settlement operation interface after receiving the order information sent by the merchant client; and after receiving the settlement operation trigger, according to the received order information, make a settlement payment for the meal service.
  • a dining service processing apparatus which is applied to a merchant client.
  • the apparatus includes:
  • the reservation reservation processing module is configured to return the reservation reservation result to the user client according to the reservation reservation information and the current seat information of the merchant after receiving the reservation reservation information sent by the user client;
  • the order processing module is used to display the order processing operation interface after receiving the order information sent by the user client; and after confirming that the merchant has completed the order, the generated order information is sent to the user client.
  • the user's reservation, ordering and payment services are integrated into one user client, so that the user only needs to be in one client during the dining process Operate without installing and opening various applications in the smart terminal, and the seat reservation information, ordering information, and order information during a meal can be automatically associated and pushed by the user terminal, simplifying the user's Operation process, and reducing the occupation of terminal resources, thereby improving the user ’s experience of dining with the application.
  • Possibility For the application system, the data during the meal are generated based on the same application system, which makes the data interaction between operations more convenient, which is conducive to providing better services to users and merchants.
  • FIG. 1 is a schematic structural diagram of a dining service processing system according to an embodiment of the present specification
  • FIG. 2 is a schematic flowchart of a dining service processing method according to an embodiment of the present specification
  • FIG. 3 is another schematic flowchart of a dining service processing method according to an embodiment of the present specification.
  • FIG. 4 is another schematic flowchart of a dining service processing method according to an embodiment of the present specification.
  • FIG. 5 is a schematic structural diagram of a dining service processing apparatus applied to a user client according to an embodiment of the present specification
  • FIG. 6 is another schematic structural diagram of a dining service processing apparatus applied to a user client according to an embodiment of the present specification
  • FIG. 7 is a schematic structural diagram of a dining service processing apparatus applied to a merchant client according to an embodiment of the present specification
  • FIG. 8 is another schematic structural diagram of a dining service processing apparatus applied to a merchant client according to an embodiment of the present specification.
  • FIG. 9 is a schematic structural diagram of a device for configuring a device according to an embodiment of the present specification.
  • the flow of the dining service processing involves the user client and the merchant client.
  • the corresponding system architecture diagram is shown in FIG. 1 and includes the user client device 10 and the merchant client device 20.
  • the user client device may be a smart terminal device such as a user's smart phone or tablet computer that can install applications, and the user client device may be an application program installed on the device.
  • the merchant client device can be a smart terminal device, such as a smart phone or tablet of a merchant staff, that can be installed with an application, or a special device that can be equipped with corresponding functions by installing an application.
  • the user client device and the merchant client device can realize communication connection through various forms of networks, and this specification does not need to limit this.
  • the data transmission between the user client and the merchant client involved in this specification can be performed through the server of the application program, which will not be described separately in the following description.
  • FIG. 2 is an interaction flowchart of a dining service processing method provided by an embodiment of the present specification, which may specifically include the following steps:
  • the user client After receiving a reservation reservation operation trigger, the user client sends the reservation reservation information input by the user to the merchant client;
  • the user client is provided with a seat reservation operation interface, such as a button marked with the word "seat reservation” and a pattern, or an input box for receiving a text instruction for seat reservation. Take the button labeled “Reservation” and the pattern as an example.
  • the user client can further pop up the interface for entering reservation information, such as prompting the user to enter or select the number of reservations, Store time or time period, name and contact information of the person who made the reservation, even reservation of the lobby or private room, reservation of table type, etc.
  • reservation reservation information input by the user can be set according to the actual application situation, which can be changed at any time, or can be changed within a limited time, or cannot be changed after confirmation.
  • the user client can also be provided with functions such as merchant search, evaluation, and recommended dishes, so that the user can use the user client's reference to determine which merchants need to be reserved, and make reservations directly through the user client.
  • functions such as merchant search, evaluation, and recommended dishes, so that the user can use the user client's reference to determine which merchants need to be reserved, and make reservations directly through the user client.
  • Those skilled in the art may set other functions related to the user's dining for the user client according to the actual situation, which is not limited in the embodiments of the present specification.
  • the merchant client After receiving the reservation reservation information sent by the user client, the merchant client returns the reservation reservation result to the user client according to the reservation reservation information and the current seat information of the merchant;
  • the current seat information of the merchant may also be expressed differently.
  • some merchants support queuing, that is, it supports multiple groups of different users to make reservations for the same time period and the same table type, and queues in the order of reservation.
  • the seat information can be the number of table types configured by the merchant, the time Segments have been reserved by several groups of users.
  • some merchants only support queuing, and cannot specify the time period and table type.
  • the seat information can be the current number of people in the queue. Or, some merchants do not support queuing, and only support the reservation of vacant seats.
  • the seat information may be the seat or table type specified in the reservation information, whether it is free during this period, and whether it is possible to reserve seats.
  • the method of obtaining the user's current reservation reservation result may be different according to the reservation reservation information and the current seat information of the merchant. For example, if the merchant only supports queuing, and the time period and table type cannot be specified, the merchant client can return the current queue number, reserved seating queue number, etc. to the user client after receiving the reservation reservation information sent by the user client. Seat occupancy results; if the merchant only supports reserved seat vacancies, it can return results such as success or failure of seat reservation to the user client.
  • the work of determining the seat reservation result based on the reservation reservation information and the current seat information of the merchant can be completed by the merchant client based on the information or by the merchant staff.
  • the merchant client obtains the preliminary results, which are reviewed and confirmed by the staff, and so on.
  • the embodiment of this specification does not limit this.
  • the user client can also design different interfaces and options for the user to enter the reservation information when making a reservation according to the form of reservation-free seating supported by different merchants, so that the staff or client of the merchant can obtain a reservation.
  • the process of results is simpler.
  • the user client terminal displays the ordering operation interface after receiving the result of the reservation reservation successfully returned by the merchant client terminal; and after confirming that the user has finished ordering, sends the ordering information entered by the user to the merchant client terminal;
  • the reservation reservation success mentioned here can be expressed in the form of "successful reservation” and other forms, and can also be expressed in the form of a reservation number and the current number of people in the queue.
  • the user client receives the result of the reservation reservation success returned by the merchant client, and can determine that the user has successfully reserved the reservation this time, thereby displaying the order operation interface to the user.
  • the user can order through the operation interface immediately after the reservation is made, or at any time after arriving at the store or at any time after arriving at the store, and can also order through other ordering operation interfaces in the user client. And you can order multiple times according to the needs of the dining process.
  • the merchant can handle the situation according to the merchant's situation. If the merchant has completed the order for the user, the corresponding order information can be generated.
  • the order information can include the total amount of the order, the list of meals, the unit price and the quantity.
  • the user client terminal After receiving the order information sent by the merchant client, the user client terminal displays the settlement operation interface; and after receiving the triggering of the settlement operation, according to the received order information, settlement payment is made for the meal service.
  • the information in each business operation is also corresponding, that is, after a meal service and the seat reservation information, ordering information and settlement payment
  • the settlement and payment information has a corresponding relationship, and can be displayed to users at the same time.
  • This interface can also set buttons for payment, evaluation, etc. for each meal.
  • the user client can receive the settlement payment operation trigger, and the user client can determine the meal service and order information corresponding to the operation, thereby performing Settle payment.
  • the user client may also trigger spontaneously or according to the operation of the user, and determine whether to notify the merchant to prepare the dishes in advance according to the user's reserved seat credit value.
  • the user's reservation reservation credit value can be expressed in various forms, for example, it can be the credit value of the user's sesame credit and other payment systems, or it can be based on whether the user has arrived on time after the reservation reservation in the application,
  • the calculated credit value such as whether to cancel temporarily, etc., of course, can also be a weighted result of several types of credit values.
  • the credit value can be further converted according to whether the user pays a temporary cancellation fee, etc.
  • a threshold value for preparing vegetables in advance can be set in advance, and in the case that the reservation reservation credit value is higher than this threshold, the user client sends a notification of preparing vegetables in advance to the merchant client.
  • the merchant client can determine the user's scheduled arrival time or time period or determine the user's queuing number based on the reservation reservation information of the dining service to estimate the user's seating time, etc .; You can also estimate the user's arrival time based on the user's current location information; you can also estimate the user's seat time after arriving at the store based on the current seat information of the merchant; etc., that is, estimate the user's seat time to determine a reasonable serving Time, combined with the time required to prepare a meal, estimate the time to start preparing.
  • the merchant can start serving dishes within a period of time before and after the user arrives at the store.
  • the user's current location information can be obtained by the user client. If the distance between the user and the merchant is less than a preset threshold, that is, the user has reached the vicinity of the merchant, such as when the user is only 1 km away from the merchant, the user can be notified to serve. Operation interface, so that when users need to start serving, they can use this interface to notify merchants to start serving.
  • the user client may further obtain the current location information of the user, and according to the location Information and reservation reservation information to determine whether the user arrived on time on the store, for example, after determining that the user arrived at the store based on the location information, based on the scheduled arrival time in the reservation reservation information, determine whether the user's arrival time is late At the scheduled arrival time, if it is, the user does not arrive on time; another example is to obtain the user's current location information at the scheduled arrival time, if the user has not arrived at the store, or is far away from the store, such as 1,000 Meters or more, the user did not arrive at the store on time.
  • the user does not arrive at the store within the scheduled arrival time period, it can be determined that the user's current reservation reservation is invalid, and the user is shown the reservation reservation operation interface so that the user can make a reservation again. You can also remind the user through other methods such as SMS that the seat reservation for this appointment has expired and you need to make a new appointment.
  • the user client can determine whether there is an invalid reservation reservation for the same merchant; if so, display the order operation interface and the point of the invalid reservation reservation. Meal information.
  • operation interfaces displayed by the user client are not limited to the ones described in this manual.
  • the user can also change or add dishes at any time through other ordering interfaces of the user client, etc. Wait.
  • the types of operations and operation interfaces listed in this specification should not be construed as limiting the solutions of the embodiments of this specification.
  • the following describes the dining business processing method performed by the user client and the merchant client from a unilateral perspective:
  • FIG. 3 is a flowchart of a dining service processing method performed by a user client, which may specifically include the following steps:
  • S302 After receiving the successful reservation reservation result returned by the merchant client, display the order operation interface; and after confirming that the user has completed the order, send the order information entered by the user to the merchant client;
  • FIG. 4 is a flowchart of a dining service processing method executed by a merchant client, which may specifically include the following steps:
  • S402 After receiving the order information sent by the user client, display the order processing operation interface; and after confirming that the merchant has completed the order, send the generated order information to the user client.
  • a user On the way to a certain merchant, a user, through his Alipay client A on his mobile phone, clicks the reservation button in Alipay, selects the appointment for the merchant, and enters the reservation seat information such as the number of people dining, and the scheduled arrival time.
  • the Alipay client A in the user's mobile phone sends the reservation reservation information entered by the user to the merchant's Alipay client B.
  • Alipay client B determines the user's reservation reservation based on the number of meals and the scheduled arrival time in the information. Table type and meal time period, so according to the table type and time period in the merchant, the number of reserved seats is determined, the user's queue number is determined, and the determined queue number is sent to Alipay client A.
  • Alipay client A After receiving the number, Alipay client A determines that the reservation is successful, and can display the ordering button to the user on the mobile phone interface. After the user clicks the button, the user jumps to the ordering interface.
  • the ordering interface can display merchants' various dishes, prices and other information, as well as operation buttons such as adding a shopping cart and confirming the completion of ordering.
  • the Alipay client A sends the name, quantity, and other requirements of the order ordered by the user to the Alipay client B.
  • Alipay client B After receiving the order information, Alipay client B will show the merchant's processing operation interface for the order. The merchant can directly place an order to complete the order, and Alipay client B will generate order information including the total amount and send it to Alipay client A.
  • the reservation will be invalidated and a new reservation is required. If the user did not order last time, he can order again. If the user has ordered the last time, he can directly use the last order information. Or adjust dishes based on this.
  • Alipay client A can also determine whether to notify the merchant to prepare vegetables in advance based on the user's sesame credit. If the user's sesame credit is higher than a preset value, such as 500, or there is no negative record, the merchant is notified to prepare vegetables in advance.
  • the LBS (Location Based Service) information of the user's mobile phone is periodically obtained and sent to the Alipay server so that after the Alipay client B receives the advance preparation notification, it can obtain and determine the current location of the user. Estimate whether the user can arrive at the store on time or in advance. If the user can be expected to arrive at the store on time, estimate the preparation time according to the ordering information and prepare the food a certain time in advance to ensure that the user can serve the food when he arrives on time.
  • Alipay client A After the merchant is notified to prepare dishes in advance, if the user arrives at the merchant on time (or within 1 km of the merchant), Alipay client A can show the user a button to notify the merchant to serve, and after the user clicks the button, the merchant can start to advance The prepared dishes can also be added by the order button of Alipay client A according to the actual needs.
  • an embodiment of the present specification further provides a dining service processing apparatus, which is applied to a user client.
  • the apparatus may include:
  • the reservation reservation module 110 is configured to send the reservation reservation information input by the user to the merchant client after receiving the reservation reservation operation trigger, so as to instruct to return to the reservation reservation according to the reservation reservation information and the current seat information of the merchant. Seat result
  • the ordering module 120 is configured to display the ordering operation interface after receiving the result of the successful reservation reservation by the merchant client; and after confirming that the user has completed ordering, send the ordering information entered by the user to the merchant client;
  • the settlement and payment module 130 is configured to display the settlement operation interface after receiving the order information sent by the merchant client; and after receiving the trigger of the settlement operation, perform settlement payment for the meal service based on the received order information.
  • the device may further include:
  • the dish preparation notification module 140 is configured to determine whether to notify a merchant to prepare dishes in advance according to the user's reserved seat reservation credit value; if so, the user client sends an advance preparation notice to the merchant client.
  • the device may further include:
  • the serving notification module 150 is configured to obtain the current location information of the user, and display a notification serving operation interface when the distance between the user and the merchant is less than a preset threshold.
  • the device may further include:
  • the invalidation determining module 160 is configured to determine whether the user arrives at the store within the scheduled time period according to the reservation reservation information and the current location information of the user; if not, determine that the reservation reservation is invalid and display the reservation reservation Operation interface.
  • the ordering module 120 may be specifically configured to:
  • the preparation notification module 140, the serving notification module 150, and the failure determination module 160 can be configured in the device at the same time as shown in FIG. 6, or can be separately configured in the device separately.
  • the structure shown in FIG. 6 should not be construed as limiting the scheme of the embodiment of the present specification.
  • An embodiment of the present specification further provides a dining service processing apparatus, which is applied to a merchant client.
  • the apparatus may include:
  • the reservation reservation processing module 210 is configured to return the reservation reservation result to the user client according to the reservation reservation information and the current seat information of the merchant after receiving the reservation reservation information sent by the user client;
  • the order processing module 220 is configured to display the order processing operation interface after receiving the order information sent by the user client; and after confirming that the merchant has completed the order, the generated order information is sent to the user customer.
  • the device may further include:
  • the preparation time point determining module 230 is configured to, after receiving the advance preparation notice, estimate a serving time point according to the reserved seat information, the current location information of the user, and / or the current seat information of the merchant; According to the ordering information, the length of time required for preparing the dishes is estimated; and the time for preparing the dishes is determined according to the estimated time of serving the dishes and the time required for preparing the dishes.
  • An embodiment of the present specification further provides a computer device including at least a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the foregoing dining service processing method when the processor executes the program.
  • the method includes at least:
  • a dining business processing method includes:
  • the user client sends the reservation reservation information input by the user to the merchant client after receiving the reservation reservation operation trigger;
  • the merchant client After receiving the reservation reservation information sent by the user client, the merchant client returns the reservation reservation result to the user client according to the reservation reservation information and the current seat information of the merchant;
  • the user client terminal displays the ordering operation interface after receiving the successful reservation reservation result returned by the merchant client; and after confirming that the user has finished ordering, sends the ordering information entered by the user to the merchant client;
  • the merchant client After receiving the order information sent by the user client, the merchant client displays the order processing operation interface; and after confirming that the merchant has completed the order, the generated order information is sent to the user client;
  • the user client terminal After receiving the order information sent by the merchant client, the user client terminal displays the settlement operation interface; and after receiving the triggering of the settlement operation, according to the received order information, settlement payment is made for this meal service.
  • FIG. 9 shows a more specific schematic diagram of the hardware structure of a computing device provided by an embodiment of the present specification.
  • the device may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050.
  • the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 implement a communication connection within the device through a bus 1050.
  • the processor 1010 may be implemented by using a general-purpose CPU (Central Processing Unit), a microprocessor, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits. Relevant programs are executed to implement the technical solutions provided by the embodiments of this specification.
  • a general-purpose CPU Central Processing Unit
  • a microprocessor e.g., a central processing unit
  • ASIC Application Specific Integrated Circuit
  • the memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage devices, dynamic storage devices, and the like.
  • the memory 1020 may store an operating system and other application programs.
  • related program codes are stored in the memory 1020 and are called and executed by the processor 1010.
  • the input / output interface 1030 is used to connect an input / output module to implement information input and output.
  • the input / output / module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions.
  • the input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc.
  • the output device may include a display, a speaker, a vibrator, and an indicator light.
  • the communication interface 1040 is used to connect a communication module (not shown in the figure) to implement communication interaction between the device and other devices.
  • the communication module can implement communication through a wired method (for example, USB, network cable, etc.), and can also implement communication through a wireless method (for example, mobile network, WIFI, Bluetooth, etc.).
  • the bus 1050 includes a path for transmitting information between various components of the device (for example, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).
  • the device may also include necessary for achieving normal operation Other components.
  • the foregoing device may also include only components necessary to implement the solutions of the embodiments of the present specification, and does not necessarily include all the components shown in the figures.
  • An embodiment of the present specification also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the foregoing dining service processing method is implemented.
  • the method includes at least:
  • a dining business processing method includes:
  • the user client sends the reservation reservation information input by the user to the merchant client after receiving the reservation reservation operation trigger;
  • the merchant client After receiving the reservation reservation information sent by the user client, the merchant client returns the reservation reservation result to the user client according to the reservation reservation information and the current seat information of the merchant;
  • the user client terminal displays the ordering operation interface after receiving the successful reservation reservation result returned by the merchant client; and after confirming that the user has finished ordering, sends the ordering information entered by the user to the merchant client;
  • the merchant client After receiving the order information sent by the user client, the merchant client displays the order processing operation interface; and after confirming that the merchant has completed the order, the generated order information is sent to the user client;
  • the user client terminal After receiving the order information sent by the merchant client, the user client terminal displays the settlement operation interface; and after receiving the triggering of the settlement operation, according to the received order information, settlement payment is made for this meal service.
  • Computer-readable media includes permanent and non-persistent, removable and non-removable media.
  • Information storage can be accomplished by any method or technology.
  • Information may be computer-readable instructions, data structures, modules of a program, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transmitting medium may be used to store information that can be accessed by a computing device.
  • computer-readable media does not include temporary computer-readable media, such as modulated data signals and carrier waves.
  • the embodiments of the present specification can be implemented by means of software plus a necessary universal hardware platform. Based on such an understanding, the technical solution of the embodiments of the present specification may be embodied in the form of a software product that is essentially or contributes to the existing technology.
  • the computer software product may be stored in a storage medium such as ROM / RAM, Magnetic disks, optical disks, and the like include a number of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments or portions of the embodiments of this specification.
  • the system, device, module, or unit described in the foregoing embodiments may be specifically implemented by a computer chip or entity, or a product with a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or a combination of any of these devices.
  • each embodiment in this specification is described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments.
  • the device embodiment since it is basically similar to the method embodiment, it is described relatively simply, and the relevant part may refer to the description of the method embodiment.
  • the device embodiments described above are only schematic, and the modules described as separate components may or may not be physically separated. When implementing the solutions of the embodiments of this specification, the functions of each module may be the same Or multiple software and / or hardware. Some or all of the modules may also be selected according to actual needs to achieve the objective of the solution of this embodiment. Those of ordinary skill in the art can understand and implement without creative efforts.

Landscapes

  • Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • Health & Medical Sciences (AREA)
  • Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

公开了一种就餐业务处理方法及系统。一种就餐业务处理方法包括：用户客户端接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端；商户客户端根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；用户客户端接收到预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；商户客户端接收到点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端；用户客户端接收到订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。

Description

一种就餐业务处理方法及系统 技术领域
本说明书实施例涉及互联网应用技术领域，尤其涉及一种就餐业务处理方法及系统。
背景技术
随着智能终端的发展和网络应用的普及，用户可以通过终端上安装的各种应用程序实现各种业务操作，例如，用户需要就餐时，可以首先通过口碑等应用程序，浏览商户的评价与优惠信息，然后可以通过预约占座的应用程序，在到达餐厅之前便进行预约并取号排队，点餐时还可以基于某些应用程序的扫码功能，扫描商户的二维码进行自助点餐，并在就餐之后通过支付应用程序结账。
对于商户而言，需要同时接收各种应用程序中的信息，并分别根据不同应用程序中用户预约、点餐及支付的信息，管理、调配餐厅的资源，安排用户就餐，因而工作流程更繁琐，并且容易发生疏漏。
发明内容
针对上述技术问题，本说明书实施例提供一种就餐业务处理方法及系统，技术方案如下：
根据本说明书实施例的第一方面，提供一种就餐业务处理方法，该方法包括：
用户客户端接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端；
商户客户端接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
用户客户端接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
商户客户端接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端；
用户客户端接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
根据本说明书实施例的第二方面，提供一种就餐业务处理方法，应用于用户客户端，该方法包括：
接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端，以指示根据该预约占座信息、及商户当前的座位信息，返回预约占座结果；
接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
根据本说明书实施例的第三方面，提供一种就餐业务处理方法，应用于商户客户端，该方法包括：
接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端。
根据本说明书实施例的第四方面，提供一种就餐业务处理系统，该系统包括：用户客户端及商户客户端；
用户客户端接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端；
商户客户端接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
用户客户端接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
商户客户端接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端；
用户客户端接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
根据本说明书实施例的第五方面，提供一种就餐业务处理装置，应用于用户客户端，该装置包括：
预约占座模块，用于接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端，以指示根据该预约占座信息、及商户当前的座位信息，返回预约占座结果；
点餐模块，用于接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
结算支付模块，用于接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
根据本说明书实施例的第六方面，提供一种就餐业务处理装置，应用于商户客户端，该装置包括：
预约占座处理模块，用于接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
点餐处理模块，用于接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端。
本说明书实施例所提供的技术方案，对于用户而言，将用户预约、点餐及支付业务，均集成到1个用户客户端中，使得用户在就餐过程中，仅需要在1个客户端中进行操作，而不需要在智能终端中安装与打开各种应用程序，并且一次就餐过程中的预约占座信息、点餐信息、订单信息等均可以由用户端自动关联与推送，简化了用户的操作过程，且减少了对终端资源的占用，从而改善用户使用应用程序就餐的体验感。对于商户而言，也可以使用同1个应用程序查看与确认用户从预约到支付的信息，统一地调配餐厅内的资源，安排用户的就餐流程，从而使商户的工作更简便，并降低发生错误的可能性。对于应用程序系统而言，就餐过程中的数据均基于同1个应用程序系统产生，使各个操作之间的数据交互更便利，从而有利于向用户及商户提供更优质的服务。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本说明书实施例。
此外，本说明书实施例中的任一实施例并不需要达到上述的全部效果。
附图说明
为了更清楚地说明本说明书实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书实施例中记载的一些实施例，对于本领域普通技术人员来讲，还可以根据这些附图获得其他的附图。
图1是本说明书实施例的就餐业务处理系统的结构示意图；
图2是本说明书实施例的就餐业务处理方法的一种流程示意图；
图3是本说明书实施例的就餐业务处理方法的另一种流程示意图；
图4是本说明书实施例的就餐业务处理方法的又一种流程示意图；
图5是本说明书实施例的应用于用户客户端的就餐业务处理装置的一种结构示意图；
图6是本说明书实施例的应用于用户客户端的就餐业务处理装置的另一种结构示意图；
图7是本说明书实施例的应用于商户客户端的就餐业务处理装置的一种结构示意图；
图8是本说明书实施例的应用于商户客户端的就餐业务处理装置的另一种结构示意图；
图9是用于配置本说明书实施例装置的一种设备的结构示意图。
具体实施方式
为了使本领域技术人员更好地理解本说明书实施例中的技术方案，下面将结合本说明书实施例中的附图，对本说明书实施例中的技术方案进行详细地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书中的实施例，本领域普通技术人员所获得的所有其他实施例，都应当属于保护的范围。
在本说明书的实施例中，就餐业务处理的流程涉及用户客户端及商户客户端，对应的系统架构示意图如图1所示，包括用户客户端设备10和商户客户端设备20。
用户客户端设备可以是用户的智能手机、平板电脑等可以安装应用程序的智能终端设备，用户客户端则可以是安装于该设备的应用程序。商户客户端设备可以是商户工作人员的智能手机、平板电脑等可以安装应用程序的智能终端设备，也可以是可通过安装 应用程序等方式配备相应功能的专用设备。
用户客户端设备与商户客户端设备可通过各种形式的网络实现通信连接，本说明书对此并不需要进行限定。并且，本说明书中所涉及的用户客户端与商户客户端的数据传输，可以经由应用程序的服务端进行，本说明书在下文中不再单独对此进行阐述。
图2为本说明书实施例提供的就餐业务处理方法的交互流程图，具体可以包括以下步骤：
S201，用户客户端接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端；
用户客户端中设置有预约占座操作接口，如标有“预约占座”字样及图案的按钮，或是接收预约占座文字指令的输入框等等。以标有“预约占座”字样及图案的按钮为例，当用户点击该按钮时，用户客户端可以进一步地弹出输入预约占座信息的界面，如，提示用户输入或选择预约人数、预定到店时间或时间段、预约人姓名及联系方式，甚至是预定大堂或者包间、预定桌型，等等。
当然，本领域技术人员可以根据实际应用情况，设置用户所输入的预约占座信息可以随时更改、或者限时更改、或者确认后不可更改等等。
此外，用户客户端中还可以设置有商户搜索、评价、推荐菜品等功能，以便用户可以使用用户客户端参考决定需要预约的商户，并直接通过用户客户端进行预约。本领域技术人员可以根据实际情况，为用户客户端设置其他与用户就餐相关的功能，本说明书实施例中对此不进行限定。
S202，商户客户端接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
根据商户所支持的预约占座形式不同，商户当前的座位信息的表示方式也可以不同。例如，有的商户支持排队，即支持多组不同的用户预约同一时间段、同一桌型，并按照预约的先后顺序排队，则其座位信息可以为商户所配置的某桌型的数量、该时间段已被几组用户预约等。又如，有的商户仅支持排队，并且不可指定时间段及桌型，则其座位信息可以为当前排队人数。或者，有的商户不支持排队，仅支持空闲座位的预约占座，则其座位信息可以为，预约信息中指定的座位或者桌型，在该时段是否空闲，是否可以预约占座等。
相应地，商户客户端接收到预约占座信息后，根据该预约占座信息、及商户当前的 座位信息，得到用户本次预约占座结果的方式也可以不同。例如，如果商户仅支持排队，并且不可指定时间段及桌型，则商户客户端接收到用户客户端发送的预约占座信息后，可以向用户客户端返回当前排队人数、预约占座队列号码等占座结果；如果商户仅支持空闲座位的预约占座，则可以向用户客户端返回预约占座成功或者失败等结果。
可以理解的是，具体地根据预约占座信息、及商户当前的座位信息，判断得到预约占座结果的工作，可以由商户客户端根据信息完成，也可以有商户工作人员来完成，还可以由商户客户端得到初步结果，并由工作人员审核确认，等等，本说明书实施例对此不进行限定。
此外，用户客户端还可以根据不同商户所支持的不用预约占座形式，针对性地设计用户在预约时输入预约信息的不同界面、选项等，从而使商户的工作人员或者客户端得到预约占座结果的过程更简便。
S203，用户客户端接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
S204，商户客户端接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端；
为了便于描述，将S203与S204结合说明。
可以理解的是，这里所说的预约占座成功，可以以“预约成功”等文字的形式表示，也可以以预约号码、当前排队人数等形式表示。用户客户端接收到商户客户端返回的预约占座成功的结果，便可以确定用户本次预约占座成功，从而向用户展示点餐操作接口。
用户可以在预约成功后立即通过该操作接口进行点餐，也可以稍后在到店前或到店后的任意时间进行点餐，还可以通过用户客户端内其他点餐操作接口进行点餐，并且可以根据就餐过程的需求，多次点餐。
商户通过商户客户端看到用户的点餐信息后，可以根据商户的情况进行处理。如果商户为用户完成了本次点餐，则可以生成对应的订单信息，订单信息中可以包括订单的总金额，餐品列表、单价及数量等信息。
S205，用户客户端接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
由于用户可以基于同一应用程序进行预约占座、点餐及结算支付，因此在各个业务 操作中的信息也是对应的，即一次就餐业务与该次的预约占座信息、点餐信息及结算付款后的结算支付信息，均具有对应关系，并且可以同一地向用户展示。
例如，可以在用户客户端的就餐详单界面中，查看每次就餐业务的预约信息、点餐信息及订单信息等，该界面还可以为每次就餐设置支付、评价等按钮，当用户需要支付某次就餐业务的金额时，通过点击该次就餐业务的支付按钮，便可以使用户客户端接收到结算支付操作触发，而用户客户端可以确定该操作所对应的就餐业务、及订单信息，从而进行结算付款。
在本说明书提供的一种具体实施方式中，用户点餐后，用户客户端还可以自发地或根据用户的操作触发，根据用户的预约占座信用值，确定是否通知商户提前备菜。
用户的预约占座信用值可以以多种形式表示，例如，可以是用户的芝麻信用等支付系统的信用值，也可以是根据用户在该应用程序中历次预约占座后，是否准时到店、是否临时取消等情况计算的信用值，等等，当然也可以是几种信用值的加权结果，此外，还可以根据用户是否缴付临时取消手续费等情况，进一步折算信用值，等等。
可以预先设定允许提前备菜的阈值，在预约占座信用值高于该阈值的情况下，由用户客户端向商户客户端发送提前备菜通知。
商户用户端接收到提前备菜通知后，可以根据该次就餐业务的预约占座信息，确定用户的预定到店时间或时间段，或者确定用户的排队号码，从而估算该用户的入座时间等；也可以根据用户当前的位置信息，估算用户的到店时间；还可以根据商户当前的座位信息，估算用户到店后的入座时间；等等，即估算用户入座的时间，从而确定合理的上菜时间，并结合备菜所需时间，估算开始备菜的时间。
如果用户客户端通知商户客户端提前进行了备菜，则商户可以在用户到店前后的一段时间内，便开始上菜。
例如，可以由用户客户端获得用户当前的位置信息，如果用户与商户的距离小于预设阈值，即用户已到达商户附近，如用户距商户仅1千米时，便可以向用户展示通知上菜操作接口，以便用户在需要开始上菜时，可以通过该操作接口，通知商户开始上菜。
在本说明书提供的又一种具体实施方式中，在用户客户端将用户输入的点餐信息发送至商户客户端的情况下，用户客户端还可以进一步地获取用户当前的位置信息，并根据该位置信息及预约占座信息，判断该用户是否准时到店了，例如，在根据位置信息确定该用户到店后，根据预约占座信息中的预定到店时间，判断该用户的到店时间是否晚 于该预定到店时间，如果是则该用户未准时到店；又如，在预定的到店时间，获取用户当前的位置信息，如果用户还未到达商户，或者距离商户较远，如1千米以上，则该用户未准时到店。
如果用户未在预定到店时间段内到店，则可以判定该用户的本次预约占座失效，并向用户展示预约占座操作接口，以便用户重新进行预约。还可以通过短信等其他方式提示用户，本次预约占座已经失效，需要重新预约。
此外，还可能存在用户取消后重新预约等情况，导致某次预约占座失效，为了便于用户在重新预约后，可以直接使用上次的点餐信息，或者直接在此基础上调整所点菜品，用户客户端可以接收到商户客户端返回的预约占座成功的结果后，确定是否存在针对同一商户的失效的预约占座；若是，则展示点餐操作接口、及该次失效预约占座的点餐信息。
可以理解的是，用户客户端展示的操作接口，并不局限于本说明书所述的几种，例如，用户点餐之后，也可以通过用户客户端的其他点餐接口，随时更改或追加菜品，等等。本说明书中所列出的操作及操作接口的种类，不应理解为对本说明书实施例方案的限定。
为了更清楚地说明本说明书实施例的就餐业务处理方案，下面分别再从单侧的角度，对用户客户端与商户客户端所执行的就餐业务处理方法进行说明：
图3所示为用户客户端所执行的就餐业务处理方法流程图，具体可以包括以下步骤：
S301，接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端，以指示根据该预约占座信息、及商户当前的座位信息，返回预约占座结果；
S302，接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
S303，接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
图4所示为商户客户端所执行的就餐业务处理方法流程图，具体可以包括以下步骤：
S401，接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
S402，接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商 户完成本次点餐后，将生成的订单信息发送至用户客户端。
关于用户客户端与商户客户端的单侧执行方法细节，可以参见前面实施例的描述，这里不再赘述。
下面结合一个更为具体的实例，对本说明书提供的就餐业务处理方法进行说明。
某用户在赶往某商户的路上，通过其手机的支付宝客户端A，点击支付宝中的预约按钮，选择预约该商户，并输入了就餐人数、预定到店时间等预约占座信息。
用户手机中的支付宝客户端A将用户输入的预约占座信息发送至该商户的支付宝客户端B，支付宝客户端B根据该信息中的就餐人数、预定到店时间，确定该用户预约占座的桌型及用餐时间段，从而根据该商户内该桌型及时间段内，预约占座的人数，确定该用户的排队号码，并将所确定的排队号码发送至支付宝客户端A。
支付宝客户端A接收到该号码后，即确定预约成功，便可以在手机界面中向用户展示点餐按钮，用户点击该按钮后，跳转到点餐界面。点餐界面中可以展示商户的各类菜品、价格等信息，以及加入购物车、确认完成点餐等操作按钮。
用户确认完成点餐后，支付宝客户端A将用户所点菜品的名称、数量及其他要求等信息，发送至支付宝客户端B。支付宝客户端B接收到点餐信息后，向商户展示本次点餐的处理操作接口，商户可以直接下单完成点餐，而支付宝客户端B将生成包括总金额等信息的订单信息，发送至支付宝客户端A。
如果用户未准时到店，则预约占座失效，需要重新预约，如果用户上次未点餐，还可以再点餐，如果用户上次已经点餐，则可以直接使用上次的点餐信息，或者在此基础上调整菜品。
此外，支付宝客户端A还可以根据用户的芝麻信用，判断是否通知商户提前备菜，如果用户的芝麻信用高于预设值，如500，或者无负面记录，则通知商户可以提前备菜。并且，周期性地获取用户手机的LBS(Location Based Service，基于移动位置服务)信息，发送至支付宝服务端，以便支付宝客户端B接收到提前备菜通知后，可以获取并判断用户当前的位置，估算用户是否能准时或提前到店，如果预计用户可以准时到店，则根据点餐信息估算备菜时间，提前一定时间备菜，以保证用户准时到店时可以上菜。
通知商户提前备菜后，如果用户准时到达商户(或者到达商户1千米范围内)，支付宝客户端A可以向用户展示通知商户上菜的按钮，用户点击该按钮后，商户便可以开始上提前备好的菜品，用户也可以根据实际需求，通过支付宝客户端A的点餐按钮加菜。
根据不同商户的不同规定，用户可以在就餐前或就餐后，通过支付宝客户端A，对本次就餐时的菜品进行支付。
可见，应用上述方案，用户只需使用支付宝1个应用程序，便可以完成从预约、点餐到支付的整个过程，操作过程简便。而商户的工作人员，也可以通过支付宝客户端，统一地接收与查看用户的各项信息，从而统一地安排座位与菜品，工作流程更加简洁，节省了人力，且降低发生错误的可能性。此外，就餐过程中的数据均基于同1个应用程序系统产生，及预约、点餐、支付等操作的数据可以直接共享，而不必用户或商户工作人员手动输入，且可以确保数据的可靠性，因而有利于向用户及商户提供更优质的服务。
相应于上述方法实施例，本说明书实施例还提供一种就餐业务处理装置，应用于用户客户端，参见图5所示，该装置可以包括：
预约占座模块110，用于接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端，以指示根据该预约占座信息、及商户当前的座位信息，返回预约占座结果；
点餐模块120，用于接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
结算支付模块130，用于接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
在本说明书提供的一种具体实施方式中，参见图6所示，该装置还可以包括：
备菜通知模块140，用于根据用户的预约占座信用值，确定是否通知商户提前备菜；若是，则用户客户端向商户客户端发送提前备菜通知。
在本说明书提供的一种具体实施方式中，参见图6所示，该装置还可以包括：
上菜通知模块150，用于获得用户当前的位置信息，在用户与商户的距离小于预设阈值的情况下，展示通知上菜操作接口。
在本说明书提供的一种具体实施方式中，参见图6所示，该装置还可以包括：
失效判断模块160，用于根据所述预约占座信息及用户当前的位置信息，判断用户是否在预定到店时间段内到店；若否，则判定本次预约占座失效，并展示预约占座操作接口。
在本说明书提供的一种具体实施方式中，所述点餐模块120，具体可以用于：
在接收到商户客户端返回的预约占座成功的结果后，确定是否存在针对同一商户的失效的预约占座；若是，则展示点餐操作接口、及该次失效预约占座的点餐信息。
可以理解的是，备菜通知模块140、上菜通知模块150与失效判断模块160作为功能独立的模块，既可以如图6所示同时配置在装置中，也可以分别单独配置在装置中，因此图6所示的结构不应理解为对本说明书实施例方案的限定。
本说明书实施例还提供一种就餐业务处理装置，应用于商户客户端，参见图7所示，该装置可以包括：
预约占座处理模块210，用于接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
点餐处理模块220，用于接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户。
在本说明书提供的一种具体实施方式中，参见图8所示，所述装置还可以包括：
备菜时间点确定模块230，用于在接收到所述提前备菜通知后，根据所述预约占座信息、用户当前的位置信息、和/或商户当前的座位信息，估算上菜时间点；并根据所述点餐信息，估算备菜所需时长；根据所估算的上菜时间点、及备菜所需时长，确定提前备菜时间点。
上述装置中各个模块的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
本说明书实施例还提供一种计算机设备，其至少包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，处理器执行所述程序时实现前述的就餐业务处理方法。该方法至少包括：
一种就餐业务处理方法，该方法包括：
用户客户端接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端；
商户客户端接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
用户客户端接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
商户客户端接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端；
用户客户端接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
图9示出了本说明书实施例所提供的一种更为具体的计算设备硬件结构示意图，该设备可以包括：处理器1010、存储器1020、输入/输出接口1030、通信接口1040和总线1050。其中处理器1010、存储器1020、输入/输出接口1030和通信接口1040通过总线1050实现彼此之间在设备内部的通信连接。
处理器1010可以采用通用的CPU(Central Processing Unit，中央处理器)、微处理器、应用专用集成电路(应用程序lication Specific Integrated Circuit，ASIC)、或者一个或多个集成电路等方式实现，用于执行相关程序，以实现本说明书实施例所提供的技术方案。
存储器1020可以采用ROM(Read Only Memory，只读存储器)、RAM(Random Access Memory，随机存取存储器)、静态存储设备，动态存储设备等形式实现。存储器1020可以存储操作系统和其他应用程序，在通过软件或者固件来实现本说明书实施例所提供的技术方案时，相关的程序代码保存在存储器1020中，并由处理器1010来调用执行。
输入/输出接口1030用于连接输入/输出模块，以实现信息输入及输出。输入输出/模块可以作为组件配置在设备中(图中未示出)，也可以外接于设备以提供相应功能。其中输入设备可以包括键盘、鼠标、触摸屏、麦克风、各类传感器等，输出设备可以包括显示器、扬声器、振动器、指示灯等。
通信接口1040用于连接通信模块(图中未示出)，以实现本设备与其他设备的通信交互。其中通信模块可以通过有线方式(例如USB、网线等)实现通信，也可以通过无线方式(例如移动网络、WIFI、蓝牙等)实现通信。
总线1050包括一通路，在设备的各个组件(例如处理器1010、存储器1020、输入/输出接口1030和通信接口1040)之间传输信息。
需要说明的是，尽管上述设备仅示出了处理器1010、存储器1020、输入/输出接口1030、通信接口1040以及总线1050，但是在具体实施过程中，该设备还可以包括实现正常运行所必需的其他组件。此外，本领域的技术人员可以理解的是，上述设备中也 可以仅包含实现本说明书实施例方案所必需的组件，而不必包含图中所示的全部组件。
本说明书实施例还提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现前述的就餐业务处理方法。该方法至少包括：
一种就餐业务处理方法，该方法包括：
用户客户端接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端；
商户客户端接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
用户客户端接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
商户客户端接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端；
用户客户端接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到本说明书实施例可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本说明书实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本说明书实施例各个实施例或者实施例的某些部分所述的方法。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于装置实施例而言，由于其基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，在实施本说明书实施例方案时可以把各模块的功能在同一个或多个软件和/或硬件中实现。也可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
以上所述仅是本说明书实施例的具体实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本说明书实施例原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本说明书实施例的保护范围。

Claims (16)

  1. 一种就餐业务处理方法，该方法包括：
    用户客户端接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端；
    商户客户端接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
    用户客户端接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
    商户客户端接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端；
    用户客户端接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
  2. 根据权利要求1所述的方法，在用户客户端将用户输入的点餐信息发送至商户客户端的情况下，所述方法进一步包括：
    用户客户端根据用户的预约占座信用值，确定是否通知商户提前备菜。
  3. 根据权利要求2所述的方法，若是，则用户客户端向商户客户端发送提前备菜通知；
    商户客户端在接收到所述提前备菜通知后，根据所述预约占座信息、用户当前的位置信息、和/或商户当前的座位信息，估算上菜时间点；并根据所述点餐信息，估算备菜所需时长；
    商户客户端根据所估算的上菜时间点、及备菜所需时长，确定提前备菜时间点。
  4. 根据权利要求3所述的方法，在用户客户端向商户客户端发送提前备菜通知的情况下，所述方法进一步包括：
    用户客户端获得用户当前的位置信息，在用户与商户的距离小于预设阈值的情况下，展示通知上菜操作接口。
  5. 根据权利要求1至4任一项所述的方法，在用户客户端将用户输入的点餐信息发送至商户客户端的情况下，所述方法进一步包括：
    用户客户端根据所述预约占座信息及用户当前的位置信息，判断用户是否在预定到店时间段内到店；若否，则判定本次预约占座失效，并展示预约占座操作接口。
  6. 根据权利要求5所述的方法，在用户客户端接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口，包括：
    在用户客户端接收到商户客户端返回的预约占座成功的结果后，确定是否存在针对同一商户的失效的预约占座；
    若是，则展示点餐操作接口、及该次失效预约占座的点餐信息。
  7. 一种就餐业务处理方法，应用于用户客户端，该方法包括：
    接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端，以指示根据该预约占座信息、及商户当前的座位信息，返回预约占座结果；
    接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
    接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
  8. 一种就餐业务处理方法，应用于商户客户端，该方法包括：
    接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
    接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端。
  9. 一种就餐业务处理系统，该系统包括：用户客户端及商户客户端；
    用户客户端接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端；
    商户客户端接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
    用户客户端接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
    商户客户端接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端；
    用户客户端接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
  10. 根据权利要求9所述的系统，在用户客户端将用户输入的点餐信息发送至商户客户端的情况下，所述系统进一步包括：
    用户客户端根据用户的预约占座信用值，确定是否通知商户提前备菜。
  11. 根据权利要求10所述的系统，若是，则用户客户端向商户客户端发送提前备菜通知；
    商户客户端在接收到所述提前备菜通知后，根据所述预约占座信息、用户当前的位置信息、和/或商户当前的座位信息，估算上菜时间点；并根据所述点餐信息，估算备菜所需时长；
    商户客户端根据所估算的上菜时间点、及备菜所需时长，确定提前备菜时间点。
  12. 根据权利要求11所述的系统，在用户客户端向商户客户端发送提前备菜通知的情况下，所述系统进一步包括：
    用户客户端获得用户当前的位置信息，在用户与商户的距离小于预设阈值的情况下，展示通知上菜操作接口。
  13. 根据权利要求9至12任一项所述的系统，在用户客户端将用户输入的点餐信息发送至商户客户端的情况下，所述系统进一步包括：
    用户客户端根据所述预约占座信息及用户当前的位置信息，判断用户是否在预定到店时间段内到店；若否，则判定本次预约占座失效，并展示预约占座操作接口。
  14. 根据权利要求13所述的系统，用户客户端具体通过以下方式在接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口：
    在接收到商户客户端返回的预约占座成功的结果后，确定是否存在针对同一商户的失效的预约占座；
    若是，则展示点餐操作接口、及该次失效预约占座的点餐信息。
  15. 一种就餐业务处理装置，应用于用户客户端，该装置包括：
    预约占座模块，用于接收到预约占座操作触发后，将用户输入的预约占座信息发送至商户客户端，以指示根据该预约占座信息、及商户当前的座位信息，返回预约占座结果；
    点餐模块，用于接收到商户客户端返回的预约占座成功的结果后，展示点餐操作接口；并在确认用户完成点餐后，将用户输入的点餐信息发送至商户客户端；
    结算支付模块，用于接收到商户客户端发送的订单信息后，展示结算操作接口；并在接收到结算操作触发后，根据接收到的订单信息，对本次就餐业务进行结算付款。
  16. 一种就餐业务处理装置，应用于商户客户端，该装置包括：
    预约占座处理模块，用于接收到用户客户端发送的预约占座信息后，根据该预约占座信息、及商户当前的座位信息，向用户客户端返回预约占座结果；
    点餐处理模块，用于接收到用户客户端发送的点餐信息后，展示点餐处理操作接口；并在确认商户完成本次点餐后，将生成的订单信息发送至用户客户端。
PCT/CN2019/079165 2018-06-19 2019-03-22 一种就餐业务处理方法及系统 WO2019242354A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810631971.4 2018-06-19
CN201810631971.4A CN109003205A (zh) 2018-06-19 2018-06-19 一种就餐业务处理方法及系统

Publications (1)

Publication Number Publication Date
WO2019242354A1 true WO2019242354A1 (zh) 2019-12-26

Family

ID=64600783

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/079165 WO2019242354A1 (zh) 2018-06-19 2019-03-22 一种就餐业务处理方法及系统

Country Status (3)

Country Link
CN (1) CN109003205A (zh)
TW (1) TWI724382B (zh)
WO (1) WO2019242354A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109003205A (zh) * 2018-06-19 2018-12-14 阿里巴巴集团控股有限公司 一种就餐业务处理方法及系统
CN109657827B (zh) * 2018-12-19 2020-07-17 口碑(上海)信息技术有限公司 基于资源状态的服务预约方法及装置
CN109816126B (zh) * 2019-01-04 2021-05-04 口碑(上海)信息技术有限公司 订餐信息的处理方法、装置及系统
CN110738340B (zh) * 2019-09-06 2022-04-19 口碑(上海)信息技术有限公司 预约产品的库存管理方法及装置
CN113890944B (zh) * 2020-07-03 2023-07-21 中移互联网有限公司 一种通话方法、系统和装置
CN113627632A (zh) * 2021-07-28 2021-11-09 的卢技术有限公司 一种台球桌预约方法、系统、介质及设备
CN114997857B (zh) * 2022-08-08 2022-11-08 小白智能科技（长春）股份有限公司 一种用于餐厅桌面可完成用餐服务的机器人及其控制方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104463721A (zh) * 2014-11-11 2015-03-25 陈志雄 基于智能移动终端的排队方法
US20160253599A1 (en) * 2015-02-26 2016-09-01 United Airlines, Inc. Method and system for automating passenger seat assignment procedures
CN107481119A (zh) * 2017-08-21 2017-12-15 贵州西部生态链电子商务有限公司 一种基于大数据特征分析的云餐饮平台及分析方法
CN107657550A (zh) * 2017-10-02 2018-02-02 头等尝网络餐饮管理科技（深圳）有限公司 点餐系统及其控制方法、装置及计算机可读存储介质
CN107977721A (zh) * 2017-11-14 2018-05-01 深圳市思迅软件股份有限公司 订单处理方法、装置、服务器及可读存储介质
CN109003205A (zh) * 2018-06-19 2018-12-14 阿里巴巴集团控股有限公司 一种就餐业务处理方法及系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104463368B (zh) * 2014-12-09 2018-01-09 北京嘀嘀无限科技发展有限公司 用于确定订单的价值的方法及设备
CN104700149A (zh) * 2015-03-15 2015-06-10 王小安 一种订座订餐软件
CN105335912A (zh) * 2015-11-17 2016-02-17 贾崇丰 餐厅自动化系统的工作方法
CN105973249A (zh) * 2016-04-21 2016-09-28 深圳天珑无线科技有限公司 智能出行方法和系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104463721A (zh) * 2014-11-11 2015-03-25 陈志雄 基于智能移动终端的排队方法
US20160253599A1 (en) * 2015-02-26 2016-09-01 United Airlines, Inc. Method and system for automating passenger seat assignment procedures
CN107481119A (zh) * 2017-08-21 2017-12-15 贵州西部生态链电子商务有限公司 一种基于大数据特征分析的云餐饮平台及分析方法
CN107657550A (zh) * 2017-10-02 2018-02-02 头等尝网络餐饮管理科技（深圳）有限公司 点餐系统及其控制方法、装置及计算机可读存储介质
CN107977721A (zh) * 2017-11-14 2018-05-01 深圳市思迅软件股份有限公司 订单处理方法、装置、服务器及可读存储介质
CN109003205A (zh) * 2018-06-19 2018-12-14 阿里巴巴集团控股有限公司 一种就餐业务处理方法及系统

Also Published As

Publication number Publication date
TW202001776A (zh) 2020-01-01
TWI724382B (zh) 2021-04-11
CN109003205A (zh) 2018-12-14

Similar Documents

Publication Publication Date Title
WO2019242354A1 (zh) 一种就餐业务处理方法及系统
US20190205834A1 (en) Application programming interfaces for structuring distributed systems
US20130226627A1 (en) Mobile reservation application
AU2021254560A1 (en) Bill splitting system
JP2022110048A (ja) 分散システムを構造化するためのアプリケーションプログラミングインタフェース
WO2017212994A1 (ja) 店舗装置、情報処理方法、および記録媒体
KR101941203B1 (ko) 선입선출 기반의 식당 예약 시스템
CN110188903B (zh) 预点单信息的处理方法及装置
JP2019207740A (ja) 座席予約装置、座席予約方法、および座席予約プログラム
KR20120066273A (ko) 좌석 예약 경매 방법 및 그를 적용한 단말 장치
JP2019004207A (ja) インターホンシステムおよびインターホンプログラム
CN110852828A (zh) 一种数据处理方法、装置及系统
US11315096B2 (en) Payment support system, payment support method, and non-transitory recording medium
KR101599469B1 (ko) 쇼핑 서비스 제공 시스템 및 쇼핑 서비스 제공 방법
US20160225069A1 (en) Needs based auction bids, inquiry bids, and bid to deal conversion
JP2019114105A (ja) 情報管理装置、情報管理方法及びプログラム
KR101816293B1 (ko) 쇼핑 서비스 제공 시스템 및 쇼핑 서비스 제공 방법
US11321699B2 (en) Payment support system, payment support method, and non-transitory recording medium
KR101745603B1 (ko) 쇼핑 서비스 제공 방법
JP6448100B1 (ja) 予約システム
JP2019160338A (ja) キャンセル料算出装置、キャンセル料算出方法およびキャンセル料算出プログラム
JP2018169711A (ja) オーダー管理システム、オーダー管理方法及びプログラム
JP6405825B2 (ja) 端末、システム、情報提供方法
US20220405868A1 (en) Automatic Restaurant Ordering System
KR101940072B1 (ko) 가상현실 체험을 통한 영업점 예약 서비스 제공 방법, 서버 및 시스템

Legal Events

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

Ref document number: 19822747

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19822747

Country of ref document: EP

Kind code of ref document: A1