System and method for providing DRM-protected media data for at least one vehicle

Abstract

System (100, 400) for providing DRM-protected media data for at least one vehicle (102), with a processing unit (104) located remote from the vehicle (102), which is designed to provide the media data as an encrypted data packet that can be decrypted for playback using at least one private key of the vehicle (102), with a control unit (108) of the vehicle (102) which is configured to provide identification data of the vehicle (102) and to decrypt the encrypted data packet with the private key of the vehicle (102) for playback by an output unit (110) of the vehicle (102), and with a mobile device (112) that is configured to receive the vehicle's (102) identification data, to communicate with the remote processing unit (104) via a remote data transmission network (106), to authenticate itself to the remote processing unit (104) at least with the vehicle's (102) identification data, to receive the encrypted data packet from the remote processing unit (104) via the remote data transmission network (106), to store the received data packet in a memory area of ​​the mobile device (112) and to provide the stored data packet to the control unit (108) of the vehicle (102), wherein the vehicle identification data (102) includes at least one public key linked to the vehicle's private key (102).

Description

[0001] The invention relates to a system for providing DRM-protected media data to at least one vehicle. The invention further relates to a method for providing DRM-protected media data to at least one vehicle.

[0002] US Patent 9,032,547 B1 discloses a method for digital rights management in a vehicle. In this method, DRM-protected media data is streamed for playback in the vehicle via an active data connection from a mobile phone.

[0003] German patent DE 10 2010 029 929 A1 discloses a method in which encrypted media data is transmitted from a vehicle to a mobile device. The mobile device then requests access rights for the media data from a central communication unit of a media data provider.

[0004] US patent 2013 / 0297456A1 discloses a method for acquiring copyrighted content for vehicles. In this method, copyrighted content is made available on a server in response to a vehicle purchase request.

[0005] Digital Rights Management (DRM) ensures that media data can only be played back by authorized devices, i.e., devices for which a user has purchased a playback license. This is achieved primarily through asymmetric encryption methods, where the media data is encrypted with a public key belonging to an authorized device, making it decryptable only with the authorized device's private key. While this allows copies of the media data to be made, these copies can only be played back by the authorized device. Typically, the necessary key exchange occurs simultaneously with the download of the media data to the authorized device. For playback of DRM-protected media data in vehicles, this means that the data can only be played back by the vehicle itself after it has been downloaded.While modern vehicles are equipped with mobile antennas that can provide internet access, this access is typically tied to limited data plans. Downloading high-resolution media, in particular, can be expensive or quickly deplete the data allowance. As a result, playing DRM-protected media in vehicles has not been very user-friendly until now.

[0006] The object of the invention is therefore to provide a system and a method for providing DRM-protected media data for at least one vehicle that are more user-friendly than previous solutions.

[0007] This problem is solved by a system having the features of claim 1 and by a method having the features of the independent method claim. Advantageous embodiments are specified in the dependent claims.

[0008] The proposed system for providing DRM-protected media data to at least one vehicle comprises a processing unit located remotely from the vehicle, configured to provide the media data as an encrypted data packet that can be decrypted for playback using at least one of the vehicle's private keys. The system also includes a control unit within the vehicle, configured to provide vehicle identification data and to decrypt the encrypted data packet using the vehicle's private key for playback by an output unit within the vehicle.The system further comprises a mobile terminal device that is designed to receive the vehicle's identification data, communicate with the remote processing unit via a remote data transmission network, authenticate itself to the remote processing unit at least with the vehicle's identification data, receive the encrypted data packet from the remote processing unit via the remote data transmission network, store the received data packet in a memory area of ​​the mobile terminal device, and provide the stored data packet to the vehicle's control unit.

[0009] The media data includes, in particular, audio, image, and / or video data that can be played back by the vehicle's output unit. The media data can also include applications that can be executed by the control unit to generate output on the output unit. In this document, "mobile device" refers specifically to smartphones, laptop computers, tablet computers, handheld game consoles, and similar portable devices that have an interface capable of connecting to the data transmission network. The data transmission network is primarily the internet, but also includes other computer networks such as LAN, MAN, or WAN networks. Communication between the mobile device and the data transmission network, or between the mobile device and the vehicle's control unit, preferably takes place via a wireless interface, such as WLAN or Bluetooth. ®Near field communication (NDC) or mobile communication, or via a wired interface, such as Ethernet or USB.

