Service gateway for interactive television

• US 7,484,236 B2
• Filed: 02/01/2002
• Issued: 01/27/2009
• Est. Priority Date: 02/02/2001
• Status: Active Grant

• Current Assignee: OpenTV, Inc. (Kudelski SA)
• Original Assignee: OpenTV, Inc. (Kudelski SA)
• Inventors: Lam, Waiman, Delpuch, Alain, Huntington, Matthew, Dureau, Vincent, Alao, Rachad, Kidd, Taylor, Henrard, Jose
• Primary Examiner(s): Kelley, Chris
• Assistant Examiner(s): Newlin, Timothy R
• Application Number:
  US10/061,114
• Publication Number:
  US 20020138848A1
• Time in Patent Office: 2,552 Days
• Field of Search: 725/78, 725/82, 725/80, 725/151, 725/60, 725/147, 725/117, 725/131, 725/127, 725/105
• US Class Current: 725/105
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/613 for the control of the source by the destination control signals issued by the client directed to the server or network components specially adapted for selective content distribution H04N21/637
• CPC Class Codes: H04L 65/752 adapting media to network capabilities
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04N 21/235 Processing of additional data, e.g. scrambling of additional data or processing content descriptors
• CPC Class Codes: H04N 21/238 Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams hybrid fiber coaxial [HFC] networks for downstream channel allocation for video distribution H04L12/2801; flow control in packet networks H04L47/10; real-time communication protocols in data switching networks H04L65/00; scheduling or organising the servicing of application requests H04L67/60
• CPC Class Codes: H04N 21/2385 Channel allocation H04N21/266 takes precedence; Bandwidth allocation H04N21/24 takes precedence ; allocation of channels according to the instantaneous demands of the users in time-division multiplex systems H04J3/1682; admission control, resource allocation in open networks H04L12/5692; arrangements for maintenance or administration in data switching networks involving bandwidth and capacity management H04L41/0896; negotiating bandwidth in wireless networks H04W28/16
• CPC Class Codes: H04N 21/2402 Monitoring of the downstream path of the transmission network, e.g. bandwidth available traffic monitoring in data switching networks H04L43/00; monitoring data switching networks utilization H04L43/0876
• CPC Class Codes: H04N 21/2542 for selling goods, e.g. TV shopping payment schemes, payment architectures or payment protocols for electronic shopping systems G06Q20/12
• CPC Class Codes: H04N 21/25858 involving client software characteristics, e.g. OS identifier
• CPC Class Codes: H04N 21/25875 involving end-user authentication restricting access to computer systems by authenticating users using a predetermined code G06F21/33; arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system H04L9/32; networks authentication protocols H04L63/08; authentication in wireless network security H04W12/06
• CPC Class Codes: H04N 21/25891 being end-user preferences retrieval of video data in a video database based on user preferences G06F16/739; arrangements for recognizing users' preferences H04H60/46; user profiles in network data switching protocols H04L67/306; processing of user preferences or user profiles in wireless networks H04W8/18
• CPC Class Codes: H04N 21/2668 Creating a channel for a dedicated end-user group, e.g. insertion of targeted commercials based on end-user profiles information retrieval from the Internet by querying with filtering and personalisation G06F16/9535; arrangements for replacing or switching information during the broadcast H04H20/10; push services over packet-switching network H04L12/1859; adaptation of message content in packet-switching networks H04L51/063
• 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/437 Interfacing the upstream path of the transmission network, e.g. for transmitting client requests to a VOD server flow control in data networks H04L47/10; streaming protocols, e.g. RTP or RTCP, H04L65/65; scheduling or organising the servicing of application requests in data packet switching networks H04L67/60
• CPC Class Codes: H04N 21/438 Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving encoded video stream packets from an IP network
• CPC Class Codes: H04N 21/643 Communication protocols network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP], H04L65/65
• CPC Class Codes: H04N 21/64707 : for transferring content from a first network to a second network, e.g. between IP and wireless
• CPC Class Codes: H04N 21/812 : involving advertisement data advertising per se G06Q30/02
• CPC Class Codes: H04N 21/8126 : involving additional data, e.g. news, sports, stocks, weather forecasts
• CPC Class Codes: H04N 21/84 : Generation or processing of descriptive data, e.g. content descriptors systems specially adapted for using meta-information in broadcast systems H04H60/73
• CPC Class Codes: H04N 21/8543 : using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML] information retrieval of semistructured data, the underlying structure being taken into account, e.g. mark-up language structure data G06F16/80
• CPC Class Codes: H04N 21/8545 : for generating interactive applications
• CPC Class Codes: H04N 7/17309 : Transmission or handling of upstream communications

Abstract

A service gateway provides a proxy between a client protocol and a plurality of standard communication protocols. The service gateway provides asymmetrical routing, data compression and encryption to optimize client processing power and communication link bandwidth. The service gateway enables content translation between clients and service providers. The service gateway keeps track of client available memory and sequence numbers in messages to generate error codes when applicable. A store and forward message capability is provided along with abstract session identifiers. The service gateway supports user datagram protocol.

Claims

1. A computer readable medium containing instructions that cause a computer to:

retrieve a client device hardware identifier for the client device from the client device dependant transport layer;

