Computer-implemented method for route planning for visually impaired people

Abstract

A computer-implemented procedure comprises: (i) determining a user's current location using location data, (ii) determining, using location data, a user device's starting point based on the current location and a user device's destination based on user input, (iii) identifying, via a pedestrian route planner of a route planning application communicating with a navigation system, a pedestrian route between the starting point and the destination, (iv) identifying, via the navigation system, waypoints between the starting point and the destination, (v) transmitting the pedestrian route to the user device, (vi) outputting, via the route planning application, i) a haptic feedback protocol and / or ii) an acoustic feedback protocol associated with the waypoints.are, (vii) receiving pedestrian route data from the user device, and (viii) processing the pedestrian route data to determine user behavior.

Description

INTRODUCTION

[0001] The present invention relates generally to a computer-implemented method for route planning to support visually impaired people by providing haptic or auditory feedback on a user device.

[0002] For example, DE 10 2018 009 629 A1 discloses a navigation system that can guide a person to a destination using haptic signals.

[0003] Further details of the state of the art can be found in the publications DE 10 2020 125 300 A1, DE 10 2007 037 520 A1, US 2019 / 0 383 634 A1, US 2022 / 0 221 296 A1, US 2018 / 0 293 980 A1, WO 2016 / 069672 A1 and US 2001 / 0 025 222 A1.

[0004] Users can often utilize a mobile application that provides pedestrian navigation when orienting themselves in a new area or when a user requires navigational assistance due to a disability. For example, some mobile applications can be used to determine a sidewalk based on a user's current location and destination, relying on the user to follow the sidewalk to reach their destination. The user typically looks at their device screen to view the sidewalk displayed in the mobile application. As the user moves along the sidewalk, the sidewalk displayed in the mobile application can be updated to reflect the user's current location. In some cases, a navigation voice configured within the mobile application can provide audible feedback to inform the user of navigation instructions along the sidewalk.For example, if the sidewalk encounters a left turn, the navigation voice can provide the user with acoustic feedback to alert them to the left turn.

[0005] Many mobile pedestrian navigation applications require the user to hold the device to maintain visual and auditory interaction. If the user is visually impaired, they may need to hold a cane in one hand while holding the device in the other to properly use the mobile application while navigating the sidewalk. For a visually impaired user, keeping both a cane and a mobile device close enough to follow the audio navigation can be cumbersome and difficult. Furthermore, the mobile application may fail to update the sidewalk map to avoid roadwork or obstacles along the way. This can render the sidewalk unsuitable as a viable route to the destination.If the user is visually impaired, they may unexpectedly encounter an obstacle and be unable to reach their destination if the mobile application does not update the route. Therefore, it is desirable to have a mobile application that can seamlessly adapt to a visually impaired user. SUMMARY

[0006] According to the invention, a computer-implemented method is presented which is characterized by the features of claim 1.

[0007] Implementations of this aspect of the invention may include one or more of the following optional features. In some examples, the navigation system includes at least one of the following systems: Global Positioning System (GPS), Real-Time Kinematic Positioning (RTK), and a GNSS (Global Navigation Satellite System) chipset. In some further examples, the method also includes continuously updating the pedestrian route in response to changes associated with the current location of the user device, the GPS, the GNSS chipset, and RTK.

[0008] In some embodiments, the method also includes coupling and transferring data between the data processing hardware and the user device over a network.

[0009] In some configurations, the haptic feedback protocol and the acoustic feedback protocol are further linked to i) the current location of the user device in relation to the pedestrian route, ii) changes to the pedestrian route, and iii) deviations of the user device from the pedestrian route.

[0010] In some examples, the haptic feedback protocol and the acoustic feedback protocol include a variety of intensities associated with one or more of the following: the current position of the user device relative to the pedestrian route, changes to the pedestrian route, deviations of the user device from the pedestrian route, and waypoints.

[0011] In some configurations, the waypoints include at least one of the following: i) obstacles on the pedestrian route, ii) changes of direction on the pedestrian route, and iii) intersections on the pedestrian route.

