{"id":498,"date":"2012-02-06T10:00:29","date_gmt":"2012-02-06T04:30:29","guid":{"rendered":"http:\/\/www.e-consystems.com\/blog\/android\/?p=498"},"modified":"2023-08-15T12:34:27","modified_gmt":"2023-08-15T07:04:27","slug":"ril","status":"publish","type":"post","link":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/ril\/","title":{"rendered":"Android RIL Architecture"},"content":{"rendered":"

Introduction<\/strong><\/p>\n

The document explains about the building blocks of Android telephony and how it works<\/p>\n

Android telephony architecture<\/strong><\/p>\n

\"Android<\/a>
Android RIL Architecture<\/figcaption><\/figure>\n

 <\/p>\n

Application:\u00a0 All the telephony related applications like Dialer, Call tracker, SMS, MMS, GPRS, Antenna signal indicator and etc, will come into this section. All these applications will be started during the android boot up. These applications will be tied up with the Android telephony framework services. The telephony framework provides APIs to access the Phone.<\/p>\n

Framework services: Telephony framework will be initialized and started during the system start up. All the queries from the application through API will directed to the Radio interface Layer of Android by these services. The service will keep tracking of all the unsolicited commands from the modem. Unsolicited commands are the commands initiated from the modem.<\/p>\n

Radio Interface Layer: It is the bridge between Android phone framework services and the hardware. In other words, it is the protocol stack for Telephone.\u00a0 The RIL consist of two primary components.<\/p>\n

    \n
  1. RIL Daemon<\/li>\n
  2. Vendor RIL<\/li>\n<\/ol>\n

    RIL Daemon <\/strong><\/p>\n

    RILD will be initialized during the Android system start up. It will read the system property to find which library has to be used for Vendor RIL, provide the appropriate input for vendor RIL and finally calls RIL_Init function of Vendor RIL to map all the Vendor RIL functions to the upper layer. Each vendor RIL has RIL_Init function.<\/p>\n

    Vendor RIL<\/strong><\/p>\n

    It is a library specific to each modem. In other words, we can call it as a driver to function the modem. The RIL daemon will call the RIL_Init function with the device location (eg: \/dev\/ttyS0). It will initiate the modem and returns theRIL_RadioFunctions structure contains the handles of radio functions<\/p>\n

     <\/p>\n\n\n\n
    \n 
    \n  type structure {<\/p>\n

             intRIL_version;<\/p>\n

             RIL_RequestFunconRequest;<\/p>\n

             RIL_RadioStateRequestonStateRequest;<\/p>\n

             RIL_Supports supports;<\/p>\n

             RIL_CancelonCancel;<\/p>\n

             RIL_GetVersiongetVersion;<\/p>\n

      } RIL_RadioFunctions;<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

     <\/p>\n

    RIL_version<\/em> : Version of Android RIL<\/p>\n

    onRequest<\/em> : Call to Vendor RIL to make a RIL_REQUEST. It must be completed with a call to RIL_onRequestComplete().It will always be called from the same thread, so returning here implies that the radio is ready to process another command (whether or not the previous command has completed)<\/p>\n

    supports\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : Return current radio state.RADIO_STATE_UNAVAILABLE should be the initial state<\/p>\n

    getVersion\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : Version of Vendor RIL<\/p>\n

    There are two forms of communications in Android RIL<\/p>\n

    Solicited Commands :<\/em><\/strong>These are commands initiated from the upper layer. Like, Dialing\/Send SMS<\/em> are the solicited commands from the upper layer to the RIL. OnRequest<\/em>is the function for sending the solicited commands from the upper layer<\/p>\n

    The following diagram describes the solicited call in Android<\/p>\n

    \"Solicited<\/a>
    Solicited call in Android<\/figcaption><\/figure>\n

     <\/p>\n

    Each onRequest call should end with RIL_onRequestComplete. It is to send the response for the previous onRequest and to intimate we are ready for the next command. Refer ril.h<\/em> for all the solicited commands<\/p>\n

    Unsolicited commands<\/strong><\/p>\n

    These are the commands initiated from the modem to the upper layer. Like, Receive Call \/Receive SMS are the commands. The Vendor RIL has to continuously monitor the device for unsolicited command from the modem.<\/p>\n

    The following diagram describes the unsolicited call in Android<\/p>\n

    \"Unsolicited<\/a>
    Unsolicited call in Android<\/figcaption><\/figure>\n

     <\/p>\n

    Implementation of Vendor RIL<\/strong><\/p>\n

    Android is providing the basic vendor RIL with minimum feature set (reference-ril). It is good to start with that reference code. Compile the Vendor RIL as a shared library with the following style<\/p>\n

    libril-<companyname>-<RIL version>.so<\/p>\n

    libril \u2013 all the Vendor ril library should start with this<\/p>\n

    Vendor RIL Configuration <\/strong>: Replace the following line in the init.rc file<\/p>\n

    serviceril-daemon \/system\/bin\/rild<\/p>\n

    with<\/p>\n

    serviceril-daemon \/system\/bin\/rild -l \/system\/lib\/libreference-ril.so — -d\/dev\/ttySx<\/p>\n

    Commands after \u201c–” will be input for Vendor ril.<\/p>\n

    Here is sample log of Sending a SMS<\/strong><\/p>\n

    D\/SMS\u00a0\u00a0\u00a0\u00a0 ( 1962): SMS send size=0time=1319439322559<\/p>\n

    D\/RILJ\u00a0\u00a0\u00a0 ( 1962): [0312]> SEND_SMS<\/p>\n

    D\/RIL\u00a0\u00a0\u00a0\u00a0 ( 1814): onRequest: SEND_SMS<\/p>\n

    D\/AT\u00a0\u00a0\u00a0\u00a0\u00a0 ( 1814): MUX[primary]: AT> AT+CMGS=14<\/p>\n

    D\/AT\u00a0\u00a0\u00a0\u00a0\u00a0 ( 1814): MUX[primary]: AT<><\/p>\n

    D\/AT\u00a0\u00a0\u00a0\u00a0\u00a0 ( 1814): AT> 0001000a814978045948000002c834^Z<\/p>\n

    D\/AT\u00a0\u00a0\u00a0\u00a0\u00a0 ( 1814): MUX[primary]: AT< Q: 31,0<\/p>\n

    D\/AT\u00a0\u00a0\u00a0\u00a0\u00a0 ( 1814): MUX[primary]: AT< +CUSD: 0,”Your Last Call charge IS Rs\u00a0 0.5000\u00a0 AND CURRENT Balance IS\u00a0 47.8770 AND EXP IS\u00a0 25\/09\/21. Love Spl 6 Caller tunes for Jd<\/p>\n

    D\/RILC\u00a0\u00a0\u00a0 ( 1814): Unsolicited Response!!!<\/p>\n

    D\/RILJ\u00a0\u00a0\u00a0 ( 1962): [UNSL]< UNSOL_ON_USSD 0<\/p>\n

    D\/AT\u00a0\u00a0\u00a0\u00a0\u00a0 ( 1814): MUX[primary]: AT< “,15<\/p>\n

    D\/AT\u00a0\u00a0\u00a0\u00a0\u00a0 ( 1814): MUX[primary]: AT< +CMGS: 219<\/p>\n

    D\/AT\u00a0\u00a0\u00a0\u00a0\u00a0 ( 1814): MUX[primary]: AT< OK<\/p>\n

     <\/p>\n

     
    \n–<\/p>\n

    We offer System-on-Modules<\/a> based on NXP iMX6<\/a>, NVIDIA Tegra K1<\/a>, TI DM3730\/AM3037<\/a>, Marvell PXA270<\/a> processors. Our ARM Cortex system on modules supports Linux, Android & WinCE. Our system on modules can be used in many applications likes Automation, Medical Imaging, Industrial Control, Remote Date Acquisition, etc. <\/p>\n","protected":false},"excerpt":{"rendered":"

    Introduction The document explains about the building blocks of Android telephony and how it works…<\/p>\n","protected":false},"author":15,"featured_media":546,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[5,95,102],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/posts\/498"}],"collection":[{"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/comments?post=498"}],"version-history":[{"count":16,"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/posts\/498\/revisions"}],"predecessor-version":[{"id":1864,"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/posts\/498\/revisions\/1864"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/media\/546"}],"wp:attachment":[{"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/media?parent=498"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/categories?post=498"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/system-on-module-som\/wp-json\/wp\/v2\/tags?post=498"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}