store the client device hardware identifier in a network operator hardware identifier list;

authenticate the client device hardware identifier before establishing a communication session between the server and the client device;

receive a first message containing at least one of application code, control, data, and audio/visual data at a server in a service provider compatible protocol;

translate the first message into a client device compatible protocol;

generate a sequence number in the first message at the server before sending the first message to the client device;

send the first message to the client device over at least one of a broadcast carrier wave, local area network and point to point connection;

store the sequence number along with a time stamp in the client device upon receipt of the first message at the client device;

reject the first message at the client device if the sequence number appears within a sliding time rejection window to avoid duplicate receipt of the first message;

send a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server;

receive the second message at the server;

generate a session identifier from the client device hardware identifier;

inserting the session identifier in place of the client device hardware identifier in the second message;

translate the second message into the service provider compatible protocol; and

send the translated message from the server to the service provider.

2. The medium of claim 1 further comprising instructions that cause the computer to:

determine whether to send the first message over the broadcast carrier wave or the point to point connection based on broadcast carrier wave and point to point connection latency, broad cast stream and point to point connection loading conditions and message size.

3. The medium of claim 1 further comprising instructions that cause the computer to:

store the second message for transmission upon satisfaction of a timing constraint comprising at a least one of as soon as possible, when connected, after a random period of time, after a set period of time, after the occurrence of an event, after occurrence of a message, and spread over available bandwidth.

4. The medium of claim 3 wherein the first message and second message comprise an ecommerce transaction.

5. The medium of claim 1 further comprising instructions that cause the computer to:

encapsulate HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server;

convert the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

receive a cookie from a service provider via a HTTP server at the server in response to the converted HTTP message;

caching the cookie at the server;

generate a cookie to session identifier translation table;

use the cookie to session identifier table to answer a client device hardware identifier name request from the HTTP server; and

use the client device hardware identifier to extract user information from a central registry.

6. The medium of claim 5 wherein the first message comprises HTTP over TCP/IP and the second message comprises LHTTP over DATP.

7. The medium of claim 1 wherein the server sends a business filter to the client device to select information to be captured from input to the client device based on at least one of client preferences, viewer profiles and transaction history.

8. The medium of claim 1 further comprising instructions that cause the computer to:

complete an ecommerce transaction between a user at the client device and the service provider when the client device is offline.

9. The medium of claim 1 further comprising instructions that cause the computer to:

send a third message to the client device requesting a quantity of memory available at the client device; and

checking a message size of a fourth message directed to the client device to verify that the quantity of available memory at the client device is sufficient to receive the fourth message before forwarding the fourth message to the client device.

10. The medium of claim 1 further comprising instructions that cause the computer to:

resolve a request to a data name service for resolving a service identifier identifying a service provider in a transport communication protocol message.

11. The medium of claim 1 further comprising instructions that cause the computer to:

provide a socket type abstraction layer to accommodate User Datagram Protocol (UDP) data, wherein the socket type abstraction layer runs on top of UDP and encapsulates UDP into transport level protocol messages.

12. The medium of claim 1 further comprising instructions that cause the computer to:

authenticate multiple users at the client device using nicknames, personal identifiers and the client device hardware identifier.

13. The medium of claim 1 further comprising instructions that cause the computer to:

control, in a business agent, access to client device user information in an ecommerce transaction between a service provider and a client device user, wherein the amount and type of client business information provided to the service provider is guided by a business rule depending on an agreement between the service provider and a network operator.

14. A computer readable medium containing instructions that when executed cause a computer to:

retrieve a client device hardware identifier for a client device from the client device dependent transport laver;

send the client device hardware identifier to an identifier list for storage for authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

receive a first message from the server at the client device over at least one of a broadcast carrier wave, local area network and point to point connection, containing at least one of application code, control, data, and audio/visual data in a service provider compatible protocol, wherein the first message has been compressed and translated into the client device compatible protocol at the server from the service provider compatible protocol, the client device compatible protocol being different from the service provider compatible protocol;

send a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider;

generate a sequence number in the first message at the server before sending the first message to the client device;

store the sequence number along with a time stamp in the client device upon receipt of the first message at the client device; and

reject the first message at the client device if the sequence number appears within a sliding time rejection window to avoid duplicate receipt of the first message.

15. The medium of claim 14 further comprising instructions that cause the computer to:

send an uncompressed second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for translation of the uncompressed second message into the service provider compatible protocol for transmission to the service provider.

16. The medium of claim 15 wherein the first message is encrypted and encapsulated into the client device compatible protocol and a flag set in the first message indicating that the message is encrypted at the server prior to receipt of the first message at the client device, further comprising instruction that cause the computer to:

decrypt the encrypted first message at the client device.

17. The medium of claim 16 wherein the first message has been divided in to fragments which have been individually encrypted at the sewer prior to receipt of the first message at the client device.

18. The medium of claim 14 wherein the client device compatible protocol is compatible with a native transport layer in the client device.

19. The medium of claim 14 further comprising instructions that cause the computer to:

control message flow rate by controlling the transmission bit rate.

20. The medium of claim 14 further comprising instructions that cause the computer to:

