Request processing method, device, electronic device and storage medium

Abstract

The present disclosure provides a request processing method, device, electronic device and storage medium, which relate to the field of computer technology, and in particular to the field of artificial intelligence technology such as big data and intelligent transportation. The specific implementation scheme is: in response to receiving a task acquisition request sent by a requester and the location information related to the task acquisition request, a road data collection task is obtained; the road data collection task is generated by modifying the original collection task by the original idle road section; and the road data collection task is sent to the requester. The embodiment of the present disclosure can reduce the idle driving sections when executing the road data collection task, and improve the efficiency of executing the task.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, in particular to the field of artificial intelligence technology such as big data and intelligent transportation, and specifically to a request processing method, device, electronic device and storage medium. Background Art

[0002] With the development of computer technology, the application of map data is becoming more and more extensive. Map data can not only be used for navigation, but also frequently used in scenarios such as taxi services and search services. In order to provide better products and services to users of map data-related services, auxiliary operations such as road data collection and map data creation need to be done well. Summary of the invention

[0003] The present disclosure provides a request processing method, device, electronic device and storage medium.

[0004] According to a first aspect of the present disclosure, a request processing method is provided, comprising:

[0005] In response to receiving a task acquisition request sent by a requester and location information related to the task acquisition request, a road data collection task is acquired; the road data collection task is generated by modifying an original collection task by modifying an original empty road section;

[0006] The road data collection task is sent to the requesting party.

[0007] According to a second aspect of the present disclosure, there is provided a request processing device, comprising:

[0008] A task acquisition module, configured to acquire a road data collection task in response to receiving a task acquisition request sent by a requester and location information related to the task acquisition request; the road data collection task is generated by modifying an original collection task by modifying an original empty road section;

[0009] A sending module is used to send the road data collection task to the requesting party.

[0010] According to a third aspect of the present disclosure, there is provided an electronic device, including:

[0011] at least one processor; and

[0012] a memory communicatively connected to the at least one processor; wherein,

[0013] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can perform the aforementioned method.

[0014] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to cause the computer to execute the aforementioned method.

[0015] According to a fifth aspect of the present disclosure, a computer program product is provided, comprising a computer program, which implements the aforementioned method when executed by a processor.

[0016] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description.

[0017] The solution provided in this embodiment can send a road data collection task generated by modifying the original idle road section to the requester of the road data collection task, so that the requester can reduce the idle driving sections when performing the road data collection task when performing the task, thereby improving the efficiency of performing the task. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure.

[0019] Figure 1 is a flowchart of a request processing method according to an embodiment of the present disclosure;

[0020] Figure 2 is a schematic diagram of a collection task according to an example of the present disclosure;

[0021] Figure 3 is a schematic diagram of a road section according to an example of the present disclosure;

[0022] Figure 4 is a flowchart of a request processing method according to another embodiment of the present disclosure;

[0023] Figure 5 is a schematic diagram of an empty road section according to an example of the present disclosure;

[0024] Figure 6 is another schematic diagram of the process of the request processing method according to another embodiment of the present disclosure;

[0025] Figure 7 This is a schematic diagram of selecting an idle road section according to an example of the present disclosure;

[0026] Figure 8 is a schematic diagram of a composition structure of a request processing device according to an embodiment of the present disclosure;

[0027] Fig. 9 is another schematic diagram of the composition structure of a request processing device according to an embodiment of the present disclosure;

[0028] Fig.10 is a schematic diagram of a composition structure of a request processing device according to another embodiment of the present disclosure;

[0029] Fig.11 is a schematic diagram of the structure of an empty road section module of a request processing device according to another embodiment of the present disclosure;

[0030] Fig.12 is a schematic diagram of the structure of a subtask processing module of a request processing device according to another embodiment of the present disclosure;

[0031] Fig.13 is another schematic diagram of the composition structure of a request processing device according to another embodiment of the present disclosure;

[0032] Fig.14 is a schematic diagram of the structure of a feedback content determination module of a request processing device according to another embodiment of the present disclosure;

[0033] Fig.15 The block diagram is a block diagram of an electronic device for implementing the request processing method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0035] The first aspect of the present disclosure provides a request processing method, such as Figure 1 As shown, including:

[0036] Step S101: in response to receiving a task acquisition request sent by a requester and location information related to the task acquisition request, a road data collection task is acquired; the road data collection task is generated by modifying the original collection task by modifying the original idle road section;

[0037] Step S102: sending the road data collection task to the requesting party.

