Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary only for explaining the present application and are not to be construed as limiting the present application.
The following disclosure provides many different embodiments, or examples, for implementing different features of the application. In order to simplify the present disclosure, components and arrangements of specific examples are described below. They are, of course, merely examples and are not intended to limit the application. Furthermore, the present application may repeat reference numerals and/or letters in the various examples, which are for the purpose of brevity and clarity, and which do not themselves indicate the relationship between the various embodiments and/or arrangements discussed.
The crowdsourcing parking routes are parking routes of vehicles collected in a crowdsourcing mode, and the routes are stored in a server, so that the number of existing crowdsourcing parking routes is huge due to the increasing number of crowdsourcing parking routes.
In the automatic parking process of the vehicle, the acquisition of the crowdsourcing parking route nearby the vehicle is beneficial to improving the parking success rate, however, how to quickly acquire the required parking route from the crowdsourcing parking route with huge base is a problem to be solved.
According to the method, the device, the equipment and the storage medium for generating the parking route list, which are provided by the embodiment of the application, can be used for quickly generating the target parking route list comprising a plurality of target parking routes, and the target running data of each target parking route is stored in the corresponding target parking route list, so that the automatic parking can be realized by utilizing the target parking route list in an auxiliary way, and the parking experience of a user can be improved.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.
Referring to fig. 1, an application scenario schematic diagram of a parking route list generating system provided by the embodiment of the application is shown, which includes a server 100 and a vehicle 200, where the server 100 and the vehicle 200 may communicate through a vehicle network, and the server 100 may receive driving data of a plurality of parking routes sent by the vehicle 200 through the vehicle network, and store the driving data to a parking route list corresponding to the parking information according to the parking information corresponding to each parking route.
The server 100 may be a storage type cloud platform, a computing type cloud platform, a comprehensive cloud computing platform, and the like; the internet of vehicles may be a wireless wide area network (Wireless Wide Area Network, WWAN), a wireless local area network (Wireless Local Area Network, WLAN), a wireless metropolitan area network (Wireless Metropolitan Area Network, WMAN), a wireless personal area network (Wireless Personal Area Network, WPAN), etc.; the types of the server 100 and the internet of vehicles are not limited herein, and may be specifically set according to actual requirements.
The vehicle 200 may be any vehicle or vehicles that have received a parking lot mapping task, and the vehicle 200 may transmit traveling data of a parking route to which the vehicle is parked to the parking space to the server 100. The vehicle 200 may include a professional surveying vehicle on which a high-precision sensor is mounted, a mass-production vehicle sold to a consumer, or the like, and is not limited in type to the vehicle 200, and may be specifically set according to actual demands.
Referring to fig. 2, a flowchart of a parking route list generating method according to an embodiment of the application is shown. In a specific embodiment, the parking route list generation method may be applied to the server 100 in the parking route list generation system shown in fig. 1, and the flow shown in fig. 2 will be described in detail below by taking the server 100 as an example, and the parking lot entry generation method may include the following steps S110 to S130.
Step S110: and acquiring driving data of a plurality of parking routes.
In the embodiment of the application, the vehicle can collect the running data of a plurality of parking routes for parking to the parking space, the collected running data can be sent to the server, the server can receive the running data sent by the vehicle, and one running data corresponds to one parking route.
The parking route may be a first travel route in which the vehicle travels from the entrance of the parking lot to the parking space, or a second travel route in which the vehicle travels from outside to the parking space. The first driving route and the second driving route can be real-time routes acquired by sensors of the vehicle, and can also be silent routes generated by a central control screen of the vehicle, and the silent routes are obtained based on fusion of the real-time routes and the map.
The driving data may be perceived data corresponding to the real-time route or map data corresponding to the silent route. The travel data may include, but is not limited to: frame number (Vehicle Identification Number, VIN), parking start position, parking end position, parking lot entrance position, floor, elevator hoistway position, provincial area name, parking route length, upload date, route status (e.g., shared, downloaded, recommended, deleted, marked blacklist, etc.), number of downloads, score, building name, building geographic location, global positioning system (Global Positioning System, GPS) signal, identification of parking lot barrier, parking space detection, parking down identification, parking lot image, attitude angle, vehicle speed, obstacle distance, etc.
In some embodiments, the vehicle may include a sensor that may communicate with the server via the internet of vehicles, the sensor may be used to collect sensory data during travel of the vehicle, and the travel data may be transmitted to the server via the internet of vehicles. The sensor can collect sensing data of a plurality of parking routes from the vehicle to the parking space, the sensing data can be sent to the server through the internet of vehicles, and the server can receive the sensing data of the plurality of parking routes sent by the sensor and serve as corresponding driving data.
The sensor may include at least any one of a GPS sensor, a camera, an inertial measurement unit (Inertial Measurement Unit, IMU), a wheel speed meter, an odometer, an ultrasonic radar, a lidar, a millimeter wave radar, and the like.
In some embodiments, the vehicle may include a central control screen, which may communicate with the server via the internet of vehicles, and the central control screen may be used to fuse the real-time route collected by the sensor with the map, generate a silent route, and obtain map data. The central control screen can fuse a plurality of parking routes acquired by the sensor with the map to generate a plurality of corresponding silent routes, one silent route corresponds to one parking route, the central control screen can send map data of the plurality of silent routes to the server through the internet of vehicles, and the server can receive the map data of the plurality of parking routes sent by the central control screen and serve as corresponding driving data.
Step S120: based on the traveling data, a target parking route satisfying a preset condition is determined from among the plurality of parking routes.
In the embodiment of the application, the perceived data acquired by the sensor have deviation in the parking process, so that the server can determine the target parking route meeting the preset condition from a plurality of parking routes based on the driving data, thereby realizing the preliminary screening of the parking routes. The preset condition can be that the parking route is smooth, and the parking route is indicated that road maintenance or road barriers arranged in epidemic situation management and control are not existed; the preset condition may also be that the parking route is not drifting, which means that the deviation of the driving data of the parking route is small.
In some embodiments, the driving data may include a parking start position and a parking end position, and the preset condition may be a smooth parking route. The server may search a map according to a parking start position and a parking end position of each parking route to obtain a corresponding map route, determine that the corresponding parking route satisfies the smooth progress of the parking route when the obtained map route is not marked as having a roadblock, and determine the parking route as a target parking route. Wherein, the map can be a database provided by a map service provider for inquiring geographic information, and the geographic information can comprise map routes, map positions and the like.
In some embodiments, the driving data may include a parking lot entrance position and a parking end position, and the preset condition may be that the parking route is not shifted. The server may calculate a position difference between the parking lot entrance position and the parking end position of each parking route, compare the position difference with a difference threshold, and when the position difference is less than or equal to the difference threshold, indicate that the parking lot entrance position is near the parking end position, may determine that the corresponding parking route satisfies the parking route without drifting, and determine the parking route as the target parking route.
Step S130: and determining target parking information corresponding to the target parking route.
In the embodiment of the application, the server can determine the target parking information corresponding to the target parking route according to the target parking route, wherein the target parking information can comprise at least any one of route coding information, vehicle identification, parking lot identification information and the like corresponding to the target parking route, and each vehicle has unique different identification so as to establish a corresponding target route list according to the target parking information.
In some embodiments, the target parking information may include a vehicle identification and the target travel data may include a VIN of the vehicle. The server can obtain VINs corresponding to the target parking route according to the target driving data of the target parking route, and generate corresponding vehicle identification marks according to the VINs, wherein the vehicle identification marks cannot be reversely analyzed to obtain the corresponding VINs, so that the vehicle privacy leakage caused by the exposure of the VINs can be avoided, and the safety of vehicle information can be improved.
In some embodiments, the target parking information may include parking lot identification information (Identity, ID), and the target travel data may include a parking lot entry location. The server may obtain a parking lot entry position corresponding to the target parking route according to target driving data of the target parking route, and may find a preset parking lot database according to the parking lot entry position to obtain a parking lot ID corresponding to the parking lot entry position, where the parking lot entry position may be a position where a global positioning system (Global Positioning System, GPS) signal corresponding to the target parking route disappears, that is, a longitude and latitude coordinate where the GPS signal disappears, for example, if the longitude and latitude coordinate where the GPS signal corresponding to the target parking route disappears is (113 ° 23'25",23 ° 17' 35"), the parking lot entry position corresponding to the target parking route is (113 ° 23'25",23 ° 17' 35"); if the longitude and latitude coordinates of the disappearance of the GPS signal corresponding to the target parking route are (114 ° 7'20",22 ° 15' 32"), the parking lot entry position corresponding to the target parking route is (114 ° 7'20",22 ° 15' 32") or the like. The preset parking lot database can be a database generated by clustering parking lot entrance positions corresponding to the crowdsourcing routes in advance by a server, and can be used for representing the corresponding relation between the parking lot entrance positions and the parking lot IDs.
For example, the correspondence between the parking lot entrance positions and the parking lot IDs may be as shown in table 1, that is, a preset parking lot database, and the parking lot IDs corresponding to the different parking lot entrance positions are shown in table 1, and the parking lot IDs corresponding to the parking lot entrance positions may be obtained from the correspondence.
TABLE 1
Parking lot entrance position
|
Parking lot ID
|
(113°21’50”,23°29’19”)
|
A parking lot
|
(113°32’27”,23°13’39”)
|
B parking lot
|
(114°10’25”,22°15’32”)
|
C parking lot |
The correspondence between the parking lot entrance position and the parking lot ID is not limited to that shown in table 1, and may be set according to actual needs.
In some embodiments, the target parking information may include route code information, and the server may encode the target parking route according to a preset encoding rule to obtain corresponding route code information.
As an example, the preset encoding rule may be a chronological order in which the server receives the target travel data. The server can sequentially encode the target parking route corresponding to each item of target driving data according to the sequence of receiving the target driving data, and corresponding route encoding information is obtained.
For example, the vehicle respectively transmits target driving data of one target parking route to the server at 10 minutes and 0 seconds of 10 days of 2021, 12 months of 2021, 10 minutes and 5 seconds of 10 days of 20 days of 2021, 12 months of 2021, 10 minutes and 10 seconds of 10 days of 20 days of 2021, 12 months of 2021, 10 minutes and 15 seconds of 10 days of 20 days of 2021 and 20 minutes and 20 seconds of 2021 through the internet of vehicles, the server receives and responds to the target driving data transmitted by the vehicle, and can encode the target parking route corresponding to the target driving data received at 10 minutes and 0 seconds of 10 days of 2021, 12 months of 2021, 20 days of 10 minutes and 0 seconds to obtain corresponding route encoding information of 1#, encoding a target parking route corresponding to target traveling data received by 10 points 0 minutes 5 seconds in 12 months of 2021 to obtain corresponding route encoding information as 2#, encoding a target parking route corresponding to target traveling data received by 10 points 0 minutes 10 seconds in 12 months of 2021 to obtain corresponding route encoding information as 3#, encoding a target parking route corresponding to target traveling data received by 10 points 0 minutes 15 seconds in 12 months of 2021 to obtain corresponding route encoding information as 4#, and encoding a target parking route corresponding to target traveling data received by 10 points 0 minutes 20 seconds in 12 months of 2021 to obtain corresponding route encoding information as 5#. The time of receiving the target travel data and the numerical value of the route code information are not limited here, and may be specifically set according to actual demands.
As another example, the preset encoding rule may also be a time sequence in which the server receives the target driving data, and a vehicle identity corresponding to the target driving data. The server can encode the multi-item standard parking route corresponding to the same identity mark according to the time sequence of receiving the target driving data corresponding to the multi-item standard parking route, and obtain corresponding route encoding information.
As another example, the preset encoding rule may also be a time sequence in which the server receives the target driving data, and a parking lot ID corresponding to the target driving data. The server can encode the multi-item target parking route corresponding to the same parking lot ID according to the time sequence of receiving the target running data corresponding to the multi-item target parking route, and obtain corresponding route encoding information.
Step S140: and storing the target driving data of the target parking route into a target parking route list corresponding to the target parking information.
In the embodiment of the application, after the target parking information corresponding to the target parking route is determined, the server can establish the target parking route list corresponding to the target parking information, and can store the target running data of the target parking route to the target parking route list corresponding to the target parking information, so that the target parking route list comprising a plurality of target parking routes can be quickly generated, and the target running data of each target parking route is stored in the corresponding target parking route list, thereby being beneficial to realizing automatic parking by utilizing the target parking route list.
In some implementations, the target parking information may include route encoding information. After the server encodes the target parking route according to the preset encoding rule and obtains the corresponding route encoding information, the server may establish a target parking route list corresponding to the route encoding information, and may store target driving data of the target parking route to the target parking route list corresponding to the route encoding information, where the target driving data corresponds to the route encoding information.
The target parking route list corresponding to the route encoding information is indexed according to the route encoding information, and the target parking route list may be used to store some attributes corresponding to the target driving data, where the attributes may include, but are not limited to: vehicle identification, province area name, building name, parking lot entrance location, parking spot information, route length, upload date, route status, number of downloads, score, etc.
In some implementations, the target parking information may include a vehicle identification. The server may establish a target parking route list corresponding to the vehicle identity after acquiring the VIN corresponding to the target parking route according to the target driving data of the target parking route and generating the corresponding vehicle identity according to the VIN, and may store the target driving data of the target parking route to the target parking route list corresponding to the vehicle identity, where the target driving data corresponds to the vehicle identity.
The target parking route list corresponding to the vehicle identity is indexed according to the vehicle identity, and the target parking route list can be used for storing some attributes of the vehicle corresponding to the target driving data, wherein the attributes can include but are not limited to: shared route, downloaded route, accessed parking lot, resident province city name, praise route, etc.
In some implementations, the target parking information may include a parking lot ID. The server obtains the parking lot entrance position corresponding to the target parking line according to the target driving data of the target parking line, searches a preset parking lot database according to the parking lot entrance position, and after obtaining the parking lot ID corresponding to the parking lot entrance position, can establish a target parking line list corresponding to the parking lot ID, and can store the target driving data of the target parking line to the target parking line list corresponding to the parking lot ID, wherein the target driving data corresponds to the parking lot ID.
The target parking route list corresponding to the parking lot ID is indexed by the parking lot ID, and may be used to store some attributes of the parking lot corresponding to the target driving data, which may include, but are not limited to: parking lot IDs, provincial area names, building geographic locations, routes shared by parking lots, vehicles shared by parking lots by routes, vehicles accessed by parking lots, parking lot maturity, and the like. The maturity of the parking lot can be positively correlated with the number of parking lines related to the corresponding parking lot, and the higher the number of parking lines related to the parking lot is, the higher the maturity of the parking lot is.
In some embodiments, after storing the target traveling data of the target parking route in the target parking route list corresponding to the target parking information, the server may receive the current traveling data of the current parking route sent by the current vehicle, determine the current parking information corresponding to the current parking route when the current parking route meets the preset condition, and store the current traveling data in the current target parking route list corresponding to the current parking information, thereby implementing timely update of the target parking route list. The current parking information may be the same as the target parking information, or may be different from the target parking information.
In some embodiments, after storing the target traveling data of the target parking route in the target parking route list corresponding to the target parking information, the server may receive a route query request sent by the vehicle, where the route query request is associated with the target parking information, and in response to the route query request, query the target parking route list corresponding to the target parking information, obtain a corresponding query parking route, and return the query parking route to the vehicle, so that the vehicle realizes automatic parking according to the assistance of the target parking route, and a parking experience of a user is improved.
As one embodiment, the inquiry parking lines may be plural, and the plurality of inquiry parking lines may indicate that the inquiry condition is satisfied. The server can acquire scoring values corresponding to the multiple query parking routes, the scoring values are obtained based on experience evaluation of the user on the target parking route, the multiple query parking routes are ranked according to the descending order of the scoring values, and the query parking route with the highest scoring value is returned to the vehicle, so that the vehicle can realize automatic parking according to the optimal query parking route assistance, and the parking experience of the user is improved.
In some embodiments, the target parking route needs to be protected, i.e., cannot be shared, when the target parking route includes a residential area or the like. Therefore, after storing the target driving data of the target parking route to the target parking route list corresponding to the target parking information, the server can establish a blacklist according to a preset list establishment rule, wherein the blacklist can be used for closing the query function of the target parking route list when receiving the route query request corresponding to the blacklist sent by the vehicle, thereby realizing the filtering of the route query request and improving the privacy protection of the target parking route.
The blacklist may be used for storing preset keywords, closing a query function of the target parking route list when a route query request including the preset keywords sent by the vehicle is received, that is, returning a failed or wrong route query result to the vehicle, and searching a target parking route corresponding to the target parking information in the target parking route list corresponding to the target parking information according to a corresponding relation between the route query request and the target parking information when the route query request not including the preset keywords is received, and returning the target parking route to the vehicle. The keyword may include at least any one of "garden", "cell", and the like.
According to the scheme provided by the application, the driving data of a plurality of parking lines are acquired, the target parking line meeting the preset condition is determined from the plurality of parking lines based on the driving data, the target parking information corresponding to the target parking line is determined, the target parking information comprises at least any one of the route coding information corresponding to the target parking line, the vehicle identity and the parking lot identity information, and the target driving data of the target parking line is stored in the target parking line list corresponding to the target parking information, so that the target parking line list comprising a plurality of target parking lines can be quickly generated, and the target driving data of each target parking line is stored in the corresponding target parking line list, thereby being beneficial to realizing automatic parking by utilizing the assistance of the target parking line list and improving the parking experience of users.
Referring to fig. 3, a flowchart of a parking route list generating method according to another embodiment of the present application is shown. In a specific embodiment, the parking route list generation method may be applied to the server 100 in the parking route list generation system shown in fig. 1, and the flow shown in fig. 3 will be described in detail below by taking the server 100 as an example, and the parking lot entry generation method may include the following steps S210 to S270.
Step S210: and acquiring driving data of a plurality of parking routes.
Step S220: based on the traveling data, a target parking route satisfying a preset condition is determined from among the plurality of parking routes.
Step S230: and determining target parking information corresponding to the target parking route.
Step S240: and storing the target driving data of the target parking route into a target parking route list corresponding to the target parking information.
In this embodiment, the steps S210, S220, S230 and S240 may refer to the content of the corresponding steps in the foregoing embodiments, which is not described herein.
Step S250: and searching a preset space database according to the parking lot ID corresponding to the target parking route, and obtaining the geographic position corresponding to the parking lot ID.
In this embodiment, after storing the target driving data of the target parking route in the target parking route list corresponding to the target parking information, the server may search a preset spatial database according to the parking lot ID corresponding to the target parking route, to obtain the geographic position corresponding to the parking lot ID, where the spatial database may be used to characterize the correspondence between the parking lot ID and the geographic position.
For example, the correspondence between the parking lot IDs and the geographic positions may be as shown in table 2, that is, a preset spatial database, and the geographic positions corresponding to the different parking lot IDs are shown in table 2, and the geographic positions corresponding to the parking lot IDs may be obtained according to the correspondence.
TABLE 2
Parking lot ID
|
Geographic location
|
A parking lot
|
G province X city M district S way No. 230
|
B parking lot
|
N area T-way 134 number of Y-City of G province
|
C parking lot
|
W-way No. 99 in Z-City O area of H province |
Note that, the correspondence between the parking lot ID and the geographic position is not limited to those shown in table 2, and may be specifically set according to actual requirements.
Step S260: and superposing the target parking route and the map to obtain the map position of the parking lot ID corresponding to the target parking route.
In this embodiment, the server may superimpose the target parking route, the parking lot ID corresponding to the target parking route, and the map to find the position of the parking lot ID in the map, and use the position as the map position of the parking lot ID.
Step S270: and sending the geographic position and the map position to a quality inspection person so that the quality inspection person can check whether the geographic position and the map position respectively corresponding to the target parking route are consistent.
In this embodiment, the server may send the geographic location and the map location corresponding to the parking lot ID to the quality inspector, and the quality inspector may check whether the geographic location and the map location corresponding to the target parking route are consistent according to the received geographic location and the map location, and when determining that the geographic location and the map location are inconsistent, may send correction information to the server, and the server may receive the correction information and correct the geographic location, so as to ensure accuracy of the target parking route list.
In some embodiments, when the quality inspector determines that the geographic position corresponding to the parking lot ID is inconsistent with the map position, the geographic position may be corrected, the corresponding target parking route is marked, and the marked target parking route is updated to the corresponding target parking route list.
As an example, when the quality inspector determines that the geographic position corresponding to the parking lot ID deviates greatly from the map position, it may be determined that the geographic position corresponding to the parking lot ID does not coincide with the map position. As another example, when the quality inspector determines that the driving data of the parking route corresponding to the parking lot ID is wrong or empty, it may be determined that the geographic position corresponding to the parking lot ID does not coincide with the map position.
According to the scheme provided by the embodiment, a preset space database is searched according to the parking lot ID corresponding to the target parking route, the geographic position corresponding to the parking lot ID is obtained, the target parking route is overlapped with the map, the map position of the parking lot ID corresponding to the target parking route is obtained, the geographic position and the map position are sent to the quality inspection personnel, so that the quality inspection personnel can check whether the geographic position corresponding to the target parking route is consistent with the map position or not, and when the geographic position is inconsistent with the map position, correction information sent by the quality inspection personnel is received, and the geographic position is corrected, so that the accuracy of a target parking route list can be ensured.
Referring to fig. 4, which illustrates a parking route list generating apparatus 400 according to an embodiment of the present application, the parking route list generating apparatus 400 may be applied to a server 100 in a parking route list generating system as illustrated in fig. 1, and hereinafter, the parking route list generating apparatus 400 illustrated in fig. 4 will be described in detail by taking the server 100 as an example, and the parking route list generating apparatus 400 may include an acquisition module 410, a first determination module 420, a second determination module 430, and a storage module 440.
The obtaining module 410 may be configured to obtain driving data of a plurality of parking routes; the first determining module 420 may be configured to determine a target parking route satisfying a preset condition from among a plurality of parking routes based on the driving data; the second determining module 430 may be configured to determine target parking information corresponding to a target parking route, where the target parking information includes at least any one of route code information, a vehicle identification, and parking lot identification information corresponding to the target parking route; the storage module 440 may be configured to store target travel data of a target parking route to a target parking route list corresponding to target parking information, where the target parking route list is configured to query the corresponding target parking route according to the target parking information.
In some embodiments, the driving data includes a parking start position and a parking end position, and the first determining module 420 may include a first searching unit and a first determining unit if the preset condition is that the parking route is smooth.
The first searching unit can be used for searching a map according to the parking start position and the parking end position of each parking route to obtain a corresponding map route; the first determining unit may be configured to determine that the corresponding parking route satisfies the smooth progress of the parking route when the map route is not indicated to have the roadblock, and determine the parking route as the target parking route.
In some embodiments, the driving data includes a parking lot entrance position and a parking end position, and the first determining module 420 may further include a calculating unit and a second determining unit if the preset condition is that the parking route is not drifting.
The calculation unit may be configured to calculate a position difference between a parking lot entrance position and a parking end position of each of the parking routes; the second determining unit may be configured to determine that the corresponding parking route satisfies the parking route without drifting when the position difference is less than or equal to the difference threshold, and determine the parking route as the target parking route.
In some embodiments, the target parking information includes route encoding information, and the second determination module 430 may include an encoding unit.
The coding unit may be configured to code the target parking route according to a preset coding rule, so as to obtain corresponding route coding information.
In some embodiments, the target parking information includes a vehicle identification, and the second determining module 430 may further include a first obtaining unit and a generating unit.
The first obtaining unit may be configured to obtain a frame number of a vehicle corresponding to the target parking route; the generating unit may be configured to generate a corresponding vehicle identification according to the frame number.
In some embodiments, the target parking information includes parking lot identification information, and the second determining module 430 may further include a second obtaining unit and a second finding unit.
The second obtaining unit may be configured to obtain a parking lot entry position corresponding to the target parking route; the second searching unit may be configured to search a preset parking lot database according to the parking lot entrance position, to obtain parking lot identification information corresponding to the parking lot entrance position, where the preset parking lot database is used for representing a correspondence between the parking lot entrance position and the parking lot identification.
In some embodiments, the acquisition module 410 may include a first receiving unit, or/and a second receiving unit.
The first receiving unit may be configured to receive, as the driving data, sensing data of a plurality of parking routes acquired by sensors of the vehicle; the second receiving unit may be configured to receive map data of a plurality of parking routes uploaded by a center control screen of the vehicle as the traveling data.
In some embodiments, the parking route list generating device 400 may further include an establishment module.
The establishing module may be configured to establish a blacklist, where the blacklist is configured to close a query function of the target parking route list when a route query request corresponding to the blacklist is received.
In some embodiments, the parking route list generating apparatus 400 may further include a lookup module, an overlay module, and a transmission module.
The searching module may be configured to, after the storing module 440 stores the target driving data of the target parking route in the target parking route list corresponding to the target parking information, search a preset spatial database according to the parking lot identification information corresponding to the target parking route, to obtain a geographic location corresponding to the parking lot identification information, where the spatial database is used to characterize a correspondence between the parking lot identification information and the geographic location; the superposition module can be used for superposing the target parking route and the map to obtain the map position of the parking lot identification information corresponding to the target parking route; the sending module may be configured to send the geographic location and the map location to a quality inspector, so that the quality inspector inspects whether the geographic location and the map location respectively corresponding to the target parking route are consistent.
In some embodiments, the parking route list generating device 400 may further include a receiving module, a query module, and a return module.
The receiving module may be configured to receive a route query request sent by the vehicle after the storage module 440 stores target travel data of the target parking route in the target parking route list corresponding to the target parking information, where the route query request is associated with the target parking information; the inquiring module can be used for responding to the route inquiring request, inquiring a target parking route list corresponding to the target parking information, and obtaining an inquired parking route; the return module may be configured to return the query parking route to the vehicle.
In some embodiments, the query parking route may be plural, and the return module may include a third acquisition unit, a ranking unit, and a return unit.
The third obtaining unit may be configured to obtain scoring values corresponding to the multiple query parking routes, where the scoring values are obtained based on experience evaluation of the user on the target parking route; the ranking unit may be configured to rank the plurality of inquiry parking routes in order of low-to-high score values; the return unit may be configured to return the inquiry parking route having the highest score value to the vehicle.
According to the scheme provided by the application, the driving data of a plurality of parking lines are acquired, the target parking line meeting the preset condition is determined from the plurality of parking lines based on the driving data, the target parking information corresponding to the target parking line is determined, the target parking information comprises at least any one of route coding information, vehicle identification and parking lot identification information corresponding to the target parking line, the target driving data of the target parking line is stored in the target parking line list corresponding to the target parking information, the target parking line list is used for inquiring the corresponding target parking line according to the target parking information, the target parking line list comprising the target parking lines with multiple entries can be quickly generated, and the target driving data of each target parking line is stored in the corresponding target parking line list, so that automatic parking can be realized by utilizing the target parking line list in an auxiliary mode, and the experience of a user can be improved.
It should be noted that, in the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described as different from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other. For the apparatus class embodiments, the description is relatively simple as it is substantially similar to the method embodiments, and reference is made to the description of the method embodiments for relevant points. Any of the described processing manners in the method embodiment may be implemented by a corresponding processing module in the device embodiment, which is not described in detail in the device embodiment.
In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in software functional modules.
Referring to fig. 5, a functional block diagram of a parking route list generating apparatus 500 according to another embodiment of the present application is shown, where the parking route list generating apparatus 500 may include one or more of the following components: memory 510, processor 520, and one or more applications, wherein the one or more applications may be stored in memory 510 and configured to be executed by the one or more processors 520, the one or more applications configured to perform the method as described in the foregoing method embodiments.
The Memory 510 may include a random access Memory (Random Access Memory, RAM) or a Read-Only Memory (Read-Only Memory). Memory 510 may be used to store instructions, programs, code sets, or instruction sets. The memory 510 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (such as obtaining travel data, determining a target parking route, determining target parking information, storing target travel data, finding a map, obtaining a map route, determining that a parking route meets a parking route penetration, calculating a position difference, determining that a parking route meets a parking route without drifting, encoding a target parking route, obtaining a frame number, generating a vehicle identity, obtaining a parking lot entry location, finding a preset parking lot database, receiving awareness data, receiving map data, establishing a blacklist, closing a query function, finding a spatial database, obtaining a geographic location, superimposing a target parking route with a map, obtaining a map location, sending a geographic location and a map location, receiving a query request, responding to a query request, querying a target parking route list, and returning a query parking route, etc.), instructions for implementing various method embodiments described below, and the like. The stored data area may also store data created by the parking route list generating device 500 in use (such as travel data, preset conditions, target parking routes, target parking information, route code information, vehicle identification, parking lot identification information, target travel data, target parking route list, parking start position, parking end position, parking route in-progress, map route, roadblock, parking route unbiased, position difference value, difference threshold value, coding rule, frame number, parking lot entry position, parking lot database, correspondence, awareness data, map data, blacklist, route query request, query function, spatial database, geographic position, map position, quality inspector, query parking route, score value, and order), and the like.
Processor 520 may include one or more processing cores. The processor 520 connects various parts within the overall parking route list generating device 500 using various interfaces and lines, and performs various functions and processes of the parking route list generating device 500 by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 510, and invoking data stored in the memory 510. Alternatively, the processor 520 may be implemented in hardware in at least one of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 520 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), and a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for being responsible for rendering and drawing of display content; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 520 and may be implemented solely by a single communication chip.
Referring to fig. 6, a block diagram of a computer readable storage medium according to an embodiment of the application is shown. The computer readable storage medium 600 has stored therein program code 610, the program code 610 being executable by a processor to perform the method described in the above method embodiments.
The computer readable storage medium 600 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer readable storage medium 600 comprises a non-volatile computer readable medium (non-transitory computer-readable storage medium). The computer readable storage medium 600 has storage space for program code 610 that performs any of the method steps described above. The program code can be read from or written to one or more computer program products. Program code 610 may be compressed, for example, in a suitable form.
According to the scheme provided by the application, the driving data of a plurality of parking lines are acquired, the target parking line meeting the preset condition is determined from the plurality of parking lines based on the driving data, the target parking information corresponding to the target parking line is determined, the target parking information comprises at least any one of route coding information, vehicle identification and parking lot identification information corresponding to the target parking line, the target driving data of the target parking line is stored in the target parking line list corresponding to the target parking information, the target parking line list is used for inquiring the corresponding target parking line according to the target parking information, the target parking line list comprising the target parking lines with multiple entries can be quickly generated, and the target driving data of each target parking line is stored in the corresponding target parking line list, so that automatic parking can be realized by utilizing the target parking line list in an auxiliary mode, and the experience of a user can be improved.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application has been described in detail with reference to the foregoing embodiments, it will be appreciated by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not drive the essence of the corresponding technical solutions to depart from the spirit and scope of the technical solutions of the embodiments of the present application.