I'm curious why it wasn't just directly applied using the ISO/OSI or TCP/IP models. I really like the idea of "everything is OSI."
(I wrote a lot of things impulsively, and there are probably many mistakes.)
I'll offer my own assessment now.
Medium layer (In fact, it's recommended to call it Layer 0, but in the OSI context, physical dimensions of interfaces are often included, as well as information about line impedance.)
However, I don't think it's a problem to disassemble it, for example:
Upper layer: FSK
Mid-range: XXX GHz RF
Lower layer: Coaxial cable, coaxial waveguide, air.
Channel layer It seems to correspond to the OSI's link layer?
The channel layer describes the method of spectrum utilization, which can be divided into 2.0 layer, 2.5 layer, and special channel layers. The 2.0 layer describes how to differentiate between different signals from the same user, including FDM, OFDM, TDM, and single-channel direct connection.
I believe that these are actually quite close to the PHY part within the MAC.
Special channel layers include textual symbols, color images, magnetic recordings, electrical recordings, mechanical recordings, biological recordings, chemical recordings, and behavioral recordings on physical media.
I believe these are still layers within the medium.
Modulation layer In OSI, it's part of the Physical layer because the modulation method is directly related to the channel type.
An important aspect of the OSI model is that the lower layers provide a relatively uniform interface for the upper layers. I noticed you mentioned, "Each layer can contain elements below it... Different elements may contain different lower-layer elements," which introduces some coupling. I prefer to group related things into a "protocol stack" outside these layers, and then abstract them back into this protocol.Two floors(What interfaces are needed? What interfaces are provided?)
Hybrid modulation refers to a modulation method that combines different modulation techniques, such as AFSK modulation with QAM or FM modulation, AFSK modulation with AM modulation, QPSK modulation with FM modulation, and QAM modulation with FM modulation.
I do not recommend introducing the concept of "mixed modulation," as this could lead to a Cartesian product in the protocol stack.
Considering "audio OOK, encapsulated in data packets for addressing, and then modulated using QAM with TDMA multiplexing," this essentially involves traversing between three layers repeatedly.
If we use a tunnel...
Audio OOK （PHY） – [Data Packet – TDMA （MAC） – QAM （PHY） – Electromagnetic Field （O）] （O）
The items within the parentheses form a tunnel with 〇 layers, used to transmit the OOK audio.
Interface Layer Including AX.25, RTTY, Pactor, ASPP, TCP/IP, PD120, Robot36, PAL, NTSC, RDT, ASCII, LoRa, IEEE 802.11, MFSK standards, letters, paper, tape, hard drive, floppy disk, CD, photos, records, smells, punched cards, drawings, language, etc.
These are all interfaces, but they provide completely different functionalities and operate at different layers. Furthermore, they violate the principle of "high-level elements utilizing low-level elements."
For example, the "Magnetic Recording" modulation layer utilizes the interface of "magnetic tape," but the magnetic tape itself is listed in the fourth layer.
The interface itself should not be a standalone layer; each layer should have its own interface.
For example, the electromagnetic field acting as a "medium layer" enables the FSK modulation at the physical layer to function. This is the interface of the electromagnetic field, which allows writing on paper; this is the interface of the paper. By defining language, the words on the paper can convey information. Therefore, language itself is also an interface. Through names, language can be used for addressing, providing a higher-level interface with the information transmitted through language.
Are layers five and six reversed?
The information should first be encapsulated before being passed to lower layers, as illustrated in the example.
SSTV is a protocol for encapsulating image data; HTTP is a protocol for encapsulating various types of information.
Interface Layer I have no objections to the name, except for the fact that I think it's too close to the interface meaning and doesn't justify being a separate layer. I suggest calling it "Purpose Layer," which indicates that all subsequent layers are intended to achieve this purpose. Perhaps "Surface Layer" would also work?
As I was writing, I realized that the topmost layer often has excessive expressiveness, to the point where it can even act as a tunnel for all the layers below it (for example, one could theoretically create a tunnel running on the MAC layer that simulates an Ethernet tunnel – i.e., a two-layer tunnel operating at Layer 3).
If you want to, you can even simulate the physical layer.
I hope this might provide some inspiration for you.
(Perhaps I've been so deeply affected by TCP/IP that I find it difficult to accept other models.)
闽ICP备2021006864号-7
闽公网安备35020602002794号
互联网举报中心