[0012] In some examples, the current location of the user device corresponds to the starting point of the user device.

[0013] In some implementations, the starting point of the user device is entered manually.

[0014] Furthermore, a system is described. The system comprises data processing hardware and storage hardware that communicates with the data processing hardware. The storage hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. The operations include (i) determining, using location data, the current location of a user device relative to the vehicle location; (ii) determining, using location data, a starting point of a user device relative to the vehicle location and based on the current location, and a destination of the user device relative to the vehicle location and based on user input; and (iii) identifying, using a pedestrian route planner of a route planning application communicating with a navigation system, a pedestrian route between the starting point of the user device and the destination of the user device.(iv) Identifying the pedestrian route based on user behavior, (v) Identifying, via the navigation system, waypoints between the user device's starting point and the user device's destination, (vi) Transmitting the pedestrian route to the user device, (vii) Outputting, via the route planning application, i) a haptic feedback protocol and / or ii) an acoustic feedback protocol associated with the waypoint(s), (viii) Receiving pedestrian route data associated with the pedestrian route from the user device, and (ix) Processing the pedestrian route data to determine user behavior.

[0015] Implementations of this aspect of the invention may include one or more of the following optional features. In some examples, the navigation system includes at least one of the following systems: Global Positioning System (GPS), Real-Time Kinematic Positioning (RTK), and a GNSS (Global Navigation Satellite System) chipset.

[0016] In some implementations, the coupling and transfer between the data processing hardware and the user device takes place over a network.

[0017] In some configurations, the haptic feedback protocol and the acoustic feedback protocol are further linked to i) the current location of the user device in relation to the pedestrian route, ii) changes to the pedestrian route, and iii) deviations of the user device from the pedestrian route.

[0018] In some examples, the waypoints include at least one of the following: i) obstacles on the pedestrian route, ii) changes of direction on the pedestrian route, and iii) intersections on the pedestrian route.

[0019] Furthermore, a route planning system for a vehicle is described. The route planning system comprises data processing hardware and storage hardware that communicates with the data processing hardware. The storage hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. These operations include (i) determining, using location data, the current location of a user device relative to the vehicle's location, (ii) determining, using location data, a starting point of a user device relative to the vehicle's location and based on its current location, and a destination of the user device relative to the vehicle's location and based on user input, and (iii) identifying, via a pedestrian route planner of a route planning application communicating with a navigation system,a pedestrian route between the user device's starting point and the user device's destination, (iv) identifying the pedestrian route based on user behavior, (v) identifying, via the navigation system, waypoints between the user device's starting point and the user device's destination, (vi) transmitting the pedestrian route to the user device, (vii) outputting, via the route planning application, i) a haptic feedback protocol and / or ii) an acoustic feedback protocol associated with the waypoint(s), (viii) receiving pedestrian route data associated with the pedestrian route from the user device, and (ix) processing the pedestrian route data to determine user behavior.

[0020] Implementations of this aspect of the invention may include one or more of the following optional features. In some examples, the navigation system includes at least one of the following systems: Global Positioning System (GPS), Real-Time Kinematic Positioning (RTK), and a GNSS (Global Navigation Satellite System) chipset. In some other examples, the pedestrian route is continuously updated in response to changes associated with the current location of the user device, the GPS, the GNSS chipset, and RTK.

[0021] In some implementations, the haptic feedback protocol and the acoustic feedback protocol are further linked to i) the current location of the user device in relation to the pedestrian route, ii) changes to the pedestrian route, and iii) deviations of the user device from the pedestrian route.

