Determining the location of a digital vehicle key wallet

Abstract

A system and procedure for estimating a method for determining the location of a digital vehicle key wallet involves a user selecting whether the digital key wallet should be stored in cloud storage or in a secure telematics unit housed within the vehicle. The digital key wallet is used to trigger an event within the vehicle. A back-office server stores data, including a radio information database and a rule-based vehicle pattern matrix. The digital key wallet is switched to an alternative device based on the status of a communication connection with the secure telematics unit, the radio information database and the rule-based vehicle pattern matrix.

Description

introduction

[0001] Vehicles are an integral part of daily life. Specialized microcontrollers, telematic communication systems, laser technologies, and sensors can be used in many different applications within a vehicle. Microcontrollers, telematics, and sensors can be used to enhance automated structures that provide customers with state-of-the-art experiences and services, for example, for tasks such as body inspection, camera vision, information display, security, autonomous control, and more. Accessing a vehicle previously required a physical key that had to be inserted into a door and turned to unlock the vehicle. Access to a vehicle is now also possible via push buttons. Wireless key fobs have also become available, allowing a person with the key fob in their pocket to unlock a vehicle and start the engine simply by touching the door and pressing a button.

[0002] With the advent of digital keys, a smartphone can perform the same functions as a car key. Unlocking, locking, starting the vehicle, and numerous other functions can be accessed via a smartphone using communication protocols such as near-field communication and ultra-wideband. The digital key's information can be securely stored in a security element integrated into the smartphone. While a digital key in a digital key wallet stored in a smartphone offers flexibility and convenience, it also carries some risks. For example, if the phone stops working because it is dropped or the battery is dead, the digital key wallet can no longer be accessed. If the digital key wallet cannot be accessed, access to the vehicle is also blocked.Accordingly, it is desirable to be able to automatically change the storage location of a digital key wallet based on applications and situational awareness. Description

[0003] Described herein is a system and method for determining the location of a digital vehicle key wallet, which may also be referred to as a digital key wallet. As disclosed herein, a method for determining the location of a digital vehicle key wallet may include a user selecting whether to store a digital key wallet in cloud storage or in a secure telematics unit located within a vehicle. The digital key wallet may be used to trigger an event within the vehicle. The method may also include storing a radio information database and a rule-based vehicle pattern matrix in a back-office server.The method may include switching the digital key wallet to a backup device based on a status of a communication link with the secure telematics unit, the radio information database, and the rule-based vehicle pattern matrix.

[0004] Another aspect of the method may be that the cloud storage contains an Internet of Things broker based on a publish-and-subscribe messaging protocol including a message queuing telemetry transport, MQTT.

[0005] Another aspect of the method may include notifying one or more backup devices via an Internet of Things broker.

[0006] Another aspect of the method may be that the backup device is located in a mobile communication device.

[0007] Another aspect of the method may be that the backup device is a fleet management server.

[0008] Another aspect of the method may be that the fallback device is the secure telematics unit located in the vehicle.

[0009] Another aspect of the method may be to determine whether the connectivity of the secure telematics unit is below a predefined threshold.

[0010] A further aspect of the method may be that the radio information database can be used to predict a probability of the status of the communication link at a particular time at a location of the vehicle.

[0011] Another aspect of the method may include switching the digital key wallet to a second fallback device based on the status of the communication link with the secure telematics unit, the radio information database, and the rule-based vehicle pattern matrix.

[0012] Another aspect of the disclosure may include a system for determining the location of a digital key wallet for a vehicle. The system may include cloud storage for storing a digital key wallet associated with a vehicle, wherein the digital key wallet may be used to trigger an event within the vehicle. The system may also include a secure telematics unit within the vehicle for storing the digital key wallet. The system may also include the backup device for storing the digital key wallet and a back-office server that may be used to store a radio information database and a rule-based vehicle pattern matrix.The system may include a user selecting whether to store an initial storage location of the digital key wallet in either cloud storage or the secure telematics unit; and then switching the digital key wallet to the backup device based on a status of a communication link with the secure telematics unit, the radio information database, and the rule-based vehicle pattern matrix.

