When I write 3-D IP Stack, I am writing about the TCP/IP bandwidth that everyone uses to communicate over WiFi and Ethernet all over the world.
What most people do not realize is that packets, which are the backbone of TCP/IP travel in wires in circular formations. Think of packets as sending cans of tomato paste down a fire hose.
In WiFi, we know these are electrical transactions (cans) travel at 2.4 Gigabytes and 5 Gigabytes per second (billions of times per second).
In Ethernet, these packets travel at 100 Megabytes per second; much slower, but still millions of times per second).
We think of these packets as digital communications because we send them as 8-bit words using ones and zeros. But, they travel through wires and then, through the air; they are still analog communications and can be affected by weather, Sunspots and any number of outages do to equipment failure. There are always bandwidth issues as well.
Stick with me, the concept of the can going through the wire is important. To keep it simple, the computer controlling the modulation of the signal before it is transmitted is where the IP Stack is located; this is normally, a server.
The IP Stack controls the many different ways/directions that packets are transmitted to ensure that the complete communication arrives at it’s proper destination at a distant server.
So… We are digitizing letters, numbers and special characters and sending them via packets. We encapsulate the data in several layers and process them two-dimensionally.
Remember the can concept; it is a 3-D construct. We are using all of our communications in 2-D, but we can get much greater efficiencies if we start using X, Y, and Z axes. To do this, we must re-design the IP Stack into a 3-D structure.
For anyone who has worked with the IP Stack, most of the bandwidth has been used up. There is some bandwidth available to add programming, but it is extremely limited. Why? Like our communications, in general, the IP Stack is two-dimensional.
What I propose is to look at the layers in the IP Stack like they were layers in a can. Because we are using digital controls, the layers can be very thin; a tomato paste can construct can have million or billions of layers.
Now, we put the IP Stack into this 3-D can-like structure and map where the available bandwidth is. This would be using software like that being used to map our Genome/DNA.
Using this approach, there is a lot of unused bandwidth in the IP Stack. One of the things that is missing in the IP Stack is Security, but there are several other very useful things that can be added using this new found bandwidth.
Now, using this 3-D approach, we can have each of the layers communicate with each other serially (like the existing IP Stack), but also pseudo-randomly using cluster bursts in an array vertically around the perimeter of the “can” construct.
Once we have the 3-D IP Stack operational, it is fairly straight forward to turn the 2-D digital packets into 3-D packets that carry much more content information such as embedded encryption and more.
I retain all rights to this concept.