[0010] Because the mobile device identifies itself to the provider using the vehicle's identification data, the provider can make the media data intended for the vehicle available for download to the mobile device. This allows the proposed system to enable users to download DRM-protected media data using their mobile device and make it available for playback in the vehicle. Users can thus download media data using their mobile device via a connection that is not restricted by a data plan. For example, users can download media data at home via a Wi-Fi connection on their home network. The proposed system is therefore much more intuitive for users than previous systems, where it was not always clear to users why media data downloaded to their mobile device could not be played back in the vehicle.This makes the proposed system much more user-friendly than previous solutions.

[0011] In a preferred embodiment, the remote processing unit is configured to provide the media data as an encrypted data packet in such a way that it can also be decrypted for playback using a private key of the mobile device. The mobile device can be configured to authenticate itself to the remote processing unit using the vehicle's identification data and the mobile device's identification data, and to decrypt the encrypted data packet using the mobile device's private key for playback by the mobile device. In this embodiment, the provider makes the media data available in such a way that it can be played back both with the vehicle's output unit and with the mobile device.This meets user expectations, as users assume they can play media downloaded to their mobile device on that same device. This makes the system even more user-friendly. Furthermore, the media data only needs to be downloaded once, saving storage space on the mobile device.

[0012] In an alternative embodiment, the remote processing unit is configured to provide the media data as a first encrypted data packet that can be decrypted for playback using the vehicle's private key, and to provide the media data as a second encrypted data packet that can be decrypted for playback using the mobile device's private key.The mobile device can be configured to authenticate itself to the remote processing unit using the vehicle's identification data and the mobile device's identification data, to receive both the first and second encrypted data packets from the remote processing unit via the remote data transmission network, to store the received data packets in the mobile device's memory, to provide the first encrypted data packet to the vehicle's control unit, and to decrypt the second encrypted data packet using the mobile device's private key for playback by the mobile device. In this alternative embodiment, the provider makes the media data available twice.The media data is provided in two ways: once in a format that can be decoded by the vehicle's control unit, and once in a format that can be decoded by the mobile device. Thus, in this embodiment as well, the media data can be played back using both the vehicle's output unit and the mobile device, and the media data provision meets the user's expectations. This alternative embodiment also increases the system's user-friendliness. However, in this embodiment, it is not necessary for the media data to be provided in a format that can be decoded using different private keys. This makes the system more versatile and compatible with a wide range of media data providers.

[0013] In a further preferred embodiment, the system comprises the control unit of another vehicle, which is configured to provide identification data of the other vehicle and to decrypt the encrypted data packet with a private key of the other vehicle for playback by an output unit of the other vehicle. The remote processing unit can be configured to provide the media data as the encrypted data packet in such a way that it can also be decrypted for playback with the private key of the other vehicle. Furthermore, the mobile device can be configured to receive the identification data of the other vehicle, authenticate itself to the remote processing unit with the identification data of the vehicle and the other vehicle, and provide the stored data packet to the other vehicle.The encrypted data packet can be decrypted for playback by both the vehicle's control unit and the control unit of another vehicle. In this implementation, the provider makes the media data available in a format that can be decrypted and played back by multiple vehicles. Users can therefore play media data downloaded once to their mobile device in several vehicles. This makes the system even more versatile and user-friendly.

[0014] In a further preferred embodiment, the system comprises another mobile device configured to provide identification data of the other mobile device and to decrypt the encrypted data packet with a private key of the other mobile device for playback by the other mobile device. The remote processing unit can be configured to provide the media data as the encrypted data packet in such a way that it can also be decrypted for playback with the private key of the other mobile device. Furthermore, the mobile device can be configured to receive the identification data of the other mobile device, authenticate itself to the remote processing unit with the identification data of the vehicle and the other mobile device, and provide the stored data packet to the other mobile device.The additional mobile device can be, in particular, a mobile device integrated into the vehicle, such as a tablet computer that serves as a display element. In this configuration, the encrypted data packet can be decrypted for playback by both the vehicle's control unit and the additional mobile device. The media data is thus provided in a format that can be decrypted and played back not only by the vehicle but also by the additional mobile device. The user can therefore play media data downloaded to their mobile device on the additional mobile device as well. Especially when the additional mobile device is integrated into the vehicle, different occupants can play different media simultaneously. This makes the system even more versatile and user-friendly.