[0013] Another aspect of the system is that the cloud storage can contain an Internet of Things broker based on a publish-and-subscribe messaging protocol that includes a message queuing telemetry transport, MQTT.

[0014] Another aspect of the system is that the Internet of Things broker can control one or more backup devices.

[0015] Another aspect of the system may be that the backup device is a mobile communications device.

[0016] Another aspect of the system may be that the backup device is a fleet management server.

[0017] Another aspect of the system may be that the fallback device is the secure telematics unit housed in the vehicle.

[0018] Another aspect of the system may be that the status of the communication link includes determining whether the connectivity of the secure telematics unit is below a predefined threshold.

[0019] Another aspect of the system may be that the radio information database is used to predict a probability of the status of the communication link at a particular time at a location of the vehicle.

[0020] Another aspect of the system may be that the rule-based vehicle pattern matrix contains a set of rules for user behavior based on vehicle patterns including a time of day, a route, a trajectory, and one or more stops.

[0021] Another aspect of the system may be that based on the status of the communication link with the secured telematics unit, the radio information database and the rule-based vehicle pattern matrix, the digital key wallet is switched to a second backup device.

[0022] Another aspect of the disclosure may include a method for determining the location of a digital vehicle key wallet, which may include determining a set of rules for user behavior based on a set of vehicle movement patterns of a vehicle in addition to determining whether the vehicle is not located in a first area. The method may proceed to determine whether the vehicle is traveling in a known roaming area, wherein, if the vehicle is traveling in the known roaming area, the method may calculate a set of radio conditions and a map of the roaming area and, based on the calculations, switch a digital key wallet to a next alternate location. If the vehicle is not traveling in the known roaming area, the method may further provide for the digital key wallet to remain at its current location.However, if the method determines that the vehicle is in the first area, then it further comprises locating the digital key wallet at a user-preferred home location, detecting and tracking when the vehicle moves out of the first area, wherein if the vehicle stops in an area of ​​known location, the method may comprise performing a change to a next best location for the digital key wallet, but if the vehicle stops in an area of ​​unknown location, the method may comprise maintaining the digital key wallet at the current location.

[0023] The above features and advantages, as well as other features and associated advantages of this disclosure, will become readily apparent from the following detailed description of illustrative examples and modes for carrying out the present disclosure, when considered in conjunction with the accompanying drawings and the appended claims. Furthermore, this disclosure expressly includes combinations and subcombinations of the elements and features presented above and below. Brief description of the drawings

[0024] The accompanying drawings, which are incorporated in this specification, illustrate embodiments of the disclosure and, together with the description, serve to explain the principles of the disclosure. Fig. 1 is an illustration of an architecture for automatically switching the digital key wallet based on patterns and radio intelligence, in accordance with the disclosure. Fig. 2 is an overview flowchart of changing the digital key wallet according to the disclosure. Fig. Figure 3 is an illustration of an architecture that uses an Internet of Things broker to manage the exchange of a digital key wallet according to the disclosure. Fig. 4 is a detailed flowchart for changing the digital key wallet according to the disclosure. Fig. 5 shows a flowchart of a method for determining the location of a digital key wallet according to the disclosure.

[0025] The accompanying drawings are not necessarily to scale and present a somewhat simplified representation of various preferred features of the present disclosure as disclosed herein, including, for example, specific dimensions, orientations, locations, and shapes. Details associated with such features will be determined in part by the particular intended application and environment of use. Detailed description

[0026] The present disclosure may be embodied in many different forms. Representative examples of the disclosure are illustrated in the drawings and are described in detail herein as non-limiting examples of the disclosed principles. To this end, elements and limitations described in the "Summary," "Introduction," "Summary," and "Detailed Description" sections, but not expressly set forth in the claims, should not be incorporated into the claims, individually or collectively, by implication, inference, or otherwise.

