Source: http://www.google.com/patents/US6505100?ie=ISO-8859-1&dq=5,072,412
Timestamp: 2014-11-23 07:46:51
Document Index: 351407687

Matched Legal Cases: ['arts 1', 'art 2', 'art 3', 'arts 1', 'art 2', 'art 3', 'art 1', 'arts 1', 'art 1']

Patent US6505100 - Distributed vehicle information processing and vehicle control system - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA distributed vehicle information processing and vehicle control system has at least one first system part on board the vehicle side and at least a second system part, each for carrying out one or more vehicle-related application functions, with the system parts communicating with one another via an...http://www.google.com/patents/US6505100?utm_source=gb-gplus-sharePatent US6505100 - Distributed vehicle information processing and vehicle control systemAdvanced Patent SearchPublication numberUS6505100 B1Publication typeGrantApplication numberUS 09/517,530Publication dateJan 7, 2003Filing dateMar 2, 2000Priority dateMar 2, 1999Fee statusPaidAlso published asDE19909157A1, EP1033691A2, EP1033691A3, EP1033691B1Publication number09517530, 517530, US 6505100 B1, US 6505100B1, US-B1-6505100, US6505100 B1, US6505100B1InventorsMatthias Stuempfle, Akthar Jameel, Axel FuchsOriginal AssigneeDaimlerchrysler AgExport CitationBiBTeX, EndNote, RefManPatent Citations (25), Non-Patent Citations (5), Referenced by (57), Classifications (11), Legal Events (6) External Links: USPTO, USPTO Assignment, EspacenetDistributed vehicle information processing and vehicle control systemUS 6505100 B1Abstract A distributed vehicle information processing and vehicle control system has at least one first system part on board the vehicle side and at least a second system part, each for carrying out one or more vehicle-related application functions, with the system parts communicating with one another via an associated data transmission network. The systems parts have a component-based construction composed of different components, which communicate with one another in order to carry out different functions. Each component has a function-calling interface, via which the function carried out by the component can be called up by other components, in this system part or in another system part, and a configuration interface via which its configuration can be defined and varied. A configuration manager unit, provided for this purpose, configures the components via this interface depending on what other components are present in the system.
BACKGROUND AND SUMMARY OF THE INVENTION This application claims the priority of German patent document 199 09 157.9, filed Mar. 2, 1999, the disclosure of which is expressly incorporated by reference herein.
In the field of general data processing, a component-based system design has recently been proposed as an alternative to central system architectures. See, for example, the Journal article D. Kiely, �Are Components�The Future of Software?�, IEEE Computer Magazine, page 10, February 1998. In this case, the function to be provided by the overall system is broken down into individual functional units (�components�), which then provide the overall desired function by suitable linking and communication with one another. Such breakdown into components on the one hand simplifies their reuse and the design of complex systems from these components, and on the other hand simplifies the production of robust components themselves (since they need be equipped with only a limited, clear functional scope). The components are characterized by their external identical architecture, which makes it possible to link them to one another in a simple manner, such that the function provided by a particular component may initially be viewed independently of this architecture.
The explosive growth in the Internet and the Worldwide Web has led to distributed systems becoming increasingly important. To simplify the implementation of such systems, and to allow component-based systems to be provided, an increasing number of distributed object models have been established. The system developers are also making ever greater use of Internet-oriented solutions for these object models and are implementing them, for example, using Java RMI or �Java Beans�. See the corresponding Internet information from Sun Microsystems with DCOM from Microsoft; see also, the publications T. Albertson, �Best Practices in Distributed Object Application Development: RMI, CORBA and DCOM, February 1998, Internet page �http://developer.com/news/techfocus/022398_distl.htm� and P. E. Chung et al., �DCOM and CORBA Side by Side, Step by Step, and Layer by Layer, September 1997, Internet page �http://www.cs.wustl.edu/≈schmitt/submit/Paper.html�, or, on the basis of CORBA, see also A. Vogel, K. Duddy, �Java Programming with CORBA�, John Wiley & Sons, 1997.
As is evident from the cited literature, the trend towards object-oriented component models can be explained by the following advantages: first, by the capability for reuse of existing algorithms and software, and for �rapid prototyping� of applications by �plug-and-play� interaction of the components; second, mutually independent development and implementation of components; third efficient code maintenance including the systematic distribution of updates; and fourth �lightweight� and �thin clients� implementations, which communicate with infrastructure-based systems, which can be localized there at various points.
One of the characteristic features of such components is that they follow a standard architecture specification, which makes it easier to join them together to form an overall system. In this case, this architecture in principle has nothing to do with the actual function of the component. In fact, it defines how the components interact with one another, but not how they �converse�. This characterization is independent of whether the specific component is in the form of software or hardware.
The trend towards component models is evident in the increasing importance of technologies which support distributed component systems, such as �Java Remote Method Invocation (RMI)� as the basis for the JavaBeans components �Common Object Request Broker Architecture (CORBA)� and �Distributed Component Object Model (DCOM)� from Microsoft for implementation of ActiveX. All these models use the client/server approach.
To this end, the configuration manager unit receives knowledge about the components that are present in the system, and configures the respective component, via its configuration interface, depending on what other components are present. In consequence, this configuration manager unit allows a component which has been newly fitted in a system part (irrespective of whether this is by reequipment of the system with the same system part or by movement from another system part) to be �configured� such that it can communicate optimally with the other components that are present.
In one embodiment of the invention, a component loader is provided for the respective system part (also referred to as a �bathtub� in general computer processing), which accommodates the respective components. The latter communicate via the component loader with an operating system in the system part to which, on the other hand, various external appliance units are coupled, depending on the system part.
In another embodiment of the invention, a function-based hierarchy of the components is provided in vehicle-component-related components or �interface� components, which are closely based on the existing hardware, vehicle appliance units and, for example, provide access to hardware interfaces for communications appliances or the display and control appliances of a user interface. Aggregation components offer services which aggregate raw information from the vehicle-component-related components, and in higher-level application components represent the actual services and have access not only to the aggregation components but also to an intermediate layer and to the vehicle-component-related components and user-interface components.
According to another feature of the invention, means are provided for dynamically moving one or more of the components between the involved system parts during the system life, and thus, in particular, at any desired times throughout the entire life of the vehicle. These means for moving components make use of the fact that the components are provided with a configuration interface and are �configurable� via this interface. Thus, they can be varied to match a new component environment of a different system part. In consequence, a respective component can, for example, be placed in one system part for certain times and in another system part for other times, depending on the changing external conditions, such as the available transmission capacity of the network communication path. Those components which are not closely related to vehicle-side hardware appliance units are particularly suitable for such movement.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 shows a schematic illustration of a distributed vehicle information processing and vehicle control system having system parts on board and external to the vehicle, which are networked with one another;
DETAILED DESCRIPTION OF THE DRAWINGS FIG. 1 shows, schematically, a distributed vehicle information processing and vehicle control system which comprises a plurality of physically separated system parts 1 a, 2 a, 3 a, which form active network nodes in a data transmission network 4, such as the Internet, and communicate with one another via this network. A first system part la is located in the vehicle 1 itself, which represents a �mobile host� in the network 4. A second, stationary system part 2 a is located in a service provider 2, while a third system part 3 a is located in a high-performance service center 3. Other vehicles may form active network nodes in the same way, which can access services from the service provider 2 and from the high-performance service center 3. (Although not shown, there may in each case also be a plurality of the two last-mentioned service providers in the data network 4.)
The components which are used to form the system parts 1, 2, 3, and thus the system overall, each include two interfaces: a function-calling (or remote) interface, via which the actual function of the relevant component (that is to say its service) can be called by another component in the same system part or elsewhere by a remote network node, and a configuration interface, which is used for variable configuration of the component, to match the situation. The configuration interface allows the component to be �configured� variably in different system environments, and existing components can be made aware of the newly positioned component via this interface.
This allows a component to be easily fitted and moved (even after the system generation) for the system life, and even if the system boundary conditions change. In this case, the newly fitted system components, and system components (which may already be present in some circumstances) would have to be matched to one another. This may mean, for example, that the addresses of the components would have to be made known to one another, for which purpose the components offer their own �home page� via which the necessary modifications can be carried out. A specific configuration manager unit is provided in this case in order to carry out this configuration task. This unit knows which components are currently in the system and, via the configuration interface, has access to the individual components, in order to modify their configuration.
The system part 2 a of the service provider 2 primarily contains application components for carrying out services with a vehicle-related functionality, while the system part 3 a of the high-performance service center 3 primarily contains application support components, which require high-performance computation capacities. Apart from application components which represent the actual service applications, the on board vehicle system part 1 a primarily also has components �close to the equipment�, which are used to control hardware appliance units installed in the vehicle 1, such as a presentation manager component 19, which accesses a visual display 24 and a loudspeaker 26.
In addition, communication manager components are used to handle data communication procedures between the system parts 1 a, 2 a, 3 a via the network 4. The entity formed by the components of the respective system part 1 a 2 a, 3 a has an associated component loader (�bathtub�) or component server 1 b, 2 b, 3 b. One suitable example of such a component loader is the ChaiServer from Hewlett-Packard, which is implemented in the Java programming language and supports the loading of the components as well as the routing of method calls to the appropriate components; for further details, see the Company information document Hewlett-Packard �HP ChaiServer: An Overview� on the Internet page �http://www.chai.hp.com/emso/pdf/chaiserverwp.pdf� and �HP Application Server� on the Internet page �http://www.hpconnect.com/embedded/vm/sweb.htm�.
Via its remote interface 5 a, the port manager component 5 allows access to the system interfaces from any given point in the network, for example from two explicitly shown applications 7 a, 7 b. The configuration interface 5 a of the port manager component 5 is also shown schematically. The port manager component 5 has no information about the semantic content of the information which is called or written via it. In the chosen Java implementation, it is thus possible for the Java Virtual Machine (JVM) 8 to use additionally formed classes 9, that is to say �port classes� to allow physical access to the serial interface 6.
Apart from appropriate interfaces, via respective interface manager components 21, 22 the presentation manager has access to user interface components in the vehicle, such as �text-to-speech� and �speech-to-text� appliances 23, visual displays 24 and �touchscreen� and �pointing� appliances to carry out its task. The presentation manager component 19 interacts closely with the system configuration management, since it requires information on the input and output appliances that are present in the vehicle. Furthermore, it is able to suitably resolve concurrent output requests from different applications, comparable to a �Window Manger�.
The communication between the system objects is based on conventional procedures, such as �remote procedure call� (RPC) and its Java version, the �remote method invocation� (RMI). Methods relating to a component which are intended to be called by another component are described in an interface file, comparable with the �interface description language� (IDL) in CORBA. The required �stubs� are then generated from this file, and are linked to a component. The �uniform resource locator� (URL) is used for addressing the method, which is used to address that machine on which the addressed component is running and on which, furthermore, the component itself and the desired method, with an argument, can be specified. URL addressing results in position transparency, that is to say positioning independent of the components, since the machine address is resolved independently of the client entity, for example via a �domain name service� (DNS).
The configuration manager KM is now used to �configure� a respective moved component into its new environment and to �inform� the already existing components about the component which is to be newly added to the relevant system part, that is to say to match its configuration to this. To this end, the configuration manager KM has access via the configuration interfaces to the individual components in the relevant system part. The configuration manager KM knows which components there are in the system, checks their consistency, and then makes the suitable modified configuration accesses to the individual components.
FIG. 7 shows the capability for dynamic movement of a component between a vehicle 31, on the one hand, and a system infrastructure 32 external to the vehicle, on the other hand, using the example of a service support component 33 and based on three different scenarios which make such component movement desirable. In this context, see also the Journal article S. Hild and P. Robinson, �Mobilizing Applications�, IEEE Personal Communications, 4, No. 5, 1997, page 26. This is based on an upgraded client/server model, in which the service support component 33 is also connected, as a server, between a presentation manager component 34 in the vehicle 31 as the client, and a server component 35 on the infrastructure side, and which, to a reduced extent, can carry out certain server functions instead of the server component 35 on the infrastructure side.
If the communications costs between the vehicle 31 and the infrastructure 32 are high, the solution illustrated in the top part of FIG. 7 is chosen, in which the service support component 33 is positioned in the vehicle 31, so that it can handle its communication with the presentation manager 34 within the vehicle, and a high proportion of the calculations are carried out in the vehicle 31, thus keeping the communication with the infrastructure 32 minimal, or avoiding it entirely at times. In this case, the vehicle forms a �thick mobile host� which contains a reduced version of the server component 35 on the infrastructure side, in the form of the service support component 33.
If the cost of communication between the vehicle 31 and the infrastructure 32 is, on the other hand, comparatively low, it is advantageous to choose the solution shown in the center part of FIG. 7, in which the service support component 33 is arranged in the infrastructure 32, where it can exploit the advantages of the greater computation capacity and the availability of further resources located in the data network, such as up-to-date traffic data. In this case, the vehicle forms a �thin mobile host�.
The dynamic movement of components, such as the service support component 33 in this case, is now used to avoid a long-term restriction to one or the other of these two solutions and, instead, to be able to move the components backwards and forwards between the system parts, in this case between the infrastructure 32 and the vehicle 31, depending on the boundary conditions, throughout the system life; that is, to move the service support component 33 optionally into the vehicle 31 or into the infrastructure 32, as is shown in the lower part of FIG. 7. The vehicle 31 then forms a �component-based host� into which it is possible selectively to load components from the infrastructure 32, and from which components can be moved into the infrastructure 32.
Depending on the requirements for vehicle-related services, such as telematics services, the present distributed vehicle information processing and vehicle control system has a specific basic number of components in vehicles and in the infrastructure, which offer services such as �time�, �location/position� or �map matching�. These basic services may then be used by a number of other services. Thus, for example, the position information may be used not only by a navigation service but also by a breakdown service, in order to pass on the present vehicle position to the breakdown assistant. Service providers do not need to repeatedly remove such basic parts of the system, but can build on the existing basic components. Using the existing component-based system architecture, new services can be provided on the basis of existing components in two ways that are supported by the system architecture, to be precise using an interface-based service model, or an event-controlled service model.
FIG. 9 shows a navigation sub-system which is designed using such an interface-based model. In this case, a �navigation service� component 45 accesses the services of other components, such as a mapping component 46, a routing component 47, a wheel rotation-speed detection component 48, a presentation manager component 49 etc., in order to provide the user with their service. When the navigation service component 45 is being programmed, the interfaces of the components used must be known.
FIG. 10 shows the situation for an event-controlled model, which is provided by using a �shared-space� component 50 which represents a server-based data memory that is used jointly by a number of components that are involved, to which the components that are involved can write specific values/objects of interest, as is illustrated in FIG. 10 for a calendar application component 51 and a further application component 52. Furthermore, the components that are involved can be registered with this �shared-space� component 50, which thus acts as a data-maintenance component in order to be informed when a new value/object which is relevant for it occurs, referred to as a so-called �event-triggered notification�.
Approaches of this type move the knowledge problem relating to the existence of components (mentioned above) to a higher level, since the communication between components always takes place via the �shared-space� component 50, which can be provided using a very small API and is known to each component. The components need agree only on the contents, which are written to the �shared-space� component 50. Such approaches are well known, for example by the terms �Linda Space�, see Internet page �http://www.cs.yale.edu/HTML/YALE/CS/Linda/linda.html� and �Java Spaces�, Sun Microsystems, Internet page http://java.sun.com/products/javaspaces/specs�, in general computer processing.
The advantage of this model is the mutually independent programming of the components and the small amount of �shared-space� API. Furthermore, new components can be integrated in the system without any problems, and immediately actively contribute to the provision of value-added services. To do this, applications must be written �cooperatively� that is to say such that they also actually write relevant information to the �shared-space� component. Suitable mechanisms, such as time monitoring, transaction models, etc., are implemented in the �shared-space� component and suppress the occurrence of oscillating effects between components when new values are alternately being written to the �shared-space� component.
A combined implementation of partially interface-based modeling and partially event-controlled modeling, depending on the respective applications, may be advantageous. Thus, for example, when processing an engine speed value, which is available all the time at intervals of a few milliseconds, an event-controlled model, in which each new speed value is written to the �shared-space� component and all potential recipient components are informed of this, makes little sense, so that interface-based modeling is to be preferred for this purpose.
A platform-independent implementation of the present distributed vehicle information processing and vehicle control system is feasible, as already explained, for example by choosing the development and implementation environment �Java�, since this already directly supports an object-oriented implementation of components at many points, and in this case, as has likewise been mentioned above, the ChaiServer from Hewlett-Packard, implemented in Java may, for example, be used as the component loader. To allow access to the system hardware, which is not envisaged as standard by Java, additional classes are introduced to the system, which are likewise monitored via the system configuration management and are loaded into the vehicle only when required. The removal of a component, in order to release the relevant resource once again, is likewise supported by the ChaiServer in the scope of the dynamic component movement process.
The Java implementation results in a high level of platform independence. Components may be stored in a component database, in the infrastructure external to the vehicle, and may be loaded into the appropriate systems as required. The components are preferably modeled and implemented using object-based viewpoints, and are in this case similar to the Java �Servlets�, which are used to increase the functionality of the server in a simple way, see for general computer processing, the publication �Servlets� from Sun Microsystems, Internet page �http://java.sun.com/products/javaserver/servlets�. Communication between the components is based on Java-RMI.
Methods for components which run in the context of the ChaiServer are called up by means of HTTP. See J. Morgan, �The HEHAW Invocation Model,� Broadband Information Systems, Hewlett-Packard, Palo Alto, 1997. The use of HTTP has the advantage that it is virtually universally supported and �firewalls� can also be transferred. The desired position transparency is achieved by the addressing and call syntax mentioned above using a �uniform resource locator� (URL).
FIG. 11 shows an application relating to this with an example of a component 57, which is implemented on a vehicle machine 58. The component 57 provides a �Foo� method, which is called up using a string argument. The result of the method may be an HTML document. The HTTP call syntax for a call 59 by another component 60 then contains the address of the vehicle machine 58, the designation of the example of a component 57, and the details of the �Foo� method with �html� characterization.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5365451 *Mar 4, 1994Nov 15, 1994Motorola, Inc.Mobile unit tracking systemUS5430656 *Sep 8, 1993Jul 4, 1995Dekel; ItzhakMobile communications systemUS5479157 *Feb 17, 1995Dec 26, 1995Prince CorporationRemote vehicle programming systemUS5625556 *Apr 28, 1995Apr 29, 1997Trimble Navigation LimitedAccurate time standard for vehicle operationUS5648769 *May 18, 1995Jul 15, 1997Toyota Jidosha Kabushiki KaishaVehicle data processing system which can communicate with information centerUS5848368 *Oct 28, 1996Dec 8, 1998Caterpillar Inc.Method for controllably loading haul vehicles by a mobile loading machineUS6064319 *Oct 22, 1998May 16, 2000Matta; David M.Method and system for regulating switching of a traffic lightUS6084510 *Apr 18, 1997Jul 4, 2000Lemelson; Jerome H.Danger warning and emergency response system and methodUS6097316 *Apr 20, 1998Aug 1, 2000Visteon Technologies, LlcCommunication protocol for a vehicle navigation systemUS6108591 *Jan 22, 1998Aug 22, 2000Qualcomm IncorporatedMethod and apparatus for validating vehicle operatorsUS6141611 *Dec 1, 1998Oct 31, 2000John J. MackeyMobile vehicle accident data systemUS6154689 *Jan 2, 1997Nov 28, 2000Integral Media S.A.Multimedia computer equipment for automatic transmission of multimedia entertainment programsUS6175789 *Sep 10, 1999Jan 16, 2001Microsoft CorporationVehicle computer system with open platform architectureUS6202008 *Sep 10, 1999Mar 13, 2001Microsoft CorporationVehicle computer system with wireless internet connectivityUS6208918 *Oct 7, 1998Mar 27, 2001Toyota Jidosha Kabushiki KaishaData recovery system and data recovery program recorded mediumUS6230097 *Aug 31, 1998May 8, 2001Trimble Navigation LimitedAccurate vehicle navigationUS6236911 *Apr 19, 2000May 22, 2001Supersensor (Proprietary) LimitedLoad monitoring system and method utilizing transponder tagsDE4140803A1Dec 11, 1991Jun 17, 1993Webasto Ag FahrzeugtechnikMatching circuitry adapting electric control devices for vehicle accessories - translates signals between vehicle transmission system and control devices using microcomputer under control of external interfaceDE4315494A Title not availableDE19620885A1May 23, 1996Nov 27, 1997Bayerische Motoren Werke AgData update method for vehicle controlDE19625002A1Jun 22, 1996Jan 2, 1998Daimler Benz AgFahrzeugkommunikationssystemDE19640735A1Oct 2, 1996Apr 23, 1998Bosch Gmbh RobertTelematikger�t f�r ein KraftfahrzeugDE19821500A1May 13, 1998Jan 28, 1999Siemens AgController of data transmission for e.g. airbag in motor vehicleEP0890937A2Jun 25, 1998Jan 13, 1999Robert Bosch GmbhDevice for transmitting data from a vehicleJPH1127749A Title not available* Cited by examinerNon-Patent CitationsReference1"Are Components the Future of Software?", Don Kiely, Industry Trands, pp. 10-11, Feb. 1998.2 *Opne System Interconnection (OSI)-3 pages.*3Opne System Interconnection (OSI)�3 pages.*4Seokhoon Lee et al., "Toward the Next Generation Public Traffic Information System Using Internet", 1997 IEEE, pp. 505-510.5Stefan G. Hild et al., "Mobilizing Applications", IEEE Personal Communications, Oct. 1997, pp. 26-34.* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS6704564 *Sep 22, 2000Mar 9, 2004Motorola, Inc.Method and system for controlling message transmission and acceptance by a telecommunications deviceUS6747365 *Aug 31, 2001Jun 8, 2004Motorola, Inc.Vehicle active network adapted to legacy architectureUS6839710Jun 28, 2002Jan 4, 2005Motorola, Inc.Method and system for maintaining a configuration history of a vehicleUS6873940 *Mar 7, 2000Mar 29, 2005Laserdynamics, Inc.Measuring method and measuring service system using communication meansUS6874012 *Nov 1, 2000Mar 29, 2005Sun Microsystems, Inc.System and method for a display device using a priority messaging protocolUS6885916Aug 31, 2001Apr 26, 2005Motorola, Inc.Data packet for a vehicle active networkUS6931004 *Aug 31, 2001Aug 16, 2005Motorola, Inc.Vehicle active network with backbone structureUS6947760 *Jan 4, 2002Sep 20, 2005Motorola, Inc.Method of optimizing the transmission of data in a wireless communication networkUS6978206 *Jun 23, 2003Dec 20, 2005Infogation CorporationDistributed navigation systemUS7010682Jun 28, 2002Mar 7, 2006Motorola, Inc.Method and system for vehicle authentication of a componentUS7027387Aug 31, 2001Apr 11, 2006Motorola, Inc.Vehicle active network with data redundancyUS7039520 *Mar 28, 2002May 2, 2006Robert Bosch GmbhMethod for operating a navigation system for a vehicle and corresponding navigation systemUS7076665Jun 28, 2002Jul 11, 2006Motorola, Inc.Method and system for vehicle subassembly authentication of a componentUS7127611Jun 28, 2002Oct 24, 2006Motorola, Inc.Method and system for vehicle authentication of a component classUS7131005Jun 28, 2002Oct 31, 2006Motorola, Inc.Method and system for component authentication of a vehicleUS7135962 *Dec 20, 2004Nov 14, 2006Dei Headquarters, Inc.Security and remote access for vehicular entertainment, safety, and convenience systemsUS7137001Jun 28, 2002Nov 14, 2006Motorola, Inc.Authentication of vehicle componentsUS7137142Jun 28, 2002Nov 14, 2006Motorola, Inc.Method and system for vehicle authentication of a component using key separationUS7146260 *Apr 24, 2001Dec 5, 2006Medius, Inc.Method and apparatus for dynamic configuration of multiprocessor systemUS7170853Aug 31, 2001Jan 30, 2007Temic Automotive Of North America, Inc.Vehicle active network topologiesUS7173903Aug 31, 2001Feb 6, 2007Temic Automotive Of North America, Inc.Vehicle active network with communication path redundancyUS7181511 *Apr 15, 2002Feb 20, 2007Yazaki North America, Inc.System and method for using software objects to manage devices connected to a network in a vehicleUS7181615 *Jun 28, 2002Feb 20, 2007Motorola, Inc.Method and system for vehicle authentication of a remote access deviceUS7228420Jun 28, 2002Jun 5, 2007Temic Automotive Of North America, Inc.Method and system for technician authentication of a vehicleUS7254604 *Jul 31, 2002Aug 7, 2007Nissan Motor Co., Ltd.Distributed information collecting systemUS7269482 *Apr 22, 2002Sep 11, 2007Vetronix CorporationIn-vehicle information system and software frameworkUS7325135Jun 28, 2002Jan 29, 2008Temic Automotive Of North America, Inc.Method and system for authorizing reconfiguration of a vehicleUS7415331Jul 25, 2005Aug 19, 2008Lockheed Martin CorporationSystem for controlling unmanned vehiclesUS7415508Aug 31, 2001Aug 19, 2008Temic Automotive Of North America, Inc.Linked vehicle active networksUS7484008 *Oct 4, 2000Jan 27, 2009Borgia/Cummins, LlcApparatus for vehicle internetworksUS7549046Jun 28, 2002Jun 16, 2009Temic Automotive Of North America, Inc.Method and system for vehicle authorization of a service technicianUS7600114Jun 28, 2002Oct 6, 2009Temic Automotive Of North America, Inc.Method and system for vehicle authentication of another vehicleUS7646285 *Sep 8, 2006Jan 12, 2010Dei Headquarters, Inc.Security and remote access for vehicular safety and convenience systemsUS7681448Jan 31, 2008Mar 23, 2010Medius, Inc.System and method for aligning sensors on a vehicleUS7693656 *Feb 20, 2007Apr 6, 2010Denso CorporationNavigation apparatusUS7734386Jul 25, 2005Jun 8, 2010Lockheed Martin CorporationSystem for intelligently controlling a team of vehiclesUS7778739Aug 7, 2006Aug 17, 2010Medius, Inc.Method and apparatus for dynamic configuration of multiprocessor systemUS7783401Aug 10, 2007Aug 24, 2010Denso CorporationMethod and device for managing tasks of in-vehicle electronic control unitUS7793136Dec 27, 2006Sep 7, 2010Eagle Harbor Holdings LLCApplication management system with configurable software applicationsUS7797367Oct 4, 2000Sep 14, 2010Gelvin David CApparatus for compact internetworked wireless integrated network sensors (WINS)US7849415 *Apr 20, 2000Dec 7, 2010Nokia CorporationCommunication terminalUS7869906Jan 8, 2007Jan 11, 2011Ford Global TechnologiesWireless gateway apparatus and method of bridging data between vehicle based and external data networksUS7984184Oct 21, 2004Jul 19, 2011Leica Geosystems AgMethod and apparatus for managing information exchanges between apparatus on a worksiteUS8027268 *Oct 24, 2008Sep 27, 2011Eagle Harbor Holdings, LlcMethod and apparatus for dynamic configuration of multiprocessor systemUS8050811 *Dec 12, 2006Nov 1, 2011General Motors LlcMethod for controlling the distribution of vehicle-related dataUS8194536Aug 31, 2001Jun 5, 2012Continental Automotive Systems, Inc.Vehicle active network with fault tolerant devicesUS8463494Oct 7, 2010Jun 11, 2013General Motors LlcAftermarket telematics unit and method for installation verificationUS8494447Jul 29, 2010Jul 23, 2013General Motors LlcAftermarket telematics unit for use with a vehicleUS8543289Sep 30, 2010Sep 24, 2013Genreal Motors LLCAftermarket telematics systemUS8571752Aug 5, 2010Oct 29, 2013General Motors LlcVehicle mirror and telematics systemUS8604937Jul 29, 2010Dec 10, 2013General Motors LlcTelematics unit and method for controlling telematics unit for a vehicleUS20100125387 *Sep 29, 2009May 20, 2010Chung-Ang University Industry-Academy Cooperation FoundationSystem of integrated telematics service and method of controlling the systemUS20130103811 *Apr 6, 2011Apr 25, 2013Volker BlaschkeMethod for providing a communication for at least one deviceCN100565446CApr 26, 2005Dec 2, 2009宝马股份公司Configuration system of a vehicle and method for configuring at least one control unit of the configuration systemDE102004051414A1 *Oct 22, 2004Apr 27, 2006Volkswagen AgCommunication device for motor vehicle, has interface between connecting module and indicator or between connecting module and control unit for transferring data of independent format between indicator, control unit and connecting moduleWO2005041519A2 *Oct 21, 2004May 6, 2005Leica Geosystems AgMethod and apparatus for managing information exchanges between apparatus on a worksiteWO2006114112A1 *Apr 26, 2005Nov 2, 2006Bayerische Motoren Werke AgConfiguration system of a vehicle and method for configuring at least one control unit of the configuration system* Cited by examinerClassifications U.S. Classification701/1, 701/24, 701/36International ClassificationG08G1/09, G06F15/177, H04B7/26, G06F9/48, B60R21/01Cooperative ClassificationB60R2021/0104, G08G1/09European ClassificationG08G1/09Legal EventsDateCodeEventDescriptionJun 22, 2010FPAYFee paymentYear of fee payment: 8Oct 22, 2008ASAssignmentOwner name: RAMSLE TECHNOLOGY GROUP GMBH, LLC, DELAWAREFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DAIMLER AG;REEL/FRAME:021719/0080Effective date: 20080727Jun 11, 2008ASAssignmentOwner name: DAIMLERCHRYSLER AG, GERMANYFree format text: CORRECTIVE ASSIGNMENT TO CORRECT THE IDENTIFYING INFORMATION IN THE ASSIGNMENT DOCUMENT PREVIOUSLY RECORDED ON REEL 010898 FRAME 0692. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT OF ASSIGNOR S INTEREST.;ASSIGNORS:STUEMPFLE, MATTHIAS;JAMEEL, AKTHAR;FUCHS, AXEL;REEL/FRAME:021078/0951;SIGNING DATES FROM 20000324 TO 20000612Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE IDENTIFYING INFORMATION IN THE ASSIGNMENT DOCUMENT PREVIOUSLY RECORDED ON REEL 010898 FRAME 0692;ASSIGNORS:STUEMPFLE, MATTHIAS;JAMEEL, AKTHAR;FUCHS, AXEL;REEL/FRAME:021078/0951;SIGNING DATES FROM 20000324 TO 20000612May 14, 2008ASAssignmentOwner name: DAIMLER AG, GERMANYFree format text: CHANGE OF NAME;ASSIGNOR:DAIMLERCHRYSLER AG;REEL/FRAME:020976/0889Effective date: 20071019Owner name: DAIMLER AG,GERMANYFree format text: CHANGE OF NAME;ASSIGNOR:DAIMLERCHRYSLER AG;US-ASSIGNMENT DATABASE UPDATED:20100311;REEL/FRAME:20976/889Free format text: CHANGE OF NAME;ASSIGNOR:DAIMLERCHRYSLER AG;US-ASSIGNMENT DATABASE UPDATED:20100223;REEL/FRAME:20976/889Free format text: CHANGE OF NAME;ASSIGNOR:DAIMLERCHRYSLER AG;US-ASSIGNMENT DATABASE UPDATED:20100406;REEL/FRAME:20976/889Free format text: CHANGE OF NAME;ASSIGNOR:DAIMLERCHRYSLER AG;US-ASSIGNMENT DATABASE UPDATED:20100504;REEL/FRAME:20976/889Free format text: CHANGE OF NAME;ASSIGNOR:DAIMLERCHRYSLER AG;US-ASSIGNMENT DATABASE UPDATED:20100511;REEL/FRAME:20976/889Free format text: CHANGE OF NAME;ASSIGNOR:DAIMLERCHRYSLER AG;REEL/FRAME:20976/889Jun 29, 2006FPAYFee paymentYear of fee payment: 4Jul 6, 2000ASAssignmentOwner name: DAIMLERCHRYSLER AG, GERMANYFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:STUEMPFLE, MATTHIAS;JAMEEL, AKTHAR;FUCHS, AXEL;REEL/FRAME:010898/0692;SIGNING DATES FROM 20000324 TO 20000612Owner name: DAIMLERCHRYSLER AG EPPLESTRASSE 225 STUTTGART GERMRotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google