[0038] The solution provided in this embodiment can be applied to electronic devices, especially terminal devices, such as personal computers, tablet computers, mobile phones, etc.

[0039] The requesting party may be the executor of the road data collection task, or the terminal of the executor of the road data collection task, for example, the mobile phone terminal, tablet terminal, vehicle computer terminal, laptop terminal, wearable smart device terminal, etc. of the user who performs the road data collection task.

[0040] The above-mentioned road data collection task can be a collection task of defining a collection route. Figure 2 As shown, in a road network distributed in the east-west, south-north direction, road data collection task A may include a subtask of collecting data from south to north along road a1. Road data collection task B may include a subtask of collecting data from south to north along road b1, and a subtask of collecting data from west to east along road b2. Road data collection task C may include a subtask of collecting data in both directions along road c1. Road data collection task D may include a subtask of collecting data in both directions along roads d1, d2, etc.

[0041] The collected content of the above road data collection task can be any data related to the road, such as road surface video data or image data, road double-side or single-side building video data or image data, road surrounding interest point location prediction data, road surrounding interest point existence status verification data, road shape data, road slope data, road traffic data, road lane division data, road length data, etc.

[0042] The road data collection task can be completed by the requester's corresponding vehicle or other means of transportation passing on the road and turning on the collection device to complete the collection. It can also be completed by the requester walking or other means, while turning on the collection device while walking or other means of transportation to complete the collection.

[0043] The road data collection task can be performed by any device capable of collecting data. For example, road data can be collected by devices including handheld cameras, driving recorders, cameras attached to terminals, etc. Road data can also be collected by devices such as radar signals and radar point cloud data collection devices.

[0044] The task acquisition request sent by the requesting party may be a request sent by a terminal corresponding to the requesting party, which indicates that the requesting party can receive the road data collection task. The request may be sent by clicking a corresponding button, by opening an APP (Application) of the road data collection task, or by performing other operations on the terminal.

[0045] The location information related to the task acquisition request can be determined based on the positioning information carried in the task acquisition request sent by the requester, or can be determined based on positioning the terminal corresponding to the requester. The positioning information carried in the task acquisition request sent by the requester can be generated based on the input operation detected by the terminal corresponding to the requester.

[0046] The step of acquiring the road data collection task in response to receiving the task acquisition request sent by the requester and the location information related to the task acquisition request may be: upon receiving the task acquisition request, acquiring the road data collection task within a set range around the location information related to the task acquisition request. The predetermined range may be set according to actual conditions, such as within a radius of 1 km, or within a radius of 2 km, or larger or smaller, which are not exhaustive here.

[0047] Alternatively, the step of acquiring the road data collection task in response to receiving the task acquisition request and the location information related to the task acquisition request sent by the requesting party may be: upon receiving the task acquisition request, acquiring the road data collection task including the location information related to the task acquisition request.

[0048] The original collection task may be an original version of the road data collection task corresponding to the road data collection task, and specifically may be an original version of the road data collection task generated only based on the road data collection requirements without considering the idle road sections. The original collection task may be modified to modify the original idle road sections, which may at least reduce the idle road sections, or eliminate the idle road sections in some way, so as to achieve the purpose of reducing the necessary driving sections that do not exist in the subtask during the road data collection process.

[0049] Since there are generally only two types of road sections, namely, empty road sections and non-empty road sections, modifying the original empty road sections of the original acquisition task may include modifying at least part of the original empty road sections into non-empty road sections.

[0050] In a possible implementation, each link may have its own link ID, which may be composed of elements such as link positioning points and directions, such as Figure 3 As shown, a road section includes a direction in which vehicles are allowed to travel (as shown by arrows) and a plurality of road section positioning points 31. Each road section positioning point 31 includes a specific location information, which can be represented by coordinates in a world coordinate system or by longitude and latitude. If a road is a one-way road, the road has at least one road section. If a road is a two-way road, the road may have at least two road sections in opposite directions.

[0051] In a possible implementation, the positioning points mentioned above and in other locations of the present disclosure may be location information points collected by a GPS system, and may be basic elements of a road section, including latitude and longitude coordinate information (e.g. Figure 3 The road segment positioning points 31 in the figure are shown in Figure 31). Each positioning point can be represented by a small dot, and each small dot represents a GPS point. The position of the positioning point can be represented by longitude and latitude coordinates. For example, longitude lon = 118.2927393455, latitude lat = 36.913867910409. In a specific implementation, a group of GPS points can constitute a Link.