[0022] In some configurations, the waypoints include at least one of the following: i) obstacles on the pedestrian route, ii) changes of direction on the pedestrian route, and iii) intersections on the pedestrian route. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings described here serve only to illustrate selected configurations. Fig. Figure 1 is a perspective view of a controller configured with a route planning application according to the present invention, wherein the controller is optionally configured as part of a vehicle and / or a user device; Fig. Figure 2 is a functional block diagram of a route planning system according to the present invention; Fig. 3 is another functional block diagram of the route planning system of Fig. 2; Fig. Figure 4 is an example of a schematic representation of a user walking along a pedestrian route and using a route planning application according to the present invention; Fig. Figure 5 is an exemplary flowchart for a route planning system according to the present invention; and Fig. 6 is another example of a flowchart for the route planning system of Fig. 4.

[0024] The corresponding reference numbers denote the corresponding parts in the drawings. DETAILED DESCRIPTION

[0025] With reference to Fig. 1 and Fig. Section 2 comprises a route planning system 100 and a controller 102 configured with a route planning application 104. The controller 102 of the route planning system 100 can be integrated as part of a vehicle 10 and / or a user device 200. Communication and data transmission between the controller 102 and the user device 200 can be achieved by pairing or connecting the user device 200 to the controller 102 via a network 300. The vehicle 10 can be an electric vehicle (EV), a hybrid vehicle, an internal combustion engine vehicle (ICE), or any other type of vehicle capable of communicating with devices outside the vehicle 10, such as the user device 200, via the network 300.

[0026] Controller 102 contains data processing hardware 106, which is configured to run the route planning application 104. Controller 102 also includes memory hardware 108, which communicates with the data processing hardware 106. The memory hardware 108 stores instructions which, when executed on the data processing hardware 106, cause the data processing hardware 106 to perform the operations described herein.

[0027] The route planning application 104 includes a pedestrian route planner 110, which is configured to provide a pedestrian route 110a to a user 12 based on location data 112 entered by the user 12 and / or obtained from the positioning of the user device 200 and / or the vehicle 10. The location data 112 may, for example, include a starting point 112a, a current location 112b, and a destination 112c. The route planning application 104 is configured to create the pedestrian route 110a between the starting point 112a and the destination 112c, so that the user 12 can follow the pedestrian route 110a until the destination 112c is reached.

[0028] The specific development of pedestrian route 110a by the pedestrian route planner 110, including how pedestrian route 110a is selected in contrast to other possible routes between starting point 112a and destination 112c, is based on a variety of factors considered by the route planning application 104. These factors include, but are not limited to, the shortest distance between starting point 112a and destination 112c, the shortest travel time between starting point 112a and destination 112c, the fewest obstacles, hazards, or changes of direction between starting point 112a and destination 112c, and many other factors.

[0029] Furthermore, pedestrian route 110a contains parameters configured to create a safe and optimal route for user 12. These parameters include, among other things, sidewalk boundaries, the marking of curbs or changes in elevation, the marking of turns or stops, and similar features. The parameters provide user 12 with a suitable route that is optimally designed in terms of efficiency, safety, and clarity, enabling the pedestrian to successfully complete pedestrian route 110a and ultimately reach destination 112c. Other factors and parameters considered by pedestrian route planner 110 are described in more detail below. However, pedestrian route planner 110 is configured to select an optimal route based on information provided to and stored by route planning application 104.

[0030] The starting point 112a represents the point where user 12 wishes to begin walking route 110a. Walking route 110a is created by the walking route planner 110 between the starting point 112a and the destination 112c. User 12 can interact with the route planning application 104 by voice input, touch, or other means to enter the starting point 112a. Alternatively, the starting point 112a can also be generated automatically by the route planning application 104. For example, the starting point 112a can be the same as, and based on, the current location 112b of the user device 200, and thus of user 12. Similarly, the destination 112c represents a desired destination to which user 12 wishes to travel. User 12 can interact with the route planning application 104 by voice, touch, or other means to enter the destination 112c.

[0031] The current location 112b corresponds to the real-time location of user device 200 at a specific point in time. For example, the current location 112b of user device 200 may coincide with the starting point 112a of user device 200 before the journey along pedestrian route 110a begins. In this context, the current location 112b could be the starting point 112a, the destination 112c, or any location along pedestrian route 110a where user device 200 is situated.

[0032] The current location 112b of user device 200 enables controller 102 to continuously determine the current position of user device 200. In this context, pedestrian route planner 110 can continuously update pedestrian route 110a based on the current location 112b of user device 200, for example, when user device 200 is traveling along pedestrian route 110a. This allows pedestrian route 110a to be optimized during the operation of the route planning application 104, regardless of where user device 200 is located. For example, the current location 112b of user device 200 can indicate to controller 102 that user device 200 has deviated from pedestrian route 110a. This can cause the pedestrian route planner 110 to reconfigure pedestrian route 110a to account for the deviation, so that user 12 is still able to reach destination 112c.

[0033] Furthermore, the route planning application 104 enables hands-free operation through the integration of notifications 114, including a haptic feedback protocol 114a and an acoustic feedback protocol 114b. The haptic feedback protocol 114a generates haptic feedback, such as...

[0034] Vibrations are generated at the user device 200. The acoustic feedback protocol 114b produces audible feedback, such as noises or tones, at the user device 200. The haptic feedback protocol 114a and the acoustic feedback protocol 114b contain instructions linked to the notifications 114 during the operation of the route planning application 104. The instructions linked to the notifications 114 may correspond to obstacles, real-time restrictions, and navigation instructions along the pedestrian route 110a, which ultimately leads the user 12 to the destination 112c. In this respect, visually impaired persons can use the route planning system 100 similarly or identically to non-visually impaired persons, the operation and configuration of which are described in more detail below.

[0035] The notifications 114 encompass a variety of intensities 114c. In other words, the haptic feedback protocol 114a can generate haptic feedback with one of the variety of intensities 114c, depending on the notification 114. Similarly, the acoustic feedback protocol 114b can generate acoustic feedback with one of the variety of intensities 114c, depending on the notification 114. For example, if the notification 114 indicates that the user 12 is approaching an edge 14 of a sidewalk 16 while walking on pedestrian route 110a, the haptic feedback protocol 114a can cause the user device 200 to vibrate gently once, and / or the acoustic feedback protocol 114b can cause the user device 200 to emit a single tone.In another example, if notification 114 indicates that user 12 is approaching a pothole in the sidewalk 16 while walking on pedestrian route 110a, the haptic feedback protocol 114a can cause the user device 200 to vibrate strongly once, for example, at a high intensity from the plurality of intensities 114c, or the acoustic feedback protocol 114b can cause the user device 200 to emit two tones. The haptic feedback protocol 114a, the acoustic feedback protocol 114b, and the plurality of intensities 114c can vary depending on the configuration of the route planning system 100, without this deviating from the context of this invention.

[0036] In another example, the haptic feedback protocol 114a can contain instructions for user device 200 to vibrate once when it begins to move away from pedestrian route 110a, and to vibrate three times when it returns to pedestrian route 110a. In another configuration, the haptic feedback protocol 114a can contain instructions for user device 200 to vibrate twice when it begins to move away from pedestrian route 110a, and to vibrate four times when it returns to pedestrian route 110a. In many cases, the haptic feedback protocol 114a is linked to the current location 112b of the user device 200 with respect to the pedestrian route 110a, changes to the pedestrian route 110a, and the deviation of the user device 200 from the pedestrian route 110a.

[0037] In one configuration, the acoustic feedback protocol 114b can contain instructions for user device 200 to emit a single audible tone (i.e., notification 114) when user device 200 begins to deviate from pedestrian route 110a, and for user device 200 to emit three audible beeps (i.e., notification 114) when user device 200 returns to pedestrian route 110a. In another example, the acoustic feedback protocol 114b can contain instructions for user device 200 to emit two acoustic notifications 114 when user device 200 begins to deviate from pedestrian route 110a, and for user device 200 to emit four acoustic notifications 114 when user device 200 returns to pedestrian route 110a.In many cases, the acoustic feedback protocol 114b is linked to the current position 112b of the user device 200 with respect to the pedestrian route 110a, changes to the pedestrian route 110a, and the deviation of the user device 200 from the pedestrian route 110a.

[0038] The route planning application 104 uses and stores user behavior 116. User behavior 116 is configured to obtain pedestrian route data 116a, such as user 12's travel characteristics 116b, while the route planning application 104 is running. For example, user behavior 116 captures data such as user 12's average walking speed, instances of the user deviating from pedestrian route 110a, the frequency of user 12 stopping on pedestrian route 110a, and other data. In this context, user behavior 116 can provide the route planning application 104 with information about user 12's characteristics and how user 12 interacts with the route planning application 104.

[0039] Since each user may have different characteristics than other users, user behavior 116 allows the route planning system 100 to tailor nuances of its operation to each individual user. For example, user 12 of the route planning application 104 may repeatedly deviate from pedestrian route 110a while traveling from starting point 112a to destination 112c. In this case, the route planning application 104 can, on subsequent uses of the route planning application 104, generate pedestrian route 110a along a sidewalk that is away from major thoroughfares or roads where vehicles travel at high speeds for safety reasons. Instead, pedestrian route 110a can run along a sidewalk located near side streets or roads where vehicles travel at low speeds.The adaptation of the pedestrian route 110a in subsequent uses of the route planning application 104 based on user behavior 116 enables the route planning system 100 to provide tailored functionality for each individual user.

[0040] As mentioned previously, the controller 102 includes the memory hardware 108, which communicates with the data processing hardware 106. The memory hardware 108 contains automatic settings 108a and manual settings 108b. The automatic settings 108a of the memory hardware 108 can receive the user behavior 116 of the route planning application 104. The route planning application 104 is configured to adjust the pedestrian route 110a based on the user behavior 116 in order to optimize the pedestrian route 110a. Therefore, the user behavior 116 is communicated to the automatic settings 108a in the memory hardware 108 of the controller 102. When the user 12 starts the route planning application 104, the automatic settings 108a communicate with the route planning application 104 to configure the pedestrian route 110a based on the user behavior 116.This ensures that pedestrian route 110a is tailored as optimally as possible to each individual user.

[0041] The manual settings 108b of the storage hardware 108 comprise settings that are manually entered by the user 12 of the route planning application 104. The manual settings 108b may include, among other things, configuring the user device 200 to vibrate at one of the various intensities 114c when the haptic feedback protocol 114a is triggered, and configuring the pedestrian route planner 110 to avoid dirt or gravel paths when the pedestrian route 110a is being developed, and other examples. The manual settings 108b may include any practical setting associated with the route planning application 104 that can be configured or adjusted by the user 12. The user 12 can adjust the manual settings 108b by interacting with the route planning application 104 on the user device 200.The manual settings 108b are then stored in the memory hardware 108 of the controller 102. This allows the pedestrian route planner 110 to take the manual settings 108b into account when creating the pedestrian route 110a.

[0042] The route planning system 100 also includes a navigation system 400. The navigation system 400 is contained in both the vehicle 10, e.g., in the controller 102, and the user device 200. In this respect, the navigation system 400 is able to communicate with both the vehicle 10 and the user device 200 and is configured to extend the functionality of the route planning application 104. For example, the navigation system 400 can assist in the development of the pedestrian route 110a by providing information about possible routes between the starting point 112a and the destination 112c, the details of which are explained below.

[0043] The navigation system 400 is configured to store information relating to the development of pedestrian route 110a, including navigation instructions such as turning left, turning right, stopping at an intersection, distance to a turn, and other examples. The Navigation System 400 comprises a GPS (Global Positioning System) 402, a Real Time Kinematic (RTK) positioning 404, and a GNSS (Global Navigation Satellite System) chipset 406. The GPS 402, the RTK 404, and the GNSS chipset 406 can operate independently or together to assist in configuring pedestrian route 110a using the pedestrian route planner 110. For example, the GPS 402 and the GNSS chipset 406 can determine a global position of the starting point 112a, a global position of the current location 112b of the user device 200, and a global position of the destination location 112c.This "real-world" information regarding global positioning enables the pedestrian route planner 110 to develop pedestrian route 110a using established paths, roads, navigation instructions, etc., which the user 12 can follow. The navigation system also maintains a global positioning of pedestrian route 110a, especially as the user walks along pedestrian route 110a, thus providing real-time updates to the navigation instructions related to reaching the destination 112c. In this way, the route planning application 104 and the route planning system 100 can operate robustly and optimally.