[0027] For the purposes of this description, the use of the singular includes the plural and vice versa, unless expressly excluded; the terms "and" and "or" apply both subjunctive and disjunctive; and the words "including," "containing," "comprising," "with," and the like mean "including without limitation." Furthermore, words of approximation such as "about," "almost," "substantially," "generally," "approximately," etc., may be used herein to mean "at, near, or almost at," or "within 0-5% of," or "within acceptable manufacturing tolerances," or logical combinations thereof. A component "configured" to perform a particular function is capable of performing the particular function without modification, rather than merely having the potential to perform the particular function after further modifications.In other words, if the hardware described is expressly configured to perform the specified function, it is specifically selected, created, implemented, used, programmed, and / or designed to perform the specified function.

[0028] In the drawings, the leftmost digit of a reference number indicates the drawing in which the reference number first appears (for example, a reference number “310” indicates that the item so numbered is first labelled or first used in Fig. 3 appears). In addition, elements with the same reference number followed by a different letter of the alphabet or another distinguishing mark (for example, an apostrophe) indicate elements that may be similar in structure, function, or form, but are located at different locations in space or recur at different times (for example, reference numbers '110a' and '110b' may indicate two different input devices that may be functionally similar but are located at different points in a simulation arena).

[0029] Vehicles are now computationally sophisticated and equipped with a multitude of microcontrollers, sensors, processors, and control systems. These include autonomous vehicles and advanced driver assistance systems (AV / ADAS) such as adaptive cruise control, automatic parking, automatic brake hold, automatic braking, evasive steering assist, lane departure warning, adaptive headlights, rear cross-traffic alert, blind spot detection, local hazard warning, and automatic rear braking, which rely on information from cameras and sensors in the vehicle. Access to these vehicles has also evolved, from using a physical key to buttons for entering a code to wireless key fobs and smartphone access via a digital key.

[0030] Digital keys stored in a digital wallet may be stored in an electronic device. This electronic device may be a mobile communications device or some type of vehicle system, for example, an electronic control unit such as a telematics system, an infotainment system, or similar, which may contain a digital key wallet and is connected to the vehicle's processor or server. A mobile communications device may be any wearable and / or electronic device, including devices such as a smartphone, a watch, glasses, a tablet, a mixed-reality headset, or similar.

[0031] While a mobile communication device can contain a digital key wallet, its capacity may also be limited. For example, a smartphone can typically only store fewer than ten different digital keys. A fleet manager who needs to store large quantities of digital keys may therefore choose to store the digital keys in a digital key wallet tied to a server or an Internet of Things (IoT) broker.

[0032] An IoT broker may be responsible for receiving messages from publisher clients, such as a mobile communications device or a vehicle telematics unit, and then filtering these messages to determine which subscriber is interested in a message. The IoT broker may use a standard protocol for message delivery, such as Message Queuing Telemetry Transport ("MQTT"). Thus, an IoT broker can route the transfer of a digital key wallet from one location to another, for example, from a mobile communications device to the IoT broker, from the IoT broker to a mobile communications device, from a vehicle telematics system to the IoT broker, and then to a fleet management server.

[0033] In certain cases, a digital key wallet can be moved from one location to another. For example, a digital key wallet may be located in a vehicle's secure telematics unit, but the vehicle is about to lose its cellular connectivity. Before connectivity is interrupted, a software algorithm can detect that connectivity falls below a predefined threshold and trigger a transfer of the digital key wallet from the vehicle's telematics unit to the cloud, for example, to the IoT broker. The IoT broker can then determine that the digital key wallet be transferred to a backup device, such as a mobile communications device.

