DE102019122669A1 - METHOD AND DEVICE FOR A PEER-TO-PEER DISTRIBUTION STRATEGY FOR UPDATES - Google Patents

Abstract

This disclosure provides a method and apparatus for a peer-to-peer distribution strategy for updates. A system includes a processor configured to receive a plurality of reports that identify a file segment distribution to reporting vehicles. The processor is also configured to determine reseed file segments to improve distribution characteristics in response to the reports. The processor is further configured to determine a plurality of possible delivery vehicles and in response to determining that a distribution threshold has been reached, sending the reseed file segments to the particular delivery vehicles.

Description

TECHNICAL AREA

The illustrative embodiments generally relate to methods and devices for a peer-to-peer distribution strategy for updates.

GENERAL PRIOR ART

Modern vehicles are complex computers with numerous electronic control units (ECUs) and software processes that communicate with each other to enable a technologically improved driving experience. As with most software and firmwares, the files that support this exchange are updated regularly to improve functionality, improve communication and fix bugs.

Before vehicles could access wireless services, file updates were typically done manually by a user or a mechanic or other certified technician. This had the advantage that large file transfers and updates were possible at once, as well as error checking and update confirmation. The disadvantage of this process was that a user either had to understand the process enough to activate it himself or had to be willing to go to a technician to get an update.

Over-the-air updates, once the vehicles were connected wirelessly, was an attempt to fix this. This process enabled vehicles to receive software updates wirelessly. However, due to the large number of vehicles on the road, using over-the-air updates to distribute even a fraction of the total updates could be a potentially expensive solution. Although it is a viable option for file updates, the associated amounts of money and data transfer have limited the use of this process, especially for non-important updates and for distribution among large fleets (e.g. an entire OEM model range) ,

SUMMARY

In a first illustrative embodiment, a system includes a processor configured to receive a plurality of reports that identify a file segment distribution to reporting vehicles. The processor is also configured to determine reseed file segments to improve distribution characteristics in response to the reports. The processor is further configured to determine a plurality of possible delivery vehicles and in response to determining that a distribution threshold has been reached, sending the reseed file segments to the particular delivery vehicles.

In a second illustrative embodiment, a system includes a processor configured to determine a plurality of vehicles located within a predefined region and corresponding to one or more predefined thresholds for seed characteristics associated with the region. The processor is also configured to set the threshold values for the characteristics to achieve a group size of the plurality of vehicles within a predefined group size range. The processor is also configured to provide file segments representing portions of completed update files to each of the plurality of vehicles in response to the group size being within the size range.

In a third illustrative embodiment, a computer-implemented method includes determining whether the vehicle has a file segment that has a predefined preferred distribution characteristic in response to detecting a vehicle ignition off. The method also includes placing the vehicle in a low power state, where the vehicle is able to receive requests for the file segment in response to determining that the vehicle has the file segment. The method further includes responding to the requests for the file segment by providing the file segment until a vehicle performance condition reaches a predefined threshold.

list of figures

• 1 Figure 3 shows an illustrative peer-to-peer distribution system;
• 2 Figure 3 shows an illustrative process for receiving and updating files;
• 3 shows an illustrative process for the reseed selection;
• 4 Figure 3 shows an illustrative process for direct peer-to-peer transmission;
• 5 Figure 3 shows an illustrative process for broadcast transmission;
• 6 Figure 3 shows an illustrative process for seed vehicle selection;
• 7 Figure 3 shows an illustrative process for segment selection; and
• 8th shows an illustrative process for parking transfer.

DETAILED DESCRIPTION

Depending on requirements, detailed embodiments are disclosed here; however, it is to be understood that the disclosed embodiments are merely illustrative and can be included in various and alternative forms. The figures are not necessarily to scale; some features may be enlarged or reduced to show details of certain components. Therefore, the specific structural and functional details disclosed here are not to be interpreted as restrictive, but merely as a representative basis in order to teach the person skilled in the art how to implement the claimed subject matter in various ways.

A vehicle that is involved in a peer-to-peer transfer and / or over-the-air updates can be equipped with a vehicle-based computing system that can include a visual front-end interface that is located in the vehicle. The user may also be able to interact with the interface if, for example, it is provided with a touchscreen display. In another illustrative embodiment, the interaction is through keystrokes, a speech dialog system with automatic speech recognition, and speech synthesis.

In such a vehicle, one or more processors controls at least part of the operation of the vehicle-based computing system. The processor provided inside the vehicle enables commands and routines to be processed within the vehicle. Furthermore, the processor is connected to both non-permanent and permanent memories. In this illustrative embodiment, the non-persistent memory is a random access memory (RAM) and the persistent memory is a hard disk drive (HDD) or flash memory. In general, persistent (non-volatile) memory can include any form of storage that stores data when a computer or other device is down. These include HDDs, CDs, DVDs, magnetic tapes, solid-state drives, portable USB drives and any other suitable form of permanent storage.

The processor is also provided with a number of different inputs that allow the user to interface with the processor. These include, for example, a microphone, an auxiliary input, a USB input, a GPS input, a screen, which can be a touchscreen display, and a BLUETOOTH or other wireless input. An input selector can also be provided to allow a user to switch between different inputs. Numerous vehicle components and auxiliary components that are in communication with the VCS can use a vehicle network (such as a CAN bus, among others) to forward data to and from the VCS (or components thereof).

Outputs to the system can include, among other things, a visual display and a speaker or stereo system output. The speaker is connected to an amplifier and receives its signal from the processor through a digital-to-analog converter. The output can also be transmitted to a remote BLUETOOTH transceiver or other wireless transceiver.

Data may be communicated between the VCS and a remote network or other vehicle that uses, for example, a data plan, voice data, or DTMF tones associated with a wireless device. Alternatively, it may be desirable to integrate an in-vehicle modem to communicate data between the VCS and the network.

In one illustrative embodiment, the processor is provided with an operating system that includes an API for communicating with modem application software. The modem application software can access an embedded module or firmware on the BLUETOOTH transceiver to complete wireless communication with a remote BLUETOOTH transceiver (such as that found in a mobile device). Bluetooth is a subset of the IEEE 802 PAN (Personal Area Network) protocols. The IEEE 802 LAN (Local Area Network) protocols include WLAN and have considerable cross-functionality with IEEE 802 PAN. Both are suitable for wireless communication within a vehicle. Other means of communication that can be used in this area are optical free space communication (such as IrDA) and non-standardized consumer IR protocol.

In another embodiment, the ND 53 includes a modem for voice band or broadband data communication. In the data-over-speech embodiment, a technique known as frequency division multiplexing can be implemented when the owner of the mobile device can speak simultaneous data transmission via the device. At other times, when the owner is not using the device, the entire bandwidth (300 Hz to 3.4 kHz in one example) can be used for data transmission. Although frequency division multiplexing can be and is still used in analogue mobile radio communication between the vehicle and the Internet, it has largely been used through hybrids of code division multiple access (Code Domain Multiple Access - CDMA), time division multiple access (TDMA) and space division multiplexing (Space Domain Multiple Access SDMA) for digital cellular communication. If the user has a data plan associated with the mobile device, there is a possibility that the data plan would enable broadband transmission and the system could use a much larger bandwidth (which increases the data transmission speed). In yet another embodiment, the ND 53 is replaced by a mobile radio communication device (not shown) that is installed in the vehicle 31. In yet another embodiment, the ND 53 may be a local area network (LAN) device that can communicate, for example (and without limitation) over an 802.11g network (ie, WLAN) or a WiMax network.

Vehicle transceivers can provide a variety of in-vehicle and off-vehicle communications that enable peer-to-peer, vehicle infrastructure, and vehicle cloud communications. Some or all of these communication functions aid in the implementation of the illustrative embodiments and the like.

In addition to executing exemplary processes by a vehicle computing system located in a vehicle, in certain embodiments, the exemplary processes may be performed by a computing system that is in communication with a vehicle computing system. Such a system may include, among other things, a wireless device (e.g., a cell phone, among others) or a remote computing system (e.g., a server, among others) connected by the wireless device. Together, such systems can be referred to as vehicle-associated computing systems (VACS). In certain embodiments, certain components of the VACS can perform certain parts of a process depending on the specific implementation of the system. For example, if a process includes a step of sending or receiving information with a paired wireless device, and is not limiting, the wireless device is likely not to perform that part of the process because the wireless device is not itself information Would send and receive. Those of ordinary skill in the art will understand when it is inappropriate to apply a particular computing system to a given solution.

