DE102010029929A1 - Method for transmitting data and vehicle - Google Patents

Abstract

A method for the transmission of data is specified in which the data is transmitted in encrypted form from a vehicle to a mobile device; in which the mobile device requests access rights from a content provider; in which the content provider checks an authorization of the mobile device at a central communication unit and, if the authorization is given, transmits the access rights to the mobile device. Furthermore, a vehicle is proposed, comprising a database in which data, in particular multimedia data, can be stored; an encryption unit for encrypting the data; a connection agent, with the aid of which the encrypted data can be transmitted to a mobile device via a first interface.

Description

The invention relates to a method for transmitting data and a vehicle.

In the automotive environment, digital rights management of multimedia data is not yet supported. So z. B. by digital rights (DRM: Digital Rights Management) protected music from a car radio not recognized and thus not be played.

This situation significantly restricts users. Particularly due to the increasing interconnectedness, there is a need of the user to be able to retrieve his files as quickly as possible at any time and at any device. For example, the user does not want to use multimedia content offered via a vehicle, not only in the vehicle. However, a transfer to other devices and use of the protected content is not possible.

The object of the invention is to obviate the above-mentioned drawbacks and, more particularly, to provide a way to provide rights-laden contents loaded in a vehicle to a user taking into account the interests of the content providers.

This object is achieved according to the features of the independent claims. Further developments of the invention will become apparent from the dependent claims.

• – bei dem die Daten verschlüsselt von einem Fahrzeug an ein mobiles Gerät übertragen werden;
• – bei dem das mobile Gerät Zugriffsrechte bei einem Inhaltsanbieter anfordert;
• – bei dem der Inhaltsanbieter eine Berechtigung des mobilen Geräts bei einer zentralen Kommunikationseinheit prüft und bei gegebener Berechtigung die Zugriffsrechte dem mobilen Gerät übermittelt.

To solve the problem, a method is given for transmitting data,

• - in which the data is transmitted encrypted from a vehicle to a mobile device;
• - in which the mobile device requests access rights to a content provider;
• - In which the content provider checks an authorization of the mobile device in a central communication unit and transmits the access rights to the mobile device for a given authorization.

It should be noted that the transmission of the encrypted data before, during or after the request for access rights for the encrypted data can be made at the content provider. Thus, the access rights can also be requested first and then the transmission of the encrypted data can take place or be completed.

In this sense, a mobile device can be any device that can be connected to the vehicle via a wireless or wired interface and, in particular, is set up to receive the data and to use it if authorization is available.

The access rights may in particular be key data (eg symmetric or asymmetric keys). It is also possible that the access rights are valid for a limited time, ie. H. only work for a certain period of time. In particular, the access rights (keys) can be changed.

An advantage of this solution is that the content provider can administer the allocation of rights with little effort by accessing the central communication unit. The content provider does not need to communicate with each vehicle, nor does it need to worry about domain management.

The central communication unit is preferably a backend of the vehicle manufacturer or a corresponding service provider. The backend includes z. B. a computer network with communication links (eg., Via a mobile network) to the vehicles. In that regard, the information from the vehicles can be collected centrally via the backend. This enables the above-mentioned efficient domain management via the central communication unit.

With the access rights, the mobile device can decrypt the encrypted data transmitted by the vehicle and z. B. represent their content or play.

Thus, it is an advantage that the vehicle can also be used for forwarding data, with the rights of the content providers being taken into account accordingly. The sharing process by the content providers is efficiently realized via the central communication unit providing the central domain management service to a plurality of vehicles. The content provider can control the assignment of rights via this interface.

A development is that the data include audio and / or video data, programs or image data.

In principle, any data, in particular those data which are provided with rights, can be provided or loaded and released via the mechanism described here.

Another development is that the data is loaded from the vehicle or transmitted to the vehicle.

The vehicle can load or receive data with rights via various interfaces (wireless or wired). These data may be forwarded to the mobile device according to the approach described herein.