[0034] In another embodiment, a digital key wallet can be moved from one location to another based on historical data. For example, a user traveling in a vehicle drives from a home location to a nearby coffee shop and then on to an office location. Each time the vehicle approaches the coffee shop within 500 feet, the cellular signal suddenly drops. In such a scenario, a rule-based matrix of vehicle patterns, also known as a rule-based matrix of vehicle patterns for user behavior, may have evolved over time, with the weekday commute pattern identified. Furthermore, a radio information database may record areas of connectivity drops.Therefore, a software algorithm in the IoT broker, based on the rule-based vehicle pattern matrix (e.g., the trip to the coffee shop) and the radio information database (e.g., areas with poor cellular signal), can trigger a transfer of the digital key wallet from the vehicle's secure telematics unit to a backup device shortly before entering the signal outage area. The backup device can be a server, the IoT broker, a mobile communications device, or another electronic device.

[0035] Accordingly, this disclosure is directed to the use of an IoT broker, one or more servers, and one or more backup devices that, in conjunction with a radio information database and a rule-based vehicle pattern matrix, can trigger a switch or transfer of a digital key wallet from one location to another. Such transfers can be initiated by client-server software algorithms monitoring a vehicle's telematics unit to determine whether a transfer should be initiated, or by a back-office server that can trigger the transfer based on radio data and a rule-based vehicle pattern matrix.

[0036] Fig. For example, Figure 1 is an illustration of an architecture 100 for automatic digital key wallet switching based on patterns and radio intelligence, according to one embodiment of the present disclosure. The architecture 100 may include an IoT broker 110, a database server 115, a vehicle 120 with a mobile digital key wallet 125, a home location 130 with a digital key wallet 135, an intermediary station 140, and a backup server 145.

[0037] Humans can be creatures of habit. We may visit the same shops, the same restaurants, the same entertainment venues. Furthermore, there may also be patterns; for example, one may stop at one's favorite cafe every weekday on the way to work. These actions may represent a travel pattern or a series of travel patterns. Such travel patterns may be collected in a rule-based vehicle pattern matrix database, for example, in database server 115. Similarly, the connectivity of a vehicle may also be recorded while driving. Consequently, a radio information database may be created containing information about connectivity, for example, the strength of cellular signals, the presence of wireless networks, and other forms of short-range communication links.

[0038] Architecture 100 illustrates that vehicle 120 may start the day at home location 130. Home location 130 may also include its own cloud storage, which may contain a smart home digital key wallet. Thus, when vehicle 120 is at home at location 130, the user may choose to store the vehicle's digital key in smart home digital key wallet 135 for additional security. Or, the user may choose to store mobile digital key wallet 125 in the secure telematics unit within the vehicle.

[0039] From the home location 130, the vehicle 120 can make a routine trip to the preferred waypoint 140, which the user ordinarily visits every weekday morning. Since the database server 115 can contain a radio information database and a rule-based vehicle pattern matrix database, this information can enable a prediction of a potential connectivity problem. For example, the rule-based vehicle pattern matrix can predict that the vehicle 120 is en route to the waypoint 140 and that there has been a cellular outage just outside the waypoint 140 every Wednesday for the past few months. Therefore, if it is a Wednesday and the vehicle 120 appears to be en route to the waypoint 140 again, the system can automatically transfer the mobile digital key wallet 125 from its current location to the backup server 145, ahead of the expected cellular outage area.Such a transfer can be controlled by the IOT broker 110 since it has access to the database server 115 as well as to the mobile digital key wallet 125 and the backup server 145.

[0040] Fig. 2 is an overview flowchart 200 for automatically changing the location of the digital key wallet according to one embodiment of the present disclosure. The flowchart 200 begins at step 210 and proceeds to step 220, where the user or customer can set a location preference for a digital key wallet. The location may be a cloud location. The cloud may be an IoT broker, such as IoT broker 110, or a home location cloud, such as the smart home digital key wallet 135. The preference may also include a vehicle's secure telematics, which may include the mobile digital key wallet 125. In one embodiment, the user may set the preference for the initial location.For example, the user may be an individual who selects a home location 130, or the user may be a fleet manager who selects a fleet management server as the preferred home location.

