US20130217331A1 - Systems and methods for vehicle policy enforcement - Google Patents

Abstract

This disclosure relates to systems and methods for vehicle policy management and enforcement. In certain embodiments, a method for enforcing a policy may include receiving policy information at a device including one or more conditions relating to a policy-managed location in a vehicle. A determination may be made whether the device is within the policy-managed location based on signals received by a short-range communication system included in the device and/or the vehicle. The received policy information may be evaluated to determine and implement one or more device actions associated with the one or more conditions.

Description

RELATED APPLICATIONS
• This application claims the benefit of priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 61/600,572, filed Feb. 17, 2012, and entitled “SYSTEMS AND METHODS FOR VEHICLE POLICY ENFORCEMENT,” which is hereby incorporated by reference in its entirety.
COPYRIGHT AUTHORIZATION
• Portions of the disclosure of this patent document may contain material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
BACKGROUND AND SUMMARY
• The present disclosure relates generally to systems and methods for vehicle policy management and enforcement. More specifically, the present disclosure relates to systems and methods for creating, managing, evaluating, and/or enforcing policies in connection with vehicles and other systems.
• Driving while distracted is one of the largest contributors to accidents, injury and death on roadways today. One of the contributing factors to driving while distracted is the use of mobile devices (e.g., smartphones, etc.) while operating a vehicle. According to the U.S. National Highway Transportation Safety Board, in 2009 alone, nearly 5,500 people were killed and 450,000 more were injured in vehicle crashes in the U.S. caused by distracted driving. Further, according to the U.S. Department of Transportation and the Virginia Tech Transportation Institute, text messaging on a mobile device while driving increases the risk of a crash by nearly 23 times over driving while not distracted.
• Sending or receiving a text message on a mobile device may take a driver's eyes off the road for an average of 4.6 seconds, the equivalent—at 55 miles per hour—of driving the length of an entire football field blind. Distracted driving in many instances is particularly concentrated within the younger age segment of the population—especially teens. Distracted driving is also an issue in other contexts, including in the operation of public transit vehicles (e.g., busses, trains, airplanes, etc.). With the widespread proliferation of mobile devices, distracted driving is a growing problem. Accordingly, systems and methods that reduce distracted driving, protect others from distracted driving, and/or otherwise enhance vehicle safety or control are desirable.
• Embodiments of the systems and methods disclosed herein relate to creating, managing, evaluating, and/or enforcing policies in connection with vehicles and other systems to enhance vehicle safety and/or control (e.g., by reducing distracted driving). In certain embodiments, a method for enforcing a policy on a device associated with a vehicle (e.g., a mobile phone) may include receiving policy information at the device including one or more conditions relating to a policy-managed location in the vehicle (e.g., a driver's seat location). The policy information may further include one or more exceptions associated with the one or more conditions.
• A determination may be made whether the device is within the policy-managed location based on signals received by a short-range communication system included in the device and/or the vehicle. The received policy information may be evaluated to determine and implement one or more device actions associated with the one or more conditions. Device actions may include, without limitation, disabling a feature or application of the device, changing an operating mode of the device, and/or the like. In certain embodiments, the policy information may further be evaluated based on sensor information received from one or more sensors included in the device and/or contextual information received from the vehicle.
• In further embodiments, a method for enforcing a policy on a vehicle and/or a system included in the vehicle may include receiving policy information including one or more conditions relating to a policy-managed location in the vehicle (e.g., a driver's seat location) at a policy management system included in the vehicle. The policy information may further include one or more exceptions associated with the one or more conditions.
• A determination may be made whether a device (e.g., a mobile phone) is within the policy-managed location based on signals received by a short-range communication system included in the device and/or the vehicle. The received policy information may be evaluated to determine and implement one or more vehicle actions associated with the one or more conditions. Vehicle actions may include, without limitation, disabling a feature of the vehicle, storing event information relating to the presence of the device within the policy-managed location, providing one or more notifications (e.g., audible or visual), and/or the like. In certain embodiments, the policy information may further be evaluated based on sensor information received from one or more sensors included in the vehicle and/or contextual information received from the device.
BRIEF DESCRIPTION OF THE DRAWINGS
• The inventive body of work will be readily understood by referring to the following detailed description in conjunction with the accompanying drawings, in which:
• FIG. 1aillustrates a vehicle equipped with an exemplary communication system consistent with embodiments of the present disclosure.
• FIG. 1billustrates a vehicle equipped with another exemplary communication system including a plurality of elements consistent with embodiments of the present disclosure.
• FIG. 2 illustrates an exemplary vehicle and device consistent with embodiments of the present disclosure.
• FIG. 3aillustrates an exemplary policy-enforced mode of operation in a device and a vehicle consistent with embodiments of the present disclosure.
• FIG. 3billustrates another exemplary policy-enforced mode of operation in a device and a vehicle consistent with embodiments of the present disclosure.
• FIG. 4aillustrates exemplary policy-enforced device actions consistent with embodiments of the present disclosure.
• FIG. 4billustrates exemplary policy-enforced vehicle actions consistent with embodiments of the present disclosure.
• FIG. 5 illustrates a flow chart of an exemplary device-based method of determining the presence of a device in a particular location within a vehicle consistent with embodiments of the present disclosure.
• FIG. 6 illustrates exemplary generation and distribution of policy data to a device consistent with embodiments of the present disclosure.
• FIG. 7 illustrates a flow chart of an exemplary device policy evaluation and enforcement process consistent with embodiments of the present disclosure.
• FIG. 8 illustrates a flow chart of an exemplary vehicle-based method of determining the presence of a device in a particular location within the vehicle consistent with embodiments of the present disclosure.
• FIG. 9 illustrates exemplary generation and distribution of policy data to a vehicle consistent with embodiments of the present disclosure.
• FIG. 10 illustrates a flow chart of an exemplary vehicle policy evaluation and enforcement process consistent with embodiments of the present disclosure.
• FIG. 11 illustrates exemplary condition-based policy enforcement actions consistent with embodiments of the present disclosure.
• FIG. 12 illustrates exemplary generation and distribution of policy data by a supervising entity to a device and a vehicle consistent with embodiments of the present disclosure
• FIG. 13 illustrates exemplary information used in a device-based policy management and enforcement decision consistent with embodiments of the present disclosure.
• FIG. 14 illustrates exemplary information used in a vehicle-based policy management and enforcement decision consistent with embodiments of the present disclosure.
• FIG. 15 illustrates exemplary vehicle sensors that can be used in policy evaluation and enforcement processes consistent with embodiments of the present disclosure.
• FIG. 16 illustrates exemplary supplemental device data that can be used in policy evaluation and enforcement processes consistent with embodiments of the present disclosure.
• FIG. 17 illustrates exemplary supplemental vehicle data that can be used in policy evaluation and enforcement processes consistent with embodiments of the present disclosure.
• FIG. 18 illustrates exemplary generation of contextual vehicle and device data consistent with embodiments of the present disclosure.
• FIG. 19 illustrates exemplary policy evaluation and enforcement by a vehicle consistent with embodiments of the present disclosure.
• FIG. 20 illustrates exemplary policy evaluation and enforcement by a device consistent with embodiments of the present disclosure.
• FIG. 21 illustrates data distribution to and from third parties that may be used in policy evaluation and enforcement processes consistent with embodiments of the present disclosure.
• FIG. 22 illustrates exemplary device and vehicle actions in response to policy evaluation and enforcement decisions consistent with embodiments of the present disclosure.
• FIG. 23 illustrates various exemplary credentials for providing secure policy generation, management, and/or enforcement consistent with embodiments of the present disclosure.
• FIG. 24 illustrates an exemplary system that may be used to implement embodiments of the systems and methods of the present disclosure.
DETAILED DESCRIPTION
• A detailed description of systems and methods consistent with the inventive body of work is provided below. While several embodiments are described, it should be understood that the disclosure is not limited to any one embodiment, but instead encompasses numerous alternatives, modifications, and equivalents. In addition, while numerous specific details are set forth in the following description in order to provide a thorough understanding of the embodiments disclosed herein, some embodiments can be practiced without some or all of these details. Moreover, for the purpose of clarity, certain technical material that is known in the related art has not been described in detail in order to avoid unnecessarily obscuring the disclosure.
• Embodiments of the disclosure may be understood by reference to the drawings, wherein like parts may be designated by like numerals. The components of the disclosed embodiments, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of various embodiments is not intended to limit the scope of the disclosure, as claimed, but is merely representative of possible embodiments. In addition, the steps of methods disclosed herein do not necessarily need to be executed in any specific order, or even sequentially, nor need the steps be executed only once, unless otherwise specified.
• Mobile devices (e.g., smartphones) often include a panoply of features and sensor systems. For example, many mobile devices may include accelerometers, Global Positioning System (“GPS”) sensors, wireless communication systems (e.g., Bluetooth®, WiFi, near field communication (NFC) technology, etc.), and/or the like. Systems and methods disclosed herein may use one or more device sensors and/or communication systems in connection with managing and enforcing policies associated with devices and/or vehicles to reduce distracted driving and/or other unsafe behavior. For example, a device may include a policy articulating that when the device is moving at speeds associated with driving, certain features of the device may not be used. GPS sensors and/or accelerometers included in the device may be used to determine when the device is moving at such speeds and, in response, policy enforcement systems operating on the device may prevent certain device features (such as text messaging, electronic mail, keyboard entry of data, etc.) from being used.
• While such a simplistic policy may help to reduce distracted driving, in certain circumstances it may not account for instances when a device is in motion but is still safe to use. For example, if a rear seat passenger in a vehicle or a rider on a public transit vehicle wishes to use their device while in motion, they can do so safely. Accordingly, systems and methods disclosed herein may detect when a device is being used in unsafe circumstances or when a device is in an environment where its use would be unsafe, and may trigger one or more responsive actions that can help reduce risk (e.g., warning a device user of safety concerns, warning others who may be impacted by an unsafe situation, disabling device features that may contribute to distractions, and/or the like).
• Mobile devices (e.g., smartphones) may include short-range communication capabilities. Systems and methods disclosed herein may use short-range communication capabilities to manage and enforce policies that encourage safe driving practices. For example, in certain embodiments, short-range communication technologies can be used to locate one or more mobile devices within a vehicle, and such location information can be used to more accurately determine whether the device and/or vehicle can be, or is being, used safely.
• FIG. 1aillustrates avehicle100 equipped with an exemplary communication system consistent with embodiments of the present disclosure. AlthoughFIG. 1aillustratesvehicle100 as a passenger vehicle, systems and methods disclosed herein may be used in connection with any suitable land, water, and/or air vehicle including, without limitation, cars, trucks, busses, motorcycles, bicycles, trains, boats, aircraft, and/or the like.
• Thevehicle100 may include a short-range communications receiver/transmitter element101. In certain embodiments, the receiver/transmitter element101 may be located proximate to a driver of thevehicle100. For example, as illustrated, the receiver/transmitter element101 may be located in or near a steering wheel of thevehicle100. In further embodiments, the receiver/transmitter element101 may be located proximate to any other location in thevehicle100 associated with policy management and enforcement decisions. For example, if a backseat passenger-side location in thevehicle100 is associated with policy management and enforcement decisions, one or more receiver/transceiver elements101 may be located proximate to the backseat passenger-side location of thevehicle100.
• In certain embodiments, the short-range communications receiver/transmitter element101 may produce a field that encompasses a policy-managed location within thevehicle100. For example, as illustrated, receiver/transmitter element101 may produce a field that encompasses a driver's seat location within thevehicle100. The short-range communications receiver/transmitter element101 may be configured to detect and/or communicate with one or more devices (not shown) located within the field associated with the policy-managed location. Similarly, devices may be able to detect their presence within a field associated with the policy-managed location. For example, receiver/transmitter element101 and/or a device may be able to detect when the device is located within a field produced by receiver/transmitter element101 associated with the driver's position within thevehicle100.
• The short-range communications receiver/transmitter element101 may use any suitable short-range communication technologies and/or protocols to communicate with a device (e.g., a smartphone) located in or near thevehicle100 within a range of the receiver/transmitter element101. For example, the receiver/transmitter element101 may use active and/or passive short-range communication technologies, near field communication (“NFC”) standards or technologies, IEEE's 802.11 standards, Bluetooth®, ultra-wide band (“UWB”), Zigbee®, Radio-frequency identification (“RFID”), and/or any other suitable wireless communication protocols or combinations thereof. In some embodiments, modified versions of standardized technologies may be used to, for example, increase (or decrease) the range or accuracy of the signal, vary the frequency that is used, and/or the like. Thus, for ease of explanation, when reference is made herein to a particular standard or protocol, it will be understood that such modified versions or extensions of the standard or protocol are intended to be encompassed as well. For example, when reference is made herein to near field communication (NFC) technology, it is meant to include technologies that may not literally comply with a formal NFC standard, but which operate in accordance with the same basic physical principles (e.g., situations where the receiver/transmitters have been modified so that the field may cover a larger area).
• In certain embodiments, the receiver/transmitter element101 may be configured to facilitate active communication with one or more devices within the range of the receiver/transmitter element101. In further embodiments, the receiver/transmitter element101 may passively determine that one or more devices are within a proximate range of the receiver/transmitter element101. Thus, it will be appreciated that, unless otherwise clear from the context, the term “receiver/transmitter” is used herein to refer to elements capable of acting as both a receiver and a transmitter, as well as elements that are capable of acting as a receiver (but not a transmitter), and elements that are capable of acting as a transmitter (but not a receiver).
• Although, as previously indicated, a variety of communications technologies may be used in conjunction with the systems and methods described herein, technologies based on near field communications (NFC) may be particularly advantageous for some embodiments where it is especially desirable to precisely determine the location of the device within a small region (such as a vehicle passenger compartment). NFC technologies have an added advantage in that coupling can typically occur only within a specific (typically short) distance from the antenna (e.g., the “near field”). Therefore, by placing one or more antennas at known location(s), it is possible to easily (and with a considerable degree of confidence) infer the location of the device that is being communicated with. Furthermore, passive near field communications has the added benefit of low battery drain on the portable device (while taking advantage of the more plentiful power source on the vehicle); and active near field communication can be employed to communicate dynamically-changing data in a bi-directional fashion (such as operating mode information sent in a message request-response sequence). Representative near field communications technologies that can be used include those that have been specified by industry standards organizations such as the NFC Forum, ECMA, ETSI, ISO/IEC, as well as other more general applications of near field communication technology, that employ different frequencies, signal strengths, thresholds and/or data protocols. Ideally, frequencies, signal strengths, and thresholds would be customized to produce a near-field that occupies a volume of space corresponding to the size of the intended policy-managed location. However, any number of antennas and their associated near fields (of similar or different sizes) may be suitably arranged to encompass a volume of whatever shape or size is desired.
• FIG. 1billustrates avehicle100 equipped with another exemplary short-range communication system including a plurality ofelements101a,101bconsistent with embodiments of the present disclosure. In certain embodiments, to increase a size of a field emitted by the short-range communication system (e.g., to increase a coverage volume) and/or to increase positional sensing accuracy, the communication system may include a plurality of receiver/transmitter elements101a,101b.For example, as illustrated, the short-range communication system may include a first receiver/transmitter element101alocated above the driver position and a second receiver/transmitter element101blocated below the driver position.
• Any suitable number and/or configuration of receiver/transmitter elements may also be located at various points within thevehicle100 to communicate with devices (not shown) and/or determine location(s) of devices within thevehicle100. For example, one or more receiver/transmitter elements may be associated with each seat location in thevehicle100, thereby enabling the short-range communication system to determine how many devices are located in thevehicle100 and the location of the devices relative to the one or more seat locations. Exemplary locations for receiver/transmitter elements include, without limitation, the vehicle dashboard, the vehicle console area, in or near driver and/or passenger visors, headrests, seatbelt components, and/or any location that is practicable and suitably allows a receiver/transmitter element to cover a designated volume of space (e.g., a policy-managed location) within thevehicle100.
• In certain embodiments, using a plurality of receiver/transmitter elements101a,101bmay allow a location of a device within thevehicle100 to be determined based on relative signal strengths provided and/or received by receiver/transmitter elements101a,101b.For example, if a device receives a signal from receiver/transmitter element101athat is stronger than a signal received from receiver/transmitter element101b, it may be determined that the device is located closer toelement101athan it is toelement101b. Similarly, if receiver/transmitter element101areceives a signal from a device that is stronger than a signal received from receiver/transmitter element101b, it may be determined that the device is located closer toelement101athan it is toelement101b. Based on the locations of the receiver/transmitter elements101a,101brelative to one or more locations within thevehicle100, a position or likely position of the device relative to the one or more locations within thevehicle100 may be determined.
• In some embodiments, the relative signal strengths between receiver/transmitter elements101a,101band a device may be used to triangulate a position or likely position of the device within thevehicle100. In some embodiments, communication delay times between a device and a plurality of receiver/transmitter elements101a,101bmay be used to determine which of the plurality ofelements101a,101bthe device is closest to and/or to triangulate a position of the device within avehicle100.
• FIG. 2 illustrates anexemplary vehicle100 anddevice200 consistent with embodiments of the present disclosure. Although illustrated as a smartphone,device200 may comprise a variety of computing devices and/or systems, including any mobile system and/or device suitable to implement the systems and methods disclosed herein. For example,device200 may comprise a laptop computer system, a wireless communication device (e.g., a cellular telephone such as a smartphone or feature phone), a tablet computer, a wireless control device (e.g., keyless entry or remote start devices), a gaming or other entertainment device, and/or the like. Additional non-limiting examples ofdevice200 include a telematics system, a navigational system, and/or an in-vehicle infotainment (“IVI”) system, which may or may not be integrated into thevehicle100.
• Thedevice200 may include a short-range communications system including one or more receiver/transmitter elements201. The receiver/transmitter element(s)201 may use any suitable short-range communication technologies and/or protocols to communicate with one or more receiver/transmitter elements101 associated with thevehicle100. For example, the receiver/transmitter element201 may use active and/or passive short-range communication technologies, NFC standards, IEEE's 802.11 standards, Bluetooth®, UWB, Zigbee®, RFID, and/or any other suitable wireless communication protocols or combinations thereof to enable thevehicle100 and/or thedevice200 to detect one another and/or to communicate data. For example, the receiver/transmitter element201 may allow thedevice200 to determine when it is located in a particular policy-managed location within the vehicle100 (e.g., a driver position). Utilizing this information, thedevice200 and/or thevehicle100 may evaluate and enforce policies regarding the use of thedevice200 and/or thevehicle100 under one or more conditions.
• FIG. 3aandFIG. 3billustrate exemplary policy-enforced modes of operation in adevice200 and avehicle100 consistent with embodiments of the present disclosure. Policies may articulate one or more rules or conditions relating to the use and/or function of thevehicle100 and/or thedevice200. For example, policies may enforce, among other things, conditions relating to thevehicle100 and/or the device200 (e.g., device location-based conditions, vehicle location-based conditions, vehicle use conditions, etc.), actions associated with the one or more conditions (e.g., disable text messaging applications and/or other device features whenvehicle100 is moving, disable starting motor orother vehicle100 features, cause emergency indicator lights ofvehicle100 to flash, etc.), exceptions to actions, and/or the like. In certain embodiments, policies may be used to enforce one or more modes of operation of adevice200 and/or avehicle100 based on the occurrence of one or more conditions.
• Policies may be device-based and/or vehicle-based. A device policy may articulate policies regarding the use and/or function of thedevice200 under one or more conditions. As illustrated inFIG. 3a, a device policy may specify an action bydevice200 in response to the occurrence of one or more conditions. For example, a device policy may provide that a text messaging application of adevice200 should be disabled when it is determined (e.g., by the device, the vehicle, and/or a combination of both or other means) that the device is within a driver's position (or other policy-managed location) of thevehicle100.
• A vehicle policy may articulate certain policies regarding the use and/or function of thevehicle100 under one or more conditions. As illustrated inFIG. 3b, a vehicle policy may articulate an action byvehicle100 in response to the occurrence of one or more conditions. For example, a vehicle policy may provide that a starter motor of thevehicle100 should be disabled when thevehicle100 determines that thedevice200 and/or a feature thereof is being used in a driver's position of thevehicle100.
• In certain embodiments, policies may be both device-based and vehicle-based. That is, a policy may articulate certain actions to be performed by both thevehicle100 and thedevice200 in response to the occurrence of one or more conditions. For example, a policy may provide that under certain conditions, thedevice200 should perform certain responsive actions (e.g., disabling certain features, etc.) and thevehicle100 should perform certain responsive actions (e.g., warning occupants of the vehicle, other drivers, and/or law enforcement of unsafe driving practices, etc.). In certain embodiments, such policies may be enforced independently and/or simultaneously by thevehicle100 and/or thedevice200.
• Policies associated with thevehicle100 and thedevice200 may further be articulated and/or enforced, at least in part, independently. For example, thedevice200 may detect that it is within a policy-managed location within the vehicle100 (e.g., a driver's position). In response, thedevice200 may switch to a safer mode of operation (e.g., a “voice control only” mode or the like). Subsequently, upon independently sensing that thedevice200 is in a safer mode of operation, thevehicle100 may perform an appropriate responsive action (e.g., disengaging a warning buzzer or the like).
• FIG. 4aillustrates exemplary policy-enforceddevice actions400 consistent with embodiments of the present disclosure. As discussed above, a policy (e.g., a device-based policy) may expresscertain actions400 to be performed by adevice200 in response to the occurrence of one or more conditions. For example, a device may take one ormore device actions400 in response to determining that thedevice200 is within a policy-managed location within avehicle100.Device actions400 may include, for example, storing information regarding the use of thedevice200 while in a policy-managed location (e.g., time and/or date, types of usage, devices and/or applications used, etc.). In certain embodiments, thedevice actions400 may include locking or disabling, temporarily or otherwise, certain features and/or functionalities of thedevice200. For example, certain communication features such as cellular radio communications, data services, text messaging communications, and/or the like may be temporarily locked or disabled. Similarly, certain device applications such as text messaging applications, e-mail applications, instant message (“IM”) applications, and/or any other application may be temporarily locked or disabled. Certain device functions may also be temporarily locked or disabled, includingdevice200 keyboards, screens, and/or other systems or services.
• Device actions400 may further include automatic reply messaging in response to incoming communications. For example, if a text message is received by thedevice200 while it is in a policy-managed location within the vehicle100 (e.g., a driver's position), the device may automatically send a responsive message (e.g., “I'm driving now, I will get back to you later” or the like). In certain embodiments, such automatic reply messages may be configurable by a user and may include further information derived fromother vehicle100 and/ordevice200 systems (e.g., a GPS system) such as an estimated arrival time to a destination.
• In certain embodiments,device actions400 may be associated with one or more modes of operation ofdevice200. Responsive to the occurrence of one or more policy-defined conditions, thedevice200 may enter one or more modes of operation. Device modes of operation may include, without limitation, a “voice control mode,” a “driving mode,” a “hands free mode,” an “airplane mode,” a “silent mode,” and/or any other suitable operational mode. In certain embodiments, a mode of operation of thedevice200 may be associated with the activation and/or disabling of a certain set of features of the device200 (e.g., features contributing to driver distraction). For example, in some embodiments, while in a “driving mode,” a keyboard, screen, and/or certain applications of thedevice200 may be disabled, and thedevice200 may only be controlled using voice commands.
• Whileseveral device actions400 and/or modes of operation are described herein, the disclosed actions and/or modes of operation are not to be considered limiting. Rather, the discloseddevice actions400 and/or modes of operation are to be viewed as examples ofpossible device actions400 and/or modes of operation, as manyother device actions400 and/or modes of operation may be implemented alternatively or in addition as part of the device-based policies disclosed herein.
• FIG. 4billustrates exemplary policy-enforcedvehicle actions402 consistent with embodiments of the present disclosure. As discussed above, a policy (e.g., a vehicle-based policy) may expresscertain actions402 to be performed by avehicle100 in response to the occurrence of one or more conditions. For example, avehicle100 may take one ormore vehicle actions402 in response to determining that adevice200 is within a policy-managed location within the vehicle100 (e.g., in a driver's position).Vehicle actions402 may include, for example, storing information regarding the use of thedevice200 and/or thevehicle100 while thedevice200 is in a policy-managed location in the vehicle100 (e.g., time and/or date, vehicle speed, vehicle drivetrain status—drive, park, etc., vehicle location, etc.)
• In certain embodiments,vehicle actions402 may include providing one or more notifications. Notifications may include audible or visual notifications or any combination thereof. For example, thevehicle100 may sound an audible warning (e.g., a buzzer or the like) similar to what occurs when a vehicle occupant is detected in a seat with an unsecured seatbelt. Notifications may also be provided external to thevehicle100. For example, thevehicle100 may dim or flash one or more head and/or taillights, thereby warning nearby traffic or pedestrians of a possible distracted driver.
• In some embodiments,vehicle actions402 may further include transmitting certain information and/or messages to one or more entities associated with thevehicle100 and/or thedevice200. For example, in response to determining that thedevice200 is being used in a policy-managed location,vehicle100 may transmit a notification to a law enforcement agency, an insurance provider, a supervising entity (e.g., fleet operators, concerned parents, etc.), and/or other interested entities indicating that thedevice200 is being used in a policy-managed location within thevehicle100.
• In further embodiments, thevehicle actions402 may include locking or disabling, temporarily or otherwise, certain features and/or functionalities of thevehicle100. For example, a starter motor of thevehicle100 and/or the ability of a driver to engage the powertrain of thevehicle100 may be temporarily disabled based on a determination that adevice200 is being used in a policy-managed location within thevehicle100 and/or in a policy-managed situation (e.g., while a public transit vehicle is in service, etc.). Such features and/or functionalities may be re-enabled when use of thedevice200 within the policy-managed location or situation ceases.
• Similar todevice actions400,vehicle actions402 may also be associated with one or more modes of operation of vehicle100 (e.g., park, drive, driving under certain speeds, etc.). Whileseveral vehicle actions402 and/or modes of operation are disclosed herein, the actions and/or modes of operation disclosed herein are to be considered as examples ofpossible vehicle actions402 and/or modes of operations, as many other types ofvehicle actions402 that may be implemented as part of vehicle-based policies are also contemplated.
• FIG. 5 illustrates a flow chart of an exemplary device-based method of determining the presence of a device in a particular location within a vehicle and/or in a particular policy-managed situation. Particularly, the illustrated method may determine the presence of a device in a policy-managed location (e.g., a sensitive location). As used herein, the terms policy-managed location and sensitive location may be used interchangeably. It will also be understood that while, for ease of explanation, many of the examples set forth herein refer simply to the application of location-based policies, situation-based (or mode of operation-based) policies can be applied alternatively or in addition. The illustrated method may be implemented by a device in a variety of ways, including using software, firmware, hardware, and/or any combination thereof.
• Referring once again toFIG. 5, at202, the method may be triggered. In certain embodiments, the method may be triggered as part of a routine start-up process of a device. Alternatively, or in addition, the method may be triggered as a result of opening a particular application or using a certain feature of the device (e.g., a text messaging application or a device keyboard, using the device to unlock the vehicle, etc.) and/or based on the occurrence of a particular device event (e.g., receiving an incoming communication such as a text message). In further embodiments, the method may be triggered based on a determination by the device and/or associated sensors (e.g., GPS sensors, accelerometers, and/or the like) that the device is in a situation where policy management is desirable. For example, the method may be triggered based on the device determining that it is located within a moving vehicle, that the vehicle is moving over a certain speed, that the vehicle is operating at a certain time of day or in certain weather or road conditions, that the vehicle is being driven by a specific driver and/or occupied by certain passengers, and/or any other suitable situation or combination of situations.
• At203, the device may check for signals from a short-range communication system in proximity to the device. Checking for signals from a short-range communication system may result in a variety of outcomes. For example, no signals may be received, signal(s) may be received that do not indicate that the device is in a policy-managed location in the vehicle, or signal(s) may be received that indicate that the device is in a policy-managed location in the vehicle (e.g., a driver's position or other sensitive position). For example, vehicle-based short range transmitters can securely transmit a signal that indicates to the device that it is in proximity to a sensitive area, and possibly communicate additional data to indicate what type of area the device is operating in. As another example, in some embodiments one or more vehicle sensors can be used to locate the source of wireless signals from the device (e.g., signal strength, differential signal strength, or disruptions to a field that can be sensed by the vehicle, and communicated to the device). Another example of how a determination could be made as to whether a device is in a sensitive location is by making use of device and/or vehicle sensors and/or tags that may actively or passively communicate using Near Field Communication links, thereby passing data relevant to device location, vehicle status, and/or device status to one another. In yet another example, a device can monitor signal strength from one or more standardized vehicle-mounted beacons, and/or make a comparison of signal characteristics from multiple beacons placed at specific locations within the vehicle. It will be appreciated that any or all of the foregoing example techniques, as well as any other suitable technique(s), could be used to determine device location.
• Referring once again toFIG. 5, based at least in part on the received signals, at204, the device may determine whether it is proximate to and/or within a policy-managed location. If the device is in a policy-managed location,device location information206 may be set to indicate that the device is in a sensitive and/or policy-managed location at205. If the device is not in a policy-managed location, thedevice location information206 may be set to indicate that the device is not in a sensitive and/or policy-managed location at207. In further embodiments, if the device is not proximate to a policy-managed location but proximate to another known location, the known location may be included in thedevice location information206 set at207.
• After thedevice location information206 has been set, the method may proceed to208 where the device may wait for a certain delay time and/or the receipt of a re-detection trigger, enabling the device to re-check its position on a periodic and/or an event-driven basis. For example, when a vehicle operator leaves the vehicle, he or she may wish to use a device in a normal manner without any policy-enforced encumbrances associated with the device being located within a policy-managed location. Waiting for a certain delay period and/or for the receipt of the re-detection trigger event may allow thedevice location information206 to be updated to reflect a current location status of the device. For example, the method may be re-triggered when an application is launched on the device and/or a screen of the device is activated. By utilizing a time delay based re-triggering process, an event-based re-triggering process, or a combination thereof, battery life of the device may be conserved in comparison to other embodiments of the systems and methods disclosed herein where location information is monitored on an effectively continuous basis (e.g., without a delay time or re-triggering event).
• Consistent with embodiments disclosed herein,device location information206 may be used in policy management and enforcement processes. For example, as discussed above, certain features and/or functions of a device and/or a vehicle may be temporarily disabled (or enabled and/or actuated) based on the status of thedevice location information206 in accordance with articulated policies. In addition todevice location information206, a device and a vehicle may exchange data that indicates contextual information about the vehicle or its status. As discussed in more detail below, this contextual vehicle information may also be used in policy management and enforcement processes disclosed herein.
• FIG. 6 illustrates exemplary generation and distribution ofpolicy data209 to adevice200 consistent with embodiments of the present disclosure.Policy data209 may specify and/or otherwise express or enable enforcement of one or more rules or conditions relating to the use and/or function of thedevice200. For example,policy data209 may express, encode, and/or otherwise be used to facilitate the enforcement of, among other things, conditions relating to the device200 (e.g., device location-based conditions, vehicle location-based conditions, device use conditions, etc.), actions associated with the one or more conditions (e.g., disable text messaging applications and/or other device features when vehicle is moving, etc.), exceptions to actions, and/or the like.
• Policy data209 may be delivered to adevice200 in a variety of ways. In certain embodiments,policy data209 may be pre-set in a device200 (e.g., by a device manufacturer or the like). In further embodiments, policy data209 (e.g., conditions, actions, exceptions, etc.) may be configurable via any suitable means or combination thereof. For example, in some embodiments,policy data209 may be set and/or configured by auser602a(e.g., a device owner or the like) directly into thedevice200. For example, one or more device inputs (e.g., a keyboard, touch screen, etc. interacting with one or more menus on a user interface) may be used to set and/or configurepolicy data209.
• In further embodiments, auser602bmay deliverpolicy data209 to thedevice200 via anetwork600. Thenetwork600 may comprise a variety of network communication devices and/or channels and may use any suitable communications protocols and/or standards facilitating communication between thedevice200 and one or more network-connectedentities602b-610. For example, thenetwork600 may comprise a wireless carrier system, such as a personal communications system (“PCS”), a global system for mobile communication, and/or any other suitable communication system incorporating any suitable communication standards and/or protocols. In further embodiments, thenetwork600 may include an analog mobile communications network and/or a digital mobile communications network utilizing, for example, code division multiple access (“CDMA”), Global System for Mobile Communications or Groupe Speciale Mobile (“GSM”), frequency division multiple access (“FDMA”), and/or time divisional multiple access (“TDMA”) standards. In certain embodiments, thenetwork600 may incorporate one or more satellite communication links. In yet further embodiments, thenetwork600 may use IEEE's 802.11 standards, Bluetooth®, ultra-wide band (“UWB”), Zigbee®, and/or any other suitable standard or standards. In some embodiments, the network may comprise the Internet and/or a local WiFi network.
• As illustrated,policy data209 may be delivered to thedevice200 from a variety of network-connectedentities602b-610. For example, as discussed above, auser602bof thedevice200 may deliverpolicy data209 to thedevice200 via thenetwork600. In certain embodiments, auser602bof thedevice200 may be a device owner. In further embodiments, theuser602bmay be a parent/employer of a device user and/or some other interested party.
• In certain embodiments, amobile service operator604 may wish to offer the ability to increase the safety of itscustomers using devices200 on theirnetwork600 by offering the ability to configuredevices200 for added safety. Accordingly,mobile service operator604 may deliverpolicy data209 to thedevice200 via thenetwork600. In some embodiments, themobile service operator604 can deliverpolicy data209 todevice200 directly or may provide policy management and enforcement services on behalf of parents/employers or other supervising entities who may be their direct customers.
• In another example, apolicy distribution service606 may deliverpolicy data209 to thedevice200 via thenetwork600. In certain embodiments, thepolicy distribution service606 may be associated with a mobile device management service or a mobile application developer. In some embodiments,policy distribution service600 may respond to location data (e.g., GPS data) that provides an indication as to the location of thedevice200 or an associated vehicle, and deliverappropriate policy data209 based on the location. For example, certain jurisdictions may have laws relating to the use ofdevices200 while operating a vehicle.Policy distribution service606 may detect when adevice200 and/or a vehicle are within such a jurisdiction and deliverappropriate policy data209 specifying rules reflecting the laws of the jurisdiction. Similarly, certain locations may have rules or regulations relating to the use ofdevices200 while in the location (e.g., a movie theater).Policy distribution service606 may detect when adevice200 is at such a location and deliverappropriate policy data209 reflecting the rules or regulations of the location.
• In some embodiments,mobile device manufacturers608 may embedpolicy data209 intodevices200 at the time of manufacture and/or, vianetwork600, deliverpolicy data209 to adevice200 at a later date (e.g., via an application that is downloaded to the device, a system update, and/or the like). In this manner,mobile device manufacturers608 can perform “late customization” of their devices. That is,mobile device manufacturers608 can ship adevice200 without embeddedpolicy data209 or withdefault policy data209, and may later deliverpolicy data209 that reflects the laws of the jurisdiction where the associateddevice200 is used and/or that reflects the preferences of the user602. In other embodiments,policy data209 may be embedded at time of manufacture or within an application in an inactive state. The policy can later be activated by the user directly or alternatively via network-based mechanisms previously described.
• A variety of other sources ofpolicy data209 are also contemplated. For example,policy data209 may be delivered to adevice200 via thenetwork600 by alaw enforcement agency610. For example, alaw enforcement agency610 may deliverpolicy data209 to adevice200 reflecting the laws of a particular jurisdiction. In yet further embodiments,policy data209 may be delivered by insurance providers that may offer discounts to drivers that use the policy management and enforcement systems and methods disclosed herein. Accordingly, the sources ofpolicy data209 detailed herein are to be viewed as illustrative and not exhaustive. In some embodiments,policy data209 may form part of, be embodied as, or otherwise be delivered in connection with, an application (or “app”) that is downloaded to thedevice200 from an application store at the request of the device's user or administrator.
• The disclosed policy management and enforcements systems and methods may be used in a variety ofdevices200. For example, package delivery services such as FedEx may choose to set policy on special-purpose devices such as shipment tracking devices and their use by employee drivers in delivery vehicles. Similarly, vehicle manufacturers may choose to set policy on telematics or IVI systems included in vehicles and their use by vehicle occupants while driving. Thus, it will be appreciated that the policy management and enforcement techniques disclosed herein may be used in connection with a variety ofdevices200 and/or scenarios, not just in connection with the use of mobile phones in vehicles.
• FIG. 7 illustrates a flow chart of an exemplary device policy evaluation and enforcement process consistent with embodiments of the present disclosure. The illustrated method may be implemented in a variety of ways, including using software, firmware, hardware, and/or any combination thereof. The illustrated process may use one or more inputs including, without limitation,device location information206,policy data209, sensed and/or receiveddata213, and/orcontextual vehicle data214. It will be appreciated that in other embodiments other combinations of these or other inputs may be used.
• Device location information206 may include an indication as to where the device is located within a vehicle. For example, thedevice location information206 may indicate if the device is in a sensitive and/or policy managed location and/or another known location in the vehicle. In some embodiments, thedevice location information206 may be generated using, at least in part, a short-range communications system included in the device and/or the vehicle.Policy information209 may include information regarding one or more conditions used to evaluate whether an action should occur, actions associated with the conditions, exceptions to the actions, and/or the like. Sensed and/or receiveddata213 may include, without limitation, data generated by device sensors (e.g., parameters associated with functions of the phone, accelerometer data, and/or the like) and/or data received by third parties.Contextual vehicle data214 may include, without limitation, information received from a vehicle over a short-range communications system or other means that, among other things, may specify environmental data about the vehicle status or other information that is sensed by the vehicle.
• At210, the device policy evaluation and enforcement process may be triggered. In certain embodiments, the method may be triggered as part of a routine start-up process of a device. Alternatively, or in addition, the method may be triggered as a result of opening a particular application or using a certain feature of the device (e.g., a text messaging application or a device keyboard) and/or based on the occurrence of a particular device event (e.g., receiving an incoming communication such as a text message). In further embodiments, the method may be triggered by a short range communication system of the device detecting a change in signal status (e.g., indicating that the device location has changed) and/or by a change in any ofinputs206,209,213, and/or214.
• At211, contextual information used for policy evaluation decisions may be read or sensed. At212, policy logic that articulates or operates onpolicy data209 may be evaluated. As illustrated, this evaluation may be based, at least in part, oninputs206,209,213, and/or214. For example, a simple policy may specify that if thedevice location information206 indicates that the device is in a sensitive and/or policy-managed location, a certain feature of the device should be disabled (e.g., text messaging applications or the like). At215, it may be determined whether an action is required based on the result of the policy evaluation at212. If an action is required, the action may be performed at216. For example, in certain embodiments, a policy-enforced action may specify thatcertain device parameters217 are to be set in a specific way (e.g., parameters disabling certain device features, parameters directing the device to log certain events, etc.). If no action is required, the process may proceed to218.
• At218, if necessary, parameters may be set to current and/or default values and/or conditions. For example, if a feature has been previously disabled because of a policy determination, it may need to be reset if the policy is later re-evaluated and the action disabling the feature is no longer triggered. In certain embodiments, reset processes performed at218 may be integrated into policy evaluation andenforcement steps212,215, and/or216.
• At219, the process may wait for a certain delay time and/or the receipt of a re-evaluation trigger before restarting the policy evaluation and enforcement steps. As discussed above in reference toFIG. 5, a user may wish to use a device in a normal manner without any policy-enforced encumbrances after the location or contextual information associated with the device has changed. Accordingly, in some embodiments, the process illustrated inFIG. 7 may be repeated as soon as is practical (e.g., following a delay time and/or the receipt of a re-evaluation trigger). Upon waiting the delay time and/or for the receipt of the re-evaluation trigger, the process can be repeated, possibly with updatedinputs206,209,213,214 resulting in updated actions or reset device and/or vehicle system parameters.
• FIG. 8 illustrates a flow chart of an exemplary vehicle-based method of determining the presence of a device in a particular location within the vehicle consistent with embodiments of the present disclosure. Particularly, the illustrated method may determine the presence of a device in a policy-managed location (e.g., a sensitive location) within a vehicle. The illustrated method may be implemented by a vehicle in a variety of ways, including using software, firmware, hardware, and/or any combination thereof. In some embodiments, certain aspects of the vehicle-based process illustrated inFIG. 8, may be similar to the device-based process illustrated inFIG. 5.
• At102, the method may be triggered. In certain embodiments, the method may be triggered as part of a routine start-up process of a vehicle. Alternatively, or in addition, the method may be triggered in response to certain vehicle operations and/or based on the occurrence of a particular vehicle event (e.g., determining that a device is within range of a short-range communication system in the vehicle). In further embodiments, the method may be triggered based on a determination by the vehicle and/or associated sensors (e.g., odometers, GPS sensors, and/or the like) that the vehicle is in a situation where policy enforcement is desirable. For example, the method may be triggered based on the vehicle determining that it is moving at or above a particular speed.
• At103, the vehicle may check for signals from a short-range communication system associated with a device in proximity to the vehicle and/or in proximity to a certain location within the vehicle. Checking for signals from a short-range communication system may result in a variety of outcomes. For example, no signal(s) may be received, signal(s) may be received that do not indicate that a device is in a policy-managed location in the vehicle, and/or signal(s) may be received that indicate that the device is in a policy-managed location in the vehicle (e.g., a driver's position or other sensitive position). Based on the received signal(s) (or lack thereof), at104 the vehicle may determine whether a device is proximate to and/or within a policy-managed location of the vehicle. If the device is in a policy-managed location of the vehicle,sensitive location information106 may be set to indicate that a device is in a policy-managed location at105. If a device is not in a policy-managed location, thesensitive location information106 may be set to indicate that the device is not in a sensitive and/or policy-managed location at107. In further embodiments, if a device is not proximate to a policy-managed location but proximate to another known location, the known location may be included in thesensitive location information106 set at107 and/or stored or otherwise recorded in some other manner.
• In some embodiments, the vehicle policy management system may also take advantage of other indicators of mobile device usage in the vehicle. For example, during the normal operation of mobile communication devices, signals are emitted that can be detected by the vehicle as indicative of mobile device usage within the vehicle. By monitoring such signals, the vehicle may passively obtain information broadly indicating use of a mobile device in or around the vehicle, and/or that may be used to determine the approximate location of the device within the vehicle. For example, the vehicle's sensing system may contain one or more sensors capable of receiving cellular-band communications signals and thereby able to detect the presence of an active mobile device in proximity to the vehicle. Various characteristics of the received signal can be monitored and used as inputs to the vehicle policy management process. For example, if the vehicle is in motion, and the signal strength of the transmission does not vary substantially over a suitable length of time and/or between multiple sensors on the vehicle, then the vehicle information system may be able to conclude that the device is being used in the vehicle and is not in a nearby vehicle that is following in traffic. This may be particularly useful for passive monitoring applications such as for safety audits of fleet operations vehicles of a transportation company or service vehicles. By securely monitoring and reporting on the use of mobile devices while vehicles are in use, companies can use this information to help guide safety training efforts or as supporting data for negotiating insurance rates for their fleet operations. Depending on the sensitivity and resolution of the sensors and their arrangement within the vehicle, differential analysis of characteristics of the received signals can also be used as a means to more accurately narrow the range of possible location of operation of the device within the vehicle (e.g., strength, timing, multi-path, interference, etc.). Although the foregoing example illustrated the use of these techniques in the context of a wide-area network technology, the passive data collection techniques can also be used with shorter-range communications as well, such as but not limited to on-board Wi-Fi networks, etc. Passive data collection techniques generally yield less detailed information about the use of the device (e.g., whether the keyboard is active, etc.), however, in some embodiments vehicles may use such passively obtained environment data in lieu of, or in addition to, active short range communications to determine sensitive location information.
• Referring once again toFIG. 8, after thesensitive location information106 has been set, the method may proceed to108 where the vehicle may wait for a certain delay time and/or for receipt of a re-detection trigger, causing the vehicle to re-check the status of the sensitive location (e.g., whether a device is present in the sensitive location) on a periodic and/or an event-driven basis. In further embodiments,sensitive location information106 may be updated on an effectively continuous basis (e.g., without a delay time or re-triggering event). Consistent with embodiments disclosed herein,sensitive location information106 may be used in policy management and enforcement processes. For example, as discussed above, certain features and/or functions of a vehicle and/or a device may be temporarily disabled (or enabled and/or actuated) based on the status of thesensitive location information106 in accordance with policies. In addition tosensitive location information106, a device and a vehicle may exchange data that provides contextual information about the device and/or the vehicle and/or the status thereof. As discussed in more detail below, this contextual information may also be used in policy management and enforcement processes disclosed herein.
• FIG. 9 illustrates exemplary generation and distribution ofpolicy data109 to avehicle100 consistent with embodiments of the present disclosure.Policy data109 for avehicle100 may articulate and/or otherwise express or enable enforcement of one or more rules or conditions relating to the use and/or function of thevehicle100. For example,policy data109 may express, encode, and/or otherwise be used to facilitate the enforcement of, among other things, conditions relating to the vehicle100 (e.g., vehicle location-based conditions, conditions relating to the use of a device within the vehicle, etc.), actions associated with the one or more conditions (e.g., disabling a vehicle starter system), exceptions to actions, and/or the like.
• Policy data109 may be delivered to thevehicle100 in a variety of ways. In certain embodiments,policy data109 may be pre-set in a vehicle100 (e.g., by a vehicle manufacturer ordealer900 or the like). In further embodiments,policy data109 may be configurable via any suitable means or combination thereof. For example, in some embodiments,policy data109 may be set and/or configured by a user902a(e.g., an owner of thevehicle100, a parent of a driver of thevehicle100, an employer of a driver of thevehicle100, etc.) directly into thevehicle100 via one or more inputs (e.g., inputs associated with a telematics or an IVI system of the vehicle100). In further embodiments, a user902bmay deliverpolicy data109 to the vehicle via anetwork600. Although illustrated as being directly coupled tonetwork600, in some embodiments, thevehicle100 may communicate with thenetwork600 using a separate intermediary device in communication with the network (e.g., a data-enabled smartphone). In some embodiments, the separate device may itself be policy-managed consistent with embodiments disclosed herein.
• Policy data109 may be delivered to the vehicle from a variety of network-connectedentities602b-606,610,900. In certain embodiments, network-connected entities capable of deliveringpolicy data109 to avehicle100 may be the same and/or similar to the network-connected entities capable of delivery policy data to a device described above in reference toFIG. 6.
• In some embodiments,policy data109 may be delivered to avehicle100 in combination with an application downloaded to operate on a telematics and/or IVI system included in thevehicle100.Policy data109 may further be delivered to avehicle100 directly or via thenetwork600 by an insurance provider, a fleet manager or other supervising entity (e.g., parents of a driver of thevehicle100, an employer, etc.), vehicle manufacturers ordealers900, and/or other entities (e.g.,law enforcement agencies610 providing jurisdiction-specific policy data109).
• FIG. 10 illustrates a flow chart of an exemplary vehicle policy evaluation and enforcement process consistent with embodiments of the present disclosure. The illustrated method may be implemented in a variety of ways, including using software, firmware, hardware, and/or any combination thereof. The illustrated process may use one or more inputs including, without limitation,sensitive location information106,policy data109, sensed and/or receiveddata113, and/or contextual device orvehicle data114. It will be appreciated that in other embodiments other combinations of these or other inputs may be used.
• Sensitive location information106 may include an indication as to whether one or more devices are located within a sensitive or policy-managed location of a vehicle. For example, thesensitive location information106 may indicate if a device is within and/or proximate to a driver's position in a vehicle.Policy information109 may include information regarding one or more conditions used to evaluate whether an action should occur, actions associated with the conditions, exceptions to the actions, and/or the like. Sensed and/or receiveddata113 may include, without limitation, data that is generated by vehicle sensors (e.g., odometers, accelerometers, GPS monitors, NFC tags, etc.) and/or data received by third parties.Contextual data114 may include information received from a device or part of the vehicle over a short-range communications system or other means that, among other things, specifies information about the device or vehicle status or other information that is sensed by the device and/or vehicle.
• At110, the vehicle policy evaluation and enforcement process may be triggered. In certain embodiments, the method may be triggered as part of a routine start-up process of a vehicle and/or by a change in any ofinputs106,109,113, and/or114. Alternatively, or in addition, the method may be triggered in response to certain vehicle operations and/or based on the occurrence of a particular vehicle event (e.g., determining that a device is within range of a short-range communication system in the vehicle). In further embodiments, the method may be triggered based on a determination by the vehicle and/or associated sensors (e.g., odometers, GPS sensors, and/or the like) that the vehicle is in a situation where policy enforcement is desirable. For example, the method may be triggered based on the vehicle determining that it is moving at or above a particular speed.
• At111, contextual information used for policy evaluation decisions may be read or sensed. At112, policy logic that acts upon and/or is articulated inpolicy data109 may be evaluated. As illustrated, this evaluation may be based, at least in part, oninputs106,109,113,114. For example, a simple policy may specify that if thesensitive location information106 indicates that a device is in a sensitive and/or policy-managed location, a certain feature of the vehicle should be disabled (e.g., a starter system of the vehicle, the ability of the vehicle to exceed a certain speed, etc.). At115, it may be determined whether an action is required based on the result of the policy evaluation at112. If an action is required, the action may be performed at116. For example, in certain embodiments, a policy-enforced action may specify that certainvehicle system parameters117 are to be set in a specific way (e.g., parameters disabling certain vehicle features, parameters limiting the ability of the vehicle to exceed a specific speed, parameters causing an audible warning sound, etc.). If no action is required, the process may proceed to118.
• At118, if necessary,vehicle system parameters117 may be set to default values and/or conditions and/or values or conditions that reflect a current state of the vehicle. For example, if a feature has been previously disabled because of a policy determination, it may need to be reset if the policy is later re-evaluated and the action disabling the feature is no longer triggered. In certain embodiments, reset processes performed at118 may be integrated into policy evaluation andenforcement steps112,115, and/or116.
• At119, the process may wait for a certain delay time and/or for receipt of a re-evaluation trigger before restarting the policy evaluation and enforcement steps. A user may wish to use a vehicle in a normal manner without any policy-enforced encumbrances after thesensitive location information106 or other information about the device and/or the vehicle has changed. Accordingly, in some embodiments, the process illustrated inFIG. 10 may be repeated as soon as is practical (e.g., following a delay time and/or the receipt of a re-evaluation trigger). Upon waiting the delay time and/or for receipt of the re-evaluation trigger, the process can be repeated, possibly with updatedinputs106,109,113,114 resulting in updated actions or a reset of vehicle system parameters.
• FIG. 11 illustrates exemplary condition-based policy enforcement actions consistent with embodiments of the present disclosure. In certain embodiments, vehicle and/or device policies may be applied based on certain temporal and/or environmental factors. For example, a first policy may be applied if a vehicle is in cloudy conditions, whereas a second policy may be applied if a vehicle is in sunny conditions. Similarly, as illustrated inFIG. 11, policies may be applied based on a time of day. For example, a policy associated with avehicle100 may specify that if a device is used in a policy-managed location in thevehicle100 during daylight driving conditions, a first action may be enforced (e.g., flashing oneheadlight1100 and/ortaillight1102 in a particular pattern, flashing hazard lights, etc.). Similarly, the policy may specify that if a device is used in a policy-managed location in thevehicle100 during nighttime driving conditions, a second action may be enforced (e.g., flashing bothheadlights1100 and/ortaillights1102 in a particular pattern, dimming vehicle lights in a particular pattern, flashing hazard lights, etc.). In certain embodiments, the different actions (e.g., the first and second actions) may be applied independent of time of day, but instead applied based on whether the vehicle'sheadlights1100 and/ortaillights1102 are on or off at the time the policy is enforced. It will be appreciated thatFIG. 11 is intended for purposes of illustration, not limitation, and that any other suitable policy could be specified and enforced.
• FIG. 12 illustrates exemplary generation and distribution ofpolicy data109,209 by a supervisingentity1200 to adevice200 and avehicle100 consistent with embodiments of the present disclosure. As discussed above in reference toFIG. 6 andFIG. 9, various entities may provide policy data tovehicles100 anddevices200. As illustrated inFIG. 12, certain of these entities may be a supervisingentity1200. A supervisingentity1200 may include a parent, an employer (e.g., a public transit authority), a fleet manager, an insurance provider, and/or any other interested party or entity.
• As an example, a safety-concerned parent who wants to ensure a child operates avehicle100 safely may distributepolicy data209 to a child'sdevice200 andpolicy data109 to thevehicle100. The distributedpolicy data109,209 may be used to enforce vehicle and device-based policies respectively consistent with the systems and methods of the present disclosure. For example,policy data209 may be delivered to a child'sdevice200 that specifies that thedevice200 must be set to a safe mode whenever thedevice200 determines it is being used in a policy-managed location in thevehicle100. Similarly,policy data109 may be delivered to thevehicle100 specifying that whenever adevice200 is used in policy-managed location in thevehicle100, such use is logged by thevehicle100.
• In some embodiments,policy data109,209 may include information that allows thevehicle100 to identify itself to thedevice200 and/or thedevice200 to identify itself to thevehicle100. Such identification information may include information specified by the vehicle or device user or administrator, or any other suitable information. In certain embodiments, such identification may provide a measure of security. For example, information used to authenticate thedevice200 and/or thevehicle100 may reduce the likelihood of malicious tampering with thedevice200 or thevehicle100. For example, a policy associated withvehicle100 might indicate that certain actions (e.g., disabling certain vehicle functions like starting the engine in response to the detection of a device being used in a sensitive location) can be performed only if the device associated with the action has been authenticated.
• FIG. 13 illustrates exemplary information used in a device-based policy management and enforcement decision consistent with embodiments of the present disclosure. As discussed above in reference toFIG. 7, adevice200 may usepolicy data209 and/or various sensed and/or receiveddata213 in evaluating and enforcing policies that make use of and/or are articulated in thepolicy data209. For example, thedevice200 may enforcepolicy data209 that encodes or otherwise parameterizes a condition that when thedevice200 is proximate to a driver's position in a vehicle, an action such as disabling a distracting phone feature (e.g., a text messaging application or the like) should be performed.
• Policies articulated inpolicy data209 may further be conditioned on sensed and/or receiveddata213 including, for example, an operational mode of the device. For example, thedevice200 may enforce a policy specifying a condition that when thedevice200 is proximate to a driver's position in a vehicle and is not in a “voice-control only” mode, thedevice200 should perform an action including switching itself to the “voice-control only” mode. It will be appreciated that any other suitable conditions, actions, and/or exceptions could also (or instead) be enforced by thedevice200.
• FIG. 14 illustrates exemplary information used in a vehicle-based policy management and enforcement decision consistent with embodiments of the present disclosure. As discussed above in reference toFIG. 10, avehicle100 may usepolicy data109 and/or various sensed and/or receiveddata113 in evaluating and enforcing policies. Avehicle100 may use sensitive position location information indicating whether devices are proximate to policy-managed locations in thevehicle100 and/or other sensed and/or receiveddata113 in evaluating and enforcing policies. For example, thevehicle100 may enforce a policy specifying a condition that when a device is proximate to a driver's position in thevehicle100 and the vehicle is moving faster than 1 MPH, an action such as lighting a warning indicator should be performed. Similarly, thevehicle100 may enforce a policy articulated inpolicy data109 specifying a condition that when a device is proximate to a driver's position in thevehicle100 and the vehicle is not in park (e.g., the drivetrain is engaged), a warning signal may be sounded in thevehicle100. It will be appreciated that any other suitable conditions, actions, and/or exceptions may also (or instead) be enforced by thevehicle100.
• FIG. 15 illustratesexemplary vehicle sensors1500 that can be used in policy evaluation and enforcement processes consistent with embodiments of the present disclosure.Vehicle sensors1500 may provide a variety of sensor information to avehicle information system1502. Vehicle sensors may include, without limitation, speedometers, motion sensors, short-range communications sensors/systems, parking brake sensors, transmission sensors (e.g., gear/park sensors), GPS sensors, airbag deployment sensors, crash sensors, driver and passenger seat occupant sensors, cellular-band communication sensors, and/or any other sensor providing sensed and/or supplemental/contextual vehicle information.
• Information provided byvehicle sensors1500 along with any additional information that is available to thevehicle information system1502 may be provided to a vehiclepolicy evaluation subsystem1504 configured to perform policy management, evaluation, and enforcement operations. Vehiclepolicy evaluation subsystem1504 may use this information, at least in part, to make policy enforcement decisions directing avehicle control subsystem1506 to take certain conditioned actions. For example, based on a policy enforcement decision, vehiclepolicy evaluation subsystem1504 may directvehicle control system1506 to prevent the drivetrain of the vehicle from being engaged and/or cause lights of the vehicle to flash in a particular pattern. Information provided byvehicle sensors1500 may further be provided to a short rangedevice communication subsystem1508 for communication to devices operating within the vehicle as supplemental and/or contextual vehicle data.
• FIG. 16 illustrates exemplarysupplemental device data220 that can be used in policy evaluation and enforcement processes consistent with embodiments of the present disclosure. Devices and vehicles may exchange supplemental data with each other, thereby allowing for richer more context-sensitive policies to be evaluated and enforced. For example, as illustrated,supplemental device data220 may be communicated to avehicle100 by adevice200.Supplemental device data220 may include, without limitation, device status information (e.g., power status, screen status, keyboard status, data services status, etc.), GPS data and/or other location information, motion sensor information (e.g., accelerometer data), device mode information (e.g., “airplane mode”, “car mode”, “voice control only mode”, etc.), information specific to certain applications executing on thedevice200, device or owner specific policy information, and/or the like. It will be appreciated that various other types ofsupplemental device data220 could also be used.
• FIG. 17 illustrates exemplarysupplemental vehicle data120 that can be used in policy evaluation and enforcement processes consistent with embodiments of the present disclosure. As illustrated,supplemental vehicle data120 may be communicated to adevice200 by avehicle100.Supplemental vehicle data120 may include, without limitation, vehicle status information (e.g., power status, powertrain status, brake status, etc.), sensor information (e.g., motion sensor data, speedometer data, crash sensor data, etc.), driver and/or occupant seat indicator information, information specific to certain applications executing on thevehicle100, vehicle or owner specific policy information, and/or the like. It will be appreciated that various other types ofsupplemental vehicle data120 could also be used.
• FIG. 18 illustrates exemplary sharing of contextual vehicle anddevice data214,114 consistent with embodiments of the present disclosure.Contextual vehicle data214, which may be used in embodiments of the policy management, evaluation, and enforcement processes disclosed herein, may comprise some or all ofsupplemental vehicle data120 provided to adevice200 from avehicle100. As illustrated,supplemental vehicle data120 may be communicated to thedevice200 ascontextual vehicle data214 using short-range communication subsystem processes1802,1800 respectively included in thevehicle100 and thedevice200.
• Contextual device data114, which may be used in embodiments of the policy management, evaluation, and enforcement processes disclosed herein, may comprise some or all ofsupplemental device data220 provided to avehicle100 from adevice200. As illustrated, thesupplemental device data220 may be communicated to thevehicle100 ascontextual device data114 using short-range communication subsystem processes1800,1802 respectively included in thedevice200 and thevehicle100.
• FIG. 19 illustrates exemplary policy evaluation and enforcement by avehicle100 consistent with embodiments of the present disclosure. As illustrated, policy evaluation and enforcement decisions by thevehicle100 may be based, among other things, onpolicy data109, sensed and/or receiveddata113, and/orcontextual device data114 communicated to thevehicle100 by adevice200. Thevehicle policy data109 may specify and/or otherwise enable enforcement or performance of one or more conditions, actions based on the conditions, and/or exceptions to the actions. For example, as illustrated, thepolicy data109 may specify conditions that if a driver or operator position in thevehicle100 includes adevice200, if thevehicle100 is not in park, and if the screen of thedevice200 is activated (e.g., based on contextual device data114), a safety warning buzzer should be sounded. Thepolicy data109 may also, however, specify an exception indicating that the safety warning buzzer should not be sounded if a crash sensor of thevehicle100 has detected a possible crash, or if airbags in thevehicle100 have been deployed. In this manner, if a driver of thevehicle100 is involved in an accident and trapped in the driver seat of thevehicle100, the driver may use thedevice200 to call for help. Likewise, if thedevice200 is being operated in proximity to the driver's seat, but thevehicle100 is in a safe state (e.g., park), thedevice200 can be enabled for use without compromising safety.
• Thepolicy data109 may further specify conditions that if a driver or operator position in thevehicle100 includes adevice200 and if a text message application on the device is activated, one headlight should be dimmed or brightened to warn oncoming traffic of a possible distracted driver. However, if the mobile device is in a “voice control only” mode, then dimming or brightening the headlight should not occur as using thedevice200 in the “voice control only” mode may not compromise safety. It should be appreciated that the various inputs used in policy evaluation and enforcement as well as the various conditions, actions, and exceptions illustrated inFIG. 19 are to be viewed as examples of possible inputs and/or policy conditions, actions, and exceptions, as many other possible inputs and/or policy conditions, actions, and exceptions may be used in accordance with the systems and methods disclosed herein.
• FIG. 20 illustrates exemplary policy evaluation and enforcement by adevice200 consistent with embodiments of the present disclosure. As illustrated, policy evaluation and enforcement decisions by thedevice200 may be based, among other things, onpolicy data209, sensed and/or receiveddata213, and/orcontextual vehicle data214 communicated to thedevice200 by avehicle100. Thedevice policy data209 may specify and/or otherwise enable enforcement or performance of one or more conditions, actions based on the conditions, and/or exceptions to the actions. For example, as illustrated, thepolicy data209 may specify conditions that if adevice200 is in proximity to a driver's location in thevehicle100 and thevehicle100 is not in park (e.g., based on contextual vehicle data214), a keyboard interface of thedevice200 should be disabled. Thepolicy data209 may also, however, specify an exception indicating that the keyboard interface should not be disabled if a crash sensor of thevehicle100 has detected a possible crash or if airbags in thevehicle100 have been deployed. In this manner, if a driver of thevehicle100 is involved in an accident and trapped in the driver seat of thevehicle100, the driver may use thedevice200 to call for help. Likewise, if thedevice200 is being operated in proximity to the driver's seat, but thevehicle100 is in a safe state (e.g., park), thedevice200 can be enabled for use without compromising safety.
• Thepolicy data209 may further specify conditions that if adevice200 is being used in thevehicle100 and seat occupant sensors in thevehicle100 indicate that the only occupant is in the driver's position, text messaging functionality of thedevice200 should be disabled. However, if a crash sensor of thevehicle100 has detected a possible crash, airbags in thevehicle100 have been deployed, or thevehicle100 is travelling less than1 mile per hour, the text messaging functionality should not be disabled as thedevice200 may be used under these conditions without compromising safety. It should be appreciated that the various inputs used in policy evaluation and enforcement as well as the various conditions, actions, and exceptions illustrated inFIG. 20 are to be viewed as examples of possible inputs and/or policy conditions, actions, and exceptions, as many other possible inputs and/or policy conditions, actions, and exceptions may be used in accordance with the systems and methods disclosed herein.
• FIG. 21 illustrates data distribution to and fromthird parties606,612,2100 that may be used in policy evaluation and enforcement processes consistent with embodiments of the present disclosure. Third parties may include apolicy distribution service606, alaw enforcement agency612, a geographical and/or contextual information service (e.g., a telematics service provider)2100, and/or any other third party or entity. As illustrated, adevice200 may communicate GPS orlocation data221 to one or morethird parties606,612,2100 vianetwork600. Thedevice200 may receivedata222. The receiveddata222 may contain policy information. For example, the policy information might reflect the laws or regulations of a jurisdiction associated with the GPS orlocation data221 and/or contextual data that may be used as inputs to an already existing policy (e.g., indications that thedevice200 is within a no texting zone location or a required hands free operation zone or the like). Avehicle100 may exchange GPS orlocation data121 and/or receiveddata122 to/from one or morethird parties606,612,2100 vianetwork600 similarly.
• FIG. 22 illustrates exemplary device andvehicle actions2200,2202 in response to policy evaluation and enforcement decisions consistent with embodiments of the present disclosure. As illustrated,device actions2200 may relate to certain functions, applications, or operating modes of a device.Device actions2200 may further include actions relating to auto and auto-reply messaging, data logging, audible and/or visual indications, and/or the like.Vehicle actions2202 may relate to certain functions, applications, or operating modes of a vehicle.Vehicle actions2202 may further include actions relating to audible and/or visional indications, data logging and reporting, external communication messaging, and/or the like. It should be appreciated that the various device andvehicle actions2200,2202 illustrated inFIG. 22 are to be viewed as illustrative and not exhaustive, as many other possible device andvehicle actions2200,2202 may be used in accordance with the systems and methods disclosed herein.
• FIG. 23 illustrates various exemplary credentials for providing secure policy generation, management, and enforcement consistent with embodiments of the present disclosure. Particularly,FIG. 23 illustrates various techniques that can be used to help guard againstdevices200 and/orvehicles100 being compromised by malicious attacks. As illustrated, athird party2300 may communicatepolicy data109,209 respectively to avehicle100 and adevice200. In certain embodiments, communicatedpolicy data109,209 may include one or moretrusted credentials123,223, that may be used in securing and/or authenticatingpolicy data109,209 and/or other information communicated by thethird party2300. In certain embodiments, thecredentials123,223 may comprise any suitable security and/or authentication information including, for example, digital keys, shared secrets, digital certificates, digital signatures, and/or the like. The policy management, evaluation, and enforcement systems and methods disclosed herein may perform verification and/or authentication of receivedpolicy data109,209 and/or other information such that policies are only enforced if thevehicle100 and/ordevice200 determine that communicated policies are trusted.
• Communication between thedevice200 and thevehicle100 may use similar secure and trusted communication techniques. In certain embodiments, identification information may be securely communicated between thedevice200 and/or thevehicle100 that may be further used in evaluating and enforcing policies (e.g., using identification information to properly log which delivery driver is in a shared truck and/or which child in a shared family car is using a device in an unsafe manner, etc.). In further embodiments,policy data109,209 may be digitally signed and/or encrypted, and the software and/or systems used to enforce the policy data may be secured (e.g., using any suitable tamper-resistance and/or other security techniques or technologies), thereby mitigating the potential for tampering withpolicy data109,209 (e.g., by a teenager or employee that wishes to override policies set by their parent or employer, etc.).
• FIG. 24 illustrates anexemplary system2400 that may be used to implement embodiments of the systems and methods disclosed herein.System2400 may, for example, comprise a computing device such as smartphone, tablet computer, personal computer and/or a system included in a vehicle that may perform the policy management, evaluation, and/or enforcement operations disclosed herein. As illustrated inFIG. 24, the system2400 may include: a processing unit2402; system memory2404, which may include high speed random access memory (“RAM”), non-volatile memory (“ROM”), and/or one or more bulk non-volatile computer-readable storage mediums (e.g., a hard disk, flash memory, etc.) for storing programs and other data for use and execution by the processing unit2402; one or more ports and/or interfaces (e.g., a wired or wireless interface)2406 for interfacing with associated sensor(s)2412; one or more ports or interfaces2407 for interfacing with removable memory2408 that may, for example, include one or more memory cards, diskettes, optical storage mediums, flash memory, thumb drives, USB dongles, compact discs, DVDs, etc. and/or other computer-readable storage mediums; a network interface2410 for communicating with other systems via one or more network connections600 using one or more communication technologies; a user interface2414 that may include a display and/or one or more input/output devices such as, for example, a touchscreen, a keyboard, a mouse, a track pad, and the like; and one or more busses2416 for communicatively coupling the elements of the system2400.
• In some embodiments, thesystem2400 may, alternatively or in addition, include a secure processing unit (“SPU”)2418 that is protected from tampering by a user ofsystem2400 or other entities by utilizing secure physical and/or virtual security techniques. AnSPU2418 can help enhance the security of sensitive operations such as trusted credential and/or key management, privacy and policy management, and other aspects of the systems and methods disclosed herein. In certain embodiments, theSPU2418 may operate in a logically secure processing domain and be configured to protect and operate on secret information. In some embodiments, theSPU2418 may include internal memory storing executable instructions or programs configured to enable to theSPU2418 to perform secure operations. For example, in some embodiments anSPU2418 such as described in commonly-assigned U.S. Pat. No. 7,430,585 (“the '585 patent”) and/or U.S. Pat. No. 5,892,900 (“the '900 patent”) can be used.
• The operation of thesystem2400 may be generally controlled by aprocessing unit2402 and/or anSPU2418 operating by executing software instructions and programs stored in the system memory2404 (and/or other computer-readable media, such as removable memory2408). Thesystem memory2404 may store a variety of executable programs or modules for controlling the operation of thesystem2400. For example, thesystem memory2404 may include an operating system (“OS”)2420 that may manage and coordinate, at least in part, system hardware resources and provide for common services for execution of various applications, and a policy management and evaluation module, program, orapplication2428 configured to implement policy management, evaluation, and enforcement functionality. Thesystem memory2404 may further include, without limitation,communication software2422 configured to enable in part communication within and by thesystem2400, applications2424 (e.g., media applications), and/orpolicy data2426.
• In certain embodiments, the systems and methods described herein could, for example, be used in connection with security and/or digital rights management (“DRM”) technologies such as those described in commonly assigned, co-pending U.S. patent application Ser. No. 11/583,693, filed Oct. 18, 2006, and published as Publ. No. 2007/0180519 A1 (“the '693 application”), U.S. Pat. No. 5,892,900, and U.S. Pat. No. 6,157,721 (“the '721 patent”), and/or service orchestration or DRM technologies such as those described in commonly assigned U.S. Pat. No. 8,234,387 (“the '387 patent”)(the contents of the '693 application and the '585 patent, '900 patent, '721 patent, and '387 patent hereby being incorporated by reference in their entireties). For example, DRM software and systems such as those described in the '693 application and/or the '900 patent could be used in some embodiments to facilitate the expression and enforcement of policies of the type described herein. In will be appreciated, however, that any other suitable security and/or policy-enforcement software, systems, and/or mechanisms could be used alternatively or in addition.
• The systems and methods disclosed herein are not inherently related to any particular computer, electronic control unit, or other apparatus and may be implemented by a suitable combination of hardware, software, and/or firmware. Software implementations may include one or more computer programs comprising executable code/instructions that, when executed by a processor, may cause the processor to perform a method defined at least in part by the executable instructions. The computer program can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. Further, a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network. Software embodiments may be implemented as a computer program product that comprises a non-transitory storage medium configured to store computer programs and instructions, that when executed by a processor, are configured to cause the processor to perform a method according to the instructions. In certain embodiments, the non-transitory storage medium may take any form capable of storing processor-readable instructions on a non-transitory storage medium. A non-transitory storage medium may be embodied by a compact disk, digital-video disk, hard disk drive, a magnetic tape, a Bernoulli drive, a magnetic disk, a punch card, flash memory, integrated circuits, or any other non-transitory digital processing apparatus or memory device.
• Example Usage Scenarios
• The following examples are provided as illustrative uses of embodiments of the inventive body of work, and are not intended to be an exhaustive list or otherwise limiting in any way of the systems and methods described herein.
• Parental Control
• With high rates of vehicle accidents and high propensity for driving while distracted among teens, parents of teens may be interested in ways to mitigate the risks resulting from equipping their children with mobile phones and keys to a car. Teens are frequently given the use of a phone or a car, but often these items or the associated mobile phone service account are owned or controlled by their parents. In accordance with some embodiments of the systems and methods described herein, parents can be enabled to configure their child's phone and/or vehicle to obey policies that they choose.
• In an illustrative example, the mobile phone operator offers a service to its customers to allow devices associated with an account to be remotely configured. After logging on to her account, a mother selects the mobile devices of her son and daughter and applies a configuration policy to each of these phones. Via the cellular network, each mobile phone is configured with a policy as to how it shall behave if it detects it is within a policy managed location in her car. Alternatively, or in addition, the parent could configure the phone simply by downloading onto each of the phones an app designed for this purpose from an app store, and entering his or her policy choices via the app's user interface.
• In this example, the parent selects a relatively unobtrusive policy that whenever the device detects that it is in a policy managed location, the device must (a) automatically switch into “voice-only” mode, and (b) if the vehicle is in motion, all text messages received will be automatically responded to as “I am driving now, I'll get back to you later.”
• The parent also configures her car to detect devices operating within the driver seat, automatically pair with them and exchange data. In this example, the parent's car is equipped with device sensing and communication capabilities described elsewhere herein. In some embodiments, these capabilities could come pre-installed when the car is purchased, or they could be installed after purchase by the parent or a technician. For example, the parent could purchase a kit containing one or more NFC tag stickers, and place these at appropriate locations in the car, then download an associated app onto her family's phones to facilitate pairing therewith and processing received data.
• Returning to the example under consideration, the next day the parent's son enters the car and sits in the driver's seat and her daughter and her friends sit in the passenger seats. After turning on the car, the son's phone immediately detects that it is in a field created by at least one NFC antenna located in close proximity to the driver seat. The device establishes a coupled link to the vehicle and receives data indicating that it is in a policy-managed location. The device executes its policy and switches to voice-only mode. During the drive, the son receives a text message from a friend. Since the device still senses that it is in a policy managed location, and the information received from the vehicle indicates that it is in motion, the text message receives an automatic response as specified by the policy. Meanwhile the daughter who is also riding in the car and carrying a phone that is similarly configured is permitted to use the full features of her phone, because her phone is not located within the policy managed location of the vehicle.
• As an added safety measure, an additional data item or shared secret may be exchanged between the vehicle and the devices that is relevant for policy enforcement. To prevent her son's or daughter's phones from being disabled by a malicious or rogue installation other than in her vehicle, the mother could also optionally configure the policy with an identifier that must also be present for the policy to be enforced. For example, when configuring the mobile phone policy, she could also enter the vehicle identification number(s) for which the policy applies. When the device interacts with the vehicle information system, the device can request the vehicle identifier and use this as an additional determining factor in enforcing the policy. As an alternative, a shared secret could be entered into both the policy and the vehicle to achieve a similar result.
• Insurance Monitoring/Verification
• As distracted driving is a leading cause of motor vehicle accidents, and insurance companies often must bear the financial cost associated with these accidents, these organizations have a significant interest in the safety of their customers and the vehicles they insure. As an incentive for safe driving practices, an insurance company can offer lower rates or rebates to customers that can submit verifiable proof that insured vehicles are not being used by drivers who are operating mobile devices while in the driver position of the vehicle. Using the technologies described herein, an insurance company can benefit from the collection of usage information about its insured drivers and/or insured vehicles. In one embodiment, the insurance company can offer an application (or “app”) that can be downloaded or installed on the vehicle's on-board automotive electronics system (e.g., extensible navigation/multimedia system, an Android™-based computer system, or the like). Using interfaces with the vehicle's electronic sensors and/or the vehicle information system, the app can register to receive data corresponding to use of devices (e.g. a mobile phone) in the policy-managed location. This data can be direct sensor data (which the app itself can analyze to determine policy actions), or it can be data that has been at least partially pre-processed by the vehicle's information system that indicates that a device is being used in a policy managed location (e.g., a warning indicator that the vehicle has activated upon determining that a device is being operated in the driver position).
• In the latter case, the automotive information system may use one or more of the techniques described herein (e.g., near field communication with strategically located antennas in the driver compartment, comparative signal analysis of radio transmissions associated with one or more vehicle mounted antennas, seat pressure indicators, vehicle speed indicators, drivetrain status, etc.) in part or in combination to determine whether a mobile device is being operated in a driver or operator position. Upon making this determination, the vehicle information system can apply its own configured policy actions (such as sounding a warning buzzer or lighting a warning indicator, etc.) and makes data related to this determination available to apps that are loaded on the system. The insurer's app in this example receives the determination data and applies its own policy as to whether to take an action in response. The application's decision as to whether take action can be based solely on the vehicle's determination data or in combination with other available environmental or vehicle data. For purposes of this example, the insurer's app uses the vehicle's determination that there is a device operating in the driver position in combination with data indicating whether the vehicle is in motion. Since the insurer is interested in logging only unsafe actions, the app is configured to log data associated with the event only when there is a determination that there is a device being used in the driver position and the vehicle is in motion. In accordance with its policy, the app collects additional event data such as the time and date, vehicle speed, and duration of usage in the unsafe condition. To ensure that the log information can be uniquely tied to a particular device, the app reads vehicle identification or customer identification information and also associates it with the log data. To ensure that that the data is not tampered with after collection, the app may optionally encrypt and/or digitally sign the collected log information, the associated identification information, and a random nonce before sending to the insurer's data center. Depending on the available equipment of the vehicle, the data may be sent directly via the vehicle's on-board cellular connection, a wireless network connection, a tethered connection to a nearby cellular phone, USB download, or other suitable means.
• Employer-managed Vehicle and Phone
• A service company finds it convenient and effective to provide their employees with mobile phones to stay in contact with their central dispatch while they complete their service routes. To reduce their liability risk and ensure their employees' safety, the company wishes to adopt strict measures on the use of these phones while operating company service vehicles. Using techniques described herein, the company configures their service vehicles with a policy that prevents the vehicle from being engaged into drive if a phone is in the driver seat and is not in a safe driving operating mode. When a driver enters the vehicle, her phone interacts with a short range communications channel in the vehicle and establishes a connection. Upon establishing the connection, the vehicle queries the phone for information about its operating state. In response, the device communicates device status information (such as keypad lock state, display state, etc.). If the vehicle determines that the keyboard and/or screen are in an unlocked state, it will enforce the policy and refuse to engage the drive of the vehicle.
• As an added safety measure, the company is also concerned that some employees may attempt to unlock and use their mobile device while driving (after the drive has been engaged). To handle these instances, the company sets a vehicle policy to periodically poll for the device status. If an unsafe device status is detected while the vehicle sensors indicate that the vehicle is in motion, the service vehicle's hazard lights will be activated, and an event will be captured and logged for later review.
• Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the systems and methods described herein. Further, the policy management and enforcement systems and methods disclosed herein may be used in a variety of contexts that do not include vehicles. For example, without limitation, in certain embodiments, systems and methods disclosed herein may be used to manage and enforce policies associated with certain buildings or other locations. For example, policy management and enforcement systems and methods disclosed herein may be used to disable certain device features (e.g., audible ringtones, backlit screens, text messaging applications, etc.) when the device is proximate to a particular location (e.g., within a movie theater, a restaurant, and/or the like). Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims (20)

What is claimed is:

1. A method comprising:

receiving one or more short-range communication signals at a short range communication system included in a mobile device;

determining that the device is within a policy-managed location in a vehicle based on the short-range communication signals;

evaluating policy information, the policy information including one or more conditions relating to the policy-managed location in the vehicle, to determine one or more responsive device actions; and

implementing the one or more device actions on the device.

2. The method ofclaim 1, wherein the one or more device actions comprise disabling a feature of the device.

3. The method ofclaim 1, wherein the one or more device actions comprise disabling an application of the device.

4. The method ofclaim 1, wherein the one or more device actions comprise changing an operating mode of the device.

5. The method ofclaim 1, wherein the policy information further comprises one or more exceptions associated with the one or more conditions.

6. The method ofclaim 1, wherein the policy-managed location in the vehicle comprises a driver's seat location in the vehicle.

7. The method ofclaim 1, wherein the device comprises a mobile phone.

8. The method ofclaim 1, wherein the signals received by the short-range communication system included in the device are generated by a short-range communication system included in the vehicle.

9. The method ofclaim 1, wherein evaluating the policy information is further based on sensor information from one or more sensors included in the device.

10. The method ofclaim 1, wherein the method further comprises:

receiving contextual information from the vehicle,

wherein evaluating the policy information is further based on the contextual information.

11. A method comprising:

determining that a device is within a policy-managed location in the vehicle based on signals received by a short-range communication system included in the vehicle;

evaluating, using a policy management system in the vehicle, policy information, the policy information comprising one or more conditions relating to the policy-managed location in the vehicle, to determine one or more vehicle actions associated with the one or more conditions; and

implementing the one or more vehicle actions on the vehicle.

12. The method ofclaim 11, wherein the one or more vehicle actions comprise disabling a feature of the vehicle.

13. The method ofclaim 11, wherein the one or more vehicle actions comprise storing event information relating to the presence of the device within the policy-managed location in the vehicle.

14. The method ofclaim 11, wherein the one or more vehicle actions comprise providing one or more notifications.

15. The method ofclaim 14, wherein the one or more notifications comprise audible notifications.

16. The method ofclaim 14, wherein the one or more notifications comprise visual notifications.

17. The method ofclaim 11, wherein the policy information further comprises one or more exceptions associated with the one or more conditions.

18. The method ofclaim 11, wherein the policy-managed location in the vehicle comprises a driver's seat location in the vehicle.

19. The method ofclaim 11, wherein the method further comprises:

receiving sensor information from one or more sensors included in the vehicle,

wherein evaluating the policy information is further based on the sensor information.

20. The method ofclaim 11, wherein the method further comprises:

receiving contextual information from the device,

wherein evaluating the policy information is further based on the contextual information.

Images