[0044] The Navigation System 400 also includes waypoints 408, which are ultimately integrated into pedestrian route 110a. Waypoints 408 can be linked to data from the GPS-402, the RTK-404, the GNSS chipset 406, and other navigation instructions and events along pedestrian route 110a. In other words, the waypoints include at least one of the following: obstacles on pedestrian route 110a, changes of direction on pedestrian route 110a, and intersections on pedestrian route 110a. In this context, one of the waypoints 408 could be a road obstruction, such as a construction container blocking part of pedestrian route 110a. One of the waypoints 408 could be a pothole on pedestrian route 110a or a transition between a paved and a dirt path. One of waypoints 408 can be a left turn, a right turn, or a stop at an intersection.The waypoints 408 contained in the navigation system 400 and integrated into pedestrian route 110a can vary in number and variety, depending on the content of pedestrian route 110a. Furthermore, the waypoints 408 can be modified or changed in real time in the navigation system 400 based on changes to waypoints 408 detected locally by the user device 200 along pedestrian route 110a. For example, the user device 200 can detect an obstacle such as a pothole along pedestrian route 110a. The user device 200 can communicate with the navigation system 400 and classify the pothole as a waypoint 408, allowing the pothole to be integrated into pedestrian route 110a as a waypoint 408.In this context, the user device can collect 200 localized object detection / recognition information to determine waypoints 408 that may not have been detected, or may have been detected inaccurately, by the GPS-402, RTK-404 or GNSS chipset 406.

[0045] Furthermore, waypoints 408 can be linked to the haptic feedback protocol 114a and / or the acoustic feedback protocol 114b. In this regard, when the user device 200 approaches one of the waypoints 408 along the pedestrian route 110a, the haptic feedback protocol 114a can trigger a notification 114 on the user device 200 in the form of haptic feedback, causing the user device 200 to vibrate when one of the waypoints 408 is nearby or when it is approaching one of the waypoints 408. The haptic feedback protocol 114a can vary in intensity 114c, depending on the specific type of waypoint 408 that the user device 200 encounters along the pedestrian route 110a. For example, the haptic feedback protocol 114a can cause notification 114 on user device 200 to vibrate once if waypoint 408, which it is approaching, is a construction site bin.In another example, the haptic feedback protocol 114a can cause notification 114 on user device 200 to vibrate twice if the waypoint 408 it is approaching is a left turn.

[0046] Similarly, the acoustic feedback protocol 114b can trigger a notification to the user device 200 in the form of an acoustic feedback signal when the user device 200 approaches one of the waypoints 408 along the pedestrian route 110a, causing the user device 200 to emit a tone or noise when one of the waypoints 408 is nearby or when it is approaching one of the waypoints 408. The acoustic feedback protocol 114b can vary depending on the type of waypoint 408 that the user device 200 encounters along the pedestrian route 110a. For example, the acoustic feedback protocol 114b can cause the notification 114 on the user device 200 to emit a beep if the waypoint 408 it is approaching is a construction site bin.In another example, the acoustic feedback protocol 114b can cause notification 114 on user device 200 to emit two audible tones when waypoint 408, which it is approaching, is a left turn.

[0047] The navigation system 400 also includes a vehicle location 410, which records the current location of the vehicle 10. Since the navigation system 400 is contained in both the vehicle 10 and the user device 200, both the vehicle 10 and the user device 200 receive the vehicle location 410. The vehicle location 410 can support the operation of the route planning application 104 by maintaining the vehicle location 410 as a reference point when developing the pedestrian route 110a.