determine whether to receive the first message over the broadcast carrier wave or the point to point connection based on broadcast carrier wave and point to point connection latency, broad cast stream and point to point connection loading conditions and message size.

21. The medium of claim 14 further comprising instructions that cause the computer to:

store the second message for transmission upon satisfaction of a timing constraint comprising at a least one of as soon as possible, when connected, after a random period of time, after a set period of time, after the occurrence of an event, after occurrence of a message, and spread over available bandwidth.

22. The medium of claim 21 wherein the first message and second message comprise an ecommerce transaction.

23. The medium of claim 14 further comprising instructions that cause the computer to:

encapsulate HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server for converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

send the session identifier to the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

24. The medium of claim 23 wherein the first message comprises HTTP over TCP/IP and the second message comprises LHTTP over DATP.

25. The medium of claim 14 wherein the client device receives a business filter from the server to select information to be captured from input to the client device based on at least one of client preferences, viewer profiles and transaction history.

26. The medium of claim 14 further comprising instructions that cause the computer to:

completing an ecommerce transaction between a user at the client device and the service provider when the client device is offline.

27. The medium of claim 14 further comprising instructions that cause the computer to:

receive a third message at the client device requesting a quantity of memory available at the client device; and

check a message size of a fourth message directed to the client device to verify that the quantity of available memory at the client device is sufficient to receive the fourth message before forwarding the fourth message to the client device.

28. The medium of claim 14 further comprising instructions that cause the computer to:

resolve request to a data name service for resolving a service identifier identifying a service provider in a transport communication protocol message.

29. The medium of claim 14 further comprising instructions that cause the computer to:

provide a socket type abstraction layer to accommodate User Datagram Protocol (UDP) data, wherein the socket type abstraction layer runs on top of UDP and encapsulates UDP into transport level protocol messages.

30. The medium of claim 14 further comprising instructions that cause the computer to:

authenticate multiple users at the client device using nicknames, personal identifiers and the client device hardware identifier.

31. The medium of claim 14 further comprising instructions that cause the computer to:

control, in a business agent, access to client device user information in an ecommerce transaction between a service provider and a client device user, wherein the amount and type of client business information provided to the service provider is guided by a business rule depending on an agreement between the service provider and a network operator.

32. A computer readable medium containing instructions that when executed cause a computer to:

send a client device hardware identifier retrieved from the client device dependent transport layer, to a server identifier list for storage and authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

send a first message containing at least one of application code, control, data, and audio/visual data at the client device from the server over at least one of a broadcast carrier wave, local area network and point to point connection, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol;

generate a sequence number in the first message at the server before sending the first message to the client device for storing the sequence number along with a time stamp in the client device upon receipt of the first message at the client device for rejection of the first message at the client device if the sequence number appears within a sliding time rejection window to avoid duplicate receipt of the first message; and

receive a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider.

33. The medium of claim 32 further comprising instructions that cause the computer to:

determine whether to send the first message from the server to the client device over the broadcast carrier wave or the point to point connection based on broadcast carrier wave and point to point connection latency, broad cast stream and point to point connection loading conditions and message size.

34. The medium of claim 32 further comprising instructions that cause the computer to:

store, at the server the second message for transmission upon satisfaction of a timing constraint comprising at a least one of as soon as possible, when connected, after a random period of time, after a set period of time, after the occurrence of an event, after occurrence of a message, and spread over available bandwidth.

35. The medium of claim 34 wherein the first message and second message comprise an ecommerce transaction.

36. The medium of claim 32 further comprising instructions that cause the computer to:

receive at the server, HTTP encapsulated in the device compatible protocol in the second message;

convert the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

receive the session identifier at the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

37. The medium of claim 36 wherein the first message comprises HTTP over TCP/IP and the second message comprises LHTTP over DATP.

38. The medium of claim 32 further comprising instructions that cause the computer to:

send a business filter from the server to the client device to select information to be captured from input to the client device based on at least one of client preferences, viewer profiles and transaction history.

39. The medium of claim 32 further comprising instructions that cause the computer to:

complete an ecommerce transaction between a user at the client device and the service provider when the client device is offline.

40. The medium of claim 32 further comprising instructions that cause the computer to:

send a third message to the client device requesting a quantity of memory available at the client device; and

check a message size of a fourth message directed to the client device to verify that the quantity of available memory at the client device is sufficient to receive the fourth message before forwarding the fourth message to the client device.

41. The medium of claim 32 further comprising instructions that cause the computer to:

resolve a request to a data name service for resolving a service identifier identifying a service provider in a transport communication protocol message.

42. The medium of claim 32 further comprising instructions that cause the computer to:

provide a socket type abstraction layer in the server to accommodate User Datagram Protocol (UDP) data, wherein the socket type abstraction layer runs on top of UDP and encapsulates UDP into transport level protocol messages.

43. The medium of claim 32 further comprising instructions that cause the computer to:

authenticate at the server, multiple users at the client device using nicknames, personal identifiers and the client device hardware identifier.

44. The medium of claim 32 further comprising instructions that cause the computer to:

control, in a business agent in the server, access to client device user information in an ecommerce transaction between the service provider and the client device user, wherein the amount and type of client business information provided to the service provider is guided by a business rule depending on an agreement between the service provider and a network operator.

