Method and system for data optimization

Information

  • Patent Grant
  • 10515390
  • Patent Number
    10,515,390
  • Date Filed
    Wednesday, December 28, 2016
    7 years ago
  • Date Issued
    Tuesday, December 24, 2019
    5 years ago
Abstract
Embodiments can provide an intelligent vehicle that determines that the vehicle interior comprises multiple occupants; identifies the occupants; based on the driving behavior of the vehicle, creates a composite occupant profile associated with the group of plural occupants, the composite occupant profile comprising the identities of the plural occupants and group preferences for various vendor products or services; and, based on the composite occupant profile and received inputs from a user interface, an automatic vehicle location system, and a plurality of sensors in the vehicle, performs one or more actions, such as: (a) proposing one or more vendor products or services for the group of occupants; (b) publishing the vendor products or services selected by the group of occupants, via a social network, to associated or selected associates of the occupants in the group; and (c) presenting advertisement information from a vendor server associated with the proposed or selected vendor products or services to one or more of the occupants in the group.
Description
FIELD

The present disclosure is generally directed to vehicle systems, in particular, toward electric and/or hybrid-electric vehicles.


BACKGROUND

In recent years, transportation methods have changed substantially. This change is due in part to a concern over the limited availability of natural resources, a proliferation in personal technology, and a societal shift to adopt more environmentally friendly transportation solutions. These considerations have encouraged the development of a number of new flexible-fuel vehicles, hybrid-electric vehicles, and electric vehicles.


While these vehicles appear to be new they are generally implemented as a number of traditional subsystems that are merely tied to an alternative power source. In fact, the design and construction of the vehicles is limited to standard frame sizes, shapes, materials, and transportation concepts. Among other things, these limitations fail to take advantage of the benefits of new technology, power sources, and support infrastructure. In particular, the implementation of an artificially intelligent vehicle has lagged far behind the development vehicle subsystems.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows a vehicle in accordance with embodiments of the present disclosure;



FIG. 2 shows a plan view of the vehicle in accordance with at least some embodiments of the present disclosure;



FIG. 3 shows a plan view of the vehicle in accordance with embodiments of the present disclosure



FIG. 4 shows an embodiment of the instrument panel of the vehicle according to one embodiment of the present disclosure;



FIG. 5 is a block diagram of a computing environment associated with the embodiments presented herein;



FIG. 6 is a block diagram of a computing device associated with one or more components described herein;



FIG. 7 is a block of a computing environment associated with the embodiments presented herein;



FIG. 8 is block diagram of a computational system in a vehicle and associated with one or more components described herein;



FIG. 9 is a flow chart associated with one or more embodiments presented herein;



FIG. 10 is a flow chart associated with one or more embodiments presented herein;



FIG. 11 is a flow chart associated with one or more embodiments presented herein; and



FIG. 12 is a block diagram of a computing system associated with one or more components described herein.





DETAILED DESCRIPTION

Embodiments of the present disclosure will be described in connection with a vehicle, and in some embodiments, an electric vehicle, rechargeable electric vehicle, and/or hybrid-electric vehicle and associated systems.


Embodiments can provide an intelligent vehicle that determines that the vehicle interior comprises multiple occupants; identifies the occupants; based on the driving behavior of the vehicle, creates a composite occupant profile associated with the group of plural occupants, the composite occupant profile comprising the identities of the plural occupants and group preferences for various vendor products or services; and, based on the composite occupant profile and received inputs from a user interface, an automatic vehicle location system, and a plurality of sensors in the vehicle, performs one or more actions, such as: (a) proposing one or more vendor products or services for the group of occupants; (b) publishing the vendor products or services selected by the group of occupants, via a social network, to associated or selected associates of the occupants in the group; and (c) presenting advertisement information from a vendor server associated with the proposed or selected vendor products or services to one or more of the occupants in the group.


The intelligent vehicle can anticipate the needs of individual occupants and groups of occupants and thereby reduce fewer operator distractions, provide a more pleasurable driving experience, enable more effective interaction between vendors and mobile customers, and publish automatically specified vehicle-collected information to a social network associated with an occupant. The ability to create and effectively use composite or group profiles can further reduce the time required for the group to agree upon a course of action or other option, reduce disagreements among vehicle occupants, and filter out unacceptable possible courses of action or options from those presented to the group.



FIG. 1 shows a perspective view of a vehicle 100 in accordance with embodiments of the present disclosure. The electric vehicle 100 comprises a vehicle front 110, vehicle aft 120, vehicle roof 130, at least one vehicle side 160, a vehicle undercarriage 140, and a vehicle interior 150. In any event, the vehicle 100 may include a frame 104 and one or more body panels 108 mounted or affixed thereto. The vehicle 100 may include one or more interior components (e.g., components inside an interior space 150, or user space, of a vehicle 100, etc.), exterior components (e.g., components outside of the interior space 150, or user space, of a vehicle 100, etc.), drive systems, controls systems, structural components, etc.


Although shown in the form of a car, it should be appreciated that the vehicle 100 described herein may include any conveyance or model of a conveyance, where the conveyance was designed for the purpose of moving one or more tangible objects, such as people, animals, cargo, and the like. The term “vehicle” does not require that a conveyance moves or is capable of movement. Typical vehicles may include but are in no way limited to cars, trucks, motorcycles, busses, automobiles, trains, railed conveyances, boats, ships, marine conveyances, submarine conveyances, airplanes, space craft, flying machines, human-powered conveyances, and the like.


Referring now to FIG. 2, a plan view of an undercarriage vehicle 100 will be described in accordance with embodiments of the present disclosure. As provided above, the vehicle 100 may comprise a number of electrical and/or mechanical systems, subsystems, etc. The mechanical systems of the vehicle 100 can include structural, power, safety, and communications subsystems, to name a few. While each subsystem may be described separately, it should be appreciated that the components of a particular subsystem may be shared between one or more other subsystems of the vehicle 100.


The structural subsystem includes the frame 104 of the vehicle 100. The frame 104 may comprise one or more surfaces, connections, protrusions, cavities, mounting points, tabs, slots, or other features that are configured to receive other components that make up the vehicle 100. For example, the body panels 108, powertrain subsystem, controls systems, interior components, communications subsystem, and safety subsystem may interconnect with, or attach to, the frame 104 of the vehicle 100.


The frame 104 may attach or operatively engage one or more modular system and/or subsystems. Among other things, the frame can be attached to batteries, capacitors, power sources 208A, 208B, motors 212, engines, safety equipment, controllers, user interfaces, interiors exterior components, body panels 108, bumpers 216, sensors, etc., and/or combinations thereof.


The power system of the vehicle 100 may include the powertrain, power distribution system, accessory power system, and/or any other components that store power, provide power, convert power, and/or distribute power to one or more portions of the vehicle 100. The powertrain may include the one or more DC or AC electric motors 212 of the vehicle 100. The electric motors 212 are configured to convert electrical energy provided by a power source into mechanical energy to propel or otherwise provide a motive force for the vehicle 100.


In some embodiments, the vehicle 100 may include one or more drive wheels 220 that are driven by the one or more electric motors 212 and motor controllers 214. The powertrain may include one or more power transmission components, motor controllers 214, and/or power controllers that can provide a controlled output of power to one or more of the drive wheels 220 of the vehicle 100. The power transmission components, power controllers, or motor controllers 214 may be controlled by at least one other vehicle controller or computer system as described herein.


The power source 208 can include one or more energy storage systems comprising batteries or modules configured as a battery pack. The battery can be any type of battery for storing electrical energy, for example, a lithium ion battery, a lead acid battery, a nickel cadmium battery, etc. Further, the battery may include different types of power storage systems, such as, ionic fluids or other types of fuel cell systems. The energy storage systems may also include one or more high-capacity capacitors. The capacitors may be used for long-term or short-term storage of electrical energy.


The powertrain includes one or more power distribution systems configured to transmit power from the power source 208 to one or more electric motors 212 in the vehicle 100. The power distribution system may include electrical interconnections 228 and 232 in the form of cables, wires, traces, wireless power transmission systems, etc., and/or combinations thereof.


In some embodiments, the power distribution system may include an energy recovery system 236. This energy recovery system 236, or kinetic energy recovery system, may be configured to recover energy produced by the movement of a vehicle 100. The recovered energy may be stored as electrical and/or mechanical energy.


The vehicle 100 may include one or more safety systems. Vehicle safety systems can include a variety of mechanical and/or electrical components including, but in no way limited to, low impact or energy-absorbing bumpers 216A, 216B, crumple zones, reinforced body panels, reinforced frame components, impact bars, power source containment zones, safety glass, seatbelts, supplemental restraint systems, air bags, escape hatches, removable access panels, impact sensors, accelerometers, vision systems, radar systems, etc., and/or the like. In some embodiments, the one or more of the safety components may include a safety sensor or group of safety sensors associated with the one or more of the safety components. For example, a crumple zone may include one or more strain gages, impact sensors, pressure transducers, etc. These sensors may be configured to detect or determine whether a portion of the vehicle 100 has been subjected to a particular force, deformation, or other impact. Once detected, the information collected by the sensors may be transmitted or sent to one or more of a controller of the vehicle 100 (e.g., a safety controller, vehicle controller, etc.) or a communication device associated with the vehicle 100 (e.g., across a communication network, etc.).



FIG. 3 shows a plan view of the vehicle 100 in accordance with embodiments of the present disclosure. In particular, FIG. 3 shows a broken section 302 of a charging system 300 for the vehicle 100. The charging system 300 may include a plug or receptacle 304 configured to receive power from an external power source (e.g., a source of power that is external to and/or separate from the vehicle 100, etc.). Power received at the plug/receptacle 304 may be transferred via at least one power transmission interconnection 308. Electrical energy in the form of charge can be transferred from the external power source to the charge controller 224. As provided above, the charge controller 224 may regulate the addition of charge to at least one power source 208 of the vehicle 100 (e.g., until the at least one power source 208 is full or at a capacity, etc.).


In addition to the mechanical components described herein, the vehicle 100 may include a number of user interface devices. The user interface devices receive and translate human input into a mechanical movement or electrical signal or stimulus. The human input may be one or more of motion (e.g., body movement, body part movement, in two-dimensional or three-dimensional space, etc.), voice, touch, and/or physical interaction with the components of the vehicle 100. In some embodiments, the human input may be configured to control one or more functions of the vehicle 100 and/or systems of the vehicle 100 described herein. User interfaces may include, but are in no way limited to, at least one graphical user interface of a display device, steering wheel or mechanism, transmission lever or button (e.g., including park, neutral, reverse, and/or drive positions, etc.), throttle control pedal or mechanism, brake control pedal or mechanism, power control switch, communications equipment, etc.



FIG. 4 shows one embodiment of the instrument panel 400 of the vehicle 100. The instrument panel 400 of vehicle 100 comprises a steering wheel 410, a vehicle operational display 420 (e.g., configured to present and/or display driving data such as speed, measured air resistance, vehicle information, entertainment information, etc.), one or more auxiliary displays 424 (e.g., configured to present and/or display information segregated from the operational display 420, entertainment applications, movies, music, etc.), a heads-up display 434 (e.g., configured to display any information previously described including, but in no way limited to, guidance information such as route to destination, or obstacle warning information to warn of a potential collision, or some or all primary vehicle operational data such as speed, resistance, etc.), a power management display 428 (e.g., configured to display data corresponding to electric power levels of vehicle 100, reserve power, charging status, etc.), and an input device 432 (e.g., a controller, touchscreen, or other interface device configured to interface with one or more displays in the instrument panel or components of the vehicle 100. The input device 432 may be configured as a joystick, mouse, touchpad, tablet, 3D gesture capture device, etc.). In some embodiments, the input device 432 may be used to manually maneuver a portion of the vehicle 100 into a charging position (e.g., moving a charging plate to a desired separation distance, etc.).


While one or more of displays of instrument panel 400 may be touch-screen displays, it should be appreciated that the vehicle operational display may be a display incapable of receiving touch input. For instance, the operational display 420 that spans across an interior space centerline 404 and across both a first zone 408A and a second zone 408B may be isolated from receiving input from touch, especially from a passenger. In some cases, a display that provides vehicle operation or critical systems information and interface may be restricted from receiving touch input and/or be configured as a non-touch display. This type of configuration can prevent dangerous mistakes in providing touch input where such input may cause an accident or unwanted control.


In some embodiments, one or more displays of the instrument panel 400 may be mobile devices and/or applications residing on a mobile device such as a smart phone. Additionally or alternatively, any of the information described herein may be presented to one or more portions 420A-N of the operational display 420 or other display 424, 428, 434. In one embodiment, one or more displays of the instrument panel 400 may be physically separated or detached from the instrument panel 400. In some cases, a detachable display may remain tethered to the instrument panel.


The portions 420A-N of the operational display 420 may be dynamically reconfigured and/or resized to suit any display of information as described. Additionally or alternatively, the number of portions 420A-N used to visually present information via the operational display 420 may be dynamically increased or decreased as required, and are not limited to the configurations shown.



FIG. 5 illustrates a block diagram of a computing environment 500 that may function as the servers, user computers, or other systems provided and described herein. The environment 500 includes one or more user computers, or computing devices, such as a vehicle computing device 504, a communication device 508, and/or more 512. The computing devices 504, 508, 512 may include general purpose personal computers (including, merely by way of example, personal computers, and/or laptop computers running various versions of Microsoft Corp.'s Windows® and/or Apple Corp.'s Macintosh® operating systems) and/or workstation computers running any of a variety of commercially-available UNIX® or UNIX-like operating systems. These computing devices 504, 508, 512 may also have any of a variety of applications, including for example, database client and/or server applications, and web browser applications. Alternatively, the computing devices 504, 508, 512 may be any other electronic device, such as a thin-client computer, Internet-enabled mobile telephone, computer wearable, and/or personal digital assistant, capable of communicating via a network 510 and/or displaying and navigating web pages or other types of electronic documents. Although the exemplary computer environment 500 is shown with two computing devices, any number of user computers or computing devices may be supported.


Environment 500 further includes a network 510. The network 510 may can be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation SIP, TCP/IP, SNA, IPX, AppleTalk, and the like. Merely by way of example, the network 510 maybe a local area network (“LAN”), such as an Ethernet network, a Token-Ring network and/or the like; a wide-area network; a virtual network, including without limitation a virtual private network (“VPN”); the Internet; an intranet; an extranet; a public switched telephone network (“PSTN”); an infra-red network; a wireless network (e.g., a network operating under any of the IEEE 802.9 suite of protocols, the Bluetooth® protocol known in the art, and/or any other wireless protocol); and/or any combination of these and/or other networks.


The system may also include one or more servers 514, 516. In this example, server 514 is shown as a web server and server 516 is shown as an application server. The web server 514, which may be used to process requests for web pages or other electronic documents from computing devices 504, 508, 512. The web server 514 can be running an operating system including any of those discussed above, as well as any commercially-available server operating systems. The web server 514 can also run a variety of server applications, including SIP (Session Initiation Protocol) servers, HTTP(s) servers, FTP servers, CGI servers, database servers, Java servers, and the like. In some instances, the web server 514 may publish operations available operations as one or more web services.


The environment 500 may also include one or more file and or/application servers 516, which can, in addition to an operating system, include one or more applications accessible by a client running on one or more of the computing devices 504, 508, 512. The server(s) 516 and/or 514 may be one or more general purpose computers capable of executing programs or scripts in response to the computing devices 504, 508, 512. As one example, the server 516, 514 may execute one or more web applications. The web application may be implemented as one or more scripts or programs written in any programming language, such as Java™, C, C#®, or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming/scripting languages. The application server(s) 516 may also include database servers, including without limitation those commercially available from Oracle®, Microsoft®, Sybase®, IBM® and the like, which can process requests from database clients running on a computing device 504, 508, 512.


The web pages created by the server 514 and/or 516 may be forwarded to a computing device 504, 508, 512 via a web (file) server 514, 516. Similarly, the web server 514 may be able to receive web page requests, web services invocations, and/or input data from a computing device 504, 508, 512 (e.g., a user computer, etc.) and can forward the web page requests and/or input data to the web (application) server 516. In further embodiments, the server 516 may function as a file server. Although for ease of description, FIG. 5 illustrates a separate web server 514 and file/application server 516, those skilled in the art will recognize that the functions described with respect to servers 514, 516 may be performed by a single server and/or a plurality of specialized servers, depending on implementation-specific needs and parameters. The computer systems 504, 508, 512, web (file) server 514 and/or web (application) server 516 may function as the system, devices, or components described in FIGS. 1-5.


