CN113135178A - Parking route sharing method, device, equipment and storage medium - Google Patents

Parking route sharing method, device, equipment and storage medium Download PDF

Info

Publication number
CN113135178A
CN113135178A CN202110453459.7A CN202110453459A CN113135178A CN 113135178 A CN113135178 A CN 113135178A CN 202110453459 A CN202110453459 A CN 202110453459A CN 113135178 A CN113135178 A CN 113135178A
Authority
CN
China
Prior art keywords
user
parking route
route
target parking
sharing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110453459.7A
Other languages
Chinese (zh)
Inventor
李欣静
魏鹏飞
宋佳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Baidu Netcom Science and Technology Co Ltd
Original Assignee
Beijing Baidu Netcom Science and Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Baidu Netcom Science and Technology Co Ltd filed Critical Beijing Baidu Netcom Science and Technology Co Ltd
Priority to CN202110453459.7A priority Critical patent/CN113135178A/en
Publication of CN113135178A publication Critical patent/CN113135178A/en
Priority to PCT/CN2022/071788 priority patent/WO2022227711A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W30/00Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
    • B60W30/06Automatic manoeuvring for parking
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W60/00Drive control systems specially adapted for autonomous road vehicles
    • B60W60/001Planning or execution of driving tasks
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2556/00Input parameters relating to data
    • B60W2556/45External transmission of data to or from the vehicle

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Human Computer Interaction (AREA)
  • Traffic Control Systems (AREA)
  • Navigation (AREA)

Abstract

The present disclosure provides a parking route sharing method, apparatus, electronic device, non-transitory computer-readable storage medium, and computer program product, which relate to the field of automatic driving technologies, and in particular, to the field of autonomous parking technologies. The parking route sharing method includes: receiving a route acquisition request sent by a second user side based on a shared link of a target parking route, wherein the shared link is shared by the first user side; and sending the target parking route to the second user end so that the second user end carries out parking based on the target parking route. The invention provides a parking route sharing method for memory parking users, which improves the application rate of the parking route of a single user and reduces the learning cost of the parking routes of other users.

Description

