Vehicle location planning using a UWB system

Abstract

Title: Vehicle UWB Location Planning A planning method implemented by a vehicle UWB system (hereafter referred to as the planning method) is proposed. The UWB system includes one or more UWB sensors. The UWB system has stored a plurality of wearable identifiers. The plurality of wearable identifiers includes a remote key fob (100). The method includes a reception S10, for each wearable identifier, of a respective programming of UWB locations with the vehicle UWB system. The method includes a detection S20 of an overlap between at least two programmed UWB locations. The at least two overlapping UWB locations include a UWB location with the key fob. The method includes an offset S30, in the respective programming of the key fob, of the overlapping UWB location. The method offers improved use of the vehicle UWB system [Fig. 2]

Description

Title of the invention: Vehicle location planning system using UWB (Ultra Wide Body Wheel) Technical field

[0001] This disclosure relates to a planning method implemented by a UWB (Ultra Wide Band) system, a method of using a UWB system, a UWB system configured to perform or be used according to such methods, a UWB sensor for such a UWB system, and a computer program for performing such methods. Technical background

[0002] Vehicles equipped with a UWB system now exist, comprising one or more UWB sensors installed in the vehicle. Such a UWB system generally records a set of portable identifiers (such as key fobs or third-party devices like mobile phones or smartwatches) and is then able to determine the position of each of these portable identifiers based on UWB location data between each of the portable identifiers and the system's UWB sensors. Such UWB systems are thus capable of simultaneously locating the driver's key fob and a passenger's mobile phone, and of executing various vehicle functions based on the location of the identifiers (such as unlocking the doors and / or starting the vehicle when a user approaches the vehicle).

[0003] To perform these location tracking operations, each wearable device can be configured to send its respective programming to the UWB system, for example, when the latter enters a certain perimeter around the vehicle. The UWB system and the wearable device can then be configured to perform UWB location tracking according to the respective programming established. The programming includes the timing information of location frames as well as the type of device (key fob or smartphone) involved in the location tracking, based on the specification of the IEEE 802.15.4z standard, "IEEE Standard for Low Rate Wireless Networks - Amendment 1: Enhanced Ultra Wideband (UWB) Physical Layers (PHYs) and Associated Ranging Techniques." Figure 1 shows an example of such programming received for a set of three wearable devices registered by a UWB system: a key fob 100 and two mobile phones 200 and 300.The programming received from each portable identifier includes, over a predetermined period divided into periods (111, 112, 113 and 114 for the key case 100), a UWB location for each of the periods of the predetermined period (location 131 for block 111, 132 for the . 112, etc). Each period is divided into a predetermined number of slots 122 (8 slots per period in this example), and the programming includes, for each location, the slot of the period on which the location is planned.

[0004] When two locations are programmed simultaneously (i.e., in such a way that they would overlap if executed, the slots on which they are programmed having a non-zero intersection), existing scheduling methods generally include canceling the programming of one of the two overlapping UWB locations. This reduces the risk of interference between the UWB exchanges of the two UWB locations. For example, in [Fig. 1], UWB location 132 of the first portable identifier 100 and UWB location 332 of the third portable identifier 300 are programmed simultaneously, and the existing method therefore cancels UWB location 332, so that, in the final system programming 400, only UWB location 132 remains programmed.Similarly, when three UWB locations overlap (such as locations 134, 234 and 335 or locations 135, 235 and 336), two of the locations can be deprogrammed to reduce the risk of interference between UWB exchanges with the different identifiers.

[0005] One limitation is that these UWB localization cancellations reduce the number of localizations ultimately performed for each handheld device when one of the localizations has been cancelled. For device 300, for example, the time interval between two localizations becomes greater than 2 periods after localization 333, for example. This results in a reduction in the accuracy and sensitivity of localization for these handheld devices.

[0006] Therefore, there is a need for an improved vehicle UWB system. Summary