In particular, it is a development that the data is encrypted by the vehicle.

In particular, a symmetric or an asymmetric encryption method (comprising a public and a private key) can be used for encryption.

It is also a development that an address information is transmitted together with the encrypted data to the mobile device.

In particular, domain information or domain identifier with the encrypted data may be transmitted from the vehicle to the mobile device. The address information may be, for example, any address, eg. As an Internet address act.

Furthermore, it is a development that is addressed based on the address information of the content providers.

For example, the content provider can be addressed directly from the mobile device by means of a URL (Uniform Resource Locator).

Within the scope of an additional development, the mobile device transmits domain information and / or identification of the mobile device to the content provider and from the content provider to the central communication unit.

For example, the mobile device has been informed of the domain by the vehicle or has received such information upon logging on to the vehicle. This domain information, the mobile device together with its own identification (ID) z. B. unencrypted communicate the central communication unit.

A next development is that the authorization of the mobile device is checked on the basis of the domain information and / or the identification of the mobile device by the central communication unit.

The result of this check is communicated to the content provider, who then forwards the access rights to the mobile device or, if the check was unsuccessful, accordingly does not transmit any access rights to the mobile device.

One embodiment is that the vehicle transmits a change of a domain to the central communication unit.

In particular, a so-called PUSH service can be used for this purpose; B. a change in the domain associated mobile devices, a corresponding message to the central communication unit. This ensures that the central communication unit is promptly informed about the status of the respective domains.

• – eine Datenbank, in der Daten, insbesondere multimediale Daten, abspeicherbar sind;
• – eine Verschlüsselungseinheit zur Verschlüsselung der Daten;
• – einen Verbindungsagenten, anhand dessen die verschlüsselten Daten über eine erste Schnittstelle an ein mobiles Gerät übertragbar sind.

Also, the above object is achieved by a vehicle comprising

• - a database in which data, in particular multimedia data, can be stored;
• An encryption unit for encrypting the data;
• A connection agent, by means of which the encrypted data can be transmitted via a first interface to a mobile device.

A further development is that the vehicle has a second interface, via which the connection agent can be connected to a central communication unit, domain information being transferable via the second interface.

It is also a development that an input unit is provided, based on which the domain information is editable.

In particular, the domain information may be changed, e.g. For example, mobile devices can be recreated, modified or deleted.

An alternative embodiment is that the data can be loaded via the second interface.

In particular, the vehicle may have a further (third) interface, on the basis of which data z. B. be transmitted by wire in the vehicle. Also, the vehicle may, for example, record radio and / or television broadcasts for later (encrypted) transmission to the mobile terminal.

Preferably, with the recorded or transmitted data, an address information (partner data) is stored in the vehicle, which indicate at which content provider, the mobile device can make a request for the rights release or how the mobile device can reach such a service provider.

• – mit einem Domänen-Manager, der mit dem Verbindungsagenten des Fahrzeugs über die zweite Schnittstelle verbindbar ist;
• – mit einer dritten Schnittstelle, über die anhand des Domänen-Managers eine Berechtigungsinformation bereitstellbar ist.

The above object is also achieved by a central communication unit for communication with a vehicle as described herein

• With a domain manager connectable to the vehicle's connection agent via the second interface;
• - With a third interface over the basis of the domain manager authorization information is available.

In particular, the authorization information is provided to at least one content provider.

A further development is that the authorization information comprises authorization of a mobile device for a specific domain or a lack of authorization of this mobile device in this domain.

Embodiments of the invention are illustrated and explained below with reference to the drawings.

Show it:

1 a schematic block diagram illustrating the process of rights transfer.

2 a schematic diagram concerning the architecture of the in 1 components involved in the communication.