45. A method for communication in a distributed computing system comprising:

retrieving a client device hardware identifier for the client device from the client device dependant transport layer;

storing the client device hardware identifier in a network operator hardware identifier list;

authenticating the client device hardware identifier before establishing a communication session between the server and the client device;

receiving a first message containing at least one of application code, control, data, and audio/visual data at a server in a service provider compatible protocol;

translating the first message into a client device compatible protocol;

generating a sequence number in the first message at the server before sending the first message to the client device;

sending the first message to the client device over at least one of a broadcast carrier wave, local area network and point to point connection;

storing the sequence number along with a time stamp in the client device upon receipt of the first message at the client device; and

rejecting the first message at the client device if the sequence number appears within a sliding time rejection window to avoid duplicate receipt of the first message;

sending a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the sewer;

receiving the second message at the server;

generating a session identifier from the client device hardware identifier;

inserting the session identifier in place of the client device hardware identifier in the second message;

translating the second message into the service provider compatible protocol; and

sending the translated message from the server to the service provider.

46. The method of claim 45 further comprising:

determining whether to send the first message over the broadcast carrier wave or the point to point connection based on broadcast carrier wave and point to point connection latency, broad cast stream and point to point connection loading conditions and message size.

47. The method of claim 45 further comprising:

storing the second message for transmission upon satisfaction of a timing constraint comprising at a least one of as soon as possible, when connected, after a random period of time, after a set period of time, after the occurrence of an event, after occurrence of a message, and spread over available bandwidth.

48. The method of claim 47 wherein the first message and second message comprise an ecommerce transaction.

49. The method of claim 45 further comprising:

encapsulating HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server;

converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

receiving a cookie from a service provider via a HTTP server at the server in response to the converted HTTP message;

caching the cookie at the server;

generating a cookie to session identifier translation table;

using the cookie to session identifier table to answer a client device hardware identifier name request from the HTTP server; and

using the client device hardware indentifer to extract user information from a central registry.

50. The method claim 49 wherein the first message comprises HTTP over TCP/IP and the second message comprises LHTTP over DATP.

51. The method claim 45 wherein the server sends a business filter to the client device to select information to be captured from input to the client device based on at least one of client preferences, viewer profiles and transaction history.

52. The method of claim 45 further comprising:

completing an ecommerce transaction between a user at the client device and the service provider when the client device is offline.

53. The method of claim 45 further comprising:

sending a third message to the client device requesting a quantity of memory available at the client device; and

checking a message size of a fourth message directed to the client device to verify that the quantity of available memory at the client device is sufficient to receive the fourth message before forwarding the fourth message to the client device.

54. The method of claim 45 further comprising:

a data name service for resolving a service identifier identifying a service provider in a transport communication protocol message.

55. The method of claim 45 further comprising:

providing a socket type abstraction layer to accommodate User Datagram Protocol (UDP) data, wherein the socket type abstraction layer runs on top of UDP and encapsulates UDP into transport level protocol messages.

56. The method of claim 45 further comprising:

authenticating multiple users at the client device using nicknames, personal identifiers and the client device hardware identifier.

57. The method of claim 45 further comprising:

controlling, in a business agent, access to client device user information in an ecommerce transaction between a service provider and a client device user, wherein the amount and type of client business information provided to the service provider is guided by a business rule depending on an agreement between the service provider and a network operator.

58. A method for communication in a distributed computing system comprising:

retrieving a client device hardware identifier for the client device from the client device dependant transport layer;

sending the client device hardware identifier to an identifier list for storage for authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

generating a sequence number in the first message at the server before sending the first message to the client device;

receiving the first message containing at least one of application code, control, data, and audio/visual data at the client device from a server over at least one of a broadcast carrier wave, local area network and point to point connection, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol;

storing the sequence number along with a time stamp in the client device upon receipt of the first message at the client device;

rejecting the first message at the client device if the sequence number appears within a sliding time rejection window to avoid duplicate receipt of the first message;

sending a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider.

59. The method of claim 58 further comprising:

determining whether to receive the first message over the broadcast carrier wave or the point to point connection based on broadcast carrier wave and point to point connection latency, broad cast stream and point to point connection loading conditions and message size.

60. The method of claim 58 further comprising:

storing the second message for transmission upon satisfaction of a timing constraint comprising at a least one of as soon as possible, when connected, after a random period of time, after a set period of time, after the occurrence of an event, after occurrence of a message, and spread over available bandwidth.

61. The method of claim 60 wherein the first message and second message comprise an ecommerce transaction.

62. The method of claim 58 further comprising:

encapsulating HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server for converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

sending the session identifier to the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

63. The method claim 62 wherein the first message comprises HTTP over TCP/IP and the second message comprises LHTTP over DATP.

64. The method claim 58 further comprising:

wherein the client device receives a business filter from the server to select information to be captured from input to the client device based on at least one of client preferences, viewer profiles and transaction history.

65. The method of claim 58 further comprising:

completing an ecommerce transaction between a user at the client device and the service provider when the client device is offline.

66. The method of claim 58 further comprising:

receiving a third message at the client device requesting a quantity of memory available at the client device; and

