CN112836838B

CN112836838B - Reservation request processing method, device, equipment and storage medium

Info

Publication number: CN112836838B
Application number: CN202110185279.5A
Authority: CN
Inventors: 陈孝良; 苏少炜; 李科研; 常乐
Original assignee: Beijing SoundAI Technology Co Ltd
Current assignee: Beijing SoundAI Technology Co Ltd
Priority date: 2021-02-10
Filing date: 2021-02-10
Publication date: 2022-03-11
Anticipated expiration: 2041-02-10
Also published as: CN112836838A

Abstract

The application discloses a method, a device, equipment and a storage medium for processing an appointment request, and belongs to the field of medical treatment. In the embodiment of the application, on one hand, in a manner that the plurality of first servers process the reservation requests in parallel, the plurality of first servers can distribute the reservation requests of the user account to be processed instead of being processed by one server, so that the load of the server can be reduced, and the processing efficiency of the reservation requests can be improved. On the other hand, after receiving the reservation request, the server firstly sends a reservation success notification to the user account when determining that the server has an available reservation identifier, and then processes the reservation request, so that the server can quickly feed back required information to the user, avoid long-time waiting of the user, optimize the processing flow of the reservation request, and improve the feedback effect of the reservation request.

Description

Reservation request processing method, device, equipment and storage medium

Technical Field

The present application relates to the medical field, and in particular, to a method, an apparatus, a device, and a storage medium for processing an appointment request.

Background

With the development of computer technology, computing power of electronic devices and interaction power between terminals and servers are used in various fields to transfer offline work to online, so as to provide convenience for users. In the medical field, if a user needs a certain health service, the user usually needs to make an appointment, and the appointment is successful and then goes to the relevant institution at the appointed time to obtain the health service.

Currently, the reservation request processing method is generally as follows: the server is used for processing the reservation request, the server receives the reservation request of the user account, can process the reservation request, and feeds back a reservation success notice to the user account after generating reservation information. If a plurality of user accounts send reservation requests, the server can process the reservation requests in sequence and feed back processing results to the user accounts after the processing is finished. Especially, when a large-scale public health event occurs, the server receives a large number of reservation requests, overload may occur, and the server may be crashed, and the reservation request processing mode is inefficient, and a user may need to wait for a long time.

Disclosure of Invention

The embodiment of the application provides a reservation request processing method, a reservation request processing device, reservation request processing equipment and a storage medium, provides a more convenient searching and displaying mode, and improves searching and displaying efficiency. The technical scheme is as follows:

in one aspect, a reservation request processing method is applied to any one of a plurality of first servers, each of which is used for processing a reservation request, and the method includes:

receiving a first reservation request of a first user account, wherein the first reservation request is used for reserving a health service for the first user account;

responding to an idle reservation identifier existing in a current first server, and sending a reservation success notification to the first user account, wherein the idle reservation identifier is an un-reserved reservation identifier;

and processing the first reservation request.

In some embodiments, the first reservation request is sent by the second server when the first user account is not reserved and outdated as determined by historical reservation records.

In some embodiments, the method further comprises:

based on a result of processing the first reservation request, a reservation record update request is transmitted to a second server, and a history reservation record is updated by the second server in response to the reservation record update request.

In some embodiments, the first reservation request is sent by the second server upon determining allocation to the first server based on at least one of load information or processing time period of the plurality of first servers.

In some embodiments, the sending a reservation success notification to the first user account in response to the presence of a free reservation identity in the current first server includes:

acquiring reservation information of a reservation identifier in a current first server;

and sending a reservation success notification to the first user account in response to the reservation information indicating that the idle reservation identifier exists in the current first server.

In some embodiments, the method further comprises:

responding to the reservation information indicating that no idle reservation identification exists in the current first server, and sending a re-reservation prompt to the first user account, wherein the re-reservation prompt is used for prompting the first user account to resend a reservation request; alternatively, the first and second electrodes may be,

and sending an allocation request to a second server in response to the reservation information indicating that no idle reservation identifier exists in the current first server, wherein the allocation request is used for requesting the second server to allocate the first reservation request of the first user account to other first servers.

In some embodiments, before the receiving the first subscription request of the first user account, the method further includes:

receiving a second reservation request of a second user account;

the processing the first reservation request includes:

and processing the first reservation request and the second reservation request according to the receiving sequence of the first reservation request and the second reservation request.

In some embodiments, the processing the first reservation request and the second reservation request in the order of receipt of the first reservation request and the second reservation request includes:

writing the first reservation request into a queue, wherein the queue comprises the second reservation request;

and processing the first reservation request and the second reservation request in the queue according to the writing sequence of the reservation requests in the queue.

In some embodiments, after the writing the first reservation request into the queue, the method further comprises:

determining a reservation time period of the first reservation request according to the position of the first reservation request in the queue;

sending the reserved time period to the first user account;

the processing the first reservation request and the second reservation request in the queue according to the writing sequence of the reservation requests in the queue includes:

and generating reservation information for a user account corresponding to the reservation request based on the reservation request for the reservation request positioned at the head of the queue.

In some embodiments, the method further comprises:

receiving a reservation canceling request of any user account, wherein the reservation canceling request carries identification information of the user account;

determining a target reservation request from the queue based on the identification information of the user account, wherein the target reservation request carries the identification information of the user account;

and deleting the target reservation request from the queue.

In some embodiments, after receiving a request for canceling a subscription of any user account, the method further includes:

writing the request for canceling reservation into the queue;

and in response to the reservation canceling request being positioned at the head of the queue, deleting the reservation information of the user account from the generated reservation information based on the reservation canceling request.

In one aspect, a reservation request processing method is provided, and is applied to a second server, and the method includes:

receiving reservation requests of a plurality of user accounts, wherein each reservation request is used for reserving health services for the user accounts;

acquiring a historical reservation record;

for each reservation request of the user account, responding to the historical reservation record indicating that the user account is not reserved, and distributing the reservation request to one of a plurality of first servers for processing the reservation request.

In some embodiments, said distributing said reservation request to one of a plurality of first servers for processing reservation requests comprises:

determining a target first server from a plurality of first servers based on at least one of load information or processing time period of the first servers, wherein each first server is used for processing a reservation request;

distributing the reservation request to the target first server.

In some embodiments, the determining a target first server from the plurality of first servers based on at least one of load information or processing time period of the plurality of first servers includes:

determining at least one candidate first server from the plurality of first servers based on the processing time periods of the plurality of first servers and the reservation time period carried in the reservation request;

determining a target first server from the at least one candidate first server based on the load information of the at least one candidate first server.

In some embodiments, the method further comprises:

determining the reserved quantity of the reservation identification according to the historical reservation record;

and in response to the reserved quantity reaching a quantity threshold value, returning a reservation failure notice to the user account in response to the received reservation request of the user account, wherein the reservation failure notice is used for informing that the user account does not have a reserved identifier which can be reserved.

In some embodiments, the method further comprises:

receiving a reservation recording updating request sent by a first server;

and updating the historical reservation record according to the reservation record updating request.

In one aspect, there is provided a reservation request processing apparatus, the apparatus including:

the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a first reservation request of a first user account, and the first reservation request is used for reserving health services for the first user account;

a sending module, configured to send a reservation success notification to the first user account in response to a free reservation identifier existing in a current first server, where the free reservation identifier is an un-reserved reservation identifier, the current first server is any one of a plurality of first servers, and each first server is configured to process a reservation request;

and the processing module is used for processing the first reservation request.

In some embodiments, the sending module is further configured to send a reservation record update request to a second server based on a result of processing the first reservation request, the second server updating the historical reservation record in response to the reservation record update request.

In some embodiments, the sending module is to:

In some embodiments, the sending module is further configured to:

In some embodiments, the receiving module is further configured to receive a second subscription request of a second user account;

the processing module is used for processing the first reservation request and the second reservation request according to the receiving sequence of the first reservation request and the second reservation request.

In some embodiments, the processing module is to:

In some embodiments, the apparatus further comprises:

the first determining module is used for determining the reservation time period of the first reservation request according to the position of the first reservation request in the queue;

the sending module is further configured to send the reserved time period to the first user account;

the processing module is used for generating reservation information for a user account corresponding to the reservation request based on the reservation request for the reservation request positioned at the head of the queue.

In some embodiments, the receiving module is further configured to receive a reservation cancellation request of any user account, where the reservation cancellation request carries identification information of the user account;

the device further comprises:

a second determining module, configured to determine, based on the identification information of the user account, a target reservation request from the queue, where the target reservation request carries the identification information of the user account;

and the first deleting module is used for deleting the target reservation request from the queue.

In some embodiments, the processing module is further configured to write the request to cancel reservation into the queue;

and the second deleting module is used for responding to the reservation canceling request positioned at the head of the queue, and deleting the reservation information of the user account from the generated reservation information based on the reservation canceling request.

the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving reservation requests of a plurality of user accounts, and each reservation request is used for reserving health services for the user account;

the acquisition module is used for acquiring a historical reservation record;

the distribution module is used for responding to the historical reservation record indicating that the user account is not reserved for the reservation request of each user account, and distributing the reservation request to one of a plurality of first servers for processing the reservation request.

In some embodiments, the assignment module includes a determination unit and an assignment unit;

the determining unit is configured to determine a target first server from a plurality of first servers based on at least one of load information or processing time periods of the plurality of first servers, each of the first servers being configured to process a reservation request;

the distribution unit is used for distributing the reservation request to the target first server.

In some embodiments, the determining unit is to:

In some embodiments, the apparatus further comprises:

the determining module is used for determining the reserved quantity of the reservation identification according to the historical reservation record;

and the sending module is used for responding to the reserved quantity reaching a quantity threshold value, responding to the received reservation request of the user account, and returning a reservation failure notice to the user account, wherein the reservation failure notice is used for informing that the user account does not have a reserved identifier which can be reserved.

In some embodiments, the receiving module is further configured to receive a reservation record update request sent by the first server;

the device further comprises:

and the updating module is used for updating the historical reservation record according to the reservation record updating request.

In one aspect, a computer device is provided that includes one or more processors and one or more memories having at least one instruction stored therein, the instruction being loaded and executed by the one or more processors to implement the operations performed by the reservation request processing method.

In one aspect, a computer-readable storage medium is provided, in which at least one instruction is stored, and the instruction is loaded and executed by a processor to implement the operation performed by the reservation request processing method.

In one aspect, a computer program product is provided, which includes at least one program code loaded and executed by a processor to implement the operations performed by the reservation request processing method.

In the embodiment of the application, on one hand, in a manner that the plurality of first servers process the reservation requests in parallel, the plurality of first servers can distribute the reservation requests of the user account to be processed instead of being processed by one server, so that the load of the server can be reduced, and the processing efficiency of the reservation requests can be improved. On the other hand, after receiving the reservation request, the server firstly sends a reservation success notification to the user account when determining that the server has an available reservation identifier, and then processes the reservation request, so that the server can quickly feed back required information to the user, avoid long-time waiting of the user, optimize the processing flow of the reservation request, and improve the feedback effect of the reservation request.

