1# IPC与RPC通信开发指导
2
3## 场景介绍
4
5IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信,包括Proxy和Stub运行在不同设备的情况。
6
7<!--Del-->
8## 接口说明
9
10**表1** Native侧IPC接口
11
12| 类/接口 | 方法名                               | 描述                                                             |
13|----------|  ------------------------------------ | ---------------------------------------------------------------- |
14| IRemoteBroker | sptr&lt;IRemoteObject&gt; AsObject() | 返回通信对象。Stub端返回RemoteObject对象本身,Proxy端返回代理对象。 |
15| IRemoteStub | virtual int OnRemoteRequest(uint32_t code, MessageParcel &amp;data, MessageParcel &amp;reply, MessageOption &amp;option) | 请求处理方法,派生类需要重写该方法用来处理Proxy的请求并返回结果。 |
16| IRemoteProxy | Remote()->SendRequest(code, data, reply, option)  | 消息发送方法,业务的Proxy类需要从IRemoteProxy类派生,该方法用来向对端发送消息。 |
17<!--DelEnd-->
18
19## 开发步骤
20
21<!--Del-->
22### **Native侧开发步骤**
23
241. 添加依赖
25
26   SDK依赖:
27
28   ```
29   #ipc场景
30   external_deps = [
31     "ipc:ipc_single",
32   ]
33
34   #rpc场景
35   external_deps = [
36     "ipc:ipc_core",
37   ]
38   ```
39
40   此外, IPC/RPC依赖的refbase实现在公共基础库下,请增加对utils的依赖:
41
42   ```
43   external_deps = [
44     "c_utils:utils",
45   ]
46   ```
47
482. 定义IPC接口ITestAbility
49
50   SA接口继承IPC基类接口IRemoteBroker,接口里定义描述符、业务函数和消息码,其中业务函数在Proxy端和Stub端都需要实现。
51
52   ```c++
53   #include "iremote_broker.h"
54
55   //定义消息码
56   const int TRANS_ID_PING_ABILITY = 5;
57
58   const std::string DESCRIPTOR = "test.ITestAbility";
59
60   class ITestAbility : public IRemoteBroker {
61   public:
62       // DECLARE_INTERFACE_DESCRIPTOR是必需的,入参需使用std::u16string;
63       DECLARE_INTERFACE_DESCRIPTOR(to_utf16(DESCRIPTOR));
64       virtual int TestPingAbility(const std::u16string &dummy) = 0; // 定义业务函数
65   };
66   ```
67
683. 定义和实现服务端TestAbilityStub
69
70   该类是和IPC框架相关的实现,需要继承 IRemoteStub&lt;ITestAbility&gt;。Stub端作为接收请求的一端,需重写OnRemoteRequest方法用于接收客户端调用。
71
72   ```c++
73   #include "iability_test.h"
74   #include "iremote_stub.h"
75
76   class TestAbilityStub : public IRemoteStub<ITestAbility> {
77   public:
78       virtual int OnRemoteRequest(uint32_t code, MessageParcel &data, MessageParcel &reply, MessageOption &option) override;
79       int TestPingAbility(const std::u16string &dummy) override;
80    };
81
82   int TestAbilityStub::OnRemoteRequest(uint32_t code,
83       MessageParcel &data, MessageParcel &reply, MessageOption &option)
84   {
85       switch (code) {
86           case TRANS_ID_PING_ABILITY: {
87               std::u16string dummy = data.ReadString16();
88               int result = TestPingAbility(dummy);
89               reply.WriteInt32(result);
90               return 0;
91           }
92           default:
93               return IPCObjectStub::OnRemoteRequest(code, data, reply, option);
94       }
95   }
96   ```
97
984. 定义服务端业务函数具体实现类TestAbility
99
100   ```c++
101   #include "iability_server_test.h"
102
103   class TestAbility : public TestAbilityStub {
104   public:
105       int TestPingAbility(const std::u16string &dummy);
106   }
107
108   int TestAbility::TestPingAbility(const std::u16string &dummy) {
109       return 0;
110   }
111   ```
112
1135. 定义和实现客户端 TestAbilityProxy
114
115   该类是Proxy端实现,继承IRemoteProxy&lt;ITestAbility&gt;,调用SendRequest接口向Stub端发送请求,对外暴露服务端提供的能力。
116
117   ```c++
118   #include "iability_test.h"
119   #include "iremote_proxy.h"
120   #include "iremote_object.h"
121
122   class TestAbilityProxy : public IRemoteProxy<ITestAbility> {
123   public:
124       explicit TestAbilityProxy(const sptr<IRemoteObject> &impl);
125       int TestPingAbility(const std::u16string &dummy) override;
126   private:
127       static inline BrokerDelegator<TestAbilityProxy> delegator_; // 方便后续使用iface_cast宏
128   }
129
130   TestAbilityProxy::TestAbilityProxy(const sptr<IRemoteObject> &impl)
131       : IRemoteProxy<ITestAbility>(impl)
132   {
133   }
134
135   int TestAbilityProxy::TestPingAbility(const std::u16string &dummy){
136       MessageOption option;
137       MessageParcel dataParcel, replyParcel;
138       dataParcel.WriteString16(dummy);
139       int error = Remote()->SendRequest(TRANS_ID_PING_ABILITY, dataParcel, replyParcel, option);
140       int result = (error == ERR_NONE) ? replyParcel.ReadInt32() : -1;
141       return result;
142   }
143   ```
144
1456. SA注册与启动
146
147   SA需要将自己的TestAbilityStub实例通过AddSystemAbility接口注册到SystemAbilityManager,设备内与分布式的注册参数不同。
148
149   ```c++
150   // 注册到本设备内
151   auto samgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
152   samgr->AddSystemAbility(saId, new TestAbility());
153
154   // 在组网场景下,会被同步到其他设备上
155   auto samgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
156   ISystemAbilityManager::SAExtraProp saExtra;
157   saExtra.isDistributed = true; // 设置为分布式SA
158   int result = samgr->AddSystemAbility(saId, new TestAbility(), saExtra);
159   ```
160
1617. SA获取与调用
162
163   通过SystemAbilityManager的GetSystemAbility方法可获取到对应SA的代理IRemoteObject,然后构造TestAbilityProxy即可。
164
165   ```c++
166   // 获取本设备内注册的SA的proxy
167   sptr<ISystemAbilityManager> samgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
168   sptr<IRemoteObject> remoteObject = samgr->GetSystemAbility(saId);
169   sptr<ITestAbility> testAbility = iface_cast<ITestAbility>(remoteObject); // 使用iface_cast宏转换成具体类型
170
171   // 获取其他设备注册的SA的proxy
172   sptr<ISystemAbilityManager> samgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
173
174   // networkId是组网场景下对应设备的标识符,可以通过GetLocalNodeDeviceInfo获取
175   sptr<IRemoteObject> remoteObject = samgr->GetSystemAbility(saId, networkId);
176   sptr<TestAbilityProxy> proxy(new TestAbilityProxy(remoteObject)); // 直接构造具体Proxy
177   ```
178<!--DelEnd-->
179### **ArkTS侧开发步骤**
180
181> **说明:**
182>
183> - 此文档中的示例代码描述的是系统应用跨进程通信。
184>
185> - 当前不支持三方应用实现ServiceExtensionAbility,三方应用的UIAbility组件可以通过Context连接系统提供的ServiceExtensionAbility。
186>
187> - 当前使用场景: 仅限客户端是三方应用,服务端是系统应用。
188
1891. 添加依赖
190
191   ```ts
192    // FA模型需要从@kit.AbilityKit导入featureAbility
193    // import { featureAbility } from '@kit.AbilityKit';
194    import { rpc } from '@kit.IPCKit';
195    ```
196
1972. 绑定Ability
198
199   首先,构造变量want,指定要绑定的Ability所在应用的包名、组件名,如果是跨设备的场景,还需要绑定目标设备NetworkId(组网场景下对应设备的标识符,可以使用distributedDeviceManager获取目标设备的NetworkId);然后,构造变量connect,指定绑定成功、绑定失败、断开连接时的回调函数;最后,FA模型使用featureAbility提供的接口绑定Ability,Stage模型通过context获取服务后用提供的接口绑定Ability。
200
201   ```ts
202    // FA模型需要从@kit.AbilityKit导入featureAbility
203    // import { featureAbility } from "@kit.AbilityKit";
204    import { Want, common } from '@kit.AbilityKit';
205    import { rpc } from '@kit.IPCKit';
206    import { hilog } from '@kit.PerformanceAnalysisKit';
207    import { distributedDeviceManager } from '@kit.DistributedServiceKit';
208    import { BusinessError } from '@kit.BasicServicesKit';
209
210    let dmInstance: distributedDeviceManager.DeviceManager | undefined;
211    let proxy: rpc.IRemoteObject | undefined;
212    let connectId: number;
213
214    // 单个设备绑定Ability
215    let want: Want = {
216      // 包名和组件名写实际的值
217      bundleName: "ohos.rpc.test.server",
218      abilityName: "ohos.rpc.test.server.ServiceAbility",
219    };
220    let connect: common.ConnectOptions = {
221      onConnect: (elementName, remoteProxy) => {
222        hilog.info(0x0000, 'testTag', 'RpcClient: js onConnect called');
223        proxy = remoteProxy;
224      },
225      onDisconnect: (elementName) => {
226        hilog.info(0x0000, 'testTag', 'RpcClient: onDisconnect');
227      },
228      onFailed: () => {
229        hilog.info(0x0000, 'testTag', 'RpcClient: onFailed');
230      }
231    };
232    // FA模型使用此方法连接服务
233    // connectId = featureAbility.connectAbility(want, connect);
234
235    let context: common.UIAbilityContext = getContext(this) as common.UIAbilityContext; // UIAbilityContext
236    // 建立连接后返回的Id需要保存下来,在解绑服务时需要作为参数传入
237    connectId = context.connectServiceExtensionAbility(want,connect);
238
239    // 跨设备绑定
240    try{
241      dmInstance = distributedDeviceManager.createDeviceManager("ohos.rpc.test");
242    } catch(error) {
243      let err: BusinessError = error as BusinessError;
244      hilog.error(0x0000, 'testTag', 'createDeviceManager errCode:' + err.code + ', errMessage:' + err.message);
245    }
246
247    // 使用distributedDeviceManager获取目标设备NetworkId
248    if (dmInstance != undefined) {
249      let deviceList = dmInstance.getAvailableDeviceListSync();
250      let networkId = deviceList[0].networkId;
251      let want: Want = {
252        bundleName: "ohos.rpc.test.server",
253        abilityName: "ohos.rpc.test.service.ServiceAbility",
254        deviceId: networkId,
255        flags: 256
256      };
257      // 建立连接后返回的Id需要保存下来,在断开连接时需要作为参数传入
258      // FA模型使用此方法连接服务
259      // connectId = featureAbility.connectAbility(want, connect);
260
261      // 第一个参数是本应用的包名,第二个参数是接收distributedDeviceManager的回调函数
262      connectId = context.connectServiceExtensionAbility(want,connect);
263    }
264   ```
265
2663. 服务端处理客户端请求
267
268   服务端被绑定的Ability在onConnect方法里返回继承自[rpc.RemoteObject](../reference/apis-ipc-kit/js-apis-rpc.md#remoteobject)的对象,该对象需要实现[onRemoteMessageRequest](../reference/apis-ipc-kit/js-apis-rpc.md#onremotemessagerequest9)方法,处理客户端的请求。
269
270   ```ts
271    import { rpc } from '@kit.IPCKit';
272    import { Want } from '@kit.AbilityKit';
273    class Stub extends rpc.RemoteObject {
274      constructor(descriptor: string) {
275        super(descriptor);
276      }
277      onRemoteMessageRequest(code: number, data: rpc.MessageSequence, reply: rpc.MessageSequence, option: rpc.MessageOption): boolean | Promise<boolean> {
278        // 根据code处理客户端的请求
279        return true;
280      }
281
282      onConnect(want: Want) {
283        const robj: rpc.RemoteObject = new Stub("rpcTestAbility");
284        return robj;
285      }
286    }
287   ```
288
2894. 客户端处理服务端响应
290
291   客户端在onConnect回调里接收到代理对象,调用[sendMessageRequest](../reference/apis-ipc-kit/js-apis-rpc.md#sendmessagerequest9-2)方法发起请求,在期约(用于表示一个异步操作的最终完成或失败及其结果值)或者回调函数里接收结果。
292
293   ```ts
294    import { rpc } from '@kit.IPCKit';
295    import { hilog } from '@kit.PerformanceAnalysisKit';
296
297    // 使用期约
298    let option = new rpc.MessageOption();
299    let data = rpc.MessageSequence.create();
300    let reply = rpc.MessageSequence.create();
301    // 往data里写入参数
302    let proxy: rpc.IRemoteObject | undefined;
303    if (proxy != undefined) {
304      proxy.sendMessageRequest(1, data, reply, option)
305        .then((result: rpc.RequestResult) => {
306          if (result.errCode != 0) {
307            hilog.error(0x0000, 'testTag', 'sendMessageRequest failed, errCode: ' + result.errCode);
308            return;
309          }
310          // 从result.reply里读取结果
311        })
312        .catch((e: Error) => {
313          hilog.error(0x0000, 'testTag', 'sendMessageRequest got exception: ' + e);
314        })
315        .finally(() => {
316          data.reclaim();
317          reply.reclaim();
318        })
319    }
320
321    // 使用回调函数
322    function sendRequestCallback(err: Error, result: rpc.RequestResult) {
323      try {
324        if (result.errCode != 0) {
325          hilog.error(0x0000, 'testTag', 'sendMessageRequest failed, errCode: ' + result.errCode);
326          return;
327        }
328        // 从result.reply里读取结果
329      } finally {
330          result.data.reclaim();
331          result.reply.reclaim();
332      }
333    }
334    let options = new rpc.MessageOption();
335    let datas = rpc.MessageSequence.create();
336    let replys = rpc.MessageSequence.create();
337    // 往data里写入参数
338    if (proxy != undefined) {
339      proxy.sendMessageRequest(1, datas, replys, options, sendRequestCallback);
340    }
341   ```
342
3435. 断开连接
344
345   IPC通信结束后,FA模型使用featureAbility的接口断开连接,Stage模型在获取context后用提供的接口断开连接。
346
347   ```ts
348    // FA模型需要从@kit.AbilityKit导入featureAbility
349    // import { featureAbility } from "@kit.AbilityKit";
350    import { Want, common } from '@kit.AbilityKit';
351    import { rpc } from '@kit.IPCKit';
352    import { hilog } from '@kit.PerformanceAnalysisKit';
353
354    function disconnectCallback() {
355      hilog.info(0x0000, 'testTag', 'disconnect ability done');
356    }
357    // FA模型使用此方法断开连接
358    // featureAbility.disconnectAbility(connectId, disconnectCallback);
359
360    let proxy: rpc.IRemoteObject | undefined;
361    let connectId: number;
362
363    // 单个设备绑定Ability
364    let want: Want = {
365      // 包名和组件名写实际的值
366      bundleName: "ohos.rpc.test.server",
367      abilityName: "ohos.rpc.test.server.ServiceAbility",
368    };
369    let connect: common.ConnectOptions = {
370      onConnect: (elementName, remote) => {
371        proxy = remote;
372      },
373      onDisconnect: (elementName) => {
374      },
375      onFailed: () => {
376        proxy;
377      }
378    };
379    // FA模型使用此方法连接服务
380    // connectId = featureAbility.connectAbility(want, connect);
381
382    connectId = this.context.connectServiceExtensionAbility(want,connect);
383
384    this.context.disconnectServiceExtensionAbility(connectId);
385   ```
386
387## 相关实例
388
389针对IPC与RPC通信开发,有以下相关实例可供参考:
390
391- [RPC通信(ArkTS)(API9)](https://gitee.com/openharmony/applications_app_samples/tree/master/code/BasicFeature/Connectivity/RPC)
392