checking a message size of a fourth message directed to the client device to verify that the quantity of available memory at the client device is sufficient to receive the fourth message before forwarding the fourth message to the client device.

67. The method of claim 58 further comprising:

a data name service for resolving a service identifier identifying a service provider in a transport communication protocol message.

68. The method of claim 58 further comprising:

providing a socket type abstraction layer to accommodate User Datagram Protocol (UDP) data, wherein the socket type abstraction layer runs on top of UDP and encapsulates UDP into transport level protocol messages.

69. The method of claim 58 further comprising:

authenticating multiple users at the client device using nicknames, personal identifiers and the client device hardware identifier.

70. The method of claim 58 further comprising:

controlling, in a business agent, access to client device user information in an ecommerce transaction between a service provider and a client device user, wherein the amount and type of client business information provided to the service provider is guided by a business rule depending on an agreement between the service provider and a network operator.

71. A method for communication in a distributed computing system comprising:

sending a client device hardware identifier retrieved from the client device dependent transport layer, to a server identifier list for storage and authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

sending a first message containing at least one of application code, control, data, and audio/visual data at the client device from the server over at least one of a broadcast carrier wave, local area network and point to point connection, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol;

receiving a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider;

generating a sequence number in the first message at the server before sending the first message to the client device for storing the sequence number along with a time stamp in the client device upon receipt of the first message at the client device for rejection of the first message at the client device if the sequence number appears within a sliding time rejection window to avoid duplicate receipt of the first message.

72. The method of claim 71 further comprising:

determining whether to send the first message from the server to the client device over the broadcast carrier wave or the point to point connection based on broadcast carrier wave and point to point connection latency, broad cast stream and point to point connection loading conditions and message size.

73. The method of claim 71 further comprising:

storing, at the server the second message for transmission upon satisfaction of a timing constraint comprising at a least one of as soon as possible, when connected, after a random period of time, after a set period of time, after the occurrence of an event, after occurrence of a message, and spread over available bandwidth.

74. The method of claim 73 wherein the first message and second message comprise an ecommerce transaction.

75. The method of claim 71 further comprising:

receiving at the server, HTTP encapsulated in the device compatible protocol in the second message;

converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

receiving the session identifer at the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

76. The method claim 75 wherein the first message comprises HTTP over TCP/IP and the second message comprises LHTTP over DATP.

77. The method claim 71 further comprising:

sending a business filter from the server to the client device to select information to be captured from input to the client device based on at least one of client preferences, viewer profiles and transaction history.

78. The method of claim 71 further comprising:

completing an ecommerce transaction between a user at the client device and the service provider when the client device is offline.

79. The method of claim 71 further comprising:

sending a third message to the client device requesting a quantity of memory available at the client device; and

checking a message size of a fourth message directed to the client device to verify that the quantity of available memory at the client device is sufficient to receive the fourth message before forwarding the fourth message to the client device.

80. The method of claim 71 further comprising:

a data name service for resolving a service identifier identifying a service provider in a transport communication protocol message.

81. The method of claim 71 further comprising:

providing a socket type abstraction layer in the server to accommodate User Datagram Protocol (UDP) data, wherein the socket type abstraction layer runs on top of UDP and encapsulates UDP into transport level protocol messages.

82. The method of claim 71 further comprising:

authenticating at the server, multiple users at the client device using nicknames, personal identifiers and the client device hardware identifier.

83. The method of claim 71 further comprising:

controlling, in a business agent in the server, access to client device user information in an ecommerce transaction between the service provider and the client device user, wherein the amount and type of client business information provided to the service provider is guided by a business rule depending on an agreement between the service provider and a network operator.

84. An apparatus for communication in a distributed computing system comprising:

a client device hardware identifier for the client device retrieved from the client device dependant transport layer;

computer memory for storing the client device hardware identifier in a network operator hardware identifier list;

a authentication component for authenticating the client device hardware identifier before establishing a communication session between the server and the client device;

a server message handling component for receiving a first message containing at least one of application code, control, data, and audio/visual data at a server in a service provider compatible protocol and sending the first message to the client device over at least one of a broadcast carrier wave, local area network and point to point connection, the server message handling component further comprising translating a second message received from a client device into the service provider compatible protocol and sending the translated second message from the server to the service provider;

a server translation component for translating the first message into a client device compatible protocol;

a sequence number generated in the first message at the server before sending the first message to the client device;

computer memory for storing the sequence number along with a time stamp in the client device upon receipt of the first message at the client device;

a rejection component for rejecting the first message at the client device if the sequence number appears within a sliding time rejection window to avoid duplicate receipt of the first message;

a client device message handling component for sending the second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server; and

a server component for generating a session identifier from the client device hardware identifier and inserting the session identifier in place of the client device hardware identifier in the second message prior to sending the second message to the service provider.

85. The apparatus of claim 84 further comprising:

a server component for determining whether to send the first message over the broadcast carrier wave or the point to point connection based on broadcast carrier wave and point to point connection latency, broad cast stream and point to point connection loading conditions and message size.

86. The apparatus of claim 84 further comprising:

computer memory for storing the second message for transmission upon satisfaction of a timing constraint comprising at a least one of as soon as possible, when connected, after a random period of time, after a set period of time, after the occurrence of an event, after occurrence of a message, and spread over available bandwidth.