[0015] In another preferred embodiment, the vehicle's identification data includes at least one token uniquely assigned to the vehicle. For example, the token could be a vehicle identification number (VIN). The token allows the provider to uniquely identify the vehicle in order to provide the corresponding encrypted data package. This eliminates the need to share the vehicle's public key with the mobile device. In this embodiment, the vehicle's public key can either reside on the remote processing unit or be received by the remote processing unit from a key server.

[0016] The vehicle's identification data includes at least one public key linked to the vehicle's private key. Using this public key, the provider can encrypt the media data in such a way that it can only be decrypted with the corresponding private key. This allows the provider to generate and deliver the encrypted data package directly using the identification data, eliminating the need for any further connection, for example, to a

[0017] A key server is required. This simplifies the system's network architecture.

[0018] In another preferred embodiment, the mobile device is configured to authenticate itself to the remote processing unit by impersonating the vehicle. In this embodiment, the mobile device emulates the vehicle to authenticate itself using the vehicle's identification data. From the provider's perspective, it therefore makes no difference whether the vehicle itself or the mobile device requests the media data. Consequently, it is not necessary for the provider to support the delivery of data packets that are not encrypted for the mobile device. The system can thus be used more flexibly and with a wider range of providers.

[0019] The invention further relates to a method for providing DRM-protected media data in at least one vehicle. In this method, vehicle identification data is transmitted to a mobile device. The mobile device communicates with a media data provider via a remote data transmission network, authenticating itself at least with the vehicle's identification data. The provider makes the media data available as an encrypted data packet, which can be decrypted for playback using at least one of the vehicle's private keys. The mobile device receives the encrypted data packet from the provider via the remote data transmission network. The mobile device stores the received data packet in a memory area of ​​the mobile device. The mobile device then makes the data packet available to the vehicle.

[0020] The method has the same advantages as the claimed device. In particular, the method can be further developed with the features of the dependent claims directed to the device.

[0021] Exemplary embodiments of the invention are explained in more detail below with reference to the figures. These show: Fig. 1 in schematic representation a system for providing DRM-protected media data for at least one vehicle; Fig. 2 in schematic representation a mobile terminal and a processing unit of the system located away from the vehicle according to Fig. 1; Fig. 3 in schematic representation a control unit of the vehicle, the mobile device and another mobile device as part of the system according to the Fig. 1 and Fig. 2; Fig. 4 in schematic representation a system for providing DRM-protected media data for at least two vehicles according to one embodiment; Fig. 5 the flowchart of a procedure for providing the DRM-protected media data for the at least one vehicle.

[0022] Fig. Figure 1 shows a schematic representation of a system 100 for providing DRM-protected media data for at least one vehicle 102.

[0023] System 100 includes a processing unit 104 located remotely from vehicle 102. Processing unit 104 belongs, for example, to a media data provider. Processing unit 104 is configured to provide the media data as an encrypted data packet that can only be decrypted with a corresponding private key. This ensures that the media data can only be played back by authorized devices, such as devices for which a user has purchased a playback license. Processing unit 104 uses an asymmetric encryption method to encrypt the media data. For this purpose, the media data is encrypted with a public key that matches the private key to create the encrypted data packet. The provider makes the encrypted media data available for download, for example, via a data transmission network 106, such as the internet.

[0024] A control unit 108 of the vehicle 102 is also part of the system 100. The control unit 108 of the vehicle 102 is configured to decrypt the encrypted data packet. To decrypt the encrypted data packet, the control unit 108 uses a private key of the vehicle 102. The control unit 108 is also configured to play back the decrypted media data via an output unit 110 of the vehicle 102. An example of an output unit 110 of the vehicle 102 is shown in Fig. Figure 1 shows a screen of vehicle 102, which may be located, for example, on the back of a headrest of vehicle 102. Other output devices may include, for example, speakers and other screens. Furthermore, the control unit 108 is configured to provide identification data of vehicle 102, which is suitable for uniquely identifying vehicle 102 to the media data provider. The identification data may, for example, include a public key belonging to the private key of vehicle 102. Alternatively or additionally, the identification data may include a token uniquely assigned to vehicle 102, such as a vehicle identification number.

[0025] System 100 also includes a mobile device 112, which is in Fig. 1. A smartphone is purely an example. The mobile device 112 is configured to receive the vehicle 102's identification data from the vehicle 102's control unit 108 and store it in a memory area of ​​the mobile device 112. To receive the identification data, the mobile device 112 communicates with the control unit 108 via a wireless interface, such as WLAN or Bluetooth. ® Near field communication (NDC) or mobile communication, or via a wired interface, such as Ethernet or USB.

[0026] Using the vehicle 102's identification data, the mobile device 112 can authenticate itself to the media data provider in order to download the media data. For this purpose, the mobile device 112 communicates with the remote processing unit 104 via the data transmission network 106 using either the wireless or wired interface. Using this connection, the mobile device 112 receives the encrypted data packet from the remote processing unit 104. The mobile device 112 stores the received data packet in its own memory and makes the data packet available to the vehicle 102's control unit 108. The steps of authentication and receiving the encrypted data packet are described below. Fig. 2 is described in more detail below. The provision of the received data packet is explained below using the following: Fig. 3 described in more detail.

[0027] In one possible embodiment, the media data can also be played back using the mobile device 112 itself. For this purpose, the remote processing unit 104 is configured to provide the media data as an encrypted data packet in such a way that it can also be decrypted for playback using a private key of the mobile device 112. In such an embodiment, the mobile device 112 is configured to authenticate itself to the remote processing unit 104 using identification data of the mobile device 112, which includes, for example, a public key belonging to the private key of the mobile device 112. Furthermore, in such an embodiment, the mobile device 112 is configured to decrypt the encrypted data packet using the private key of the mobile device 112 for playback by the mobile device 112.

[0028] As an optional element, the system 100 includes another mobile device 114, which is in Fig. Let 1 be a tablet computer, purely as an example. If the system 100 includes the additional mobile device 114, the remote processing unit 104 is configured to provide the encrypted data packet in such a way that it can also be decrypted with a private key of the additional mobile device 114. The additional mobile device 114 is configured to provide identification data of the additional mobile device 114, which includes, for example, a public key belonging to the private key of the additional mobile device 114. Furthermore, the additional mobile device 114 is configured to decrypt the encrypted data packet with a private key of the additional mobile device 114 for playback by the additional mobile device 114.In such an embodiment, the mobile terminal 112 is configured to receive the identification data of the further mobile terminal 114, to authenticate itself to the remote processing unit 104 with the identification data of the vehicle 102 and the further mobile terminal 114, and to provide the stored data packet to the further mobile terminal 114.

[0029] Fig. Figure 2 shows a schematic representation of the mobile terminal 112 and the remote processing unit 104 of the system 100 according to Fig. 1.

[0030] In the representation according to Fig. In Figure 2, the mobile device 112 is connected to the remote data transmission network 106 via a WLAN interface provided by a router 200 of a home network. The mobile device 112 is then connected to the remote processing unit 104 of the media data provider via the remote data transmission network 106. Because the communication between the mobile device 112 and the media data provider takes place via a home network, the media data can be downloaded independently of mobile data plans.

[0031] To receive the media data, the mobile device 112 first sends the identification data of the vehicle 102, and if applicable, the identification data of the mobile device 112 and / or the other mobile device 114, to the remote processing unit 104. The remote processing unit 104 then generates the encrypted data packet in such a way that it can be decrypted with the private key of the devices for which the remote processing unit 104 received identification data in the previous step. The remote processing unit 104 then transmits the encrypted data packet to the mobile device 112, which stores the encrypted data packet in its memory. In a subsequent step, the user can then insert the mobile device 112 back into the vehicle 102 to make the encrypted data packet, and thus the media data, available to the control unit 108.This will be shown below using the following example. Fig. 3 described.

[0032] Fig. Figure 3 shows a schematic representation of the control unit 108 of the vehicle 102, the mobile device 112 and the further mobile device 114 as part of the system 100 according to the Fig. 1 and Fig. 2.

[0033] In the representation according to Fig. In Figure 3, mobile device 112 and mobile device 114 are installed in the interior of vehicle 102. Mobile device 112 is connected via Bluetooth. ® -Interface connected to the control unit 108 of the vehicle 102 and to the other mobile device 112.