[0052] Sending the road data collection task to the requester may be sending at least one acquired road data collection task to a terminal corresponding to the requester.

[0053] The method provided by the embodiments of the present disclosure can be applied to a variety of products related to road data collection tasks, such as the LuTao product (a part-time data collection tool APP, users can use this APP to drive on the task road, take pictures and upload data to obtain corresponding rewards). Due to changes in the real world, the task road tasks issued by LuTao cannot fully perceive the road conditions and difficulty collected by the user (who can be the requester) at the time, resulting in idle consumption for the user and failure to maximize user benefits. In a specific possible implementation method, modifying the original idle consumption section of the original collection task may include adjusting the task issuance strategy and the user reward amount according to the idle consumption mileage, thereby at least reducing the idle consumption or even eliminating the idle consumption.

[0054] Exemplarily, the above steps S101 and S102 may be implemented by the following process: the user generates a task acquisition request by opening the APP on the terminal and automatically sends the task acquisition request through the APP. When the APP is opened, the automatic positioning function is turned on to determine the location of the user terminal as the location related to the task acquisition request, and at least one road data collection task near the user terminal location is determined. At least one road data collection task near the user terminal location may be displayed in the form of an icon on the map or a special color mark for the user to select, and when the user terminal selects a specific road data collection task (as a target task), the detailed information of the road data collection task may be presented on the display interface, including the specific road section where data needs to be collected, the collection direction and collection target corresponding to each road section where data needs to be collected, and the reward corresponding to the specific road section where data needs to be collected. Since the road data collection task sent to the user terminal and presented on the terminal display interface is generated by modifying the original idle road section of the original collection task, the idle driving road sections contained in all road data collection tasks sent to the user terminal are smaller than the idle driving road sections (original idle road sections) contained in the original collection task. Thereby reducing the idle driving mileage of the task executor as a whole.

[0055] It can be seen that through the above scheme, the road data collection task generated by modifying the original idle road section can be sent to the requester of the road data collection task, so that the requester can reduce the mileage on the idle road section when performing the task, thereby increasing the enthusiasm of the requester to perform the road data collection task and improving the efficiency of the execution of the road data collection task.

[0056] In one embodiment, Figure 4 As shown in the figure, the generation method of the road data collection task includes:

[0057] Step S401: determining an original passable road section according to the original collection task; the original collection task is used to instruct the requesting party to collect road data for the original passable road section;

[0058] Step S402: determining an original idle road section according to the original passable road section;

[0059] Step S403: based on the supplementary subtask of the original idle road section, modify the original idle road section; the supplementary subtask is used to instruct the requesting party to collect road data for the original idle road section;

[0060] Step S404: generating the road data collection task based on the original collection task and the supplementary subtask.

[0061] The above-mentioned original collection task may be a collection task generated only based on the need for road data collection without considering the reduction or modification of idle road sections.

[0062] In a system where road data collection tasks are repeatedly issued, the original collection task can be generated based on the execution data of the previous executor or executor. In this case, the original idle road section can also be determined based on the execution data generated by the executor performing the original collection task. The road section that has and does not have the corresponding subtask to be executed in the execution data can be determined as the original idle road section.

[0063] For example, in the map data, there are updates of surrounding buildings on road a1 and updates of lane lines on road a2. a1 and a2 have no direct connection with each other. Based on the need to collect updated building-related data, an original road collection task can be generated, including one-way road data collection for a1 and two-way road data collection for a2.

[0064] The above-mentioned original passable road section may be a road section for which road data needs to be collected in the original road collection task. For example, the original road collection task may include collecting unidirectional road data for a1 and collecting bidirectional road data for a2, and the original passable road section includes a1 and a2, or the original passable road section may also include the unidirectional road of a1 and the bidirectional road of a2.

[0065] The determining of the original idle road section according to the original passable road section may be:

[0066] According to the original passable road section, the non-original passable road section that needs to be traveled is determined when the original passable road section is completed at one time; the non-original passable road section that needs to be traveled is used as the original empty road section. For example, the total road section required to execute the original collection task is subtracted from the original passable road section.

[0067] The above-mentioned original empty road section may be a non-original road section that must or may be passed through in order to complete the road data collection of all original road sections at one time. It can be understood that the non-original road section here may be a road section for which the original collection task does not have a supplementary subtask or other road data collection subtask.