[0007] A planning method implemented by a vehicle UWB system (hereafter referred to as the "planning method" or "method") is proposed. The UWB system comprises one or more UWB sensors. The UWB system has stored a plurality of wearable identifiers. The plurality of wearable identifiers includes a remote key fob. The method includes receiving, for each wearable identifier, a respective programming of UWB locations from the vehicle's UWB system. The method includes detecting an overlap between at least two programmed UWB locations. The at least two overlapping UWB locations include a UWB location with the key fob. The method includes shifting the overlapping UWB location in the respective programming of the key fob.

[0008] The superimposed UWB location can be programmed within a first slot of a respective period comprising several slots. The UWB location can be shifted to a second slot of the respective period.

[0009] The offset of the superimposed UWB location may include a projection, onto the respective programming of the key case, of the UWB locations of each other portable device, a determination of at least one free slot of the respective period by excluding each slot on which at least one projected UWB location overlaps, and a reprogramming of the superimposed UWB location on the at least one determined free slot.

[0010] The detection of the overlap may include a projection of the UWB locations of each of the handheld devices onto a common time axis, and a determination of an overlap between the projections of the at least two superimposed UWB locations.

[0011] The offset of the superimposed UWB location may include sending, by the UWB system to the key box, an order to execute the respective programming with the offset UWB location.

[0012] The plurality of wearable identifiers may include at least two third-party devices. The at least two overlapping UWB locations may include at least one UWB location with each of the at least two third-party devices. The method may further include determining a priority device among the at least two third-party devices, and deprogramming, for each third-party device other than the priority device, the UWB location included in the at least two overlapping UWB locations.

[0013] The detection and offset steps can be repeated each time a new respective programming is received for a new portable identifier.

[0014] A method for using a vehicle UWB system (hereafter referred to as the "use method") is also proposed. The UWB system comprises one or more UWB sensors. The UWB system has stored a plurality of portable identifiers. The plurality of portable identifiers includes the key fob. The use method comprises executing the planned UWB locations according to the planning method.

[0015] A vehicle UWB system comprising one or more UWB sensors is also proposed. The UWB system is configured to execute the planning process and / or to be used according to the operating process.

[0016] A UWB sensor for a vehicle UWB system is also proposed. The UWB sensor is configured for execution by the planning process system and / or for use by the system according to the operating process.

[0017] A first computer program for a vehicle UWB system is also proposed. The second computer program includes instructions which, when the program is executed by a processor of the vehicle UWB system, cause the latter to execute the planning process and / or to be used according to the operating process.

[0018] A second computer program for a vehicle UWB system UWB sensor is also proposed. The second computer program includes instructions which, when executed by a UWB sensor processor, lead to the system executing the planning process and / or to the system operating according to the operating process.

[0019] A third computer program is also proposed, comprising the first computer program and the second computer program.

[0020] A computer-readable storage medium is also proposed on which one or more of said computer programs are recorded. Brief description of the figures

[0021] Non-limiting examples will be described with reference to the following figures:

[0022] [Fig.1] illustrates an example of an existing UWB location planning solution with handheld devices.

[0023] Figure [Fig. 2] illustrates an example of a flowchart of the planning process.

[0024] Figure 3 illustrates examples of offsetting superimposed UWB locations according to the planning process.

[0025] Figure 4 illustrates examples of determining free slots.

[0026] Fig. 5 illustrates an example of a vehicle UWB system. Detailed description

[0027] With reference to the flowchart in [Fig. 2], a planning method implemented by a vehicle UWB system (hereafter referred to as the planning method) is proposed. The UWB system comprises one or more UWB sensors. The UWB system has stored a plurality of wearable identifiers. The plurality of wearable identifiers includes a remote key fob. The method includes a reception S10, for each wearable identifier, of a respective programming of UWB locations with the vehicle UWB system. The method includes a detection S20 of an overlap between at least two programmed UWB locations. The at least two overlapping UWB locations include a UWB location with the key fob. The method includes an offset S30, in the respective programming of the key fob, of the overlapping UWB location.

[0028] The method offers improved use of the vehicle's UWB system.