87. The apparatus of claim 86 wherein the first message and second message comprise an ecommerce transaction.

88. The apparatus of claim 84 further comprising:

a client device component for encapsulating HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server;

a HTTP conversion component for converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

computer memory for caching a cookie received from a service provider via a HTTP server at the server in response to the converted HTTP message;

a server component for generating a cookie to session identifier translation table and using the cookie to session identifier table to answer a client device hardware identifier name request from the HTTP server and using the client device hardware identifier to extract user information from a central registry.

89. The apparatus of claim 88 wherein the first message comprises HTTP over TCP/IP and the second message comprises LHTTP over DATP.

90. The apparatus of claim 84 wherein the server sends a business filter to the client device to select information to be captured from input to the client device based on at least one of client preferences, viewer profiles and transaction history.

91. The apparatus of claim 84 further comprising:

a server component for completing an ecommerce transaction between a user at the client device and the service provider when the client device is offline.

92. The apparatus of claim 84 further comprising:

a third message sent to the client device requesting a quantity of memory available at the client device; and

a component for checking a message size of a fourth message directed to the client device to verify that the quantity of available memory at the client device is sufficient to receive the fourth message before forwarding the fourth message to the client device.

93. The apparatus of claim 84 further comprising:

a data name service component for resolving a service identifier identifying a service provider in a transport communication protocol message.

94. The apparatus of claim 84 further comprising:

a socket type abstraction layer component to accommodate User Datagram Protocol (UDP) data, wherein the socket type abstraction layer runs on top of UDP and encapsulates UDP into transport level protocol messages.

95. The apparatus of claim 84 further comprising:

an authentication component for authenticating multiple users at the client device using nicknames, personal identifiers and the client device hardware identifier.

96. The apparatus of claim 84 further comprising:

a business agent for controlling access to client device user information in an ecommerce transaction between a service provider and a client device user, wherein the amount and type of client business information provided to the service provider is guided by a business rule depending on an agreement between the service provider and a network operator.

97. An apparatus for communication in a distributed computing system comprising:

a first message containing at least one of application code, control, data, and audio/visual data at a client device from a server, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol and sent the first message to the client device over at least one of a broadcast carrier wave, local area network and point to point connection;

a client device hardware identifier for the client device retrieved from the client device dependant transport layer;

a client device message handler for sending the client device hardware identifier to an identifier list for storage for authentication of the client device hardware identifier before establishing a communication session between the client device and a server, and sending a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider;

a sequence number in the first message at the server before sending the first message to the client device;

computer memory for storing the sequence number along with a time stamp in the client device upon receipt of the first message at the client device; and

a rejection component for rejecting the first message at the client device if the sequence number appears within a sliding time rejection window to avoid duplicate receipt of the first message.

98. The apparatus of claim 97 further comprising:

a client component for determining whether to receive the first message over the broadcast carrier wave or the point to point connection based on broadcast carrier wave and point to point connection latency, broad cast stream and point to point connection loading conditions and message size.

99. The apparatus of claim 97 further comprising:

computer memory for storing the second message for transmission upon satisfaction of a timing constraint comprising at a least one of as soon as possible, when connected, after a random period of time, after a set period of time, after the occurrence of an event, after occurrence of a message, and spread over available bandwidth.

100. The apparatus of claim 99 wherein the first message and second message comprise an ecommerce transaction.

101. The apparatus of claim 97 wherein the second message encapsulates HTTP in the device compatible protocol at the client device prior to sending the second message to the server for converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

a session identifier component for sending the session identifier to the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

102. The apparatus of claim 101 wherein the first message comprises HTTP over TCP/IP and the second message comprises LHTTP over DATP.

103. The apparatus claim 97 wherein the client device receives a business filter from the server to select information to be captured from input to the client device based on at least one of client preferences, viewer profiles and transaction history.

104. The apparatus of claim 97 further comprising:

a client component for completing an ecommerce transaction between a user at the client device and the service provider when the client device is offline.

105. The apparatus of claim 97 further comprising:

a third message at the client device requesting a quantity of memory available at the client device; and

a message size of a fourth message directed to the client device to verify that the quantity of available memory at the client device is sufficient to receive the fourth message before forwarding the fourth message to the client device.

106. The apparatus of claim 97 further comprising:

a data name service for resolving a service identifier identifying a service provider in a transport communication protocol message.

107. The apparatus of claim 97 further comprising:

a socket type abstraction layer to accommodate User Datagram Protocol (UDP) data, wherein the socket type abstraction layer runs on top of UDP and encapsulates UDP into transport level protocol messages.

108. The apparatus of claim 97 further comprising:

multiple users identifiers authenticated at the client device using nicknames, personal identifiers and the client device hardware identifier.

109. The apparatus of claim 97 further comprising:

a business agent for controlling access to client device user information in an ecommerce transaction between a service provider and a client device user, wherein the amount and type of client business information provided to the service provider is guided by a business rule depending on an agreement between the service provider and a network operator.

110. An apparatus for communication in a distributed computing system comprising:

a client device hardware identifier retrieved from the client device dependent transport layer, to a server identifier list for storage and authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