[0068] For example, Figure 5 As shown, the original traffic section includes a1 one-way road (such as Figure 5 In order to complete the one-way road data collection of a1 and the two-way road data collection of a2 at the same time, it is necessary to pass through at least the one-way road of a3, then a3 is an empty road section, or the one-way road of a3 is an empty road section.

[0069] The above-mentioned supplementary subtasks may be supplementary subtasks that are not indicated for collection in the original collection task and are subsequently generated. Figure 5 In the corresponding example, the supplementary subtask may be used to instruct the collection of road data for the one-way road a3.

[0070] In the case where there are multiple empty road sections, the supplementary subtask can be used to instruct the collection of road data for at least any one of the empty road sections. The collected road data of the empty road section can be used to verify and check the existing road data of the empty road section. In the case where the empty road section includes a two-way road of a certain section, the supplementary subtask can be used to instruct the collection of road data for at least one one-way road of the empty road section.

[0071] It can be seen that through the above embodiments, supplementary subtasks can be generated for idle road sections, thereby reducing idle road sections, increasing the enthusiasm of the requesting party to complete the road data collection task, and helping to improve the efficiency of task execution.

[0072] In one implementation, determining the original idle road section according to the original passable road section includes:

[0073] Determine a target route covering the original passable road section;

[0074] The difference section between the target route and the original pass section is used as the original idle section.

[0075] The target route may be a minimum driving route covering the original passable road section, or may be one of the better driving routes covering the original passable road section.

[0076] In a possible implementation, the preferred driving route covering the original passable road section may include multiple types, at least one of which can be selected as the target route; when different target routes are selected, the original idle road section determined is different.

[0077] It can be seen that the original idle road section is determined by covering the target route of the original passable road section, so that the original idle road section can connect at least two original passable road sections that have no direct connection relationship, so that the road data collection task generated after reducing the idle road section reduces the idle driving in a driving collection process.

[0078] In one implementation, generating the road data collection task based on the original collection task and the supplementary subtask includes:

[0079] Determine the unit mileage feedback content corresponding to the original collection task and the supplementary subtask respectively;

[0080] The road data collection task is generated according to the original collection task, the supplementary subtask, and the unit mileage feedback contents respectively corresponding to the original collection task and the supplementary subtask.

[0081] The unit mileage feedback content may be the content fed back to the executor per unit mileage after the task is completed, such as unit price, lottery opportunity, prize, right, etc. The task may include the original collection task and the supplementary subtask.

[0082] The determining of the unit mileage feedback content corresponding to the original collection task and the supplementary subtask respectively may include: determining the unit mileage feedback content corresponding to the original collection task and the unit mileage feedback content corresponding to the supplementary subtask respectively.

[0083] The unit mileage feedback contents respectively corresponding to the original collection task and the supplementary subtask may be the same or different.

[0084] The generating of the road data collection task according to the original collection task, the supplementary subtask, and the unit mileage feedback contents respectively corresponding to the original collection task and the supplementary subtask may be: combining the driving section corresponding to the original collection task and the unit mileage feedback contents corresponding to the original collection task, the driving section corresponding to the supplementary subtask, and the unit mileage feedback contents corresponding to the supplementary subtask, to generate the road data collection task.

[0085] It can be seen that by determining the unit mileage feedback content for the supplementary subtask, the enthusiasm of the executors in performing the road data collection task can be improved, which helps to improve the efficiency of task execution.

[0086] In one embodiment, Figure 6 As shown, the determining of the unit mileage feedback content corresponding to the original collection task and the supplementary subtask includes:

[0087] Step S601: determining the original feedback content preset in the original collection task;

[0088] Step S602: Allocate the original feedback content to the original collection task and the supplementary subtask to obtain the unit mileage feedback content corresponding to the original collection task and the unit mileage feedback content corresponding to the supplementary subtask.

[0089] The original feedback content may be the original unit mileage feedback content, and specifically may be the unit mileage feedback content for the original travel section set when the original collection task is created, such as giving a reward of X fee per unit mileage.

[0090] The allocating the original feedback content to the original collection task and the supplementary subtask to obtain the unit mileage feedback content corresponding to the original collection task and the unit mileage feedback content corresponding to the supplementary subtask may be:

[0091] A first part is reduced from the original feedback content corresponding to the original collection task, and the reduced first part is added to the supplementary subtask to obtain the unit mileage feedback content corresponding to the supplementary subtask and the unit mileage feedback content corresponding to the original collection task.

[0092] For example, the original feedback content corresponding to the original collection task is the fee given to X1 per unit mileage. The original feedback content is allocated to the original collection task and the supplementary subtask, and the X2 fee in the X1 fee can be allocated to the supplementary subtask as the unit mileage feedback content corresponding to the supplementary subtask, and the X1-X2 fee is used as the unit mileage feedback content corresponding to the original collection task.

[0093] Exemplarily, the original feedback content corresponding to the original collection task is an X3 fee per unit mileage. The original feedback content is distributed to the original collection task and the supplementary subtask, which can be obtained by multiplying the X3 fee by the estimated mileage of the original passable road section and dividing it by the sum of the estimated mileage of the original passable road section and the driving mileage corresponding to the supplementary subtask to obtain X4. The X4 fee is used as the unit mileage feedback content corresponding to the original collection task and the supplementary subtask. The estimated mileage can be determined based on the execution data of the completed previous batch of road data collection tasks.

[0094] It can be seen that by allocating the unit mileage feedback content corresponding to the original collection task to the travelable road section corresponding to the supplementary subtask, the waste of road data collection tasks can be reduced without increasing costs.

[0095] In one embodiment, the request processing method further includes:

[0096] receiving execution data sent by the requesting party; the execution data is generated by the requesting party executing the road data collection task;

[0097] Based on the execution data and the unit mileage feedback content corresponding to the road data collection task, target content to be fed back to the requesting party is determined.

[0098] The above-mentioned execution data may include at least one of video data, positioning data, speed data, etc.

[0099] Exemplarily, the above-mentioned execution data can be a file package consisting of GPS coordinates (lon, lat), speed (Speed), driving direction (Head), positioning timestamp (Time) and other information obtained by the corresponding APP through obtaining the terminal positioning information corresponding to the requester.

[0100] It can be seen that by sending feedback content to the requesting party through the above-mentioned execution data and the predetermined unit mileage feedback content, it is possible to report on the task execution results, increase the motivation and enthusiasm of the executors to perform the road data collection tasks, and improve the execution efficiency of the road data collection tasks.

[0101] In one implementation, determining the target content to be fed back to the requesting party based on the execution data and the unit mileage feedback content corresponding to the road data collection task includes:

[0102] Determining the mileage corresponding to the road data collection task based on the execution data;

[0103] The target content to be fed back to the requesting party is determined based on the driving mileage and the unit mileage feedback content corresponding to the road data collection task.

[0104] Wherein, determining the mileage corresponding to the road data collection task based on the execution data may be determining the actual mileage traveled to complete the road data collection task based on the execution data.

[0105] In a possible implementation, the multiple road sections included in the road data collection task may correspond to different unit mileage feedback contents.

[0106] In this embodiment, the content of feedback to the requesting party is determined based on the execution data, so that the task executor can be given an accurate reward.

[0107] In one implementation, the execution data includes a positioning point and a speed corresponding to the positioning point; and determining the mileage corresponding to the road data collection task based on the execution data includes:

[0108] Determining a plurality of target positioning points for calculating mileage based on the speeds corresponding to the positioning points;

[0109] The driving mileage corresponding to the road data collection task is determined based on the distance between every two adjacent target positioning points among the multiple target positioning points.

[0110] Among them, the determination of multiple target positioning points for calculating the mileage based on the speed corresponding to the positioning points can be based on the corresponding relationship between the preset speed and the number N of positioning point intervals, and the first positioning point and the positioning points every N positioning points thereafter are determined as target positioning points.

[0111] In one possible implementation, considering that there may be errors in the coordinates of the positioning points determined by the GPS (Global Position System), the positioning coordinates may drift when the acquisition terminal does not move. Therefore, the target positioning points can be selected at intervals of a certain number of positioning points to reduce the distance calculation error caused by positioning drift.

[0112] In a possible implementation, during the road data collection process, the faster the driving speed, the smaller the number of positioning points between the corresponding target positioning points, and vice versa.

[0113] In a specific implementation, due to the user parking and other reasons, the GPS point positioning is stagnant or drifts back and forth, so it can be divided into three rules based on the driving speed (Speed) of the requesting terminal in the trajectory file:

[0114] When Speed<=a first value (such as 10 km / h, etc.), a target positioning point may be determined every first positive integer (such as 10, etc.) of positioning points;

[0115] When Speed>the first value and Speed<=the second value (such as 30 km / h, etc.), a target positioning point may be determined every second positive integer (such as 5, etc.) of positioning points;

[0116] When Speed>the second value, a target positioning point may be determined every third positive integer (such as 2, etc.) of positioning points.

[0117] The distance between each two adjacent target positioning points can be calculated by the coordinates of each two adjacent target positioning points. The mileage of each road section corresponding to the road data collection task can be calculated by the sum of the distances between the target positioning points.

[0118] In a specific implementation, the distance between each two adjacent target positioning points can be calculated by the distance formula between two points. For example, considering the shape of the earth, the spherical distance formula can be used for calculation. Assume that the target point A is at latitude angle β1 and longitude angle α1; the target positioning point B is at latitude angle β2 and longitude angle α2. Then the distance S = R × arc cos [cosβ1cosβ2cos (α1-α2) + sinβ1sinβ2], where R is the radius of the sphere.

[0119] It can be seen that the above embodiment takes into account the drift phenomenon of positioning data when calculating the actual mileage, and thus selects the target positioning points in a manner of spacing a certain number of positioning points, so that the actual mileage can be accurately calculated. Under the premise that there is an association between the trajectory and the Link corresponding to the road data collection task, the recovery mileage can be improved, and user satisfaction can also be improved under the experience of higher task connectivity.

[0120] In other implementations, the unit price of the original driving section corresponding to the original collection task (unit mileage feedback content) can be adjusted or the overall reward can be increased to compensate for the user's actual idle running fuel subsidy and increase the user's enthusiasm for collection.

[0121] In one example of the present disclosure, for example Figure 7 The original driving sections 701 and 702 shown in the figure can be set with supplementary subtasks based on the idle section 703 or 704. Specifically, the unit mileage feedback content (such as unit price) corresponding to at least one of the original driving sections 701 and 702 can be reduced, and the reduced part can be allocated to 703 or 704. In this way, the idle consumption is reduced and the task recovery mileage is increased without changing the total content fed back to the requesting party.

[0122] In an example of the present disclosure, the distance between adjacent target positioning points is calculated by using the spherical distance formula between two points, and the implementation method is as follows:

[0123] Get the longitude and latitude of two adjacent target positioning points; where the longitude and latitude can be integers, decimals, floating point decimals, etc.; for example, get the longitude angle A1 and latitude angle B1 of the first target positioning point; get the longitude angle C2 and latitude angle D2 of the second target positioning point;

[0124] The angle is calculated based on the longitude and latitude of two adjacent target positioning points, and the angle is converted into radians; for example, the longitude and latitude angles of the first target positioning point are converted into radians: longitude angle α1 = A1 / π, latitude angle β1 = B1 / π; the longitude and latitude angles of the second target positioning point are converted into radians: longitude angle α2 = A2 / π, latitude angle β2 = B2 / π;

[0125] The first intermediate variable of the distance between two target positioning points is calculated by the sine formula (Sin) and the cosine formula (Cos); for example, the first intermediate variable = cosβ1cosβ2cos(α1-α2)+sinβ1sinβ2;

[0126] Perform arc cosine (Acos) calculation on the first intermediate variable to obtain a second intermediate variable of the distance between the two target positioning points; for example, the second intermediate variable = arc cos[cosβ1cosβ2cos(α1-α2)+sinβ1sinβ2];

[0127] The second intermediate variable is converted to obtain distance data in miles, nautical miles or other units, such as distance = R × arc cos[cosβ1cosβ2cos(α1-α2)+sinβ1sinβ2], where R is the radius of the earth.

[0128] In an example of the present disclosure, before receiving the execution data, the target task selected by the requesting party in the road data collection task may be determined. Figure 8 Steps shown:

[0129] Step S801: Sending a road data collection task to the requesting party.

[0130] This step can be based on Figure 1 The process shown and the related embodiments are executed.

[0131] Step S802: The executor selects a target task from the road data collection tasks.

[0132] The executor or executor may be the requester.

[0133] Step S803: receiving execution data obtained by the executor when executing one of the road data collection tasks (ie, the target task).

[0134] Execution data may include information such as traces and timestamps.

[0135] Step S804: Determine the content of feedback to the executor according to the adjusted unit mileage feedback content and the actual driving mileage obtained according to the execution data.

[0136] The present disclosure also provides a request processing device, such as Fig. 9 As shown, including:

[0137] The task acquisition module 901 is used to acquire a road data collection task in response to receiving a task acquisition request sent by a requester and location information related to the task acquisition request; the road data collection task is generated by modifying the original collection task by modifying the original empty road section;

[0138] The sending module 902 is used to send the road data collection task to the requesting party.

[0139] In one embodiment, Fig.10 As shown, the request processing device also includes:

[0140] The original passable road section module 1001 is used to determine the original passable road section according to the original collection task; the original collection task is used to instruct the requesting party to collect road data for the original passable road section;

[0141] An idle road section module 1002 is used to determine an original idle road section according to an original passable road section;

[0142] Subtask module 1003, used to modify the original idle road section based on the supplementary subtask of the original idle road section; the supplementary subtask is used to instruct the requesting party to collect road data for the original idle road section;

[0143] The subtask processing module 1004 is used to generate a road data collection task based on the original collection task and the supplementary subtask.

[0144] In one embodiment, Fig.11 As shown, the empty road section module includes:

[0145] A target route unit 1101 is used to determine a target route covering the original passable road section;

[0146] The target route processing unit 1102 is used to use the difference between the target route and the original passable route as the original idle route.

[0147] In one embodiment, Fig.12 As shown, the subtask processing module includes:

[0148] The unit mileage feedback content determining unit 1201 is used to determine the unit mileage feedback content corresponding to the original collection task and the supplementary subtask respectively;

[0149] The collection task generating unit 1202 is used to generate the road data collection task according to the original collection task, the supplementary subtask, and the unit mileage feedback contents corresponding to the original collection task and the supplementary subtask respectively.

[0150] In one embodiment, the unit mileage feedback content determination unit 1201 is used to determine the original feedback content preset for the original collection task; allocate the original feedback content to the original collection task and the supplementary subtask to obtain the unit mileage feedback content corresponding to the original collection task and the unit mileage feedback content corresponding to the supplementary subtask.

[0151] In one embodiment, Fig.13 As shown, the request processing device also includes:

[0152] The execution data receiving module 1301 is used to receive the execution data sent by the requesting party; the execution data is generated by the requesting party executing the road data collection task;

[0153] The feedback content determination module 1302 is used to determine the target content to be fed back to the requesting party based on the execution data and the unit mileage feedback content corresponding to the road data collection task.

[0154] In one embodiment, Fig.14 As shown, the feedback content determination module includes:

[0155] The mileage determination unit 1401 is used to determine the driving mileage corresponding to the road data collection task based on the execution data;

[0156] The calculation unit 1402 is used to determine the target content to be fed back to the requesting party based on the driving mileage and the unit mileage feedback content corresponding to the road data collection task.

[0157] In one embodiment, the execution data includes positioning points and speeds corresponding to the positioning points; the mileage determination unit is used to determine multiple target positioning points for calculating the mileage based on the speeds corresponding to the positioning points; and determine the mileage corresponding to the road data collection task based on the distance between each two adjacent target positioning points among the multiple target positioning points.

[0158] In the technical solution disclosed herein, the acquisition, storage and application of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0159] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

