CN110728385B - Shared object distribution method, server and system - Google Patents
Shared object distribution method, server and system Download PDFInfo
- Publication number
- CN110728385B CN110728385B CN201810776315.3A CN201810776315A CN110728385B CN 110728385 B CN110728385 B CN 110728385B CN 201810776315 A CN201810776315 A CN 201810776315A CN 110728385 B CN110728385 B CN 110728385B
- Authority
- CN
- China
- Prior art keywords
- user terminal
- shared object
- reserved
- shared
- reservation
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
- G06Q10/025—Coordination of plural reservations, e.g. plural trip segments, transportation combined with accommodation
-
- 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
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0645—Rental transactions; Leasing transactions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
Abstract
The embodiment of the invention provides a method, a server and a system for distributing shared objects, wherein the method comprises the following steps: receiving a first message which is sent by a second user terminal and applies for using a first shared object; judging whether the allocable sharing object can be allocated to the first user terminal for use; if yes, distributing the distributable shared object to the first user terminal, and allowing the second user terminal to use the first shared object; otherwise, the second user terminal is refused to use the first shared object. The embodiment of the invention can ensure that the reservation user can be distributed to the shared object, simultaneously reduces the steps of using the shared object by the second user terminal and improves the user experience.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, a server, and a system for allocating shared objects.
Background
The shared service gradually enters our lives, taking a shared bicycle as an example, some shared bicycle enterprises put forward a shared bicycle reservation service for users to use a bicycle conveniently, that is, for a shared bicycle supporting a GPS (Global Positioning System) function, a user can check nearby shared bicycles on a map of a mobile phone application program and select one shared bicycle for reservation. And the shared bicycle background server reserves the shared bicycle for the reservation user until the reservation user takes the shared bicycle away or cancels the reservation. During the time that the sharing bicycle is reserved, any other user will not be able to use the sharing bicycle. For areas with few shared bicycle releases, the prior art can meet the use requirements of users. However, in an area where a lot of shared vehicles are released, for the second user terminal, when the vehicle requested to be used is just the reserved vehicle, the second user terminal can only replace another shared vehicle for use, and may scan the reserved shared vehicle for multiple times, which leads to complicated process steps of using the shared vehicle by the second user terminal, and affects user experience.
Disclosure of Invention
The embodiment of the invention provides a method, a server and a system for distributing a shared object, and aims to solve the problems that the step of applying for using the shared object by a second user terminal is complicated and the user experience is influenced.
According to a first aspect provided by an embodiment of the present invention, there is provided a method for allocating a shared object, including: receiving a first message which is sent by a second user terminal and applies for using a first shared object, wherein the first shared object is reserved for use by the first user terminal; judging whether the reserved use relationship between the first user terminal and the first sharing object can be released or not; if so, releasing the reserved use relationship between the first user terminal and the first shared object, distributing other shared objects which are not reserved currently to the first user terminal, and allowing the second user terminal to use the first shared object; and if not, refusing the second user terminal to use the first shared object.
Optionally, before the receiving a first message requesting to use a first shared object sent by a second user terminal, the allocating method further includes: receiving a second message which is sent by the first user terminal and applies for reserving the first shared object, and recording the position information of the first shared object; and establishing a reserved use relation between the first shared object and the first user terminal.
Optionally, the determining whether the reserved usage relationship between the first user terminal and the first shared object can be released includes: judging whether a sharing object which is not reserved and used by other reserved users exists in a first area, wherein the first area is determined according to the position information of the first sharing object contained in a second message sent by the first user terminal; if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object can be released; otherwise, determining that a second shared object reserved for use by a third user terminal exists in the first area, releasing the reserved use relationship between the third user terminal and the second shared object, establishing the reserved use relationship between the third user terminal and the third shared object, adjusting the state of the second shared object to be not reserved, and determining that the reserved use relationship between the first user terminal and the first shared object can be released as a judgment result, wherein the third shared object is located outside the first area.
Optionally, the determining whether the reserved usage relationship between the first user terminal and the first shared object can be released includes: setting a maximum iteration level, a current iteration query user terminal set, a next iteration query user terminal set and an accumulated queried user terminal set, wherein the current iteration query user terminal set comprises a first user terminal, and the user terminal of the last iteration level of the first user terminal is an empty user terminal; the next iteration inquiry user terminal set and the accumulated inquiry user terminal set are both empty sets; at least one fourth user terminal in the current iteration query user terminal set determines a designated area according to position information of a fourth shared object contained in a reservation application sent by the fourth user terminal; judging whether a fifth sharing object which is not reserved and used by other reservation users exists in the designated area; if so, establishing a reserved use relationship between the fourth user terminal and the fifth shared object, adjusting the state of the fourth shared object to be not reserved, establishing a reserved use relationship between the fourth shared object and a fifth user terminal of a previous iteration layer, repeating the above processes until the user terminal of the previous iteration layer is the first user terminal, ending the iteration process, and determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object can be released.
Optionally, the determining whether the reserved usage relationship between the first user terminal and the first shared object can be released further includes: if a fifth shared object which is not reserved for use by other reserved users does not exist in the designated area, setting a user terminal of a previous iteration layer of a reserved user terminal corresponding to the reserved shared object in the designated area as the fourth user terminal, adding the reserved user terminal into a next iteration inquiry user terminal set, and adding the fourth user terminal into an accumulated inquiry user terminal set; if all the user terminals in the current iteration query user terminal set are processed, increasing the current iteration level, and judging whether the current iteration level is greater than the maximum iteration level; if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object cannot be released; otherwise, setting the current iteration inquiry user terminal set equal to the next iteration user terminal set minus the accumulated inquiry user terminal set, setting the next iteration inquiry user terminal set equal to the empty set, repeatedly executing at least one fourth user terminal in the current iteration inquiry user terminal set, and determining a designated area according to the position information of a fourth shared object contained in a reservation application sent by the fourth user terminal; and judging whether a fifth sharing object which is not reserved and used by other reservation users exists in the designated area.
According to a second aspect of the embodiments of the present invention, there is provided a server, including: the system comprises a first transceiver and a first processor, wherein the first transceiver is used for receiving a first message sent by a second user terminal for applying for using a first shared object, and the first transceiver is used for receiving a first message sent by the second user terminal for applying for using the first shared object, and the first shared object is reserved for use by the first user terminal; the first processor is used for judging whether the reserved use relationship between the first user terminal and the first shared object can be released or not; if so, releasing the reserved use relationship between the first user terminal and the first shared object, distributing other shared objects which are not reserved at present to the first user terminal, and allowing the second user terminal to use the first shared object; and if not, refusing the second user terminal to use the first shared object.
Optionally, the first transceiver is further configured to: receiving a second message which is sent by the first user terminal and applies for using the first shared object in a reserved mode, and recording position information of the first shared object; the first processor is further configured to: and establishing a reserved use relation between the first shared object and the first user terminal.
Optionally, the first processor is further configured to: judging whether a sharing object which is not reserved and used by other reserved users exists in a first area, wherein the first area is determined according to the position information of the first sharing object contained in a second message sent by the first user terminal; if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object can be released; otherwise, determining a second shared object reserved for use by a third user terminal in the first area, releasing the reserved use relationship between the third user terminal and the second shared object, establishing the reserved use relationship between the third user terminal and the third shared object, adjusting the state of the second shared object to be not reserved, and determining that the reserved use relationship between the first user terminal and the first shared object can be released as a result of determination, wherein the third shared object is located outside the first area.
Optionally, the first processor is further configured to: setting a maximum iteration level, a current iteration query user terminal set, a next iteration query user terminal set and an accumulated queried user terminal set, wherein the current iteration query user set comprises a first user terminal, and a user terminal of a last iteration level of the first user terminal is an empty user terminal; the next iteration inquiry user terminal set and the accumulated inquiry user terminal set are both empty sets; at least one fourth user terminal in the current iteration query user terminal set determines a designated area according to position information of a fourth shared object contained in a reservation application sent by the fourth user terminal; judging whether a fifth sharing object which is not reserved and used by other reservation users exists in the designated area; if yes, establishing a reserved use relationship between the fourth user terminal and the fifth shared object. And adjusting the state of the fourth shared object to be not reserved, establishing a reserved use relationship between the fourth shared object and a fifth user terminal of a previous iteration chromatography, repeating the process until the user terminal of the previous iteration layer is the first user terminal, finishing the iteration process, and determining that the reserved use relationship between the first user terminal and the first shared object can be released as a judgment result.
Optionally, the first processor is further configured to: if a fifth shared object which is not reserved and used by other reserved users does not exist in the designated area, setting a user terminal of a previous iteration layer of a reserved user terminal corresponding to reserved sharing in the designated area as the fourth user terminal, adding the reserved user terminal into a next iteration inquiry user terminal set, and adding the fourth user terminal into an accumulated inquiry user terminal set; if all the user terminals in the current iteration query user terminal set are processed, increasing the current iteration level, and judging whether the current iteration level is greater than the maximum iteration level; if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object cannot be released; otherwise, setting the current iteration inquiry user terminal set to be equal to the next iteration user terminal set minus the accumulation and inquiry user terminal set, setting the next iteration inquiry user terminal set to be equal to the empty set, repeatedly executing at least one fourth user terminal in the current iteration inquiry user terminal set, and determining a specified area according to the position information of a fourth shared object contained in a reservation application sent by the fourth user terminal; and judging whether a fifth sharing object which is not reserved and used by other reservation users exists in the designated area.
According to a third aspect of the embodiments of the present invention, there is provided a shared object allocation system, including: a user terminal, a shared object and a server as described in the second aspect.
According to a fourth aspect of the embodiments of the present invention, there is provided a server, including: a processor, a memory and a program of an allocation method of a shared object stored on the memory and executable on the processor, the program of an allocation method of a shared object implementing the steps of the allocation method of a shared object as described in the first aspect when executed by the processor.
According to a fifth aspect of embodiments of the present invention, there is provided a computer-readable storage medium having stored thereon a program of an allocation method of a shared object, the program of the allocation method of the shared object implementing the steps of the allocation method of the shared object as described in the first aspect when executed by a processor.
The embodiment of the invention has the following beneficial effects: when the second user terminal applies for using the reserved shared object, the server firstly judges whether a new shared object can be allocated to the first user terminal reserving the shared object, if so, the new shared object is allocated to the first user, and the second user is allowed to use the shared object; otherwise, the second user terminal is refused to use the reserved shared object. Therefore, the steps that other second user terminals apply for using the shared object are reduced while the user can be distributed to the shared object, and the user experience is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
Fig. 1 is a diagram illustrating a method for allocating a shared object according to an embodiment of the present invention;
FIG. 2 is a second method for allocating shared objects according to the present invention;
FIG. 3 is a third method for allocating a shared object according to an embodiment of the present invention;
FIGS. 4a to 4b are schematic distribution diagrams of a shared object according to an embodiment of the present invention;
FIG. 5 is a fourth method for allocating a shared object according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of another distribution of shared objects according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a server according to an embodiment of the present invention;
FIG. 8 is a diagram illustrating a system for allocating shared objects according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of another server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, an embodiment of the present invention provides a method for allocating shared objects, which includes the following specific steps:
in the embodiment of the invention, the first sharing object is reserved to be used by the first user terminal. The first message may carry the identifier of the second user terminal and the first shared object.
It should be noted that the second user terminal may select a nearby shared object to apply for use because the shared object that is reserved for use is not found, or the second user terminal may reserve for use another shared object.
The manner for triggering the second user terminal to send the first message may be based on the second user terminal scanning the two-dimensional code on the shared object, or may be based on the number of the shared object input on the second user terminal.
in the embodiment of the present invention, the basis of the determination may be whether to allocate an allocable shared object to the first user terminal, it should be noted that the allocable shared object may be a shared object that is not reserved by other users and is in an unreserved state, or the allocable shared object may also be a shared object that is currently reserved, but a user corresponding to the shared object may be allocated with another shared object, and the server may adjust the state of the reserved shared object to be unreserved, and allocate the shared object to the first user terminal as a new shared object.
103, releasing the reserved use relationship between the first user terminal and the first shared object, distributing other shared objects which are not reserved currently to the first user terminal, and allowing the second user terminal to use the first shared object;
in the embodiment of the invention, the server releases the reserved use relationship between the first user terminal and the first shared object, adjusts the state of the first shared object to be not reserved, allocates a new shared object to the first user terminal, and allocates the first shared object to the second user terminal for use. Optionally, the position of the newly allocated shared object is displayed through the application program of the first user terminal, and the display content may include the identifier of the shared object or may not include the identifier of the shared object.
104, refusing the second user terminal to use the first shared object;
in the embodiment of the present invention, since a new shared object cannot be allocated to the first user terminal and the reserved usage relationship between the first user terminal and the first shared object cannot be released, it is preferable to ensure the usage requirement of the first user terminal and reject the usage request of the second user terminal.
Thus, when the second user terminal applies for using the reserved shared object, the server will firstly judge whether a new shared object can be allocated to the first user terminal of the shared object, if so, the server allocates the new shared object to the first user terminal, and allows the second user terminal to use the shared object; otherwise, the second user terminal is refused to use the reserved shared object. Therefore, the steps of using the shared object by the second user terminal are reduced while the first user terminal is ensured to be allocated to the shared object, and the user experience is improved.
Referring to fig. 2, an embodiment of the present invention further provides a method for allocating a shared object, which includes the following specific steps:
in the embodiment of the present invention, the second message carries the identifier of the first user terminal and the first reserved shared object, and the embodiment of the present invention does not specifically limit the manner in which the first user terminal sends the second message for reserving the first reserved shared object. The server records the position information of the first reserved sharing object, and the server can select to send the position information of the first reserved sharing object to the first user terminal in an image mode.
the first reservation sharing object and the first sharing object may be the same or different. In addition, the reserved usage relationship between the first shared object and the first user terminal is not fixed, the server can change the reserved usage relationship between the first user terminal and the shared object at any time, the server can determine an area according to the position information of the first reserved shared object, and the shared objects capable of establishing the reserved usage relationship with the first user terminal are all selected from the area.
in the embodiment of the invention, the first sharing object is reserved for use by the first user terminal. The first message carries the identifiers of the second user terminal and the first shared object.
It should be noted that the second user terminal may select a nearby shared object to apply for use because the shared object previously reserved for use cannot be found without reserving the shared object or reserving another shared object for use.
The manner for triggering the second user terminal to send the first message may be based on the second user terminal scanning the two-dimensional code on the shared object, or may be based on the number of the shared object input on the second user terminal.
in the embodiment of the present invention, the basis of the determination may be whether to allocate an allocable shared object to the first user terminal, it should be noted that the allocable shared object may be a shared object that is not reserved by other users and is in an unreserved state, or the allocable shared object may also be a shared object that is currently reserved, but a user corresponding to the shared object may be allocated with another shared object, and the server may adjust the state of the reserved shared object to be unreserved, and allocate the shared object to the first user terminal as a new shared object.
in the embodiment of the invention, the server releases the reserved use relationship between the first user terminal and the first shared object, adjusts the state of the first shared object to be not reserved, allocates a new shared object to the first user terminal, and allocates the first shared object to the second user terminal for use. Optionally, the position of the newly allocated shared object is displayed through the application program of the first user terminal, and the display content may include the identifier of the shared object or may not include the identifier of the shared object.
in the embodiment of the present invention, since a new shared object cannot be allocated to the first user terminal and the reserved usage relationship between the first user terminal and the first shared object cannot be released, it is preferable to ensure the usage requirement of the first user terminal and reject the usage request of the second user terminal.
Thus, when the second user terminal applies for using the reserved shared object, the server will firstly judge whether a new shared object can be allocated to the reservation user of the shared object, if so, the server allocates the new shared object to the reservation user and allows the reservation user to use the shared object; otherwise, the second user terminal is refused to use the reserved shared object. The steps of using the shared object by the second user terminal are reduced while the reservation user is ensured to be allocated to the shared object, and the user experience is improved.
Referring to fig. 3, an embodiment of the present invention provides another method for allocating shared objects, which includes the following specific steps:
in the embodiment of the invention, the first sharing object is reserved for use by the first user terminal. The first message carries the identifiers of the second user terminal and the first shared object.
It should be noted that the second user terminal may select a nearby shared object to apply for use because the shared object previously reserved for use cannot be found without reserving the shared object or reserving another shared object for use.
The manner for triggering the second user terminal to send the first message may be based on the second user terminal scanning the two-dimensional code on the shared object, or may be based on the number of the shared object input on the second user terminal.
in the embodiment of the present invention, the server determines a first region by taking the position of the first reserved shared object as a center according to the position information of the first reserved shared object, where the first region includes a plurality of other shared objects, and the server searches whether there is an un-reserved shared object in the other shared objects. The first reservation sharing object is a sharing object initially applied when the first user terminal initiates a reservation application.
in the embodiment of the invention, the server releases the reserved use relationship between the first user terminal and the first shared object, adjusts the state of the first shared object to be not reserved, allocates a new shared object to the first user terminal, and allocates the first shared object to the second user terminal for use.
in the embodiment of the invention, other shared objects in the first area are reserved, the server selects one of the other shared objects as a second shared object, and the corresponding user is a third user terminal.
Specifically, referring to fig. 4a, P1 is a first shared object, and P2 is a second shared object.
The server determines an area according to the position information of a second reserved sharing object initially applied when a third user terminal initiates a reservation application, by taking the position of the second reserved sharing object as a center, allocates any non-reserved sharing object in the area to the third user terminal as a third sharing object, and the third sharing object is located outside the first area.
Specifically, referring to fig. 4b, P1 is a first shared object, P2 is a second shared object, and P3 is a third shared object.
in the embodiment of the invention, the server allocates the third shared object to the third user terminal, allocates the second shared object to the first user terminal and allocates the first shared object to the second user terminal, so that the users who previously reserve the shared object can be allocated with the shared object, and meanwhile, the second user terminal can use the shared object.
Therefore, when the second user terminal applies for using the reserved shared object, the server can firstly judge whether a new shared object can be allocated to the reserved user of the shared object, and when the first area has no reserved shared object, the server can reallocate the shared object based on the reserved shared object in the first area, so that the allocation of the shared object is more flexible while the reserved user can be allocated to the shared object, the steps of using the shared object by the second user terminal are reduced, and the user experience is improved.
Referring to fig. 5, an embodiment of the present invention provides another method for allocating a shared object, which includes the following specific steps:
in the embodiment of the invention, the first sharing object is reserved to be used by the first user terminal. The first message carries the identifiers of the second user terminal and the first shared object.
It should be noted that the second user terminal may select a nearby shared object to apply for use because the shared object previously reserved for use cannot be found without reserving the shared object or reserving another shared object for use.
The manner for triggering the second user terminal to send the first message may be based on the second user terminal scanning the two-dimensional code on the shared object, or may be based on the number of the shared object input on the second user terminal.
in the embodiment of the present invention, the basis of the determination may be whether an allocatable shared object can be allocated to the first user terminal, it should be noted that the allocatable shared object may be a shared object that is not reserved by other users and is in an unsubscribed state, or the allocatable shared object may also be a shared object that is currently reserved, but a user corresponding to the shared object may be allocated with another shared object, and the server may adjust the state of the reserved shared object to be unsubscribed and allocate the shared object as a new shared object to the first user terminal.
in the embodiment of the invention, the server releases the reserved use relationship between the first user terminal and the first shared object, adjusts the state of the first shared object to be not reserved, allocates a new shared object to the first user terminal, and allocates the first shared object to the second user terminal for use.
in the embodiment of the present invention, since there is no unreserved shared object in the first area, the server tries to check the area determined by the reserved shared object in the first area, and reallocates the user terminal and the shared object in sequence, which is an iterative process. The maximum iteration level is used for controlling the number of times of executing the iteration process to be limited. The first region is determined according to the position information of a first reservation sharing object initially applied when the first user terminal initiates a reservation application.
When the iterative process is started, initialization setting is carried out, namely the current iterative query user terminal set comprises a first user terminal, the user terminal in the last iterative layer of the first user terminal is set as an empty user terminal, the iterative layer where the first user terminal is located is represented as an initial iterative layer, and the next iterative query user terminal set and the accumulated queried user terminal set are set as empty sets.
in the embodiment of the present invention, after the fourth user terminal performs an iteration process several times, and then, the user terminal currently performs an inquiry, the embodiment of the present invention does not specifically limit the iteration hierarchy corresponding to the fourth user terminal, and determines a designated region according to the location information of the third reserved sharing object initially applied when the reservation application is sent by the fourth user terminal.
in the embodiment of the invention, if the shared objects in the designated area are reserved, the iteration process of the next iteration layer is needed, and before the iteration is carried out, the fourth user terminal is added into the accumulated queried user terminal set, and the next iteration queried user terminal set is determined.
509, increasing the current iteration level, and judging whether the iteration chromatography is larger than the maximum iteration level; if yes, go back to step 510; otherwise, go to step 511;
in the embodiment of the present invention, since a new shared object cannot be allocated to the first user terminal, and the reserved usage relationship between the first user terminal and the first shared object cannot be released, it is preferable to ensure the usage requirement of the first user terminal and reject the usage request of the second user terminal.
in the embodiment of the invention, the current iteration inquiry user terminal set is equal to the next iteration user terminal set minus the accumulated inquiry user terminal set, and the judged user terminals are not repeatedly judged, so that the cyclic judgment is avoided, and the result cannot be obtained.
Therefore, when the second user terminal applies for using the reserved shared object, the server can firstly judge whether a new shared object can be allocated to the reserved user of the shared object, and the operation of searching for the new allocable shared object can be carried out for a plurality of times, so that the allocation of the shared object is more flexible while the reserved user can be allocated to the shared object, the steps of using the shared object by the second user terminal are reduced, and the user experience is improved.
Referring to fig. 6, an application scenario is provided, which is suitable for the method embodiment shown in fig. 5. B1 is a first shared object, and B2 to B4 are other shared objects. For the sake of simplicity of description, it is not assumed here that the user terminal initiates the reservation application as the shared object initially applied for, and at the same time, the server allocates the shared object to the user terminal for use. For the case that the iteration level is 1, the server checks whether B2 and B3 are non-reservation sharing objects; if both the objects are reserved, the iteration level is 2, that is, as shown in the figure, it is detected whether B4 is an object which is not reserved for sharing in the designated area of B3. B2 and B3 are both located in the designated areas of each other, if the server performs the investigation on the designated area of B2 and then performs the investigation on the designated area of B3, the determination on B2 is skipped when performing the investigation on the designated area of B3, otherwise the loop determination between B2 and B3 is caused, and the determination cannot be finished, it should be noted that fig. 6 is only one embodiment of the present invention, and the distribution manner and the determination sequence of the shared objects are not specifically limited in the embodiment of the present invention.
B4 is an unsubscribed shared object, B4 is allocated to the original user terminal of B3, B3 is allocated to the original user terminal of B1, i.e. the first user terminal, and B2 is allocated to the second user terminal, so that the second user terminal can use the shared object while ensuring that the reserved user terminals are all allocated with the shared object.
Referring to fig. 7, an embodiment of the present invention provides a server 700, including: a first transceiver 701 and a first processor 702.
The first transceiver 701 is configured to receive a first message, sent by a second user terminal, for applying for using a first shared object, where the first shared object has been reserved for use by the first user terminal;
the first processor 702 is configured to determine whether a reserved usage relationship between the first user terminal and the first shared object can be released; if so, releasing the reserved use relationship between the first user terminal and the first shared object, distributing other shared objects which are not reserved currently to the first user terminal, and allowing the second user terminal to use the first shared object; and if not, refusing the second user terminal to use the first shared object.
Optionally, the first transceiver 701 is further configured to receive a second message, sent by the first user terminal, for applying for making a reservation to use the first shared object;
optionally, the first processor 702 is further configured to record location information of the first shared object; establishing a reserved use relation between the first shared object and the first user terminal;
optionally, the first processor 702 is further configured to determine whether a shared object not reserved for use by other reservation users exists in a first area, where the first area is determined according to location information of the first shared object included in a second message sent by the first user terminal; if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object can be released; otherwise, determining a second shared object reserved for use by a third user terminal in the first area, releasing the reserved use relationship between the third user terminal and the second shared object, establishing the reserved use relationship between the third user terminal and the third shared object, adjusting the state of the second shared object to be not reserved, and determining that the reserved use relationship between the first user terminal and the first shared object can be released as a result of determination, wherein the third shared object is located outside the first area.
Optionally, the first processor 702 is further configured to: setting a maximum iteration level, a current iteration query user terminal set, a next iteration query user terminal set and an accumulated queried user terminal set, wherein the current iteration query user set comprises a first user terminal, and the user terminal of the last iteration level of the first user terminal is an empty user terminal; the next iteration inquiry user terminal set and the accumulated inquiry user terminal set are both empty sets; aiming at least one fourth user terminal in the current iteration query user terminal set, determining a designated area according to position information of a fourth shared object contained in a reservation application sent by the fourth user terminal; judging whether a fifth sharing object which is not reserved for use by other reservation users exists in the designated area; if yes, establishing a reserved use relationship between the fourth user terminal and the fifth shared object. And adjusting the state of the fourth shared object to be not reserved, establishing a reserved use relationship between the fourth shared object and a fifth user terminal of the previous iteration chromatography, repeating the process until the user terminal of the previous iteration layer is the first user terminal, ending the iteration process, and determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object can be released.
Optionally, the first processor 702 is further configured to: if a fifth shared object which is not reserved and used by other reserved users does not exist in the designated area, setting a user terminal of a previous iteration layer of a reserved user terminal corresponding to reserved sharing in the designated area as the fourth user terminal, adding the reserved user terminal into a next iteration inquiry user terminal set, and adding the fourth user terminal into an accumulated inquiry user terminal set; if all the user terminals in the current iteration query user terminal set are processed, increasing the current iteration level, and judging whether the current iteration level is greater than the maximum iteration level; if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object cannot be released; otherwise, setting the current iteration inquiry user terminal set to be equal to the next iteration user terminal set minus the accumulation and inquiry user terminal set, setting the next iteration inquiry user terminal set to be equal to the empty set, repeatedly executing at least one fourth user terminal in the current iteration inquiry user terminal set, and determining a specified area according to the position information of a fourth shared object contained in a reservation application sent by the fourth user terminal; and judging whether a fifth sharing object which is not reserved and used by other reservation users exists in the designated area.
Therefore, when the second user terminal applies for using the reserved shared object, the server can firstly judge whether a new shared object can be allocated to the reservation user of the shared object, and the operation of searching the new allocable shared object can be carried out for a plurality of times, so that the allocation of the shared object is more flexible while the reservation user can be allocated to the shared object, the steps of using the shared object by the second user terminal are reduced, and the user experience is improved.
Referring to fig. 8, an embodiment of the present invention provides a system 800 for allocating a shared object, including: a subscriber terminal 801, a non-subscriber terminal 802, a shared object 803, and the server 804 described above. In the embodiment of the present invention, the numbers of the subscribed user terminal 801, the non-subscribed user terminal 802, and the shared object 803 may be one or more, and the number of the subscribed user terminal 801, the non-subscribed user terminal 802, and the shared object 803 in the embodiment of the present invention is not specifically limited.
Referring to fig. 9, another server 900 is provided in an embodiment of the present invention, including: a processor 901, a transceiver 902, a memory 903 and a bus interface.
Among other things, the processor 901 may be responsible for managing the bus architecture and general processing. The memory 903 may store data used by the processor 901 in performing operations.
In this embodiment of the present invention, the server 900 may further include: a computer program stored on the memory 903 and executable on the processor 901, the computer program implementing the steps of the allocation method of the shared object provided by the embodiment of the present invention when executed by the processor 901.
In fig. 9, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 901 and various circuits of memory represented by memory 903 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further by the embodiments. The bus interface provides an interface. The transceiver 902 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the processes of the foregoing shared object allocation method embodiment, and can achieve the same technical effects, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present invention or portions thereof contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a user equipment (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the method according to the embodiments of the present invention.
The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A distribution method of a shared object is applied to a server, and is characterized in that the distribution method comprises the following steps:
receiving a first message which is sent by a second user terminal and applies for using a first shared object, wherein the first shared object is reserved for using by the first user terminal;
judging whether a reserved use relationship between the first user terminal and the first shared object can be released or not according to whether a shared object which is not reserved for use by other reserved users exists in a first area or not; the first area is determined according to the position information of the first reservation sharing object transmitted by the first user terminal;
if so, releasing the reserved use relationship between the first user terminal and the first shared object, distributing other shared objects which are not reserved currently to the first user terminal, and allowing the second user terminal to use the first shared object;
otherwise, refusing the second user terminal to use the first shared object;
the determining whether the reserved usage relationship between the first user terminal and the first shared object can be released includes:
judging whether a sharing object which is not reserved for use by other reservation users exists in the first area;
if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object can be released;
otherwise, other shared objects except the first shared object in the first area are reserved, a second shared object reserved and used by a third user terminal is determined to exist in the first area, the server selects one of the other shared objects as a second shared object, a corresponding user is a third user terminal, the server determines an area by taking the position of the second reserved shared object as the center according to the position information of the second reserved shared object initially applied when the third user terminal initiates a reservation application, any one reserved shared object in the area is allocated to the third user terminal as the third shared object, the reservation use relationship between the third user terminal and the second shared object is released, the reservation use relationship between the third user terminal and the third shared object is established, the state of the second shared object is adjusted to be not reserved, and the judgment result is determined that the reservation use relationship between the first user terminal and the first shared object can be released, wherein the third shared object is located outside the first area.
2. The allocation method according to claim 1, wherein before said receiving the first message requesting to use the first shared object sent by the second user terminal, the allocation method further comprises:
receiving a second message which is sent by the first user terminal and applies for reserving a first reserved sharing object, and recording the position information of the first reserved sharing object;
establishing a reserved using relation between the first reserved sharing object and the first user terminal;
wherein the first reservation sharing object is the same as or different from the first sharing object.
3. The allocation method according to claim 2, wherein the determining whether the reserved usage relationship between the first user terminal and the first shared object can be released comprises:
setting a maximum iteration level, a current iteration query user terminal set, a next iteration query user terminal set and an accumulated queried user terminal set, wherein the current iteration query user terminal set comprises a first user terminal, and a user terminal of a last iteration level of the first user terminal is an empty user terminal; the next iteration inquiry user terminal set and the accumulated inquiry user terminal set are both empty sets;
aiming at least one fourth user terminal in the current iteration query user terminal set, determining a designated area according to position information of a third reservation sharing object initially applied when a reservation application is sent by the fourth user terminal; judging whether a fifth sharing object which is not reserved and used by other reservation users exists in the designated area;
if yes, establishing a reserved use relationship between the fourth user terminal and the fifth shared object, adjusting the state of a fourth shared object currently allocated by the fourth user terminal to be reserved, establishing a reserved use relationship between the fourth shared object and a fifth user terminal in a previous iteration layer, repeating the process of establishing the reserved use relationship between the fourth user terminal and the fifth shared object, adjusting the state of the fourth shared object currently allocated by the fourth user terminal to be reserved, establishing a reserved use relationship between the fourth shared object and the fifth user terminal in the previous iteration layer until the user terminal in the previous iteration layer is the first user terminal, ending the iteration process, and determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object can be released.
4. The allocation method according to claim 3, wherein the determining whether the reserved usage relationship between the first user terminal and the first shared object can be released further comprises:
if a fifth shared object which is not reserved and used by other reserved users does not exist in the designated area, setting a user terminal of a previous iteration layer of a reserved user terminal corresponding to the reserved shared object in the designated area as the fourth user terminal, adding the reserved user terminal into a next iteration inquiry user terminal set, and adding the fourth user terminal into an accumulated inquiry user terminal set;
if all the user terminals in the current iteration query user terminal set are processed, increasing the current iteration level, and judging whether the current iteration level is greater than the maximum iteration level;
if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object cannot be released;
otherwise, setting the current iteration inquiry user terminal set equal to the next iteration user terminal set minus the accumulated inquiry user terminal set, setting the next iteration inquiry user terminal set equal to the empty set, repeatedly executing at least one fourth user terminal in the current iteration inquiry user terminal set, and determining a designated area according to the position information of a fourth shared object contained in a reservation application sent by the fourth user terminal; and judging whether a fifth sharing object which is not reserved and used by other reservation users exists in the designated area.
5. A server, characterized in that the server comprises: a first transceiver and a first processor, wherein,
the first transceiver is to: receiving a first message which is sent by a second user terminal and applies for using a first shared object, wherein the first shared object is reserved for using by the first user terminal;
the first processor is to: judging whether a reserved use relationship between the first user terminal and the first shared object can be released or not according to whether a shared object which is not reserved for use by other reserved users exists in a first area or not; the first area is determined according to the position information of the first reservation sharing object transmitted by the first user terminal;
if so, releasing the reserved use relationship between the first user terminal and the first shared object, distributing other shared objects which are not reserved currently to the first user terminal, and allowing the second user terminal to use the first shared object;
otherwise, refusing the second user terminal to use the first shared object;
the first processor is further configured to: judging whether a sharing object which is not reserved and used by other reservation users exists in the first area; if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object can be released; otherwise, other shared objects except the first shared object in the first area are reserved, a second shared object reserved and used by a third user terminal is determined in the first area, the server selects one of the other shared objects as a second shared object, a corresponding user is a third user terminal, the server determines an area according to the position information of the second reserved shared object initially applied when the third user terminal initiates reservation application, the position of the second reserved shared object is taken as a center, any non-reserved shared object in the area is taken as the third shared object to be distributed to the third user terminal, the reservation use relation between the third user terminal and the second shared object is released, the reservation use relation between the third user terminal and the third shared object is established, the state of the second shared object is adjusted to be not reserved, and the judgment result is determined that the reservation use relation between the first user terminal and the first shared object can be released, wherein the third shared object is located outside the first shared object.
6. The server according to claim 5,
the first transceiver is further configured to: receiving a second message which is sent by the first user terminal and applies for reserving the first reservation sharing object;
the first processor is further configured to: recording the position information of the first reservation sharing object; establishing a reservation use relation between the first reservation sharing object and the first user terminal;
wherein the first reservation sharing object is the same as or different from the first sharing object.
7. The server according to claim 6, wherein the first processor is further configured to: setting a maximum iteration level, a current iteration query user terminal set, a next iteration query user terminal set and an accumulated queried user terminal set, wherein the current iteration query user terminal set comprises a first user terminal, and the user terminal of the last iteration level of the first user terminal is an empty user terminal; the next iteration inquiry user terminal set and the accumulated inquiry user terminal set are both empty sets; aiming at least one fourth user terminal in the current iteration query user terminal set, determining a designated area according to position information of a third reservation sharing object initially applied when a reservation application is sent by the fourth user terminal; judging whether a fifth sharing object which is not reserved and used by other reservation users exists in the designated area; if so, establishing a reserved use relationship between the fourth user terminal and the fifth shared object, adjusting the state of a fourth shared object currently allocated by the fourth user terminal to be not reserved, establishing a reserved use relationship between the fourth shared object and a fifth user terminal of a previous iteration level, repeating the above-mentioned process of establishing the reserved use relationship between the fourth user terminal and the fifth shared object, adjusting the state of the fourth shared object currently allocated by the fourth user terminal to be not reserved, and establishing a reserved use relationship between the fourth shared object and the fifth user terminal of the previous iteration level until the user terminal of the previous iteration level is the first user terminal, ending the iteration process, and determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object can be released.
8. The server according to claim 7, wherein the first processor is further configured to: if a fifth shared object which is not reserved and used by other reserved users does not exist in the designated area, setting a user terminal of a previous iteration layer of a reserved user terminal corresponding to the reserved shared object in the designated area as the fourth user terminal, adding the reserved user terminal into a next iteration inquiry user terminal set, and adding the fourth user terminal into an accumulated inquiry user terminal set; if all the user terminals in the current iteration query user terminal set are processed, increasing the current iteration level, and judging whether the current iteration level is greater than the maximum iteration level; if so, determining that the judgment result is that the reserved use relationship between the first user terminal and the first shared object cannot be released; otherwise, setting the current iteration inquiry user terminal set equal to the next iteration user terminal set minus the accumulated inquiry user terminal set, setting the next iteration inquiry user terminal set equal to the empty set, repeatedly executing at least one fourth user terminal in the current iteration inquiry user terminal set, and determining a designated area according to the position information of a fourth shared object contained in a reservation application sent by the fourth user terminal; and judging whether a fifth sharing object which is not reserved and used by other reservation users exists in the designated area.
9. A distribution system for shared objects, the distribution system comprising: a user terminal, a shared object and a server as claimed in any one of claims 5 to 8.
10. A server, characterized by comprising: a processor, a memory, and a program of a shared object allocation method stored on the memory and executable on the processor, wherein the program of the shared object allocation method realizes the steps of the shared object allocation method according to any one of claims 1 to 4 when executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810776315.3A CN110728385B (en) | 2018-07-16 | 2018-07-16 | Shared object distribution method, server and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810776315.3A CN110728385B (en) | 2018-07-16 | 2018-07-16 | Shared object distribution method, server and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110728385A CN110728385A (en) | 2020-01-24 |
| CN110728385B true CN110728385B (en) | 2023-01-03 |
Family
ID=69217293
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810776315.3A Active CN110728385B (en) | 2018-07-16 | 2018-07-16 | Shared object distribution method, server and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110728385B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH11353390A (en) * | 1998-06-05 | 1999-12-24 | Nec Inf Service Ltd | Board room reservation management system, and recording medium recorded with program thereof |
| JP2011154648A (en) * | 2010-01-28 | 2011-08-11 | Kddi Corp | Reservation management device for shared object, system, program, and method |
| CN105760940A (en) * | 2016-02-03 | 2016-07-13 | 武汉天梯极客网络科技有限公司 | Vehicle reservation method and cloud management server |
| CN106454207A (en) * | 2016-12-19 | 2017-02-22 | 深圳市中讯网联科技有限公司 | Distribution method and system of video conference resource |
| CN106682971A (en) * | 2017-01-13 | 2017-05-17 | 上海量明科技发展有限公司 | Shared bicycle reservation method, user terminal and system |
| CN107945408A (en) * | 2017-12-05 | 2018-04-20 | 上海同耀通信技术有限公司 | A kind of method, system, server and mobile terminal using shared bicycle |
-
2018
- 2018-07-16 CN CN201810776315.3A patent/CN110728385B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH11353390A (en) * | 1998-06-05 | 1999-12-24 | Nec Inf Service Ltd | Board room reservation management system, and recording medium recorded with program thereof |
| JP2011154648A (en) * | 2010-01-28 | 2011-08-11 | Kddi Corp | Reservation management device for shared object, system, program, and method |
| CN105760940A (en) * | 2016-02-03 | 2016-07-13 | 武汉天梯极客网络科技有限公司 | Vehicle reservation method and cloud management server |
| CN106454207A (en) * | 2016-12-19 | 2017-02-22 | 深圳市中讯网联科技有限公司 | Distribution method and system of video conference resource |
| CN106682971A (en) * | 2017-01-13 | 2017-05-17 | 上海量明科技发展有限公司 | Shared bicycle reservation method, user terminal and system |
| CN107945408A (en) * | 2017-12-05 | 2018-04-20 | 上海同耀通信技术有限公司 | A kind of method, system, server and mobile terminal using shared bicycle |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110728385A (en) | 2020-01-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20040078339A1 (en) | Priority based licensing | |
| CN112269641B (en) | Scheduling method, scheduling device, electronic equipment and storage medium | |
| CN110661894A (en) | User IP address allocation method, network device and storage medium | |
| CN112887228A (en) | Cloud resource management method and device, electronic equipment and computer readable storage medium | |
| US20110035499A1 (en) | Discontinuous access management method using waiting ticket for resource allocation control, waiting ticket management method, and resource allocation control method | |
| CN114385370B (en) | Memory allocation method, system, device and medium | |
| CN111093160A (en) | Calling method, equipment and system | |
| CN111726241B (en) | Network resource management method, system, network device and readable storage medium | |
| CN108667940B (en) | Resource allocation method and device of cloud platform and computer readable storage medium | |
| CN110728385B (en) | Shared object distribution method, server and system | |
| CN108933675B (en) | Conference resource allocation method, device and storage medium | |
| CN111343240B (en) | Service request processing method and device, electronic equipment and storage medium | |
| CN110677838A (en) | Service distribution method and device | |
| KR20150074531A (en) | Apparatus and method for providing bandwidth on demand service | |
| CN110661630B (en) | Method, device and system for distributing network slice instances | |
| CN109561411B (en) | Taxi taking service optimization method and device | |
| CN112616143B (en) | Method and device for distributing communication numbers, electronic equipment and storage medium | |
| CN111611081B (en) | Request method, request device, computer equipment and storage medium | |
| CN111988841B (en) | Registration, registration request sending method, device, communication equipment and storage medium | |
| US11212352B2 (en) | Sharing system, method, and management server | |
| CN112910673B (en) | Method, device, equipment and storage medium for determining network element deployment information | |
| US20230239727A1 (en) | Method for predictively operating a communication network | |
| CN117478722B (en) | P2P identifier allocation method, system, electronic equipment and storage medium | |
| US20230274300A1 (en) | Mobility service apparatus and method using flexible rate | |
| CN117596594A (en) | License management method, license management device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |