Thin network protocol

• US 9,325,810 B2
• Filed: 09/30/2013
• Issued: 04/26/2016
• Est. Priority Date: 07/10/2006
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Orady, Aly E., Bunger, Nils
• Primary Examiner(s): Zong, Ruolei
• Application Number:
  US14/041,777
• Publication Number:
  US 20140040351A1
• Time in Patent Office: 939 Days
• Field of Search: 709/220, 709/222, 709/223, 709/249, 709/250, 719/321, 719/322, 719/310, 370/395.2
• US Class Current: 1/1
• CPC Class Codes: G06F 3/14 Digital output to display device ; Cooperation and interconnection of the display device with other functional units
• CPC Class Codes: G09G 2340/02 Handling of images in compressed format, e.g. JPEG, MPEG
• CPC Class Codes: G09G 2360/18 Use of a frame buffer in a display terminal, inclusive of the display panel
• CPC Class Codes: G09G 2370/10 Use of a protocol of communication by packets in interfaces along the display data pipeline
• CPC Class Codes: G09G 5/003 Details of a display terminal, the details relating to the control arrangement of the display terminal and to the interfaces thereto specific for a CRT G09G1/165; for a flat panel G09G3/2092
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet

Abstract

A method for a server to process a transaction on remote client hardware is disclosed. A local request is generated for the transaction. A driver level message to the remote client hardware is generated. The driver level message is sent directly to the remote client hardware to process the transaction.

Claims

1. A server to process a transaction on remote client hardware, including:

an interface;

a processor; and

a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to;

generate a local request for the transaction comprising read operation on the remote client hardware;

generate a driver level message for the remote client hardware, wherein the driver level message comprises an opcode indicating the read operation on the remote client hardware and an address indicating location of resources of the remote client hardware;

send the driver level message directly to the remote client hardware to implement the transaction; and

receive a response message comprising an opcode indicating return of the read operation and data stored in the resources of the remote client hardware indicated by the address, from the remote client hardware.

2. The server as recited in claim 1, wherein the driver level message is a message that requires no processing by the remote client hardware and is directly implementable by hardware of the remote client hardware.

3. A server as recited in claim 1, wherein the driver level message is a message implementable by a hardware without a need for a central processing unit (CPU), a micro processing unit (MCU), and digital signal processor (DSP).

4. A server as recited in claim 1, wherein type of operation indicated by the opcode is selected from a group consisting of CSR reads, CSR writes, block data transfers, and interrupts.

5. A server as recited in claim 1, wherein the driver level message is a message that is implementable by hardware and type of operation indicated by the opcode is selected from the group consisting of CSR reads, CSR writes, block data transfers, and interrupts, and wherein the remote client hardware combines interrupt data with the interrupts.

6. A server as recited in claim 1, wherein the transaction occurs over a digitally switched network.

7. A server as recited in claim 1, wherein the transaction occurs over a digitally switched network on a packet-based protocol.

8. A server as recited in claim 1, wherein the transaction occurs over a digitally switched network on a packet-based protocol with unreliable service.

9. A server as recited in claim 1, wherein the transaction occurs over a digitally switched network on a packet-based protocol with unreliable service, UDP/IP.

10. A server as recited in claim 1, wherein the transaction occurs within connection-oriented transport.

11. A server as recited in claim 1, wherein the transaction occurs within connectionless transport.

12. A server as recited in claim 1, wherein the remote client hardware include devices that generate a client-originated driver level message and send the client-originated driver level message directly to the server.

13. A server as recited in claim 1, wherein the remote client hardware include devices restricted to a small number of connections, or one connection.

14. A server as recited in claim 1, wherein the remote client hardware include devices using double buffering of a frame buffer.

15. A server as recited in claim 1, wherein the remote client hardware include devices comprised of only hardware.

16. A server as recited in claim 1, wherein the remote client hardware include stateless devices.

17. A server as recited in claim 1, wherein the remote client hardware include stateless devices without a need for a central processing unit (CPU), a micro processing unit (MCU), and digital signal processor (DSP).