Digital rights management may allow a vehicle manufacturer and a vehicle managed by the vehicle manufacturer or service provider to control who uses which content and how the content is used. The contents mentioned herein are data, in particular multimedia data, audio data, video data with audio data (AV data), programs, etc. These data can enter the vehicle in different ways, for example via a radio interface (of a mobile radio network or a WLAN) from the vehicle z. B. be requested from the Internet and downloaded. It is also possible to transmit the data to the vehicle via a wired or wireless interface. So far, the vehicle served as information sink, d. H. the loaded or transmitted contents or data remain in the vehicle and are not for redistribution z. B. on mobile devices of users available. The solution proposed here allows redistribution, while preserving the rights of content providers to their data.

It should be noted that the proposed solution does not require support for DRM protected content.

It is proposed an in-vehicle encryption component, the z. For example, DRM-free content is encrypted for transfer to external devices and provides the user with the opportunity to obtain the respective usage rights from the content owners.

Thus, it is possible to leave a rights management and rights exhibition centrally with the respective content providers and z. For example, to provide centralized domain management in a back end of the vehicle manufacturer or service provider. In particular, it is possible for the vehicle manufacturer or the service provider providing the communication interface with the vehicle to cooperate with the content provider whose DRM system does not provide domain functionality.

The domain includes z. As a vehicle and registered for the vehicle (mobile) devices. The mobile device may be a mobile phone, a personal digital assistant (PDA), a portable computer (laptop, etc.), or any device that may also be used to communicate with the vehicle. The communication with the vehicle preferably takes place via a wireless interface (eg WLAN, Bluetooth, near field communication (NDC), mobile radio) or via a wired interface (eg an Ethernet interface, a USB interface, etc.). , Preferably, the mobile device also includes a mobile radio interface for communicating with the content provider.

For example, rights files may be protected with a public key of the requesting (eg, mobile) device. Alternatively, asymmetric encryption methods can be used comprising a public and a private key for the communication partners involved

1 shows a schematic block diagram illustrating the process of rights transfer.

A mobile device 101 , z. As a mobile computer, a mobile phone, a smartphone or a PDA, authenticated in a step (1) z. B. via a radio interface in a vehicle 102 , Authentication requests content in step (2). The vehicle 102 in a step (3) transmits encrypted content, e.g. B. multimedia data to the mobile device 101 ,

To get the encrypted content on the mobile device 101 to use, requires the mobile device 101 the appropriate rights. These rights become available to a content provider in a step (4) 103 requested. The content provider 103 transfers to a step (5) a request to a backend 104 to clarify whether the mobile device 101 and / or the vehicle 102 belong to a specified domain or whether the mobile device 101 is entitled to play the content.

It should be noted that in step (4) the content provider 103 the domain can be communicated. Alternatively, it is possible to check if the vehicle 102 and the mobile device 101 belong to the same domain. In this case, in the step (4), information for identifying the vehicle and other information for identifying the mobile device 101 be transmitted.

The backend 104 determines the answer to the request according to the step (5) and transmits it to the content provider in a step (6) 103 who may have the rights to the mobile device 101 in a step (7) passes.

It should also be noted that the communication of steps (1), (2) and (3) via a WLAN or a Bluetooth connection between the mobile device 101 and the vehicle 102 and the communication of steps (4) and (7) via a mobile radio connection (eg 2G, 3G, LTE, etc.) between the mobile device 101 and the content provider 103 can be done.

It should also be noted that the backend can be at least one computer, in particular a computer network, a vehicle manufacturer or a service provider. Via the backend, data relating to a large number of vehicles and possibly a large number of (for example, registered) mobile devices can be centrally managed. In particular, the backend may have a communication link with the vehicle, e.g. B. via a mobile radio interface. For example, the vehicle may have its own mobile radio interface, so that the vehicle can contact the backend or vice versa, the vehicle can be contacted by the backend.

2 shows a schematic diagram relating to the architecture of the in 1 components involved in the communication. As 1 also shows 2 the mobile device 101 , the vehicle 102 , the content provider 103 and the backend 104 ,

The mobile device 101 Can connect to a connection agent 201 of the vehicle 102 build up. The connection agent 201 can via a database 202 determine which mobile devices are authorized to connect. The mobile device 101 can at the connection agent 201 Request content or contents from the connection agent 201 receive.