[0034] To make the media data available for playback in the vehicle 102 and / or on the other mobile device 112, the mobile device 112 first transmits the encrypted data packet to the control unit 108 of the vehicle 102 and to the other mobile device 114. The control unit 108 then stores the encrypted data packet in a memory area of ​​the control unit 108, and the other mobile device 114 then stores the encrypted data packet in a memory area of ​​the other mobile device 114. To play the media data in the vehicle 102, the control unit 108 first decrypts the data packet using the private key of the vehicle 102 and then plays the decrypted media data, for example, on the monitor of the vehicle 102.To play back the media data on the other mobile device 112, the other mobile device 114 first decrypts the data packet using the private key of the other mobile device 114 and then plays back the decrypted media data. If the media data was encrypted accordingly on the provider's side, mobile device 112 itself can also decrypt the data packet using its own private key and then play back the decrypted media data.

[0035] Fig. Figure 4 shows a schematic representation of a system 400 for providing DRM-protected media data for at least two vehicles 102, 402 according to an embodiment.

[0036] System 100 according to Fig. 4 differs from system 100 according to the Fig. 1 to 3 in that it includes a control unit 404 of another vehicle 402. The system 400 according to Fig. 4 allows media data downloaded once with the mobile device 112 to be played back in the two vehicles 102, 402.

[0037] Similar to the control unit 108 of vehicle 102, the control unit 404 of the other vehicle 402 is configured to decrypt the encrypted data packet with a private key of the other vehicle 402 for playback by an output unit 406 of the other vehicle 402. The control unit 404 of the other vehicle 402 is further configured to provide identification data of the other vehicle 402 and to transmit it to the mobile device 112 via the wireless or wired interface. The identification data of the other vehicle 402 includes, for example, a public key belonging to the private key of the other vehicle 402 or a token that uniquely identifies the other vehicle 402, such as a vehicle identification number.

[0038] In this embodiment, the remote processing unit 104 is additionally configured to provide the media data as an encrypted data packet in such a way that it can also be decrypted for playback using the private key of the other vehicle 402. The mobile terminal 112 is further configured to receive the identification data of the other vehicle 402, to authenticate itself to the remote processing unit 104 using the identification data of both vehicle 102 and the other vehicle 402, and to provide the stored data packet to the other vehicle 402.

[0039] Fig. Figure 5 shows the flowchart of a procedure for providing the DRM-protected media data for at least one vehicle 102.

[0040] The process is initiated in step S500. In step S502, the control unit 108 of the vehicle 102 transmits the vehicle 102's identification data to the mobile device 112. In step S504, the mobile device 112 establishes a connection with the media data provider via the data transmission network 106. For this purpose, the mobile device 112 authenticates itself using at least the vehicle 102's identification data. In step S506, the provider makes the media data available as an encrypted data packet, which can be decrypted for playback using at least the vehicle 102's private key. In step S508, the mobile device 112 receives the encrypted data packet from the provider via the data transmission network 106 and stores the received data packet in a memory area of ​​the mobile device 112. In step S510, the mobile device 112 makes the data packet available to the vehicle 102. The procedure ends in step S512.

[0041] In the based on the Fig. Examples of implementation described in sections 1 to 5 include media data, in particular audio data, for example DRM-protected music or audiobooks, image data, or a combination of audio and video data, for example DRM-protected films or series. The media data can also include an application, which can be executed in particular by the control units 108, 404 of the vehicles 102, 402, the mobile device 112, or the further mobile device 114.

[0042] At least the processing unit 104, the control unit 108 of the vehicle 102, and the mobile terminal 112, located away from the vehicle 102, form the system 100 for providing the DRM-protected media data to the at least one vehicle 102. Further details in the Fig. Elements and features shown in 1 to 5 and mentioned in the preceding description can be part of System 100. Reference symbol list 100 System 102 vehicles 104 processing units 106 Data transmission network 108 Control unit 110 output units 112, 114 mobile device 200 routers 400 System 402 Vehicle 404 Control unit 406 output unit

Claims

