# RIL Adapter<a name="EN-US_TOPIC_0000001106353742"></a>

-   [Introduction](#section117mcpsimp)
-   [Directory Structure](#section122mcpsimp)
-   [Constraints](#section126mcpsimp)
-   [Usage Guidelines](#section264mcpsimp)
-   [Repositories Involved](#section279mcpsimp)

## Introduction<a name="section117mcpsimp"></a>

The RIL Adapter module provides functions such as vendor library loading, service interface implementation, and event scheduling and management. The module shields the differences of modems supplied by different vendors to provide a unified interface for the telephony service layer. It communicates with the telephony service layer by registering a Hardware Driver Foundation \(HDF\) service.

**Figure  1**  Architecture of the RIL Adapter module<a name="fig1675210296494"></a>
![](figures/en-us_architecture-of-the-ril-adapter-module.png)

## Directory Structure<a name="section122mcpsimp"></a>

```shell
base/telephony/ril_adapter
├── figures                             # Resource file of readme
├── frameworks
│   ├── BUILD.gn
│   └── src                             # Serialized file
├── interfaces                          # Provide internal interfaces for each business
│   └── innerkits
├── services                            # Service
│   ├── hril                            # Implementation of each business module interface of the hri layer
│   ├── hril_hdf                        # HDF service
│   └── vendor                          # vendor file
└── test                                # Test code
    ├── BUILD.gn
    ├── mock
    └── unittest                        # Unit test code
```

## Constraints<a name="section126mcpsimp"></a>

-   In terms of software, the RIL Adapter needs to work with the telephony core service \(core\_service\) and an interworking interface needs to be implemented by the modem vendor lib.
-   In terms of hardware, the device must be equipped with a modem capable of independent cellular communication.

## Usage Guidelines<a name="section264mcpsimp"></a>

The RIL Adapter does not provide external APIs and can only be called by the telephony core service.

## Repositories Involved<a name="section279mcpsimp"></a>

[Telephony](https://gitee.com/openharmony/docs/blob/master/en/readme/telephony.md)

**telephony_ril_adapter**

[telephony_core_service](https://gitee.com/openharmony/telephony_core_service/blob/master/README.md)

# RIL Adapter<a name="ZH-CN_TOPIC_0000001106353742"></a>

-   [简介](#section117mcpsimp)
-   [目录](#section122mcpsimp)
-   [约束](#section126mcpsimp)
-   [使用说明](#section264mcpsimp)
-   [相关仓](#section279mcpsimp)

## 简介<a name="section117mcpsimp"></a>

RIL Adapter模块主要包括厂商库加载，业务接口实现以及事件调度管理。主要用于屏蔽不同modem厂商硬件差异，为上层提供统一的接口，通过注册HDF服务与上层接口通讯。

**图 1**  RIL Adapter模块架构图<a name="fig1675210296494"></a>
![](figures/zh-cn_architecture-of-the-ril-adapter-module.png "RIL-Adapter模块架构图")

## 目录<a name="section122mcpsimp"></a>
```sh
base/telephony/ril_adapter
├── figures                             # readme资源文件
├── frameworks
│   ├── BUILD.gn
│   └── src                             # 序列化文件
├── interfaces                          # 对应提供上层各业务内部接口
│   └── innerkits
├── services                            # 服务
│   ├── hril                            # hril层的各个业务模块接口实现
│   ├── hril_hdf                        # HDF服务
│   └── vendor                          # 厂商库文件
└── test                                # 测试代码
    ├── BUILD.gn
    ├── mock
    └── unittest                        # 单元测试代码
```

## 约束<a name="section126mcpsimp"></a>

-   软件上，需要与以下服务配合使用：Telephony核心服务（core\_service），需要Modem厂商库实现接口。
-   硬件上，需要搭载的设备支持以下硬件：可以进行独立蜂窝通信的Modem。

## 使用说明<a name="section264mcpsimp"></a>

ril\_adapter不对外暴露接口，可通过核心服务调用。

## 相关仓<a name="section279mcpsimp"></a>

[电话服务子系统](https://gitee.com/openharmony/docs/blob/master/zh-cn/readme/%E7%94%B5%E8%AF%9D%E6%9C%8D%E5%8A%A1%E5%AD%90%E7%B3%BB%E7%BB%9F.md)

**telephony_ril_adapter**

[telephony_core_service](https://gitee.com/openharmony/telephony_core_service/blob/master/README_zh.md)