Methods and systems for establishing an interface with a vehicle data processing system via multiple data transport channels
The method and system address the challenge of interfacing diverse devices with a vehicle data processing system by implementing a general transport protocol for efficient and secure data exchange, allowing remote operation and enhanced user interaction.
Patent Information
- Application Number
- DE102011075066
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2010-05-27
- Filing Date
- 2011-05-02
- Publication Date
- 2024-11-28
- Estimated Expiration
- 2031-05-02
AI Technical Summary
Existing systems struggle to efficiently interface and operate applications installed on diverse devices with a vehicle data processing system due to the use of different communication protocols, limiting remote operation and functionality.
A method and system that employs a data processor to determine the communication protocols of multiple devices, imposing a general transport protocol for data exchange, enabling simultaneous or individual connections, and managing events like media streaming and diagnostics through a transport agnostic protocol, while ensuring secure resource access.
Enables seamless operation of applications across devices with varying protocols, facilitating remote control of vehicle systems and secure resource utilization, enhancing user interaction and functionality.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[0001] One or more embodiments relate to an interface for transmitting data between a number of devices and a vehicle data processing system. The devices can transmit data via various communication protocols. In certain embodiments, the devices can be wired or wireless.
[0002] In technology, there are various examples of tools that enable communication between multiple end devices via a communication network.
[0003] US 2007 / 0016362 A1, DE 102 54 284 A1, DE 10 2008 046 918 A1 and US 7,046,638 B1 disclose methods for connecting a vehicle's on-board network to external devices. These methods involve protocol conversion and, in US 7,046,638 B1, also the creation of a network-independent intermediate protocol.
[0004] U.S. Patent No. 7,602,782, owned by Doviak et al., discloses a device and method for intelligently routing data between a remote facility and a host system. More specifically, Doviak et al. ensure transparent communication between a remote or mobile facility and a fixed communications host network. A remote network controller, logically residing between the host network and the existing infrastructure(s), is used to establish communications network contact with one or more remote facilities. The remote network controller is connected to the host communications network as a protocol-compliant communications controller, making remote facilities indistinguishable from locally connected facilities to the host network.Each remote facility can be equipped with an asynchronous serial data interface to communicate with a mobile data controller. The mobile data controller, in combination with the remote network controller, ensures end-to-end data communication in such a way that incompatible protocols between the remote facility and the host communication network are transparent. A router can be provided that selects a communication network according to user-configured parameters. The router communicates across multiple incompatible networks and can use a variety of different protocols. Switching between these multiple incompatible networks is transparent to both the remote facility and the host communication network.
[0005] US patent application Publication No. 2006 / 0150197 for Werner discloses a connection between clients for managing the system. Werner discloses the creation of an instance of a program object for a client system, wherein the client system is of one computer platform type, and the program object is compatible with several different computer platform types. Werner further discloses connecting the instance of the program object to an interface of a server and managing an application on the server using the instance of the program object.
[0006] US patent application Publication No. 2006 / 0156315 for Wood et al. discloses a method, a computer-readable medium, and a device for providing a graphical user interface in a client-server environment. Specifically, Wood et al. disclose a client program in a client / server relationship that receives commands, thereby generating a specific implementation of graphical user interface components, and receives any data to be displayed in the interface components from the server program. As the end user interacts with the client, the client returns events and data to the server for processing. The commands and events constitute a protocol that is published via an API. The transmission of command events between the client and the server is achieved without linking the programs.The specific GUI implementation is specified by the server application and revealed to the client only at runtime.
[0007] One aspect comprises a method for establishing an interface between two or more devices and a vehicle data processing system. A request to connect to a vehicle data processing system can be received by the two or more devices, which transmit data using various communication protocols. These communication protocols may include, but are not limited to, Internet protocols, Bluetooth protocols, proprietary protocols, 802.11 protocols, and mass storage device protocols.
[0008] The connection, which may or may not be a simultaneous connection, can be established between the two or more devices based on the connection request. The procedure may further include determining the communication protocol of the two or more devices. A general transport protocol can be imposed on the communication protocol of the two or more devices for the transmission of data between them, based on their respective communication protocols. Data exchange can be achieved between the two or more devices based on the general transport protocol. The data may, but are not limited to, instructions for activating one or more application programs installed on the two or more devices, or instructions for executing the event based on one or more service types.Service types can include, but are not limited to, Remote Procedure Call, Bulk Transport, or Media Streaming.
[0009] The procedure may also include executing an event in the vehicle data processing system or the two or more devices based on the data.
[0010] In one embodiment, the general transport protocol can be transport-agnostic (transport-independent).
[0011] Another aspect can include a system that incorporates a data processor designed to connect to two or more devices. These two or more devices can communicate using different communication protocols. The data processor can further determine the protocol(s) of the two or more devices. A general protocol for transmitting data to the two or more devices can be imposed based on their respective communication protocols. Data can be transmitted to the device(s) to execute an event.
[0012] In a non-restrictive embodiment, the data processor can be a vehicle computer.
[0013] In certain embodiments, the two or more devices can be configured to listen for a connection request from the data processor. Furthermore, the two or more devices can be connected to the data processor simultaneously.
[0014] Another aspect involves a computer program product implemented in a computer-readable medium for establishing an interface between two or more devices and a vehicle data processing system. The computer program product may include instructions for establishing a connection (which may or may not be a simultaneous connection) with two or more devices transmitting data using different communication protocols. The communication protocol of the two or more devices can be determined, and a general transport protocol for transmitting data between the two or more devices can be imposed on them based on their respective communication protocols.
[0015] The computer program product may further include instructions for transmitting data based on the general transport protocol to execute an event based on the data. An event may, but is not limited to, the following: playing media files, performing vehicle diagnostics, audibly outputting one or more messages, acknowledging the existence of an application session, and executing location-based services.
[0016] In one embodiment, the computer program product may include instructions for receiving a request to connect to the vehicle data processing system from the two or more devices.
[0017] In certain embodiments, the data may include instructions for executing the event based on one or more service types, each with a predefined priority. The computer program may also include instructions for transporting the event instructions based on the service type priority. A service type may, but is not limited to, a remote procedure call, a bulk transport service, or a heartbeat.
[0018] These and other aspects will become more understandable with regard to the accompanying drawings and the following detailed description of the invention.
[0019] The figures identified below illustrate certain embodiments of the invention. The figures are not intended to limit the invention as defined in the appended claims. The embodiments, both in terms of their organization and operation, along with further tasks and advantages, can best be understood with reference to the following description in conjunction with the accompanying drawings. They show: Fig. 1 a block topology for a vehicle data processing system; Fig. 2 an exemplary system architecture that defines the communication interface between one or more remote terminal units and the vehicle data processing system of Fig. 1 exemplified; Fig. 3. A non-restrictive example of a data flow for generating one or more data packets for exchange through the communication interface of Fig. 2; Fig. 4 an exemplary operation for establishing a connection between one or more remote terminal devices and the vehicle data processing system; Fig. 5a and Fig. 5b Non-restrictive examples of data exchange scenarios between the number of remote terminals and the vehicle data processing system; Fig. 6. an aspect of the operation to generate a message for transmission; and Fig. 7. Operation for message transmission and exchange between the remote terminals and the vehicle data processing system.
[0020] Detailed embodiments of the invention are disclosed herein. It is understood, however, that the disclosed embodiments are merely exemplary of an invention that can be realized in various and alternative forms. The specific functional details disclosed herein are therefore not to be interpreted as limiting, but merely as a representative basis for the claims and / or as a representative basis for teaching those skilled in the art how to use the present invention in different ways.
[0021] Devices such as personal computers, handheld diagnostic tools, mobile phones, smartphones, personal digital assistants (PDAs), and the like may each employ various communication channels for transmitting data. Non-restrictive examples include cellular, Bluetooth, Wi-Fi, WiMAX, infrared (IF), radio frequency (RF), and the like. Certain devices, such as the iPhone manufactured by Apple Corporation, may transmit data using proprietary protocols.
[0022] Furthermore, applications or programs (hereinafter referred to as "applications") may be installed on these devices for use by a user of the device. These applications may serve a variety of purposes for the user, such as correspondence, entertainment, diagnostics, and social networking. A user typically operates these applications locally on the mobile device. Accordingly, these applications may be programmed with instructions for receiving input and operational commands from the local mobile device in order to operate the application(s).
[0023] In certain cases, however, a user can operate these applications remotely. For example, a user might operate these applications from a vehicle infotainment system. One example of such a vehicle infotainment system is SYNC from THE FORD MOTOR COMPANY. In such scenarios, the application(s) may be installed on the remote device, but the operation of the application(s) is performed by the vehicle's data processing system. However, the application(s) are generally not programmed to be operated by the remote device, such as the vehicle's data processing system. Thus, without any way to interface with the functionality and controls of the remote device, a user may not be able to access the functionality of these applications.
[0024] Fig.Figure 1 shows an exemplary block topology for a vehicle-based data processing system (VCS) 1 for a vehicle 31. It is understood that the arrangement of Fig. 1 (and the following Fig. 2-7) is not restrictive. The disclosure and arrangement of Fig. 1-7 can therefore be modified or rearranged to best fit a particular implementation of the various embodiments of the invention.
[0025] A vehicle equipped with an on-board data processing system may include a visual front-end interface 4 located within the vehicle. The user may also be able to interact with the interface, for example, if it is equipped with a touch-sensitive screen. In another exemplary embodiment, the interaction takes place through key presses, audible speech, and speech synthesis.
[0026] At the in Fig.In the exemplary embodiment shown in Figure 1, a processor 3 controls at least part of the operation of the vehicle-based data processing system. The processor is located in the vehicle and allows onboard processing of instructions and routines. Furthermore, the processor is connected to both non-persistent 5 and persistent memory 7. In this exemplary embodiment, the non-persistent memory is random access memory (RAM) and the persistent memory is a hard disk drive (HDD) or flash memory.
[0027] The processor is also equipped with a number of different inputs that allow the user to establish an interface with the processor. In this exemplary embodiment, a microphone 29, an auxiliary input 25 (for input 33), a USB input 23, a GPS input 24, and a BLUETOOTH input 15 are provided. An input selector 51 is also provided to allow the user to switch between different inputs. The input to both the microphone and the auxiliary input is converted from analog to digital by a converter 27 before being forwarded to the processor.
[0028] Outputs from the system can include, but are not limited to, a visual display 4 and a loudspeaker 13, or a stereo system output. The loudspeaker is connected to an amplifier 11 and receives its signal from the processor 3 via a digital-to-analog converter 9. Output can also be made to a remote BLUETOOTH device, such as the PND 54, or a USB device, such as the vehicle navigation device 60, along the bidirectional data streams shown at 19 and 21, respectively.
[0029] In one exemplary embodiment, the system 1 uses the BLUETOOTH transmitter / receiver 15 to communicate 17 with a user's nomadic device 53 (e.g., mobile phone, smartphone, PDA, etc.). The nomadic device can then be used, for example, to communicate 59 with a network 61 outside the vehicle 31 by communicating 55 with a cell tower 57. In certain embodiments, the tower 57 can be a WiFi access point.
[0030] The exemplary communication between the nomadic facility and the BLUETOOTH transmitter / receiver is represented by signal 14.
[0031] Pairing a nomadic device 53 and the BLUETOOTH transmitter / receiver 15 can be instructed by pressing a button 52 or similar input.
[0032] Accordingly, the CPU is instructed that the onboard Bluetooth transmitter / receiver will be paired with a Bluetooth transmitter / receiver in a nomadic setup.
[0033] Data can be transmitted between the CPU 3 and the network 61, for example, using a data plan, Data Over Voice, or DTMF tones associated with the nomadic device 53. Alternatively, it may be desirable to provide an onboard modem 63 with an antenna 18 to transmit data between the CPU 3 and the network 61 over the voice band 16. The nomadic device 53 can then be used, for example, to communicate with a network 61 outside the vehicle 31 59 via communication 55 with a cellular tower 57. In certain embodiments, the modem 63 can establish communication 20 with the tower 57 to communicate with the network 61. As a non-limiting example, the modem 63 can be a USB cellular modem, and the communication 20 can be cellular communication.
[0034] In one exemplary embodiment, the processor is equipped with an operating system that includes an API for communicating with modem application software. The modem application software can access an embedded module or firmware in the Bluetooth transmitter / receiver to establish wireless communication with a remote Bluetooth transmitter / receiver (such as one encountered in a nomadic setup).
[0035] In another embodiment, the nomadic device 53 includes a modem for voice-band or broadband data communication. In the data-over-voice embodiment, a technique known as frequency-division multiplexing can be implemented when the owner of the nomadic device can speak over the device while data is being transferred. At other times, when the owner is not using the device, the data transfer can use the entire bandwidth (300 Hz to 3.4 kHz in one example).
[0036] If the user has a data plan associated with the nomadic device, it is possible that the data plan allows broadband transmission and the system could use a significantly larger bandwidth (thereby accelerating data transfer). In another embodiment, the nomadic device 53 is replaced by a cellular communication device (e.g., but not limited to, a modem 63) installed in the vehicle 31. In yet another embodiment, the nomadic device 53 can be a wireless LAN device (LAN = local area network) that can communicate, for example, via an 802.11 network (including, but not limited to, Wi-Fi and WiMAX) and LTE (Long Term Evolution) networks.
[0037] In one embodiment, incoming data can be routed via a Data-Over-Voice or data plan through the nomadic device, through the onboard Bluetooth transmitter / receiver, and into the vehicle's internal processor 3. In the case of certain temporary data, the data can be stored, for example, on the HDD or another storage medium 7 until the data is no longer needed.
[0038] Additional sources that can be connected to the vehicle would be a personal navigation device 54, which, for example, has a USB connection 56 or an antenna 58, or a vehicle navigation device 60 with a USB 62 or other connection, an onboard GPS device 24 or remote navigation system (not shown) with connectivity to the network 61.
[0039] Furthermore, the CPU could be in communication with various other auxiliary devices 65. These devices can be connected via a wireless 67 or wired 69 connection. Alternatively, or in addition, the CPU could, for example, be connected to a vehicle-mounted wireless router 73 using a WiFi transmitter / receiver 71. This would allow the CPU to connect to remote networks within range of the local router 73.
[0040] Fig.Figure 2 shows a non-restrictive framework in which a user can establish an interface between several devices and a vehicle data processing system (VCS) 1. More specifically, the system 100 can allow a user to establish an interface between the applications 103a-f installed on the devices 102a-f and the VCS 1 for the operation of the applications 103a-f by the VCS 1. The operation of the applications 103a-f may, but is not limited to, the following: activating the applications 103a-f, inputting commands and instructions (via speech, keystrokes, etc.), and receiving outputs (e.g., visual, graphical, textual, audible, and other similar outputs).
[0041] It goes without saying, however, that the architecture of Fig.2 and the associated description are not restrictive. For example, and without restriction, the operation of applications 103a-f can additionally or alternatively be carried out by facilities 102a-f. For example, and without restriction, inputs, outputs, and commands can be performed at facility 102a-f.
[0042] Furthermore, it goes without saying that the various aspects relating to Fig. The embodiments described in section 2 can be used additionally or as an alternative for telematics support. As a non-restrictive example, the various embodiments can be used for exchanging vehicle integrity report data. As another non-restrictive example, the various embodiments can be used for exchanging licensing data for an application 103a-f. As a further non-restrictive example, the various embodiments can be used for remote door unlocking.
[0043] Now with reference to Fig. 2 there can be one or more facilities 102a-f that can establish an interface with the VCS 1. For the sake of presentation and clarity, Fig. 2, however, with several devices shown in 102a-f. Non-restrictive examples of such devices would be mobile phones, handheld diagnostic tools, personal computers, smartphones, personal digital assistants (PDAs), media devices (e.g., and without limitation, MP3 players), portable storage devices (e.g., and without limitation, USB thumb drives, memory cards / sticks, SLOTMUSIC cards, and other suitable storage devices) and / or adapters for receiving such storage devices, and other devices that may now or subsequently be known.
[0044] The applications 103a-f installed on the equipment 102a-f may be factory-installed on the equipment 102a-f or installed by a user after purchase of the equipment 102a-f. A user may, for example, and without limitation, install the application from a computer-readable medium (e.g., a CD or USB drive) or download the application from the Internet (e.g., from a third-party site). A user may, but without limitation, include: a consumer, a vehicle dealer (and persons employed by the dealer), or a service center (and persons employed by the service center). Non-restrictive examples of the applications 103a-f that may be installed on the equipment 102a-f include: vehicle diagnostic applications, communication applications (e.g., and without limitation, email, VoIP, and text messaging), entertainment applications (e.g.,and without restriction multimedia streaming, videos, music, games, etc.), social networking applications, location-based applications, personalized advertising applications, and others.
[0045] Each device 102a-f can transmit data through one or more communication channels using one or more communication protocols 104a-f. Non-restrictive examples of such communication protocols 104a-f would be the BLUETOOTH protocol, 802.11 protocols, TCP / IP, proprietary protocols (such as, without limitation, the iAP protocol of APPLE CORPORATION), mass storage protocols (e.g., USB protocols), USB-based networking protocols (e.g., and without limitation, USB-Serial or USB-RNDIS), and other protocols now known or hereafter discovered. It is understood that the devices 102a-f can transmit data using multiple communication protocols (e.g., and without limitation, BLUETOOTH and 802.11). This relationship between the VCS 1 and the devices 102a-f can be referred to as a network.In certain embodiments, the relationship between the devices 102a-f and the VCS 1 can generate an "ad-hoc" network. It is understood that, although the various embodiments are described with reference to communication with a data processing system in an automobile, there may be other environments in which the network can be implemented. Non-limiting examples of such environments include an apartment, an office, a school, an airplane, a train, a bus, and other similar settings.
[0046] Again with reference to Fig.2. With regard to BLUETOOTH-enabled devices, each device may also include one or more BLUETOOTH profiles that define which devices the BLUETOOTH-enabled device can communicate with. Profiles can be standard profiles (such as A2DP, HFP, SDAP, and HSP) or customized profiles. As a non-restrictive example, the BLUETOOTH-enabled device may include the SDAP profile to discover which services may be available on the VCS 1. In certain embodiments, the discovery process may be based on an SDAP record that has a universally unique identifier (UUID) registered for the SDAP profile.
[0047] The devices 102a-f can establish a connection with the VCS 1 using a communication channel described above. In one embodiment, the device 102a-f can listen for a connection request from the VCS 1. In other embodiments, the VCS 1 can listen for connection requests from the devices 102a-f. When a connection is established, a data transport manager 106 (which may or may not be implemented as software on the CPU 3 of the VCS 1) can receive the messages / data transmitted by the one or more applications 103a-f (via the device 102a-f) and process the messages / data for further transmission.
[0048] In certain embodiments, the device 102a-f can be connected to the VCS 1 simultaneously. In other embodiments, the device 102a-f can establish individual and separate (i.e., non-simultaneous) connections.
[0049] In one embodiment, the transport manager 106 can send this data to the security manager 108. Accordingly, the transport manager 106 can enable communication between the device 102a-f and the security manager 108. Further details of the security manager are described later. In certain embodiments, the transport manager can also communicate with a data manager (not shown), which can transmit the data to the security manager. The data manager can store system data available between applications in a database structure.
[0050] Non-restrictive examples of the tasks of the Transport Manager 106 would be abstracting (i.e., standardizing) the communication protocols 104a-f and forwarding the following non-restrictive information: data, transport state changes, discovered applications, and startup requests. The Transport Manager 106 can perform these tasks as the interface for connecting to a facility 102a-f with a given name over a given communication channel 104a-f. In particular, the Transport Manager 106 can send and / or receive data over an existing session. A session can be a logical connection between an application 103a-f on the facility 102a-f and the VCS 1. The Transport Manager can also feed notifications to the protocol module 105 (e.g., and without restriction, a connection to the device).In one embodiment, notifications can be identifying information that defines an event triggering the notification. Furthermore, the transport manager 106 can maintain various connection mappings, including a mapping between connections and all active sessions over a given connection, and a mapping between connections and corresponding communication channels 104a-f. A "connection" can be a connection between the transport layers of the facilities 102a-f and the VCS 1. Thus, the transport manager 106 can encapsulate transport-specific details from the communication channels 104a-f with the data transport protocol (described later). The transport manager 106 can also maintain information about the connected facility 102a-f (e.g., the facility name) and information about the communication channels 104a-f (e.g., the transport name).Accordingly, the transport manager can enable the exchange of user instructions between the applications 103a-f and the VCS 1 via any of the communication protocols 104a-f used to transmit data to / from the facility 102a-f.
[0051] As described above, the transport manager can enable the discovery of applications 103a-f and / or devices 102a-f. As a non-restrictive example, discovery can be achieved using zero-configuration networking. However, in certain implementations, discovery can be specific to each communication protocol 104a-f (e.g., and without restriction, using the SDP (Service Discovery Protocol) for Bluetooth devices).
[0052] In one embodiment, the data transport manager 106 can include a data transport plugin 107 implemented on the CPU 3. The data transport plugin 107 can be specified and manage the connection for each communication protocol 104a-f. For example, and without limitation, a plugin can exist for proprietary protocols, Bluetooth protocols, 802.11 protocols, and the like. In certain embodiments, the plugin 107 can be implemented as a Dynamic Link Library (DLL). Accordingly, capabilities for current and new communication channels 104a-f can be provided. The plugin 107 can be implemented by an OEM or by third-party developers (such as Wipro Technologies).
[0053] The data transport plugin 107 can provide an interface for connecting to a device 102a-f. In one embodiment, the plugin 107 can listen for incoming connections from the device 102a-f. The connection established by the plugin 107 can allow the sending and / or receiving of data over an existing connection (as defined above). The interface can be independent of the underlying communication transport protocol 104a-f. In certain embodiments, the plugin 107 can notify the transport manager 106 of events (e.g., and without limitation, a connection) based on information it receives. In one embodiment, notifications can include identifying information that defines the event. In other embodiments, the plugin 107 can buffer data received over a transport connection.
[0054] As described above, the Transport Manager 106 can send and / or receive data transmitted over an existing session (as defined above). In one embodiment, messages can be received / sent by a Protocol Module 105, which can communicate with the Transport Manager 106. The Protocol Module 105 can perform a number of tasks when enabling a user to operate the Applications 103a-f from the VCS 1. Some non-restrictive tasks would be: (1) initializing / deinitializing the Protocol Module, (2) starting / ending a session (defined above) over a given connection (defined above), (3) adding / removing new and existing services (defined below), and (4) sending / receiving data over an existing session (defined above). In one embodiment, the Protocol Module 105 can also provide notifications.These notifications can be triggered when the protocol module 105 (e.g., from the transport manager 106) receives a data packet.
[0055] Protocol module 105 can determine the type of service requested by applications 103a-f. A service can be a heartbeat (HB), a remote procedure call (RPC), or a bulk service. Other non-restrictive services can include media streaming, use of application-specific transport protocols (e.g., applications may have domain-specific protocols), use of other protocols (such as HTTP, FTP, IRC, SOAP, and IMAP), and other suitable service types. More generally, a service can specify the type of action that an application 103a-f can request. In one embodiment, each service type can be queued in protocol module 105 and sent according to a transmission pattern. In a non-restrictive example, this transmission pattern can be a first-in-first-out (FIFO) transmission pattern.
[0056] Additionally or alternatively, protocol module 105 can assign a priority to each service type. A service type with a higher priority can thus be sent before a service type with a lower priority. As a non-restrictive example, a heartbeat service could have the lowest priority, an RPC an intermediate priority, and a bulk transfer the highest priority. It is understood that other priority schemes can be used without compromising the scope of protection and the underlying principles of the various implementations.
[0057] In one embodiment, the protocol module 105 can alternatively or additionally periodically send and / or listen for heartbeat messages for each active session. When listening for heartbeat messages (e.g., from devices 102a-f), the protocol module 105 can listen for a heartbeat for a predetermined period and / or a predetermined number of times. If no heartbeat is received, the protocol module 105 can close the session and send a status notification to the application 103a-f. Furthermore, each heartbeat can span a predetermined period (e.g., 5 seconds, without limitation).
[0058] Protocol module 105 can also segment messages that exceed a certain payload threshold. Transport plugin 107 may have a limit on the amount of payload it can receive. This can be referred to as the maximum transmission unit (MTU). Accordingly, protocol 105 can segment the incoming message and send the messages in segmented form to comply with the MTU rules of the transport plugin. On the return journey, protocol module 105 can also reassemble the segmented messages before sending a message to application 103a-f. In one embodiment, application 103a-f can only receive reassembled messages. Segmentation can also ensure increased performance of system 100 by providing data nesting. In certain embodiments, there may be a limit on the number of nested interactions. Fig. 5A and Fig. 5B shows non-restrictive examples of unsegmented data exchange ( Fig. 5A) and a segmented data exchange ( Fig. 5B).
[0059] The protocol can be divided into two layers (e.g., a higher layer and a lower layer). A higher layer can contain the function calls required to achieve facility communication and system control flow. A lower layer can provide the basic communication functions. This lower layer can be agnostic with respect to hardware and system details.
[0060] Further details of the interaction between the various components of System 100 will be given with reference to Fig.3 described. As described above, the one or more messages (or data packets) received by the application 103a-f (as represented by arrow 200) can be sent according to a data transport protocol. This data transport protocol can be "transport-agnostic." In this way, the data transport protocol can be a dynamic protocol, so that it can support extensibility without significant (or any) changes to its architecture. Instructions (i.e., data) from the applications 103a-f can thus be transported via the data transport protocol, regardless of which of the communication protocols 104a-f (i.e., both current and future communication protocols) the facility 102a-f uses to transport data.
[0061] For example, and without restriction, one facility can run the application 103a-f using BLUETOOTH (e.g., using the RFComm (Radio Frequency Communication) and L2CAP (Logical Link Control and Adaptation) protocols), while another facility can run the application 103a-f using a proprietary protocol (such as Apple's iAP). The data transport protocol allows the applications to run on the respective facilities 102a-f from the VCS 1 regardless of the data communication channel 103a-f used by each facility. From a user's perspective, the application can be used seamlessly on any facility 102a-f. From the perspective of a developer of the application 103a-f, the application does not need to be individually developed based on the different communication protocols 104a-f.
[0062] Furthermore, the data transport protocol 200 can be bandwidth- and latency-neutral. Thus, in this embodiment, the protocol makes no assumptions regarding the speed of the data connection or latency delays from the applications 104a-f. In certain embodiments, a lowest common denominator of the communication channels 104a-f can determine the interaction. The lowest common denominator can be relative. For example, BLUETOOTH is limited to approximately 700 kbps throughput, compared to WiFi, which can achieve approximately 10-20 mbs throughput.
[0063] In one embodiment, the data transport protocol may include generic commands. In such an embodiment, no specific functionality for interacting with the VCS 1 (such as VCS 1-specific commands) may be programmed into the protocol. Instead, general data transport abstractions between the VCS 1 and the application 103a-f may be provided.
[0064] As in Fig. As shown in Figure 3, certain aspects of data exchange can be unidirectional (as represented, for example, by data flow arrow 208). Additionally, or alternatively, certain aspects can be bidirectional (as represented, for example, by data flow arrow 200). However, it is understood that the disclosure and arrangement of Fig. 3 can be modified or rearranged to best fit a particular implementation of the various embodiments of the invention.
[0065] Application 103a-f can send an application identifier (“AppID”), session information (“Session”), a service type (“ServType”), and application data (arrow 200). Application data can include, but is not limited to, user instructions / requests (e.g., and without limitation, the correlation ID for binding a request to a response, commands to be executed, events to be fired, and status return codes) and application scripts (e.g., and without limitation, including the boundaries that define which resources of VCS 1 the application 103a-f is permitted to use). Application data can also include icons, sound files, and graphics. From the vehicle's perspective, application data can include, but is not limited to, sound captures and vehicle diagnostic captures.It is understood that the structure of the application data is open and non-restrictive, so that it can be added to and modified in other ways.
[0066] The ApplD can be a unique ID associated with an application 103a-f. In certain implementations, it can be a numeric ID, a user-friendly description, a symbol, and the like. The ApplD can define that the applications 103a-f are operable with the VCS 1. Furthermore, once a session is established, the ApplD can be used to identify the applications 103a-f to the user in the vehicle (e.g., on display 4).
[0067] Certain of this data may be included in the data transport protocol. For example, and without limitation, the service type (e.g., RPC or Bulk) may comprise at least one byte of the data protocol. Additionally, a session ID (which identifies the session) may comprise one or more bytes of the data protocol. Data from applications 103a-f may be sent upon activation or during the operation of applications 103a-f. Table 1 below provides definitions for this data.
[0068] Additional content of the data transport protocol can include: a frame type (e.g., and without limitation, a control frame, single frame, first frame, or successive frame), frame data (which may be based on the frame type), a protocol version number, a compression flag (i.e., the presence of compressed data), an algorithm used for compression, and the data size (which may be based on the frame type). Each of these data elements can comprise one or more bytes of the data transport protocol.
[0069] As in Fig.As further shown in Figure 3, other data can be exchanged between applications 103a-f and the transport plug-in 107. Various commands can be sent from applications 103a-f to the transport manager 106. Non-exhaustive examples of some of these commands are given in Table 1. The ApplD (which may or may not be contained in a separate data packet), a protocol header for the data transport protocol, and application data (e.g., user instructions / requests, application scripts, etc.) can also be sent to the transport manager 106 (data flow arrow 202). The same information can be returned to the data transport protocol module 105 (e.g., if the operation was performed in VCS1) (data flow arrow 202).
[0070] The transport manager can also submit transport properties to the protocol module 105 (data flow arrow 214). Optionally, a transport status can be received from the transport plugin 107 (data flow arrow 216) and sent to the protocol module (data flow arrow 212). The transport properties and transport status are described in Table 1. The transport manager 106 can also send the protocol header (PH) and application data to and from the transport plugin 107 (data flow arrow 204). The transport plugin 107 can generate a transport header (TH) and send it with the PH and application data (data flow arrow 206). In one embodiment, the TH can be an optional header that holds excess data that the data transport protocol cannot hold. Data can be considered excess based on data size requirements prescribed by the underlying communication protocol 104a-f.This data can be sent to the security manager 108. Table 1 Data / Tax Information Definition / Description ApplD Application ID: A parameter that uniquely identifies an application within a given institution. Session ID An ID to identify a logical connection between applications on facilities 102a-f and VCS 1 ServType Service type: e.g., and without restriction, Remote Procedure Call (RPC), Bulk, Media Streaming, use of application-specific transports, use of other transports (such as HTTP), and other suitable service types. Transport properties Information regarding the transport plugin (e.g., and without limitation, transport plugin name) Transport status Includes information about the transport status (e.g., initialized / deinitialized, connected / disconnected, and errors). commands Data transport commands, including but not limited to initializing / deinitializing, connecting / disconnecting, and sending messages PH Data Transport Protocol Header TH Transportation header: information added by the transportation plugin
[0071] Again with reference to Fig. 2. The security manager 108 can receive data from the transport manager 106 to ensure that application-specific policies and / or default security policies are enforced. In this way, applications 103a-f cannot gain greater access to the resources of VCS 1 than they require. Furthermore, based on the security policies of the security manager 108, each application can be restricted to operating within its allocation parameters. In one embodiment, security policy enforcement can be considered a sandbox environment.
[0072] For example, if a user requests to run a music program (e.g., PANDORA) from a facility 102a-f, the security manager 108 can determine the usage restrictions (i.e., limits) with respect to the music program's VCS resources based on the computer-readable instructions (e.g., application scripts) from the application 103a-f. More specifically, the restrictions can stipulate that the music program may have access to graphics and audio, but not to vehicle diagnostics. Accordingly, the restrictions can be based on the specific function of the application.
[0073] Accordingly, the security manager (108) can determine which resources are requested by an application (103a-f) and block access to other resources. Furthermore, they can evaluate the policies defined for each incoming request from an application (103a-f) to further restrict its access to the resource to which it already has access.
[0074] In one embodiment, access to the resources of the VCS 1 (e.g., vehicle control units 112 and vehicle modules 114) can be achieved through application programming interfaces (APIs) 110 installed on the VCS 1. These APIs can be developed by the vehicle OEM. In one embodiment, the APIs can be programmed as DLLs in the C or C++ programming languages. Furthermore, each API can have its own set of security parameters, enabling them to enforce unique policy restrictions.
[0075] Non-restrictive examples of vehicle controls 112 can include text-to-speech (TTS) functionality, speech-to-text (STT) functionality, voice controls, button controls (e.g., steering wheel button controls and / or center console button controls), and touchscreen button controls. Operation on one or more vehicle modules 114 can be achieved in response to the use of one or more vehicle controls 112. Data can be transmitted via the communication link 115 between the vehicle controls 112 and the vehicle modules 115. In one embodiment, the communication link can be a vehicle network 115. Non-restrictive examples of vehicle modules 114 would be power transmission control modules (PCMs), body control modules (BCMs), ABS control modules, and the like.In additional alternative embodiments, data for audible, textual and / or graphical output can be sent to other vehicle modules 114. These may include, but are not limited to, one or more displays (including, but not limited to, the display 4, cluster screen displays (not shown) or rear entertainment displays (not shown), loudspeakers 13 or other similar output modules in the vehicle 31).
[0076] The APIs can be OEM-developed, third-party-developed, and / or open APIs. Open APIs, as is known in the technology, are APIs that allow interconnectivity between websites (e.g., social networking sites). Non-restrictive examples of APIs and their non-restrictive functions that can be installed on the VCS 1 are listed in Table 2 below. Table 2 API Description / Function Vehicle dialogue Dialogue through the vehicle network interface layer; dialogue with the vehicle network (e.g., CAN); diagnostic systems, GPS; timers; personalization. Advertisement Menu dialog; graphical widget dialog; dialog with buttons; access to display properties. Audio Dialogue with a text-to-speech (TTS) engine; dialogue with a speech recognition module; access to microphone audio stream; digital audio playback; audio file push for playback. VCS system administration Event registration and notification facilities; internal database access to transient and persistent data (e.g., media and telephone databases); to system status and application status information. System administration Extensions to provide functionality for various features of the VCS; language selection and internationalization; system configuration parameters; access to flash and external file systems. Networking Default socket access, network access; events related to network availability
[0077] Fig. Figure 4 is a block diagram of the dialogue between facilities 102a-f and the VCS 1, enabling applications 103a-f to be operated from the VCS 1. Communication between facilities 102a-f and the VCS 1 can take place via any communication channels known now or later. For the sake of illustration and clarity, Figure 4 shows... Fig. 4. However, one device communicating via BLUETOOTH 301a, one device communicating via USB 301b, and one device communicating via WiFi 301c. Furthermore, it is understood that communication can take place between one or more devices.
[0078] As described above, in one embodiment this dialogue can take place in an ad-hoc network environment. Devices 103a-f can search for devices to connect to (Block 300). In this case, the device can search for VCS 1. The search can be specific to the communication channel 104a-f of device 102a-f. For example, and without limitation, a Bluetooth device can search for the name of VCS 1 (e.g., "SYNC") on the Bluetooth network. This can be done during the pairing process. As another example, a WiFi-enabled device can search for a predefined Internet Protocol (IP) address. Device 102a-f can send a connection request (Block 304) to VCS 1. VCS 1 can wait for the connection request from device 102a-f (Block 302).
[0079] Alternatively, the VCS 1 can search for devices 102a-f to establish a connection. In this embodiment, the devices 102a-f can listen for a connection request from the VCS 1.
[0080] Data can be exchanged over the established connection. The channel over which the connection request is sent can depend on the communication channel 104a-f used by the device 102a-f. As a non-restrictive example, a BLUETOOTH device can publish an SDP record for an SPP channel over which data is to be transmitted. As another non-restrictive example, a WiFi device can send the connection request (block 304) to a specific port from which the VCS 1 can listen for the incoming connection request and over which the data can be transmitted after the connection is established.
[0081] Once a connection is established, a session (i.e., an application-level connection) can begin in facility 102a-f (block 306). VCS 1 can wait for the session request (block 308) and accept the session (block 310). A session can then be created. Furthermore, VCS 1 can initiate a new service type for dialoging with the application via the session. In one embodiment, multiple sessions can be multiplexed over the same facility-level connection.
[0082] As shown in blocks 312 and 314, respectively, the application 103a-f and the VCS 1 can exchange capabilities. These capabilities can define the resources that the VCS 1 can allow the application 103a-f to use. From the application's perspective, the capabilities can define the general capabilities of the application 103a-f. As a non-restrictive example, the capabilities that can be exchanged from the VCS 1 might include language support, display type, and GPS support. Other non-restrictive examples would be capabilities for specific functionality and a version level of the VCS 1. Non-restrictive examples of capabilities that can be exchanged by the application 103a-f might include the ability to support GPS, vehicle data, and media applications. Application capabilities can also include the version of the VCS 1 that supports them.In one embodiment, the VCS 1 can also publish its capabilities to other facilities 102a-f that may be located in the network (Block 316).
[0083] Device 102a-f and VCS 1 can send and receive data (Block 318 and Block 320). Data can be exchanged between Device 102a-f and VCS 1 as RPCs or bulk data. It is understood that the method of data exchange described is an example and other methods of data exchange may be used without deviating from the concept and scope of protection of the various embodiments.
[0084] As shown in blocks 322 and 324, respectively, facility 102a-f and VCS 1 can close or terminate a session. The session(s) can be terminated at any time during the data exchange process.
[0085] Fig.Figure 6 shows an operation for generating and sending a data packet for transport using the data transport protocol after a connection and session have been established. In block 400, the application 103a-f can send a request to operate the application. The request can be received in VCS 1. Furthermore, the communication channel 104a-f, over which the session was established, can be received (block 402). As shown in block 404, it can be determined whether the payload is larger than the MTU. If so, the data can be segmented (block 406) and the segmented data message reassembled (block 408). If not, an unsegmented data message can be reassembled (block 410).
[0086] In block 412, the message can be added to a queue corresponding to the service type identified from the message sent by application 103a-f. In one embodiment, a session heartbeat timer can be triggered or activated to check that an active session exists (block 414). As shown in block 416, the session status can be returned based on the heartbeat.
[0087] Fig.Figure 7 shows a non-restrictive operation of the priority scheme used by the data transport protocol to determine which service type is given priority. At block 500, the service (or task) to be executed is received from facility 102a-f based on user instructions. The service can be received from application 103a-f based on messages / instructions. The priority value(s) can be defined in the data transport protocol (block 502). The priorities can be pre-programmed into the data transport protocol. For example, the priority values can define which service is given maximum priority, intermediate priority, and lowest priority. As another non-restrictive example, the priority value can define a single priority value or a group of possible priority values (e.g.,(which service is given maximum priority and which service is given the lowest priority).
[0088] As shown in block 504, it can be determined whether a queue exists for any of the services. Each service can have its own queue. In other embodiments, the different services can be placed together in one queue (e.g., the RPC and Bulk services can be in the same queue). If the queue is empty, a further determination can be made as to whether any services exist (block 506).
[0089] If so, the next highest-priority service is examined to determine the status of its queue (Block 514). The service queue status can then be determined (Block 504). If no other service exists, the process can be suspended (Block 510).
[0090] When a service is added to the queue, the message can be received from the queue (Block 508). In one embodiment, the retrieval can be done on a FIFO (first-in, first-out) basis. After the message is retrieved, it can be sent (Block 512). As a non-restrictive example of this priority scheme, multiple HB (Hardware Bus) and / or one RPC (Request for Processing) message can be sent while a bulk transport file is in process.
[0091] Although exemplary embodiments have been presented and described above, it is not intended that these embodiments represent and describe all possibilities. Instead, the words used in the description are not words of limitation, but of description, and it is understood that various modifications can be made without deviating from the concept and scope of protection of the invention.
Claims
[1] A method for establishing an interface between two or more devices and a vehicle data processing system, comprising the following steps: Receiving a request from two or more devices to connect to a vehicle computing system, wherein the two or more devices transmit data using different communication protocols; Establishing a connection with the two or more devices based on the connection request; Determining the communication protocol of the two or more devices; using a common transport protocol in a computer-readable medium to transmit data with the two or more devices based on the respective communication protocols to the communication protocol of the two or more devices; Transmitting data with the two or more devices based on the common transport protocol; and Executing an event in the vehicle computing system or the two or more devices based on the data. [2] The method of claim 1, wherein the connection is a simultaneous connection. [3] The method of claim 1, wherein the common transport protocol is transport-independent with respect to the communication protocols of the two or more devices. [4] The method of claim 3, wherein the communication protocols are selected from the group consisting of Internet protocols, BLUETOOTH protocols, proprietary protocols, 802.11 protocols, and mass storage device protocols. [5] The method of claim 1, wherein the data comprises instructions for operating one or more application programs installed on the two or more devices. [6] The method of claim 5, further comprising: Receiving application session information over the connection; Establish one or more application sessions over the connection based on the application session information. [7] The method of claim 6, wherein multiple application sessions are multiplexed over the connection. [8] The method of claim 1, wherein the data comprises instructions for executing the event based on the one or more service types. [9] The method of claim 8, wherein the service type is a remote procedure call. [10] The method of claim 8, wherein the service type is a bulk transport service. [11] The method of claim 8, wherein the service type is media streaming.
Citation Information
Patent Citations
Connection of clients for management of systems
US20060150197A1
Method, computer-readable medium and apparatus for providing a graphical user interface in a client-server environment
US20060156315A1
Apparatus and method for intelligent routing of data between a remote device and a host system
US7602782B2
Method and device for realizing a mobile server
DE102008046918A1
Method and device for a vehicle-related telematics service
DE10254284A1
