Reliable transport layer protocol in low performance 8-bit microcontrollers
First Claim
1. A method for providing a reliable connectionless protocol to transfer short pieces of information, the method comprising the steps of:
- Using a data transfer process using a layers stack model consisting of multiple layers; and
Adding an intermediate transport layer with the following fields, type of packet and packet ID.
0 Assignments
0 Petitions
Accused Products
Abstract
A reliable communication protocol RUDP is provided to transfer data between two systems connected in a network. Working over the unreliable UDP transport layer protocol, the RUDP protocol adds an acknowledging mechanism to otherwise unreliable UDP packets. Contrary to the TCP transport layer protocol, which establishes a connection before any data transfer, the RUDP is used to transfer short amounts of information or messages, so a connectionless communication is used. In a connectionless context the complexity of the encoding-decoding algorithm and the amount of memory consumed by the protocol is reduced. Such characteristics makes the RUDP protocol suitable for its implementation in systems with limited memory and speed, like low processing power 8-bit microcontrollers. Furthermore, by programming the RUDP protocol over the UDP protocol, its implementation in a personal computer can be made with common programming tools.
-
Citations
17 Claims
-
1. A method for providing a reliable connectionless protocol to transfer short pieces of information, the method comprising the steps of:
-
Using a data transfer process using a layers stack model consisting of multiple layers; and
Adding an intermediate transport layer with the following fields, type of packet and packet ID. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer program wherein the base component has interfaces and the program code for:
-
Using a data transfer process using a layers stack model consisting of multiple layers; and
Adding an an intermediate transport layer with the following fields, type of packet and packet ID. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17)
-
Specification