The connection agent 201 manages the connected mobile devices and serves as a mediator for requests from the mobile devices.

Furthermore, in the vehicle 102 stored a symmetric key (secure). This symmetric key is the content provider 103 known and can be changed if necessary. The vehicle 102 also has an encryption unit 203 on that with a database 205 and a database 206 connected is.

In the database 205 are unencrypted (DRM-free) content stored. In the database 206 Partner data are stored, including z. As access information, links (URL, Uniform Resource Locator) or provider identification information.

The connection agent 201 is with the encryption unit 203 connected. The encryption unit 203 encrypted using the symmetric key locally in the database 205 stored content and places it (eg packed as archive) for download via the connection agent 201 the mobile device 101 preferably together with the partner data associated with the content.

Further manages (changes, adds, deletes) the connection agent 201 the partner data of the database 206 ,

Thus, the mobile device receives 101 the contents encoded with the symmetric key together with the partner data, e.g. B. an address information regarding the content provider 103 , This partner data is used by the mobile device to be the content provider 103 to address (eg via a URL) and from this content provider 103 to gain the rights to access the loaded (and still encrypted) content. For this purpose, an identification (ID) of the mobile device 101 and domain information provided by the vehicle together with the encrypted contents from the mobile device 101 to the content provider 103 transmitted.

The content provider 103 Checks if the mobile device 101 in the domain (identifiable by the transmitted domain information) has the necessary access rights and may use the already downloaded content.

For this, the content provider submits 103 a request to the backend 104 , especially a domain manager 207 the backend 104 , The domain manager 207 can on domain data 208 and on a "black list" 209 access. The domain data 208 include domain identifications (e.g., domain ID), owner information, and / or Device information. The "black list" 209 may be implemented as a database comprising identities of mobile devices that are not authorized to access. The device identifications stored in the "black list" can be blocked globally (eg for all domains) or domain-related (eg only for a specific domain).

For example, the domain is at least one mobile device registered to a vehicle. Accordingly, multiple mobile devices may be registered for a vehicle and thus belong to a domain. In addition, it should be noted that a mobile device for multiple domains (ie for multiple vehicles) may be registered.

The request from the content provider 103 to the domain manager 207 is checked by determining whether the transmitted identification of the mobile device matches the transmitted domain information, that is, whether the mobile device is part of the specified domain. This review may be based on the databases 208 . 209 be performed. The result of the review is shared by the domain manager 207 the content provider 103 With.

It should be noted that the communication between the content provider 103 and the backend 104 z. B. via the Internet can be done. The interface between the content provider 103 and the backend 104 may include at least one wired and / or at least one wireless connection.

In this case, it is advantageous that the domain functionality belongs to the content provider 103 can be offered centrally, so no communication of the content provider 103 with the individual vehicles 102 is needed. The backend 104 receives the required information actively from each vehicle 102 , z. For example, changes in the domains become active from the compounding agent 201 to the domain manager 207 transfer. An elaborate (regular) query of the backend 104 at (all) vehicles 102 concerning the status of the respective domains can therefore be omitted.

Informs the domain manager 207 the content provider 103 about that the mobile device 101 is the legitimate communication partner in the domain, then the content provider submits 103 the mobile device 101 the key to decrypting the vehicle 102 downloaded content.

In addition, it should be noted that instead of the symmetric key used here, an asymmetric encryption method with a public and a private key can also be used.

It should also be noted that the communication between the mobile device 101 and the content provider 103 can be secured with an asymmetric encryption method. In this case, the (symmetric) key may be from the content provider 103 to the mobile device 101 secured (for example, encrypted with the public key of the mobile device 101 ) be transmitted. The mobile device 101 can use the transmitted (symmetric) key to access the from the vehicle 102 decrypt downloaded content with the private key.

