Apparatus for entitling and transmitting service instances to remote client devices

• US 7,860,250 B2
• Filed: 12/03/2008
• Issued: 12/28/2010
• Est. Priority Date: 05/24/2002
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Scientific-Atlanta LLC (Cisco Systems, Inc.)
• Inventors: Pinder, Howard G., Russ, Samuel H., Gaul, Michael A., Wasilewski, Anthony J.
• Primary Examiner(s): SMITHERS, MATTHEW
• Application Number:
  US12/327,157
• Publication Number:
  US 20090089369A1
• Time in Patent Office: 755 Days
• Field of Search: 380/211, 380/234
• US Class Current: 380/234
• CPC Class Codes: H04L 12/2803 Home automation networks
• CPC Class Codes: H04L 12/2805 Home Audio Video Interoperability [HAVI] networks
• CPC Class Codes: H04N 21/234309 by transcoding between formats or standards, e.g. from MPEG-2 to MPEG-4 or from Quicktime to Realvideo conversion of standards in analog television systems H04N7/01
• CPC Class Codes: H04N 21/2347 involving video stream encryption
• CPC Class Codes: H04N 21/23608 Remultiplexing multiplex streams, e.g. involving modifying time stamps or remapping the packet identifiers
• CPC Class Codes: H04N 21/41265 having a remote control device for bidirectional communication between the remote control device and client device unidirectional remote control device H04N21/42204
• 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/4344 Remultiplexing of multiplex streams, e.g. by modifying time stamps or remapping the packet identifiers
• CPC Class Codes: H04N 21/43615 Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals home Audio Video Interoperability [HAVI] data switching networks H04L12/2805
• CPC Class Codes: H04N 21/43637 involving a wireless protocol, e.g. Bluetooth, RF or wireless LAN [IEEE 802.11] arrangements for wireless networking or broadcasting of information in indoor or near-field type systems H04B10/114
• CPC Class Codes: H04N 21/4367 Establishing a secure communication between the client and a peripheral device or smart card
• CPC Class Codes: H04N 21/4405 involving video stream decryption
• CPC Class Codes: H04N 21/4408 involving video stream encryption, e.g. re-encrypting a decrypted video stream for redistribution in a home network
• CPC Class Codes: H04N 21/4623 Processing of entitlement messages, e.g. ECM [Entitlement Control Message] or EMM [Entitlement Management Message] arrangements for conditional access to broadcast information or to broadcast-related services H04H60/14
• CPC Class Codes: H04N 21/472 End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content end-user interfaces for retrieving video data from a database G06F16/739; network services for supporting unicast streaming H04L65/612
• CPC Class Codes: H04N 21/47815 Electronic shopping payment schemes, payment architectures or payment protocols for electronic shopping systems G06Q20/12
• CPC Class Codes: H04N 21/482 End-user interface for program selection broadcast systems using EPGs H04H60/72
• CPC Class Codes: H04N 21/8586 by using a URL processing chained hypermedia data for information retrieval G06F16/94; information retrieval from the Internet by using URLs G06F16/955; URL in broadcast information H04H20/93; Web-based protocols H04L67/02
• CPC Class Codes: H04N 7/162 Authorising the user terminal, e.g. by paying; Registering the use of a subscription channel, e.g. billing
• CPC Class Codes: H04N 7/163 by receiver means only
• CPC Class Codes: H04N 7/1675 : Providing digital key or authorisation information for generation or regeneration of the scrambling sequence pseudo-random number generators in general G06F7/58

Abstract

A server in a subscriber television network receives service instances from a headend of the subscriber television network. The server is adapted to encrypt according to an encryption scheme and re-transmit service instances to a client-receiver. The server reformats the service instance from a first format into a second format the client-receiver can access the service instance.

Claims

1. A system for transmitting service instances comprising:

a local network at a subscriber premises including;

at least one remote client device to request service instances; and

a communications device coupled to said at least one remote client device and including;

a memory;

store logic to receive a service instance from a headend and store the service instance in the memory;

request logic to receive a request for the stored service instance from a remote client device; and

service logic to determine whether the requesting remote client device is entitled to receive the requested stored service instance, and responsive to determining the requesting remote client device is entitled to receive the requested stored service instance, to transmit the requested service instance to the requesting remote client device.

2. The system of claim 1, wherein said communications device further includes:

device type logic to determine a device type for the requesting remote client device; and

reformat logic to determine a format protocol for the requested service instance using the determined device type, and to reformat the requested service instance prior to transmitting the requested service instance.

3. The system of claim 1, wherein the communications device further includes:

encryption logic to determine an encryption scheme for the requested service instance based on the requesting remote client device, and prior to transmitting the requested service instance, to encrypt the requested service instance.

4. The system of claim 3, wherein the communications device further includes:

scheme logic to receive a message along with the request from the requesting remote client device, the message having device type information regarding the requesting remote client device, and to determine from the device type information the encryption scheme for encryption of the requested service instance.

