OK, a few disconncted ideas to try and put you on the right path.
LVDS is a HARDWARE protocol, it defines the electrical connection.
It defines voltages, and line impedances.
Look at this link to some LVDS line drivers and receivers:
https://www.electro-tech-online.com/custompdfs/2010/08/slld009.pdf
it may help.
It does NOT define the data which is passed through the LVDS connection.
An example.
Say I want to send some date between two devices, I want to send the data at a fast rate over a long distance.
I decide that LVDS line drivers and receivers will do the job if I use a suitable twin twisted cable between them.
Device 1 which is doing the sending, I program this to send the data out of a digital I/O port pin, I am sending 1s and 0s, 5v and 0v.
Device 2 which is doing the receiving, I program this to read the data in from a digital I/O port pin, I am receiving 1s and 0s, 5v and 0v.
I can connect the output pin from device 1 to the input pin of device 2 and they will communicate across the bench.
Once I have this working, I can move the devices apart, connect an LVDS driver to the output pin of device 1, connect an LVDS receiver to the input pin of device 2, and finally connect a cable between the LVDS driver and receiver.
With a bit of luck my devices will communicate again, even though they are now a long way apart.
I hope this simplistic description has cleared the fog for you!
JimB
Afterthoughts
The data which is passing from device 1 to device 2, could be as simple as asynchronous serial data, 1 start bit, 8 data bits and 1 stop bit. Just like good old RS232 ASCII.
Or, it could be just a stream of bits. I which case I may need a second LVDS path carrying a clock, so I know where one bit starts and the other ends.