Parking route sharing method, device, equipment and storage medium
Technical Field
The present disclosure relates to the field of automated driving techniques, and more particularly, to the field of autonomous parking techniques.
Background
In order to solve the parking requirement of the last kilometer in an open scene, the memory parking function is developed. The user only needs to finish the learning of the parking route according to the system prompt, and the vehicle can realize the autonomous parking according to the learned parking route in the subsequent use. Data collected by cameras and sensors around a vehicle body during parking is memorized, a scene map is constructed by a visual SLAM (Simultaneous localization and mapping) technology, and high-precision localization can be realized without depending on a high-precision map.
At present, memory parking requires a user to build a parking route, and parking is carried out by using the self-built parking route.
Disclosure of Invention
The present disclosure proposes a parking route sharing method, apparatus, electronic device, non-transitory computer-readable storage medium, and computer program product.
In a first aspect, an embodiment of the present disclosure provides a parking route sharing method, including: receiving a route acquisition request sent by a second user side based on a shared link of a target parking route, wherein the shared link is shared by the first user side; and sending the target parking route to the second user end to instruct the second user end to park based on the target parking route.
In a second aspect, an embodiment of the present disclosure provides a parking route sharing device, including: the system comprises a first receiving module, a second receiving module and a third receiving module, wherein the first receiving module is configured to receive a route obtaining request sent by a second user terminal based on a shared link of a target parking route, and the shared link is shared by the first user terminal; and the sending module is configured to send the target parking route to the second user end so as to instruct the second user end to park the vehicle based on the target parking route.
In a third aspect, an embodiment of the present disclosure provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method as described in any one of the implementations of the first aspect.
In a fourth aspect, the disclosed embodiments propose a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the method as described in any one of the implementations of the first aspect.
In a fifth aspect, the present disclosure provides a computer program product, which includes a computer program that, when executed by a processor, implements the method described in any of the implementation manners in the first aspect, or implements the method described in any of the implementation manners in the second aspect.
The embodiment of the disclosure provides a parking route sharing method for memory parking users, and a parking route of a single user can be shared by other users. Therefore, the parking route originally used by only a single user can be shared by other users. The application rate of the parking route of a single user is improved, the learning cost of the parking routes of other users is reduced, and the practicability of memory parking is further improved. In addition, in the process of sharing the parking route, the first user interacts with the second user, and social attributes of memory parking are increased.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
Other features, objects, and advantages of the disclosure will become apparent from a reading of the following detailed description of non-limiting embodiments which proceeds with reference to the accompanying drawings. The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is an exemplary system architecture diagram of an application scenario of the present disclosure;
FIG. 2 is a flow chart of one embodiment of a parking route sharing method of the present disclosure;
FIG. 3 is a flow chart of yet another embodiment of a parking route sharing method of the present disclosure;
FIG. 4 is a timing diagram of one embodiment of sharing a shared link;
FIG. 5 is a timing diagram of one embodiment of determining a shared link;
FIG. 6 is a timing diagram of one embodiment of issuing parking routes;
FIG. 7 is a scene diagram of one embodiment of parking route reconstruction;
FIG. 8 is a schematic structural diagram of an embodiment of a parking route sharing apparatus of the present disclosure;
fig. 9 is a block diagram of an electronic device for implementing the parking route sharing method of the embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary system architecture 100 for an application scenario of the present disclosure.
As shown in fig. 1, the system architecture 100 may include a first user side 101, a second user side 102, a network 103, and a cloud side 104. The network 103 is used to provide a medium for communication links between the first user terminal 101, the second user terminal 102, and the cloud 104. Network 103 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few. The first user terminal 101 may include a first user terminal 1011 and a first user cart end 1012. The second user terminal 102 may include a second user terminal 1021 and a second user cart terminal 1022. Cloud 104 may include a cloud user management system 1041 and a cloud map management system 1042.
The first user 101 may share its parking route with the second user 102 through the cloud 104 for the second user 102 to park.
The cloud 104 may store the parking route of the first user end 101, and send the parking route of the first user end 101 to the second user end 102 when receiving the route acquisition request of the second user end 102.
It should be noted that the parking route sharing method provided by the embodiment of the disclosure is generally executed by the cloud end 104, and accordingly, the parking route sharing device is generally disposed in the cloud end 104.
It should be understood that the number of first clients, second clients, and cloud in fig. 1 is merely illustrative. According to implementation needs, any number of first user terminals, second user terminals and cloud terminals can be provided.
With continued reference to FIG. 2, a flow chart 200 illustrating one embodiment of the parking route sharing method of the present disclosure is shown. The parking route sharing method comprises the following steps:
step 201, receiving a route acquisition request sent by a second user end based on a shared link of a target parking route.
In this embodiment, the first user may share the shared link of the target parking route. If the second user side acquires the shared link, a route acquisition request can be sent to the cloud side based on the shared link.
Here, the target parking route may be a parking route of the first user, including but not limited to a parking route learned based on data collected by the first user, a parking route downloaded by the first user, and so on. The parking route downloaded by the first user end can be a parking route of other user ends. Generally, parking routes shared by other clients are stored in the cloud, and the first client can download from the cloud. The parking route learned based on the data collected by the first user side can be learned by the first user side and also can be learned by the cloud side. Generally, if the current network condition is better, the data collected by the first user side can be sent to the cloud side, and the cloud side learns the parking route. If the current network condition is poor, the first user end can learn the parking route. And when the network condition is better, the parking route is sent to the cloud.
Here, the shared link of the target parking route may be generated based on the summary information of the target parking route. In order to save the storage space of the user terminal, the summary information of the parking route can be stored in the cloud. At this time, the first user side may send a summary information acquisition request of the target parking route to the cloud side. The summary information acquisition request may include an identifier of the target parking route. The cloud end can index summary information of the target parking route based on the identification of the target parking route and send the summary information to the first user end. The first user terminal may generate a sharing link based on the summary information. For example, the first user may open a memory parking page. And an identification list of the parking route of the first user end is displayed on the memory parking page. The first user can select any one parking route as the target parking route.
Here, the first user side can flexibly share the shared link of the target parking route to the second user side through multiple sharing modes.
Firstly, a sharing mode of the public link is as follows: that is, a public shared link is generated, and any user can download the parking route based on the shared link. Specifically, a route sharing button is arranged on the memory parking page, and the first user can click the route sharing button after selecting the target parking route. At this time, a plurality of sharing channels can be displayed on the memory parking page. The first user can select any one of the sharing channels to publish the sharing link. The sharing channel may include, but is not limited to, a social space of a social application, a group chat of a social application, among others. The shared link may be posted on a social space of the social application or shared into a group chat of the social application.
Secondly, a point-to-point sharing mode: that is, the first user designates the parking route to be shared with the second user. Specifically, an account number input box and a route sharing button can be arranged on the memory parking page. The first user can input the account number of the second user in the account number input box and click the route sharing button. At this time, the sharing link may be shared to the second user through the account of the second user.
Thirdly, based on the position recommendation, the sharing mode is as follows: that is, the location-based route recommendation service, any user can view a nearby parking route. Specifically, an authorization disclosure button can be arranged on the memory parking page. The first user may click the authorization disclosure button after selecting the target parking route. The cloud can obtain the location of the second user terminal. And if the position of the second user end is within the sharing range of the target parking route (for example, within 300 meters near the target parking route), sharing the sharing link to the second user end.
Here, the second user may click on the shared link of the target parking route received by the second user. When the second user clicks the shared link of the target parking route, a route acquisition request can be triggered to be sent to the cloud.
Step 202, sending the target parking route to the second user end to instruct the second user end to park based on the target parking route.
In this embodiment, after receiving the route acquisition request, the cloud may send the target parking route to the second user side. The second user terminal can park the vehicle based on the target parking route, and the user is helped to take the vehicle or return the vehicle.
In some embodiments, the end point of the target parking route is the target slot. At this time, the parking can be automatically carried out to the target parking space based on the target parking route. In some embodiments, the end point of the target parking route is the location of the second user. At this time, the parking can be automatically called out of the garage based on the target parking route to reach the position of the second user. Under the condition that a user is inconvenient to take or return a car due to heavy objects in hand or hot weather, the user can be helped to take or return the car in a long distance directly based on the target parking route, the use scene of the parking function is expanded, and therefore the user can be better served.
In general, in the case of simpler environment and less variation, the second user can park the vehicle directly according to the target parking route. Under the conditions of complex environment and large change, the second user end can collect data in the process of parking according to the target parking route. And performing fusion reconstruction based on the acquired data and the target parking route to obtain a fusion parking route. The second user end may then park in accordance with the fused parking route. It should be noted that the fused parking route may be obtained by the second user side, or may be obtained by the cloud side. The specific learning manner may refer to a target parking route, which is not described herein again.
In some optional implementations of this embodiment, the first user terminal may include a first user terminal and a first user vehicle terminal. The second user terminal may include a second user terminal and a second user vehicle terminal. The operations related to the interaction are performed by the user terminal. For example, sharing a shared link, sending a route acquisition request, etc. The parking-related operations are performed by the user on the vehicle side. Such as collecting data, downloading parking routes, parking based on parking routes, etc. The cloud may include a cloud user management system and a cloud map management system. The cloud user management system can be used for storing user information and summary information of the parking route. The cloud map management system may be used to generate and store parking routes.
With the increasing demands of users on parking route use scenes and use places, the parking route learned by a single user is not enough to meet the demands, and meanwhile, the map data are enriched due to the learned routes of different users. Therefore, the parking route sharing method for the memory parking user is provided, the parking route of a single user can be shared by other users, and the parking route originally used by the single user can be shared by other users. The embodiment improves the application rate of the parking route of a single user, reduces the learning cost of the parking routes of other users, and further increases the practicability of memory parking. In addition, in the process of sharing the parking route, the first user interacts with the second user, and social attributes of memory parking are increased.
With further reference to fig. 3, a flow 300 of yet another embodiment of a parking route sharing method of the present disclosure is shown. The parking route sharing method comprises the following steps:
step 301, receiving first data collected by a first user terminal in a parking process.
In this embodiment, the first user terminal can collect the first data during the parking process, and send the first data to the cloud.
Typically, the first user end is configured with a camera (e.g., a wide-angle camera, a look-around camera, etc.) and a sensor such as an ultrasonic radar. The sensors may collect first data during parking.
Step 302, learning to obtain a target parking route based on the first data.
In this embodiment, the cloud end may learn the target parking route based on the first data. Generally, the cloud can construct a target parking route through a visual SLAM technology, so that high-precision positioning can be realized without depending on a high-precision map.
Step 303, receiving a route acquisition request sent by the second user end based on the shared link of the target parking route.
In this embodiment, the specific operation of step 303 has been described in detail in step 201 in the embodiment shown in fig. 2, and is not described herein again.
And step 304, judging whether the account number of the second user meets a preset condition.
In this embodiment, the cloud may determine whether the account of the second user meets a preset condition. Under the condition that the account number of the second user does not meet the preset condition, ending the process; in the case that the account of the second user satisfies the preset condition, step 305 is executed.
And 305, sending the target parking route to a second user end to instruct the second user end to park based on the target parking route.
In this embodiment, the cloud end may send the target parking route to the second user end when the account of the second user meets the preset condition. The second user terminal may park the vehicle based on the target parking route. And determining whether to send the target parking route by judging whether the account number of the second user meets the preset condition, so that the sent target parking route is more suitable for parking of the second user.
The preset condition may be a preset condition related to the account. For example, the preset conditions may include, but are not limited to, at least one of: the account of the second user is registered, the account of the second user is associated with at least one vehicle of which the vehicle type is the same as that of the first user side, the second user selects at least one vehicle of which the vehicle type is the same as that of the first user side from the vehicles associated with the account of the second user, the number of parking routes associated with the account of the second user is smaller than a preset threshold value, and the like.
Typically, the vehicle associated with the account of the second user may be a vehicle associated with the second user, including but not limited to a vehicle under the name of the second user, a vehicle that the second user has driven, and so on. In some application scenarios, the account of the second user may be associated with a plurality of vehicles. The plurality of associated vehicles may have a vehicle of the same type as the first user side or a vehicle of a type different from the first user side. Since vehicles of the same model are more suitable for sharing the parking route, the parking route is generally transmitted when the account of the second user is associated with a vehicle of the same model as the first user. In the case where the account of the second user is associated with a plurality of vehicles of the same type as the first user, the user is required to select one or more vehicles for receiving the parking route. For example, a list of identifications of vehicles with which the account is associated is displayed on the second user side. The mark of the vehicle of the same type as the vehicle type of the first user end is displayed in a form of a mark for distinguishing other vehicles (such as a font color different from the marks of other vehicles, a marking pattern added near the mark, and the like). When the second user clicks the identification of one or more vehicles of the same type as the first user, the second user can send the identification of the vehicle clicked by the user to the cloud. The cloud end can determine the vehicle selected by the second user according to the received identification of the vehicle, and can send the parking route to the vehicle selected by the second user.
And step 306, receiving second data collected by the second user end in the parking process.
In this embodiment, the second user side may collect the second data while parking according to the target parking route, and send the second data to the cloud.
Typically, the second user end is configured with a camera (e.g., a wide-angle camera, a look-around camera, etc.) and a sensor such as an ultrasonic radar. These sensors may collect second data during the parking process.
And 307, performing fusion reconstruction based on the second data and the target parking route to obtain a fusion parking route.
In this embodiment, the cloud end may perform fusion reconstruction based on the data acquired by the second user end and the target parking route, so as to obtain a fusion parking route. The cloud end can send the fused parking route to the second user end. The second user end may then park in accordance with the fused parking route. The cloud end can reconstruct the parking route through a visual SLAM technology.
Generally, a plurality of clients commonly use a target parking route of a first client. And different user sides enter the geographic fence range of the target parking route, start data records are recorded, and the start data records are packaged and uploaded to the cloud. The cloud end fuses the historical data for many times to reconstruct the route, and issues the updated parking route to the user end, so that the scene adaptability of the parking route is improved.
In some optional implementations of this embodiment, the first user terminal may include a first user terminal and a first user vehicle terminal. The second user terminal may include a second user terminal and a second user vehicle terminal. The operations related to the interaction are performed by the user terminal. For example, sharing a shared link, sending a route acquisition request, etc. The parking-related operations are performed by the user on the vehicle side. Such as collecting data, downloading parking routes, parking based on parking routes, etc. The cloud may include a cloud user management system and a cloud map management system. The cloud user management system can be used for storing user information and summary information of the parking route. The cloud map management system may be used to generate and store parking routes.
As can be seen from fig. 3, the parking route sharing method in the present embodiment adds the generation step and the update step of the parking route, as compared with the embodiment corresponding to fig. 2. Therefore, according to the scheme described in the embodiment, the parking route is generated and updated at the cloud end, and the cloud end has stronger computing capability, so that the computing speed of updating the parking route is increased, and the occupation of computing resources of a user end is reduced. In the process of parking according to the parking route, data are collected in real time to update the parking route, and the method can adapt to complex and changeable environments. By means of the cloud learning capability of the parking route, the multi-user end carries out fusion reconstruction on the parking route, invalid and outdated route features can be eliminated, new route features in a scene are supplemented, scene adaptability of the parking route is improved, and robustness of the parking route is improved.
With further reference to FIG. 4, a timing diagram of one embodiment of sharing shared links is shown, as follows:
step 401, the first user terminal opens a memory parking page.
In step 402, the first user terminal selects a target parking route.
Here, the first user terminal selects a target parking route and shares its shared link. The sharing mode can comprise a public link sharing mode, a point-to-point sharing mode and a position recommendation based sharing mode. If the sharing link is shared by the sharing method of the public link, the steps 403, 404 and 411 are executed in sequence. If the sharing link is shared by the location-based recommended sharing method, steps 405, 406, 407, 408, and 411 are sequentially performed. If the sharing link is shared in a peer-to-peer sharing manner, steps 405, 409, 410, and 411 are sequentially performed.
In step 403, the cloud user management system indexes summary information of the target parking route and marks the summary information as a public route.
In step 404, the first user terminal marks successfully, and nearby users can view and download the target parking route.
In step 405, the first user terminal clicks a share button.
In step 406, the first user terminal selects a sharing channel.
Step 407, the cloud user management system indexes summary information of the target parking route.
In step 408, the first user terminal generates a sharing link.
And step 409, the cloud user management system indexes summary information of the target parking route.
In step 410, the first user terminal inputs an account number of the second user.
And step 411, the second user terminal clicks the sharing link to view and collect.
With further reference to fig. 5, a timing diagram of one embodiment of determining a shared-shared connection is shown, as follows:
step 501, the cloud user management system enters a sharing judgment process.
Step 502, the cloud user management system searches the registered account stored in the cloud user management system through the mobile phone number of the second user.
In step 503, the cloud user management system determines whether the mobile phone number of the second user is registered as an account number.
Here, the cloud user management system may search through the registered account number stored by the second user through the mobile phone number of the second user. If the mobile phone number of the second user is not searched, determining that the mobile phone number of the second user is not registered, and executing step 504. If the mobile phone number of the second user is searched, determining that the mobile phone number of the second user is registered as an account number, and executing step 505.
And step 504, the second user terminal receives prompt information of collection failure fed back by the cloud user management system.
Here, if the mobile phone number of the second user is not searched, or a vehicle of the same type as the vehicle end of the first user is not associated, or the number of parking routes associated with the account number of the second user is not less than a preset threshold, the cloud user management system may feed back a prompt message of "collection failure" to the second user terminal.
In step 505, the cloud user management system determines whether the account of the second user is associated with a vehicle of the same type as the vehicle of the first user.
Here, if the mobile phone number of the second user is searched, the cloud user management system may determine whether the account number of the second user is associated with a vehicle of the same type as the vehicle end of the first user. If the vehicle type of the first user vehicle end is not associated, step 504 is executed. If a vehicle of the same type as the vehicle of the first user is associated, step 506 is executed.
In step 506, the cloud user management system determines whether the associated vehicles of the same vehicle type as the vehicle end of the first user are multiple.
Here, if a vehicle of the same type as the vehicle side of the first user is associated, the cloud user management system may determine whether the associated vehicle of the same type as the vehicle side of the first user is multiple. If there are more, go to step 507. If so, go to step 509.
And step 507, the second user terminal receives prompt information of 'vehicle selection' sent by the cloud user management system.
Here, if there are multiple associated vehicles of the same vehicle type as the vehicle side of the first user, the cloud user management system may send a prompt message of "select vehicle" to the second user terminal.
In step 508, the second user terminal determines a vehicle selected by the second user.
Here, the second user may select one vehicle from the associated vehicles of the same type as the vehicle of the first user according to the prompt message, and send the selected vehicle information to the cloud user management system.
In step 509, the cloud user management system determines whether the number of parking routes associated with the account of the second user is less than a preset threshold.
Here, if the associated vehicle of the same type as the vehicle of the first user vehicle end is one vehicle, or the first user terminal selects one vehicle from the associated vehicles of the same type as the vehicle of the first user vehicle end, the cloud user management system may determine whether the number of parking routes associated with the account of the second user is less than a preset threshold. If not, go to step 504. If the value is less than the predetermined threshold, go to step 510.
And step 510, the second user terminal receives the prompt information of 'collection success' fed back by the cloud user management system.
Here, if the value is smaller than the preset threshold, the cloud user management system may feed back a prompt message of "collection success" to the second user terminal. Then, the second user vehicle end can download the target parking route from the cloud map management system.
With further reference to FIG. 6, a timing diagram of one embodiment of issuing a parking route is shown, as follows:
step 601, the cloud user management system records summary information of the target parking route collected by the second user terminal.
Step 602, the cloud map management system enters a sharing process.
And step 603, the cloud map management system indexes a target parking route and suspends the sharing task.
And step 604, establishing connection between the second user vehicle end and the cloud map management system.
And step 605, the cloud map management system issues the target parking route to the second user vehicle end.
Here, if the delivery fails, step 606 is executed. If the delivery is successful, go to step 607.
And 606, receiving a prompt message of 'sharing failure' fed back by the cloud map management system by the second user terminal.
And step 607, the second user vehicle end completes receiving.
Here, after the second user terminal finishes receiving, step 608-.
In step 608, the cloud map management system receives the prompt message of "successful reception" fed back by the second user vehicle.
And step 609, the cloud user management system completes the sharing.
And step 610, the first user terminal receives the prompt information of 'someone collects your route' fed back by the cloud user management system.
And 611, enabling the second user vehicle end to synchronize the target parking route to the vehicle machine.
And step 612, the car machine uploads the summary information of the target parking route to the cloud user management system.
Step 613, the cloud user management system receives summary information of the target parking route of the vehicle end of the second user.
In step 614, the second user terminal displays the target parking route.
Here, the cloud user management system may issue the summary information of the target parking route to the second user terminal, so that the summary information is displayed by the second user terminal.
With further reference to FIG. 7, a scene diagram of one embodiment of parking route reconstruction is shown, as follows:
and step 701, positioning the vehicle end.
Generally, the second user vehicle end is equipped with a front wide-angle camera, a panoramic camera, an IMU (Inertial Measurement Unit), a GPS (Global Positioning System), and a wheel speed sensor. And if the second user vehicle end is positioned to enter the target parking route geo-fence range, starting a front wide-angle camera, a look-around camera, an IMU, a GPS and a wheel speed sensor to acquire data, and packaging and uploading the data to a cloud map management system.
Step 702, the cloud builds a map.
And step 703, controlling the vehicle end.
Generally, the second user vehicle end can perform vehicle end control according to the fused parking route issued by the cloud map management system.
With further reference to fig. 8, as an implementation of the methods shown in the above-mentioned figures, the present disclosure provides an embodiment of a parking route sharing device, which corresponds to the embodiment of the method shown in fig. 2, and which is particularly applicable to various electronic devices.
As shown in fig. 8, the parking route sharing device 800 of the present embodiment may include: a first receiving module 801 and a sending module 802. The first receiving module 801 is configured to receive a route obtaining request sent by a second user terminal based on a shared link of a target parking route, where the shared link is shared by the first user terminal; a sending module 802, configured to send the target parking route to the second user end to instruct the second user end to park the vehicle based on the target parking route.
In the present embodiment, in the parking route sharing device 800: the detailed processing of the first receiving module 801 and the sending module 802 and the technical effects thereof can be referred to the related description of step 201 and step 202 in the corresponding embodiment of fig. 2, and are not repeated herein.
In some optional implementations of the present embodiment, the parking route sharing device 800 further includes: the second receiving module is configured to receive first data collected by the first user end in the parking process; and the learning module is configured to learn the target parking route based on the first data.
In some optional implementations of the present embodiment, the parking route sharing device 800 further includes: the third receiving module is configured to receive second data collected by a second user end in the parking process; and the fusion module is configured to perform fusion reconstruction based on the second data and the target parking route to obtain a fusion parking route.
In some optional implementations of this embodiment, the sending module 802 is further configured to: and responding to the fact that the account number of the second user meets the preset condition, and sending the target parking route to the second user side.
In some optional implementations of the present embodiment, the parking route sharing device 800 preset condition includes at least one of: the second user registers an account number, the account number of the second user is associated with at least one vehicle of which the vehicle type is the same as that of the first user side, the second user selects at least one vehicle of which the vehicle type is the same as that of the first user side from the vehicles associated with the account number of the second user, and the number of parking routes associated with the account number of the second user is smaller than a preset threshold value.
In some optional implementations of the present embodiment, the parking route sharing device 800 further includes: the fourth receiving module is configured to receive a summary information acquisition request of the target parking route sent by the first user end; and the index module is configured to index the summary information of the target parking route and send the summary information to the first user terminal so as to instruct the first user terminal to generate the sharing link based on the summary information.
In some optional implementations of the embodiment, the sharing manner of the link shared by the parking route sharing device 800 includes at least one of the following: the sharing mode of the public link, the point-to-point sharing mode and the sharing mode based on the position recommendation.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, and do not violate the good customs of the public order.
The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.
FIG. 9 illustrates a schematic block diagram of an example electronic device 900 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may 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 meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 9, the apparatus 900 includes a computing unit 901, which can perform various appropriate actions and processes in accordance with a computer program stored in a Read Only Memory (ROM)902 or a computer program loaded from a storage unit 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the device 900 can also be stored. The calculation unit 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
A number of components in the device 900 are connected to the I/O interface 905, including: an input unit 906 such as a keyboard, a mouse, and the like; an output unit 907 such as various types of displays, speakers, and the like; a storage unit 908 such as a magnetic disk, optical disk, or the like; and a communication unit 909 such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 909 allows the device 900 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.
The computing unit 901 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 901 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, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 901 performs the respective methods and processes described above, such as the parking route sharing method. For example, in some embodiments, the parking route sharing method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 908. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 900 via ROM 902 and/or communications unit 909. When the computer program is loaded into the RAM 903 and executed by the computing unit 901, one or more steps of the parking route sharing method described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform the parking route sharing method in any other suitable manner (e.g., by way of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods 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, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The 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, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here 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 a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, 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 may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in this disclosure may be performed in parallel or sequentially or in a different order, as long as the desired results of the technical solutions provided by this disclosure can be achieved, and are not limited herein.
The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims (17)

1. A parking route sharing method comprising:
receiving a route acquisition request sent by a second user side based on a shared link of a target parking route, wherein the shared link is shared by the first user side;
and sending the target parking route to the second user end to instruct the second user end to park on the basis of the target parking route.
2. The method of claim 1, further comprising:
receiving first data collected by the first user terminal in a parking process;
and learning to obtain the target parking route based on the first data.
3. The method of claim 1, further comprising:
receiving second data collected by the second user terminal in the parking process;
and performing fusion reconstruction on the basis of the second data and the target parking route to obtain a fusion parking route.
4. The method according to any one of claims 1-3, wherein said transmitting the target parking route to the second user terminal comprises:
and responding to the fact that the account number of the second user meets the preset condition, and sending the target parking route to the second user terminal.
5. The method of claim 4, wherein the preset conditions include at least one of: the account of the second user is registered, the account of the second user is associated with at least one vehicle of which the vehicle type is the same as that of the first user side, the second user selects at least one vehicle of which the vehicle type is the same as that of the first user side from the vehicles associated with the account of the second user, and the number of parking routes associated with the account of the second user is smaller than a preset threshold value.
6. The method of any of claims 1-5, further comprising:
receiving a summary information acquisition request of the target parking route sent by the first user end;
and indexing summary information of the target parking route, and sending the summary information to the first user side to instruct the first user side to generate the sharing link based on the summary information.
7. The method of any of claims 1-6, wherein the sharing of the shared link comprises at least one of: the sharing mode of the public link, the point-to-point sharing mode and the sharing mode based on the position recommendation.
8. A parking route sharing device comprising:
the system comprises a first receiving module, a second receiving module and a third receiving module, wherein the first receiving module is configured to receive a route obtaining request sent by a second user terminal based on a shared link of a target parking route, and the shared link is shared by the first user terminal;
a sending module configured to send the target parking route to the second user end to instruct the second user end to park based on the target parking route.
9. The apparatus of claim 8, wherein the apparatus further comprises:
the second receiving module is configured to receive first data collected by the first user end in a parking process;
a learning module configured to learn the target parking route based on the first data.
10. The apparatus of claim 8, wherein the apparatus further comprises:
the third receiving module is configured to receive second data collected by the second user end in a parking process;
and the fusion module is configured to perform fusion reconstruction on the second data and the target parking route to obtain a fusion parking route.
11. The apparatus of any of claims 8-10, wherein the transmitting module is further configured to:
and responding to the fact that the account number of the second user meets the preset condition, and sending the target parking route to the second user terminal.
12. The apparatus of claim 11, wherein the preset conditions comprise at least one of: the account number of the second user is registered, the account number of the second user is associated with at least one vehicle of which the vehicle type is the same as that of the first user side, the second user selects at least one vehicle of which the vehicle type is the same as that of the first user side from the vehicles associated with the account number of the second user, and the number of parking routes associated with the account number of the second user is smaller than a preset threshold value.
13. The apparatus of any one of claims 8-12, wherein the apparatus further comprises:
a fourth receiving module, configured to receive a summary information acquisition request of the target parking route sent by the first user end;
the index module is configured to index summary information of the target parking route and send the summary information to the first user side so as to instruct the first user side to generate the sharing link based on the summary information.
14. The apparatus according to any one of claims 8-13, wherein the sharing of the shared link includes at least one of: the sharing mode of the public link, the point-to-point sharing mode and the sharing mode based on the position recommendation.
15. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
16. A non-transitory computer-readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-7.
17. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-7.
CN202110453459.7A 2021-04-26 2021-04-26 Parking route sharing method, device, equipment and storage medium Pending CN113135178A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202110453459.7A CN113135178A (en) 2021-04-26 2021-04-26 Parking route sharing method, device, equipment and storage medium
PCT/CN2022/071788 WO2022227711A1 (en) 2021-04-26 2022-01-13 Parking route sharing method and apparatus, and device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110453459.7A CN113135178A (en) 2021-04-26 2021-04-26 Parking route sharing method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN113135178A true CN113135178A (en) 2021-07-20

Family

ID=76812040

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110453459.7A Pending CN113135178A (en) 2021-04-26 2021-04-26 Parking route sharing method, device, equipment and storage medium

Country Status (2)

Country Link
CN (1) CN113135178A (en)
WO (1) WO2022227711A1 (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113808434A (en) * 2021-10-15 2021-12-17 广州小鹏汽车科技有限公司 Parking route sharing processing method and device, vehicle and readable storage medium
CN113947942A (en) * 2021-10-15 2022-01-18 广州小鹏自动驾驶科技有限公司 Parking map sharing processing method, device, equipment and system
CN113945223A (en) * 2021-10-15 2022-01-18 广州小鹏汽车科技有限公司 Parking route sharing processing method, device and equipment
CN113947935A (en) * 2021-10-15 2022-01-18 广州小鹏汽车科技有限公司 Parking route downloading processing method, device and equipment
CN113947934A (en) * 2021-10-15 2022-01-18 广州小鹏汽车科技有限公司 Parking route processing method, device and system
CN114228700A (en) * 2021-09-30 2022-03-25 江铃汽车股份有限公司 Parking information sharing method and device, electronic equipment and storage medium
CN114613180A (en) * 2022-02-22 2022-06-10 恒大新能源汽车投资控股集团有限公司 Autonomous parking method, device, vehicle and parking lot end server
WO2022227711A1 (en) * 2021-04-26 2022-11-03 北京百度网讯科技有限公司 Parking route sharing method and apparatus, and device and storage medium
CN116246479A (en) * 2023-03-28 2023-06-09 长城汽车股份有限公司 Vehicle control method and device and server

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108520014A (en) * 2018-03-21 2018-09-11 广东欧珀移动通信有限公司 Information sharing method, device, mobile terminal and computer-readable medium
CN110782701A (en) * 2019-11-14 2020-02-11 广东科学技术职业学院 Parking management method and device, server and unmanned vehicle
CN111143307A (en) * 2019-12-12 2020-05-12 中国第一汽车股份有限公司 Map sharing system
CN111301403A (en) * 2018-12-06 2020-06-19 现代自动车株式会社 System, method, infrastructure and vehicle for automated valet parking
CN112422658A (en) * 2020-11-06 2021-02-26 广州小鹏汽车科技有限公司 Parking space sharing method and device
CN112562388A (en) * 2020-11-13 2021-03-26 浙江吉利控股集团有限公司 Vehicle connection management method and device and storage medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104386063B (en) * 2014-09-19 2017-07-11 奇瑞汽车股份有限公司 Drive assist system based on artificial intelligence
DE102017112386A1 (en) * 2017-06-06 2018-12-06 Connaught Electronics Ltd. A method for providing stored data of a trained parking operation, corresponding computer program product and system
CN110942653A (en) * 2019-10-20 2020-03-31 黄旭仕 Intelligent driving automobile auxiliary parking system based on Internet of vehicles
CN113135178A (en) * 2021-04-26 2021-07-20 北京百度网讯科技有限公司 Parking route sharing method, device, equipment and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108520014A (en) * 2018-03-21 2018-09-11 广东欧珀移动通信有限公司 Information sharing method, device, mobile terminal and computer-readable medium
CN111301403A (en) * 2018-12-06 2020-06-19 现代自动车株式会社 System, method, infrastructure and vehicle for automated valet parking
CN110782701A (en) * 2019-11-14 2020-02-11 广东科学技术职业学院 Parking management method and device, server and unmanned vehicle
CN111143307A (en) * 2019-12-12 2020-05-12 中国第一汽车股份有限公司 Map sharing system
CN112422658A (en) * 2020-11-06 2021-02-26 广州小鹏汽车科技有限公司 Parking space sharing method and device
CN112562388A (en) * 2020-11-13 2021-03-26 浙江吉利控股集团有限公司 Vehicle connection management method and device and storage medium

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022227711A1 (en) * 2021-04-26 2022-11-03 北京百度网讯科技有限公司 Parking route sharing method and apparatus, and device and storage medium
CN114228700A (en) * 2021-09-30 2022-03-25 江铃汽车股份有限公司 Parking information sharing method and device, electronic equipment and storage medium
CN114228700B (en) * 2021-09-30 2024-01-09 江铃汽车股份有限公司 Parking information sharing method and device, electronic equipment and storage medium
CN113808434A (en) * 2021-10-15 2021-12-17 广州小鹏汽车科技有限公司 Parking route sharing processing method and device, vehicle and readable storage medium
CN113947942A (en) * 2021-10-15 2022-01-18 广州小鹏自动驾驶科技有限公司 Parking map sharing processing method, device, equipment and system
CN113945223A (en) * 2021-10-15 2022-01-18 广州小鹏汽车科技有限公司 Parking route sharing processing method, device and equipment
CN113947935A (en) * 2021-10-15 2022-01-18 广州小鹏汽车科技有限公司 Parking route downloading processing method, device and equipment
CN113947934A (en) * 2021-10-15 2022-01-18 广州小鹏汽车科技有限公司 Parking route processing method, device and system
WO2023060837A1 (en) * 2021-10-15 2023-04-20 广州小鹏自动驾驶科技有限公司 Parking map sharing processing method, apparatus and system, and device and storage medium
CN114613180A (en) * 2022-02-22 2022-06-10 恒大新能源汽车投资控股集团有限公司 Autonomous parking method, device, vehicle and parking lot end server
CN116246479A (en) * 2023-03-28 2023-06-09 长城汽车股份有限公司 Vehicle control method and device and server

Also Published As

Publication number Publication date
WO2022227711A1 (en) 2022-11-03

Similar Documents

Publication Publication Date Title
CN113135178A (en) Parking route sharing method, device, equipment and storage medium
CN109212530B (en) Method and apparatus for determining velocity of obstacle
JP6639640B2 (en) Navigation reference point identification and navigation method, apparatus, and storage medium
US11668576B2 (en) Using sensor data for coordinate prediction
US20150149545A1 (en) Apparatus and method for sharing of location information using social network service
CN115140090A (en) Vehicle control method, device, electronic equipment and computer readable medium
CN111311144B (en) Data processing method, device, server and nonvolatile storage medium
CN114554391A (en) Parking lot vehicle searching method, device, equipment and storage medium
CN114047760A (en) Path planning method and device, electronic equipment and automatic driving vehicle
CN114221960B (en) Data pushing method based on automatic driving bus and automatic driving bus
JP7397116B2 (en) Map query methods, devices and electronic equipment
CN113850909B (en) Point cloud data processing method and device, electronic equipment and automatic driving equipment
CN116312013A (en) Multi-modal navigation system
CN114590246A (en) Dual-channel communication automatic parking method, device, equipment and storage medium
CN114862491A (en) Vehicle position determining method, order dispatching method, device, server and storage medium
CN113800343A (en) Building elevator control method and system of vehicle intelligent control system and vehicle
CN114428917A (en) Map-based information sharing method, map-based information sharing device, electronic equipment and medium
US11783441B2 (en) Systems and methods for dynamically connecting one or more transportation vehicles to customers
CN112747733A (en) Navigation method, navigation device, storage medium and electronic device
CN104897166A (en) Remote navigation method and system
CN111460067A (en) Method and device for automatically updating navigation route and electronic equipment
KR102068796B1 (en) Navigation apparatus, method thereof and computer readable medium having computer program recorded therefor
CN112414423B (en) Planning method and device for vehicle guidance starting point road, electronic equipment and storage medium
CN110646000A (en) Navigation method, navigation device and storage medium
CN114596707B (en) Traffic control method, traffic control device, traffic control equipment, traffic control system and traffic control medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20210720

RJ01 Rejection of invention patent application after publication