US20140380442A1 - System and method for enabling secure transactions using flexible identity management in a vehicular environment - Google Patents
System and method for enabling secure transactions using flexible identity management in a vehicular environment Download PDFInfo
- Publication number
- US20140380442A1 US20140380442A1 US14/484,664 US201414484664A US2014380442A1 US 20140380442 A1 US20140380442 A1 US 20140380442A1 US 201414484664 A US201414484664 A US 201414484664A US 2014380442 A1 US2014380442 A1 US 2014380442A1
- Authority
- US
- United States
- Prior art keywords
- agent
- vehicle
- identity
- obu
- identity profile
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 241000497429 Obus Species 0.000 claims description 3
- 230000006854 communication Effects 0.000 description 97
- 238000004891 communication Methods 0.000 description 96
- 238000013507 mapping Methods 0.000 description 48
- 230000009471 action Effects 0.000 description 25
- 238000012545 processing Methods 0.000 description 20
- 238000007726 management method Methods 0.000 description 19
- 230000000694 effects Effects 0.000 description 12
- 230000008859 change Effects 0.000 description 11
- 238000013475 authorization Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 230000001413 cellular effect Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 241000282412 Homo Species 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000006855 networking Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000000977 initiatory effect Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000037361 pathway Effects 0.000 description 4
- 230000003213 activating effect Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 238000013478 data encryption standard Methods 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 2
- 230000008867 communication pathway Effects 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 230000001276 controlling effect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 101001093748 Homo sapiens Phosphatidylinositol N-acetylglucosaminyltransferase subunit P Proteins 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000001010 compromised effect Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 238000000275 quality assurance Methods 0.000 description 1
- 230000002459 sustained effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
- H04W52/0219—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave where the power saving management affects multiple terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/08—Interaction between the driver and the control system
- B60W50/10—Interpretation of driver requests or demands
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/017—Gesture based interaction, e.g. based on a set of recognized hand gestures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/16—Sound input; Sound output
- G06F3/167—Audio in a user interface, e.g. using voice commands for navigating, audio feedback
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
- H04L1/0079—Formats for control data
- H04L1/008—Formats for control data where the control data relates to payload of a different packet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
- H04L43/0858—One way delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/12—Shortest path evaluation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/02—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2592—Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0227—Filtering policies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q9/00—Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/03—Protecting confidentiality, e.g. by encryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
- H04W40/20—Communication route or path selection, e.g. power-based or shortest path routing based on geographic position or location
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/02—Access restriction performed under specific conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/02—Access restriction performed under specific conditions
- H04W48/06—Access restriction performed under specific conditions based on traffic conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
- H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
- H04W52/0264—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by selectively disabling software applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/06—TPC algorithms
- H04W52/12—Outer and inner loops
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/40—Connection management for selective distribution or broadcast
- H04W76/45—Connection management for selective distribution or broadcast for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0009—Control or signalling for completing the hand-off for a plurality of users or terminals, e.g. group communication or moving wireless networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/06—TPC algorithms
- H04W52/14—Separate analysis of uplink or downlink
- H04W52/143—Downlink power control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/18—TPC being performed according to specific parameters
- H04W52/22—TPC being performed according to specific parameters taking into account previous information or commands
- H04W52/225—Calculation of statistics, e.g. average, variance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/18—TPC being performed according to specific parameters
- H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
- H04W52/241—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account channel quality metrics, e.g. SIR, SNR, CIR, Eb/lo
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/30—TPC using constraints in the total amount of available transmission power
- H04W52/34—TPC management, i.e. sharing limited amount of power among users or channels or data types, e.g. cell loading
- H04W52/346—TPC management, i.e. sharing limited amount of power among users or channels or data types, e.g. cell loading distributing total power among users or channels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/005—Moving wireless networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/18—Interfaces between hierarchically similar devices between terminal devices
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A30/00—Adapting or protecting infrastructure or their operation
- Y02A30/60—Planning or developing urban green infrastructure
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- This invention relates in general to the field of electronic communications and, more particularly, to enabling secure transactions using flexible identity management in a vehicular environment.
- Networking architectures have grown increasingly complex and have been designed for use in a wide variety of communications environments. Demand continues to rise among the subscriber base of end users, however, for network access across diverse network environments. In particular, configuring suitable network architecture for vehicular environments (e.g., automobiles, airplanes, trains, boats, etc.) presents unique difficulties. Vehicles can be mobile across a large geographic area, can have internal networks related to the vehicle itself, can include more than one end user at a time, and can have more than one owner during the life of the vehicle. Providing the ability to conduct transactions in vehicular network environments in a secure manner and providing a secure and flexible identity management framework for various agents conducting the transactions present significant challenges to system designers, automobile manufacturers, service providers, and the like.
- vehicular environments e.g., automobiles, airplanes, trains, boats, etc.
- FIG. 1 is a simplified schematic diagram of a communication system for enabling secure transactions using flexible identity management in a vehicular environment in accordance with embodiments of the present disclosure
- FIG. 2 is a simplified schematic diagram of the communication system in exemplary network environments associated with embodiments the present disclosure
- FIG. 3 is another simplified schematic diagram of the communication system in exemplary network environments associated with embodiments of the present disclosure
- FIG. 4 is a simplified block diagram of an on-board unit of the communication system and possible agents of the on-board unit;
- FIG. 5 is a block diagram of a plurality of identity profiles in an example scenario of the communication system.
- FIGS. 6-15 are simplified flowcharts associated with possible activities associated with the communication system of the present disclosure.
- a method in one example embodiment includes detecting an event for a transaction on an on-board unit (OBU) of a vehicle, where the event has a trigger associated with an agent.
- the method also includes determining whether the transaction is authorized, identifying network credentials of the agent, and providing the network credentials to a transaction application corresponding to the transaction.
- the method further includes accessing a remote network using the network credentials.
- the network credentials are identified in an identity profile associated with the agent.
- the method includes providing application programming interfaces (APIs) to the transaction application to enable the transaction application to access one or more of a plurality of pieces of information of the identity profile.
- the method includes evaluating a memory element to determine whether the transaction application is mapped to the agent.
- a method in an another example embodiment includes initiating a transaction on an on board unit (OBU) of a vehicle and selecting first network credentials for a transaction application associated with the transaction to establish a network connection between the OBU and a remote node.
- the first network credentials are selected from a plurality of available network credentials that correspond to an agent associated with the transaction.
- the first network credentials include one or more virtual subscriber identity modules (VSIMs).
- VSIMs virtual subscriber identity modules
- the first network credentials are selected based on a mapping of the first network credentials to one or more predefined criteria and the agent.
- a method in yet another example embodiment includes authenticating a first agent to an on board unit (OBU) of a vehicle if the first agent validates a first set of one or more authentication requirements and identifying a first identity profile corresponding to the first agent.
- the method also includes determining a role of the first agent in the vehicle and configuring the vehicle with the first identity profile, where the vehicle is configured based on the role of the first agent.
- the first identity profile is one of a plurality of identity profiles provisioned on the OBU.
- FIG. 1 is a simplified block diagram of a communication system 10 for enabling secure transactions using flexible identity management in a vehicular environment.
- the example architecture of FIG. 1 includes an end user (driver) 2 operating a vehicle 4 that includes an on-board unit (OBU) 30 .
- OBU 30 includes processing elements 21 , which include a computing processor 22 and a routing processor 23 .
- OBU 30 also includes a memory element 24 , network interfaces 26 , a user interface 27 , and a display 28 .
- OBU 30 can be suitably coupled to a plurality of sensors 14 a - c , a plurality of controls (e.g., electronic control units (ECUs)) 16 a - c , and a plurality of actuators, such as actuator 13 .
- sensors 14 a - b and controls 16 a - b may be part of an automotive diagnostic system, indicated by vehicle diagnostics 19 , which may also be suitably integrated with OBU 30 .
- OBU 30 may also be suitably coupled to various in-vehicle mobile devices 18 a - b at any given time, where such devices may be associated with particular end users (passengers or driver) within vehicle 4 .
- OBU 30 may also include capabilities associated with navigation system 17 (e.g., a global positioning system (GPS)).
- FIG. 1 also includes networks 40 , representing various types of connectivity to vehicle 4 (e.g., via antenna 29 ). Each established network of networks 40 has a logical coupling to remote network nodes or other external electronic devices, which may include transaction systems 50 , authorized entities 98 , and other vehicles 59 .
- GPS global positioning system
- Communication system 10 may include a configuration capable of transmission control protocol/Internet protocol (TCP/IP) communications for the electronic transmission or reception of packets in a network.
- Communication system 10 may also operate in conjunction with a user datagram protocol/IP (UDP/IP) or any other suitable protocol, where appropriate and based on particular needs.
- TCP/IP transmission control protocol/Internet protocol
- UDP/IP user datagram protocol/IP
- communication system 10 may also include a configuration capable of accommodating legacy bus subsystems that may be employed to convey information across the myriad of machine devices (e.g., sensors 14 a - c , controls 16 a - c , actuator 13 ) in vehicle 4 .
- machine devices e.g., sensors 14 a - c , controls 16 a - c , actuator 13 .
- Embodiments of communication system 10 can enable secure transactions in a vehicular environment by using flexible identity management for agents associated with the transactions.
- agents e.g., machine devices, humans, software agents, mobile devices, and authorized entities
- possible transactions e.g., accessing one or more wireless/mobile/cellular networks and using network bandwidth and services, gaining access to various resources of the vehicle based on an identity profile and/or associated databases, gaining access to transaction applications in the vehicle, and engaging in commercial activities
- numerous transaction scenarios may occur over the life of the vehicle.
- Such transaction scenarios may encompass, for example, toll or parking payments, vehicle miles traveled (VMT) systems, Internet commerce, original equipment manufacturer (OEM), gas and electric charging stations, roadside and/or drive-through kiosks, banking applications, vehicle dealer systems, location based service (LBS) system, vehicle system and its resources, mobile network operator system, travel agencies, rental and leasing agencies, network connection to Internet sites, vehicle-to-vehicle commerce, vehicle-to-mobile-device commerce, in-vehicle commerce systems, etc.
- VMT vehicle miles traveled
- OEM original equipment manufacturer
- LBS location based service
- Communication system 10 may include on-board unit (OBU) 30 that validates credentials of each agent, grants appropriate levels of access, manages potential conflicts (e.g., by assigning priority to different agents), and provisions the appropriate wireless/mobile connectivity.
- An agent may be provisioned for authentication and access to a particular vehicle by provisioning at least one virtual subscriber identity module (VSIM) and/or an identity profile in OBU 30 of communication system 10 .
- VSIM virtual subscriber identity module
- an individualized, multi-factor authorization process may be used to validate the particular agent's credentials for accessing OBU 30 and for authorizing transactions on OBU 30 .
- Authentication and confidentiality schemes may be specified for transaction applications corresponding to the particular transactions.
- appropriate wireless/mobile connectivity may be dynamically determined by evaluating the transaction, the agent, and a current geographical location of the vehicle.
- vehicular transactions may be securely enabled by managing the identity and authentication of agents associated with transactions.
- CAN controller-area network
- GPS geographical positioning system
- personal mobile devices e.g., mobile phones, smart mobile phones/devices, e-book readers, tablets, laptops/net books, portable navigation systems, multimedia devices, etc.
- a CAN bus is a vehicle bus standard designed to allow microcontrollers, sensors, and other devices associated with a vehicle to communicate with each other within the vehicle (e.g., without a host computer).
- CAN is a message based protocol, designed for and typically used by automotive applications.
- the CAN bus can be used to provide real-time vehicle diagnostics from associated sensors and controls to a manufacturer of the vehicle or to any other authorized entity.
- a separate network in the vehicle may exist for IP devices involved in the vehicle navigation system (e.g., GPS) and, possibly, another network associated with simple content delivery.
- Other networks could be used for Internet access for end users through, for example, mobile devices.
- various levels of network usage, different purposes of network usage, and different agents (e.g., humans, machine devices, external devices, mobile devices) associated with the network usage may occur in a single vehicle.
- Network usage in each of the identified cases may have a different usage scope, different latency, different associated routing, different policy requirements, and the like.
- each of the devices associated with a particular network may have a one-to-one mapping to either a human agent or to the vehicle. Network access and any resulting fees from such access are typically dictated by the human agent or vehicle mapped to the particular device. While some of these devices may be used by other human agents (e.g., another human agent borrows a cell phone, has account privileges on a laptop, borrows an automobile with a GPS, etc.) network access and fee accrual does not ordinarily accommodate the preferences of the new user.
- a mobile router used to facilitate network access among various agents associated with a vehicle could provide predetermined network access and billing, without regard to the particular agent or transaction.
- a vehicle that provides networking capabilities between entities inside the vehicle and the external world (“connected vehicle”)
- the amount of possible transactions and the changeability of agents associated with those transactions require a flexible framework to ensure security and appropriate network access.
- multiple agents may use the vehicle and perform transactions on or via the vehicle over any given time period.
- Individual users such as, for example, an owner, a driver, a passenger, a temporary driver (e.g., borrower or renter), or a new owner of a used automobile, may use the vehicle as a personal computing and communication platform for navigational, recreational, and/or business-related purposes.
- a manufacturer of the vehicle may want to collect vehicle centric data from the vehicle and send firmware/software upgrades to the vehicle.
- Government entities may want to identify and locate the vehicle for law enforcement or government regulation (e.g., emissions controls) purposes.
- Vehicle dealers may want to obtain sensor data and other vehicle diagnostic information for maintenance updates and/or scheduling.
- a one-to-one exclusive mapping between an agent (e.g., a human or a device) and a connected vehicle does not exist.
- a one-to-one mapping is typically provided between a mobile phone and a single user.
- credentials that bind the user and the device may be stored in a physical subscriber identity module (SIM) or provisioning module.
- SIM subscriber identity module
- the mobile device is subsequently operated by a new user (e.g., someone borrowing the mobile phone)
- the credentials in the current SIM, associated with the original user will be used to access a cellular network and to bill for the network access usage.
- the original user mapped to the mobile phone will be billed for any network usage fees incurred by the new user.
- the mobile phone can be provisioned with the new user's credentials by physically replacing the existing SIM hardware with a SIM of the new user.
- SIM swapping or identity reassignment across different service providers is often problematic or simply not feasible in a mobile phone.
- agents may change over any given period of time, and it may be impossible or impractical to physically switch a SIM in the vehicle or to make a trip to a service center each time a new agent needs network access to or from the vehicle.
- a manufacturer of an automobile may want to use a transaction application to collect real time data from sensors in the vehicle. If the automobile is manufactured in one country and shipped to another country (e.g., manufactured in Japan and shipped to the United States), then before the automobile is even purchased it would have traveled across international boundaries and multiple telecom service provider areas. Thus, if the manufacturer (i.e., the agent) provisions the automobile with credentials for a first service provider usable in the first country, the manufacturer may prefer a different service provider to be provisioned in the automobile once the automobile is shipped to another country.
- Another example of possible agent changes in a vehicle includes owners, drivers, renters, and passengers of a vehicle.
- the new owner needs access rights to various transactions (e.g., toll payments, gas and charging stations, Internet commerce, personal vehicle settings, etc.) provided by the vehicle.
- the new owner may need wireless access to networks and devices external to the vehicle using an appropriate service provider and a desired billing scheme. These access rights may need to change each time the vehicle is driven by a different driver (e.g., another person in the owner's family, a current renter of a rental car, etc.).
- a new owner and associated drivers and passengers also need access rights and the previously existing access rights need to be removed from the vehicle.
- multiple agents may want to access the vehicle concurrently, such as a driver and one or more passengers of the vehicle who desire access rights to at least some of the vehicle transactions.
- a passenger may want to use an Internet commerce transaction to download music or videos, or the passenger may want to pay for transportation costs, such as toll expenses and/or gas and charging station expenses.
- Supporting a multi-agent and multi-transaction vehicular environment may also require more protection layers than typically used in traditional authentication schemes such as a simple user identification (“user ID”) and password.
- additional protection layers may be necessary for certain transactions and agents to avoid compromising security (e.g., highly sensitive transactions such as transactions allowing modifications by a manufacturer of the vehicle itself) and/or regulatory compliance of a transaction.
- security e.g., highly sensitive transactions such as transactions allowing modifications by a manufacturer of the vehicle itself
- regulatory compliance of a transaction e.g., highly sensitive transactions such as transactions allowing modifications by a manufacturer of the vehicle itself
- flexible agent identity management is needed with a strong authentication component that provides adequate security for dynamically changing agents and transactions, such that security, privacy, authenticity, accountability, and regulatory compliance are not compromised.
- a system for enabling secure transactions in a vehicular environment using flexible identity management for agents associated with the transactions can resolve many of these issues.
- a method for agent identity management that is flexible, secure, and allows network access to be switched dynamically for different agents.
- the method provides for authenticating an agent to on-board unit (OBU) 30 of vehicle 4 , provisioning an identity profile associated with the agent, and provisioning one or more virtual subscriber identity modules (VSIMs) associated with the agent.
- the identity profile can include individualized vehicle preferences (e.g., seat position, cabin temperature settings, radio or other media, navigation locations, etc.).
- Boundaries such as parental controls and transaction access controls may also be provided in an identity profile, which can be added by another agent having appropriate authority.
- the method also provides for verifying whether a particular transaction is authorized when the transaction is associated with the agent. For authorized transactions requiring remote network access to external devices, the method allows for opportunistic selection of network credentials, such as VSIMs, WiFi, etc., associated with the particular agent, which may be determined by evaluating the agent, the transaction, and a current geographical location of the vehicle.
- network credentials such as VSIMs, WiFi, etc.
- network access can be opportunistically selected depending on one or more factors, including the agent, the transaction and the current location of the vehicle.
- references to various features e.g., elements, structures, modules, components, steps, operations, characteristics, etc.
- references to various features e.g., elements, structures, modules, components, steps, operations, characteristics, etc.
- references to various features are intended to mean that any such features are included in one or more embodiments of the present disclosure, but may or may not necessarily be combined in the same embodiments.
- end user 2 can be associated with a human agent (e.g., a driver or passenger) having any type of relationship to the vehicle such as an owner, a renter, a temporary driver, a family member or friend of the owner, etc.
- End user 2 may initiate communication in communication system 10 via some network, and such communication may be initiated through any suitable device, inclusive of an in-vehicle mobile device 18 a or 18 b , display 28 , and navigation system 17 .
- additional displays may be provided for one or more passengers in vehicle 4 .
- In-vehicle mobile devices 18 a - b are inclusive of mobile phones, smart mobile phones (smartphones), e-book readers, tablets, iPads, personal digital assistants (PDAs), laptops or electronic notebooks, portable navigation systems, multimedia gadgets (e.g., cameras, players, etc.), and any other device, component, element, or object capable of initiating voice, audio, video, media, or data exchanges within communication system 10 .
- Data refers to any type of numeric, voice, video, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another in electronic devices and/or networks.
- In-vehicle mobile devices 18 a - b may communicate with OBU 30 of communication system 10 through any wired or wireless communication link and may be configured as a personal area network (PAN) or a wireless personal area network (WPAN) or any other appropriate architecture or system that facilitates communications in a network environment.
- Wired and wireless communication links may be inclusive of any electronic link such as Bluetooth, wireless technologies (e.g., IEEE 802.11x), a USB cable, an HDMI cable, etc.
- Connection between mobile devices and OBU 30 may be configured based on particular needs and logistics.
- an external mobile device may be connected to OBU 30 through a USB cable or wireless network when, for example, the external mobile device is a diagnostic tool used by a mechanic for servicing vehicle 4 .
- Networks 40 represent a series of points or nodes of interconnected communication paths for receiving and transmitting packets of information that propagate through communication system 10 .
- Networks 40 offer communicative interfaces between any of the components of FIG. 1 and remote network nodes and other electronic devices (e.g., transaction systems 50 , authorized entities 98 , and other vehicles 59 ), and may be any local area network (LAN), wireless local area network (WLAN), wide area network (WAN), wireless wide area network (WWAN), metropolitan area network (MAN), wireless metropolitan area network (WMAN), wireless single hop or multi-hop vehicle-to-vehicle network, virtual private network (VPN), Intranet, Extranet, or any other appropriate architecture or system that facilitates communications in a network environment.
- LAN local area network
- WLAN wireless local area network
- WAN wide area network
- WWAN wireless wide area network
- MAN metropolitan area network
- WMAN wireless metropolitan area network
- VPN virtual private network
- Intranet Extranet, or any other appropriate architecture or system that facilitates communications in a
- Networks 40 may include any suitable communication link to OBU 30 such as wireless technologies (e.g., IEEE 802.11x), satellite, cellular technologies (e.g., 3G, 4G, etc.), etc., or any combination thereof.
- Networks 40 may also include configurations capable of transmission control protocol/Internet protocol (TCP/IP) communications, user datagram protocol/IP (UDP/IP), or any other suitable protocol, where appropriate and based on particular needs.
- TCP/IP transmission control protocol/Internet protocol
- UDP/IP user datagram protocol/IP
- Embodiments of OBU 30 may include one or more distinct interfaces, represented by network interfaces 26 , to facilitate communication via the various networks described herein.
- network interfaces 26 may be inclusive of multiple wireless interfaces (e.g., WiFi, WiMax, 3G, 4G, white space, 802.11x, satellite, Bluetooth, LTE, GSM/HSPA, CDMA/EVDO, DSRC, CAN, GPS etc.).
- Other interfaces represented by network interfaces 26 may include physical ports (e.g., Ethernet, USB, HDMI, etc.), and the like.
- each of the network elements and user equipment (e.g., mobile devices) of communication system 10 can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.
- OBU 30 can include one or more memory elements (e.g., memory element 24 ) for storing information to be used in achieving operations associated with the enablement of secure transactions using flexible identity management, as outlined herein. Any of the memory or storage items discussed herein should be construed as being encompassed within the broad term ‘memory element’ as used herein in this Specification.
- the operations for enabling secure transactions using flexible identity management outlined herein may be implemented by logic encoded in one or more tangible media, which may be inclusive of non-transitory media (e.g., embedded logic provided in an ASIC, digital signal processor (DSP) instructions, software potentially inclusive of object code and source code to be executed by a processor or other similar machine, etc.).
- non-transitory media e.g., embedded logic provided in an ASIC, digital signal processor (DSP) instructions, software potentially inclusive of object code and source code to be executed by a processor or other similar machine, etc.
- one or more memory elements e.g., memory element 24
- OBU 30 may include processing elements 21 , including computing processor 22 and routing processor 23 , that can execute software or algorithms to perform the activities to enable secure transactions, to use flexible identity management, and to route packets, using suitable routing protocols, associated with the secure transactions and identity management.
- a processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, the processors (as shown in FIG. 1 ) could transform an element or an article (e.g., data) from one state or thing to another state or thing.
- the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., an FPGA, an EPROM, an EEPROM), or an ASIC that includes digital logic, software, code, electronic instructions, flash memory, optical disks, CD-ROMs, DVD ROMs, magnetic or optical cards, other types of machine-readable mediums suitable for storing electronic instructions, or any suitable combination thereof.
- programmable digital logic e.g., an FPGA, an EPROM, an EEPROM
- ASIC programmable digital logic
- any suitable permutation may be applied based on particular needs and requirements, including the design of the particular vehicle in which OBU 30 is implemented.
- various components of OBU 30 may be installed in different physical areas of the vehicle or may be installed as single unit, with display 28 being positioned to allow driver access.
- Other displays may be provided in suitable locations for access by passengers in particular passenger seats.
- multimedia, networking, and communication components may be positioned at some distance from the vehicle engine (e.g., in or near the rear or trunk area if the engine is in the front area of the vehicle).
- Communication system 10 may be configured to facilitate communication with machine devices (e.g., vehicle sensors, instruments, electronic control units (ECUs), embedded devices, actuators, etc.).
- OBU 30 may be implemented to provide one or more suitable communication interfaces (e.g., network interfaces 26 ) to legacy systems in vehicles such as, for example, a controller area network (CAN) a low speed network (LIN), a flexray communications protocol network, media oriented systems transport (MOST), and the like.
- CAN controller area network
- LIN low speed network
- MOST media oriented systems transport
- Sensors 14 a - b may represent, for example, wheel and headlight sensors, respectively.
- Controls 16 a - b may be inclusive of any embedded system or ECU that controls one or more of the electrical systems or subsystems in vehicle 4 .
- Actuator 13 represents a vehicle setting device such as, for example, a seat positioning device for adjusting various seat positions (e.g., longitudinal position relative to the brake and gas pedals, tilt position, lumbar support, etc.). Actuator 13 and other similar vehicle setting devices (e.g., temperature controls, sunroof, door locks, power windows, etc.) may be configured for communications in a LIN bus, in one embodiment.
- Sensor 14 c represents a type of sensor or device that may be configured for communications via flexray communications protocol (e.g., a radar collision sensor).
- Control 16 c representing one or more ECUs, may be suitably integrated for controlling the flexray network and sensors and other associated components. Additionally, OBU 30 may be implemented to provide one or more suitable communication interfaces (e.g., network interfaces 26 ) to an Internet Protocol (IP) network, user datagram protocol (UDP) network, or any other suitable protocol or communication architecture provided to enable network communication with machine devices in vehicle 4 .
- IP Internet Protocol
- UDP user datagram protocol
- vehicle 4 includes capabilities associated with navigation system 17 and vehicle diagnostics 19 .
- Navigation system 17 may be provided in various embodiments including, for example, a portable navigation system or, alternatively, a fixed navigation system, each of which may be configured for wireless or wired communications to OBU 30 .
- Other more specific machine devices may include display panel instruments, climate controls, interior lights, door locks, trunk open/shut actuator, hood open/shut actuator, seat heater and/or cooler, sunroof open/shut actuator, window heater/defroster/defogger, entertainment systems (e.g., speakers, radio, DVD, CD, etc.), and the like.
- agents 90 can include machine devices 92 , humans 94 , and mobile devices 96 .
- agents can also include software agents 95 and authorized entities 98 .
- Software agents 95 can include any executable file comprising instructions that can be understood and processed on a computer, and provisioned in a memory element accessible to OBU 30 (e.g., memory element 24 ), and which may be initiated automatically in response to a particular set of criteria or conditions (e.g., every time network connectivity is detected on OBU 30 , whenever OBU 30 is powered on and a particular time interval has passed, in response to another software agent, etc.).
- Authorized entities 98 may include various entities having authorization to access a vehicle 4 such as, for example, a dealer of the vehicle, a manufacturer of the vehicle, OEMs associated with the vehicle, and public entities having an interest in the vehicle (e.g., State Departments of Transportation, local police departments, etc.).
- a network node of such authorized entities will typically be remotely located from OBU 30 and, therefore, accessible from OBU 30 through networks 40 such as the Internet or other WANs and any available communication link (e.g., 3G, 4G, local wireless, etc.) providing network access from OBU 30 to the Internet or other WAN.
- OBU 30 may be locally accessible to an authorized entity such that Internet access is unnecessary.
- OBU 30 may be capable of directly accessing the manufacturer's network through a LAN or WLAN.
- the OBU 30 may connect to the dealer network through a communication link that does not include the Internet or any other wide area network.
- Networks 40 may also facilitate communication between certain agents 90 (e.g., machine devices 92 , humans 94 , software agents 95 , mobile devices 96 ) and transaction systems 50 .
- transaction systems 50 may include services transaction systems 52 , commercial transaction systems 54 , roadside transaction systems 56 , and transportation transaction systems 58 on network nodes or other electronic devices. Each of the transaction systems can be associated with many different types of entities and many different transaction scenarios.
- Services transaction systems 52 can encompass numerous entities providing services such as identity service providers, mobile wireless service providers, banks and other financial institutions, location-based services (LBS), travel agencies, vehicle rental and leasing agencies, Internet websites, etc.
- LBS location-based services
- a vehicle rental and leasing entity may be provisioned as an agent of the OBU, such as when the vehicle itself is owned by the rental and leasing entity.
- the rental and leasing agency could be an authorized entity of vehicle 4
- any authorized employees could be human agents of the vehicle.
- Commercial transaction systems 54 may include entities facilitating commercial transactions through the Internet (e.g., video and music download sites, online retailers, etc.), etc.
- Roadside transaction systems 56 may include various entities providing roadside services such as gas and electric charging stations, kiosks (both roadside and drive-through), etc.
- Transportation transaction systems 58 may include entities or devices facilitating vehicle charging transactions related to toll payments, ferry charges, bridge toll payments, parking, Vehicle Miles Traveled (VMT), and any other transportation costs incurred as a result of moving vehicle 4 from one location to another.
- the transaction systems 52 , 54 , 56 , and 58 as categorized, are provided for purposes of illustration and ease of understanding, and it will be appreciated that certain entities may logically be included in multiple transaction systems (e.g., a bank could be described as both a services transaction system and a commercial transaction system) and that numerous types of transaction systems and entities other than those enumerated herein may also be possible.
- An available network represented by networks 40 may provide a communicative pathway between vehicle 4 and other vehicles 59 , where vehicle 4 includes OBU 30 and other vehicles 59 include a suitable communication device (e.g., mobile device, OBU or similar device).
- the communicative pathway between vehicle 4 and other vehicles 59 could be established as a single hop or multi-hop vehicle-to-vehicle network through WiFi, WiMax, or any other suitable wireless technologies allowing a sustained connection between vehicle 4 and other vehicles 59 .
- communication system 10 depicts a more detailed representation of certain elements of OBU 30 , and of networks 40 providing a communication pathway to a particular service transaction system 52 (i.e., an identity service provider 60 ).
- end user computer 42 and mobile devices 96 are also shown with network access to identity service provider 60 .
- one or more virtual subscriber identity modules 32 a , 32 b , and 32 c (referred to collectively herein as VSIMs 32 ) may be provisioned in OBU 30 for each agent authenticated to the OBU and having a subscription with a mobile network operator providing cellular services (e.g., AT&T, Verizon, T-Mobile, Sprint, PCS, etc.).
- a mobile network operator providing cellular services
- VSIMs 32 each include a unique identifier or key 33 that identifies an agent on mobile telephony devices such as OBU 30 .
- VSIMs 32 may also contain security authentication to authenticate the agent to the corresponding mobile network operator.
- one or more VSIMs 32 may be provisioned in OBU 30 for each agent of OBU 30 , and multiple VSIMs for one or more agents can be stored in OBU 30 concurrently.
- Multiple VSIMs 32 provisioned in OBU 30 can enable flexible and opportunistic use of available mobile network operators to provide one or more network access links from OBU 30 to a remote node, and can also enable these network access links (i.e., communication pathways) on behalf of multiple agents using OBU 30 as a communication source.
- OBU 30 is equipped with a Universal Integrated Circuit Card (UICC) that allows for multiple universal subscriber identity module (USIM) applications to accommodate VSIMs 32 .
- UICC Universal Integrated Circuit Card
- USIM universal subscriber identity module
- one or more of VSIMs 32 having a desired mobile network operator may be opportunistically selected, if certain criteria are met, so that the desired one or more mobile network operators can be utilized for network access from OBU 30 .
- multiple SIM cards may be connected to OBU 30 to accommodate a corresponding number of VSIMs.
- a software module could be configured to opportunistically select an appropriate one or more SIM cards corresponding to a desired one or more mobile network operators if certain criteria are met.
- VSIMs could be simply soft SIM information stored in a storage repository of OBU 30 such as part of an identity profile of a corresponding agent. Once downloaded, VSIMs 32 can reside in OBU 30 in accordance with whatever particular implementation is employed, until an expiration of the VSIM or until the VSIM is replaced, updated, or removed by an agent with appropriate authentication and authorization.
- OBU 30 may also be provisioned with one or more identity profiles 34 a , 34 b , and 34 c (referred to collectively herein as identity profiles 34 ), with each identity profile 34 corresponding to an agent that can authenticate to OBU 30 .
- Identity profiles 34 can include credentials and profile information for a particular agent. Credentials contain information that uniquely identifies an agent (e.g., a personal identifier (PID)) and that may be used for authentication purposes.
- PID personal identifier
- credentials may include one or more of name, address, phone number, driver's license number, social security number, business license number, IP address, user ID/password, biometrics, personal device identifier (e.g., authentication information corresponding to key fob, access card, credit card, mobile phone, etc.), security keys, and certificates (e.g., public key infrastructure (PKI) certificate, trusted third party (TTP) certificate, etc.).
- PKI public key infrastructure
- TTP trusted third party
- Profile information aggregates agent attributes, account information, preferences, and/or settings, which can enable appropriate transactions by authenticated agents.
- profile information can include vehicle settings, dashboard preferences, wireless interface preferences (e.g., VSIM information, WiFi account information, etc.), web account information (e.g., multimedia, social networking, etc.), mobile device list (e.g., smartphones, mobile phones, tablets, laptops, etc.) including network configurations for mobile devices, network service provider membership account information, insurance information, credit card/payment account information, manufacturer web account information, network interface account information, GPS favorite locations, and phone contact list.
- the information included in a particular identity profile will be at least partially dependent upon the particular agent to which it corresponds.
- an authorized entity e.g., a manufacturer of the vehicle, etc.
- a profile identity may be provisioned for a vehicle itself including information to distinctly identity the vehicle (e.g., a vehicle identification number (VIN)).
- VIN vehicle identification number
- identity profiles 34 are stored in dedicated hardware (e.g., physical SIM card, memory card, etc.). Software can be configured to virtually switch between different hardware or the hardware itself may be programmable to store different agent identity information over time.
- identity profiles 34 are stored in a programmable storage module or virtual identity module that can store one or more identity profiles 34 .
- identity profiles 34 may be kept in any suitable memory element, software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs.
- identity profiles 34 may be provided in any database, register, cache, queue, control list, or storage structure.
- VSIMs 32 and identity profiles 34 may be provisioned and managed through one or more identity service providers, represented by identity service provider 60 in FIG. 3 .
- identity service provider 60 could be a third party provider (e.g., in the cloud) and could offer identity services to mobile network operators.
- identity service provider 60 could be a mobile network operator, a vehicle manufacturer, a vehicle rental and leasing agency, a vehicle dealer, a government agency, or any other entity having an interest in managing identities associated with a vehicle over the life of the vehicle.
- identity profiles 34 and/or VSIMs 32 can be managed through the same or different identity service providers.
- the VSIM and identity profile can be associated with an agent rather than to a particular vehicle. Consequently, a human agent (e.g., driver, passenger, owner, renter, etc.) can retrieve his VSIM and identity profile in any vehicle. Depending on the make/model of the vehicle, the human agent can leverage relevant parts of the identity profile for available features in virtually any vehicle.
- a human agent e.g., driver, passenger, owner, renter, etc.
- the human agent can leverage relevant parts of the identity profile for available features in virtually any vehicle.
- Provisioning and managing an identity profile or VSIM through identity service provider 60 can be accomplished in various ways.
- a user could access identity service provider 60 through the Internet or other available network from computer 42 (e.g., home computer, publicly accessible computer, business computer, etc.) or mobile devices 96 .
- end user 2 could access identity service provider 60 by bootstrapping a communication link through OBU 30 (e.g., accessing a home WLAN through WiFi, using a preprogrammed VSIM in OBU 30 , using another agent's VSIM already provisioned in OBU 30 , etc.)
- the identity service provider 60 may be accessed through a local network (e.g., manufacturer who is an identity service provider locally accessing provisioning modules of OBU 30 prior to shipping the vehicle, etc.) or other wireless networks (e.g., user accessing mobile network operator through a cellular network if the mobile network operator is its own identity service provider, etc.).
- Identity service provider 60 may provide modules allowing the creation of an account with authentication credentials 66 (which may be saved for future access of the account) for an agent.
- a VSIM module 61 may be provided by identity service provider 60 to allow a user to provision a VSIM for an agent, with the VSIM being associated with a desired mobile network operator and stored, for example, in VSIM database 64 .
- An identity profile module 63 may also be provided by identity service provider 60 to allow the user to provision an identity profile for the agent and to store the identity profile in, for example, identity profile database 62 .
- a user is the agent and provisions a VSIM and/or an identity profile for himself.
- the user may provision a VSIM and/or an identity profile for another agent (e.g., a vehicle dealer provisioning a VSIM and/or an identity profile for a new vehicle owner, a vehicle rental agency provisioning a VSIM and/or an identity profile for an agent renting a vehicle, a user at an OEM provisioning a VSIM and identity profile for a software agent configured in the OBU to make network connections to the OEM from the OBU, etc.).
- another agent e.g., a vehicle dealer provisioning a VSIM and/or an identity profile for a new vehicle owner, a vehicle rental agency provisioning a VSIM and/or an identity profile for an agent renting a vehicle, a user at an OEM provisioning a VSIM and identity profile for a software agent configured in the OBU to make network connections to the OEM from the OBU, etc.
- VSIM 32 and identity profile 34 may be dynamically added, removed, and updated via local or remote network access.
- the VSIM and/or identity profile may be downloaded using control channels or otherwise provided to OBU 30 if the agent associated with the VSIM and/or identity profile has been authenticated to OBU 30 .
- the agent e.g., end user 2
- end user 2 may access a local network of an identity service provider if a vehicle is in close physical proximity to identity service provider 60 .
- identity service provider 60 Once identity service provider 60 is accessed, the user can authenticate to identity service provider 60 via authentication credentials 66 , access the desired account, and download one or more associated VSIMs 32 and/or identity profiles 34 .
- the associated agent can use an available VSIM or other available communication link in OBU 30 to access identity service provider 60 to download the new VSIM and/or updated identity profile.
- the VSIM and/or identity profile may be stored on a transportable memory element (e.g., USB stick, CD, etc.), which may be provided locally to OBU 30 by a user, such as end user 2 .
- the VSIM and/or identity profile can then be downloaded to OBU 30 from the transportable memory element.
- an identity profile may be dynamically created and managed (e.g., removed or updated) locally, directly through OBU 30 .
- OBU 30 may provide an identity profile creation tool through display 28 for a user to enter desired credentials and profile information and associate such information with an agent.
- the identity profile creation tool may be accessible through a user's mobile device. In these scenarios, the identity profile would not be accessible through identity service provider 60 and could only be accessed in the particular vehicle containing the identity profile.
- OBU 30 includes a transaction security framework 70 , a secure database/storage layer 80 , transaction applications 78 , and a secure communication module 77 .
- Transaction security framework 70 may include multiple software modules, VSIMs 32 , and a trusted platform module (TPM) 76 .
- the software modules can include agent provisioning module 71 , authentication and secure transaction module 72 , VSIM provisioning module 73 , multi-factor authentication module 74 , identity profile provisioning module 75 , and payment association module 79 .
- Agent provisioning module 71 provides the overall flow for provisioning and authenticating an agent to OBU 30 .
- Agent provisioning module 71 allows provisioning new agents, provisioning new and updated VSIMs 32 , provisioning new and updated identity profiles 34 , authenticating agents to OBU 30 , and activating any applicable identity profiles 34 .
- agent provisioning module may also invoke payment association module to determine whether to associate a payment method available through the agent (e.g., in the identity profile or through an associated VSIM) to certain transaction applications not typically initiated by an agent having a payment method (e.g., automatic toll payment transactions, automatic parking transactions, etc.)
- Multi-factor authentication module 74 provides a flow for using one or more predefined authentication credentials to authenticate an agent to OBU 30 and to ascertain that the agent is authorized to conduct a particular transaction on OBU 30 .
- multi-factor authentication module 74 may be invoked upon initial authentication of an agent to gain access to OBU 30 and in addition, when particular transactions are initiated on OBU 30 .
- Authentication credentials may include who, what, and where criteria related to the agent.
- authentication requirements for machine devices and some mobile devices could include one or more of machine hardware signature, challenge-response, predefined certificate (e.g., PKI certificate, TTP certificate, etc.), and physical location relative to OBU 30 .
- Authentication requirements for a human agent 94 could include one or more of biometrics, (e.g., fingerprinting, etc.), challenge-response, key fob, access card, mobile phone, user ID and password, a one-time password (OTP), and physical location relative to OBU 30 .
- biometrics e.g., fingerprinting, etc.
- challenge-response key fob
- key fob access card
- mobile phone user ID and password
- OTP one-time password
- Authentication requirements for authorized entities could include challenge-response, predefined certificate, and the like.
- the authentication requirements for each agent may be provided in an agents-to-multi-factor mapping database 83 of secure database/storage layer 80 .
- the predefined authentication credentials that are required to authenticate to OBU 30 are specific to the particular agent being authenticated. For example, a key fob may allow an owner agent to authenticate to a vehicle, but only a simple user name and password may be required for a child of the owner to authenticate. In this case, a lesser amount of security may be required for the child to authenticate because the child may have limited access to transaction applications and resources of OBU 30 .
- authentication requirements to gain access to OBU 30 may be different than authentication requirements for a particular transaction.
- an owner of a vehicle may only need to use a key fob to gain access to OBU 30 , but additional authentication may be required for the owner to access various transaction applications and resources of OBU 30 .
- Security can be strengthened as the number and diversity of authentication requirements mapped to a particular agent is increased.
- TPM 76 is a hardware approach that can authenticate an agent, once the agent has provided appropriate credentials.
- TPM 76 is a secure processor that performs cryptographic functions and can store cryptographic keys for protecting information.
- a software container e.g., a secure virtualized operating system container
- any hardware, software, or suitable combination thereof can be implemented to accomplish the authentication requirements of multi-factor authentication module 74 .
- TPM 76 can also be used to protect data and transaction applications.
- TPM 76 can be a safe store for an encryption key so that only an authorized agent who properly authenticates to TPM 76 can access the encryption key to decrypt protected data (e.g., data in secure database/storage layer 80 ).
- TPM 76 can also be used to ensure the integrity of transaction applications 78 executing on OBU 30 , which can be achieved locally or remotely depending on the particular transaction application and associated agent. Locally, the OBU 30 can self-ensure that the operating system is on a trusted platform.
- Transaction applications 78 may each include a signature that can be verified prior to execution.
- Transaction applications 78 can also be verified remotely to third parties, such as authorized entities 98 .
- an authorized entity such as a manufacturer may access a transaction application that monitors the brakes and accelerator of vehicle 4 .
- TPM 76 can be used to verify the integrity of the application to the manufacturer. Based on the information provided, the manufacturer can respond accordingly (e.g., process data received from the transaction application if the transaction application is verified, cease execution of the transaction application if the transaction application is not verified).
- TPM 76 has a permanent identity associated with vehicle 4 and does not change even if vehicle ownership changes.
- a vehicle identity (vehicle ID) of vehicle 4 such as a vehicle identification number (VIN) is also a permanent identity associated with vehicle 4 .
- VIN vehicle identification number
- a TPM endorsement key, which can be used to encrypt data, may have a public key part that can be used as a TPM identifier (TPM ID).
- TPM ID TPM identifier
- vehicle ID and TPM ID do not ordinarily change, if TPM 76 or OBU 30 is replaced during the life of vehicle 4 , then a new TPM ID would need to be associated to vehicle 4 .
- VSIM provisioning module 73 and identity profile provisioning module 75 allow the provisioning of new or updated VSIMs and or identity profiles on OBU 30 .
- provisioning may include downloading new or updated VSIMs and identity profiles from an identity service provider either locally or remotely.
- Provisioning may also include downloading new or updated VSIMs and identity profiles from a transportable memory element or mobile device.
- identity profiles may also be manually created in OBU 30 , without involving an identity service provider.
- Authentication and secure transaction module 72 provides a flow for detecting an event for a transaction, determining whether the transaction is authorized, authenticating an associated agent if required, and obtaining network credentials and other profile information as needed.
- Network credentials may include one or more VSIMs' information, user ID and password, and/or security certificates (e.g., asymmetric/symmetric key pair, etc.), and any other information to facilitate vehicle internal network access or external network access via an available wired or wireless communication link.
- this module may be configured to query secured storage such as transaction-to-agents mapping database 82 , transaction-to-authentication-and-confidentiality-schemes mapping database 84 , agents-to-multi-factor-authentication mapping database 83 , and agent identity profiles database 81 .
- a mapping of data, elements, objects, or components is intended to mean an electronic association, correspondence, relationship, or correlation between the data, elements, objects, or components, provided in electronic devices and/or networks.
- these databases in addition to any other databases or memory elements in secure database/storage layer 80 , can be maintained in a secure manner using the default security credentials obtained from TPM 76 .
- various confidentiality schemes can be used to protect the data stored in the various memory elements of secure database/storage layer 80 such as, for example, cryptographic algorithms including Data Encryption Standard (DES/3DES), Secure Hash Algorithm (SHA-1/2), Advanced Encryption Standard (AES), etc.
- cryptographic algorithms including Data Encryption Standard (DES/3DES), Secure Hash Algorithm (SHA-1/2), Advanced Encryption Standard (AES), etc.
- Transaction-to-agents mapping database 82 indicates which transactions are authorized for which agents.
- Mapping database 82 may include mappings of agent identities to user-level and system-level transaction applications corresponding to transactions and also to types of transactions (e.g., transactions requiring remote network credentials, transactions requiring payment information, etc.).
- types of transactions e.g., transactions requiring remote network credentials, transactions requiring payment information, etc.
- Example mappings that could be found in database 82 include: 1) a manufacturer mapped to transaction applications for accessing vehicle sensor data (e.g., in order to perform diagnostics), for performing software or firmware upgrades, and for accessing a “black box” of the vehicle, 2) a dealer mapped to transaction applications for accessing sensor data (e.g., read only access in order to schedule maintenance services), 3) an emergency service provider mapped to transaction applications for controlling the vehicle (e.g., opening a vehicle door, disabling a vehicle engine, etc.), 4) a public entity mapped to transaction applications for accessing sensor data or other vehicle diagnostic data (e.g., for inspection, security, surveillance, etc.), 5) an owner of the vehicle mapped to all transaction applications except those allowing “write” or “modify” access to vehicle software and/or firmware, 6) a passenger mapped to a subset of transaction applications and features available to an owner of the vehicle, and 7) a sensor mapped to a transaction application compiling diagnostic data.
- a dealer may only need to read vehicle sensor data for maintenance scheduling purposes. Consequently, the dealer would be mapped to a transaction application that only allows read operations of vehicle sensors to be performed.
- a manufacturer may need to read and update vehicle sensors and controls for performing firmware and/or software upgrades and fixes. Therefore, the transaction applications mapped to the manufacturer could allow read and update functions to be performed.
- a software agent may be a system-level transaction application that does not have a separate agent initiating its execution or otherwise associated with it.
- the software agent could be a low level application that automatically initiates processing based upon predefined criteria (e.g., specific time periods, whenever network connectivity is detected, etc.).
- authorization for the software agent to execute could be provided in any suitable way, including an appropriate indication in transaction-to-agents mapping database 82 (e.g., mapping the software agent to a type of transaction, mapping the software agent to itself).
- Authentication and secure transaction module 72 may also determine which authentication and confidentiality schemes to use for particular transactions for exchanging data between OBU 30 and transaction systems in the cloud.
- authentication protocols include secure socket layer (SSL), Internet Protocol Security (IP SEC), Extensible Authentication Protocol (EAP-*), Hypertext Transfer Protocol Authentication (HTTP Auth), Kerberos, Simple Authentication and Security Layer (SASL), Web Service Security (WS-Security), etc.
- confidentiality schemes that can be used include encryption or cryptographic algorithms such as DES/3DES, SHA-1/2, AES, etc. Accordingly, transaction-to-authentication-and-confidentiality-schemes mapping database 84 may provide a mapping of which types of transactions and particular transaction applications require which authentication and confidentiality schemes.
- mapping database 84 could be a banking application's related data and other sensitive information mapped to a desired encryption mechanism. Furthermore, in certain implementations, the criticality of the communication may dictate the applicable authentication method (e.g., different types of authentication may be required for highly sensitive transaction applications). In some embodiments, mapping database 84 may also indicate which types of transactions and particular transaction applications require multi-factor authentication to be performed for an associated agent.
- authentication and secure transaction module 72 may also access agents-to-multi-factor-authentication mapping database 83 .
- a human agent 94 accessing benign features such as gaming, video, and the like may require a simple user name and password during the initial authentication to OBU 30 .
- additional authentication e.g., physical presence in the form of biometric authentication, etc.
- highly critical functions such as software/firmware changes by a manufacturer, or emergency services by an emergency service provider, may require multiple layers of authentication by the manufacturer or emergency services provider. These multiple layers of authentication could be satisfied by the agent in the initial authentication to OBU 30 , or additional required layers may need to be satisfied when the agent initiates access to the particular transaction application requiring the additional authentication.
- Secure database/storage layer 80 may also provide an agent identity profiles database 81 , for storing identity profiles 34 provisioned locally (e.g., using a transportable memory element to download an identity profile, creating an identity profile directly through OBU 30 ) or remotely (e.g., downloading an identity profile from identity service provider 60 ).
- agent identity profiles database 81 may also include security keys, certificates, and credentials corresponding to various transaction applications and agents.
- Secure communication module 77 of OBU 30 may enable secure communication to various networks (e.g., networks 40 as shown in FIGS. 1-3 ). Secure communication module 77 selects secure and authenticated network access for an agent and associated transaction application. In addition, secure communication module 77 may also provide opportunistic selection of a VSIM available to the agent, when multiple VSIMs are available for use. VSIM selection rules database 85 may be configured to provide a pre-specified mapping of rules that represent preferences regarding which single VSIM, multiple VSIMs, and/or other wireless communication option (e.g., WiFi) to select for network access.
- networks 40 e.g., networks 40 as shown in FIGS. 1-3
- Secure communication module 77 selects secure and authenticated network access for an agent and associated transaction application.
- secure communication module 77 may also provide opportunistic selection of a VSIM available to the agent, when multiple VSIMs are available for use.
- VSIM selection rules database 85 may be configured to provide a pre-spec
- rules may include combinations of an agent, a transaction application (or type of transaction), and/or a geographical location of the vehicle mapped to a VSIM or other wireless communication.
- rules include agent and transaction application, agent and location, or agent, transaction application, and location.
- agent and transaction application combination is mapped to a VSIM
- the VSIM will be used when the agent and transaction application are associated with a network access request, regardless of where the vehicle is physically located.
- the VSIM will be used if the vehicle is physically located in the mapped location and if the agent is associated with the network access request, regardless of which particular transaction application is associated with the network access request.
- VSIMs and/or other wireless communication options can also be mapped to transaction applications or types of transactions, agents, and/or geographical locations to allow a network connection to be split among the designated multiple VSIMs and/or other wireless communication options.
- a large file download may utilize multiple VSIMs (e.g., two different 3G mobile networks) in order to split the file to increase the speed of the download.
- a transaction application and agent associated with the file download may be mapped to two or more VSIMs provisioned in OBU 30 for the agent.
- one VSIM may be preferred over another VSIM due to the vehicle location because of the mobile network operator rate.
- Agent X and California are mapped to VSIM 1 and Agent X and New York are mapped to VSIM 2.
- Agent X is traveling in California, then VSIM 1 will be used for any network access requested by Agent X.
- Agent X is traveling in New York, then VSIM 2 will be used for any network access requested by Agent X.
- a human agent 94 may prefer to have particular types of transactions tied to different VSIMs or combinations of VSIMs (e.g., home transactions mapped to VSIM 1, work related transactions mapped to VSIM 2, child's transactions mapped to VSIM 1).
- mappings can be configured in VSIM selection rules mapping database 85 with appropriate authorization.
- the VSIM selection rules mapping could also be provided in any other suitable memory element including, for example, an identity profile associated with the agent.
- only transaction application and/or location may need to be mapped to available VSIMs and/or other wireless communication options.
- VSIMs may also be opportunistically selected in real-time.
- a real-time VSIM selection may occur based on current network conditions/demands, mobile network rate plan of an agent, remaining data/minutes of a mobile network rate plan.
- network performance characteristics such as, for example, data rate, signal level, congestion, etc. may also be evaluated in real-time and used to opportunistically select a suitable one or more VSIMs, other wireless communication options, or any suitable combination thereof.
- Transaction applications 78 represent a plethora of user-level and system-level transaction applications that may be configured on OBU 30 . With proper authentication to OBU 30 and authorization through transaction-to-agents mapping database 82 , however, numerous types of transactions using transaction applications 78 may be performed through OBU 30 . Generally, types of transactions are inclusive of 1) accessing one or more wireless/mobile/cellular networks and using network bandwidth and services, 2) gaining access to various resources of the vehicle based on an identity profile and/or associated databases, 3) gaining access to applications in the vehicle, and 4) engaging in commercial activities (e.g., paying for receiving goods or services, or receiving payment for selling goods or services).
- the user-level and system-level transaction applications of OBU 30 may be mapped to any appropriate agent 90 (e.g., machine devices 92 , humans 94 , software agents 95 , mobile devices 96 , and authorized entities 98 ) in transaction-to-agents mapping database 82 .
- Example transaction applications 78 can include applications facilitating external network access such as banking applications, LBS applications, travel agency applications, vehicle rental & leasing agency applications, Internet commerce applications, kiosk applications, gas & electric charging applications, transportation charging applications, vehicle-to-vehicle applications, vehicle-to-mobile applications, dealer transaction applications, OEM transaction applications, and the like.
- Other transaction applications 78 may include hardware and/or software applications involving internal access of OBU 30 such as gaining access to various resources, vehicle subsystems, or software applications not involving remote network access.
- a unified identity management framework as illustrated in FIG. 4 , is capable of aggregation and association of all agents 90 and transaction scenarios into a unified system.
- application programming interfaces APIs may be exported to integrate these agent identities with various transaction applications.
- Authorized entities 98 may access appropriate transaction applications (e.g., dealer transaction application, OEM transaction application, etc.) after gaining access to OBU 30 through an authenticated software agent 95 .
- the software agent 95 may first authenticate to OBU 30 and can then establish a network connection to the authorized entity using an appropriate VSIM (e.g., the manufacturer's VSIM).
- the authorized entity to which the software agent establishes a network connection may need to authenticate to OBU 30 before being able to access transaction applications on OBU 30 , such as transactions applications related to vehicle sensor data, diagnostic data, firmware/software upgrades, emissions data, etc.
- an OEM software agent on OBU 30 may be configured to establish a network connection to the OEM whenever internal connectivity to a network is detected on OBU 30 .
- OEM software agent may first authenticate to OBU 30 and, for example, VSIM 1 may be selected for network access. Once a network connection is established between OBU 30 and the OEM using VSIM 1, the OEM may update the VSIM 1 to VSIM 2 if, for example, the OEM has negotiated a new rate with a different mobile network provider and wishes to update its VSIM.
- a VSIM being updated e.g., VSIM 1
- a VSIM being updated may need to remain active and available for use by the associated agent for a specified period of time, until the new VSIM (e.g., VSIM 2) has been successfully provisioned (and possibly tested) in OBU 30 .
- the OEM may need to be authenticated to OBU 30 and authorized in transaction-to-agents mapping database 82 in order to update the VSIM or to access an OEM transaction application (e.g., one of transaction applications 78 ), which could be configured to access various vehicle components (e.g., vehicle sensors, vehicle firmware/software, etc.).
- OEM transaction application e.g., one of transaction applications 78
- vehicle components e.g., vehicle sensors, vehicle firmware/software, etc.
- Machine devices 92 may also authenticate to OBU 30 and then provide an automatic network connection to an external entity or transaction system 50 .
- a machine device agent e.g., a detector
- transaction-to-agents mapping database 82 may be evaluated to determine whether the detector is mapped to the transportation charging application. Once the detector is determined to be authorized to access the transportation charging application, network credentials and payment information may be obtained so that transportation charging application can connect to the toll system and provide appropriate payment.
- Identity profiles are included for a parent/owner 502 , a child 504 , a vehicle sensor 506 , and a manufacturer 508 .
- Common elements in each of the identity profiles include agent identification, VSIM, and security profile.
- Agent identification could include credentials information such as a key fob for the parent/owner 502 , a birth date for the child 504 , a device identifier for the vehicle sensor 506 , and a name for the manufacturer 508 .
- the security profile information could also be credentials such as a user name and password for the parent/owner 502 and child 504 , a security key for the vehicle sensor 506 , and a PKI certificate for the manufacturer 508 .
- Identity profiles for human agents may also include vehicle settings, other wireless interfaces, device list, and web accounts.
- vehicle settings may include items such as preferred seat positions as a driver and a passenger, temperature controls, music or radio settings, and the like.
- Other wireless interfaces and preferences may include, for example, a WiFi account established with a mobile network provider. Wireless interface information can be included in the identity profiles so that whenever the vehicle is near a hotspot of the mobile network operator, network connections by the parent/owner or child can be made through the WiFi interface.
- Identity profiles for the parent/owner 502 and child 504 may also include specific web accounts, such as those related to social networking and media.
- Device lists may include any personal mobile devices of the parent/owner or child.
- the device list could include network interface accounts, passwords, and network configurations.
- the device list is essentially an identity profile for mobile devices within identity profiles of the parent/owner 502 and child 504 .
- the device list information is provided to allow each of the identified mobile devices to be recognized and connected to the OBU 30 and to other networks in a desired manner.
- OBU 30 may be used as a communication link to the Internet for mobile devices identified in a device list of an identity profile of another agent.
- Identity profile of parent/owner 502 may also include other profile information of a sensitive nature such as credit/payment information.
- Credit/payment information may be included in an identity profile to allow the agent of the identity profile to use his own credit/payment information for various charges/payments incurred during commercial transactions (e.g., transportation charging, gas and charging stations, kiosks, Internet commerce, rental and leasing, travel, etc.).
- the credit/payment information may be associated with authorized transaction applications during provisioning of the identity profile or at other times.
- the owner's credit/payment information may be set as the default credit/payment method for various transaction applications.
- payment information associated with transaction applications for transportation and gas and charging systems could be changed during a trip in vehicle 4 when a passenger offers to use his own credit/payment information to pay for such expenses.
- OBU 30 could provide an interface to allow modification to appropriate settings to effect such a change using proper authentication and authorization.
- the driver's credit/payment information may be associated with the various transportation and gas and charging transaction applications. However, if the driver is not the default payer/creditor, then OBU 30 could provide confirmation screens to notify the driver that his credit/payment information will be used and to receive confirmation and approval of this change.
- Identity profile of parent/owner 502 may also include machine device access. While a manufacturer or an OEM may have access to vehicle machine devices to read and update or modify firmware or software of such machine devices, an owner of a vehicle may only be allowed to retrieve data from vehicle sensors. Accordingly, machine device access can indicate which machine devices the owner is authorized to access and what type of access is allowed. In addition, other passengers may not be allowed any type of access to the vehicle sensors and actuators, for example, and therefore, machine device access information may be omitted from identity profiles associated with other human agents.
- Identity profile of child 504 may also contain parental controls and may not contain certain information that allows use of particular resources or transactions.
- Parental controls may be included to allow a parent to set desired limits on a child's use of OBU 30 resources and the vehicle itself. For example, any type of common computer parental controls related to accessing networks such as the Internet could be provided in parental controls.
- parental controls could relate to particular activities of the vehicle. For example, if the child is authenticated as a driver, parental controls could require a notification be sent to the parent (e.g., via an email account, a text message, to a messaging center of the OBU 30 , etc.) if the vehicle is driven beyond a specified boundary or perimeter or if the vehicle is driven beyond a specified speed.
- Parental controls could also be configured to limit certain vehicle functions (e.g., vehicle speed, entertainment systems, etc.).
- identity profile of child 504 may not have credit/payment information if the child is not allowed to engage in commercial transactions through OBU 30 .
- Identity profile of manufacturer 508 may also include machine device access information, which can indicate which machine devices the manufacturer is authorized to access and what type of access is allowed.
- the identify profile of manufacturer 508 may also include information related to diagnostics of vehicle 4 and a history of vehicle technical problems. Thus, when the manufacturer accesses vehicle 4 , valuable historical information related specifically to vehicle 4 can be readily available for the manufacturer. Web accounts may also be provided in identity profile of manufacturer 508 . Such information could allow the manufacturer to communicate with the driver/owner and provide information including, for example, marketing information such as coupons or sales events.
- FIGS. 6 through 15 simplified flowcharts illustrating various aspects of embodiments of the present disclosure are shown.
- FIGS. 6-15 will be described herein with reference to various elements, objects, modules, and components of the present disclosure as provided in preceding FIGS. 1-5 .
- FIG. 6 is a simplified agent provisioning flow 600 providing example steps of agent provisioning module 71 for provisioning an agent to OBU 30 , which may be configured as a background process open and running whenever OBU 30 is booted up.
- Agent provisioning flow 600 begins at step 601 , waiting for an agent. When an agent attempts to gain access to OBU 30 , flow moves to step 602 and an agent is detected. This can occur whenever a new or existing agent initiates a vehicle-based transaction via OBU 30 .
- a human 94 e.g., an owner, a renter, a borrower, etc.
- OBU 30 is powered on (e.g., by using a key fob to enter the vehicle, by starting the vehicle or otherwise providing power to OBU 30 ).
- Agent provisioning flow 600 may also occur when a mobile device 96 is powered on within vehicle 4 , when a software agent 95 is initiated, when a machine device 92 is activated (e.g., by powering on vehicle 4 ) or attempts to access resources or transaction applications of OBU 30 (e.g., vehicle sensor or actuator sending data or information to OBU 30 , detector initiating a transportation transaction application after detecting proximity to a toll system), when an authorized entity 98 attempts to access OBU 30 (e.g., after a corresponding software agent 95 has established network access to the authorized entity 98 from OBU 30 ).
- agent provisioning may also occur when a human agent provisions another agent (e.g., machine device, software agent, mobile device, authorized entity), typically for the first time.
- step 604 to perform authentication of the agent to the vehicle, which will be described in more detail with reference to FIGS. 7-10 .
- VSIMs and/or an identity profile may be provisioned for the agent if the agent is properly authenticated.
- Flow then passes to decision box 606 where a determination is made as to whether the agent was properly authenticated to the vehicle. If the agent was not properly authenticated then flow passes back to step 601 to wait for another agent. If the agent was properly authenticated as determined in decision box 606 , however, then flow passes to decision box 608 to determine whether an identity profile is provisioned for the agent.
- step 610 activates the identity profile, including determining agent priority and role in the vehicle, adjusting vehicle settings, configuring agent preferences, and the like, which will be further described herein with reference to FIG. 11 .
- step 610 After the identity profile is activated in step 610 , or if the agent does not have a corresponding identity profile in OBU 30 , then flow passes to decision box 612 to determine whether the agent has an associated payment method (e.g., payment method information in identity profile, VSIM that can be used for payment). If the agent has an associated payment method, then flow passes to step 614 to invoke payment association module, which will be further described with reference to FIG. 12 . After the payment association processing is completed in step 614 , or if the agent does not have an associated payment method as determined in decision box 612 , then flow passes back to step 601 to wait for another agent.
- an associated payment method e.g., payment method information in identity profile, VSIM that can be used for payment.
- Certain agents may not have associated payment methods because these agents may not engage in commercial transactions through OBU 30 and, therefore, may not interact with transaction applications requiring payments.
- FIG. 7 is a simplified authentication to vehicle flow 700 , which may be performed at step 604 of FIG. 6 and which illustrates example steps for authenticating an agent to the vehicle.
- Authentication to vehicle flow 700 begins at step 702 where a determination is made as to whether the detected agent is a new agent.
- “New agent” refers to an agent that does not have any authentication credentials, profile information, or VSIMs currently provisioned in OBU 30 .
- New human agents could include, for example, a new owner, rental or lease driver, borrower, or passenger who has not previously been provisioned on the vehicle.
- new agents include, for example, a new mobile device attempting to access a local network of OBU 30 , a new machine device (e.g., sensor, actuator, etc.) added to the vehicle, or a new software agent installed on OBU (e.g., a new dealership adds a software agent to automatically initiate connection with the dealership).
- a new machine device e.g., sensor, actuator, etc.
- a new software agent installed on OBU e.g., a new dealership adds a software agent to automatically initiate connection with the dealership.
- agent identity of a human can be inferred from a key fob used by the human agent to enter the vehicle.
- display 28 can prompt the driver to confirm that his identity matches the displayed owner identity (or provisioned default driver) of the vehicle. If other identities of human agents have been provisioned in the vehicle, then the display could also provide a list of provisioned identities from which the agent can choose to authenticate. Display 28 could also provide the option to select “New Driver”, “New Passenger”, or the like.
- OBU 30 may include a policy module that allows various policy controls, including new agent provisioning.
- new agent provisioning For example, for an added layer of security, an owner may set policies that by default block any new agents from being added to OBU 30 . Thus, whenever a new agent needs to be added, the owner would have to reset or override the policy with credentials to allow the new agent to be provisioned.
- Such policy settings can be controlled through a policy settings interface by an appropriate agent (e.g., the owner or other superagent with a specified high level of authority for conducting transactions and configuring policies in OBU 30 ). If the policies do not allow new agents as determined in decision box 720 , then authentication to vehicle flow 700 ends and flow returns to agent provisioning flow 600 with the agent not authenticated.
- an appropriate agent e.g., the owner or other superagent with a specified high level of authority for conducting transactions and configuring policies in OBU 30 .
- decision box 722 a determination is made as to whether VSIM provisioning is requested.
- a display screen may offer the choice to the agent to provision a VSIM. If VSIM provisioning is requested, then flow passes to step 724 to perform VSIM provisioning, which will be further described with reference to FIGS. 9A and 9B .
- VSIM provisioning allows an agent to create or update one or more VSIMs with an identity service provider (e.g., third party identity service provider accessible through the Internet), and/or to download one or more VSIMs (e.g., from the identity service provider, from a transportable storage medium, from a mobile device) to OBU 30 .
- an identity service provider e.g., third party identity service provider accessible through the Internet
- VSIMs e.g., from the identity service provider, from a transportable storage medium, from a mobile device
- step 724 After the one or more VSIMs are provisioned in step 724 , or if VSIM provisioning was not requested, flow passes to decision box 726 to determine whether identity profile provisioning is requested. In the case of a human agent, a display screen may offer the choice to the agent to provision an identity profile. If identity profile provisioning is requested, then flow passes to step 728 to perform identity profile provisioning, which will be further described herein with reference to FIGS. 10A and 10B .
- Identity profile provisioning allows an agent to create or update an identity profile through an identity service provider (e.g., third party identity service provider accessible through the Internet) or directly onto OBU 30 . If an identity profile is created or updated through an identity service provider, or if an identity profile is stored on transportable storage medium or mobile device, then the identity profile can be downloaded to OBU 30 .
- identity service provider e.g., third party identity service provider accessible through the Internet
- step 730 where one or more authentication factors or requirements may be provisioned for the new agent in agents-to-multi-factor-authentication mapping database 83 .
- factors could include user ID and password, biometrics, key fob, access card, etc., and one or more of these factors could be obtained by accessing the agent's identity profile credentials. For example, if an identity was provisioned and includes a user ID and password, the agent could be prompted to confirm that the user ID and password from the identity profile should be included as one of the authentication factors.
- step 704 to perform multi-factor authentication, which will be described in more detail herein with reference to FIG. 8 .
- Multi-factor authentication requires the detected agent to authenticate himself using one or more factors provided in agents-to-multi-factor-authentication mapping database 83 .
- decision box 706 determines whether the detected agent passed the required multi-factor authentication. If the agent did not pass, then authentication to vehicle flow 700 flow ends and returns to agent provisioning flow 600 without the detected agent being authenticated.
- steps 710 through 718 essentially perform the same function as steps 722 through 728 with regard to VSIM and identity profile provisioning.
- the existing, authenticated agent is allowed to provision (by creating or updating) one or more VSIMs and/or an identity profile and to download such data to OBU 30 .
- a multi-factor authentication flow 800 is shown, which may be invoked in step 704 of FIG. 7 , to authenticate the agent to access OBU 30 .
- Multi-factor authentication flow 800 may also be used to authenticate the agent when the agent is attempting to conduct particular transactions through OBU 30 , which will be further described herein with reference to FIG. 13 .
- Flow begins at step 802 where agents-to-multi-factor-authentication mapping database 83 is evaluated.
- the agent can be mapped to one or more authentication requirements necessary for authenticating to OBU 30 .
- each agent provisioned in OBU 30 could have various required authentication requirements and various numbers of such requirements.
- an owner having significant privileges and access to OBU 30 and its resources may have several authentication requirements, whereas a passenger in the vehicle with limited access to OBU 30 and its resources may only need to provide a user ID and password.
- a key fob used to open a door for a human agent could be the first authentication requirement for a driver or owner of the vehicle.
- the agent passes the authentication requirement e.g., entering a correct user ID and password, providing a matching fingerprint, providing a valid PKI certificate, etc.
- the agent passes all of the authentication requirements, then the agent is authenticated to the vehicle, as indicated in step 814 , and multi-factor authentication flow 800 ends. If, however, the agent fails one of the authentication requirements, then the agent is not authenticated to the vehicle, as indicated in step 808 , and the multi-factor authentication flow 800 ends.
- FIGS. 9A and 9B simplified flowcharts of a VSIM provisioning flow 900 A and an identity service provider access flow 900 B, respectively, are illustrated.
- VSIM provisioning flow 900 A may represent at least a portion of the flow of VSIM provisioning module 73 of OBU 30 .
- flow 900 A can be invoked during authentication to vehicle flow 700 and also at any time during which an agent is authenticated to OBU 30 .
- Flow begins at step 906 where an available communication link is identified.
- Various communication links may be used to provision a VSIM, including some form of wireless communication (e.g., WiFi, WiMax, 3G, 4G, white space, 802.11x, satellite, etc.) to connect to identity service provider 60 , a local network within vehicle 4 (e.g., local WiFi, Bluetooth, Ethernet, etc.) to connect to a mobile device, or a direct connection to a transportable medium (e.g., USB, CD, etc.).
- Flow passes to decision box 908 to determine whether the identified link is for local provisioning. If the identified communication link is not for local provisioning, then flow passes to step 910 to access identity service provider 60 via an available network. Example processing of identity service provider 60 will be described in more detail herein with reference to FIG. 9B .
- decision box 912 When a network connection has been established to identity service provider 60 in step 910 , or if the available communication link was identified for local provisioning, flow passes to decision box 912 . In decision box 912 a determination is made with regard to what VSIM action to perform. If a VSIM is to be removed from OBU 30 , then flow passes to step 914 to remove the VSIM. If a VSIM on OBU 30 is to be updated, then flow passes to step 918 to download a VSIM using the identified communication link (e.g., from identity service provider 60 , from a transportable storage medium directly connected to OBU 30 , from a mobile device) to update an existing VSIM.
- the identified communication link e.g., from identity service provider 60 , from a transportable storage medium directly connected to OBU 30 , from a mobile device
- step 916 downloads the new VSIM using the identified communication link (e.g., from identity service provider 60 , from a transportable storage medium directly connected to OBU 30 , from a mobile device).
- the desired action i.e., remove, update, or add
- an agent may be associated with multiple VSIMs provisioned in OBU 30 . Therefore, multiple VSIM actions may occur during a single VSIM provisioning process.
- FIG. 9B a simplified flowchart illustrates possible processing steps of identity service provider 60 providing identity services for managing VSIMs, including accessing and downloading VSIMs to connected vehicles.
- VSIMs may be managed and stored by identity service provider 60 in a memory element such as VSIM database 64 .
- Flow 900 B will be described with reference to a user, which includes a human provisioning the VSIM for any type of agent (e.g., software agent, machine device, authorized entity, human agent), including provisioning the VSIM for himself as a human agent.
- Flow could start at decision box 922 , where a determination is made as to whether the user accessing identity service provider 60 has been authenticated to the identity service provider. For example, the user may log on to an account created with identity service provider 60 . If the user is not authenticated, then flow ends. Although not shown in FIG. 9B , the user could potentially create a new account with identity service provider 60 .
- a VSIM was previously created by the user (e.g., a user on a computer or mobile device creating a VSIM through identity service provider 60 )
- the user may simply need to access and download the existing VSIM to OBU 30 .
- decision box 926 determine whether to add a new
- decision box 930 determines whether a request was made to update an existing VSIM. If an update request was made, then flow passes to step 932 where an existing VSIM is updated. If an update request is not made, as determined in decision box 930 , however, then flow passes to step 934 where an identified VSIM is removed.
- flow 900 B may also occur when a user establishes a network connection to identity service provider 60 from a remote computer or mobile device to manage his associated VSIMs.
- Identity profile provisioning flow 1000 A may represent at least a portion of the flow of identity profile provisioning module 75 of OBU 30 .
- flow 1000 A can be invoked during authentication to vehicle flow 700 and also at any time during which an agent is authenticated to OBU 30 .
- Flow begins at decision box 1002 where a determination is made as to whether an agent is locally creating an identity profile.
- an agent can manually create an identity profile on OBU 30 by entering profile information directly into OBU 30 through an appropriate user interface. If the agent is locally creating an identity profile, then flow passes to step 1004 where the agent is permitted to manually create an identity profile, and then flow ends.
- step 1006 If it is determined that the agent is not locally creating an identity profile, then flow passes to step 1006 where an available communication link is identified.
- Various communication links may be used to provision a identity profile, including some form of wireless communication (e.g., WiFi, WiMax, 3G, 4G, white space, 802.11x, satellite, etc.) to connect to identity service provider 60 , a local network within vehicle 4 (e.g., local WiFi, Bluetooth, Ethernet, etc.) to connect to a mobile device, or a direct connection to a transportable medium (e.g., USB, CD, etc.).
- a transportable medium e.g., USB, CD, etc.
- decision box 1012 When a network connection has been established to identity service provider 60 in step 1010 , or if the available communication link was identified for local provisioning, flow passes to decision box 1012 . In decision box 1012 a determination is made with regard to what identity profile action to perform. If an identity profile is to be removed from OBU 30 , then flow passes to step 1014 to remove the identity profile. If a identity profile on OBU 30 is to be updated, then flow passes to step 1018 to download a identity profile using the identified communication link (e.g., from identity service provider 60 , from a transportable storage medium directly connected to OBU 30 , or from a mobile device) to update an existing identity profile.
- the identified communication link e.g., from identity service provider 60 , from a transportable storage medium directly connected to OBU 30 , or from a mobile device
- step 1016 downloads the new identity profile using the identified communication link (e.g., from identity service provider 60 , from a transportable storage medium directly connected to OBU 30 , or from a mobile device).
- the desired action i.e., remove, update, or add
- decision box 1020 determines whether more identity profile actions are to be performed. If more identity profile actions are to be performed, then flow passes back to decision box 1012 to repeat the determination of whether to remove, update, or add a identity profile and to perform the desired action accordingly. This processing may continue until all identity profile actions have been completed.
- FIG. 10B a simplified flowchart illustrates possible processing steps of identity service provider 60 providing identity services for managing identity profiles, including accessing and downloading identity profiles to connected vehicles.
- identity profiles may be managed and stored by identity service provider 60 in a memory element such as identity profile memory element 62 .
- Flow 1000 B will be described with reference to a user, which includes a human provisioning the identity profile for any type of agent (e.g., software agent, machine device, authorized entity, human agent), including provisioning the identity profile for himself as a human agent.
- Flow could start at decision box 1022 , where a determination is made as to whether the agent accessing identity service provider 60 has been authenticated to the identity service provider. For example, the user may log on to an account created with identity service provider 60 . If the user is not authenticated, then flow ends. Although not shown in FIG. 10B , the user could potentially create a new account with identity service provider 60 .
- decision box 1024 determines whether there is an identity profile action to perform. If, for example, an identity profile was previously created by the user (e.g., a user on a computer or mobile device creating an identity profile through identity service provider 60 ), then the user may simply need to access and download the existing identity profile to OBU 30 . However, if the user needs to create, update, and/or remove an identity profile, then flow passes to decision box 1026 to determine whether to add a new identity profile to OBU 30 . If a request is made to add a new identity profile (e.g., to identity profile database 64 ), then flow passes to step 1028 to add the new identity profile.
- an identity profile was previously created by the user (e.g., a user on a computer or mobile device creating an identity profile through identity service provider 60 )
- the user may simply need to access and download the existing identity profile to OBU 30 .
- decision box 1026 determine whether to add a new identity profile to OBU 30 . If a request is made to add a new identity profile
- decision box 1030 determines whether a request was made to update an existing identity profile. If an update request was made, then flow passes to step 1032 where an existing identity profile is updated. If an update request is not made, as determined in decision box 1030 , however, then flow passes to step 1034 where an identified identity profile is removed.
- FIG. 11 illustrates a simplified flowchart of example steps for activating an identity profile, as indicated in step 610 of FIG. 6 , after the identity profile has been provisioned in OBU 30 and an associated agent has been authenticated to OBU 30 .
- flow may begin in decision box 1102 where a determination is made regarding whether any control/access limitations have been set by one agent that apply to another agent.
- an owner of the vehicle or other superagent will have authority to set such controls/access limitations by configuring policies through an appropriate policy module.
- Such controls/access limitations may include, for example, parental controls set by a parent of a child (e.g., restrictions on certain web content, media features, any transactions involving credit cards or payments, vehicle functions, etc.). If control/access limitations exist, then flow passes to step 1104 to apply such control/access limitations to the identity profile of the agent.
- step 1105 determines the role and priority of the agent in the vehicle.
- role can be determined based on which seat of the vehicle the agent occupies (e.g., driver seat, front passenger seat, rear left passenger seat, rear right passenger seat, etc.).
- step 1106 configures the vehicle settings based on the agent's role in the vehicle.
- OBU 30 may communicate the agent's identity profile parameters corresponding to actuators and software applications of the particular seat occupied by the agent. For example, seat positioning, air temperature settings, seat heater/cooler, dashboard features, and the like may be configured for the agent if the agent is the driver. If the agent is a passenger, however, the seat positioning, seat heater/cooler, and temperature settings may be applied to the agent's particular passenger seat, if such settings are available for the passenger seat.
- step 1108 may configure other identity profile parameters based on an agent's priority.
- OBU may communicate the agent's identity profile parameters corresponding to any appropriate actuators, software applications, and the like related to agent preferences (e.g., radio channel list, phonebook, address book, GPS favorite locations, etc.).
- agent preferences e.g., radio channel list, phonebook, address book, GPS favorite locations, etc.
- a driver has highest priority and driver preferences will override any conflicting passenger preferences. It should be understood, however, that a passenger could be configured with a higher priority and override the driver's preferences for preferences not pertaining to the safety of the vehicle.
- OBU 30 may also configure network interface accounts and network configurations for other mobile devices identified in the agent's identity profile (e.g., in a device list). Moreover, while examples have been provided for human agents, activating an identity profile of other types of agents authenticated to the OBU may also occur for any appropriate identity profile parameters in an authenticated agent's identity profile.
- FIG. 12 illustrates a simplified flowchart of example steps of payment association module 79 , for associating a payment method to certain transaction applications that are not associated with or initiated by an agent that has an associated payment method (e.g., payment information in identity profile, VSIM).
- a payment method e.g., payment information in identity profile, VSIM.
- the payment method could be payment information such as a credit card or bank account from an agent's identity profile, or a VSIM to be used as payment on a back end of the corresponding mobile network operator.
- payment association flow 1200 of FIG. 12 represents both automatic and manual payment association to transaction applications.
- Flow 1200 may be invoked when an agent is being provisioned, as indicated in step 614 of FIG. 6 , or at any time during which an agent is authenticated to the vehicle.
- flow 1200 may occur automatically and, depending on the role and priority of the agent, may automatically associate the agent's payment methods to the identified one or more transactions.
- flow 1200 may be invoked by the agent through an appropriate user interface of OBU 30 in which the agent may individually or collectively identify which transaction applications to associate with which payment methods.
- Flow begins in step 1202 where a transaction application is identified.
- the identified transaction application may be an application that is not associated with or initiated by an agent that has an associated payment method.
- Flow then passes to decision box 1204 where a determination is made as to whether the agent attempting to make the payment association is authorized to change payment association for the identified transaction application (e.g., if the agent is being provisioned but is not the driver then the agent may not be authorized, if policies do not allow the agent to change payment associations then the agent will not be authorized, etc.). If the agent is not authorized as determined in decision box 1204 , then flow 1200 ends and payment associations are not made.
- step 1206 a new payment method is identified from the agent's identity profile payment information or from the agent's corresponding VSIM.
- the agent's identity profile payment information may include information for a credit card, a debit card, a bank account, or other payment service providers.
- a VSIM associated with the agent could be used to provide payment.
- the VSIM could be used to connect to the associated mobile network operator, the payment could be received from the mobile network operator, and then the mobile network operator could bill the agent on the back end (e.g., with a set periodic or stand-alone bill to the agent).
- the agent can simply be provided with suitable options to select a desired payment method from options associated with the agent.
- priority of available payment options can be pre-specified in any suitable way (e.g., an indication provided in the identity profile, etc.).
- step 1208 to associate the selected payment method to the identified transaction application.
- a separate mapping database may be provided to map identified transaction applications to selected payment methods.
- an existing mapping database such as transaction-to-agents mapping database 82 , may be used and may include any suitable mechanism (e.g., pointer, link list, additional field, etc.) to indicate which agent to select to retrieve an associated payment method for the transaction application.
- another transaction application e.g., parking transaction application
- Authentication and secure transaction flow 1300 may be configured as a background process open and running whenever OBU 30 is booted up. Flow starts at step 1301 where the process waits for an event for a transaction, which could have a trigger associated with an agent to initiate the transaction.
- Triggers could include, for example, a human agent attempting to initiate a transaction (e.g., by pressing a button or otherwise issuing commands through any suitable user interface on display 28 , by using a mobile device to access OBU 30 ), a machine device receiving or transmitting a signal (e.g., a detector receiving a signal from a toll system, a detector receiving a signal from a parking system, a sensor in the vehicle sending a signal to OBU 30 , etc.), a software agent attempting to execute (e.g., requesting network credentials to automatically connect to an authorized entity, etc.), or an authorized entity attempting to access OBU 30 (e.g., authorized entity connected to the vehicle and attempting to access transaction applications on the vehicle, etc.).
- a human agent attempting to initiate a transaction (e.g., by pressing a button or otherwise issuing commands through any suitable user interface on display 28 , by using a mobile device to access OBU 30 ), a machine device receiving or transmitting a signal (e.
- step 1302 When an event occurs, the event is detected in step 1302 and then flow moves to step 1304 to evaluate transaction-to-agents mapping database 82 .
- decision box 1306 a determination is made as to whether the transaction is authorized. If the mapping database 82 does not indicate the transaction is authorized (e.g., the agent is not mapped to a transaction application corresponding to the transaction), then flow passes to 1307 where the transaction is blocked. Flow then passes back to step 1301 to wait for another event.
- mapping database 82 may include which transactions require authentication of the associated agent. Although the agent should already be provisioned and authenticated to the vehicle when transaction processing occurs, some transactions may be of a sensitive nature, and authentication must be provided again.
- initial authentication to the vehicle may be provided with a single authentication requirement, whereas authentication to conduct certain transactions may require multiple authentication requirements as indicated in agent-to-multi-factor-authentication mapping database 83 and transaction-to-authentication-and-confidentiality-schemes mapping database 84 .
- access to a banking transaction application that facilitates transactions to personal bank accounts of agents may require re-authenticating the agent with multiple authentication requirements (e.g., biometrics in addition to a key fob used to initially authenticate to OBU 30 ).
- mapping database 84 may also indicate other authentication and confidentiality schemes to be used by a transaction application such as, for example, a particular encryption mechanism for data associated with the transaction application. Additionally, any authentication protocols required for establishing network connections may also be provided in mapping database 84 .
- step 1308 After authentication and confidentiality schemes are identified in step 1308 , flow passes to decision box 1309 to determine whether agent authentication is required for the transaction. In one embodiment, if authentication is required, then multifactor authentication module 74 may be invoked in step 1310 , as previously discussed herein with reference to FIG. 8 . If multi-factor authentication is required, the agent could be mapped to one or more of the same or different authentication requirements used during the initial authentication of the agent to OBU 30 . Thus, multi-factor authentication flow 800 could be configured to distinguish between initial authentication of an agent to OBU 30 and authentication of an agent for particular transactions. If the agent does not pass authentication as determined in decision box 1312 , then flow passes to step 1313 where the transaction is blocked. Flow then passes back to step 1301 to wait for another event.
- step 1316 in which the identity profile may be accessed to obtain network credentials and any other needed profile information such as payment information for commercial transactions. Accessing the identity profile will be described in more detail herein with reference to FIG. 14 .
- step 1318 After the network credentials and any needed profile information are provided to the transaction application in step 1316 , flow passes to step 1318 to allow the transaction. Flow then returns to step 1301 to wait for another event.
- FIG. 14 illustrates a simplified flowchart of an access identity profile flow 1400 , which may occur in step 1316 of FIG. 13 .
- Flow 1400 includes step 1402 where application programming interfaces (APIs) are exposed to a transaction application corresponding to the transaction to enable the transaction application to securely access relevant parts of the identity profile.
- APIs may be provided to export parts of the identity profile to the transaction application to the extent that the transaction application is authorized to access the profile information. (e.g., credit/payment information, social media web accounts, etc.)
- step 1404 determines the identity of the agent to be used to provide network credentials and/or other profile information such as payment information.
- a human agent who initiates a commercial transaction by triggering an Internet commerce transaction application on OBU 30 may have an identity profile that can be used to obtain network credentials and payment information.
- the agent associated with the event may not have payment information and/or network credentials. Therefore, the determination in step 1404 accommodates certain transaction applications that need profile information from an agent other than the agent associated transaction. For example, a driver or other passenger may want to pay for toll transactions that occur automatically when a detector (agent) senses the toll system and initiates a toll transaction application. Therefore, the identity of the particular agent with the payment information needs to be determined. This can be accomplished in various ways including, for example, a display screen offering a human agent the option to pay the toll using identity profile information. Alternatively, a human agent could preconfigure the payment information through, for example, payment association module 79 .
- step 1408 determines whether the identity profile of the agent is needed.
- network credentials for remote network access e.g., VSIM, WiFi, etc.
- flow passes to step 1410 to get network credentials for in-vehicle networks, if the transaction application accesses an in-vehicle network.
- step 1420 passes to step 1420 to provide the in-vehicle network credentials to the transaction application, if needed.
- step 1412 network credentials are obtained from identity profile, if needed.
- Flow may then pass to step 1414 to perform opportunistic selection of VSIM, if needed, which will be further described herein with reference to FIG. 15 .
- Opportunistic selection of VSIM may be needed if VSIM selection rules apply to the particular agent, the transaction application, and/or vehicle geographical location. Steps 1412 and 1414 may not be necessary if the transaction application does not need remote network access.
- step 1416 determines whether other profile information is needed from the agent's identity profile. Other information includes, for example, payment information, which could be necessary if the transaction application has a commercial component. If other profile information is needed, then flow passes to step 1418 to get the other profile information and provide such information to the transaction application. Finally, after the profile information is provided to the transaction application in step 1418 , or if other profile information is not needed as determined in decision box 1416 , flow passes to step 1420 to provide any obtained network credentials, including the VSIM, to the transaction application.
- FIG. 15 is a simplified flowchart of an opportunistic VSIM selection flow 1500 .
- the VSIMs may be opportunistically selected for better connectivity, for different traffic and application types, for different locations, and for a better user experience.
- opportunistic VSIM selection flow 1500 dynamically evaluates VSIM selection rules database 85 to determine whether a particular VSIM selected for connectivity is the preferred VSIM for a particular set of criteria (e.g., agent identity, location of the vehicle, transaction application).
- Opportunistic VSIM selection flow 1500 may occur when a transaction has been initiated and a corresponding transaction application is waiting for network credentials, or during an established network connection associated with a transaction application.
- FIG. 15 is described with reference to opportunistically selecting a VSIM, it will be appreciated that other wireless connection options (e.g., WiFi, etc.) may also be opportunistically selected and may be mapped to particular sets of criteria.
- Flow may begin in steps 1504 through 1508 where the set of criteria are determined.
- an agent associated with the network access/attempt may be identified.
- a transaction application associated with the network access/attempt may be identified.
- a current location of the vehicle may determined (e.g., by navigation system 17 ).
- Flow then passes to step 1510 where one or more preferred VSIMs are identified from VSIM selection rules mapping database 85 .
- decision box 1512 a determination is made as to whether the current VSIM(s), which could include one or more VSIMs, are equivalent to the preferred VSIM(s) identified from VSIM selection rules mapping database 85 .
- the current VSIM(s) When opportunistic VSIM selection flow 1500 is processing to evaluate an established network connection associated with a transaction application, the current VSIM(s) could be one or more VSIMs currently being used for the established network connection. However, when opportunistic VSIM selection flow 1500 is processing during identity profile access flow 1400 at step 1414 , then the current VSIM(s) could be one or more VSIMs selected from an identity profile for a transaction application waiting to receive network credentials. If the preferred VSIM(s) are different than the current VSIM(s), then flow passes to step 1514 where the current VSIM(s) are changed to the preferred VSIM(s). In the case of an established network connection, the network connection may be moved to network access links enabled by the preferred VSIM(s).
- step 1514 After the current VSIM(s) are changed to the preferred VSIM(s) in step 1514 , or if the current VSIM(s) are equivalent to the preferred VSIM(s) as determined in decision box 1512 , then flow passes to step 1516 to evaluate network conditions.
- step 1518 a determination is made as to whether any policies override the current VSIM(s) because, in one embodiment, various network conditions and policies related to such network conditions may override a VSIM preference. For example, a VSIM preference based on a particular location, such as a preference for using mobile network operator X in New York because it is more cost effective than using mobile network operator Y, may be overridden if the network conditions of mobile network operator X are not suitable.
- VSIMs or a VSIM associated with another agent may be selected, depending on network conditions and authorization to use the other agent's network credentials.
- the associated transaction application may establish a network connection using the current VSIM(s) or may continue network access with the current VSIM(s), as appropriate.
- a connected vehicle can opportunistically switch between multiple VSIM identities to allow for multiple identity profiles to be used during the vehicle's lifecycle.
- the infrastructure enables multiple agents to source communication from the vehicle.
- a manufacturer of the vehicle may provision an OBU (e.g., OBU 30 ) configured within vehicle 4 with a physical UICC card that is initialized with an identity associated with the vehicle manufacturer, which can be used for authentication to download soft SIM or VSIM identities issued by mobile network operators.
- OBU e.g., OBU 30
- a software agent may also be provisioned in OBU 30 to connect to a desired an identity service provider 60 (e.g., third party identity service provider, mobile network operator, manufacturer identity service provider, etc.) to obtain the VSIM.
- an identity service provider 60 e.g., third party identity service provider, mobile network operator, manufacturer identity service provider, etc.
- vehicle 4 is manufactured in Japan
- software agent may use the manufacturer VSIM to authenticate vehicle 4 to the identity service provider, and then download a VSIM to be used during quality assurance testing before vehicle 4 is exported from Japan to an automotive dealer in the United States (U.S.).
- the software agent can use manufacturer VSIM identity to download a VSIM of a local mobile network operator (e.g., Verizon, AT&T, T-Mobile, SPRINT, PCS, etc.), by accessing an identity service provider 60 through which the manufacturer has provisioned VSIMs.
- a local mobile network operator e.g., Verizon, AT&T, T-Mobile, SPRINT, PCS, etc.
- the manufacturer may be able to negotiate a better rate (e.g., for a particular area) with different mobile network operators at any time and simply update the associated VSIM on vehicle 4 .
- a consumer purchases vehicle 4 from the automotive dealer and becomes an owner of vehicle 4 , he may provision one or more different VSIMs on the OBU of vehicle 4 for his own network access.
- the owner may authenticate to a desired identity service provider 60 and download a desired one or more VSIMs to be used for connectivity (e.g., 3G or 4G) by the owner.
- the owner may also download an identity profile to allow personalization of contacts and various preferences provided in the identity profile, as previously described herein (e.g., personalized contacts, vehicle settings, payment methods, device lists, etc.).
- the owner may also configure authentication requirements to authenticate to vehicle 4 (e.g., set up as desired via key fob, user ID and password, biometrics, etc.).
- another VSIM may be provisioned.
- the family member may authenticate to the same or different identity service provider and download his own one or more VSIMs, which could correspond to the same or different mobile network operators.
- a separate identity profile for the family member may also be downloaded to allow for personalization of preferences, subject to policies implemented by the owner or other superagent and subject to priorities related to the role of an agent at a particular time (e.g., driver vs. passenger).
- the family member may also configure authentication requirements, which could be provided in identity profile, in order to authenticate to vehicle 4 each time the family member is in the vehicle as a driver or a passenger.
- the new owner can download his particular one or more VSIMs and/or identity profile from an appropriate identity service provider, and can create authentication requirements for authenticating to the vehicle.
- the VSIMs and identity profiles associated with the previous owner, any human agent associated with the previous owner, and any mobile devices may be removed from OBU 30 .
- other identity profiles and VSIMs associated with agents such as authorized entities, machine devices, and software agents may remain on OBU 30 , if appropriate.
- vehicle 10 is described with reference to an automobile.
- Communication system 10 is not limited to automobiles, but can be applied to a myriad of other types of vehicles (e.g., airplanes, boats, trains, etc.). It will be appreciated that the broad teachings disclosed herein are intended to include any type of vehicle used to move from one location to another location, including vehicles that are not designed to transport humans.
- enabling secure transactions and flexible identity management activities outlined herein may be implemented in software. This could be inclusive of software provided in transaction security framework 70 of OBU 30 and in other modules and elements such as secure communication module 77 . These elements and/or modules can cooperate with each other in order to perform the enabling secure transactions and flexible identity management activities as discussed herein. In other embodiments, one or more of these features may be implemented in hardware, provided external to these elements, or consolidated in any appropriate manner. For example, some of the processors associated with the various elements may be removed, or otherwise consolidated such that a single processor and a single memory location are responsible for certain activities. In a general sense, the arrangements depicted in FIGS. 1 , 3 and 4 may be more logical in their representations, whereas a physical architecture may include various permutations, combinations, and/or hybrids of these elements.
- OBU 30 may also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.
- communication system 10 may be applicable to other exchanges or routing protocols in which packets are exchanged in order to provide mobility data, connectivity parameters, access management, etc.
- communication system 10 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements and operations may be replaced by any suitable architecture or process that achieves the intended functionality of communication system 10 .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Multimedia (AREA)
- Environmental & Geological Engineering (AREA)
- Human Computer Interaction (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Mechanical Engineering (AREA)
- Automation & Control Theory (AREA)
- Medical Informatics (AREA)
- Transportation (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Mobile Radio Communication Systems (AREA)
- Traffic Control Systems (AREA)
- Navigation (AREA)
- Small-Scale Networks (AREA)
- Telephonic Communication Services (AREA)
- Electric Propulsion And Braking For Vehicles (AREA)
Abstract
A method in one embodiment includes authenticating a first agent to an on board unit (OBU) of a vehicle if the first agent validates a first set of one or more authentication requirements and identifying a first identity profile corresponding to the first agent. The method also includes determining a role of the first agent in the vehicle and configuring the vehicle with the first identity profile, where the vehicle is configured based, at least in part, on the role of the first agent. In this embodiment, the first identity profile is one of a plurality of identity profiles provisioned on the OBU. In specific embodiments, each one of a plurality of agents corresponds to a respective one of the plurality of identity profiles, and includes one or more of a human agent, a machine device, a software agent, an authorized entity, and a mobile device.
Description
- This application is a divisional (and claims the benefit under 35 U.S.C. §120) of U.S. application Ser. No. 13/014,605, filed Jan. 26, 2011, entitled “SYSTEM AND METHOD FOR ENABLING SECURE TRANSACTIONS USING FLEXIBLE IDENTITY MANAGEMENT IN A VEHICULAR ENVIRONMENT,” Inventors Sateesh K. Addepalli, et al., which application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Application Ser. No. 61/433,138, filed Jan. 14, 2011, by Sateesh K. Addepalli, et al., entitled “SYSTEM, METHOD, AND PROCESSES ASSOCIATED WITH CONNECTED VEHICLES.” The disclosures of both of the prior applications are considered part of (and are incorporated by reference in) the disclosure of this application in their entireties.
- This invention relates in general to the field of electronic communications and, more particularly, to enabling secure transactions using flexible identity management in a vehicular environment.
- Networking architectures have grown increasingly complex and have been designed for use in a wide variety of communications environments. Demand continues to rise among the subscriber base of end users, however, for network access across diverse network environments. In particular, configuring suitable network architecture for vehicular environments (e.g., automobiles, airplanes, trains, boats, etc.) presents unique difficulties. Vehicles can be mobile across a large geographic area, can have internal networks related to the vehicle itself, can include more than one end user at a time, and can have more than one owner during the life of the vehicle. Providing the ability to conduct transactions in vehicular network environments in a secure manner and providing a secure and flexible identity management framework for various agents conducting the transactions present significant challenges to system designers, automobile manufacturers, service providers, and the like.
- To provide a more complete understanding of the present invention and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:
-
FIG. 1 is a simplified schematic diagram of a communication system for enabling secure transactions using flexible identity management in a vehicular environment in accordance with embodiments of the present disclosure; -
FIG. 2 is a simplified schematic diagram of the communication system in exemplary network environments associated with embodiments the present disclosure; -
FIG. 3 is another simplified schematic diagram of the communication system in exemplary network environments associated with embodiments of the present disclosure; -
FIG. 4 is a simplified block diagram of an on-board unit of the communication system and possible agents of the on-board unit; -
FIG. 5 is a block diagram of a plurality of identity profiles in an example scenario of the communication system; and -
FIGS. 6-15 are simplified flowcharts associated with possible activities associated with the communication system of the present disclosure. - A method in one example embodiment includes detecting an event for a transaction on an on-board unit (OBU) of a vehicle, where the event has a trigger associated with an agent. The method also includes determining whether the transaction is authorized, identifying network credentials of the agent, and providing the network credentials to a transaction application corresponding to the transaction. The method further includes accessing a remote network using the network credentials. In one embodiment, the network credentials are identified in an identity profile associated with the agent. In specific embodiments, the method includes providing application programming interfaces (APIs) to the transaction application to enable the transaction application to access one or more of a plurality of pieces of information of the identity profile. In other specific embodiments, the method includes evaluating a memory element to determine whether the transaction application is mapped to the agent.
- A method in an another example embodiment includes initiating a transaction on an on board unit (OBU) of a vehicle and selecting first network credentials for a transaction application associated with the transaction to establish a network connection between the OBU and a remote node. In this embodiment, the first network credentials are selected from a plurality of available network credentials that correspond to an agent associated with the transaction. In more specific embodiments, the first network credentials include one or more virtual subscriber identity modules (VSIMs). In other more specific embodiments, the first network credentials are selected based on a mapping of the first network credentials to one or more predefined criteria and the agent.
- A method in yet another example embodiment includes authenticating a first agent to an on board unit (OBU) of a vehicle if the first agent validates a first set of one or more authentication requirements and identifying a first identity profile corresponding to the first agent. The method also includes determining a role of the first agent in the vehicle and configuring the vehicle with the first identity profile, where the vehicle is configured based on the role of the first agent. In the example method, the first identity profile is one of a plurality of identity profiles provisioned on the OBU.
- Turning to
FIG. 1 ,FIG. 1 is a simplified block diagram of acommunication system 10 for enabling secure transactions using flexible identity management in a vehicular environment. The example architecture ofFIG. 1 includes an end user (driver) 2 operating avehicle 4 that includes an on-board unit (OBU) 30. In this particular example, OBU 30 includesprocessing elements 21, which include acomputing processor 22 and arouting processor 23. OBU 30 also includes amemory element 24,network interfaces 26, auser interface 27, and adisplay 28. OBU 30 can be suitably coupled to a plurality of sensors 14 a-c, a plurality of controls (e.g., electronic control units (ECUs)) 16 a-c, and a plurality of actuators, such asactuator 13. In one example embodiment, sensors 14 a-b and controls 16 a-b may be part of an automotive diagnostic system, indicated byvehicle diagnostics 19, which may also be suitably integrated withOBU 30. OBU 30 may also be suitably coupled to various in-vehicle mobile devices 18 a-b at any given time, where such devices may be associated with particular end users (passengers or driver) withinvehicle 4. OBU 30 may also include capabilities associated with navigation system 17 (e.g., a global positioning system (GPS)).FIG. 1 also includesnetworks 40, representing various types of connectivity to vehicle 4 (e.g., via antenna 29). Each established network ofnetworks 40 has a logical coupling to remote network nodes or other external electronic devices, which may includetransaction systems 50, authorizedentities 98, andother vehicles 59. - Elements of
FIG. 1 may be coupled to one another through one or more interfaces (e.g., network interfaces 26) employing any suitable connection (wired or wireless), which provides a viable pathway for electronic communications. Additionally, any one or more of these elements may be combined or removed from the architecture based on particular configuration needs.Communication system 10 may include a configuration capable of transmission control protocol/Internet protocol (TCP/IP) communications for the electronic transmission or reception of packets in a network.Communication system 10 may also operate in conjunction with a user datagram protocol/IP (UDP/IP) or any other suitable protocol, where appropriate and based on particular needs. In addition,communication system 10 may also include a configuration capable of accommodating legacy bus subsystems that may be employed to convey information across the myriad of machine devices (e.g., sensors 14 a-c, controls 16 a-c, actuator 13) invehicle 4. - Embodiments of
communication system 10 can enable secure transactions in a vehicular environment by using flexible identity management for agents associated with the transactions. Given the plethora of transaction agents (e.g., machine devices, humans, software agents, mobile devices, and authorized entities) and possible transactions (e.g., accessing one or more wireless/mobile/cellular networks and using network bandwidth and services, gaining access to various resources of the vehicle based on an identity profile and/or associated databases, gaining access to transaction applications in the vehicle, and engaging in commercial activities), numerous transaction scenarios may occur over the life of the vehicle. Such transaction scenarios may encompass, for example, toll or parking payments, vehicle miles traveled (VMT) systems, Internet commerce, original equipment manufacturer (OEM), gas and electric charging stations, roadside and/or drive-through kiosks, banking applications, vehicle dealer systems, location based service (LBS) system, vehicle system and its resources, mobile network operator system, travel agencies, rental and leasing agencies, network connection to Internet sites, vehicle-to-vehicle commerce, vehicle-to-mobile-device commerce, in-vehicle commerce systems, etc. Accordingly, it is important to have a unified, flexible, and secure identity and access framework to ensure that appropriate transactions can be executed by different agents over time in a secure manner. A unified identity management framework enables aggregation and association of these agents and transactions. -
Communication system 10 may include on-board unit (OBU) 30 that validates credentials of each agent, grants appropriate levels of access, manages potential conflicts (e.g., by assigning priority to different agents), and provisions the appropriate wireless/mobile connectivity. An agent may be provisioned for authentication and access to a particular vehicle by provisioning at least one virtual subscriber identity module (VSIM) and/or an identity profile in OBU 30 ofcommunication system 10. For each agent, an individualized, multi-factor authorization process may be used to validate the particular agent's credentials for accessingOBU 30 and for authorizing transactions onOBU 30. Authentication and confidentiality schemes may be specified for transaction applications corresponding to the particular transactions. Finally, appropriate wireless/mobile connectivity may be dynamically determined by evaluating the transaction, the agent, and a current geographical location of the vehicle. Thus, vehicular transactions may be securely enabled by managing the identity and authentication of agents associated with transactions. - For purposes of illustrating the operational aspects of
communication system 10, it is important to first understand the activities and problems that may be present in electronic communication scenarios in a vehicular environment such as the one shown inFIG. 1 . The following foundational information may be viewed as a basis from which the present disclosure may be properly explained. Such information is offered earnestly for purposes of explanation only and, accordingly, should not be construed in any way to limit the broad scope of the present disclosure and its potential applications. - Many useful, but disparate, networks may exist in today's vehicles. For example, a controller-area network (CAN) bus, a geographical positioning system (GPS), and personal mobile devices (e.g., mobile phones, smart mobile phones/devices, e-book readers, tablets, laptops/net books, portable navigation systems, multimedia devices, etc.) facilitate the coexistence of some of the many possible networks within a single vehicle such as a personal automobile. A CAN bus is a vehicle bus standard designed to allow microcontrollers, sensors, and other devices associated with a vehicle to communicate with each other within the vehicle (e.g., without a host computer). CAN is a message based protocol, designed for and typically used by automotive applications. With appropriate network access, the CAN bus can be used to provide real-time vehicle diagnostics from associated sensors and controls to a manufacturer of the vehicle or to any other authorized entity. A separate network in the vehicle may exist for IP devices involved in the vehicle navigation system (e.g., GPS) and, possibly, another network associated with simple content delivery. Other networks could be used for Internet access for end users through, for example, mobile devices. Hence, various levels of network usage, different purposes of network usage, and different agents (e.g., humans, machine devices, external devices, mobile devices) associated with the network usage may occur in a single vehicle. Network usage in each of the identified cases may have a different usage scope, different latency, different associated routing, different policy requirements, and the like.
- In a vehicle that does not offer combined networking capabilities for the various possible networks, each of the devices associated with a particular network (e.g., CAN bus sensors, mobile devices, GPS, etc.) may have a one-to-one mapping to either a human agent or to the vehicle. Network access and any resulting fees from such access are typically dictated by the human agent or vehicle mapped to the particular device. While some of these devices may be used by other human agents (e.g., another human agent borrows a cell phone, has account privileges on a laptop, borrows an automobile with a GPS, etc.) network access and fee accrual does not ordinarily accommodate the preferences of the new user. In some cases, a mobile router used to facilitate network access among various agents associated with a vehicle, could provide predetermined network access and billing, without regard to the particular agent or transaction.
- In a vehicle that provides networking capabilities between entities inside the vehicle and the external world (“connected vehicle”), the amount of possible transactions and the changeability of agents associated with those transactions require a flexible framework to ensure security and appropriate network access. In a real-life scenario for a connected vehicle, multiple agents may use the vehicle and perform transactions on or via the vehicle over any given time period. Individual users such as, for example, an owner, a driver, a passenger, a temporary driver (e.g., borrower or renter), or a new owner of a used automobile, may use the vehicle as a personal computing and communication platform for navigational, recreational, and/or business-related purposes. A manufacturer of the vehicle may want to collect vehicle centric data from the vehicle and send firmware/software upgrades to the vehicle. Government entities may want to identify and locate the vehicle for law enforcement or government regulation (e.g., emissions controls) purposes. Vehicle dealers may want to obtain sensor data and other vehicle diagnostic information for maintenance updates and/or scheduling. Thus, a one-to-one exclusive mapping between an agent (e.g., a human or a device) and a connected vehicle does not exist.
- In a contrasting example, a one-to-one mapping is typically provided between a mobile phone and a single user. In a mobile phone, credentials that bind the user and the device may be stored in a physical subscriber identity module (SIM) or provisioning module. Thus, if the mobile device is subsequently operated by a new user (e.g., someone borrowing the mobile phone), the credentials in the current SIM, associated with the original user, will be used to access a cellular network and to bill for the network access usage. Thus, the original user mapped to the mobile phone will be billed for any network usage fees incurred by the new user. In some cases involving the same service provider, the mobile phone can be provisioned with the new user's credentials by physically replacing the existing SIM hardware with a SIM of the new user. However, SIM swapping or identity reassignment across different service providers is often problematic or simply not feasible in a mobile phone.
- In a connected vehicle, agents may change over any given period of time, and it may be impossible or impractical to physically switch a SIM in the vehicle or to make a trip to a service center each time a new agent needs network access to or from the vehicle. In one example, a manufacturer of an automobile may want to use a transaction application to collect real time data from sensors in the vehicle. If the automobile is manufactured in one country and shipped to another country (e.g., manufactured in Japan and shipped to the United States), then before the automobile is even purchased it would have traveled across international boundaries and multiple telecom service provider areas. Thus, if the manufacturer (i.e., the agent) provisions the automobile with credentials for a first service provider usable in the first country, the manufacturer may prefer a different service provider to be provisioned in the automobile once the automobile is shipped to another country.
- Another example of possible agent changes in a vehicle includes owners, drivers, renters, and passengers of a vehicle. When an automobile is sold to a customer, the new owner needs access rights to various transactions (e.g., toll payments, gas and charging stations, Internet commerce, personal vehicle settings, etc.) provided by the vehicle. In addition, the new owner may need wireless access to networks and devices external to the vehicle using an appropriate service provider and a desired billing scheme. These access rights may need to change each time the vehicle is driven by a different driver (e.g., another person in the owner's family, a current renter of a rental car, etc.). In addition, if the vehicle is sold again, a new owner and associated drivers and passengers also need access rights and the previously existing access rights need to be removed from the vehicle. Finally, multiple agents may want to access the vehicle concurrently, such as a driver and one or more passengers of the vehicle who desire access rights to at least some of the vehicle transactions. For example, a passenger may want to use an Internet commerce transaction to download music or videos, or the passenger may want to pay for transportation costs, such as toll expenses and/or gas and charging station expenses.
- Supporting a multi-agent and multi-transaction vehicular environment may also require more protection layers than typically used in traditional authentication schemes such as a simple user identification (“user ID”) and password. In one example, additional protection layers may be necessary for certain transactions and agents to avoid compromising security (e.g., highly sensitive transactions such as transactions allowing modifications by a manufacturer of the vehicle itself) and/or regulatory compliance of a transaction. Thus, flexible agent identity management is needed with a strong authentication component that provides adequate security for dynamically changing agents and transactions, such that security, privacy, authenticity, accountability, and regulatory compliance are not compromised.
- A system for enabling secure transactions in a vehicular environment using flexible identity management for agents associated with the transactions, outlined by
FIG. 1 , can resolve many of these issues. In accordance with one example implementation ofcommunication system 10, a method is provided for agent identity management that is flexible, secure, and allows network access to be switched dynamically for different agents. The method provides for authenticating an agent to on-board unit (OBU) 30 ofvehicle 4, provisioning an identity profile associated with the agent, and provisioning one or more virtual subscriber identity modules (VSIMs) associated with the agent. For a human agent, the identity profile can include individualized vehicle preferences (e.g., seat position, cabin temperature settings, radio or other media, navigation locations, etc.). Boundaries such as parental controls and transaction access controls may also be provided in an identity profile, which can be added by another agent having appropriate authority. The method also provides for verifying whether a particular transaction is authorized when the transaction is associated with the agent. For authorized transactions requiring remote network access to external devices, the method allows for opportunistic selection of network credentials, such as VSIMs, WiFi, etc., associated with the particular agent, which may be determined by evaluating the agent, the transaction, and a current geographical location of the vehicle. Thus, transactions are securely enabled for different agents by providing a dynamic identity framework for agents. In addition, network access can be opportunistically selected depending on one or more factors, including the agent, the transaction and the current location of the vehicle. - Note that in this Specification, references to various features (e.g., elements, structures, modules, components, steps, operations, characteristics, etc.) included in “one embodiment”, “example embodiment”, “an embodiment”, “another embodiment”, “some embodiments”, “various embodiments”, “other embodiments”, “alternative embodiment”, and the like are intended to mean that any such features are included in one or more embodiments of the present disclosure, but may or may not necessarily be combined in the same embodiments.
- Turning to the infrastructure of
FIG. 1 ,end user 2 can be associated with a human agent (e.g., a driver or passenger) having any type of relationship to the vehicle such as an owner, a renter, a temporary driver, a family member or friend of the owner, etc.End user 2 may initiate communication incommunication system 10 via some network, and such communication may be initiated through any suitable device, inclusive of an in-vehiclemobile device display 28, andnavigation system 17. In one embodiment, additional displays may be provided for one or more passengers invehicle 4. In-vehicle mobile devices 18 a-b are inclusive of mobile phones, smart mobile phones (smartphones), e-book readers, tablets, iPads, personal digital assistants (PDAs), laptops or electronic notebooks, portable navigation systems, multimedia gadgets (e.g., cameras, players, etc.), and any other device, component, element, or object capable of initiating voice, audio, video, media, or data exchanges withincommunication system 10. Data, as used herein in this specification, refers to any type of numeric, voice, video, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another in electronic devices and/or networks. - In-vehicle mobile devices 18 a-b, and mobile devices external to
vehicle 4, may communicate withOBU 30 ofcommunication system 10 through any wired or wireless communication link and may be configured as a personal area network (PAN) or a wireless personal area network (WPAN) or any other appropriate architecture or system that facilitates communications in a network environment. Wired and wireless communication links may be inclusive of any electronic link such as Bluetooth, wireless technologies (e.g., IEEE 802.11x), a USB cable, an HDMI cable, etc. Connection between mobile devices andOBU 30 may be configured based on particular needs and logistics. In one particular example, an external mobile device may be connected toOBU 30 through a USB cable or wireless network when, for example, the external mobile device is a diagnostic tool used by a mechanic for servicingvehicle 4. -
Networks 40 represent a series of points or nodes of interconnected communication paths for receiving and transmitting packets of information that propagate throughcommunication system 10.Networks 40 offer communicative interfaces between any of the components ofFIG. 1 and remote network nodes and other electronic devices (e.g.,transaction systems 50, authorizedentities 98, and other vehicles 59), and may be any local area network (LAN), wireless local area network (WLAN), wide area network (WAN), wireless wide area network (WWAN), metropolitan area network (MAN), wireless metropolitan area network (WMAN), wireless single hop or multi-hop vehicle-to-vehicle network, virtual private network (VPN), Intranet, Extranet, or any other appropriate architecture or system that facilitates communications in a network environment.Networks 40 may include any suitable communication link toOBU 30 such as wireless technologies (e.g., IEEE 802.11x), satellite, cellular technologies (e.g., 3G, 4G, etc.), etc., or any combination thereof.Networks 40 may also include configurations capable of transmission control protocol/Internet protocol (TCP/IP) communications, user datagram protocol/IP (UDP/IP), or any other suitable protocol, where appropriate and based on particular needs. - Embodiments of
OBU 30 may include one or more distinct interfaces, represented bynetwork interfaces 26, to facilitate communication via the various networks described herein. Such network interfaces 26 may be inclusive of multiple wireless interfaces (e.g., WiFi, WiMax, 3G, 4G, white space, 802.11x, satellite, Bluetooth, LTE, GSM/HSPA, CDMA/EVDO, DSRC, CAN, GPS etc.). Other interfaces represented bynetwork interfaces 26, may include physical ports (e.g., Ethernet, USB, HDMI, etc.), and the like. Similarly, each of the network elements and user equipment (e.g., mobile devices) ofcommunication system 10 can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment. -
OBU 30 can include one or more memory elements (e.g., memory element 24) for storing information to be used in achieving operations associated with the enablement of secure transactions using flexible identity management, as outlined herein. Any of the memory or storage items discussed herein should be construed as being encompassed within the broad term ‘memory element’ as used herein in this Specification. - In example embodiments, the operations for enabling secure transactions using flexible identity management outlined herein may be implemented by logic encoded in one or more tangible media, which may be inclusive of non-transitory media (e.g., embedded logic provided in an ASIC, digital signal processor (DSP) instructions, software potentially inclusive of object code and source code to be executed by a processor or other similar machine, etc.). In some of these instances, one or more memory elements (e.g., memory element 24) can store data used for the operations described herein. This includes the memory elements being able to store software, logic, code, or processor instructions that are executed to carry out the activities described in this Specification.
- Additionally,
OBU 30 may include processingelements 21, includingcomputing processor 22 androuting processor 23, that can execute software or algorithms to perform the activities to enable secure transactions, to use flexible identity management, and to route packets, using suitable routing protocols, associated with the secure transactions and identity management. A processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, the processors (as shown inFIG. 1 ) could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., an FPGA, an EPROM, an EEPROM), or an ASIC that includes digital logic, software, code, electronic instructions, flash memory, optical disks, CD-ROMs, DVD ROMs, magnetic or optical cards, other types of machine-readable mediums suitable for storing electronic instructions, or any suitable combination thereof. Any of the potential processing elements, modules, microprocessors, digital signal processors (DSPs), and other devices described in this Specification should be construed as being encompassed within the broad term ‘processor.’ - Regarding a physical implementation of
OBU 30, any suitable permutation may be applied based on particular needs and requirements, including the design of the particular vehicle in whichOBU 30 is implemented. In example implementations, various components ofOBU 30 may be installed in different physical areas of the vehicle or may be installed as single unit, withdisplay 28 being positioned to allow driver access. Other displays may be provided in suitable locations for access by passengers in particular passenger seats. In one implementation, multimedia, networking, and communication components may be positioned at some distance from the vehicle engine (e.g., in or near the rear or trunk area if the engine is in the front area of the vehicle). -
Communication system 10 may be configured to facilitate communication with machine devices (e.g., vehicle sensors, instruments, electronic control units (ECUs), embedded devices, actuators, etc.).OBU 30 may be implemented to provide one or more suitable communication interfaces (e.g., network interfaces 26) to legacy systems in vehicles such as, for example, a controller area network (CAN) a low speed network (LIN), a flexray communications protocol network, media oriented systems transport (MOST), and the like. Typically, multiple ECUs, with different embedded software, may be found in a single automobile and may communicate via a CAN bus. Sensors 14 a-b may represent, for example, wheel and headlight sensors, respectively. Controls 16 a-b may be inclusive of any embedded system or ECU that controls one or more of the electrical systems or subsystems invehicle 4.Actuator 13 represents a vehicle setting device such as, for example, a seat positioning device for adjusting various seat positions (e.g., longitudinal position relative to the brake and gas pedals, tilt position, lumbar support, etc.).Actuator 13 and other similar vehicle setting devices (e.g., temperature controls, sunroof, door locks, power windows, etc.) may be configured for communications in a LIN bus, in one embodiment.Sensor 14 c represents a type of sensor or device that may be configured for communications via flexray communications protocol (e.g., a radar collision sensor).Control 16 c, representing one or more ECUs, may be suitably integrated for controlling the flexray network and sensors and other associated components. Additionally,OBU 30 may be implemented to provide one or more suitable communication interfaces (e.g., network interfaces 26) to an Internet Protocol (IP) network, user datagram protocol (UDP) network, or any other suitable protocol or communication architecture provided to enable network communication with machine devices invehicle 4. - In this particular example,
vehicle 4 includes capabilities associated withnavigation system 17 andvehicle diagnostics 19.Navigation system 17 may be provided in various embodiments including, for example, a portable navigation system or, alternatively, a fixed navigation system, each of which may be configured for wireless or wired communications toOBU 30. Other more specific machine devices, not shown inFIG. 1 , may include display panel instruments, climate controls, interior lights, door locks, trunk open/shut actuator, hood open/shut actuator, seat heater and/or cooler, sunroof open/shut actuator, window heater/defroster/defogger, entertainment systems (e.g., speakers, radio, DVD, CD, etc.), and the like. - Turning to
FIG. 2 ,communication system 10 is illustrated withOBU 30 shown coupled toagents 90 andnetworks 40. As previously discussed herein,agents 90 can includemachine devices 92,humans 94, andmobile devices 96. In addition, agents can also includesoftware agents 95 and authorizedentities 98.Software agents 95 can include any executable file comprising instructions that can be understood and processed on a computer, and provisioned in a memory element accessible to OBU 30 (e.g., memory element 24), and which may be initiated automatically in response to a particular set of criteria or conditions (e.g., every time network connectivity is detected onOBU 30, wheneverOBU 30 is powered on and a particular time interval has passed, in response to another software agent, etc.). -
Authorized entities 98 may include various entities having authorization to access avehicle 4 such as, for example, a dealer of the vehicle, a manufacturer of the vehicle, OEMs associated with the vehicle, and public entities having an interest in the vehicle (e.g., State Departments of Transportation, local police departments, etc.). A network node of such authorized entities will typically be remotely located fromOBU 30 and, therefore, accessible fromOBU 30 throughnetworks 40 such as the Internet or other WANs and any available communication link (e.g., 3G, 4G, local wireless, etc.) providing network access fromOBU 30 to the Internet or other WAN. In some scenarios, however,OBU 30 may be locally accessible to an authorized entity such that Internet access is unnecessary. For example, whenvehicle 4 is being manufactured and is located at one of the manufacturer's facilities,OBU 30 may be capable of directly accessing the manufacturer's network through a LAN or WLAN. Similarly, when avehicle 4 is taken to a dealer for maintenance, theOBU 30 may connect to the dealer network through a communication link that does not include the Internet or any other wide area network. -
Networks 40 may also facilitate communication between certain agents 90 (e.g.,machine devices 92,humans 94,software agents 95, mobile devices 96) andtransaction systems 50. By way of example,transaction systems 50 may includeservices transaction systems 52,commercial transaction systems 54,roadside transaction systems 56, andtransportation transaction systems 58 on network nodes or other electronic devices. Each of the transaction systems can be associated with many different types of entities and many different transaction scenarios.Services transaction systems 52 can encompass numerous entities providing services such as identity service providers, mobile wireless service providers, banks and other financial institutions, location-based services (LBS), travel agencies, vehicle rental and leasing agencies, Internet websites, etc. In some implementations, however, a vehicle rental and leasing entity may be provisioned as an agent of the OBU, such as when the vehicle itself is owned by the rental and leasing entity. In this particular scenario, the rental and leasing agency could be an authorized entity ofvehicle 4, and any authorized employees could be human agents of the vehicle.Commercial transaction systems 54 may include entities facilitating commercial transactions through the Internet (e.g., video and music download sites, online retailers, etc.), etc.Roadside transaction systems 56 may include various entities providing roadside services such as gas and electric charging stations, kiosks (both roadside and drive-through), etc.Transportation transaction systems 58 may include entities or devices facilitating vehicle charging transactions related to toll payments, ferry charges, bridge toll payments, parking, Vehicle Miles Traveled (VMT), and any other transportation costs incurred as a result of movingvehicle 4 from one location to another. Thetransaction systems - Other commercial transactions may occur through
OBU 30 by accessing other vehicles 59 (vehicle-to-vehicle commerce). An available network represented bynetworks 40, may provide a communicative pathway betweenvehicle 4 andother vehicles 59, wherevehicle 4 includesOBU 30 andother vehicles 59 include a suitable communication device (e.g., mobile device, OBU or similar device). The communicative pathway betweenvehicle 4 andother vehicles 59 could be established as a single hop or multi-hop vehicle-to-vehicle network through WiFi, WiMax, or any other suitable wireless technologies allowing a sustained connection betweenvehicle 4 andother vehicles 59. Commercial transactions could occur between a mobile device in one vehicle (connected to an OBU) and an OBU in another vehicle, between mobile devices in separate vehicles with OBUs, or between OBUs of separate vehicles. Commercial transactions may also be conducted betweenOBU 30 and mobile devices 96 (vehicle-to-mobile device commerce), such as when a mobile device purchases content fromOBU 30. Another type of commercial transaction can include in-vehicle commerce in which a user of a mobile device pays for the use of resources through OBU 30 (e.g., in the case of a passenger in a commercial vehicle such as a taxi cab) or when mobile devices within a vehicle use the network available throughOBU 30 to conduct commercial transactions with each other. In addition to commercial transactions, these communicative pathways involving vehicles and mobile devices may also be established for any other suitable services or transactions, providing proper authentication and network credentials are obtained. - Turning to
FIG. 3 ,communication system 10 depicts a more detailed representation of certain elements ofOBU 30, and ofnetworks 40 providing a communication pathway to a particular service transaction system 52 (i.e., an identity service provider 60). In addition,end user computer 42 andmobile devices 96 are also shown with network access toidentity service provider 60. In accordance with embodiments of the present disclosure, one or more virtualsubscriber identity modules OBU 30 for each agent authenticated to the OBU and having a subscription with a mobile network operator providing cellular services (e.g., AT&T, Verizon, T-Mobile, Sprint, PCS, etc.).VSIMs 32 each include a unique identifier or key 33 that identifies an agent on mobile telephony devices such asOBU 30.VSIMs 32 may also contain security authentication to authenticate the agent to the corresponding mobile network operator. In addition, one or more VSIMs 32 may be provisioned inOBU 30 for each agent ofOBU 30, and multiple VSIMs for one or more agents can be stored inOBU 30 concurrently. Multiple VSIMs 32 provisioned inOBU 30 can enable flexible and opportunistic use of available mobile network operators to provide one or more network access links fromOBU 30 to a remote node, and can also enable these network access links (i.e., communication pathways) on behalf of multipleagents using OBU 30 as a communication source. - In one embodiment,
OBU 30 is equipped with a Universal Integrated Circuit Card (UICC) that allows for multiple universal subscriber identity module (USIM) applications to accommodateVSIMs 32. In this embodiment, one or more ofVSIMs 32 having a desired mobile network operator may be opportunistically selected, if certain criteria are met, so that the desired one or more mobile network operators can be utilized for network access fromOBU 30. In another implementation, multiple SIM cards may be connected toOBU 30 to accommodate a corresponding number of VSIMs. In this implementation involving multiple SIM cards, a software module could be configured to opportunistically select an appropriate one or more SIM cards corresponding to a desired one or more mobile network operators if certain criteria are met. In yet another implementation, VSIMs could be simply soft SIM information stored in a storage repository ofOBU 30 such as part of an identity profile of a corresponding agent. Once downloaded,VSIMs 32 can reside inOBU 30 in accordance with whatever particular implementation is employed, until an expiration of the VSIM or until the VSIM is replaced, updated, or removed by an agent with appropriate authentication and authorization. - In accordance with embodiments of
communication system 10,OBU 30 may also be provisioned with one or more identity profiles 34 a, 34 b, and 34 c (referred to collectively herein as identity profiles 34), with each identity profile 34 corresponding to an agent that can authenticate toOBU 30. Identity profiles 34, as further detailed below, can include credentials and profile information for a particular agent. Credentials contain information that uniquely identifies an agent (e.g., a personal identifier (PID)) and that may be used for authentication purposes. Examples of credentials may include one or more of name, address, phone number, driver's license number, social security number, business license number, IP address, user ID/password, biometrics, personal device identifier (e.g., authentication information corresponding to key fob, access card, credit card, mobile phone, etc.), security keys, and certificates (e.g., public key infrastructure (PKI) certificate, trusted third party (TTP) certificate, etc.). - Profile information aggregates agent attributes, account information, preferences, and/or settings, which can enable appropriate transactions by authenticated agents. For example, profile information can include vehicle settings, dashboard preferences, wireless interface preferences (e.g., VSIM information, WiFi account information, etc.), web account information (e.g., multimedia, social networking, etc.), mobile device list (e.g., smartphones, mobile phones, tablets, laptops, etc.) including network configurations for mobile devices, network service provider membership account information, insurance information, credit card/payment account information, manufacturer web account information, network interface account information, GPS favorite locations, and phone contact list. The information included in a particular identity profile will be at least partially dependent upon the particular agent to which it corresponds. For example, an authorized entity (e.g., a manufacturer of the vehicle, etc.) would not need vehicle settings, GPS favorite locations, or multimedia information in its identity profile. In addition to agents, a profile identity may be provisioned for a vehicle itself including information to distinctly identity the vehicle (e.g., a vehicle identification number (VIN)). It will be apparent that the examples provided herein of credentials and profile information are not all-inclusive, and any other suitable information or data could be included as credentials or profile information.
- Various implementations can accommodate identity profiles 34 in
OBU 30. For example, in one embodiment identity profiles 34 are stored in dedicated hardware (e.g., physical SIM card, memory card, etc.). Software can be configured to virtually switch between different hardware or the hardware itself may be programmable to store different agent identity information over time. In another embodiment, identity profiles 34 are stored in a programmable storage module or virtual identity module that can store one or more identity profiles 34. Generally, identity profiles 34 may be kept in any suitable memory element, software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. In addition, identity profiles 34 may be provided in any database, register, cache, queue, control list, or storage structure. - In example embodiments of the present disclosure,
VSIMs 32 and identity profiles 34 may be provisioned and managed through one or more identity service providers, represented byidentity service provider 60 inFIG. 3 . In one embodiment,identity service provider 60 could be a third party provider (e.g., in the cloud) and could offer identity services to mobile network operators. In other embodiments,identity service provider 60 could be a mobile network operator, a vehicle manufacturer, a vehicle rental and leasing agency, a vehicle dealer, a government agency, or any other entity having an interest in managing identities associated with a vehicle over the life of the vehicle. Moreover, identity profiles 34 and/orVSIMs 32 can be managed through the same or different identity service providers. By storing a VSIM and/or an identity profile in a remote cloud, the VSIM and identity profile can be associated with an agent rather than to a particular vehicle. Consequently, a human agent (e.g., driver, passenger, owner, renter, etc.) can retrieve his VSIM and identity profile in any vehicle. Depending on the make/model of the vehicle, the human agent can leverage relevant parts of the identity profile for available features in virtually any vehicle. - Provisioning and managing an identity profile or VSIM through
identity service provider 60 can be accomplished in various ways. In one scenario, a user could accessidentity service provider 60 through the Internet or other available network from computer 42 (e.g., home computer, publicly accessible computer, business computer, etc.) ormobile devices 96. Additionally,end user 2 could accessidentity service provider 60 by bootstrapping a communication link through OBU 30 (e.g., accessing a home WLAN through WiFi, using a preprogrammed VSIM inOBU 30, using another agent's VSIM already provisioned inOBU 30, etc.) In other scenarios, theidentity service provider 60 may be accessed through a local network (e.g., manufacturer who is an identity service provider locally accessing provisioning modules ofOBU 30 prior to shipping the vehicle, etc.) or other wireless networks (e.g., user accessing mobile network operator through a cellular network if the mobile network operator is its own identity service provider, etc.). -
Identity service provider 60 may provide modules allowing the creation of an account with authentication credentials 66 (which may be saved for future access of the account) for an agent. AVSIM module 61 may be provided byidentity service provider 60 to allow a user to provision a VSIM for an agent, with the VSIM being associated with a desired mobile network operator and stored, for example, inVSIM database 64. Anidentity profile module 63 may also be provided byidentity service provider 60 to allow the user to provision an identity profile for the agent and to store the identity profile in, for example,identity profile database 62. In some scenarios, a user is the agent and provisions a VSIM and/or an identity profile for himself. In other scenarios, the user may provision a VSIM and/or an identity profile for another agent (e.g., a vehicle dealer provisioning a VSIM and/or an identity profile for a new vehicle owner, a vehicle rental agency provisioning a VSIM and/or an identity profile for an agent renting a vehicle, a user at an OEM provisioning a VSIM and identity profile for a software agent configured in the OBU to make network connections to the OEM from the OBU, etc.). -
VSIM 32 and identity profile 34 may be dynamically added, removed, and updated via local or remote network access. After provisioning a VSIM and/or identity profile withidentity service provider 60, the VSIM and/or identity profile may be downloaded using control channels or otherwise provided toOBU 30 if the agent associated with the VSIM and/or identity profile has been authenticated toOBU 30. In one example, to downloadVSIMs 32 and/or identity profiles 34, the agent (e.g., end user 2) may bootstrap a communication link in OBU 30 (e.g., WiFi, an available VSIM, etc.) to accessidentity service provider 60 using control channels through the Internet or other network. - In another example,
end user 2 may access a local network of an identity service provider if a vehicle is in close physical proximity toidentity service provider 60. Onceidentity service provider 60 is accessed, the user can authenticate toidentity service provider 60 viaauthentication credentials 66, access the desired account, and download one or more associatedVSIMs 32 and/or identity profiles 34. Similarly, if a new VSIM for the same agent is provisioned or the identity profile is updated inidentity service provider 60, then the associated agent can use an available VSIM or other available communication link inOBU 30 to accessidentity service provider 60 to download the new VSIM and/or updated identity profile. In another scenario, the VSIM and/or identity profile may be stored on a transportable memory element (e.g., USB stick, CD, etc.), which may be provided locally toOBU 30 by a user, such asend user 2. The VSIM and/or identity profile can then be downloaded toOBU 30 from the transportable memory element. - In other example scenarios, an identity profile may be dynamically created and managed (e.g., removed or updated) locally, directly through
OBU 30. For example,OBU 30 may provide an identity profile creation tool throughdisplay 28 for a user to enter desired credentials and profile information and associate such information with an agent. In another embodiment, the identity profile creation tool may be accessible through a user's mobile device. In these scenarios, the identity profile would not be accessible throughidentity service provider 60 and could only be accessed in the particular vehicle containing the identity profile. - With reference now to
FIG. 4 , a block diagram illustrating an embodiment of the overall identity management and secure transaction processing architecture is shown.OBU 30 includes atransaction security framework 70, a secure database/storage layer 80,transaction applications 78, and asecure communication module 77.Transaction security framework 70 may include multiple software modules,VSIMs 32, and a trusted platform module (TPM) 76. The software modules can includeagent provisioning module 71, authentication andsecure transaction module 72,VSIM provisioning module 73,multi-factor authentication module 74, identityprofile provisioning module 75, andpayment association module 79. -
Agent provisioning module 71 provides the overall flow for provisioning and authenticating an agent toOBU 30.Agent provisioning module 71 allows provisioning new agents, provisioning new and updatedVSIMs 32, provisioning new and updated identity profiles 34, authenticating agents toOBU 30, and activating any applicable identity profiles 34. In addition, agent provisioning module may also invoke payment association module to determine whether to associate a payment method available through the agent (e.g., in the identity profile or through an associated VSIM) to certain transaction applications not typically initiated by an agent having a payment method (e.g., automatic toll payment transactions, automatic parking transactions, etc.) -
Multi-factor authentication module 74 provides a flow for using one or more predefined authentication credentials to authenticate an agent toOBU 30 and to ascertain that the agent is authorized to conduct a particular transaction onOBU 30. In one embodiment,multi-factor authentication module 74 may be invoked upon initial authentication of an agent to gain access toOBU 30 and in addition, when particular transactions are initiated onOBU 30. Authentication credentials may include who, what, and where criteria related to the agent. By way of example, authentication requirements for machine devices and some mobile devices could include one or more of machine hardware signature, challenge-response, predefined certificate (e.g., PKI certificate, TTP certificate, etc.), and physical location relative toOBU 30. Authentication requirements for a human agent 94 (accessingOBU 30 through a mobile device or directly through a user interface such as display 28) could include one or more of biometrics, (e.g., fingerprinting, etc.), challenge-response, key fob, access card, mobile phone, user ID and password, a one-time password (OTP), and physical location relative toOBU 30. Authentication requirements for authorized entities could include challenge-response, predefined certificate, and the like. - In one embodiment, the authentication requirements for each agent may be provided in an agents-to-
multi-factor mapping database 83 of secure database/storage layer 80. In some embodiments, the predefined authentication credentials that are required to authenticate toOBU 30 are specific to the particular agent being authenticated. For example, a key fob may allow an owner agent to authenticate to a vehicle, but only a simple user name and password may be required for a child of the owner to authenticate. In this case, a lesser amount of security may be required for the child to authenticate because the child may have limited access to transaction applications and resources ofOBU 30. Furthermore, authentication requirements to gain access toOBU 30 may be different than authentication requirements for a particular transaction. By way of example, an owner of a vehicle may only need to use a key fob to gain access toOBU 30, but additional authentication may be required for the owner to access various transaction applications and resources ofOBU 30. Security can be strengthened as the number and diversity of authentication requirements mapped to a particular agent is increased. - Implementation of the authentication requirements can be accomplished with any appropriate hardware and/or software. For example,
TPM 76 is a hardware approach that can authenticate an agent, once the agent has provided appropriate credentials.TPM 76 is a secure processor that performs cryptographic functions and can store cryptographic keys for protecting information. In another embodiment, a software container (e.g., a secure virtualized operating system container) could be provided with appropriate authentication logic to authenticate an agent once credentials are provided. Thus, any hardware, software, or suitable combination thereof can be implemented to accomplish the authentication requirements ofmulti-factor authentication module 74. -
TPM 76 can also be used to protect data and transaction applications. For data,TPM 76 can be a safe store for an encryption key so that only an authorized agent who properly authenticates toTPM 76 can access the encryption key to decrypt protected data (e.g., data in secure database/storage layer 80).TPM 76 can also be used to ensure the integrity oftransaction applications 78 executing onOBU 30, which can be achieved locally or remotely depending on the particular transaction application and associated agent. Locally, theOBU 30 can self-ensure that the operating system is on a trusted platform.Transaction applications 78 may each include a signature that can be verified prior to execution.Transaction applications 78 can also be verified remotely to third parties, such as authorizedentities 98. For example, an authorized entity such as a manufacturer may access a transaction application that monitors the brakes and accelerator ofvehicle 4. Before the transaction application executes,TPM 76 can be used to verify the integrity of the application to the manufacturer. Based on the information provided, the manufacturer can respond accordingly (e.g., process data received from the transaction application if the transaction application is verified, cease execution of the transaction application if the transaction application is not verified). - In one embodiment,
TPM 76 has a permanent identity associated withvehicle 4 and does not change even if vehicle ownership changes. Similarly, a vehicle identity (vehicle ID) ofvehicle 4, such as a vehicle identification number (VIN) is also a permanent identity associated withvehicle 4. A TPM endorsement key, which can be used to encrypt data, may have a public key part that can be used as a TPM identifier (TPM ID). Although vehicle ID and TPM ID do not ordinarily change, ifTPM 76 orOBU 30 is replaced during the life ofvehicle 4, then a new TPM ID would need to be associated tovehicle 4. -
VSIM provisioning module 73 and identityprofile provisioning module 75 allow the provisioning of new or updated VSIMs and or identity profiles onOBU 30. Such provisioning may include downloading new or updated VSIMs and identity profiles from an identity service provider either locally or remotely. Provisioning may also include downloading new or updated VSIMs and identity profiles from a transportable memory element or mobile device. In addition, identity profiles may also be manually created inOBU 30, without involving an identity service provider. - Authentication and
secure transaction module 72 provides a flow for detecting an event for a transaction, determining whether the transaction is authorized, authenticating an associated agent if required, and obtaining network credentials and other profile information as needed. Network credentials may include one or more VSIMs' information, user ID and password, and/or security certificates (e.g., asymmetric/symmetric key pair, etc.), and any other information to facilitate vehicle internal network access or external network access via an available wired or wireless communication link. In order to perform necessary authentication and evaluations to ensure secure transaction processing, this module may be configured to query secured storage such as transaction-to-agents mapping database 82, transaction-to-authentication-and-confidentiality-schemes mapping database 84, agents-to-multi-factor-authentication mapping database 83, and agentidentity profiles database 81. As used in this Specification, a mapping of data, elements, objects, or components is intended to mean an electronic association, correspondence, relationship, or correlation between the data, elements, objects, or components, provided in electronic devices and/or networks. In one embodiment, these databases, in addition to any other databases or memory elements in secure database/storage layer 80, can be maintained in a secure manner using the default security credentials obtained fromTPM 76. Moreover, various confidentiality schemes can be used to protect the data stored in the various memory elements of secure database/storage layer 80 such as, for example, cryptographic algorithms including Data Encryption Standard (DES/3DES), Secure Hash Algorithm (SHA-1/2), Advanced Encryption Standard (AES), etc. - Transaction-to-
agents mapping database 82 indicates which transactions are authorized for which agents.Mapping database 82 may include mappings of agent identities to user-level and system-level transaction applications corresponding to transactions and also to types of transactions (e.g., transactions requiring remote network credentials, transactions requiring payment information, etc.). Thus, once an agent has authenticated toOBU 30, only transaction applications that are mapped to the agent, or that correspond to a type of transaction that is mapped to the agent, are authorized and accessible to the agent. Example mappings that could be found indatabase 82 include: 1) a manufacturer mapped to transaction applications for accessing vehicle sensor data (e.g., in order to perform diagnostics), for performing software or firmware upgrades, and for accessing a “black box” of the vehicle, 2) a dealer mapped to transaction applications for accessing sensor data (e.g., read only access in order to schedule maintenance services), 3) an emergency service provider mapped to transaction applications for controlling the vehicle (e.g., opening a vehicle door, disabling a vehicle engine, etc.), 4) a public entity mapped to transaction applications for accessing sensor data or other vehicle diagnostic data (e.g., for inspection, security, surveillance, etc.), 5) an owner of the vehicle mapped to all transaction applications except those allowing “write” or “modify” access to vehicle software and/or firmware, 6) a passenger mapped to a subset of transaction applications and features available to an owner of the vehicle, and 7) a sensor mapped to a transaction application compiling diagnostic data. - Additionally, different agents may have different levels of authorization. For example, a dealer may only need to read vehicle sensor data for maintenance scheduling purposes. Consequently, the dealer would be mapped to a transaction application that only allows read operations of vehicle sensors to be performed. On the other hand, a manufacturer may need to read and update vehicle sensors and controls for performing firmware and/or software upgrades and fixes. Therefore, the transaction applications mapped to the manufacturer could allow read and update functions to be performed.
- In one embodiment, a software agent may be a system-level transaction application that does not have a separate agent initiating its execution or otherwise associated with it. For example, the software agent could be a low level application that automatically initiates processing based upon predefined criteria (e.g., specific time periods, whenever network connectivity is detected, etc.). Accordingly, authorization for the software agent to execute could be provided in any suitable way, including an appropriate indication in transaction-to-agents mapping database 82 (e.g., mapping the software agent to a type of transaction, mapping the software agent to itself).
- Authentication and
secure transaction module 72 may also determine which authentication and confidentiality schemes to use for particular transactions for exchanging data betweenOBU 30 and transaction systems in the cloud. Examples of authentication protocols that can be used include secure socket layer (SSL), Internet Protocol Security (IP SEC), Extensible Authentication Protocol (EAP-*), Hypertext Transfer Protocol Authentication (HTTP Auth), Kerberos, Simple Authentication and Security Layer (SASL), Web Service Security (WS-Security), etc. Examples of confidentiality schemes that can be used include encryption or cryptographic algorithms such as DES/3DES, SHA-1/2, AES, etc. Accordingly, transaction-to-authentication-and-confidentiality-schemes mapping database 84 may provide a mapping of which types of transactions and particular transaction applications require which authentication and confidentiality schemes. One example database mapping could be a banking application's related data and other sensitive information mapped to a desired encryption mechanism. Furthermore, in certain implementations, the criticality of the communication may dictate the applicable authentication method (e.g., different types of authentication may be required for highly sensitive transaction applications). In some embodiments,mapping database 84 may also indicate which types of transactions and particular transaction applications require multi-factor authentication to be performed for an associated agent. - In scenarios in which multi-factor authentication is required for an agent, authentication and
secure transaction module 72 may also access agents-to-multi-factor-authentication mapping database 83. For example, ahuman agent 94 accessing benign features such as gaming, video, and the like may require a simple user name and password during the initial authentication toOBU 30. However, once thehuman agent 94 decides to access a banking transaction application, additional authentication (e.g., physical presence in the form of biometric authentication, etc.) may be required. In another example, highly critical functions such as software/firmware changes by a manufacturer, or emergency services by an emergency service provider, may require multiple layers of authentication by the manufacturer or emergency services provider. These multiple layers of authentication could be satisfied by the agent in the initial authentication toOBU 30, or additional required layers may need to be satisfied when the agent initiates access to the particular transaction application requiring the additional authentication. - Secure database/
storage layer 80 may also provide an agentidentity profiles database 81, for storing identity profiles 34 provisioned locally (e.g., using a transportable memory element to download an identity profile, creating an identity profile directly through OBU 30) or remotely (e.g., downloading an identity profile from identity service provider 60). In addition, agentidentity profiles database 81 may also include security keys, certificates, and credentials corresponding to various transaction applications and agents. -
Secure communication module 77 ofOBU 30 may enable secure communication to various networks (e.g.,networks 40 as shown inFIGS. 1-3 ).Secure communication module 77 selects secure and authenticated network access for an agent and associated transaction application. In addition,secure communication module 77 may also provide opportunistic selection of a VSIM available to the agent, when multiple VSIMs are available for use. VSIMselection rules database 85 may be configured to provide a pre-specified mapping of rules that represent preferences regarding which single VSIM, multiple VSIMs, and/or other wireless communication option (e.g., WiFi) to select for network access. In one embodiment, rules may include combinations of an agent, a transaction application (or type of transaction), and/or a geographical location of the vehicle mapped to a VSIM or other wireless communication. Examples of such rule combinations include agent and transaction application, agent and location, or agent, transaction application, and location. For illustration purposes, if an agent and transaction application combination is mapped to a VSIM, then the VSIM will be used when the agent and transaction application are associated with a network access request, regardless of where the vehicle is physically located. If an agent and location combination is mapped to a VSIM, then the VSIM will be used if the vehicle is physically located in the mapped location and if the agent is associated with the network access request, regardless of which particular transaction application is associated with the network access request. - Multiple VSIMs and/or other wireless communication options can also be mapped to transaction applications or types of transactions, agents, and/or geographical locations to allow a network connection to be split among the designated multiple VSIMs and/or other wireless communication options. In one example scenario, a large file download may utilize multiple VSIMs (e.g., two different 3G mobile networks) in order to split the file to increase the speed of the download. To accomplish this, a transaction application and agent associated with the file download may be mapped to two or more VSIMs provisioned in
OBU 30 for the agent. - In certain scenarios, one VSIM may be preferred over another VSIM due to the vehicle location because of the mobile network operator rate. To illustrate this case, assume Agent X and California are mapped to
VSIM 1 and Agent X and New York are mapped toVSIM 2. If Agent X is traveling in California, then VSIM 1 will be used for any network access requested by Agent X. If Agent X is traveling in New York, then VSIM 2 will be used for any network access requested by Agent X. In another scenario, ahuman agent 94 may prefer to have particular types of transactions tied to different VSIMs or combinations of VSIMs (e.g., home transactions mapped toVSIM 1, work related transactions mapped toVSIM 2, child's transactions mapped to VSIM 1). Such mappings can be configured in VSIM selectionrules mapping database 85 with appropriate authorization. The VSIM selection rules mapping could also be provided in any other suitable memory element including, for example, an identity profile associated with the agent. In this alternative implementation, only transaction application and/or location may need to be mapped to available VSIMs and/or other wireless communication options. - In addition to pre-specifying VSIM selection rules, VSIMs may also be opportunistically selected in real-time. A real-time VSIM selection may occur based on current network conditions/demands, mobile network rate plan of an agent, remaining data/minutes of a mobile network rate plan. In addition, network performance characteristics such as, for example, data rate, signal level, congestion, etc. may also be evaluated in real-time and used to opportunistically select a suitable one or more VSIMs, other wireless communication options, or any suitable combination thereof.
-
Transaction applications 78 represent a plethora of user-level and system-level transaction applications that may be configured onOBU 30. With proper authentication toOBU 30 and authorization through transaction-to-agents mapping database 82, however, numerous types of transactions usingtransaction applications 78 may be performed throughOBU 30. Generally, types of transactions are inclusive of 1) accessing one or more wireless/mobile/cellular networks and using network bandwidth and services, 2) gaining access to various resources of the vehicle based on an identity profile and/or associated databases, 3) gaining access to applications in the vehicle, and 4) engaging in commercial activities (e.g., paying for receiving goods or services, or receiving payment for selling goods or services). These general transactions may overlap in certain cases, for example, where an agent accesses a cellular network in order to connect to an online retailer (e.g., commercial transaction system 54) in order to pay for purchased goods, and uses an Internet commerce transaction application to enable a secure transaction. - The user-level and system-level transaction applications of
OBU 30 may be mapped to any appropriate agent 90 (e.g.,machine devices 92,humans 94,software agents 95,mobile devices 96, and authorized entities 98) in transaction-to-agents mapping database 82.Example transaction applications 78 can include applications facilitating external network access such as banking applications, LBS applications, travel agency applications, vehicle rental & leasing agency applications, Internet commerce applications, kiosk applications, gas & electric charging applications, transportation charging applications, vehicle-to-vehicle applications, vehicle-to-mobile applications, dealer transaction applications, OEM transaction applications, and the like.Other transaction applications 78 may include hardware and/or software applications involving internal access ofOBU 30 such as gaining access to various resources, vehicle subsystems, or software applications not involving remote network access. A unified identity management framework, as illustrated inFIG. 4 , is capable of aggregation and association of allagents 90 and transaction scenarios into a unified system. In one embodiment, application programming interfaces (APIs) may be exported to integrate these agent identities with various transaction applications. -
Authorized entities 98 may access appropriate transaction applications (e.g., dealer transaction application, OEM transaction application, etc.) after gaining access toOBU 30 through an authenticatedsoftware agent 95. Thesoftware agent 95 may first authenticate toOBU 30 and can then establish a network connection to the authorized entity using an appropriate VSIM (e.g., the manufacturer's VSIM). The authorized entity to which the software agent establishes a network connection may need to authenticate toOBU 30 before being able to access transaction applications onOBU 30, such as transactions applications related to vehicle sensor data, diagnostic data, firmware/software upgrades, emissions data, etc. Thus, for example, an OEM software agent onOBU 30 may be configured to establish a network connection to the OEM whenever internal connectivity to a network is detected onOBU 30. OEM software agent may first authenticate toOBU 30 and, for example,VSIM 1 may be selected for network access. Once a network connection is established betweenOBU 30 and theOEM using VSIM 1, the OEM may update theVSIM 1 toVSIM 2 if, for example, the OEM has negotiated a new rate with a different mobile network provider and wishes to update its VSIM. In some embodiments, a VSIM being updated (e.g., VSIM 1) may need to remain active and available for use by the associated agent for a specified period of time, until the new VSIM (e.g., VSIM 2) has been successfully provisioned (and possibly tested) inOBU 30. Additionally, the OEM may need to be authenticated toOBU 30 and authorized in transaction-to-agents mapping database 82 in order to update the VSIM or to access an OEM transaction application (e.g., one of transaction applications 78), which could be configured to access various vehicle components (e.g., vehicle sensors, vehicle firmware/software, etc.). -
Machine devices 92 may also authenticate toOBU 30 and then provide an automatic network connection to an external entity ortransaction system 50. For example, a machine device agent (e.g., a detector) may sense a toll system and initiate a transportation charging application. After the detector is authenticated toOBU 30, transaction-to-agents mapping database 82 may be evaluated to determine whether the detector is mapped to the transportation charging application. Once the detector is determined to be authorized to access the transportation charging application, network credentials and payment information may be obtained so that transportation charging application can connect to the toll system and provide appropriate payment. - Turning to
FIG. 5 , an example selection of identity profiles that could be provided in an OBU is illustrated. Identity profiles are included for a parent/owner 502, achild 504, avehicle sensor 506, and amanufacturer 508. Common elements in each of the identity profiles include agent identification, VSIM, and security profile. Agent identification could include credentials information such as a key fob for the parent/owner 502, a birth date for thechild 504, a device identifier for thevehicle sensor 506, and a name for themanufacturer 508. The security profile information could also be credentials such as a user name and password for the parent/owner 502 andchild 504, a security key for thevehicle sensor 506, and a PKI certificate for themanufacturer 508. - Identity profiles for human agents, such as parent/
owner 502 andchild 504 may also include vehicle settings, other wireless interfaces, device list, and web accounts. The vehicle settings may include items such as preferred seat positions as a driver and a passenger, temperature controls, music or radio settings, and the like. Other wireless interfaces and preferences may include, for example, a WiFi account established with a mobile network provider. Wireless interface information can be included in the identity profiles so that whenever the vehicle is near a hotspot of the mobile network operator, network connections by the parent/owner or child can be made through the WiFi interface. Identity profiles for the parent/owner 502 andchild 504 may also include specific web accounts, such as those related to social networking and media. - Device lists may include any personal mobile devices of the parent/owner or child. The device list could include network interface accounts, passwords, and network configurations. Thus, the device list is essentially an identity profile for mobile devices within identity profiles of the parent/
owner 502 andchild 504. The device list information is provided to allow each of the identified mobile devices to be recognized and connected to theOBU 30 and to other networks in a desired manner. For example, if the child wants to download a movie from the Internet to a mobile device (e.g., a laptop, iPad, etc.) and the mobile device is included in the device list of the child'sidentity profile 504, then the mobile device could be connected toOBU 30 through a local wireless connection andOBU 30 could route traffic to the Internet through appropriate and available network connections fromOBU 30 to the Internet (e.g., using a VSIM identified in the identity profile of the child 504). Thus,OBU 30 may be used as a communication link to the Internet for mobile devices identified in a device list of an identity profile of another agent. - Identity profile of parent/
owner 502 may also include other profile information of a sensitive nature such as credit/payment information. Credit/payment information may be included in an identity profile to allow the agent of the identity profile to use his own credit/payment information for various charges/payments incurred during commercial transactions (e.g., transportation charging, gas and charging stations, kiosks, Internet commerce, rental and leasing, travel, etc.). The credit/payment information may be associated with authorized transaction applications during provisioning of the identity profile or at other times. By way of example, during the provisioning of an identity profile of an owner ofvehicle 4, the owner's credit/payment information may be set as the default credit/payment method for various transaction applications. In a further example, payment information associated with transaction applications for transportation and gas and charging systems could be changed during a trip invehicle 4 when a passenger offers to use his own credit/payment information to pay for such expenses.OBU 30 could provide an interface to allow modification to appropriate settings to effect such a change using proper authentication and authorization. In another example, each time a driver is authenticated tovehicle 4, the driver's credit/payment information may be associated with the various transportation and gas and charging transaction applications. However, if the driver is not the default payer/creditor, thenOBU 30 could provide confirmation screens to notify the driver that his credit/payment information will be used and to receive confirmation and approval of this change. - Identity profile of parent/
owner 502 may also include machine device access. While a manufacturer or an OEM may have access to vehicle machine devices to read and update or modify firmware or software of such machine devices, an owner of a vehicle may only be allowed to retrieve data from vehicle sensors. Accordingly, machine device access can indicate which machine devices the owner is authorized to access and what type of access is allowed. In addition, other passengers may not be allowed any type of access to the vehicle sensors and actuators, for example, and therefore, machine device access information may be omitted from identity profiles associated with other human agents. - Identity profile of
child 504 may also contain parental controls and may not contain certain information that allows use of particular resources or transactions. Parental controls may be included to allow a parent to set desired limits on a child's use ofOBU 30 resources and the vehicle itself. For example, any type of common computer parental controls related to accessing networks such as the Internet could be provided in parental controls. In addition parental controls could relate to particular activities of the vehicle. For example, if the child is authenticated as a driver, parental controls could require a notification be sent to the parent (e.g., via an email account, a text message, to a messaging center of theOBU 30, etc.) if the vehicle is driven beyond a specified boundary or perimeter or if the vehicle is driven beyond a specified speed. Parental controls could also be configured to limit certain vehicle functions (e.g., vehicle speed, entertainment systems, etc.). In addition, identity profile ofchild 504 may not have credit/payment information if the child is not allowed to engage in commercial transactions throughOBU 30. - Identity profile of
manufacturer 508 may also include machine device access information, which can indicate which machine devices the manufacturer is authorized to access and what type of access is allowed. In addition, the identify profile ofmanufacturer 508 may also include information related to diagnostics ofvehicle 4 and a history of vehicle technical problems. Thus, when the manufacturer accessesvehicle 4, valuable historical information related specifically tovehicle 4 can be readily available for the manufacturer. Web accounts may also be provided in identity profile ofmanufacturer 508. Such information could allow the manufacturer to communicate with the driver/owner and provide information including, for example, marketing information such as coupons or sales events. - Turning to
FIGS. 6 through 15 , simplified flowcharts illustrating various aspects of embodiments of the present disclosure are shown. For ease of reference,FIGS. 6-15 will be described herein with reference to various elements, objects, modules, and components of the present disclosure as provided in precedingFIGS. 1-5 . -
FIG. 6 is a simplifiedagent provisioning flow 600 providing example steps ofagent provisioning module 71 for provisioning an agent toOBU 30, which may be configured as a background process open and running wheneverOBU 30 is booted up.Agent provisioning flow 600 begins atstep 601, waiting for an agent. When an agent attempts to gain access toOBU 30, flow moves to step 602 and an agent is detected. This can occur whenever a new or existing agent initiates a vehicle-based transaction viaOBU 30. For example, when a human 94 (e.g., an owner, a renter, a borrower, etc.) enters a vehicle such asvehicle 4 andOBU 30 is powered on (e.g., by using a key fob to enter the vehicle, by starting the vehicle or otherwise providing power to OBU 30).Agent provisioning flow 600 may also occur when amobile device 96 is powered on withinvehicle 4, when asoftware agent 95 is initiated, when amachine device 92 is activated (e.g., by powering on vehicle 4) or attempts to access resources or transaction applications of OBU 30 (e.g., vehicle sensor or actuator sending data or information toOBU 30, detector initiating a transportation transaction application after detecting proximity to a toll system), when an authorizedentity 98 attempts to access OBU 30 (e.g., after acorresponding software agent 95 has established network access to the authorizedentity 98 from OBU 30). Furthermore, agent provisioning may also occur when a human agent provisions another agent (e.g., machine device, software agent, mobile device, authorized entity), typically for the first time. - Once an agent has been detected in
step 602, flow passes to step 604 to perform authentication of the agent to the vehicle, which will be described in more detail with reference toFIGS. 7-10 . During the authentication, VSIMs and/or an identity profile may be provisioned for the agent if the agent is properly authenticated. Flow then passes todecision box 606 where a determination is made as to whether the agent was properly authenticated to the vehicle. If the agent was not properly authenticated then flow passes back to step 601 to wait for another agent. If the agent was properly authenticated as determined indecision box 606, however, then flow passes todecision box 608 to determine whether an identity profile is provisioned for the agent. If the agent has a corresponding identity profile, then flow passes to step 610 to activate the identity profile, including determining agent priority and role in the vehicle, adjusting vehicle settings, configuring agent preferences, and the like, which will be further described herein with reference toFIG. 11 . - After the identity profile is activated in
step 610, or if the agent does not have a corresponding identity profile inOBU 30, then flow passes todecision box 612 to determine whether the agent has an associated payment method (e.g., payment method information in identity profile, VSIM that can be used for payment). If the agent has an associated payment method, then flow passes to step 614 to invoke payment association module, which will be further described with reference toFIG. 12 . After the payment association processing is completed in step 614, or if the agent does not have an associated payment method as determined indecision box 612, then flow passes back to step 601 to wait for another agent. Certain agents (e.g., vehicle machines such as a brake sensor or a seat actuator, a human agent without payment information in an identity profile, etc.) may not have associated payment methods because these agents may not engage in commercial transactions throughOBU 30 and, therefore, may not interact with transaction applications requiring payments. -
FIG. 7 is a simplified authentication tovehicle flow 700, which may be performed atstep 604 ofFIG. 6 and which illustrates example steps for authenticating an agent to the vehicle. Authentication tovehicle flow 700 begins atstep 702 where a determination is made as to whether the detected agent is a new agent. “New agent” refers to an agent that does not have any authentication credentials, profile information, or VSIMs currently provisioned inOBU 30. New human agents could include, for example, a new owner, rental or lease driver, borrower, or passenger who has not previously been provisioned on the vehicle. Other types of new agents include, for example, a new mobile device attempting to access a local network ofOBU 30, a new machine device (e.g., sensor, actuator, etc.) added to the vehicle, or a new software agent installed on OBU (e.g., a new dealership adds a software agent to automatically initiate connection with the dealership). - In one embodiment, agent identity of a human can be inferred from a key fob used by the human agent to enter the vehicle. In certain embodiments, when a driver enters a vehicle,
display 28 can prompt the driver to confirm that his identity matches the displayed owner identity (or provisioned default driver) of the vehicle. If other identities of human agents have been provisioned in the vehicle, then the display could also provide a list of provisioned identities from which the agent can choose to authenticate.Display 28 could also provide the option to select “New Driver”, “New Passenger”, or the like. - If the agent is determined to be a new agent in
decision box 702, then flow may pass todecision box 720 where a query is made as to whether policies allow a new agent to be provisioned. In some embodiments,OBU 30 may include a policy module that allows various policy controls, including new agent provisioning. Thus, for example, for an added layer of security, an owner may set policies that by default block any new agents from being added toOBU 30. Thus, whenever a new agent needs to be added, the owner would have to reset or override the policy with credentials to allow the new agent to be provisioned. Such policy settings can be controlled through a policy settings interface by an appropriate agent (e.g., the owner or other superagent with a specified high level of authority for conducting transactions and configuring policies in OBU 30). If the policies do not allow new agents as determined indecision box 720, then authentication tovehicle flow 700 ends and flow returns toagent provisioning flow 600 with the agent not authenticated. - If policies allow new agents to be provisioned as determined in
decision box 720, however, then flow passes todecision box 722 where a determination is made as to whether VSIM provisioning is requested. In the case of a human agent, a display screen may offer the choice to the agent to provision a VSIM. If VSIM provisioning is requested, then flow passes to step 724 to perform VSIM provisioning, which will be further described with reference toFIGS. 9A and 9B . VSIM provisioning allows an agent to create or update one or more VSIMs with an identity service provider (e.g., third party identity service provider accessible through the Internet), and/or to download one or more VSIMs (e.g., from the identity service provider, from a transportable storage medium, from a mobile device) toOBU 30. - After the one or more VSIMs are provisioned in
step 724, or if VSIM provisioning was not requested, flow passes todecision box 726 to determine whether identity profile provisioning is requested. In the case of a human agent, a display screen may offer the choice to the agent to provision an identity profile. If identity profile provisioning is requested, then flow passes to step 728 to perform identity profile provisioning, which will be further described herein with reference toFIGS. 10A and 10B . Identity profile provisioning allows an agent to create or update an identity profile through an identity service provider (e.g., third party identity service provider accessible through the Internet) or directly ontoOBU 30. If an identity profile is created or updated through an identity service provider, or if an identity profile is stored on transportable storage medium or mobile device, then the identity profile can be downloaded toOBU 30. - After the identity profile is provisioned in
step 728, or if identity profile provisioning was not requested, flow passes to step 730, where one or more authentication factors or requirements may be provisioned for the new agent in agents-to-multi-factor-authentication mapping database 83. Such factors could include user ID and password, biometrics, key fob, access card, etc., and one or more of these factors could be obtained by accessing the agent's identity profile credentials. For example, if an identity was provisioned and includes a user ID and password, the agent could be prompted to confirm that the user ID and password from the identity profile should be included as one of the authentication factors. After the authentication factors are provisioned instep 730, flow returns toagent provisioning flow 600 ofFIG. 6 . - Referring again to
decision box 702, if the detected agent is determined to be an existing agent (e.g., with authentication credentials, VSIMs, identity profile), then flow passes to step 704 to perform multi-factor authentication, which will be described in more detail herein with reference toFIG. 8 . Multi-factor authentication requires the detected agent to authenticate himself using one or more factors provided in agents-to-multi-factor-authentication mapping database 83. After the multi-factor authentication is performed, flow passes todecision box 706 to determine whether the detected agent passed the required multi-factor authentication. If the agent did not pass, then authentication tovehicle flow 700 flow ends and returns toagent provisioning flow 600 without the detected agent being authenticated. - If in
decision box 706, it is determined that the detected agent passed the multi-factor authentication, however, then flow passes tosteps 710 through 718. These steps essentially perform the same function assteps 722 through 728 with regard to VSIM and identity profile provisioning. Thus, the existing, authenticated agent is allowed to provision (by creating or updating) one or more VSIMs and/or an identity profile and to download such data toOBU 30. - Turning to
FIG. 8 , amulti-factor authentication flow 800 is shown, which may be invoked instep 704 ofFIG. 7 , to authenticate the agent to accessOBU 30.Multi-factor authentication flow 800 may also be used to authenticate the agent when the agent is attempting to conduct particular transactions throughOBU 30, which will be further described herein with reference toFIG. 13 . Flow begins atstep 802 where agents-to-multi-factor-authentication mapping database 83 is evaluated. In one embodiment, the agent can be mapped to one or more authentication requirements necessary for authenticating toOBU 30. Moreover, each agent provisioned inOBU 30 could have various required authentication requirements and various numbers of such requirements. For example, an owner having significant privileges and access toOBU 30 and its resources may have several authentication requirements, whereas a passenger in the vehicle with limited access toOBU 30 and its resources may only need to provide a user ID and password. Flow moves to step 804 to get a first authentication requirement frommapping database 83. In one embodiment, a key fob used to open a door for a human agent could be the first authentication requirement for a driver or owner of the vehicle. - Flow then passes to
decision box 806 where a determination is made as to whether the agent passes the authentication requirement (e.g., entering a correct user ID and password, providing a matching fingerprint, providing a valid PKI certificate, etc.). If the agent passes the authentication requirement, then flow moves todecision box 810 where a determination is made as to whether more authentication requirements are identified in agents-to-multi-factor-authentication mapping database 83. If additional requirements are necessary to authenticate the agent, flow passes to step 812 to identify the next requirement, and then passes back todecision box 806 to repeat the steps determining whether the agent passes the authentication requirement. This processing continues until the agent has passed all of the authentication requirements or until the agent fails one of the authentication requirements. If the agent passes all of the authentication requirements, then the agent is authenticated to the vehicle, as indicated instep 814, andmulti-factor authentication flow 800 ends. If, however, the agent fails one of the authentication requirements, then the agent is not authenticated to the vehicle, as indicated instep 808, and themulti-factor authentication flow 800 ends. - Turning to
FIGS. 9A and 9B , simplified flowcharts of aVSIM provisioning flow 900A and an identity serviceprovider access flow 900B, respectively, are illustrated.VSIM provisioning flow 900A may represent at least a portion of the flow ofVSIM provisioning module 73 ofOBU 30. In one embodiment, flow 900A can be invoked during authentication tovehicle flow 700 and also at any time during which an agent is authenticated toOBU 30. - Flow begins at
step 906 where an available communication link is identified. Various communication links may be used to provision a VSIM, including some form of wireless communication (e.g., WiFi, WiMax, 3G, 4G, white space, 802.11x, satellite, etc.) to connect toidentity service provider 60, a local network within vehicle 4 (e.g., local WiFi, Bluetooth, Ethernet, etc.) to connect to a mobile device, or a direct connection to a transportable medium (e.g., USB, CD, etc.). Flow passes todecision box 908 to determine whether the identified link is for local provisioning. If the identified communication link is not for local provisioning, then flow passes to step 910 to accessidentity service provider 60 via an available network. Example processing ofidentity service provider 60 will be described in more detail herein with reference toFIG. 9B . - When a network connection has been established to
identity service provider 60 instep 910, or if the available communication link was identified for local provisioning, flow passes todecision box 912. In decision box 912 a determination is made with regard to what VSIM action to perform. If a VSIM is to be removed fromOBU 30, then flow passes to step 914 to remove the VSIM. If a VSIM onOBU 30 is to be updated, then flow passes to step 918 to download a VSIM using the identified communication link (e.g., fromidentity service provider 60, from a transportable storage medium directly connected toOBU 30, from a mobile device) to update an existing VSIM. Finally, if a new VSIM is to be added toOBU 30, flow passes to step 916 to download the new VSIM using the identified communication link (e.g., fromidentity service provider 60, from a transportable storage medium directly connected toOBU 30, from a mobile device). Once the desired action (i.e., remove, update, or add) has been performed, flow passes todecision box 920 to determine whether more VSIM actions are to be performed. If more VSIM actions are to be performed, then flow passes back todecision box 912 to repeat the determination of whether to remove, update, or add a VSIM and to perform the desired action accordingly. This processing may continue until all VSIM actions have been completed. In one embodiment, an agent may be associated with multiple VSIMs provisioned inOBU 30. Therefore, multiple VSIM actions may occur during a single VSIM provisioning process. - Turning to
FIG. 9B , a simplified flowchart illustrates possible processing steps ofidentity service provider 60 providing identity services for managing VSIMs, including accessing and downloading VSIMs to connected vehicles. As previously described herein, VSIMs may be managed and stored byidentity service provider 60 in a memory element such asVSIM database 64.Flow 900B will be described with reference to a user, which includes a human provisioning the VSIM for any type of agent (e.g., software agent, machine device, authorized entity, human agent), including provisioning the VSIM for himself as a human agent. Flow could start atdecision box 922, where a determination is made as to whether the user accessingidentity service provider 60 has been authenticated to the identity service provider. For example, the user may log on to an account created withidentity service provider 60. If the user is not authenticated, then flow ends. Although not shown inFIG. 9B , the user could potentially create a new account withidentity service provider 60. - If the user is authenticated to
identity service provider 60, then flow passes todecision box 924 to determine whether there is a VSIM action to perform. If, for example, a VSIM was previously created by the user (e.g., a user on a computer or mobile device creating a VSIM through identity service provider 60), then the user may simply need to access and download the existing VSIM toOBU 30. However, if the user needs to create, update, and/or remove a VSIM, then flow passes todecision box 926 to determine whether to add a new VSIM toOBU 30. If a request is made to add a new VSIM (e.g., to VSIM database 64), then flow passes to step 928 to add the new VSIM. If adding a new VSIM is not requested, as determined indecision box 926, then flow passes todecision box 930 to determine whether a request was made to update an existing VSIM. If an update request was made, then flow passes to step 932 where an existing VSIM is updated. If an update request is not made, as determined indecision box 930, however, then flow passes to step 934 where an identified VSIM is removed. - After a VSIM is either added (step 928), updated (step 932), or removed (step 934), flow passes to
decision box 936 where it is determined whether there are more VSIM actions to perform. If more VSIM actions are requested, then flow passes back todecision box 926 andsteps 926 through 936 continue to be processed until no more VSIM actions are requested. Once no more VSIM actions are requested, or after it is determined that there are no VSIM actions to perform, then the connection toidentity service provider 60 fromOBU 30 may continue until one or more VSIMs are downloaded toOBU 30. In addition, it will be apparent thatflow 900B may also occur when a user establishes a network connection toidentity service provider 60 from a remote computer or mobile device to manage his associated VSIMs. - Turning to
FIGS. 10A and 10B simplified flowcharts of an identityprofile provisioning flow 1000A and another identity serviceprovider access flow 1000B, respectively, are illustrated. Identityprofile provisioning flow 1000A may represent at least a portion of the flow of identityprofile provisioning module 75 ofOBU 30. In one embodiment, flow 1000A can be invoked during authentication tovehicle flow 700 and also at any time during which an agent is authenticated toOBU 30. - Flow begins at
decision box 1002 where a determination is made as to whether an agent is locally creating an identity profile. In one embodiment, an agent can manually create an identity profile onOBU 30 by entering profile information directly intoOBU 30 through an appropriate user interface. If the agent is locally creating an identity profile, then flow passes to step 1004 where the agent is permitted to manually create an identity profile, and then flow ends. - If it is determined that the agent is not locally creating an identity profile, then flow passes to step 1006 where an available communication link is identified. Various communication links may be used to provision a identity profile, including some form of wireless communication (e.g., WiFi, WiMax, 3G, 4G, white space, 802.11x, satellite, etc.) to connect to
identity service provider 60, a local network within vehicle 4 (e.g., local WiFi, Bluetooth, Ethernet, etc.) to connect to a mobile device, or a direct connection to a transportable medium (e.g., USB, CD, etc.). If the identified communication link is not for local provisioning, then flow passes to step 1010 to accessidentity service provider 60 via an available network. Example processing ofidentity service provider 60 will be described herein in more detail with reference toFIG. 10B . - When a network connection has been established to
identity service provider 60 instep 1010, or if the available communication link was identified for local provisioning, flow passes todecision box 1012. In decision box 1012 a determination is made with regard to what identity profile action to perform. If an identity profile is to be removed fromOBU 30, then flow passes to step 1014 to remove the identity profile. If a identity profile onOBU 30 is to be updated, then flow passes to step 1018 to download a identity profile using the identified communication link (e.g., fromidentity service provider 60, from a transportable storage medium directly connected toOBU 30, or from a mobile device) to update an existing identity profile. Finally, if a new identity profile is to be added toOBU 30, flow passes to step 1016 to download the new identity profile using the identified communication link (e.g., fromidentity service provider 60, from a transportable storage medium directly connected toOBU 30, or from a mobile device). Once the desired action (i.e., remove, update, or add) has been performed, flow passes todecision box 1020 to determine whether more identity profile actions are to be performed. If more identity profile actions are to be performed, then flow passes back todecision box 1012 to repeat the determination of whether to remove, update, or add a identity profile and to perform the desired action accordingly. This processing may continue until all identity profile actions have been completed. - Turning to
FIG. 10B , a simplified flowchart illustrates possible processing steps ofidentity service provider 60 providing identity services for managing identity profiles, including accessing and downloading identity profiles to connected vehicles. As previously described herein, identity profiles may be managed and stored byidentity service provider 60 in a memory element such as identityprofile memory element 62.Flow 1000B will be described with reference to a user, which includes a human provisioning the identity profile for any type of agent (e.g., software agent, machine device, authorized entity, human agent), including provisioning the identity profile for himself as a human agent. Flow could start atdecision box 1022, where a determination is made as to whether the agent accessingidentity service provider 60 has been authenticated to the identity service provider. For example, the user may log on to an account created withidentity service provider 60. If the user is not authenticated, then flow ends. Although not shown inFIG. 10B , the user could potentially create a new account withidentity service provider 60. - If the user is authenticated to
identity service provider 60, then flow passes todecision box 1024 to determine whether there is an identity profile action to perform. If, for example, an identity profile was previously created by the user (e.g., a user on a computer or mobile device creating an identity profile through identity service provider 60), then the user may simply need to access and download the existing identity profile toOBU 30. However, if the user needs to create, update, and/or remove an identity profile, then flow passes todecision box 1026 to determine whether to add a new identity profile toOBU 30. If a request is made to add a new identity profile (e.g., to identity profile database 64), then flow passes to step 1028 to add the new identity profile. If adding a new identity profile is not requested, as determined indecision box 1026, then flow passes todecision box 1030 to determine whether a request was made to update an existing identity profile. If an update request was made, then flow passes to step 1032 where an existing identity profile is updated. If an update request is not made, as determined indecision box 1030, however, then flow passes to step 1034 where an identified identity profile is removed. - After an identity profile is either added (step 1028), updated (step 1032), or removed (step 1034), flow passes to
decision box 1036 where it is determined whether there are more identity profile actions to perform. If more identity profile actions are requested, then flow passes back todecision box 1026 andsteps 1026 through 1036 continue to be processed until no more identity profile actions are requested. Once no more identity profile actions are requested, or after it is determined that there are no identity profile actions to perform, then the connection toidentity service provider 60 fromOBU 30 may continue until one or more identity profiles are downloaded toOBU 30. In addition, it will be apparent thatflow 1000B may also occur when a user establishes a network connection toidentity service provider 60 from a remote computer or mobile device to manage his identity profiles. -
FIG. 11 illustrates a simplified flowchart of example steps for activating an identity profile, as indicated instep 610 ofFIG. 6 , after the identity profile has been provisioned inOBU 30 and an associated agent has been authenticated toOBU 30. For example, flow may begin indecision box 1102 where a determination is made regarding whether any control/access limitations have been set by one agent that apply to another agent. Typically, an owner of the vehicle or other superagent will have authority to set such controls/access limitations by configuring policies through an appropriate policy module. Such controls/access limitations may include, for example, parental controls set by a parent of a child (e.g., restrictions on certain web content, media features, any transactions involving credit cards or payments, vehicle functions, etc.). If control/access limitations exist, then flow passes to step 1104 to apply such control/access limitations to the identity profile of the agent. - After the limitations are applied, or if no limitations exist for the agent, then flow may pass to step 1105 to determine the role and priority of the agent in the vehicle. For human agents, role can be determined based on which seat of the vehicle the agent occupies (e.g., driver seat, front passenger seat, rear left passenger seat, rear right passenger seat, etc.). Once the role and priority of the agent are determined, flow passes to step 1106 to configure the vehicle settings based on the agent's role in the vehicle. Depending on the role of the agent,
OBU 30 may communicate the agent's identity profile parameters corresponding to actuators and software applications of the particular seat occupied by the agent. For example, seat positioning, air temperature settings, seat heater/cooler, dashboard features, and the like may be configured for the agent if the agent is the driver. If the agent is a passenger, however, the seat positioning, seat heater/cooler, and temperature settings may be applied to the agent's particular passenger seat, if such settings are available for the passenger seat. - Once the vehicle settings are applied in
step 1106, flow may pass to step 1108 to configure other identity profile parameters based on an agent's priority. Depending on the agent's priority, OBU may communicate the agent's identity profile parameters corresponding to any appropriate actuators, software applications, and the like related to agent preferences (e.g., radio channel list, phonebook, address book, GPS favorite locations, etc.). For purposes of illustration, it is assumed that a driver has highest priority and driver preferences will override any conflicting passenger preferences. It should be understood, however, that a passenger could be configured with a higher priority and override the driver's preferences for preferences not pertaining to the safety of the vehicle. Additionally,OBU 30 may also configure network interface accounts and network configurations for other mobile devices identified in the agent's identity profile (e.g., in a device list). Moreover, while examples have been provided for human agents, activating an identity profile of other types of agents authenticated to the OBU may also occur for any appropriate identity profile parameters in an authenticated agent's identity profile. -
FIG. 12 illustrates a simplified flowchart of example steps ofpayment association module 79, for associating a payment method to certain transaction applications that are not associated with or initiated by an agent that has an associated payment method (e.g., payment information in identity profile, VSIM). For example, if a toll payment transaction application is configured to pay tolls automatically, then a payment method needs to be associated with the toll payment transaction application. The payment method could be payment information such as a credit card or bank account from an agent's identity profile, or a VSIM to be used as payment on a back end of the corresponding mobile network operator. In addition, over the life of the vehicle, changes to the payment methods associated with such transaction applications may be desired (e.g., each driver of a vehicle owned by a rental car agency may be required to pay their own tolls, a new owner will need to associate a new payment method with such vehicle transaction applications, an owner of a vehicle may have a credit card or banking account change that needs to be updated., someone borrowing a car or sharing trip expenses may want to pay for all certain transactions through a payment method provided in their identity profile, etc.) - Generally,
payment association flow 1200 ofFIG. 12 represents both automatic and manual payment association to transaction applications.Flow 1200 may be invoked when an agent is being provisioned, as indicated in step 614 ofFIG. 6 , or at any time during which an agent is authenticated to the vehicle. In the scenario in which the agent is being provisioned,flow 1200 may occur automatically and, depending on the role and priority of the agent, may automatically associate the agent's payment methods to the identified one or more transactions. In another scenario in which the agent has already been provisioned and authenticated to the vehicle, then flow 1200 may be invoked by the agent through an appropriate user interface ofOBU 30 in which the agent may individually or collectively identify which transaction applications to associate with which payment methods. - Flow begins in
step 1202 where a transaction application is identified. The identified transaction application may be an application that is not associated with or initiated by an agent that has an associated payment method. Flow then passes todecision box 1204 where a determination is made as to whether the agent attempting to make the payment association is authorized to change payment association for the identified transaction application (e.g., if the agent is being provisioned but is not the driver then the agent may not be authorized, if policies do not allow the agent to change payment associations then the agent will not be authorized, etc.). If the agent is not authorized as determined indecision box 1204, then flow 1200 ends and payment associations are not made. - If is determined in
decision box 1204 that the agent is authorized to change payment association for the identified transaction application, then flow passes to step 1206. In step 1206 a new payment method is identified from the agent's identity profile payment information or from the agent's corresponding VSIM. The agent's identity profile payment information may include information for a credit card, a debit card, a bank account, or other payment service providers. Alternatively, a VSIM associated with the agent could be used to provide payment. The VSIM could be used to connect to the associated mobile network operator, the payment could be received from the mobile network operator, and then the mobile network operator could bill the agent on the back end (e.g., with a set periodic or stand-alone bill to the agent). In a manual process of payment association, the agent can simply be provided with suitable options to select a desired payment method from options associated with the agent. In the automatic payment association, however, priority of available payment options can be pre-specified in any suitable way (e.g., an indication provided in the identity profile, etc.). - Once the payment method is determined in
step 1206, flow passes to step 1208 to associate the selected payment method to the identified transaction application. In one embodiment, a separate mapping database may be provided to map identified transaction applications to selected payment methods. In another embodiment, an existing mapping database, such as transaction-to-agents mapping database 82, may be used and may include any suitable mechanism (e.g., pointer, link list, additional field, etc.) to indicate which agent to select to retrieve an associated payment method for the transaction application. - After the selected payment method is associated to the identified transaction application, flow passes to
decision box 1210 to determine whether another transaction application has been identified. If another transaction application has been identified (e.g., parking transaction application), then flow passes back todecision box 1204 to process the newly identified transaction application.Steps 1204 through 1210 can be repeated until no more transaction applications are identified, and flow ends. - Turning to
FIGS. 13 and 14 , simplified flowcharts with an authentication andsecure transaction flow 1300 and an identityprofile access flow 1400 are illustrated. Authentication andsecure transaction flow 1300 may be configured as a background process open and running wheneverOBU 30 is booted up. Flow starts atstep 1301 where the process waits for an event for a transaction, which could have a trigger associated with an agent to initiate the transaction. Triggers could include, for example, a human agent attempting to initiate a transaction (e.g., by pressing a button or otherwise issuing commands through any suitable user interface ondisplay 28, by using a mobile device to access OBU 30), a machine device receiving or transmitting a signal (e.g., a detector receiving a signal from a toll system, a detector receiving a signal from a parking system, a sensor in the vehicle sending a signal toOBU 30, etc.), a software agent attempting to execute (e.g., requesting network credentials to automatically connect to an authorized entity, etc.), or an authorized entity attempting to access OBU 30 (e.g., authorized entity connected to the vehicle and attempting to access transaction applications on the vehicle, etc.). - When an event occurs, the event is detected in
step 1302 and then flow moves to step 1304 to evaluate transaction-to-agents mapping database 82. Indecision box 1306, a determination is made as to whether the transaction is authorized. If themapping database 82 does not indicate the transaction is authorized (e.g., the agent is not mapped to a transaction application corresponding to the transaction), then flow passes to 1307 where the transaction is blocked. Flow then passes back to step 1301 to wait for another event. - If transaction-to-
agents mapping database 82 indicates the transaction is authorized (e.g., the agent is mapped to a transaction application corresponding to the transaction), as determined indecision box 1306, then flow may pass to step 1308 to identify authentication and confidentiality schemes by evaluating transaction-to-authentication/confidentiality-schemes mapping database 84.Mapping database 84 may include which transactions require authentication of the associated agent. Although the agent should already be provisioned and authenticated to the vehicle when transaction processing occurs, some transactions may be of a sensitive nature, and authentication must be provided again. In addition, in one embodiment, initial authentication to the vehicle may be provided with a single authentication requirement, whereas authentication to conduct certain transactions may require multiple authentication requirements as indicated in agent-to-multi-factor-authentication mapping database 83 and transaction-to-authentication-and-confidentiality-schemes mapping database 84. For example, access to a banking transaction application that facilitates transactions to personal bank accounts of agents, may require re-authenticating the agent with multiple authentication requirements (e.g., biometrics in addition to a key fob used to initially authenticate to OBU 30). In addition,mapping database 84 may also indicate other authentication and confidentiality schemes to be used by a transaction application such as, for example, a particular encryption mechanism for data associated with the transaction application. Additionally, any authentication protocols required for establishing network connections may also be provided inmapping database 84. - After authentication and confidentiality schemes are identified in
step 1308, flow passes todecision box 1309 to determine whether agent authentication is required for the transaction. In one embodiment, if authentication is required, thenmultifactor authentication module 74 may be invoked in step 1310, as previously discussed herein with reference toFIG. 8 . If multi-factor authentication is required, the agent could be mapped to one or more of the same or different authentication requirements used during the initial authentication of the agent toOBU 30. Thus,multi-factor authentication flow 800 could be configured to distinguish between initial authentication of an agent toOBU 30 and authentication of an agent for particular transactions. If the agent does not pass authentication as determined indecision box 1312, then flow passes to step 1313 where the transaction is blocked. Flow then passes back to step 1301 to wait for another event. - If the agent passes authentication, as determined in
decision box 1312, or if authentication of the agent was not required, as determined indecision box 1309, then flow passes to step 1316 in which the identity profile may be accessed to obtain network credentials and any other needed profile information such as payment information for commercial transactions. Accessing the identity profile will be described in more detail herein with reference toFIG. 14 . After the network credentials and any needed profile information are provided to the transaction application instep 1316, flow passes to step 1318 to allow the transaction. Flow then returns to step 1301 to wait for another event. Although transactions can be processed bytransaction processing flow 1300 sequentially, it will be apparent thattransaction processing flow 1300 is intended to initiate each time an event is detected, which can occur simultaneously with other events. Thus, multiple transactions may be occurring onOBU 30 simultaneously. - Turning now to
FIG. 14 ,FIG. 14 illustrates a simplified flowchart of an accessidentity profile flow 1400, which may occur instep 1316 ofFIG. 13 .Flow 1400 includesstep 1402 where application programming interfaces (APIs) are exposed to a transaction application corresponding to the transaction to enable the transaction application to securely access relevant parts of the identity profile. APIs may be provided to export parts of the identity profile to the transaction application to the extent that the transaction application is authorized to access the profile information. (e.g., credit/payment information, social media web accounts, etc.) - Flow then moves to step 1404 to determine the identity of the agent to be used to provide network credentials and/or other profile information such as payment information. In a simple case, a human agent who initiates a commercial transaction by triggering an Internet commerce transaction application on
OBU 30 may have an identity profile that can be used to obtain network credentials and payment information. In other transaction scenarios, however, the agent associated with the event may not have payment information and/or network credentials. Therefore, the determination instep 1404 accommodates certain transaction applications that need profile information from an agent other than the agent associated transaction. For example, a driver or other passenger may want to pay for toll transactions that occur automatically when a detector (agent) senses the toll system and initiates a toll transaction application. Therefore, the identity of the particular agent with the payment information needs to be determined. This can be accomplished in various ways including, for example, a display screen offering a human agent the option to pay the toll using identity profile information. Alternatively, a human agent could preconfigure the payment information through, for example,payment association module 79. - Once the determination is made in
step 1404, flow passes todecision box 1408 to determine whether the identity profile of the agent is needed. In some transaction scenarios, network credentials for remote network access (e.g., VSIM, WiFi, etc.) may not be required for a transaction application. For example, a transaction application merely accessing in-vehicle networks and having no commercial component may not need any identity profile information. In this case, flow passes to step 1410 to get network credentials for in-vehicle networks, if the transaction application accesses an in-vehicle network. Flow then passes to step 1420 to provide the in-vehicle network credentials to the transaction application, if needed. - If the identity profile is needed for a transaction application requiring remote network access or a transaction application occurring internally (e.g., not requiring remote network access), as determined in
decision box 1408, then flow passes to step 1412. Instep 1412, network credentials are obtained from identity profile, if needed. Flow may then pass to step 1414 to perform opportunistic selection of VSIM, if needed, which will be further described herein with reference toFIG. 15 . Opportunistic selection of VSIM may be needed if VSIM selection rules apply to the particular agent, the transaction application, and/or vehicle geographical location.Steps - After the VSIM is selected, then flow passes to
decision box 1416 to determine whether other profile information is needed from the agent's identity profile. Other information includes, for example, payment information, which could be necessary if the transaction application has a commercial component. If other profile information is needed, then flow passes to step 1418 to get the other profile information and provide such information to the transaction application. Finally, after the profile information is provided to the transaction application instep 1418, or if other profile information is not needed as determined indecision box 1416, flow passes to step 1420 to provide any obtained network credentials, including the VSIM, to the transaction application. -
FIG. 15 is a simplified flowchart of an opportunisticVSIM selection flow 1500. Because a vehicle may at any given time use multiple VSIMs, the VSIMs may be opportunistically selected for better connectivity, for different traffic and application types, for different locations, and for a better user experience. In one embodiment, opportunisticVSIM selection flow 1500 dynamically evaluates VSIMselection rules database 85 to determine whether a particular VSIM selected for connectivity is the preferred VSIM for a particular set of criteria (e.g., agent identity, location of the vehicle, transaction application). If the set of criteria is mapped to a different VSIM than a currently selected VSIM, then the VSIM can be dynamically changed to accommodate the agent or vehicle owner's preferences. OpportunisticVSIM selection flow 1500 may occur when a transaction has been initiated and a corresponding transaction application is waiting for network credentials, or during an established network connection associated with a transaction application. AlthoughFIG. 15 is described with reference to opportunistically selecting a VSIM, it will be appreciated that other wireless connection options (e.g., WiFi, etc.) may also be opportunistically selected and may be mapped to particular sets of criteria. - Flow may begin in
steps 1504 through 1508 where the set of criteria are determined. Instep 1504 an agent associated with the network access/attempt may be identified. Instep 1506, a transaction application associated with the network access/attempt may be identified. Finally, instep 1508, a current location of the vehicle may determined (e.g., by navigation system 17). Flow then passes to step 1510 where one or more preferred VSIMs are identified from VSIM selectionrules mapping database 85. In decision box 1512 a determination is made as to whether the current VSIM(s), which could include one or more VSIMs, are equivalent to the preferred VSIM(s) identified from VSIM selectionrules mapping database 85. When opportunisticVSIM selection flow 1500 is processing to evaluate an established network connection associated with a transaction application, the current VSIM(s) could be one or more VSIMs currently being used for the established network connection. However, when opportunisticVSIM selection flow 1500 is processing during identityprofile access flow 1400 atstep 1414, then the current VSIM(s) could be one or more VSIMs selected from an identity profile for a transaction application waiting to receive network credentials. If the preferred VSIM(s) are different than the current VSIM(s), then flow passes to step 1514 where the current VSIM(s) are changed to the preferred VSIM(s). In the case of an established network connection, the network connection may be moved to network access links enabled by the preferred VSIM(s). - After the current VSIM(s) are changed to the preferred VSIM(s) in
step 1514, or if the current VSIM(s) are equivalent to the preferred VSIM(s) as determined indecision box 1512, then flow passes to step 1516 to evaluate network conditions. In thenext decision box 1518, a determination is made as to whether any policies override the current VSIM(s) because, in one embodiment, various network conditions and policies related to such network conditions may override a VSIM preference. For example, a VSIM preference based on a particular location, such as a preference for using mobile network operator X in New York because it is more cost effective than using mobile network operator Y, may be overridden if the network conditions of mobile network operator X are not suitable. Similarly, multiple VSIMs, or a VSIM associated with another agent may be selected, depending on network conditions and authorization to use the other agent's network credentials. Thus, if policies based on network conditions override the current VSIM(s), then flow passes to step 1520 where the current VSIM(s) are changed to one or more VSIMs consistent with the policy. After the current VSIM(s) are changed instep 1520, or if policies and network conditions did not require a change to the current VSIM(s) as determined indecision box 1518, flow ends, and the associated transaction application may establish a network connection using the current VSIM(s) or may continue network access with the current VSIM(s), as appropriate. - By using the infrastructure described above, a connected vehicle can opportunistically switch between multiple VSIM identities to allow for multiple identity profiles to be used during the vehicle's lifecycle. Thus, the infrastructure enables multiple agents to source communication from the vehicle. To illustrate these features, an example scenario will now be described of a possible lifecycle of a connected vehicle and identities associated with the connected vehicle.
- In the beginning of the life of a vehicle (e.g., vehicle 4), a manufacturer of the vehicle may provision an OBU (e.g., OBU 30) configured within
vehicle 4 with a physical UICC card that is initialized with an identity associated with the vehicle manufacturer, which can be used for authentication to download soft SIM or VSIM identities issued by mobile network operators. A software agent may also be provisioned inOBU 30 to connect to a desired an identity service provider 60 (e.g., third party identity service provider, mobile network operator, manufacturer identity service provider, etc.) to obtain the VSIM. For example, ifvehicle 4 is manufactured in Japan, then software agent may use the manufacturer VSIM to authenticatevehicle 4 to the identity service provider, and then download a VSIM to be used during quality assurance testing beforevehicle 4 is exported from Japan to an automotive dealer in the United States (U.S.). - After
vehicle 4 is shipped and crosses an international border such as the U.S., the software agent can use manufacturer VSIM identity to download a VSIM of a local mobile network operator (e.g., Verizon, AT&T, T-Mobile, SPRINT, PCS, etc.), by accessing anidentity service provider 60 through which the manufacturer has provisioned VSIMs. This may be desirable for the manufacturer to avoid expensive roaming charges. Thus, the manufacturer may be able to negotiate a better rate (e.g., for a particular area) with different mobile network operators at any time and simply update the associated VSIM onvehicle 4. - When a
consumer purchases vehicle 4 from the automotive dealer and becomes an owner ofvehicle 4, he may provision one or more different VSIMs on the OBU ofvehicle 4 for his own network access. The owner may authenticate to a desiredidentity service provider 60 and download a desired one or more VSIMs to be used for connectivity (e.g., 3G or 4G) by the owner. The owner may also download an identity profile to allow personalization of contacts and various preferences provided in the identity profile, as previously described herein (e.g., personalized contacts, vehicle settings, payment methods, device lists, etc.). The owner may also configure authentication requirements to authenticate to vehicle 4 (e.g., set up as desired via key fob, user ID and password, biometrics, etc.). - If another member of the owner's family drives
vehicle 4, another VSIM may be provisioned. The family member may authenticate to the same or different identity service provider and download his own one or more VSIMs, which could correspond to the same or different mobile network operators. In addition, a separate identity profile for the family member may also be downloaded to allow for personalization of preferences, subject to policies implemented by the owner or other superagent and subject to priorities related to the role of an agent at a particular time (e.g., driver vs. passenger). The family member may also configure authentication requirements, which could be provided in identity profile, in order to authenticate tovehicle 4 each time the family member is in the vehicle as a driver or a passenger. - Finally, if
vehicle 4 is sold, the new owner can download his particular one or more VSIMs and/or identity profile from an appropriate identity service provider, and can create authentication requirements for authenticating to the vehicle. The VSIMs and identity profiles associated with the previous owner, any human agent associated with the previous owner, and any mobile devices may be removed fromOBU 30. However, other identity profiles and VSIMs associated with agents such as authorized entities, machine devices, and software agents may remain onOBU 30, if appropriate. - In certain implementations and numerous examples provided herein,
vehicle 10 is described with reference to an automobile.Communication system 10, however, is not limited to automobiles, but can be applied to a myriad of other types of vehicles (e.g., airplanes, boats, trains, etc.). It will be appreciated that the broad teachings disclosed herein are intended to include any type of vehicle used to move from one location to another location, including vehicles that are not designed to transport humans. - In certain example implementations, at least some portions of enabling secure transactions and flexible identity management activities outlined herein may be implemented in software. This could be inclusive of software provided in
transaction security framework 70 ofOBU 30 and in other modules and elements such assecure communication module 77. These elements and/or modules can cooperate with each other in order to perform the enabling secure transactions and flexible identity management activities as discussed herein. In other embodiments, one or more of these features may be implemented in hardware, provided external to these elements, or consolidated in any appropriate manner. For example, some of the processors associated with the various elements may be removed, or otherwise consolidated such that a single processor and a single memory location are responsible for certain activities. In a general sense, the arrangements depicted inFIGS. 1 , 3 and 4 may be more logical in their representations, whereas a physical architecture may include various permutations, combinations, and/or hybrids of these elements. - Any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’ Furthermore,
OBU 30, and each separate component ofOBU 30, may also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment. - Note that with the numerous examples provided herein, interaction may be described in terms of two, three, four, or more network elements. However, this has been done for purposes of clarity and example only. It should be appreciated that the system can be consolidated in any suitable manner. Along similar design alternatives, any of the illustrated computers, modules, components, and elements of FIGURES lthrough 4 may be combined in various possible configurations, all of which are clearly within the broad scope of this Specification. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that
communication system 10 ofFIGS. 1 through 3 and its teachings are readily scalable and can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings ofcommunication system 10 as potentially applied to a myriad of other architectures. - It is also important to note that the operations and steps described with reference to the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within, the system. Some of these operations may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the discussed concepts. In addition, the timing of these operations may be altered considerably and still achieve the results taught in this disclosure. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by the system in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the discussed concepts.
- Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure. For example, although the present disclosure has been described with reference to particular communication exchanges involving certain network access and protocols,
communication system 10 may be applicable to other exchanges or routing protocols in which packets are exchanged in order to provide mobility data, connectivity parameters, access management, etc. Moreover, althoughcommunication system 10 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements and operations may be replaced by any suitable architecture or process that achieves the intended functionality ofcommunication system 10. - Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims.
Claims (20)
1. A method, comprising:
authenticating a first agent to an on board unit (OBU) of a vehicle if the first agent validates a first set of one or more authentication requirements;
identifying a first identity profile corresponding to the first agent;
determining a role of the first agent in the vehicle; and
configuring the vehicle with the first identity profile, the vehicle configured based, at least in part, on the role of the first agent,
wherein the first identity profile is one of a plurality of identity profiles provisioned on the OBU.
2. The method of claim 1 , wherein the first agent is a human agent.
3. The method of claim 1 , wherein each one of a plurality of agents corresponds to a respective one of the plurality of identity profiles, wherein the plurality of agents includes one or more of a human agent, a machine device, a software agent, an authorized entity, and a mobile device.
4. The method of claim 1 , further comprising:
establishing a network connection from the OBU to a remote node of an identity service provider; and
downloading the first identity profile from the remote node to the OBU.
5. The method of claim 1 , further comprising:
authenticating a second agent to the OBU if the second agent validates a second set of one or more authentication requirements;
identifying a second identity profile corresponding to the second agent;
determining the role of the second agent in the vehicle; and
configuring the vehicle with the second identity profile, wherein the vehicle is configured based, at least in part, on the role of the second agent.
6. The method of claim 1 , further comprising:
determining the first agent has priority over a second agent if the first and second agents are authenticated to the OBU concurrently,
wherein any preferences in a second identity profile associated with the second agent conflicting with preferences in the first identity profile are overridden by the preferences associated with the first identity profile.
7. The method of claim 1 , wherein the first identity profile of the first agent is stored on the OBU of the vehicle and on one or more other OBUs of one or more other vehicles, respectively.
8. The method of claim 1 , further comprising:
determining whether one or more limitations are set for the first identity profile; and
applying the one or more limitations when the vehicle is configured with the first identity profile.
9. One or more non-transitory media that includes code for execution and when executed by a processor is operable to perform operations comprising:
authenticating a first agent to an on board unit (OBU) of a vehicle if the first agent validates a first set of one or more authentication requirements;
identifying a first identity profile corresponding to the first agent;
determining a priority of the first agent in the vehicle; and
configuring the vehicle with the first identity profile, the vehicle configured based, at least in part, on the priority of the first agent,
wherein the first identity profile is one of a plurality of identity profiles provisioned on the OBU.
10. The one or more non-transitory media of claim 9 , wherein each one of a plurality of agents corresponds to a respective one of the plurality of identity profiles, wherein the plurality of agents includes one or more of a human agent, a machine device, a software agent, an authorized entity, and a mobile device.
11. The one or more non-transitory media of claim 9 , wherein the configuring the vehicle with the first identity profile includes configuring vehicle settings based, at least in part, on a role of the first agent.
12. The one or more non-transitory media of claim 9 , wherein the configuring the vehicle with the first identity profile includes configuring preferences indicated in the first identity profile.
13. The one or more non-transitory media of claim 12 , the operations further comprising:
determining the first agent has priority over a second agent if the first and second agents are authenticated to the OBU concurrently,
wherein any preferences in a second identity profile associated with the second agent that conflict with the preferences in the first identity profile are overridden by the preferences in the first identity profile.
14. The one or more non-transitory media of claim 9 , wherein the code for execution, when executed by a processor, is operable to perform further operations comprising:
establishing a network connection from the OBU to a remote node of an identity service provider when the first agent is authenticated; and
performing one of adding, removing, or updating a virtual subscriber identity module (VSIM) in the first identity profile.
15. The one or more non-transitory media of claim 9 , wherein configuring the vehicle with the first identity profile includes configuring a network interface account and network configurations on the OBU for one or more mobile devices identified in the first identity profile.
16. An apparatus, comprising:
at least one memory element configured to store data;
an agent provisioning module; and
at least one processor operable to execute instructions associated with the data and the agent provisioning module to:
authenticate a first agent to the apparatus if the first agent validates a first set of one or more authentication requirements, the apparatus configured for operation in a vehicle;
identify a first identity profile corresponding to the first agent;
determine a role of the first agent in the vehicle; and
configure the vehicle with the first identity profile, wherein the vehicle is configured based, at least in part, on the role of the first agent,
wherein the first identity profile is one of a plurality of identity profiles provisioned in the memory element.
17. The apparatus of claim 16 , further comprising:
an identity profile provisioning module, wherein the processor is operable to execute further instructions associated with the data and the identity profile provisioning module to:
establish a network connection from the apparatus to a remote node of an identity service provider;
download the first identity profile from the remote node to the apparatus; and
store the first identity profile in the memory element in an encrypted format.
18. The apparatus of claim 16 , wherein configuring the vehicle with the first identity profile includes configuring preferences indicated in the first identity profile.
19. The apparatus of claim 16 , wherein configuring the vehicle with the first identity profile includes configuring a network interface account and network configurations indicated in the first identity profile for one or more mobile devices identified in the first identity profile.
20. The apparatus of claim 16 , further comprising:
a virtual subscriber identity module (VSIM) provisioning module, wherein the processor is operable to execute further instructions associated with the data and the VSIM provisioning module to:
establish a network connection from the apparatus to a remote node of an identity service provider when the first agent is authenticated; and
perform one of adding, removing, or updating a virtual subscriber identity module (VSIM) in the first identity profile.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/484,664 US20140380442A1 (en) | 2011-01-14 | 2014-09-12 | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161433138P | 2011-01-14 | 2011-01-14 | |
US13/014,605 US8863256B1 (en) | 2011-01-14 | 2011-01-26 | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
US14/484,664 US20140380442A1 (en) | 2011-01-14 | 2014-09-12 | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/014,605 Division US8863256B1 (en) | 2011-01-14 | 2011-01-26 | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140380442A1 true US20140380442A1 (en) | 2014-12-25 |
Family
ID=48952184
Family Applications (19)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/014,605 Active - Reinstated 2031-10-14 US8863256B1 (en) | 2011-01-14 | 2011-01-26 | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
US13/071,367 Active - Reinstated 2032-02-01 US8848608B1 (en) | 2011-01-14 | 2011-03-24 | System and method for wireless interface selection and for communication and access control of subsystems, devices, and data in a vehicular environment |
US13/083,305 Active US8989954B1 (en) | 2011-01-14 | 2011-04-08 | System and method for applications management in a networked vehicular environment |
US13/104,737 Active 2031-06-26 US8705527B1 (en) | 2011-01-14 | 2011-05-10 | System and method for internal networking, data optimization and dynamic frequency selection in a vehicular environment |
US13/108,631 Active 2031-09-23 US8718797B1 (en) | 2011-01-14 | 2011-05-16 | System and method for establishing communication channels between on-board unit of vehicle and plurality of nodes |
US13/111,425 Active 2032-11-06 US9083581B1 (en) | 2011-01-14 | 2011-05-19 | System and method for providing resource sharing, synchronizing, media coordination, transcoding, and traffic management in a vehicular environment |
US13/114,659 Expired - Fee Related US9154900B1 (en) | 2011-01-14 | 2011-05-24 | System and method for transport, network, translation, and adaptive coding in a vehicular network environment |
US13/118,220 Active 2031-07-08 US9036509B1 (en) | 2011-01-14 | 2011-05-27 | System and method for routing, mobility, application services, discovery, and sensing in a vehicular network environment |
US13/118,024 Active 2031-12-12 US8514825B1 (en) | 2011-01-14 | 2011-05-27 | System and method for enabling a vehicular access network in a vehicular environment |
US13/117,860 Expired - Fee Related US8903593B1 (en) | 2011-01-14 | 2011-05-27 | System and method for analyzing vehicular behavior in a network environment |
US13/943,114 Active 2031-11-26 US9225782B2 (en) | 2011-01-14 | 2013-07-16 | System and method for enabling a vehicular access network in a vehicular environment |
US14/242,122 Active US9277370B2 (en) | 2011-01-14 | 2014-04-01 | System and method for internal networking, data optimization and dynamic frequency selection in a vehicular environment |
US14/243,304 Active 2033-02-17 US9860709B2 (en) | 2011-01-14 | 2014-04-02 | System and method for real-time synthesis and performance enhancement of audio/video data, noise cancellation, and gesture based user interfaces in a vehicular environment |
US14/485,050 Active 2033-06-26 US10117066B2 (en) | 2011-01-14 | 2014-09-12 | System and method for wireless interface selection and for communication and access control of subsystems, devices, and data in a vehicular environment |
US14/484,664 Abandoned US20140380442A1 (en) | 2011-01-14 | 2014-09-12 | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
US14/619,247 Active 2031-12-24 US9888363B2 (en) | 2011-01-14 | 2015-02-11 | System and method for applications management in a networked vehicular environment |
US14/664,101 Active US9654937B2 (en) | 2011-01-14 | 2015-03-20 | System and method for routing, mobility, application services, discovery, and sensing in a vehicular network environment |
US15/594,379 Expired - Fee Related US10602329B2 (en) | 2011-01-14 | 2017-05-12 | System and method for routing, mobility, application services, discovery, and sensing in a vehicular network environment |
US16/128,027 Active 2031-04-09 US10979875B2 (en) | 2011-01-14 | 2018-09-11 | System and method for wireless interface selection and for communication and access control of subsystems, devices, and data in a vehicular environment |
Family Applications Before (14)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/014,605 Active - Reinstated 2031-10-14 US8863256B1 (en) | 2011-01-14 | 2011-01-26 | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
US13/071,367 Active - Reinstated 2032-02-01 US8848608B1 (en) | 2011-01-14 | 2011-03-24 | System and method for wireless interface selection and for communication and access control of subsystems, devices, and data in a vehicular environment |
US13/083,305 Active US8989954B1 (en) | 2011-01-14 | 2011-04-08 | System and method for applications management in a networked vehicular environment |
US13/104,737 Active 2031-06-26 US8705527B1 (en) | 2011-01-14 | 2011-05-10 | System and method for internal networking, data optimization and dynamic frequency selection in a vehicular environment |
US13/108,631 Active 2031-09-23 US8718797B1 (en) | 2011-01-14 | 2011-05-16 | System and method for establishing communication channels between on-board unit of vehicle and plurality of nodes |
US13/111,425 Active 2032-11-06 US9083581B1 (en) | 2011-01-14 | 2011-05-19 | System and method for providing resource sharing, synchronizing, media coordination, transcoding, and traffic management in a vehicular environment |
US13/114,659 Expired - Fee Related US9154900B1 (en) | 2011-01-14 | 2011-05-24 | System and method for transport, network, translation, and adaptive coding in a vehicular network environment |
US13/118,220 Active 2031-07-08 US9036509B1 (en) | 2011-01-14 | 2011-05-27 | System and method for routing, mobility, application services, discovery, and sensing in a vehicular network environment |
US13/118,024 Active 2031-12-12 US8514825B1 (en) | 2011-01-14 | 2011-05-27 | System and method for enabling a vehicular access network in a vehicular environment |
US13/117,860 Expired - Fee Related US8903593B1 (en) | 2011-01-14 | 2011-05-27 | System and method for analyzing vehicular behavior in a network environment |
US13/943,114 Active 2031-11-26 US9225782B2 (en) | 2011-01-14 | 2013-07-16 | System and method for enabling a vehicular access network in a vehicular environment |
US14/242,122 Active US9277370B2 (en) | 2011-01-14 | 2014-04-01 | System and method for internal networking, data optimization and dynamic frequency selection in a vehicular environment |
US14/243,304 Active 2033-02-17 US9860709B2 (en) | 2011-01-14 | 2014-04-02 | System and method for real-time synthesis and performance enhancement of audio/video data, noise cancellation, and gesture based user interfaces in a vehicular environment |
US14/485,050 Active 2033-06-26 US10117066B2 (en) | 2011-01-14 | 2014-09-12 | System and method for wireless interface selection and for communication and access control of subsystems, devices, and data in a vehicular environment |
Family Applications After (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/619,247 Active 2031-12-24 US9888363B2 (en) | 2011-01-14 | 2015-02-11 | System and method for applications management in a networked vehicular environment |
US14/664,101 Active US9654937B2 (en) | 2011-01-14 | 2015-03-20 | System and method for routing, mobility, application services, discovery, and sensing in a vehicular network environment |
US15/594,379 Expired - Fee Related US10602329B2 (en) | 2011-01-14 | 2017-05-12 | System and method for routing, mobility, application services, discovery, and sensing in a vehicular network environment |
US16/128,027 Active 2031-04-09 US10979875B2 (en) | 2011-01-14 | 2018-09-11 | System and method for wireless interface selection and for communication and access control of subsystems, devices, and data in a vehicular environment |
Country Status (1)
Country | Link |
---|---|
US (19) | US8863256B1 (en) |
Cited By (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105608530A (en) * | 2015-12-18 | 2016-05-25 | 北京四方继保自动化股份有限公司 | Operation, distribution and dispatching data integrity verification method for power distribution network |
US20160323256A1 (en) * | 2015-04-28 | 2016-11-03 | Qualcomm Incorporated | Systems and Methods for Performing Remote Authentication of a Virtual Subscriber Identity Module (SIM) |
CN106327172A (en) * | 2015-06-17 | 2017-01-11 | 西安中兴新软件有限责任公司 | Payment method and device for virtual SIM card terminal |
US9622159B2 (en) * | 2015-09-01 | 2017-04-11 | Ford Global Technologies, Llc | Plug-and-play interactive vehicle interior component architecture |
US20170134298A1 (en) * | 2015-11-05 | 2017-05-11 | Qualcomm Incorporated | System and Methods for Improving Support of a Virtual Subscriber Identity Module (SIM) in a Multi-SIM Wireless Communication Device |
US9654937B2 (en) | 2011-01-14 | 2017-05-16 | Cisco Technology, Inc. | System and method for routing, mobility, application services, discovery, and sensing in a vehicular network environment |
US20170164314A1 (en) * | 2015-12-03 | 2017-06-08 | Mobile Technologies, Inc. | Electronically connected environment |
US20170180440A1 (en) * | 2015-12-22 | 2017-06-22 | Caterpillar Inc. | Information management system and method of delivering data associated with machine |
CN107018090A (en) * | 2015-09-08 | 2017-08-04 | 现代自动车株式会社 | The operating method of communication node in network |
US9747740B2 (en) | 2015-03-02 | 2017-08-29 | Ford Global Technologies, Llc | Simultaneous button press secure keypad code entry |
US9744852B2 (en) | 2015-09-10 | 2017-08-29 | Ford Global Technologies, Llc | Integration of add-on interior modules into driver user interface |
US20170272935A1 (en) * | 2016-03-18 | 2017-09-21 | Ford Global Technologies, Llc | Method and apparatus for cellular subscription tethering |
US9860710B2 (en) | 2015-09-08 | 2018-01-02 | Ford Global Technologies, Llc | Symmetrical reference personal device location tracking |
US20180014269A1 (en) * | 2016-07-06 | 2018-01-11 | Gogo Llc | Hyper-number portability |
US20180012273A1 (en) * | 2016-07-07 | 2018-01-11 | NextEv USA, Inc. | Methods and systems for controlling communications by a driver in a vehicle |
US9914418B2 (en) | 2015-09-01 | 2018-03-13 | Ford Global Technologies, Llc | In-vehicle control location |
US9914415B2 (en) | 2016-04-25 | 2018-03-13 | Ford Global Technologies, Llc | Connectionless communication with interior vehicle components |
US20180081669A1 (en) * | 2016-09-20 | 2018-03-22 | At&T Mobility Ii Llc | Facilitating use of a universal integrated circuit card (uicc) for secure device updates |
US20180109623A1 (en) * | 2016-10-17 | 2018-04-19 | Robert Bosch Gmbh | Secure controlling of vehicle components in a telecommunication network |
US9967717B2 (en) | 2015-09-01 | 2018-05-08 | Ford Global Technologies, Llc | Efficient tracking of personal device locations |
US10046637B2 (en) | 2015-12-11 | 2018-08-14 | Ford Global Technologies, Llc | In-vehicle component control user interface |
US10082877B2 (en) | 2016-03-15 | 2018-09-25 | Ford Global Technologies, Llc | Orientation-independent air gesture detection service for in-vehicle environments |
US10198036B2 (en) | 2012-12-05 | 2019-02-05 | Mobile Tech, Inc. | Docking station for tablet device |
US10251144B2 (en) | 2015-12-03 | 2019-04-02 | Mobile Tech, Inc. | Location tracking of products and product display assemblies in a wirelessly connected environment |
WO2019172929A1 (en) * | 2018-03-09 | 2019-09-12 | Ford Global Technologies, Llc | Integrating transportation services and facility access services through a calendar system |
WO2019232154A1 (en) * | 2018-06-01 | 2019-12-05 | Sherr David M | Software-defined network resource provisioning architecture |
US10593443B1 (en) | 2019-01-24 | 2020-03-17 | Mobile Tech, Inc. | Motion sensing cable for intelligent charging of devices |
US10650621B1 (en) | 2016-09-13 | 2020-05-12 | Iocurrents, Inc. | Interfacing with a vehicular controller area network |
US10728868B2 (en) | 2015-12-03 | 2020-07-28 | Mobile Tech, Inc. | Remote monitoring and control over wireless nodes in a wirelessly connected environment |
US10754381B2 (en) | 2016-07-29 | 2020-08-25 | Mobile Tech, Inc. | Docking system for portable computing device |
US10834199B2 (en) * | 2018-09-18 | 2020-11-10 | Ford Global Technologies, Llc | Cloud authorized vehicle control |
DE102020104712A1 (en) | 2020-02-23 | 2021-08-26 | Bayerische Motoren Werke Aktiengesellschaft | Method and system for providing a communication function in a mobile network |
US11109335B2 (en) | 2015-12-03 | 2021-08-31 | Mobile Tech, Inc. | Wirelessly connected hybrid environment of different types of wireless nodes |
US11184340B2 (en) * | 2017-12-15 | 2021-11-23 | Volkswagen Aktiengesellschaft | Apparatus, method, and computer program for enabling a transportation vehicle component and vehicle-to-vehicle communication module |
WO2021254743A1 (en) * | 2020-06-16 | 2021-12-23 | innogy eMobility Solutions GmbH | Charging station for an electric vehicle, central processing unit and charging station system |
CN114162063A (en) * | 2020-09-10 | 2022-03-11 | 动态Ad有限责任公司 | Vehicle, method for vehicle, and storage medium |
DE102020124249A1 (en) | 2020-09-17 | 2022-03-17 | Bayerische Motoren Werke Aktiengesellschaft | Method and system for providing a communication function in a means of transportation |
US11472293B2 (en) | 2015-03-02 | 2022-10-18 | Ford Global Technologies, Llc | In-vehicle component user interface |
US11510051B2 (en) | 2017-12-15 | 2022-11-22 | Volkswagen Aktiengesellschaft | Devices, methods, and computer program for releasing transportation vehicle components, and vehicle-to-vehicle communication module |
US11540350B2 (en) | 2018-10-25 | 2022-12-27 | Mobile Tech, Inc. | Proxy nodes for expanding the functionality of nodes in a wirelessly connected environment |
DE102022117811B3 (en) | 2022-07-15 | 2023-09-07 | Cariad Se | Method and device for deleting user data in a motor vehicle and motor vehicle |
EP4239562A3 (en) * | 2018-03-28 | 2023-11-22 | Pioneer Corporation | Server device, information processing method, program, and storage medium |
WO2024008542A1 (en) * | 2022-07-05 | 2024-01-11 | Mercedes-Benz Group AG | Method for registering a control unit of a vehicle in a service infrastructure |
US12047418B2 (en) | 2019-06-05 | 2024-07-23 | Cisco Technology, Inc. | Adaptive network controls for IoT and other applications |
Families Citing this family (1172)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10022422A1 (en) * | 2000-05-09 | 2001-11-15 | Bosch Gmbh Robert | Accessing device in communications network in motor vehicle by external device involves gateway checking if device requested by external device allows access, sending software element |
US7472231B1 (en) * | 2001-09-07 | 2008-12-30 | Netapp, Inc. | Storage area network data cache |
US20110276609A1 (en) | 2001-12-27 | 2011-11-10 | Denison William D | Method for Controlling and Recording the Security of an Enclosure |
US10117078B1 (en) * | 2005-04-12 | 2018-10-30 | Ehud Mendelson | Medical information communication method |
US7899583B2 (en) | 2005-04-12 | 2011-03-01 | Ehud Mendelson | System and method of detecting and navigating to empty parking spaces |
US9420423B1 (en) * | 2005-04-12 | 2016-08-16 | Ehud Mendelson | RF beacon deployment and method of use |
US8677377B2 (en) | 2005-09-08 | 2014-03-18 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
US8355410B2 (en) | 2007-08-17 | 2013-01-15 | At&T Intellectual Property I, L.P. | Location-based mobile gaming application and method for implementing the same using a scalable tiered geocast protocol |
US9762600B2 (en) * | 2006-05-16 | 2017-09-12 | Lear Corporation | Mobile router with vehicle intrusion detection |
US9776597B2 (en) * | 2006-05-16 | 2017-10-03 | Lear Corporation | Vehicle with electronic system intrusion detection |
US9787694B2 (en) * | 2006-05-16 | 2017-10-10 | Lear Corporation | Method for vehicle electronic system intrusion detection |
US9787703B2 (en) * | 2006-05-16 | 2017-10-10 | Lear Corporation | Method for vehicle intrusion detection with mobile router |
US9813436B2 (en) * | 2006-05-16 | 2017-11-07 | Lear Corporation | Method for vehicle intrusion detection with electronic control unit |
US9787702B2 (en) * | 2006-05-16 | 2017-10-10 | Lear Corporation | Electronic control unit with vehicle intrusion detection |
US9318108B2 (en) | 2010-01-18 | 2016-04-19 | Apple Inc. | Intelligent automated assistant |
US8977255B2 (en) | 2007-04-03 | 2015-03-10 | Apple Inc. | Method and system for operating a multi-function portable electronic device using voice-activation |
US7986914B1 (en) * | 2007-06-01 | 2011-07-26 | At&T Mobility Ii Llc | Vehicle-based message control using cellular IP |
US8553623B2 (en) * | 2007-07-20 | 2013-10-08 | Broadcom Corporation | Method and system for utilizing standardized interface in a wireless device to discover and use local and remote resources |
US7769806B2 (en) | 2007-10-24 | 2010-08-03 | Social Communications Company | Automated real-time data stream switching in a shared virtual area communication environment |
EP2279472A4 (en) | 2008-04-05 | 2013-11-20 | Social Communications Co | Shared virtual area communication environment based apparatus and methods |
US8676904B2 (en) | 2008-10-02 | 2014-03-18 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
WO2010065848A2 (en) | 2008-12-05 | 2010-06-10 | Social Communications Company | Realtime kernel |
US9853922B2 (en) | 2012-02-24 | 2017-12-26 | Sococo, Inc. | Virtual area communications |
US10706373B2 (en) | 2011-06-03 | 2020-07-07 | Apple Inc. | Performing actions associated with task items that represent tasks to perform |
US9111538B2 (en) * | 2009-09-30 | 2015-08-18 | T-Mobile Usa, Inc. | Genius button secondary commands |
US9118428B2 (en) | 2009-11-04 | 2015-08-25 | At&T Intellectual Property I, L.P. | Geographic advertising using a scalable wireless geocast protocol |
US10276170B2 (en) | 2010-01-18 | 2019-04-30 | Apple Inc. | Intelligent automated assistant |
US10016684B2 (en) * | 2010-10-28 | 2018-07-10 | At&T Intellectual Property I, L.P. | Secure geographic based gaming |
DE102010053803B3 (en) * | 2010-12-08 | 2012-02-23 | Brose Fahrzeugteile Gmbh & Co. Kommanditgesellschaft, Hallstadt | Method for operating a vehicle electrical system of a motor vehicle and then working bus system |
US20130321607A1 (en) * | 2011-01-28 | 2013-12-05 | Vigilent Telesystemes Inc. | Monitoring system for controlling the pan/tilt of a camera used in a surgery room |
WO2012105215A1 (en) * | 2011-01-31 | 2012-08-09 | 本田技研工業株式会社 | Vehicle control device |
CN102158310A (en) * | 2011-02-15 | 2011-08-17 | 中兴通讯股份有限公司 | Method and device for realizing multi-cell precoding |
JP5565476B2 (en) | 2011-02-17 | 2014-08-06 | 日本電気株式会社 | Network system and network flow tracking method |
US9949309B2 (en) * | 2011-02-19 | 2018-04-17 | Nomad Spectrum Limited | Methods, computer readable mediums, and apparatuses for providing communication to a mobile device using virtual connections |
US9854055B2 (en) * | 2011-02-28 | 2017-12-26 | Nokia Technologies Oy | Method and apparatus for providing proxy-based content discovery and delivery |
WO2012118917A2 (en) * | 2011-03-03 | 2012-09-07 | Social Communications Company | Realtime communications and network browsing client |
US9288836B1 (en) * | 2011-03-18 | 2016-03-15 | Marvell International Ltd. | Electronic bracelet |
US8707022B2 (en) * | 2011-04-05 | 2014-04-22 | Apple Inc. | Apparatus and methods for distributing and storing electronic access clients |
EP2695074B1 (en) * | 2011-04-06 | 2016-07-06 | Robert Bosch GmbH | Method and apparatus for adapting the data transmission security in a serial bus system |
JP5770924B2 (en) | 2011-04-06 | 2015-08-26 | ローベルト ボッシュ ゲゼルシャフト ミット ベシュレンクテル ハフツング | Method and apparatus for increasing data transmission capacity in a serial bus system |
DE102011007914A1 (en) * | 2011-04-21 | 2012-10-25 | Deere & Company | Data communication interface for an agricultural utility vehicle |
US9229905B1 (en) * | 2011-04-22 | 2016-01-05 | Angel A. Penilla | Methods and systems for defining vehicle user profiles and managing user profiles via cloud systems and applying learned settings to user profiles |
WO2012146649A1 (en) * | 2011-04-26 | 2012-11-01 | Robert Bosch Gmbh | Method and device for serial data transmission which is adapted to memory sizes |
PT2518977T (en) * | 2011-04-29 | 2019-07-12 | Icomera Ab | Vehicle communication system |
CN110225051A (en) * | 2011-05-03 | 2019-09-10 | 诺基亚技术有限公司 | Method and apparatus for keeping active signal to send |
US20140341109A1 (en) * | 2011-06-02 | 2014-11-20 | Interdigital Patent Holdings, Inc. | Methods, Apparatus and Systems for Managing Converged Gateway Communications |
US8797938B2 (en) * | 2011-06-13 | 2014-08-05 | Electronics And Telecommunications Research Institute | Multicasting system and method for vehicular communication network |
US9161158B2 (en) | 2011-06-27 | 2015-10-13 | At&T Intellectual Property I, L.P. | Information acquisition using a scalable wireless geocast protocol |
US9319842B2 (en) | 2011-06-27 | 2016-04-19 | At&T Intellectual Property I, L.P. | Mobile device configured point and shoot type weapon |
US9235971B1 (en) * | 2011-06-28 | 2016-01-12 | Emc Corporation | Service window optimized system alert engine |
ES2548409T3 (en) | 2011-06-29 | 2015-10-16 | Robert Bosch Gmbh | Method and device for serial data transmission with a flexible message size and a variable bit length |
US10855734B2 (en) * | 2011-06-29 | 2020-12-01 | Interdigital Ce Patent Holdings | Remote management of devices |
US8850075B2 (en) * | 2011-07-06 | 2014-09-30 | Microsoft Corporation | Predictive, multi-layer caching architectures |
DE102011078869A1 (en) * | 2011-07-08 | 2013-01-10 | Robert Bosch Gmbh | Method and device for operating a vehicle, computer program, computer program product |
WO2013008448A1 (en) * | 2011-07-08 | 2013-01-17 | パナソニック株式会社 | Terminal apparatus and communication system |
US9184779B2 (en) * | 2011-07-22 | 2015-11-10 | Texas Instruments Incorporated | Dynamic medium switch in co-located PLC and RF networks |
US20130038437A1 (en) * | 2011-08-08 | 2013-02-14 | Panasonic Corporation | System for task and notification handling in a connected car |
CN102795250A (en) * | 2012-08-27 | 2012-11-28 | 白维 | Networking operation dispatching system for railway vehicles based on electronic intervals |
US9474018B2 (en) * | 2011-08-16 | 2016-10-18 | Telefonaktiebolaget L M Ericsson (Publ) | Smart radio area network for wireless distributed cloud computing |
US8989089B2 (en) * | 2011-08-18 | 2015-03-24 | Ofinno Technologies, Llc | Automobile data transmission |
US9919598B2 (en) * | 2011-08-22 | 2018-03-20 | Lg Electronics Inc. | Mobile terminal, image display apparatus mounted in vehicle and data processing method using the same |
US20130159940A1 (en) * | 2011-08-22 | 2013-06-20 | International Technological University | Gesture-Controlled Interactive Information Board |
JP5859771B2 (en) * | 2011-08-22 | 2016-02-16 | ソニー株式会社 | Information processing apparatus, information processing system information processing method, and program |
US9177427B1 (en) | 2011-08-24 | 2015-11-03 | Allstate Insurance Company | Vehicle driver feedback device |
US8862767B2 (en) | 2011-09-02 | 2014-10-14 | Ebay Inc. | Secure elements broker (SEB) for application communication channel selector optimization |
DE102011112447A1 (en) * | 2011-09-03 | 2013-03-07 | Volkswagen Aktiengesellschaft | Method and arrangement for providing a graphical user interface, in particular in a vehicle |
DE102011112599A1 (en) * | 2011-09-06 | 2013-03-07 | Volkswagen Aktiengesellschaft | Vehicle comfort system for using and / or controlling vehicle functions using a mobile device |
US9928485B2 (en) | 2011-09-07 | 2018-03-27 | Elwha Llc | Computational systems and methods for regulating information flow during interactions |
US9690853B2 (en) | 2011-09-07 | 2017-06-27 | Elwha Llc | Computational systems and methods for regulating information flow during interactions |
US10523618B2 (en) | 2011-09-07 | 2019-12-31 | Elwha Llc | Computational systems and methods for identifying a communications partner |
US10606989B2 (en) | 2011-09-07 | 2020-03-31 | Elwha Llc | Computational systems and methods for verifying personal information during transactions |
US10074113B2 (en) | 2011-09-07 | 2018-09-11 | Elwha Llc | Computational systems and methods for disambiguating search terms corresponding to network members |
US10546306B2 (en) | 2011-09-07 | 2020-01-28 | Elwha Llc | Computational systems and methods for regulating information flow during interactions |
US9473647B2 (en) | 2011-09-07 | 2016-10-18 | Elwha Llc | Computational systems and methods for identifying a communications partner |
US10546295B2 (en) | 2011-09-07 | 2020-01-28 | Elwha Llc | Computational systems and methods for regulating information flow during interactions |
US9747561B2 (en) * | 2011-09-07 | 2017-08-29 | Elwha Llc | Computational systems and methods for linking users of devices |
US9491146B2 (en) | 2011-09-07 | 2016-11-08 | Elwha Llc | Computational systems and methods for encrypting data for anonymous storage |
WO2013050216A1 (en) * | 2011-10-04 | 2013-04-11 | International Business Machines Corporation | Pre-emptive content caching in mobile networks |
US8983681B2 (en) * | 2011-10-06 | 2015-03-17 | General Motors Llc | Method of communicating with a vehicle having a telematics unit |
US9495870B2 (en) * | 2011-10-20 | 2016-11-15 | At&T Intellectual Property I, L.P. | Vehicular communications using a scalable ad hoc geographic routing protocol |
DE102011085814B3 (en) * | 2011-11-07 | 2013-03-28 | Robert Bosch Gmbh | Interconnecting device for interconnecting travel groups existing in multiple vehicles, is configured with system linked with mobile telephones connected with one another over common central server |
EP2748716B1 (en) | 2011-11-15 | 2018-05-16 | Nicira Inc. | Network control system for configuring middleboxes |
US20130282946A1 (en) * | 2012-04-23 | 2013-10-24 | Flextronics Ap, Llc | Controller area network bus |
US20130219039A1 (en) * | 2011-11-16 | 2013-08-22 | Flextronics Ap, Llc | Network selector in a vehicle infotainment system |
US9088572B2 (en) | 2011-11-16 | 2015-07-21 | Flextronics Ap, Llc | On board vehicle media controller |
EP2781136A1 (en) * | 2011-11-16 | 2014-09-24 | Telefonaktiebolaget L M Ericsson (PUBL) | Ue control of downlink data |
US10862764B2 (en) | 2011-11-16 | 2020-12-08 | AutoConnect Holdings, LLC | Universal console chassis for the car |
WO2013105916A1 (en) * | 2011-12-01 | 2013-07-18 | Intel Corporation | Secure message filtering to vehicle electronic control units with secure provisioning of message filtering rules |
CN103167464B (en) * | 2011-12-09 | 2018-06-15 | 中兴通讯股份有限公司 | Method, MS and the MN of triggering update mobile node map information |
DE102011121255B3 (en) * | 2011-12-15 | 2013-04-18 | Lear Corporation Gmbh | Control system for motor vehicle, has control device for extracting and passing HTTP request from controlled area network bus by compatible message onto web server, where bus connects control device and another control device |
US8744419B2 (en) | 2011-12-15 | 2014-06-03 | At&T Intellectual Property, I, L.P. | Media distribution via a scalable ad hoc geographic protocol |
CN104010914B (en) * | 2011-12-29 | 2017-11-07 | 英特尔公司 | System, method and apparatus for recognizing automotive occupant |
US20130201316A1 (en) | 2012-01-09 | 2013-08-08 | May Patents Ltd. | System and method for server based control |
US20130210412A1 (en) * | 2012-01-13 | 2013-08-15 | Logic PD, Inc. | Method for embedding device-specific data to enable provisioning a device with a mobile device |
US9686647B2 (en) * | 2012-01-17 | 2017-06-20 | Comcast Cable Communications, Llc | Mobile WiFi network |
US8848558B1 (en) | 2012-01-18 | 2014-09-30 | Sprint Communications Company L.P. | Mesh wireless connectivity |
JP5510471B2 (en) * | 2012-01-20 | 2014-06-04 | トヨタ自動車株式会社 | Driving model creation device, driving model creation method, driving evaluation device, driving evaluation method, and driving support system |
US9647721B2 (en) * | 2012-02-06 | 2017-05-09 | Kfx Circuits And Systems Private Limited | Variable impedance scheme for providing a wired communication |
WO2013119802A1 (en) | 2012-02-11 | 2013-08-15 | Social Communications Company | Routing virtual area based communications |
DE102013101508A1 (en) * | 2012-02-20 | 2013-08-22 | Denso Corporation | A data communication authentication system for a vehicle, a network coupling device for a vehicle, a data communication system for a vehicle, and a data communication device for a vehicle |
KR101386809B1 (en) * | 2012-02-29 | 2014-04-21 | 주식회사 팬택 | Communication Terminal creating Multiple MTU and Data Transferring Method Using The Same |
WO2014172369A2 (en) | 2013-04-15 | 2014-10-23 | Flextronics Ap, Llc | Intelligent vehicle for assisting vehicle occupants and incorporating vehicle crate for blade processors |
US9412273B2 (en) | 2012-03-14 | 2016-08-09 | Autoconnect Holdings Llc | Radar sensing and emergency response vehicle detection |
US20140309839A1 (en) | 2013-04-15 | 2014-10-16 | Flextronics Ap, Llc | Vehicle Registration to Enter Automated Control of Vehicular Traffic |
US9384609B2 (en) | 2012-03-14 | 2016-07-05 | Autoconnect Holdings Llc | Vehicle to vehicle safety and traffic communications |
US9147298B2 (en) | 2012-03-14 | 2015-09-29 | Flextronics Ap, Llc | Behavior modification via altered map routes based on user profile information |
US9082238B2 (en) | 2012-03-14 | 2015-07-14 | Flextronics Ap, Llc | Synchronization between vehicle and user device calendar |
US9378601B2 (en) | 2012-03-14 | 2016-06-28 | Autoconnect Holdings Llc | Providing home automation information via communication with a vehicle |
DE102012005471A1 (en) * | 2012-03-17 | 2013-09-19 | GM Global Technology Operations LLC (n.d. Ges. d. Staates Delaware) | Traffic Information System |
ES2805290T3 (en) | 2012-03-29 | 2021-02-11 | Arilou Information Security Tech Ltd | Device to protect an electronic system of a vehicle |
EP2645780A1 (en) * | 2012-03-30 | 2013-10-02 | British Telecommunications Public Limited Company | Access point detection |
US20130279473A1 (en) | 2012-04-06 | 2013-10-24 | Suitable Technologies, Inc. | Method for wireless connectivity continuity and quality |
US9307568B2 (en) | 2012-04-06 | 2016-04-05 | Suitable Technologies, Inc. | System for wireless connectivity continuity and quality |
US20130279472A1 (en) | 2012-04-06 | 2013-10-24 | Suitable Technologies, Inc. | System for wireless connectivity continuity and quality |
US20130279479A1 (en) | 2012-04-06 | 2013-10-24 | Suitable Technologies, Inc. | Method for wireless connectivity continuity and quality |
US20130279487A1 (en) | 2012-04-06 | 2013-10-24 | Suitable Technologies, Inc. | System for wireless connectivity continuity and quality |
US9320076B2 (en) | 2012-04-06 | 2016-04-19 | Suitable Technologies, Inc. | System for wireless connectivity continuity and quality |
US20130343344A1 (en) | 2012-04-06 | 2013-12-26 | Suitable Technologies, Inc. | Method for wireless connectivity continuity and quality |
CN103359050B (en) * | 2012-04-06 | 2016-03-30 | 比亚迪股份有限公司 | Vehicle, Vehicular intelligent key device, vehicle remote control control loop and method |
WO2013152360A1 (en) | 2012-04-06 | 2013-10-10 | Suitable Technologies, Inc. | System for wireless connectivity continuity and quality |
US9344935B2 (en) | 2012-04-06 | 2016-05-17 | Suitable Technologies, Inc. | System for wireless connectivity continuity and quality |
US20130279411A1 (en) | 2012-04-06 | 2013-10-24 | Suitable Technologies, Inc. | Method for wireless connectivity continuity and quality |
US9320074B2 (en) * | 2012-04-06 | 2016-04-19 | Suitable Technologies, Inc. | Method for wireless connectivity continuity and quality |
CN103359060B (en) * | 2012-04-06 | 2016-01-13 | 比亚迪股份有限公司 | Vehicle, Vehicular intelligent key device, vehicle remote control control loop and method |
CN103359051B (en) * | 2012-04-06 | 2016-03-30 | 比亚迪股份有限公司 | Vehicle, Vehicular intelligent key device, vehicle remote control control loop and method |
US9907113B2 (en) * | 2012-04-06 | 2018-02-27 | Intel Corporation | Efficiency of wireless wide area networks utilizing local wireless connections |
US20130265885A1 (en) | 2012-04-06 | 2013-10-10 | Suitable Technologies, Inc. | Method for wireless connectivity continuity and quality |
CN103379580B (en) | 2012-04-13 | 2018-12-14 | 华为技术有限公司 | The method, apparatus and system of equipment discovery |
US20130283351A1 (en) * | 2012-04-18 | 2013-10-24 | Nokia Corporation | Method and apparatus for configuring services based on touch selection |
US9146603B2 (en) | 2012-05-08 | 2015-09-29 | William Reber, Llc | Cloud computing system, vehicle cloud processing device and methods for use therewith |
US8949974B2 (en) * | 2012-05-11 | 2015-02-03 | Tyfone, Inc. | Mobile device with password protected desktop screen |
US10417037B2 (en) | 2012-05-15 | 2019-09-17 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
JP6094259B2 (en) * | 2012-05-23 | 2017-03-15 | 株式会社デンソー | Management server |
DE102012010723A1 (en) * | 2012-05-30 | 2012-11-29 | Daimler Ag | Method for diagnosing component of motor vehicle, involves generating diagnostic script for diagnostic medium of motor vehicle, which is separate from another diagnostic script provided by diagnostic script providing device |
WO2013181026A1 (en) | 2012-06-02 | 2013-12-05 | Social Communications Company | Interfacing with a spatial virtual communications environment |
FR2993425B1 (en) * | 2012-07-13 | 2014-07-18 | Commissariat Energie Atomique | DEVICE AND METHOD FOR GENERATING INTERNET PROTOCOL (IP) ADDRESS FROM VEHICLE IDENTIFICATION NUMBER (VIN) |
US9088514B2 (en) * | 2012-07-23 | 2015-07-21 | Broadcom Corporation | Flexray communications using ethernet |
DE102012213328B4 (en) * | 2012-07-30 | 2020-06-10 | Bayerische Motoren Werke Aktiengesellschaft | Communication device for a vehicle |
WO2014020547A1 (en) | 2012-07-31 | 2014-02-06 | Indoorgo Navigation Systems Ltd. | Navigation method and device |
JP5840090B2 (en) * | 2012-08-17 | 2016-01-06 | 株式会社東芝 | Power consumption estimation device |
JP6031894B2 (en) * | 2012-08-24 | 2016-11-24 | 富士通株式会社 | Relay program, relay device, and relay method |
US9306743B2 (en) * | 2012-08-30 | 2016-04-05 | Texas Instruments Incorporated | One-way key fob and vehicle pairing verification, retention, and revocation |
KR102150289B1 (en) | 2012-08-30 | 2020-09-01 | 삼성전자주식회사 | User interface appratus in a user terminal and method therefor |
US20160164976A1 (en) | 2012-09-24 | 2016-06-09 | Suitable Technologies, Inc. | Systems and methods for remote presence |
CN102932531B (en) | 2012-09-27 | 2015-05-27 | 华为技术有限公司 | Method for keeping subscriber identity module cards on standby and terminal equipment |
DE102012019185B4 (en) * | 2012-09-28 | 2015-02-12 | Audi Ag | Method and system for determining mobile network quality and charging mobile data |
US8806613B2 (en) * | 2012-09-28 | 2014-08-12 | Intel Corporation | Intelligent task assignment and authorization systems and methods |
US11188652B2 (en) | 2012-10-02 | 2021-11-30 | Mordecai Barkan | Access management and credential protection |
US9342695B2 (en) * | 2012-10-02 | 2016-05-17 | Mordecai Barkan | Secured automated or semi-automated systems |
GB201217897D0 (en) * | 2012-10-05 | 2012-11-21 | Tomtom Int Bv | Location-based dynamic objects |
US9443432B2 (en) * | 2012-11-09 | 2016-09-13 | Trimble Navigation Limited | Vehicle association with driver using mobile technologies |
GB2508355B (en) * | 2012-11-28 | 2021-02-17 | Nomad Digital Ltd | Communication method |
US8914225B2 (en) | 2012-12-04 | 2014-12-16 | International Business Machines Corporation | Managing vehicles on a road network |
US9224289B2 (en) * | 2012-12-10 | 2015-12-29 | Ford Global Technologies, Llc | System and method of determining occupant location using connected devices |
EP2741452A1 (en) * | 2012-12-10 | 2014-06-11 | Robert Bosch Gmbh | Method for data transmission among ECUs and/or measuring devices |
US20140163771A1 (en) * | 2012-12-10 | 2014-06-12 | Ford Global Technologies, Llc | Occupant interaction with vehicle system using brought-in devices |
US9660745B2 (en) | 2012-12-12 | 2017-05-23 | At&T Intellectual Property I, L.P. | Geocast-based file transfer |
JP6113491B2 (en) * | 2012-12-18 | 2017-04-12 | 三菱重工メカトロシステムズ株式会社 | OBE, communication method and program |
CN103078848B (en) * | 2012-12-27 | 2015-09-23 | 合一网络技术(北京)有限公司 | A kind of system and method for multi-screen fuse coordination |
EP2944101A4 (en) * | 2013-01-09 | 2016-12-28 | Paxgrid Telemetric Systems Inc | Vehicle communications via wireless access vehicular environment |
US10102594B2 (en) * | 2013-01-09 | 2018-10-16 | International Business Machines Corporation | Dynamic power allocation among points of energy consumption for attaining an objective |
US9209985B1 (en) * | 2013-01-31 | 2015-12-08 | Maritime Telecommunications Network Inc. | Association of diverse application logic across multiple distinct devices with priority bandwidth channel |
EP4138075A1 (en) | 2013-02-07 | 2023-02-22 | Apple Inc. | Voice trigger for a digital assistant |
FR3002394B1 (en) * | 2013-02-15 | 2015-03-27 | Thales Sa | ARCHITECTURE FOR TRANSMITTING INFORMATION WITH A BRIDGE, IN PARTICULAR FOR APPLICATION TO THE AIRCRAFT |
EP2963863B1 (en) * | 2013-02-17 | 2018-01-03 | Parallel Wireless Inc. | Methods of incorporating an ad hoc cellular network into a fixed cellular network |
DE102013003040B4 (en) * | 2013-02-22 | 2015-11-12 | Audi Ag | Motor vehicle with later by application program changeable driving behavior and method for this purpose |
US9898725B2 (en) * | 2013-02-22 | 2018-02-20 | Creative Mobile Technologies, LLC | Passenger information module |
JP5838983B2 (en) * | 2013-02-25 | 2016-01-06 | トヨタ自動車株式会社 | Information processing apparatus and information processing method |
WO2014133496A1 (en) * | 2013-02-27 | 2014-09-04 | Hitachi Data Systems Corporation | Resource fencing for vlan multi-tenant systems |
GB2511301B (en) * | 2013-02-27 | 2019-11-20 | Nomad Spectrum Ltd | Providing wireless connectivity to a vehicle |
KR102046910B1 (en) * | 2013-03-08 | 2019-11-22 | 한국전자통신연구원 | System and method for providing tile-map using electronic navigation chart |
KR101548948B1 (en) * | 2013-03-08 | 2015-09-03 | 주식회사 케이티 | Method and system for providing electric vehicle in charging with contents |
US10313345B2 (en) | 2013-03-11 | 2019-06-04 | Amazon Technologies, Inc. | Application marketplace for virtual desktops |
US9002982B2 (en) * | 2013-03-11 | 2015-04-07 | Amazon Technologies, Inc. | Automated desktop placement |
US10142406B2 (en) | 2013-03-11 | 2018-11-27 | Amazon Technologies, Inc. | Automated data center selection |
US9148350B1 (en) | 2013-03-11 | 2015-09-29 | Amazon Technologies, Inc. | Automated data synchronization |
US9688243B2 (en) * | 2013-03-12 | 2017-06-27 | Robert Bosch Gmbh | System and method for creating and distributing diagnostic tests in an adaptive diagnostic development platform |
US9256615B2 (en) * | 2013-03-12 | 2016-02-09 | Verizon Patent And Licensing Inc. | Personalized navigation information based on user behavior |
US10652394B2 (en) | 2013-03-14 | 2020-05-12 | Apple Inc. | System and method for processing voicemail |
GB2511860A (en) * | 2013-03-15 | 2014-09-17 | Vodafone Ip Licensing Ltd | A Method and System of Providing Data Service According to a User's Future Location |
US9270516B2 (en) * | 2013-03-15 | 2016-02-23 | Genband Us Llc | Peer-to-peer interconnection between service providers |
US9349282B2 (en) * | 2013-03-15 | 2016-05-24 | Aliphcom | Proximity sensing device control architecture and data communication protocol |
US20140286496A1 (en) * | 2013-03-15 | 2014-09-25 | Aliphcom | Proximity sensing device control architecture and data communication protocol |
US10748529B1 (en) | 2013-03-15 | 2020-08-18 | Apple Inc. | Voice activated device for use with a voice-based digital assistant |
US11294396B2 (en) | 2013-03-15 | 2022-04-05 | Peloton Technology, Inc. | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles |
US9319916B2 (en) | 2013-03-15 | 2016-04-19 | Isco International, Llc | Method and appartus for signal interference processing |
US10698577B2 (en) * | 2013-03-18 | 2020-06-30 | Dennis Bushmitch | Integrated mobile device |
US20140286440A1 (en) * | 2013-03-19 | 2014-09-25 | Nvidia Corporation | Quality of service management system and method of forward error correction |
CN105075335B (en) | 2013-03-26 | 2019-01-25 | 瑞典爱立信有限公司 | Method and apparatus for cooperative localization in cordless communication network |
JP6024564B2 (en) * | 2013-03-28 | 2016-11-16 | 株式会社オートネットワーク技術研究所 | In-vehicle communication system |
ITMI20130495A1 (en) * | 2013-03-29 | 2014-09-30 | Atlas Copco Blm Srl | ELECTRONIC CONTROL AND CONTROL DEVICE FOR SENSORS |
JP6131686B2 (en) * | 2013-04-05 | 2017-05-24 | 株式会社デンソー | Display control device |
DE102013206661A1 (en) * | 2013-04-15 | 2014-10-16 | Robert Bosch Gmbh | Communication method for transmitting user data and corresponding communication system |
US9479923B2 (en) * | 2013-04-17 | 2016-10-25 | Nokia Technologies Oy | Provisioning wireless subscriptions using software-based subscriber identity modules |
US20140094148A1 (en) | 2013-05-08 | 2014-04-03 | Vringo Infrastructure Inc. | Cognitive Radio System And Cognitive Radio Carrier Device |
US9525524B2 (en) | 2013-05-31 | 2016-12-20 | At&T Intellectual Property I, L.P. | Remote distributed antenna system |
US9999038B2 (en) | 2013-05-31 | 2018-06-12 | At&T Intellectual Property I, L.P. | Remote distributed antenna system |
GB2514817A (en) * | 2013-06-05 | 2014-12-10 | Nordic Semiconductor Asa | Digital radio communication |
US20140362785A1 (en) * | 2013-06-05 | 2014-12-11 | Max4G, Inc. | Mapping Via Back To Back Ethernet Switches |
EP3008641A1 (en) | 2013-06-09 | 2016-04-20 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
US10176167B2 (en) | 2013-06-09 | 2019-01-08 | Apple Inc. | System and method for inferring user intent from speech inputs |
EP3008931B1 (en) * | 2013-06-13 | 2022-04-20 | Telefonaktiebolaget LM Ericsson (publ) | Controlling vehicle-to-vehicle communication using a distribution scheme |
WO2014204885A1 (en) * | 2013-06-17 | 2014-12-24 | International Electronic Machines Corporation | Vehicle group monitoring |
KR101509892B1 (en) * | 2013-06-25 | 2015-04-14 | 현대자동차주식회사 | Apparatus and method for experience information of user, and system thereof |
US10686646B1 (en) | 2013-06-26 | 2020-06-16 | Amazon Technologies, Inc. | Management of computing sessions |
JP6170757B2 (en) * | 2013-06-26 | 2017-07-26 | 富士通テン株式会社 | Display control apparatus, display system, information providing method, and program |
US10623243B2 (en) | 2013-06-26 | 2020-04-14 | Amazon Technologies, Inc. | Management of computing sessions |
US9244939B2 (en) * | 2013-06-27 | 2016-01-26 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Managing I/O operations in a shared file system |
US9280897B2 (en) * | 2013-07-11 | 2016-03-08 | Siemens Industry, Inc. | Emergency traffic management system |
US9473931B2 (en) * | 2013-07-17 | 2016-10-18 | Qualcomm Incorporated | Methods to achieve modem-assisted-service-classification functionality in a device with multiple subscriptions |
KR20150011223A (en) * | 2013-07-22 | 2015-01-30 | 엘에스산전 주식회사 | Apparatus and method for controlling of vehicle |
CN105493524A (en) * | 2013-07-25 | 2016-04-13 | 康维达无线有限责任公司 | End-to-end M2M service layer sessions |
CN105340338B (en) * | 2013-07-26 | 2019-03-08 | 华为技术有限公司 | The method of multiple transmission powers is determined in cellular radio Communication system |
WO2015019234A1 (en) * | 2013-08-05 | 2015-02-12 | Universidade De Aveiro | Method and apparatus for multi-network communication in vehicular networks |
CN105453026A (en) | 2013-08-06 | 2016-03-30 | 苹果公司 | Auto-activating smart responses based on activities from remote devices |
US9508199B2 (en) * | 2013-08-09 | 2016-11-29 | Honda Motor Co., Ltd. | Mobile device communicating with motor vehicle system |
US9110561B2 (en) * | 2013-08-12 | 2015-08-18 | Apple Inc. | Context sensitive actions |
US9135756B2 (en) * | 2013-08-14 | 2015-09-15 | Hti Ip, L.L.C. | Providing communications between a vehicle control device and a user device via a head unit |
KR101509707B1 (en) * | 2013-08-26 | 2015-04-07 | 현대자동차 주식회사 | Vehicle control system and virtual electronic control unit development method |
US20150063329A1 (en) * | 2013-08-28 | 2015-03-05 | General Motors Llc | Selective vehicle wi-fi access |
GB2517732A (en) * | 2013-08-29 | 2015-03-04 | Sim & Pin Ltd | System for accessing data from multiple devices |
DE102013217259A1 (en) * | 2013-08-29 | 2015-03-05 | Bayerische Motoren Werke Aktiengesellschaft | Mode switching of a controller between diagnostic bus and external Ethernet connection |
KR101500130B1 (en) * | 2013-09-02 | 2015-03-06 | 현대자동차주식회사 | Apparatus for Controlling Vehicle installation on Steering wheel |
US20150074003A1 (en) * | 2013-09-06 | 2015-03-12 | Google Inc. | Synchronizing passenger check-in with the local caching of cloud-based media on a vehicle |
DE102013014878B3 (en) * | 2013-09-06 | 2014-10-30 | Audi Ag | Maintenance of motor vehicle control units by mobile phone |
DE102013015370A1 (en) * | 2013-09-13 | 2015-03-19 | Wabco Gmbh | Method for providing and transmitting data, in particular in connection with a vehicle |
GB201316386D0 (en) * | 2013-09-15 | 2013-10-30 | Tomtom Dev Germany Gmbh | Generating routes to optimise traffic flow |
CN104035947B (en) * | 2013-09-16 | 2016-04-13 | 腾讯科技(深圳)有限公司 | Point of interest recommend method and device, acquisition recommend method and the device of point of interest |
US9400564B2 (en) | 2013-09-17 | 2016-07-26 | Toyota Motor Engineering & Manufacturing North America, Inc. | Interactive vehicle window display system with a safe driving reminder system |
US9760698B2 (en) | 2013-09-17 | 2017-09-12 | Toyota Motor Sales, U.S.A., Inc. | Integrated wearable article for interactive vehicle control system |
US20150081133A1 (en) * | 2013-09-17 | 2015-03-19 | Toyota Motor Sales, U.S.A., Inc. | Gesture-based system enabling children to control some vehicle functions in a vehicle |
US9807196B2 (en) | 2013-09-17 | 2017-10-31 | Toyota Motor Sales, U.S.A. | Automated social network interaction system for a vehicle |
US9902266B2 (en) | 2013-09-17 | 2018-02-27 | Toyota Motor Engineering & Manufacturing North America, Inc. | Interactive vehicle window display system with personal convenience reminders |
JP6187086B2 (en) * | 2013-09-20 | 2017-08-30 | 富士通株式会社 | Information processing apparatus, communication method, and communication program |
EP2901400A4 (en) | 2013-09-23 | 2015-12-02 | Farmobile Llc | Farming data collection and exchange system |
US9906609B2 (en) | 2015-06-02 | 2018-02-27 | GeoFrenzy, Inc. | Geofence information delivery systems and methods |
WO2015043652A1 (en) * | 2013-09-27 | 2015-04-02 | Volkswagen Aktiengesellschaft | User interface and method for assisting a user with the operation of an operating unit |
US9642055B2 (en) * | 2013-09-27 | 2017-05-02 | Intel Corporation | Techniques for switching between wireless networks |
JP6191367B2 (en) | 2013-09-30 | 2017-09-06 | トヨタ自動車株式会社 | Safety information transmission method and safety information transmission system |
FR3011420A1 (en) * | 2013-09-30 | 2015-04-03 | Orange | IMPROVED MANAGEMENT OF NETWORK CONNECTIONS |
WO2015048995A1 (en) * | 2013-10-02 | 2015-04-09 | Nec Europe Ltd. | Integration of cellular and ieee 802.11 networks in vanets |
GB2519120B (en) | 2013-10-10 | 2017-10-18 | Abb Ltd | Methods and apparatus relating to measurement instruments |
WO2015057779A1 (en) * | 2013-10-15 | 2015-04-23 | Spectrum Bridge, Inc. | Systems and methods for determining and specifying spectrum availability for a predetermined travel route |
KR101556618B1 (en) * | 2013-10-16 | 2015-10-01 | 팅크웨어(주) | Apparatus and method for providing map data and system thereof |
US11349675B2 (en) * | 2013-10-18 | 2022-05-31 | Alcatel-Lucent Usa Inc. | Tamper-resistant and scalable mutual authentication for machine-to-machine devices |
LU92297B1 (en) * | 2013-10-22 | 2015-04-23 | Iee Sarl | Vehicle heating system |
KR101569510B1 (en) * | 2013-10-22 | 2015-11-17 | 네이버 주식회사 | Method for adaptive real-time transcoding, and streaming server thereof |
US9391891B2 (en) * | 2013-10-23 | 2016-07-12 | University Of Electronic Science And Technology Of China | Method for accessing internet via a vehicle network |
CN104602194B (en) | 2013-10-31 | 2019-04-12 | 国际商业机器公司 | Data transmission method and equipment in car networking |
US20150135271A1 (en) * | 2013-11-11 | 2015-05-14 | GM Global Technology Operations LLC | Device and method to enforce security tagging of embedded network communications |
US8897697B1 (en) | 2013-11-06 | 2014-11-25 | At&T Intellectual Property I, Lp | Millimeter-wave surface-wave communications |
US20150127192A1 (en) * | 2013-11-06 | 2015-05-07 | Hitachi, Ltd | Wireless vehicle control system |
US9693276B1 (en) * | 2013-11-25 | 2017-06-27 | Google Inc. | System and method for intelligent network connection selection |
US9282110B2 (en) | 2013-11-27 | 2016-03-08 | Cisco Technology, Inc. | Cloud-assisted threat defense for connected vehicles |
US10169051B2 (en) | 2013-12-05 | 2019-01-01 | Blue Yonder GmbH | Data processing device, processor core array and method for characterizing behavior of equipment under observation |
KR101558685B1 (en) * | 2013-12-09 | 2015-10-07 | 현대자동차주식회사 | System And Method for providing a Communication Service, and Vehicle supporting the same |
US9120365B2 (en) * | 2013-12-09 | 2015-09-01 | Ford Global Technologies, Llc | Automatic temperature override pattern recognition system |
GB2521377B (en) * | 2013-12-17 | 2018-09-19 | Jaguar Land Rover Ltd | A method and system for replaying a vehicle journey |
JP6433657B2 (en) * | 2013-12-18 | 2018-12-05 | 株式会社Nttドコモ | Wireless base station, mobile station, and wireless communication method |
US10929661B1 (en) * | 2013-12-19 | 2021-02-23 | Amazon Technologies, Inc. | System for user identification |
CN105794251B (en) * | 2013-12-20 | 2019-06-25 | 英特尔公司 | Using multiple Radio Access Networks, link performance is measured |
US9970768B2 (en) * | 2013-12-20 | 2018-05-15 | Fca Us Llc | Vehicle information/entertainment management system |
WO2015101070A1 (en) * | 2013-12-30 | 2015-07-09 | 北京奇虎科技有限公司 | Device and method for controlling electronic map |
US20160035152A1 (en) * | 2013-12-31 | 2016-02-04 | Agnik, Llc | Vehicle data mining based on vehicle onboard analysis and cloud-based distributed data stream mining algorithm |
EP3090235B1 (en) * | 2014-01-03 | 2024-06-19 | Google LLC | Input/output functions related to a portable device in an automotive environment |
US9300417B2 (en) * | 2014-01-06 | 2016-03-29 | GM Global Technology Operations LLC | Methods and apparatus for providing user-selectable preset options and associated data for a vehicle onboard computer system |
EP3358800B1 (en) | 2014-01-06 | 2021-10-20 | Argus Cyber Security Ltd | Bus watchman |
DE102014200226A1 (en) * | 2014-01-09 | 2015-07-09 | Bayerische Motoren Werke Aktiengesellschaft | Central communication unit of a motor vehicle |
US10580001B2 (en) * | 2014-01-13 | 2020-03-03 | Epona Llc | Vehicle transaction data communication using communication device |
US10469548B1 (en) * | 2014-01-15 | 2019-11-05 | Open Invention Network Llc | Transport communication |
EP3086515B1 (en) * | 2014-01-17 | 2019-03-13 | Huawei Technologies Co., Ltd. | Transmission method and transmission device for data packet |
KR20150087985A (en) * | 2014-01-23 | 2015-07-31 | 한국전자통신연구원 | Providing Apparatus and the Method of Safety Driving Information |
US9891064B2 (en) * | 2014-01-31 | 2018-02-13 | Aruba Networks, Inc. | Selection of a route based on prior user behavior or commercial interests |
US9826039B2 (en) * | 2014-02-04 | 2017-11-21 | Honeywell International Inc. | Configurable communication systems and methods for communication |
JP2015149578A (en) * | 2014-02-06 | 2015-08-20 | 株式会社日立製作所 | operation management apparatus |
CN105980839A (en) * | 2014-02-07 | 2016-09-28 | 英派尔科技开发有限公司 | Roadway infrastructure monitoring based on aggregated mobile vehicle communication parameters |
WO2015120318A1 (en) * | 2014-02-07 | 2015-08-13 | Recargo, Inc. | Presenting routing information for electric vehicles |
US10015049B2 (en) * | 2014-02-13 | 2018-07-03 | Sap Se | Configuration of network devices in a network |
TWI531197B (en) * | 2014-02-14 | 2016-04-21 | 天鉞電子股份有限公司 | Peer-to-peer connecting system, peer-to-peer connecting method and computer application program thereof |
KR20150096853A (en) * | 2014-02-17 | 2015-08-26 | 한국전자통신연구원 | Method for load balancing using multiple interface apparatus therefor |
US20190180118A1 (en) * | 2014-02-17 | 2019-06-13 | Ge Global Sourcing Llc | Locomotive imaging system and method |
CA2941641C (en) * | 2014-03-04 | 2022-10-25 | Sirius Xm Radio Inc. | Satellite provisioning of cell service |
US9533597B2 (en) * | 2014-03-05 | 2017-01-03 | Ford Global Technologies, Llc | Parameter identification offloading using cloud computing resources |
US9446678B2 (en) | 2014-03-05 | 2016-09-20 | Ford Global Technologies, Llc | Battery model with robustness to cloud-specific communication issues |
EP3114806B1 (en) * | 2014-03-06 | 2020-06-17 | Telefonaktiebolaget LM Ericsson (publ) | Network node, device and methods for providing an authentication module |
US9791485B2 (en) | 2014-03-10 | 2017-10-17 | Silver Spring Networks, Inc. | Determining electric grid topology via a zero crossing technique |
KR101601397B1 (en) * | 2014-03-13 | 2016-03-08 | 현대자동차주식회사 | Telematics system for wifi direct communicating using near field communication |
US9106887B1 (en) * | 2014-03-13 | 2015-08-11 | Wowza Media Systems, LLC | Adjusting encoding parameters at a mobile device based on a change in available network bandwidth |
US10015720B2 (en) | 2014-03-14 | 2018-07-03 | GoTenna, Inc. | System and method for digital communication between computing devices |
US20150195765A1 (en) * | 2014-03-25 | 2015-07-09 | Sanjay Bhardwaj | Method, Apparatus and System for Connected Automobiles |
EP2925025B1 (en) * | 2014-03-27 | 2016-03-23 | dSPACE digital signal processing and control engineering GmbH | Computer implemented method for implementing a Car2x application |
US10630774B2 (en) * | 2014-03-27 | 2020-04-21 | Hitachi Kokusai Electric Inc. | Intra-formation network system, intra-formation network management method, and management apparatus |
CN104980391B (en) * | 2014-04-01 | 2018-08-21 | 华为技术有限公司 | The transmission method and device of security message |
EP3418890A1 (en) * | 2014-04-02 | 2018-12-26 | Continental Automotive GmbH | Early logo display in a multiprocessor architecture |
DE102014206393A1 (en) * | 2014-04-03 | 2015-10-08 | Bayerische Motoren Werke Aktiengesellschaft | Method for resource management in a vehicle-based mobile radio device |
US10466657B2 (en) * | 2014-04-03 | 2019-11-05 | Honda Motor Co., Ltd. | Systems and methods for global adaptation of an implicit gesture control system |
US10409382B2 (en) | 2014-04-03 | 2019-09-10 | Honda Motor Co., Ltd. | Smart tutorial for gesture control system |
KR101573607B1 (en) * | 2014-04-04 | 2015-12-02 | 현대자동차주식회사 | System for providing personalized telematics service |
WO2015158606A1 (en) | 2014-04-14 | 2015-10-22 | Continental Teves Ag & Co. Ohg | Method of processing a vehicle-to-x message, vehicle-to-x communications module and storage medium |
WO2015157933A1 (en) * | 2014-04-16 | 2015-10-22 | Qualcomm Incorporated | System and methods for dynamic sim provisioning on a dual-sim wireless communication device |
DE102014106019A1 (en) * | 2014-04-29 | 2015-10-29 | Beckhoff Automation Gmbh | Network participants |
US9794888B2 (en) | 2014-05-05 | 2017-10-17 | Isco International, Llc | Method and apparatus for increasing performance of a communication link of a communication node |
US9532194B2 (en) | 2014-05-09 | 2016-12-27 | Cisco Technology, Inc. | Dynamic adjustment of wireless communication transmission rates |
US10320746B2 (en) * | 2014-05-12 | 2019-06-11 | Michael C. Wood | Computer security system and method based on user-intended final destination |
JP6305826B2 (en) * | 2014-05-13 | 2018-04-04 | アルパイン株式会社 | In-vehicle device and device authentication method |
US9767516B1 (en) * | 2014-05-20 | 2017-09-19 | State Farm Mutual Automobile Insurance Company | Driver feedback alerts based upon monitoring use of autonomous vehicle |
CN105100167B (en) * | 2014-05-20 | 2019-06-07 | 华为技术有限公司 | The processing method and car-mounted terminal of message |
US10383059B2 (en) * | 2014-05-23 | 2019-08-13 | General Motors Llc | Vehicle telematics unit power management |
GB2526619A (en) * | 2014-05-30 | 2015-12-02 | Vodafone Ip Licensing Ltd | Service provisioning |
US9715875B2 (en) | 2014-05-30 | 2017-07-25 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
CN106471570B (en) | 2014-05-30 | 2019-10-01 | 苹果公司 | Order single language input method more |
US10170123B2 (en) | 2014-05-30 | 2019-01-01 | Apple Inc. | Intelligent assistant for home automation |
US10887817B2 (en) * | 2014-06-04 | 2021-01-05 | International Mobile Iot Corp. | Location-based network system and location-based communication method |
US9635486B2 (en) * | 2014-06-10 | 2017-04-25 | Microsoft Technology Licensing, Llc | Network selection for a given application or context |
US9215228B1 (en) | 2014-06-17 | 2015-12-15 | Cisco Technology, Inc. | Authentication of devices having unequal capabilities |
US9330030B2 (en) * | 2014-06-24 | 2016-05-03 | Google Inc. | Bridge decoder for a vehicle infotainment system |
US9269328B2 (en) * | 2014-06-24 | 2016-02-23 | Google Inc. | Efficient frame rendering |
US9338493B2 (en) | 2014-06-30 | 2016-05-10 | Apple Inc. | Intelligent automated assistant for TV user interactions |
EP3164781B1 (en) * | 2014-07-02 | 2020-03-11 | Humavox Ltd. | Cloud based power management system for electronic devices |
TWI653598B (en) * | 2014-07-14 | 2019-03-11 | 鎮裕貿易股份有限公司 | Vehicle after-sales service system |
US9955412B2 (en) * | 2014-07-21 | 2018-04-24 | Lenovo (Singapore) Pte. Ltd. | Selecting a network |
US9875251B2 (en) | 2015-06-02 | 2018-01-23 | GeoFrenzy, Inc. | Geofence information delivery systems and methods |
US11240628B2 (en) | 2014-07-29 | 2022-02-01 | GeoFrenzy, Inc. | Systems and methods for decoupling and delivering geofence geometries to maps |
US12022352B2 (en) | 2014-07-29 | 2024-06-25 | GeoFrenzy, Inc. | Systems, methods and apparatus for geofence networks |
US10582333B2 (en) * | 2014-07-29 | 2020-03-03 | GeoFrenzy, Inc. | Systems and methods for geofence security |
US11838744B2 (en) | 2014-07-29 | 2023-12-05 | GeoFrenzy, Inc. | Systems, methods and apparatus for geofence networks |
WO2016018044A1 (en) * | 2014-07-31 | 2016-02-04 | Samsung Electronics Co., Ltd. | Wearable device and method of controlling the same |
US9389831B2 (en) * | 2014-08-06 | 2016-07-12 | Toyota Jidosha Kabushiki Kaisha | Sharing speech dialog capabilities of a vehicle |
US9501927B2 (en) * | 2014-08-20 | 2016-11-22 | Trapeze Software Ulc | Method and system for queue-based processing of RFID locating and sequencing events |
US9918001B2 (en) * | 2014-08-21 | 2018-03-13 | Toyota Motor Sales, U.S.A., Inc. | Crowd sourcing exterior vehicle images of traffic conditions |
US9767065B2 (en) * | 2014-08-21 | 2017-09-19 | GM Global Technology Operations LLC | Dynamic vehicle bus subscription |
EP3187023B1 (en) * | 2014-08-29 | 2021-02-17 | Intel Corporation | Method for a wireless network bridge |
US10148485B2 (en) | 2014-09-03 | 2018-12-04 | Honeywell International Inc. | Apparatus and method for on-process migration of industrial control and automation system across disparate network types |
US10986029B2 (en) | 2014-09-08 | 2021-04-20 | Liveu Ltd. | Device, system, and method of data transport with selective utilization of a single link or multiple links |
US10411958B2 (en) * | 2014-09-08 | 2019-09-10 | Intel Corporation | Automatic device configuration |
US9380044B2 (en) | 2014-09-10 | 2016-06-28 | Cisco Technology, Inc. | Supporting differentiated secure communications among heterogeneous electronic devices |
US9317617B2 (en) * | 2014-09-12 | 2016-04-19 | E-Lead Electronic Co., Ltd. | Trip plan sharing and matching method |
US9768833B2 (en) | 2014-09-15 | 2017-09-19 | At&T Intellectual Property I, L.P. | Method and apparatus for sensing a condition in a transmission medium of electromagnetic waves |
US10063280B2 (en) | 2014-09-17 | 2018-08-28 | At&T Intellectual Property I, L.P. | Monitoring and mitigating conditions in a communication network |
RU2608477C2 (en) * | 2014-09-22 | 2017-01-18 | Общество с ограниченной ответственностью "Оригинал Софт" | Method of automotive device with wi-fi module connection and automatic adjustment |
JP5765474B1 (en) * | 2014-09-24 | 2015-08-19 | 富士ゼロックス株式会社 | Information processing apparatus and information processing program |
EP3197730B1 (en) * | 2014-09-25 | 2020-02-19 | Tower-Sec Ltd. | Vehicle correlation system for cyber attacks detection and method thereof |
US9615269B2 (en) | 2014-10-02 | 2017-04-04 | At&T Intellectual Property I, L.P. | Method and apparatus that provides fault tolerance in a communication network |
US9685992B2 (en) | 2014-10-03 | 2017-06-20 | At&T Intellectual Property I, L.P. | Circuit panel network and methods thereof |
DE102014014601A1 (en) * | 2014-10-07 | 2016-04-07 | Audi Ag | Method for operating a motor vehicle and motor vehicle |
WO2016054767A1 (en) * | 2014-10-08 | 2016-04-14 | 华为技术有限公司 | Information interaction method between on-board terminals, and on-board terminal |
JP6331947B2 (en) * | 2014-10-09 | 2018-05-30 | トヨタ自動車株式会社 | Wireless communication apparatus and communication method |
US10027573B2 (en) | 2014-10-10 | 2018-07-17 | At&T Intellectual Property I, L.P. | Centralized radio access network virtualization mechanism |
US9503189B2 (en) | 2014-10-10 | 2016-11-22 | At&T Intellectual Property I, L.P. | Method and apparatus for arranging communication sessions in a communication system |
US9973299B2 (en) | 2014-10-14 | 2018-05-15 | At&T Intellectual Property I, L.P. | Method and apparatus for adjusting a mode of communication in a communication network |
US20160113043A1 (en) * | 2014-10-15 | 2016-04-21 | Lear Corporation | Vehicle Gateway Module Configured to Provide Wireless Hotspot |
US9653770B2 (en) | 2014-10-21 | 2017-05-16 | At&T Intellectual Property I, L.P. | Guided wave coupler, coupling module and methods for use therewith |
US9312919B1 (en) | 2014-10-21 | 2016-04-12 | At&T Intellectual Property I, Lp | Transmission device with impairment compensation and methods for use therewith |
US9780834B2 (en) | 2014-10-21 | 2017-10-03 | At&T Intellectual Property I, L.P. | Method and apparatus for transmitting electromagnetic waves |
US9627768B2 (en) | 2014-10-21 | 2017-04-18 | At&T Intellectual Property I, L.P. | Guided-wave transmission device with non-fundamental mode propagation and methods for use therewith |
US9769020B2 (en) | 2014-10-21 | 2017-09-19 | At&T Intellectual Property I, L.P. | Method and apparatus for responding to events affecting communications in a communication network |
US9577306B2 (en) | 2014-10-21 | 2017-02-21 | At&T Intellectual Property I, L.P. | Guided-wave transmission device and methods for use therewith |
US9667437B2 (en) * | 2014-10-23 | 2017-05-30 | Verizon Patent And Licensing Inc. | Billing multiple packet flows associated with a client router |
US9478076B2 (en) | 2014-10-24 | 2016-10-25 | Telogis, Inc. | Systems and methods for executing custom fleet vehicle management scripts |
DE102014221977A1 (en) * | 2014-10-28 | 2016-04-28 | Robert Bosch Gmbh | Method and device for storing data in a motor vehicle |
CN106471826B (en) * | 2014-10-29 | 2019-10-25 | 宝马股份公司 | For supporting method, remote communication server and the base station of vehicle communication in cellular networks |
DE102014116172A1 (en) * | 2014-11-06 | 2016-05-12 | Dr. Ing. H.C. F. Porsche Aktiengesellschaft | Data transmission unit for a vehicle |
EP3023961B1 (en) * | 2014-11-18 | 2017-05-03 | Fujitsu Limited | Methods and devices for controlling vehicular wireless communications |
US10243784B2 (en) | 2014-11-20 | 2019-03-26 | At&T Intellectual Property I, L.P. | System for generating topology information and methods thereof |
US9800327B2 (en) | 2014-11-20 | 2017-10-24 | At&T Intellectual Property I, L.P. | Apparatus for controlling operations of a communication device and methods thereof |
US9544006B2 (en) | 2014-11-20 | 2017-01-10 | At&T Intellectual Property I, L.P. | Transmission device with mode division multiplexing and methods for use therewith |
US10340573B2 (en) | 2016-10-26 | 2019-07-02 | At&T Intellectual Property I, L.P. | Launcher with cylindrical coupling device and methods for use therewith |
US10009067B2 (en) | 2014-12-04 | 2018-06-26 | At&T Intellectual Property I, L.P. | Method and apparatus for configuring a communication interface |
US9742462B2 (en) | 2014-12-04 | 2017-08-22 | At&T Intellectual Property I, L.P. | Transmission medium and communication interfaces and methods for use therewith |
US9461706B1 (en) | 2015-07-31 | 2016-10-04 | At&T Intellectual Property I, Lp | Method and apparatus for exchanging communication signals |
US9954287B2 (en) | 2014-11-20 | 2018-04-24 | At&T Intellectual Property I, L.P. | Apparatus for converting wireless signals and electromagnetic waves and methods thereof |
US9997819B2 (en) | 2015-06-09 | 2018-06-12 | At&T Intellectual Property I, L.P. | Transmission medium and method for facilitating propagation of electromagnetic waves via a core |
US9773354B2 (en) * | 2014-12-11 | 2017-09-26 | Hyundai Motor Company | Terminal mounted in vehicle, control method thereof, data center and control method thereof |
KR101673305B1 (en) * | 2014-12-11 | 2016-11-22 | 현대자동차주식회사 | Head unit for providing streaming service between different device and streaming control method the same, and computer-readable medium storing program for executing the same |
EP3035268A1 (en) * | 2014-12-15 | 2016-06-22 | Mastercard International, Inc. | Payment system with reduced user interaction |
US9668111B2 (en) * | 2014-12-19 | 2017-05-30 | Infobank Corp. | Terminal for contents sharing, an operating method thereof, and a vehicle information providing terminal |
FR3030991B1 (en) * | 2014-12-22 | 2018-03-23 | Commissariat A L'energie Atomique Et Aux Energies Alternatives | NETWORK OF MEASURING DEVICES COMMUNICATING BY RADIO LINK |
US9781000B1 (en) * | 2014-12-22 | 2017-10-03 | EMC IP Holding Company LLC | Storage mobility using locator-identifier separation protocol |
CN105812404A (en) * | 2014-12-29 | 2016-07-27 | 罗伯特·博世有限公司 | Data upgrading method and device for vehicle diagnosis equipment and vehicle diagnosis equipment |
US10367869B2 (en) * | 2014-12-30 | 2019-07-30 | Ford Global Technologies, Llc | Remote vehicle control and operation |
US10500955B2 (en) * | 2014-12-30 | 2019-12-10 | Visteon Global Technologies, Inc. | Automatic upgrade of a vehicle-based processor based on a physical component change |
US9958278B2 (en) * | 2015-01-14 | 2018-05-01 | Telenav, Inc. | Navigation system with scalable display mechanism and method of operation thereof |
US9472098B2 (en) * | 2015-01-15 | 2016-10-18 | International Business Machines Corporation | Vehicle-based abnormal travel event detecting and reporting |
US10015057B2 (en) * | 2015-01-26 | 2018-07-03 | Ciena Corporation | Representative bandwidth calculation systems and methods in a network |
US9446770B2 (en) * | 2015-01-29 | 2016-09-20 | GM Global Technology Operations LLC | Method and apparatus for monitoring a rear passenger seating area of a vehicle |
US9695764B1 (en) * | 2015-02-10 | 2017-07-04 | Brunswick Corporation | Multi-fuel marine engine control system |
US9838480B2 (en) * | 2015-02-18 | 2017-12-05 | Visa International Service Association | Systems and methods implementing a communication protocol for data communication with a vehicle |
US9876570B2 (en) | 2015-02-20 | 2018-01-23 | At&T Intellectual Property I, Lp | Guided-wave transmission device with non-fundamental mode propagation and methods for use therewith |
US10127375B2 (en) | 2015-03-07 | 2018-11-13 | Protegrity Corporation | Enforcing trusted application settings for shared code libraries |
US9721566B2 (en) | 2015-03-08 | 2017-08-01 | Apple Inc. | Competing devices responding to voice triggers |
US9886953B2 (en) | 2015-03-08 | 2018-02-06 | Apple Inc. | Virtual assistant activation |
US10587639B2 (en) * | 2015-03-10 | 2020-03-10 | Ca, Inc. | Assessing trust of components in systems |
US11736468B2 (en) * | 2015-03-16 | 2023-08-22 | Assa Abloy Ab | Enhanced authorization |
US10725758B2 (en) * | 2015-03-17 | 2020-07-28 | Automotive Data Solutions, Inc. | Telematics system |
US9749013B2 (en) | 2015-03-17 | 2017-08-29 | At&T Intellectual Property I, L.P. | Method and apparatus for reducing attenuation of electromagnetic waves guided by a transmission medium |
DE102015204924B4 (en) * | 2015-03-18 | 2022-05-25 | Röchling Automotive SE & Co. KG | LIN network |
US9814817B2 (en) * | 2015-03-27 | 2017-11-14 | Fresenius Medical Care Holdings, Inc. | Adjusting sound on a medical device |
US10013816B2 (en) * | 2015-03-27 | 2018-07-03 | Drew Technologies, Inc. | Vehicle diagnostic system and method |
US10225795B2 (en) | 2015-04-07 | 2019-03-05 | At&T Intellectual Property I, L.P. | Resource-sensitive token-based access point selection |
US9973561B2 (en) * | 2015-04-17 | 2018-05-15 | International Business Machines Corporation | Conferencing based on portable multifunction devices |
US9705561B2 (en) | 2015-04-24 | 2017-07-11 | At&T Intellectual Property I, L.P. | Directional coupling device and methods for use therewith |
US10224981B2 (en) | 2015-04-24 | 2019-03-05 | At&T Intellectual Property I, Lp | Passive electrical coupling device and methods for use therewith |
US9793954B2 (en) | 2015-04-28 | 2017-10-17 | At&T Intellectual Property I, L.P. | Magnetic coupling device and methods for use therewith |
DE102015208242A1 (en) * | 2015-05-05 | 2016-11-10 | Volkswagen Aktiengesellschaft | Vehicle, apparatus, methods and computer programs for controlling traffic and data transmission to vehicle components |
US9748626B2 (en) | 2015-05-14 | 2017-08-29 | At&T Intellectual Property I, L.P. | Plurality of cables having different cross-sectional shapes which are bundled together to form a transmission medium |
US9490869B1 (en) | 2015-05-14 | 2016-11-08 | At&T Intellectual Property I, L.P. | Transmission medium having multiple cores and methods for use therewith |
EP3295653A1 (en) | 2015-05-14 | 2018-03-21 | Airbiquity Inc. | Centralized management of mobile-assisted motor vehicle software upgrading and vehicle data analytics |
US9871282B2 (en) | 2015-05-14 | 2018-01-16 | At&T Intellectual Property I, L.P. | At least one transmission medium having a dielectric surface that is covered at least in part by a second dielectric |
US10650940B2 (en) | 2015-05-15 | 2020-05-12 | At&T Intellectual Property I, L.P. | Transmission medium having a conductive material and methods for use therewith |
US10460227B2 (en) | 2015-05-15 | 2019-10-29 | Apple Inc. | Virtual assistant in a communication session |
US9894491B2 (en) | 2015-05-22 | 2018-02-13 | Ford Global Technologies, Llc | Context-based wireless network link access prioritization system |
US9936337B2 (en) | 2015-05-23 | 2018-04-03 | Square, Inc. | Tuning a NFC antenna of a device |
US10200824B2 (en) | 2015-05-27 | 2019-02-05 | Apple Inc. | Systems and methods for proactively identifying and surfacing relevant content on a touch-sensitive device |
US9917341B2 (en) | 2015-05-27 | 2018-03-13 | At&T Intellectual Property I, L.P. | Apparatus and method for launching electromagnetic waves and for modifying radial dimensions of the propagating electromagnetic waves |
CN107430394B (en) | 2015-05-29 | 2020-11-06 | 华为技术有限公司 | Method, server, mobile terminal and device for data interaction with vehicle machine |
US9866309B2 (en) | 2015-06-03 | 2018-01-09 | At&T Intellectual Property I, Lp | Host node device and methods for use therewith |
US9912381B2 (en) | 2015-06-03 | 2018-03-06 | At&T Intellectual Property I, Lp | Network termination and methods for use therewith |
US10812174B2 (en) | 2015-06-03 | 2020-10-20 | At&T Intellectual Property I, L.P. | Client node device and methods for use therewith |
JP6464932B2 (en) * | 2015-06-05 | 2019-02-06 | 株式会社デンソー | Relay device |
US11023878B1 (en) * | 2015-06-05 | 2021-06-01 | Square, Inc. | Apparatuses, methods, and systems for transmitting payment proxy information |
KR102402688B1 (en) * | 2015-06-08 | 2022-05-26 | 엘지이노텍 주식회사 | Antenna device |
US10230750B2 (en) * | 2015-06-08 | 2019-03-12 | Securboration, Inc. | Secure computing environment |
US9913139B2 (en) | 2015-06-09 | 2018-03-06 | At&T Intellectual Property I, L.P. | Signal fingerprinting for authentication of communicating devices |
US9820146B2 (en) | 2015-06-12 | 2017-11-14 | At&T Intellectual Property I, L.P. | Method and apparatus for authentication and identity management of communicating devices |
US9646493B2 (en) | 2015-06-19 | 2017-05-09 | International Business Machines Corporation | Management of moving objects |
US10013883B2 (en) * | 2015-06-22 | 2018-07-03 | Digital Ally, Inc. | Tracking and analysis of drivers within a fleet of vehicles |
US9815371B2 (en) * | 2015-06-23 | 2017-11-14 | Yazaki Corporation | Information providing apparatus for vehicle |
US9763089B2 (en) * | 2015-06-23 | 2017-09-12 | International Business Machines Corporation | Protecting sensitive data in a security area |
JP6428502B2 (en) * | 2015-06-24 | 2018-11-28 | 株式会社デンソー | Relay device |
US9509415B1 (en) | 2015-06-25 | 2016-11-29 | At&T Intellectual Property I, L.P. | Methods and apparatus for inducing a fundamental wave mode on a transmission medium |
US9865911B2 (en) | 2015-06-25 | 2018-01-09 | At&T Intellectual Property I, L.P. | Waveguide system for slot radiating first electromagnetic waves that are combined into a non-fundamental wave mode second electromagnetic wave on a transmission medium |
US9640850B2 (en) | 2015-06-25 | 2017-05-02 | At&T Intellectual Property I, L.P. | Methods and apparatus for inducing a non-fundamental wave mode on a transmission medium |
CN105116817A (en) * | 2015-06-26 | 2015-12-02 | 小米科技有限责任公司 | Balance car management method and device |
US10200480B2 (en) * | 2015-06-29 | 2019-02-05 | Huawei Technologies Co., Ltd. | System and method for connectivity management |
US10798114B2 (en) | 2015-06-29 | 2020-10-06 | Argus Cyber Security Ltd. | System and method for consistency based anomaly detection in an in-vehicle communication network |
US11165851B2 (en) * | 2015-06-29 | 2021-11-02 | Argus Cyber Security Ltd. | System and method for providing security to a communication network |
US11115433B2 (en) | 2015-06-29 | 2021-09-07 | Argus Cyber Security Ltd. | System and method for content based anomaly detection in an in-vehicle communication network |
US20160378747A1 (en) | 2015-06-29 | 2016-12-29 | Apple Inc. | Virtual assistant for media playback |
CA2991289C (en) * | 2015-06-30 | 2020-07-28 | Laird Technologies Inc. | Monitoring and controlling of distributed machines |
EP3318456B1 (en) * | 2015-07-02 | 2021-09-22 | Sony Group Corporation | Vehicle control device, vehicle control method, and program |
US10749734B2 (en) | 2015-07-07 | 2020-08-18 | International Business Machines Corporation | Management of events and moving objects |
US9598009B2 (en) | 2015-07-09 | 2017-03-21 | Nissan North America, Inc. | Vehicle intersection warning system and method with false alarm suppression |
US9725037B2 (en) * | 2015-07-09 | 2017-08-08 | Nissan North America, Inc. | Message occlusion detection system and method in a vehicle-to-vehicle communication network |
DE102015212951B4 (en) * | 2015-07-10 | 2021-10-28 | Bayerische Motoren Werke Aktiengesellschaft | Communication system for units and control units of a vehicle and vehicle comprising the communication system |
US10178176B2 (en) * | 2015-07-10 | 2019-01-08 | Carnegie Mellon University | Methods and systems for managing network communications to and from a vehicle network |
US9853342B2 (en) | 2015-07-14 | 2017-12-26 | At&T Intellectual Property I, L.P. | Dielectric transmission medium connector and methods for use therewith |
US9628116B2 (en) | 2015-07-14 | 2017-04-18 | At&T Intellectual Property I, L.P. | Apparatus and methods for transmitting wireless signals |
US10205655B2 (en) | 2015-07-14 | 2019-02-12 | At&T Intellectual Property I, L.P. | Apparatus and methods for communicating utilizing an antenna array and multiple communication paths |
US9882257B2 (en) | 2015-07-14 | 2018-01-30 | At&T Intellectual Property I, L.P. | Method and apparatus for launching a wave mode that mitigates interference |
US10148016B2 (en) | 2015-07-14 | 2018-12-04 | At&T Intellectual Property I, L.P. | Apparatus and methods for communicating utilizing an antenna array |
US9847566B2 (en) | 2015-07-14 | 2017-12-19 | At&T Intellectual Property I, L.P. | Method and apparatus for adjusting a field of a signal to mitigate interference |
US10044409B2 (en) | 2015-07-14 | 2018-08-07 | At&T Intellectual Property I, L.P. | Transmission medium and methods for use therewith |
US10090606B2 (en) | 2015-07-15 | 2018-10-02 | At&T Intellectual Property I, L.P. | Antenna system with dielectric array and methods for use therewith |
US9912027B2 (en) | 2015-07-23 | 2018-03-06 | At&T Intellectual Property I, L.P. | Method and apparatus for exchanging communication signals |
US9948333B2 (en) | 2015-07-23 | 2018-04-17 | At&T Intellectual Property I, L.P. | Method and apparatus for wireless communications to mitigate interference |
US9749053B2 (en) | 2015-07-23 | 2017-08-29 | At&T Intellectual Property I, L.P. | Node device, repeater and methods for use therewith |
US9871283B2 (en) | 2015-07-23 | 2018-01-16 | At&T Intellectual Property I, Lp | Transmission medium having a dielectric core comprised of plural members connected by a ball and socket configuration |
US9973935B2 (en) * | 2015-07-24 | 2018-05-15 | Parallel Wireless, Inc. | SON-controlled DFS |
JPWO2017017883A1 (en) * | 2015-07-28 | 2018-05-10 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | Terminal device and communication method |
KR102583850B1 (en) * | 2015-07-28 | 2023-10-04 | 삼성전자주식회사 | Apparatus and method for transmitting/receiving signal in mesh network supporting conncetion scheme |
US9735833B2 (en) | 2015-07-31 | 2017-08-15 | At&T Intellectual Property I, L.P. | Method and apparatus for communications management in a neighborhood network |
US9967173B2 (en) | 2015-07-31 | 2018-05-08 | At&T Intellectual Property I, L.P. | Method and apparatus for authentication and identity management of communicating devices |
US10775180B2 (en) * | 2015-08-03 | 2020-09-15 | Here Global B.V. | Method and apparatus for syncing an embedded system with plurality of devices |
US10614640B2 (en) | 2015-08-05 | 2020-04-07 | EZ Lynk SEZC | System and method for real time wireless ECU monitoring and reprogramming |
US10621796B2 (en) | 2015-08-05 | 2020-04-14 | EZ Lynk SEZC | System and method for real time wireless ECU monitoring and reprogramming |
US11430273B2 (en) | 2015-08-05 | 2022-08-30 | EZ Lynk SEZC | Apparatus and method for remote ELD monitoring and ECU reprogramming |
US11210871B2 (en) | 2015-08-05 | 2021-12-28 | EZ Lynk SEZC | System and method for remote emissions control unit monitoring and reprogramming |
US20170054596A1 (en) * | 2015-08-18 | 2017-02-23 | Klas Technologies Limited | Integrated internet access router |
JP6646248B2 (en) * | 2015-08-19 | 2020-02-14 | ヤマハ株式会社 | Audio system, audio equipment and audio system reconnection method |
US20170054204A1 (en) * | 2015-08-21 | 2017-02-23 | Laird Technologies, Inc. | V2x antenna systems |
TWI581646B (en) * | 2015-08-27 | 2017-05-01 | 鴻海精密工業股份有限公司 | A method with dynamic frequency selection and an electronic device |
JP6994643B2 (en) * | 2015-08-28 | 2022-01-14 | パナソニックIpマネジメント株式会社 | Information terminal control method and information terminal |
DE102015011920A1 (en) * | 2015-09-03 | 2017-03-09 | Continental Automotive Gmbh | Method for checking the data integrity of a C2C transmission |
KR102425517B1 (en) * | 2015-09-04 | 2022-07-27 | 삼성전자주식회사 | Apparatus and method for uploading data in mobile communication system supporting a plurality of radio access interfaces |
RU2693908C1 (en) * | 2015-09-04 | 2019-07-05 | ФОРД ГЛОУБАЛ ТЕКНОЛОДЖИЗ, ЭлЭлСи | System and method for contacting with people occupying place of remote vehicle using dsrc |
US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
US10331312B2 (en) | 2015-09-08 | 2019-06-25 | Apple Inc. | Intelligent automated assistant in a media environment |
US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
US10740384B2 (en) | 2015-09-08 | 2020-08-11 | Apple Inc. | Intelligent automated assistant for media search and playback |
US9904535B2 (en) | 2015-09-14 | 2018-02-27 | At&T Intellectual Property I, L.P. | Method and apparatus for distributing software |
EP3350779A1 (en) * | 2015-09-14 | 2018-07-25 | Vinli, Inc. | Cloud integrated vehicle platform |
JP6406193B2 (en) * | 2015-09-17 | 2018-10-17 | 株式会社デンソー | Communication device |
US10482440B1 (en) | 2015-09-18 | 2019-11-19 | Square, Inc. | Simulating NFC experience |
US9756024B2 (en) * | 2015-09-18 | 2017-09-05 | Trillium Incorporated | Computer-implemented cryptographic method for improving a computer network, and terminal, system and computer-readable medium for the same |
US10084782B2 (en) * | 2015-09-21 | 2018-09-25 | Early Warning Services, Llc | Authenticator centralization and protection |
US9591676B1 (en) * | 2015-09-22 | 2017-03-07 | Veniam, Inc. | Systems and methods for managing mobility in a network of moving things |
US9641391B2 (en) | 2015-09-22 | 2017-05-02 | Veniam, Inc. | Communication network of moving things |
US9743451B2 (en) * | 2015-09-22 | 2017-08-22 | Veniam, Inc. | Integrated communication network for a network of moving things |
US10194264B2 (en) * | 2015-09-22 | 2019-01-29 | Veniam, Inc. | Systems and methods for collecting sensor data in a network of moving things |
US9648446B2 (en) * | 2015-09-22 | 2017-05-09 | Veniam, Inc. | Systems and methods for shipping management in a network of moving things |
US9610853B1 (en) * | 2015-09-24 | 2017-04-04 | Ford Global Technologies, Llc | Identification of acceptable vehicle charge stations |
US10861003B1 (en) | 2015-09-24 | 2020-12-08 | Square, Inc. | Near field communication device coupling system |
US11397801B2 (en) * | 2015-09-25 | 2022-07-26 | Argus Cyber Security Ltd. | System and method for controlling access to an in-vehicle communication network |
FR3041845B1 (en) * | 2015-09-25 | 2018-10-12 | Eliocity | ELECTRONIC DEVICE CLEAN TO BE CONNECTED TO A VEHICLE NETWORK, AND METHOD OF TRANSMITTING MESSAGES IMPLEMENTED BY SUCH AN ELECTRONIC DEVICE |
US9769128B2 (en) | 2015-09-28 | 2017-09-19 | At&T Intellectual Property I, L.P. | Method and apparatus for encryption of communications over a network |
US10057022B2 (en) * | 2015-09-28 | 2018-08-21 | Yazaki Corporation | Method for controlling access to an in-vehicle wireless network |
DE102015218800A1 (en) | 2015-09-29 | 2017-03-30 | Continental Automotive Gmbh | Communication system for V2X communication |
US11587559B2 (en) | 2015-09-30 | 2023-02-21 | Apple Inc. | Intelligent device identification |
US9729197B2 (en) | 2015-10-01 | 2017-08-08 | At&T Intellectual Property I, L.P. | Method and apparatus for communicating network management traffic over a network |
US9876264B2 (en) | 2015-10-02 | 2018-01-23 | At&T Intellectual Property I, Lp | Communication system, guided wave switch and methods for use therewith |
CN108028794B (en) * | 2015-10-05 | 2021-02-02 | 日立汽车系统株式会社 | Vehicle-mounted gateway device |
US9604541B1 (en) * | 2015-10-06 | 2017-03-28 | Samsung Electronics Co., Ltd. | System and method for customizing a vehicle operating environment |
US9723473B2 (en) * | 2015-10-14 | 2017-08-01 | Toyota Jidosha Kabushiki Kaisha | Millimeter wave communication system |
US10355367B2 (en) | 2015-10-16 | 2019-07-16 | At&T Intellectual Property I, L.P. | Antenna structure for exchanging wireless signals |
US10524108B2 (en) * | 2015-10-19 | 2019-12-31 | Qualomm Incorporated | D2D communication for eMTC design considerations |
WO2017070609A1 (en) | 2015-10-23 | 2017-04-27 | Yazaki Corporation | Limiting distraction from in-vehicle portable devices |
CN106612211B (en) * | 2015-10-23 | 2020-02-21 | 华为技术有限公司 | Path detection method, controller and network equipment in VxLAN |
US9900315B2 (en) * | 2015-10-30 | 2018-02-20 | GM Global Technology Operations LLC | Enabling and inhibiting synchronization of privacy settings |
US9693229B2 (en) * | 2015-11-05 | 2017-06-27 | International Business Machines Corporation | Logical subscriber identification module (SIM) |
US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
EP3374945A1 (en) * | 2015-11-09 | 2018-09-19 | Innogy Innovation GmbH | System and method for transporting an object |
US10956666B2 (en) | 2015-11-09 | 2021-03-23 | Apple Inc. | Unconventional virtual assistant interactions |
US9741183B2 (en) * | 2015-11-10 | 2017-08-22 | Veniam, Inc | Systems and methods for optimizing data gathering in a network of moving things |
KR102358009B1 (en) | 2015-11-10 | 2022-02-04 | 삼성전자주식회사 | Beam projection device and method of projecting beam using beam projection device |
KR101774661B1 (en) * | 2015-11-11 | 2017-09-04 | 현대자동차주식회사 | Apparatus and method for adjusting driving position of driver |
US10692126B2 (en) | 2015-11-17 | 2020-06-23 | Nio Usa, Inc. | Network-based system for selling and servicing cars |
US9693297B2 (en) | 2015-11-19 | 2017-06-27 | Veniam, Inc. | Systems and methods for delay tolerant networking in a network of moving things, for example including a network of autonomous vehicles |
US20170214744A1 (en) * | 2015-11-30 | 2017-07-27 | Veniam, Inc. | Systems and methods for adapting a network of moving things, for example including autonomous vehicles, based on user feedback |
US9537914B1 (en) * | 2015-12-01 | 2017-01-03 | International Business Machines Corporation | Vehicle domain multi-level parallel buffering and context-based streaming data pre-processing system |
US10630723B1 (en) | 2015-12-03 | 2020-04-21 | United Services Automobile Association (Usaa) | Determining policy characteristics based on route similarity |
SE541941C2 (en) * | 2015-12-04 | 2020-01-07 | Icomera Ab | Dynamic traffic shaping for communication networks in moving vehicles, such as trains |
WO2017094190A1 (en) * | 2015-12-04 | 2017-06-08 | 三菱電機株式会社 | Transfer control apparatus, vehicle and transfer control method |
US9998892B2 (en) * | 2015-12-11 | 2018-06-12 | GM Global Technology Operations LLC | Determining vehicle user location following a collision event |
US10445603B1 (en) * | 2015-12-11 | 2019-10-15 | Lytx, Inc. | System for capturing a driver image |
JP6423402B2 (en) * | 2015-12-16 | 2018-11-14 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | Security processing method and server |
WO2017104112A1 (en) | 2015-12-16 | 2017-06-22 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ | Security processing method and server |
US20180262401A1 (en) * | 2015-12-17 | 2018-09-13 | Nebulae LLC | Systems and Methods for Selection of Parent Nodes in a Network |
US10482419B2 (en) * | 2015-12-17 | 2019-11-19 | Tive, Inc. | Sensor device having configuration changes |
EP3391681B1 (en) * | 2015-12-17 | 2021-10-06 | OnBoard Security, Inc. | Secure vehicle communication system |
US20180350227A1 (en) * | 2015-12-17 | 2018-12-06 | Tive, Inc. | Sensor device having spectrum monitoring |
US10867508B2 (en) * | 2015-12-17 | 2020-12-15 | Tive, Inc. | Multi-sensor electronic device with wireless connectivity and sensing as a service platform and web application |
US20170176192A1 (en) * | 2015-12-22 | 2017-06-22 | Veniam, Inc. | Systems and methods to extrapolate high-value data from a network of moving things, for example including a network of autonomous vehicles |
US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US10701059B2 (en) | 2015-12-29 | 2020-06-30 | Morphotrust Usa, Llc | Onboard vehicle digital identification transmission |
US10063904B2 (en) * | 2015-12-30 | 2018-08-28 | Voxx International Corporation | Interchangeable rear seat infotainment system |
US11715025B2 (en) | 2015-12-30 | 2023-08-01 | Nutanix, Inc. | Method for forecasting distributed resource utilization in a virtualization environment |
US10375106B1 (en) * | 2016-01-13 | 2019-08-06 | National Technology & Engineering Solutions Of Sandia, Llc | Backplane filtering and firewalls |
US10417918B2 (en) * | 2016-01-20 | 2019-09-17 | Honeywell International Inc. | Methods and systems to assist in a search and rescue mission |
US9949155B2 (en) | 2016-01-22 | 2018-04-17 | Panasonic Avionics Corporation | Methods and systems for managing bandwidth for user devices on a transportation vehicle |
CN105744636B (en) * | 2016-01-22 | 2017-09-22 | 广州极飞科技有限公司 | Earth station and earth station and the communication means of unmanned plane |
KR20170089328A (en) * | 2016-01-26 | 2017-08-03 | 삼성전자주식회사 | Automotive control systems and method for operating thereof |
WO2017130292A1 (en) * | 2016-01-26 | 2017-08-03 | 株式会社ソラコム | Server, mobile terminal, and program |
EP3409043A1 (en) * | 2016-01-28 | 2018-12-05 | Telefonaktiebolaget LM Ericsson (publ) | Oss node, network node and methods performed therein |
SE540352C2 (en) * | 2016-01-29 | 2018-07-24 | Icomera Ab | Wireless communication system and method for trains and other vehicles using trackside base stations |
US9843500B2 (en) | 2016-01-29 | 2017-12-12 | International Business Machines Corporation | Accurate mobile traffic information acquisition with minimal transmission cost and optional V2V extension |
CN105592165B (en) * | 2016-02-02 | 2019-05-07 | 中国科学院深圳先进技术研究院 | A kind of network system connecting interior controller |
US10250925B2 (en) * | 2016-02-11 | 2019-04-02 | Motorola Mobility Llc | Determining a playback rate of media for a requester |
US10003951B2 (en) | 2016-02-25 | 2018-06-19 | Sirqul, Inc. | Automated mobile device onboard camera recording |
US9776630B2 (en) | 2016-02-29 | 2017-10-03 | Nissan North America, Inc. | Vehicle operation based on converging time |
US10706645B1 (en) * | 2016-03-09 | 2020-07-07 | Drew Technologies, Inc. | Remote diagnostic system and method |
DE102016002944C5 (en) * | 2016-03-11 | 2022-08-04 | Audi Ag | Control device and method for coupling an antenna arrangement of a motor vehicle with at least one vehicle component |
CN105657777B (en) * | 2016-03-14 | 2018-11-20 | 西安电子科技大学 | Design of Routing Protocol method based on link-quality and node transfer capability |
US10154048B2 (en) * | 2016-03-18 | 2018-12-11 | Qualcomm Incorporated | Methods and systems for location-based authentication using neighboring sensors |
US9942861B2 (en) | 2016-03-21 | 2018-04-10 | At&T Mobility Ii Llc | Facilitation of link loss reduction for radio antennas |
US20190110176A1 (en) * | 2016-03-23 | 2019-04-11 | Ford Global Technologies, Llc | Articulated vehicle communication extension |
US9707913B1 (en) | 2016-03-23 | 2017-07-18 | Toyota Motor Enegineering & Manufacturing North America, Inc. | System and method for determining optimal vehicle component settings |
US10275955B2 (en) | 2016-03-25 | 2019-04-30 | Qualcomm Incorporated | Methods and systems for utilizing information collected from multiple sensors to protect a vehicle from malware and attacks |
US10634507B2 (en) * | 2016-03-28 | 2020-04-28 | Avaya Inc. | Interfacing emergency events with map/routing software to re-route non-emergency traffic to create paths for emergency vehicles |
US11321072B2 (en) | 2016-03-30 | 2022-05-03 | Ford Global Technologies, Llc | Vehicle computer update authentication |
US10706140B2 (en) | 2016-03-30 | 2020-07-07 | Ford Global Technologies, Llc | Vehicle computer update authentication |
US10118696B1 (en) | 2016-03-31 | 2018-11-06 | Steven M. Hoffberg | Steerable rotating projectile |
US20170295104A1 (en) * | 2016-04-07 | 2017-10-12 | Qualcomm Incorporated | Network selection for relaying of delay-tolerant traffic |
US20170295471A1 (en) * | 2016-04-07 | 2017-10-12 | Industrial Technology Research Institute | Access point in geographic routing system and controlling method thereof |
US9866563B2 (en) * | 2016-04-12 | 2018-01-09 | Gaurdknox Cyber Technologies Ltd. | Specially programmed computing systems with associated devices configured to implement secure communication lockdowns and methods of use thereof |
US10291583B2 (en) * | 2016-04-13 | 2019-05-14 | VisualThreat Inc. | Vehicle communication system based on controller-area network bus firewall |
EP3232413B1 (en) * | 2016-04-15 | 2021-11-24 | Volvo Car Corporation | Method and system for enabling a vehicle occupant to report a hazard associated with the surroundings of the vehicle |
EP3442836A4 (en) * | 2016-04-15 | 2019-09-18 | Mobile Tech, Inc. | Gateway-based anti-theft security system and method |
US10405260B2 (en) | 2016-04-21 | 2019-09-03 | At&T Intellectual Property I, L.P. | Vehicle-based mobile node fleet for network service deployment |
US10200945B2 (en) * | 2016-04-22 | 2019-02-05 | Veniam, Inc. | Systems and methods for managing mobility of users in a network of moving things at the edge |
US10462612B2 (en) * | 2016-04-22 | 2019-10-29 | Veniam, Inc. | Systems and methods for managing mobility of users in a network of moving things at the backhaul |
US10127741B2 (en) | 2016-04-25 | 2018-11-13 | Lunatech, Llc | Electronic vaporizing device with vehicle monitoring functionality |
US10054454B2 (en) * | 2016-05-06 | 2018-08-21 | Ford Global Technologies, Llc | Network based storage of vehicle and infrastructure data for optimizing vehicle routing |
CN105979577A (en) * | 2016-05-11 | 2016-09-28 | 百度在线网络技术(北京)有限公司 | Method and system for obtaining visit information of user |
US10057742B2 (en) * | 2016-05-18 | 2018-08-21 | Veniam, Inc. | Systems and methods for managing the routing and replication of data in the download direction in a network of moving things |
US10298691B2 (en) | 2016-05-18 | 2019-05-21 | Veniam, Inc. | Systems and methods for managing the storage and dropping of data in a network of moving things |
US10423971B2 (en) * | 2016-05-19 | 2019-09-24 | Toyota Jidosha Kabushiki Kaisha | Roadside service estimates based on wireless vehicle data |
US9813542B1 (en) * | 2016-05-19 | 2017-11-07 | GM Global Technology Operations LLC | Adaptive virtualization of a networked-resource between a vehicle and a peripheral device |
US10168953B1 (en) | 2016-05-20 | 2019-01-01 | Nutanix, Inc. | Dynamic scheduling of distributed storage management tasks using predicted system characteristics |
US9940142B2 (en) | 2016-05-20 | 2018-04-10 | At&T Mobility Ii Llc | Connected car resource manager with associated applications control |
US10142425B2 (en) * | 2016-05-23 | 2018-11-27 | Wyse Technology L.L.C. | Session reliability for a redirected USB device |
HUE046886T2 (en) * | 2016-05-31 | 2020-03-30 | Teleste Oyj | Method and system for dynamic management of multimedia content in vehicles |
EP3466125B1 (en) * | 2016-05-31 | 2021-01-27 | Telefonaktiebolaget LM Ericsson (publ) | Method and platoon manager for enabling a wireless device in a vehicle to communicate over a cellular network |
US9926875B2 (en) * | 2016-05-31 | 2018-03-27 | Ford Global Technologies, Llc | Fuel tank pressure sensor rationality testing using V2X technology |
TWI597513B (en) * | 2016-06-02 | 2017-09-01 | 財團法人工業技術研究院 | Positioning system, onboard positioning device and positioning method thereof |
US11227589B2 (en) | 2016-06-06 | 2022-01-18 | Apple Inc. | Intelligent list reading |
US10511542B2 (en) * | 2016-06-10 | 2019-12-17 | Microsoft Technology Licensing, Llc | Multi-interface power-aware networking |
US10586535B2 (en) | 2016-06-10 | 2020-03-10 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
DK179415B1 (en) | 2016-06-11 | 2018-06-14 | Apple Inc | Intelligent device arbitration and control |
DK201670540A1 (en) | 2016-06-11 | 2018-01-08 | Apple Inc | Application integration with a digital assistant |
US10956758B2 (en) | 2016-06-13 | 2021-03-23 | Xevo Inc. | Method and system for providing auto space management using virtuous cycle |
US10902324B2 (en) | 2016-06-13 | 2021-01-26 | Nutanix, Inc. | Dynamic data snapshot management using predictive modeling |
DE102016007183A1 (en) | 2016-06-14 | 2017-12-14 | Audi Ag | Motor vehicle control device and method for monitoring a mobile Internet connection and motor vehicle |
US10631319B2 (en) | 2016-06-15 | 2020-04-21 | Convida Wireless, Llc | Grant-less uplink transmission for new radio |
JP6631415B2 (en) * | 2016-06-15 | 2020-01-15 | 株式会社デンソー | Relay device |
US9961496B2 (en) * | 2016-06-17 | 2018-05-01 | Qualcomm Incorporated | Methods and systems for context based anomaly monitoring |
US10361925B1 (en) | 2016-06-23 | 2019-07-23 | Nutanix, Inc. | Storage infrastructure scenario planning |
JP6494567B2 (en) * | 2016-06-27 | 2019-04-03 | 矢崎総業株式会社 | Communication management apparatus and communication system |
US10321291B2 (en) * | 2016-06-28 | 2019-06-11 | Veniam, Inc. | Systems and methods for the flexible access and management of monitoring applications in a network of moving things including, for example, autonomous vehicles |
DE102016211549A1 (en) * | 2016-06-28 | 2017-12-28 | Bayerische Motoren Werke Aktiengesellschaft | Routing method and device for establishing a communication connection |
US10687242B2 (en) | 2016-06-30 | 2020-06-16 | Apple Inc. | Dynamic offloading of V2X services to DSRC |
EP3481661A4 (en) * | 2016-07-05 | 2020-03-11 | Nauto, Inc. | System and method for automatic driver identification |
JP6675943B2 (en) * | 2016-07-06 | 2020-04-08 | アルプスアルパイン株式会社 | Communication device |
CA3158974A1 (en) * | 2016-07-08 | 2018-01-11 | Airbiquity Inc. | Automatic secure data transfer with a motor vehicle |
WO2018009828A1 (en) | 2016-07-08 | 2018-01-11 | Vid Scale, Inc. | Systems and methods for region-of-interest tone remapping |
US10187751B2 (en) * | 2016-07-11 | 2019-01-22 | Veniam, Inc. | Systems and methods for vehicular positioning using adaptive wireless fingerprinting in a network of moving things including, for example, autonomous vehicles |
US10342067B2 (en) * | 2016-07-11 | 2019-07-02 | Veniam, Inc. | Systems and methods for vehicular positioning based on wireless fingerprinting data in a network of moving things including, for example, autonomous vehicles |
CN107612954A (en) * | 2016-07-12 | 2018-01-19 | 鸿富锦精密电子(天津)有限公司 | Control terminal, mobile device, mobile device control system and method |
US10616808B2 (en) * | 2016-07-19 | 2020-04-07 | Qualcomm Incorporated | Exchanging network server registration credentials over a D2D network |
SE542673C2 (en) * | 2016-07-22 | 2020-06-23 | Icomera Ab | Wireless communication system for vehicles using both trackside wlan and cellular network communication |
WO2018015612A1 (en) * | 2016-07-22 | 2018-01-25 | Nokia Technologies Oy | Determining a modulation and coding scheme for a broadcast or multicast transmission |
US10705517B1 (en) * | 2016-07-26 | 2020-07-07 | UEMSI/HTV, Inc. | Equipment monitoring system |
US11178641B2 (en) | 2016-07-28 | 2021-11-16 | Lg Electronics, Inc. | Signal transmission/reception method associated with platoon communication in wireless communication system |
US10037698B2 (en) | 2016-07-28 | 2018-07-31 | Nissan North America, Inc. | Operation of a vehicle while suppressing fluctuating warnings |
US9928734B2 (en) | 2016-08-02 | 2018-03-27 | Nio Usa, Inc. | Vehicle-to-pedestrian communication systems |
US9936065B2 (en) * | 2016-08-08 | 2018-04-03 | Toyota Motor Engineering & Manufacturing North America, Inc. | Selectively limiting a non-vehicle user input source of a handheld mobile device |
CN109906165A (en) | 2016-08-10 | 2019-06-18 | 兹沃公司 | The method and apparatus of information is provided via the metadata collected and stored using the attention model of deduction |
US10708751B2 (en) * | 2016-08-11 | 2020-07-07 | Qualcomm Incorporated | Detection of technologies for coexistence |
WO2018027799A1 (en) * | 2016-08-11 | 2018-02-15 | 富士通株式会社 | Information transmission method, device and communication system |
DE102016215243A1 (en) * | 2016-08-16 | 2018-02-22 | Siemens Aktiengesellschaft | Arrangement with a technical system and method for its operation |
CN106251410A (en) * | 2016-08-16 | 2016-12-21 | 广西咪付网络技术有限公司 | A kind of parking charge system combined based on bluetooth and sound wave |
JP6690056B2 (en) | 2016-08-22 | 2020-04-28 | ぺロトン テクノロジー インコーポレイテッド | Control system architecture for motor vehicle |
US11588905B2 (en) * | 2016-08-23 | 2023-02-21 | Veniam, Inc. | Systems and methods for flexible software update in a network of moving things |
JP7026675B2 (en) * | 2016-08-23 | 2022-02-28 | 華為技術有限公司 | How and equipment to manage the mobility pattern of the terminal |
US9860075B1 (en) | 2016-08-26 | 2018-01-02 | At&T Intellectual Property I, L.P. | Method and communication node for broadband distribution |
US10950229B2 (en) * | 2016-08-26 | 2021-03-16 | Harman International Industries, Incorporated | Configurable speech interface for vehicle infotainment systems |
KR20180024450A (en) * | 2016-08-30 | 2018-03-08 | 현대자동차주식회사 | Usb communication control method of usb host |
CN106339266A (en) * | 2016-08-31 | 2017-01-18 | 深圳市金立通信设备有限公司 | Virtual positioning method and terminal |
US10084868B2 (en) * | 2016-09-03 | 2018-09-25 | Microsoft Technology Licensing, Llc | IoT gateway for weakly connected settings |
US10313470B2 (en) * | 2016-09-06 | 2019-06-04 | Integrated Device Technology, Inc. | Hierarchical caching and analytics |
US10178531B2 (en) * | 2016-09-15 | 2019-01-08 | Qualcomm Incorporated | Methods and apparatus for efficient sensor data sharing in a vehicle-to-vehicle (V2V) network |
US10819793B2 (en) * | 2016-09-15 | 2020-10-27 | At&T Mobility Ii Llc | Method and apparatus for extending content access |
DE102017121765A1 (en) * | 2016-09-20 | 2018-03-22 | Huf Hülsbeck & Fürst Gmbh & Co. Kg | Method for activating at least one function of a vehicle |
US11068918B2 (en) * | 2016-09-22 | 2021-07-20 | Magna Electronics Inc. | Vehicle communication system |
US20180091981A1 (en) * | 2016-09-23 | 2018-03-29 | Board Of Trustees Of The University Of Arkansas | Smart vehicular hybrid network systems and applications of same |
CN107872794A (en) * | 2016-09-26 | 2018-04-03 | 平安科技(深圳)有限公司 | Channel connection control method and device |
US11096235B2 (en) * | 2016-09-29 | 2021-08-17 | Teleste Oyj | Method for detecting link status |
US10484301B1 (en) * | 2016-09-30 | 2019-11-19 | Nutanix, Inc. | Dynamic resource distribution using periodicity-aware predictive modeling |
US10345804B2 (en) * | 2016-10-04 | 2019-07-09 | General Electric Company | Method and system for remote processing and analysis of industrial asset inspection data |
DE102016219134B4 (en) * | 2016-10-04 | 2024-05-16 | Volkswagen Aktiengesellschaft | Method for accessing an external electronic device |
FR3057127B1 (en) | 2016-10-05 | 2019-04-19 | Airbus Operations | PROCESSOR ADAPTED FOR ETHERNET NETWORK DETERMINISTIC SWITCH |
US10691491B2 (en) | 2016-10-19 | 2020-06-23 | Nutanix, Inc. | Adapting a pre-trained distributed resource predictive model to a target distributed computing environment |
DE102017204326A1 (en) * | 2016-10-21 | 2018-04-26 | Volkswagen Aktiengesellschaft | A method for monitoring the quality of a data connection and subscriber station and network management unit for use in the method |
US10811767B2 (en) | 2016-10-21 | 2020-10-20 | At&T Intellectual Property I, L.P. | System and dielectric antenna with convex dielectric radome |
US10374316B2 (en) | 2016-10-21 | 2019-08-06 | At&T Intellectual Property I, L.P. | System and dielectric antenna with non-uniform dielectric |
US10031740B2 (en) * | 2016-10-24 | 2018-07-24 | Lear Corporation | Method for programming vehicle electronic control modules |
JP6870273B2 (en) * | 2016-10-25 | 2021-05-12 | 住友電気工業株式会社 | Communication control device, switch device, out-of-vehicle communication device, communication control method and communication control program |
US10312567B2 (en) | 2016-10-26 | 2019-06-04 | At&T Intellectual Property I, L.P. | Launcher with planar strip antenna and methods for use therewith |
DE102016221233B3 (en) * | 2016-10-27 | 2017-09-14 | Volkswagen Aktiengesellschaft | Method for managing a first communication connection, system comprising a first communication partner and a second communication partner and vehicle |
TWI604744B (en) * | 2016-11-02 | 2017-11-01 | 財團法人工業技術研究院 | Routing method and wireless node for wireless mesh network |
US10291334B2 (en) | 2016-11-03 | 2019-05-14 | At&T Intellectual Property I, L.P. | System for detecting a fault in a communication system |
US10498044B2 (en) | 2016-11-03 | 2019-12-03 | At&T Intellectual Property I, L.P. | Apparatus for configuring a surface of an antenna |
CN109891772B (en) | 2016-11-03 | 2022-10-04 | 康维达无线有限责任公司 | Frame structure in NR |
US10225025B2 (en) | 2016-11-03 | 2019-03-05 | At&T Intellectual Property I, L.P. | Method and apparatus for detecting a fault in a communication system |
US10224634B2 (en) | 2016-11-03 | 2019-03-05 | At&T Intellectual Property I, L.P. | Methods and apparatus for adjusting an operational characteristic of an antenna |
US10638418B2 (en) * | 2016-11-04 | 2020-04-28 | Ford Global Technologies, Llc | Method and apparatus for data transfer connection management |
DE102016221690A1 (en) | 2016-11-04 | 2018-05-09 | Audi Ag | Method for transmitting data packets between an Ethernet and a bus system in a motor vehicle, and gateway device and motor vehicle |
JP6460080B2 (en) | 2016-11-07 | 2019-01-30 | トヨタ自動車株式会社 | In-vehicle network system |
US11024160B2 (en) | 2016-11-07 | 2021-06-01 | Nio Usa, Inc. | Feedback performance control and tracking |
WO2018085814A1 (en) | 2016-11-07 | 2018-05-11 | Whelen Engineering Company, Inc. | Network and connected devices for emergency response and roadside operations |
US10410064B2 (en) | 2016-11-11 | 2019-09-10 | Nio Usa, Inc. | System for tracking and identifying vehicles and pedestrians |
US10694357B2 (en) | 2016-11-11 | 2020-06-23 | Nio Usa, Inc. | Using vehicle sensor data to monitor pedestrian health |
US10708547B2 (en) | 2016-11-11 | 2020-07-07 | Nio Usa, Inc. | Using vehicle sensor data to monitor environmental and geologic conditions |
US10560312B2 (en) * | 2016-11-13 | 2020-02-11 | Harman International Industries, Incorporated | Multi-mode configurable network audio |
SE542335C2 (en) * | 2016-11-14 | 2020-04-14 | Wiretronic Ab | Method and system for vehicle analysis |
US10635621B2 (en) * | 2016-11-16 | 2020-04-28 | Baidu Usa Llc | Apparatus for controlling and operating an autonomous vehicle |
DE102016222741A1 (en) | 2016-11-18 | 2018-05-24 | Continental Automotive Gmbh | Method for a communication network and electronic control unit |
US10699305B2 (en) | 2016-11-21 | 2020-06-30 | Nio Usa, Inc. | Smart refill assistant for electric vehicles |
US11089459B2 (en) * | 2016-11-22 | 2021-08-10 | Toyota Jidosha Kabushiki Kaisha | Storage service for mobile nodes in a roadway area |
US10382436B2 (en) * | 2016-11-22 | 2019-08-13 | Daniel Chien | Network security based on device identifiers and network addresses |
US10394245B2 (en) * | 2016-11-22 | 2019-08-27 | Baidu Usa Llc | Method and system to predict vehicle traffic behavior for autonomous vehicles to make driving decisions |
US10340603B2 (en) | 2016-11-23 | 2019-07-02 | At&T Intellectual Property I, L.P. | Antenna system having shielded structural configurations for assembly |
US10178445B2 (en) | 2016-11-23 | 2019-01-08 | At&T Intellectual Property I, L.P. | Methods, devices, and systems for load balancing between a plurality of waveguides |
US10340601B2 (en) | 2016-11-23 | 2019-07-02 | At&T Intellectual Property I, L.P. | Multi-antenna system and methods for use therewith |
US10090594B2 (en) | 2016-11-23 | 2018-10-02 | At&T Intellectual Property I, L.P. | Antenna system having structural configurations for assembly |
US10535928B2 (en) | 2016-11-23 | 2020-01-14 | At&T Intellectual Property I, L.P. | Antenna system and methods for use therewith |
JP6547154B2 (en) * | 2016-11-30 | 2019-07-24 | 本田技研工業株式会社 | Communications system |
US10305190B2 (en) | 2016-12-01 | 2019-05-28 | At&T Intellectual Property I, L.P. | Reflecting dielectric antenna system and methods for use therewith |
US10361489B2 (en) | 2016-12-01 | 2019-07-23 | At&T Intellectual Property I, L.P. | Dielectric dish antenna system and methods for use therewith |
US10637149B2 (en) | 2016-12-06 | 2020-04-28 | At&T Intellectual Property I, L.P. | Injection molded dielectric antenna and methods for use therewith |
US10819035B2 (en) | 2016-12-06 | 2020-10-27 | At&T Intellectual Property I, L.P. | Launcher with helical antenna and methods for use therewith |
US9927517B1 (en) | 2016-12-06 | 2018-03-27 | At&T Intellectual Property I, L.P. | Apparatus and methods for sensing rainfall |
US10694379B2 (en) | 2016-12-06 | 2020-06-23 | At&T Intellectual Property I, L.P. | Waveguide system with device-based authentication and methods for use therewith |
US10249104B2 (en) | 2016-12-06 | 2019-04-02 | Nio Usa, Inc. | Lease observation and event recording |
US10020844B2 (en) | 2016-12-06 | 2018-07-10 | T&T Intellectual Property I, L.P. | Method and apparatus for broadcast communication via guided waves |
US10135145B2 (en) | 2016-12-06 | 2018-11-20 | At&T Intellectual Property I, L.P. | Apparatus and methods for generating an electromagnetic wave along a transmission medium |
US10382976B2 (en) | 2016-12-06 | 2019-08-13 | At&T Intellectual Property I, L.P. | Method and apparatus for managing wireless communications based on communication paths and network device positions |
US10439675B2 (en) | 2016-12-06 | 2019-10-08 | At&T Intellectual Property I, L.P. | Method and apparatus for repeating guided wave communication signals |
US10326494B2 (en) | 2016-12-06 | 2019-06-18 | At&T Intellectual Property I, L.P. | Apparatus for measurement de-embedding and methods for use therewith |
US10727599B2 (en) | 2016-12-06 | 2020-07-28 | At&T Intellectual Property I, L.P. | Launcher with slot antenna and methods for use therewith |
US10755542B2 (en) | 2016-12-06 | 2020-08-25 | At&T Intellectual Property I, L.P. | Method and apparatus for surveillance via guided wave communication |
US10027397B2 (en) | 2016-12-07 | 2018-07-17 | At&T Intellectual Property I, L.P. | Distributed antenna system and methods for use therewith |
US10359749B2 (en) | 2016-12-07 | 2019-07-23 | At&T Intellectual Property I, L.P. | Method and apparatus for utilities management via guided wave communication |
US10243270B2 (en) | 2016-12-07 | 2019-03-26 | At&T Intellectual Property I, L.P. | Beam adaptive multi-feed dielectric antenna system and methods for use therewith |
US10168695B2 (en) | 2016-12-07 | 2019-01-01 | At&T Intellectual Property I, L.P. | Method and apparatus for controlling an unmanned aircraft |
US9893795B1 (en) | 2016-12-07 | 2018-02-13 | At&T Intellectual Property I, Lp | Method and repeater for broadband distribution |
US10389029B2 (en) | 2016-12-07 | 2019-08-20 | At&T Intellectual Property I, L.P. | Multi-feed dielectric antenna system with core selection and methods for use therewith |
CN110325929B (en) | 2016-12-07 | 2021-05-25 | 阿瑞路资讯安全科技股份有限公司 | System and method for signal waveform analysis for detecting changes in wired networks |
US10547348B2 (en) | 2016-12-07 | 2020-01-28 | At&T Intellectual Property I, L.P. | Method and apparatus for switching transmission mediums in a communication system |
US10139820B2 (en) | 2016-12-07 | 2018-11-27 | At&T Intellectual Property I, L.P. | Method and apparatus for deploying equipment of a communication system |
US10446936B2 (en) | 2016-12-07 | 2019-10-15 | At&T Intellectual Property I, L.P. | Multi-feed dielectric antenna system and methods for use therewith |
US10601494B2 (en) | 2016-12-08 | 2020-03-24 | At&T Intellectual Property I, L.P. | Dual-band communication device and method for use therewith |
US10916969B2 (en) | 2016-12-08 | 2021-02-09 | At&T Intellectual Property I, L.P. | Method and apparatus for providing power using an inductive coupling |
US10326689B2 (en) | 2016-12-08 | 2019-06-18 | At&T Intellectual Property I, L.P. | Method and system for providing alternative communication paths |
US10103422B2 (en) | 2016-12-08 | 2018-10-16 | At&T Intellectual Property I, L.P. | Method and apparatus for mounting network devices |
US9911020B1 (en) | 2016-12-08 | 2018-03-06 | At&T Intellectual Property I, L.P. | Method and apparatus for tracking via a radio frequency identification device |
US10530505B2 (en) | 2016-12-08 | 2020-01-07 | At&T Intellectual Property I, L.P. | Apparatus and methods for launching electromagnetic waves along a transmission medium |
US10938108B2 (en) | 2016-12-08 | 2021-03-02 | At&T Intellectual Property I, L.P. | Frequency selective multi-feed dielectric antenna system and methods for use therewith |
US10777873B2 (en) | 2016-12-08 | 2020-09-15 | At&T Intellectual Property I, L.P. | Method and apparatus for mounting network devices |
US10411356B2 (en) | 2016-12-08 | 2019-09-10 | At&T Intellectual Property I, L.P. | Apparatus and methods for selectively targeting communication devices with an antenna array |
US9998870B1 (en) | 2016-12-08 | 2018-06-12 | At&T Intellectual Property I, L.P. | Method and apparatus for proximity sensing |
US10389037B2 (en) | 2016-12-08 | 2019-08-20 | At&T Intellectual Property I, L.P. | Apparatus and methods for selecting sections of an antenna array and use therewith |
US10069535B2 (en) | 2016-12-08 | 2018-09-04 | At&T Intellectual Property I, L.P. | Apparatus and methods for launching electromagnetic waves having a certain electric field structure |
US10340983B2 (en) | 2016-12-09 | 2019-07-02 | At&T Intellectual Property I, L.P. | Method and apparatus for surveying remote sites via guided wave communications |
US9838896B1 (en) | 2016-12-09 | 2017-12-05 | At&T Intellectual Property I, L.P. | Method and apparatus for assessing network coverage |
US10264586B2 (en) | 2016-12-09 | 2019-04-16 | At&T Mobility Ii Llc | Cloud-based packet controller and methods for use therewith |
US10362509B2 (en) | 2016-12-09 | 2019-07-23 | Redpine Signals, Inc. | Incident broadcast retransmission in a vehicular network |
JP2020513708A (en) * | 2016-12-09 | 2020-05-14 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | Interface, vehicle control system and network equipment for combining vehicle control with communication services |
US10097473B2 (en) * | 2016-12-13 | 2018-10-09 | Livio, Inc. | Mobile device to vehicle output stream packet prioritization |
US10542477B2 (en) | 2016-12-14 | 2020-01-21 | The Boeing Company | Multi-hop networking protocol for wide-area energy harvesting sensor network deployments |
GB2562824B (en) * | 2016-12-15 | 2022-04-13 | Pismo Labs Technology Ltd | Methods and systems for providing electricity according to power policy |
DE102016225226B4 (en) | 2016-12-16 | 2022-03-24 | Volkswagen Aktiengesellschaft | Method, device and computer program for a mobile device for reducing interference between a first mobile communication system and a second mobile communication system |
EP3339898A1 (en) * | 2016-12-20 | 2018-06-27 | Nxp B.V. | Sensor data network |
EP3340704B1 (en) | 2016-12-22 | 2020-06-10 | Volkswagen Aktiengesellschaft | Method for resource allocation in a mobile communication system and base station, and participant communication module for the use in the method |
WO2018119423A1 (en) * | 2016-12-22 | 2018-06-28 | Surround. Io Corporation | Method and system for providing artificial intelligence analytic (aia) services for performance prediction |
US11113690B2 (en) | 2016-12-22 | 2021-09-07 | Mastercard International Incorporated | Systems and methods for processing data messages from a user vehicle |
US20200019415A1 (en) * | 2016-12-22 | 2020-01-16 | Volkswagen Aktiengesellschaft | User terminal, user interface, computer program product, signal sequence, means of transport, and method for setting up a user interface of a means of transport |
JP6508188B2 (en) * | 2016-12-26 | 2019-05-08 | トヨタ自動車株式会社 | Cryptographic communication system |
US10993165B2 (en) * | 2016-12-27 | 2021-04-27 | Veniam, Inc. | Flexible support of multi-homing in networks of moving things including autonomous vehicles based networks |
US10343631B2 (en) * | 2016-12-28 | 2019-07-09 | Uber Technologies, Inc. | Decreasing autonomous vehicle power consumption |
US11477202B2 (en) * | 2016-12-29 | 2022-10-18 | AVAST Software s.r.o. | System and method for detecting unknown IoT device types by monitoring their behavior |
CN114900858A (en) | 2016-12-30 | 2022-08-12 | 英特尔公司 | Method and apparatus for radio communication |
US10110721B2 (en) * | 2016-12-30 | 2018-10-23 | GM Global Technology Operations LLC | Wireless-enabled consumer port apparatus for accommodating after-market devices flexibly in vehicles |
US10558978B1 (en) * | 2016-12-30 | 2020-02-11 | Wells Fargo Bank, N.A. | One-time passcode |
US11204787B2 (en) | 2017-01-09 | 2021-12-21 | Apple Inc. | Application integration with a digital assistant |
WO2018132493A1 (en) * | 2017-01-10 | 2018-07-19 | LifePASS Inc. | Vehicular personnel accountability & safety system |
EP3349372B1 (en) * | 2017-01-11 | 2019-12-04 | Volkswagen Aktiengesellschaft | Method for adjusting the interference level for a wireless communication from a first mobile station to a second mobile station and adapted mobile station for the use in the method and adapted vehicle |
US10074223B2 (en) | 2017-01-13 | 2018-09-11 | Nio Usa, Inc. | Secured vehicle for user use only |
US10031521B1 (en) | 2017-01-16 | 2018-07-24 | Nio Usa, Inc. | Method and system for using weather information in operation of autonomous vehicles |
US10471829B2 (en) | 2017-01-16 | 2019-11-12 | Nio Usa, Inc. | Self-destruct zone and autonomous vehicle navigation |
US9984572B1 (en) | 2017-01-16 | 2018-05-29 | Nio Usa, Inc. | Method and system for sharing parking space availability among autonomous vehicles |
US10286915B2 (en) | 2017-01-17 | 2019-05-14 | Nio Usa, Inc. | Machine learning for personalized driving |
US10464530B2 (en) | 2017-01-17 | 2019-11-05 | Nio Usa, Inc. | Voice biometric pre-purchase enrollment for autonomous vehicles |
JP6981755B2 (en) * | 2017-01-25 | 2021-12-17 | トヨタ自動車株式会社 | In-vehicle network system |
JP6809913B2 (en) * | 2017-01-26 | 2021-01-06 | パナソニック株式会社 | Robots, robot control methods, and map generation methods |
US10966070B2 (en) * | 2017-01-30 | 2021-03-30 | Veniam, Inc. | Systems and methods for managing data with heterogeneous multi-paths and multi-networks in an internet of moving things |
CN110235430B (en) * | 2017-01-31 | 2021-01-08 | 兴和株式会社 | Camera operating device |
FR3062544A1 (en) * | 2017-02-01 | 2018-08-03 | Peugeot Citroen Automobiles Sa | METHOD AND DEVICE FOR ASSISTING DOWNLOADING. |
US10897469B2 (en) | 2017-02-02 | 2021-01-19 | Nio Usa, Inc. | System and method for firewalls between vehicle networks |
US10127814B2 (en) * | 2017-02-03 | 2018-11-13 | Ford Global Technologies, Llc | Advanced V2X event dissemination |
US10498600B2 (en) * | 2017-02-06 | 2019-12-03 | Veniam, Inc. | Systems and methods for real-time, selective and event-driven data model to feed services and applications for access points including access points related to autonomous and non-autonomous vehicles in a network of moving things |
US9852405B1 (en) * | 2017-02-09 | 2017-12-26 | Rubicon Global Holdings, Llc | System and method for managing waste services |
US10146288B2 (en) * | 2017-02-15 | 2018-12-04 | Vigyanlabs Innovations Private Limited | Adaptive power consumption management in smart devices |
WO2018152437A1 (en) | 2017-02-17 | 2018-08-23 | Vid Scale, Inc. | Systems and methods for selective object-of-interest zooming in streaming video |
US10880409B2 (en) | 2017-02-20 | 2020-12-29 | Cisco Technology, Inc. | Mixed qualitative, quantitative sensing data compression over a network transport |
DE102017223399B4 (en) * | 2017-12-20 | 2023-11-30 | Bayerische Motoren Werke Aktiengesellschaft | Display assembly for a means of transportation |
JP6798349B2 (en) * | 2017-02-23 | 2020-12-09 | 株式会社デンソー | Communication system and relay device |
US9973940B1 (en) | 2017-02-27 | 2018-05-15 | At&T Intellectual Property I, L.P. | Apparatus and methods for dynamic impedance matching of a guided wave launcher |
US10215145B2 (en) * | 2017-02-27 | 2019-02-26 | Honda Motor Co., Ltd. | Dual controller area network (CAN) starter |
US10433243B2 (en) * | 2017-03-01 | 2019-10-01 | Veniam, Inc. | Systems and methods for integrating and exploiting the availability of multiple communication technologies in a network of moving things, for example including a network of autonomous vehicles |
US10819651B2 (en) | 2017-03-08 | 2020-10-27 | Arris Enterprises Llc | Excess bitrate distribution based on quality gain |
US10298293B2 (en) | 2017-03-13 | 2019-05-21 | At&T Intellectual Property I, L.P. | Apparatus of communication utilizing wireless network devices |
US10162357B2 (en) * | 2017-03-15 | 2018-12-25 | Toyota Research Institute, Inc. | Distributed computing among vehicles |
US10601710B2 (en) * | 2017-03-15 | 2020-03-24 | Qualcomm Incorporated | IP level multipath protocol |
US10616772B2 (en) * | 2017-03-15 | 2020-04-07 | At&T Mobility Ii Llc | Systems and methods for using femtocell functionality in user devices |
US10560263B2 (en) * | 2017-03-24 | 2020-02-11 | Micron Technology, Inc. | Secure memory arrangements |
US10315520B2 (en) * | 2017-04-04 | 2019-06-11 | Southwest University | Apparatuses and methods of an in-vehicle gateway system for monitoring and controling in-vehicle subsystems |
US10666766B2 (en) * | 2017-04-05 | 2020-05-26 | Cisco Technology, Inc. | Application descriptive language for network gateways |
US20180293814A1 (en) * | 2017-04-05 | 2018-10-11 | GM Global Technology Operations LLC | Method to classify system performance and detect environmental information |
US10269192B2 (en) | 2017-04-07 | 2019-04-23 | Airbiquity Inc. | Technologies for verifying control system operation |
US10917387B2 (en) * | 2017-04-11 | 2021-02-09 | Panasonic Intellectual Property Management Co., Ltd. | Information processing device, information processing system, information processing method, and information processing program |
US10873600B2 (en) * | 2017-04-11 | 2020-12-22 | Panasonic Intellectual Property Management Co., Ltd. | Information processing device, information processing system, information processing method, and information processing program |
US10756924B2 (en) * | 2017-04-12 | 2020-08-25 | Denso International America, Inc. | System and method for encoding data within a vehicle communication network |
US10104564B1 (en) * | 2017-04-13 | 2018-10-16 | The Nielsen Company (Us), Llc | Methods and apparatus to determine mobile device application usage in vehicles including media applications |
US10363796B2 (en) | 2017-04-19 | 2019-07-30 | Ford Global Technologies, Llc | Control module activation of vehicles in a key-off state |
US10378919B2 (en) | 2017-04-19 | 2019-08-13 | Ford Global Technologies, Llc | Control module activation of vehicles in a key-off state to determine driving routes |
US10217297B2 (en) | 2017-04-19 | 2019-02-26 | Ford Global Technologies, Llc | Control module activation to monitor vehicles in a key-off state |
WO2018194617A1 (en) * | 2017-04-20 | 2018-10-25 | Hewlett-Packard Development Company, L.P. | Data connection switching |
US10425330B2 (en) | 2017-04-24 | 2019-09-24 | International Business Machines Corporation | Routing packets in multiple destination networks with overlapping address spaces |
WO2018203336A1 (en) | 2017-05-04 | 2018-11-08 | Liveu Ltd. | Device, system, and method of pre-processing and data delivery for multi-link communications and for media content |
US20180322273A1 (en) * | 2017-05-04 | 2018-11-08 | GM Global Technology Operations LLC | Method and apparatus for limited starting authorization |
DK201770383A1 (en) | 2017-05-09 | 2018-12-14 | Apple Inc. | User interface for correcting recognition errors |
US10726832B2 (en) | 2017-05-11 | 2020-07-28 | Apple Inc. | Maintaining privacy of personal information |
DK180048B1 (en) | 2017-05-11 | 2020-02-04 | Apple Inc. | MAINTAINING THE DATA PROTECTION OF PERSONAL INFORMATION |
DK201770429A1 (en) | 2017-05-12 | 2018-12-14 | Apple Inc. | Low-latency intelligent automated assistant |
DK179496B1 (en) | 2017-05-12 | 2019-01-15 | Apple Inc. | USER-SPECIFIC Acoustic Models |
DK179745B1 (en) | 2017-05-12 | 2019-05-01 | Apple Inc. | SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT |
DK201770411A1 (en) | 2017-05-15 | 2018-12-20 | Apple Inc. | Multi-modal interfaces |
US20180336892A1 (en) | 2017-05-16 | 2018-11-22 | Apple Inc. | Detecting a trigger of a digital assistant |
DK179549B1 (en) * | 2017-05-16 | 2019-02-12 | Apple Inc. | Far-field extension for digital assistant services |
US20180336275A1 (en) | 2017-05-16 | 2018-11-22 | Apple Inc. | Intelligent automated assistant for media exploration |
US10970942B2 (en) * | 2017-05-16 | 2021-04-06 | Wistron Aiedge Corporation | Fog data agent for connected cars |
US11873005B2 (en) * | 2017-05-18 | 2024-01-16 | Driveu Tech Ltd. | Device, system, and method of wireless multiple-link vehicular communication |
US10708823B2 (en) * | 2017-05-23 | 2020-07-07 | Veniam, Inc. | Systems and methods for cooperative, dynamic, and balanced access to the infrastructure supporting the network of moving things, for example including autonomous vehicles |
US11610441B1 (en) * | 2017-05-23 | 2023-03-21 | State Farm Mutual Automobile Insurance Company | Detecting and mitigating local individual driver anomalous behavior |
CN107182074B (en) * | 2017-06-16 | 2019-08-23 | 大连大学 | A kind of routing optimal path choosing method based on Zigbee |
US10585180B2 (en) | 2017-06-21 | 2020-03-10 | International Business Machines Corporation | Management of mobile objects |
US10546488B2 (en) | 2017-06-21 | 2020-01-28 | International Business Machines Corporation | Management of mobile objects |
US10504368B2 (en) | 2017-06-21 | 2019-12-10 | International Business Machines Corporation | Management of mobile objects |
US10535266B2 (en) | 2017-06-21 | 2020-01-14 | International Business Machines Corporation | Management of mobile objects |
US10600322B2 (en) | 2017-06-21 | 2020-03-24 | International Business Machines Corporation | Management of mobile objects |
US10540895B2 (en) | 2017-06-21 | 2020-01-21 | International Business Machines Corporation | Management of mobile objects |
US10234302B2 (en) | 2017-06-27 | 2019-03-19 | Nio Usa, Inc. | Adaptive route and motion planning based on learned external and internal vehicle environment |
US10405215B2 (en) * | 2017-06-27 | 2019-09-03 | Veniam, Inc. | Self-organized fleets of autonomous vehicles to optimize future mobility and city services |
US11012254B2 (en) * | 2017-06-28 | 2021-05-18 | Bloom Energy Corporation | Method and apparatus for handling controller area network (CAN) messages in a fuel cell system |
US11146991B2 (en) * | 2017-06-29 | 2021-10-12 | Sony Corporation | Communication system and transmission apparatus |
WO2019009874A1 (en) * | 2017-07-01 | 2019-01-10 | Intel Corporation | Mmwave dielectric waveguide interconnect topology for automotive applications |
AU2018296964A1 (en) * | 2017-07-03 | 2020-02-20 | Gp Network Asia Pte. Ltd. | Processing payments |
US20190014026A1 (en) * | 2017-07-05 | 2019-01-10 | Ford Global Technologies, Llc | Method and apparatus for ignition state monitoring |
US10567923B2 (en) * | 2017-07-07 | 2020-02-18 | Toyota Jidosha Kabushiki Kaisha | Computation service for mobile nodes in a roadway environment |
US10369974B2 (en) | 2017-07-14 | 2019-08-06 | Nio Usa, Inc. | Control and coordination of driverless fuel replenishment for autonomous vehicles |
US10710633B2 (en) | 2017-07-14 | 2020-07-14 | Nio Usa, Inc. | Control of complex parking maneuvers and autonomous fuel replenishment of driverless vehicles |
EP3435617B1 (en) * | 2017-07-24 | 2021-05-26 | Nxp B.V. | A node, a vehicle, an integrated circuit and method for updating at least one rule in a controller area network |
US10402192B2 (en) | 2017-07-25 | 2019-09-03 | Aurora Labs Ltd. | Constructing software delta updates for vehicle ECU software and abnormality detection based on toolchain |
WO2019023565A1 (en) | 2017-07-27 | 2019-01-31 | Upstream Security Ltd. | System and method for connected vehicle cybersecurity |
US10141967B1 (en) * | 2017-07-28 | 2018-11-27 | Ford Global Technologies, Llc | Virtual network interface connectivity |
CN107332711B (en) * | 2017-07-31 | 2019-11-22 | 北京新能源汽车股份有限公司 | Vehicular diagnostic method and device |
US10837790B2 (en) | 2017-08-01 | 2020-11-17 | Nio Usa, Inc. | Productive and accident-free driving modes for a vehicle |
US10475344B2 (en) * | 2017-08-01 | 2019-11-12 | Denso International America, Inc. | Systems and methods for adaptive filtering of vehicle-to-vehicle messages from remote vehicles |
US11076273B2 (en) * | 2017-08-07 | 2021-07-27 | Veniam, Inc. | Systems and methods for controlling data transfer in a network of moving things, for example including autonomous vehicles |
WO2019029793A1 (en) * | 2017-08-08 | 2019-02-14 | Continental Automotive Gmbh | Method of operating a cache |
US10708542B1 (en) | 2017-08-23 | 2020-07-07 | Clifford D. Griffin | Video conference call camera for an automobile |
US11362882B2 (en) * | 2017-08-25 | 2022-06-14 | Veniam, Inc. | Methods and systems for optimal and adaptive urban scanning using self-organized fleets of autonomous vehicles |
US10272840B2 (en) * | 2017-08-31 | 2019-04-30 | Karen Schmahl | Communication device for a vehicle |
WO2019041051A1 (en) * | 2017-09-01 | 2019-03-07 | Automobility Distribution Inc. | Device control app with advertising |
EP3450265B1 (en) | 2017-09-04 | 2019-12-18 | Polestar Performance AB | Method and system for passive start of a vehicle |
WO2019043446A1 (en) | 2017-09-04 | 2019-03-07 | Nng Software Developing And Commercial Llc | A method and apparatus for collecting and using sensor data from a vehicle |
US11072311B2 (en) * | 2017-09-05 | 2021-07-27 | Future Mobility Corporation Limited | Methods and systems for user recognition and expression for an automobile |
US11140628B2 (en) | 2017-09-11 | 2021-10-05 | Continental Automotive Gmbh | Method for controlling power of a radio frequency system |
JP6801619B2 (en) * | 2017-09-25 | 2020-12-16 | 株式会社デンソー | Data transfer route calculation device and data transfer terminal |
KR102288799B1 (en) * | 2017-09-27 | 2021-08-11 | 현대모비스 주식회사 | Apparatus for controlling group driving and method thereof |
US11012945B2 (en) * | 2017-09-29 | 2021-05-18 | Apple Inc. | Devices and methods for power allocation |
CN111417867B (en) * | 2017-10-02 | 2023-10-03 | 安全堡垒有限责任公司 | Detection and prevention of cyber physical attacks against sensors |
US20190101914A1 (en) * | 2017-10-02 | 2019-04-04 | Allstate Insurance Company | Data Processing System with Machine Learning Engine for Providing Driving Data Analysis and Vehicle Control Functions |
US10545751B2 (en) | 2017-10-03 | 2020-01-28 | Accenture Global Solutions Limited | Automated usage driven engineering |
US10635109B2 (en) | 2017-10-17 | 2020-04-28 | Nio Usa, Inc. | Vehicle path-planner monitor and controller |
US10349335B2 (en) * | 2017-10-27 | 2019-07-09 | Cisco Technology, Inc. | Methods and apparatus for use in selecting a connection path for low-latency, deterministic multi-hop D2D communications |
US10935978B2 (en) | 2017-10-30 | 2021-03-02 | Nio Usa, Inc. | Vehicle self-localization using particle filters and visual odometry |
US10606274B2 (en) | 2017-10-30 | 2020-03-31 | Nio Usa, Inc. | Visual place recognition based self-localization for autonomous vehicles |
GB2568237B (en) * | 2017-10-31 | 2020-04-22 | Jaguar Land Rover Ltd | Improved vehicle data communications network |
US10791543B2 (en) * | 2017-10-31 | 2020-09-29 | Toyota Jidosha Kabushiki Kaisha | Service discovery and provisioning for a macro-vehicular cloud |
GB2568236B (en) * | 2017-10-31 | 2020-11-04 | Jaguar Land Rover Ltd | Improved vehicle data communications network |
US11553398B2 (en) * | 2017-10-31 | 2023-01-10 | Cable Television Laboratories, Inc. | Systems and methods for internet of things security environment |
KR102392017B1 (en) * | 2017-11-06 | 2022-05-02 | 현대자동차주식회사 | Server, Vehicle communicating with the server and method for controlling the server |
US10717412B2 (en) | 2017-11-13 | 2020-07-21 | Nio Usa, Inc. | System and method for controlling a vehicle using secondary access methods |
US10426424B2 (en) | 2017-11-21 | 2019-10-01 | General Electric Company | System and method for generating and performing imaging protocol simulations |
US10674332B2 (en) * | 2017-12-01 | 2020-06-02 | Veniam, Inc. | Systems and methods for the data-driven and distributed interoperability between nodes to increase context and location awareness in a network of moving things, for example in a network of autonomous vehicles |
US10917490B2 (en) * | 2017-12-04 | 2021-02-09 | Hyundai Motor Company | Method and apparatus for transmitting data in system |
DE102017222216B3 (en) * | 2017-12-07 | 2019-05-29 | Volkswagen Aktiengesellschaft | Method for carrying out distance measurements between the vehicles of a vehicle convoy and vehicle module for use in the method and vehicle |
CN107967590A (en) * | 2017-12-13 | 2018-04-27 | 浙江理工大学 | A kind of optimization constructing method of Urban Underground Logistics System |
US10499189B2 (en) | 2017-12-14 | 2019-12-03 | Cisco Technology, Inc. | Communication of data relating to endpoint devices |
DE102017222905A1 (en) * | 2017-12-15 | 2019-06-19 | Audi Ag | Method for coupling a final vehicle to a stationary data network and system for carrying out the method |
DE102017223398A1 (en) * | 2017-12-20 | 2019-06-27 | Bayerische Motoren Werke Aktiengesellschaft | DATA PROCESSING SYSTEM, VEHICLE AND COMMUNICATION PROCESS |
US20200389469A1 (en) | 2017-12-24 | 2020-12-10 | Arilou Information Security Technologies Ltd. | System and method for tunnel-based malware detection |
SE541396C2 (en) * | 2017-12-27 | 2019-09-10 | Scania Cv Ab | Method and control unit for communicating with a vehicle |
US10909017B2 (en) * | 2017-12-27 | 2021-02-02 | Intel Corporation | Latency reporting for algorithm weighting in multiagent systems |
WO2019126861A1 (en) * | 2017-12-28 | 2019-07-04 | Paxgrid Cdn Inc. | System for authenticating and authorizing access to and accounting for wireless access vehicular environment consumption by client devices |
EP3506207A1 (en) * | 2017-12-28 | 2019-07-03 | Centre National d'Etudes Spatiales | Dynamic streetview with view images enhancement |
CN109996126B (en) * | 2017-12-29 | 2021-06-22 | 浙江宇视科技有限公司 | Dynamic scheduling method and system for equipment connection under hybrid network architecture |
US10311404B1 (en) * | 2018-01-05 | 2019-06-04 | Accenture Global Solutions Limited | Software product development defect and issue prediction and diagnosis |
US11079758B2 (en) * | 2018-01-12 | 2021-08-03 | Toyota Research Institute, Inc. | Systems and methods for incentivizing user-aided improvement of autonomous vehicle control systems and methods of operating a vehicle using the same |
CN108269087B (en) | 2018-01-12 | 2020-07-28 | 阿里巴巴集团控股有限公司 | Method and device for processing position information |
US10798104B2 (en) * | 2018-01-15 | 2020-10-06 | Ford Global Technologies, Llc | Networked communications control for vehicles |
US11777785B2 (en) | 2018-01-21 | 2023-10-03 | Cisco Technology, Inc. | Alert throttling |
JP7045286B2 (en) * | 2018-01-22 | 2022-03-31 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ | Data analysis device, data analysis method and program |
US11188897B2 (en) | 2018-02-13 | 2021-11-30 | Bank Of America Corporation | Multi-tiered digital wallet security |
CN108171858A (en) * | 2018-02-13 | 2018-06-15 | 南京东屋电气有限公司 | A kind of automobile door lock with separate type infrared image acquisition device |
JP7047444B2 (en) * | 2018-02-16 | 2022-04-05 | トヨタ自動車株式会社 | Vehicle control unit, electronic control unit, control method, control program, vehicle, OTA master, system and center |
US11257184B1 (en) | 2018-02-21 | 2022-02-22 | Northrop Grumman Systems Corporation | Image scaler |
CN108282400B (en) * | 2018-03-05 | 2020-10-13 | 中科边缘智慧信息科技(苏州)有限公司 | DTN routing method based on cooperative game theory |
US11057769B2 (en) | 2018-03-12 | 2021-07-06 | At&T Digital Life, Inc. | Detecting unauthorized access to a wireless network |
US10498555B2 (en) * | 2018-03-13 | 2019-12-03 | Ambit Microsystems (Shanghai) Ltd. | System for combining wireless sensor networks and method thereof |
US10904891B2 (en) | 2018-03-14 | 2021-01-26 | Toyota Jidosha Kabushiki Kaisha | Edge-assisted data transmission for connected vehicles |
US10769009B2 (en) * | 2018-03-21 | 2020-09-08 | International Business Machines Corporation | Root cause analysis for correlated development and operations data |
US11712637B1 (en) | 2018-03-23 | 2023-08-01 | Steven M. Hoffberg | Steerable disk or ball |
US10818288B2 (en) | 2018-03-26 | 2020-10-27 | Apple Inc. | Natural assistant interaction |
US11934520B2 (en) * | 2018-03-28 | 2024-03-19 | Nvidia Corporation | Detecting data anomalies on a data interface using machine learning |
US11157003B1 (en) | 2018-04-05 | 2021-10-26 | Northrop Grumman Systems Corporation | Software framework for autonomous system |
CN109474912B (en) * | 2018-04-10 | 2022-02-18 | 西南大学 | Vehicle-mounted gateway system and monitoring method and device of vehicle-mounted subsystem |
US10608921B2 (en) * | 2018-04-19 | 2020-03-31 | Cisco Technology, Inc. | Routing in fat tree networks using negative disaggregation advertisements |
DE102018206068A1 (en) | 2018-04-20 | 2019-10-24 | Audi Ag | Communication device, control component, mobile station, vehicle, system, method and computer program for configuring local wireless communication between the communication device and a vehicle-mounted mobile device |
US10928918B2 (en) | 2018-05-07 | 2021-02-23 | Apple Inc. | Raise to speak |
US11075740B2 (en) | 2018-05-07 | 2021-07-27 | ENK Wireless, Inc. | Systems/methods of communications using a plurality of cooperative devices |
US11145294B2 (en) | 2018-05-07 | 2021-10-12 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
US11001273B2 (en) * | 2018-05-22 | 2021-05-11 | International Business Machines Corporation | Providing a notification based on a deviation from a determined driving behavior |
US10369966B1 (en) | 2018-05-23 | 2019-08-06 | Nio Usa, Inc. | Controlling access to a vehicle using wireless access devices |
DK180639B1 (en) | 2018-06-01 | 2021-11-04 | Apple Inc | DISABILITY OF ATTENTION-ATTENTIVE VIRTUAL ASSISTANT |
DK201870355A1 (en) | 2018-06-01 | 2019-12-16 | Apple Inc. | Virtual assistant operation in multi-device environments |
DK179822B1 (en) | 2018-06-01 | 2019-07-12 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
US10892996B2 (en) | 2018-06-01 | 2021-01-12 | Apple Inc. | Variable latency device coordination |
US11875418B2 (en) * | 2018-06-07 | 2024-01-16 | American Express Travel Related Services Company, Inc. | Automated remote payments between a vehicle and a refueling station |
JP6750646B2 (en) * | 2018-06-07 | 2020-09-02 | トヨタ自動車株式会社 | In-vehicle device, information processing method, and information processing program |
US11416784B2 (en) | 2018-06-14 | 2022-08-16 | American Express Travel Related Services Company, Inc. | Automated remote transactions between a vehicle and a lodging system |
US20200007410A1 (en) * | 2018-06-27 | 2020-01-02 | Viasat, Inc. | Vehicle communication service performance monitoring |
US11244222B2 (en) * | 2018-06-27 | 2022-02-08 | Sony Corporation | Artificial intelligence-enabled device for network connectivity independent delivery of consumable information |
US10629067B1 (en) | 2018-06-29 | 2020-04-21 | Tive, Inc. | Selective prevention of signal transmission by device during aircraft takeoff and/or landing |
EP3821576A4 (en) * | 2018-07-09 | 2022-03-02 | Saferide Technologies Ltd. | Optimizing size of protocol communication in a vehicle internal networks |
US10349059B1 (en) | 2018-07-17 | 2019-07-09 | Wowza Media Systems, LLC | Adjusting encoding frame size based on available network bandwidth |
US10841240B2 (en) * | 2018-07-18 | 2020-11-17 | EMC IP Holding Company LLC | Data distribution management in mobile network |
CA3107919A1 (en) | 2018-07-27 | 2020-01-30 | GoTenna, Inc. | Vinetm: zero-control routing using data packet inspection for wireless mesh networks |
US11025632B2 (en) | 2018-07-30 | 2021-06-01 | Cisco Technology, Inc. | Serial network communication using intelligent access policies |
US11601825B2 (en) * | 2018-08-08 | 2023-03-07 | Faraday&Future Inc. | Connected vehicle network data transfer optimization |
JP7408937B2 (en) * | 2018-08-10 | 2024-01-09 | 株式会社デンソー | Center device, distribution package generation method, and distribution package generation program |
US10939296B2 (en) * | 2018-08-20 | 2021-03-02 | Ford Global Technologies, Llc | Vehicle smart connection |
EP3614347B1 (en) * | 2018-08-21 | 2024-05-08 | Polestar Performance AB | Mobile phone as a car key |
US11064323B2 (en) * | 2018-08-23 | 2021-07-13 | Ford Global Technologies, Llc | Method and apparatus for peer to peer distribution strategy for updates |
US11109308B2 (en) * | 2018-08-28 | 2021-08-31 | Faraday&Future Inc. | Connected vehicle bandwidth-based network selection |
CN109116720A (en) * | 2018-08-31 | 2019-01-01 | 百度在线网络技术(北京)有限公司 | Long-range control method, device and the server of automatic driving vehicle |
FR3085567B1 (en) * | 2018-09-03 | 2020-07-31 | Airbus Operations Sas | COMMUNICATION NETWORK ON BOARD OF A VEHICLE, SUBSCRIBER EQUIPMENT OF SUCH COMMUNICATION NETWORK AND CORRESPONDING PROCEDURE |
CN116501932A (en) * | 2018-09-18 | 2023-07-28 | 唐纳森公司 | Filtration system with multi-layer data exchange capability |
US10745018B2 (en) | 2018-09-19 | 2020-08-18 | Byton Limited | Hybrid user recognition systems for vehicle access and control |
US10419408B1 (en) | 2018-09-24 | 2019-09-17 | Karamba Security | In-place authentication scheme for securing intra-vehicle communication |
US11010561B2 (en) | 2018-09-27 | 2021-05-18 | Apple Inc. | Sentiment prediction from textual data |
US10999156B2 (en) * | 2018-09-27 | 2021-05-04 | Aptiv Technologies Limited | Mobility services platform for self-healing mobility clients |
US11871451B2 (en) | 2018-09-27 | 2024-01-09 | Interdigital Patent Holdings, Inc. | Sub-band operations in unlicensed spectrums of new radio |
US11462215B2 (en) | 2018-09-28 | 2022-10-04 | Apple Inc. | Multi-modal inputs for voice commands |
US11188622B2 (en) * | 2018-09-28 | 2021-11-30 | Daniel Chien | Systems and methods for computer security |
CN109347993B (en) * | 2018-09-30 | 2021-11-05 | 新华三信息安全技术有限公司 | Port allocation method and device |
EP3861772B1 (en) | 2018-10-08 | 2023-11-29 | Huawei Technologies Co., Ltd. | User equipment and method for reducing interference for a communication session |
US20200114920A1 (en) * | 2018-10-11 | 2020-04-16 | Ford Global Technologies, Llc | Light-based lane-change control |
CN109561066B (en) * | 2018-10-15 | 2022-02-01 | 达闼机器人有限公司 | Data processing method and device, terminal and access point computer |
KR102132598B1 (en) * | 2018-10-23 | 2020-07-10 | 울산과학기술원 | Method and apparatus of partitioning memory bandwidth of system |
US11475898B2 (en) | 2018-10-26 | 2022-10-18 | Apple Inc. | Low-latency multi-speaker speech recognition |
EP3647984A1 (en) * | 2018-10-31 | 2020-05-06 | Hewlett-Packard Development Company, L.P. | Region restricted data routing |
US12010757B2 (en) * | 2018-11-01 | 2024-06-11 | Kyocera Corporation | Vehicle-to-vehicle unicast/groupcast communications based on a periodic discovery channel broadcast |
US11392284B1 (en) | 2018-11-01 | 2022-07-19 | Northrop Grumman Systems Corporation | System and method for implementing a dynamically stylable open graphics library |
DE102018218927A1 (en) * | 2018-11-07 | 2020-05-07 | Volkswagen Aktiengesellschaft | Data transmission device and data transmission method for a vehicle, device and method for a vehicle component of a vehicle and computer program |
US20200153926A1 (en) * | 2018-11-09 | 2020-05-14 | Toyota Motor North America, Inc. | Scalable vehicle data compression systems and methods |
US11032370B2 (en) * | 2018-11-14 | 2021-06-08 | Toyota Jidosha Kabushiki Kaisha | Wireless communications in a vehicular macro cloud |
EP3654605B1 (en) * | 2018-11-15 | 2024-02-21 | Nxp B.V. | Wireless vehicular communications with dynamic protocol-based relationships |
CN111224866B (en) * | 2018-11-23 | 2022-07-05 | 上海汽车集团股份有限公司 | Vehicle-mounted gateway equipment |
CN111223302B (en) * | 2018-11-23 | 2021-12-03 | 明创能源股份有限公司 | External coordinate real-time three-dimensional road condition auxiliary device for mobile carrier and system |
US10771379B2 (en) * | 2018-12-04 | 2020-09-08 | Juniper Networks, Inc. | Apparatus, system, and method for discovering network paths |
DE112018008095T5 (en) * | 2018-12-04 | 2021-08-26 | Mitsubishi Electric Corporation | Update management apparatus, update management system, and update management method |
US11248917B2 (en) * | 2018-12-06 | 2022-02-15 | Here Global B.V. | Method, apparatus, and computer program product for determining the criticality of an emergency |
KR102663210B1 (en) * | 2018-12-11 | 2024-05-02 | 현대자동차주식회사 | Control method for air-conditioning of vehicle during stop or parking |
US10694239B1 (en) | 2018-12-12 | 2020-06-23 | Sling Media Pvt Ltd | Systems, methods, and devices for optimizing streaming bitrate based on multiclient display profiles |
US11021147B2 (en) * | 2018-12-12 | 2021-06-01 | Toyota Research Institute, Inc. | Vehicles and methods for determining objects of driver focus |
US11182770B1 (en) | 2018-12-12 | 2021-11-23 | Square, Inc. | Systems and methods for sensing locations of near field communication devices |
DE102018221710A1 (en) | 2018-12-13 | 2020-06-18 | Volkswagen Aktiengesellschaft | Roof console for a vehicle |
US11832184B2 (en) | 2018-12-13 | 2023-11-28 | Lg Electronics Inc. | System and method for exchanging data or signals for vehicle |
TWI682091B (en) * | 2018-12-14 | 2020-01-11 | 財團法人工業技術研究院 | Intelligent door lock, control method thereof, and unlocking apparatus and method thereof |
US10826912B2 (en) | 2018-12-14 | 2020-11-03 | Daniel Chien | Timestamp-based authentication |
US10848489B2 (en) | 2018-12-14 | 2020-11-24 | Daniel Chien | Timestamp-based authentication with redirection |
DE102018222139A1 (en) * | 2018-12-18 | 2020-06-18 | Continental Automotive Gmbh | Telematics control unit with dispatcher for "Always On" radio connections |
US11840244B2 (en) * | 2018-12-21 | 2023-12-12 | Upstream Security, Ltd. | System and method for detecting behavioral anomalies among fleets of connected vehicles |
CA3124092A1 (en) | 2018-12-21 | 2020-06-25 | Polaris Industries Inc. | Managing recreational vehicles and accessories |
US11741763B2 (en) | 2018-12-26 | 2023-08-29 | Allstate Insurance Company | Systems and methods for system generated damage analysis |
SG10201811695WA (en) * | 2018-12-27 | 2020-07-29 | Mastercard International Inc | Methods and systems for a reliable payment transaction |
US11638059B2 (en) | 2019-01-04 | 2023-04-25 | Apple Inc. | Content playback on multiple devices |
FR3091592B1 (en) * | 2019-01-04 | 2021-01-29 | Balyo | Method for the control by a supervision server of the movement of a fleet of autonomous guided vehicles |
US10805146B2 (en) * | 2019-01-17 | 2020-10-13 | Northrop Grumman Systems Corporation | Mesh network |
WO2020148746A1 (en) | 2019-01-20 | 2020-07-23 | Arilou Information Security Technologies Ltd. | System and method for data compression based on data position in frames structure |
EP3915238A4 (en) * | 2019-01-24 | 2022-08-24 | Citrix Systems, Inc. | Optimized network selection |
US20200245141A1 (en) * | 2019-01-30 | 2020-07-30 | International Business Machines Corporation | Privacy protection of entities in a transportation system |
US11151866B2 (en) * | 2019-02-05 | 2021-10-19 | Intel Corporation | Enhanced high definition maps for a vehicle |
US11941922B2 (en) * | 2019-02-05 | 2024-03-26 | Sram, Llc | Component based automated identification of a configurable vehicle |
US11330401B2 (en) | 2019-02-06 | 2022-05-10 | At&T Intellectual Property I, L.P. | Centrally assisted associations with a local manager by peers in a peer to peer wireless network |
US11284404B2 (en) * | 2019-02-07 | 2022-03-22 | Raytheon Company | Apparatus and method for communications in congested radio frequency environments via dynamic usage exchange |
US11624630B2 (en) * | 2019-02-12 | 2023-04-11 | International Business Machines Corporation | Using augmented reality to present vehicle navigation requirements |
DE102019202025B4 (en) | 2019-02-15 | 2020-08-27 | Zf Friedrichshafen Ag | System and method for the safe operation of an automated vehicle |
US10834524B2 (en) | 2019-02-19 | 2020-11-10 | International Business Machines Corporation | Delegating cloud-side roles to devices |
US10814835B2 (en) * | 2019-02-28 | 2020-10-27 | Ford Global Technologies, Llc | Method and apparatus for vehicle assisted dynamic multi-factor authentication |
EP3918500B1 (en) * | 2019-03-05 | 2024-04-24 | Siemens Industry Software Inc. | Machine learning-based anomaly detections for embedded software applications |
US20220052871A1 (en) * | 2019-03-13 | 2022-02-17 | Nec Corporation | Vehicle control system, vehicle control method, and non-transitory computer-readable medium in which vehicle control program is stored |
EP3709594B1 (en) * | 2019-03-13 | 2023-09-13 | Nxp B.V. | Wireless vehicular communications with channel allocation |
US11348573B2 (en) | 2019-03-18 | 2022-05-31 | Apple Inc. | Multimodality in digital assistant systems |
US11292504B2 (en) * | 2019-03-20 | 2022-04-05 | Volvo Car Corporation | Vehicle having multiple driving positions |
US11184354B2 (en) | 2019-03-22 | 2021-11-23 | International Business Machines Corporation | Network-based authorization for disconnected devices |
DE102019002164A1 (en) * | 2019-03-26 | 2020-10-01 | Daimler Ag | Method for transmitting information from a central electronic computing device external to the vehicle to a first electronic computing device or to a second electronic computing device, as well as a network system |
US11516632B2 (en) * | 2019-03-26 | 2022-11-29 | Veniam, Inc. | Systems and methods for the dynamic management and control of multiple Wi-Fi radios in a network of moving things including, for example, autonomous vehicles |
US10575155B1 (en) * | 2019-03-27 | 2020-02-25 | GM Global Technology Operations LLC | Unified vehicle service framework for interfacing independently located providers and recipients |
JP7247712B2 (en) * | 2019-03-29 | 2023-03-29 | 株式会社デンソー | Relay device and relay method |
US11403624B2 (en) | 2019-04-01 | 2022-08-02 | Honda Motor Co., Ltd. | System and method for layered authorization to manage a payment wallet for in-vehicle payments |
US10703383B1 (en) | 2019-04-05 | 2020-07-07 | State Farm Mutual Automobile Insurance Company | Systems and methods for detecting software interactions for individual autonomous vehicles |
US11321972B1 (en) | 2019-04-05 | 2022-05-03 | State Farm Mutual Automobile Insurance Company | Systems and methods for detecting software interactions for autonomous vehicles within changing environmental conditions |
US11048261B1 (en) | 2019-04-05 | 2021-06-29 | State Farm Mutual Automobile Insurance Company | Systems and methods for evaluating autonomous vehicle software interactions for proposed trips |
DE102019205368B4 (en) * | 2019-04-12 | 2024-07-11 | Volkswagen Aktiengesellschaft | Motor vehicle |
WO2020223414A1 (en) | 2019-04-30 | 2020-11-05 | Phantom Auto Inc. | Low latency wireless communication system for teleoperated vehicle environments |
US11137814B2 (en) * | 2019-04-30 | 2021-10-05 | Thales Avionics, Inc. | Managing application execution by in-flight processing systems to protect health and capacity of multi-cell battery packs |
US10708887B1 (en) | 2019-05-01 | 2020-07-07 | Cypress Semiconductor Corporation | Devices, systems, and methods for predicting communication channel conditions |
DK201970509A1 (en) | 2019-05-06 | 2021-01-15 | Apple Inc | Spoken notifications |
US11423908B2 (en) | 2019-05-06 | 2022-08-23 | Apple Inc. | Interpreting spoken requests |
US11475884B2 (en) | 2019-05-06 | 2022-10-18 | Apple Inc. | Reducing digital assistant latency when a language is incorrectly determined |
US11307752B2 (en) | 2019-05-06 | 2022-04-19 | Apple Inc. | User configurable task triggers |
US11323435B2 (en) * | 2019-05-08 | 2022-05-03 | The Boeing Company | Method and apparatus for advanced security systems over a power line connection |
KR20200131639A (en) * | 2019-05-14 | 2020-11-24 | 현대자동차주식회사 | Gateway appratus and controlling method thereof |
KR102647646B1 (en) * | 2019-05-15 | 2024-03-13 | 현대자동차주식회사 | Method And Apparatus for operating a vehicle based on edge computing |
US11140099B2 (en) | 2019-05-21 | 2021-10-05 | Apple Inc. | Providing message response suggestions |
JP6896793B2 (en) * | 2019-05-27 | 2021-06-30 | 本田技研工業株式会社 | Information processing device |
US10993118B2 (en) * | 2019-05-30 | 2021-04-27 | Ford Global Technologies, Llc | Spectrum sharing infrastructure |
US11289073B2 (en) | 2019-05-31 | 2022-03-29 | Apple Inc. | Device text to speech |
DK180129B1 (en) | 2019-05-31 | 2020-06-02 | Apple Inc. | User activity shortcut suggestions |
DK201970510A1 (en) | 2019-05-31 | 2021-02-11 | Apple Inc | Voice identification in digital assistant systems |
US11496600B2 (en) | 2019-05-31 | 2022-11-08 | Apple Inc. | Remote execution of machine-learned models |
US11227599B2 (en) | 2019-06-01 | 2022-01-18 | Apple Inc. | Methods and user interfaces for voice-based control of electronic devices |
US11360641B2 (en) | 2019-06-01 | 2022-06-14 | Apple Inc. | Increasing the relevance of new available information |
US11240061B2 (en) * | 2019-06-03 | 2022-02-01 | Progress Rail Locomotive Inc. | Methods and systems for controlling locomotives |
EP3981131A4 (en) * | 2019-06-04 | 2022-12-14 | Phantom Auto Inc. | Platform for redundant wireless communications optimization |
US11189152B2 (en) | 2019-06-05 | 2021-11-30 | Donaldson Company, Inc. | Multi-zone filtration monitoring systems and methods |
JP7389144B2 (en) * | 2019-06-07 | 2023-11-29 | エヌイーシー ラボラトリーズ ヨーロッパ ゲーエムベーハー | Methods and systems for dynamic event identification and dissemination |
US11455571B2 (en) | 2019-06-14 | 2022-09-27 | Bank Of America Corporation | Data structure tool |
KR20200143881A (en) * | 2019-06-17 | 2020-12-28 | 현대자동차주식회사 | Controller commnication device and method thereof |
US11227490B2 (en) | 2019-06-18 | 2022-01-18 | Toyota Motor North America, Inc. | Identifying changes in the condition of a transport |
US11184833B2 (en) * | 2019-06-19 | 2021-11-23 | Citrix Systems, Inc. | Bandwidth sharing amongst trusted peers |
US11140524B2 (en) * | 2019-06-21 | 2021-10-05 | International Business Machines Corporation | Vehicle to vehicle messaging |
US11620389B2 (en) | 2019-06-24 | 2023-04-04 | University Of Maryland Baltimore County | Method and system for reducing false positives in static source code analysis reports using machine learning and classification techniques |
US11381636B2 (en) * | 2019-06-28 | 2022-07-05 | Intel Corporation | Network function execution in information centric networks |
CN112224217B (en) * | 2019-06-30 | 2021-09-03 | 比亚迪股份有限公司 | Integrated control chip, environment recognition method and device, storage medium and vehicle |
US11665754B2 (en) * | 2019-07-01 | 2023-05-30 | AINA Wireless Finland Oy | Wireless communication network enabling combined use of several different network technologies |
US11368471B2 (en) * | 2019-07-01 | 2022-06-21 | Beijing Voyager Technology Co., Ltd. | Security gateway for autonomous or connected vehicles |
JP7379888B2 (en) * | 2019-07-08 | 2023-11-15 | オムロン株式会社 | Control system and control method |
US11095741B2 (en) * | 2019-07-11 | 2021-08-17 | Ghost Locomotion Inc. | Value-based transmission in an autonomous vehicle |
US11089560B2 (en) * | 2019-07-15 | 2021-08-10 | Cisco Technology, Inc. | Distributed time sync in a directed acyclic graph of a time-synchronized network based on correlating timing information from higher network devices |
US11206588B2 (en) * | 2019-07-22 | 2021-12-21 | Microsoft Technology Licensing, Llc | Network connection planning using crowd-sourced data |
JP7164494B2 (en) * | 2019-07-26 | 2022-11-01 | トヨタ自動車株式会社 | Charge/discharge management system |
US11109394B2 (en) | 2019-07-30 | 2021-08-31 | Cypress Semiconductor Corporation | Methods, systems and devices for providing differentiated quality of service for wireless communication devices |
US11533614B1 (en) * | 2019-07-31 | 2022-12-20 | United Services Automobile Association (Usaa) | Systems and methods of multi-factor authentication utilizing a vehicle |
US10931638B1 (en) * | 2019-07-31 | 2021-02-23 | Capital One Services, Llc | Automated firewall feedback from network traffic analysis |
US11996108B2 (en) | 2019-08-01 | 2024-05-28 | Dolby Laboratories Licensing Corporation | System and method for enhancement of a degraded audio signal |
US11095735B2 (en) * | 2019-08-06 | 2021-08-17 | Tealium Inc. | Configuration of event data communication in computer networks |
US11781875B2 (en) * | 2019-08-21 | 2023-10-10 | Toyota Motor Engineering & Manufacturing North America, Inc. | Apparatus and method for forming and analyzing connected roads |
US11165787B2 (en) | 2019-08-26 | 2021-11-02 | Bank Of America Corporation | System for authorization of electronic data access and processing functions within a distributed server network |
CN112805645B (en) * | 2019-09-02 | 2023-07-04 | 深圳市元征科技股份有限公司 | Vehicle remote diagnosis method and related device |
US11808858B2 (en) * | 2019-09-04 | 2023-11-07 | Pony Ai Inc. | Systems and methods for constructing and utilizing field-of-view (FOV) information |
CN112477781B (en) * | 2019-09-12 | 2022-08-26 | 华为技术有限公司 | System and method for realizing electronic control function in automobile and automobile |
CN118124505A (en) * | 2019-09-12 | 2024-06-04 | 华为技术有限公司 | System and method for realizing electronic control function in automobile and automobile |
US10940832B1 (en) * | 2019-09-18 | 2021-03-09 | Toyota Motor North America, Inc. | Identifying suspicious events relating to a vehicle |
US11538287B2 (en) | 2019-09-20 | 2022-12-27 | Sonatus, Inc. | System, method, and apparatus for managing vehicle data collection |
CN114651427B (en) | 2019-09-20 | 2024-08-27 | 桑纳特斯公司 | Systems, methods, and apparatus for supporting hybrid network communications on a vehicle |
US11488406B2 (en) | 2019-09-25 | 2022-11-01 | Apple Inc. | Text detection using global geometry estimators |
EP4035442A4 (en) * | 2019-09-27 | 2024-01-24 | The Regents of The University of Michigan | Automated can message translator |
US11641365B2 (en) | 2019-10-10 | 2023-05-02 | Honeywell International Inc. | Hybrid intrusion detection model for cyberattacks in avionics internet gateways using edge analytics |
EP3806518A1 (en) * | 2019-10-10 | 2021-04-14 | Honeywell International Inc. | Hybrid intrusion detection model for cyber-attacks in avionics internet gateways using edge analytics |
US11064030B2 (en) | 2019-10-17 | 2021-07-13 | Cisco Technology, Inc. | Automatic on-boarding agent for IOT edge routers in connected vehicles |
US12088473B2 (en) | 2019-10-23 | 2024-09-10 | Aryaka Networks, Inc. | Method, device and system for enhancing predictive classification of anomalous events in a cloud-based application acceleration as a service environment |
US11365007B2 (en) * | 2019-10-24 | 2022-06-21 | Panasonic Avionics Corporation | Systems and methods for providing a wake-up user interface for a night mode on transportation vehicles |
KR102615478B1 (en) * | 2019-10-24 | 2023-12-19 | 현대모비스 주식회사 | Automotive sensor integration module |
US11391595B2 (en) * | 2019-10-25 | 2022-07-19 | Here Global B.V. | Method, apparatus, and computer program product for updating a map database |
EP3816749A1 (en) | 2019-10-29 | 2021-05-05 | Volkswagen AG | Teleoperated driving of a vehicle |
EP3817413A1 (en) * | 2019-10-30 | 2021-05-05 | Volkswagen AG | Vehicle, computer program, method, apparatus for data communication services of a vehicle |
US20210134084A1 (en) * | 2019-10-30 | 2021-05-06 | Honeywell International Inc. | Communication management using rules-based decision systems and artificial intelligence |
CN110891023B (en) * | 2019-10-31 | 2021-12-14 | 上海赫千电子科技有限公司 | Signal routing conversion method and device based on priority strategy |
KR20210053801A (en) * | 2019-11-04 | 2021-05-12 | 성균관대학교산학협력단 | Vehicular mobility management for ip-based vehicular networks |
CN114868372B (en) * | 2019-11-12 | 2024-09-06 | 马维尔亚洲私人有限公司 | Automotive network with centralized storage |
US11983425B2 (en) * | 2019-11-12 | 2024-05-14 | Toyota Motor Engineering & Manufacturing North America, Inc. | Vehicular communications redundant data identification and removal |
EP3828652A1 (en) * | 2019-11-26 | 2021-06-02 | Siemens Aktiengesellschaft | Method and test arrangement for testing an autonomous behaviour for a technical system |
CN111083708B (en) * | 2019-12-02 | 2022-09-23 | 北京邮电大学 | V2V communication heterogeneous frequency spectrum allocation method based on interference perception multiple graphs |
US11677754B2 (en) | 2019-12-09 | 2023-06-13 | Daniel Chien | Access control systems and methods |
US12030391B2 (en) * | 2019-12-11 | 2024-07-09 | Lyft, Inc. | Modular bicycle designs |
FR3104878A1 (en) * | 2019-12-12 | 2021-06-18 | Psa Automobiles Sa | Vehicle communication method and device |
US11416874B1 (en) * | 2019-12-26 | 2022-08-16 | StratoKey Pty Ltd. | Compliance management system |
US11395118B2 (en) * | 2020-01-06 | 2022-07-19 | Toyota Motor Engineering & Manufacturing North America, Inc. | Vehicular micro cloud hubs |
US11489792B2 (en) * | 2020-01-10 | 2022-11-01 | Toyota Motor Engineering & Manufacturing North America, Inc. | Vehicular micro clouds for on-demand vehicle queue analysis |
US11102519B2 (en) * | 2020-01-15 | 2021-08-24 | Panasonic Avionics Corporation | Centralized architecture for in-vehicle entertainment systems |
US11159489B2 (en) * | 2020-01-29 | 2021-10-26 | Dell Products L.P. | Multi-link VPN link selection system |
US11196799B2 (en) * | 2020-02-03 | 2021-12-07 | Dell Products L.P. | Redirection of USB devices from hardware isolated virtual desktop infrastructure clients |
US11287806B2 (en) | 2020-02-11 | 2022-03-29 | Uatc, Llc | Vehicle computing system cooling systems |
DE102020103658A1 (en) | 2020-02-12 | 2021-08-12 | Horsch Maschinen Gmbh | Communication device for an agricultural machine and method for data transmission between an agricultural machine and an external server |
DE102020104405A1 (en) * | 2020-02-19 | 2021-08-19 | HELLA GmbH & Co. KGaA | Device and method for connecting a service-oriented communication with a signal-based communication |
US11665760B2 (en) * | 2020-02-24 | 2023-05-30 | Qualcomm Incorporated | Service set identifier (SSID) for wireless communications using multiple link aggregation |
US11727271B2 (en) | 2020-02-27 | 2023-08-15 | Calamp Corp. | Systems and methods for identifying a vehicle platform using machine learning on vehicle bus data |
CN111246485B (en) * | 2020-02-27 | 2022-09-20 | 华南理工大学 | Internet of vehicles resource allocation method under high-density vehicle-mounted communication environment |
WO2021173141A1 (en) * | 2020-02-27 | 2021-09-02 | Calamp Corp. | Systems and methods for identifying a vehicle platform using machine learning on vehicle bus data |
US11587376B2 (en) | 2020-02-27 | 2023-02-21 | CalAmpCorp. | Systems and methods for delivering vehicle parameters to a remote device via vehicle module identities |
US10972760B1 (en) * | 2020-03-05 | 2021-04-06 | Panasonic Avionics Corporation | Secure testing of vehicle entertainment systems for commercial passenger vehicles |
US11745548B2 (en) | 2020-03-06 | 2023-09-05 | Tactile Mobility Ltd. | Estimating an effective radius of a tire of a vehicle |
US12094259B2 (en) | 2020-03-06 | 2024-09-17 | Sonatus, Inc. | System, method, and apparatus for managing vehicle automation |
US11397589B2 (en) * | 2020-03-06 | 2022-07-26 | EMC IP Holding Company LLC | Snapshot transmission from storage array to cloud using multi-path input-output |
DE112021001453T5 (en) * | 2020-03-06 | 2023-01-05 | Denso Corporation | VEHICLE DATA COMMUNICATION DEVICE, CENTRAL DEVICE, DATA COMMUNICATION METHOD AND COMPUTER PROGRAM |
WO2021176383A1 (en) | 2020-03-06 | 2021-09-10 | Tactile Mobility Ltd. | Vehicle monitor |
GB2593228B (en) * | 2020-03-20 | 2022-09-07 | Perkins Engines Co Ltd | Charging of electric vehicles and construction machines |
EP3886373B1 (en) * | 2020-03-24 | 2023-12-27 | Rohde & Schwarz GmbH & Co. KG | Communication system and method for operating a communication system |
US11314495B2 (en) | 2020-03-30 | 2022-04-26 | Amazon Technologies, Inc. | In-vehicle synthetic sensor orchestration and remote synthetic sensor service |
CN111462487B (en) * | 2020-03-31 | 2021-01-22 | 长安大学 | Optimized edge computing node selection method and system in Internet of vehicles environment |
US20210314752A1 (en) * | 2020-04-03 | 2021-10-07 | Cavh Llc | Device allocation system |
EP4144050A1 (en) * | 2020-04-29 | 2023-03-08 | Lenovo (Singapore) Pte. Ltd. | Application requirements for vehicle-to-everything applications |
WO2021222808A1 (en) * | 2020-05-01 | 2021-11-04 | Neutron Holdings, Inc. Dba Lime | Power tier management system for light electric vehicles |
US11061543B1 (en) | 2020-05-11 | 2021-07-13 | Apple Inc. | Providing relevant data items based on context |
US11038934B1 (en) | 2020-05-11 | 2021-06-15 | Apple Inc. | Digital assistant hardware abstraction |
US11755276B2 (en) | 2020-05-12 | 2023-09-12 | Apple Inc. | Reducing description length based on confidence |
EP3909804A1 (en) * | 2020-05-13 | 2021-11-17 | Ningbo Geely Automobile Research & Development Co. Ltd. | A method for achieving a desired operational state in a vehicle |
DE102020113977A1 (en) | 2020-05-25 | 2021-11-25 | Bayerische Motoren Werke Aktiengesellschaft | SYSTEM FOR DATA TRANSFER IN A MOTOR VEHICLE, PROCEDURES AND MOTOR VEHICLE |
US11463850B2 (en) * | 2020-05-29 | 2022-10-04 | Qualcomm Incorporated | Upper layers realization of unicast for C-V2X |
US11509463B2 (en) | 2020-05-31 | 2022-11-22 | Daniel Chien | Timestamp-based shared key generation |
US11438145B2 (en) | 2020-05-31 | 2022-09-06 | Daniel Chien | Shared key generation based on dual clocks |
FR3111204B1 (en) * | 2020-06-04 | 2023-12-22 | Renault | Securing the connection between a vehicle and a remote server for managing said vehicle |
US20210392146A1 (en) * | 2020-06-16 | 2021-12-16 | Zscaler, Inc. | Machine Learning-based user and entity behavior analysis for network security |
US11089118B1 (en) * | 2020-06-19 | 2021-08-10 | Northrop Grumman Systems Corporation | Interlock for mesh network |
CN111703385B (en) * | 2020-06-28 | 2022-03-11 | 广州易点智慧出行科技有限公司 | Content interaction method and vehicle |
CN113938983B (en) * | 2020-06-29 | 2023-02-28 | 成都极米科技股份有限公司 | Multi-link terminal, method and device for performing link exchange and storage medium |
US20220014598A1 (en) * | 2020-07-09 | 2022-01-13 | Ge Aviation Systems Llc | Data service tracker module for a communication system and method of determining a set of data couplings |
FR3112446B1 (en) * | 2020-07-10 | 2022-12-09 | Alstom Transp Tech | Vehicle Condition Diagnostic Kit |
US11490204B2 (en) | 2020-07-20 | 2022-11-01 | Apple Inc. | Multi-device audio adjustment coordination |
US11438683B2 (en) | 2020-07-21 | 2022-09-06 | Apple Inc. | User identification using headphones |
US11327981B2 (en) | 2020-07-28 | 2022-05-10 | Bank Of America Corporation | Guided sampling for improved quality testing |
US11659372B2 (en) * | 2020-07-30 | 2023-05-23 | Toyota Motor Engineering & Manufacturing North America, Inc. | Adaptive sensor data sharing for a connected vehicle |
JP7364539B2 (en) * | 2020-08-03 | 2023-10-18 | 本田技研工業株式会社 | Network management device, network management method, and program |
US11681828B2 (en) * | 2020-08-05 | 2023-06-20 | Ford Global Technologies, Llc | Passthrough mobile application policy |
US11608081B2 (en) * | 2020-08-06 | 2023-03-21 | Gm Cruise Holdings Llc | Autonomous vehicle low battery management |
JP7438892B2 (en) * | 2020-08-20 | 2024-02-27 | 本田技研工業株式会社 | Information processing device, information processing method, and program |
US11665619B2 (en) | 2020-08-26 | 2023-05-30 | Honda Motor Co., Ltd. | Data and connectivity management systems and methods thereof |
KR20220031442A (en) * | 2020-09-04 | 2022-03-11 | 현대자동차주식회사 | V2x mesh network system and operating method thereof |
US20220078077A1 (en) * | 2020-09-08 | 2022-03-10 | Amazon Technologies, Inc. | Virtual vehicle domain control unit (dcu) service and orchestration environments |
US11597395B2 (en) | 2020-09-16 | 2023-03-07 | Toyota Motor Engineering & Manufacturing North America, Inc. | Systems and methods to manage vehicles under anomalous driving behavior |
EP3975083A1 (en) * | 2020-09-29 | 2022-03-30 | Deutsche Telekom AG | A method for optimizing ad-hoc provision of capacity in a mobile communications network, and system |
EP3979160A1 (en) * | 2020-09-30 | 2022-04-06 | SITA Switzerland Sàrl | Method and system for identifying an optimised internet connectivity configuration |
JP7484633B2 (en) * | 2020-09-30 | 2024-05-16 | 株式会社デンソー | Shared storage management device and shared storage management method |
US11709061B2 (en) | 2020-10-16 | 2023-07-25 | Argo AI, LLC | Systems and methods for multi-modal transfer capabilities for smart infrastructure |
US11935310B2 (en) | 2020-10-27 | 2024-03-19 | Toyota Motor Engineering & Manufacturing North America, Inc. | Systems and methods to regulate joining and leaving a vehicular micro cloud |
US20220135047A1 (en) * | 2020-11-03 | 2022-05-05 | Toyota Motor North America, Inc. | Managing data delivery in a transport |
KR20220062939A (en) * | 2020-11-09 | 2022-05-17 | 현대자동차주식회사 | Apparatus and method for emergency call sending |
DE102020131284A1 (en) | 2020-11-26 | 2022-06-02 | Bayerische Motoren Werke Aktiengesellschaft | Device and method for data communication between an on-board network and a third-party component |
DE102020214945A1 (en) * | 2020-11-27 | 2022-06-02 | Robert Bosch Gesellschaft mit beschränkter Haftung | Method for checking a message in a communication system |
CN112637813B (en) * | 2020-12-16 | 2022-09-13 | 温州大学 | C-V2X dynamic power control method based on channel inversion |
US11451492B2 (en) * | 2020-12-22 | 2022-09-20 | Honeywell International Inc. | Methods, systems, and apparatuses for enhanced parallelism of time-triggered ethernet traffic using interference-cognizant network scheduling |
US11463470B2 (en) * | 2020-12-29 | 2022-10-04 | Trane International Inc. | Network security management for a building automation system |
US11987144B2 (en) | 2021-01-13 | 2024-05-21 | Toyota Motor North America, Inc. | Transport energy transfer using real-time cost information |
US11623540B2 (en) | 2021-01-13 | 2023-04-11 | Toyota Motor North America, Inc. | Transport recharge level determination |
US11887411B2 (en) | 2021-01-27 | 2024-01-30 | Amazon Technologies, Inc. | Vehicle data extraction service |
JP2022124165A (en) * | 2021-02-15 | 2022-08-25 | キオクシア株式会社 | memory system |
CN113170004B (en) * | 2021-03-15 | 2023-01-06 | 华为技术有限公司 | Data transmission method, device and system |
JP7535002B2 (en) * | 2021-03-30 | 2024-08-15 | 本田技研工業株式会社 | In-vehicle electronic system, vehicle, control method, and program |
US11789807B1 (en) | 2021-03-30 | 2023-10-17 | Amazon Technologies, Inc. | Autonomous management of communication links |
US11743334B2 (en) | 2021-03-31 | 2023-08-29 | Amazon Technologies, Inc. | In-vehicle distributed computing environment |
US20220322242A1 (en) * | 2021-04-05 | 2022-10-06 | Ntt Docomo, Inc. | Data-driven uplink power control in a wireless network |
US11853100B2 (en) * | 2021-04-12 | 2023-12-26 | EMC IP Holding Company LLC | Automated delivery of cloud native application updates using one or more user-connection gateways |
DE102021203786A1 (en) | 2021-04-16 | 2022-10-20 | Volkswagen Aktiengesellschaft | Method for operating a driver assistance system and vehicle with a driver assistance system |
CN115273453B (en) * | 2021-04-30 | 2023-12-26 | 阿波罗智联(北京)科技有限公司 | Method and device for managing road side equipment in vehicle-road cooperation, cloud control platform and system |
US11798136B2 (en) | 2021-06-10 | 2023-10-24 | Bank Of America Corporation | Automated teller machine for detecting security vulnerabilities based on document noise removal |
US11492119B1 (en) * | 2021-06-23 | 2022-11-08 | Panasonic Avionics Corporation | Methods and systems for streaming content on a transportation vehicle |
US11445231B1 (en) | 2021-06-23 | 2022-09-13 | Panasonic Avionics Corporation | Credential management systems and associated methods thereof for streaming content on a transportation vehicle |
US11909850B1 (en) * | 2021-06-23 | 2024-02-20 | Amazon Technologies, Inc. | Dynamic improvement of a communication channel |
US11640389B2 (en) | 2021-07-23 | 2023-05-02 | Bank Of America Corporation | Hash-based identification of data corruption issues in time-series data |
US11645252B2 (en) | 2021-07-23 | 2023-05-09 | Bank Of America Corporation | System and method for efficiently validating time-series data using a hash-based representation of the data |
GB2609258B (en) * | 2021-07-27 | 2024-01-31 | Cubic Telecom Ltd | Vehicle data |
US11726940B2 (en) | 2021-08-06 | 2023-08-15 | Lear Corporation | System for communicating with removable components |
CN118119540A (en) * | 2021-08-18 | 2024-05-31 | 特斯拉公司 | Machine learning model for predicting driving events |
US12074768B1 (en) | 2021-09-09 | 2024-08-27 | T-Mobile Usa, Inc. | Dynamic configuration of consensus-based network |
DE102021123597A1 (en) * | 2021-09-13 | 2023-03-16 | Dr. Ing. H.C. F. Porsche Aktiengesellschaft | Process and control unit for the automated application of driver assistance systems in series production |
GB2610853A (en) * | 2021-09-17 | 2023-03-22 | Aptiv Tech Ltd | In-vehicle video conferencing system |
US12021806B1 (en) | 2021-09-21 | 2024-06-25 | Apple Inc. | Intelligent message delivery |
KR20230052484A (en) * | 2021-10-13 | 2023-04-20 | 현대자동차주식회사 | Vehicle and controlling method of vehicle. |
US11556403B1 (en) | 2021-10-19 | 2023-01-17 | Bank Of America Corporation | System and method for an application programming interface (API) service modification |
CN114062806B (en) * | 2021-11-08 | 2023-06-30 | 广州小鹏汽车科技有限公司 | Vehicle testing method and device |
US11843987B2 (en) * | 2021-11-16 | 2023-12-12 | Crius Technology Group, Inc. | Methods, systems, and apparatus for routing data over medium and high voltage power lines |
DE102021212896A1 (en) * | 2021-11-17 | 2023-05-17 | Zf Friedrichshafen Ag | Electronic circuit, control device with such a circuit and method for communicating data |
US11683286B2 (en) * | 2021-11-18 | 2023-06-20 | Cisco Technology, Inc. | Anonymizing server-side addresses |
US12034707B2 (en) | 2021-11-18 | 2024-07-09 | Cisco Technology, Inc. | Randomizing server-side addresses |
KR20240093995A (en) * | 2021-11-29 | 2024-06-24 | 아마존 테크놀로지스, 인크. | Dynamic vehicle data extraction service |
US11902374B2 (en) | 2021-11-29 | 2024-02-13 | Amazon Technologies, Inc. | Dynamic vehicle data extraction service |
US20230188491A1 (en) * | 2021-12-13 | 2023-06-15 | Ben Iceton | Method and Related Systems for Dynamic Notification Management |
SE2151550A1 (en) * | 2021-12-17 | 2023-06-18 | Icomera Ab | Wireless communication system for moving vehicles, such as trains, with improved prioritization |
WO2023141506A1 (en) * | 2022-01-19 | 2023-07-27 | Commscope Technologies Llc | System and method of cloud based congestion control for virtualized base station |
US11652655B1 (en) | 2022-01-31 | 2023-05-16 | Zoom Video Communications, Inc. | Audio capture device selection for remote conference participants |
US11431793B1 (en) | 2022-02-04 | 2022-08-30 | Bank Of America Corporation | System and method using peer-to-peer connections with ultra-wideband for an interaction |
US11892940B2 (en) | 2022-02-09 | 2024-02-06 | Bank Of America Corporation | Network integrated diagnostic system and predictive analysis tool for mitigating service impacts on application services |
US12052261B2 (en) | 2022-02-15 | 2024-07-30 | Bank Of America Corporation | System and method for authenticating the receiving end of data transmission via LiFi and holochain network |
US12074641B2 (en) | 2022-02-15 | 2024-08-27 | Bank Of America Corporation | System and method for secured data transmission using LiFi and holochain network |
US20230286451A1 (en) * | 2022-03-01 | 2023-09-14 | Terraline, Inc. | Vehicle interface system and/or method |
DE102022203392A1 (en) | 2022-04-06 | 2023-03-16 | Zf Friedrichshafen Ag | Data processing device and processing system on board a vehicle |
US11983974B2 (en) | 2022-05-13 | 2024-05-14 | Bank Of America Corporation | System and method for ultra-wideband short-range location access |
US11950017B2 (en) | 2022-05-17 | 2024-04-02 | Digital Ally, Inc. | Redundant mobile video recording |
US11606583B1 (en) * | 2022-06-08 | 2023-03-14 | Panasonic Avionics Corporation | Distributed data storage for in-vehicle entertainment system |
DE102022115191B4 (en) | 2022-06-17 | 2024-07-04 | Cariad Se | Method and motor vehicle control unit for cyclically generating current observation data of at least one determined observation variable, which are distributed in a data network of a motor vehicle |
US12022135B2 (en) | 2022-09-09 | 2024-06-25 | Hcl Technologies Limited | Method and system for providing media content to in-flight wireless media servers |
WO2024059132A1 (en) * | 2022-09-13 | 2024-03-21 | Fort Robotics, Inc. | Method for decreasing probability of undetected errors on large messages over a black channel |
US11972682B2 (en) | 2022-09-18 | 2024-04-30 | International Business Machines Corporation | Displaying vehicle information to a pedestrian using a visual indicator |
US20240121258A1 (en) * | 2022-10-05 | 2024-04-11 | Denso Corporation | System and method for dynamically updating firewall rules for a vehicle network of a vehicle |
US11818235B1 (en) | 2022-11-21 | 2023-11-14 | Guardknox Cyber Technologies Ltd. | Systems, devices and methods for hardware accelerated universal routing interface |
DE102022212629A1 (en) | 2022-11-25 | 2024-05-29 | Zf Friedrichshafen Ag | Data processing device and processing system on board a vehicle |
US20240275634A1 (en) * | 2023-02-13 | 2024-08-15 | Garrett Transportation I Inc. | Diagnostic system for engine management system |
US12070971B1 (en) | 2023-07-19 | 2024-08-27 | Tactile Mobility Ltd. | Device and method for automatically determining wear of tires |
Citations (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6505780B1 (en) * | 2001-12-05 | 2003-01-14 | Koninklijke Philips Electronics N.V. | Personalize vehicle settings using RF tags |
US6542071B1 (en) * | 1999-11-09 | 2003-04-01 | Mazda Motor Corporation | Opening-closing member control apparatus for vehicle |
US20040249915A1 (en) * | 2002-05-21 | 2004-12-09 | Russell Jesse E. | Advanced multi-network client device for wideband multimedia access to private and public wireless networks |
US20050038581A1 (en) * | 2000-08-18 | 2005-02-17 | Nnt, Inc. | Remote Monitoring, Configuring, Programming and Diagnostic System and Method for Vehicles and Vehicle Components |
US20050060070A1 (en) * | 2000-08-18 | 2005-03-17 | Nnt, Inc. | Wireless communication framework |
US20050096836A1 (en) * | 2002-05-16 | 2005-05-05 | Katsuaki Minami | Vehicle operation information management evaluation system |
US20060282554A1 (en) * | 2005-04-14 | 2006-12-14 | Nokia Corporation | Method, apparatus and computer program providing network-associated system priority list for multimode system selection |
US20070030119A1 (en) * | 2005-07-08 | 2007-02-08 | Mitsubishi Denki Kabushiki Kaisha | Communication apparatus for vehicle |
US20070030136A1 (en) * | 2005-08-03 | 2007-02-08 | Denso Corporation | On-board illumination controlling system and method |
US20070186106A1 (en) * | 2006-01-26 | 2007-08-09 | Ting David M | Systems and methods for multi-factor authentication |
US20070255797A1 (en) * | 2006-04-28 | 2007-11-01 | Dunn Douglas L | Method for selecting an air interface using an access list on a multi-mode wireless device |
US20080238135A1 (en) * | 2007-03-29 | 2008-10-02 | Aisin Seiki Kabushiki Kaisha | Control apparatus of opening and closing body for vehicle |
US20090163175A1 (en) * | 2007-12-24 | 2009-06-25 | Guangming Shi | Virtual sim card for mobile handsets |
US20090284359A1 (en) * | 2008-05-19 | 2009-11-19 | Gm Global Technology Operations, Inc. | Vehicle-setting-based driver identification system |
US20100049626A1 (en) * | 2007-03-09 | 2010-02-25 | Airbiquity Inc. | In-vehicle mobile music purchase |
US20100087987A1 (en) * | 2008-10-08 | 2010-04-08 | Gm Global Technoloogy Operations, Inc. | Apparatus and Method for Vehicle Driver Recognition and Customization Using Onboard Vehicle System Settings |
US20100167702A1 (en) * | 2008-12-29 | 2010-07-01 | General Motors Corporation | Voice fallback strategy for vehicle originated cellular communication to a call center |
US20100167721A1 (en) * | 2008-12-29 | 2010-07-01 | General Motors Corporation | Vehicle originated cellular communication to a call center |
US20100210304A1 (en) * | 2009-02-13 | 2010-08-19 | At&T Intellectual Property I, L.P. | Systems and Methods for Multi-Device Wireless SIM Management |
US7849020B2 (en) * | 2005-04-19 | 2010-12-07 | Microsoft Corporation | Method and apparatus for network transactions |
US20110144980A1 (en) * | 2009-12-11 | 2011-06-16 | General Motors Llc | System and method for updating information in electronic calendars |
US20110246317A1 (en) * | 2009-10-23 | 2011-10-06 | Apriva, Llc | System and device for facilitating a transaction through use of a proxy account code |
US20110306318A1 (en) * | 2010-06-14 | 2011-12-15 | Clive Edward Rodgers | Apparatus and methods for provisioning subscriber identity data in a wireless network |
US20110307143A1 (en) * | 2003-12-15 | 2011-12-15 | Honda Motor Co., Ltd. | Method And System For Facilitating The Exchange Of Information Between A Vehicle And A Remote Location |
US20120226413A1 (en) * | 2009-04-29 | 2012-09-06 | Gm Global Technology Operations Llc. | Hierarchical recognition of vehicle driver and select activation of vehicle settings based on the recognition |
US8352730B2 (en) * | 2004-12-20 | 2013-01-08 | Proxense, Llc | Biometric personal data key (PDK) authentication |
US8514825B1 (en) * | 2011-01-14 | 2013-08-20 | Cisco Technology, Inc. | System and method for enabling a vehicular access network in a vehicular environment |
US8762288B2 (en) * | 2009-04-22 | 2014-06-24 | The Western Union Company | Methods and systems for establishing an identity confidence database |
Family Cites Families (328)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7050897B2 (en) | 1992-05-05 | 2006-05-23 | Automotive Technologies International, Inc. | Telematics system |
US6735506B2 (en) | 1992-05-05 | 2004-05-11 | Automotive Technologies International, Inc. | Telematics system |
US5315161A (en) * | 1990-09-27 | 1994-05-24 | Ncr Corporation | Power failure detection and shut down timer |
CA2064646A1 (en) | 1991-04-02 | 1992-10-03 | Kipling W. Fyfe | Automatic number assignment module selection for mobile telephone |
SE467559B (en) | 1991-04-12 | 1992-08-03 | Comvik Gsm Ab | PHONE SYSTEM PROCEDURES |
US6823244B2 (en) | 1995-06-07 | 2004-11-23 | Automotive Technologies International, Inc. | Vehicle part control system including electronic sensors |
US7082359B2 (en) | 1995-06-07 | 2006-07-25 | Automotive Technologies International, Inc. | Vehicular information and monitoring system and methods |
US5604787A (en) | 1994-10-07 | 1997-02-18 | Motorola, Inc. | Method and apparatus for transferring information to a device in a communication system |
GB2294787A (en) | 1994-11-07 | 1996-05-08 | Motorola Israel Ltd | Electronic device and method of cloning |
US8229624B2 (en) | 1995-06-07 | 2012-07-24 | American Vehicular Sciences Llc | Vehicle diagnostic information generating and transmission systems and methods |
US8019501B2 (en) | 1995-06-07 | 2011-09-13 | Automotive Technologies International, Inc. | Vehicle diagnostic and prognostic methods and systems |
US8024084B2 (en) | 1995-06-07 | 2011-09-20 | Automotive Technologies International, Inc. | Vehicle diagnostic techniques |
US7650210B2 (en) * | 1995-06-07 | 2010-01-19 | Automotive Technologies International, Inc. | Remote vehicle diagnostic management |
US8060282B2 (en) | 1995-06-07 | 2011-11-15 | Automotive Technologies International, Inc. | Vehicle component control methods and systems based on vehicle stability |
US8169311B1 (en) | 1999-12-15 | 2012-05-01 | Automotive Technologies International, Inc. | Wireless transmission system for vehicular component control and monitoring |
US6720920B2 (en) | 1997-10-22 | 2004-04-13 | Intelligent Technologies International Inc. | Method and arrangement for communicating between vehicles |
US7630802B2 (en) | 1995-06-07 | 2009-12-08 | Automotive Technologies International, Inc. | Information management and monitoring system and method |
US7889096B2 (en) | 2000-09-08 | 2011-02-15 | Automotive Technologies International, Inc. | Vehicular component control using wireless switch assemblies |
US8036788B2 (en) | 1995-06-07 | 2011-10-11 | Automotive Technologies International, Inc. | Vehicle diagnostic or prognostic message transmission systems and methods |
WO1997001103A1 (en) * | 1995-06-21 | 1997-01-09 | Jones, Gerald, Patrick | Battery monitor |
US5545967A (en) * | 1995-07-21 | 1996-08-13 | Precision Automation Systems, Inc. | Automatic battery management system |
US6078652A (en) | 1995-07-21 | 2000-06-20 | Call Manage, Ltd. | Least cost routing system |
GB2304257A (en) | 1995-08-08 | 1997-03-12 | Northern Telecom Ltd | Method of Effecting SIM Card Replacement |
US5794164A (en) | 1995-11-29 | 1998-08-11 | Microsoft Corporation | Vehicle computer system |
US5737215A (en) | 1995-12-13 | 1998-04-07 | Caterpillar Inc. | Method and apparatus for comparing machines in fleet |
SE506584C2 (en) | 1996-05-13 | 1998-01-19 | Ericsson Telefon Ab L M | Method and apparatus for monitoring mobile communication device |
GB2313257A (en) | 1996-05-17 | 1997-11-19 | Motorola Ltd | Selecting data relevant to multiple communication systems in vicinity of a programmable subscriber unit |
US5763862A (en) | 1996-06-24 | 1998-06-09 | Motorola, Inc. | Dual card smart card reader |
FI103469B1 (en) | 1996-09-17 | 1999-06-30 | Nokia Telecommunications Oy | Prevention of abuse of a copied subscriber code in a mobile telephone system |
US6026075A (en) | 1997-02-25 | 2000-02-15 | International Business Machines Corporation | Flow control mechanism |
US5987325A (en) | 1997-05-19 | 1999-11-16 | Motorola, Inc. | Multiple smart card phone and method |
US6578077B1 (en) | 1997-05-27 | 2003-06-10 | Novell, Inc. | Traffic monitoring tool for bandwidth management |
US6816903B1 (en) | 1997-05-27 | 2004-11-09 | Novell, Inc. | Directory enabled policy management tool for intelligent traffic management |
FI104681B (en) | 1997-06-04 | 2000-04-14 | Sonera Oyj | Method of administering a subscriber identity module in a telecommunication system and telecommunication system |
US6002929A (en) | 1997-09-29 | 1999-12-14 | Mototrola, Inc. | Exchange which extends SIM based authentication and method therefor |
US8965677B2 (en) | 1998-10-22 | 2015-02-24 | Intelligent Technologies International, Inc. | Intra-vehicle information conveyance system and method |
DK0950229T3 (en) | 1997-11-07 | 2001-04-09 | Swisscom Mobile Ag | Method, system and arrangement for determining the authenticity of persons |
WO1999027681A2 (en) | 1997-11-25 | 1999-06-03 | Motorola Inc. | Audio content player methods, systems, and articles of manufacture |
DE59800948D1 (en) | 1997-11-25 | 2001-08-02 | Swisscom Mobile Ag | METHOD AND INFORMATION SYSTEM FOR TRANSMITTING INFORMATION ON IDENTIFICATION CARDS |
US6169387B1 (en) | 1997-12-22 | 2001-01-02 | Lifecor, Inc. | Battery management apparatus for portable electronic devices |
US5929601A (en) * | 1997-12-22 | 1999-07-27 | Lifecor, Inc. | Battery management apparatus for portable electronic devices |
DE19838628A1 (en) | 1998-08-26 | 2000-03-02 | Ibm | Extended smart card communication architecture and method for communication between smart card application and data carrier |
AUPP223998A0 (en) | 1998-03-10 | 1998-04-02 | Lindley, Robyn A. Dr | Mobile intelligent memory unit (mim) |
US6196459B1 (en) | 1998-05-11 | 2001-03-06 | Ubiq Incorporated | Smart card personalization in a multistation environment |
KR100300629B1 (en) | 1998-11-07 | 2001-09-07 | 윤종용 | Code division multiple access system System and method for using SIM card in service area |
US6574734B1 (en) * | 1998-12-28 | 2003-06-03 | International Business Machines Corporation | Method and apparatus for securing access to automotive devices and software services |
US6427072B1 (en) | 1998-12-30 | 2002-07-30 | Ericsson Inc. | Reserve power system for any battery operated device |
JP3822990B2 (en) | 1999-01-07 | 2006-09-20 | 株式会社日立製作所 | Translation device, recording medium |
US6490679B1 (en) | 1999-01-18 | 2002-12-03 | Shym Technology, Inc. | Seamless integration of application programs with security key infrastructure |
US6604140B1 (en) | 1999-03-31 | 2003-08-05 | International Business Machines Corporation | Service framework for computing devices |
US7039221B1 (en) | 1999-04-09 | 2006-05-02 | Tumey David M | Facial image verification utilizing smart-card with integrated video camera |
US6526272B1 (en) | 1999-06-03 | 2003-02-25 | At&T Corp. | Reducing calling costs for wireless phones using multiple mobile identification numbers |
US6362730B2 (en) | 1999-06-14 | 2002-03-26 | Sun Microsystems, Inc. | System and method for collecting vehicle information |
WO2000079368A1 (en) | 1999-06-23 | 2000-12-28 | The Brodia Group | Software smart card |
AU755933B2 (en) | 1999-08-06 | 2003-01-02 | Precise Biometrics Ab | Checking of right to access |
FI109445B (en) | 1999-08-06 | 2002-07-31 | Nokia Corp | A method for transmitting user credentials to a wireless device |
US8140658B1 (en) * | 1999-10-06 | 2012-03-20 | Borgia/Cummins, Llc | Apparatus for internetworked wireless integrated network sensors (WINS) |
US6823457B1 (en) * | 1999-11-22 | 2004-11-23 | International Business Machines Corporation | Method and system for verifying control accesses between a device on a non-proprietary bus and a device on a proprietary bus |
US6615186B1 (en) | 2000-04-24 | 2003-09-02 | Usa Technologies, Inc. | Communicating interactive digital content between vehicles and internet based data processing resources for the purpose of transacting e-commerce or conducting e-business |
JP3704022B2 (en) | 2000-04-25 | 2005-10-05 | 株式会社東芝 | Radio communication system, radio control station, and radio communication method |
JP3077019U (en) | 2000-05-08 | 2001-05-11 | 新暉貿易有限公司 | Intelligent switch for battery |
US6484082B1 (en) | 2000-05-24 | 2002-11-19 | General Motors Corporation | In-vehicle network management using virtual networks |
JP5118793B2 (en) * | 2000-06-29 | 2013-01-16 | ソニー株式会社 | Service provision system |
US6643504B1 (en) | 2000-07-10 | 2003-11-04 | At&T Corp. | Automatic wireless service activation in a private local wireless system |
JP3578058B2 (en) | 2000-07-13 | 2004-10-20 | 株式会社デンソー | Multiplex communication system |
DE10039861C2 (en) | 2000-08-10 | 2002-11-07 | T Mobile Deutschland Gmbh | Process for the simplified exchange of a SIM card for participants in a digital mobile communication network |
US6957199B1 (en) | 2000-08-30 | 2005-10-18 | Douglas Fisher | Method, system and service for conducting authenticated business transactions |
US6813488B2 (en) | 2000-09-07 | 2004-11-02 | Traq Wireless, Inc. | System and method for determining optimal wireless communication service plans based on spectrum licenses |
GB0021988D0 (en) | 2000-09-07 | 2000-10-25 | Nokia Mobile Phones Ltd | Management of portable radiotelephones |
US6757262B1 (en) | 2000-09-15 | 2004-06-29 | Motorola, Inc. | Service framework supporting remote service discovery and connection |
US6925425B2 (en) | 2000-10-14 | 2005-08-02 | Motorola, Inc. | Method and apparatus for vehicle operator performance assessment and improvement |
US6721580B1 (en) | 2000-10-27 | 2004-04-13 | Cisco Technology, Inc. | Ensuring emergency availability of communications devices |
EP1337951A1 (en) | 2000-11-30 | 2003-08-27 | PIRELLI PNEUMATICI Società per Azioni | System and method for monitoring tyres |
US6668179B2 (en) | 2000-12-08 | 2003-12-23 | Intel Corporation | Special battery reserve of portable electronic devices for emergency use |
US20020072388A1 (en) | 2000-12-11 | 2002-06-13 | Korneluk Jose E. | Wireless multimode communication with timed affiliation |
US20020097855A1 (en) | 2001-01-23 | 2002-07-25 | Neudeck Alexander J. | Method for automatic phone service selection |
JP2002229859A (en) | 2001-01-31 | 2002-08-16 | Toshiba Corp | Disk memory and authenticating method applied thereto |
GB0103918D0 (en) | 2001-02-16 | 2001-04-04 | Pathfinder Tech Resources Ltd | Mobile telephone operation |
JP3763349B2 (en) | 2001-04-03 | 2006-04-05 | 日本電気株式会社 | Mobile phone using subscriber card |
US6914517B2 (en) | 2001-04-17 | 2005-07-05 | Dalton Patrick Enterprises, Inc. | Fingerprint sensor with feature authentication |
GB2375261B (en) | 2001-04-30 | 2004-10-13 | Nokia Corp | Radiotelephone system |
US7089586B2 (en) * | 2001-05-02 | 2006-08-08 | Ipr Licensing, Inc. | Firewall protection for wireless users |
WO2002093811A2 (en) | 2001-05-16 | 2002-11-21 | Adjungo Networks Ltd. | Access to plmn networks for non-plmn devices |
US7383561B2 (en) | 2001-06-29 | 2008-06-03 | Nokia Corporation | Conditional access system |
US6694235B2 (en) | 2001-07-06 | 2004-02-17 | Denso Corporation | Vehicular relay device, in-vehicle communication system, failure diagnostic system, vehicle management device, server device and detection and diagnostic program |
WO2003007639A1 (en) | 2001-07-11 | 2003-01-23 | Dormehl, Peter, Gerard (Snr) | System for maintaining data of a mobile station |
US7900242B2 (en) | 2001-07-12 | 2011-03-01 | Nokia Corporation | Modular authentication and authorization scheme for internet protocol |
US7191468B2 (en) | 2001-07-17 | 2007-03-13 | The Boeing Company | System and method for multidimensional data compression |
WO2003017125A1 (en) | 2001-08-07 | 2003-02-27 | Tatara Systems, Inc. | Method and apparatus for integrating billing and authentication functions in local area and wide area wireless data networks |
US20030046228A1 (en) | 2001-08-28 | 2003-03-06 | Jean-Marc Berney | User-wearable functional jewelry with biometrics and smartcard to remotely sign and/or authenticate to e-services |
US20040171386A1 (en) | 2001-09-04 | 2004-09-02 | Enric Mitjana | Method for identifying a station with specific functions in a wireless-based ad-hoc network, and a substation for carrying out the method |
DE10146664A1 (en) | 2001-09-21 | 2003-02-13 | Peter Eimannsberger | Radiotelephone, transfers user-selectable data from memory to removable back-up memory unit or from back-up |
US7792618B2 (en) | 2001-12-21 | 2010-09-07 | Oshkosh Corporation | Control system and method for a concrete vehicle |
JP3885585B2 (en) | 2001-12-28 | 2007-02-21 | 松下電器産業株式会社 | Router device and network system using the same |
KR100711913B1 (en) | 2002-02-04 | 2007-04-27 | 엘지전자 주식회사 | Method for securing data stored in hard discs of a computer system |
EP1337119A1 (en) | 2002-02-19 | 2003-08-20 | Alcatel | Network server for storage of SIM data |
US7844817B2 (en) | 2002-02-28 | 2010-11-30 | Siemens Aktiengesellschaft | Ensuring quality of service in a communications network |
CN1281086C (en) | 2002-03-12 | 2006-10-18 | 斯伦贝谢(北京)智能卡科技有限公司 | User identification module card, method for activating user identification module card in sky and its system |
WO2003077572A1 (en) | 2002-03-13 | 2003-09-18 | Adjungo Networks Ltd. | Accessing cellular networks from non-native local networks |
GB2386803A (en) | 2002-03-20 | 2003-09-24 | Nexus Ltd | Protecting a digital certificate stored on a physical token using biometric authentication |
US6868282B2 (en) | 2002-03-26 | 2005-03-15 | Ericsson, Inc. | Method and apparatus for accessing a network using remote subscriber identity information |
US20080254766A1 (en) | 2007-04-10 | 2008-10-16 | Craven Jeffrey A | Method and system for using an integrated subscriber identity module in a network interface unit |
TW564627B (en) | 2002-04-08 | 2003-12-01 | Quanta Comp Inc | System and method for authentication in public networks |
EP1502221A4 (en) | 2002-04-29 | 2009-08-05 | Contentguard Holdings Inc | Rights management system using legality expression language |
US20030212616A1 (en) | 2002-05-09 | 2003-11-13 | Casabyte, Inc. | Method, apparatus and article to remotely associate wireless communications devices with subscriber identities and/or proxy wireless communications devices |
US7471675B2 (en) | 2002-07-12 | 2008-12-30 | Intel Corporation | Arrangements facilitating ordered transactions |
WO2004010372A1 (en) | 2002-07-24 | 2004-01-29 | Banque-Tec International Pty Ltd | Biometric smartcard system and method of secure transmission |
FI117586B (en) | 2002-08-02 | 2006-11-30 | Nokia Corp | Method for arranging a SIM function in a digital wireless terminal device as well as the corresponding terminal device and server |
US7646737B2 (en) | 2002-08-02 | 2010-01-12 | Qualcomm Incorporated | Multimode wireless device system provision validation and acquisition method and apparatus |
DE60317206T2 (en) | 2002-08-05 | 2008-08-07 | Roamware, Inc., Cupertino | METHOD AND SYSTEM FOR TRANSMITTING TRAFFIC IN A CELLULAR NETWORK |
US6985740B2 (en) | 2002-08-08 | 2006-01-10 | Green Wireless Llc | System for and method of providing priority access service and cell load redistribution |
CA2438051C (en) | 2002-08-22 | 2009-12-15 | Research In Motion Limited | System and method for erasing a data frames queue on a mobile device |
WO2004021296A1 (en) | 2002-09-02 | 2004-03-11 | Kingsley Paul Maunder | Remote storing and retrieval of information from a portable radio communication device |
DE10248679A1 (en) | 2002-10-18 | 2004-04-29 | Robert Bosch Gmbh | Vehicle electrical system with battery status detection at the positive pole of the battery |
JP4134672B2 (en) | 2002-10-18 | 2008-08-20 | 株式会社デンソー | Vehicle control system |
US7548746B2 (en) | 2002-11-01 | 2009-06-16 | At&T Mobility Ii Llc | General purpose automated activation and provisioning technologies |
JP4039622B2 (en) | 2002-11-06 | 2008-01-30 | Kddi株式会社 | Route prediction method for content providing apparatus |
EP1574092A1 (en) | 2002-12-20 | 2005-09-14 | Nokia Corporation | Communication system and method for operating such a system |
US7631033B2 (en) | 2003-01-15 | 2009-12-08 | Xerox Corporation | Hosted method and system for automated proxy creation of device resident services |
AU2003225439A1 (en) | 2003-02-11 | 2004-09-06 | Unisys Corporation | Method and apparatus for updating a control file |
JP2004249817A (en) | 2003-02-19 | 2004-09-09 | Denso Corp | Electronic control device and control system having a plurality of electronic control devices |
US7042925B2 (en) | 2003-02-24 | 2006-05-09 | Thomson Licensing | Correlation detection improvement by averaging spread spectrum signals |
DE10316290B4 (en) | 2003-04-09 | 2005-07-14 | Siemens Ag | Method for the iterative determination of the distance between a receiving station and a transmitting station and calculation unit |
US7178724B2 (en) | 2003-04-21 | 2007-02-20 | Stmicroelectronics, Inc. | Smart card device and method used for transmitting and receiving secure e-mails |
US6862500B2 (en) | 2003-05-12 | 2005-03-01 | Circumnav Networks, Inc. | Methods for communicating between elements in a hierarchical floating car data network |
US7680491B2 (en) | 2003-05-15 | 2010-03-16 | Redknee Inc. | Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) |
CN100584076C (en) | 2003-05-22 | 2010-01-20 | 雅斯拓股份有限公司 | Remote SIM card replacement and activation process |
US7277697B2 (en) | 2003-05-23 | 2007-10-02 | Adesh Desai | Method and system for establishing a teleconference over a telephony network |
WO2004114055A2 (en) | 2003-05-23 | 2004-12-29 | Nnt, Inc. | An enterprise resource planning system with integrated vehicle diagnostic and information system |
US7400627B2 (en) | 2003-06-05 | 2008-07-15 | Brooktree Broadband Holding, Inc. | ATM header compression using hash tables |
US7096316B1 (en) | 2003-06-30 | 2006-08-22 | Veritas Operating Corporation | Multi-host environment with coordinated distributed logging for writes to a raid storage volume |
WO2005004420A2 (en) | 2003-07-02 | 2005-01-13 | Mitsubishi Electric Research Laboratories, Inc. | Method and apparatus for routing data in a personal area network |
EP1652128B1 (en) | 2003-07-07 | 2014-05-14 | Insurance Services Office, Inc. | Traffic information system |
FR2857538B1 (en) | 2003-07-08 | 2006-10-06 | At & T Corp | SYSTEM AND METHOD FOR PACKET HEADER COMPRESSION BASED ON THE DYNAMIC CREATION OF A TEMPLATE |
US20050018883A1 (en) * | 2003-07-09 | 2005-01-27 | Cross Match Technologies, Inc. | Systems and methods for facilitating transactions |
US7729725B2 (en) | 2003-07-10 | 2010-06-01 | Sony Ericsson Mobile Communications Ab | Methods, electronic devices and computer program products for transferring data stored in an electronic device when a subscriber identity module is absent therefrom |
CA2531634A1 (en) | 2003-07-10 | 2005-01-27 | Magnetic Applications Inc. | Compact high power alternator |
US20050039027A1 (en) | 2003-07-25 | 2005-02-17 | Shapiro Michael F. | Universal, biometric, self-authenticating identity computer having multiple communication ports |
TWI257797B (en) | 2003-07-31 | 2006-07-01 | Acer Inc | Automatic identification and log-on system of wireless network |
US7259469B2 (en) | 2003-07-31 | 2007-08-21 | Scs Frigette Inc. | Vehicle auxiliary power unit, assembly, and related methods |
AU2003274700A1 (en) | 2003-09-19 | 2005-04-11 | Innova S.R.L. | Pocket digital wireless device for the personal information management and for the authentication of the communication and the information exchange with other digital devices |
US20060031590A1 (en) | 2003-09-23 | 2006-02-09 | Jean-Yves Monette | Communication circuit for a vehicle |
GB2406925B (en) * | 2003-10-09 | 2007-01-03 | Vodafone Plc | Facilitating and authenticating transactions |
KR100511317B1 (en) | 2003-10-31 | 2005-08-31 | 엘지전자 주식회사 | Fraud protection method and apparatus for contactless card in mobile communication terminal |
US7389178B2 (en) | 2003-12-11 | 2008-06-17 | Greenroad Driving Technologies Ltd. | System and method for vehicle driver behavior analysis and evaluation |
US7412380B1 (en) | 2003-12-17 | 2008-08-12 | Creative Technology Ltd. | Ambience extraction and modification for enhancement and upmix of audio signals |
US7412313B2 (en) * | 2004-01-07 | 2008-08-12 | Temic Automotive Of North America, Inc. | Maintenance assistance for a vehicle |
US7328016B2 (en) | 2004-01-07 | 2008-02-05 | Research In Motion Limited | Apparatus, and associated method, for facilitating network selection at a mobile node utilizing a network selection list maintained thereat |
US6995857B2 (en) * | 2004-01-23 | 2006-02-07 | Vpr Matrix, Inc. | System and method for routing service requests from a paired digital camera and transceiver module |
US7707039B2 (en) | 2004-02-15 | 2010-04-27 | Exbiblio B.V. | Automatic modification of web pages |
EP1710692B1 (en) | 2004-01-28 | 2018-09-12 | Panasonic Intellectual Property Management Co., Ltd. | Secure device, terminal device, gate device, and device |
KR100571837B1 (en) * | 2004-03-05 | 2006-04-17 | 삼성전자주식회사 | Method and apparatus for controlling navigation in automatic navigation vehicle |
US7613185B2 (en) | 2004-03-17 | 2009-11-03 | Verizon Corporate Services Group Inc. | Packet header compression for lossy channels |
US7356337B2 (en) | 2004-03-23 | 2008-04-08 | Starhome Gmbh | Dialing services on a mobile handset and remote provisioning therefor |
JP2007533004A (en) | 2004-04-06 | 2007-11-15 | 本田技研工業株式会社 | Method and system for controlling the exchange of vehicle related messages regarding application information |
US7940932B2 (en) | 2004-04-08 | 2011-05-10 | Texas Instruments Incorporated | Methods, apparatus, and systems for securing SIM (subscriber identity module) personalization and other data on a first processor and secure communication of the SIM data to a second processor |
US20050239504A1 (en) | 2004-04-23 | 2005-10-27 | Sharp Laboratories Of America, Inc. | SIM-based automatic feature activation for mobile phones |
FR2870412B1 (en) | 2004-05-13 | 2006-09-15 | Gemplus Sa | TRANSFER OF DATA BETWEEN TWO CHIP CARDS |
US8615272B2 (en) | 2004-05-26 | 2013-12-24 | Nokia Corporation | Method and system for associating subscriber identity module |
FR2871020B1 (en) | 2004-05-27 | 2006-07-07 | Radiotelephone Sfr | METHOD AND SYSTEM FOR SECURE REPLACEMENT OF SIM CARD INFORMATION TO AT LEAST ONE COMMUNICABLE OBJECT |
US7174174B2 (en) | 2004-08-20 | 2007-02-06 | Dbs Communications, Inc. | Service detail record application and system |
US20060059340A1 (en) | 2004-09-10 | 2006-03-16 | Eldenmalm Jan P | Method and system for dynamic authentication and authorization |
US7676223B2 (en) | 2004-09-13 | 2010-03-09 | Alcatel-Lucent Usa Inc. | Method for controlling a flow of information between secondary agents and a mobile device in a wireless communications system |
US9282455B2 (en) | 2004-10-01 | 2016-03-08 | Intel Corporation | System and method for user certificate initiation, distribution, and provisioning in converged WLAN-WWAN interworking networks |
US7665667B2 (en) | 2004-10-09 | 2010-02-23 | Gemalto Inc. | System and method for updating access control mechanisms |
US20060079237A1 (en) | 2004-10-12 | 2006-04-13 | Mino Holdings, Inc. | Method and system for least call routing for one or more telephone calls |
US8005483B2 (en) | 2004-10-27 | 2011-08-23 | Qwest Communications International Inc. | Mobile caching and data relay vectoring systems and methods |
EP2527859B1 (en) * | 2004-10-29 | 2016-04-20 | Skyhook Wireless, Inc. | Location beacon database and server, method of building location beacon database, and location based service using same |
EP1667407A1 (en) | 2004-12-01 | 2006-06-07 | Siemens Aktiengesellschaft | Network address translation by the home network domain of a moving network |
US20060129311A1 (en) | 2004-12-09 | 2006-06-15 | Jason Bauman | Remote navigation server interface |
US7912504B2 (en) | 2004-12-30 | 2011-03-22 | Telepo Ab | Alternative routing |
US7447502B2 (en) | 2005-01-14 | 2008-11-04 | Research In Motion Limited | Scheme for providing regulatory compliance in performing network selection in a foreign country |
KR100735427B1 (en) | 2005-02-07 | 2007-07-04 | 삼성전자주식회사 | Method for sharing sim card in a mobile communication terminal |
US20060181521A1 (en) | 2005-02-14 | 2006-08-17 | Atrua Technologies, Inc. | Systems for dynamically illuminating touch sensors |
JP4711701B2 (en) | 2005-02-25 | 2011-06-29 | 富士通株式会社 | Biometric authentication device authentication method and biometric authentication device |
CN1703004B (en) | 2005-02-28 | 2010-08-25 | 联想(北京)有限公司 | Method for implementing network access authentication |
WO2006094564A1 (en) | 2005-03-09 | 2006-09-14 | Telecom En Consulting | Method for rerouting mobile phone communications |
JP4718216B2 (en) | 2005-03-24 | 2011-07-06 | 富士通株式会社 | Program, client authentication request method, server authentication request processing method, client, and server |
US7912497B2 (en) | 2005-03-25 | 2011-03-22 | Isidore Eustace P | Single wireless communication device with multiple, concurrent subscriber number capability |
US7636626B2 (en) | 2005-03-28 | 2009-12-22 | General Motors Company | Method and system for monitoring and retrieving device usage |
US7694331B2 (en) | 2005-04-01 | 2010-04-06 | Nokia Corporation | Phone with secure element and critical data |
WO2006113858A2 (en) | 2005-04-19 | 2006-10-26 | Panasonic Avionics Corporation | System and method for presenting high-quality video |
US7957744B2 (en) | 2005-05-13 | 2011-06-07 | General Motors Llc | Method and system for delivering telematics services via a handheld communication device |
EP1727383A1 (en) | 2005-05-27 | 2006-11-29 | BRITISH TELECOMMUNICATIONS public limited company | Mobile communications |
US9525996B2 (en) | 2005-06-21 | 2016-12-20 | Nokia Technologies Oy | System, terminal, network entity, method, and computer program product for system selection in a multi-mode communication system |
EP1737160B1 (en) | 2005-06-21 | 2013-08-14 | Alcatel Lucent | Method for predicting access points along a travel route |
US20070015485A1 (en) * | 2005-07-14 | 2007-01-18 | Scosche Industries, Inc. | Wireless Media Source for Communication with Devices on Data Bus of Vehicle |
JP2007034359A (en) | 2005-07-22 | 2007-02-08 | Hitachi Ltd | Distributed control system |
US20070038346A1 (en) * | 2005-08-11 | 2007-02-15 | Wabash National, L.P. | System and method of wireless communication between a trailer and a tractor |
JP4716815B2 (en) | 2005-08-11 | 2011-07-06 | アルパイン株式会社 | Inter-vehicle communication device, inter-vehicle communication system, and moving image information application applicability determination method |
DE602005002748T2 (en) | 2005-08-26 | 2008-07-17 | Research In Motion Ltd., Waterloo | Method and device for maintaining suitable authentication data and providing up-to-date authentication data for a wireless communication terminal |
ES2339677T3 (en) | 2005-09-01 | 2010-05-24 | France Telecom | CUSTOMIZATION OF MOBILE STATIONS. |
US7590481B2 (en) | 2005-09-19 | 2009-09-15 | Ford Global Technologies, Llc | Integrated vehicle control system using dynamically determined vehicle conditions |
CN100558176C (en) | 2005-09-30 | 2009-11-04 | 华为技术有限公司 | Communication terminal device and communication control method |
JP4593626B2 (en) | 2005-10-12 | 2010-12-08 | 株式会社オートネットワーク技術研究所 | In-vehicle database system |
AU2006306522B9 (en) | 2005-10-21 | 2011-12-08 | Deere & Company | Networked multi-role robotic vehicle |
EP1938520B1 (en) | 2005-10-21 | 2010-08-04 | Research In Motion Limited | Instant messaging device/server protocol |
US20070105531A1 (en) | 2005-11-04 | 2007-05-10 | Ascenna Mobile, Inc. | Dynamic Processing of Virtual Identities for Mobile Communications Devices |
US9002342B2 (en) | 2005-12-02 | 2015-04-07 | Nokia Corporation | System, apparatus, and method for dynamically customizing and configuring applications |
US7738891B2 (en) | 2005-12-02 | 2010-06-15 | Nokia Corporation | System, apparatus, and method for dynamically configuring application access point settings |
US8296373B2 (en) | 2007-02-02 | 2012-10-23 | Facebook, Inc. | Automatically managing objectionable behavior in a web-based social network |
US20070149170A1 (en) | 2005-12-23 | 2007-06-28 | Sony Ericsson Mobile Communications Ab | Sim authentication for access to a computer/media network |
US10373400B2 (en) | 2005-12-31 | 2019-08-06 | General Motors Llc | Vehicle email notification system and method |
US20070202895A1 (en) | 2006-02-27 | 2007-08-30 | Benco David S | SMS notification of called party availability |
JP4728839B2 (en) | 2006-03-02 | 2011-07-20 | 株式会社デンソーアイティーラボラトリ | In-vehicle device controller |
US20070266428A1 (en) * | 2006-03-06 | 2007-11-15 | James Downes | Method, System, And Apparatus For Nested Security Access/Authentication |
GB0605283D0 (en) | 2006-03-16 | 2006-04-26 | Ghost Telecom Ltd | Method and architecture(s) for a virtual wireless network(s) and its interfacing and interconnecting with wireless network(s) and public access |
US7940408B2 (en) | 2006-03-21 | 2011-05-10 | Ricoh Company, Ltd. | Bi-directional status and control between image capture device and backend device |
JP2007253792A (en) | 2006-03-23 | 2007-10-04 | Denso Corp | Software system of vehicular electronic control device, and its design method |
US7653055B2 (en) | 2006-03-31 | 2010-01-26 | Alcatel-Lucent Usa Inc. | Method and apparatus for improved multicast streaming in wireless networks |
JP2007282208A (en) | 2006-04-05 | 2007-10-25 | Samsung Electronics Co Ltd | Mobile terminal service limiting device and method |
US7606643B2 (en) | 2006-04-20 | 2009-10-20 | Delphi Technologies, Inc. | Technique for providing management of a motor vehicle information system |
US8060285B2 (en) | 2006-04-26 | 2011-11-15 | Toyota Motor Engineering & Manufacturing North America, Inc. | System and method of intelligent agent management using an overseer agent for use in vehicle diagnostics |
US20070254713A1 (en) | 2006-04-28 | 2007-11-01 | Isaac Lagnado | System and method for managing operation of a system based at least in part on a component of the system being physically accessible |
JP2007317170A (en) | 2006-04-28 | 2007-12-06 | Renesas Technology Corp | Ic module and cellular phone |
US20080028230A1 (en) | 2006-05-05 | 2008-01-31 | Tri-D Systems, Inc. | Biometric authentication proximity card |
US20080020755A1 (en) | 2006-05-16 | 2008-01-24 | Mino Holdings, Inc. | Method and system for international roaming using virtual sim card |
US7689231B2 (en) | 2006-05-17 | 2010-03-30 | Sandisk Il Ltd. | Territorial enforcement of device functionality |
GB2438452B (en) | 2006-05-24 | 2010-12-15 | Nokia Corp | Portable telecommunications apparatus |
US20080020773A1 (en) | 2006-07-21 | 2008-01-24 | Motorola, Inc. | Wireless communication device and method for managing the call routing for multiple services each respectively associated with a corresponding one of multiple sets of stored subscriber identity information |
FR2904747B1 (en) | 2006-08-01 | 2009-02-13 | Wavecom Sa | METHOD AND DEVICE FOR CUSTOMIZING A RADIO COMMUNICATION TERMINAL, RADIO COMMUNICATION TERMINAL, SIM CARD, SERVER, COMPUTER PROGRAM PRODUCT AND CORRESPONDING STORAGE MEDIUM |
US8194682B2 (en) * | 2006-08-07 | 2012-06-05 | Pine Valley Investments, Inc. | Multiple protocol land mobile radio system |
WO2008022291A2 (en) | 2006-08-16 | 2008-02-21 | Snapin Software Inc. | Local triggering methods, such as applications for device-initiated diagnostic or configuration management |
US20080043759A1 (en) | 2006-08-17 | 2008-02-21 | Northrop Grumman Systems Corporation | System, Apparatus, Method and Computer Program Product for an Intercom System |
KR101234194B1 (en) | 2006-08-28 | 2013-02-18 | 삼성전자주식회사 | Apparatus and method for downloading of sim data in mobile communication system |
US8135443B2 (en) | 2006-08-31 | 2012-03-13 | Qualcomm Incorporated | Portable device with priority based power savings control and method thereof |
US8744436B2 (en) | 2006-09-01 | 2014-06-03 | At&T Mobility Ii Llc | Roaming selection services |
KR100793093B1 (en) | 2006-09-08 | 2008-01-10 | 엘지전자 주식회사 | Method of service setting for mobile communication terminal using a multi sim card |
US7787602B2 (en) | 2006-09-11 | 2010-08-31 | At&T Intellectual Property I, Lp | Methods and apparatus to provide a telephone system configuration interface |
US8548734B2 (en) | 2006-09-14 | 2013-10-01 | University Of South Florida | System and method for real-time travel path prediction and automatic incident alerts |
US8006283B2 (en) | 2006-09-20 | 2011-08-23 | Sabse Technologies, Inc. | Method and system for triggering internet applications using messages |
WO2008047555A1 (en) | 2006-09-27 | 2008-04-24 | Fujitsu Ten Limited | Simulation device, simulation model, and simulation model forming device |
GB0619711D0 (en) | 2006-10-05 | 2006-11-15 | Christie Tyrone M | Virtual subscriber identities for mobile communications networks |
US20080087720A1 (en) | 2006-10-11 | 2008-04-17 | Yevgeny Boris Levitov | Biometric Access Control System for Vending Machines |
US8719431B2 (en) | 2006-10-26 | 2014-05-06 | Blackberry Limited | Transient WLAN connection profiles |
US8838975B2 (en) | 2006-10-31 | 2014-09-16 | Blackberry Limited | System and method for protecting a password against brute force attacks |
US8004394B2 (en) | 2006-11-07 | 2011-08-23 | Rosco Inc. | Camera system for large vehicles |
US8335493B2 (en) | 2006-11-10 | 2012-12-18 | Sony Ericsson Mobile Communications Ab | System and method for service selection in a portable device |
WO2008065667A2 (en) | 2006-11-30 | 2008-06-05 | Pinhas Patarkazishvili | Bridging between a mobile cellular telephone network and a data, voice over internet protocol (voip) network |
US8628019B2 (en) | 2007-01-03 | 2014-01-14 | Actividentity, Inc. | Configurable digital badge holder |
JP2008181295A (en) | 2007-01-24 | 2008-08-07 | Sony Corp | Authentication system, information processor and method, program and recording medium |
US20080205416A1 (en) | 2007-02-23 | 2008-08-28 | Honeywell International, Inc. | Flight control computers with ethernet based cross channel data links |
WO2008104039A2 (en) | 2007-02-28 | 2008-09-04 | Nolink | Method of transferring data being stored in a database |
US8061140B2 (en) | 2007-03-07 | 2011-11-22 | Thermal Power Recovery Llc | High efficiency multicycle internal combustion engine with waste heat recovery |
US8100816B2 (en) | 2007-03-14 | 2012-01-24 | Leed By Example | Training device for an ambulatory user |
US20080226074A1 (en) | 2007-03-15 | 2008-09-18 | Interdigital Technology Corporation | Method and apparatus for ciphering packet units in wireless communications |
US8244468B2 (en) | 2007-11-06 | 2012-08-14 | Location Based Technology Inc. | System and method for creating and managing a personalized web interface for monitoring location information on individuals and objects using tracking devices |
US7808375B2 (en) | 2007-04-16 | 2010-10-05 | Midtronics, Inc. | Battery run down indicator |
US8712474B2 (en) | 2007-04-20 | 2014-04-29 | Telefonaktiebolaget L M Ericsson (Publ) | Secure soft SIM credential transfer |
US20080265024A1 (en) | 2007-04-30 | 2008-10-30 | Tracy Mark S | Electronic device with functional module |
US8331399B2 (en) | 2007-05-07 | 2012-12-11 | Qualcomm Incorporated | Re-using sequence number by multiple protocols for wireless communication |
US20080287144A1 (en) * | 2007-05-18 | 2008-11-20 | Ashok Sabata | Vehicles as Nodes of Wireless Sensor Networks for Information Collection & Prognostication |
JP2008312024A (en) | 2007-06-15 | 2008-12-25 | Auto Network Gijutsu Kenkyusho:Kk | Transit connection unit |
US20080311912A1 (en) | 2007-06-15 | 2008-12-18 | Qualcomm Incorporated | System selection based on application requirements and preferences |
US20090007250A1 (en) | 2007-06-27 | 2009-01-01 | Microsoft Corporation | Client authentication distributor |
US8195233B2 (en) | 2007-07-30 | 2012-06-05 | Motorola Mobility, Inc. | Methods and systems for identity management in wireless devices |
US8244223B2 (en) | 2007-08-02 | 2012-08-14 | At&T Intellectual Property I, Lp | Automated transfer of wireless provisioning parameters between existing and new devices |
JP5007904B2 (en) | 2007-08-22 | 2012-08-22 | 国立大学法人名古屋大学 | Communication system and communication method |
US8107953B2 (en) | 2007-08-31 | 2012-01-31 | Tracfone Wireless, Inc. | System and method for activating services on a wireless device |
US7917251B2 (en) | 2007-09-05 | 2011-03-29 | Consolidated Edison Company Of New York, Inc. | Metering system and method of operation |
US7693609B2 (en) | 2007-09-05 | 2010-04-06 | Consolidated Edison Company Of New York, Inc. | Hybrid vehicle recharging system and method of operation |
DE102007044905A1 (en) | 2007-09-19 | 2009-04-09 | InterDigital Patent Holdings, Inc., Wilmington | Method and device for enabling service usage and determination of subscriber identity in communication networks by means of software-based access authorization cards (vSIM) |
JP4922120B2 (en) | 2007-10-05 | 2012-04-25 | 株式会社オートネットワーク技術研究所 | Communication system and relay device |
WO2009050766A1 (en) | 2007-10-18 | 2009-04-23 | Fujitsu Limited | Video compression encoding/decompression device, video compression encoding/decompression program, and video generating/output device |
US20090135843A1 (en) | 2007-11-25 | 2009-05-28 | Michel Veillette | System and method for operating mesh devices in multi-tree overlapping mesh networks |
US7755472B2 (en) | 2007-12-10 | 2010-07-13 | Grossman Victor A | System and method for setting functions according to location |
US8059651B2 (en) | 2007-12-17 | 2011-11-15 | Motorola Solutions, Inc. | Method for recovering lost header |
US20090152943A1 (en) * | 2007-12-17 | 2009-06-18 | Wael William Diab | Method and system for vehicular power distribution utilizing power over ethernet |
US9185601B2 (en) * | 2007-12-18 | 2015-11-10 | At&T Mobility Ii Llc | Optimal utilization of multiple transceivers in a wireless environment |
CN101960497B (en) * | 2007-12-26 | 2015-09-30 | 约翰逊控制技术公司 | The system and method for commercial affairs in management vehicle |
US8140064B2 (en) | 2008-01-27 | 2012-03-20 | Sandisk Il Ltd. | Methods and apparatus to use an identity module in telecommunication services |
US20090215449A1 (en) | 2008-02-26 | 2009-08-27 | Netanel Avner | System and Method for Virtual Roaming of Mobile Communication Devices |
US8090949B2 (en) * | 2008-03-13 | 2012-01-03 | GM Global Technology Operations LLC | Certificate assignment strategies for efficient operation of the PKI-based security architecture in a vehicular network |
JP4535297B2 (en) | 2008-03-28 | 2010-09-01 | 三菱自動車工業株式会社 | Vehicle power generation control device |
CA2757647A1 (en) | 2008-04-04 | 2009-12-03 | Powerwave Cognition, Inc. | Methods and systems for a mobile, broadband, routable internet |
KR101020948B1 (en) | 2008-04-22 | 2011-03-09 | 현대자동차주식회사 | Network gateway and network system for a vehicle |
US8412107B2 (en) | 2008-04-30 | 2013-04-02 | Mitsubishi Electric Corporation | On-board communication device and cooperative road-to-vehicle/car-to-car communication system |
EP2283674B1 (en) | 2008-04-30 | 2015-09-16 | Alexander Poltorak | Multi-tier and secure service wireless communications networks |
JP5131589B2 (en) | 2008-06-23 | 2013-01-30 | アイシン・エィ・ダブリュ株式会社 | Car navigation system |
EP2151808A1 (en) * | 2008-08-07 | 2010-02-10 | Aisin Aw Co., Ltd. | Safe driving evaluation system and safe driving evaluation method |
CN102216731B (en) * | 2008-08-11 | 2014-10-01 | Tti发明D有限公司 | System and method for using networked mobile devices in vehicles |
US8964781B2 (en) | 2008-11-05 | 2015-02-24 | Qualcomm Incorporated | Relays in a multihop heterogeneous UMTS wireless communication system |
US9088931B2 (en) | 2008-12-30 | 2015-07-21 | United States Cellular Corporation | System selection based on service-specific preferred roaming list in a wireless network |
KR101711171B1 (en) | 2009-01-09 | 2017-02-28 | 인터디지탈 패튼 홀딩스, 인크 | A wtru and a method for use in the wtru |
US8503484B2 (en) | 2009-01-19 | 2013-08-06 | Honeywell International Inc. | System and method for a cross channel data link |
US8054038B2 (en) | 2009-01-29 | 2011-11-08 | Tesla Motors, Inc. | System for optimizing battery pack cut-off voltage |
US20100202346A1 (en) | 2009-02-12 | 2010-08-12 | Sitzes Ryan Z | Wireless communication system and method |
US9231680B2 (en) | 2009-03-03 | 2016-01-05 | Rfaxis, Inc. | Multi-channel radio frequency front end circuit |
US20100234071A1 (en) | 2009-03-12 | 2010-09-16 | Comsys Communication & Signal Processing Ltd. | Vehicle integrated communications system |
US8538404B2 (en) | 2009-03-12 | 2013-09-17 | International Business Machines Corporation | Centrally managing user-specified configuration data for a configurable device |
US8295257B2 (en) | 2009-03-13 | 2012-10-23 | Telcordia Technologies, Inc. | Scalable disruptive-resistant communication method |
US9369938B2 (en) | 2009-03-31 | 2016-06-14 | Microsoft Technology Licensing, Llc | Subscriber identity module (SIM) for mobile stations |
US8428514B2 (en) * | 2009-05-15 | 2013-04-23 | Telcordia Applied Research Center Taiwan, Co. | Asymmetric and asynchronous energy conservation protocol for vehicular networks |
US8552668B2 (en) | 2009-05-20 | 2013-10-08 | Robert Bosch Gmbh | Architecture for automotive electrical body systems |
US8606232B2 (en) | 2009-06-08 | 2013-12-10 | Qualcomm Incorporated | Method and system for performing multi-stage virtual SIM provisioning and setup on mobile devices |
US8634828B2 (en) | 2009-06-08 | 2014-01-21 | Qualcomm Incorporated | Method and apparatus for switching virtual SIM service contracts based upon a user profile |
US8639245B2 (en) | 2009-06-08 | 2014-01-28 | Qualcomm Incorporated | Method and apparatus for updating rules governing the switching of virtual SIM service contracts |
US8649789B2 (en) | 2009-06-08 | 2014-02-11 | Qualcomm Incorporated | Method and apparatus for switching virtual SIM service contracts when roaming |
US8244909B1 (en) | 2009-06-18 | 2012-08-14 | Google Inc. | Method, apparatus and networking equipment for performing flow hashing using quasi cryptographic hash functions |
US20120109418A1 (en) | 2009-07-07 | 2012-05-03 | Tracktec Ltd. | Driver profiling |
US8140709B2 (en) | 2009-08-07 | 2012-03-20 | Alcatel Lucent | Two stage internet protocol header compression |
US8233389B2 (en) | 2009-08-19 | 2012-07-31 | Mitsubishi Electric Research Laboratories, Inc. | Method and protocol for congestion control in a vehicular network |
GB2474007A (en) * | 2009-08-27 | 2011-04-06 | Simon R Daniel | Communication in and monitoring of a disaster area, optionally including a disaster medical pack |
US20110055292A1 (en) | 2009-09-03 | 2011-03-03 | Dinu Petre Madau | System and method for standardizing vehicle network data across vehicle product lines |
US8725139B2 (en) | 2009-09-08 | 2014-05-13 | Movirtu Limited | Method and system to enable multiple virtual numbers across different mobile networks |
GB2476449B (en) * | 2009-09-18 | 2013-12-11 | Optasense Holdings Ltd | Wide area seismic detection |
US8294420B2 (en) | 2009-09-29 | 2012-10-23 | Schneider Electric USA, Inc. | Kiosk vehicle charging and selecting systems |
US20110106375A1 (en) | 2009-11-03 | 2011-05-05 | Vishnu Gurusamy Sundaram | Method and system for providing an integrated platform for entertainment, information, communication, control and computing applications in vehicles |
KR101325807B1 (en) | 2009-12-17 | 2013-11-05 | 한국전자통신연구원 | APPARATUS AND METHOD FOR COMMUNICATION OF VEHICLE USING IPv6 NETWORK |
KR20110071995A (en) | 2009-12-22 | 2011-06-29 | 한국전자통신연구원 | Ethernet-most gateway apparatus |
US8541903B2 (en) * | 2010-02-03 | 2013-09-24 | Panasonic Automotive Systems Company Of America, Division Of Panasonic Corporation Of North America | Power line communication system and method |
US20120004933A1 (en) | 2010-02-09 | 2012-01-05 | At&T Mobility Ii Llc | System And Method For The Collection And Monitoring Of Vehicle Data |
US9377528B2 (en) | 2010-03-19 | 2016-06-28 | Northeastern University | Roaming mobile sensor platform for collecting geo-referenced data and creating thematic maps |
US8602141B2 (en) * | 2010-04-05 | 2013-12-10 | Daimler Trucks North America Llc | Vehicle power system with fuel cell auxiliary power unit (APU) |
US8582631B2 (en) | 2010-04-26 | 2013-11-12 | Sierra Wireless, Inc. | Managing communication operations of wireless devices |
US8364959B2 (en) * | 2010-05-26 | 2013-01-29 | Google Inc. | Systems and methods for using a domain-specific security sandbox to facilitate secure transactions |
US8593253B2 (en) * | 2010-06-09 | 2013-11-26 | Gm Global Technology Operations, Inc. | Systems and methods for efficient authentication |
US8964549B2 (en) | 2010-06-22 | 2015-02-24 | Sierra Wireless, Inc. | Method and apparatus for managing wireless communication based on network traffic level |
US9350174B2 (en) | 2010-06-26 | 2016-05-24 | Lg Electronics Inc. | Network system |
US8063797B1 (en) | 2010-07-31 | 2011-11-22 | ParkMe LLC | Parking information collection system and method |
US8527143B2 (en) * | 2010-10-29 | 2013-09-03 | Nissan North America, Inc. | Vehicle user interface system and method having location specific feature availability |
US20120105637A1 (en) | 2010-11-03 | 2012-05-03 | Broadcom Corporation | Multi-Level Video Processing Within A Vehicular Communication Network |
US8378623B2 (en) | 2010-11-05 | 2013-02-19 | General Electric Company | Apparatus and method for charging an electric vehicle |
US9167618B2 (en) | 2010-11-16 | 2015-10-20 | At&T Mobility Ii Llc | Data bundling and fast dormancy based upon intelligent application learning |
US20120173051A1 (en) * | 2011-01-05 | 2012-07-05 | Tarnutzer Stephan A | OEM safe aftermarket gateway |
US20120182935A1 (en) | 2011-01-14 | 2012-07-19 | Cisco Technology, Inc. | System and method for packet distribution in a vehicular network environment |
JP5472276B2 (en) | 2011-12-14 | 2014-04-16 | 株式会社デンソー | Vehicle communication control device |
US8674856B2 (en) * | 2012-08-16 | 2014-03-18 | International Business Machines Corporation | Data compression utilizing longest common subsequence template |
-
2011
- 2011-01-26 US US13/014,605 patent/US8863256B1/en active Active - Reinstated
- 2011-03-24 US US13/071,367 patent/US8848608B1/en active Active - Reinstated
- 2011-04-08 US US13/083,305 patent/US8989954B1/en active Active
- 2011-05-10 US US13/104,737 patent/US8705527B1/en active Active
- 2011-05-16 US US13/108,631 patent/US8718797B1/en active Active
- 2011-05-19 US US13/111,425 patent/US9083581B1/en active Active
- 2011-05-24 US US13/114,659 patent/US9154900B1/en not_active Expired - Fee Related
- 2011-05-27 US US13/118,220 patent/US9036509B1/en active Active
- 2011-05-27 US US13/118,024 patent/US8514825B1/en active Active
- 2011-05-27 US US13/117,860 patent/US8903593B1/en not_active Expired - Fee Related
-
2013
- 2013-07-16 US US13/943,114 patent/US9225782B2/en active Active
-
2014
- 2014-04-01 US US14/242,122 patent/US9277370B2/en active Active
- 2014-04-02 US US14/243,304 patent/US9860709B2/en active Active
- 2014-09-12 US US14/485,050 patent/US10117066B2/en active Active
- 2014-09-12 US US14/484,664 patent/US20140380442A1/en not_active Abandoned
-
2015
- 2015-02-11 US US14/619,247 patent/US9888363B2/en active Active
- 2015-03-20 US US14/664,101 patent/US9654937B2/en active Active
-
2017
- 2017-05-12 US US15/594,379 patent/US10602329B2/en not_active Expired - Fee Related
-
2018
- 2018-09-11 US US16/128,027 patent/US10979875B2/en active Active
Patent Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6542071B1 (en) * | 1999-11-09 | 2003-04-01 | Mazda Motor Corporation | Opening-closing member control apparatus for vehicle |
US20050038581A1 (en) * | 2000-08-18 | 2005-02-17 | Nnt, Inc. | Remote Monitoring, Configuring, Programming and Diagnostic System and Method for Vehicles and Vehicle Components |
US20050060070A1 (en) * | 2000-08-18 | 2005-03-17 | Nnt, Inc. | Wireless communication framework |
US6505780B1 (en) * | 2001-12-05 | 2003-01-14 | Koninklijke Philips Electronics N.V. | Personalize vehicle settings using RF tags |
US20050096836A1 (en) * | 2002-05-16 | 2005-05-05 | Katsuaki Minami | Vehicle operation information management evaluation system |
US20040249915A1 (en) * | 2002-05-21 | 2004-12-09 | Russell Jesse E. | Advanced multi-network client device for wideband multimedia access to private and public wireless networks |
US20110307143A1 (en) * | 2003-12-15 | 2011-12-15 | Honda Motor Co., Ltd. | Method And System For Facilitating The Exchange Of Information Between A Vehicle And A Remote Location |
US8352730B2 (en) * | 2004-12-20 | 2013-01-08 | Proxense, Llc | Biometric personal data key (PDK) authentication |
US20060282554A1 (en) * | 2005-04-14 | 2006-12-14 | Nokia Corporation | Method, apparatus and computer program providing network-associated system priority list for multimode system selection |
US7849020B2 (en) * | 2005-04-19 | 2010-12-07 | Microsoft Corporation | Method and apparatus for network transactions |
US20070030119A1 (en) * | 2005-07-08 | 2007-02-08 | Mitsubishi Denki Kabushiki Kaisha | Communication apparatus for vehicle |
US20070030136A1 (en) * | 2005-08-03 | 2007-02-08 | Denso Corporation | On-board illumination controlling system and method |
US20070186106A1 (en) * | 2006-01-26 | 2007-08-09 | Ting David M | Systems and methods for multi-factor authentication |
US20070255797A1 (en) * | 2006-04-28 | 2007-11-01 | Dunn Douglas L | Method for selecting an air interface using an access list on a multi-mode wireless device |
US20100049626A1 (en) * | 2007-03-09 | 2010-02-25 | Airbiquity Inc. | In-vehicle mobile music purchase |
US20080238135A1 (en) * | 2007-03-29 | 2008-10-02 | Aisin Seiki Kabushiki Kaisha | Control apparatus of opening and closing body for vehicle |
US20090163175A1 (en) * | 2007-12-24 | 2009-06-25 | Guangming Shi | Virtual sim card for mobile handsets |
US20090284359A1 (en) * | 2008-05-19 | 2009-11-19 | Gm Global Technology Operations, Inc. | Vehicle-setting-based driver identification system |
US20100087987A1 (en) * | 2008-10-08 | 2010-04-08 | Gm Global Technoloogy Operations, Inc. | Apparatus and Method for Vehicle Driver Recognition and Customization Using Onboard Vehicle System Settings |
US20100167702A1 (en) * | 2008-12-29 | 2010-07-01 | General Motors Corporation | Voice fallback strategy for vehicle originated cellular communication to a call center |
US20100167721A1 (en) * | 2008-12-29 | 2010-07-01 | General Motors Corporation | Vehicle originated cellular communication to a call center |
US20100210304A1 (en) * | 2009-02-13 | 2010-08-19 | At&T Intellectual Property I, L.P. | Systems and Methods for Multi-Device Wireless SIM Management |
US8762288B2 (en) * | 2009-04-22 | 2014-06-24 | The Western Union Company | Methods and systems for establishing an identity confidence database |
US20120226413A1 (en) * | 2009-04-29 | 2012-09-06 | Gm Global Technology Operations Llc. | Hierarchical recognition of vehicle driver and select activation of vehicle settings based on the recognition |
US20110246317A1 (en) * | 2009-10-23 | 2011-10-06 | Apriva, Llc | System and device for facilitating a transaction through use of a proxy account code |
US20110144980A1 (en) * | 2009-12-11 | 2011-06-16 | General Motors Llc | System and method for updating information in electronic calendars |
US20110306318A1 (en) * | 2010-06-14 | 2011-12-15 | Clive Edward Rodgers | Apparatus and methods for provisioning subscriber identity data in a wireless network |
US8514825B1 (en) * | 2011-01-14 | 2013-08-20 | Cisco Technology, Inc. | System and method for enabling a vehicular access network in a vehicular environment |
US8848608B1 (en) * | 2011-01-14 | 2014-09-30 | Cisco Technology, Inc. | System and method for wireless interface selection and for communication and access control of subsystems, devices, and data in a vehicular environment |
US9225782B2 (en) * | 2011-01-14 | 2015-12-29 | Cisco Technology, Inc. | System and method for enabling a vehicular access network in a vehicular environment |
Cited By (68)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9654937B2 (en) | 2011-01-14 | 2017-05-16 | Cisco Technology, Inc. | System and method for routing, mobility, application services, discovery, and sensing in a vehicular network environment |
US9888363B2 (en) | 2011-01-14 | 2018-02-06 | Cisco Technology, Inc. | System and method for applications management in a networked vehicular environment |
US9860709B2 (en) | 2011-01-14 | 2018-01-02 | Cisco Technology, Inc. | System and method for real-time synthesis and performance enhancement of audio/video data, noise cancellation, and gesture based user interfaces in a vehicular environment |
US10782735B2 (en) | 2012-12-05 | 2020-09-22 | Mobile Tech, Inc. | Docking station for tablet device |
US10198035B2 (en) | 2012-12-05 | 2019-02-05 | Mobile Tech, Inc. | Docking station for tablet device |
US10198036B2 (en) | 2012-12-05 | 2019-02-05 | Mobile Tech, Inc. | Docking station for tablet device |
US11472293B2 (en) | 2015-03-02 | 2022-10-18 | Ford Global Technologies, Llc | In-vehicle component user interface |
US9747740B2 (en) | 2015-03-02 | 2017-08-29 | Ford Global Technologies, Llc | Simultaneous button press secure keypad code entry |
US9781094B2 (en) * | 2015-04-28 | 2017-10-03 | Qualcomm Incorporated | Systems and methods for performing remote authentication of a virtual subscriber identity module (SIM) |
US20160323256A1 (en) * | 2015-04-28 | 2016-11-03 | Qualcomm Incorporated | Systems and Methods for Performing Remote Authentication of a Virtual Subscriber Identity Module (SIM) |
CN106327172A (en) * | 2015-06-17 | 2017-01-11 | 西安中兴新软件有限责任公司 | Payment method and device for virtual SIM card terminal |
US9914418B2 (en) | 2015-09-01 | 2018-03-13 | Ford Global Technologies, Llc | In-vehicle control location |
US9967717B2 (en) | 2015-09-01 | 2018-05-08 | Ford Global Technologies, Llc | Efficient tracking of personal device locations |
US9622159B2 (en) * | 2015-09-01 | 2017-04-11 | Ford Global Technologies, Llc | Plug-and-play interactive vehicle interior component architecture |
CN107018090A (en) * | 2015-09-08 | 2017-08-04 | 现代自动车株式会社 | The operating method of communication node in network |
US9860710B2 (en) | 2015-09-08 | 2018-01-02 | Ford Global Technologies, Llc | Symmetrical reference personal device location tracking |
US9744852B2 (en) | 2015-09-10 | 2017-08-29 | Ford Global Technologies, Llc | Integration of add-on interior modules into driver user interface |
US20170134298A1 (en) * | 2015-11-05 | 2017-05-11 | Qualcomm Incorporated | System and Methods for Improving Support of a Virtual Subscriber Identity Module (SIM) in a Multi-SIM Wireless Communication Device |
US9712452B2 (en) * | 2015-11-05 | 2017-07-18 | Qualcomm Incorporated | System and methods for improving support of a virtual subscriber identity module (SIM) in a multi-SIM wireless communication device |
US10728868B2 (en) | 2015-12-03 | 2020-07-28 | Mobile Tech, Inc. | Remote monitoring and control over wireless nodes in a wirelessly connected environment |
US10674466B2 (en) | 2015-12-03 | 2020-06-02 | Mobile Tech, Inc. | Location tracking of products and product display assemblies in a wirelessly connected environment |
US11109335B2 (en) | 2015-12-03 | 2021-08-31 | Mobile Tech, Inc. | Wirelessly connected hybrid environment of different types of wireless nodes |
US10524220B2 (en) | 2015-12-03 | 2019-12-31 | Mobile Tech, Inc. | Location tracking of products and product display assemblies in a wirelessly connected environment |
US10517056B2 (en) * | 2015-12-03 | 2019-12-24 | Mobile Tech, Inc. | Electronically connected environment |
US10667227B2 (en) | 2015-12-03 | 2020-05-26 | Mobile Tech, Inc. | Electronically connected environment |
US20170164314A1 (en) * | 2015-12-03 | 2017-06-08 | Mobile Technologies, Inc. | Electronically connected environment |
US10251144B2 (en) | 2015-12-03 | 2019-04-02 | Mobile Tech, Inc. | Location tracking of products and product display assemblies in a wirelessly connected environment |
US10046637B2 (en) | 2015-12-11 | 2018-08-14 | Ford Global Technologies, Llc | In-vehicle component control user interface |
CN105608530A (en) * | 2015-12-18 | 2016-05-25 | 北京四方继保自动化股份有限公司 | Operation, distribution and dispatching data integrity verification method for power distribution network |
US20170180440A1 (en) * | 2015-12-22 | 2017-06-22 | Caterpillar Inc. | Information management system and method of delivering data associated with machine |
US10082877B2 (en) | 2016-03-15 | 2018-09-25 | Ford Global Technologies, Llc | Orientation-independent air gesture detection service for in-vehicle environments |
US10499239B2 (en) * | 2016-03-18 | 2019-12-03 | Ford Global Technologies, Llc | Method and apparatus for cellular subscription tethering |
US20170272935A1 (en) * | 2016-03-18 | 2017-09-21 | Ford Global Technologies, Llc | Method and apparatus for cellular subscription tethering |
US9914415B2 (en) | 2016-04-25 | 2018-03-13 | Ford Global Technologies, Llc | Connectionless communication with interior vehicle components |
US20180014269A1 (en) * | 2016-07-06 | 2018-01-11 | Gogo Llc | Hyper-number portability |
US10028244B2 (en) * | 2016-07-06 | 2018-07-17 | Gogo Llc | Hyper-number portability |
US10679276B2 (en) | 2016-07-07 | 2020-06-09 | Nio Usa, Inc. | Methods and systems for communicating estimated time of arrival to a third party |
US11005657B2 (en) | 2016-07-07 | 2021-05-11 | Nio Usa, Inc. | System and method for automatically triggering the communication of sensitive information through a vehicle to a third party |
US20180012273A1 (en) * | 2016-07-07 | 2018-01-11 | NextEv USA, Inc. | Methods and systems for controlling communications by a driver in a vehicle |
US10672060B2 (en) | 2016-07-07 | 2020-06-02 | Nio Usa, Inc. | Methods and systems for automatically sending rule-based communications from a vehicle |
US10685503B2 (en) | 2016-07-07 | 2020-06-16 | Nio Usa, Inc. | System and method for associating user and vehicle information for communication to a third party |
US10754381B2 (en) | 2016-07-29 | 2020-08-25 | Mobile Tech, Inc. | Docking system for portable computing device |
US10650621B1 (en) | 2016-09-13 | 2020-05-12 | Iocurrents, Inc. | Interfacing with a vehicular controller area network |
US11232655B2 (en) | 2016-09-13 | 2022-01-25 | Iocurrents, Inc. | System and method for interfacing with a vehicular controller area network |
US10346152B2 (en) * | 2016-09-20 | 2019-07-09 | At&T Intellectual Property I, L.P. | Facilitating use of a universal integrated circuit card (UICC) for secure device updates |
US11216267B2 (en) * | 2016-09-20 | 2022-01-04 | At&T Iniellectual Property I, L.P. | Facilitating use of a universal integrated circuit card (UICC) for secure device updates |
US20180081669A1 (en) * | 2016-09-20 | 2018-03-22 | At&T Mobility Ii Llc | Facilitating use of a universal integrated circuit card (uicc) for secure device updates |
US20180109623A1 (en) * | 2016-10-17 | 2018-04-19 | Robert Bosch Gmbh | Secure controlling of vehicle components in a telecommunication network |
US11184340B2 (en) * | 2017-12-15 | 2021-11-23 | Volkswagen Aktiengesellschaft | Apparatus, method, and computer program for enabling a transportation vehicle component and vehicle-to-vehicle communication module |
US11510051B2 (en) | 2017-12-15 | 2022-11-22 | Volkswagen Aktiengesellschaft | Devices, methods, and computer program for releasing transportation vehicle components, and vehicle-to-vehicle communication module |
WO2019172929A1 (en) * | 2018-03-09 | 2019-09-12 | Ford Global Technologies, Llc | Integrating transportation services and facility access services through a calendar system |
EP4239562A3 (en) * | 2018-03-28 | 2023-11-22 | Pioneer Corporation | Server device, information processing method, program, and storage medium |
WO2019232154A1 (en) * | 2018-06-01 | 2019-12-05 | Sherr David M | Software-defined network resource provisioning architecture |
US11140019B2 (en) | 2018-06-01 | 2021-10-05 | David M. Sherr | Software-defined network resource provisioning architecture |
US10834199B2 (en) * | 2018-09-18 | 2020-11-10 | Ford Global Technologies, Llc | Cloud authorized vehicle control |
US11540350B2 (en) | 2018-10-25 | 2022-12-27 | Mobile Tech, Inc. | Proxy nodes for expanding the functionality of nodes in a wirelessly connected environment |
US10614682B1 (en) | 2019-01-24 | 2020-04-07 | Mobile Tech, Inc. | Motion sensing cable for tracking customer interaction with devices |
US10593443B1 (en) | 2019-01-24 | 2020-03-17 | Mobile Tech, Inc. | Motion sensing cable for intelligent charging of devices |
US12047418B2 (en) | 2019-06-05 | 2024-07-23 | Cisco Technology, Inc. | Adaptive network controls for IoT and other applications |
DE102020104712B4 (en) | 2020-02-23 | 2021-09-16 | Bayerische Motoren Werke Aktiengesellschaft | Method and system for providing a communication function in a mobile network |
DE102020104712A1 (en) | 2020-02-23 | 2021-08-26 | Bayerische Motoren Werke Aktiengesellschaft | Method and system for providing a communication function in a mobile network |
WO2021254743A1 (en) * | 2020-06-16 | 2021-12-23 | innogy eMobility Solutions GmbH | Charging station for an electric vehicle, central processing unit and charging station system |
KR20220033956A (en) * | 2020-09-10 | 2022-03-17 | 모셔널 에이디 엘엘씨 | Managing power of electronic devices on a vehicle |
CN114162063A (en) * | 2020-09-10 | 2022-03-11 | 动态Ad有限责任公司 | Vehicle, method for vehicle, and storage medium |
KR102527022B1 (en) | 2020-09-10 | 2023-04-27 | 모셔널 에이디 엘엘씨 | Managing power of electronic devices on a vehicle |
DE102020124249A1 (en) | 2020-09-17 | 2022-03-17 | Bayerische Motoren Werke Aktiengesellschaft | Method and system for providing a communication function in a means of transportation |
WO2024008542A1 (en) * | 2022-07-05 | 2024-01-11 | Mercedes-Benz Group AG | Method for registering a control unit of a vehicle in a service infrastructure |
DE102022117811B3 (en) | 2022-07-15 | 2023-09-07 | Cariad Se | Method and device for deleting user data in a motor vehicle and motor vehicle |
Also Published As
Publication number | Publication date |
---|---|
US9277370B2 (en) | 2016-03-01 |
US20140303807A1 (en) | 2014-10-09 |
US10117066B2 (en) | 2018-10-30 |
US9225782B2 (en) | 2015-12-29 |
US20150264554A1 (en) | 2015-09-17 |
US8848608B1 (en) | 2014-09-30 |
US20170251339A1 (en) | 2017-08-31 |
US20150029987A1 (en) | 2015-01-29 |
US20130301584A1 (en) | 2013-11-14 |
US20190020985A1 (en) | 2019-01-17 |
US8718797B1 (en) | 2014-05-06 |
US9036509B1 (en) | 2015-05-19 |
US8863256B1 (en) | 2014-10-14 |
US10979875B2 (en) | 2021-04-13 |
US8989954B1 (en) | 2015-03-24 |
US9654937B2 (en) | 2017-05-16 |
US9888363B2 (en) | 2018-02-06 |
US9083581B1 (en) | 2015-07-14 |
US8514825B1 (en) | 2013-08-20 |
US20150222708A1 (en) | 2015-08-06 |
US9154900B1 (en) | 2015-10-06 |
US8903593B1 (en) | 2014-12-02 |
US8705527B1 (en) | 2014-04-22 |
US20140215491A1 (en) | 2014-07-31 |
US10602329B2 (en) | 2020-03-24 |
US9860709B2 (en) | 2018-01-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8863256B1 (en) | System and method for enabling secure transactions using flexible identity management in a vehicular environment | |
US20200314103A1 (en) | Mobile device enabled tiered data exchange via a vehicle | |
US10231125B2 (en) | Secure telematics | |
EP3576378B1 (en) | Transferring control of vehicles | |
CN106921647B (en) | Automobile management system and method | |
US10308198B2 (en) | Electronic device and vehicle control method using the same | |
US11397823B1 (en) | Remote hardware access service | |
US10367795B2 (en) | Vehicle wireless internet security | |
US11637832B2 (en) | Vehicle, server, and method for controlling the same | |
US20200079320A1 (en) | Biometric authentication and vehicle function control based on a vehicle operation pattern | |
US10489132B1 (en) | Authenticating mobile device for on board diagnostic system access | |
US20200216077A1 (en) | Systems and methods for vehicle systems customization for one or more users of the vehicle | |
EP2797780B1 (en) | Secured electronic device | |
US20170076279A1 (en) | Authenticating purchases made with a handheld wireless device using a vehicle | |
Pelzl et al. | Automotive embedded systems applications and platform embedded security requirements | |
CN111886814A (en) | Method and system for establishing connection between vehicle network service and external application |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |