METHOD AND APPARATUS FOR RENDERING A PARKING SEARCH ROUTE

An approach is provided for presenting to a user in a vehicle a visual representation of a route for finding a parking space for the vehicle, wherein the route comprises road segments having potential parking spaces for the vehicle within a threshold of a destination. The approach involves upon determining that a visual representation of the route meets a criterion for complexity, providing a visual representation of an initial extent of the route to the user in a user interface, wherein the initial extent comprises a portion of the route ahead of a current position of the user and further wherein the visual representation of the initial extent does not meet the criterion for complexity. The approach also involves providing a route extension icon rendered at the initial extent in the user interface.

BACKGROUND

Providing navigation support to users is an important function for map service providers. Modern devices such as sophisticated navigation and communication systems can enable users or drivers of vehicles to have a better understanding of what is ahead or approaching on a road or route (e.g., points of interest (POIs), complicated interchanges, traffic status, road closures, etc.). In addition, providing parking support information (e.g., parking locations and/or parking availability) is another important function for map service providers. Parking support information is particularly useful in areas (e.g., a city center) where finding available parking may be time consuming and/or frustrating. However, presenting or visualizing a parking search route to users in a quickly readable manner can be challenging where such routes overlap, intersect, and/or loop, etc. until an available parking space is found within the vicinity of a destination.

SOME EXAMPLE EMBODIMENTS

As a result, there is a need for presenting to a user of a vehicle an efficient visual representation of a complex parking search route.

According to one embodiment, a computer-implemented method for presenting to a user in a vehicle a visual representation of a route for finding a parking space for the vehicle, wherein the route comprises road segments having potential parking spaces for the vehicle with a threshold of a destination, the method comprising upon determining that a visual representation of the route meets a criterion for complexity, providing a visual representation of an initial extent of the route to the user in a user interface, wherein the initial extent comprises a portion of the route ahead of a current position of the user and further wherein the visual representation of the initial extent does not meet the criterion for complexity. The method also comprises providing a route extension icon rendered at the initial extent in the user interface.

According to another embodiment, an apparatus for presenting to a user in a vehicle a visual representation of a route for finding a parking space for the vehicle, wherein the route comprises road segments having potential parking spaces for the vehicle within a threshold of a destination comprises at least one processor, and at least one memory including computer program code for one or more computer programs, the at least one memory and the computer program code configured to, with the at least one processor, cause, at least in part, the apparatus to upon determining that a visual representation of the route meets a criterion for complexity, provide a visual representation of an initial extent of the route to the user in a user interface, wherein the initial extent comprises a portion of the route ahead of a current position of the user and further wherein the visual representation of the initial extent does not meet the criterion for complexity. The apparatus is also caused to provide a route extension icon rendered at the initial extent in the user interface.

According to another embodiment, a non-transitory computer-readable storage medium for presenting to a user in a vehicle a visual representation of a route that circles in a vicinity of a location until a condition is met, wherein the route comprises road segments within a threshold of the location carries one or more sequences of one or more instructions which, when executed by one or more processors, cause, at least in part, an apparatus to upon determining that a visual representation of the route meets a criterion for complexity, provide a visual representation of an initial extent of the route to the user in a user interface, wherein the initial extent comprises a portion of the route ahead of a current position of the user and further wherein the visual representation of the initial extent does not meet the criterion for complexity. The apparatus is also caused to provide a route extension icon rendered at the initial extent in the user interface.

According to another embodiment, an apparatus for presenting to a user in a vehicle a visual representation of a route for finding a parking space for the vehicle, wherein the route comprises road segments having potential parking spaces for the vehicle within a threshold of a destination comprises means for upon determining that a visual representation of the route meets a criterion for complexity, providing a visual representation of an initial extent of the route to the user in a user interface, wherein the initial extent comprises a portion of the route ahead of a current position of the user and further wherein the visual representation of the initial extent does not meet the criterion for complexity. The apparatus also comprises means for providing a route extension icon rendered at the initial extent in the user interface.

For various example embodiments, the following is applicable: An apparatus comprising means for performing the method of any of the claims.

DESCRIPTION OF SOME EMBODIMENTS

Examples of a method, apparatus, and computer program for presenting to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle are disclosed. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention. It is apparent, however, to one skilled in the art that the embodiments of the invention may be practiced without these specific details or with an equivalent arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the invention.

FIG. 1is a diagram of a system capable of presenting to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle (i.e., a parking search route), according to one embodiment. As described above, providing navigation support to users is an important function for map service providers. By way of example, a user may be a driver of a standard vehicle (e.g., a car, a truck, a motorcycle, etc.), a passenger of an autonomous or highly-assisted vehicles (HAD) vehicle, a cyclist, a pedestrian, or a combination thereof. Navigation systems (e.g., an embedded car navigation system, a mobile device, etc.) can enable users to have a better understanding of what is coming ahead or approaching on a road or route on which they are traveling (e.g., POIs, complicated interchanges, traffic status, road closures, detours, etc.). In some instances, the rendered route may also include secondary or tertiary or other information. For example, certain portions of the route may be rendered in a color to represent a level of traffic and/or delay. In another example, multiple or alternative routes may be simultaneously rendered to provide a user with various options to reach a given destination. As the complexity of the routes and/or associated information being conveyed increases, service providers face significant challenges to presenting route information in a way that can be quickly and easily understood by end users (i.e., without confusion of the user).

One example of a potentially complex parking search route is a route that continues, overlaps, intersects, and/or loops, etc. until an available parking space is found within the vicinity of a destination (i.e., the route may be considered infinite and/or endless). As mentioned above, parking guidance and/or parking related information is also an integral function for map service providers. For example, a user may want to know where she or he can find parking (e.g., on-street parking, car parks, parking garages, etc.) at or near a given destination and she or he may also want to know whether parking is or will be available at such locations and times. In many instances, a user wants to know this information in real time or substantially real time. Parking guidance and/or parking search routes may be particularly useful to users in areas where finding a parking space is often time consuming and/or frustrating due to a limited number of free spaces and/or many users simultaneously looking for parking (e.g., city centers). In addition, drivers need to pay attention to applicable driving restrictions (e.g., no left turns) while monitoring the possibly free spaces, which can also make finding parking in such areas challenging.