In each of the illustrative embodiments discussed herein, an exemplary, non-limiting example of a process that can be performed by a computing system is shown. With respect to each process, it is possible that the computing system that executes the process is configured as a special purpose processor for performing the process for the limited purpose of executing the process. All processes need not be carried out in their entirety and are to be understood as examples of process types that can be carried out in order to achieve elements of the invention. Additional steps can be added to or removed from the example processes as needed.

With respect to the illustrative embodiments described in the figures that show illustrative process flows, it should be noted that a general purpose processor may be temporarily activated as a special purpose processor for the purpose of performing some or all of the exemplary methods shown by these figures. If code is executed that provides instructions for performing some or all of the steps of the process, the processor can again be temporarily used as a special purpose processor until the process is complete. In another example, firmware that operates according to a preconfigured processor may, to an appropriate extent, cause the processor to act as a special purpose processor provided for the purpose of performing the method or an appropriate variation thereof.

With the ability to transfer files with limited packet size in conjunction with a dynamic distribution strategy, the illustrative concepts and embodiments offer opportunities to improve the utility and functionality of over-the-air updates. The illustrative embodiments enable tremendous saturation at a fraction of the cost of distributing updates directly to a large number of vehicles. Since the distribution strategy is adaptive, the system can also effectively and efficiently take into account distribution delays. The novel, unusual and atypical examples and concepts described here show possible improvements which can be achieved by using these examples, concepts and the like.

Although it may be undesirable or even costly, using an over-the-air (OTA) distribution to distribute a large number of updates to a large number of vehicles, distribute small portions of update files to selected vehicles, and enable that these parts can spread throughout the motion system represented by moving vehicles, a distribution strategy that leverages the OTA delivery capabilities associated with the vehicle-all (FX) communication capabilities of many modern vehicles.

Splitting a file into segments and strategically selecting seed vehicles to increase deployment spread require limited OTA transmission (from OEM to vehicles), but vehicles can still receive OTA updates that don't require it that the user updates a file manually. Using intelligent and adaptive delivery strategies can reseed missing parts of the file (which have not been distributed at sufficient speed), and the strategic use of stationary vehicles and roadside infrastructure can help maintain a reliable delivery strategy while minimizing costs and distribution time ,

1 Figure 3 shows an illustrative peer-to-peer distribution system. This is a simplified example of a file distribution process 111 on a cloud basis 101 an update file 109 for distribution to a vehicle. In this example there are three vehicles 103 . 105 . 107 to update. If the file were 300 Kb, the process would require at least 900 Kb of total data transfer to distribute the entire file to each vehicle. If the process instead the file in three parts 113 . 115 . 117 would disassemble with a size of 100 Kb each and send each part to a vehicle, then the total transmitted data would be closer to 300 Kb. The vehicles themselves could then transfer the missing parts among themselves 119 by taking advantage of localized communication, which potentially causes zero data transmission costs for everyone.

Even in this simple example, data savings are threefold, and if it is 100 Vehicles that needed the files, but each of them 97 other vehicles, as expected or expected to get into the transmission range of one of the vehicles shown or another of the hundred vehicles after this vehicle has received some or all of the files until all vehicles have finally transferred all the parts to one another, the data savings would be more than 300 times ,

While some vehicles may never get a portion of a file, especially if the file is broken down into dozens of segments or more, and eventually need to request the missing part (s), using the illustrative embodiments and the like may help massive data savings can still be achieved.

2 shows an illustrative process for receiving and updating files. In this example receives 201 the process takes a piece of file from, for example, another vehicle or from an infrastructure component. In addition to using vehicles to share files, the illustrative examples can use the roadside infrastructure to distribute, for example, parts of files or often missing parts. These units, which can be constantly active, can send missing parts or most frequently requested parts or use a recurring strategy to send many different parts early in an update cycle. While the cycle is spreading the update, missing parts can often be identified and the broadcast by the roadside unit can change to take into account the completion of the spread. This means, for example, that the unit can initially send one of 10 parts, changing every minute. While the parts or segments are spreading, it can be observed that segments six and eight are not as widely spread, and thus the units can switch to a higher frequency or exclusive provision of segments 6 and 8. If segment 8 becomes sufficiently saturated, the unit can proceed to send only to segment 6.