5. The system of claim 3, wherein the communications device further includes:

message logic to receive a message along with the request from the requesting remote client device, the message having device type information regarding the requesting remote client device; and

headend logic to transmit a second message to the headend, the second message having the device type information included therein, to enable the headend to determine the encryption scheme using at least the device type information.

6. A system for transmitting service instances comprising:

a local network at a subscriber premises including;

at least one remote client device to request service instances; and

a communications device coupled to said at least one remote client device and including;

request logic to receive a request for a service instance from a remote client device and determine whether the requesting remote client device is entitled to receive the requested service instance; and

service logic to determine whether the requested service instance is accessible within the communications device in response to determining the remote client device is entitled to receive the requested service instance, and if the requested service instance is accessible, to transmit the service instance to the requesting remote client device, and if the requested service instance is not accessible, to send a request to a headend for the requested service instance, and to transmit the service instance to the requesting remote client device upon receipt of the service instance from the headend.

7. The system of claim 6, wherein the communications device further includes:

store logic to store the received service instance in a memory of the communications device prior to transmitting the service instance to the requesting remote client device.

8. The system of claim 6, wherein the communications device further includes:

device type logic to determine a device type for the requesting remote client device; and

reformat logic to determine a format protocol for the requested service instance using the determined device type, and to reformat the requested service instance prior to transmitting the requested service instance.

9. The system of claim 6, wherein the communications device further includes:

encryption logic to determine an encryption scheme for the requested service instance based on the requesting remote client device, and prior to transmitting the requested service instance, to encrypt the requested service instance.

10. The system of claim 9, wherein the communications device further includes:

scheme logic to receive a message along with the request from the requesting remote client device, the message having device type information regarding the requesting remote client device, and to determine from the device type information the encryption scheme for encryption of the requested service instance.

11. The system of claim 9, wherein the communications device further includes:

message logic to receive a message along with the request from the requesting remote client device, the message having device type information regarding the requesting remote client device; and

headend logic to transmit a second message to the headend, the second message having the device type information included therein, to enable the headend to determine the encryption scheme using at least the device type information.

12. A system for transmitting service instances comprising:

a local network at a subscriber premises including;

a plurality of remote client devices to request service instances; and

a communications device coupled to said plurality of remote client devices and including;

first request logic to receive a first request for a service instance from a first remote client device;

first service logic to determine whether the first remote client device is entitled to receive the requested service instance, and responsive to determining the first remote client device is entitled to receive the requested service instance, to transmit the requested service instance to the first remote client device;

second request logic to receive a second request for the service instance from a second remote client device in the local network; and

second service logic to determine whether the second remote client device is entitled to receive the requested service instance, and responsive to determining the second remote client device is entitled to receive the requested service instance, to transmit the requested service instance to the second remote client device based upon local availability of the requested service instance within the communications device.

13. The system of claim 12, wherein the communications device further includes:

device type logic to determine a device type for each of the first and second remote client devices; and

reformat logic to determine a format protocol for the requested service instance using the device type of the first and second remote client devices, and to reformat the requested service instance prior to transmitting the requested service instance.

14. The system of claim 12, wherein the communications device further includes:

encryption logic to determine an encryption scheme for the requested service instance based on the first and second remote client devices, and prior to transmitting the requested service instance, to encrypt the requested service instance.

15. The system of claim 14, wherein the communications device further includes:

scheme logic to receive a message along with the request from each of the first and second remote client devices, the message having device type information regarding the respective remote client device, and to determine from the device type information the encryption scheme for encryption of the requested service instance.

16. The system of claim 12, wherein the communications device further includes:

message logic to receive a message along with the request from each of the first and second remote client devices, the message having device type information regarding the respective remote client device; and

headend logic to transmit a second message to a headend, the second message having the device type information included therein, to enable the headend to determine an encryption scheme using at least the device type information.

17. The system of claim 16, wherein the device type information from each of the first and second remote devices includes the same encryption scheme or a different encryption scheme.

18. The system of claim 12, wherein the communications device further includes:

headend logic to determine whether the requested service instance is accessible within the communications device prior to transmitting the requested service instance to the first remote client device, and if the requested service instance is not accessible, to send a request to a headend for the requested service instance and to transmit the service instance to the first remote client device upon receipt of the service instance.

19. The system of claim 18, wherein the requested service instance is accessible if the service instance is stored in a memory of the communications device.

20. The system of claim 18, wherein the communications device further includes:

store logic to store the received service instance in a memory of the communications device prior to transmitting the service instance to the first remote client device.

21. Logic encoded in one or more nontransitory media of a memory device for execution to transmit service instances to a remote client device in a local network, including a communications device and one or more of said remote client devices, at a subscriber premises, and when executed operable for:

receiving a service instance at the communications device of the subscriber premises from a headend, wherein the service instance is stored in memory of the communications device;

receiving a request at the communications device for the stored service instance from the remote client device;

determining whether the remote client device is entitled to receive the requested stored service instance; and

