System and method for supporting multiple identities for a secure identity device

• US 10,334,305 B2
• Filed: 06/03/2014
• Issued: 06/25/2019
• Est. Priority Date: 10/17/2008
• Status: Active Grant

• Current Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Original Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Inventors: Reynolds, Steven J.
• Primary Examiner(s): Pyzocha, Michael
• Application Number:
  US14/295,026
• Publication Number:
  US 20140351875A1
• Time in Patent Office: 1,848 Days
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04N 21/25816 involving client authentication restricting access to computer systems by authenticating users using a predetermined code G06F21/33; cryptographic authentication protocols H04L9/32; networks authentication protocols H04L63/08; authentication in wireless network security H04W12/06
• CPC Class Codes: H04N 21/42684 Client identification by a unique number or address, e.g. serial number, MAC address, socket ID network arrangements, protocols or services for addressing or naming H04L61/00
• CPC Class Codes: H04N 21/647 Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless real-time session protocols H04L65/1101

Abstract

A multiple-identity secure device (MISD) persistently stores a single identification code (a “seed identity”). The seed identity need not be a network address, and may be stored in an integral memory of the device, or on an interchangeable card received in a physical interface of the MISD. The MISD is provided with a transformation engine, in hardware or software form, that is subsequently used to generate one or more unique identities (e.g., network addresses) from the stored seed identity using predefined logic. The generated identities may be dynamically generated, e.g., in real-time as needed after deployment of a device into possession of a subscriber/customer/user, etc., or may be securely stored in the MISD for subsequent retrieval. The transformation engine may generate a unique identity in accordance with an addressing scheme identified as a default setting, a global/network setting, or as determined from a received data transmission.

Claims

1. A method comprising:

generating, by a device and using a seed code stored by the device, a plurality of unique addresses for the device, wherein each unique address of the plurality of unique addresses is compliant with a different addressing scheme;

storing, by the device, the plurality of unique addresses;

determining a first addressing scheme used to direct a data transmission to the device; and

retrieving, by the device and from among the plurality of unique addresses, a first unique address that is compliant with the first addressing scheme used to direct the data transmission to the device.

2. The method of claim 1, wherein the data transmission comprises a recipient identifier, the method further comprising:

evaluating, by the device, whether the first unique address corresponds to the recipient identifier.

3. The method of claim 2, further comprising:

processing, by the device, the data transmission after determining that the first unique address corresponds to the recipient identifier.

4. The method of claim 1, wherein the plurality of unique addresses comprises the first unique address and a second unique address, and wherein generating the plurality of unique addresses comprises:

using a first predefined logic and the first addressing scheme to generate the first unique address; and

using a second predefined logic and a second addressing scheme to generate the second unique address, wherein the first addressing scheme is different from the second addressing scheme.

5. A device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the device to;

generate, using a seed code stored by the device, a plurality of unique addresses for the device, wherein each unique address of the plurality of unique addresses is compliant with a different addressing scheme;

store the plurality of unique addresses;

determine a first addressing scheme used to direct a data transmission to the device; and

retrieve, from among the plurality of unique addresses, a first unique address that is compliant with the first addressing scheme used to direct the data transmission to the device.

6. The device of claim 5, wherein:

the data transmission comprises a recipient identifier; and

the instructions, when executed by the one or more processors, further cause the device to evaluate whether the first unique address corresponds to the recipient identifier.

7. The device of claim 6, wherein the instructions, when executed by the one or more processors, further cause the device to process the data transmission after determining that the first unique address corresponds to the recipient identifier.

8. The device of claim 5, wherein:

the plurality of unique addresses comprises the first unique address and a second unique address; and

wherein the instructions, when executed by the one or more processors, cause the device to generate the plurality of unique addresses at least by;

using a first predefined logic and the first addressing scheme to generate the first unique address; and

using a second predefined logic and a second addressing scheme to generate the second unique address, wherein the first addressing scheme is different from the second addressing scheme.

9. A method comprising:

storing, by a computing device, a first unique address of the computing device, wherein the first unique address was generated using a seed code stored by the computing device, and wherein the first unique address is compliant with a first addressing scheme;

receiving, by the computing device, a data transmission; and

responsive to a determination that a second addressing scheme used to direct the data transmission to the computing device is different from the first addressing scheme, generating, by the computing device and using the seed code, a second unique address of the computing device, the second unique address being compliant with the second addressing scheme.

10. The method of claim 9, further comprising:

storing, by the computing device, the second unique address with the first unique address.

11. The method of claim 9, wherein the data transmission comprises a recipient identifier, the method further comprising:

extracting, by the computing device, the recipient identifier from the data transmission; and

evaluating whether the recipient identifier corresponds to the second unique address.

12. The method of claim 11, further comprising:

discarding, by the computing device, the data transmission after determining that the recipient identifier does not correspond to the second unique address.

13. The method of claim 9, further comprising:

receiving, by the computing device, a second data transmission, wherein the second data transmission comprises a recipient identifier; and

responsive to a determination that the first addressing scheme is used to direct the second data transmission to the computing device, retrieving the first unique address for comparison with the recipient identifier.

14. A device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the device to;

store a first unique address of the device, wherein the first unique address was generated using a seed code stored by the device, and wherein the first unique address is compliant with a first addressing scheme;

receive a data transmission; and

responsive to a determination that a second addressing scheme used to direct the data transmission to the device is different from the first addressing scheme, generate, using the seed code, a second unique address of the device, the second unique address being compliant with the second addressing scheme.

15. The device of claim 14, wherein the instructions, when executed by the one or more processors, further cause the device to store the second unique address with the first unique address.

16. The device of claim 14, wherein:

the data transmission comprises a recipient identifier; and

the instructions, when executed by the one or more processors, further cause the device to;

extract the recipient identifier from the data transmission; and

evaluate whether the recipient identifier corresponds to the second unique address.

17. The device of claim 16, wherein the instructions, when executed by the one or more processors, further cause the device to discard the data transmission after determining that the recipient identifier does not correspond to the second unique address.

18. The device of claim 14, wherein the instructions, when executed by the one or more processors, further cause the device to:

receive a second data transmission, wherein the second data transmission comprises a recipient identifier; and

responsive to a determination that the first addressing scheme is used to direct the second data transmission to the device, retrieve the first unique address for comparison with the recipient identifier.