Drawings

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

Fig. 1 is an implementation environment of a reservation request processing method according to an embodiment of the present application;

fig. 2 is a flowchart of a reservation request processing method according to an embodiment of the present application;

fig. 3 is a flowchart of a reservation request processing method according to an embodiment of the present application;

fig. 4 is a flowchart of a reservation request processing method according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a reservation request processing apparatus according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a reservation request processing apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a server provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

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

Fig. 1 is an implementation environment of a reservation request processing method provided in an embodiment of the present application, and referring to fig. 1, the implementation environment includes: a plurality of terminals 101, a second server 102, and a plurality of first servers 103; the plurality of terminals 101 are connected to the second server 102 through a wireless network or a wired network, and the second server 102 is connected to the first server 103 through a wireless network or a wired network.

The terminal 101 may be at least one of a smart phone, a game console, a desktop computer, a tablet computer, an e-book reader, an MP3(Moving Picture Experts Group Audio Layer III, motion Picture Experts compression standard Audio Layer 3) player, an MP4(Moving Picture Experts Group Audio Layer IV, motion Picture Experts compression standard Audio Layer 4) player, and a laptop computer. The terminal 101 is installed and operated with an application program, which can be operated through a browser or through a separate client.

Each first server 103 may run a business system to implement the same or different business services. For example, the terminal 101 can transmit a reservation request to the second server 102, assign the reservation request to one of the plurality of first servers 103 by the second server 102, and process the assigned reservation request by the first server 103.

Those skilled in the art will appreciate that the number of the above-mentioned terminals 101, the second servers 102, and the first servers 103 may be more or less. For example, the number of the terminal 101, the server 103, and the database 1023 is dozens or hundreds, or more, in which case the implementation environment further includes other terminals, other servers, or other databases. The number of the terminals and the servers and the type of the equipment are not limited in the embodiment of the application.

Fig. 2 is a flowchart of a reservation request processing method provided in an embodiment of the present application, and referring to fig. 2, the method is applied to any one of a plurality of first servers, each of the first servers is used for processing a reservation request, and the method includes:

201. the first server receives a first reservation request of a first user account, wherein the first reservation request is used for reserving health services for the first user account.

202. And the first server responds to the triggering operation of the reservation control to acquire the historical reservation information of the currently logged first user account.

203. The first server processes the first reservation request.

In some embodiments, the method further comprises:

and sending a reservation success notice to the first user account in response to the reservation information indicating that the current first server has a free reservation identifier.

In some embodiments, the method further comprises:

In some embodiments, before the receiving the first subscription request of the first user account, the method further comprises:

receiving a second reservation request of a second user account;

the processing the first reservation request includes:

In some embodiments, the processing the first reservation request and the second reservation request in the order in which the first reservation request and the second reservation request are received includes:

In some embodiments, after the writing the first reservation request to the queue, the method further comprises:

sending the reserved time period to the first user account;

the processing the first reservation request and the second reservation request in the queue according to the writing sequence of the reservation requests in the queue comprises the following steps:

In some embodiments, the method further comprises:

the target reservation request is deleted from the queue.

writing the request for canceling reservation into the queue;

and in response to the reservation cancellation request being positioned at the head of the queue, deleting the reservation information of the user account from the generated reservation information based on the reservation cancellation request.

Fig. 3 is a flowchart of a reservation request processing method provided in an embodiment of the present application, and referring to fig. 3, the method is applied to a second server, and includes:

301. the second server receives reservation requests of a plurality of user accounts, and each reservation request is used for reserving health services for the user account.

302. The second server obtains a historical reservation record.

303. For each reservation request of the user account, the second server distributes the reservation request to one of the first servers for processing the reservation request in response to the historical reservation record indicating that the user account has not reserved.

In the embodiment of the application, on one hand, in a manner that the plurality of first servers process the reservation requests in parallel, the plurality of first servers can distribute the reservation requests of the user account to be processed instead of being processed by one server, so that the load of the server can be reduced, and the processing efficiency of the reservation requests can be improved.

In some embodiments, the distributing the reservation request to one of a plurality of first servers for processing reservation requests comprises:

the reservation request is distributed to the target first server.

In some embodiments, the determining the target first server from the plurality of first servers based on at least one of load information or processing time period of the plurality of first servers comprises:

In some embodiments, the method further comprises:

determining the reserved quantity of the reservation identifier according to the historical reservation record;

In some embodiments, the method further comprises:

receiving a reservation recording updating request sent by a first server;

the historical reservation record is updated according to the reservation record update request.

The following describes a processing flow of the reservation request in an interactive manner among the terminal where the user account is located, the first server, and the second server. Fig. 4 is a flowchart of a method for processing a reservation request according to an embodiment of the present application, and referring to fig. 4, the method may include the following steps.

401. And the terminal where the second user account is located sends a second reservation request of the second user account to the second server.

The second subscription request is used for subscribing the health service for the second user account. The user can log in the user account on the terminal and perform reservation operation so as to trigger the terminal to send a second reservation request to the second server.

The second server is used for distributing the reservation requests and distributing the reservation requests of the user accounts to different first servers in the first servers, and the first servers can process the reservation requests in parallel, so that the processing efficiency is improved, and the load of the servers is reduced.