[0048] The network 300 belonging to the route planning system 100 enables wireless communication between the vehicle 10, and thus the controller 102, and the user device 200. The network 300 can also enable wireless communication with third-party servers outside of the route planning system 100. In this context, information provided by third-party servers can be retrieved by the vehicle 10 and / or the user device 200 and ultimately made available to the route planning application 104.

[0049] For example, the network 300 can be configured to enable communication with a continuously operating reference station (CORS) server 500 to obtain route and traffic data 500a. The route and traffic data 500a on the CORS server 500 is provided by a third party, such as a government-operated real-time traffic database. In other words, the route and traffic data 500a can provide information about current traffic reports, such as a car accident blocking a lane, roadworks, road closures, etc. In this context, the functionality of the route planning application 104 is enhanced by the route and traffic data 500a provided by the CORS server 500.

[0050] The route and traffic data 500a from the CORS server 500 provides navigation data with an extremely high degree of precision and accuracy. The network 300 is capable of transmitting the route and traffic data 500a to both the controller 102 in the vehicle 10 and the user device 200. This allows the pedestrian route 110a to be designed as optimally and precisely as possible. The route and traffic data 500a can be taken into account by the pedestrian route planner 110 when developing the pedestrian route 110a. For example, the route and traffic data 500a can indicate a road closure between the starting point 112a and the destination 112c. As a result, the pedestrian route planner 110 can configure the pedestrian route 110a to bypass the road closure.In another example, the route and traffic data 500a may indicate a sudden vehicle accident that occurred on pedestrian route 110a while user 12 is already en route to destination 112c. As a result, the pedestrian route planner 110 can reconfigure pedestrian route 110a to bypass the vehicle accident, allowing user 12 to reach destination 112c in a way that avoids the accident.

[0051] According to Fig. 1-4 The operation of the route planning system 100 is based on the configuration and interaction of the controller 102, the user device 200, the navigation system 400, and the CORS server 500 via the network 300. The operation of the route planning system 100 is enabled by the interaction of the user 12 with the route planning application 104. However, it should be emphasized that the route planning application 104 is included on both the user device 200 and the controller 102 in the vehicle 10. The route planning application 104 can be displayed on the user device 200, thus enabling its operation through user interaction with the user device 200. For example, if the user device 200 has a touchscreen, the user can interact with the route planning application 104 by physically touching the user device 200.However, it can be assumed that the user's interaction with the route planning application 104 is facilitated by speech recognition functions of the route planning application 104, for example, by a user speaking into the user device 200 to control the operation of the route planning application 104. Furthermore, a combination of physically touching the user device 200, speaking into the user device 200, or any other type of user interaction with the user device 200 can control the operation of the route planning application 104 without deviating from the context of this invention.

[0052] The current location 112b of user device 200 also helps controller 102 determine that user device 200 has successfully reached destination 112c. For example, controller 102 can use the current location 112b of user device 200 as confirmation of user device 200's arrival at destination 112c. The current location 112b of user device 200 can also provide portions of the pedestrian route data 116a to controller 102 by comparing the current location 112b of user device 200 at several points between starting point 112a and destination 112c with the pedestrian route 110a after destination 112c has been reached. The pedestrian route data 116a can, for example, indicate how accurately the pedestrian route 110a was followed between starting point 112a and destination 112c.For example, if the user device 200 has partially deviated from the pedestrian route 110a between the starting point 112a and the destination 112c, the current location 112b of the user device 200 will report the deviation as part of the pedestrian route data 116a to the controller 102.

[0053] With reference to Fig. Figure 5 describes a configuration procedure for the route planning system 100 at 600. Once the starting point 112a and the destination 112c have been received by the controller 102, the coordinates of the waypoints 408 between the starting point 112a and the destination 112c are determined in 602. The determination of the coordinates of the waypoints 408 can be performed by at least one of the GPS 402, RTK 404, and GNSS chipsets 406. At 604, the pedestrian route planner 110, which communicates with the navigation system 400 and the CORS server 500, generates the pedestrian route 110a. At 606, the pedestrian route 110a is located between the controller 102 and the user device 200.