[0160] Fig.15 A schematic block diagram of an example electronic device 1500 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.

[0161] like Fig.15As shown, the electronic device 1500 includes a computing unit 1501, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 1502 or a computer program loaded from a storage unit 1508 into a random access memory (RAM) 1503. In the RAM 1503, various programs and data required for the operation of the electronic device 1500 can also be stored. The computing unit 1501, the ROM 1502, and the RAM 1503 are connected to each other via a bus 1504. An input / output (I / O) interface 1505 is also connected to the bus 1504.

[0162] Multiple components in the electronic device 1500 are connected to the I / O interface 1505, including: an input unit 1506, such as a keyboard, a mouse, etc.; an output unit 1507, such as various types of displays, speakers, etc.; a storage unit 1508, such as a disk, an optical disk, etc.; and a communication unit 1509, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 1509 allows the electronic device 1500 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0163] The computing unit 1501 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 1501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 1501 performs the various methods and processes described above. For example, in some embodiments, the various methods described above may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 1508. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 1500 via ROM 1502 and / or communication unit 1509. When the computer program is loaded into RAM 1503 and executed by the computing unit 1501, one or more steps of the various methods described above may be performed. Alternatively, in other embodiments, the computing unit 1501 may be configured to perform the various methods described above in any other appropriate manner (e.g., by means of firmware).