[0041] In step 230, a back-office server, for example, database server 115, dynamically monitors a radio information database and a rule-based vehicle pattern matrix. A radio information database can predict the probability of a signal at a particular time at the location of the vehicle in question. A radio detection algorithm tracks possible communication connections with a vehicle telematics unit and can output a probability of a connection. Furthermore, the prediction can also be based on one or more categories of radio connectivity. For example, a home range can be defined as a particular distance around a vehicle's home location. The home range is likely well-defined in terms of communication connectivity, for example, the signal strength of a cellular connection or the presence of a home cloud or other wireless network access.A second category may include a smart roaming area. A smart roaming area may include areas that are occasionally traveled and where, therefore, a certain level of connectivity may be known. A third category may include a roaming area where such roaming takes place in unfamiliar territory and, therefore, connectivity may be unknown.

[0042] In addition to the databases monitored by the back-office server, in one embodiment, a vehicle telematics system may also dynamically monitor the status and signal levels in the vehicle. For example, the vehicle telematics system or other electronic control unit may monitor the communication performance level and alert the IoT broker of a performance level or connection access failure and publish this information. Such an alert may occur when the performance level drops below a predefined threshold or when the connection to the client or IoT is interrupted. The back-office server may subscribe to the topic, which may have some degree of control over the vehicle in question.

[0043] In step 240, a comparison is made as to whether the radio information database or the rule-based vehicle pattern matrix predicts that a communication signal will fall below a predefined threshold, such that connectivity could be lost. If the predefined threshold is exceeded, a command may be triggered in step 250 to change or transfer the location of the digital key wallet to an assigned fallback mechanism and location. As described in Fig. 1, for example, the backup server 145 or even the IoT broker 110 can be used as the backup location for the digital key wallet. Flowchart 200 can then end at step 260.

[0044] Fig. Figure 3 is an illustration of the architecture 300 based on an IoT broker, according to one embodiment of the present disclosure. The architecture 300 may include the IoT broker 310, a vehicle 320, a mobile communication device 330, a fallback server 340, a friend server 350, a fleet server 360, and a back-office server 370. Furthermore, the back-office server 370 may include a rule-based vehicle pattern matrix 373 and a radio information database 375.

[0045] The IoT broker 310 can be considered the controlling element in the architecture 300. The IoT broker 310 can act as an intermediary entity that enables communication between MQTT clients. The IoT broker 310 can receive messages published by clients, for example, a vehicle's secure telematics unit, a mobile communication device, or even a server. The IoT broker 310 can then filter the messages by topic and then distribute the filtered messages to the participants. In this way, the IoT broker 310 can control the location of a digital key wallet.

[0046] The IOT broker 310 can be considered the primary location for a digital key wallet because it is a central device with access to servers, for example, fleet server 360, backup server 340, and friendship server 350. Furthermore, the vehicle 320 with its secure telematics unit can also be treated as the primary location for the digital key wallet because it is the vehicle connected to and controlled by the digital key wallet. As in Fig. 2, a user can decide whether the digital key wallet is initially located in the IOT broker 310 or in the vehicle 320.

[0047] The mobile communication device 330 can be treated as a fallback option. For example, if the vehicle 320 has detected that its cellular signal is weakening, e.g., the cellular signal strength falls below a predetermined threshold, the vehicle's telematics unit can inform the IoT broker 310 of the deteriorating communication links, whereupon the IoT broker 310 can transfer the digital key wallet from the vehicle's telematics unit 320 to the mobile communication device 330. Such a transfer can be referred to as a conditional fallback.