The vehicle 102 also has an interaction unit 204 , z. B. in the form of a central controller with a display unit and an input unit, on. About this interaction unit 204 a user can manage the domain, e.g. For example, sign in or delete mobile devices from the domain. Such interaction can be done by the connection agent 201 to the domain manager 207 forwarded and accordingly by this in the databases 208 . 209 be saved so that is sure that the domain manager 207 Has access to the current state of the domain.

The contents mentioned here may be different, preferably multimedia content or data. These can have different interfaces in the vehicle 102 get there and there (in the database 205 ) get saved. For example, audio and / or audio / video streams may be loaded from the Internet. It is also possible that radio broadcasts or television programs are recorded. Basically, from different sources, identifiable among others through the partner database 206 , Contents are loaded or recorded.

Other advantages:

The user receives a mobility solution with many possibilities of transferring multimedia data, while respecting the rights of content providers.

In particular, content can be managed by different content providers.

Another advantage is that domain management is centralized for many vehicles or multiple domains. Thus, a content provider can centrally regulate the domain rights management.

It is also an advantage that the transmission of the contents from the vehicle to the mobile device can take place by means of a broadband connection (wireless or wired). This eliminates the need for time-consuming downloading over a narrowband or possibly expensive cellular connection (eg using GPRS).

Another advantage is that the data can be transmitted to the vehicle unencrypted and stored there unencrypted, because the vehicle has an integrated data storage that is difficult to access from the outside or an expansion of the data store is disproportionately complicated and expensive. Thus, due to the structural conditions of the vehicle, it can be achieved that the data is transmitted unencrypted to the vehicle and / or can be stored unencrypted and yet relatively "safely" in the vehicle. This reduces the effort in dealing with the data.

LIST OF REFERENCE NUMBERS

101

mobile device

102

vehicle

103

content provider

104

backend

201

connection Agent

202

Database (including eligible mobile devices)

203

encryption unit

204

Interaction device

205

Database (with unencrypted content)

206

Database (partner data)

207

Domain Manager

208

domain data

209

"Black list" (ID of mobile devices that are not authorized to access)

Claims (15)

Method of transmitting data, - in which the data is transmitted encrypted from a vehicle to a mobile device; - in which the mobile device requests access rights to a content provider; - In which the content provider checks an authorization of the mobile device in a central communication unit and transmits the access rights to the mobile device for a given authorization. The method of claim 1, wherein the data comprises audio and / or video data, programs or image data. Method according to one of the preceding claims, in which the data has been loaded from the vehicle or transmitted to the vehicle. Method according to one of the preceding claims, in which the data is encrypted by the vehicle. Method according to one of the preceding claims, in which an address information is transmitted together with the encrypted data to the mobile device. Method according to Claim 5, in which the content information is addressed on the basis of the address information. Method according to one of the preceding claims, in which the mobile device transmits domain information and / or an identification of the mobile device to the content provider and from the content provider to the central communication unit. Method according to Claim 7, in which the authorization of the mobile device is checked by the central communication unit on the basis of the domain information and / or the identification of the mobile device. Method according to one of the preceding claims, in which the vehicle transmits a change of a domain to the central communication unit. Vehicle comprising - a database in which data, in particular multimedia data, can be stored; An encryption unit for encrypting the data; A connection agent, by means of which the encrypted data can be transmitted via a first interface to a mobile device. Vehicle according to claim 10, comprising a second interface, via which the connection agent can be connected to a central communication unit, wherein domain information can be transmitted via the second interface. Vehicle according to claim 11, comprising an input unit by means of which the domain information is editable. Vehicle according to one of claims 11 or 12, in which the data can be loaded via the second interface. A central communication unit for communicating with a vehicle according to any one of claims 11 to 13, - having a domain manager connectable to the connection agent of the vehicle via the second interface; - With a third interface over the basis of the domain manager authorization information is available. Central communication unit according to claim 14, wherein the authorization information comprises a permission of a mobile device for a particular domain or a lack of authorization of that mobile device in this domain.

Images