CN110751532A - Resource allocation method and device - Google Patents

Resource allocation method and device Download PDF

Info

Publication number
CN110751532A
CN110751532A CN201910386332.0A CN201910386332A CN110751532A CN 110751532 A CN110751532 A CN 110751532A CN 201910386332 A CN201910386332 A CN 201910386332A CN 110751532 A CN110751532 A CN 110751532A
Authority
CN
China
Prior art keywords
service
description information
information
resource allocation
resource
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.)
Granted
Application number
CN201910386332.0A
Other languages
Chinese (zh)
Other versions
CN110751532B (en
Inventor
何棣
周婧柔
宋宇波
蒋雪梅
许嘉程
林泽慧
胡晓婷
祁鹤鹏
于飞
赵俊显
霍印虎
张亮
赵刚
王海川
齐颖
张淼
张君秋
李俊飞
王旭
徐伟伟
田冲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Didi Infinity Technology and Development Co Ltd
Original Assignee
Beijing Didi Infinity Technology and Development Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Didi Infinity Technology and Development Co Ltd filed Critical Beijing Didi Infinity Technology and Development Co Ltd
Priority to CN201910386332.0A priority Critical patent/CN110751532B/en
Publication of CN110751532A publication Critical patent/CN110751532A/en
Application granted granted Critical
Publication of CN110751532B publication Critical patent/CN110751532B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9535—Search customisation based on user profiles and personalisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0609—Buyer or seller confidence or verification
    • 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/55—Push-based network services

Landscapes

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

Abstract

The application provides a method and a device for resource allocation, which comprise the following steps: receiving first description information of service resources to be allocated, which is sent by a service provider, and receiving second description information of the requested service resources, which is sent by different service request terminals respectively; determining at least one piece of second description information matched with the first description information, and notifying resource detail interface information containing the at least one piece of second description information to a service provider; receiving target second description information selected by a service provider from the resource detail interface information, and sending a resource allocation request to a target service request end issuing the target second description information, wherein the resource allocation request is used for indicating the target service request end to confirm whether to accept service resources to be allocated or not; and determining a resource allocation result and notifying the service provider of the resource allocation result based on the resource allocation response sent by the target service request terminal. By the method, the utilization rate of the service resources can be improved.

Description

Resource allocation method and device
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for resource allocation.
Background
In some service scenarios, a service provider has certain service resources, a service requester needs to request required service resources, and how to correctly allocate the service resources that can be provided by the service provider to the service requester affects the utilization efficiency of the service resources.
For example, taking a network car booking scene as an example, the service providing terminal is a driver terminal, the service request terminal is a passenger terminal, the driver terminal has transportation capacity resources, the driver terminal can issue a trip route and request the passenger terminal matched with the trip route from the service platform, and then the driver terminal can select the passenger terminal from the passenger terminal information pushed by the service platform and provide the transportation capacity resources for the selected passenger terminal so as to meet the trip requirement of the passenger terminal. However, the allocation method of the capacity resources is determined only based on the matching degree of the travel route and the selection of the driver end, and is likely not to conform to the actual travel plan of the passenger end, which easily causes the problem of low utilization rate of service resources due to the fact that the passenger end cancels the capacity resources allocated this time and re-issues the resource allocation request.
Disclosure of Invention
In view of the above, an object of the present application is to provide a method and an apparatus for resource allocation to improve utilization of service resources.
In a first aspect, an embodiment of the present application provides a method for resource allocation, which is applied to a server, and includes:
receiving first description information of service resources to be allocated, which is sent by a service provider, and receiving second description information of the requested service resources, which is sent by different service request terminals respectively;
determining at least one piece of second description information matched with the first description information, and notifying resource detail interface information containing the at least one piece of second description information to the service provider;
receiving target second description information selected by the service provider from the resource detail interface information, and sending a resource allocation request to a target service request end issuing the target second description information, wherein the resource allocation request is used for indicating the target service request end to confirm whether to accept the service resource to be allocated;
and determining a resource allocation result and notifying the service provider of the resource allocation result based on the resource allocation response sent by the target service request terminal.
In a second aspect, an embodiment of the present application provides a method for resource allocation, which is applied to a service provider, and includes:
generating first description information of service resources to be allocated, and sending the first description information to a server;
receiving resource detail interface information sent by the server, wherein the resource detail interface information comprises at least one piece of second description information matched with the first description information, and each piece of second description information represents the description of a service request end issuing the second description information on a requested service resource;
selecting target second description information from the resource detail interface information, and informing the server to send a resource allocation request to a target service request end issuing the target second description information, wherein the resource allocation request is used for indicating the target service request end to confirm whether to accept the service resource to be allocated;
and receiving a resource allocation result sent by the server, wherein the resource allocation result is determined by the server based on the resource allocation response of the target service request terminal.
In a third aspect, an embodiment of the present application provides a method for resource allocation, which is applied to a service request end, and includes:
generating second description information of the requested service resource, and sending the second description information to a server;
receiving a resource allocation request sent by the server under the notification of a service provider, wherein the resource allocation request is used for indicating whether to accept the service resource to be allocated of the service provider; the first description information of the service resource to be distributed issued by the service provider is matched with the second description information;
and replying a resource allocation response to the server based on the resource allocation request.
In a fourth aspect, an embodiment of the present application provides an apparatus for resource allocation, including:
the system comprises a receiving module, a service providing terminal and a service request terminal, wherein the receiving module is used for receiving first description information of service resources to be distributed sent by the service providing terminal and receiving second description information of the requested service resources sent by different service request terminals;
the first processing module is used for determining at least one piece of second description information matched with the first description information and notifying the resource detail interface information containing the at least one piece of second description information to the service provider;
the receiving module is further used for receiving target second description information selected by the service provider from the resource detail interface information;
a sending module, configured to send a resource allocation request to a target service request end that issues the target second description information, where the resource allocation request is used to indicate the target service request end to determine whether to accept the service resource to be allocated;
and the second processing module is used for determining a resource allocation result and notifying the service provider of the resource allocation result based on the resource allocation response sent by the target service request terminal.
In a fifth aspect, an embodiment of the present application provides an apparatus for resource allocation, including:
the generation module is used for generating first description information of the service resources to be distributed;
the sending module is used for sending the first description information to a server;
a receiving module, configured to receive resource detail interface information sent by the server, where the resource detail interface information includes at least one piece of second description information matched with the first description information, and each piece of second description information represents a description of a service resource requested by a service request end issuing the second description information;
and the processing module is used for selecting the target second description information from the resource detail interface information.
The sending module is further configured to notify the server to send a resource allocation request to a target service request end that issues the target second description information, where the resource allocation request is used to indicate that the target service request end determines whether to accept the service resource to be allocated;
the receiving module is further configured to receive a resource allocation result sent by the server, where the resource allocation result is determined by the server based on the resource allocation response of the target service request end.
In a sixth aspect, an embodiment of the present application provides an apparatus for resource allocation, including:
a generating module, configured to generate second description information for the requested service resource;
the sending module is used for sending the second description information to a server;
a receiving module, configured to receive a resource allocation request sent by the server under a notification of a service provider, where the resource allocation request is used to indicate whether to accept a service resource to be allocated of the service provider; the first description information of the service resource to be distributed issued by the service provider is matched with the second description information;
and the replying module is also used for replying a resource allocation response to the server based on the resource allocation request.
In a seventh aspect, the present application provides an electronic device, comprising: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when an electronic device runs, the processor and the storage medium communicate with each other through the bus, and the processor executes the machine-readable instructions to perform the steps of the method for resource allocation according to the first aspect or any one of the possible implementation manners of the first aspect.
In an eighth aspect, the present application provides another electronic device, comprising: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device runs, the processor communicates with the storage medium through the bus, and the processor executes the machine-readable instructions to perform the steps of the method for resource allocation according to the second aspect or any one of the possible embodiments of the second aspect.
In a ninth aspect, the present application provides yet another electronic device, comprising: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device runs, the processor communicates with the storage medium through the bus, and the processor executes the machine-readable instructions to perform the steps of the method for resource allocation according to the third aspect or any one of the possible embodiments of the third aspect.
A tenth aspect is a computer-readable storage medium having a computer program stored thereon, where the computer program is executed by a processor to perform the steps of the method for resource allocation according to the first aspect, or any one of the possible embodiments of the first aspect; or, the computer program is executed by a processor to perform the steps of the method for resource allocation according to the second aspect or any one of the possible embodiments of the second aspect; alternatively, the computer program is executed by a processor to perform the steps of the method for resource allocation according to the third aspect or any one of the possible embodiments of the third aspect.
According to the resource allocation method provided by the application, the matched second description information is pushed to the service providing terminal, so that the service providing terminal can select the appropriate second description information from the second description information, after the service providing terminal selects the second description information, the service resource is not immediately allocated to the service request terminal corresponding to the selected second description information, but the resource allocation request is sent to the service request terminal, and therefore when the service resource is allocated, the service request terminal can participate in the selection, and whether the service resource is accepted or not is finally determined. By the method, the problem that the service request terminal requests the resources again due to unreasonable resource allocation can be effectively solved, and the utilization rate of the service resources is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic diagram illustrating an architecture of a service system provided in an embodiment of the present application;
fig. 2 is a flowchart illustrating a method for resource allocation provided by an embodiment of the present application;
fig. 3 is a schematic diagram illustrating a common location information display area in a resource allocation method according to an embodiment of the present application;
FIG. 4 is a schematic diagram illustrating a resource detail interface displayed by a service provider according to an embodiment of the present disclosure;
FIG. 5 is a schematic diagram illustrating a detail page interface corresponding to a selection box provided in an embodiment of the present application;
fig. 6 is a schematic diagram illustrating a resource allocation interface displayed by a service request end according to an embodiment of the present application;
FIG. 7 is a schematic diagram illustrating a resource allocation request interface provided by an embodiment of the present application;
fig. 8 is a flowchart illustrating another method for resource allocation according to an embodiment of the present application;
fig. 9 is a schematic diagram illustrating a display interface for a service provider to display a resource allocation result according to an embodiment of the present application;
fig. 10 is a schematic diagram illustrating a candidate set presentation interface presented by a service provider according to an embodiment of the present application;
fig. 11 is a schematic architecture diagram illustrating an apparatus for resource allocation according to an embodiment of the present application;
fig. 12 is a schematic architecture diagram of another apparatus for resource allocation provided in an embodiment of the present application;
fig. 13 is a schematic architecture diagram illustrating an apparatus for resource allocation according to an embodiment of the present application;
fig. 14 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;
fig. 15 is a schematic structural diagram of another electronic device provided in an embodiment of the present application;
fig. 16 shows a schematic structural diagram of another electronic device provided in an embodiment of the present application.
Detailed Description
In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for illustrative and descriptive purposes only and are not used to limit the scope of protection of the present application. Additionally, it should be understood that the schematic drawings are not necessarily drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be performed out of order, and steps without logical context may be performed in reverse order or simultaneously. One skilled in the art, under the guidance of this application, may add one or more other operations to, or remove one or more operations from, the flowchart.
In addition, the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
First, an application scenario to which the present application is applicable will be described. The method and the device can be applied to service scenes related to service resource allocation. The service resource may be understood as a resource corresponding to a certain service requested by the service request terminal. In an example, in a network car booking scenario, the service providing end is a driver end, and the service requesting end is a passenger end, so that the driver end capable of providing the riding service can be regarded as a service resource and also as a capacity resource. In another example, in an online meal delivery scenario, the service provider is a terminal used by a courier, and the service requester is a terminal used by a meal orderer, so that the courier capable of providing a meal delivery service may also be regarded as a service resource. Of course, the above examples are only examples, and in actual applications, the presentation forms of the service resources in different application scenarios are not necessarily the same, and the present application is not limited thereto.
Considering that, when service resources are allocated at present, one way is that the backend server directly allocates the matched service resources to the service request end, and the other way is that the backend server pushes information of the service request end to the matched service provider end, and the service provider end selects which service request end to provide service for, but the two ways are usually unaware to the side of the service request end, which easily causes that the service resources allocated to the service request end may not meet the service requirement, causes the service request end to initiate a cancellation procedure of the service resources, and re-initiates a resource allocation request.
Therefore, on one hand, when the service resources are allocated, the problem that the service resources cannot be accurately allocated to the corresponding service request end exists, which may result in a low utilization rate of the service resources, and on the other hand, when the service resources allocated to the service request end do not meet the service requirement, the allocation process of the service resources may be repeatedly initiated among the service providing end, the background server and the service request end, which may also waste the processing resources of the service providing end, the service request end and the background server, and the processing efficiency of the service resource allocation process is low.
In view of the above problems, the present application provides a method and an apparatus for resource allocation, in the method, in the process of allocating service resources, a background server matches a service request end and a service providing end corresponding to service resources to be allocated, and finally determines an allocation result of the service resources to be allocated by adopting a manner that the service providing end and the service request end perform bidirectional selection. By the method, the problem that the service request terminal repeatedly requests the service resources due to unreasonable resource allocation can be effectively solved, so that the utilization efficiency of the service resources is improved, the processing resources can be saved, and the processing efficiency of the service resource allocation process is improved.
Before introducing the specific technical solutions provided in the present application, a service system to which the present application is applicable will be described first. Referring to fig. 1, a schematic architecture diagram of a service system 100 according to an embodiment of the present disclosure is shown. For example, the service system 100 may be an online transportation service platform for transportation services such as taxi, designated driving service, express, carpool, bus service, driver rental, or regular service, or any combination thereof, and of course, the service system 100 may also be an online meal delivery service platform such as online meal ordering. The service system 100 may include one or more of a server 110, a network 120, a service requester terminal 130, a service provider terminal 140, and a database 150. In the application, the service requester terminal and the service requester terminal can be used interchangeably, and the service provider terminal can be used interchangeably.
In some embodiments, the server 110 may include a processor. The processor may process information and/or data related to the service request to perform one or more of the functions described herein. For example, the processor may match the service resources to be allocated of the service provider terminal 140 with the service requester terminal 130. Merely by way of example, a Processor may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction set Processor (ASIP), a Graphics Processing Unit (GPU), a Physical Processing Unit (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a microcontroller Unit, a Reduced Instruction Set Computer (RISC), a microprocessor, or the like, or any combination thereof.
In some embodiments, the device types corresponding to the service requester terminal 130 and the service provider terminal 140 may be mobile devices, such as smart mobile devices, smart home devices, wearable devices, virtual reality devices, augmented reality devices, and the like, and may also be tablet computers, laptop computers, built-in devices in motor vehicles, and the like.
In some embodiments, a database 150 may be connected to the network 120 to communicate with one or more components in the service system 100 (e.g., the server 110, the service requester terminal 130, the service provider terminal 140, etc.). One or more components in the service system 100 may access data or instructions stored in the database 150 via the network 120. In some embodiments, the database 150 may be directly connected to one or more components in the service system 100, or the database 150 may be part of the server 110.
The method for allocating resources provided by the present application is described in detail below with reference to the content described in the service system 100 shown in fig. 1.
Referring to fig. 2, a schematic flow chart of a method for resource allocation provided in the embodiment of the present application is shown, including the following steps:
step 201, the service provider generates first description information of the service resource to be allocated, and sends the first description information to the server.
The first description information is used for describing service resources to be allocated. In one example, if the service resource represents a capacity resource in a network appointment service scenario, the first description information for describing the service resource may include at least one of the following a1 to a 4:
a1, service provider's travel route information.
Illustratively, the trip route information includes a trip start position and a trip end position. The trip route information may include a trip center point position in addition to the trip start position and the trip end position, so that the trip route may be generated based on the three positions. Alternatively, a route may be generated based on the travel start position and the travel end position, and the intermediate point position of the route may be arbitrarily selected on the route.
In one possible implementation, the service provider may input the common location information to the service provider in advance, and when the service provider inputs the route information, the service provider may directly select the route start position and the route end position from the common location information. In order to facilitate management of the common location information, the service provider may be allowed to input a preset number of common location information, and the service provider may be allowed to periodically update the input common location information.
In an example, referring to a common location information display area a shown in fig. 3, the common location information display area may be displayed in a release travel interface of a service provider after being triggered, where the common location information display area a includes, but is not limited to: a prompt information field a1, an add place option a2, and a manage place option a 3. Under the condition that the common place information is not added, the prompt information area a1 shows prompt information of 'the common place information can be issued after the common place information is added', and under the condition that the common place information is added, the prompt information area a1 can show the common place information input by the service provider; after the adding place option a2 is triggered, a common place information input interface can be entered, so that the common place information can be input in a map point selection mode, and the common place information can also be manually input; after the management place option a3 is triggered, a common place information management interface may be entered, in which a service provider may be supported to modify, delete or add common place information, etc.
A2, travel time of service provider.
For example, in a network appointment scene, the travel time may include a trip departure time, and of course, may also include a trip end time. The journey end time can be estimated based on the journey route information and the journey departure time, and the estimated journey end time can be directly input by the service provider. The trip start time and the trip end time may be time points or time periods, and the time period may be set within a reasonable range. For example, assuming that the service provider plans to go at 7 am, the time of "7: 00" may be entered in the service provider, and of course, a time period range of "7: 00 to 7: 10" may be entered.
A3, itinerary participant information of the service provider.
For example, in a network appointment scenario, the information of the trip participants may be information of persons in the same line as the service provider, specifically including the number of persons in the same line as the service provider, and may further include description information of the persons in the same line, such as the sex, age, relationship with the service provider, and the like of the persons in the same line.
A4, number of service requesters able to provide the service.
For example, in a network appointment scenario, since the number of passengers capable of being carried in a vehicle is limited, the number of passengers capable of being carried in may be input by a service provider (i.e., a driver) when generating the first description information of the resource to be allocated.
Of course, in practical applications, the first description information generated by the service provider may also be different with the replacement of the service scenario, and the above information is only used as an example in the present application and may be adjusted according to the actual service scenario.
Step 202, the service request end generates second description information of the requested service resource and sends the second description information to the server.
The second description information is used for describing the service resource requested by the service request end. For example, in a network car appointment scenario, the second description information may be used to describe riding demand information of a service requester (i.e., a passenger), including a description of required transportation resources, and the like. The above second description information may include at least one of the following B1 to B5:
b1, service requester's travel route information.
Illustratively, the trip route information includes a trip start position and a trip end position. In addition, the travel route information may further include a position of a middle point of the travel, so that the travel route may be generated based on the three positions. Alternatively, a route may be generated based on the travel start position and the travel end position, and the intermediate point position of the route may be arbitrarily selected on the route. In some application scenarios, the service request end may also select a trip start position and a trip end position from the common location information. The service request end may also display the common location information display area a shown in fig. 3, which is not described herein.
B2, travel time of the service requester.
For example, in a network appointment scene, the travel time may include a trip departure time, and of course, may also include a trip end time. The journey end time may be estimated based on the journey route information and the journey departure time, or the estimated journey end time may be directly input by the service provider. The trip start time and the trip end time may be time points or time periods, and the time period may be set within a reasonable range. For example, assuming that the service requester plans to go at 8 am, the time of "8: 00" may be input in the service requester, and of course, a time period range of "8: 00 to 8: 10" may be input.
B3, itinerary participant information of the service requester.
For example, in a car appointment scenario, the information of the trip participants may be information of persons who are in the same line as the service requester, specifically including the number of persons in the same line as the service requester, and may further include description information of the persons in the same line, such as the sex, age, relationship with the service requester, and the like of the persons in the same line.
And B4, car pooling selection information.
In order to maximize the utilization of service resources in the online car appointment scene, the service request end can display a car pooling selection information input interface so that the service request party can input car pooling selection information, and the car pooling selection information comprises options of whether the service request end is willing to share cars, the number of journey participants and the like.
B5, service charge information.
The service charge information may be determined based on the trip route information input by the service requester and the carpool selection information. In one possible implementation manner, the service request end may upload the travel route information and the car pool selection information input by the service request party to the server, and the server calculates the service charge information based on the received travel route information and car pool selection information and pushes the service charge information to the service request end.
In addition, a special requirement interface can be displayed on the service request side, and in the special requirement interface, the service requester can input some travel requirement information, for example, information such as providing a child seat and the like. Of course, the second description information is only used as an example, and in practical applications, the second description information may be adjusted according to a change of a service scenario, which is not limited in the present application.
Step 203, after receiving the first description information of the service resource to be allocated sent by the service provider and receiving the second description information of the requested service resource sent by different service requesters, the server determines at least one piece of second description information matched with the first description information and notifies the service provider of the resource detail interface information containing at least one piece of second description information.
In the embodiment of the application, the server may match the service resources to be allocated of the service provider with the service resource requirements of the service request terminal, and specifically may match the first description information of the service provider with the second description information of different service request terminals, so as to determine the second description information matched with the first description information.
In a specific implementation, since the first description information and the second description information may include a plurality of kinds of description information, matching may be performed for each kind of description information. The matching process that may be implemented includes at least one of C1 to C3:
c1, matching of the travel route information.
In a possible implementation manner, a travel route corresponding to the service provider is generated for a travel start position and a travel end position uploaded by the service provider, and a travel route corresponding to each service request is generated for a travel start position and a travel end position uploaded by each service request. Further, if the travel route information further includes the intermediate point position, the travel route may be generated based on the travel start position, the travel end position, and the intermediate point position when the travel route is generated. After generating the travel routes respectively, a matching degree between the travel route corresponding to the service provider and the travel route corresponding to each service requester may be determined. The calculation of the specific matching degree may use a similarity calculation algorithm, which is not limited in this application.
C2, matching travel time.
In one possible implementation, if the travel time includes the travel departure time, the travel departure time corresponding to the service request end and the travel departure time corresponding to the service providing end may be directly matched, and the matching degree of the travel departure time may be calculated. Wherein, the closer the travel departure time between the two is, the higher the matching degree between the two is. If the travel time includes the travel end time, the travel end time corresponding to the service request end and the travel end time corresponding to the service providing end may be matched, and the matching degree of the travel end time may be calculated. Wherein, the closer the travel end time between the two is, the higher the matching degree between the two is. If the travel starting time and the travel ending time are included at the same time, the matching degree of the travel starting time and the matching degree of the travel ending time may be subjected to weighted summation to obtain the final matching degree of the travel time.
C3, matching the trip participant information.
The server can determine the number of the personnel capable of providing the service resources by the service provider based on the travel participant information provided by the service provider, the travel participant information provided by the service request reflects the number of the personnel requesting the service resources, and the matching degree of the travel participant information can be determined by matching the number of the personnel capable of providing the service resources with the number of the personnel requesting the service resources. For example, if the number of people requesting service resources exceeds the number of people providing service resources, in this case, the matching degree may be 0 if the information of the trip participants is not matched, and conversely, if the number of people requesting service resources does not exceed the number of people providing service resources, the information of the trip participants may be matched, and the matching degree may be 1.
In a specific implementation, after each kind of description information is respectively matched to obtain a corresponding matching degree, the obtained matching degrees may be subjected to weighted summation to determine the matching degree between the first description information and the second description. The weight corresponding to each kind of description information may be set based on the importance degree of each kind of description information in a specific service scenario.
For example, in a network car appointment scene, if the description information includes the trip participant information, if the trip participant information does not match, it may be directly determined that the first description information does not match the second description information, that is, the matching degree is 0. If the trip participant information is matched, the matching degree of the first description information and the second description information can be determined based on the matching degree and the weight of the trip route information and the matching degree and the weight of the trip time.
After determining the matching degree between the first description information and each piece of second description information, the second description information with the matching degree satisfying the set matching condition may be selected as the second description information matched with the first description information. The set matching condition is, for example, that the matching degree is greater than a set matching degree threshold, or the matching degree is arranged in the first N bits, where N is a positive integer.
Further, the server can generate resource detail interface information and push the service provider.
Specifically, the resource detail interface information may include at least one of the following D1 to D4:
d1, each second description information matching the first description information.
The resource detail interface information may show all the second description information sent by the service request end, or may show part of the second description information. Illustratively, the second description information displayed includes, for example, one or more of travel route information (travel starting position, travel ending position), travel time (travel starting time, travel ending time), service fee information, car sharing selection information (car sharing willing or unwilling), and the like.
D2, the matching degree of the first description information and each second description information.
The matching degree of the first description information and each of the second description information may be the matching degree of each specific description information, or the matching degree obtained by weighting and summing the matching degrees of various description information. In an example, if the specific description information is the travel route information, the matching degree between the first description information and the second description information may be expressed as the matching degree of the travel route information, that is, the degree of the way between the service provider and the service requester.
D3, and the evaluation information of the service request end corresponding to each piece of second description information.
In order to facilitate the service provider to screen the service requesters willing to provide the service, the evaluation information of the service requester corresponding to the second description information may be further displayed in the resource detail interface. The evaluation information includes, for example, a trust level of the service requester, and the trust level may be determined according to, for example, operation behavior information of a historical service order of the service requester, or may be determined according to an evaluation score given by the service provider.
D4, the number of resource allocation requests received by the service request end corresponding to each second description information.
For example, in a car appointment scenario, a service provider may select a service requester who wants to provide a service, and then a server may send a resource allocation request to the service requester selected by the service provider, where the resource allocation request may be understood as an invitation request, where the service provider invites the service requester to receive a corresponding service resource.
Since any one of the first description information and any one of the second description information can be matched, a situation that the first description information of different service providers is matched with the second description information of the same service request terminal may occur, and correspondingly, the second description information of the same service request terminal may be simultaneously included in resource detail interface information pushed by the server to different service providers, so that different service providers are allowed to select the same service request terminal, that is, different service providers are allowed to invite the same service request terminal to receive corresponding service resources. Of course, in some specific application scenarios, the same service requester is only allowed to accept service resources of one service provider. The service provider can timely acquire a relatively comprehensive resource allocation condition by informing the service provider of the number of the resource allocation requests received by the service request terminal.
Receiving the step 203, further executing:
and step 204, the service provider selects the target second description information from the resource detail interface information, and notifies the server to send a resource allocation request to the target service request end issuing the target second description information, wherein the resource allocation request is used for indicating the target service request end to confirm whether to accept the service resource to be allocated.
In specific implementation, after receiving the resource detail interface information, the service provider may generate and display a resource detail interface based on the resource detail interface information. The resource detail interface displays selection boxes corresponding to second description information matched with the first description information, and each selection box corresponding to the second description information can display contents of D1 to D4 in the resource detail interface information corresponding to the second description information, including the second description information, matching degree of the second description information and the first description information, evaluation information of a corresponding service request end, and number of resource allocation requests received by the corresponding service request end.
And a selection box corresponding to each piece of second description information displayed in the resource detail interface can be selected by the service provider. If the selection box corresponding to the target second description information in the resource detail interface is selected, the service provider may detect that the option corresponding to the target second description information in the resource detail interface is triggered, and further may display a detail page of the target second description information.
Wherein, the contents of D1 to D4 in the above-mentioned resource detail interface information corresponding to the target second description information can be shown in the detail page of the target second description information. And, a resource allocation request option is also included in the detail page of the target second description information. If the service provider selects the resource allocation request option, the service provider may notify the server to send the resource allocation request to the target service request end that issues the target second description information after detecting that the resource allocation request option in the detail page of the target second description information is triggered.
For example, in a network appointment scenario, a resource detail interface displayed by the service provider is shown in fig. 4, for example, the resource detail interface b includes selection boxes corresponding to a plurality of pieces of second description information, and for example, if there are two pieces of second description information matching the first description information, the resource detail interface may include selection boxes b1 and b 2. Taking the selection box b1 as an example, the information includes, but is not limited to, travel time (e.g. 12 months, 31 days, 8:30-9:45), travel route information (e.g. travel start position is L1, and travel end position is L2), service cost information (e.g. 28 yuan), car sharing selection information (willing to share cars), matching degree with the first description information (i.e. 95%), evaluation information of the service request end (trust degree 90 points), and the number of received resource allocation requests (e.g. 3 requests from the driver end have been received). The arrangement order of the selection frames in the resource detail interface may be determined based on the matching degree with the first description information, for example, although other arrangement strategies may also be adopted, which is not limited in this application.
Further, if the service provider selects a certain selection box from the displayed resource detail interface b, then the display interface of the service provider may display a detail page c corresponding to the selected selection box, for example, as shown in fig. 5, the detail page c may include a selection box information display area c1, for example, including part or all of the content displayed in the selection box b1, a map display area c2, on which a pickup navigation route to the location of the service requester may be marked, and a resource allocation request option c3, for example, an option of "invite to the same row" may be displayed. After detecting that the resource allocation request option c3 is triggered, the server may be notified to send a resource allocation request to the target service request end corresponding to the presented selection box.
Further, after the resource allocation request option c3 in the detail page c is triggered, the resource allocation status interface d may be displayed in the display interface of the service provider, for example, as shown in fig. 6, a resource allocation status prompt region d1 (for example, "waiting for confirmation of the service requester") may be included in the resource allocation status interface d, and a checkbox information display region d2 may also be included in the resource allocation status interface d, where the checkbox information display region d2 may include part or all of the content displayed in the checkbox.
Step 205, the server sends a resource allocation request to the target service request end issuing the target second description information.
In this embodiment of the present application, the resource allocation request sent by the server to the target service request end may include at least one of the following E1 to E4:
e1, some or all of the first description information.
For example, the first description information that can be presented includes one or more of travel route information (travel starting position, travel ending position), travel time (travel departure time, travel ending time), travel participants, and the like of the service provider.
E2, evaluation information of the service provider.
For example, the evaluation information of the service provider may be determined according to the operation behavior information of the historical service order executed by the service provider and the evaluation information input by the service requester. For example, the information includes the trust value of the service provider, the number of trips of the service provider for the current trip route, and the evaluation content of the service process (whether the vehicle is tidy, on time, whether the vehicle is driving smoothly, etc.).
E3, estimated service providing time of the service providing terminal.
The estimated service providing time can be determined based on the travel time and the travel route information reported by the service providing terminal and the travel time and the travel route information reported by the service requesting terminal.
E4, service cost information.
The service fee information is the fee to be paid for the service requested by the service requesting terminal. Illustratively, in a network car booking scenario, the service charge information is influenced by travel route information, travel time, whether car pooling is required, and the like.
Receiving the step 205, further performing:
and step 206, the target service request end replies a resource allocation response to the server based on the resource allocation request.
In this embodiment of the application, after the target service request end receives the resource allocation request, a resource allocation request interface may be generated based on at least one type of information carried in the resource allocation request, and a plurality of to-be-processed sub-interfaces are displayed in the resource allocation request interface, where each to-be-processed sub-interface displays at least one type of information, E1 to E4, carried in the resource allocation request corresponding to one service provider. And each pending sub-interface comprises an acceptance option and a rejection option. The accepting option refers to accepting the service resource to be allocated of the service provider and paying corresponding service cost, and the rejecting option refers to rejecting the service resource to be allocated of the service provider.
And if detecting that an acceptance option for accepting the service resources to be allocated in each sub-interface to be processed is triggered or a rejection option for rejecting the service resources to be allocated is triggered, replying a resource allocation response to the server. The resource allocation response is used for indicating the acceptance of the resource to be allocated or the rejection of the resource to be allocated.
For example, in a car appointment scenario, a resource allocation request interface displayed by a service request end is, for example, as shown in fig. 7, where the resource allocation request interface e includes a plurality of to-be-processed sub-interfaces, and for example, if the service request end receives resource allocation requests triggered by 2 service providers, the resource allocation request interface e may include a to-be-processed sub-interface e1 and a to-be-processed sub-interface e 2. Take the pending sub-interface e1 as an example, including but not limited to, pre-estimated service providing time (e.g., "today 9:30 you get"), service fee information (e.g., 28 yuan), car sharing situation (e.g., "two passengers are willing to share car), evaluation information of the service provider (e.g., including 90 minutes of trust, 10 trips of the current trip route, etc.), and the like. The arrangement order of the sub-interfaces to be processed in the resource detail interface may be determined based on the time of receiving the resource allocation request, for example, and other arrangement strategies may also be adopted, which is not limited in this application. Besides, the pending sub-interface e1 includes, in addition to the related information of the resource allocation request, an accept option e11 and a reject option e 12. Here, the acceptance option e11 is represented by "confirm with the same line and pay", and the rejection option e12 is represented by "reject", for example.
Further, if the service request end detects that the receiving option e11 is triggered, a service fee payment interface may be displayed in the display interface of the service request end, and the service request end is prompted to pay the corresponding service fee. If the service requester detects that the reject option e12 is triggered, a prompt box may be displayed in the display interface of the service provider, for example. The prompt content in the prompt box is, for example, "reject this owner and need to wait for the invitation of other owners again to be able to go together" or the like, and two options can also be provided in the prompt box, one is an option of "i want to" and the other is an option of "reject owner". After the option of 'i think about me' is triggered, the last showing interface can be returned, and after the option of 'rejecting the owner' is triggered, the invitation of other owners needs to be continuously waited.
Step 207, the server determines a resource allocation result based on the resource allocation response sent by the target service request end, and notifies the service provider of the resource allocation result.
If the resource allocation response indicates that the target service request end confirms to receive the service resources to be allocated, the resource allocation result is successful allocation; and if the resource allocation response indicates that the target service request terminal confirms to reject the service resources to be allocated, the resource allocation result is allocation failure.
In some embodiments of the present application, the service resource to be allocated may be shared by multiple service requesters, for example, in a network car appointment scenario, a same service provider (e.g., a driver) may provide a riding service for multiple server requesters (e.g., passengers), which is also referred to as a car pooling service, and then in the car pooling service, the service requesters may select whether to allow sharing of the same service resource, that is, whether to allow sharing of capacity resource of the same service provider. Specifically, the information indicating whether the service request terminal selects to allow sharing of the same service resource may be carried in the second description information. In one example, the sharing of the same service resource may be indicated by the car sharing selection information, for example, if the sharing is willing, the sharing of the same service resource is allowed, and if the sharing is not willing, the sharing of the same service resource is not allowed.
In view of the fact that the utilization rate of the service resources can be further improved when the service resources to be allocated are shared, in the process of resource allocation, a processing procedure of whether the service resources can be shared may be further added, and as shown in fig. 8, a flow diagram of another resource allocation method provided in the embodiment of the present application is shown, and the method includes the following steps:
step 801, a service provider generates first description information of a service resource to be allocated, and sends the first description information to a server.
Step 802, the service request end generates second description information of the requested service resource, and sends the second description information to the server.
Step 803, the server determines at least one piece of second description information matched with the first description information, and notifies the resource detail interface information containing the at least one piece of second description information to the service provider.
Step 804, the service provider selects the target second description information from the resource detail interface information, and notifies the server to send a resource allocation request to the target service request end issuing the target second description information, where the resource allocation request is used to indicate the target service request end to determine whether to accept the service resource to be allocated.
The specific processing procedure of steps 801 to 804 may refer to the related description of steps 201 to 204 in fig. 2.
Step 805, after receiving the target second description information selected by the service provider from the resource detail interface information, if it is detected that the target second description information indicates that the same service resource is allowed to be shared, the server prompts the service provider to allow other service requesters to continue to request to share the service resource to be allocated after the target service requester confirms to receive the service resource to be allocated.
For example, in a car booking scenario, the prompt message from the server may be displayed in a detail page as shown in fig. 5, and a prompt message "car pooling may be started after confirmation of the current passenger" may be displayed in the detail page.
Step 806, the server sends a resource allocation request to the target service request terminal issuing the target second description information.
In a possible implementation manner, after sending the resource allocation request to the target service request terminal that issues the target second description information, if it is detected that the target service request terminal does not reply the resource allocation response within a preset time period, or it is detected that the target service request terminal has confirmed to accept service resources to be allocated of other service providing terminals, the server updates the second description information except the target second description information in the resource detail interface information to a failure state.
After the second description information is updated to the failure state, the service provider does not have the right to continue to select the second description information of the failure state.
Step 807, the target service request end replies a resource allocation response to the server based on the resource allocation request.
Step 808, the server determines a resource allocation result based on the resource allocation response sent by the target service request terminal.
If the resource allocation response indicates that the target service request end confirms to receive the service resources to be allocated, the resource allocation result is successful allocation; and if the resource allocation response indicates that the target service request terminal confirms to reject the service resources to be allocated, the resource allocation result is allocation failure.
In the embodiment of the application, the executed processing flows are different when the resource allocation result is allocation success or allocation failure, and different processing flows can be executed based on whether the target service request end with successful allocation is willing to share the selection information of the service resource or not when the resource allocation result is allocation success.
Wherein, in case that the resource allocation result is allocation failure, the server executes step 809:
step 809, the server sends the resource allocation result of the allocation failure to the service provider, and prompts the service provider whether to continue to select other service request terminals.
Here, in the case that the resource allocation result is that allocation fails, the server may instruct the service provider to continue to jump to the resource detail interface, and prompt the service provider whether to continue to select other target second description information in the resource detail interface, so as to prompt the service provider whether to continue to select other service request providers. If it is detected that the service provider continues to select another service provider, the process may return to step 805 to continue to execute the subsequent processing flow.
Wherein, under the condition that the resource allocation result is that the allocation is successful, two processing flows can be executed between the server and the service providing terminal: first, in the case that the target service provider is willing to share the same service resource, the processing flow executed includes steps 810 to 813; second, in case the target service provider does not want to share the same service resource, the process flow executed includes step 814.
Step 810, if the server detects that the target second description information indicates that the same service resource is allowed to be shared, the server sends the resource allocation result to the service provider and simultaneously prompts the service provider whether to continue requesting other service request terminals to share the service resource to be allocated.
Step 811, the service provider receives the resource allocation result sent by the server for indicating successful allocation, and detects that an option for continuously requesting other service requesters to share the service resource to be allocated is triggered in the display interface of the resource allocation result.
In some embodiments of the present application, after the service provider receives the resource allocation result, a presentation interface of the resource allocation result may be presented. For example, referring to the resource allocation result display interface f shown in fig. 9, the resource allocation result information display area f1 is included, for example, in a car-booking scenario, when resource allocation is successful, the resource allocation result displayed in f1 is, for example, "peer success", and in addition, related prompt information may be displayed, for example, to prompt a service requester to arrive at a booked location at a booked time. The display interface f further comprises a list-sharing selection area f2, an option for continuously requesting the shared service resources of other service requesters, namely an option for continuously sharing the list, can be included in the list-sharing selection area f2, and after detecting that the option for continuously sharing the list is triggered, a request for continuously sharing the list can be sent to the server. In addition, the display interface f further includes a schedule information display area f3, and the schedule information display area f3 displays relevant information of the service request end that has currently received the service resource to be allocated, such as the second description information of the service request end, which is not limited in this application.
Step 812, after detecting that the service provider selects to continue to request other service requesters to share the service resource to be allocated, the server sends a candidate set of second description information to the service provider, where the second description information included in the candidate set indicates that the same service resource is allowed to be shared.
Step 813, the service provider receives the candidate set of the second description information sent by the server, and continues to select the target second description information from the candidate set.
For example, after receiving the candidate set of the second description information, the service provider may present a candidate set presentation interface g on the service provider, for example, as shown in fig. 10, a plurality of presentation areas of the second description information may be included in the candidate set presentation interface g, for example, if 2 pieces of the second description information are included in the candidate set, a presentation area g1 of the second description information, a presentation area g2 of the second description information, and the like may be presented in the candidate set presentation interface g. Of course, other information matching with the service scenario may also be presented, which is not limited in the present application.
Subsequently, after detecting that the service provider continues to select the target second description information from the candidate set, the server may send a resource allocation request to the service request provider corresponding to the selected target second description information, determine a resource allocation result based on a resource allocation response replied by the service request provider, and notify the service provider of the resource allocation result, which is not illustrated, and refer to the contents in the foregoing embodiment.
Step 814, if the server detects that the target second description information indicates that the same service resource is not allowed to be shared, the server sends the resource allocation result to the service providing end, and updates the second description information except the target second description information in the resource detail interface information to a failure state.
After the second description information is updated to the failure state, the service provider does not have the right to continue to select the second description information of the failure state.
In the foregoing embodiment of the present application, in the process of allocating the service resources, the background server matches the service request end and the service provider end corresponding to the service resources to be allocated, and finally determines the allocation result of the service resources to be allocated by using a manner that the service provider end and the service request end perform bidirectional selection. By the method, the problem that the service request terminal repeatedly requests the service resources due to unreasonable resource allocation can be effectively solved, so that the utilization efficiency of the service resources is improved, the processing resources can be saved, and the processing efficiency of the service resource allocation process is improved.
Based on the same technical concept, an embodiment of the present application further provides a resource allocation apparatus, and referring to fig. 11, an architecture diagram of the resource allocation apparatus provided by the present application is shown, including: the receiving module 1101, the first processing module 1102, the sending module 1103, and the second processing module 1104 specifically:
a receiving module 1101, configured to receive first description information of service resources to be allocated sent by a service provider, and receive second description information of requested service resources sent by different service requesters, respectively;
a first processing module 1102, configured to determine at least one piece of second description information that matches the first description information, and notify the service provider of resource detail interface information that includes the at least one piece of second description information;
a receiving module 1101, configured to receive target second description information selected by the service provider from the resource detail interface information;
a sending module 1103, configured to send a resource allocation request to a target service request end that issues the target second description information, where the resource allocation request is used to indicate that the target service request end determines whether to accept the service resource to be allocated;
a second processing module 1104, configured to determine a resource allocation result based on the resource allocation response sent by the target service request end, and notify the service provider of the resource allocation result.
In some embodiments of the present application, the apparatus further comprises:
a prompting module 1105, configured to, after the receiving module 1101 receives the target second description information selected by the service provider from the resource detail interface information, if it is detected that the target second description information indicates that the same service resource is allowed to be shared, prompt the service provider to allow other service requesters to continue to request to share the service resource to be allocated after the target service requester confirms to receive the service resource to be allocated.
In some embodiments of the present application, when determining a resource allocation result and notifying the service provider of the resource allocation result based on the resource allocation response sent by the target service request end, the second processing module 1104 is specifically configured to:
and if the resource allocation response indicates that the target service request end confirms to accept the service resources to be allocated, determining that the resource allocation result is successful in allocation.
If the target second description information indicates that the same service resource is allowed to be shared, sending the resource allocation result to the service provider and prompting the service provider whether to continuously request other service request terminals to share the service resource to be allocated;
and if the target second description information indicates that the same service resource is not allowed to be shared, sending the resource allocation result to the service provider, and updating second description information except the target second description information in the resource detail interface information to be in a failure state.
In some embodiments of the present application, after prompting whether the service provider continuously requests other service requesters to share the service resource to be allocated, the second processing module 1104 is further configured to:
and when the service provider is detected to select to continuously request other service request terminals to share the service resources to be allocated, sending a candidate set of second description information to the service provider, wherein the second description information contained in the candidate set indicates that the same service resources are allowed to be shared.
In some embodiments of the present application, the first processing module 1102 is further configured to:
after the sending module 1103 sends a resource allocation request to a target service request end that issues the target second description information, if the first processing module 1102 detects that the target service request end does not reply the resource allocation response within a preset time period, or detects that the target service request end has confirmed to accept service resources to be allocated of other service providing ends, the second description information except the target second description information in the resource detail interface information is updated to a failure state.
In some embodiments of the present application, the resource detail interface information further includes at least one of the following information: the matching degree of the first description information and each second description information, the evaluation information of the service request end corresponding to each second description information, and the quantity of the resource allocation requests received by the service request end corresponding to each second description information.
In some embodiments of the present application, the resource allocation request includes at least one of the following information: part or all of the information in the first description information, the evaluation information of the service provider and the estimated service providing time of the service provider.
In some embodiments of the present application, the first description information includes at least one of the following information: the travel route information of the service provider, the travel time of the service provider and the travel participant information of the service provider;
the second description information includes at least one of the following information: the system comprises travel route information of a service requester, travel time of the service requester, travel participant information of the service requester, car sharing selection information and service cost information.
Based on the same technical concept, an embodiment of the present application further provides another resource allocation apparatus, and referring to fig. 12, an architecture diagram of the resource allocation apparatus provided in the embodiment of the present application is shown, and the apparatus includes: the generating module 1201, the sending module 1202, the receiving module 1203, and the processing module 1204 specifically:
a generating module 1201, configured to generate first description information of a service resource to be allocated;
a sending module 1202, configured to send the first description information to a server;
a receiving module 1203, configured to receive resource detail interface information sent by the server, where the resource detail interface information includes at least one piece of second description information matched with the first description information, and each piece of second description information represents a description of a service resource requested by a service request end issuing the second description information;
and a processing module 1204, configured to select target second description information from the resource detail interface information.
The sending module 1202 is further configured to notify the server to send a resource allocation request to a target service request end that issues the target second description information, where the resource allocation request is used to indicate that the target service request end determines whether to accept the service resource to be allocated;
the receiving module 1203 is further configured to receive a resource allocation result sent by the server, where the resource allocation result is determined by the server based on the resource allocation response of the target service request end.
In some embodiments of the present application, when the processing module 1204 selects the target second description information from the resource detail interface information, it is specifically configured to:
generating and displaying a resource detail interface based on the resource detail interface information;
and if the fact that the option corresponding to the target second description information in the resource detail interface is triggered is detected, determining that the target second description information is selected.
In some embodiments of the present application, after selecting the target second description information from the resource detail interface information, the processing module 1204 is further configured to:
a detail page showing the target second description information;
the sending module 1202, when notifying the server to send the resource allocation request to the target service request terminal that issues the target second description information, is specifically configured to:
and after detecting that the resource allocation request option is triggered in the detail page of the target second description information, informing the server to send a resource allocation request to a target service request end which issues the target second description information.
In some embodiments of the present application, the receiving module 1203, when receiving the resource allocation result sent by the server, is specifically configured to:
receiving the resource allocation result sent by the server and used for indicating successful allocation;
if an option for continuously requesting other service request terminals to share the service resources to be allocated in a display interface of the resource allocation result is triggered, receiving a candidate set of second description information sent by the server, wherein the second description information contained in the candidate set indicates that the same service resources are allowed to be shared;
the processing module 1204 is further configured to:
continuing to select target second description information from the candidate set.
In some embodiments of the present application, the first description information includes at least one of the following information: the travel route information of the service provider, the travel time of the service provider and the travel participant information of the service provider;
the second description information includes at least one of the following information: the system comprises travel route information of a service requester, travel time of the service requester, travel participant information of the service requester, car sharing selection information and service cost information.
In some embodiments of the present application, the resource detail interface information further includes at least one of the following information: the matching degree of the first description information and each second description information, the evaluation information of the service request end corresponding to each second description information, and the quantity of the resource allocation requests received by the service request end corresponding to each second description information.
Based on the same technical concept, an embodiment of the present application further provides another resource allocation apparatus, and referring to fig. 13, an architecture diagram of the resource allocation apparatus provided in the embodiment of the present application is shown, including: the generating module 1301, the sending module 1302, the receiving module 1303, and the replying module 1304 specifically:
a generating module 1301, configured to generate second description information for the requested service resource;
a sending module 1302, configured to send the second description information to a server;
a receiving module 1303, configured to receive a resource allocation request sent by the server under a notification of a service provider, where the resource allocation request is used to indicate whether to accept a service resource to be allocated of the service provider; the first description information of the service resource to be distributed issued by the service provider is matched with the second description information;
a replying module 1304, configured to reply a resource allocation response to the server based on the resource allocation request.
In some embodiments of the present application, when the reply module 1304 replies a resource allocation response to the server based on the resource allocation request, it is specifically configured to:
generating and displaying a resource allocation request interface based on at least one type of information carried in the resource allocation request; the resource allocation request interface comprises a plurality of to-be-processed sub-interfaces, and each to-be-processed sub-interface comprises at least one information in a resource allocation request corresponding to one service provider;
and if detecting that an acceptance option for accepting the service resources to be distributed in each sub-interface to be processed is triggered or a rejection option for rejecting the service resources to be distributed is triggered, replying the resource distribution response to the server.
In some embodiments of the present application, the first description information includes at least one of the following information: the travel route information of the service provider, the travel time of the service provider and the travel participant information of the service provider;
the second description information includes at least one of the following information: the system comprises travel route information of a service requester, travel time of the service requester, travel participant information of the service requester, car sharing selection information and service cost information.
In some embodiments of the present application, the resource allocation request includes at least one of the following information: part or all of the information in the first description information, the evaluation information of the service provider and the estimated service providing time of the service provider.
Based on the same technical concept, the embodiment of the application also provides the electronic equipment. Referring to fig. 14, a schematic structural diagram of an electronic device 1400 provided in the embodiment of the present application includes a processor 1401, a memory 1402, and a bus 1403. The storage 1402 is used for storing execution instructions, and includes a memory 14021 and an external storage 14022; the memory 14021 is also referred to as an internal memory, and is used for temporarily storing the operation data in the processor 1401 and the data exchanged with the external memory 14022 such as a hard disk, the processor 1401 exchanges data with the external memory 14022 through the memory 14021, and when the electronic device 1400 is operated, the processor 1401 and the memory 1402 communicate with each other through the bus 1403, so that the processor 1401 executes the following instructions:
receiving first description information of service resources to be allocated, which is sent by a service provider, and receiving second description information of the requested service resources, which is sent by different service request terminals respectively;
determining at least one piece of second description information matched with the first description information, and notifying resource detail interface information containing the at least one piece of second description information to the service provider;
receiving target second description information selected by the service provider from the resource detail interface information, and sending a resource allocation request to a target service request end issuing the target second description information, wherein the resource allocation request is used for indicating the target service request end to confirm whether to accept the service resource to be allocated;
and determining a resource allocation result and notifying the service provider of the resource allocation result based on the resource allocation response sent by the target service request terminal.
Based on the same technical concept, the embodiment of the application also provides the electronic equipment. Referring to fig. 15, a schematic structural diagram of an electronic device 1500 provided in the embodiment of the present application includes a processor 1501, a memory 1502, and a bus 1503. The storage 1502 is used for storing execution instructions and includes a memory 15021 and an external storage 15022; here, the memory 15021 is also referred to as an internal memory, and is used for temporarily storing the operation data in the processor 1501 and the data exchanged with the external memory 15022 such as a hard disk, the processor 1501 exchanges data with the external memory 15022 through the memory 15021, and when the electronic device 1500 is operated, the processor 1501 communicates with the memory 1502 through the bus 1503, so that the processor 1501 executes the following instructions:
generating first description information of service resources to be allocated, and sending the first description information to a server;
receiving resource detail interface information sent by the server, wherein the resource detail interface information comprises at least one piece of second description information matched with the first description information, and each piece of second description information represents the description of a service request end issuing the second description information on a requested service resource;
selecting target second description information from the resource detail interface information, and informing the server to send a resource allocation request to a target service request end issuing the target second description information, wherein the resource allocation request is used for indicating the target service request end to confirm whether to accept the service resource to be allocated;
and receiving a resource allocation result sent by the server, wherein the resource allocation result is determined by the server based on the resource allocation response of the target service request terminal.
Based on the same technical concept, the embodiment of the application also provides the electronic equipment. Referring to fig. 16, a schematic structural diagram of an electronic device 1600 provided in the embodiment of the present application includes a processor 1601, a memory 1602, and a bus 1603. The storage 1602 is used for storing execution instructions and includes a memory 16021 and an external storage 16022; the memory 16021 is also referred to as an internal memory for temporarily storing operation data in the processor 1601 and data exchanged with an external memory 16022 such as a hard disk, the processor 1601 exchanges data with the external memory 16022 through the memory 16021, and when the electronic device 1600 operates, the processor 1601 communicates with the storage 1602 through the bus 1603, so that the processor 1601 executes the following instructions:
generating second description information of the requested service resource, and sending the second description information to a server;
receiving a resource allocation request sent by the server under the notification of a service provider, wherein the resource allocation request is used for indicating whether to accept the service resource to be allocated of the service provider; the first description information of the service resource to be distributed issued by the service provider is matched with the second description information;
and replying a resource allocation response to the server based on the resource allocation request.
An embodiment of the present application 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 performs the steps of the method for resource allocation.
Specifically, the storage medium can be a general-purpose storage medium, such as a removable disk, a hard disk, and the like, and when a computer program on the storage medium is executed, the method for allocating resources can be executed, so as to improve the utilization rate of service resources.
The computer program product of the resource allocation method provided in the embodiment of the present application includes a computer-readable storage medium storing a program code, where instructions included in the program code may be used to execute the method in the foregoing method embodiment, and specific implementation may refer to the method embodiment, which is not described herein again.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system and the apparatus described above may refer to corresponding processes in the method embodiments, and are not described in detail in this application. In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and there may be other divisions in actual implementation, and for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or modules through some communication interfaces, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall 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 (33)

1. A method for resource allocation is applied to a server, and is characterized by comprising the following steps:
receiving first description information of service resources to be allocated, which is sent by a service provider, and receiving second description information of the requested service resources, which is sent by different service request terminals respectively;
determining at least one piece of second description information matched with the first description information, and notifying resource detail interface information containing the at least one piece of second description information to the service provider;
receiving target second description information selected by the service provider from the resource detail interface information, and sending a resource allocation request to a target service request end issuing the target second description information, wherein the resource allocation request is used for indicating the target service request end to confirm whether to accept the service resource to be allocated;
and determining a resource allocation result and notifying the service provider of the resource allocation result based on the resource allocation response sent by the target service request terminal.
2. The method according to claim 1, further comprising, after receiving the target second description information selected by the service provider from the resource detail interface information:
and if the target second description information indicates that the sharing of the same service resource is allowed, prompting the service provider to allow other service request terminals to continue requesting to share the service resource to be allocated after the target service request terminal confirms to accept the service resource to be allocated.
3. The method according to claim 1, wherein the determining a resource allocation result and notifying the service provider of the resource allocation result based on the resource allocation response sent by the target service requester comprises:
if the resource allocation response indicates that the target service request terminal confirms to accept the service resources to be allocated, determining that the resource allocation result is successful in allocation,
if the target second description information indicates that the same service resource is allowed to be shared, sending the resource allocation result to the service provider and prompting the service provider whether to continuously request other service request terminals to share the service resource to be allocated;
and if the target second description information indicates that the same service resource is not allowed to be shared, sending the resource allocation result to the service provider, and updating second description information except the target second description information in the resource detail interface information to be in a failure state.
4. The method according to claim 3, further comprising, after prompting the service provider whether to continue to request other service requesters to share the service resource to be allocated, the step of:
and when the service provider is detected to select to continuously request other service request terminals to share the service resources to be allocated, sending a candidate set of second description information to the service provider, wherein the second description information contained in the candidate set indicates that the same service resources are allowed to be shared.
5. The method of claim 1, further comprising, after sending a resource allocation request to a target service requester that issues the target second description information:
and if the target service request end is detected not to reply the resource allocation response within a preset time period, or the target service request end is detected to confirm that the target service request end receives the service resources to be allocated of other service providing ends, updating second description information except the target second description information in the resource detail interface information into a failure state.
6. The method according to any one of claims 1 to 5, wherein the resource detail interface information further comprises at least one of the following information: the matching degree of the first description information and each second description information, the evaluation information of the service request end corresponding to each second description information, and the quantity of the resource allocation requests received by the service request end corresponding to each second description information.
7. The method according to any of claims 1 to 5, wherein the resource allocation request comprises at least one of the following information: part or all of the information in the first description information, the evaluation information of the service provider and the estimated service providing time of the service provider.
8. The method according to any one of claims 1 to 5, wherein the first description information includes at least one of the following information: the travel route information of the service provider, the travel time of the service provider and the travel participant information of the service provider;
the second description information includes at least one of the following information: the system comprises travel route information of a service requester, travel time of the service requester, travel participant information of the service requester, car sharing selection information and service cost information.
9. A method for resource allocation is applied to a service provider, and is characterized by comprising the following steps:
generating first description information of service resources to be allocated, and sending the first description information to a server;
receiving resource detail interface information sent by the server, wherein the resource detail interface information comprises at least one piece of second description information matched with the first description information, and each piece of second description information represents the description of a service request end issuing the second description information on a requested service resource;
selecting target second description information from the resource detail interface information, and informing the server to send a resource allocation request to a target service request end issuing the target second description information, wherein the resource allocation request is used for indicating the target service request end to confirm whether to accept the service resource to be allocated;
and receiving a resource allocation result sent by the server, wherein the resource allocation result is determined by the server based on the resource allocation response of the target service request terminal.
10. The method of claim 9, wherein selecting the target second description information from the resource detail interface information comprises:
generating and displaying a resource detail interface based on the resource detail interface information;
and if the fact that the option corresponding to the target second description information in the resource detail interface is triggered is detected, determining that the target second description information is selected.
11. The method of claim 10, after selecting target second description information from the resource detail interface information, further comprising:
a detail page showing the target second description information;
the notifying the server to send a resource allocation request to a target service request end issuing the target second description information includes:
and after detecting that the resource allocation request option is triggered in the detail page of the target second description information, informing the server to send a resource allocation request to a target service request end which issues the target second description information.
12. The method of claim 9, wherein the receiving the resource allocation result sent by the server comprises:
receiving the resource allocation result sent by the server and used for indicating successful allocation;
if an option for continuously requesting other service request terminals to share the service resources to be allocated in a display interface of the resource allocation result is triggered, receiving a candidate set of second description information sent by the server, wherein the second description information contained in the candidate set indicates that the same service resources are allowed to be shared;
continuing to select target second description information from the candidate set.
13. The method of any of claims 9 to 12, wherein the first description information comprises at least one of: the travel route information of the service provider, the travel time of the service provider and the travel participant information of the service provider;
the second description information includes at least one of the following information: the system comprises travel route information of a service requester, travel time of the service requester, travel participant information of the service requester, car sharing selection information and service cost information.
14. The method according to any one of claims 9 to 12, wherein the resource detail interface information further comprises at least one of the following information: the matching degree of each second description information, the evaluation information of the service request end corresponding to each second description information, and the quantity of the resource allocation requests received by the service requester corresponding to each second description information.
15. A method for resource allocation is applied to a service request end, and is characterized by comprising the following steps:
generating second description information of the requested service resource, and sending the second description information to a server;
receiving a resource allocation request sent by the server under the notification of a service provider, wherein the resource allocation request is used for indicating whether to accept the service resource to be allocated of the service provider; the first description information of the service resource to be distributed issued by the service provider is matched with the second description information;
and replying a resource allocation response to the server based on the resource allocation request.
16. The method of claim 15, wherein the resource allocation request comprises at least one of the following information: the service resource allocation method comprises the steps of obtaining partial or all information in first description information of service resources to be allocated, evaluation information of a service provider who issues the first description information, and estimated service providing time of the service provider who issues the first description information.
17. The method of claim 16, wherein said replying to the server a resource allocation response based on the resource allocation request comprises:
generating and displaying a resource allocation request interface based on at least one type of information carried in the resource allocation request; the resource allocation request interface comprises a plurality of to-be-processed sub-interfaces, and each to-be-processed sub-interface comprises at least one information in a resource allocation request corresponding to one service provider;
and if detecting that an acceptance option for accepting the service resources to be distributed in each sub-interface to be processed is triggered or a rejection option for rejecting the service resources to be distributed is triggered, replying the resource distribution response to the server.
18. An apparatus for resource allocation, comprising:
the system comprises a receiving module, a service providing terminal and a service request terminal, wherein the receiving module is used for receiving first description information of service resources to be distributed sent by the service providing terminal and receiving second description information of the requested service resources sent by different service request terminals;
the first processing module is used for determining at least one piece of second description information matched with the first description information and notifying the resource detail interface information containing the at least one piece of second description information to the service provider;
the receiving module is further used for receiving target second description information selected by the service provider from the resource detail interface information;
a sending module, configured to send a resource allocation request to a target service request end that issues the target second description information, where the resource allocation request is used to indicate the target service request end to determine whether to accept the service resource to be allocated;
and the second processing module is used for determining a resource allocation result and notifying the service provider of the resource allocation result based on the resource allocation response sent by the target service request terminal.
19. The apparatus of claim 18, further comprising:
and a prompting module, configured to, after the receiving module receives target second description information selected by the service provider from the resource detail interface information, if it is detected that the target second description information indicates that the service provider is allowed to share the same service resource, prompt the service provider to allow other service providers to continue to request that other service providers share the service resource to be allocated after the target service provider confirms to receive the service resource to be allocated.
20. The apparatus of claim 18, wherein the second processing module, when determining a resource allocation result based on the resource allocation response sent by the target service requester and notifying the service provider of the resource allocation result, is specifically configured to:
if the resource allocation response indicates that the target service request terminal confirms to accept the service resources to be allocated, determining that the resource allocation result is successful in allocation,
if the target second description information indicates that the same service resource is allowed to be shared, sending the resource allocation result to the service provider and prompting the service provider whether to continuously request other service request terminals to share the service resource to be allocated;
and if the target second description information indicates that the same service resource is not allowed to be shared, sending the resource allocation result to the service provider, and updating second description information except the target second description information in the resource detail interface information to be in a failure state.
21. The apparatus of claim 20, wherein the second processing module, after prompting the service provider whether to continue to request other service requesters to share the service resource to be allocated, is further configured to:
and when the service provider is detected to select to continuously request other service request terminals to share the service resources to be allocated, sending a candidate set of second description information to the service provider, wherein the second description information contained in the candidate set indicates that the same service resources are allowed to be shared.
22. The apparatus of claim 18, wherein the first processing module is further configured to:
after the sending module sends a resource allocation request to a target service request end which issues the target second description information, if the first processing module detects that the target service request end does not reply the resource allocation response within a preset time period, or detects that the target service request end confirms to accept service resources to be allocated of other service providing ends, the second description information except the target second description information in the resource detail interface information is updated to be in a failure state.
23. The apparatus according to any one of claims 18 to 22, wherein the resource detail interface information further comprises at least one of the following information: the matching degree of the first description information and each second description information, the evaluation information of the service request end corresponding to each second description information, and the quantity of the resource allocation requests received by the service request end corresponding to each second description information.
24. The apparatus according to any of claims 18 to 22, wherein the resource allocation request comprises at least one of the following information: part or all of the information in the first description information, the evaluation information of the service provider and the estimated service providing time of the service provider.
25. The apparatus according to any one of claims 18 to 22, wherein the first description information comprises at least one of the following information: the travel route information of the service provider, the travel time of the service provider and the travel participant information of the service provider;
the second description information includes at least one of the following information: the system comprises travel route information of a service requester, travel time of the service requester, travel participant information of the service requester, car sharing selection information and service cost information.
26. An apparatus for resource allocation, comprising:
the generation module is used for generating first description information of the service resources to be distributed;
the sending module is used for sending the first description information to a server;
a receiving module, configured to receive resource detail interface information sent by the server, where the resource detail interface information includes at least one piece of second description information matched with the first description information, and each piece of second description information represents a description of a service resource requested by a service request end issuing the second description information;
the processing module is used for selecting target second description information from the resource detail interface information;
the sending module is further configured to notify the server to send a resource allocation request to a target service request end that issues the target second description information, where the resource allocation request is used to indicate that the target service request end determines whether to accept the service resource to be allocated;
the receiving module is further configured to receive a resource allocation result sent by the server, where the resource allocation result is determined by the server based on the resource allocation response of the target service request end.
27. The apparatus according to claim 26, wherein the processing module, when selecting the target second description information from the resource detail interface information, is specifically configured to:
generating and displaying a resource detail interface based on the resource detail interface information;
and if the fact that the option corresponding to the target second description information in the resource detail interface is triggered is detected, determining that the target second description information is selected.
28. The apparatus of claim 27, wherein the processing module, after selecting the target second description information from the resource detail interface information, is further to:
a detail page showing the target second description information;
the sending module, when notifying the server to send a resource allocation request to the target service request terminal that issued the target second description information, is specifically configured to:
and after detecting that the resource allocation request option is triggered in the detail page of the target second description information, informing the server to send a resource allocation request to a target service request end which issues the target second description information.
29. The apparatus of claim 26, wherein the receiving module, when receiving the resource allocation result sent by the server, is specifically configured to:
receiving the resource allocation result sent by the server and used for indicating successful allocation;
if an option for continuously requesting other service request terminals to share the service resources to be allocated in a display interface of the resource allocation result is triggered, receiving a candidate set of second description information sent by the server, wherein the second description information contained in the candidate set indicates that the same service resources are allowed to be shared;
the processing module is further configured to:
continuing to select target second description information from the candidate set.
30. An apparatus for resource allocation, comprising:
a generating module, configured to generate second description information for the requested service resource;
the sending module is used for sending the second description information to a server;
a receiving module, configured to receive a resource allocation request sent by the server under a notification of a service provider, where the resource allocation request is used to indicate whether to accept a service resource to be allocated of the service provider; the first description information of the service resource to be distributed issued by the service provider is matched with the second description information;
and the replying module is also used for replying a resource allocation response to the server based on the resource allocation request.
31. The apparatus according to claim 30, wherein the replying module, when replying a resource allocation response to the server based on the resource allocation request, is specifically configured to:
generating and displaying a resource allocation request interface based on at least one type of information carried in the resource allocation request; the resource allocation request interface comprises a plurality of to-be-processed sub-interfaces, and each to-be-processed sub-interface comprises at least one information in a resource allocation request corresponding to one service provider;
and if detecting that an acceptance option for accepting the service resources to be distributed in each sub-interface to be processed is triggered or a rejection option for rejecting the service resources to be distributed is triggered, replying the resource distribution response to the server.
32. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is operating, the processor executing the machine-readable instructions to perform the steps of the method of any one of claims 1 to 8, or to perform the steps of the method of any one of claims 9 to 14, or to perform the steps of the method of any one of claims 15 to 17.
33. A computer-readable storage medium, having stored thereon a computer program for performing, when executed by a processor, the steps of the method of any one of claims 1 to 8, or for performing the steps of the method of any one of claims 9 to 14, or for performing the steps of the method of any one of claims 15 to 17.
CN201910386332.0A 2019-05-09 2019-05-09 Resource allocation method and device Active CN110751532B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910386332.0A CN110751532B (en) 2019-05-09 2019-05-09 Resource allocation method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910386332.0A CN110751532B (en) 2019-05-09 2019-05-09 Resource allocation method and device

Publications (2)

Publication Number Publication Date
CN110751532A true CN110751532A (en) 2020-02-04
CN110751532B CN110751532B (en) 2021-01-05

Family

ID=69275731

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910386332.0A Active CN110751532B (en) 2019-05-09 2019-05-09 Resource allocation method and device

Country Status (1)

Country Link
CN (1) CN110751532B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114040225A (en) * 2021-11-17 2022-02-11 聚好看科技股份有限公司 Server, display equipment and media asset mapping method

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110009098A1 (en) * 2009-07-10 2011-01-13 Kong Jae Young Method of calling a vehicle and mobile terminal for the same
CN107015988A (en) * 2016-01-27 2017-08-04 滴滴出行科技有限公司 A kind of information matching method based on map and user-association for applying to special train
CN108701320A (en) * 2016-03-08 2018-10-23 北京嘀嘀无限科技发展有限公司 The system and method for share-car

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110009098A1 (en) * 2009-07-10 2011-01-13 Kong Jae Young Method of calling a vehicle and mobile terminal for the same
CN107015988A (en) * 2016-01-27 2017-08-04 滴滴出行科技有限公司 A kind of information matching method based on map and user-association for applying to special train
CN108701320A (en) * 2016-03-08 2018-10-23 北京嘀嘀无限科技发展有限公司 The system and method for share-car

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114040225A (en) * 2021-11-17 2022-02-11 聚好看科技股份有限公司 Server, display equipment and media asset mapping method
CN114040225B (en) * 2021-11-17 2023-08-11 聚好看科技股份有限公司 Server, display equipment and media asset mapping method

Also Published As

Publication number Publication date
CN110751532B (en) 2021-01-05

Similar Documents

Publication Publication Date Title
US20190057326A1 (en) Method and system for booking transportation services
JP7235647B2 (en) Systems and methods for allocating pending orders
Lam Combinatorial auction-based pricing for multi-tenant autonomous vehicle public transportation system
RU2018126467A (en) METHOD AND SYSTEM FOR INDIVIDUALIZED DEMAND SERVICES
WO2016025926A1 (en) Transportation services for package delivery
US20190019146A1 (en) System and method for arranging deliveries and ride sharings
US20200160235A1 (en) Method and system of scheduling rides in a ride-sharing platform
TW201909055A (en) System and method for allocating service requests
CN111861081A (en) Order allocation method and device, electronic equipment and storage medium
CN111105251A (en) Information pushing method and device
US20180365597A1 (en) Service provider appointment booking system
CN111768254A (en) Order processing method and device
CN106373382A (en) Method and apparatus for vehicle scheduling
CN112017001A (en) Network appointment vehicle type recommendation method and device, electronic equipment and storage medium
CN110751532B (en) Resource allocation method and device
JP6973278B2 (en) Server systems, control methods, and programs
US20210118082A1 (en) Shared vehicle managing system
CN112001516B (en) Information processing method, device, electronic equipment and storage medium
CN114372714A (en) Automatic vehicle allocation method, device, equipment, medium and program product
CN111833119A (en) Order allocation method and device, electronic equipment and storage medium
CN111612493B (en) User grouping method and device
CN111798258A (en) Service request price calculation method, device and system
JP2021182293A (en) Delivery matching system
CN113330467A (en) Method, system, and medium for controlling terminal based on state information of vehicle
CN112884627B (en) Control device, system, medium, terminal device, and payment distribution method

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