For the health service, the health service may be provided by a medical institution, and the user may reserve the health service through the electronic device, and then the health service may be provided to the user by the medical institution at a reserved time. For example, the health service may be nucleic acid testing, and the user may make an appointment in advance, and then may go to an appointment hospital for nucleic acid testing by medical staff for the user. For another example, the health service may be blood tests, and the user may make an appointment in advance and then go to a hospital for blood drawing tests by medical staff. For another example, the health service may be a medical service, and the user may make a medical appointment in advance, and then may go to an appointment hospital to make a medical diagnosis for the user by the appointment doctor. Of course, the health service may also be other health services, which are not listed here, and the embodiment of the present application does not limit this.

In some embodiments, the second subscription request may carry identification information of a second user account. The second user account can be uniquely identified through the identification information, and the corresponding relation between the second reservation request and the second user account is determined. For example, the identification information may be an account ID or an identity card number of the user, which is not limited in this embodiment of the application.

The second reservation request may further include other information, for example, personal information of the user, a reservation time period, a reserved health service, a reservation type, a reservation mode, or the like, which is not limited in this embodiment of the application.

402. And the second server receives a second reservation request of the second user account.

403. The second server obtains a historical reservation record.

For the historical reservation record, the historical reservation record may include the reservation condition of the historical user account, and it is at least known whether a certain user account has been reserved through the historical reservation record. For example, the historical reservation record includes identification information of a user account with a successful reservation, and the historical reservation record may further include identification information of a user account with a failed reservation, or the historical reservation record may further include reservation information of a user account with a successful reservation, and the like, and the reservation information may include a reservation time period of the user account, a reserved health service, and the like, which is not limited in this embodiment of the application.

The storage address of the historical reservation record may include a plurality of conditions, and accordingly, the second server may obtain the historical reservation record in a plurality of ways.

In some embodiments, the historical reservation record may be stored locally at the second server, for example, in an in-memory database of the second server. Accordingly, the electronic device may retrieve the historical reservation records from a local (or in-memory database).

In other embodiments, the historical reservation records may be stored in a database of another server, and accordingly, the electronic device may send a reservation record obtaining request to the other server and receive the historical reservation records sent by the other server.

404. The second server distributes the second reservation request to one of the plurality of first servers for processing the reservation request in response to the historical reservation record indicating that the second user account is not reserved.

After the second server acquires the historical reservation record, whether the second user account has reserved or not can be judged according to the historical reservation record, and if the second user account has not reserved, the second user account can be distributed to the first server for processing.

In some embodiments, the second server may allocate according to a certain allocation policy when allocating the reservation request. For example, load information of a plurality of first servers may be considered and preferentially allocated to a first server having a light load. For another example, different first servers may be responsible for different processing time periods, and the processing time periods of the plurality of first servers may be considered and allocated to the first servers of the corresponding processing time periods according to the reservation time period of the reservation request. For another example, the load information and the processing time period may be considered together and allocated to the first server whose processing time period coincides with the processing time period and whose load is light.

Specifically, the second server may determine a target first server from the plurality of first servers based on at least one of load information or processing time periods of the plurality of first servers, each of the first servers being configured to process a reservation request, and allocate the reservation request to the target first server.

The second server may determine at least one candidate first server from the plurality of first servers based on the processing time periods of the plurality of first servers and the reservation time period carried in the reservation request, and determine the target first server from the at least one candidate first server based on the load information of the at least one candidate first server. Therefore, the second server screens all the first servers with the processing time period matched according to the processing time period, then the load information of the first servers is considered, and the first server with the lightest load is selected as the target server.

In some embodiments, the second server may determine the reserved quantity of the reservation identifier according to the historical reservation record, and in response to the reserved quantity reaching a quantity threshold, return a reservation failure notification to the user account in response to the received reservation request of the user account, the reservation failure notification being used for informing the user account that no reservation identifier capable of being reserved exists. For example, 1000000 reservation numbers are shared, and a reservation request is processed by 200 servers, each server being responsible for 5000 reservation numbers. When the reserved number reaches 1000000, the second server may not allocate the reservation request any more, but directly return a reservation failure notification, informing that there is no reservation number.

405. The first server receives a second reservation request of the second user account.

The second reservation request is sent by the second server when the second user account is not reserved and outdated according to the historical reservation record. The non-reserved means that the second user account does not perform a reservation action or the second user account performs a reservation action but fails to make a reservation.

406. And the first server responds to the existence of an idle reservation identifier in the current first server, and sends a reservation success notification to the terminal where the second user account is located, wherein the idle reservation identifier is an un-reserved reservation identifier.

After receiving the second reservation request, the first server may determine whether there is an available reservation identifier, and if so, may associate the reservation identifier with the second user account, and then send a reservation success notification to the second user account.

In some embodiments, the subscription identifier may be continuously managed by subscription information of the subscription identifier, and the first server may be able to know a subscription condition of the subscription identifier through the subscription information of the subscription identifier. For example, the subscription information may include the total number of subscription identifications in the first server and the number of subscribed identifications, and may further include the number of unsubscribed subscription identifications. Specifically, the first server may obtain subscription information of a subscription identifier in the current first server, and send a subscription success notification to the second user account in response to the subscription information indicating that a free subscription identifier exists in the current first server.

In a specific possible embodiment, the subscription identifier may be a subscription number, and the free subscription identifier may be referred to as a number source. Each first server in the plurality of first servers can have a certain number of number sources, the first servers can judge whether the first servers have the number sources after receiving the reservation request, and if the first servers have the number sources, reservation can be performed on the second user account, so that a reservation success notification can be fed back to the first servers to inform the user that reservation is performed, and the following specific reservation information and the like of the user can be determined by the first servers.

If the user does not have a number source, feedback can be given to the user, so that the user can resubmit a reservation request, or directly request the second server to reallocate other first servers for the second user account. Specifically, the first server may send a re-subscription prompt to the first user account in response to the subscription information indicating that no idle subscription identifier exists in the current first server, where the re-subscription prompt is used to prompt the first user account to resend the subscription request; alternatively, the first server may send, in response to the reservation information indicating that no free reservation identifier exists in the current first server, an allocation request to the second server, where the allocation request is used to request the second server to allocate the first reservation request of the first user account to the other first servers.

When the idle reservation identifier does not exist, the user is fed back in time, or other first servers are redistributed, so that the user can obtain real-time feedback to know the processing condition of the reservation request, or the processing flow of the reservation request can be perfected in a redistribution mode, the reservation request processing is provided for the user as far as possible, and the user can obtain the processing result most quickly.

407. The first server writes the second reservation request into the queue.

Here, the reservation request is managed by a queue, and the first server may not be queued, for example, may be placed in a reservation request pool.

408. And the terminal where the first user account is located sends a first reservation request of the first user account to the second server.

409. The second server receives a first reservation request of the first user account.

The first subscription request is used for subscribing to health services for a first user account. Steps 408 to 409 are similar to steps 401 to 402, and are not described herein again.

410. The second server obtains a historical reservation record.

411. The second server distributes the first reservation request to one of the plurality of first servers for processing reservation requests in response to the historical reservation record indicating that the first user account is not reserved.

412. The first server receives a first reservation request of a first user account.

The first reservation request is sent by the second server when determining to be allocated to the first server according to at least one of load information or processing time periods of the plurality of first servers. The first reservation request is sent by the second server when the first user account is not reserved and outdated according to the historical reservation record. The non-reserved means that the first user account does not perform a reservation action or the first user account performs a reservation action but fails to make a reservation.

413. And the first server responds to the idle reservation identification existing in the current first server, and sends a reservation success notification to the terminal where the first user account is located.

Similarly to step 406, the first server may obtain the subscription information of the subscription identifier in the current first server, and send a subscription success notification to the first user account in response to the subscription information indicating that a free subscription identifier exists in the current first server.

414. The first server writes the first reservation request into a queue.

The steps 410 to 414 are similar to the steps 403 to 407, and are not described herein again. Thus, the queue may include a first reservation request and a second reservation request, which are only described as two reservation requests, and may also include reservation requests that have been written before and have not been processed yet.

Similarly, the first server determines the reservation time period of the first reservation request according to the position of the first reservation request in the queue, and sends the reservation time period to the first user account. In the subsequent step 415, the first server may generate reservation information for the reservation request at the head of the queue, based on the reservation request, for the user account corresponding to the reservation request.

415. And the first server processes the first reservation request and the second reservation request in the queue according to the writing sequence of the reservation requests in the queue.

The queue is a first-in first-out queue, and reservation requests written into the queue first are processed first. And if a certain reservation request is at the head of the queue, the first server can read the reservation request, process the reservation request and delete the reservation request from the queue after the processing is finished. Thus, the next reservation request of the reservation request is located at the head of the queue, and the first server can process the next reservation request again.

In the embodiment of the application, the second reservation request is written first, and when the second reservation request is not processed yet, the first server writes the first reservation request again. When the second reservation request is located at the head of the queue, the second reservation request can be processed, and after the processing is finished, the second reservation request can be deleted from the queue, so that the first reservation request is located at the head of the queue, and the first server can process the first reservation request again.

Step 415 is a process of processing the first reservation request and the second reservation request according to a receiving sequence of the first reservation request and the second reservation request, and the writing sequence is the same as the receiving sequence.

In some embodiments, after the first server generates the reservation information, the reservation information may be written into a database, where the database may be an internal memory database in the second server or a database in another server, and the embodiment of the present application is not limited thereto.

In some embodiments, the first server may further send a reservation record update request to the second server based on a result of processing the second reservation request, the second server updating the historical reservation record in response to the reservation record update request. Thus, the second user account reserved is recorded in the history reservation record. The second server may receive the reservation record update request sent by the first server, and update the historical reservation record according to the reservation record update request.

In some embodiments, the first server may further send a reservation record update request to the second server based on a result of processing the first reservation request, the second server updating the historical reservation record in response to the reservation record update request. Thus, the history reservation record records that the first user account is reserved.

In some embodiments, after sending the reservation request, the user may want to cancel the reservation, and then may send a reservation cancellation request to the second server, where the reservation cancellation request carries identification information of the user account. The second server may determine a first server for processing a reservation request of the user account according to the identification information of the user account, and then send a reservation cancellation request to the first server.

After receiving the request for canceling the reservation, the first server may process the request in various ways. Referring specifically to the following two ways, the embodiments of the present application may adopt either way.

In the first manner, the first server may receive a reservation cancellation request of any user account, determine a target reservation request from the queue based on the identification information of the user account, where the target reservation request carries the identification information of the user account, and delete the target reservation request from the queue. The reservation canceling request and the target reservation request are offset through the identification information of the user account, so that the first server does not need to process the two requests, the calculated amount is reduced, and the processing efficiency of other reservation requests is improved.

In the foregoing, for the case that the target reservation request is not processed, there is a possibility that the target reservation request of the user account is processed, and the first server directly processes the reservation cancellation request and deletes the reservation information of the user account.

