Secure border area communication system and method - Patents.com
The method and system for secure vehicular data transfer address the challenge of securing communications by dynamically allocating zones based on file size, transfer rate, and vehicle speed, ensuring secure and efficient data transfer.
Patent Information
- Application Number
- JP2022577196
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-06-15
- Filing Date
- 2021-06-14
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2041-06-14
AI Technical Summary
The challenge in connected vehicle technology is securing vehicular communications from attacks and ensuring privacy in dynamic and potentially hostile environments, such as moving vehicles with sporadic connectivity and exposure to hackers.
A method and system for secure data transfer in vehicles that involves determining file size and transfer rate, predicting vehicle mileage, and dynamically allocating or creating secure data transfer zones based on vehicle speed and route to ensure secure communication.
Ensures secure and efficient data transfer by dynamically adjusting communication zones to accommodate transfer requirements, enhancing security and privacy in vehicular communications.
Smart Images

Figure 0007583837000005 
Figure 0007583837000006 
Figure 0007583837000007
Abstract
Description
[Technical field]
[0001] The present disclosure relates generally to secure communications, and in particular, some implementations may relate to secure data transfer within a geofenced area. [Background technology]
[0002] Connected vehicle technology is growing in importance and demand seemingly exponentially as autonomous vehicles and ADAS technologies play an increasing role in vehicle operation. Vehicle-to-Vehicle (V2V) and Vehicle-to-Infrastructure (V2I) wireless communications (collectively referred to as V2X) enable vehicles to communicate with each other and with infrastructure elements (e.g. road signs, smart highway elements, etc.).
[0003] A key aspect for the successful deployment of vehicular communications is the security of the communications. For example, these potentially life-critical communications must be secured against attacks or tampering by hackers, and personal information must be protected as well. However, implementing security measures can be challenging in the vehicle's particular operating environment (e.g., moving vehicle, sporadic connectivity, exposure to potential hackers in the vicinity, etc.). Summary of the Invention
[0004] According to various embodiments of the disclosed technology, a method for secure data transfer with a vehicle may include determining a size of a file to be transferred to or from the vehicle; determining a data transfer rate at which the file may be transferred; determining a vehicle mileage required to complete the transfer of the file based on the file size and the transfer rate; and assigning a secure data transfer zone in which to perform the transfer based on the determined mileage and based on the size of the secure data transfer zone.
[0005] In various embodiments, allocating the secure data transfer zone may include identifying an existing secure data transfer zone of sufficient size to conduct the transfer and allocating the identified secure data transfer zone for conducting the transfer. In embodiments, allocating the secure data transfer zone may include identifying an existing secure data transfer zone for conducting the transfer, dynamically modifying boundaries of the identified secure data transfer zone to accommodate a determined mileage for the transfer, and allocating the identified secure data transfer zone for the transfer.
[0006] The assigned secure data transfer zone may include multiple secure data transfer zones of sufficient cumulative size to effect the transfer.
[0007] The method may further include adjusting boundaries of one or more of the plurality of secure data transfer zones such that the plurality of secure data transfer zones constitute a cumulative size sufficient to accommodate the determined mileage.
[0008] Allocating the secure data transfer zone may include creating a new secure data transfer zone or multiple new secure data transfer zones of a size sufficient to accommodate the determined mileage.
[0009] The method may further include predicting a speed of the vehicle while traveling through the assigned secure data transfer zone and further determining a vehicle distance required to complete the transfer of the file using the predicted vehicle speed. The method may further include predicting a path of the vehicle and determining one or more available secure data transfer zones within the predicted path of the vehicle, and allocating the secure data transfer zone may include allocating one or more of the one or more available secure data transfer zones.
[0010] In various embodiments, the one or more available secure data transfer zones include one or more existing secure data transfer zones, one or more dynamically created secure data transfer zones, or a combination of at least one existing secure data transfer zone and at least one dynamically created secure data transfer zone.
[0011] In various embodiments, predicting the vehicle's path is performed using machine learning.
[0012] A non-transitory machine-readable medium has stored therein instructions that, when executed by the processor, cause the processor to perform operations that may include: determining a size of a file to be transferred to or from the vehicle; determining a data transfer rate at which the file may be transferred; determining a vehicle mileage required to complete the transfer of the file based on the file size and the transfer rate; and assigning a secure data transfer zone in which to perform the transfer based on the determined mileage and based on the size of the secure data transfer zone.
[0013] A system for secure vehicular communications may include: a processor; and a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to perform operations, which may include: determining a size of a file to be transferred to or from the vehicle; determining a data transfer rate at which the file may be transferred; determining a vehicle mileage required to complete the transfer of the file based on the file size and the transfer rate; and assigning a secure data transfer zone in which to perform the transfer based on the determined mileage and based on the size of the secure data transfer zone.
[0014] In various embodiments, allocating the secure data transfer zone may include identifying an existing secure data transfer zone of sufficient size to conduct the transfer and allocating the identified secure data transfer zone for conducting the transfer. In embodiments, allocating the secure data transfer zone may include identifying an existing secure data transfer zone for conducting the transfer, dynamically modifying boundaries of the identified secure data transfer zone to accommodate a determined mileage for the transfer, and allocating the identified secure data transfer zone for the transfer.
[0015] The assigned secure data transfer zone may include multiple secure data transfer zones of sufficient cumulative size to effect the transfer.
[0016] The operations may further include adjusting boundaries of one or more of the plurality of secure data transfer zones such that the plurality of secure data transfer zones constitute a cumulative size sufficient to accommodate the determined mileage.
[0017] Allocating the secure data transfer zone may include creating a new secure data transfer zone or multiple new secure data transfer zones of a size sufficient to accommodate the determined mileage.
[0018] The operations may further include predicting a speed of the vehicle while traveling through the assigned secure data transfer zone and further determining a vehicle distance required to complete the transfer of the file using the predicted vehicle speed. The method may further include predicting a path of the vehicle and determining one or more available secure data transfer zones within the predicted path of the vehicle, and allocating the secure data transfer zone may include allocating one or more of the one or more available secure data transfer zones.
[0019] In various embodiments, the one or more available secure data transfer zones include one or more existing secure data transfer zones, one or more dynamically created secure data transfer zones, or a combination of at least one existing secure data transfer zone and at least one dynamically created secure data transfer zone.
[0020] In various embodiments, predicting the vehicle's path is performed using machine learning.
[0021] Other features and aspects of the disclosed technology will become apparent from consideration of the following detailed description in conjunction with the accompanying drawings which illustrate, by way of example, features of embodiments of the disclosed technology. The Abstract is not intended to limit the scope of any inventions described herein, which are defined solely by the claims appended hereto.
[0022] The present disclosure, in accordance with one or more various embodiments, will now be described in detail with reference to the following figures, which are provided for illustrative purposes only and which merely depict typical or exemplary embodiments. [Brief description of the drawings]
[0023] [Figure 1] FIG. 1 illustrates an exemplary autonomous or semi-autonomous vehicle that may implement embodiments of the disclosed subject technology. [Diagram 2] FIG. 1 illustrates an example of secure border area communication according to various embodiments. [Diagram 3] 1 is a diagram illustrating an example process for secure border area communication according to one embodiment. [Figure 4] 1 is a diagram illustrating another exemplary process for secure file transfer according to various embodiments. [Diagram 5] FIG. 2 illustrates exemplary computing components that may be used to implement various features of the embodiments described in this disclosure.
[0024] The figures are not exhaustive and are not intended to limit the disclosure to the precise forms disclosed. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0025] The embodiments of the systems and methods disclosed herein provide a system and method for coordinating secure vehicle communications with one or more secure communication zones. The embodiments may be configured to recognize that secure information must be uploaded or downloaded from the vehicle and work to schedule the transfer. The system can be configured to determine the size of the file to be transferred to or from the vehicle and the data transfer rate at which the file may be transferred. Using this information and the predicted vehicle speed, the system can determine the vehicle mileage required to complete the transfer of the file. Using this information, the system can assign one or more secure data transfer zones within which to perform the transfer based on the determined mileage and based on the size of the secure data transfer zone or zones.
[0026] If the dimensions of an existing secure communications zone are insufficient to accommodate the transfer (e.g., if a vehicle passes through a zone too quickly to complete the transfer), the system can dynamically add one or more new secure communications zones, or dynamically increase the dimensions of one or more existing secure communications zones, or both, to accommodate the transfer.
[0027] The systems and methods disclosed herein can be implemented in any of many different vehicles and vehicle types, including autonomous or semi-autonomous vehicles. For example, the systems and methods disclosed herein can be used in cars, trucks, motorcycles, recreational vehicles, and other similar on-road or off-road vehicles. These can include vehicles for transporting personnel / personnel, materials, or other items. Additionally, the principles disclosed herein can be extended to other vehicle types as well.
[0028] FIG. 1 illustrates an exemplary autonomous or semi-autonomous vehicle in which embodiments of the disclosed technology can be implemented. In this example, vehicle 100 includes computing system 110, sensors 120, AV control system 130, and vehicle system 140. Vehicle 100 may include more or fewer systems and subsystems, each of which could include multiple elements. Thus, one or more of the functions of the technology disclosed herein may be divided into additional functional or physical components or combined into a fewer number of functional or physical components. Additionally, although the systems and subsystems illustrated in FIG. 1 are shown as partitioned in a particular manner, the functions of vehicle 100 may be partitioned in other ways. For example, various vehicle systems and subsystems may be combined in different ways to share functionality.
[0029] The sensors 120 may include multiple different sensors for collecting data about the vehicle 100, its operator, its operation, and its surrounding environment. In this example, the sensors 120 include a lidar 111, a radar 112, or other similar distance measuring sensor, an image sensor 113, a throttle and brake sensor 114, a 3D accelerometer 115, a steering sensor 116, and a GPS or other vehicle positioning system 117. One or more of the sensors 120 may collect data and send the data to the vehicle's ECU or other processing unit. The sensors 120 (and other vehicle components) may be duplicated for redundancy.
[0030] Distance measuring sensors, such as lidar 111, radar 112, IR sensors, and other similar sensors, can be used to collect data to measure distances and approach speeds to various external objects, such as other vehicles, traffic signs, pedestrians, light poles, and other objects. Image sensor 113 can include one or more cameras or other image sensors to capture images of the environment around the vehicle as well as the interior of the vehicle. Information from image sensor 113 can be used to determine information about the environment surrounding vehicle 100, including, for example, information about other objects surrounding vehicle 100. For example, image sensor 113 can recognize landmarks or other features (including, for example, road signs, traffic lights, etc.), road gradients, lines on the road, curbs, objects to avoid (e.g., other vehicles, pedestrians, cyclists, etc.), and other landmarks or features. Information from image sensor 113 can be used in conjunction with other information, such as map data or information from positioning system 117, to determine, refine, or confirm the location of the vehicle.
[0031] The throttle and brake sensors 114 can be used to collect data regarding the application of throttle and brake by a human or autonomous operator. The accelerometers 115 include 3D accelerometers to measure the roll, pitch and yaw of the vehicle. The accelerometers 115 can include any combination of accelerometers and gyroscopes for the vehicle or any of a number of systems or subsystems within the vehicle for the purpose of sensing inertial based changes in position and orientation.
[0032] A steering sensor 116 (e.g., a steering angle sensor) can be included to collect data regarding steering inputs for the vehicle by a human or autonomous operator. The steering sensor may include a position encoder to monitor the angle of the steering input in degrees. An analog sensor can collect a voltage difference that can be used to determine information about the angle and direction of rotation, while a digital sensor can detect the angle of the steering input using an LED or other light source. The steering sensor can also provide information about how fast the steering wheel is being turned. A steering wheel being turned quickly is generally normal while the vehicle is operating at low speeds, but is generally unusual at highway driving speeds. If the driver is turning the steering wheel at a high rate while driving at highway speeds, the vehicle's computing system may interpret it as an indication that the vehicle is out of control. The steering sensor 116 can also include a steering torque sensor to detect the amount of force the driver is applying to the steering wheel.
[0033] A vehicle positioning system 117 (eg, a GPS or other positioning system) may be used to gather position information about the vehicle's current location as well as other positioning or navigation information.
[0034] Although not illustrated, other sensors 120 may also be included. Various sensors 120 may be used to provide input to the computing system 110 and other systems of the vehicle 100 so that the system has information useful for operating in an autonomous, semi-autonomous, or manual mode.
[0035] AV control system 130 may include a number of different systems / subsystems for purposes of controlling the operation of vehicle 100. In this example, AV control system 130 includes a steering unit 136, a throttle and brake control unit 135, a sensor fusion module 131, a computer vision module 134, a pathing module 138, and an obstacle avoidance module 139. Sensor fusion module 131 may be included to evaluate data from multiple sensors, including sensor 120. Sensor fusion module 131 may use computing system 110 or its own computing system to execute algorithms to assess inputs from the various sensors.
[0036] The throttle and brake control unit 135 can be used to control activation of the vehicle's throttle and braking mechanisms to accelerate, decelerate, stop, or otherwise regulate the speed of the vehicle. For example, the throttle unit can control the operating speed of an engine or motor used to provide motive power for the vehicle. Similarly, the brake unit can be used to activate brakes (e.g., disc, drum, etc.) or engage regenerative braking (e.g., in hybrid or electric vehicles) to slow or stop the vehicle.
[0037] The steering unit 136 may include any of a number of different mechanisms for controlling or altering the direction of travel of the vehicle. For example, the steering unit 136 may include a suitable control mechanism for adjusting the orientation of the vehicle's front or rear wheels to accomplish changes in direction of the vehicle during operation. Electronic, hydraulic, mechanical, or other steering mechanisms may be controlled by the steering unit 136.
[0038] A computer vision module 134 can be included to process image data (e.g., image data captured from the image sensor 113 or other image data) for purposes of evaluating the interior of the vehicle or the environment surrounding the vehicle. For example, algorithms operating as part of the computer vision module 134 can evaluate still or moving imagery to determine features and landmarks (e.g., road signs, traffic lights, lane markings and other road boundaries, etc.), obstacles (e.g., pedestrians, bicyclists, other vehicles, other obstacles in the path of the subject vehicle), and other objects. The system can include video tracking and other algorithms to recognize such objects, estimate their speed, map the surroundings, etc.
[0039] A routing module 138 may be included to calculate a desired path for the vehicle 100 based on inputs from various other sensors and systems. For example, the routing module 138 may use information from the positioning system 117, the sensor fusion module 131, the computer vision module 134, the obstacle avoidance module 139 (described below), and other systems to navigate the vehicle along a segment of a desired route. The routing module 138 may similarly be configured to dynamically update the path of the vehicle as it receives real-time information from the sensors 120 and other control systems 130.
[0040] An obstacle avoidance module 139 may be included to determine the control inputs required to avoid obstacles detected by the sensors 120 or the AV control system 130. The obstacle avoidance module 139 may work in conjunction with the routing module 138 to determine an appropriate path to avoid the detected obstacles.
[0041] Vehicle systems 140 may include a number of different systems / subsystems to control the operation of vehicle 100. In this example, AV control system 130 includes steering system 121, throttle system 122, brakes 123, transmission 124, electronic control unit (ECU) 125, and propulsion system 126. These vehicle systems 140 may be controlled by AV control system 130 in autonomous, semi-autonomous, or manual modes. For example, in autonomous or semi-autonomous modes, AV control system 130, alone or in conjunction with other systems, may control vehicle systems 140 to operate the vehicle fully autonomously or semi-autonomously. This also includes assisted modes in which the vehicle assumes partial control or activates ADAS controls to assist the driver in operating the vehicle.
[0042] The computing system 110 in the illustrated example includes a processor 106 and a memory 103. Some or all of the functionality of the vehicle 100 may be controlled by the computing system 110. The processor 106 may include one or more GPUs, CPUs, microprocessors, or any other suitable processing system. The processor 106 may include one or more single-core or multi-core processors. The processor 106 executes instructions 108 stored in a non-transitory computer-readable medium, such as the memory 103.
[0043] Memory 103 may store instructions (e.g., program logic) that processor 106 may execute to perform various functions of vehicle 100, including those of the vehicle systems and subsystems. Memory 103 may store additional instructions as well, including instructions for transmitting data to, receiving data from, interacting with, and / or controlling one or more of sensors 120, AV control system 130, and vehicle systems 140. In addition to instructions, memory 103 may store data and other information used by the vehicle and its systems and subsystems for operation, including operation of vehicle 100 in an autonomous, semi-autonomous, or manual mode.
[0044] 1, one computing system 110 is illustrated, in various embodiments, multiple computing systems 110 may be included. Additionally, one or more systems and subsystems of vehicle 100 may include their own dedicated or shared computing system 110, or variations thereof. Thus, while computing 110 is illustrated as a separate system, this is merely for ease of illustration and computing system 110 may be distributed among various vehicle systems or subsystems.
[0045] Vehicle 100 may also include a wireless communication system (not shown) for communicating with other vehicles, infrastructure elements, cloud components, and other external entities using any of a number of communication protocols, including, for example, V2V, V2I, and V2X protocols. Such a wireless communication system may enable vehicle 100 to receive information from other objects, including, for example, map data, data regarding infrastructure elements, data regarding the operation and intent of surrounding vehicles, and the like. The wireless communication system may also enable vehicle 100 to transmit information to other objects. In some applications, the computational functions for the various embodiments disclosed herein may be performed entirely on computing system 110, distributed among two or more computing systems 110 of vehicle 100, performed on a cloud-based platform, performed on an edge-based platform, or a combination of the above.
[0046] The example of Figure 1 is provided for illustrative purposes only as one example of a vehicle system in which embodiments of the disclosed technology may be implemented, and upon reading this description, one of ordinary skill in the art will understand how the disclosed embodiments may be implemented in this and other vehicle platforms.
[0047] Figure 2 shows an example of secure boundary area communications according to various embodiments. Referring now to Figure 2, the example illustrates three different types of mobile communication platforms: a tractor trailer 222, a passenger vehicle 224, and a mobile device 226, such as a smart watch or smartphone worn by a cyclist, stroller, or other pedestrian. Each platform may be in communication with each other and with infrastructure elements (e.g., V2V, V2P, and V2I, not shown), and with one or more wireless networks 232.
[0048] These and other vehicles may communicate information over the wireless network 232 for a variety of reasons, including, for example, to receive map updates, navigation assistance, and perform other mobility management functions; to communicate through Lexus®, Enform®, Toyota®, Safety Connect®, and others to provide communications related to concierge services such as automatic crash notification, SOS assistance, stolen vehicle location, and towing services; to enable commerce-related applications including shopping and toll booths while driving; to communicate information for maintenance tracking and breakdown prevention (e.g., to share data with back-end algorithms that can predict failures or identify the need for service); to provide entertainment features; to provide driver assistance for partially or fully automated driving and ADAS; and to communicate information to enhance or ensure driver / occupant wellness.
[0049] Some of the above and other communications may involve secure or otherwise sensitive data. This may include personal information about the driver and passengers, such as health-related data, banking or payment information, and other personal information. This may also include information related to the autonomous or semi-autonomous operation of the vehicle. Thus, in many instances, it may be desirable to provide a secure communication channel for this and other sensitive information.
[0050] The illustrative scenario in FIG. 2 shows an example of a secure communication zone 252 whose boundaries are depicted with dashed lines. Although vehicles may in many instances communicate with other vehicles outside these boundaries, it may be desired that secure communication occur only within the balance of the secure communication zone 252. In some applications, the secure communication zone 252 may be a geofenced area and may be defined as having a fixed size and a fixed location, while in other applications, the size and location of one or more secure communication areas may be dynamic, thus allowing either or both of the size and location to change depending on the needs of secure communication. The secure communication zone 252 may be constrained based on the availability of secure network channels, which may be defined, for example, by the communication capabilities (e.g., encryption capabilities, availability of secure channels, etc.) of the equipment that constitutes that portion of the network. It is contemplated that other factors may also constrain the boundaries and locations of one or more secure communication zones 252.
[0051] The example of Figure 2 also illustrates a back-end server, such as a cloud server, or other computing device that may be used to coordinate secure communications for various vehicles. For simplicity, the computing power in this example is depicted as a single secure communication boundary area computing system 240 located in the cloud. Although depicted and described as a single network device, the computing system may be located on the vehicle or may be implemented using edge computing, for example, distributed across multiple vehicles. Similarly, the functionality of the secure communication boundary area communications system 240 may be distributed among one or more vehicles and one or more servers.
[0052] The secure communication boundary area computing system 240 in this example includes a communication circuit 241 and a decision circuit 243 (which in this example includes a processor 246 and a memory 248). The components of the secure communication boundary area computing system 240 are illustrated as communicating with each other via a data bus, although other communications within an interface may also be included.
[0053] The processor 246 may include one or more GPUs, CPUs, microprocessors, or any other suitable processing systems. The processor 246 may include single-core or multi-core processors. The memory 248 may include one or more various forms of memory or data storage (e.g., flash, RAM, etc.) that may be used to store calibration parameters, images (analysis or history), point parameters, instructions and variables, and any other suitable information for the processor 246. The memory 248 may be comprised of one or more modules of one or more different types of memory and may be configured to store data and other information as well as operational instructions that the processor 246 may use for the secure communication boundary area computing system 240.
[0054] 2 is illustrated with a processor and memory circuitry, as described below with respect to the circuitry disclosed herein, the decision circuitry 203 may be implemented utilizing any form of circuitry including, for example, hardware, software, or a combination thereof. As a further example, one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logic components, software routines, or other mechanisms could be implemented to configure the secure communication boundary area computing system 240.
[0055] The communication circuitry 241 includes a wireless transceiver circuitry 242 with an associated antenna 214, and a wired I / O interface 244 with an associated hardwired data port (not shown). As this example illustrates, communication with the secure communication boundary area computing system 240 may include either or both of the wired and wireless communication circuitry 241. The wireless transceiver circuitry 242 may include a transmitter and receiver (not shown) to enable wireless communication via any of a number of communication protocols, whether standard, proprietary, open, point-to-point, networked or otherwise. An antenna 214 is coupled to the wireless transceiver circuitry 242 and is used by the wireless transceiver circuitry 242 to wirelessly transmit wireless signals to connected wireless equipment and receive wireless signals as well. These RF signals may include nearly any type of information that may be transmitted by the secure communication boundary area computing system 240 to or received from other entities, such as the sensors 152 and the vehicle systems 158.
[0056] The wired I / O interface 244 may include a transmitter and receiver (not shown) for hardwired communication with other devices. For example, the wired I / O interface 244 may provide a hardwired interface to other components including the sensors 152 and vehicle systems 158. The wired I / O interface 244 may communicate with other devices using Ethernet or any of a number of wired communication protocols, whether standard, proprietary, open, point-to-point, networked, or otherwise.
[0057] During operation, the secure communications boundary area computing system 240 can receive information from various vehicle systems and sensors to determine parameters that may be useful for regulating secure data transfers. These parameters may include, for example, information regarding data to be uploaded from or downloaded to the vehicle (e.g., data type, file size, etc.), security requirement information for uploading or downloading such data, vehicle type information, vehicle speed and direction of travel, and other information.
[0058] The secure communication boundary area computing system 240 may also be configured to receive and store information regarding one or more secure communication zones 252. This may include, for example, information about these areas, such as geofence boundaries; secure communication capabilities within the secure communication zone 252; speed limits, average speeds or other speed information within the boundaries of the secure communication zone 252; and the like.
[0059] The instructions in memory 248 may be configured to cause boundary area computing system 242 to perform steps to coordinate a secure data transfer. This may include, for example, determining that a secure data transfer is needed or desired for a given vehicle, determining the size of the file to be uploaded or downloaded for the secure data transfer, determining the level of security required for the transfer, determining vehicle parameters of the subject vehicle (e.g., speed, direction of travel, and route along which the vehicle is intended to travel), determining the distance required to complete the transfer based on the file size and vehicle speed, and allocating a secure file transfer area based on the distance required. In some embodiments, the secure file transfer area may be dynamically defined in real time (e.g., on the fly) as communication requirements are determined. In other embodiments, the secure transfer may be scheduled to occur during one or more upcoming secure communication zones 252 along the vehicle's predicted route.
[0060] The example of FIG. 2 also illustrates the use of codes to aid in vehicle classification. The illustrated example includes three codes, Code A, Code B, and Code C. In this example, Code A is assigned to a tractor trailer 222, Code B is assigned to a passenger vehicle 224, and Code C is assigned to a mobile device 226. These codes can be used, for example, to identify a type or class of vehicle. Although three different classes are shown, any of many different classes can be utilized. Moreover, higher levels of granularity can be used beyond the three levels depicted here. For example, different passenger vehicle types can be assigned different codes (e.g., sports car, compact sedan, large sedan, crossover, large SUV, pickup truck, economy vehicle, luxury car, etc.).
[0061] In various embodiments, each code can be associated with a number of vehicle parameters that typically apply to the vehicle class or type represented by the code. For example, a vehicle in code A can be identified as a tractor trailer, defined as traveling within a certain speed window on certain road types, identified as following a certain route (which can be useful when proper navigation system or other routing information is not available), and so on. Thus, in some embodiments, the secure communication boundary area computing system 240 can simply receive the vehicle's code along with the secure data transfer requirements and make a decision based on the information associated with the vehicle type or class in the code. This can reduce data transfer requirements, for example by avoiding the need to send additional information about vehicle speed. In some embodiments, the vehicle can be configured to recognize whether it is performing within the parameters defined for its type or class, and if not, provide additional information to the secure communication boundary area computing system 240 so that the secure communication boundary area computing system 240 has accurate information.
[0062] As a further example, the code can be used to define other parameters / capabilities of the coded vehicle. For example, the code can identify the type of information the vehicle may have. Continuing with this example, if a semi-trailer is identified, the additional information could include payload information (e.g., hazardous or perishable goods, or a particular type of payload), payload weight, gross vehicle weight, gross vehicle weight rating (GVWR), origin and destination, hours on the road, special license information, etc. The code can also define the communication capabilities of the type or class of vehicle. For example, some vehicle classes may have higher bandwidth communication capabilities or needs, while other vehicle classes may have lower bandwidth capabilities or needs. Thus, the code can be used to determine what data or data types can be transferred and how much data the system should expect to be able to transfer.
[0063] FIG. 3 is a diagram illustrating an exemplary process for secure boundary area communication according to one embodiment. Referring now to FIG. 3, in operation 312, a secure communication system (e.g., secure communication boundary area computing system 240) determines that a secure file needs to be uploaded from or downloaded to the vehicle. The secure communication system may be, for example, part of another infrastructure facility that may otherwise be in communication with the vehicle. This determination may be made based on communication with the vehicle. For example, during communication, the vehicle may indicate that it has a secure communication requirement (e.g., upload or download) that needs to be met. As another example, the secure communication requirement may be scheduled in advance, for example, based on a known requirement or as part of a scheduled periodic event.
[0064] In operation 314, the secure communications system determines the size of the file or files to be transferred (e.g., uploaded or downloaded) between the vehicle and another means. If the vehicle has a file or files to upload, it can provide file size information to the secure communications system, which can include, for example, the number of bytes to be transferred.
[0065] In operation 314, the secure communication system determines vehicle parameters. These may include any of a number of parameters that may be useful in determining the amount of time or distance required to complete a subject secure file transfer. As noted above, in some embodiments, some or all of these parameters may be predefined or tied to a particular vehicle code (e.g., Code A, Code B, Code C, as described above in FIG. 2). In other embodiments, some or all of these parameters may be uploaded to the secure communication system by the vehicle. Vehicle speed is one example of a parameter that may be used to determine the amount of distance required to complete a subject secure file transfer. If a secure communication area is defined or created within the system along certain areas of the vehicle's route, the speed limits of one or more road segments within the secure communication area may be used to inform the prediction regarding the vehicle's speed through the secure communication area.
[0066] The speed limit information can be combined with collected driver behavior information to provide accurate speed predictions through the secure communication area. For example, if historical driver information indicates that a driver has a tendency to operate the vehicle at speeds 6-10 mph over the speed limit, the system will assume that the driver will also exceed the speed limit by a similar amount when maneuvering the vehicle through the secure communication area.
[0067] It is contemplated that precise speed predictions may also be made based on crowdsourced data. For example, if data from multiple vehicles indicates that vehicles tend to drive within a particular speed range through a given area, this information can be used to precisely predict vehicle speeds in that area. Further to this example, crowdsourced data may indicate that drivers tend to operate their vehicles faster on sustained downhill sections and slower on sustained uphill sections. Thus, average speeds or speed envelopes (e.g., based on a Gaussian distribution of speeds) on particular road segments (e.g., uphill and downhill segments) may be used to inform speed predictions.
[0068] Other information can be used to inform the system's prediction of vehicle speeds through the secure communication area. For example, road construction, inclement weather, current road obstructions, the presence of the highway patrol, or other factors could be information the system could use to reduce the system's predicted vehicle speed. Similarly, the presence of special events such as concerts, sporting events, graduations, etc. could be used to inform the prediction. Additionally, variations in traffic volume over time could be used to inform the vehicle speed prediction.
[0069] Another vehicle parameter that the secure communication system can collect is routing information or direction of travel. Direction of travel can be used by the secure signage system to determine whether the vehicle is heading towards one or more defined secure communication areas (e.g., secure communication zone 252). Routing information can provide more definitive information than direction of travel and can be used to identify one or more secure communication areas along a precise route identified by the vehicle. To the extent that routing information changes, the vehicle can provide updated routing information to the secure adjudication system so that the identification of the secure communication area can be updated according to the new route as well. Routing information can be provided, for example, by the vehicle's navigation system or navigation app.
[0070] In operation 318, the system uses the file size and the predicted vehicle speed to determine the distance required to complete the file transfer. For example, if it is known how much time is required to transfer a target amount of data, the system can multiply this time by the vehicle speed to determine the distance required for the transfer according to the following equation:
number
number
[0071] Combining these two equations, we get:
number
[0072] The system may be configured to provide distance mitigation measures if the vehicle is actually traveling through the secure communication area faster than predicted.
[0073] In operation 320, the secure communications system allocates a secure communications area for the subject data transfer. For example, the allocation may be based on the distance required to complete the subject transfer (e.g., as calculated above) and the distance spanned by one or more available secure communications areas along or in the direction of travel of the route the subject vehicle is to travel. In some applications, the system may allocate multiple secure communications areas when one area is not sufficient to communicate the amount of data scheduled for transfer.
[0074] In some embodiments, the allocation may be based on one or more available secure communication areas that pre-exist and may be located along the vehicle's projected travel path. It is contemplated that the allocation may be made without adjusting the boundaries of these geofenced areas, either because the secure communication areas are fixed and cannot be redefined, or because the secure transfer may fit well within one or more of these areas.
[0075] In other embodiments, the establishment or sizing of the secure communication area may be dynamic to accommodate different securely transferred data volumes. As an example, a secure communication area may be established to accommodate a secure transfer, which may be useful in situations where one or more secure communication areas are not otherwise available to complete the data transfer in time. As another example, an existing secure communication area may be adapted to increase its perimeter (e.g., extend it along the direction of the roadway) to provide a greater driving distance over which secure communication can occur. Thus, the system and method may be implemented to adapt availability, location, and size to accommodate data transfer.
[0076] Adaptation is not limited to increasing the availability of a secure communication zone, but can also be used to decrease availability when secure communication requirements become less. For example, the system can be configured to abolish or disable (temporarily or permanently) a secure communication zone when there are no pending or expected secure transfers. As another example, the system can be configured to shrink the secure communication zone when the amount of secure transfers is low. It is contemplated that decreasing the availability of a secure communication zone can be beneficial, for example, when communication resources are expensive or in high demand for other uses.
[0077] As noted above, a secure communication area may be defined by the level of security provided for data transfer within that zone. For example, in some applications, the level of security provided may be such that it requires unlimited (or limited) validity public key certificates. As another example, in some applications, the level of security provided may require private key encryption. As a further example, some applications may provide a higher level of security that provides both encryption as well as a higher level of hardware security. A higher level of hardware security could include, for example, physical site security for the equipment that constitutes all or part of the network, tamper-resistant or tamper-evident enclosures, fiber optic communication links, and the like.
[0078] In some embodiments, the system may be configured to predict the routing or future positioning of the vehicle beyond the current route. Machine learning techniques may be implemented to allow the system to learn the behavior of vehicle types or classes, individual vehicles, or vehicle operators or occupants. For example, data may be collected for various vehicles and patterns for vehicle travel may be learned. These patterns may be used to predict the speed of the vehicle as it travels through one or more secure communication zones. These patterns may also be used to predict that the vehicle may enter the secure communication zone at a particular date and time, for example, in the evening, tomorrow or the next day, or the next week, or at some point in the future. For example, in the case of a tractor trailer, the secure communication system may learn that semi-tractors typically travel back and forth. Thus, if the secure communication zone is not large enough to accommodate secure data transfer during the outbound leg, the system may be configured to initiate secure data transfer when the vehicle enters the geofenced secure communication zone and to stop data transfer when the vehicle exits the secure communication zone. The system may then schedule the remainder of the transfer during the return leg. The decision to add a new secure communication zone or adjust an existing one for scheduling a return trip is considered based on factors such as the predictability of the vehicle making the return leg of the trip, the expected amount of time that will elapse between the outbound and return legs, the time sensitivity of the information, etc. As another example, the system may be configured to learn other regular patterns, such as driver or vehicle commuting patterns, and use these patterns to schedule secure data transfers across multiple separate trips. Since some of this analysis may be driver or passenger or cargo based as opposed to or in addition to vehicle based, embodiments may be implemented to search for the identity of the driver, passenger or payload of the target vehicle.
[0079] 4 is a diagram illustrating another exemplary process for secure file transfer according to various embodiments. Referring now to FIG. 4, at operation 412, upon determining that a secure transfer is desired, the secure communications system determines the size of the secure file to be uploaded or downloaded during the secure transfer.
[0080] In operation 414, the secure communications system determines a transfer speed or data rate at which the secure file can be transferred. The available transfer speed may be affected by vehicle hardware limitations, data rate limitations of the network components serving the secure communications zone, actual or expected traffic volume on the network, and other factors that may affect the data transfer rate. Because the data transfer rate may be affected by the characteristics of the secure communications zone, in some embodiments the system is required to identify available secure communications transfer zones (operation 432) before determining the available data rate.
[0081] In operation 416, the secure communications system determines the speed of the subject vehicle. In some embodiments, the system may use the existing vehicle speed and assume that the vehicle will maintain this speed (or within + / - 5% or 10% of this speed or some other determined amount) in the near future. This assumption may be valid for secure communications zones close to the vehicle on similar road segments. As mentioned above, in other embodiments, the vehicle speed determined in operation 416 may be a predicted speed based on a number of factors used to estimate the speed of the subject vehicle through one or more available (or to be created) secure communications zones. In some embodiments, this may be calculated as the predicted average speed of the vehicle through the secure communications zone. A prediction of the average speed may be useful when instantaneous vehicle speed is expected to change as the vehicle travels through the security communications zone. In embodiments where the vehicle speed is predicted based on the location or arrangement of the zones, the zones may be identified (e.g., in operation 432) prior to predicting the vehicle speed.
[0082] In operation 420, based on the determined size of the secure information to be transferred (e.g., file size) and based on the available data transfer rate, the secure communications system determines the amount of time to complete the file transfer. As discussed above, this is done using the following formula:
number
[0083] In operation 434, the secure communications system estimates the distance required to complete the secure transfer. As discussed above, this is a function of the amount of time required to complete the transfer and the distance the vehicle should travel in that time based on the predicted vehicle speed. In some embodiments, the system can provide mitigation measures for the distance required to accommodate the contingency that the vehicle may travel faster than predicted through the secure communications zone.
[0084] In operation 442, the secure communication system determines whether one or more available secure communication zones will provide sufficient mileage based on the calculated distance and zone size required for the transfer. If the identified secure communication zone or zones are sufficient to accommodate the mileage required for the transfer (including, in some embodiments, with buffering), the system assigns the secure communication zone to the subject secure file transfer. The system may command the vehicle to initiate the transfer (initiate and upload or request download) upon reaching a geofence boundary of the identified secure communication zone or zones. Thus, in some embodiments, the secure communication system may download to the vehicle the boundaries for the secure communication zone or zones within which the secure transfer is to occur. In some applications, the zone boundaries and identifications may be preloaded on the vehicle, for example, during route planning or otherwise. If the zone boundaries and identifications are preloaded, the secure communication system may only need to identify the appropriate secure communication zone or zones within which the transfer is to occur.
[0085] If the secure communications system determines that the available secure communications zones do not provide sufficient driving distance for the secure communications transfer, it can allocate multiple secure communications zones to the secure data transfer task. This is shown in operation 454. As another option, if the secure communications system determines that the available secure communications zones do not provide sufficient driving distance for the secure communications transfer, it can dynamically adjust the zones to accommodate the secure communications transfer. For example, the system can extend the zones along the roadway so that the vehicle has more driving time to complete the transfer.
[0086] If a secure communication zone is not available at a location to complete the transfer by the required time for completion, or if one or more zones are available but are too short to accommodate the transfer, the secure communication system can dynamically adjust the size of one or more existing secure communication zones to accommodate the transfer. In some embodiments, the secure communication system may be configured to dynamically create a new secure transfer zone or multiple new secure transfer zones to accommodate the secure communication transfer. In further embodiments, the secure communication system may be configured to dynamically adjust one or more existing secure communication zones while simultaneously dynamically creating one or more new secure communication zones to accommodate the transfer.
[0087] Secure communication zones may be dynamically created, resized, removed, or otherwise modified, including changing security parameters, to better address scenarios as they occur. For example, consider the creation of a geofenced zone for the purpose of toll collection. Additionally, consider a scenario in which a special event (e.g., sporting event, concert, etc.) is taking place in a given part of a town. One or more dynamic toll booths can be virtually constructed to turn otherwise open highways into toll roads for revenue generation, traffic reduction, or other purposes. Dynamic toll booths can be constructed and installed in desired locations to achieve these and other goals. Vehicles that enter these zones may be requested to upload payment information, which may be secure, for the purpose of paying the toll. Additionally, drivers may be given advance warning, such as via V2I communication with infrastructure elements, before reaching a road segment with a toll booth. As a similar example, a dynamic toll booth can be virtually constructed to similarly turn an otherwise open parking area into a paid parking area.
[0088] It is believed that the terms circuitry and components used herein may describe a given functional unit that may be performed according to one or more embodiments of the present application. It is believed that the components used herein may be implemented utilizing any form of hardware, software, or combination thereof. For example, it is believed that one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logic components, software routines, or other mechanisms may be implemented to configure the components. The various components described herein may be implemented as separate components, and the described functions and features may be shared, in part or in whole, among one or more components. In other words, the various features and functionalities described herein may be implemented in any given application, as would be apparent to one of ordinary skill in the art upon reading this description. They may be implemented in one or more separate or shared components in various combinations and permutations. It should be understood that although various features or functional elements are described and claimed individually as separate components, these features / functionality may be shared among one or more common software and hardware elements. Such description does not require or imply that separate hardware or software components be used to implement such features or functionality.
[0089] When all or part of a component is implemented using software, these software elements can be implemented to operate in conjunction with a computing or processing component capable of performing the functionality described with respect thereto. One such computing component is illustrated in FIG. 5. Various embodiments are described in terms of this exemplary computing component 500. After reading this description, it will be apparent to one skilled in the art how to implement the application using other computing components or architectures.
[0090] Referring now to FIG. 5, computing component 500 may represent, for example, the computation or processing capabilities found in self-adjusting displays, desktop, laptop, notebook and tablet computers. These capabilities are found in handheld computing devices (tablets, PDAs, smart phones, cell phones, pocket calculators, etc.). They are found in workstations or other devices with displays, or any other type of special-purpose or general-purpose computing device, as may be desirable or appropriate for a given application or environment. Computing component 500 also represents computation capabilities embedded within or otherwise available to a given device. For example, it is contemplated that computing components may be found in other electronic devices, such as, for example, portable computing devices and other electronic devices that may include some form of processing capabilities.
[0091] It is contemplated that computing component 500 may include, for example, one or more processors, controllers, control components, or other processing devices. It is contemplated that processor 504 may be implemented using a general-purpose or special-purpose processing engine, such as, for example, a microprocessor, controller, or other control logic. Processor 504 may be coupled to bus 502. However, any communication medium may be used to facilitate interaction with other components of computing component 500 or for external communication.
[0092] It is contemplated that computing component 500 may also include one or more memory components, referred to herein simply as main memory 508. For example, it is contemplated that a random access memory (RAM) or other dynamic memory may be used to store instructions and information to be executed by processor 504. It is contemplated that main memory 508 may also be used to store temporary variables or other intermediate information during execution of instructions to be executed by processor 504. It is contemplated that computing component 500 may also include a read only memory ("ROM") or other static storage device coupled to bus 502 for storing instructions and static information for processor 504.
[0093] The computing component 500 may also include one or more various forms of information storage mechanisms 510, which may include, for example, a media drive 512 and a storage unit interface 520. The media drive 512 may include drives and other mechanisms for carrying fixed or removable storage media 514. For example, a hard disk drive, a solid state drive, a magnetic tape drive, an optical drive, a compact disk (CD) or digital video disk (DVD) drive (R or RW), or other removable or fixed media drive may be provided. The storage media 514 may include, for example, a hard disk, an integrated circuit assembly, a magnetic tape, a cartridge, an optical disk, a CD or a DVD. The storage media 514 may be any other fixed or removable media that is read, written or accessed by the media drive 512. As these examples show, the storage media 514 may include a computer usable storage medium having computer software or data stored therein.
[0094] In alternative embodiments, it is contemplated that the information storage mechanism 510 may include other similar means for allowing computer programs or other instructions or data to be loaded into the computing component 500. It is contemplated that such means may include, for example, a fixed or removable storage unit 522 and an interface 520. Examples of such storage units 522 and interfaces 520 may include program cartridges and cartridge interfaces, removable memory (e.g., flash memory or other removable memory components) and memory slots. Other examples may include PCMCIA slots and cards, and other fixed or removable storage units 522 and interfaces 520 that allow software and data to be transferred from the storage unit 522 to the computing component 500.
[0095] It is contemplated that the computing component 500 may also include a communications interface 524. It is contemplated that the communications interface 524 may be used to allow software and data to be transferred between the computing component 500 and external devices. It is contemplated that examples of the communications interface 524 may include a modem or soft modem, a network interface (e.g., Ethernet, network interface card, IEEE802.XX or other interface, etc.). Other examples include a communications port (e.g., a USB port, an IR port, an RS232 port, a Bluetooth interface, or other port), or other communications interface. The software / data transferred via the communications interface 524 may be carried on signals that may be electronic signals, electromagnetic signals (including optical signals), or other signals capable of being exchanged by a given communications interface 524. It is contemplated that these signals may be provided to the communications interface 524 via a channel 528. It is contemplated that the channel 528 may carry signals and may be implemented using a wired or wireless communications medium. Some examples of channels may include telephone lines, cellular links, RF links, optical links, network interfaces, local or wide area networks, and other wired or wireless communications channels.
[0096] As used herein, the terms "computer program medium" and "computer usable medium" generally refer to a transitory or non-transitory medium. Such medium may be, for example, memory 508, storage unit 520, medium 514, and channel 528. These and other various forms of computer program medium or computer usable medium may be involved in carrying one or more sequences of one or more instructions to a processing device for execution. Such instructions embodied on the medium are generally referred to as "computer program code" or a "computer program product" (which may be grouped into a computer program or other grouping). When executed, such instructions may enable computing component 500 to perform the features or functions of the present application as discussed herein.
[0097] It should be understood that the various features, aspects, and functionality described in one or more of the individual embodiments are not limited in applicability to the particular embodiment in which they are described. Rather, they may be applicable alone or in various combinations to one or more other embodiments, regardless of whether such an embodiment is described and whether such features are presented as part of a described embodiment. Thus, the breadth and scope of the present application should not be limited by any of the exemplary embodiments described above.
[0098] The terms and phrases used herein, and variations thereof, unless expressly stated otherwise, should be considered open ended rather than limiting. As examples above, the term "including" should be read to mean "including, but not limited to," and the like. The term "example" is used to provide illustrative examples rather than an exhaustive or exclusive list of the items being discussed. The terms "a" or "an" should be read to mean "at least one," "one or more," and the like, and terms such as "conventional," "traditional," "normal," "standard," and "known." Terms of similar meaning should not be considered to limit the items being described to those available in a given period or at a given time. Rather, they should be read to encompass conventional, traditional, or standard technology that may be available or known now or at any time in the future. Where this specification refers to technology that is believed to be apparent or known to those of ordinary skill in the art, such technology encompasses technology that is apparent or known to those of ordinary skill in the art now or at any time in the future.
[0099] The presence in some instances of broader terms and phrases such as "one or more," "at least," "but not limited to," or other similar terms should not be construed to imply that a narrower case is intended or desired in instances where such broader terms may be absent. Use of the term "component" does not imply that aspects or functionality described or claimed as part of that component are all configured within a common package. Indeed, any or all of the various aspects of a component, whether control logic or other components, may be combined in a single package or maintained separately, and may even be distributed in multiple groupings or packages or across multiple locations.
[0100] Moreover, various embodiments described herein are described with reference to exemplary block diagrams, flow charts, and other illustrations. As will become apparent to one of ordinary skill in the art after reading this specification, the illustrated embodiments and various variations thereof can be implemented without being limited to the examples shown. For example, the block diagrams and their accompanying description should not be construed as mandating a particular architecture or configuration. The invention disclosed in this specification includes the following aspects. [Aspect 1] 1. A method for secure data transfer to and from a vehicle, comprising: determining a size of a file to be transferred to or from the vehicle; determining a data transfer rate at which the file may be transferred; determining a distance traveled by the vehicle required to complete the transfer of the file based on the size of the file and the transfer rate; assigning a secure data transfer zone within which the transfer should occur based on the determined distance traveled and based on a size of the secure data transfer zone; A method comprising: [Aspect 2] 2. The method of embodiment 1, wherein allocating a secure data transfer zone includes identifying an existing secure data transfer zone of sufficient size to perform the transfer, and allocating the identified secure data transfer zone to perform the transfer. [Aspect 3] 2. The method of claim 1, wherein allocating a secure data transfer zone includes identifying an existing secure data transfer zone for conducting the transfer, dynamically modifying boundaries of the identified secure data transfer zone to accommodate the determined mileage for the transfer, and allocating the identified secure data transfer zone for the transfer. Aspect 4 2. The method of claim 1, wherein the assigned secure data transfer zone includes a plurality of secure data transfer zones of a cumulative size sufficient to effect the transfer, and further comprising adjusting boundaries of one or more of the plurality of secure data transfer zones such that the plurality of secure data transfer zones constitute a cumulative size sufficient to accommodate the determined mileage. Aspect 5 2. The method of embodiment 1, wherein allocating a secure data transfer zone includes creating a new secure data transfer zone or a plurality of new secure data transfer zones of a size sufficient to accommodate the determined mileage. Aspect 6 2. The method of claim 1, further comprising: predicting a speed of the vehicle while traveling through the assigned secure data transfer zone; and determining the distance traveled by the vehicle required to complete the transfer of the file using the predicted vehicle speed. Aspect 7 The method of embodiment 1, further comprising: predicting a path for the vehicle; and determining one or more available secure data transfer zones within the predicted path for the vehicle, wherein allocating a secure data transfer zone comprises allocating one or more secure data transfer zones among the one or more available secure data transfer zones. Aspect 8 8. The method of embodiment 7, wherein the one or more available secure data transfer zones include one or more existing secure data transfer zones, one or more dynamically created secure data transfer zones, or a combination of at least one existing secure data transfer zone and at least one dynamically created secure data transfer zone. Aspect 9 1. A system for secure vehicular communications, comprising: A processor, and a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to perform operations, the operations including: Determining a size of a file to be transferred to or from the vehicle; determining a data transfer rate at which the file may be transferred; determining a distance traveled by the vehicle required to complete the transfer of the file based on the size of the file and the transfer rate; assigning a secure data transfer zone within which the transfer should occur based on the determined distance traveled and based on a size of the secure data transfer zone; Memory, including Including, the system. Aspect 10 10. The system of embodiment 9, wherein allocating includes identifying an existing secure data transfer zone of sufficient size to accommodate the transfer, and allocating the identified secure data transfer zone to accommodate the transfer. Aspect 11 10. The system of claim 9, wherein allocating a secure data transfer zone includes identifying an existing secure data transfer zone for conducting the transfer, dynamically modifying boundaries of the identified secure data transfer zone to accommodate the determined mileage for the transfer, and allocating the identified secure data transfer zone for the transfer. Aspect 12 10. The system of claim 9, wherein the assigned secure data transfer zone includes a plurality of secure data transfer zones of a cumulative size sufficient to perform the transfer, and the operation further includes adjusting boundaries of one or more of the plurality of secure data transfer zones such that the plurality of secure data transfer zones constitute a cumulative size sufficient to accommodate the determined mileage. Aspect 13 10. The system of embodiment 9, wherein allocating the secure data transfer zone includes creating a new secure data transfer zone or a plurality of new secure data transfer zones of a size sufficient to accommodate the determined mileage. Aspect 14 10. The system of claim 9, wherein the operations further include predicting a speed of the vehicle while traveling through the assigned secure data transfer zone, and further determining the distance traveled by the vehicle required to complete the transfer of the file using the predicted vehicle speed. Aspect 15 10. The system of claim 9, wherein the operations further include predicting a route for the vehicle and determining one or more available secure data transfer zones within the predicted route for the vehicle, and wherein allocating a secure data transfer zone includes allocating one or more secure data transfer zones among the one or more available secure data transfer zones.
Claims
1. 1. A method for secure data transfer to and from a vehicle, comprising: determining a size of a file to be transferred to or from the vehicle; determining a data transfer rate at which the file may be transferred; determining a distance traveled by the vehicle required to complete the transfer of the file based on the size of the file and the data transfer rate; assigning a secure data transfer zone within which the transfer should occur based on the determined distance traveled and based on a size of a secure data transfer zone, wherein assigning the secure data transfer zone includes creating a new secure data transfer zone or a plurality of new secure data transfer zones of a size sufficient to accommodate the determined distance traveled; Locating the created secure data transfer zones at locations determined to control traffic volume; A method comprising:
2. The method of claim 1, wherein allocating the secure data transfer zone includes identifying an existing secure data transfer zone of sufficient size to perform the transfer, and allocating the identified secure data transfer zone to perform the transfer.
3. The method of claim 1, wherein allocating the secure data transfer zone includes identifying an existing secure data transfer zone for performing the transfer, dynamically modifying boundaries of the identified secure data transfer zone to accommodate the determined mileage for the transfer, and allocating the identified secure data transfer zone for the transfer.
4. 2. The method of claim 1, wherein the assigned secure data transfer zone includes a plurality of secure data transfer zones of a cumulative size sufficient to effect the transfer, and further comprising adjusting boundaries of one or more of the plurality of secure data transfer zones such that the plurality of secure data transfer zones constitute a cumulative size sufficient to accommodate the determined mileage.
5. 2. The method of claim 1, further comprising: predicting a speed of the vehicle while traveling through the assigned secure data transfer zone; and further determining the distance traveled by the vehicle required to complete the transfer of the file using the predicted vehicle speed.
6. 2. The method of claim 1, further comprising: predicting a path for the vehicle; and determining one or more available secure data transfer zones within the predicted path for the vehicle, and wherein allocating the secure data transfer zones comprises allocating one or more of the one or more available secure data transfer zones.
7. 7. The method of claim 6, wherein the one or more available secure data transfer zones include one or more existing secure data transfer zones, one or more dynamically created secure data transfer zones, or a combination of at least one existing secure data transfer zone and at least one dynamically created secure data transfer zone.
8. 1. A system for secure vehicular communications, comprising: A processor, and a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to perform operations, the operations including: Determining a size of a file to be transferred to or from the vehicle; determining a data transfer rate at which the file may be transferred; determining a distance traveled by the vehicle required to complete the transfer of the file based on the size of the file and the data transfer rate; assigning a secure data transfer zone within which the transfer should occur based on the determined distance traveled and based on a size of a secure data transfer zone, wherein assigning the secure data transfer zone includes creating a new secure data transfer zone or a plurality of new secure data transfer zones of a size sufficient to accommodate the determined distance traveled; Locating the created secure data transfer zones at locations determined to control traffic volume; Memory, including Including, the system.
9. The system of claim 8, wherein allocating the secure data transfer zone includes identifying an existing secure data transfer zone of sufficient size to perform the transfer, and allocating the identified secure data transfer zone to perform the transfer.
10. The system of claim 8, wherein allocating the secure data transfer zone includes identifying an existing secure data transfer zone for performing the transfer, dynamically modifying boundaries of the identified secure data transfer zone to accommodate the determined mileage for the transfer, and allocating the identified secure data transfer zone for the transfer.
11. 10. The system of claim 8, wherein the assigned secure data transfer zone includes a plurality of secure data transfer zones of a cumulative size sufficient to effect the transfer, and the operation further includes adjusting boundaries of one or more of the plurality of secure data transfer zones such that the plurality of secure data transfer zones constitute a cumulative size sufficient to accommodate the determined mileage.
12. 10. The system of claim 8, wherein the operations further include predicting a speed of the vehicle while traveling through the assigned secure data transfer zone, and further determining the distance traveled by the vehicle required to complete the transfer of the file using the predicted vehicle speed.
13. 10. The system of claim 8, wherein the operations further include predicting a path for the vehicle and determining one or more available secure data transfer zones within the predicted path for the vehicle, and wherein allocating the secure data transfer zones includes allocating one or more of the one or more available secure data transfer zones.
Citation Information
Patent Citations
Onboard download control device, and download control method
JP2017090092A