a first message sent from the server to the client device containing at least one of application code, control, data, and audio/visual data sent over at least one of a broadcast carrier wave, local area network and point to point connection, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol;

a sequence number in the first message at the server before sending the first message to the client device for storing the sequence number along with a time stamp in the client device upon receipt of the first message at the client device for rejection of the first message at the client device if the sequence number appears within a sliding time rejection window to avoid duplicate receipt of the first message;

a second message containing at least one of application code, control, data, and audio/visual data received from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider.

111. The apparatus of claim 110 further comprising:

a server routing component for determining whether to send the first message from the server to the client device over the broadcast carrier wave or the point to point connection based on broadcast carrier wave and point to point connection latency, broad cast stream and point to point connection loading conditions and message size.

112. The apparatus of claim 110 further comprising:

computer memory for storing at the server the second message for transmission upon satisfaction of a timing constraint comprising at a least one of as soon as possible, when connected, after a random period of time, after a set period of time, after the occurrence of an event, after occurrence of a message, and spread over available bandwidth.

113. The apparatus of claim 112 wherein the first message and second message comprise an ecommerce transaction.

114. The apparatus of claim 110 further comprising a converter for receiving the second message containing HTTP encapsulated in the device compatible protocol in the second message converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

a session identifier component for receiving the session identifier at the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

115. The apparatus of claim 114 wherein the first message comprises HTTP over TCP/IP and the second message comprises LHTTP over DATP.

116. The apparatus claim 110 further comprising:

a business filter from the server to the client device to select information to be captured from input to the client device based on at least one of client preferences, viewer profiles and transaction history.

117. The apparatus of claim 110 further comprising:

a server component for completing an ecommerce transaction between a user at the client device and the service provider when the client device is offline.

118. The apparatus of claim 110 further comprising:

a third message to the client device requesting a quantity of memory available at the client device; and

a message size of a fourth message directed to the client device to verify that the quantity of available memory at the client device is sufficient to receive the fourth message before forwarding the fourth message to the client device.

119. The apparatus of claim 110 further comprising:

a data name service for resolving a service identifier identifying a service provider in a transport communication protocol message.

120. The apparatus of claim 110 further comprising:

a socket type abstraction layer in the server to accommodate User Datagram Protocol (UDP) data, wherein the socket type abstraction layer runs on top of UDP and encapsulates UDP into transport level protocol messages.

121. The apparatus of claim 110 further comprising:

an authentication component authenticating at the server, multiple users at the client device using nicknames, personal identifiers and the client device hardware identifier.

122. The apparatus of claim 110 further comprising:

a business agent in the server, for controlling access to client device user information in an ecommerce transaction between the service provider and the client device user, wherein the amount and type of client business information provided to the service provider is guided by a business rule depending on an agreement between the service provider and a network operator.

123. A computer readable medium containing instructions that cause a computer to:

retrieve a client device hardware identifier for the client device from the client device dependant transport layer;

store the client device hardware identifier in a network operator hardware identifier list;

authenticate the client device hardware identifier before establishing a communication session between the server and the client device;

receive a first message containing at least one of application code, control, data, and audio/visual data at a server in a service provider compatible protocol;

translate the first message into a client device compatible protocol;

send the first message to the client device over at least one of a broadcast carrier wave, local area network and point to point connection;

send a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server;

receive the second message at the server;

generate a session identifier from the client device hardware identifier, inserting the session identifier in place of the client device hardware identifier in the second message;

translate the second message into the service provider compatible protocol; and

send the translated message from the server to the service provider;

encapsulate HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server;

convert the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

receive a cookie from a service provider via a HTTP server at the server in response to the converted HTTP message;

cache the cookie at the server;

generate a cookie to session identifier translation table;

use the cookie to session identifier table to answer a client device hardware identifier name request from the HTTP server; and

use the client device hardware identifier to extract user information from a central registry.

124. A computer readable medium containing instructions that when executed cause a computer to:

receive a first message from a server at a client device, containing at least one of application code, control, data, and audio/visual data in a service provider compatible protocol, wherein the first message has been compressed and translated into the client device compatible protocol at the server from the service provider compatible protocol, the client device compatible protocol being different from the service provider compatible protocol;

retrieve a client device hardware identifier for the client device from the client device dependant transport layer;

send the client device hardware identifier to an identifier list for storage for authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

receive a first message containing at least one of application code, control, data, and audio/visual data at the client device from a server, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol;

receive the first message at the client device over at least one of a broadcast carrier wave, local area network and point to point connection;

send a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider;

encapsulate HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server for converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

send the session identifier to the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

125. A computer readable medium containing instructions that when executed cause a computer to:

send a client device hardware identifier retrieved from the client device dependent transport layer, to a server identifier list for storage and authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

send a first message containing at least one of application code, control, data, and audio/visual data at the client device from the server over at least one of a broadcast carrier wave, local area network and point to point connection, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol;

receive a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider;

receive at the server, HTTP encapsulated in the device compatible protocol in the second message;

convert the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

receive the session identifier at the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

126. A method for communication in a distributed computing system comprising:

retrieving a client device hardware identifier for the client device from the client device dependant transport layer;

storing the client device hardware identifier in a network operator hardware identifier list;