By selecting and positioning units where a high level of traffic is observed (but which can also move at a speed sufficient to receive a segment, e.g. at a traffic light or stop sign), these units can be extremely effective in distributing updates and improving distribution. Although this is not always necessary, it can serve a useful purpose. Because these units can be firmly connected to a network and / or have a local power supply and can always be active, they can serve a useful, localized purpose in distribution. The disadvantage of these units is that they typically do not move, so vehicles can still be a good medium for transporting the update segments to more distant locations.

Checked the vehicle 203 After receiving the update, an in-vehicle log of which file sections or segments have been received and saved. When the file is complete (all segments have been received), the process can merge the update file 217 , The process can also report success (when merging or at a reasonable time) to the remote system 219 , For example, this report can also include total merging time, locations where segments were received, reception errors, segment errors, and other demographic and visual factors that may be useful to the cloud as it improves distribution strategies.

If the file is not complete, the process can update an in-vehicle directory 207 , which indicates which segments are present and / or which segments are required. This list is useful in deciding which segments to share and / or to request from other vehicles and infrastructure.

This example also takes into account that vehicles are able to complete part files themselves by requesting the remaining parts from a server. If a vehicle is removed or drives irregularly, it may take a while for the vehicle to be able to receive all parts of an update. In this example, the vehicle has three illustrative self-closing options.

First, the process in this example determines whether a maximum update time has passed 209 , For example, an update can have a maximum completion time associated with it. This time could be applied to all segments so that the vehicle can easily compare the "expiration date" with the current date and know that the maximum time has expired. This time can also depend on how often the vehicle receives parts, and / or the time since the vehicle was last driven, the last time a part was received, or the last drive to a geographic area associated with frequent file transfers. This would allow accelerated (based on a maximum) completion based on the fact that the vehicle is driving irregularly or encounters other vehicles with parts irregularly.

In this example, the process also determines whether there is a maximum number of parts (or bytes) left 211 , That is, if the total cost of transferring the remaining parts of the file is low, the vehicle can request a last part or a few last parts. Since this vehicle can also encounter other vehicles, additional efficiency can arise by allowing certain vehicles to complete their files in this way, since the requested parts are also forwarded to other vehicles via peer-to-peer transmission can.

The process also determines whether the vehicle is missing only rare parts. It makes sense to assume that certain parts are distributed at a lower frequency since saturation continues, and therefore there may be some parts that lack sufficient distribution. The fact that a vehicle that only has rare parts is able to request these parts directly makes this vehicle the carrier for the few parts for the purpose of redistribution. Any or all of these completion functions may also be associated with a determination of other of these functions and / or the use of the vehicle in question as a seed vehicle (e.g. vehicles that are more good seed vehicles may have a preferred ability to self-complete receive).

If the parameters for self-completion are met, the process can complete 215 by requesting the missing segments directly from the OEM server. The process could then merge the file again. Regardless of whether the completion is complete or not, the process can output statistics on the most recently received part and all other relevant data to determine whether self-completion and / or an improvement in distribution efficiency has occurred. For example, if fifty vehicles are requested in an area and the rarest part of an update is provided, the system can wait for some time for these vehicles to distribute the part until a voluntary reseeding takes place.

After editing the received segment, the vehicle can display the current set of available data 221 and / or request missing data from other transmission units (e.g. other vehicles and / or roadside elements).

3 shows an illustrative process for the reseed selection. In this example receives 301 the process server side reports of vehicles when segments are distributed through the network of working vehicles. This enables the server to update the distribution pattern 303 , effectively considering where the segments are sent to, which segments were previously broadcast, and which vehicles now have segments for a probability of determining distribution across those vehicles.

Examining a distribution pattern can also include the presence of rare segments 305 disclose, which are essentially segments that are not disseminated with sufficient frequency. Additionally or alternatively, the patterns may have a slow distribution rate 307 specify what a poor selection for seed vehicles and / or insufficient initial seeding may indicate. All of this data can have both ways to improve seeding and ways to reseed certain vehicles for quick distribution.

