# US 11,115,700 B2 · Method and device for identifying a peripheral device from a digital content > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,115,700 B2 - Document ID: US11115700B2 - Status: Granted - Kind: B2 - Application number: 16/077,297 - Filed: 2017-02-09 - Published: 2019-02-14 - Granted: 2021-09-07 - Earliest claimed: 2016-02-12 - Assignees: Nagravision S.A. - Applicants: Nagravision S.A. - Inventors: Philippe Stransky-Heilkron; Frederic Thomas - Web page: https://patentgrep.com/patent/US11115700B2 ## CPC - H04N 21/4108: {characterised by an identification number or address, e.g. local network address (protecting specific internal or external computer components using identification number G06F21/73; network arrangements, protocols or services for addressing or naming H04L61/00)} - H04N 21/436: Interfacing a local distribution network, e.g. communicating with another STB {or one or more peripheral devices} inside the home - H04N 21/43635: {HDMI} - H04N 21/8358: involving watermark {(protecting executable software by watermarking G06F21/16; image watermarking in general G06T1/0021; watermarks inserted in still images for transmission purposes H04N1/32144; inserting watermarks during video coding H04N19/467)} - H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION ## Abstract A method for identifying a peripheral device from a digital content having been received by said peripheral device from a master device located at a user end, said master device being further configured to be connected to a server located at a back end, said method comprising the steps of: receiving, by the master device from the peripheral device, at least peripheral identification data; generating, at the master device, a first mark as a function of at least a part of said peripheral identification data; and watermarking said digital content using said first mark before transmitting said digital content to said peripheral device. ## Claims ### Claim 1 A method for identifying a peripheral device from a digital content having been received by said peripheral device from a master device located at a user end, said master device being further configured to be connected to a server located at a back end, said method comprising: receiving, by the master device from the peripheral device, at least a peripheral identifier; generating, at the master device, a first mark as a function of said peripheral identifier and a code, the code being generated from event data that includes at least a master device identifier and transaction information related to the digital content; and watermarking said digital content using said first mark before transmitting said digital content to said peripheral device, wherein said peripheral device is connected to said master device through an HDMI or DTCP connection, and the peripheral device is a rendering device. ### Claim 2 (depends on 1) The method of claim 1, further comprising: generating, at the master device, the event data; and sending said event data to a server via a return path linking the master device to said server and/or storing said event data in the master device. ### Claim 3 (depends on 2) The method of claim 2, further comprising: receiving, at the master device, the code that is generated by the server in response to said event data received by the server. ### Claim 4 (depends on 2) The method of claim 2, wherein said event data is generated each time said peripheral identifier is received by the master device from the peripheral device and/or each time the peripheral device is disconnected from said master device. ### Claim 5 (depends on 2) The method of claim 2, wherein said event data is sent to the server on a periodic basis, on request of the server or once a predefined number of event data has been stored. ### Claim 6 (depends on 1) The method of claim 1, further comprising generating, at the master device, a second mark as a function of at least the master device identifier; and wherein said watermarking step further includes using said second mark. ### Claim 7 (depends on 6) The method of claim 6, wherein at least one of said first mark and second mark is less than 32 bits long. ### Claim 8 (depends on 1) The method of claim 1, wherein said function is a hash function. ### Claim 9 (depends on 1) The method of claim 1, wherein said function is defined by the server through a control message received by the master device. ### Claim 10 (depends on 2) The method of claim 2, wherein sending said digital content by the master device to the peripheral device is controlled by the server on the basis of said event data received by the server. ### Claim 11 (depends on 10) The method of claim 10, wherein sending said digital content by the master device to the peripheral device depends on a command sent by the server and executed by the master device upon receipt; said command authorizes or prevents the master device to send said digital content to the peripheral device. ### Claim 12 A master device to transmit a digital content to a peripheral device, said master device being located at a user end and being configured to be connected to a server located at a back end, said master device comprising: a data interface configured to receive, from said peripheral device, at least peripheral identifier; a mark generator configured to generate a first mark as a function of said peripheral identifier and a code, the code being generated from event data that includes at least a master device identifier and transaction information related to the digital content; a watermarking unit configured to watermark said digital content using at least said first mark; and a controller configured to instruct the watermarking unit to watermark said digital content before transmitting said digital content to said peripheral device, wherein said peripheral device is connected to said master device through an HDMI or DTCP connection, and the peripheral device is a rendering device. ### Claim 13 (depends on 12) The master device of claim 12 comprising: a logger configured to generate the event data; and a return path interface for linking the master device to said server; wherein said controller is further configured to send said event data to the server. ### Claim 14 (depends on 13) The master device of claim 13, wherein the data interface is further configured to receive, from the server, the code in response to the transmission of the event data.