[0048] Similarly, instead of being transmitted to the mobile communication device 330, the digital key wallet may be transferred to the backup server 340, which may be under the control of the vehicle manufacturer or dealer. Another example: If the vehicle 320 is part of a fleet, a fleet server 360 may be the most suitable location to store the digital key wallet. Another example: If the vehicle 320 is to be shared with friends or family members, the digital key wallet may be located on a friendship server 350 to which the friends and family members have access.

[0049] While the IOT broker 310 may have access to the back office server 370 and its radio information database 375 and the rule-based vehicle pattern matrix 373, the fleet server 360 may also have access to these databases relating to its fleet vehicles. Thus, the fleet server 360, as shown in Fig. 1, access radio intelligence data to predict the likelihood of a signal at a given time at the location of one of its fleet vehicles. Fleet server 360 can also access the rule-based vehicle pattern matrix to predict routes and destinations, as well as the need to transmit the digital key wallet, if desired.

[0050] Fig. 4 is a detailed flowchart 400 of the digital key wallet switching according to an embodiment of the present disclosure. Flowchart 400 begins at step 410 and proceeds to step 415, where it may be determined which rule-based vehicle pattern matrix is ​​applicable, which may be based on the time of day, the location of the vehicle, the route traveled, the vehicle's trajectory, the number of stops made, and other possible attributes. In step 420, based on the determination in step 415, it may be determined whether the vehicle is currently in its home territory. A home territory may be defined as a known area in the vicinity of the vehicle's typical residence, for example, at home location 130.

[0051] If the vehicle is not in the home area, it may be determined in step 425 whether the vehicle is in a known roaming area, which may also be referred to as a smart roaming area. A known or smart roaming area is located outside the home area but may be occasionally traveled through, so its communication connectivity patterns, while reasonably accurate, may not be completely known. For example, the Fig. 1 may represent a smart roaming area. If the vehicle is in a known or smart roaming area, a dynamic calculation of the current radio conditions may be performed in step 430 to update a map of the known roaming area. Since the connection pattern is sufficiently known, the digital key wallet may be switched to the next alternate location, for example, when the vehicle approaches a work location where it might be appropriate to switch to an alternate device, such as the alternate server 145. In this scenario, the flowchart would then end at step 470.

[0052] However, if the vehicle is not in a known or smart roaming area at step 425, then by default it is in a roaming area where connectivity patterns may be unknown. Because connectivity patterns are unknown, there is a possibility of lost connectivity, and therefore the digital key wallet must be located on a mobile communication device connected to the vehicle. Therefore, at step 435, the location of the digital key wallet must be verified. If the digital key wallet is not located on the mobile communication device, it must be transferred to the mobile communication device's applet. If the digital key wallet is already located on the mobile communication device, no further action may be required. In this case, the flowchart may end at step 470.

[0053] If it is determined in step 420 that the vehicle is in the living area, in step 440 the digital key wallet can be switched to the user's preferred living area, for example to the digital key wallet 135 in the smart home in a smart home cloud, as in Fig. 1. Or, the user may prefer to switch the digital key wallet in the cloud in the IOT broker 110 or IOT broker 310. Or, the user may prefer that the digital key wallet be located in a backup device such as the mobile communication device 330.

[0054] In step 445, tracking of the vehicle continues. For example, if the vehicle remains at the home address, the vehicle may continue to be tracked in step 450 to determine when it leaves the home location, for example, if the vehicle is more than a quarter mile from the home location. The vehicle's route may continue to be tracked to determine if it matches a known driving pattern, for example, the rule-based vehicle pattern matrix 373.

[0055] In step 455, it may be determined whether the route actually matches a known driving pattern in the rule-based vehicle pattern matrix. If so, in step 460, the digital key wallet may be switched to a next-best digital key wallet location. For example, if the vehicle is a fleet vehicle, the next-best location for the digital key wallet may be the fleet server 360. However, if there is no match in step 455, the vehicle may be traveling in an unknown roaming area and the connectivity patterns may be unknown, so there is a possibility of lost connectivity. Accordingly, the digital key wallet must be located in a mobile communication device connected to the vehicle. Therefore, in step 435, the digital key wallet location must be verified.If the digital key wallet is not located in the mobile communication device, it must be transferred to the mobile communication device's applet. If the digital key wallet containing the digital key is already located in the mobile communication device, no further action may be required. In this case, the flowchart may end at step 470.