If reseeding of rare or inadequate segments is needed, the process can identify suitable vehicles for reseeding. For example, in the case of a slow distribution, the process can use a threshold based on time or geography. For example, in the time-based case, the process can expect to see a certain volume of transmissions over a certain period of time. If there are no rare parts (i.e., if no particular part itself is identified as sufficiently irregularly transmitted), the process can determine that all segments should be reeeded.

With the geographic threshold, the process can determine an insufficient volume of parts within a defined geographic region. For example, the process could map the segment distribution on a thermal map and recognize that a certain volume of a geographic region has few or no segments. In another example, the process could track a route that is associated with each segment through the total route or through vectors. This could be done using GPS coordinates during the transmission, for example, and the segment movement and the flow direction of segments could be determined. For example, if all segments tend to flow around a certain radius, the process may want to reeed all vehicles that are outside that radius and drive out, or vehicles that are likely to move in such a way, to increase the outward flow of segments.

The selection of the reseed vehicles can also depend on the reason for the reseeding. If the distribution does not spread quickly enough, e.g. B. in the time-based model, the process can select vehicles that are expected or likely to travel on important traffic routes and / or meet a large number of vehicles. In the geographic model, the process can select vehicles that are expected or likely to go to non-seedless areas and / or outside of the limited areas. While these are just examples of how the reseed determination could be made and how the perceived deficiency could be remedied, they generally reflect the fact that the reseeding can be adjusted for a variety of reasons that serve as the basis for the reseed - serve needs. For example, in the reseed determination of “rare” parts, the process could identify one or more possible vehicles that are expected or likely to drive within areas that have the least occurrence of the rare parts, or in another example possible vehicles that are expected to hit most vehicles (for the purpose of sharing). Based on the effectiveness of the trials for a specific scenario, future reseed optimization strategies can be adjusted accordingly.

4 shows an illustrative process for direct peer-to-peer transmission. In this example, connects 401 the process with another vehicle (a peer) and requests one or more missing segments 403 , For example, the process could identify that segments 1, 3, and 5 are missing. The peer could respond 405 to having segments 1 and 3, and then the process could receive segment 1, for example 407 , Which of a plurality of segments is selected may be random or dependent on the optimized distribution, so that, for example, a least distributed segment is first distributed (as indicated by a server or by in-vehicle metrics) to improve the general segment distribution.

The process can then receive a request from the peer vehicle 409 , the request specifying a segment desired by the peer. The peer will either already know which segments the underlying vehicle has (based on the original request), or the peer can identify which segments it needs. The process can then send the requested segment (and / or an answer if necessary) 411 , and then when the two vehicles are still connected 413 are and if every vehicle still has a need 415 the transmission loop can be repeated. While not necessary, this type of mutual sharing can increase distribution by alternately sharing file segments so that each vehicle is improved. In some models, vehicles that have been identified as seed vehicles can move all segments in first Get peer-to-peer before sharing them based on their expected driving patterns, so they can move most segments to most other vehicles the fastest (because once they have full files, they don't need to get segments and can do it with everyone) divide). If both vehicles no longer need segments, the process can end the communication 413 , Of course, this also happens if the vehicle is outside a wireless range.

5 shows an illustrative process for broadcast transmission. In this example, the process uses a send strategy instead of a direct transfer strategy. A particular vehicle can receive a broadcast from another local vehicle 501 , which indicates the availability (or need) of the segment. If the vehicle has one or more segments identified in a required shipment, the receiving vehicle can point to the sending vehicle (by sending or direct communication with a vehicle ID contained in the sending vehicle's shipment) with an identification of the im Owned segments react 503 , The original vehicle that needs a shipment can then send a request received from the vehicle owning the segment 505 has been. The vehicle owning the segment can then send (or transmit directly) 507 of the requested segment. If the vehicle owning the segment sends the segment, other local vehicles that also need the segment could opportunistically receive the segment from sending. As soon as the requesting vehicle received the segment and confirmed the receipt 509 has or as soon as a certain time without confirmation 511 the dividing vehicle may have passed 513 Stop sending and start sending available data (or needs) (or waiting for a request).

A vehicle can send both needs and available data, and if two vehicles meet and at least one can help the other, the vehicles can accommodate the meeting by sharing the segment with the vehicle that needs the segment. In this way, if the vehicle sending the segment provides the segment to other local vehicles that need the segment, transmission of segments among multiple vehicles can be achieved.

6 Figure 3 shows an illustrative process for seed vehicle selection. This is a non-limiting example of how a seed vehicle can be selected. Seed vehicles can be selected for a reason. For example, if one reason is to transfer the segment to as many vehicles as possible, the seed vehicle may be a vehicle that has been observed to frequently drive on roads where it encounters many other vehicles. On the other hand, if the reason is to transfer the segment to geographically distant regions, the seed vehicle may be a vehicle that is known to both travel to the distant region and with a certain frequency (e.g., time / Distance) within the distant region, increasing the likelihood that it will encounter other vehicles within the distant region. Reseeding can have a specific reason associated with restoring, and possible reseed vehicles can be selected to compensate for the reason (e.g., if the reason is that insufficient data is reaching a particular region, the compensating reseed vehicles often drive to this region).

Examined in this example 601 the process recorded driving behavior and / or (past or current) route information for a group of vehicles. For example, all vehicles on the road within a time window of 1 hour of a planned seed time or within planned seed times. In other examples, the group can be any known vehicle that is known to drive through specific regions and at specific times or frequencies, through specific regions, etc. There may be a set of minimum requirements, and based on the observed driving behavior, the group of possible vehicles may initially be determined by sorting.

The process can also apply other filters. In this example, the process filters for vehicles with a pre-defined frequency 603 used vehicles that have certain geographical limits 605 cross, and / or vehicles that are on a certain number of other vehicles (above a threshold) 607 meet, for example based on traffic forecasts or encounters at intersections. Some of these may be necessary characteristics, others may be secondary considerations. In this example, the process would only select the vehicles that match all three filter characteristics; however, if this would result in too few vehicles, the process could relax the restrictions (either by adjusting the threshold or by choosing an OR group rather than an AND group). The change in thresholds, filters, and AND / OR selectivity can eventually be a sentence within provide a targeted size range. The process can assign the seeds among the vehicles (random or strategic) 611 and if the group size is sufficient 613 , the process can distribute the restores.

Observing the results for the seeding of certain vehicles with certain characteristics can reveal the effectiveness of the specific vehicles and characteristics as a seed strategy supporting over time. This means that future seed planning can also be taken into account and the model can be adapted accordingly. In addition, a particular region may have one or more predefined seed characteristics associated therewith that correspond to an effective (predicted or observed) strategy for seeding that region. Each region can have different threshold values for each characteristic and even different characteristics for seed determinations.

7 shows an illustrative process for segment selection. In this example, vehicles can be commanded to provision certain segments first and / or queue specific segments for faster provision. For example, in this case the vehicle can count requests for each segment 701 and the most requested segment (s) caching 703 , This would allow faster deployment to those segments that were most frequently requested by this vehicle.

In this example, the vehicle can also receive cloud-based instructions 705 that tell the vehicle what order to use when deploying segments. For example, if a vehicle has segments 1 and 7 and segment 1 is distributed frequently and segment 7 is rarely distributed, the cloud can first instruct segment 7 to be deployed (for any vehicle that needs it) to distribute segment 7 to accelerate if both segments cannot be provided because the vehicles lose contact before a second segment can be exchanged. This can enable the cloud to adaptively accelerate the delivery of “rare” segments by prioritizing them, and the vehicle can deploy the rare segments first in response 707 , In other examples, the cloud instructions can be somewhat more complex, with deployment strategies associated with the present vehicle location, for example.

As an example, if the vehicle has segments 1 and 7 and 7 is the rare segment, the vehicle can often be ordered to provide segment 7 first. However, if the vehicle is in a geographic portion of the region where segment 1 is rare locally, the process may instruct the vehicle to switch from segment 1 to provision first instead 709 , Since the cloud does not really need to know which segments are in a particular vehicle or where the vehicle is or will be, the cloud can easily prioritize segments and assign any secondary parameters to secondary prioritizations (e.g. example for segment 1 above ) and deploy the strategy to some or all vehicles. The strategy itself can be seeded and distributed, and if the cloud observes the effects of the strategy, it can adapt to newly revealed needs and redistribute a new strategy. This monitoring, if available, can help to reduce deficiencies, although the system could also allow the distribution to grow organically and to compensate for the deficiencies after a long period.

8th shows an illustrative process for parking transfer. This is a stationary vehicle strategy that is not limited to parked vehicles, but can be used at any time when a vehicle is likely to be above a predefined threshold time. For example, if the vehicles stop at only one traffic light, the performance considerations may be less relevant. The specific strategy applies to parked, off vehicles, but could also be adapted to a variety of other stopping situations and could also be modified based on the characteristics of the parked vehicle.

Determined in this example 801 the process that the vehicle is in a parked state with the ignition off. Since the vehicle sends data in this example and is switched off, determined 803 the process of whether the vehicle has enough power to complete a transmission. If the vehicle has an appropriate power level, the process also determines whether the vehicle has rare segments 805 includes. The definition of what a rare segment is can change over time, so this definition could be updated by a server while the vehicle was parking, or could be updated before the vehicle's ignition was turned off.

In this example, if the vehicle has a rare segment, the process can put the vehicle into a low performance state 807 , being able to Receive and respond to requests for the rare segment. The condition may only be able to receive the request and the vehicle may remain on to respond to a request 817 , and then go back to sleep to save power. This cycle may continue, for example, as long as the performance is above a predetermined threshold.

The process can also determine whether the vehicle is in a location that is suitable for deployment. This could be based on an absolute location (e.g. on a street side) or based on a relative location (e.g. many surrounding vehicles), even if the vehicle is in a garage.

Even if the vehicle lacks a specific rare segment, or if there are currently no segments for a particular distribution, the process may define an activation strategy for a vehicle 809 as long as the vehicle needs or has data to share. For example, the vehicle can be activated at predefined intervals or at certain times of the day 811 and display available segments 813 (or received requests for it). At the same time or at different intervals, the process can also request missing segments from passing or locally parked vehicles 815 , By allowing the vehicle to function effectively as a roadside transmission in this way, the distribution can continue even when the owner is not on the vehicle.

Although exemplary embodiments have been described above, these embodiments are not intended to describe all possible forms of the invention. Rather, the terms used in the description are descriptive and not restrictive, and it is to be understood that various changes can be made without departing from the spirit and scope of the disclosure. In addition, the features of different embodiments can be combined in a logical manner for implementation in order to form situation-appropriate variations of the embodiments described here.

According to the present invention, there is provided a system comprising a processor configured to receive a plurality of reports that identify a file segment distribution to reporting vehicles; Determining reseed file segments to improve the distribution characteristics in response to the reports; Determining a plurality of possible delivery vehicles; and in response to determining that a distribution threshold has been reached, sending the reseed file segments to the particular delivery vehicles.

In one embodiment, the reports identify which segments were received by each of the reporting vehicles.

In one embodiment, the reports identify when a segment was received by a reporting vehicle.

In one embodiment, determining reseed file segments includes identifying a file segment for which the reporting indicates a distribution below a predefined threshold.

According to one embodiment, determining reseed file segments includes identifying all file segments if the reporting indicates a distribution below a predefined threshold.

According to one embodiment, the threshold value is a time-based threshold value and the distribution below the threshold value indicates a combined distribution of segments with a volume below a predefined volume over a predefined period of time.

In one embodiment, the threshold is a geographically based threshold and the subthreshold distribution indicates a volume of files below the threshold over a predefined portion of a predefined geographic region.

In one embodiment, the threshold is a geographically based threshold and the subthreshold distribution indicates a volume of files below the threshold over a predefined portion of a predefined geographic region.

According to one embodiment, the processor is configured to determine the plurality of possible vehicles based on a reason associated with a need for reseeding, the possible vehicles having previous driving patterns that are predefined to compensate for the reason.

According to the present invention, there is provided a system comprising a processor configured to determine a plurality of vehicles located within a predefined region and corresponding to one or more predefined thresholds for seed characteristics associated with the region; Setting the threshold values for the characteristics in order to achieve a group size of the plurality of vehicles within a predefined group size range; and in response to the group size being within the size range, providing file segments representing portions of completed update files for each of the plurality of vehicles.

In one embodiment, the vehicle that is within the region includes a determination that the vehicle is currently within the predefined region.

In one embodiment, the vehicle located within the region includes a determination that the vehicle has previously spent more than a certain amount of time within the predefined region.

According to one embodiment, the processor is configured to provide the segments with the same frequency, but at random, to the vehicles.

In one embodiment, the processor is configured to provide the segments according to a strategy that takes into account each of the anticipated driving habits of the plurality of vehicles.

In accordance with the present invention, a computer-implemented method in response to detecting a vehicle ignition off, includes determining whether the vehicle has a file segment that has a predefined preferred distribution characteristic; in response to determining that the vehicle owns the file segment, placing the vehicle in a low power state, the vehicle being able to receive requests for the file segment; and responding to the requests for the file segment by providing the file segment until a vehicle performance condition reaches a predefined threshold.

In one embodiment, the predefined distribution characteristic is identified by a server that is remote from the vehicle and is received by the vehicle from the server.

According to one embodiment, the above invention is further characterized by regularly activating the vehicle at predefined time intervals and responding to requests received during an activated period by providing file segments that belong to the vehicle and are requested by the requests in response to that Determine that the vehicle is missing the file segment.

According to one embodiment, the above invention is further characterized by regularly activating the vehicle at predefined intervals and sending a request for the missing file segment in response to determining that the vehicle is missing a file segment to complete a file.

In one embodiment, the above invention is further characterized by displaying the file segment as available for transmission.

In one embodiment, placing the vehicle in the low power state also occurs in response to determining that the vehicle is in a location that is predefined as suitable for distribution.

Claims (15)

System comprising: a processor configured to: Receiving a plurality of reports identifying a file segment distribution to reporting vehicles; Determining reseed file segments to improve the distribution characteristics in response to the reports; Determining a plurality of possible delivery vehicles; and in response to determining that a distribution threshold has been reached, sending the reseed file segments to the particular delivery vehicles. System according to Claim 1 The reports identify which segments were received by each of the reporting vehicles. System according to Claim 1 where the reports identify when a segment was received by a reporting vehicle. System according to Claim 1 , wherein determining reseed file segments includes identifying a file segment for which reporting indicates a distribution below a predefined threshold. System according to Claim 1 , wherein determining reseed file segments includes identifying all file segments if the reporting indicates a distribution below a predefined threshold. System according to Claim 5 , wherein the threshold value is a time-based threshold value and the distribution below the threshold value indicates a combined spread of segments with a volume below a predefined volume over a predefined period of time. System according to Claim 5 , wherein the threshold is a geographically based threshold and the sub-threshold distribution indicates a volume of files below the threshold over a predefined portion of a predefined geographic region. System according to Claim 5 , wherein the threshold is a geographically based threshold and the sub-threshold distribution indicates a volume of files below the threshold over a predefined portion of a predefined geographic region. System according to Claim 1 wherein the processor is configured to determine the plurality of possible vehicles based on a reason associated with a need for reseeding, the possible vehicles having previous driving patterns that are predefined to compensate for the reason. System comprising: a processor configured to: Determining a plurality of vehicles located within a predefined region and corresponding to one or more predefined thresholds for seed characteristics associated with the region; Setting the threshold values for the characteristics in order to achieve a group size of the plurality of vehicles within a predefined group size range; and in response to the group size being within the size range, providing file segments representing portions of completed update files for each of the plurality of vehicles. System according to Claim 10 , wherein the vehicle that is within the region includes a determination that the vehicle is currently within the predefined region. System according to Claim 10 wherein the vehicle located within the region includes a determination that the vehicle has previously spent more than a certain amount of time within the predefined region. System according to Claim 10 , wherein the processor is configured to provide the segments with the same frequency, but at random, to the vehicles. System according to Claim 10 wherein the processor is configured to provide the segments according to a strategy that takes into account each of the anticipated driving habits of the plurality of vehicles. A computer-implemented method comprising: in response to the detection of a switched-off vehicle ignition, determining whether the vehicle has a file segment that has a predefined preferred distribution characteristic, in response to determining that the vehicle owns the file segment, placing the vehicle in a low power state, the vehicle being able to receive requests for the file segment; and Respond to the requests for the file segment by providing the file segment until a vehicle performance condition reaches a predefined threshold.

Images