[0029] Indeed, the offset of the overlapping UWB location avoids the risk of interference between the UWB exchanges of the at least two UWB locations that were initially programmed to run simultaneously. The scheduling method thus reduces the risk of reliability loss caused by interference between the UWB exchanges of different UWB locations.

[0030] Furthermore, the verification avoids the direct but suboptimal solution of systematically canceling the programming of overlapping UWB locations. Indeed, the method preserves the programming of the initially overlapped UWB location. In particular, canceling a UWB location reduces the number of locations programmed for the portable identifier involved in the canceled location, which consequently reduces the accuracy and sensitivity of the location. By preserving the programming of UWB locations, the method therefore increases the accuracy and sensitivity of portable identifier localization.

[0031] A method for using a vehicle UWB system is also proposed, comprising executing the planned UWB locations according to the planning method. In particular, the method of use may include executing the UWB locations of the key fob according to the new programming defined (i.e., in which the initially superimposed location is offset). The execution of each location may include performing the UWB exchanges between the portable identifier and the vehicle that the location encompasses.

[0032] After or during the execution of the localization operations, the method of use may include determining the position of each of the wearable identifiers from the localization operations that have been performed. For example, for each wearable identifier, the execution of a localization operation involving the wearable identifier may include providing a relative position of the wearable identifier with respect to the UWB system. For example, the localization may include, for each UWB sensor (or anchor), a respective distance measurement between the wearable identifier and the UWB sensor, and a determination of the relative position of the wearable identifier with respect to the UWB system from the respective distance measurements between the wearable identifier and each of the UWB sensors. The determined position may vary over time.For example, each location can provide the position of a wearable identifier relative to the UWB system at a given time, and the set of locations involving this wearable identifier that are executed can provide an evolution of the position of this wearable identifier over time. The usage process can thus determine an evolution of the position of all wearable identifiers.

[0033] After the location operations, the usage method may include one or more uses of the relative positions of the determined portable identifiers. By For example, the usage process may include activating one or more vehicle features based on the relative positions of the wearable tags. For instance, the feature may include locking the vehicle when it is determined that the wearable tags are outside the vehicle, such as after a predetermined time has elapsed between the time it is determined that each wearable tag is outside. In other examples, the feature may include selectively unlocking one or more vehicle openings (for example, a driver's door, a passenger's door, or a trunk) based on the determined relative positions of the wearable tags.For example, the functionality might include unlocking the driver's door and the vehicle's trunk when one of the wearable devices approaches the driver's door (e.g., the key fob) and another wearable device (e.g., a third-party device) approaches the trunk (i.e., when two users carrying these devices approach these openings, for example, simultaneously or sequentially). In other examples, the functionality might include unlocking the driver's door and / or passenger doors (e.g., when one or more users approach these openings), and implementing one or more settings for each user (e.g., adjusting the headrest height or seat position) based on a user's access zone (e.g., based on which opening the user approached).In other examples, the functionality may include activating one or more vehicle functions, such as turning on the music or adjusting the mirrors to suit the person wearing the portable identifier positioned in the driver's seat. The method of use may include any combination of these functionality examples.

[0034] The planning process is now discussed. The steps of the planning process can be executed by the vehicle's UWB system. Each step of this process is now discussed in more detail.

[0035] The UWB system has registered a plurality of wearable identifiers (or wearable devices). The term "wearable identifier" refers to a mobile object identifiable by the vehicle, and whose location may or may not authorize one or more (specific) actions of the vehicle. For example, the identifier may be used to unlock the vehicle and / or start the vehicle's engine. For example, the process may include unlocking the vehicle when the identifier is located near the vehicle, or starting the engine when the identifier is inside the vehicle. The wearable identifiers registered by the system include at least one remote key fob for the vehicle. The wearable identifiers registered by the system may also include one or more third-party devices, i.e., devices manufactured by a third party. company that differs from the one manufacturing the vehicle's UWB system. For example, one or more third-party devices may include smart devices, such as smartwatches or mobile phones.

[0036] The vehicle and each wearable identifier can be configured to communicate using the UWB (Ultra Wide Band) communication protocol. UWB can refer to a communication protocol, for example, that specified by IEEE 802.15.4. The vehicle and one or more wearable identifiers (for example, all of them) can also be configured to communicate using one or more other communication protocols, such as the BLE (Bluetooth Low Energy) communication protocol or the NFC (Near Field Communication) communication protocol.

[0037] The method comprises, for each portable identifier, a reception S10 of a respective UWB location programming with the vehicle's UWB system by one or more UWB sensors. The received programming may be numerical data. The respective programming received for each portable identifier may include, for each UWB location in the programming, numerical data defining a temporal positioning of the UWB location, for example, on a time axis (or line). For example, the respective programming received for each portable identifier may include, for each UWB location in the programming, start and end times specified on this time axis. The time axis may represent a future duration that has not yet elapsed at the time the programming is received.For example, the respective programming may include, for a set of successive periods (of substantially equal duration), a UWB location for each period. In particular, each period may include an identical number of successive slots (of substantially equal duration), and the UWB location may be programmed within one of these slots. The digital data may in this case include, for each UWB location, the slot number on which the UWB location is programmed. Alternatively or additionally, the digital data may include data designating a start time of this slot on which the location is programmed and data designating an end time of this slot. Alternatively or additionally, the digital data defining each location may include digital data defining each of the UWB emissions of the UWB location. For example, the digital data... can designate a start time and an end time of each UWB exchange in the UWB location.

[0038] Each registered handheld identifier can be configured to send its respective programming, which is received by the UWB system. Each registered handheld identifier can be within a given range around the vehicle, allowing it to send its respective programming to the UWB system. The respective programming can be sent by the handheld identifiers and received by the UWB system using a companion communication protocol (such as the BLE communication protocol). The UWB system may also have registered one or more other handheld identifiers (or devices), which may, for example, currently be out of range. The consideration of these other handheld identifiers is discussed later.

[0039] After or during the S10 reception, the method may include recording all received programming, for example, in system memory. The programming received from each handheld identifier may include the number of slots per period and / or the duration of each slot or period. For each period, the programming may also include an indication of the slot on which the UWB location is programmed for that period (this slot may vary randomly from period to period or be fixed). This information may be specific to the handheld identifier. The handheld identifier may be configured to enforce certain parameters of its programming.

[0040] Each UWB location may include one or more UWB exchanges between the wearable identifier and the system's UWB sensors. Each UWB exchange may consist of frame transmissions between the identifier and one or more UWB sensors. The programming of one or more locations may include, for each location, the determination of a time position for each frame transmission of each of the location's UWB exchanges. A frame transmission of a UWB exchange may have a duration of between 60 and 137 microseconds.

[0041] After the S10 reception, the method includes the S20 detection of the overlap between at least two programmed UWB locations. The at least two overlapping UWB locations include a UWB location with the key fob. In other words, the time slots on which the at least two UWB locations are programmed have a non-zero intersection. For example, the time slot on which a first UWB location involving a first portable identifier is programmed can begin before the end of the time slot on which a second UWB location involving a second portable identifier is programmed (the first or second portable identifier being the key fob).

[0042] The S20 detection can be performed in any manner. For example, as illustrated in [Fig. 2], the S20 detection of the overlap can comprise two steps, S21 and S22. The first step, S21, can be a projection of the UWB locations of each of the handheld devices onto a common time axis. The S21 projection of the UWB locations can include, for each UWB location, an indication of the start and end times of the UWB location on this common time axis. The second step, S22, can be a determination of an overlap between the projections of at least two overlapping UWB locations. The determination of the overlap can be performed using the start and end times indicated on the axis for each UWB location.For example, determining the overlap may include determining that the end time of the slot on which the second UWB location involving the second portable identifier is scheduled is located before the start time of the slot on which the first UWB location involving the first portable identifier is scheduled.

[0043] After detection S20, the method includes shifting S30, in the respective programming of the key fob, the superimposed UWB location. The superimposed location that is shifted is the one involving the key fob. For this key fob, the received programming includes, for each period, a respective location, and, for a given period, the UWB location is superimposed with the UWB location of at least one other handheld device. This given period may include several successive slots (of substantially equal duration), and the superimposed UWB location may be located within the first of these successive slots. The shift S30 may include a modification of the slot on which the UWB location is programmed. For example, the UWB location may be shifted to a second slot (other than the first) of the given period.The S30 shift may involve determining a new respective programming for the key fob, the location initially superimposed with another being shifted in this new respective programming.

[0044] The S30 offset of the superimposed UWB location may include sending, by the UWB system to the key fob, a command to execute the respective programming with the offset UWB location. For example, the S30 offset may include sending the determined new programming to the key fob. The key fob may be configured to receive and execute such a command. The remote key fob may be configured to execute such new programming sent by the UWB system. When the plurality of wearable identifiers includes one or more third-party devices, these third-party devices may not be able to modify their respective programming as easily as the key fob. This makes the a particularly effective method, since it proposes to solve the overlapping problem by modifying the programming of the key fob (and not third-party devices).

[0045] The offset S30 can be implemented in any way. For example, as illustrated in [Fig. 2], the offset S30 can comprise the three steps S31, S32, and S33. The first step, S31, can be a projection, onto the respective programming of the key fob, of the UWB locations of each other handheld device. The projection S31 can include an indication of all the start and end times of the UWB locations of each other handheld device on the time axis of the respective programming of the key fob. For each UWB location, the start and end times that are projected can be the start and end times of the time slot on which the UWB location is programmed. In other words, the method can assume that each UWB location lasts for the entire length of the time slot on which it is scheduled.

[0046] The second step S32 may be a determination of at least one free slot in the respective period by excluding each slot on which at least one projected UWB location overlaps. The respective period is the period during which the overlapping UWB location is currently programmed. The determination of at least one free slot may include, for each slot in this respective period, a check that the slot is free and, if so, a recording of the slot as free. The check that a slot is free may include a check for the absence of a UWB location involving another portable device programmed during that slot (for example, by verifying that the intersection, on said time axis, of that slot and the projection of the slot on which the nearest UWB location for each other portable identifier is zero).

[0047] The third step S33 may be a reprogramming of the superimposed UWB location to at least one determined free time slot. For example, the third step S33 may include selecting a time slot from among at least one determined free time slot, and then reprogramming the superimposed UWB location to the selected time slot. The selection of a time slot from among the at least one determined free time slot may be carried out in any way, such as randomly or by closest proximity to the time slot on which the superimposed UWB location is initially programmed. The reprogramming may include determining a new program for the key fob in which the initially superimposed UWB location is shifted to be executed on the selected time slot, and sending this new program to the key fob. (accompanied, for example, by an order to execute UWB localizations according to this new programming).

[0048] In examples, the method can detect multiple overlaps of UWB locations in the respective programming of the portable identifiers. In this case, the method can repeat the S30 shift step for each of the detected overlaps in order to resolve the overlap problem at each detected overlap. Each S30 shift can, in this case, be executed as previously discussed, considering each time a new overlap of UWB locations (and potentially new identifiers involved, these including at least one key fob).

[0049] In examples, the plurality of wearable identifiers includes at least two third-party devices. The at least two overlapping UWB locations include at least one UWB location with each of the at least two third-party devices. In this case, the method may further include determining a priority device from among the at least two third-party devices. The determination of the priority device may be derived from a predetermined order for all third-party devices applied by the UWB system. For example, the third-party devices may include a priority device, i.e., one that is predetermined or designated as such in the UWB system. For example, the third-party devices may include a priority device and one or more secondary devices. The priority device may have priority operation in the locations, relative to the one or more secondary devices.For example, the programming of locations involving the primary device can override the programming of locations involving one or more secondary devices. The process can then include deprogramming, for each third-party device other than the primary device, the UWB location included in the at least two overlapping UWB locations. This allows only the UWB location of the primary device to be retained.

[0050] In examples, the detection steps S20 and offset steps S30 can be repeated each time a new programming is received for a new wearable identifier. For example, this new wearable identifier may initially be out of range of the vehicle, and the user wearing it may approach the vehicle. This new identifier may also be registered by the UWB system (in addition to the others). As the user approaches the vehicle, once the new identifier enters the BLE perimeter around the vehicle, the new identifier can be configured to begin locating the vehicle. To do this, the new identifier can be configured to send its respective programming to the UWB system. The method may then include receiving this programming. respective for this new identifier (as for the other identifiers in step S10). In this case, the process may include repeating steps S20 and S30 with the respective new programming received for the new identifier. For example, detection S20 may include detecting a new overlap between at least two locations, one of which involves the new identifier, and then, if this identifier is a key fob, shifting this location in the programming of the new identifier. Alternatively, the process may include shifting another location among those overlapping that involves a key fob.

[0051] Examples will now be described with reference to Figures 3 to 6.

[0052] Figure 3 illustrates examples of overlapping UWB location shifting according to the planning method. In particular, the method is applied here to the same situation shown in Figure 1. The method comprises receiving, for each wearable identifier (WI), a respective UWB location programming (S10). These UWB locations are then used to determine the position of each WI. Each WI can, for example, be configured to send its respective programming when it enters a certain perimeter around the vehicle, for example, after a preliminary identification step. The UWB system and the WI can then be configured to perform the UWB locations according to the established respective programming.The figure shows the received programming for a set of three portable identifiers registered by the UWB system: a key fob 100 and two mobile phones 200 and 300. The received programming for each portable identifier comprises, over a predetermined duration divided into periods (periods 111, 112, 113, and 114 for key fob 100), a UWB location for each period of the predetermined duration (location 131 for block 111, 132 for 112, and so on). Specifically, each period is divided into a predetermined number of slots 122 (8 slots per period in this example), and the programming includes, for each location, the slot within the period on which the location is scheduled. For example, for the first period 111 of the session for the first portable device 100, the programming includes a numeric value indicating that the UWB location is scheduled for the first slot 131 of period 111.Each programmed UWB location of a handheld device includes UWB exchanges between the handheld device and each of the UWB sensors in the UWB system, and these UWB exchanges are performed during the window of the period over which the UWB location is planned.

[0053] The method then includes the S20 detection step for overlap(s). In this example, the method detects several overlaps of UWB locations in the respective programming of the portable identifiers. In particular, the method detects a first superposition between locations 132 and 332, a second superposition between locations 134, 234 and 335 and a third superposition between locations 135, 235 and 336. The detection S20 of each superposition can include the two steps S21 and S22 previously discussed, namely a first step S21 of projecting the UWB locations of the handheld devices 100, 200, 300 onto a common time axis (for example the 500 axis), then, a second step S22 of determining, for each superposition, an overlap between the projections of the UWB locations.

[0054] Once the overlaps are detected, the process repeats the S30 shift step for each detected overlap in order to resolve the interference problem at each detected overlap. Each location overlap resolution is now discussed in more detail.

[0055] The first superposition is a superposition of two locations: location 132 involving the key fob 100 and location 332 involving the mobile phone 300. The method includes an offset S30, in the respective programming of the key fob 100, of the superimposed UWB location 132. The superimposed UWB location 132 is currently programmed within the third slot of period 112. The method shifts the UWB location 132 to the first slot 132' of period 112. The offset S30 comprises the three steps S31, S32, and S33 previously discussed. The first step S31 is a projection, onto the respective programming of the key case 100, of the UWB locations of each other portable device 200, 300. The second step S32 is a determination of at least one free slot of the respective period by excluding each slot on which at least one projected UWB location overlaps.In this example, the process can determine that the first, second, fifth, sixth, seventh, and eighth slots of period 112 are free. The third step S33 is a reprogramming of the superimposed UWB location 132 onto the at least one determined free slot (the offset UWB location 132' is now scheduled for the first slot).

[0056] The second superposition is a superposition of three locations: location 134 involving the key fob 100, location 234 involving the mobile phone 200, and location 335 involving the mobile phone 300. The method includes an S30 shift, in the respective programming of the key fob 100, of the superimposed UWB location 134. The superimposed UWB location 134 is currently programmed within the eighth slot of period 114. For this superposition, the method shifts the UWB location 134 to the third slot 134' of period 114 (the third and sixth slots of period 114 being free). In this second superposition, the locations involved include the location 234 involving mobile phone 200 and location 335 involving mobile phone 300. As these two locations are not superimposed on each other (they are only superimposed with location 134 involving key fob 100), the process preserves the programming of these locations (and does not modify the programming of mobile phones 200 and 300).

[0057] The third overlay is an overlay of three locations: location 135 involving the key fob 100, location 235 involving the mobile phone 200, and location 336 involving the mobile phone 300. The superimposed UWB location 135 is currently programmed within the seventh slot of period 115. For this overlay, the method shifts the UWB location 135 to the fourth slot 135' of period 115 (the second, third, fourth, and fifth slots of period 115 being free). In this third overlay, the locations involved include location 235 involving the mobile phone 200 and location 336 involving the mobile phone 300. These two locations are superimposed on each other. The method includes determining the overlay of at least one UWB location with each of the at least two third-party devices (200 and 300 in this example).The method includes an S40 determination of a priority device among at least two third-party devices 200, 300. In this example, mobile phone 200 has priority over mobile phone 300 (it is, for example, registered as such by the UWB system). The method then includes an S42 deprogramming, for third-party device 200, of the UWB location 336.

[0058] After each S30 shift, the method includes determining a new respective program for the key fob 100. This new program includes the shifted locations 132', 134', and 135'. The method includes sending, via the UWB system, to the key fob 100, a command to execute the new program with the shifted locations 132', 134', and 135'. The key fob 100 is configured to receive and execute such a command. The method also includes sending, via the UWB system, to the mobile phone 300, a command to deprogram (or cancel) location 336. The mobile phone 300 is configured not to execute location 336 in this case. The method thus avoids the cancellation of four locations (one for the first overlay, two for the second, and one for the third). This improves the accuracy of locating the three portable identifiers.

[0059] Figure 4 illustrates examples of determining free time slots. The figure reproduces the example of Figure 3 with programs received by the UWB system from three handheld devices 100, 200, and 300. For each overlay, the offset S30 comprises the three steps S31, S32, and S33 previously discussed. The first Step S31 projects the UWB locations of each other handheld device 200, 300 onto the respective programming of key fob 100. The second step, S32, determines at least one free slot in the respective period by excluding each slot on which at least one projected UWB location overlaps. For the first overlap, the process determines that the first and second slots 151 and the fifth, sixth, seventh, and eighth slots of period 112 are free. The overlapping UWB location 132 is therefore reprogrammed to one of these free slots (the first slot in this example). For the second overlap, the process determines that the third 153 and sixth 154 slots of period 114 are free. The process therefore shifts the UWB location 134 to the third slot of period 114.For the third overlay, the process determines that the second, third, fourth, and fifth slots 155 of period 115 are free. The process therefore shifts the UWB 135 location to the fourth slot of period 115. The free slot is a slot located within the period where the overlay occurs and prior to this overlay. Thus, the location of the identifier is not delayed.

[0060] Figure 5 illustrates an example of a vehicle system 10. The system 10 is configured to implement the unlocking procedure. The system includes several secondary UWB sensors (or anchors) 11 connected to a private CAN (Controller Area Network) 12. The secondary UWB sensors 11 are sensors located inside the vehicle. The system also includes a master sensor (or anchor) 13, which is a master unit for the system. Each UWB sensor includes means for transmitting and receiving UWB exchanges (such as one or more transmitting and / or receiving antennas for such UWB exchanges) with handheld devices, for example, to perform UWB location tracking of these handheld devices. The system also includes an NFC reader 14. The system supports Bluetooth technology. The master anchor 13 and the NFC reader 14 are also connected to the system's network 12.