The environment 500 may also include a database 518. The database 518 may reside in a variety of locations. By way of example, database 518 may reside on a storage medium local to (and/or resident in) one or more of the computers 504, 508, 512, 514, 516. Alternatively, it may be remote from any or all of the computers 504, 508, 512, 514, 516, and in communication (e.g., via the network 510) with one or more of these. The database 518 may reside in a storage-area network (“SAN”) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to the computers 504, 508, 512, 514, 516 may be stored locally on the respective computer and/or remotely, as appropriate. The database 518 may be a relational database, such as Oracle 20i®, that is adapted to store, update, and retrieve data in response to SQL-formatted commands.



FIG. 6 illustrates one embodiment of a computer system 600 upon which the servers, user computers, computing devices, or other systems or components described above may be deployed or executed. The computer system 600 is shown comprising hardware elements that may be electrically coupled via a bus 604. The hardware elements may include one or more central processing units (CPUs) 608; one or more input devices 612 (e.g., a mouse, a keyboard, etc.); and one or more output devices 616 (e.g., a display device, a printer, etc.). The computer system 600 may also include one or more storage devices 620. By way of example, storage device(s) 620 may be disk drives, optical storage devices, solid-state storage devices such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable and/or the like.


The computer system 600 may additionally include a computer-readable storage media reader 624; a communications system 628 (e.g., a modem, a network card (wireless or wired), an infra-red communication device, etc.); and working memory 636, which may include RAM and ROM devices as described above. The computer system 600 may also include a processing acceleration unit 632, which can include a DSP, a special-purpose processor, and/or the like.


The computer-readable storage media reader 624 can further be connected to a computer-readable storage medium, together (and, optionally, in combination with storage device(s) 620) comprehensively representing remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing computer-readable information. The communications system 628 may permit data to be exchanged with a network and/or any other computer described above with respect to the computer environments described herein. Moreover, as disclosed herein, the term “storage medium” may represent one or more devices for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine readable mediums for storing information.


The computer system 600 may also comprise software elements, shown as being currently located within a working memory 636, including an operating system 640 and/or other code 644. It should be appreciated that alternate embodiments of a computer system 600 may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.


Examples of the processors 608 as described herein may include, but are not limited to, at least one of Qualcomm® Snapdragon® 800 and 801, Qualcomm® Snapdragon® 620 and 615 with 4G LTE Integration and 64-bit computing, Apple® A7 processor with 64-bit architecture, Apple® M7 motion coprocessors, Samsung® Exynos® series, the Intel® Core™ family of processors, the Intel® Xeon® family of processors, the Intel® Atom™ family of processors, the Intel Itanium® family of processors, Intel® Core® i5-4670K and i7-4770K 22 nm Haswell, Intel® Core® i5-3570K 22 nm Ivy Bridge, the AMD® FX™ family of processors, AMD® FX-4300, FX-6300, and FX-8350 32 nm Vishera, AMD® Kaveri processors, Texas Instruments® Jacinto C6000™ automotive infotainment processors, Texas Instruments® OMAP™ automotive-grade mobile processors, ARM® Cortex™-M processors, ARM® Cortex-A and ARM926EJ-S™ processors, other industry-equivalent processors, and may perform computational functions using any known or future-developed standard, instruction set, libraries, and/or architecture.


With reference to FIG. 7, the vehicle 120 is in wireless communication, via network 510, with one or more vendor server(s) 808A-N, a map database manager 812 and associated map database 816, and a vehicle database manager 820 and associated vehicle database 824.



FIG. 7 is a particular implementation of the computing environment of FIG. 5. The vendor server(s) 808A-N are each associated with a corresponding vendor location, such as a brick-and-mortar storefront or office building and communicate with the vehicle 120, map database manager 2012, and vehicle database manager 820 regarding information related to the respective vendor. For example, the vendor server 808 can provide to the vehicle 120 and/or map database manager 812 information related to the respective vendor and its product and/or service offerings, such as hours of operation, available product and/or service types, prices, brands, specifications, requirements, availabilities, advertising, and the like, sales specials and other price discounts and special offers and terms and conditions, referral percentages, fees, or payments for referring the vendor to an occupant of the vehicle 120, and other data element(s) and further data fields, such as geographical location of the respective vendor location, and the like.


The map database manager 812 and map database 816 interact with an automatic vehicle location system 908 (discussed below) in the vehicle 120 to provide navigation or map output to the vehicle occupants.


The map database manager 812 stores and recalls spatial map information from the map database 816.


The map database 816 contains plural maps. Maps are commonly stored as graphs, or two or three dimensional arrays of objects with attributes of location and category, where some common categories include parks, roads, cities, and the like. A map database commonly represents a road network along with associated features, with the road network corresponding to a selected road network model. Commonly, such a model comprises basic elements (nodes, links and areas) of the road network and properties of those elements (location coordinates, shape, addresses, road class, speed range, etc.). The basic elements are referred to as features and the properties as attributes. Other information associated with the road network can also be included, such as points of interest, waypoints, building shapes, and political boundaries. Geographic Data Files (GDF) is a standardized description of such a model. Each node within a map graph represents a point location of the surface of the Earth and can be represented by a pair of longitude (lon) and latitude (lat) coordinates. Each link can represent a stretch of road between two nodes, and be represented by a line segment (corresponding to a straight section of road) or a curve having a shape that is generally described by intermediate points (called shape points) along the link. However, curves can also be represented by a combination of centroid (point or node), with a radius, and polar coordinates to define the boundaries of the curve. Shape points can be represented by longitude and latitude coordinates as are nodes, but shape points generally do not serve the purpose of connecting links, as do nodes. Areas are generally two- or three-dimensional shapes that represent things like parks, cities, blocks and are defined by their boundaries (usually formed by a closed polygon).


Auxiliary data can be attached to the features and/or attributes. Various navigational functions, involving vendor information require data that is not considered to be part of a map database and is likely supplied by the vendor. This data (such as any of the data structures: information related to the respective vendor and its product and/or service offerings, such as hours of operation, available product and/or service types, prices, brands, specifications, requirements, availabilities, advertising, and the like, sales specials and other price discounts and special offers and terms and conditions, referral percentages, fees, or payments for referring the vendor to an occupant of the vehicle 120, and other data element(s) and further data fields, such as geographical location of the respective vendor location, and the like), should be cross-referenced with the entities and attributes of the main map database 816.


Since the auxiliary data is not necessarily compiled with the main map database some other means is generally needed to establish cross-referencing, which is referred to as attaching the auxiliary data. The common approaches are function-specific referencing tables and generic referencing.


Function-specific referencing tables provide a technique for attaching function-specific data to a map-data base produced by any participating vendor. Such a table can be collaboratively produced to support a specific function or class of functions involving location-based service, active-safety or advanced driver assistance. It will generally include a list of map elements of a specific type (e.g., links, intersections, point-of-interest locations, etc.) along with identifying attributes (e.g., street names, longitude/latitude coordinates, etc.). Additionally, each entry in the table can be assigned a unique identifier.


Generic referencing attaches data to any map database by discovering reference information through a form of map matching. The function-specific data items can be assigned to elements, such as points, links or areas, that likely only approximate the corresponding map elements in a specific map database. A search of the map database can be made for the best fit. To enhance the search process, neighboring elements can be appended to each given element to help ensure that the correct solution is found in each case. For example, if the map element is a link connecting two intersections, then one or both cross streets could be appended for the sake of the search thereby making an incorrect match unlikely.


The vehicle database manager 820 and vehicle database 824 interact with an automatic vehicle location system 908 (discussed below) in the vehicle 120 and vendor server(s) 808 to provide vehicle occupant information and vehicle location (such as determined by the automatic vehicle location system) to the vendor server(s) 808, provide received vendor information to the vehicle occupants, and effect payments by the corresponding vendor to the operator or owner of the vehicle database 824 for referrals. The owner of the vehicle database 824 is typically the vehicle manufacturer but can be any data management entity, such as a provider of satellite-based navigation information (e.g., Garmin™, Google™, Waze™, and the like), or an online network transportation company (such as Uber Technologies™ or Lyft™).


The vehicle database manager 812 stores and recalls vehicle and occupant information from the vehicle database 816.


The vehicle database 816 can be constructed according to any data model, whether conceptual, logical, or physical, such as a flat model, hierarchical model, network model, relational model, object-relational model, star schema, entity-relationship model, geographic model, generic model, semantic model, and the like. The data contained in the vehicle database 816 includes vehicle-related information (such as vehicle manufacturer, type, model, manufacture year, ownership, warranty coverage, serial number(s), current geographic location and occupant identifications, specifications, capabilities, currently sensed operational parameters for the vehicle, service history, and other information), occupant or potential occupant (whether operator or passenger) information (such as occupation, identities, age, sex, biometric information, authentication information, preferences, hobbies, and other interests, socioeconomic status, historic behavior patterns, profiles, transaction history with one or more vendors, nationality, ethnicity and race, language preferences (e.g., Spanish, English, Chinese, etc.), current occupant role (e.g., operator or passenger), Internet search history, social networking memberships and relationships, (e.g., friends), credit card and other financial information, electronic calendar information (e.g., Outlook™), medical information and history, and other information.


The vehicle database 816 can obtain occupant permissive access to the data collected by an occupant assistant in the vehicle by one or more techniques. In one technique, the purchaser of a vehicle is given a price discount in exchange for agreeing to enable the vehicle to collect certain types of data and provide the data to the vehicle database manager. In another technique, the occupant is given a financial incentive, such as price discounts on application offerings and other add-on services provided by an entity operating the vehicle database, in exchange for permitting the vehicle to collect and provide certain types of data to the vehicle database manager. In another technique, the occupant is provided with updates or application downloads in exchange for consenting to the vehicle collection and provision of certain types of data.


With reference to FIG. 8, an on board occupant interaction system 900 in the vehicle 120 is depicted. The interaction system 900 includes an occupant assistant 904 in communication with an automatic vehicle location system 908 and associated satellite location system 912, social networking system 970, sensed user data 916, occupant profile(s) 974, sensor connectivity manager 966 and associated first, second, . . . mth sensors 912A-M, user interface 920, authentication system 978, and navigation information 924.


The occupant assistant 904, based on received inputs from the automatic vehicle location system 908, social networking system 970, sensed user data 916, sensor connectivity manager 966, user interface 920, authentication system 978, and navigation information 924 received from the map database manager 812, can perform various functions including: proposing one or more destinations or waypoints (such as a restaurant, store, other vendor location, point of interest, etc.) in navigation information provided to an occupant, such as a driver, via the user interface 920; publishing occupant- or vehicle-related information, via a social network, to associated or selected associates of the occupant; collecting occupant- and vehicle-related information (including any of the information described above) and forwarding the collected information to a vendor server, map database manager 812, and/or vehicle database manager 820; and presenting advertisement information, such as web pages and hyperlinks, from a vendor server 808 or vehicle database manager 820 to an occupant. The occupant can select a recommended or suggested destination or waypoint, which is then updated by the vehicle map database manager 812 to direct the vehicle 120 to the waypoint or destination.


The automatic vehicle location system 908 is in communication with the satellite location system 912 (such as a Global Positioning System (or Navstar GPS) or GPS transmitter) to acquire current vehicle position coordinates, which position coordinates are then correlated by the map database manager 812 to a position on a road. Dead reckoning using distance data from one or more sensors 912 attached to the drive train, a gyroscope sensor 912 and/or an accelerometer sensor 912 can be used for greater reliability, as GPS signal loss and/or multipath can occur due to the map database manager 812, such as due to a cellular signal dead or low signal strength area or passage of the vehicle through a tunnel. As will be appreciated, a GPS satellite location system or GPS receiver, and when used for vehicle navigation commonly referred to simply as a GPS, is a device that is capable of receiving information from GPS satellites (not shown) and then to accurately calculate the GPS location system's geographical location. The GPS navigation device or GPS receiver can be on board the vehicle 120 on a portable computational or communication device of an occupant (such as a smart phone, tablet computer, personal navigation assistant, or laptop PC), As will be appreciated, any other satellite location or navigation system can be employed, such as GLOM SS, DeiDou Navigation Satellite System, Galileo, GAGAN, IRNSS, and the like.


The social networking system 970 maintains occupant social networking information, such as social networking service memberships or affiliations, associations with other social network members (e.g., friends), and member profiles, and posts or publishes content selected by the occupant assistant 904 to one or more social networking sites and/or friends selected by the occupant. For example, the social networking system 970 can post or publish selected sensed user data, such as occupant observations based on occupant driving behavior (e.g., a frequently visited location of the occupant), or vehicle data, such as vehicle geographical location.


The sensed user data 916 is user or occupant behavior and state information sensed by the on board computer in the vehicle 120, such as current or historical user driving behavior, historical user route, destination, and waypoint preferences, user identities, and the like. This information can be sensed by the first, second, . . . Mth sensor 912A-M. This information can be used by the occupant assistant 904 to develop an occupant profile 974.


The occupant profile 974 can include a variety of occupant information, including occupation, identity, age, sex, biometric information, authentication information, preferences, hobbies, and other interests, socioeconomic status, historic behavior patterns, profiles, visitation and/or transaction history with one or more vendors, nationality, ethnicity and race, language preferences (e.g., Spanish, English, Chinese, etc.), current occupant role (e.g., operator or passenger), occupant priority ranking (e.g., vehicle owner is given a higher ranking than a child occupant), Internet search history, social networking memberships and relationships, (e.g., friends), credit card and other financial information, electronic calendar information (e.g., Outlook™), medical information and history, and other information. The occupant profile 974 is normally attributed to the vehicle operator and the occupant preference values are populated and/or updated by the occupant assistant 904 or vehicle database manager 820 as the occupant operates the vehicle.


The first, second, . . . mth sensors 912a-m can include a camera to capture images captured of interior or exterior objects (such as occupants, roadways, roadside signals, and the like), a seat belt sensor to determine seat belt settings (e.g., closed or open), a seat weight sensor settings, a microphone to capture audio within the vehicle (such as occupant comments which are then input into a speech-tip-text engine to determine or identify one or more words spoken by an occupant), a wireless network node that receives unique identifiers of occupant portable computing devices (which identifiers can be associated with a corresponding occupant to identify the occupant), and the like. In some applications, a portable computing device of the occupant is employed as a sensor that tracks occupant location when he or she is absent from the vehicle, collects social networking service and site affiliations and member associations, Internet searches and browsing history, and other types and products of occupant behavior. The information is uploaded to the sensor connectivity manager 966 when the occupant returns to the vehicle. The sensor output provided, by the sensor connectivity manager 966, is then provided to the occupant assistant 904.


The user interface 920 receives user commands and other input, such as user selections, preferences, and settings that are used in configuring, determining, and selecting vehicle parameters, settings, or operations, such as navigation route selection, Internet search requests or browsing history, social networking service and site affiliations and member associations, and other types and products of occupant behavior. The user interface 920 can be one or more of vehicle instrument panel 400, vehicle operational display 420, heads-up display 434, and power management display 428. It can also be a portable computational or communication device of an occupant.


The authentication system 978 authenticates occupants using user selected credentials (e.g., password or personal identification number), a user computing device or keyfob emitted signal sequence or content (which sequence or content can be unique or substantially unique and therefore used to identify an associated user), and biometric physiological or behavioral information of the occupant, such as a fingerprint, palm vein pattern, facial characteristic, DNA sequence, palm print, hand geometry, iris characteristic, retina characteristic, odour/scent, occupant weight, and voice print or spectral characteristic. Behavioral biometric information includes seat settings, typing rhythm, and gait.


The navigation information 924 can take many forms depending on the configuration. When the navigation information 924 received by the vehicle from the automatic vehicle location system is provided, via network 510, to the map database manager 812, it can be the map or other navigation information provided by the map database manager 812 to the occupant, including possible routes and is periodically updated with selected route map information. When the navigation information is received by the automatic vehicle location system and used by the vehicle itself to configure, determine or select possible routes, it is map information from the map database 816 that is selected based on a request received by the map database manager 812 from the vehicle 120. The request can include the current vehicle location as determined by the automatic vehicle location system 908 and the locations of the user selected waypoints and destination.


A number of examples will now be used to explain the various operations of the occupant assistant 904.


In a first example, the occupant assistant 904, in response to a trigger such as time-of-day, vehicle location, a vehicle being parked, or other stimulus, determines a current location of the vehicle, retrieves a selected occupant or composite profile corresponding to a selected occupant of group of occupants currently in the vehicle, causes the map database manager 812 to search the map database 816 for specific information referenced in the selected occupant or composite profile, such as a restaurant, storefront, other vendor location, point of interest, and the like, within a defined spatial range of the vehicle, and, when a map feature matches the specific information, the occupant assistant 904 alerts one or more vehicle occupants, such as by updating a displayed navigation map or providing a message or prompt on the user interface or providing an audible voice message to the occupant(s) via a voice synthesizer.


In one variation of the first example, the occupant assistant 904 and/or vehicle database manager compares a need, specification, or requirement against a need, specification, or requirement of a vendor in determining whether or not to recommend or suggest the vendor to the selected occupant(s). For example, the occupant assistant 904 determines that the vehicle contains a family of four occupants (two adults and two children). The vehicle 904 directly or via the vehicle database manager, publishes this information to vendors within a selected spatial range of the current vehicle location (e.g., 2 miles). Each of the various vendors reviews its needs, specifications, requirements, or availabilities (e.g., it currently has an open table for a family of four) and responds with this information, possibly including a price discount or other incentive to the vehicle occupants, to select the respective vendor. Likewise, a vendor can review its needs, specifications, requirements, or availabilities and respond with a disincentive to the vehicle occupants to select its nearby vendor location. The response is received by the occupant assistant, which provides the response to one or more of the occupants or assigns a compliance score to each of the responses (based on occupant preferences and the attractiveness of the response to the needs, specifications or requirements of the occupant(s)), filters the various responses based on the assigned scores, and provides a subset of the responses to the one or more occupants. The occupant assistant 904 can, at the request of the one or more occupants, automatically make a reservation with the vendor (e.g., reserve the table).


In a second example, the occupant assistant 904, in response to a trigger such as time-of-day, vehicle location, a vehicle being parked, or other stimulus, determines a current location of the vehicle, retrieves a selected occupant or composite profile, causes the map database manager 812 to search the map database 816 for specific information referenced in the selected occupant or composite profile, such as a restaurant, storefront, other vendor location, point of interest, and the like, within a defined spatial range of the vehicle, and, when a map feature matches the specific information, publishes, as a recommendation, rating, or preference of the occupant or group of occupants, via a social networking service to the occupant friends or friends of each member of the group of occupants the located specific information. For example, the published information could be occupant X likes restaurant Y or occupant X is eating lunch at restaurant Y, and the like. Such a message could be customized for each occupant X in the occupant group and each friend Y of each occupant X.


In a third example, the occupant assistant 904 collects occupant- and vehicle-related information (including any of the information described above) and forwards the collected information to a vendor server, map database manager 812, and/or vehicle database manager 820. The vendor server can push advertisements to the occupant(s) via the user interface(s). The map database manager 812 or vehicle database manager 820 can use the collected information to update a profile of the occupant or composite profile of the occupant group, which is then provided to the occupant assistant for local storage as a profile 974.


In a fourth example, the occupant assistant 904 presents advertisement information, such as web pages and hyperlinks, from a vendor server 808 or vehicle database manager 820 to an occupant(s), monitors the occupant or occupant group behavior, such as a request to update the displayed navigation information to reflect a vendor location associated with the advertisement information or otherwise determines that the vehicle has traveled to the vendor location; and provides the visit to the vendor location to the vehicle database manager 820. The vehicle database manager 820 can determine from the vendor server associated with the visited vendor location that the occupant or a member of the occupant group has purchased goods or services. A referral fee, which can be a percentage of the transaction, a flat rate, or other basis, can be paid by the vendor to the entity operating the vehicle database manager. In some applications, the vehicle database manager uses information in the vehicle database to identify the vehicle occupant or a member of the occupant group as complying with stipulated criteria received from the vendor server (e.g., which criteria can be any of the occupant or vehicle information described above) and, when the occupant or occupant group is within a specified spatial range of a vendor location associated with the vendor server, alerts one or more of the occupant(s) to the vendor location or provides vendor generated advertisements to the vehicle for presentation to the occupant(s) and, in exchange receives a referral fee. Where the vendor location is in a mall, the occupant portable computing device can be used by the occupant assistant to track occupant or occupant group member location while the vehicle is parked and one or more of the occupants is absent.


When multiple occupants are in the vehicle, the occupant assistant 904 can blend profiles of the occupants to yield an aggregate or composite profile for use in any of the examples above. The composite profile recognizes that a given occupant's behavior when the occupant is alone is often different than the occupant's behavior when in a group. The composite profile for the group contains, in the occupant identity field, the identities of each of the occupants in the vehicle or occupant group. The role field, which defines the role of each individual participant in the behavior of the group on a group preference-by-preference basis or universally across all group preferences, contains a role value for each of the identified occupants. The role value indicates the degree of influence the corresponding occupant has over the behavior of the group. For example, a first occupant in the group has a first role value while a second occupant in the group has a different second role value, which means that the first and second occupants have different degrees of influence over the group behavior. The occupant having the superior role value has a greater weighting assigned to that occupant's field values in each of various group preference or predictive behavior fields. For a given field, the sum of all of the weighted values assigned to the group's occupant members is the aggregate value assigned to the field. By way of example, if a given field relates to preference for Italian food and first and second occupants are in the group, the value assigned to the field in the composite profile is (first occupant's preference value for Italian food)×(first occupant's role value)+(second occupant's preference value for Italian food)×(second occupant's role value)=group preference value for Italian food. When considering group preference for food type, the group food preference values for different food types are compared, with the field having the highest (or lowest depending on the configuration) group food preference value being the food type to be used in the restaurant search and recommendation. As will be appreciated, other approaches can be employed, such as assigning a restaurant preference field rather than food type preference.


When any field in the profiles of the various group members contains one or more conflicting values, a number of other different approaches can be used to resolve the conflict. In one approach, the most frequently occurring value for the field is given precedence for the entire carload of occupants regardless of the respective role ranking of each occupant, e.g., most passengers or occupants in the vehicle prefer Mexican food, a restaurant having outside seating, and/or romantic movies. In another approach, one occupant profile having a highest role ranking is given precedence over the profiles of the other occupants for the conflicting field. In another approach, the field is given multiple, different values, each of which can be the source of a stimulus or suggestion or recommendation. The occupants are then empowered to decide amongst themselves, what conflicting choice is to be selected. Other techniques can be used to resolve conflicting fields.


In yet another approach, the intelligent assistant 904 or vehicle database manager constructs a composite profile based on observations of vehicle behavior while the occupant group members are in a common vehicle. The observed vehicle behavior is attributed to the group rather than to the operator. As the vehicle is operated with the occupant group in the vehicle, the various group preference field values are populated and/or updated.


In yet another approach, the behavior of a given occupant or group of occupants is predicted using one or more dynamic models, such as predictive analytics (e.g., predictive models, descriptive models, and decision models), among others. The approaches used to conduct predictive analytics include regression techniques, linear regression models, discrete choice models, logistic regression, multinomial logistic regression, probit regression, time series models, survival or duration analysis, classification and regression trees, multivariate adaptive regression splines, machine learning techniques, neural networks, multilayer perception, radial basis functions, support vector machines, Naïve Bayes, k-nearest neighbors, and geospatial predictive modeling. One specific example is the use of plural Kalman filters sequenced by a Markov chain.


In yet another approach, the behavior of a given occupant or group of occupants is predicted using behavioral segmentation. Behavioral segmentation divides the occupants of multiple vehicles into groups or classes based on selected parameters of behavior, such as those set forth above. There are two broad set of methodologies for segmentation: namely objective (supervised) and lion-objective (unsupervised) segmentation methodologies. The most common techniques used for building an objective segmentation are CHAID and CRT. Each of these techniques attempts to maximize the difference among segments with regards to the stated objective or target for segmentation, which are the selected behavior parameters. CHAID uses a chi square statistic while CRT uses Gini impurity for the difference maximization. The most common techniques for building non-objective segmentation are cluster analysis and K nearest neighbor techniques. Each of these techniques uses a distance measure (e.g. Euclidian distance, Manhattan distance, or Mahalanobis distance). The distance measure maximizes the distance between the selected behavior parameters in the two segments.


In yet another approach, the behavior of a given occupant or group of occupants is predicted using occupant input on the selected parameters of behavior. The occupant input can be received by the user interface on board the vehicle.


When a given occupant is included in multiple composite profiles when he or she is in different occupant groups, the role and preference field values of the various composite profiles can be used to predict the given occupant's role value and preference field values of a different group of occupants containing different occupants besides the given occupant. This can be particularly true where the given occupant has a high or low role value consistently in the various composite values.


The operations of the various executable modules will now be discussed with reference to FIGS. 9-10.


With reference to FIG. 9, the occupant assistant 904, in step 1000, detects a stimulus, such as any set forth above, and commences execution of the instructions.


In step 1004, the occupant assistant 904 determines from the automatic vehicle location system 908 the current geographical location of the vehicle 120.


In step 1008, the occupant assistant 904 collects vehicle-related information from the sensor connectivity manager 966. This information comprises, in addition to the information set forth above, whether the vehicle is in park or in gear (e.g., motion), whether one or more occupants have left the vehicle (e.g. by sensing door openings or closings, by processing an image of the vehicle interior to detect an absent occupant, detecting a change of sensed weight by a seat weight sensor or change of safety belt setting (e.g., open or closed), and the like.


In step 1012, the occupant assistant 904 collects occupant-related information, such as the information set forth above. This includes, for example, the identities of the vehicle occupants, the roles of each identified occupant (e.g., driver or passenger), a current activity of each occupant (e.g., operating vehicle, operating portable computing device, interacting with an on board vehicle user interface, and the like), content provided to each identified occupant since the last data collection (e.g., Internet search or browsing session content, such as web pages), and the like.


In step 1016, the occupant assistant 904, depending on the embodiment, provides the collected information to the map database manager, vendor server(s), or vehicle database manager to update a set of occupant-related or vehicle-related data structures maintained thereby.


In step 1020, the occupant assistant 908 optionally updates locally stored occupant profiles 974 or receives updated occupant and composite profiles from the vehicle database manager.


With reference to FIG. 10, the occupant assistant 904, in step 1100, detects a stimulus, such as any set forth above and receipt of a request from a vendor server, map database manager, or vehicle database manager, and commences execution of the instructions.


In step 1104, the occupant assistant 904 determines from the automatic vehicle location system 908 the current geographical location of the vehicle 120 and, from sensed user data 916, the current vehicle-related and occupant-related information.


In step 1108, the occupant assistant 904 retrieves selected occupant or composite profile(s), typically for each occupant in the vehicle.


In step 1112, the occupant assistant 904 causes the map database manager to search the map database for specific information in the occupant or composite profile(s). The data structures searched can be auxiliary data embedded in the map information. The type of specific information to be searched depends on the nature of the stimulus. If the stimulus is detection of a habitual or predetermined time to consume breakfast, lunch, or dinner, the occupant assistant selects food preference or preferred restaurants fields. If the stimulus is receipt of a request from a vendor server or vehicle database manager for a request to provide potential advertisement information or recommendation or suggestion to visit a vendor, the fields selected relate to conditions set forth in the request defining preconditions for the potential advertisement or recommendation or suggestion (e.g., occupant age, sex, socioeconomic status, interaction history of occupant with the vendor, and the like).


In step 1116, the occupant assistant 904, depending on the nature of the stimuli and results of search, applies rules defining what, if any, actions are to be undertaken. Actions include, for example, proposing one or more destinations or waypoints (such as a restaurant, store, other vendor location, point of interest, etc.) in navigation information provided to an occupant, such as a driver, or group of occupants via the user interface 920; publishing occupant- or vehicle-related information, via a social network, to associated or selected associates of the each of the occupant(s); collecting occupant- and vehicle-related information (including any of the information described above) and forwarding the collected information to a vendor server, map database manager 812, and/or vehicle database manager 820; and presenting advertisement information, such as web pages and hyperlinks, from a vendor server 808 or vehicle database manager 820 to an occupant.


With reference to FIG. 11, the vehicle database manager 820, in step 1200, detects a stimulus, such as for example any of the stimulus set forth above, a request for advertising targets received from a vendor server, a request for vendor information received from the occupant assistant 904, and other stimuli, and commences execution of the instructions.


In step 1204, the vehicle database manager determines from the vehicle database 824 and/or from the automatic vehicle location system 908 of the vehicle 120 the current geographical location of the vehicle 120 and the current vehicle-related and occupant-related information, including individual vehicle occupant profiles and/or a composite vehicle occupant profile, depending on the application, or vendor profiles depending on whether the request is received from a vendor server or occupant assistant.


In step 1208, the vehicle database manager 820 receives search criteria from one or more of the vendor server(s) 808A-N or occupant assistant.


In step 1212, the vehicle database manager 820 searches the vehicle location and vehicle-related and occupant-related information for qualifying occupant and/or composite profile(s) when the request is from a vendor server or one or more vendor profiles for qualifying vendors and qualifying vendor locations when the request is from the occupant assistant. “Qualifying” is deemed to exist when a search target satisfies the search criteria specified by the vendor or occupant assistant, as the case may be.


In step 1216, the vehicle database manager pushes advertising content from the requesting vendor server to qualifying or selected vehicles or from qualifying vendor server(s) to the requesting vehicle. When appropriate, the vehicle database manager receives a payment from the vendor server corresponding to the advertising content for pushing the advertising content to the vehicle, such payment terms discussed above in more detail.


With reference to FIG. 12, the logical instructions are executed by an arithmetic/logic unit (“ALU”), which performs mathematical operations, such as addition, subtraction, multiplication, and division, machine instructions, an address bus (that sends an address to memory), a data bus (that can send data to memory or receive data from memory), a read and write line to tell the memory whether to set or get the addressed location, a clock line that enables a clock pulse to sequence the processor, and a reset line that resets the program counter to zero or another value and restarts execution. The arithmetic/logic unit can be a floating point processor that performs operations on floating point numbers. The occupant assistant 904, vehicle database manager 820, and/or map database manager 812 further includes first, second, and third registers that are typically configured from flip-flops, an address latch, a program counter (which can increment by “1” and reset to “0”), a test register to hold values from comparisons performed in the arithmetic/logic unit (such as comparisons in steps 1020, 1112, 1116, and 1212), plural tri-state buffers to pass a “1” or “0” or disconnect its output (thereby allowing multiple outputs to connect to a wire but only one of them to actually drive a “1” or “0” into the line), and an instruction register and decoder to control other components. Control lines, in the occupant assistant 904, vehicle database manager 820, and/or map database manager 812, from the instruction decoder can: command the first register to latch the value currently on the data bus, command the second register to latch the value currently on the data bus, command the third register to latch the value currently output by the ALU, command the program counter register to latch the value currently on the data bus, command the address register to latch the value currently on the data bus, command the instruction register to latch the value currently on the data bus, command the program counter to increment, command the program counter to reset to zero, activate any of the plural tri-state buffers (plural separate lines), command the ALU what operation to perform, command the test register to latch the ALU's test bits, activate the read line, and activate the write line. Bits from the test register and clock line as well as the bits from the instruction register come into the instruction decoder. Hardware similar or identical to that of FIG. 12 is in each of the occupant assistant 904, vehicle database manager 820 and/or map database manager 812 for executing the instructions of FIGS. 9-11. The ALU executes instructions for a random or pseudo-random number generation algorithm and generates the recipient identifier using the appropriate seed values.


Any of the steps, functions, and operations discussed herein can be performed continuously and automatically.


The exemplary systems and methods of this disclosure have been described in relation to vehicle systems and electric vehicles. However, to avoid unnecessarily obscuring the present disclosure, the preceding description omits a number of known structures and devices. This omission is not to be construed as a limitation of the scope of the claimed disclosure. Specific details are set forth to provide an understanding of the present disclosure. It should, however, be appreciated that the present disclosure may be practiced in a variety of ways beyond the specific detail set forth herein.


Furthermore, while the exemplary embodiments illustrated herein show the various components of the system collocated, certain components of the system can be located remotely, at distant portions of a distributed network, such as a LAN and/or the Internet, or within a dedicated system. Thus, it should be appreciated, that the components of the system can be combined into one or more devices, such as a server, communication device, or collocated on a particular node of a distributed network, such as an analog and/or digital telecommunications network, a packet-switched network, or a circuit-switched network. It will be appreciated from the preceding description, and for reasons of computational efficiency, that the components of the system can be arranged at any location within a distributed network of components without affecting the operation of the system.


Furthermore, it should be appreciated that the various links connecting the elements can be wired or wireless links, or any combination thereof, or any other known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements. These wired or wireless links can also be secure links and may be capable of communicating encrypted information. Transmission media used as links, for example, can be any suitable carrier for electrical signals, including coaxial cables, copper wire, and fiber optics, and may take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.


While the flowcharts have been discussed and illustrated in relation to a particular sequence of events, it should be appreciated that changes, additions, and omissions to this sequence can occur without materially affecting the operation of the disclosed embodiments, configuration, and aspects.


A number of variations and modifications of the disclosure can be used. It would be possible to provide for some features of the disclosure without providing others.


In yet another embodiment, the systems and methods of this disclosure can be implemented in conjunction with a special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element(s), an ASIC or other integrated circuit, a digital signal processor, a hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device or gate array such as PLD, PLA, FPGA, PAL, special purpose computer, any comparable means, or the like. In general, any device(s) or means capable of implementing the methodology illustrated herein can be used to implement the various aspects of this disclosure. Exemplary hardware that can be used for the present disclosure includes computers, handheld devices, telephones (e.g., cellular, Internet enabled, digital, analog, hybrids, and others), and other hardware known in the art. Some of these devices include processors (e.g., a single or multiple microprocessors), memory, nonvolatile storage, input devices, and output devices. Furthermore, alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.


In yet another embodiment, the disclosed methods may be readily implemented in conjunction with software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer or workstation platforms. Alternatively, the disclosed system may be implemented partially or fully in hardware using standard logic circuits or VLSI design. Whether software or hardware is used to implement the systems in accordance with this disclosure is dependent on the speed and/or efficiency requirements of the system, the particular function, and the particular software or hardware systems or microprocessor or microcomputer systems being utilized.


In yet another embodiment, the disclosed methods may be partially implemented in software that can be stored on a storage medium, executed on programmed general-purpose computer with the cooperation of a controller and memory, a special purpose computer, a microprocessor, or the like. In these instances, the systems and methods of this disclosure can be implemented as a program embedded on a personal computer such as an applet, JAVA® or CGI script, as a resource residing on a server or computer workstation, as a routine embedded in a dedicated measurement system, system component, or the like. The system can also be implemented by physically incorporating the system and/or method into a software and/or hardware system.


Although the present disclosure describes components and functions implemented in the embodiments with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Other similar standards and protocols not mentioned herein are in existence and are considered to be included in the present disclosure. Moreover, the standards and protocols mentioned herein and other similar standards and protocols not mentioned herein are periodically superseded by faster or more effective equivalents having essentially the same functions. Such replacement standards and protocols having the same functions are considered equivalents included in the present disclosure.


The present disclosure, in various embodiments, configurations, and aspects, includes components, methods, processes, systems and/or apparatus substantially as depicted and described herein, including various embodiments, subcombinations, and subsets thereof. Those of skill in the art will understand how to make and use the systems and methods disclosed herein after understanding the present disclosure. The present disclosure, in various embodiments, configurations, and aspects, includes providing devices and processes in the absence of items not depicted and/or described herein or in various embodiments, configurations, or aspects hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease, and/or reducing cost of implementation.


The foregoing discussion of the disclosure has been presented for purposes of illustration and description. The foregoing is not intended to limit the disclosure to the form or forms disclosed herein. In the foregoing Detailed Description for example, various features of the disclosure are grouped together in one or more embodiments, configurations, or aspects for the purpose of streamlining the disclosure. The features of the embodiments, configurations, or aspects of the disclosure may be combined in alternate embodiments, configurations, or aspects other than those discussed above. This method of disclosure is not to be interpreted as reflecting an intention that the claimed disclosure requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment, configuration, or aspect. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate preferred embodiment of the disclosure.


Moreover, though the description of the disclosure has included description of one or more embodiments, configurations, or aspects and certain variations and modifications, other variations, combinations, and modifications are within the scope of the disclosure, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights, which include alternative embodiments, configurations, or aspects to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges, or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges, or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter.


Embodiments include a vehicle comprising:


a vehicle interior for receiving one or more occupants;


a powertrain to transmit power from a power source to an electric motor to propel the vehicle;


a user interface to receive input from an occupant and provide output to the occupant;


a plurality of sensors to sense information related to occupants;


an automatic vehicle location system to determine a current spatial location of the vehicle;


a computer readable medium to store a composite occupant profile; and


a microprocessor, coupled to the user interface, plurality of sensors, automatic vehicle location system, and computer readable medium, to:


determine that the vehicle interior comprises plural occupants;


identify the plural occupants;


based on the driving behavior of the vehicle, create a composite occupant profile associated with the group of plural occupants, the composite occupant profile comprising the identities of the plural occupants and group preferences for various vendor products or services; and


based on the composite occupant profile and received inputs from the user interface, automatic vehicle location system, and plurality of sensors, one or more of: (a) propose one or more vendor products or services for the group of occupants; (b) publish the one or more vendor products or services selected by the group of occupants, via a social network, to associated or selected associates of one or more of the occupants in the group; and (c) present advertisement information from a vendor server associated with the proposed or selected one or more vendor products or services to one or more of the occupants in the group.


Embodiments include a method that includes the steps:


determining, by a microprocessor, that the vehicle interior comprises plural occupants;


identifying, by the microprocessor, the plural occupants;


based on the driving behavior of the vehicle, creating, by the microprocessor, a composite occupant profile associated with the group of plural occupants, the composite occupant profile comprising the identities of the plural occupants and group preferences for various vendor products or services; and


based on the composite occupant profile and received inputs from a user interface, an automatic vehicle location system, and a plurality of sensors in the vehicle, the microprocessor one or more of: (a) proposing one or more vendor products or services for the group of occupants; (b) publishing the one or more vendor products or services selected by the group of occupants, via a social network, to associated or selected associates of one or more of the occupants in the group; and (c) presenting advertisement information from a vendor server associated with the proposed or selected one or more vendor products or services to one or more of the occupants in the group.


Aspects of the above vehicle or method can include one or more of: the driving behavior being one or more of current or historical user driving behavior, historical route driven by the vehicle, destination of the vehicle, and waypoints of the vehicle; the driving behavior of the vehicle being attributed to the group of occupants; the plurality of sensors comprising a plurality of: a camera to capture images of the occupants in the vehicle interior, a camera to capture images of objects outside the vehicle, a seat belt sensor to determine a seat belt setting, a seat weight sensor to determine a weight of a seated occupant, a microphone to capture speech of the plurality of occupants, and a portable computing device of one or more of the occupants to sense interaction of the one or more of the occupants with the portable computing device; and the composite profile comprising, for each occupant in the group, the occupant's identity and the occupant's age or the occupant's biometric information and, for the group, visitation and/or transaction history with one or more vendors.


Aspects of the above vehicle or method can include the composite profile comprising, for each occupant in the occupant group, a role value indicating a role the corresponding occupant plays in a group decision.


Aspects of the above vehicle or method can include one or more of: the microprocessor proposing one or more vendor products or services for the group of occupants and the proposed one or more vendor products being proposed based on a number of group members, ages of the group members, and sexes of the group members and a need, specification, or availability of a product or service offered by a vendor.


Aspects of the above vehicle or method can include the microprocessor publishing the one or more vendor products or services selected by the group of occupants, via a social network, to associated or selected associates of one or more of the occupants in the group.


Aspects of the above vehicle or method can include the microprocessor presenting advertisement information from a vendor server associated with the proposed or selected one or more vendor products or services to one or more of the occupants in the group and the advertisement information being associated with a vendor product or service located within a selected spatial range of a current vehicle location.


Aspects of the above vehicle or method can include the composite profile being created by combining like preference field values in the individual profiles of the occupants in the group using one or more of a role value for each occupant in the group for that preference field, an unweighted average of the field values of the group occupants for a selected preference, a mode of the field values of the group occupants for a selected preference, and a median of the field values of the group occupants for a selected preference.


Aspects of the above vehicle or method can include the composite profile being created by combining like preference field values in the individual profiles of the occupants in the group using predictive analytics.


Embodiments include a method that includes the steps:


receiving, by a computer server, a request to provide advertising information to a vehicle;


determining, by the computer server, a current location of plural vehicles comprising the vehicle and current vehicle related and occupant-related information associated with occupants of the plurality of vehicles;


receiving, by the computer server, search criteria from a vendor server or the vehicle;


searching, by the computer server and in accordance with the search criteria, the determined current locations and the vehicle-related and occupant-related information associated with the occupants of the plurality of vehicles or plural vendor profiles including vendor locations; and


based on the searching, providing, by the computer server, to the vehicle selected advertising content responsive to the search criteria.


Aspects of the above vehicle or method can include the search criteria beings received from the vendor server and the computer server searching the determined current locations and the vehicle-related and occupant-related information to determine the vehicles in the plurality of vehicles to receive the advertising content from the vendor server and not receive the advertising content from the vendor server.


Aspects of the above vehicle or method can include the search criteria being received from the vehicle and the computer server searching the plural vendor profiles to determine vendor locations in spatial proximity to the vehicle and meeting a need, specification or requirement of the vehicle occupants and wherein the advertising content is associated with the determined vendor locations.


Aspects of the above vehicle or method can include the computer server causing payment to be made by or an invoice to be received from a vendor server providing the advertising content in exchange for the computer server providing the advertising content to the vehicle.


Any one or more of the aspects/embodiments as substantially disclosed herein.


Any one or more of the aspects/embodiments as substantially disclosed herein optionally in combination with any one or more other aspects/embodiments as substantially disclosed herein.


One or means adapted to perform any one or more of the above aspects/embodiments as substantially disclosed herein.


The phrases “at least one,” “one or more,” “or,” and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C,” “at least one of A, B, or C,” “one or more of A, B, and C,” “one or more of A, B, or C,” “A, B, and/or C,” and “A, B, or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.


The term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more,” and “at least one” can be used interchangeably herein. It is also to be noted that the terms “comprising,” “including,” and “having” can be used interchangeably.


The term “automatic” and variations thereof, as used herein, refers to any process or operation, which is typically continuous or semi-continuous, done without material human input when the process or operation is performed. However, a process or operation can be automatic, even though performance of the process or operation uses material or immaterial human input, if the input is received before performance of the process or operation. Human input is deemed to be material if such input influences how the process or operation will be performed. Human input that consents to the performance of the process or operation is not deemed to be “material.”


Aspects of the present disclosure may take the form of an embodiment that is entirely hardware, an embodiment that is entirely software (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” or “system.” Any combination of one or more computer-readable medium(s) may be utilized. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium.


A computer-readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.


A computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer-readable signal medium may be any computer-readable medium that is not a computer-readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer-readable medium may be transmitted using any appropriate medium, including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.


The terms “determine,” “calculate,” “compute,” and variations thereof, as used herein, are used interchangeably and include any type of methodology, process, mathematical operation or technique.


The term “electric vehicle” (EV), also referred to herein as an electric drive vehicle, may use one or more electric motors or traction motors for propulsion. An electric vehicle may be powered through a collector system by electricity from off-vehicle sources, or may be self-contained with a battery or generator to convert fuel to electricity. An electric vehicle generally includes a rechargeable electricity storage system (RESS) (also called Full Electric Vehicles (FEV)). Power storage methods may include: chemical energy stored on the vehicle in on-board batteries (e.g., battery electric vehicle or BEV), on board kinetic energy storage (e.g., flywheels), and/or static energy (e.g., by on-board double-layer capacitors). Batteries, electric double-layer capacitors, and flywheel energy storage may be forms of rechargeable on-board electrical storage.


The term “hybrid electric vehicle” refers to a vehicle that may combine a conventional (usually fossil fuel-powered) powertrain with some form of electric propulsion. Most hybrid electric vehicles combine a conventional internal combustion engine (ICE) propulsion system with an electric propulsion system (hybrid vehicle drivetrain). In parallel hybrids, the ICE and the electric motor are both connected to the mechanical transmission and can simultaneously transmit power to drive the wheels, usually through a conventional transmission. In series hybrids, only the electric motor drives the drivetrain, and a smaller ICE works as a generator to power the electric motor or to recharge the batteries. Power-split hybrids combine series and parallel characteristics. A full hybrid, sometimes also called a strong hybrid, is a vehicle that can run on just the engine, just the batteries, or a combination of both. A mid hybrid is a vehicle that cannot be driven solely on its electric motor, because the electric motor does not have enough power to propel the vehicle on its own.


The term “rechargeable electric vehicle” or “REV” refers to a vehicle with on board rechargeable energy storage, including electric vehicles and hybrid electric vehicles.

Claims
  • 1. A vehicle, comprising: a vehicle interior for receiving one or more occupants;a powertrain to transmit power from a power source to an electric motor to propel the vehicle;a user interface to receive input from an occupant and provide output to the occupant;a plurality of sensors to sense information related to occupants;an automatic vehicle location system to determine a current spatial location of the vehicle;a computer readable medium to store a composite occupant profile; anda microprocessor, coupled to the user interface, plurality of sensors, automatic vehicle location system, and computer readable medium, to: determine that the vehicle interior comprises a group of plural occupants;identify each occupant of the group of plural occupants;based on individual profiles of the group of plural occupants, create a composite occupant profile that represents the group of plural occupants, the composite occupant profile comprising an identity of each occupant of the group of plural occupants and group preferences for various vendor products or services, wherein each occupant of the group of plural occupants has a corresponding individual occupant profile, each individual occupant profile comprising individual preference values, wherein the composite occupant profile and the group preferences are created by combining, for a selected preference, a preference value for the selected preference retrieved from the individual preference values for each occupant using one or more of a role value for each occupant of the group of plural occupants, an unweighted average of the individual preference values of each occupant of the group of plural occupants for the selected preference, a mode of the individual preference values of each occupant of the group of plural occupants for the selected preference, and a median of the individual preference values of each occupant of the group of plural occupants for the selected preference; andbased on the composite occupant profile and received inputs from the user interface, automatic vehicle location system, and plurality of sensors, one or more of: (a) propose one or more vendor products or services for the group of plural occupants; (b) publish the one or more vendor products or services selected by the group of plural occupants, via a social network, to associated or selected associates of one or more of the occupants in the group of plural occupants; and (c) present advertisement information from a vendor server associated with the proposed or selected one or more vendor products or services to one or more of the occupants in the group of plural occupants.
  • 2. The vehicle of claim 1, wherein the composite occupant profile comprises plural preference fields, wherein a preference value of at least one of the plural preference fields in the composite occupant profile is based on a preference value in an individual occupant profile of an occupant of a different vehicle and not currently an occupant of the vehicle, wherein creating the composite occupant profile is based on a driving behavior of the vehicle, wherein the driving behavior is one or more of current or historical user driving behavior, historical route driven by the vehicle, destination of the vehicle, and waypoints of the vehicle, wherein the driving behavior of the vehicle is attributed to the group of plural occupants, wherein the plurality of sensors comprise a plurality of: a camera to capture images of the occupants in the vehicle interior, a camera to capture images of objects outside the vehicle, a seat belt sensor to determine a seat belt setting, a seat weight sensor to determine a weight of a seated occupant, a microphone to capture speech of the group of plural occupants, and a portable computing device of at least one of the group of plural occupants to sense interaction of the at least one of the group of plural occupants with the portable computing device, and wherein the composite occupant profile comprises, for each occupant of the group of plural occupants, an age or biometric information for each occupant and, for the group of plural occupants, visitation and/or transaction history with one or more vendors.
  • 3. The vehicle of claim 1, wherein the microprocessor provides information in the composite occupant profile to multiple vendor servers of multiple vendors, wherein the composite occupant profile comprises, for each occupant in the group of plural occupants the role value indicating a role a corresponding occupant plays in a group decision, each occupant of the group of plural occupants having a different role value, wherein, in response to providing the information, the microprocessor receives multiple vendor responses from the multiple vendors, assigns a compliance score to each of the multiple vendor responses, the compliance score indicating a degree of compliance of a respective vendor response with one or more of an occupant preference and an attractiveness of the respective vendor response to a need, specification, or requirement of the composite occupant profile, filters the multiple vendor responses based on the assigned compliance scores, and provides a subset of the multiple vendor responses to at least one occupant of the group of plural occupants.
  • 4. The vehicle of claim 1, wherein the microprocessor directly or indirectly provides vehicle occupant information in the composite occupant profile and current vehicle location to the vendor server, wherein the microprocessor proposes one or more vendor products or services for the group of plural occupants, wherein the microprocessor provides to an occupant of the group of plural occupants a plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of a respective vendor, wherein the microprocessor provides to the occupant a geographic data file comprising the geographic location of the respective vendor, wherein the plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of the respective vendor are cross-referenced by a function-specific referencing table and/or generic reference features or attributes of the geographic data file, and wherein the proposed one or more vendor products is proposed based on a number of members in the group of plural occupants, ages of the members in the group of plural occupants, and sexes of the members in the group of plural occupants and a need, specification, or availability of a product or service offered by a vendor.
  • 5. The vehicle of claim 1, wherein the microprocessor publishes the one or more vendor products or services selected by the group of plural occupants, via the social network, to associated or selected associates of one or more of the occupants in the group of plural occupants and the publication comprises a plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of a respective vendor.
  • 6. The vehicle of claim 1, wherein the microprocessor directly or indirectly provides vehicle occupant information in the composite occupant profile and current vehicle location to the vendor server, wherein the microprocessor presents advertisement information from the vendor server associated with the proposed or selected one or more vendor products or services to one or more of the occupants in the group of plural occupants, wherein the microprocessor provides to an occupant a plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of a respective vendor, wherein the microprocessor provides to the occupant a geographic data file comprising the geographic location of the respective vendor, wherein the plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of the respective vendor are cross-referenced by a function-specific referencing table and/or generic reference features or attributes of the geographic data file, and wherein the advertisement information is associated with a vendor product or service located within a selected spatial range of a current vehicle location.
  • 7. The vehicle of claim 1, wherein the composite occupant profile comprises plural preference fields, wherein, when the microprocessor determines that a selected preference field in each individual occupant profile of two or more occupants comprise of the group of plural occupants comprises a conflicting value, the microprocessor uses, for the selected preference field value in the composite occupant profile, one or more of a most frequently occurring value for the selected preference, the value of the selected preference field in the individual occupant profile having a highest role ranking and multiple, different values in the individual occupant profiles, each of which is a source of a stimulus or suggestion or recommendation to the two or more occupants of the group of plural occupants.
  • 8. The vehicle of claim 1, wherein the composite profile is created by combining like preference field values in the individual occupant profiles of the group of plural occupants using one or more of (i) predictive analytics comprising one or more of a regression technique, linear regression model, discrete choice model, logistic regression, multinomial logistic regression, probit regression, time series model, survival or duration analysis, classification and regression tree, multivariate adaptive regression spline, machine learning technique, neural network, multilayer perception, radial basis function, support vector machine, Nave Bayes, k-nearest neighbor, and geospatial predictive modeling and (ii) behavioral segmentation, in which the microprocessor divides occupants of multiple different vehicles into groups or classes based on selected parameters of behavior using one or more of an objective and non-objective segmentation methodology to maximize a difference among segments with regards to each selected behavior parameter.
  • 9. A method, comprising: determining, by a microprocessor, that a vehicle interior comprises a group of plural occupants;identifying, by the microprocessor, each occupant of the group of plural occupants;based on individual profiles of the group of plural occupants, creating, by the microprocessor, a composite occupant profile that represents the group of plural occupants, the composite occupant profile comprising an identity of each occupant of the group of plural occupants and group preferences for various vendor products or services, wherein each occupant of the group of plural occupants has a corresponding individual occupant profile, each individual occupant profile comprising individual preference values, wherein the composite occupant profile and the group preferences are created by combining, for a selected preference, a preference value for the selected preference retrieved from the individual preference values for each occupant using one or more of a role value for each occupant of the group of plural occupants, an unweighted average of the individual preference values of each occupant of the group of plural occupants for the selected preference, a mode of the individual preference values of each occupant of the group of plural occupants for the selected preference, and a median of the individual preference values of each occupant of the group of plural occupants for the selected preference; andbased on the composite occupant profile and received inputs from a user interface, an automatic vehicle location system, and a plurality of sensors in the vehicle, one or more of: (a) proposing, by the microprocessor, one or more vendor products or services for the group of plural occupants; (b) publishing, by the microprocessor, the one or more vendor products or services selected by the group of plural occupants, via a social network, to associated or selected associates of one or more of the occupants in the group; and (c) presenting, by the microprocessor, advertisement information from a vendor server associated with the proposed or selected one or more vendor products or services to one or more of the occupants in the group of plural occupants.
  • 10. The method of claim 9, wherein the composite occupant profile comprises plural preference fields, wherein a preference value of at least one of the plural preference fields in the composite occupant profile is based on a preference value in an individual occupant profile of an occupant of a different vehicle and not currently an occupant of the vehicle, wherein creating the composite occupant profile is based on a driving behavior of the vehicle, wherein the driving behavior is one or more of current or historical user driving behavior, historical route driven by the vehicle, destination of the vehicle, and waypoints of the vehicle, wherein the driving behavior of the vehicle is attributed to the group of plural occupants, wherein the plurality of sensors comprise a plurality of: a camera to capture images of the occupants in the vehicle interior, a camera to capture images of objects outside the vehicle, a seat belt sensor to determine a seat belt setting, a seat weight sensor to determine a weight of a seated occupant, a microphone to capture speech of the group of plural occupants, and a portable computing device of at least one of the group of plural occupants to sense interaction of the at least one of the group of plural occupants with the portable computing device, and wherein the composite occupant profile comprises, for each occupant of the group of plural occupants, an age or biometric information for each occupant and, for the group of plural occupants, visitation and/or transaction history with one or more vendors.
  • 11. The method of claim 9, further comprising: providing, by the microprocessor, information in the composite occupant profile to multiple vendor servers of multiple vendors, wherein the composite occupant profile comprises, for each occupant in the group of plural occupants, the role value indicating a role a corresponding occupant plays in a group decision, each occupant of the group of plural occupants having a different role value;receiving, by the microprocessor and in response to providing the information, multiple vendor responses from the multiple;assigning, by the microprocessor, a compliance score to each of the multiple vendor responses received, the compliance score indicating a degree of compliance of the respective vendor response with one or more of an occupant preference and an attractiveness of the respective vendor response to a need, specification or requirement of the composite occupant profile;filtering, by the microprocessor, the multiple vendor responses based on the assigned compliance scores; andproviding, by the microprocessor and based on the filtering, a subset of the multiple vendor responses to at least one occupant of the group of plural occupants.
  • 12. The method of claim 9, wherein the microprocessor directly or indirectly provides vehicle occupant information in the composite occupant profile and current vehicle location to the vendor server, wherein the microprocessor proposes one or more vendor products or services for the group of plural occupants, wherein the microprocessor provides to an occupant of the group of plural occupants a plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of a respective vendor, wherein the microprocessor provides to the occupant a geographic data file comprising the geographic location of the respective vendor, wherein the plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of the respective vendor are cross-referenced by a function-specific referencing table and/or generic reference features or attributes of the geographic data file, and wherein the proposed one or more vendor products is proposed based on a number of members in the group of plural occupants, ages of the members in the group of plural occupants, and sexes of the members in the group of plural occupants and a need, specification, or availability of a product or service offered by a vendor.
  • 13. The method of claim 9, further comprising: publishing, by the microprocessor, the one or more vendor products or services selected by the group of plural occupants, via the social network, to associated or selected associates of one or more of the occupants in the group of plural occupants and the publication comprises a plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of a respective vendor.
  • 14. The method of claim 9, further comprising: providing, by the microprocessor directly or indirectly, vehicle occupant information in the composite occupant profile and current vehicle location to the vendor server;presenting, by the microprocessor, advertisement information from the vendor server associated with the proposed or selected one or more vendor products or services to one or more of the occupants in the group of plural occupants;providing, by the microprocessor, to an occupant a plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of a respective vendor; andproviding, by the microprocessor, to the occupant a geographic data file comprising the geographic location of the respective vendor, wherein the plurality of vendor hours of operation, available product and/or service types, available product and/or service prices, available product and/or service specifications or requirements, and geographical location of the respective vendor are cross-referenced by a function-specific referencing table and/or generic reference features or attributes of the geographic data file, and wherein the advertisement information is associated with a vendor product or service located within a selected spatial range of a current vehicle location.
  • 15. The method of claim 9, further comprising: determining, by the microprocessor, that a selected preference field in each individual occupant profile of two or more occupants of the group of plural occupants comprises a conflicting value;using, by the microprocessor, for the selected preference field value in the composite occupant profile, one or more of a most frequently occurring value for the selected preference, the value of the selected preference in the individual occupant profile having a highest role ranking and multiple, different values in the individual occupant profiles, each of which is a source of a stimulus or suggestion or recommendation to the two or more occupants of the group of plural occupants.
  • 16. The method of claim 9, wherein the composite occupant profile is created by the microprocessor combining like preference field values in the individual occupant profiles of the group of plural occupants using one or more of (i) predictive analytics comprising one or more of a regression technique, linear regression model, discrete choice model, logistic regression, multinomial logistic regression, probit regression, time series model, survival or duration analysis, classification and regression tree, multivariate adaptive regression spline, machine learning technique, neural network, multilayer perception, radial basis function, support vector machine, Naïve Bayes, k-nearest neighbor, and geospatial predictive modeling and (ii) behavioral segmentation, in which the microprocessor divides occupants of multiple different vehicles into groups or classes based on selected parameters of behavior using one or more of an objective and non-objective segmentation methodology to maximize a difference among segments with regards to each selected behavior parameter.
CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims the benefits of and priority, under 35 U.S.C. § 119(e), to U.S. Provisional Application Ser. No. 62/424,976, filed on Nov. 21, 2016, entitled “Next Generation Vehicle,” the entire disclosure of which is hereby incorporated by reference, in its entirety, for all that it teaches and for all purposes.

US Referenced Citations (940)
Number Name Date Kind
4361202 Minovitch Nov 1982 A
4476954 Johnson et al. Oct 1984 A
4754255 Sanders et al. Jun 1988 A
4875391 Leising et al. Oct 1989 A
5136498 McLaughlin et al. Aug 1992 A
5204817 Yoshida Apr 1993 A
5363306 Kuwahara et al. Nov 1994 A
5508689 Rado et al. Apr 1996 A
5521815 Rose May 1996 A
5529138 Shaw et al. Jun 1996 A
5531122 Chatham et al. Jul 1996 A
5572450 Worthy Nov 1996 A
5610821 Gazis et al. Mar 1997 A
5648769 Sato et al. Jul 1997 A
5710702 Hayashi et al. Jan 1998 A
5794164 Beckert et al. Aug 1998 A
5797134 McMillan et al. Aug 1998 A
5812067 Bergholz et al. Sep 1998 A
5825283 Camhi Oct 1998 A
5838251 Brinkmeyer et al. Nov 1998 A
5847661 Ricci Dec 1998 A
5890080 Coverdill et al. Mar 1999 A
5928294 Zelinkovsky Jul 1999 A
5949345 Beckert et al. Sep 1999 A
5983161 Lemelson et al. Nov 1999 A
5986575 Jones et al. Nov 1999 A
6038426 Williams, Jr. Mar 2000 A
6081756 Mio et al. Jun 2000 A
D429684 Johnson Aug 2000 S
6128003 Smith et al. Oct 2000 A
6141620 Zyburt et al. Oct 2000 A
6148261 Obradovich et al. Nov 2000 A
6152514 McLellen Nov 2000 A
6157321 Ricci Dec 2000 A
6198996 Berstis Mar 2001 B1
6199001 Ohta et al. Mar 2001 B1
6202008 Beckert et al. Mar 2001 B1
6252544 Hoffberg Jun 2001 B1
6267428 Baldas et al. Jul 2001 B1
6302438 Stopper, Jr. et al. Oct 2001 B1
6310542 Gehlot Oct 2001 B1
6317058 Lemelson et al. Nov 2001 B1
6339826 Hayes, Jr. et al. Jan 2002 B2
6356838 Paul Mar 2002 B1
6388579 Adcox et al. May 2002 B1
6480224 Brown Nov 2002 B1
6502022 Chastain et al. Dec 2002 B1
6519519 Stopczynski Feb 2003 B1
6557752 Yacoob May 2003 B1
6563910 Menard et al. May 2003 B2
6587739 Abrams et al. Jul 2003 B1
6598227 Berry et al. Jul 2003 B1
6607212 Reimer et al. Aug 2003 B1
6617981 Basinger Sep 2003 B2
6662077 Haag Dec 2003 B2
6675081 Shuman et al. Jan 2004 B2
6678747 Goossen et al. Jan 2004 B2
6681176 Funk et al. Jan 2004 B2
6690260 Ashihara Feb 2004 B1
6690940 Brown et al. Feb 2004 B1
6724920 Berenz et al. Apr 2004 B1
6754580 Ask et al. Jun 2004 B1
6757593 Mori et al. Jun 2004 B2
6762684 Camhi Jul 2004 B1
6765495 Dunning et al. Jul 2004 B1
6778888 Cataldo et al. Aug 2004 B2
6782240 Tabe Aug 2004 B1
6785531 Lepley et al. Aug 2004 B2
6816783 Hashima et al. Nov 2004 B2
6820259 Kawamata et al. Nov 2004 B1
6944533 Obradovich et al. Sep 2005 B2
6950022 Breed Sep 2005 B2
6958707 Siegel Oct 2005 B1
6992580 Kotzin et al. Jan 2006 B2
7019641 Lakshmanan et al. Mar 2006 B1
7020544 Shinada et al. Mar 2006 B2
7021691 Schmidt et al. Apr 2006 B1
7042345 Ellis May 2006 B2
7047129 Uotani May 2006 B2
7058898 McWalter et al. Jun 2006 B2
7096431 Tambata et al. Aug 2006 B2
7142696 Engelsberg et al. Nov 2006 B1
7164117 Breed et al. Jan 2007 B2
7187947 White et al. Mar 2007 B1
7203598 Whitsell Apr 2007 B1
7233861 Van Buer et al. Jun 2007 B2
7239960 Yokota et al. Jul 2007 B2
7277454 Mocek et al. Oct 2007 B2
7284769 Breed Oct 2007 B2
7289645 Yamamoto et al. Oct 2007 B2
7295921 Spencer et al. Nov 2007 B2
7313547 Mocek et al. Dec 2007 B2
7333012 Nguyen Feb 2008 B1
7343148 O'Neil Mar 2008 B1
7386376 Basir et al. Jun 2008 B2
7386799 Clanton et al. Jun 2008 B1
7432829 Poltorak Oct 2008 B2
7474264 Bolduc et al. Jan 2009 B2
7493140 Michmerhuizen et al. Feb 2009 B2
7526539 Hsu Apr 2009 B1
7548815 Watkins et al. Jun 2009 B2
7566083 Vitito Jul 2009 B2
7606660 Diaz et al. Oct 2009 B2
7606867 Singhal et al. Oct 2009 B1
7643913 Taki et al. Jan 2010 B2
7650234 Obradovich et al. Jan 2010 B2
7671764 Uyeki et al. Mar 2010 B2
7680596 Uyeki et al. Mar 2010 B2
7683771 Loeb Mar 2010 B1
7711468 Levy May 2010 B1
7734315 Rathus et al. Jun 2010 B2
7748021 Obradovich et al. Jun 2010 B2
RE41449 Krahnstoever et al. Jul 2010 E
7791499 Mohan et al. Sep 2010 B2
7796190 Basso et al. Sep 2010 B2
7802832 Carnevali Sep 2010 B2
7821421 Tamir et al. Oct 2010 B2
7832762 Breed Nov 2010 B2
7864073 Lee et al. Jan 2011 B2
7872591 Kane et al. Jan 2011 B2
7873471 Gieseke Jan 2011 B2
7881703 Roundtree et al. Feb 2011 B2
7891004 Gelvin et al. Feb 2011 B1
7891719 Carnevali Feb 2011 B2
7899610 McClellan Mar 2011 B2
7966678 Ten Eyck et al. Jun 2011 B2
7969290 Waeller et al. Jun 2011 B2
7969324 Chevion et al. Jun 2011 B2
8060631 Collart et al. Nov 2011 B2
8064925 Sun et al. Nov 2011 B1
8066313 Carnevali Nov 2011 B2
8098170 Szczerba et al. Jan 2012 B1
8113564 Carnevali Feb 2012 B2
8131419 Ampunan et al. Mar 2012 B2
8157310 Carnevali Apr 2012 B2
8162368 Carnevali Apr 2012 B2
8175802 Forstall et al. May 2012 B2
8233919 Haag et al. Jul 2012 B2
8245609 Greenwald et al. Aug 2012 B1
8306514 Nunally Nov 2012 B1
8334847 Tomkins Dec 2012 B2
8346233 Aaron et al. Jan 2013 B2
8346432 Van Wiemeersch et al. Jan 2013 B2
8350721 Carr Jan 2013 B2
8352282 Jensen et al. Jan 2013 B2
8369263 Dowling et al. Feb 2013 B2
8417449 Denise Apr 2013 B1
8432260 Talty et al. Apr 2013 B2
8442389 Kashima et al. May 2013 B2
8442758 Rovik et al. May 2013 B1
8467965 Chang Jun 2013 B2
8497842 Tomkins et al. Jul 2013 B2
8498809 Bill Jul 2013 B2
8509982 Montemerlo et al. Aug 2013 B2
8521410 Mizuno et al. Aug 2013 B2
8527143 Tan Sep 2013 B2
8527146 Jackson et al. Sep 2013 B1
8532574 Kirsch Sep 2013 B2
8543330 Taylor et al. Sep 2013 B2
8547340 Sizelove et al. Oct 2013 B2
8548669 Naylor Oct 2013 B2
8559183 Davis Oct 2013 B1
8577600 Pierfelice Nov 2013 B1
8578279 Chen et al. Nov 2013 B2
8583292 Preston et al. Nov 2013 B2
8589073 Guha et al. Nov 2013 B2
8600611 Seize Dec 2013 B2
8613385 Hulet et al. Dec 2013 B1
8621645 Spackman Dec 2013 B1
8624727 Saigh et al. Jan 2014 B2
8634984 Sumizawa Jan 2014 B2
8644165 Saarimaki et al. Feb 2014 B2
8660735 Tengler et al. Feb 2014 B2
8671068 Harber et al. Mar 2014 B2
8688372 Bhogal et al. Apr 2014 B2
8705527 Addepalli et al. Apr 2014 B1
8706143 Elias Apr 2014 B1
8718797 Addepalli et al. May 2014 B1
8725311 Breed May 2014 B1
8730033 Yarnold et al. May 2014 B2
8737986 Rhoads et al. May 2014 B2
8761673 Sakata Jun 2014 B2
8774842 Jones et al. Jul 2014 B2
8779947 Tengler et al. Jul 2014 B2
8782262 Collart et al. Jul 2014 B2
8793065 Seltzer et al. Jul 2014 B2
8798918 Onishi et al. Aug 2014 B2
8805110 Rhoads et al. Aug 2014 B2
8812171 Fillev et al. Aug 2014 B2
8817761 Gruberman et al. Aug 2014 B2
8825031 Aaron et al. Sep 2014 B2
8825277 McClellan et al. Sep 2014 B2
8825382 Liu Sep 2014 B2
8826261 Anand AG et al. Sep 2014 B1
8838088 Henn et al. Sep 2014 B1
8862317 Shin et al. Oct 2014 B2
8977408 Cazanas et al. Mar 2015 B1
9043016 Filippov et al. May 2015 B2
9229905 Penilla et al. Jan 2016 B1
20010010516 Roh et al. Aug 2001 A1
20010015888 Shaler et al. Aug 2001 A1
20020009978 Dukach et al. Jan 2002 A1
20020023010 Rittmaster et al. Feb 2002 A1
20020026278 Feldman et al. Feb 2002 A1
20020045484 Eck et al. Apr 2002 A1
20020065046 Mankins et al. May 2002 A1
20020077985 Kobata et al. Jun 2002 A1
20020095249 Lang Jul 2002 A1
20020097145 Tumey et al. Jul 2002 A1
20020103622 Burge Aug 2002 A1
20020105968 Pruzan et al. Aug 2002 A1
20020126876 Paul et al. Sep 2002 A1
20020128774 Takezaki et al. Sep 2002 A1
20020143461 Burns et al. Oct 2002 A1
20020143643 Catan Oct 2002 A1
20020152010 Colmenarez et al. Oct 2002 A1
20020154217 Ikeda Oct 2002 A1
20020169551 Inoue et al. Nov 2002 A1
20020174021 Chu et al. Nov 2002 A1
20030004624 Wilson et al. Jan 2003 A1
20030007227 Ogino Jan 2003 A1
20030046164 Sato Mar 2003 A1
20030055557 Dutta et al. Mar 2003 A1
20030060937 Shinada et al. Mar 2003 A1
20030065432 Shuman et al. Apr 2003 A1
20030069870 Ras et al. Apr 2003 A1
20030101451 Bentolila et al. May 2003 A1
20030109972 Tak Jun 2003 A1
20030125846 Yu et al. Jul 2003 A1
20030132666 Bond et al. Jul 2003 A1
20030149530 Stopczynski Aug 2003 A1
20030158638 Yakes et al. Aug 2003 A1
20030182435 Redlich et al. Sep 2003 A1
20030202683 Ma et al. Oct 2003 A1
20030204290 Sadler et al. Oct 2003 A1
20030222134 Boyd Dec 2003 A1
20030230443 Cramer et al. Dec 2003 A1
20040017292 Reese et al. Jan 2004 A1
20040024502 Squires et al. Feb 2004 A1
20040036622 Dukach et al. Feb 2004 A1
20040039500 Amendola et al. Feb 2004 A1
20040039504 Coffee et al. Feb 2004 A1
20040068364 Zhao et al. Apr 2004 A1
20040070920 Flueli Apr 2004 A1
20040093155 Simonds et al. May 2004 A1
20040117494 Mitchell et al. Jun 2004 A1
20040119589 French Jun 2004 A1
20040128062 Ogino et al. Jul 2004 A1
20040153356 Lockwood et al. Aug 2004 A1
20040162019 Horita et al. Aug 2004 A1
20040180653 Royalty Sep 2004 A1
20040182574 Adnan et al. Sep 2004 A1
20040193347 Harumoto et al. Sep 2004 A1
20040203974 Seibel Oct 2004 A1
20040204837 Singleton Oct 2004 A1
20040209594 Naboulsi Oct 2004 A1
20040217850 Perttunen et al. Nov 2004 A1
20040225557 Phelan et al. Nov 2004 A1
20040255123 Noyama et al. Dec 2004 A1
20040257208 Huang et al. Dec 2004 A1
20040260470 Rast Dec 2004 A1
20050012599 DeMatteo Jan 2005 A1
20050031100 Iggulden et al. Feb 2005 A1
20050038598 Oesterling et al. Feb 2005 A1
20050042999 Rappaport Feb 2005 A1
20050065678 Smith et al. Mar 2005 A1
20050065711 Dahlgren et al. Mar 2005 A1
20050086051 Brulle-Drews Apr 2005 A1
20050093717 Lilja May 2005 A1
20050097541 Holland May 2005 A1
20050114864 Surace May 2005 A1
20050122235 Teffer et al. Jun 2005 A1
20050124211 Diessner et al. Jun 2005 A1
20050130744 Eck et al. Jun 2005 A1
20050144156 Barber Jun 2005 A1
20050149752 Johnson et al. Jul 2005 A1
20050153760 Varley Jul 2005 A1
20050159853 Takahashi et al. Jul 2005 A1
20050159892 Chung Jul 2005 A1
20050192727 Shostak et al. Sep 2005 A1
20050197748 Holst et al. Sep 2005 A1
20050197767 Nortrup Sep 2005 A1
20050251324 Wiener et al. Nov 2005 A1
20050261815 Cowelchuk et al. Nov 2005 A1
20050278093 Kameyama Dec 2005 A1
20050283284 Grenier et al. Dec 2005 A1
20060015819 Hawkins et al. Jan 2006 A1
20060036358 Hale et al. Feb 2006 A1
20060044119 Egelhaaf Mar 2006 A1
20060047386 Kanevsky et al. Mar 2006 A1
20060058948 Blass et al. Mar 2006 A1
20060059229 Bain et al. Mar 2006 A1
20060125631 Sharony Jun 2006 A1
20060130033 Stoffels et al. Jun 2006 A1
20060142933 Feng Jun 2006 A1
20060173841 Bill Aug 2006 A1
20060175403 McConnell et al. Aug 2006 A1
20060184319 Seick et al. Aug 2006 A1
20060212909 Girard et al. Sep 2006 A1
20060241836 Kachouh et al. Oct 2006 A1
20060243056 Sundermeyer et al. Nov 2006 A1
20060250272 Puamau Nov 2006 A1
20060253307 Warren et al. Nov 2006 A1
20060259210 Tanaka et al. Nov 2006 A1
20060274829 Siemens et al. Dec 2006 A1
20060282204 Breed Dec 2006 A1
20060287807 Teffer Dec 2006 A1
20060287865 Cross et al. Dec 2006 A1
20060288382 Vitito Dec 2006 A1
20060290516 Muehlsteff et al. Dec 2006 A1
20070001831 Raz et al. Jan 2007 A1
20070002032 Powers et al. Jan 2007 A1
20070010942 Bill Jan 2007 A1
20070015485 DeBiasio et al. Jan 2007 A1
20070028370 Seng Feb 2007 A1
20070032225 Konicek et al. Feb 2007 A1
20070057781 Breed Mar 2007 A1
20070061057 Huang et al. Mar 2007 A1
20070067614 Berry et al. Mar 2007 A1
20070069880 Best et al. Mar 2007 A1
20070083298 Pierce et al. Apr 2007 A1
20070088488 Reeves et al. Apr 2007 A1
20070103328 Lakshmanan et al. May 2007 A1
20070115101 Creekbaum et al. May 2007 A1
20070118301 Andarawis et al. May 2007 A1
20070120697 Ayoub et al. May 2007 A1
20070135995 Kikuchi et al. Jun 2007 A1
20070156317 Breed Jul 2007 A1
20070182625 Kerai et al. Aug 2007 A1
20070182816 Fox Aug 2007 A1
20070185969 Davis Aug 2007 A1
20070192486 Wilson et al. Aug 2007 A1
20070194902 Blanco et al. Aug 2007 A1
20070194944 Galera et al. Aug 2007 A1
20070195997 Paul et al. Aug 2007 A1
20070200663 White et al. Aug 2007 A1
20070208860 Zellner et al. Sep 2007 A1
20070213090 Holmberg Sep 2007 A1
20070228826 Jordan et al. Oct 2007 A1
20070233341 Logsdon Oct 2007 A1
20070250228 Reddy et al. Oct 2007 A1
20070257815 Gunderson et al. Nov 2007 A1
20070276596 Solomon et al. Nov 2007 A1
20070280505 Breed Dec 2007 A1
20080005974 Delgado Vazquez et al. Jan 2008 A1
20080023253 Prost-Fin et al. Jan 2008 A1
20080027337 Dugan et al. Jan 2008 A1
20080033635 Obradovich et al. Feb 2008 A1
20080042824 Kates Feb 2008 A1
20080051957 Breed et al. Feb 2008 A1
20080052627 Oguchi Feb 2008 A1
20080054072 Katragadda Mar 2008 A1
20080071465 Chapman et al. Mar 2008 A1
20080082237 Breed Apr 2008 A1
20080086455 Meisels et al. Apr 2008 A1
20080090522 Oyama Apr 2008 A1
20080104227 Birnie et al. May 2008 A1
20080119994 Kameyama May 2008 A1
20080129475 Breed et al. Jun 2008 A1
20080143085 Breed et al. Jun 2008 A1
20080147280 Breed Jun 2008 A1
20080148374 Spaur et al. Jun 2008 A1
20080154712 Wellman Jun 2008 A1
20080154957 Taylor et al. Jun 2008 A1
20080161986 Breed Jul 2008 A1
20080164985 Iketani et al. Jul 2008 A1
20080169940 Lee et al. Jul 2008 A1
20080174451 Harrington et al. Jul 2008 A1
20080212215 Schofield et al. Sep 2008 A1
20080216067 Villing Sep 2008 A1
20080228358 Wang et al. Sep 2008 A1
20080234919 Ritter et al. Sep 2008 A1
20080252487 McClellan et al. Oct 2008 A1
20080253613 Jones et al. Oct 2008 A1
20080255721 Yamada Oct 2008 A1
20080255722 McClellan et al. Oct 2008 A1
20080269958 Filev et al. Oct 2008 A1
20080281508 Fu Nov 2008 A1
20080300778 Kuznetsov Dec 2008 A1
20080305780 Williams et al. Dec 2008 A1
20080319602 McClellan et al. Dec 2008 A1
20090006525 Moore Jan 2009 A1
20090024419 McClellan et al. Jan 2009 A1
20090037719 Sakthikumar et al. Feb 2009 A1
20090040026 Tanaka Feb 2009 A1
20090055178 Coon Feb 2009 A1
20090082951 Graessley Mar 2009 A1
20090099720 Elgali Apr 2009 A1
20090112393 Maten et al. Apr 2009 A1
20090112452 Buck et al. Apr 2009 A1
20090119657 Link, II May 2009 A1
20090125174 Delean May 2009 A1
20090132294 Haines May 2009 A1
20090138336 Ashley et al. May 2009 A1
20090144622 Evans et al. Jun 2009 A1
20090157312 Black et al. Jun 2009 A1
20090158200 Palahnuk et al. Jun 2009 A1
20090180668 Jones et al. Jul 2009 A1
20090189373 Schramm et al. Jul 2009 A1
20090189979 Smyth Jul 2009 A1
20090193217 Korecki et al. Jul 2009 A1
20090195370 Huffman et al. Aug 2009 A1
20090210257 Chalfant et al. Aug 2009 A1
20090216935 Flick Aug 2009 A1
20090222200 Link et al. Sep 2009 A1
20090224931 Dietz et al. Sep 2009 A1
20090224942 Goudy et al. Sep 2009 A1
20090234578 Newby et al. Sep 2009 A1
20090241883 Nagoshi et al. Oct 2009 A1
20090254446 Chernyak Oct 2009 A1
20090264849 La Croix Oct 2009 A1
20090275321 Crowe Nov 2009 A1
20090278750 Man et al. Nov 2009 A1
20090278915 Kramer et al. Nov 2009 A1
20090279839 Nakamura et al. Nov 2009 A1
20090284359 Huang et al. Nov 2009 A1
20090287405 Liu et al. Nov 2009 A1
20090299572 Fujikawa et al. Dec 2009 A1
20090312998 Berckmans et al. Dec 2009 A1
20090319181 Khosravy et al. Dec 2009 A1
20100008053 Osternack et al. Jan 2010 A1
20100023204 Basir et al. Jan 2010 A1
20100035620 Naden et al. Feb 2010 A1
20100036560 Wright et al. Feb 2010 A1
20100042498 Schalk Feb 2010 A1
20100052945 Breed Mar 2010 A1
20100057337 Fuchs Mar 2010 A1
20100066498 Fenton Mar 2010 A1
20100069115 Liu Mar 2010 A1
20100070338 Siotia et al. Mar 2010 A1
20100077094 Howarter et al. Mar 2010 A1
20100087987 Huang et al. Apr 2010 A1
20100090817 Yamaguchi et al. Apr 2010 A1
20100097178 Pisz et al. Apr 2010 A1
20100097239 Campbell et al. Apr 2010 A1
20100097458 Zhang et al. Apr 2010 A1
20100106344 Edwards et al. Apr 2010 A1
20100106418 Kindo et al. Apr 2010 A1
20100118025 Smith et al. May 2010 A1
20100121570 Tokue et al. May 2010 A1
20100121645 Seitz et al. May 2010 A1
20100125387 Sehyun et al. May 2010 A1
20100125405 Chae et al. May 2010 A1
20100125811 Moore et al. May 2010 A1
20100127847 Evans et al. May 2010 A1
20100131300 Collopy et al. May 2010 A1
20100131642 Chalikouras May 2010 A1
20100134958 Disaverio et al. Jun 2010 A1
20100136944 Taylor et al. Jun 2010 A1
20100137037 Basir Jun 2010 A1
20100144284 Chutorash et al. Jun 2010 A1
20100145700 Kennewick et al. Jun 2010 A1
20100145987 Harper et al. Jun 2010 A1
20100152976 White et al. Jun 2010 A1
20100169432 Santori et al. Jul 2010 A1
20100174474 Nagase Jul 2010 A1
20100179712 Pepitone et al. Jul 2010 A1
20100185341 Wilson et al. Jul 2010 A1
20100188831 Ortel Jul 2010 A1
20100197359 Harris Aug 2010 A1
20100202346 Sitzes et al. Aug 2010 A1
20100211259 McClellan Aug 2010 A1
20100211282 Nakata et al. Aug 2010 A1
20100211300 Jaffe et al. Aug 2010 A1
20100211304 Hwang et al. Aug 2010 A1
20100211441 Sprigg et al. Aug 2010 A1
20100217458 Schweiger et al. Aug 2010 A1
20100222939 Namburu et al. Sep 2010 A1
20100228404 Link et al. Sep 2010 A1
20100234071 Shabtay et al. Sep 2010 A1
20100235042 Ying Sep 2010 A1
20100235744 Schultz Sep 2010 A1
20100235891 Oglesbee et al. Sep 2010 A1
20100250071 Pala et al. Sep 2010 A1
20100253493 Szczerba et al. Oct 2010 A1
20100256836 Mudalige Oct 2010 A1
20100259058 Knighton Oct 2010 A1
20100265104 Zlojutro Oct 2010 A1
20100268426 Pathak et al. Oct 2010 A1
20100274410 Tsien et al. Oct 2010 A1
20100280751 Breed Nov 2010 A1
20100287303 Smith et al. Nov 2010 A1
20100289632 Seder et al. Nov 2010 A1
20100289643 Trundle et al. Nov 2010 A1
20100291427 Zhou Nov 2010 A1
20100295676 Khachaturov et al. Nov 2010 A1
20100304640 Sofman et al. Dec 2010 A1
20100305807 Basir et al. Dec 2010 A1
20100306080 Trandal et al. Dec 2010 A1
20100306309 Santori et al. Dec 2010 A1
20100306435 Nigoghosian et al. Dec 2010 A1
20100315218 Cades et al. Dec 2010 A1
20100321151 Matsuura et al. Dec 2010 A1
20100325626 Greschler et al. Dec 2010 A1
20100332130 Shimizu et al. Dec 2010 A1
20110015853 DeKock et al. Jan 2011 A1
20110018736 Carr Jan 2011 A1
20110021213 Carr Jan 2011 A1
20110021234 Tibbits et al. Jan 2011 A1
20110028138 Davies-Moore et al. Feb 2011 A1
20110035098 Goto et al. Feb 2011 A1
20110035141 Barker et al. Feb 2011 A1
20110040438 Kluge et al. Feb 2011 A1
20110050589 Yan et al. Mar 2011 A1
20110053506 Lemke et al. Mar 2011 A1
20110077808 Hyde et al. Mar 2011 A1
20110078024 Messier et al. Mar 2011 A1
20110080282 Kleve et al. Apr 2011 A1
20110082615 Small et al. Apr 2011 A1
20110084824 Tewari et al. Apr 2011 A1
20110090078 Kim et al. Apr 2011 A1
20110092159 Park et al. Apr 2011 A1
20110093154 Moinzadeh et al. Apr 2011 A1
20110093158 Theisen et al. Apr 2011 A1
20110093438 Poulsen Apr 2011 A1
20110093846 Moinzadeh et al. Apr 2011 A1
20110105097 Tadayon et al. May 2011 A1
20110106375 Sundaram et al. May 2011 A1
20110112717 Resner May 2011 A1
20110112969 Zaid et al. May 2011 A1
20110117933 Andersson May 2011 A1
20110119344 Eustis May 2011 A1
20110130915 Wright et al. Jun 2011 A1
20110134749 Speks et al. Jun 2011 A1
20110137520 Rector et al. Jun 2011 A1
20110145331 Christie et al. Jun 2011 A1
20110172873 Szwabowski et al. Jul 2011 A1
20110175754 Karpinsky Jul 2011 A1
20110183658 Zellner Jul 2011 A1
20110187520 Filev et al. Aug 2011 A1
20110193707 Ngo Aug 2011 A1
20110193726 Szwabowski et al. Aug 2011 A1
20110195699 Tadayon et al. Aug 2011 A1
20110197187 Roh Aug 2011 A1
20110205047 Patel et al. Aug 2011 A1
20110209079 Tarte et al. Aug 2011 A1
20110210867 Benedikt Sep 2011 A1
20110212717 Rhoads et al. Sep 2011 A1
20110221656 Haddick et al. Sep 2011 A1
20110224865 Gordon et al. Sep 2011 A1
20110224898 Scofield et al. Sep 2011 A1
20110225527 Law et al. Sep 2011 A1
20110227757 Chen et al. Sep 2011 A1
20110231091 Gourlay et al. Sep 2011 A1
20110234369 Cai et al. Sep 2011 A1
20110245999 Kordonowy Oct 2011 A1
20110246210 Matsur Oct 2011 A1
20110247013 Feller et al. Oct 2011 A1
20110251734 Schepp et al. Oct 2011 A1
20110257973 Chutorash et al. Oct 2011 A1
20110267204 Chuang et al. Nov 2011 A1
20110267205 McClellan et al. Nov 2011 A1
20110286676 El Dokor Nov 2011 A1
20110291886 Krieter Dec 2011 A1
20110291926 Gokturk et al. Dec 2011 A1
20110298808 Rovik Dec 2011 A1
20110301844 Aono Dec 2011 A1
20110307354 Erman et al. Dec 2011 A1
20110307570 Speks Dec 2011 A1
20110309926 Eikelenberg et al. Dec 2011 A1
20110309953 Petite et al. Dec 2011 A1
20110313653 Lindner Dec 2011 A1
20110320089 Lewis Dec 2011 A1
20120006610 Wallace et al. Jan 2012 A1
20120010807 Zhou Jan 2012 A1
20120016581 Mochizuki et al. Jan 2012 A1
20120029852 Goff et al. Feb 2012 A1
20120030002 Bous et al. Feb 2012 A1
20120030512 Wadhwa et al. Feb 2012 A1
20120038489 Goldshmidt Feb 2012 A1
20120046822 Anderson Feb 2012 A1
20120047530 Shkedi Feb 2012 A1
20120053793 Sala et al. Mar 2012 A1
20120053888 Stahlin et al. Mar 2012 A1
20120059789 Sakai et al. Mar 2012 A1
20120065815 Hess Mar 2012 A1
20120065834 Senart Mar 2012 A1
20120068956 Jira et al. Mar 2012 A1
20120071097 Matsushita et al. Mar 2012 A1
20120072244 Collins et al. Mar 2012 A1
20120074770 Lee Mar 2012 A1
20120083960 Zhu et al. Apr 2012 A1
20120083971 Preston Apr 2012 A1
20120084773 Lee et al. Apr 2012 A1
20120089299 Breed Apr 2012 A1
20120092251 Hashimoto et al. Apr 2012 A1
20120101876 Truvey et al. Apr 2012 A1
20120101914 Kumar et al. Apr 2012 A1
20120105613 Weng et al. May 2012 A1
20120106114 Caron et al. May 2012 A1
20120109446 Yousefi et al. May 2012 A1
20120109451 Tan May 2012 A1
20120110356 Yousefi et al. May 2012 A1
20120113822 Letner May 2012 A1
20120115446 Guatama et al. May 2012 A1
20120116609 Jung et al. May 2012 A1
20120116678 Witmer May 2012 A1
20120116696 Wank May 2012 A1
20120146766 Geisler et al. Jun 2012 A1
20120146809 Oh et al. Jun 2012 A1
20120149341 Tadayon et al. Jun 2012 A1
20120150651 Hoffberg et al. Jun 2012 A1
20120155636 Muthaiah Jun 2012 A1
20120158436 Bauer et al. Jun 2012 A1
20120173900 Diab et al. Jul 2012 A1
20120173905 Diab et al. Jul 2012 A1
20120179325 Faenger Jul 2012 A1
20120179547 Besore et al. Jul 2012 A1
20120188876 Chow et al. Jul 2012 A1
20120197523 Kirsch Aug 2012 A1
20120197669 Kote et al. Aug 2012 A1
20120204166 Ichihara Aug 2012 A1
20120210160 Fuhrman Aug 2012 A1
20120215375 Chang Aug 2012 A1
20120217928 Kulidjian Aug 2012 A1
20120218125 Demirdjian et al. Aug 2012 A1
20120226413 Chen et al. Sep 2012 A1
20120238286 Mallavarapu et al. Sep 2012 A1
20120239242 Uehara Sep 2012 A1
20120242510 Choi et al. Sep 2012 A1
20120254763 Protopapas et al. Oct 2012 A1
20120254804 Shema et al. Oct 2012 A1
20120259951 Schalk et al. Oct 2012 A1
20120265359 Das Oct 2012 A1
20120274459 Jaisimha et al. Nov 2012 A1
20120274481 Ginsberg et al. Nov 2012 A1
20120284080 de Oliveira Nov 2012 A1
20120284292 Rechsteiner et al. Nov 2012 A1
20120289217 Reimer et al. Nov 2012 A1
20120289253 Haag et al. Nov 2012 A1
20120296567 Breed Nov 2012 A1
20120313771 Wottlifff, III Dec 2012 A1
20120316720 Hyde et al. Dec 2012 A1
20120317561 Aslam et al. Dec 2012 A1
20120323413 Kedar-Dongarkar et al. Dec 2012 A1
20120327231 Cochran et al. Dec 2012 A1
20130005263 Sakata Jan 2013 A1
20130005414 Bindra et al. Jan 2013 A1
20130013157 Kim et al. Jan 2013 A1
20130019252 Haase et al. Jan 2013 A1
20130024060 Sukkarie et al. Jan 2013 A1
20130029693 Bradley, Jr. Jan 2013 A1
20130030645 Divine et al. Jan 2013 A1
20130030811 Olleon et al. Jan 2013 A1
20130031540 Throop et al. Jan 2013 A1
20130031541 Wilks et al. Jan 2013 A1
20130035063 Fisk et al. Feb 2013 A1
20130046624 Calman Feb 2013 A1
20130050069 Ota Feb 2013 A1
20130055096 Kim et al. Feb 2013 A1
20130059607 Herz et al. Mar 2013 A1
20130063336 Sugimoto et al. Mar 2013 A1
20130066512 Willard et al. Mar 2013 A1
20130067599 Raje et al. Mar 2013 A1
20130075530 Shander et al. Mar 2013 A1
20130079964 Sukkarie et al. Mar 2013 A1
20130083805 Lu et al. Apr 2013 A1
20130085787 Gore et al. Apr 2013 A1
20130086164 Wheeler et al. Apr 2013 A1
20130099915 Prasad et al. Apr 2013 A1
20130103196 Monceaux et al. Apr 2013 A1
20130116882 Link et al. May 2013 A1
20130116915 Ferreira et al. May 2013 A1
20130134730 Ricci May 2013 A1
20130135118 Ricci May 2013 A1
20130138591 Ricci May 2013 A1
20130138714 Ricci May 2013 A1
20130139140 Rao et al. May 2013 A1
20130141247 Ricci Jun 2013 A1
20130141252 Ricci Jun 2013 A1
20130143495 Ricci Jun 2013 A1
20130143546 Ricci Jun 2013 A1
20130143601 Ricci Jun 2013 A1
20130144459 Ricci Jun 2013 A1
20130144460 Ricci Jun 2013 A1
20130144461 Ricci Jun 2013 A1
20130144462 Ricci Jun 2013 A1
20130144463 Ricci et al. Jun 2013 A1
20130144469 Ricci Jun 2013 A1
20130144470 Ricci Jun 2013 A1
20130144474 Ricci Jun 2013 A1
20130144486 Ricci Jun 2013 A1
20130144520 Ricci Jun 2013 A1
20130144657 Ricci Jun 2013 A1
20130145065 Ricci Jun 2013 A1
20130145279 Ricci Jun 2013 A1
20130145297 Ricci et al. Jun 2013 A1
20130145360 Ricci Jun 2013 A1
20130145401 Ricci Jun 2013 A1
20130145482 Ricci et al. Jun 2013 A1
20130147638 Ricci Jun 2013 A1
20130151031 Ricci Jun 2013 A1
20130151065 Ricci Jun 2013 A1
20130151088 Ricci Jun 2013 A1
20130151288 Bowne et al. Jun 2013 A1
20130152003 Ricci et al. Jun 2013 A1
20130154298 Ricci Jun 2013 A1
20130157640 Aycock Jun 2013 A1
20130157647 Kolodziej Jun 2013 A1
20130158778 Tengler et al. Jun 2013 A1
20130158821 Ricci Jun 2013 A1
20130166096 Jotanovic Jun 2013 A1
20130166097 Ricci Jun 2013 A1
20130166098 Lavie et al. Jun 2013 A1
20130166152 Butterworth Jun 2013 A1
20130166208 Forstall et al. Jun 2013 A1
20130167159 Ricci et al. Jun 2013 A1
20130173531 Rinearson et al. Jul 2013 A1
20130179689 Matsumoto et al. Jul 2013 A1
20130190978 Kato et al. Jul 2013 A1
20130194108 Lapiotis et al. Aug 2013 A1
20130197796 Obradovich et al. Aug 2013 A1
20130198031 Mitchell et al. Aug 2013 A1
20130198737 Ricci Aug 2013 A1
20130198802 Ricci Aug 2013 A1
20130200991 Ricci et al. Aug 2013 A1
20130203400 Ricci Aug 2013 A1
20130204455 Chia et al. Aug 2013 A1
20130204457 King Aug 2013 A1
20130204466 Ricci Aug 2013 A1
20130204484 Ricci Aug 2013 A1
20130204493 Ricci et al. Aug 2013 A1
20130204678 Liu et al. Aug 2013 A1
20130204943 Ricci Aug 2013 A1
20130205026 Ricci Aug 2013 A1
20130205412 Ricci Aug 2013 A1
20130207794 Patel et al. Aug 2013 A1
20130212065 Rahnama Aug 2013 A1
20130212659 Maher et al. Aug 2013 A1
20130215116 Siddique et al. Aug 2013 A1
20130218412 Ricci Aug 2013 A1
20130218445 Basir Aug 2013 A1
20130219039 Ricci Aug 2013 A1
20130226365 Brozovich Aug 2013 A1
20130226371 Rovik et al. Aug 2013 A1
20130226392 Schneider et al. Aug 2013 A1
20130226449 Rovik et al. Aug 2013 A1
20130226622 Adamson et al. Aug 2013 A1
20130227648 Ricci Aug 2013 A1
20130231784 Rovik et al. Sep 2013 A1
20130231800 Ricci Sep 2013 A1
20130232142 Nielsen et al. Sep 2013 A1
20130238165 Garrett et al. Sep 2013 A1
20130241720 Ricci et al. Sep 2013 A1
20130245882 Ricci Sep 2013 A1
20130246181 Lobsenz Sep 2013 A1
20130250933 Yousefi et al. Sep 2013 A1
20130261871 Hobbs et al. Oct 2013 A1
20130261966 Wang et al. Oct 2013 A1
20130265178 Tengler et al. Oct 2013 A1
20130274997 Chien Oct 2013 A1
20130279111 Lee Oct 2013 A1
20130279491 Rubin et al. Oct 2013 A1
20130282238 Ricci et al. Oct 2013 A1
20130282357 Rubin et al. Oct 2013 A1
20130282946 Ricci Oct 2013 A1
20130288606 Kirsch Oct 2013 A1
20130293364 Ricci et al. Nov 2013 A1
20130293452 Ricci et al. Nov 2013 A1
20130293480 Kritt et al. Nov 2013 A1
20130295901 Abramson et al. Nov 2013 A1
20130295908 Zeinstra et al. Nov 2013 A1
20130295913 Matthews et al. Nov 2013 A1
20130300554 Braden Nov 2013 A1
20130301584 Addepalli et al. Nov 2013 A1
20130304371 Kitatani et al. Nov 2013 A1
20130308265 Arnouse Nov 2013 A1
20130309977 Heines et al. Nov 2013 A1
20130311038 Kim et al. Nov 2013 A1
20130325453 Levien et al. Dec 2013 A1
20130325568 Mangalvedkar et al. Dec 2013 A1
20130329372 Wilkins Dec 2013 A1
20130332023 Bertosa et al. Dec 2013 A1
20130338914 Weiss Dec 2013 A1
20130339027 Dokor et al. Dec 2013 A1
20130345929 Bowden et al. Dec 2013 A1
20140028542 Lovitt et al. Jan 2014 A1
20140032014 DeBiasio et al. Jan 2014 A1
20140054957 Bellis Feb 2014 A1
20140058672 Wansley et al. Feb 2014 A1
20140058826 Ogawa Feb 2014 A1
20140066014 Nicholson et al. Mar 2014 A1
20140067201 Visintainer et al. Mar 2014 A1
20140067564 Yuan Mar 2014 A1
20140070917 Protopapas Mar 2014 A1
20140081544 Fry Mar 2014 A1
20140087760 Bennett Mar 2014 A1
20140088798 Himmelstein Mar 2014 A1
20140095294 Vick Apr 2014 A1
20140096068 Dewan et al. Apr 2014 A1
20140097955 Lovitt et al. Apr 2014 A1
20140109075 Hoffman et al. Apr 2014 A1
20140109080 Ricci Apr 2014 A1
20140120829 Bhamidipati et al. May 2014 A1
20140121862 Zarrella et al. May 2014 A1
20140125802 Beckert et al. May 2014 A1
20140143839 Ricci May 2014 A1
20140164611 Molettiere et al. Jun 2014 A1
20140168062 Katz et al. Jun 2014 A1
20140168436 Pedicino Jun 2014 A1
20140169621 Burr Jun 2014 A1
20140171752 Park et al. Jun 2014 A1
20140172727 Abhyanker et al. Jun 2014 A1
20140188533 Davidson Jul 2014 A1
20140188920 Sharma Jul 2014 A1
20140195272 Sadiq et al. Jul 2014 A1
20140198216 Zhai et al. Jul 2014 A1
20140200737 Lortz et al. Jul 2014 A1
20140207328 Wolf et al. Jul 2014 A1
20140220966 Muetzel et al. Aug 2014 A1
20140222298 Gurin Aug 2014 A1
20140222551 Jain Aug 2014 A1
20140223384 Graumann Aug 2014 A1
20140240089 Chang Aug 2014 A1
20140244078 Downey et al. Aug 2014 A1
20140244111 Gross et al. Aug 2014 A1
20140244156 Magnusson et al. Aug 2014 A1
20140245277 Petro et al. Aug 2014 A1
20140245278 Zellen Aug 2014 A1
20140245284 Alrabady et al. Aug 2014 A1
20140252091 Morse et al. Sep 2014 A1
20140257627 Hagan, Jr. Sep 2014 A1
20140267035 Schalk et al. Sep 2014 A1
20140277936 El Dokor et al. Sep 2014 A1
20140278070 McGavran et al. Sep 2014 A1
20140278071 San Filippo et al. Sep 2014 A1
20140281971 Isbell, III et al. Sep 2014 A1
20140282161 Cash Sep 2014 A1
20140282278 Anderson et al. Sep 2014 A1
20140282470 Buga et al. Sep 2014 A1
20140282931 Protopapas Sep 2014 A1
20140292545 Nemoto Oct 2014 A1
20140292665 Lathrop et al. Oct 2014 A1
20140303899 Fung Oct 2014 A1
20140306799 Ricci Oct 2014 A1
20140306814 Ricci Oct 2014 A1
20140306817 Ricci Oct 2014 A1
20140306826 Ricci Oct 2014 A1
20140306833 Ricci Oct 2014 A1
20140306834 Ricci Oct 2014 A1
20140306835 Ricci Oct 2014 A1
20140307655 Ricci Oct 2014 A1
20140307724 Ricci Oct 2014 A1
20140308902 Ricci Oct 2014 A1
20140309789 Ricci Oct 2014 A1
20140309790 Ricci Oct 2014 A1
20140309804 Ricci Oct 2014 A1
20140309805 Ricci Oct 2014 A1
20140309806 Ricci Oct 2014 A1
20140309813 Ricci Oct 2014 A1
20140309814 Ricci et al. Oct 2014 A1
20140309815 Ricci et al. Oct 2014 A1
20140309838 Ricci Oct 2014 A1
20140309839 Ricci et al. Oct 2014 A1
20140309847 Ricci Oct 2014 A1
20140309849 Ricci Oct 2014 A1
20140309852 Ricci Oct 2014 A1
20140309853 Ricci Oct 2014 A1
20140309862 Ricci Oct 2014 A1
20140309863 Ricci Oct 2014 A1
20140309864 Ricci Oct 2014 A1
20140309865 Ricci Oct 2014 A1
20140309866 Ricci Oct 2014 A1
20140309867 Ricci Oct 2014 A1
20140309868 Ricci Oct 2014 A1
20140309869 Ricci Oct 2014 A1
20140309870 Ricci et al. Oct 2014 A1
20140309871 Ricci Oct 2014 A1
20140309872 Ricci Oct 2014 A1
20140309873 Ricci Oct 2014 A1
20140309874 Ricci Oct 2014 A1
20140309875 Ricci Oct 2014 A1
20140309876 Ricci Oct 2014 A1
20140309877 Ricci Oct 2014 A1
20140309878 Ricci Oct 2014 A1
20140309879 Ricci Oct 2014 A1
20140309880 Ricci Oct 2014 A1
20140309885 Ricci Oct 2014 A1
20140309886 Ricci Oct 2014 A1
20140309891 Ricci Oct 2014 A1
20140309892 Ricci Oct 2014 A1
20140309893 Ricci Oct 2014 A1
20140309913 Ricci et al. Oct 2014 A1
20140309919 Ricci Oct 2014 A1
20140309920 Ricci Oct 2014 A1
20140309921 Ricci et al. Oct 2014 A1
20140309922 Ricci Oct 2014 A1
20140309923 Ricci Oct 2014 A1
20140309927 Ricci Oct 2014 A1
20140309929 Ricci Oct 2014 A1
20140309930 Ricci Oct 2014 A1
20140309934 Ricci Oct 2014 A1
20140309935 Ricci Oct 2014 A1
20140309982 Ricci Oct 2014 A1
20140310031 Ricci Oct 2014 A1
20140310075 Ricci Oct 2014 A1
20140310103 Ricci Oct 2014 A1
20140310186 Ricci Oct 2014 A1
20140310277 Ricci Oct 2014 A1
20140310379 Ricci et al. Oct 2014 A1
20140310594 Ricci et al. Oct 2014 A1
20140310610 Ricci Oct 2014 A1
20140310702 Ricci et al. Oct 2014 A1
20140310739 Ricci et al. Oct 2014 A1
20140310788 Ricci Oct 2014 A1
20140322676 Raman Oct 2014 A1
20140347207 Zeng et al. Nov 2014 A1
20140347265 Allen et al. Nov 2014 A1
20150007155 Hoffman et al. Jan 2015 A1
20150012186 Horseman Jan 2015 A1
20150032328 Healey Jan 2015 A1
20150032366 Man et al. Jan 2015 A1
20150032670 Brazell Jan 2015 A1
20150057839 Chang et al. Feb 2015 A1
20150061895 Ricci Mar 2015 A1
20150081133 Schulz Mar 2015 A1
20150081167 Pisz et al. Mar 2015 A1
20150088423 Tuukkanen Mar 2015 A1
20150088515 Beaumont et al. Mar 2015 A1
20150106204 Pudar Apr 2015 A1
20150116200 Kurosawa et al. Apr 2015 A1
20150120135 Lawrenson Apr 2015 A1
20150158499 Koravadi Jun 2015 A1
20150178034 Penilla et al. Jun 2015 A1
20150262239 Goralnick Sep 2015 A1
20150332330 Dawson et al. Nov 2015 A1
20160008985 Kim et al. Jan 2016 A1
20160070527 Ricci Mar 2016 A1
20160086391 Ricci Mar 2016 A1
20160232565 Goergen Aug 2016 A1
20160247221 Blumberg et al. Aug 2016 A1
20160253710 Publicover Sep 2016 A1
20160269456 Ricci Sep 2016 A1
20160269469 Ricci Sep 2016 A1
20170057516 Gordon Mar 2017 A1
20170217445 Tzirkel-Hancock Aug 2017 A1
20170349184 Tzirkel-Hancock Dec 2017 A1
20180122024 Carpenter May 2018 A1
20180137487 Wang May 2018 A1
20190012324 Parameswaran Jan 2019 A1
Foreign Referenced Citations (36)
Number Date Country
1417755 May 2003 CN
1847817 Oct 2006 CN
101303878 Nov 2008 CN
102467827 May 2012 CN
1223567 Jul 2002 EP
1484729 Dec 2004 EP
2192015 Jun 2010 EP
2004-284450 Oct 2004 JP
2006-0128484 Dec 2006 KR
WO 2007126204 Nov 2007 WO
WO 2012102879 Aug 2012 WO
WO 2013074866 May 2013 WO
WO 2013074867 May 2013 WO
WO 2013074868 May 2013 WO
WO 2013074897 May 2013 WO
WO 2013074899 May 2013 WO
WO 2013074901 May 2013 WO
WO 2013074919 May 2013 WO
WO 2013074981 May 2013 WO
WO 2013074983 May 2013 WO
WO 2013075005 May 2013 WO
WO 2013181310 Dec 2013 WO
WO 2014014862 Jan 2014 WO
WO 2014143563 Sep 2014 WO
WO 2014158667 Oct 2014 WO
WO 2014158672 Oct 2014 WO
WO 2014158766 Oct 2014 WO
WO 2014172312 Oct 2014 WO
WO 2014172313 Oct 2014 WO
WO 2014172316 Oct 2014 WO
WO 2014172320 Oct 2014 WO
WO 2014172322 Oct 2014 WO
WO 2014172323 Oct 2014 WO
WO 2014172327 Oct 2014 WO
WO 2016145073 Sep 2016 WO
WO 2016145100 Sep 2016 WO
Non-Patent Literature Citations (34)
Entry
U.S. Appl. No. 61/567,962, filed Dec. 7, 2011, Baarman et al.
“Automatic vehicle location,” Wikipedia, The Free Encyclopedia, Apr. 21, 2016 version, available at https://en.wikipedia.org/w/index.php?title=Automatic_vehicle_location&oldid=716386212, 6 pages.
“Automotive navigation system,” Wikipedia, The Free Encyclopedia, Dec. 10, 2016 version, available at https://en.wikipedia.org/w/index.php?title=Automotive_navigation_system&oldid=753968543, 5 pages.
“Global positioning system,” Wikipedia, The Free Encyclopedia, Dec. 29, 2016 version, available at https://en.wikipedia.org/w/index.php?title=Global_Positioning_System&oldid=757286677, 16 pages.
“Guide to Build Better Predictive Models using Segmentation,” Analytics Vidyha Guest Blog, Feb. 26, 2016, available at https://www.analyticsvidhya.com/blog/2016/02/guide-build-predictive-models-segmentation/, 13 pages.
“Map database management,” Wikipedia, The Free Encyclopedia, Nov. 15, 2016 version, available at https://en.wikipedia.org/w/index.php?title=Map_database_management&oldid=749668002, 7 pages.
“Nexus 10 Guidebook for Android,” Google Inc., © 2012, Edition 1.2, 166 pages.
“Predictive analytics,” Wikipedia, The Free Encyclopedia, Dec. 19, 2016 version, available at https://en.wikipedia.org/w/index.php?title=Predictive_analytics&oldid=755669107, 18 pages.
“Self-Driving: Self-Driving Autonomous Cars,” available at http://www.automotivetechnologies.com/autonomous-self-driving-cars, accessed Dec. 2016, 9 pages.
Amor-Segan et al., “Towards the Self Healing Vehicle,” Automotive Electronics, Jun. 2007, 2007 3rd Institution of Engineering and Technology Conference, 7 pages.
Bennett, “Meet Samsung's Version of Apple AirPlay,” CNET.com, Oct. 10, 2012, 11 pages.
Cairnie et al., “Using Finger-Pointing to Operate Secondary Controls in Automobiles,” Proceedings of the IEEE Intelligent Vehicles Symposium 2000, Oct. 3-5, 2000, 6 pages.
Clark, “How Self-Driving Cars Work: The Nuts and Bolts Behind Google's Autonomous Car Program,” Feb. 21, 2015, available at http://www.makeuseof.com/tag/how-self-driving-cars-work-the-nuts-and-bolts-behind-googles-autonomous-car-program/, 9 pages.
Davies, “This NIO EP9 performance EV wants to be the Tesla of Supercars,” SlashGear, 2016, retrieved from https//www.slashgear.com/nextev-nio-ep9-car-tesla-of-performance-evs-21464829, 6 pages.
Deaton et al., “How Driverless Cars Will Work,” Jul. 1, 2008, HowStuffWorks.com. <http://auto.howstuffworks.com/under-the-hood/trends-innovations/driverless-car.htm> Sep. 18, 2017, 10 pages.
Dumbaugh, “Safe Streets, Livable Streets: A Positive Approach to urban Roadside Design,” Ph.D. dissertation for School of Civil & Environ. Engr., Georgia Inst. of Technology, Dec. 2005, 235 pages.
Fei et al., “A QoS-aware Dynamic Bandwidth Allocation Algorithm for Relay Stations in IEEE 802.16j-based Vehicular Networks,” Proceedings of the 2010 IEEE Global Telecommunications Conference, Dec. 10, 2010, 10 pages.
Ge et al., “Optimal Relay Selection in IEEE 802.16j Multihop Relay Vehicular Networks,” IEEE Transactions on Vehicular Technology, 2010, vol. 59(5), pp. 2198-2206.
Guizzo, Erico, “How Google's Self-Driving Car Works,” Oct. 18, 2011, available at https://spectrum.ieee.org/automaton/robotics/artificial-intelligence/how-google-self-driving-car-works, 5 pages.
Heer et al., “ALPHA: An Adaptive and Lightweight Protocol for Hop-by-hop Authentication,” Proceedings of CoNEXT 2008, Dec. 2008, pp. 1-12.
Jahnich et al., “Towards a Middleware Approach for a Self-Configurable Automotive Embedded System,” International Federation for Information Processing, 2008, pp. 55-65.
Kautonen, “NextEV unveils the NIO EP9 electric supercar in London,” Autoblog, 2016, retrieved from http://www.autoblog.com/2016/11/21/nextev-unveiles-the-nio-ep9-electric-supercar-in-london/, 3 pages.
Pentland et al., “Modeling and Prediction of Human Behavior,” Neural Computation, 1999, vol. 11, pp. 229-242.
Persson “Adaptive Middleware for Self-Configurable Embedded Real-Time Systems,” KTH Industrial Engineering and Management, 2009, pp. iii-71 and references.
Raychaudhuri et al., “Emerging Wireless Technologies and the Future Mobile Internet,” p. 48, Cambridge Press, 2011, 3 pages.
Stephens, Leah, “How Driverless Cars Work,” Interesting Engineering, Apr. 28, 2016, available at https://interestingengineering.com/driverless-cars-work/, 7 pages.
Stoller, “Leader Election in Distributed Systems with Crash Failures,” Indiana University, 1997, pp. 1-15.
Strunk et al., “The Elements of Style,” 3d ed., Macmillan Publishing Co., 1979, 3 pages.
Suwatthikul, “Fault detection and diagnosis for in-vehicle networks,” Intech, 2010, pp. 283-286 [retrieved from: www.intechopen.com/books/fault-detection-and-diagnosis-for-in-vehicle-networks].
Walter et al., “The smart car seat: personalized monitoring of vital signs in automotive applications.” Personal and Ubiquitous Computing, Oct. 2011, vol. 15, No. 7, pp. 707-715.
White, “NextEV's NIO IP9 is an incredible four-wheel-rive electric hypercar,” WIRED, 2016, retrieved from http://www.wired.co.uk/article/nextev-hypercar-nio-ep9, 6 pages.
Wolf et al., “Design, Implementation, and Evaluation of a Vehicular Hardware Security Module,” ICISC'11 Proceedings of the 14th Int'l Conf. Information Security & Cryptology, Springer-Verlag Berlin, Heidelberg, 2011, pp. 302-318.
International Search Report and Written Opinion for PCT Application No. PCT/US2017/062709, dated Feb. 6, 2018, 25 pages.
International Preliminary Report on Patentability for PCT Application No. PCT/US2017/062709; dated May 31, 2019, 23 pages.
Related Publications (1)
Number Date Country
20180144369 A1 May 2018 US
Provisional Applications (1)
Number Date Country
62424976 Nov 2016 US