[0056] Fig. Figure 5 shows a detailed flowchart of a method 500 for determining the location of a digital vehicle key wallet according to an embodiment of the present disclosure. In step 505, the method may include a user selecting whether to store a digital key wallet in cloud storage or in a secure telematics unit located within a vehicle, wherein the digital key wallet is configured to trigger an event within the vehicle. As shown in Fig. 2, the user or customer can specify where the digital key wallet should be located. For example, the digital key wallet can be located in a cloud storage at home. In this way, household members can be granted permission to access the digital key wallet. Once accessed, the digital key wallet can be used to lock and unlock the vehicle, start the vehicle, and access vehicle functions, such as an infotainment system or other functions. As described in step 440 in Fig. 4, the digital key wallet can also be switched to the user's preferred storage location at home, for example, to the digital key wallet 135 in a smart home cloud, as in Fig. 1. Or, the user may prefer to switch the digital key wallet in the cloud in the IOT broker 110 or IOT broker 310. Or, the user may prefer that the digital key wallet be located in a backup device such as the mobile communication device 330.

[0057] In step 510, the method may include storing a radio information database and a rule-based vehicle pattern matrix in a back-office server. As in Fig. 1, the database server 115 may include a rule-based vehicle pattern matrix that may be built over time and may identify various routes and stops of a user. Such rule sets for user behavior may be based on vehicle patterns, including time of day, route, trajectory, stops, and the like. Furthermore, the database server may also include a radio information database that may store data related to cellular, wireless networks, and other short- and long-range communication links that may be used to predict the likelihood of a signal at a particular time at the location of the vehicle in question.

[0058] As in Fig. As explained in Figure 3, the back office server 370 may also include a rule-based vehicle pattern matrix 373 and a radio information database 375. Furthermore, the fleet server 360 may also have access to the back office server 370 and its databases.

[0059] In step 515, the method may include switching the digital key wallet to a backup device based on a status of a communication link with the secure telematics unit, the radio information database, and the rule-based vehicle pattern matrix. As in Fig. 4, the digital key wallet can be relocated to a backup device under certain conditions. In steps 240 and 250 of Fig. 2, for example, compares whether the radio information database or the rule-based vehicle pattern matrix predicts that a communication signal will fall below a predefined threshold such that connectivity may be lost, and that if the predefined threshold is exceeded, a command may be triggered to change or transfer the location of the digital key wallet to an assigned fallback mechanism and location.

[0060] In step 520, the method may include notifying one or more backup devices using an Internet of Things broker. As in Fig. 1 and Fig. As shown in Figure 3, an IoT broker may be responsible for receiving messages from publisher clients, for example, a mobile communications device or a vehicle telematics unit, and then filtering these messages to determine which subscriber is interested in a message and then sending the messages to the subscribed clients, for example, a fleet management server. The IoT broker may use a standard protocol for message delivery, for example, Message Queuing Telemetry Transport ("MQTT"). Thus, an IoT broker may route the transfer of a digital key wallet from one location to another, for example, from a mobile communications device to the IoT broker, from the IoT broker to a mobile communications device, from a vehicle telematics system to the IoT broker, and then to a fleet management server.

[0061] Step 525 of the method may include determining whether the connectivity of the secure telematics unit is below a predefined threshold. As in steps 240 and 250 of Fig. 2, a comparison is performed to determine whether the radio information database or the rule-based vehicle pattern matrix predicts that a communication signal will fall below a predefined threshold such that connectivity may be lost, wherein in step 250, if the predefined threshold is exceeded, a command may be triggered to change or transfer the location of the digital key wallet to an assigned fallback mechanism and location.

