Source: https://patents.justia.com/patent/7904569
Timestamp: 2019-09-21 11:25:41
Document Index: 298252497

Matched Legal Cases: ['Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'art\n2245963']

US Patent for Method for remote access of vehicle components Patent (Patent # 7,904,569 issued March 8, 2011) - Justia Patents Search
Justia Patents Network Resources Access ControllingUS Patent for Method for remote access of vehicle components Patent (Patent # 7,904,569)
This application claims the benefit of United States Provisional Application No. 60/158,013, filed Oct. 6, 1999, U.S. Provisional Application No. 60/170,865, filed Dec. 15, 1999, U.S. Provisional Application No. 60/208,397, filed May 30, 2000, U.S. Provisional Application No. 60/210,296, filed Jun. 8, 2000, United States Patent Application Number (to be assigned-reference number 21200.702), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.706), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.707), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.708), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.709), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.710), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.711), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.712), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.713), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.714), filed Oct. 4, 2000, and United States Patent Application Number (to be assigned-reference number 21200.715), filed Oct. 4, 2000, all of which are incorporated by reference.
In order to address some of the limitations of present-day vehicle information networks, the Automotive Multimedia Interface Consortium (AMI-C) has developed a set of common specifications for a multimedia interface to motor vehicle electronic systems. A particular aim is to accommodate a wide variety of consumer electronic and computer-based devices in the vehicle. The AMI-C standard network architecture, adopted by nearly all automobile manufacturers worldwide, reduces time to market and facilitates upgrades of vehicle electronics, supports deployment of telematics by providing standard interfaces, and reduces relative costs of electronic components. A variety of standards are being considered for AMI-C buses, among them IEEE 1394, MOST, and Intelligent Data Bus (MB-C), with the possibility of multiple AMI-C approved buses within a vehicle.
The WINS vehicle internetwork of an embodiment provides an information and control internetwork for vehicles, including the associated hardware, together with a suite of applications. An embodiment of the vehicle internetwork disclosed and claimed herein includes a wireline/wireless automotive gateway, programmable IDB-C bus interfaces, and complete internetworked vehicle systems. Automotive Multimedia Interface Consortium (AMI-C) network functions, including telematics, access to vehicle data systems, and security are enabled in this vehicle internetwork using open interfaces that enable interaction with standard web-based software, tools, and databases. The vehicle internetwork leverages the development of hybrid wireless, wireline networked embedded systems, described in U.S. Provisional Application No. 60/158,013, filed Oct. 6, 1999, U.S. Provisional Application No. 60/170,865, filed Dec. 15, 1999, U.S. Provisional Application No. 60/208,397, filed May 30, 2000, U.S. Provisional Application No. 60/210,296, filed Jun. 8, 2000, United States Patent Application Number (to be assigned-reference number 21200.702), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.706), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.707), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.708), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.709), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.710), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.711), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.712), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number 21200.713), filed Oct. 4, 2000, United States Patent Application Number (to be assigned-reference number to 21200.714), filed Oct. 4, 2000, and United States Patent Application Number (to be assigned-reference number 21200.715), filed Oct. 4, 2000, and incorporated herein by reference.
Some networks may not support LP because of resource constraints and legacy or proprietary hardware. These networks link into a non-IP router 710. The non-EP router 710 extracts the raw data from packets into an intermediate format and multiplexes them into a single data stream. This data stream is securely tunneled to the proxy 708 (i.e., encapsulated within a secure IP packet). Return traffic from the proxy 708 is demultiplexed and exported onto the appropriate busses using their native link layer protocols. This device has a known address on one of the networks serviced by the IP router 702. The stub protocols in the proxy 708 take on the task of making these non-IP capable devices appear to be IP devices to the rest of the network, so that this larger network can employ IP-based protocols and routers. In this way, security features and the like are added for the longer-range transport of messages from legacy devices or subnetworks, without imposing impractical burdens on these networks or devices.
The WINS vehicle internetwork of an embodiment uses an interface for each device that is to attach to buses or other networks within a vehicle. For example, an interface is used between an AMI-C bus, such as the Intelligent Data Bus (IDB-C) or IEEE 1394, and consumer appliances that are supported by the bus. The port nodes perform this function. As part of the interface, the port node performs functions including, but not limited to, physical connection to the buses, physical connection to the consumer devices, protocol translation, and security. Although a port node is used for interface to AMI-C buses, the concept of an interface device has broader to implications for vehicle internetwork embodiments, namely, the non-IP router, SNIC and PNP devices.
Regarding node architecture, FIG. 13 shows a number of ways a WINS NG system of an embodiment can be reconfigured to accommodate different applications. For telematic applications, the processor 1302 may be identified with a telematics processor. For diagnostic/prognostic applications, the processor 1302 can be configured as it would in sensor node applications. The legacy OEM port set 1304 aggregates information for more efficient use of the RTIP 1306, and avoids using a large number of its interfaces. For AMI-C applications, there can be to additional processors 1310 and 1312 coupled directly to the RTIP 1306 or coupled through the high speed network, or a combination of both as a result of upgrades over the life of the vehicle. For sensor applications, the automotive ports are replaced by sensor ports.
coupling an Original Equipment Manufacturer (OEM) bus, an Automotive Multimedia Interface Consortium (AMI-C) bus, and an external network via a gateway device, wherein the OEM bus interconnects OEM vehicle systems that perform vehicle functions, and the AMI-C bus interconnects AMI-C devices;
authenticating devices connected to the AMI-C bus at the gateway device using an application processor, wherein authenticating devices connected to the AMI-C bus at the gateway device using an application processor comprises: consulting a security database to determine whether a device attempting to access the AMI-C bus via a port node is authorized to communicate with the AMI-C bus; and in response to determining that the device is unauthorized, instructing the port node to prevent traffic from the unauthorized device from being passed from the device to the AMI-C bus;
routing communications from at least one source to the application processor using a real time processor in the gateway device, the at least one source being selected from the group consisting of the OEM vehicle systems, the AMI-C devices, and the external network;
hosting vehicle applications associated with the OEM vehicle systems and the AMI-C devices on the application processor; and
receiving an external communication at the gateway device and responsively altering a function of a vehicle system of the OEM vehicle systems.
2. The method of claim 1, wherein the function of the vehicle system is selected from the group consisting of vehicle control functions, security functions, diagnostic functions, and network access functions.
3. The method of claim 1, further comprising using the gateway device to provide a firewall between the AMI-C bus and the OEM bus.
4. The method of claim 3, wherein the firewall prevents AMI-C devices connected to the AMI-C bus from disrupting essential functions of the vehicle.
5. The method of claim 1, wherein the gateway device is coupled to a local development network, and wherein the gateway device acts as a bridge between the OEM bus, the AMI-C bus, the external network, and a local development network.
6. The method of claim 5, wherein, in bridging the OEM bus, the AMI-C bus, the external network, and the local development network, the gateway device provides a function selected from the group consisting of protocol translation, security, and privacy functions.
7. The method of claim 5, wherein the local development network supports wireless transfer of information among a remote information station and at least one of vehicle systems and AMI-C devices.
8. The method of claim 5, wherein the gateway device selects a communication method for communications between vehicle systems on the OEM bus, AMI-C devices on the AMI-C bus, the external network, and the local development network.
9. The method of claim 8, wherein an internet coupling provides a low-cost communication method, wherein a wider coverage communication selected from the group consisting of two-way paging and cellular telephone communication provides a higher-cost communication method, and wherein selecting a cost effective communication method comprises:
selecting the low-cost communication method for low priority communications; and
selecting the higher-cost communication method for high priority communications.
10. The method of claim 9, wherein the low priority communication is a communication selected from the group consisting of uploading of video entertainment, uploading of audio entertainment, software upgrading, transfer of vehicle reliability records and transfer of vehicle performance histories.
11. The method of claim 9, wherein the high priority communication is a communication relating to an emergency situation detected by on-board vehicle diagnostics.
12. The method of claim 1, wherein the OEM bus is connected to at least one peripheral electronic device, wherein the at least one peripheral electronic device is selected from the group consisting of a climate control device, a position location device, a Global Positioning System device, a sensor device, a switch cluster, and a device subnetwork, and wherein the AMI-C bus is connected to at least one peripheral AMI-C electronic device, wherein the at least one peripheral AMI-C electronic device is selected from the group consisting of a pager, a video device, an audio device, a multimedia player, a personal digital assistant, and a wireless local area network port.
13. The method of claim 1, wherein hosting vehicle applications associated with the OEM vehicle systems and the AMI-C devices on the application processor comprises hosting applications associated with at least one of passenger conveniences and vehicle operations.
14. The method of claim 1, wherein the vehicle applications associated with the OEM vehicle systems and the AMI-C devices are upgradable via input from the gateway device.
15. The method of claim 1, further comprising supporting atomic transactions among vehicle systems on the OEM bus, AMI-C devices on the AMI-C bus, and the external network.
16. A gateway device comprising:
an Original Equipment Manufacturer (OEM) bus interface port adapted to communicate with OEM vehicle systems connected to an OEM bus;
an Automotive Multimedia Interface Consortium (AMI-C) bus interface port adapted to communicate with an AMI-C device connected to an AMI-C bus;
a gateway port adapted to communicate with an external network, wherein the gateway device couples the OEM bus, the AMI-C bus, and the external network;
a real-time information processor and an application processor, wherein the real-time information processor is adapted to route communications from at least one source to an application processor, the at least one source being selected from the group consisting of the OEM vehicle systems, the AMI-C device, and the external network; and
an application processor, wherein the application processor is adapted to authenticate AMI-C devices connected to the AMI-C bus and host vehicle applications associated with the OEM vehicle systems and the AMI-C devices, wherein authenticating devices connected to the AMI-C bus comprises: consulting a security database to determine whether a device attempting to access the AMI-C bus via a port node is authorized to communicate with the AMI-C bus; and in response to determining that the device is unauthorized, instructing the port node to prevent any traffic from the unauthorized device from being passed from the device to the AMI-C bus, and
wherein the gateway device is operable to receive an external communication and responsively alter a function of a vehicle system.
17. The gateway device of claim 16, further comprising a local development port, wherein the local development port is adapted to communicate with a local development network.
18. The gateway device of claim 17, wherein the gateway device is operable to act as a bridge between the OEM bus, the AMI-C bus, the external network, and the local development network.
19. The gateway device of claim 18, wherein, in bridging the OEM bus, the AMI-C bus, the external network, and the local development network, the gateway device is operable to provide a function selected from the group consisting of protocol translation, security, and privacy functions.
20. The gateway device of claim 18, wherein the gateway device is operable to select a communication method for communications among vehicle systems on the OEM bus, AMI-C devices on the AMI-C bus, the external network, and the local development network.
21. The gateway device of claim 20, wherein selecting a communication method comprises:
selecting a low-cost communication method for low priority communications, wherein the low-cost communication method comprises communication via an internet coupling; and
selecting a higher-cost communication method for high priority communications, wherein the high cost communication method comprises communication via a cellular connection.
22. The gateway device of claim 16, wherein the function of the vehicle system is selected from the group consisting of vehicle control functions, security functions, diagnostic functions, and network access functions.
23. The gateway device of claim 16, wherein hosting vehicle applications associated with the OEM vehicle systems and the AMI-C devices on the application processor comprises hosting vehicle applications associated with at least one of passenger conveniences and vehicle operations.
3475755 October 1969 Bassen et al.
4187492 February 5, 1980 Delignieres
4406016 September 20, 1983 Abrams et al.
4494121 January 15, 1985 Walter et al.
4520674 June 4, 1985 Canada et al.
4642639 February 10, 1987 Nelson
4649524 March 10, 1987 Vance
4862422 August 29, 1989 Brac
4928246 May 22, 1990 Crawley et al.
5095531 March 10, 1992 Ito
5184311 February 2, 1993 Kraus et al.
5203199 April 20, 1993 Henderson et al.
5206806 April 27, 1993 Gerardi et al.
5369584 November 29, 1994 Kajiwara
5420825 May 30, 1995 Fischer et al.
5428636 June 27, 1995 Meier
5475687 December 12, 1995 Markkula, Jr. et al.
5479932 January 2, 1996 Higgins et al.
5483827 January 16, 1996 Kulka et al.
5535380 July 9, 1996 Bergkvist et al.
5553076 September 3, 1996 Behtash et al.
5563948 October 8, 1996 Diehl et al.
5615175 March 25, 1997 Carter et al.
5617371 April 1, 1997 Williams
5701120 December 23, 1997 Perelman et al.
5726911 March 10, 1998 Canada et al.
5734699 March 31, 1998 Lu et al.
5737529 April 7, 1998 Dolin, Jr. et al.
5745758 April 28, 1998 Shaw
5745759 April 28, 1998 Hayden
5760530 June 2, 1998 Kolesar
5794164 August 11, 1998 Beckert et al.
5852232 December 22, 1998 Samsaver et al.
5852351 December 22, 1998 Canada et al.
5854994 December 29, 1998 Canada et al.
5946083 August 31, 1999 Melendez et al.
5946488 August 31, 1999 Tanguay et al.
5959529 September 28, 1999 Kail
5973309 October 26, 1999 Livingston
5987552 November 16, 1999 Chittor et al.
5991806 November 23, 1999 McHann, Jr.
6009363 December 28, 1999 Beckert et al.
6011787 January 4, 2000 Nakano et al.
6014406 January 11, 2000 Shida et al.
6038436 March 14, 2000 Priest
6048276 April 11, 2000 Vandergrift
6061021 May 9, 2000 Zibell
6078269 June 20, 2000 Markwell et al.
6114970 September 5, 2000 Kirson et al.
6144905 November 7, 2000 Gannon
6145082 November 7, 2000 Gannon et al.
6175789 January 16, 2001 Beckert et al.
6175868 January 16, 2001 Lavian et al.
6181994 January 30, 2001 Colson
6184798 February 6, 2001 Egri
6185491 February 6, 2001 Gray
6233610 May 15, 2001 Hayball et al.
6246688 June 12, 2001 Angwin
6246935 June 12, 2001 Buckley
6252544 June 26, 2001 Hoffberg et al.
6255942 July 3, 2001 Knudsen
6285899 September 4, 2001 Ghaem et al.
6298445 October 2, 2001 Shostak et al.
6327607 December 4, 2001 Fant
6341288 January 22, 2002 Yach et al.
6343218 January 29, 2002 Kaneda et al.
6351776 February 26, 2002 O'Brien et al.
6389483 May 14, 2002 Larsson
6400953 June 4, 2002 Furukawa
6414955 July 2, 2002 Clare
6425004 July 23, 2002 Hardjono
6430164 August 6, 2002 Jones
6453910 September 24, 2002 Lloyd
6469639 October 22, 2002 Tanenhaus et al.
6477143 November 5, 2002 Ginossar
6480900 November 12, 2002 Habert
6496575 December 17, 2002 Vasell et al.
6499027 December 24, 2002 Weinberger
6504631 January 7, 2003 Barry et al.
6505086 January 7, 2003 Dodd, Jr. et al.
6505100 January 7, 2003 Stuempfle
6507810 January 14, 2003 Razavi et al.
6532494 March 11, 2003 Frank et al.
6563796 May 13, 2003 Saito
6580979 June 17, 2003 Payton et al.
6584382 June 24, 2003 Karem
6615099 September 2, 2003 Muller et al.
6624881 September 23, 2003 Waibel
6661773 December 9, 2003 Pelissier et al.
6662091 December 9, 2003 Wilson et al.
6678250 January 13, 2004 Grabelsky et al.
6715077 March 30, 2004 Vasudevan et al.
6728514 April 27, 2004 Bandeira et al.
6738814 May 18, 2004 Cox et al.
6779004 August 17, 2004 Zintel
6813542 November 2, 2004 Peshkin et al.
6829437 December 7, 2004 Kirby
6911997 June 28, 2005 Okamoto et al.
6916096 July 12, 2005 Ebert
6990080 January 24, 2006 Bahl et al.
7027773 April 11, 2006 McMillin
7049953 May 23, 2006 Monroe
7069188 June 27, 2006 Roberts
7120508 October 10, 2006 Peshkin
7158758 January 2, 2007 Lim et al.
7161926 January 9, 2007 Elson et al.
7305467 December 4, 2007 Kaiser et al.
7383341 June 3, 2008 Saito et al.
7577872 August 18, 2009 DiBartolomeo et al.
20010056540 December 27, 2001 Ober et al.
20020111213 August 15, 2002 McEntee
20020154631 October 24, 2002 Makansi et al.
20020181501 December 5, 2002 Nova et al.
20040006424 January 8, 2004 Joyce
20040008651 January 15, 2004 Ahmed
20040049428 March 11, 2004 Soehnlen
20060083217 April 20, 2006 Bae et al.
20060206576 September 14, 2006 Obradovich et al.
20070060056 March 15, 2007 Whitaker
20080015748 January 17, 2008 Nagy
20080031213 February 7, 2008 Kaiser et al.
20080126565 May 29, 2008 Osano
20080261529 October 23, 2008 Rosenblatt
20090122723 May 14, 2009 Hirano
20090221275 September 3, 2009 Trip
20090282458 November 12, 2009 Hjelm
20090304009 December 10, 2009 Kolhi
20100057290 March 4, 2010 Brillhart
2245963 February 2000 CA
19743137 April 1999 DE
0814393 December 1997 EP
9917477 April 1999 WO
0054237 September 2000 WO
G. Asada, et al.“Low Power Wireless Communication and Signal Processing Circuits for Distributed Microsensors”, Proceedings of 1997 IEEE International Symposium on Circuits and Systems; Jun. 9-12, 1997, Hong Kong, pp. 2817-2820.
K. Bult, et al.“Low Power Systems for Wireless Microsensors”, 1996 International Symposium on Low Power Electronics and Design; pp. 17-21.
K. Sohrabi, J. Gao, V. Ailawadhi, G. Pottie, “A Self-Organizing Wireless Sensor Network,” Proc. 37th Allerton Conf. On Comm., Control, and Computing, Monticello, IL, Sep. 1999.
U.S. Appl. No. 09/684,388, filed Oct. 4, 2000.
Bhatnagar et al., “Layer Net: A New Self-Organizing Network Protocol,” 1990 IEEE Military Communications Conference, Monterey, CA pp. 0845-0849.
Abramson, “The Throughput of Packet Broadcasting Channels,” IEE Transactions on Communications, vol. COM-25, No. 1, 117-128, Jan. 1977.
Young, “USAP: A Unifying Dynamic Distributed Multichannel TDMA Slot Assignment Protocol,” Milcom 96 Conference Proceedings, pp. 235-239 1996 IEEE.
Asada et al., “Low Power Wireless Communication and Signal Processing Circuits for Distributed Microsensors,” Proceedings of 1997 IEEE International Symposium on Circuits and Systems, (The IEEE Circuits and Systems Society), 2817-2820, Jun. 9-12, 1997, Hong Kong.
Bult et al., “Low Power Systems for Wireless Microsensors,” 1996 International Symposium on Low Power Electronics and Design, pp. 17-21 (1996).
Ephremides et al., “A Design Concept for Reliable Mobile Radio Networks with Frequency Hopping Signaling,” Proceedings of the IEEE, 75(1):56-73, 1987.
Bult et al. “Wireless Integrated Microsensors,” Solid-State Sensor and Actuator Workshop, pp. 205-210, 1996.
Young, “A Unifying Dynamic Distributed Multichannel TDMA Slot Assignment Protocol,” Rockwell International, pp. 1-29 (1995).
Lin et al., “Wireless Integrated Network Sensors (WINS) for Tactical Information Systems,” Rockwell Science Center, Thousand Oaks, pp. 1-6, Jan. 1998.
Asada et al., “Wireless Integrated Network Sensors: Low Power Systems on a Chip,” , ESSCIRC '98, Proceedings of the 24th European Solid-State Circuits Conference, Sep. 22-24, 1998, pp. 9-16 (1998).
Vardhan et al., “WINS: Distributed in Situ Sensing for Mission and Flight Systems,” Aerospace Conference Proceedings, IEEE, 7:459-463, Mar. 18-25, 2000.
International Search Report for PCT/US00/27602 mailed Oct. 23, 2001.
International Search Report for PCT/US00/27601 mailed Oct. 23, 2001.
International Search Report for PCT/US00/27600 mailed Oct. 18, 2001.
W. Merrill, K. Sohrabi, L. Girod, J. Elson, F. Newburg & W. Kaiser, “Open Standard Development Platforms for Distributed Sensor Networks,” Proceedsings of SPIE, Unattended Ground Sensor Technologies and Applications IV, AeroSense 2002, vol. 4743, Apr. 2-5, 2002, Orlando, FL, pp. 327-337.
Patent number: 7904569
Inventors: David C. Gelvin (Escondido, CA), Lewis D. Girod (Los Angeles, CA), William J. Kaiser (Los Angeles, CA), Fredric Newberg (San Diego, CA), Gregory J. Pottie (Los Angeles, CA)
Application Number: 09/680,608
Current U.S. Class: Network Resources Access Controlling (709/229); Network Computer Configuring (709/220); Computer-to-computer Session/connection Establishing (709/227); Session/connection Parameter Setting (709/228); 701/29; 701/33