[0164] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0165] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0166] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0167] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0168] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communications network). Examples of communications networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0169] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0170] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0171] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A request processing method, comprising: In response to receiving a task acquisition request sent by a requester and location information related to the task acquisition request, acquiring a road data collection task; The road data collection task is generated by modifying the original empty road section of the original collection task; Sending the road data collection task to the requesting party; It also includes: determining an original passable road section according to the original collection task; the original collection task is used to instruct the requester to collect road data for the original passable road section; determining a target route covering the original passable road section; using the difference between the target route and the original passable road section as the original idle road section; modifying the original idle road section based on a supplementary subtask of the original idle road section, wherein the supplementary subtask is used to instruct the requester to collect road data for the original idle road section; determining unit mileage feedback content corresponding to the original collection task and the supplementary subtask respectively; generating the road data collection task according to the original collection task, the supplementary subtask, and the unit mileage feedback content corresponding to the original collection task and the supplementary subtask respectively.

2. The method according to claim 1, wherein: The determining of the unit mileage feedback content corresponding to the original collection task and the supplementary subtask respectively includes: Determining the original feedback content preset in the original collection task; The original feedback content is distributed to the original collection task and the supplementary subtask to obtain the unit mileage feedback content corresponding to the original collection task and the unit mileage feedback content corresponding to the supplementary subtask.

3. The method according to claim 1 or 2, further comprising: receiving execution data sent by the requesting party; The execution data is generated by the requesting party executing the road data collection task; Based on the execution data and the unit mileage feedback content corresponding to the road data collection task, target content to be fed back to the requesting party is determined.

4. The method according to claim 3, wherein: The determining of target content to be fed back to the requesting party based on the execution data and the unit mileage feedback content corresponding to the road data collection task includes: Determining the mileage corresponding to the road data collection task based on the execution data; The target content to be fed back to the requesting party is determined based on the driving mileage and the unit mileage feedback content corresponding to the road data collection task.

5. The method according to claim 4, wherein: The execution data includes a positioning point and a speed corresponding to the positioning point; The determining, based on the execution data, the mileage corresponding to the road data collection task includes: Determining a plurality of target positioning points for calculating mileage based on the speeds corresponding to the positioning points; The driving mileage corresponding to the road data collection task is determined based on the distance between every two adjacent target positioning points among the multiple target positioning points.

6. A request processing device, comprising: A task acquisition module, configured to acquire a road data collection task in response to receiving a task acquisition request sent by a requester and location information related to the task acquisition request; The road data collection task is generated by modifying the original empty road section of the original collection task; A sending module, used for sending the road data collection task to the requesting party; It also includes an original passable road section module, which is used to determine the original passable road section according to the original collection task; The original collection task is used to instruct the requesting party to collect road data for the original pass section; A target route unit, used to determine a target route covering the original passable road section; A target route processing unit, used for taking the difference section between the target route and the original passable section as the original idle section; A subtask module is used to modify the original idle road section based on the supplementary subtask of the original idle road section, wherein the supplementary subtask is used to instruct the requesting party to collect road data for the original idle road section; a unit mileage feedback content determination unit is used to determine the unit mileage feedback content corresponding to the original collection task and the supplementary subtask respectively; and a collection task generation unit is used to generate the road data collection task according to the original collection task, the supplementary subtask, and the unit mileage feedback content corresponding to the original collection task and the supplementary subtask respectively.

7. The device according to claim 6, wherein: The unit mileage feedback content determination unit is used to determine the original feedback content preset for the original collection task; allocate the original feedback content to the original collection task and the supplementary subtask to obtain the unit mileage feedback content corresponding to the original collection task and the unit mileage feedback content corresponding to the supplementary subtask.

8. The device according to claim 6 or 7, further comprising: An execution data receiving module, used for receiving the execution data sent by the requesting party; The execution data is generated by the requesting party executing the road data collection task; The feedback content determination module is used to determine the target content to be fed back to the requesting party based on the execution data and the unit mileage feedback content corresponding to the road data collection task.

9. The device according to claim 8, wherein: The feedback content determination module includes: a mileage determination unit, configured to determine the mileage corresponding to the road data collection task based on the execution data; A calculation unit is used to determine the target content to be fed back to the requesting party based on the driving mileage and the unit mileage feedback content corresponding to the road data collection task.

10. The device according to claim 9, wherein: The execution data includes a positioning point and a speed corresponding to the positioning point; The mileage determination unit is used to determine multiple target positioning points for calculating the mileage based on the speeds corresponding to the positioning points; and determine the mileage corresponding to the road data collection task based on the distance between every two adjacent target positioning points among the multiple target positioning points.

11. An electronic device, comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 5.

12. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to make a computer execute the method according to any one of claims 1-5.

13. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 5.

Images