RIL Architecture (Windows Embedded CE 6.0)
1/6/2010
The RIL is divided into two separate components, a RIL Driver and a RIL Proxy. The RIL Driver processes radio commands and events. The RIL Proxy performs arbitration between multiple clients for access to the single RIL driver.
**The RIL driver architecture is based on the Windows Embedded CE standard MDD/PDD driver model. It is divided into two major sections, the MDD and PDD layers. The following illustration shows the RIL architecture.
.gif "Ee497437.5a79be04-3e4a-4a6d-b71b-aabf8e8801a1(en-US,WinEmbedded.60).gif")
The MDD (Model Device Driver) layer is independent of the radio stack. It contains code that interfaces with the RIL Proxy and code that implements any radio stack independent features in the RIL driver.
PDD (Platform Dependent Driver) layer is radio stack dependent. It contains code specific to implementation of RIL APIs for a specific radio stack. This is the layer that must implemented by OEMs. To further ease the implementation task the PDD layer itself can be separated into a layer that contains code common to a category of radios and code for a specific radio in that category. For example, the previous illustration shows a PDD layer that is separated into code common to AT based radio stacks and code for a specific AT based radio.
Although the RIL driver is divided, into 2 major parts, the output of the build process is still a single DLL. **
For more information, refer to topics RIL Driver and RIL Proxy.