authenticating the client device hardware identifier before establishing a communication session between the server and the client device;

receiving a first message containing at least one of application code, control, data, and audio/visual data at a server in a service provider compatible protocol;

translating the first message into a client device compatible protocol;

sending the first message to the client device over at least one of a broadcast carrier wave, local area network and point to point connection;

sending a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server;

receiving the second message at the server;

generating a session identifier from the client device hardware identifier;

inserting the session identifier in place of the client device hardware identifier in the second message;

translating the second message into the service provider compatible protocol; and

sending the translated message from the server to the service provider;

encapsulating HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server;

converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

receiving a cookie from a service provider via a HTTP server at the server in response to the converted HTTP message;

caching the cookie at the server;

generating a cookie to session identifier translation table;

using the cookie to session identifier table to answer a client device hardware identifier name request from the HTTP server; and

using the client device hardware indentifer to extract user information from a central registry.

127. A method for communication in a distributed computing system comprising:

retrieving a client device hardware identifier for the client device from the client device dependant transport layer;

sending the client device hardware identifier to an identifier list for storage for authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

receiving a first message containing at least one of application code, control, data, and audio/visual data at the client device from a server, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol;

receiving the first message at the client device over at least one of a broadcast carrier wave, local area network and point to point connection;

sending a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider;

encapsulating HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server for converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

sending the session identifier to the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

128. A method for communication in a distributed computing system comprising:

sending a client device hardware identifier retrieved from the client device dependent transport layer, to a server identifier list for storage and authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

sending a first message containing at least one of application code, control, data, and audio/visual data at the client device from the server over at least one of a broadcast carrier wave, local area network and point to point connection, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol;

receiving a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider;

receiving at the server, HTTP encapsulated in the device compatible protocol in the second message;

converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

receiving the session identifier at the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

129. An apparatus for communication in a distributed computing system comprising:

a client device hardware identifier for the client device retrieved from the client device dependant transport layer;

computer memory for storing the client device hardware identifier in a network operator hardware identifier list;

a authentication component for authenticating the client device hardware identifier before establishing a communication session between the server and the client device;

a server message handling component for receiving a first message containing at least one of application code, control, data, and audio/visual data at a server in a service provider compatible protocol and sending the first message to the client device over at least one of a broadcast carrier wave, local area network and point to point connection, the server message handling component further comprising translating a second message received from a client device into the service provider compatible protocol and sending the translated second message from the server to the service provider;

a server translation component for translating the first message into a client device compatible protocol;

a client device message handling component for sending the second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server; and

a server component for generating a session identifier from the client device hardware identifier and inserting the session identifier in place of the client device hardware identifier in the second message prior to sending the second message to the service provider;

a client device component for encapsulating HTTP in the device compatible protocol in the second message at the client device prior to sending the second message to the server;

a HTTP conversion component for converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

computer memory for caching a cookie received from a service provider via a HTTP server at the server in response to the converted HTTP message;

a server component for generating a cookie to session identifier translation table and using the cookie to session identifier table to answer a client device hardware identifier name request from the HTTP server and using the client device hardware identifier to extract user information from a central registry.

130. An apparatus for communication in a distributed computing system comprising:

a first message containing at least one of application code, control, data, and audio/visual data at the client device from a server, wherein the sewer translated the message from a service provider compatible protocol into the client device compatible protocol and sent the first message to the client device over at least one of a broadcast carrier wave, local area network and point to point connection;

a client device hardware identifier for the client device retrieved from the client device dependant transport layer;

a client device message handler for sending the client device hardware identifier to an identifier list for storage for authentication of the client device hardware identifier before establishing a communication session between the client device and a server, and sending a second message containing at least one of application code, control, data, and audio/visual data from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the sewer inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider;

wherein the second message encapsulates HTTP in the device compatible protocol at the client device prior to sending the second message to the server for converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

a session identifier component for sending the session identifier to the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.

131. An apparatus for communication in a distributed computing system comprising:

a client device hardware identifier retrieved from the client device dependent transport layer, to a server identifier list for storage and authentication of the client device hardware identifier before establishing a communication session between the client device and a server;

a first message sent from the server to the client device containing at least one of application code, control, data, and audio/visual data sent over at least one of a broadcast carrier wave, local area network and point to point connection, wherein the server translated the message from a service provider compatible protocol into the client device compatible protocol;

a second message containing at least one of application code, control, data, and audio/visual data received from the client device in the client device compatible protocol to the server for generating a session identifier from the client device hardware identifier, wherein the server inserts the session identifier in place of the client device hardware identifier in the second message and translates the second message into the service provider compatible protocol for sending the translated message to the service provider;

a converter for receiving the second message containing HTTP encapsulated in the device compatible protocol in the second message converting the second message into a standard HTTP communication protocol message at the server prior to sending the converted HTTP message to the service provider;

a session identifier component for receiving the session identifier at the server for association with a cached cookie received from a service provider via a HTTP server in response to the converted HTTP message sent by the client device, wherein the cookie is identified in a cookie to session identifier translation table, wherein the cookie to session identifier table is used to answer a client device hardware identifier name request from the HTTP server and to extract user information from a central registry.