[0054] With reference to Fig.At 700, an implementation procedure of the route planning system 100 is described. At 702, the user navigates to the starting point 112a to prepare the journey to the destination 112c. At 704, the pedestrian route 110a is created by the pedestrian route planner 110, which is included in the route planning application 104. At 706, the pedestrian route 110a is identified by the user device 200 within the route planning application 104. In addition, the waypoints 408 along the pedestrian route 110a are also identified and generated within the route planning application 104. The haptic feedback protocol 114a and the acoustic feedback protocol 114b are collected by the route planning application 104 to trigger the instructed notifications 114 at each waypoint 408 encountered along the pedestrian route 110a at 708.

[0055] When user device 200, and thus user 12, arrives at destination 112c, controller 102 confirms the arrival at destination 112c to 710 via the current location 112b of user device 200, which matches the destination 112c of user device 200. Furthermore, the current location 112b of user device 200 enables user behavior 116 of the route planning application 104 to collect pedestrian route data 116a associated with user device 200's adherence to pedestrian route 110a. The pedestrian route data 116a can also contain movement characteristics of the user device 200, which are obtained from the location data 112 as it moves along the pedestrian route 110a, in order to characterize, for example, user behavior 116 at 712 via machine learning algorithms and post-processing of the user's movement 12. At 714, the user behavior 116 is stored in the memory hardware 108.In subsequent uses of the route planning application 104, the pedestrian route planner 110 can use the user behavior 116 stored in the automatic settings 108a of the memory hardware 108 to further optimize the pedestrian route 110a based on the user's unique characteristics.

Claims

[1] Computer-implemented procedure which, when executed by data processing hardware, causes the data processing hardware to perform operations which include: Determine, using location data, the current location of a user device relative to the vehicle location of a vehicle; Determine, using location data, a starting point of a user device relative to the vehicle location and based on the current location, and a destination of the user device relative to the vehicle location and based on user input; Identify, via a pedestrian route planner of a route planning application communicating with a navigation system, a pedestrian route between the starting point of the user device and the destination of the user device; Identify, via the navigation system, waypoints between the starting point of the user device and the destination of the user device; Transmitting the pedestrian route to the user device; Output, via the route planning application, i) a haptic feedback protocol and / or ii) an acoustic feedback protocol that is / are linked to the waypoint(s); Receiving pedestrian route data linked to the pedestrian route from the user device; and Processing pedestrian route data to determine user behavior, based on which the pedestrian route is identified. [2] Method according to claim 1, wherein the navigation system comprises at least one of the following systems: Global Positioning System (GPS), Real Time Kinematic Positioning (RTK) and a GNSS (Global Navigation Satellite System) chipset. [3] Method according to claim 2, further comprising: continuously updating the pedestrian route in response to changes associated with the current location of the user device, the GPS, the GNSS chipset and RTK. [4] Method according to claim 1, further comprising: coupling and transferring between the data processing hardware and the user device via a network. [5] Method according to claim 1, wherein the haptic feedback protocol and the acoustic feedback protocol are further linked to i) the current location of the user device in relation to the pedestrian route, ii) changes in the pedestrian route and iii) the deviation of the user device from the pedestrian route. [6] Method according to claim 1, wherein the haptic feedback protocol and the acoustic feedback protocol comprise a plurality of intensities associated with one or more of the following: the current position of the user device in relation to the pedestrian route, changes to the pedestrian route, the deviation of the user device from the pedestrian route and the waypoints. [7] Method according to claim 1, wherein the waypoints comprise at least one of the following elements: i) obstacles on the pedestrian route, ii) changes of direction on the pedestrian route and iii) intersections on the pedestrian route. [8] Method according to claim 1, wherein the current location of the user device corresponds to the starting point of the user device. [9] Method according to claim 1, wherein the starting point of the user device is entered manually.

Images