[0061] A vehicle remote control key fob 110, or "identifier," may include a protective housing enclosing the key fob components. The protective housing may be made of plastic, metal, and / or rubberized plastic. The key fob 110 may include a logo, for example, made of metal. The logo may be located on the outer casing of the protective housing, and / or the logo may represent a manufacturer's mark. The key fob 110 may include, within the protective housing, a metal insert that allows a vehicle 120 to be opened and / or started manually by inserting and manipulating the insert into a respective lock of the vehicle 120.

[0062] The key housing 110 includes a BLE component 112, configured to perform BLE communication with a vehicle, and including, for example, a microprocessor. The key fob 110 also includes an antenna 116 connected to the BLE component 112. The antenna 116 is configured to transmit or receive BLE signals. The microprocessor of the BLE component 112 can store a computer program in its memory that enables BLE communication and performs various specific functions. The BLE component 112 can store the BLE key 132 exchanged with the vehicle 120. The key fob 110 also includes a UWB component 111 for UWB communication with a vehicle.

Claims

Demands

1. A planning method implemented by a vehicle UWB system, the UWB system (10) comprising one or more UWB sensors (11, 13), the UWB system (10) having stored a plurality of portable identifiers (100, 200, 300), the plurality of portable identifiers comprising a remote control key fob (100), the method comprising: • a reception (S 10), for each portable identifier, of a respective programming of UWB locations (131, 132...) with the vehicle's UWB system; • a detection (S20) of an overlap between at least two programmed UWB locations (132, 332), the at least two overlapping UWB locations including a UWB location with the key fob (100); and • an offset (S30), in the respective programming of the key fob (100), of the overlapping UWB location (132, 332), the overlapping UWB location being programmed within a first slot of a respective period (112) including several slots, the UWB location being offset to a second slot of the respective period.

2. A method according to claim 1, wherein the offset (S30) of the superimposed UWB location comprises: • a projection (S31), onto the respective programming of the key case (100), of the UWB locations of each other portable device; • a determination (S32) of at least one free slot of the respective period (112) by excluding each slot on which at least one projected UWB location overlaps; and • a reprogramming (S33) of the superimposed UWB location on the at least one determined free slot.

3. A method according to any one of claims 1 or 2, wherein the superposition detection comprises: • a projection (S21) of the UWB locations of each of the handheld devices onto a common time axis; and • a determination (S22) of an overlap between the projections of at least two superimposed UWB locations.

4. A method according to any one of claims 1 to 3, wherein the offset of the superimposed UWB location comprises sending, by the UWB system (10) to the key box (100), an order to execute the respective programming with the offset UWB location.

5. A method according to any one of claims 1 to 4, wherein the plurality of wearable identifiers (100, 200, 300) comprising at least two third devices (200, 300), the at least two overlapping UWB locations including at least one UWB location with each of the at least two third devices, the method further comprising: • a determination (S40) of a priority device (200) among the at least two third devices; and • a deprogramming (S42), for each third device other than the priority device, of the UWB location included in the at least two overlapping UWB locations.

6. A method according to any one of claims 1 to 4, wherein the detection (S20) and shift (S30) steps are repeated at each receipt of a new respective programming for a new portable identifier.

7. Method of using a vehicle UWB system, the UWB system comprising one or more UWB sensors (11, 13), the UWB system (10) having recorded a plurality of portable identifiers, the plurality of portable identifiers comprising the key fob (100), the method comprising an execution of the planned UWB locations according to the method of any one of claims 1 to 6.

8. Vehicle UWB system, the UWB system comprising one or more UWB sensors and being configured to perform the method of any one of claims 1 to 6 and / or to be used according to the method of claim 7.

9. A computer program comprising program code instructions for carrying out the process according to any of claims 1 to 6 and / or according to claim 7, when said program is executed by a processor.

Images