In the second mode, the first server writes the reservation cancellation request into the queue; and in response to the reservation cancellation request being positioned at the head of the queue, deleting the reservation information of the user account from the generated reservation information based on the reservation cancellation request. The first server does not need to inquire the reservation request, places the reservation cancellation request into the queue, and deletes reserved information until the reservation cancellation request is processed at the head of the queue.

Of course, the reservation cancellation process may be implemented in other manners, for example, the second server may maintain a queue, where the queue includes all reservation processing requests in the queue of the first server, and the processing progress of the reservation requests may be synchronized between the first server and the second server in real time. After receiving the reservation cancellation request, the second server may determine the target reservation request from its own queue, and then delete the target reservation request from the queue, and then the second server may send a deletion notification to the corresponding first server, and the first server may delete the target reservation request in its own queue.

All the above optional technical solutions may be combined arbitrarily to form optional embodiments of the present application, and are not described herein again.

Fig. 5 is a schematic structural diagram of a reservation request processing apparatus according to an embodiment of the present application, and referring to fig. 5, the apparatus includes:

a receiving module 501, configured to receive a first reservation request of a first user account, where the first reservation request is used to reserve a health service for the first user account;

a sending module 502, configured to send a reservation success notification to the first user account in response to an idle reservation identifier existing in a current first server, where the idle reservation identifier is an un-reserved reservation identifier, and the current first server is any one of a plurality of first servers, and each first server is configured to process a reservation request;

a processing module 503, configured to process the first reservation request.

In some embodiments, the sending module 502 is further configured to send a reservation record update request to a second server based on a result of processing the first reservation request, the second server updating the historical reservation record in response to the reservation record update request.

In some embodiments, the sending module 502 is configured to:

In some embodiments, the sending module 502 is further configured to:

In some embodiments, the receiving module 501 is further configured to receive a second reservation request of a second user account;

the processing module 503 is configured to process the first reservation request and the second reservation request according to a receiving order of the first reservation request and the second reservation request.

In some embodiments, the processing module 503 is configured to:

In some embodiments, the apparatus further comprises:

the sending module 502 is further configured to send the reserved time period to the first user account;

the processing module 503 is configured to, for a reservation request at the head of the queue, generate reservation information for a user account corresponding to the reservation request based on the reservation request.

In some embodiments, the receiving module 501 is further configured to receive a reservation cancellation request of any user account, where the reservation cancellation request carries identification information of the user account;

the device also includes:

In some embodiments, the processing module 503 is further configured to write the cancel reservation request into the queue;

It should be noted that: the reservation request processing apparatus provided in the above embodiment is only illustrated by dividing the functional modules when processing the reservation request, and in practical applications, the above function allocation may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. In addition, the reservation request processing apparatus and the reservation request processing method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.

Fig. 6 is a schematic structural diagram of a reservation request processing apparatus according to an embodiment of the present application, and referring to fig. 6, the apparatus includes:

a receiving module 601, configured to receive reservation requests of multiple user accounts, where each reservation request is used to reserve a health service for a user account;

an obtaining module 602, configured to obtain a historical reservation record;

the allocating module 603 is configured to, for a reservation request of each user account, allocate the reservation request to one of the first servers for processing the reservation request in response to the historical reservation record indicating that the user account has not reserved.

In some embodiments, the assignment module 603 includes a determination unit and an assignment unit;

the determining unit is configured to determine a target first server from the plurality of first servers based on at least one of load information or processing time periods of the plurality of first servers, each of the first servers being configured to process the reservation request;

In some embodiments, the determining unit is to:

In some embodiments, the apparatus further comprises:

In some embodiments, the receiving module 601 is further configured to receive a reservation recording update request sent by the first server;

the device also includes:

According to the embodiment of the application, by means of parallel processing of the reservation requests by the plurality of first servers, the reservation requests of the user accounts can be processed in a shunting manner instead of being processed by one server, so that the load of the server can be reduced, and the processing efficiency of the reservation requests can be improved.

It should be noted that: the reservation request processing apparatus provided in the above embodiment is only illustrated by dividing the functional modules when processing the reservation request, and in practical applications, the above function allocation may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above described functions. In addition, the reservation request processing apparatus and the reservation request processing method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.

Fig. 7 is a schematic structural diagram of an electronic device 700 according to an embodiment of the present disclosure, where the electronic device 700 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 701 and one or more memories 702, where the one or more memories 702 store at least one instruction, and the at least one instruction is loaded and executed by the one or more processors 701 to implement the reservation request Processing method provided by each of the method embodiments. Of course, the electronic device 700 may further have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input and output, and the electronic device 700 may further include other components for implementing device functions, which are not described herein again.

The electronic device may be a terminal. Fig. 8 is a schematic structural diagram of a terminal according to an embodiment of the present application. The terminal 800 may be: a smart phone, a tablet computer, an MP3(Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3) player, an MP4(Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4) player, a notebook computer or a desktop computer. The terminal 800 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, etc.

In general, the terminal 800 includes: one or more processors 801 and one or more memories 802.

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

Memory 802 may include one or more computer-readable storage media, which may be non-transitory. Memory 802 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 802 is used to store at least one instruction for execution by processor 801 to implement the reservation request processing methods provided by method embodiments herein.

In some embodiments, the terminal 800 may further include: a peripheral interface 803 and at least one peripheral. The processor 801, memory 802 and peripheral interface 803 may be connected by bus or signal lines. Various peripheral devices may be connected to peripheral interface 803 by a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 804, a display screen 805, a camera assembly 806, an audio circuit 807, a positioning assembly 808, and a power supply 809.