18. A server as recited in claim 1, wherein the remote client hardware include thin clients.

19. A server as recited in claim 1, wherein the remote client hardware include network printers.

20. A server as recited in claim 1, wherein the remote client hardware include VoIP phones.

21. A server as recited in claim 1, wherein the remote client hardware include computer peripherals, wherein the computer peripherals are selected from a group consisting of:

serial devices, parallel devices, USB devices, Firewire devices, keyboard devices, mouse devices, human input devices, video devices, audio devices, printers, scanners, and network adapters.

22. A server as recited in claim 1, wherein the server supports a loopback interface for compatibility with a remote protocol and wherein the loopback interface is configured to receive and decode an encoded action and generate the driver level message based on the decoded action.

23. A server as recited in claim 1, wherein the server supports client USB termination on the server.

24. A server as recited in claim 2, wherein the remote client hardware includes thin clients.

25. A server as recited in claim 10, wherein the remote client hardware includes thin clients.

26. A server as recited in claim 2, wherein the remote client hardware include computer peripherals, wherein the computer peripherals are selected from a group consisting of:

serial devices, parallel devices, USB devices, Firewire devices, keyboard devices, mouse devices, human input devices, video devices, audio devices, printers, scanners, and network adapters.

27. A server as recited in claim 3, wherein the remote client hardware include computer peripherals, wherein the computer peripherals are selected from a group consisting of:

serial devices, parallel devices, USB devices, Firewire devices, keyboard devices, mouse devices, human input devices, video devices, audio devices, printers, scanners, and network adapters.

28. A server as recited in claim 4, wherein the remote client hardware include computer peripherals, wherein the computer peripherals are selected from a group consisting of:

serial devices, parallel devices, USB devices, Firewire devices, keyboard devices, mouse devices, human input devices, video devices, audio devices, printers, scanners, and network adapters.

29. A server as recited in claim 10, wherein the remote client hardware include computer peripherals, wherein the computer peripherals are selected from a group consisting of:

serial devices, parallel devices, USB devices, Firewire devices, keyboard devices, mouse devices, human input devices, video devices, audio devices, printers, scanners, and network adapters.

30. The server as recited in claim 1, wherein the memory is configured to provide the processor with further instructions which when executed cause the processor to:

send and Ack of the response message to the remote client hardware.

31. The server as recited in claim 1, wherein the transaction further comprises write operation on the remote client hardware, the memory is configured to provide the processor with further instructions which when executed cause the processor to:

generate another driver level message comprising an opcode indicating the write operation on the remote client hardware;

send the another driver level message directly to the remote client hardware to implement the transaction; and

receive an Ack signifying the write operation on the remote client hardware was successful, from the remote client hardware.

32. A method for a server to process a transaction on remote client hardware, including:

generating a local request for the transaction comprising read operation on the remote client hardware;

generating a driver level message for the remote client hardware, wherein the driver level message comprises an opcode indicating the read operation on the remote client hardware and an address indicating location of resources of the remote client hardware;

sending the driver level message directly to the remote client hardware to implement the transaction; and

receiving a response message comprising an opcode indicating return of the read operation and data stored in the resources of the remote client hardware indicated by the address, from the remote client hardware.

33. A method as recited in claim 32, wherein the driver level message is a message that requires no processing and is directly implementable by hardware of the remote client hardware.

34. A method as recited in claim 32, wherein the transaction occurs over a digitally switched network.

35. A method as recited in claim 32, wherein the remote client hardware include devices comprised of only hardware.

36. A method as recited in claim 32, wherein the remote client hardware include stateless devices.

37. A method as recited in claim 32, wherein the remote client hardware include thin clients.

38. A method as recited in claim 32, wherein the remote client hardware include network printers.

39. A method as recited in claim 32, wherein the remote client hardware include VoIP phones.

40. A method as recited in claim 32, wherein the remote client hardware include computer peripherals, wherein the computer peripherals are selected from the group consisting of serial devices, parallel devices, USB devices, Firewire devices, keyboard devices, mouse devices, human input devices, video devices, audio devices, printers, scanners, and network adapters.