responsive to determining the remote client device is entitled to receive the requested stored service instance, transmitting the requested service instance from the communications device to the remote client device.

22. The logic of claim 21, further operable for:

determining a device type for the remote client device;

using the device type of the remote client device to determine a format protocol for the requested service instance; and

reformatting the requested service instance prior to transmitting the requested service instance.

23. The logic of claim 21, further operable for:

determining an encryption scheme for the requested service instance based on the remote client device; and

prior to transmitting the requested service instance, encrypting the requested service instance.

24. The logic of claim 23, further operable for:

receiving a message along with the request from the remote client device, the message having device type information regarding the remote client device; and

determining from the device type information the encryption scheme for encryption of the requested service instance.

25. The logic of claim 23, further operable for:

receiving a message along with the request from the remote client device, the message having device type information regarding the remote client device; and

transmitting a second message to the headend, the second message having the device type information included therein, wherein the headend determines the encryption scheme using at least the device type information.

26. Logic encoded in one or more nontransitory media of a memory device for execution to transmit service instances to a remote client device in a local network, including a communications device and one or more of said remote client devices, at a subscriber premises, and when executed operable for:

receiving a request at the communications device of the subscriber premises for a service instance from the remote client device;

determining whether the remote client device is entitled to receive the requested service instance;

responsive to determining the remote client device is entitled to receive the requested service instance, determining whether the requested service instance is accessible within the communications device;

if the requested service instance is accessible, transmitting the service instance from the communications device to the remote client device; and

if the requested service instance is not accessible, sending a request from the communications device to a headend for the requested service instance, wherein upon receipt of the service instance at the communications device, transmitting the service instance from the communications device to the remote client device.

27. The logic of claim 26, further operable for, prior to transmitting the service instance to the remote client device, storing the received service instance in memory of the communications device.

28. The logic of claim 26, further operable for:

determining a device type for the remote client device;

using the device type of the remote client device to determine a format protocol for the requested service instance; and

reformatting the requested service instance prior to transmitting the requested service instance.

29. The logic of claim 26, further operable for:

determining an encryption scheme for the requested service instance based on the remote client device; and

prior to transmitting the requested service instance, encrypting the requested service instance.

30. The logic of claim 29, further operable for:

receiving a message along with the request from the remote client device, the message having device type information regarding the remote client device; and

determining from the device type information the encryption scheme for encryption of the requested service instance.

31. The logic of claim 29, further operable for:

receiving a message along with the request from the remote client device, the message having device type information regarding the remote client device; and

transmitting a second message to the headend, the second message having the device type information included therein, wherein the headend determines the encryption scheme using at least the device type information.

32. Logic encoded in one or more nontransitory media of a memory device for execution to transmit service instances to a plurality of remote client devices in a local network, including a communications device, at a subscriber premises, and when executed operable for:

receiving a first request for a service instance at the communications device of the subscriber premises from a first remote client device;

determining whether the first remote client device is entitled to receive the requested service instance;

responsive to determining the first remote client device is entitled to receive the requested service instance, transmitting the requested service instance from the communications device to the first remote client device;

receiving a second request for the service instance at the communications device from a second remote client device in the local network;

determining whether the second remote client device is entitled to receive the requested service instance; and

responsive to determining the second remote client device is entitled to receive the requested service instance, transmitting the requested service instance from the communications device to the second remote client device based upon local availability of the requested service instance within the communications device.

33. The logic of claim 32, further operable for:

determining a device type for each of the first and second remote client devices;

using the device type of the first and second remote client devices to determine a format protocol for the requested service instance; and

reformatting the requested service instance prior to transmitting the requested service instance.

34. The logic of claim 32, further operable for:

determining an encryption scheme for the requested service instance based on the first and second remote client devices; and

prior to transmitting the requested service instance, encrypting the requested service instance.

35. The logic of claim 34, further operable for:

receiving a message along with the request from each of the first and second remote client devices, the message having device type information regarding the respective remote client device; and

determining from the device type information the encryption scheme for encryption of the requested service instance.

36. The logic of claim 32, further operable for:

receiving a message along with the request from each of the first and second remote client devices, the message having device type information regarding the respective remote client device; and

transmitting a second message to a headend, the second message having the device type information included therein, wherein the headend determines an encryption scheme using at least the device type information.

37. The logic of claim 36, wherein the device type information from each of the first and second remote devices includes the same encryption scheme or a different encryption scheme.

38. The logic of claim 32, further operable for:

prior to transmitting the requested service instance to the first remote client device, determining whether the requested service instance is accessible within the communications device; and

if the requested service instance is not accessible, sending a request to a headend for the requested service instance, wherein upon receipt of the service instance, transmitting the service instance from the communications device to the first remote client device.

39. The logic of claim 38, wherein the requested service instance is accessible if the service instance is stored in memory of the communications device.

40. The logic of claim 38, further operable for, prior to transmitting the service instance to the first remote client device, storing the received service instance in memory of the communications device.