The peripheral interface 803 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 801 and the memory 802. In some embodiments, the processor 801, memory 802, and peripheral interface 803 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 801, the memory 802, and the peripheral interface 803 may be implemented on separate chips or circuit boards, which are not limited by this embodiment.

The Radio Frequency circuit 804 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 804 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 804 converts an electrical signal into an electromagnetic signal to be transmitted, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 804 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 8G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 804 may further include NFC (Near Field Communication) related circuits, which are not limited in this application.

The display screen 805 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display 805 is a touch display, the display 805 also has the ability to capture touch signals on or above the surface of the display 805. The touch signal may be input to the processor 801 as a control signal for processing. At this point, the display 805 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 805 may be one, providing the front panel of the terminal 800; in other embodiments, the display 805 may be at least two, respectively disposed on different surfaces of the terminal 800 or in a folded design; in still other embodiments, the display 805 may be a flexible display disposed on a curved surface or a folded surface of the terminal 800. Even further, the display 805 may be arranged in a non-rectangular irregular pattern, i.e., a shaped screen. The Display 805 can be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), and other materials.

The camera assembly 806 is used to capture images or video. Optionally, camera assembly 806 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 806 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.

The audio circuit 807 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 801 for processing or inputting the electric signals to the radio frequency circuit 804 to realize voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones may be provided at different portions of the terminal 800. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 801 or the radio frequency circuit 804 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 807 may also include a headphone jack.

The positioning component 808 is used to locate the current geographic position of the terminal 800 for navigation or LBS (Location Based Service). The Positioning component 808 may be a Positioning component based on the GPS (Global Positioning System) in the united states, the beidou System in china, the graves System in russia, or the galileo System in the european union.

Power supply 809 is used to provide power to various components in terminal 800. The power supply 809 can be ac, dc, disposable or rechargeable. When the power source 809 comprises a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, terminal 800 also includes one or more sensors 810. The one or more sensors 810 include, but are not limited to: acceleration sensor 811, gyro sensor 812, pressure sensor 813, fingerprint sensor 814, optical sensor 815 and proximity sensor 816.

The acceleration sensor 811 may detect the magnitude of acceleration in three coordinate axes of the coordinate system established with the terminal 800. For example, the acceleration sensor 811 may be used to detect the components of the gravitational acceleration in three coordinate axes. The processor 801 may control the display 805 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 811. The acceleration sensor 811 may also be used for acquisition of motion data of a game or a user.

The gyro sensor 812 may detect a body direction and a rotation angle of the terminal 800, and the gyro sensor 812 may cooperate with the acceleration sensor 811 to acquire a 3D motion of the user with respect to the terminal 800. From the data collected by the gyro sensor 812, the processor 801 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

Pressure sensors 813 may be disposed on the side frames of terminal 800 and/or underneath display 805. When the pressure sensor 813 is disposed on the side frame of the terminal 800, the holding signal of the user to the terminal 800 can be detected, and the processor 801 performs left-right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 813. When the pressure sensor 813 is disposed at a lower layer of the display screen 805, the processor 801 controls the operability control on the UI interface according to the pressure operation of the user on the display screen 805. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The fingerprint sensor 814 is used for collecting a fingerprint of the user, and the processor 801 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 814, or the fingerprint sensor 814 identifies the identity of the user according to the collected fingerprint. Upon identifying that the user's identity is a trusted identity, the processor 801 authorizes the user to perform relevant sensitive operations including unlocking a screen, viewing encrypted information, downloading software, paying for and changing settings, etc. Fingerprint sensor 814 may be disposed on the front, back, or side of terminal 800. When a physical button or a vendor Logo is provided on the terminal 800, the fingerprint sensor 814 may be integrated with the physical button or the vendor Logo.

The optical sensor 815 is used to collect the ambient light intensity. In one embodiment, processor 801 may control the display brightness of display 805 based on the ambient light intensity collected by optical sensor 815. Specifically, when the ambient light intensity is high, the display brightness of the display screen 805 is increased; when the ambient light intensity is low, the display brightness of the display 805 is reduced. In another embodiment, the processor 801 may also dynamically adjust the shooting parameters of the camera assembly 806 based on the ambient light intensity collected by the optical sensor 815.

A proximity sensor 816, also known as a distance sensor, is typically provided on the front panel of the terminal 800. The proximity sensor 816 is used to collect the distance between the user and the front surface of the terminal 800. In one embodiment, when the proximity sensor 816 detects that the distance between the user and the front surface of the terminal 800 gradually decreases, the processor 801 controls the display 805 to switch from the bright screen state to the dark screen state; when the proximity sensor 816 detects that the distance between the user and the front surface of the terminal 800 becomes gradually larger, the display 805 is controlled by the processor 801 to switch from the breath-screen state to the bright-screen state.

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

Fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application, where the server 900 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 901 and one or more memories 902, where the one or more memories 902 store at least one instruction, and the at least one instruction is loaded and executed by the one or more processors 901 to implement the reservation request Processing method provided by the foregoing method embodiments. Certainly, the server 900 may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input and output, and the server 900 may also include other components for implementing device functions, which are not described herein again.

In an exemplary embodiment, there is also provided a computer-readable storage medium, such as a memory, including instructions executable by a processor to perform the reservation request processing method in the above-described embodiments. For example, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A reservation request processing method applied to a system including a plurality of first servers and a plurality of second servers, the method comprising:

the second server receives reservation requests of a plurality of user accounts, and each reservation request is used for reserving health services for the user account;

the second server acquires a historical reservation record; for a reservation request of each user account, in response to the historical reservation record indicating that the user account is not reserved, determining at least one candidate first server from the plurality of first servers based on the processing time periods of the plurality of first servers and the reservation time period carried in the reservation request; determining a target first server from the at least one candidate first server based on load information of the at least one candidate first server; distributing the reservation request to the target first server;

the target first server receives a first reservation request of a first user account, wherein the first reservation request is used for reserving a health service for the first user account; acquiring reservation information of reservation identifiers in the target first server, wherein the reservation information comprises the total number of the reservation identifiers in the target first server, the number of reserved reservation identifiers and the number of reservation identifiers which are not reserved;

the target first server responds to the reservation information and indicates that an idle reservation identifier exists in the target first server, and sends a reservation success notification to the first user account, wherein the idle reservation identifier is a reservation identifier which is not reserved; writing the first reservation request into a queue, wherein the queue comprises a second reservation request which is a reservation request received before the first reservation request; determining a reservation time period of the first reservation request according to the position of the first reservation request in the queue; sending the reserved time period to the first user account; for a reservation request positioned at the head of the queue, generating reservation information for a user account corresponding to the reservation request based on the reservation request, wherein the reservation information comprises a reservation time period of the user account corresponding to the reservation request and reserved health services;

the target first server transmits a reservation recording update request to the second server based on a processing result of the first reservation request;

the second server receives a reservation record updating request sent by the target first server; updating the historical reservation record according to the reservation record updating request;

the method further comprises the following steps:

the second server determines the reserved quantity of the reservation identification according to the historical reservation record; in response to the reserved quantity reaching a quantity threshold value, returning a reservation failure notice to the user account in response to the received reservation request of the user account, wherein the reservation failure notice is used for informing that the user account does not have a reserved identifier which can be reserved;

the method further comprises the following steps:

the target first server responds to the reservation information and indicates that no idle reservation identification exists in the target first server, and sends a reservation re-prompting to the first user account, wherein the reservation re-prompting is used for prompting the first user account to resend a reservation request; or, in response to the reservation information indicating that no idle reservation identifier exists in the target first server, sending an allocation request to the second server, where the allocation request is used to request the second server to allocate the first reservation request of the first user account to another first server.

2. The method of claim 1, further comprising:

and deleting the target reservation request from the queue.

3. The method according to claim 2, wherein after receiving a request for canceling a subscription of any user account, the method further comprises:

writing the request for canceling reservation into the queue;

4. A reservation request processing system, the system comprising a plurality of first servers and a plurality of second servers;

the second server is used for receiving reservation requests of a plurality of user accounts, and each reservation request is used for reserving health services for the user account;

the second server is also used for acquiring a historical reservation record; for a reservation request of each user account, in response to the historical reservation record indicating that the user account is not reserved, determining at least one candidate first server from the plurality of first servers based on the processing time periods of the plurality of first servers and the reservation time period carried in the reservation request; determining a target first server from the at least one candidate first server based on load information of the at least one candidate first server; distributing the reservation request to the target first server;

the target first server is used for receiving a first reservation request of a first user account, wherein the first reservation request is used for reserving a health service for the first user account; acquiring reservation information of reservation identifiers in the target first server, wherein the reservation information comprises the total number of the reservation identifiers in the target first server, the number of reserved reservation identifiers and the number of reservation identifiers which are not reserved;

the target first server is further configured to send a reservation success notification to the first user account in response to the reservation information indicating that an idle reservation identifier exists in the target first server, where the idle reservation identifier is an un-reserved reservation identifier; writing the first reservation request into a queue, wherein the queue comprises a second reservation request which is a reservation request received before the first reservation request; determining a reservation time period of the first reservation request according to the position of the first reservation request in the queue; sending the reserved time period to the first user account; for a reservation request positioned at the head of the queue, generating reservation information for a user account corresponding to the reservation request based on the reservation request, wherein the reservation information comprises a reservation time period of the user account corresponding to the reservation request and reserved health services;

the target first server is further used for sending a reservation record updating request to the second server based on the processing result of the first reservation request;

the second server is further used for receiving a reservation record updating request sent by the first server; updating the historical reservation record according to the reservation record updating request;

the second server is also used for determining the reserved quantity of the reservation identifier according to the historical reservation record; in response to the reserved quantity reaching a quantity threshold value, returning a reservation failure notice to the user account in response to the received reservation request of the user account, wherein the reservation failure notice is used for informing that the user account does not have a reserved identifier which can be reserved;

the target first server is further configured to send a re-subscription prompt to the first user account in response to the subscription information indicating that no idle subscription identifier exists in the target first server, where the re-subscription prompt is used to prompt the first user account to resend a subscription request; or, in response to the reservation information indicating that no idle reservation identifier exists in the target first server, sending an allocation request to the second server, where the allocation request is used to request the second server to allocate the first reservation request of the first user account to another first server.

5. A computer device comprising one or more processors and one or more memories having stored therein at least one instruction that is loaded and executed by the one or more processors to perform operations performed by the reservation request processing method of any of claims 1 to 3.

6. A computer-readable storage medium having stored therein at least one instruction, which is loaded and executed by a processor to perform operations performed by the reservation request processing method of any of claims 1 to 3.

7. A computer program product, characterized in that the computer program product comprises at least one program code, which is loaded and executed by a processor to implement the operations performed by the reservation request processing method according to any of the claims 1 to 3.