However, a parking search route or other complex navigation route may become very hard to read in a quick and efficient manner when being visualized or rendered in a user interface (UI) to a user in a vehicle. For example, a complex route can be calculated to have a user or a driver circle within a defined area (e.g., a geo-fenced area) around a specified destination. As a result, different portions of the presented route may overlap, intersect (e.g., self-intersect or cross over itself), even loop making it difficult for a user to know what is coming ahead and/or confused by this information. In addition, providing a user with all available information/options/alternatives can make the parking search route convoluted and difficult to quickly understand, especially in a user interface (e.g., a mobile device). In some instances, such displays may be distracting and/or may not comply with applicable regulations (e.g., National Highway Traffic Safety Administration (NHTSA) prohibiting users from looking at a display too long to understand what actions to take (i.e., keeping one's eyes away from the road).

FIGS. 2A and 2Bare diagrams illustrating examples of visualizations of complex parking search routes. Referring toFIG. 2A, an example route201to the destination203is rendered or visualized in the UI205(e.g., an embedded navigation system). In this example, the segment201aof the route201comprises destination guidance and the segment201bcomprises a parking search route for finding parking in proximity to the destination203. In this instance, it may be hard to read the route201. For example, it may be unclear where the segment201astops and the segment201bstarts due a portion of the segment201aoverlapping a portion of the segment20lb. Specifically, a user may want to know where to begin looking for an available parking space. In addition, the segment201bloops around and intersects with itself (i.e., crossing itself), possibly making it difficult for a user to know where to go and/or what is being recommended.

Referring toFIG. 2B, an example route207to the destination209is rendered or visualized in the UI211(e.g., a mobile device). In this example, the segment207acomprises destination guidance and the segments207b-207dcomprise links of a parking search route for finding parking in proximity to the destination209. Specifically, in this example, the segments207b-207dare rendered in colors based on a determined parking probability (e.g., red, orange, and green). In this instance, rather than assisting the user, the additional layers of information may make the route207difficult to read. For example, a user may have a hard time discerning where one segment stops, and another starts, particularly where one or more segments intersect and/or loop around each other.

To address these technical problems, a system100ofFIG. 1introduces a capability to visualize a complex parking search route in a convenient way by dynamically computing the limit or extent of the route to be presented to a user of a vehicle at one time (i.e., the initial extent) and by updating the extent and/or presentation to visualize additional route segments as the user travels along the route. In other words, the system100may only visualize to the user of the vehicle the portion of the route that is immediately relevant to the user at her or his present location despite the system100's ability to visualize or present the entire and/or potentially endless route to an available parking space in the vicinity of the destination. Then, once the user moves along the route, the system100can present a new limited portion of the route (i.e., another extent) to the user based on the user's new location. In one embodiment, to make a complex parking search route useful and visually appealing, the system100reduces the amount of information that is simultaneously presented to the user (e.g., through an embedded navigation system, mobile device, or a combination thereof), hence the system100computes a route and then simplifies the rendering of the route to advantageously help users to more quickly view and absorb the route and related information (e.g., to find an available parking spot). In one embodiment, the system100reduces the information and/or simplifies the route through the detection of one or more “route limits” that determine how much of the route is presented to a user at one time as described below. Consequently, a user can know what is coming ahead without being confused by too much information and/or irrelevant information. Although the disclosure is primarily described herein with respect to presenting a parking search route to a user of a vehicle, it is contemplated that the disclosure may apply to any complex navigation route wherein a user is in a vehicle and the user and/or the vehicle (e.g., an autonomous vehicle) is searching for someone (e.g., one or more additional passengers), something (e.g., one or more pick-up/drop-off locations, one or more gas or charging stations, etc.), or a combination thereof and the visualized route may continue, overlap, intersect, and/or loop, etc. until the someone and/or something is located.

In one embodiment, the system100ofFIG. 1may include one or more vehicles101a-101n(also collectively referred to herein as vehicles101) configured with one or more vehicle sensors103a-103n(also collectively referred to herein as vehicle sensors103) (e.g., a global positioning system (GPS) sensor), one or more user equipment (UE)105a-105n(also collectively referred to herein as UEs105) (e.g., an embedded navigation system, a mobile device, a smartphone, etc.) having connectivity to a routing platform107via a communication network109. By way of example, the vehicles101may be standard vehicles (e.g., a car, a truck, a motorcycle, etc.), autonomous vehicles, or highly assisted driving (HAD) vehicles. Although the vehicles101are depicted as automobiles, it is contemplated that the vehicles101may be any type of transportation that parks, at least occasionally (e.g., a car, a truck, a motorcycle, a bike, a scooter, etc.).

In one embodiment, the system100first determines a destination (e.g., a restaurant, a movie theater, a shop, etc.) that does not have convenient available parking (e.g., an attached parking lot or parking structure). In one instance, the system100determines the destination based on a user manually setting or inputting the destination using one or more applications111a-111n(also collectively referred to herein as applications111) (e.g., a navigation application, a mapping application, a parking application, etc.) associated with the UEs105.

In one embodiment, the system100then determines the parking spot availability in a zone around a destination or within a threshold of the destination and computes the best possible route to the parking spot. In one instance, the best possible route comprises an infinite/endless route. For example, the system100may continue to calculate and to render the parking search route until the user finds parking and has parked. Further, in one instance, if a user is unable to find parking at or around the given destination (e.g., within a threshold distance of the destination), the system100may suggest another comparable destination and continue or extend the route to that destination. In one embodiment, the system100determines the best possible route depending on parking availability, driving situation, and walking distance. In one instance, the system100may determine the parking spot availability based on information or data stored in or accessible via a geographic database (e.g., a geographic database113), a digital map, or a combination thereof. In one embodiment, the system100may also determine the parking spot availability based on one or more parking related factors. For example, the one or more relevant parking related factors may include temporal factors (e.g., time of day, day of week); contextual factors (e.g., starting and/or ending times of an event); regulatory factors (e.g., no parking permitted), or a combination thereof. In one embodiment, the system100can define the zone based on a driving situation and/or a walking distance. For example, in one instance, the system100can compute the zone to include at least one or more roads or links that would permit the user or the driver to find available parking. In one embodiment, the threshold can be time-based, distance-based, or a combination thereof. By way of example, the system100can define the zone such that when a user finds parking, they are less than a certain distance and/or an amount of time away from the destination (e.g., within walking distance).

In one embodiment, the system100identifies when the readability of the parking search route would become low if visualized to a user all at one time and, therefore, leading to bad user experience. In one instance, the system100determines the readability of the route by computing the structural and aesthetical components of the route (i.e., “route limits”) such as intersections, overlaps, turns, walk time, etc. In one embodiment, the system100determines the so called “limit” of the route to be rendered or “route limits” based on one or more of the following rules: (1) road segments should not overlap; (2) route segments should ideally not intersect or cross; (3) route segments should ideally not make loops; (4) the system 100 should consider the aesthetics of the route if possible; and (5) some availability threshold may be considered by the system100for the route rendering as well. In other words, if a user is likely to quickly find a spot, the route displayed by the system100may be shorter than the same path which would have lower parking chances. By way of example, an overlapping segment is a segment that is rendered in opposite directions on the same road in connection with a destination such that two segments overlap each other. A looping segment, for example, is a segment that passes through the same node (e.g., an intersection) in connection with a destination without overlapping. In both instances, the route may be difficult for a user to read without being confused.

In one embodiment, the system100only displays or presents the segments of the parking search route up until the computed virtual limit of the route rendering (i.e., the route meets a criterion for complexity). In one instance, the system100renders only the segments that can be displayed without potential confusion to the user despite the system100's ability to render the entire route to the destination. In one embodiment, the system100can “unlock” the route (i.e., render the route) when a driver of a vehicle101passes the intersection point with the “limit” of the parking search route. In one embodiment, the system100can render or visualize the route up to a certain probability of finding a parking space. For example, the system100can render shorter routes when a user or a driver of a vehicle101is passing through road segments with a high probability of having potential parking spaces for the vehicle101and the system100can render longer routes when a user or a driver of a vehicle101is passing through road segments with a low probability of having potential parking spaces for the vehicle101. In one embodiment, the system100can determine the probability of available parking by collecting data or information from the geographic database113relative to the one or more road segments.

In one embodiment, the system100can enable a user to preview one or more “future” portions of the parking search route through one or more interactions (e.g., touch, voice, gesture, etc.). For example, the system100can render a route extension icon at the end of the currently visible route (i.e., the initial extent). In one embodiment, the system100can enable the user to extend the rendering of the route (e.g., beyond the computed “limit”) based on determining one or more interactions by the user. For example, a user can manually adjust the limit of the route (e.g., via an application111) to see how it further expands (e.g., to let a friend following behind know where additional parking may be available). In one instance, the route could also expand when a vehicle101speed is null (e.g., the vehicle101is stopped at a traffic light or a stop sign) so that the user can preview a few more maneuvers. In one embodiment, the system100can also enable a user to extend the route through a voice command (e.g., “show me more”). In one embodiment, the system100returns the rendering back to the previous state after the user releases/finishes her or his manual interaction, so that the user-friendly guidance of the system100can continue as described above.

FIGS. 3A-3Gare diagrams illustrating the process ofFIG. 1for presenting to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle, according to one embodiment. In one embodiment, the system100generates a UI301for a UE105(e.g., an embedded navigation system, a mobile device, or a combination thereof) to enable a visualization of the route303. In this example, the system100determines that a user or a driver of a vehicle101will need a parking spot at or near the destination305. By way of example, the system100may determine the destination305based on an input from the user via an application111(e.g., a navigation application). In this example, the user or the driver of the vehicle101may first want to know how to get to the destination305and then where she or he may park. In one embodiment, the system100identifies when the readability of the route303will become low, leading to a potentially bad user experience. In this instance, the system100may render or present to the user or the driver of the vehicle101only the portion of the route303(e.g., segment303a) that is within an aesthetic and/or readability limit given the determined location of the user or the driver of the vehicle101, as depicted inFIG. 3A. For example, the system100can determine that at the current location and/or time, any parking related information would make the route303hard to read and likely to confuse the user or the driver of the vehicle101and, therefore, should not be presented at this time despite the system100's ability to do so.

Referring toFIG. 3B, in one embodiment, the system100only displays the segments (e.g.,303aand303b) until the route303reaches a computed limit (e.g., a route limit, a criterion for complexity, or a combination thereof). In one embodiment, the system100adapts the rendering of the route303dynamically and extends this “limit” when possible. In this example, the system100may render or extend the route303up until the point where the segment303bwould intersect with the segment303a.In this instance, the segment303bcomprises a parking search route as opposed to the destination guidance portion303a.In one embodiment, the system100discontinues rendering the portions of the route303that the user or the driver has already traveled (e.g., portions of segment303a) to simplify and to improve the visual appeal of the route303. In one embodiment, the system100can update or re-render the route303in real time or substantially real time based on the location of the user or the driver of the vehicle101relative to the route303and/or the destination305. In one embodiment, the system100can determine the location of the user or the driver of the vehicle101by collecting sensor data from the vehicle sensors103, the satellites115, or a combination thereof.

As shown inFIG. 3C, in one embodiment, once the system100determines that the user or the driver of the vehicle101has passed the location where the segment303bwould have previously intersected with the segment303a,the system100can continue rendering or extending the route303accordingly. In one embodiment, the system100continues to render or to extend the route303up until the limit and/or until the user or the driver of the vehicle101finds parking. Referring toFIG. 3D, in this example, the system100can determine that the user or the driver of the vehicle101still requires parking search assistance; however, the segment303bis about to intersect and/or overlap with itself. Accordingly, in one embodiment, the system100will not present the route303past this location until the user or the driver of the vehicle101proceeds further. As shown inFIG. 3E, in one embodiment, the system100can enable a user to view an alternative route303(e.g., segment303c) so long as the route303does not include any overlapping and/or intersecting paths (i.e., can be displayed without confusion of the user).

In one embodiment, the system100can render the route303up to a certain probability value of finding a parking space. For example, the route303rendered by the system100may be shorter where the user of the vehicle101is passing through portions of segment303bthat have a relatively high probability of finding parking for the vehicle101and longer where the user or the vehicle101is passing though portions of segment303bthat have a relatively low probability of finding parking for the vehicle101, as depicted inFIGS. 3F and 3G, respectively. In one embodiment, the system100may determine the probabilities of the respective portions or segments based on data or information stored in the geographic database113. In one instance, the system100may render each portion of the segment303bwith a respective percentage of likelihood or probability of finding parking, a color suggestive of the respective probabilities, or a combination thereof. For example, the system100may render the segment303bofFIG. 3Fcorresponding to 10% as red and the system100may render the segments303bofFIG. 3Gcorresponding to 20% and 60% as yellow and green, respectively.

FIG. 4is a diagram of the components of the routing platform107, according to one embodiment. By way of example, the routing platform107includes one or more components for presenting to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle. It is contemplated that the functions of these components may be combined in one or more components or performed by other components of equivalent functionality. In one embodiment, the routing platform107includes a mapping module401, a data processing module403, a rendering module405, a user interface (UI) module407, and a calculation module409with connectivity to the geographic database113. The above presented modules and components of the routing platform107can be implemented in hardware, firmware, software, or a combination thereof. Though depicted as separate entities inFIG. 1, it is contemplated that the routing platform107may be implemented as a module of any of the components of the system100. In another embodiment, the routing platform107and/or one or more of the modules401-409may be implemented as a cloud-based service, local service, native application, or combination thereof. The functions of the routing platform107and/or the modules401-409are discussed with respect toFIG. 5below.

FIG. 5is a flowchart of a process for presenting to a user of a vehicle (e.g., a vehicle101) an efficient visual representation of a complex route for finding a parking space for the vehicle (i.e., a parking search route). In various embodiments, the routing platform107and/or the modules401-409may perform one or more portions of the process500and may be implement in, for instance, a chip set including a processor and a memory as shown inFIG. 9. As such, the routing module platform107and/or modules401-409can provide means for accomplishing various parts of the process500, as well as means for accomplishing embodiments of other processes described herein in conjunction with other components of the system100. Although the process500is illustrated and described as a sequence of steps, it is contemplated that various embodiments of the process500may be performed in any order or combination and need not include all of the illustrated steps.

In one embodiment, the route comprises road segments having potential parking spaces for the vehicle within a threshold of a destination (e.g., within a walking distance). In another embodiment, the route circles in the vicinity of a location until a condition is met, wherein the route comprises road segments within a threshold of the location. By way of example, the route may circle in the vicinity of a friend's or colleague's home and the condition may be met when the friend or colleague is ready to be picked up by a user of a vehicle101(e.g., a driver or an operator) and/or a vehicle101(e.g., an autonomous vehicle) to go work, a POI (e.g., a restaurant), etc. In another example, the route may circle in the vicinity of a school and the condition may be met when the students attending the school are picked up by a user of vehicle101and/or a vehicle101and brought to school. In a further example, the route may circle in the vicinity of an airport, a sporting or entertainment venue, etc. and the condition may be met when the travelers or the attendees are picked up by a user of a vehicle101and/or a vehicle101from one or more satellite locations and brought to the airport or the venue, respectively. In one embodiment, the route can be any navigation or complex route that is to be presented to an end user in a vehicle (e.g., a vehicle101). As discussed above, the route can include but is not limited to a parking search route or other complex navigation route (e.g., a route that includes self-intersections, loops, etc. that can be visually confusing to render). This route can be computed by the mapping module401or otherwise provided to the mapping module401. For example, the route may have no specified destination and/or may be traveled until a condition is achieved (e.g., all students are picked up before the start of school).

In one embodiment, the condition is finding a parking space (e.g., for a vehicle101) proximate to or in the vicinity of at a destination specified by a user (e.g., within a distance-based threshold, a time-based threshold, or a combination thereof). By way of example, the destination may be any POI such as a home, an office, a restaurant, a hospital, a shop, a park, a playground, a museum, a sport or an entertainment venue, etc. that a user or driver of a vehicle (e.g., a vehicle101) wants to park at or near, but that does not have convenient available parking (e.g., an attached parking lot or parking structure). Typically, such destinations are in densely populated areas (e.g., a city center) and do not have convenient available parking due to the high costs associated with such properties. In one embodiment, a user can specify the destination through an interaction or input (e.g., a touch, a voice command, a gesture, etc.) with an application111(e.g., a navigation application) associated with a UE105, a vehicle101, or a combination thereof. By way of example, the computed route may be considered a complex route because the route can be traveled infinitely, endlessly, indeterminately, etc. until the condition is met (i.e., the user parks). In this way, the mapping module403may continue to render or visualize the route (e.g., via an embedded navigation system) until the user parks or ends the route. For example, the route may “circle” around itself or along one or more streets around the destination before an available parking space is found. The problem with such complex parking search routes; however, is that they can become very hard to quickly and efficiently read when being visualized to a user in a vehicle, especially if a user is having difficulty finding parking. For example, the rendered road segments may start to overlap, intersect, or make loops, with previously traveled portions, portions not yet traveled, or a combination thereof, all which can prevent a user from knowing what is coming ahead without being confused by the information. Other navigation routes that can be used according to the process500can include any route wherein a user is in a vehicle101and the user and/or the vehicle101(e.g., an autonomous vehicle) is searching for someone (e.g., one or more additional passengers), something (e.g., one or more pick-up/drop-off locations, one or more gas or charging stations, etc.), or a combination thereof and the visualized route may continue, overlap, intersect, and/or loop, etc. until the someone and/or something is located (i.e., a condition is met).

In step501, upon the data processing module403determining in conjunction with the mapping module401that a visual representation of the route (e.g., a parking search route) meets a criterion of complexity (i.e., cannot be displayed without confusing the user), the rendering module405in connection with the UI module407provides a visual representation of an initial extent of the route to a user in a vehicle (e.g., a vehicle101) in a user interface (e.g., a UE105). In one embodiment, the initial extent comprises a portion of the route ahead of a current position of the user and the visual representation of the initial extent does not meet the criterion for complexity (i.e., can be displayed without confusion of the user). By way of example, the initial extent may be the minimal amount of the route ahead of the current position of the user that the calculation module409determines is useful and/or visually appealing to the user. For example, a visualization or rendering of a parking search route at the end of the destination guidance route when there are still hours of traveling before the destination is likely to make the route hard to read and/or confuse the user. This is especially true at higher zoom levels (e.g., in a route overview mode). Likewise, a visualization or rendering of previously traveled portions when a user is searching for parking is likely to make the route hard to read and/or confuse the user.

In one embodiment, the rendering module405renders another extent of the route beyond the initial extent rendered in the user interface based on the mapping module401determining that a location of the user of the route is at or within a proximity threshold of the initial extent (e.g., the user is about to complete traveling the initial extent of the route). In this regard, the rendering module405can provide the visual representation to the user dynamically. Specifically, in one embodiment, the calculation module409is constantly updating the criterion for complexity (i.e., the amount that can or cannot be displayed without confusion of the user) and the rendering module405is constantly updating the presentation or rendering within the computed limits as the user travels the route.

In one embodiment, the calculation module409determines the visual representation of the initial extent of the route based on a criterion for complexity or a route limit. In one instance, the criterion or route limit is a structural and/or aesthetical component of the route (e.g., intersections, overlaps, turns, walk times, etc.). In one embodiment, the criterion for complexity includes avoiding at least one of: (1) an overlap of two or more road segments; (2) an intersection of two or more road segments; and (3) a making of a loop with two or more road segments. In one instance, the road segments have potential parking spaces for the vehicle101within a threshold of the destination (e.g., a walkable or walking distance). By way of example, an intersection of two or more road segments comprises self-intersecting segments or a perpendicular crossing of the segments. By way of another example, a loop passes through the same node (e.g., an intersection) without overlapping. In one instance, the calculation module409also determines the criterion of complexity based on a route aesthetic criterion, a route readability criterion, or a combination thereof. By way of example, an aesthetically pleasing and/or readable route may be a simple route that includes the minimal amount of information needed to find a parking spot. Further, the calculation module409determines the criterion for complexity, in one instance, based on a speed of a vehicle101traveling the route. By way of example, because the calculation module409is constantly updating the route as the user drives or travels it, the criterion of complexity corresponds to the speed of the vehicle101(i.e., the faster or slower that the vehicle101moves, the faster or slower that the calculation module409needs to determine the criterion).

In one embodiment, the calculation module409can decrease the initial extent provided to the user based on determining an increase in the potential parking spaces on the road segments of the route and the calculation module409can increase the initial extent provided to the user based on determining a decrease in the in the potential parking spaces on the road segments of the route. By way of example, the data processing module403may provide parking space data stored in or accessible via the geographic database113, a digital map, or a combination thereof. In one embodiment, the data process module401may provide parking space data based on one or more parking related factors. For example, the one or more relevant parking related factors may include temporal factors (e.g., time of day, day of week); contextual factors (e.g., starting and/or ending times of an event); regulatory factors (e.g., no parking permitted), or a combination thereof.

In one embodiment, the data processing module403provides parking space data relative to a zone around the destination. For example, the mapping module401and/or the calculation module409can define the zone based on a driving situation and/or a walking distance. In one embodiment, the mapping module401can compute the zone to include at least one or more roads or links that would permit the user or the driver of a vehicle101to find available parking. In one instance, the calculation module409can define the zone such that when a user finds parking, they are less than a distance-based threshold, a time-based threshold, or a combination thereof from the destination (e.g., within walking distance). In one embodiment, the data processing module403can then provide the parking space data to the rendering module405for rendering of the initial extent of the route to the user in a user interface (e.g., a UE105). By way of example, if a user is likely to quickly find a spot, the initial extent presented may be shorter than a route which would have lower parking chances. In one instance, the calculation module409determines a stricter criterion of complexity, hence a shorter route, where the user is passing through road segments that are likely to have available parking and the calculation module409determines a more generous criterion, hence a longer route, where the user is passing through road segments that are unlikely to have available parking.

In step503, the rendering module405in connection with the UI module407provides a route extension icon rendered at the initial extent in the user interface (e.g., a UE105). In one embodiment, the rendering module405renders or presents another extent of the route beyond the initial extent rendered in the user interface (e.g., an embedded navigation system, a mobile device, or a combination thereof) based on the UI module407detecting a user interaction with the route extension icon in the user interface (e.g., a UE105). Specifically, in one instance, the visual representation includes a route extension icon rendered at the initial extent of the route in the user interface. An example of a route extension icon is depicted inFIG. 6C. In one embodiment, the UI module407enables a user (e.g., a user or a driver of a vehicle101) to extend the presentation of the route beyond the initial extent at any time. Whereas in one instance, the route “unlocks” itself when the user passes the intersection point with the “limit” of the route without any user interaction (i.e., dynamically), in another instance, the UI module407enables a user to manually preview one or more future portions or segments of the route irrespective of the user's location. For example, a user may extend the route by manually pressing the route extension icon (e.g., via an application111) to see how the route further expands (even if endlessly). In another example, the rendering module405can render a route extension icon when the user or the driver of a vehicle101is stopped (e.g., at a traffic light or a stop sign) so that the user or the driver can preview a few more maneuvers. Further, in one embodiment, the rendering module405can extend the route based on the UI module407receiving a voice command (e.g., “show me more”).

FIGS. 6A-6Dare diagrams of example user interfaces for presenting to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle or other complex/potentially visually confusing navigation routes), according to one embodiment. In this example, a UI601is generated for a UE105(e.g., an embedded navigation system, a mobile device, or a combination thereof) that includes a display603that enables a user to access a navigation application111of the system100to initiate the visualization of a complex route, as described above. In this example, a driver of a vehicle101uses the input605of the UI601to enter the destination607(e.g., “Restaurant ABC”). In this instance, the destination607is in a nearby city center. In one embodiment, the system100can determine that the destination607does not have any convenient parking (e.g., via data or information collected from the geographic database113). Accordingly, in one embodiment, the system100can ask the user if she or he wants the system100to present a visual representation of a route for finding a parking space for the vehicle101in the UI601(i.e., present a parking search route). In this example, the driver uses the input609to prompt the system100in the affirmative (e.g., by tapping “yes”). As described above, if the system100were to simultaneously render the complete destination guidance route and/or parking search route to the destination607, the route could become very hard to read and/or confusing to the user.

In one embodiment, the system100determines the part or portions of the route that can be displayed without confusing the user (i.e., the initial extent that does not meet the criterion for complexity and/or would confuse the user). Specifically, the system100dynamically computes the limit of the route to be presented and then updates the route as the user drives or travels along the route. In this instance, the system100can determine to present only the portion of the route611(e.g., segment611a) that is within an aesthetic and/or readability limit given the determined location of the user or the driver of the vehicle101(e.g., at home or a start of the journey). For example, the system100can determine that at this distance and/or time from the location607, providing parking search information to the user would likely decrease the readability of the route611and, therefore, lead to a potentially bad user experience.

Alternatively, in one embodiment, the system100can show the user a next step (e.g., segment611b), as depicted inFIG. 6B, but only enable or allow additional previews through a user interaction with the route extension icon613in the UI601, as depicted inFIGS. 6C and 6D, respectively. Referring toFIG. 6B, in one embodiment, the system100renders the segment611bup until the limit where the segment611bwould intersect segment611aor itself at or near the destination607(i.e., the route611would meet the criterion for complexity). As described above, the reason for limiting the rendering in this instance is that intersecting route segments may reduce the readability of the route611.

Referring toFIG. 6C, in one embodiment, once the system100presents the route611to a limit (i.e., an initial extent), the system100can enable the user to manually extend the route611past the virtual limit (i.e., view another extent) by interacting with the route extension icon613(e.g., via a touch, a tap, a gesture, or the like). It is contemplated that the user could also interact with the route extension icon613through a voice command (e.g., “show me more”). Once the system100determines an interaction by the user, the system100can extend the route611(e.g., segment611c). In one embodiment, the system100may extend the route611one segment at a time corresponding to each interaction with the route extension icon613(e.g., a tap or a press), the system100may extend the route611completely in response to a double tap or long press of the route extension icon613, or a combination thereof. In one embodiment, the system100discontinues rendering the segment611conce the user releases/finishes interacting with the route extension icon613so that the user-friendly guidance can continue.

Returning toFIG. 1, in one embodiment, the UEs105can be associated with any of the vehicles101or a user or driver of a vehicle101. By way of example, the UEs105can be any type of mobile terminal, fixed terminal, or portable terminal including a mobile handset, station, unit, device, multimedia computer, multimedia tablet, Internet node, communicator, desktop computer, laptop computer, notebook computer, netbook computer, tablet computer, personal communication system (PCS) device, personal navigation device, personal digital assistants (PDAs), audio/video player, digital camera/camcorder, positioning device, fitness device, television receiver, radio broadcast receiver, electronic book device, game device, devices associated with one or more vehicles or any combination thereof, including the accessories and peripherals of these devices, or any combination thereof. It is also contemplated that a UE105can support any type of interface to the user (such as “wearable” circuitry, etc.). In one embodiment, the one or more vehicles101may have cellular or wireless fidelity (Wi-Fi) connection either through the inbuilt communication equipment or from a UE105associated with the vehicles101. Also, the UEs105may be configured to access the communication network109by way of any known or still developing communication protocols. In one embodiment, the UEs105may include the routing platform107to present to a user in a vehicle101a visual representation of a route for finding a parking space for the vehicle101(i.e., a parking search route).

In one embodiment, the routing platform107performs the process for presenting to a user of a vehicle101an efficient visual representation of a complex route for finding a parking space for the vehicle101as discussed with respect to the various embodiments described herein.

In one embodiment, the routing platform107can be a standalone server or a component of another device with connectivity to the communication network109. For example, the component can be part of an edge computing network where remote computing devices (not shown) are installed along or within proximity of an intended destination (e.g., a city center). In one embodiment, the routing platform107has connectivity over the communication network109to the services platform117(e.g., an OEM platform) that provides one or more services119a-119n(also collectively referred to herein as services119) (e.g., traffic/routing services). By way of example, the services119may also be other third-party services and include mapping services, navigation services, parking services, travel planning services, notification services, social networking services, content (e.g., audio, video, images, etc.) provisioning services, application services, storage services, contextual information determination services, location-based services, information-based services (e.g., weather, news, etc.), etc.

In one embodiment, content providers121a-121n(also collectively referred to herein as content providers121) may provide content or data (e.g., navigation-based content such as destination information, routing instructions, POI data, historical data, etc.) to the vehicles101, the routing platform107, the UEs105, the applications111, the geographic database113, the services platform117, and the services119. The content provided may be any type of content, such as map content, contextual content, audio content, video content, image content, etc. In one embodiment, the content providers121may also store content associated with the vehicles101, the UEs105, the routing platform107, the applications111, the geographic database113, the services platform117, and/or the services119. In another embodiment, the content providers121may manage access to a central repository of data, and offer a consistent, standard interface to data, such as a repository of the geographic database113.

By way of example, as previously stated the vehicle sensors103may be any type of sensor. In certain embodiments, the vehicle sensors103may include, for example, a global positioning system (GPS) sensor for gathering location data, a network detection sensor for detecting wireless signals or receivers for different short-range communications (e.g., Bluetooth, Wi-Fi, light fidelity (Li-Fi), near field communication (NFC) etc.), temporal information sensors, a camera/imaging sensor for gathering image data (e.g., lights or exhaust associated with a vehicle101about to leave a parking spot), velocity sensors, and the like. In another embodiment, the vehicle sensors103may include sensors (e.g., mounted along a perimeter of the vehicle101) to detect the relative distance of the vehicle from lanes or roadways, the presence of other vehicles101, pedestrians, animals, traffic lights, road features (e.g., curves) and any other objects, or a combination thereof. In one scenario, the vehicle sensors103may detect weather data, traffic information, or a combination thereof. In one example embodiment, the vehicles101may include GPS receivers to obtain geographic coordinates from satellites115for determining current or live location and time. Further, the location can be determined by a triangulation system such as A-GPS, Cell of Origin, or other location extrapolation technologies when cellular or network signals are available. In another example embodiment, the services119may provide in-vehicle navigation services.

In one embodiment, the routing platform107may be a platform with multiple interconnected components. By way of example, the routing platform107may include multiple servers, intelligent networking devices, computing devices, components and corresponding software for presenting to a user of a vehicle101an efficient visual representation of a complex route for finding a parking space for the vehicle101. In addition, it is noted that the routing platform107may be a separate entity of the system100, a part of the services platform117, the one or more services119, or the content providers121.

In one embodiment, the geographic database113stores information regarding parking spot availability in a zone around or a threshold from a destination (e.g., available parking location, historic parking probability data, parking restriction data, etc.). In one instance, the geographic database113also stores driving situation data (e.g., historic or current traffic levels) and walking distance (e.g., average walk times). The information may be any of multiple types of information that can provide means for providing navigation-based content (e.g., a parking search route). In another embodiment, the geographic database113may be in a cloud and/or in a vehicle101, a UE105, or a combination thereof.

FIG. 7is a diagram of the geographic database113, according to one embodiment. In one embodiment, parking search route information, parking spot availability data, and/or any other information used or generated by the system100with respect to presenting to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle can be stored, associated with, and/or linked to the geographic database113or data thereof. In one embodiment, the geographic or map database113includes geographic data701used for (or configured to be compiled to be used for) mapping and/or navigation-related services, such as for route information, service information, estimated time of arrival information, location sharing information, speed sharing information, and/or geospatial information sharing, according to exemplary embodiments. For example, the geographic database113includes node data records703, road segment or link data records705, POI data records707, parking availability data709, other data records711, and indexes713, for example. More, fewer or different data records can be provided. In one embodiment, the other data records711include cartographic (“carto”) data records, routing data, and maneuver data. One or more portions, components, areas, layers, features, text, and/or symbols of the POI or event data can be stored in, linked to, and/or associated with one or more of these data records. For example, one or more portions of the POI, event data, or recorded route information can be matched with respective map or geographic records via position or GPS data associations (such as using known or future map matching or geo-coding techniques), for example. In one embodiment, the POI data records707may also include information on locations of traffic controls (e.g., stoplights, stop signs, crossings, etc.), driving restrictions (e.g., speed, direction of travel, etc.), or a combination thereof.

In exemplary embodiments, the road segment data records705are links or segments representing roads, streets, or paths, as can be used in calculating a likelihood of overlap, intersection, or looping between two or more route segments. The node data records703are end points corresponding to the respective links or segments of the road segment data records705. The road link data records705and the node data records703represent a road network, such as used by vehicles, cars, and/or other entities. Alternatively, the geographic database113can contain path segment and node data records or other data that represent pedestrian paths or areas in addition to or instead of the vehicle road record data, for example.

The road link and nodes can be associated with attributes, such as geographic coordinates, street names, address ranges, speed limits, turn restrictions at intersections, and other navigation related attributes, as well as POIs, such as traffic controls (e.g., stoplights, stop signs, crossings, etc.), gas or petrol stations, hotels, restaurants, museums, stadiums, offices, shopping centers or malls, parking lots, automobile dealerships, auto repair shops, buildings, stores, parks, etc. The geographic database113can include data about the POIs and their respective locations in the POI data records707(e.g., proximity of convenient available parking such as an attached parking lot or parking structure). The geographic database113can also include data about places, such as cities, city centers, towns, or other communities, and other geographic features, such as bodies of water, mountain ranges, etc. Such place or feature data can be part of the POI data records707or can be associated with POIs or POI data records707(such as a data point used for displaying or representing a position of a city).

In one embodiment, the parking availability data709can include any data item used to detect or identify parking spaces, available parking spaces, or a combination thereof. In one instance, the parking availability data709can also include any data related to a vehicle in a parking space (e.g., time of parking, time remaining on a meter, etc.). In one embodiment, the parking availability data709in connection with the road segment data records705or separately can include any data item use to detect or identify a probability value to find a parking space on a road or segment (e.g., a historic value, a current value, or a combination thereof).

The geographic database113can be maintained by the content providers121in association with the services platform117(e.g., a map developer). The map developer can collect geographic data to generate and enhance the geographic database113. There can be different ways used by the map developer to collect data. These ways can include obtaining data from other sources, such as municipalities or respective geographic authorities. In addition, the map developer can employ field personnel to travel by vehicle along roads throughout the geographic region to observe features and/or record information about them, for example. Also, remote sensing, such as aerial or satellite photography, can be used.

For example, geographic data or geospatial information is compiled (such as into a platform specification format (PSF) format) to organize and/or configure the data for performing map or navigation-related functions and/or services, such as map annotation, route calculation, route guidance, map display, speed calculation, distance and travel time functions, and other functions, by a navigation device, such as by a UE105, for example. The navigation-related functions can correspond to vehicle navigation, pedestrian navigation, or other types of navigation. The compilation to produce the end user databases can be performed by a party or entity separate from the map developer. For example, a customer of the map developer, such as a navigation device developer or other end user device developer, can perform compilation on a received geographic database in a delivery format to produce one or more compiled navigation databases.

As mentioned above, the geographic database113can be a master geographic database, but in alternate embodiments, the geographic database113can represent a compiled navigation database that can be used in or with end user devices (e.g., a UE105) to provide navigation-related functions. For example, the geographic database113can be used with the end user device to provide an end user with navigation features (e.g., a parking search route). In such a case, the geographic database113can be downloaded or stored on the end user device, such as in an application111, or the end user device can access the geographic database113through a wireless or wired connection (such as via a server and/or the communication network109), for example.

The processes described herein for presenting to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle may be advantageously implemented via software, hardware (e.g., general processor, Digital Signal Processing (DSP) chip, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Arrays (FPGAs), etc.), firmware or a combination thereof. Such exemplary hardware for performing the described functions is detailed below.

A bus810includes one or more parallel conductors of information so that information is transferred quickly among devices coupled to the bus810. One or more processors802for processing information are coupled with the bus810.

Computer system800also includes a memory804coupled to bus810. The memory804, such as a random-access memory (RAM) or other dynamic storage device, stores information including processor instructions for presenting to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle. Dynamic memory allows information stored therein to be changed by the computer system800. RAM allows a unit of information stored at a location called a memory address to be stored and retrieved independently of information at neighboring addresses. The memory804is also used by the processor802to store temporary values during execution of processor instructions. The computer system800also includes a read only memory (ROM)806or other static storage device coupled to the bus810for storing static information, including instructions, that is not changed by the computer system800. Some memory is composed of volatile storage that loses the information stored thereon when power is lost. Also coupled to bus810is a non-volatile (persistent) storage device808, such as a magnetic disk, optical disk or flash card, for storing information, including instructions, that persists even when the computer system800is turned off or otherwise loses power.

Information, including instructions for presenting to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle, is provided to the bus810for use by the processor from an external input device812, such as a keyboard containing alphanumeric keys operated by a human user, or a sensor. A sensor detects conditions in its vicinity and transforms those detections into physical expression compatible with the measurable phenomenon used to represent information in computer system800. Other external devices coupled to bus810, used primarily for interacting with humans, include a display device814, such as a cathode ray tube (CRT) or a liquid crystal display (LCD), or plasma screen or printer for presenting text or images, and a pointing device816, such as a mouse or a trackball or cursor direction keys, or motion sensor, for controlling a position of a small cursor image presented on the display814and issuing commands associated with graphical elements presented on the display814. In some embodiments, for example, in embodiments in which the computer system800performs all functions automatically without human input, one or more of external input device812, display device814and pointing device816is omitted.

In one embodiment, a non-transitory computer-readable storage medium carrying one or more sequences of one or more instructions (e.g., computer code) which, when executed by one or more processors (e.g., a processor as described inFIG. 5), cause an apparatus (e.g., the routing platform107, a vehicle101, a UE105, etc.) to perform any steps of the various embodiments of the methods described herein.

FIG. 9illustrates a chip set900upon which an embodiment of the invention may be implemented. Chip set900is programmed to present to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle as described herein and includes, for instance, the processor and memory components described with respect toFIG. 8incorporated in one or more physical packages (e.g., chips). By way of example, a physical package includes an arrangement of one or more materials, components, and/or wires on a structural assembly (e.g., a baseboard) to provide one or more characteristics such as physical strength, conservation of size, and/or limitation of electrical interaction. It is contemplated that in certain embodiments the chip set can be implemented in a single chip.

The processor903and accompanying components have connectivity to the memory905via the bus901. The memory905includes both dynamic memory (e.g., RAM, magnetic disk, writable optical disk, etc.) and static memory (e.g., ROM, CD-ROM, etc.) for storing executable instructions that when executed perform the inventive steps described herein to present to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle. The memory905also stores the data associated with or generated by the execution of the inventive steps.

FIG. 10is a diagram of exemplary components of a mobile terminal1001(e.g., handset or vehicle or part thereof) capable of operating in the system ofFIG. 1, according to one embodiment. In one embodiment the mobile station can be the vehicle101or a component of the vehicle101configured to perform or more of the embodiments described herein. In another embodiment, the mobile station is an example of the UE and can perform embodiments of the processes associated with functions of the UE. Generally, a radio receiver is often defined in terms of front-end and back-end characteristics. The front-end of the receiver encompasses all of the Radio Frequency (RF) circuitry whereas the back-end encompasses all of the base-band processing circuitry. Pertinent internal components of the telephone include a Main Control Unit (MCU)1003, a Digital Signal Processor (DSP)1005, and a receiver/transmitter unit including a microphone gain control unit and a speaker gain control unit. A main display unit1007provides a display to the user in support of various applications and mobile station functions that offer automatic contact matching. An audio function circuitry1009includes a microphone1011and microphone amplifier that amplifies the speech signal output from the microphone1011. The amplified speech signal output from the microphone1011is fed to a coder/decoder (CODEC)1013.

A radio section1015amplifies power and converts frequency in order to communicate with a base station, which is included in a mobile communication system, via antenna1017. The power amplifier (PA)1019and the transmitter/modulation circuitry are operationally responsive to the MCU1003, with an output from the PA1019coupled to the duplexer1021or circulator or antenna switch, as known in the art. The PA1019also couples to a battery interface and power control unit1020.

The encoded signals are then routed to an equalizer1025for compensation of any frequency-dependent impairments that occur during transmission though the air such as phase and amplitude distortion. After equalizing the bit stream, the modulator1027combines the signal with a RF signal generated in the RF interface1029. The modulator1027generates a sine wave by way of frequency or phase modulation. In order to prepare the signal for transmission, an up-converter1031combines the sine wave output from the modulator1027with another sine wave generated by a synthesizer1033to achieve the desired frequency of transmission. The signal is then sent through a PA1019to increase the signal to an appropriate power level. In practical systems, the PA1019acts as a variable gain amplifier whose gain is controlled by the DSP1005from information received from a network base station. The signal is then filtered within the duplexer1021and optionally sent to an antenna coupler1035to match impedances to provide maximum power transfer. Finally, the signal is transmitted via antenna1017to a local base station. An automatic gain control (AGC) can be supplied to control the gain of the final stages of the receiver. The signals may be forwarded from there to a remote telephone which may be another cellular telephone, other mobile phone or a land-line connected to a Public Switched Telephone Network (PSTN), or other telephony networks.

Voice signals transmitted to the mobile station1001are received via antenna1017and immediately amplified by a low noise amplifier (LNA)1037. A down-converter1039lowers the carrier frequency while the demodulator1041strips away the RF leaving only a digital bit stream. The signal then goes through the equalizer1025and is processed by the DSP1005. A Digital to Analog Converter (DAC)1043converts the signal and the resulting output is transmitted to the user through the speaker1045, all under control of a Main Control Unit (MCU)1003—which can be implemented as a Central Processing Unit (CPU) (not shown).

The MCU1003receives various signals including input signals from the keyboard1047. The keyboard1047and/or the MCU1003in combination with other user input components (e.g., the microphone1011) comprise a user interface circuitry for managing user input. The MCU1003runs a user interface software to facilitate user control of at least some functions of the mobile station1001to present to a user of a vehicle an efficient visual representation of a complex route for finding a parking space for the vehicle. The MCU1003also delivers a display command and a switch command to the display1007and to the speech output switching controller, respectively. Further, the MCU1003exchanges information with the DSP1005and can access an optionally incorporated SIM card1049and a memory1051. In addition, the MCU1003executes various control functions required of the station. The DSP1005may, depending upon the implementation, perform any of a variety of conventional digital processing functions on the voice signals. Additionally, DSP1005determines the background noise level of the local environment from the signals detected by microphone1011and sets the gain of microphone1011to a level selected to compensate for the natural tendency of the user of the mobile station1001.

An optionally incorporated SIM card1049carries, for instance, important information, such as the cellular phone number, the carrier supplying service, subscription details, and security information. The SIM card1049serves primarily to identify the mobile station1001on a radio network. The card1049also contains a memory for storing a personal telephone number registry, text messages, and user specific mobile station settings.