WO2018133699A1 - 一种业务对象预订系统、方法及装置 - Google Patents

一种业务对象预订系统、方法及装置 Download PDF

Info

Publication number
WO2018133699A1
WO2018133699A1 PCT/CN2018/071872 CN2018071872W WO2018133699A1 WO 2018133699 A1 WO2018133699 A1 WO 2018133699A1 CN 2018071872 W CN2018071872 W CN 2018071872W WO 2018133699 A1 WO2018133699 A1 WO 2018133699A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription
information
request
reservation
inventory
Prior art date
Application number
PCT/CN2018/071872
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 阿里巴巴集团控股有限公司
Priority to JP2019539285A priority Critical patent/JP2020506470A/ja
Priority to KR1020197020498A priority patent/KR20190103199A/ko
Publication of WO2018133699A1 publication Critical patent/WO2018133699A1/zh
Priority to US16/514,888 priority patent/US20190340710A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders

Definitions

  • the present application relates to the field of electronic technologies, and in particular, to a business object reservation system, method, and apparatus.
  • Hotel online booking service refers to the process of providing Internet service for hotel room reservation by providing users with a web page or mobile application (app) for users to fill in hotel reservation information and submit the reservation information to the hotel.
  • the existing subscription service is that after the client submits the subscription information to the platform server, the platform server initiates a request to the agent system, and then the agent system sends a request to the channel management system, and the channel management system requests again.
  • the hotel property management system (PMS) system finally returns the booking result, that is, the created order information to the client.
  • the booking success rate is low. For example, suppose the processing success rate of each system is 99%. After the online booking service system, agent system, channel management system, and hotel PMS system, the total success rate is 99% of the 4th power, which is approximately equal to 96%.
  • the subsequent order information creation process has a lot of links, resulting in a low booking success rate.
  • the embodiment of the present application provides a service object reservation system, method, and device, which are used to solve the problem that the order information creation process passes through many links, resulting in a low subscription success rate.
  • the embodiment of the present application provides a business object reservation system, including:
  • a platform server configured to receive a first subscription request that is sent by the client and carry the subscription object information; and determine, according to the subscription object information and the inventory reservation information, whether the subscription information of the inventory satisfies the first reservation request, wherein the inventory
  • the subscription information is obtained by the platform server pre-initiating the second subscription request carrying the subscription object information; if yes, generating the first subscription result corresponding to the first subscription request, and if not, passing the service to the service object server Sending the first reservation request to obtain a first reservation result; feeding the first reservation result to the client;
  • a client configured to receive subscription object information submitted by the user, and send the first subscription request to the platform server based on the subscription object information; and receive, by the platform server, subscription object information in the first subscription request and the The first reservation result of the inventory reservation information feedback;
  • a service object server configured to receive the second subscription request initiated by the platform server, and feed back a second subscription result to the platform server, where the second subscription result includes a second subscription request
  • the information about the subscription success is used as the subscription information of the initial inventory of the platform server; and is further configured to receive the first subscription request initiated by the user sent by the platform server, and feed back to the platform server A booking result.
  • the embodiment of the present application provides a business object reservation method, including:
  • the platform server Receiving, by the platform server, a first subscription request sent by the client; the first subscription request carries the subscription object information;
  • the subscription information of the inventory includes a platform server in advance to a business object After the server initiates the second reservation request carrying the reservation object information, the obtained reservation success information;
  • the first subscription result is fed back to the client.
  • the embodiment of the present application further provides a business object reservation method, including:
  • the client receives the subscription object information submitted by the user;
  • the platform server Receiving, by the platform server, a first subscription result that is fed back based on the subscription object information in the first subscription request and the subscription information of the inventory; wherein the subscription information of the inventory includes a platform server that initiates carrying a subscription to the business object server in advance After the second reservation request of the object information, the obtained reservation success information; the first reservation result includes information about the subscription success corresponding to the first reservation request.
  • the embodiment of the present application provides a platform server, including:
  • a receiving module configured to receive a first subscription request sent by the client, where the first subscription request carries the subscription object information
  • a reservation processing module configured to determine, according to the subscription object information in the first reservation request and the subscription information of the inventory, whether the subscription information of the inventory satisfies the first reservation request; wherein the subscription information of the inventory includes an advance After the second module request carrying the reservation object information is sent to the service object server by the sending module, the obtained reservation success information; if the inventory subscription information satisfies the first reservation request, based on the first reservation request Corresponding subscription object information, generating a first subscription result; if the inventory subscription information does not satisfy the first subscription request, the control sending module sends the first subscription request to the service object server, and by using the Receiving, by the receiving module, the first subscription result fed back by the service object server;
  • the sending module is further configured to feed back the first subscription result to the client.
  • the embodiment of the present application further provides a client, including:
  • a first receiving module configured to receive subscription object information submitted by a user
  • a first generating module configured to generate a first subscription request based on the subscription object information, where the first subscription request carries the subscription object information
  • a sending module configured to send the first subscription request
  • a second receiving module configured to receive, by the platform server, a first subscription result that is fed back based on the subscription object information in the first subscription request and the subscription information in the inventory; wherein the inventory subscription information includes a platform server in advance The information that the service object server initiates the second reservation request with the reservation object information, and the obtained reservation success information; the first reservation result includes the information about the subscription success corresponding to the first reservation request.
  • the platform server may initiate a reservation request to the business object server outside the system before the user actually initiates the reservation request to the platform server, and store the obtained reservation result as the subscription information of the initial inventory.
  • the subscription result corresponding to the actual subscription request of the user is returned to the client based on the subscription information of the local inventory.
  • Figure 1 is a schematic diagram of a reservation process in the background
  • FIG. 2 is a flowchart of a service object reservation method according to Embodiment 1 of the present application.
  • FIG. 4 is a flowchart of a service object reservation method according to Embodiment 2 of the present application.
  • FIG. 5 is a schematic diagram of a service object reservation system according to Embodiment 3 of the present application.
  • FIG. 6 is a schematic structural diagram of a platform server according to Embodiment 4 of the present application.
  • FIG. 7 is a schematic structural diagram of a client provided in Embodiment 5 of the present application.
  • the embodiment of the present application is mainly applied to a scenario in which a platform server needs to send a reservation request to a service object server outside the system to provide a subscription result for the client user.
  • the platform server after receiving the subscription request actually initiated by the user, the platform server requests the subscription result to the service object server outside the system, because the subscription process experiences more links.
  • the booking request failure rate is high.
  • a flowchart of a service object reservation method according to Embodiment 1 of the present application includes:
  • S201 The client receives the subscription object information submitted by the user.
  • the information of the reservation object submitted by the user may include information such as the hotel name and the room type.
  • S202 The client sends a first reservation request to the platform server based on the received subscription object information, where the first reservation request carries the subscription object information.
  • the client transmits a first reservation request carrying the subscription object information selected by the user to the platform server.
  • the platform server determines, according to the reservation object information in the first reservation request and the inventory reservation information, whether the reservation information of the inventory satisfies the first reservation request, if the process proceeds to S204a, if not, the process proceeds to S204b;
  • the subscription information of the inventory includes information that the platform server obtains the subscription success after the second registration request that carries the subscription object information is previously sent to the service object server.
  • the platform server initiates a second subscription request carrying the subscription object information to the business object server according to the inventory requirement in the future subscription period, and after the subscription is successful, the subscription returned by the storage service object server is successful. Reservation information. After receiving the subscription request actually initiated by the user, first check whether the stored subscription information can satisfy the subscription request of the user, and if yes, return the subscription result directly to the user, see S204a, if not, According to the existing process, a request is sent to the business object server, see S204b.
  • the platform server determines, according to the historical subscription data, an inventory requirement in a future subscription time period, the historical subscription data includes a subscription object provided for the business object server, and the subscription data of the user actually initiates the reservation, where the inventory requirement includes each user
  • the total amount of demand for each subscription object provided by the business object server (such as the number of standard rooms, how many rooms are needed for the double bed room); sending a second reservation request to the business object server according to the determined inventory demand; receiving the service
  • the second subscription result returned by the object server carrying the information of the subscription success is used as the subscription information of the initial inventory.
  • the historical subscription data here can be stored in the platform server, or can be stored in a separate database, and the platform server initiates a query request to the database when needed.
  • the platform server may predict, according to the historical order data corresponding to the plurality of service object service parties (such as a certain hotel), the inventory demand information for each business object service party within the subscription time period. Thereafter, a second subscription request is sent to the business object server (such as the hotel management system of the hotel) corresponding to the business object server according to the predicted inventory demand for the business object server.
  • the business object server such as the hotel management system of the hotel
  • the mapping relationship between the obtained subscription success information and the service party identification information (such as the hotel name) corresponding to the service object server is established. And store the mapping as inventory reservation information.
  • the subscription information corresponding to the service party identification information is searched for from the inventory reservation information, and then according to the Other subscription object information (room type, number of rooms, such as two rooms in the standard room) in the first reservation request, and whether the information of the found reservation success satisfies the first reservation request.
  • the platform server sends the second reservation request to the business object server, firstly, the second reservation request is initiated to the agent system, and the agent system receives the first request. After the second reservation request, the channel management system continues to initiate the request, and finally the channel management system initiates a request to the business object server (such as the hotel management system), and returns the second reservation result returned by the business object server to the agent system.
  • the business object server such as the hotel management system
  • the platform server stores the obtained second reservation result as the reservation information of the initial inventory, such as recording the hotel name, hotel room type, check-in time, order number, etc. of the reservation.
  • the platform server When the subscription information of the inventory meets the first reservation request, the platform server generates a first reservation result based on the subscription object information corresponding to the first reservation request, and updates the reservation information of the inventory.
  • the platform server searches for the reservation information corresponding to the first reservation request from the inventory reservation information, and generates a first reservation result corresponding to the first reservation request based on the found reservation information.
  • the inventory reservation information includes 10 standard room information of a hotel chain that the platform server pre-booked successfully. If the first reservation request requests to book a standard room of the hotel chain, the previous reservation is successful. Choose one of the standard rooms and return the relevant order information (hotel information, room type, check-in time, order number, etc.) to the client.
  • the platform server since the platform server does not know the actual user information when the order is created in advance, when the order is created in advance, the default user information of the platform may be used to initiate the subscription, and subsequent After the order is created for the actual user, the order information update process is initiated.
  • the platform server generates a first subscription result based on the client user information carried in the first subscription request and the subscription object information corresponding to the first subscription request, where the first subscription result includes the first subscription request The subscription success information and the client user information; after generating the first subscription result, sending a subscription information update request to the business object server, the subscription information update request for requesting the user information associated with the first subscription result from the sending The default user information used in the second subscription request is updated to the client user information.
  • the platform server needs to carry the guest-related information in the pre-initiated second reservation request.
  • the platform server can use the default user information to initiate the hotel reservation request, and obtain the successfully booked hotel information as the initial inventory. Booking information.
  • the platform server may further initiate an order information update request to the hotel management system, and change the previously reserved default user information to the real client user information.
  • the platform server can ensure that the pre-completed subscription information is in an inventory-sufficient state to satisfy the subscription request initiated by the user in real time.
  • the platform server sends a first reservation request to the business object server when the subscription information of the inventory does not satisfy the first reservation request, and receives the first reservation result fed back by the business object server.
  • the platform server when the platform server is insufficient in inventory, for example, the client requests to subscribe to two standard rooms of a hotel, and there is no or only one standard room in the inventory, then the platform server can initiate the business object server according to the existing process. First booking request.
  • S205 The platform server feeds back the first subscription result to the client.
  • the first subscription result fed back to the client by the platform server may be the subscription result directly generated by the platform server if the inventory meets the demand, or may be the temporary request of the platform server to the business object server in case of insufficient inventory.
  • the client receives the first predetermined result returned by the server based on the inventory-based subscription information, and presents the first reservation result to the user.
  • the platform server may initiate a reservation request to the business object server outside the system before the user actually initiates the reservation request to the platform server, and store the obtained reservation result as the subscription information of the initial inventory.
  • the subscription result corresponding to the actual subscription request of the user is returned to the client based on the subscription information of the local inventory.
  • the platform server pre-booked 10 standard rooms with XX Hotel and YY Hotel according to the pre-stated inventory requirements.
  • User A subsequently initiated a request to subscribe to a standard room of XX Hotel.
  • the platform server was pre-stored.
  • the inventory information is determined to satisfy the subscription request of the user A, and the information about the reservation success related to a standard room of the XX hotel is provided to the user A, so that the user A can quickly obtain the information of the reservation success.
  • User B subsequently initiates a request to subscribe to a big bed room of YY hotel.
  • the platform server determines that the reservation request of user B cannot be satisfied, and then needs to temporarily send a reservation request to the YY hotel PMS system, and The booking result returned by the YY Hotel PMS system is returned to User B. Obviously, User B's booking process takes longer than User A.
  • the present application is applicable to any other scenario that requires the platform server to send a reservation request to the business object server to provide the subscription result for the client user, such as ticket reservation, movie ticket reservation, and the like.
  • the platform server counts user requirements in advance, initiates a reservation request to the service party outside the platform in advance, and stores the requested result of the reservation as inventory reservation information. Then, when the client actually initiates the request, the client provides the relevant subscription result based on the subscription information previously requested in advance.
  • a flowchart of a service object reservation method provided by Embodiment 2 of the present application includes:
  • the platform server determines, according to the historical subscription data, an inventory requirement in a future subscription time period; the historical subscription data includes a subscription object provided for the business object server, and the subscription data that the user actually initiates the reservation
  • the inventory requirement includes a total amount of demand of each user for a subscription object provided by the business object server.
  • the platform server may separately count each business object service party (such as XX hotel chain, YY hotel chain, etc.) in each subscription service according to various reservation services provided for the user (such as hotel reservation and air ticket reservation). It can also be a combination of hotel chains and agents) the inventory requirements of each business object (such as standard rooms, double rooms, etc.) that can be provided. Specifically, it is possible to count the order data completed for each business object within the latest preset duration (for example, one month), and the statistical order data predicts the inventory demand information of the business object within the reservation time period (such as one day).
  • the number of reservations for the standard room of the hotel chain in the last month is counted, so that the number of reservations per day for the standard room of the hotel chain can be predicted. It is about N/30, so the platform server can book N/30 standard rooms in the hotel chain at 7:00 am every day.
  • the foregoing prediction process is only an example.
  • the attribute information of the subscription time period (such as whether it is a holiday, whether an event is held in a specific city, etc.)
  • the same historical time period as the subscription time period attribute is obtained.
  • the order data is then predicted based on the order data. For example, if a booking period is during the May Day holiday, the order data of the May 1 period in the last 3 years can be obtained, and the order demand information of a request object is predicted based on the order data.
  • the platform server generates a second subscription request based on the predicted inventory demand for each business object within the subscription time period.
  • the platform server can complete the reservation of the business object within the reservation time period in one request, for example, predicting that the number of reservation requirements of the standard room of a hotel hotel is N/30 per day, then the platform The server may request the hotel management system to book N/30 standard room rooms of the hotel in a single booking request.
  • the platform server may also subscribe to N/30 standards of the hotel chain by initiating multiple booking requests. Rooms, such as booking only one room per request.
  • the length of the foregoing subscription time period may be one cycle
  • the platform server may periodically initiate a second subscription request to obtain a second subscription result.
  • the server may initiate the system outside the morning. Hotel reservation request to book the hotel room on the day.
  • the platform server sends a second subscription request to the service object server according to the determined inventory requirement, where the second subscription request carries default user information.
  • the platform server may also initiate a cancellation request to the business object server when the remaining business objects are not subscribed in the reservation information of the determined inventory according to the subscription request actually initiated by the client. For example, the platform server requests to book 10 standard room rooms of a hotel chain at 7:00 in the morning, and finds that the remaining 5 rooms are not reserved at 6 pm, at which time the platform server can initiate a request to cancel the reservation of the five rooms.
  • the platform server receives a second subscription result that is returned by the service object server and carries the information about the subscription success, and is used as the subscription information of the initial inventory.
  • S404 The client receives the subscription object information submitted by the user.
  • S405 The client sends a first reservation request to the platform server based on the received subscription object information, where the first reservation request carries the subscription object information and the client user information.
  • the platform server determines, according to the subscription object information in the first reservation request and the subscription information of the inventory, whether the subscription information of the inventory satisfies the first reservation request, and if it satisfies the process of proceeding to S407a, if not, the process proceeds to S407b.
  • S407a When the subscription information of the inventory meets the first reservation request, the platform server generates a first reservation result, updates the inventory reservation information, and proceeds to S408 and S409 based on the subscription object information corresponding to the first reservation request and the client user information.
  • S408 Send a subscription information update request to the business object server, to request that the user information associated with the first subscription result is updated from the default user information used when the second subscription request is sent to the client user information.
  • the platform server sends a first reservation request to the business object server when the subscription information of the inventory does not satisfy the first reservation request, and receives the first reservation result fed back by the business object server.
  • the platform server initiates the subscription based on the normal subscription process.
  • the client receives a first subscription result fed back by the platform server based on the subscription object information in the first reservation request and the subscription information of the inventory.
  • the platform server may initiate a reservation request to the business object server outside the system before the user actually initiates the reservation request to the platform server, and store the obtained reservation result as the subscription information of the initial inventory.
  • the subscription result corresponding to the actual subscription request of the user is returned to the client based on the subscription information of the local inventory.
  • the embodiment of the present invention further provides a service object reservation system and device corresponding to the business object reservation method.
  • the principle of the system and the device for solving the problem is similar to the business object reservation method in the embodiment of the present application. Therefore, the implementation of the system and the device can be referred to the implementation of the method, and the repeated description is not repeated.
  • a schematic diagram of a business object reservation system 500 provided in Embodiment 3 of the present application includes:
  • the platform server 51 is configured to receive a first subscription request that is sent by the client and that carries the subscription object information, and determine, according to the subscription object information and the inventory reservation information, whether the subscription information of the inventory satisfies the first reservation request, where The subscription information of the inventory is obtained by the platform server pre-initiating the second reservation request carrying the reservation object information; if yes, the first reservation result corresponding to the first reservation request is generated, and if not, the service object is Sending, by the server, the first subscription request to obtain a first subscription result; and feeding back the first subscription result to the client;
  • the client 52 is configured to receive the subscription object information submitted by the user, and send the first subscription request to the platform server based on the subscription object information; and receive, by the platform server, the subscription object information and the location in the first subscription request.
  • the service object server 53 is configured to receive the second subscription request initiated by the platform server, and feed back a second subscription result to the platform server, where the second subscription result includes the second subscription request Corresponding information about the success of the subscription, used as the subscription information of the initial inventory of the platform server; and configured to receive the first subscription request initiated by the user sent by the platform server, and feed back to the platform server First booking result.
  • the subscription object is a hotel
  • the business object server is a hotel management server
  • the subscription object information includes a reserved hotel name and a room type.
  • the platform server 51 is specifically configured to initiate the second subscription request according to the following steps:
  • the historical subscription data including subscription data for a user to actually initiate a subscription for the subscription object, the inventory requirement including each user providing for the business object server The total amount of demand for the booked object;
  • the first subscription request further carries client user information;
  • the second subscription request further carries default user information;
  • the platform server 51 is specifically configured to generate the first subscription result according to the following steps:
  • the first subscription result includes the The information of the subscription success corresponding to the first reservation request and the client user information;
  • the platform server 51 is also used to:
  • the subscription information update request is for requesting to send user information associated with the first subscription result from sending the second subscription
  • the default user information used at the request is updated to the client user information
  • the business object server 53 is also used to:
  • the platform server 51 is further configured to:
  • the inventory alarm information is pushed to the management party to prompt the management party to select whether to replenish the inventory; or, the subscription process is automatically initiated to the business object server.
  • FIG. 6 is a schematic structural diagram of a platform server 600 according to Embodiment 4 of the present application, including:
  • the receiving module 61 is configured to receive a first subscription request sent by the client, where the first subscription request carries the subscription object information;
  • the subscription processing module 62 is configured to determine, according to the subscription object information in the first subscription request and the subscription information of the inventory, whether the subscription information of the inventory satisfies the first subscription request; wherein the subscription information of the inventory includes Receiving, by the sending module 63, the information about the successful reservation after the second subscription request carrying the reservation object information is sent to the business object server; if the inventory subscription information satisfies the first reservation request, based on the first And generating, by the reservation object corresponding to the reservation request, a first reservation result; if the inventory reservation information does not satisfy the first reservation request, the control sending module 63 sends a first reservation request to the service object server, and passes the receiving module 61. Receiving a first subscription result fed back by the business object server;
  • the sending module 63 is further configured to feed back the first subscription result to the client.
  • the subscription processing module 62 is specifically configured to send the second subscription request according to the following steps:
  • the historical subscription data including subscription data for a user to actually initiate a subscription for the subscription object, the inventory requirement including each user providing for the business object server The total amount of demand for the booked object;
  • the first subscription request further carries client user information;
  • the second subscription request further carries default user information;
  • the subscription processing module 62 is specifically configured to generate the first subscription result according to the following steps:
  • the first subscription result includes the The information of the subscription success corresponding to the first reservation request and the client user information;
  • the sending module 63 is further configured to:
  • the subscription information update request is for requesting that the user information associated with the first subscription result be updated from the default user information used when the second subscription request is sent to Describe client user information.
  • the subscription processing module 62 is further configured to:
  • the inventory reservation information is updated.
  • the subscription processing module 62 is further configured to:
  • the subscription process is automatically initiated to the business object server.
  • the first subscription request further carries service provider identifier information
  • the platform server 600 further includes:
  • the storage module 64 is configured to: after the sending module 63 initiates the second subscription request carrying the subscription object information to the service object server, establish a mapping between the obtained subscription success information and the service party identity information corresponding to the service object server. Relationship, and store the mapping relationship as inventory reservation information;
  • the subscription processing module 62 is specifically configured to determine, according to the following steps, whether the subscription information of the inventory satisfies the first subscription request:
  • the platform server may pre-initiate a reservation request to the business object server outside the system before the user actually initiates the reservation request to the platform server, and store the obtained reservation result as the initial inventory reservation information.
  • the subscription result corresponding to the actual subscription request of the user is returned to the client based on the subscription information of the local inventory. In this way, since the platform server does not need to temporarily initiate a request to the service object server when receiving the client request, the client can obtain the reservation result returned by the platform server in time, thereby improving the reservation efficiency and the subscription success rate, thereby improving the user experience. .
  • FIG. 7 is a schematic structural diagram of a client 700 according to Embodiment 5 of the present application, including:
  • the first receiving module 71 is configured to receive subscription object information submitted by the user
  • a generating module 72 configured to generate a first subscription request based on the subscription object information, where the first subscription request carries the subscription object information;
  • a sending module 73 configured to send the first subscription request
  • a second receiving module 74 configured to receive, by the platform server, a first subscription result that is fed back based on the subscription object information in the first subscription request and the subscription information in the inventory; wherein the inventory subscription information includes a platform server in advance After the second subscription request carrying the reservation object information is sent to the business object server, the obtained subscription success information is included; the first subscription result includes information about the subscription success corresponding to the first subscription request.
  • the above-mentioned client can promptly return the subscription result returned by the platform server based on the pre-stored subscription information, thereby improving the reservation efficiency and the subscription success rate, thereby improving the user experience.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Tourism & Hospitality (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Development Economics (AREA)
  • Databases & Information Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Health & Medical Sciences (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请涉及电子技术领域，尤其涉及一种业务对象预订系统、方法及装置，用以解决预订流程经过的环节较多，导致预订成功率较低的问题。本申请实施例提供一种业务对象预订方法，包括：平台服务器接收客户端发送的第一预订请求；根据所述第一预订请求中的预订对象信息以及库存的预订信息，判断所述库存的预订信息是否满足所述第一预订请求；若满足，则基于所述第一预订请求对应的预订对象信息，生成第一预订结果；若不满足，则向所述业务对象服务器发送所述第一预订请求，并接收所述业务对象服务器反馈的第一预订结果；将所述第一预订结果反馈给所述客户端。

Description

一种业务对象预订系统、方法及装置
本申请要求2017年01月20日递交的申请号为201710045851.1、发明名称为“一种业务对象预订系统、方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及电子技术领域，尤其涉及一种业务对象预订系统、方法及装置。
背景技术
酒店在线预订服务是指通过向用户提供网页(web)页面或手机应用(app)，供用户填写酒店预订信息，并将预订信息提交给酒店，完成酒店客房预订的互联网服务过程。
如图1所示，现有的预订服务都是在客户端向平台服务器提交预订信息后，平台服务器向代理商系统发起请求，然后由代理商系统向渠道管理系统发送请求，渠道管理系统再请求酒店物业管理系统(Property Management System，PMS)系统，最后再将预订结果，也即创建完成的订单信息反馈给客户端。
可见，现有的订单信息创建流程经过的环节非常多，其中任何一个环节有问题就会导致预订失败，所以预订成功率较低。比如，假设每个系统的处理成功率是99％，经过在线预订服务系统、代理商系统、渠道管理系统、酒店PMS系统4个系统处理后总的成功率是99％的4次方，约等于96％。
综上，目前由于在用户提交预订信息后，后续的订单信息创建流程经过的环节非常多，导致预订成功率较低。
发明内容
本申请实施例提供一种业务对象预订系统、方法及装置，用以解决订单信息创建流程经过的环节较多，导致预订成功率较低的问题。
本申请实施例提供一种业务对象预订系统，包括：
平台服务器，用于接收客户端发送的携带有预订对象信息的第一预订请求；根据该预订对象信息以及库存的预订信息，判断库存的预订信息是否满足所述第一预订请求，其中所述库存的预订信息为平台服务器通过预先发起携带有预订对象信息的第二预订请求得到的；若满足，则生成所述第一预订请求对应的第一预订结果，若不满足，则通过 向业务对象服务器发送所述第一预订请求得到第一预订结果；将所述第一预订结果反馈给客户端；
客户端，用于接收用户提交的预订对象信息，并基于该预订对象信息向平台服务器发送所述第一预订请求；接收所述平台服务器基于所述第一预订请求中的预订对象信息和所述库存的预订信息反馈的所述第一预订结果；
业务对象服务器，用于接收所述平台服务器预先发起的所述第二预订请求，并向所述平台服务器反馈第二预订结果，所述第二预订结果中包含有与所述第二预订请求对应的预订成功的信息，用于作为所述平台服务器初始库存的预订信息；还用于接收所述平台服务器发送的由用户发起的所述第一预订请求，并向所述平台服务器反馈所述第一预订结果。
本申请实施例提供一种业务对象预订方法，包括：
平台服务器接收客户端发送的第一预订请求；所述第一预订请求中携带有预订对象信息；
根据所述第一预订请求中的预订对象信息以及库存的预订信息，判断所述库存的预订信息是否满足所述第一预订请求；其中所述库存的预订信息中包含有平台服务器预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息；
若满足，则基于所述第一预订请求对应的预订对象信息，生成第一预订结果；若不满足，则向所述业务对象服务器发送所述第一预订请求，并接收所述业务对象服务器反馈的第一预订结果；
将所述第一预订结果反馈给所述客户端。
本申请实施例还提供一种业务对象预订方法，包括：
客户端接收用户提交的预订对象信息；
向平台服务器发送第一预订请求；其中，所述第一预订请求中携带有所述预订对象信息；
接收所述平台服务器基于所述第一预订请求中的预订对象信息和库存的预订信息反馈的第一预订结果；其中所述库存的预订信息中包含有平台服务器预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息；所述第一预订结果中包含有与所述第一预订请求对应的预订成功的信息。
本申请实施例提供一种平台服务器，包括：
接收模块，用于接收客户端发送的第一预订请求；所述第一预订请求中携带有预订 对象信息；
预订处理模块，用于根据所述第一预订请求中的预订对象信息以及库存的预订信息，判断所述库存的预订信息是否满足所述第一预订请求；其中所述库存的预订信息中包含预先通过发送模块向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息；若所述库存的预订信息满足所述第一预订请求，则基于所述第一预订请求对应的预订对象信息，生成第一预订结果；若所述库存的预订信息不满足所述第一预订请求，则控制发送模块向所述业务对象服务器发送所述第一预订请求，并通过所述接收模块接收所述业务对象服务器反馈的第一预订结果；
所述发送模块，还用于将所述第一预订结果反馈给所述客户端。
本申请实施例还提供一种客户端，包括：
第一接收模块，用于接收用户提交的预订对象信息；
第一生成模块，用于基于所述预订对象信息，生成第一预订请求；其中，所述第一预订请求中携带有所述预订对象信息；
发送模块，用于发送所述第一预订请求；
第二接收模块，用于接收所述平台服务器基于所述第一预订请求中的预订对象信息和库存的预订信息反馈的第一预订结果；其中所述库存的预订信息中包含有平台服务器预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息；所述第一预订结果中包含有与所述第一预订请求对应的预订成功的信息。
采用上述实施例，平台服务器可以在用户实际向该平台服务器发起预订请求之前预先向系统外的业务对象服务器发起预订请求，将得到的预订结果作为初始库存的预订信息存储起来。在接收到客户端实际发起的预订请求后，再基于本地库存的预订信息向客户端返回与用户实际的预订请求对应的预订结果。这样，由于不需要平台服务器在接收到客户端请求时再临时向业务对象服务器发起请求，客户端可以及时得到平台服务器返回的预订结果，从而提高了预订效率及预订成功率，进而提升了用户体验。
附图说明
图1为背景中的预订流程示意图；
图2为本申请实施例一提供的业务对象预订方法流程图；
图3为本申请实施的一个示例效果图；
图4为本申请实施例二提供的业务对象预订方法流程图；
图5为本申请实施例三提供的业务对象预订系统示意图；
图6为本申请实施例四提供的平台服务器结构示意图；
图7为本申请实施例五提供的客户端结构示意图。
具体实施方式
本申请实施例主要应用在平台服务器需要向系统外的业务对象服务器发送预订请求才能为客户端用户提供预订结果的场景下。在这种场景下，按照现有的请求流程，平台服务端是在接收到用户实际发起的预订请求后，再向系统外的业务对象服务器请求预订结果，由于预订过程经历的环节较多，导致预订请求失败率较高。
下面以酒店预订为例，对本申请方案做进一步介绍。
实施例一
如图2所示，为本申请实施例一提供的业务对象预订方法流程图，包括：
S201：客户端接收用户提交的预订对象信息。
这里，针对酒店预订，用户提交的预订对象信息中可以包括酒店名称和房间类型等信息。
S202：客户端基于接收的预订对象信息，向平台服务器发送第一预订请求；其中，所述第一预订请求中携带有所述预订对象信息。
这里，客户端在用户确认预订后，向平台服务器发送携带有用户选择的预订对象信息的第一预订请求。
S203：平台服务器根据所述第一预订请求中的预订对象信息以及库存的预订信息，判断所述库存的预订信息是否满足所述第一预订请求，若满足进入S204a，若不满足，进入S204b；其中所述库存的预订信息中包含有平台服务器预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息。
在具体实施中，平台服务器会预先根据在未来预订时间段内的库存需求，向业务对象服务器发起携带有预订对象信息的第二预订请求，并在预订成功后，存储业务对象服务器返回的预订成功的预订信息。之后，在接收到用户实际发起的预订请求后，首先查看存储的预订信息是否能够满足用户的预订请求，若能够满足，则可以直接向用户返回预订结果，见S204a，若不满足，则还需要按照现有流程，向业务对象服务器发送请求，见S204b。
具体地，平台服务器根据历史预订数据，确定在未来预订时间段内的库存需求，该 历史预订数据包括针对业务对象服务器提供的预订对象，用户实际发起预订的预订数据，所述库存需求包括各用户针对所述业务对象服务器提供的每种预订对象的需求总量(比如标准间需求多少间，大床房需要多少间)；根据确定的库存需求，向业务对象服务器发送第二预订请求；接收业务对象服务器返回的携带预订成功的信息的第二预订结果，用于作为初始库存的预订信息。
这里的历史预订数据可以存储在平台服务器中，也可以存储在独立的数据库中，平台服务器在有需求时向数据库发起查询请求。
在实际实施时，平台服务器可以根据存储的与多个业务对象服务方(比如某个酒店)分别对应的历史订单数据，预测在预订时间段内，针对每个业务对象服务方的库存需求信息。之后，根据预测的针对该业务对象服务方的库存需求，向该业务对象服务方对应的业务对象服务器(比如酒店的酒店管理系统)发送第二预订请求。
在平台服务器预先向一个业务对象服务器发起携带有预订对象信息的第二预订请求后，建立得到的预订成功的信息与该业务对象服务器对应的服务方标识信息(比如酒店名称)之间的映射关系，并将该映射关系作为库存的预订信息进行存储。之后，在用户实际发起第一预订请求后，根据该第一预订请求中携带的服务方标识信息，从库存的预订信息中查找与该服务方标识信息对应的预订成功的信息，再根据所述第一预订请求中的其它预订对象信息(房间类型，房间数量，比如标准间2间)，判断查找到的预订成功的信息是否满足所述第一预订请求。
针对平台服务器→代理商系统→渠道管理系统→业务对象服务器这种请求路径，平台服务器在向业务对象服务器发送第二预订请求时，首先向代理商系统发起第二预订请求，代理商系统接收第二预订请求后，还会向渠道管理系统继续发起请求，最后由渠道管理系统向业务对象服务器(比如酒店管理系统)发起请求，并将业务对象服务器返回的第二预订结果再经过代理商系统返回给平台服务器。平台服务器将得到的第二预订结果存储起来，作为初始库存的预订信息，比如记录下预订成功的酒店名称、酒店房间类型、入住时间、订单号等。
S204a：平台服务器在库存的预订信息满足第一预订请求时，基于第一预订请求对应的预订对象信息，生成第一预订结果，并更新库存的预订信息。
这里，平台服务器从库存的预订信息中，查找是否存在与第一预订请求对应的预订信息，基于查找出的预订信息生成与第一预订请求对应的第一预订结果。比如，库存的预订信息中包括平台服务器预先预订成功的某连锁酒店的10间标准间客房信息，若第一 预订请求中请求预订一间该连锁酒店的标准间客房，则从之前预订成功的10间标准间客房中选择一间，并将相关订单信息(酒店信息、房间类型、入住时间、订单号等)返回给客户端。
在具体实施中，对于一些需要填写用户信息发起预订的场景，由于平台服务器预先创建订单时并不知道实际的用户信息，因此在预先创建订单时，可以首先使用平台默认的用户信息发起预订，后续在为实际用户创建订单后，再发起订单信息更新流程。
具体地，平台服务器基于第一预订请求中携带的客户端用户信息，和第一预订请求对应的预订对象信息，生成第一预订结果；其中，第一预订结果中包含有与第一预订请求对应的预订成功的信息和客户端用户信息；在生成第一预订结果之后，向业务对象服务器发送预订信息更新请求，该预订信息更新请求用于请求将与第一预订结果关联的用户信息从发送第二预订请求时使用的默认用户信息更新为客户端用户信息。
比如，根据酒店的预订要求，平台服务器需要在预先发起的第二预订请求中携带住客相关信息，此时平台服务器可以使用默认用户信息发起酒店预订请求，得到预订成功的酒店信息作为初始库存的预订信息。在接收到客户端用户实际发起的第一预订请求后，从之前预订好的房间中选择提供给客户端用户的房间，并向客户端返回使用真实的客户端用户信息生成的酒店预订结果，之后，平台服务器可以再向酒店管理系统发起订单信息更新请求，将之前预留的默认用户信息更改为真实的客户端用户信息。
可选地，在更新库存的预订信息之后，还可以判断所述预订对象的库存量是否低于设定阈值；若是，则向管理方推送库存告警信息，用于提示管理方选择是否补充库存；或者，自动向业务对象服务器发起预订流程。这样，平台服务器可以保证预先完成的预订信息处于库存充足的状态，以满足用户实时发起的预订请求。
S204b：平台服务器在库存的预订信息不满足第一预订请求时，向业务对象服务器发送第一预订请求，并接收业务对象服务器反馈的第一预订结果。
这里，平台服务器在库存不足时，比如客户端请求预订某酒店的2个标准间，库存中没有了或只剩1个标准间，则此时平台服务器可以按照现有流程，向业务对象服务器发起第一预订请求。
S205：平台服务器将第一预订结果反馈给客户端。
这里，平台服务器反馈给客户端的第一预订结果可能是在库存满足需求的情况下，平台服务器直接生成的预订结果，也可能是平台服务器在库存不足的情况下，临时向业务对象服务器请求回的预订结果。客户端接收服务端基于库存的预订信息返回的第一预 订结果，并将该第一预订结果展示给用户。
采用上述实施例，平台服务器可以在用户实际向该平台服务器发起预订请求之前预先向系统外的业务对象服务器发起预订请求，将得到的预订结果作为初始库存的预订信息存储起来。在接收到客户端实际发起的预订请求后，再基于本地库存的预订信息向客户端返回与用户实际的预订请求对应的预订结果。这样，由于不需要平台服务器在接收到客户端请求时再临时向业务对象服务器发起请求，客户端可以及时得到平台服务器返回的预订结果，从而提高了预订效率及预订成功率，进而提升了用户体验。
如图3所示，平台服务器根据预先统计的库存需求，分别向XX酒店和YY酒店预先预订了10间标准间，用户A后续发起了预订XX酒店一个标准间的请求，此时平台服务器根据预存的库存信息，确定满足用户A的预订请求，则将与XX酒店一个标准间相关的预订成功的信息提供给用户A，从而可以使用户A快速获取到预订成功的信息。而用户B后续发起了预订YY酒店一个大床房的请求，此时平台服务器根据预存的库存信息，确定无法满足用户B的预订请求，则就需要临时向YY酒店PMS系统发送预订请求，并将YY酒店PMS系统反馈的预订结果再返回给用户B，显然，相比用户A，用户B的预订过程需要的时间要长些。
在实际实施中，本申请除了酒店预订的场景外，还适用于其它任何需要平台服务器向业务对象服务器发送预订请求才能为客户端用户提供预订结果的场景，比如机票预订、电影票预订等。在这些场景下，平台服务器提前统计用户需求，预先向平台外的服务方发起预订请求，并将请求回的预订结果作为库存的预订信息进行存储。之后在客户端实际发起请求时，再基于之前预先请求回的预订信息为客户端提供相关预订结果。
下面再通过一个具体的实施例对本申请思想作进一步说明。
如图4所示，为本申请实施例二提供的业务对象预订方法流程图，包括：
S401：针对每个业务对象服务器，平台服务器根据历史预订数据，确定在未来预订时间段内的库存需求；所述历史预订数据包括针对该业务对象服务器提供的预订对象，用户实际发起预订的预订数据，所述库存需求包括各用户针对所述业务对象服务器提供的预订对象的需求总量。
在具体实施中，平台服务器可以根据为用户提供的各项预订服务(比如酒店预订、机票预订)，分别统计每项预订服务中每个业务对象服务方(比如XX连锁酒店、YY连锁酒店等，还可以是连锁酒店和代理商的组合)能够提供的每个业务对象(比如标准间客房、大床房等)的库存需求。具体地，可以统计在最近预设时长(比如一个月)内 针对每个业务对象完成的订单数据，基于统计的订单数据预测出在预订时间段(比如一天)内对该业务对象的库存需求信息，比如，根据存储的某连锁酒店的标准间客房的订单数据，统计在最近一个月内该连锁酒店的标准间客房的预订数量N，从而可以预测出该连锁酒店的标准间客房每天的预订数量约为N/30，从而平台服务器可以在之后每一天的早上7点钟开始提前预订N/30个该连锁酒店的标准间客房。
上述预测过程仅为举例，在实际实施中，还可以根据预订时间段的属性信息(比如是否为节假日，是否在特定城市举办活动等)，首先获取与该预订时间段属性相同的历史时间段内的订单数据，然后基于这些订单数据进行订单需求信息预测。比如，若某预订时间段处于五一假日期间，则可以获取最近3年内五一期间的订单数据，基于这些订单数据预测某请求对象的订单需求信息。
这里，平台服务器基于预测的在预订时间段内对每个业务对象的库存需求，生成第二预订请求。这里针对每个业务对象，平台服务器可以在一次请求中完成在预订时间段内对该业务对象的预订，比如，预测出某连锁酒店的标准间客房每天的预订需求数量为N/30，则平台服务器可以在一次预订请求中向该连锁酒店管理系统请求预订N/30个该连锁酒店的标准间客房，当然，平台服务器也可以通过发起多次预订请求来预订N/30个该连锁酒店的标准间客房，比如每次请求只预订一个房间。
在具体实施中，可以以上述预订时间段的长度为一个周期，平台服务器可以周期性发起第二预订请求来得到第二预订结果，比如，在上述举例中，服务端可以每天早上向系统外发起酒店预订请求，以预订好当天的酒店房间。
S402：平台服务器根据确定的库存需求，向所述业务对象服务器发送第二预订请求，该第二预订请求中携带默认用户信息。
在实际实施中，平台服务器还可以根据客户端实际发起的预订请求，在确定库存的预订信息中有剩余的业务对象未被预订时，向业务对象服务器发起取消预订请求。比如，平台服务器早上7点请求预订了10间某连锁酒店的标准间客房，在晚上6点时发现剩余5间房间没有被预订，此时平台服务器可以发起取消预订这5间房间的请求。
S403：平台服务器接收业务对象服务器返回的携带预订成功的信息的第二预订结果，用于作为初始库存的预订信息。
S404：客户端接收用户提交的预订对象信息。
S405：客户端基于接收的预订对象信息，向平台服务器发送第一预订请求；其中，所述第一预订请求中携带有所述预订对象信息以及客户端用户信息。
S406：平台服务器根据所述第一预订请求中的预订对象信息以及库存的预订信息，判断所述库存的预订信息是否满足所述第一预订请求，若满足进入S407a，若不满足，进入S407b。
S407a：平台服务器在库存的预订信息满足第一预订请求时，基于第一预订请求对应的预订对象信息以及客户端用户信息，生成第一预订结果，更新库存的预订信息，并进入S408及S409。
S408：向业务对象服务器发送预订信息更新请求，用于请求将与第一预订结果关联的用户信息从发送第二预订请求时使用的默认用户信息更新为客户端用户信息。
S407b：平台服务器在库存的预订信息不满足第一预订请求时，向业务对象服务器发送第一预订请求，并接收业务对象服务器反馈的第一预订结果。
这里，平台服务器基于正常的预订流程发起预订。
S409：平台服务器将第一预订结果反馈给客户端。
这里，客户端接收平台服务器基于所述第一预订请求中的预订对象信息和库存的预订信息反馈的第一预订结果。
采用上述实施例，平台服务器可以在用户实际向该平台服务器发起预订请求之前预先向系统外的业务对象服务器发起预订请求，将得到的预订结果作为初始库存的预订信息存储起来。在接收到客户端实际发起的预订请求后，再基于本地库存的预订信息向客户端返回与用户实际的预订请求对应的预订结果。这样，由于不需要平台服务器在接收到客户端请求时再临时向业务对象服务器发起请求，客户端可以及时得到平台服务器返回的预订结果，从而提高了预订效率及预订成功率，进而提升了用户体验。
基于同一发明构思，本发明实施例中还提供了一种与业务对象预订方法对应的业务对象预订系统及装置，由于该系统及装置解决问题的原理与本申请实施例的业务对象预订方法相似，因此该系统及装置的实施可以参见方法的实施，重复之处不再赘述。
实施例三
如图5所示，为本申请实施例三提供的业务对象预订系统500示意图，包括：
平台服务器51，用于接收客户端发送的携带有预订对象信息的第一预订请求；根据该预订对象信息以及库存的预订信息，判断库存的预订信息是否满足所述第一预订请求，其中所述库存的预订信息为平台服务器通过预先发起携带有预订对象信息的第二预订请求得到的；若满足，则生成所述第一预订请求对应的第一预订结果，若不满足，则通过向业务对象服务器发送所述第一预订请求得到第一预订结果；将所述第一预订结果反馈 给客户端；
客户端52，用于接收用户提交的预订对象信息，并基于该预订对象信息向平台服务器发送所述第一预订请求；接收所述平台服务器基于所述第一预订请求中的预订对象信息和所述库存的预订信息反馈的所述第一预订结果；
业务对象服务器53，用于接收所述平台服务器预先发起的所述第二预订请求，并向所述平台服务器反馈第二预订结果，所述第二预订结果中包含有与所述第二预订请求对应的预订成功的信息，用于作为所述平台服务器初始库存的预订信息；还用于接收所述平台服务器发送的由用户发起的所述第一预订请求，并向所述平台服务器反馈所述第一预订结果。
可选地，所述预订对象为酒店，所述业务对象服务器为酒店管理服务器，所述预订对象信息包括预订的酒店名称和房间类型。
可选地，所述平台服务器51具体用于根据以下步骤发起所述第二预订请求：
根据历史预订数据，确定在未来预订时间段内的库存需求；所述历史预订数据包括针对所述预订对象，用户实际发起预订的预订数据，所述库存需求包括各用户针对所述业务对象服务器提供的预订对象的需求总量；
根据确定的所述库存需求，向所述业务对象服务器发送所述第二预订请求。
可选地，所述第一预订请求中还携带有客户端用户信息；所述第二预订请求中还携带有默认用户信息；
在所述库存的预订信息满足所述第一预订请求时，平台服务器51具体用于根据以下步骤生成所述第一预订结果：
基于所述第一预订请求中携带的客户端用户信息，和所述第一预订请求对应的预订对象信息，生成所述第一预订结果；其中，所述第一预订结果中包含有与所述第一预订请求对应的预订成功的信息和所述客户端用户信息；
平台服务器51还用于：
在生成所述第一预订结果之后，向所述业务对象服务器发送预订信息更新请求；所述预订信息更新请求用于请求将与所述第一预订结果关联的用户信息从发送所述第二预订请求时使用的默认用户信息更新为所述客户端用户信息；
业务对象服务器53还用于：
根据所述预订信息更新请求，将存储的与所述第一预订结果关联的用户信息从所述默认用户信息更新为所述客户端用户信息。
可选地，平台服务器51还用于：
在更新库存的预订信息之后，判断所述预订对象的库存量是否低于设定阈值；
若是，则向管理方推送库存告警信息，用于提示管理方选择是否补充库存；或者，自动向所述业务对象服务器发起预订流程。
实施例四
如图6所示，为本申请实施例四提供的平台服务器600结构示意图，包括：
接收模块61，用于接收客户端发送的第一预订请求；所述第一预订请求中携带有预订对象信息；
预订处理模块62，用于根据所述第一预订请求中的预订对象信息以及库存的预订信息，判断所述库存的预订信息是否满足所述第一预订请求；其中所述库存的预订信息中包含预先通过发送模块63向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息；若所述库存的预订信息满足所述第一预订请求，则基于所述第一预订请求对应的预订对象信息，生成第一预订结果；若所述库存的预订信息不满足所述第一预订请求，则控制发送模块63向业务对象服务器发送第一预订请求，并通过接收模块61接收所述业务对象服务器反馈的第一预订结果；
发送模块63，还用于将所述第一预订结果反馈给所述客户端。
可选地，预订处理模块62具体用于根据以下步骤发送所述第二预订请求：
根据历史预订数据，确定在未来预订时间段内的库存需求；所述历史预订数据包括针对所述预订对象，用户实际发起预订的预订数据，所述库存需求包括各用户针对所述业务对象服务器提供的预订对象的需求总量；
根据确定的所述库存需求，向所述业务对象服务器发送所述第二预订请求。
可选地，所述第一预订请求中还携带有客户端用户信息；所述第二预订请求中还携带有默认用户信息；
所述预订处理模块62具体用于根据以下步骤生成所述第一预订结果：
基于所述第一预订请求中携带的客户端用户信息，和所述第一预订请求对应的预订对象信息，生成所述第一预订结果；其中，所述第一预订结果中包含有与所述第一预订请求对应的预订成功的信息和所述客户端用户信息；
所述发送模块63还用于：
向所述业务对象服务器发送预订信息更新请求；所述预订信息更新请求用于请求将与所述第一预订结果关联的用户信息从发送所述第二预订请求时使用的默认用户信息更 新为所述客户端用户信息。
可选地，所述预订处理模块62还用于：
基于所述第一预订请求对应的预订对象信息，生成第一预订结果之后，更新库存的预订信息。
可选地，所述预订处理模块62还用于：
在更新库存的预订信息之后，判断所述预订对象的库存量是否低于设定阈值；若是，则通过所述发送模块63向管理方推送库存告警信息，用于提示管理方选择是否补充库存；或者，自动向所述业务对象服务器发起预订流程。
可选地，所述第一预订请求中还携带有服务方标识信息；
所述平台服务器600还包括：
存储模块64，用于在发送模块63预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，建立得到的预订成功的信息与该业务对象服务器对应的服务方标识信息之间的映射关系，并将该映射关系作为库存的预订信息进行存储；
所述预订处理模块62具体用于根据以下步骤判断所述库存的预订信息是否满足所述第一预订请求：
根据所述第一预订请求中携带的服务方标识信息，从库存的预订信息中查找与该服务方标识信息对应的预订成功的信息；根据所述第一预订请求中的预订对象信息，判断查找到的预订成功的信息是否满足所述第一预订请求。
上述平台服务器，可以在用户实际向该平台服务器发起预订请求之前预先向系统外的业务对象服务器发起预订请求，将得到的预订结果作为初始库存的预订信息存储起来。在接收到客户端实际发起的预订请求后，再基于本地库存的预订信息向客户端返回与用户实际的预订请求对应的预订结果。这样，由于不需要平台服务器在接收到客户端请求时再临时向业务对象服务器发起请求，客户端可以及时得到平台服务器返回的预订结果，从而提高了预订效率及预订成功率，进而提升了用户体验。
实施例五
如图7所示，为本申请实施例五提供的客户端700结构示意图，包括：
第一接收模块71，用于接收用户提交的预订对象信息；
生成模块72，用于基于所述预订对象信息，生成第一预订请求；其中，所述第一预订请求中携带有所述预订对象信息；
发送模块73，用于发送所述第一预订请求；
第二接收模块74，用于接收所述平台服务器基于所述第一预订请求中的预订对象信息和库存的预订信息反馈的第一预订结果；其中所述库存的预订信息中包含有平台服务器预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息；所述第一预订结果中包含有与所述第一预订请求对应的预订成功的信息。
采用上述客户端，可以向用户及时返回平台服务器基于预先存储的预订信息返回的预订结果，提高了预订效率及预订成功率，进而提升了用户体验。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、装置(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神 和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (19)

  1. 一种业务对象预订系统，其特征在于，该系统包括：
    平台服务器，用于接收客户端发送的携带有预订对象信息的第一预订请求；根据该预订对象信息以及库存的预订信息，判断库存的预订信息是否满足所述第一预订请求，其中所述库存的预订信息为平台服务器通过预先发起携带有预订对象信息的第二预订请求得到的；若满足，则生成所述第一预订请求对应的第一预订结果，若不满足，则通过向业务对象服务器发送所述第一预订请求得到第一预订结果；将所述第一预订结果反馈给客户端；
    客户端，用于接收用户提交的预订对象信息，并基于该预订对象信息向平台服务器发送所述第一预订请求；接收所述平台服务器基于所述第一预订请求中的预订对象信息和所述库存的预订信息反馈的所述第一预订结果；
    业务对象服务器，用于接收所述平台服务器预先发起的所述第二预订请求，并向所述平台服务器反馈第二预订结果，所述第二预订结果中包含有与所述第二预订请求对应的预订成功的信息，用于作为所述平台服务器初始库存的预订信息；还用于接收所述平台服务器发送的由用户发起的所述第一预订请求，并向所述平台服务器反馈所述第一预订结果。
  2. 如权利要求1所述的系统，其特征在于，所述预订对象为酒店，所述业务对象服务器为酒店管理服务器，所述预订对象信息包括预订的酒店名称和房间类型。
  3. 如权利要求1所述的系统，其特征在于，所述平台服务器具体用于根据以下步骤发起所述第二预订请求：
    根据历史预订数据，确定在未来预订时间段内的库存需求；所述历史预订数据包括针对所述预订对象，用户实际发起预订的预订数据，所述库存需求包括各用户针对所述业务对象服务器提供的预订对象的需求总量；
    根据确定的所述库存需求，向所述业务对象服务器发送所述第二预订请求。
  4. 如权利要求1所述的系统，其特征在于，所述第一预订请求中还携带有客户端用户信息；所述第二预订请求中还携带有默认用户信息；
    在所述库存的预订信息满足所述第一预订请求时，所述平台服务器具体用于根据以下步骤生成所述第一预订结果：
    基于所述第一预订请求中携带的客户端用户信息，和所述第一预订请求对应的预订对象信息，生成所述第一预订结果；其中，所述第一预订结果中包含有与所述第一预订 请求对应的预订成功的信息和所述客户端用户信息；
    所述平台服务器还用于：
    在生成所述第一预订结果之后，向所述业务对象服务器发送预订信息更新请求；所述预订信息更新请求用于请求将与所述第一预订结果关联的用户信息从发送所述第二预订请求时使用的默认用户信息更新为所述客户端用户信息；
    所述业务对象服务器还用于：
    根据所述预订信息更新请求，将存储的与所述第一预订结果关联的用户信息从所述默认用户信息更新为所述客户端用户信息。
  5. 如权利要求1所述的系统，其特征在于，所述平台服务器还用于：
    在更新库存的预订信息之后，判断所述预订对象的库存量是否低于设定阈值；
    若是，则向管理方推送库存告警信息，用于提示管理方选择是否补充库存；或者，自动向所述业务对象服务器发起预订流程。
  6. 一种业务对象预订方法，其特征在于，该方法包括：
    平台服务器接收客户端发送的第一预订请求；所述第一预订请求中携带有预订对象信息；
    根据所述第一预订请求中的预订对象信息以及库存的预订信息，判断所述库存的预订信息是否满足所述第一预订请求；其中所述库存的预订信息中包含有平台服务器预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息；
    若满足，则基于所述第一预订请求对应的预订对象信息，生成第一预订结果；若不满足，则向所述业务对象服务器发送所述第一预订请求，并接收所述业务对象服务器反馈的第一预订结果；
    将所述第一预订结果反馈给所述客户端。
  7. 如权利要求6所述的方法，其特征在于，所述平台服务器预先向业务对象服务器发起所述第二预订请求，包括：
    所述平台服务器根据历史预订数据，确定在未来预订时间段内的库存需求；所述历史预订数据包括针对所述预订对象，用户实际发起预订的预订数据，所述库存需求包括各用户针对所述业务对象服务器提供的预订对象的需求总量；
    根据确定的所述库存需求，向所述业务对象服务器发送所述第二预订请求。
  8. 如权利要求6所述的方法，其特征在于，所述第一预订请求中还携带有客户端用 户信息；所述第二预订请求中还携带有默认用户信息；
    在所述库存的预订信息满足所述第一预订请求时，所述基于所述第一预订请求对应的预订对象信息，生成所述第一预订结果，包括：
    基于所述第一预订请求中携带的客户端用户信息，和所述第一预订请求对应的预订对象信息，生成所述第一预订结果；其中，所述第一预订结果中包含有与所述第一预订请求对应的预订成功的信息和所述客户端用户信息；
    生成所述第一预订结果之后，还包括：
    向所述业务对象服务器发送预订信息更新请求；所述预订信息更新请求用于请求将与所述第一预订结果关联的用户信息从发送所述第二预订请求时使用的默认用户信息更新为所述客户端用户信息。
  9. 如权利要求6所述的方法，其特征在于，基于所述第一预订请求对应的预订对象信息，生成第一预订结果之后，还包括：
    更新库存的预订信息。
  10. 如权利要求9所述的方法，其特征在于，所述更新库存的预订信息之后，还包括：
    判断所述预订对象的库存量是否低于设定阈值；
    若是，则向管理方推送库存告警信息，用于提示管理方选择是否补充库存；或者，自动向所述业务对象服务器发起预订流程。
  11. 如权利要求6所述的方法，其特征在于，所述第一预订请求中还携带有服务方标识信息；
    所述平台服务器预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，还包括：
    建立得到的预订成功的信息与该业务对象服务器对应的服务方标识信息之间的映射关系，并将该映射关系作为库存的预订信息进行存储；
    所述根据所述第一预订请求中的预订对象信息以及库存的预订信息，判断所述库存的预订信息是否满足所述第一预订请求，包括：
    根据所述第一预订请求中携带的服务方标识信息，从库存的预订信息中查找与该服务方标识信息对应的预订成功的信息；
    根据所述第一预订请求中的预订对象信息，判断查找到的预订成功的信息是否满足所述第一预订请求。
  12. 一种用户请求处理方法，其特征在于，该方法包括：
    客户端接收用户提交的预订对象信息；
    向平台服务器发送第一预订请求；其中，所述第一预订请求中携带有所述预订对象信息；
    接收所述平台服务器基于所述第一预订请求中的预订对象信息和库存的预订信息反馈的第一预订结果；其中所述库存的预订信息中包含有平台服务器预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息；所述第一预订结果中包含有与所述第一预订请求对应的预订成功的信息。
  13. 一种平台服务器，其特征在于，包括：
    接收模块，用于接收客户端发送的第一预订请求；所述第一预订请求中携带有预订对象信息；
    预订处理模块，用于根据所述第一预订请求中的预订对象信息以及库存的预订信息，判断所述库存的预订信息是否满足所述第一预订请求；若满足，则基于所述第一预订请求对应的预订对象信息，生成第一预订结果；若不满足，则控制发送模块向业务对象服务器发送所述第一预订请求，并通过所述接收模块接收业务对象服务器反馈的第一预订结果；
    所述发送模块，还用于将所述第一预订结果反馈给所述客户端；
    其中，所述库存的预订信息中包含预先通过发送模块向所述业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信息。
  14. 如权利要求13所述的平台服务器，其特征在于，所述预订处理模块具体用于根据以下步骤发送所述第二预订请求：
    根据历史预订数据，确定在未来预订时间段内的库存需求；所述历史预订数据包括针对所述预订对象，用户实际发起预订的预订数据，所述库存需求包括各用户针对所述业务对象服务器提供的预订对象的需求总量；根据确定的所述库存需求，向所述业务对象服务器发送所述第二预订请求。
  15. 如权利要求13所述的平台服务器，其特征在于，所述第一预订请求中还携带有客户端用户信息；所述第二预订请求中还携带有默认用户信息；
    所述预订处理模块具体用于根据以下步骤生成所述第一预订结果：
    基于所述第一预订请求中携带的客户端用户信息，和所述第一预订请求对应的预订对象信息，生成所述第一预订结果；其中，所述第一预订结果中包含有与所述第一预订请求对应的预订成功的信息和所述客户端用户信息；
    所述发送模块还用于：
    向所述业务对象服务器发送预订信息更新请求；所述预订信息更新请求用于请求将与所述第一预订结果关联的用户信息从发送所述第二预订请求时使用的默认用户信息更新为所述客户端用户信息。
  16. 如权利要求13所述的平台服务器，其特征在于，所述预订处理模块还用于：
    基于所述第一预订请求对应的预订对象信息，生成第一预订结果之后，更新库存的预订信息。
  17. 如权利要求16所述的平台服务器，其特征在于，所述预订处理模块还用于：
    在更新库存的预订信息之后，判断所述预订对象的库存量是否低于设定阈值；若是，则通过所述发送模块向管理方推送库存告警信息，用于提示管理方选择是否补充库存；或者，自动向所述业务对象服务器发起预订流程。
  18. 如权利要求13所述的平台服务器，其特征在于，所述第一预订请求中还携带有服务方标识信息；
    所述平台服务器还包括：
    存储模块，用于在所述发送模块预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，建立得到的预订成功的信息与该业务对象服务器对应的服务方标识信息之间的映射关系，并将该映射关系作为库存的预订信息进行存储；
    所述预订处理模块具体用于根据以下步骤判断所述库存的预订信息是否满足所述第一预订请求：
    根据所述第一预订请求中携带的服务方标识信息，从库存的预订信息中查找与该服务方标识信息对应的预订成功的信息；根据所述第一预订请求中的预订对象信息，判断查找到的预订成功的信息是否满足所述第一预订请求。
  19. 一种客户端，其特征在于，包括：
    第一接收模块，用于接收用户提交的预订对象信息；
    生成模块，用于基于所述预订对象信息，生成第一预订请求；其中，所述第一预订请求中携带有所述预订对象信息；
    发送模块，用于发送所述第一预订请求；
    第二接收模块，用于接收平台服务器基于所述第一预订请求中的预订对象信息和库存的预订信息反馈的第一预订结果；其中所述库存的预订信息中包含有平台服务器预先向业务对象服务器发起携带有预订对象信息的第二预订请求后，得到的预订成功的信 息；所述第一预订结果中包含有与所述第一预订请求对应的预订成功的信息。
PCT/CN2018/071872 2017-01-20 2018-01-09 一种业务对象预订系统、方法及装置 WO2018133699A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2019539285A JP2020506470A (ja) 2017-01-20 2018-01-09 取引対象予約システム、方法、及び装置
KR1020197020498A KR20190103199A (ko) 2017-01-20 2018-01-09 트랜잭션 객체 예약 시스템, 방법 및 장치
US16/514,888 US20190340710A1 (en) 2017-01-20 2019-07-17 Transaction object reservation system, method, and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710045851.1A CN108334964A (zh) 2017-01-20 2017-01-20 一种业务对象预订系统、方法及装置
CN201710045851.1 2017-01-20

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/514,888 Continuation US20190340710A1 (en) 2017-01-20 2019-07-17 Transaction object reservation system, method, and apparatus

Publications (1)

Publication Number Publication Date
WO2018133699A1 true WO2018133699A1 (zh) 2018-07-26

Family

ID=62907720

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/071872 WO2018133699A1 (zh) 2017-01-20 2018-01-09 一种业务对象预订系统、方法及装置

Country Status (6)

Country Link
US (1) US20190340710A1 (zh)
JP (1) JP2020506470A (zh)
KR (1) KR20190103199A (zh)
CN (1) CN108334964A (zh)
TW (1) TWI751213B (zh)
WO (1) WO2018133699A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108460507A (zh) * 2017-02-22 2018-08-28 阿里巴巴集团控股有限公司 订单处理方法、交易系统及服务器
US11657322B2 (en) * 2018-08-30 2023-05-23 Nec Corporation Method and system for scalable multi-task learning with convex clustering
CN109784648A (zh) * 2018-12-14 2019-05-21 北京三快在线科技有限公司 调度资源分配方法、装置、电子设备及可读存储介质
JP6938717B1 (ja) * 2020-05-11 2021-09-22 Kddi株式会社 管理装置、対象物確保方法及びプログラム
CN112836838B (zh) * 2021-02-10 2022-03-11 北京声智科技有限公司 预约请求处理方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150161636A1 (en) * 2013-12-11 2015-06-11 Skyscanner Limited Method and server for providing a set of price estimates, such as air fare price estimates
CN104751386A (zh) * 2015-04-14 2015-07-01 携程计算机技术（上海）有限公司 酒店的分布式比价方法
CN104809506A (zh) * 2015-03-30 2015-07-29 张泽 房间信息交互方法、装置及系统
CN105512901A (zh) * 2015-12-24 2016-04-20 上海携程商务有限公司 客户服务自动提供系统及方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100334586C (zh) * 2003-03-05 2007-08-29 珠海金山软件股份有限公司 针对团体入住的酒店管理系统
CN1851749A (zh) * 2005-04-22 2006-10-25 马颖 看图购物超市及其经营管理方法
TWM533788U (en) * 2016-08-29 2016-12-11 First Commercial Bank Co Ltd Global fund management system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150161636A1 (en) * 2013-12-11 2015-06-11 Skyscanner Limited Method and server for providing a set of price estimates, such as air fare price estimates
CN104809506A (zh) * 2015-03-30 2015-07-29 张泽 房间信息交互方法、装置及系统
CN104751386A (zh) * 2015-04-14 2015-07-01 携程计算机技术（上海）有限公司 酒店的分布式比价方法
CN105512901A (zh) * 2015-12-24 2016-04-20 上海携程商务有限公司 客户服务自动提供系统及方法

Also Published As

Publication number Publication date
JP2020506470A (ja) 2020-02-27
CN108334964A (zh) 2018-07-27
KR20190103199A (ko) 2019-09-04
TWI751213B (zh) 2022-01-01
TW201828174A (zh) 2018-08-01
US20190340710A1 (en) 2019-11-07

Similar Documents

Publication Publication Date Title
WO2018133699A1 (zh) 一种业务对象预订系统、方法及装置
CN109948017B (zh) 一种信息处理方法及装置
US10922646B1 (en) Multi-echelon inventory planning under dynamic fulfillment policies
US20190392357A1 (en) Request optimization for a network-based service
US20240107338A1 (en) Systems and method for management of computing nodes
EP3369050A1 (en) Rules based driver selection
CN109789553A (zh) 机器人编队调度请求系统
CN109426989B (zh) 一种订购处理方法、提供预约服务方法及设备
WO2018214411A1 (zh) 订单分配方法、装置、电子设备及计算机可读存储介质
CN108205711A (zh) 一种智能约车方法和装置
CN103297528A (zh) 一种获取票务信息的方法和装置
US11226982B2 (en) Synchronization of offline instances
US20190310888A1 (en) Allocating Resources in Response to Estimated Completion Times for Requests
WO2021036319A1 (zh) 数据清洗方法和系统
CN111563125B (zh) 数据存储系统、数据查询方法及装置
US20220284404A1 (en) Systems and Methods for Task Assistance
TW200541259A (en) Data distribution device and method for changing data distribution time
KR20160043315A (ko) 물품배송처리방법 및 물품배송처리서버
US20170352009A1 (en) Method for assigning time windows for Vehicle Routing problem
US11164157B2 (en) Internet of things based scheduler
WO2016077225A1 (en) Managing warehouse information
US20180189791A1 (en) Methods and system for addressing locations with personalized and user-selected tags
CN104735134B (zh) 一种用于提供计算服务的方法和装置
US10798208B2 (en) Availability data caching in meeting systems
JP2021501945A (ja) ネットワーク配達サービスを実行するコンピュータシステム

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: 18742271

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20197020498

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019539285

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18742271

Country of ref document: EP

Kind code of ref document: A1