BROADCAST APPARATUS AND METHOD OF AUTHENTICATING BROADCAST DATA

• US 20160227406A1
• Filed: 01/22/2016
• Published: 08/04/2016
• Est. Priority Date: 02/03/2015
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: OUTTERS, Jan, WALLER, Arthur Simon, ADAM, John
• Granted Patent: US 10,412,589 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/51 at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04N 21/2362 Generation or processing of Service Information [SI]
• CPC Class Codes: H04N 21/23892 involving embedding information at multiplex stream level, e.g. embedding a watermark at packet level
• CPC Class Codes: H04N 21/4345 Extraction or processing of SI, e.g. extracting service information from an MPEG stream
• CPC Class Codes: H04N 21/435 Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
• CPC Class Codes: H04N 21/44236 Monitoring of piracy processes or activities protecting computer platforms against harmful, malicious or unexpected behaviour or activities using intrusion detection and counter measures G06F21/566; computer virus detection and handling G06F21/56
• CPC Class Codes: H04N 21/4433 Implementing client middleware, e.g. Multimedia Home Platform [MHP]
• CPC Class Codes: H04N 21/4622 Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet web site content organization and management for information retrieval from the Internet G06F16/958; transmission by internet of broadcast information H04H60/82; stock exchange data over packet-switching network H04L12/1804; push services including data channel over packet-switching network H04L12/1859
• CPC Class Codes: H04N 21/8173 End-user applications, e.g. Web browser, game
• CPC Class Codes: H04N 21/835 Generation of protective data, e.g. certificates protecting software against unauthorised usage in a vending or licensing environment G06F21/10
• CPC Class Codes: H04W 12/106 Packet or message integrity
• CPC Class Codes: H04W 4/06 Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Abstract

A broadcast receiver includes a communicator configured to receive broadcast data including metadata associated with an application and a controller configured to obtain a comparison result by comparing a reference hash with a metadata hash generated based on the metadata, authenticate the metadata based on the comparison result, and launch the application based on a result of the authentication.

Claims

1. A broadcast receiver comprising:

a communicator configured to receive broadcast data including metadata associated with an application; and

a controller configured to obtain a comparison result by comparing a reference hash with a metadata hash generated based on the metadata, authenticate the metadata based on the comparison result, and launch the application based on a result of the authentication.

2. The broadcast receiver of claim 1, further comprising:

a display configured to display information corresponding to the launched application.

3. The broadcast receiver of claim 1, wherein the controller is further configured to generate the metadata hash and compare the generated metadata hash with the reference hash.

4. The broadcast receiver of claim 3, further comprising:

a storage configured to store a plurality of reference hashes for a same application,

wherein the controller is further configured to select a reference hash from among the stored plurality of reference hashes and compare the selected reference hash with the metadata hash.

5. The broadcast receiver of claim 3 further comprising:

a storage configured to store a plurality of reference hashes for a same application and authentication information indicating valid periods for a plurality of the reference hashes, wherein

the controller is further configured to select a reference hash from among the stored plurality of reference hashes having a valid period at a time when the metadata is received, based on the authentication information.

6. The broadcast receiver of claim 3, wherein the communicator is further configured to transmit a request for the reference hash to a server and receive the reference hash from the server, and

the request for the reference hash comprises service identification information for identifying a service corresponding to the application which is received along with the metadata.

7. The broadcast receiver of claim 6, wherein the communicator is further configured to receive a plurality of reference hashes from the server in response to the request, and

the controller is further configured to authenticate the metadata by comparing the received plurality of reference hashes with the metadata hash to determine whether a reference hash of the received plurality of reference hashes matches the metadata hash.

8. The broadcast receiver of claim 1, wherein the communicator is further configured to transmit an authentication request for the received metadata to a server, and

the communicator is further configured to receive from the server, in response to the authentication request, a comparison result obtained by comparing the metadata hash with the reference hash.

9. The broadcast receiver of claim 8, wherein the authentication request comprises the metadata and service identification information for identifying a service corresponding to the application.

10. The broadcast receiver of claim 1, wherein the controller is further configured to generate the metadata hash,

the communicator is further configured to transmit, to the server, service identification information for identifying a service corresponding to the application and an authentication request including the generated metadata hash, and

the communicator is further configured to receive from the server, in response to the authentication request, the comparison result.

11. The broadcast receiver of claim 6, wherein the service identification information comprises at least one of an original network identifier (ON-ID), a transport stream identifier (TS-ID), a service identifier (S-ID), a country identifier (ID) for identifying a country at which the broadcast receiver is located, and a broadcast medium ID for identifying a broadcast medium through which the broadcast data received by the broadcast receiver passes.

12. The broadcast receiver of claim 1, further comprising:

a display,

wherein the controller is further configured to, in response to the authentication of the metadata failing, control the display to display a warning message indicating that the metadata is not authenticated.

13. The broadcast receiver of claim 1, further comprising:

a user input device configured to receive a user input for forcibly executing the application when the authentication of the metadata fails,

wherein the controller is further configured to forcibly execute the application, based on the user input.

14. A server for authenticating metadata associated with an application, the server comprising:

a storage configured to store a reference hash;

a communicator configured to receive an authentication request from a broadcast receiver; and

a controller configured to obtain a metadata hash of the metadata based on the authentication request, search for a reference hash corresponding to the authentication request in the storage, compare the obtained metadata hash with the reference hash, and control the communicator to transmit a result of the comparison to the broadcast receiver.

15. The server of claim 14, wherein the authentication request comprises service identification information for identifying a service corresponding to the metadata, and

the controller is further configured to search for the reference hash corresponding to the identified service in the storage.

16. The server of claim 14, wherein the authentication request comprises the metadata, and

the controller is further configured to generate the metadata hash from the metadata.

17. The server of claim 14, wherein the authentication request comprises the metadata hash, and

the controller is further configured to extract the metadata hash from the authentication request.

18. The server of claim 15, wherein the controller is further configured to search for a plurality of reference hashes in the storage, compare the metadata hash with the plurality of reference hashes to determine whether the metadata hash matches a reference hash of the plurality of reference hashes, and control the communicator to transmit a result of the comparison to the broadcast receiver.

19. A broadcast provider comprising:

a controller configured to obtain metadata associated with an application, generate a reference hash of the metadata, and insert the metadata into broadcast data; and

a communicator configured to transmit the broadcast data including the metadata to a broadcast receiver,

wherein the controller is further configured to control the communicator to transmit the reference hash to an external device so that the reference hash is used to authenticate the metadata.

20. A metadata authentication method comprising:

receiving broadcast data including metadata associated with an application;

obtaining a comparison result by comparing a reference hash with a metadata hash generated based on the metadata; and

authenticating the metadata, based on the comparison result.