[1] System (100, 400) for providing DRM-protected media data for at least one vehicle (102), with a processing unit (104) located away from the vehicle (102), which is designed to provide the media data as an encrypted data packet that can be decrypted for playback using at least one private key of the vehicle (102), with a control unit (108) of the vehicle (102) which is configured to provide identification data of the vehicle (102) and to decrypt the encrypted data packet with the private key of the vehicle (102) for playback by an output unit (110) of the vehicle (102), and with a mobile device (112) that is configured to receive the vehicle's (102) identification data, to communicate with the remote processing unit (104) via a remote data transmission network (106), to authenticate itself to the remote processing unit (104) at least with the vehicle's (102) identification data, to receive the encrypted data packet from the remote processing unit (104) via the remote data transmission network (106), to store the received data packet in a memory area of ​​the mobile device (112) and to provide the stored data packet to the control unit (108) of the vehicle (102), wherein the vehicle identification data (102) includes at least one public key linked to the vehicle's private key (102). [2] System (100, 400) according to claim 1, wherein the remote processing unit (104) is configured to provide the media data as the encrypted data packet in such a way that it can also be decrypted with a private key of the mobile device (112) for playback, and wherein the mobile device (112) is configured to authenticate itself to the remote processing unit (104) with the identification data of the vehicle (102) and with identification data of the mobile device (112) and to decrypt the encrypted data packet with the private key of the mobile device (112) for playback by the mobile device (112). [3] System (100, 400) according to claim 1, wherein the remote processing unit (104) is configured to provide the media data as a first encrypted data packet that can be decrypted for playback using the private key of the vehicle (102), and to provide the media data as a second encrypted data packet that can be decrypted for playback using a private key of the mobile device (112), and wherein the mobile device (112) is configured to authenticate itself to the remote processing unit (104) with the identification data of the vehicle (102) and with identification data of the mobile device (112), to receive both the first encrypted data packet and the second encrypted data packet from the remote processing unit (104) via the remote data transmission network (106), to store the received data packets in the memory area of ​​the mobile device (112), the first encrypted data packet of the control unit (108) of the vehicle (102) and to decrypt the second encrypted data packet with the private key of the mobile device (112) for playback by the mobile device (112). [4] System (400) according to claim 1 or 2, comprising the control unit (108) of a further vehicle (402) configured to provide identification data of the further vehicle (402) and to decrypt the encrypted data packet with a private key of the further vehicle (402) for playback by an output unit (406) of the further vehicle (402), wherein the remote processing unit (104) is configured to provide the media data as the encrypted data packet in such a way that it can also be decrypted for playback using the private key of the other vehicle (402), and wherein the mobile terminal (112) is configured to receive the identification data of the other vehicle (402), to authenticate itself to the remote processing unit (104) with the identification data of the vehicle (102) and the other vehicle (402) and to provide the stored data packet to the other vehicle (402). [5] System (100, 400) according to one of the preceding claims, comprising a further mobile device (114) configured to provide identification data of the further mobile device (114) and to decrypt the encrypted data packet with a private key of the further mobile device (114) for playback by the further mobile device (114), wherein the remote processing unit (104) is configured to provide the media data as the encrypted data packet in such a way that it can also be decrypted for playback using the private key of the other mobile device (114), and wherein the mobile device (112) is configured to receive the identification data of the other mobile device (114), to authenticate itself to the remote processing unit (104) with the identification data of the vehicle (102) and the other mobile device (114) and to provide the stored data packet to the other mobile device (114). [6] System (100, 400) according to one of the preceding claims, wherein the identification data of the vehicle (102) includes at least one token uniquely assigned to the vehicle (102). [7] System (100, 400) according to one of the preceding claims, wherein the mobile terminal (112) is configured to authenticate itself to the remote processing unit (104) by the mobile terminal (112) identifying itself to the remote processing unit (104) as the vehicle (102). [8] Method for providing DRM-protected media data in at least one vehicle (102), where the vehicle identification data (102) is transmitted to a mobile device (112), where the mobile device (112) communicates with a media data provider via a remote data transmission network (106), the mobile device (112) authenticating itself at least with the vehicle's identification data (102), where the provider makes the media data available as an encrypted data packet which can be decrypted for playback at least with a private key of the vehicle (102), where the mobile device (112) receives the encrypted data packet from the provider via the remote data transmission network (106), where the mobile device (112) stores the received data packet in a storage area of ​​the mobile device (112), and where the mobile device (112) provides the data package to the vehicle (102), wherein the vehicle identification data (102) includes at least one public key linked to the vehicle's private key (102).

Images