[0062] Step 530 of the method may include switching the digital key wallet to a second backup device based on the status of the communication link with the secure telematics unit, the radio information database, and the rule-based vehicle pattern matrix. As in Fig.4, in steps 430 and 460, a next best location for a digital key wallet may be used to relocate a digital key wallet in certain situations. For example, the IOT broker 310 may receive multiple messages from the in-vehicle telematics unit 320 about changing connectivity issues or from the back-office server 370 about changes in the rule-based vehicle pattern matrix or the radio information database 375 that require multiple relocations of a digital key wallet.For example, the fleet server 360 may notify the IOT broker 310 that it wishes to retrieve a particular digital key wallet from the vehicle 320, where the vehicle 320 may have stored the digital key wallet in a key wallet 135, such that the digital wallet is transferred from the key wallet 135 to the telematics unit of the vehicle 320, to the IOT broker 310, and finally to the fleet server 360. There is no provision for where or how often a digital key wallet may be exchanged or relocated.

[0063] The method 500 can then be terminated.

[0064] The description and abstract paragraphs may represent one or more embodiments of the present disclosure as conceived by the inventor(s) and are therefore not intended to limit the present disclosure and the appended claims.

[0065] Embodiments of the present disclosure have been described above using functional building blocks that illustrate the implementation of certain functions and their relationships. The boundaries of these functional building blocks have been arbitrarily defined here for ease of description. Other boundaries may also be defined as long as the specified functions and relationships can be reasonably implemented.

[0066] The foregoing description of the specific embodiments will so fully disclose the general nature of the disclosure that others, by applying knowledge corresponding to the prior art, can readily modify and / or adapt such specific embodiments for various applications without undue experimentation and without departing from the general concept of the present disclosure. Therefore, such adaptations and modifications are intended to be within the meaning and range of equivalents of the disclosed embodiments based on the teachings and guidance presented herein. It is to be understood that the phraseology or terminology used herein is for the purpose of description and not of limitation, so that the terminology or phraseology of the present specification is to be interpreted by those skilled in the art in light of the teachings and guidance.

[0067] The breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.

[0068] Exemplary embodiments of the present disclosure have been presented. The disclosure is not limited to these examples. These examples are for illustrative purposes and not limiting. Alternatives (including equivalents, extensions, variations, deviations, etc., from those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings incorporated herein. Such alternatives are within the scope and spirit of the disclosure.

Claims

[1] A method for determining a location of a digital key wallet, comprising: Selecting, by a user, whether the digital key wallet is to be stored in cloud storage or in a secure telematics unit housed within a vehicle, wherein the digital key wallet is configured to trigger an event within the vehicle; Storing, in a back office server, a radio information database and a rule-based vehicle pattern matrix; and Switching the digital key wallet to a backup device based on a status of a communication link with the secure telematics unit, the radio information database, and the rule-based vehicle pattern matrix. [2] The method of claim 1, wherein the cloud storage comprises an Internet of Things broker based on a publish-and-subscribe messaging protocol including a message queuing telemetry transport, MQTT. [3] The method of claim 2, further comprising notifying one or more backup devices using the Internet of Things broker. [4] The method of claim 1, wherein the backup device is located in a mobile communication device. [5] The method of claim 1, wherein the backup device is a fleet management server. [6] The method of claim 1, wherein the fallback device is the secure telematics unit housed in the vehicle. [7] The method of claim 1, further comprising determining whether the connectivity of the secure telematics unit is below a predefined threshold. [8] The method of claim 1, wherein the radio information database is configured to predict a probability of the status of the communication link at a given time at a location of the vehicle. [9] The method of claim 1, further comprising switching the digital key wallet to a second backup device based on the status of the communication link with the secure telematics unit, the radio information database, and the rule-based vehicle pattern matrix.

Images