# RPC binding Source: [https://docs.qualcomm.com/doc/80-41102-1/topic/rpc-binding.html](https://docs.qualcomm.com/doc/80-41102-1/topic/rpc-binding.html) RPC binding means binding with a remote service for an application. Because the RPC proxy creates a local TelAF proxy service for each RPC service, the TelAF application can leverage the binding section in the .adef file to set the RPC binding. The server interface of an RPC service shall follow the following format (replace ``, `` and `` with the correct information): .rpcServer___Copy to clipboard For instance, if the TelAF platform service `.taf_dcs` on a remote system (ID=0x102) is declared as an RPC service, then the corresponding RPC server interface created by the local RPC server proxy is `.rpcServer_102_telaf_taf_dcs`. The default client interface of `taf_dcs` service can access the remote DCS service through this server interface. The following binding allows the client interface `dcExe.dcComp.taf_dcs` of the DCS application to access the DCS service on remote system (ID=0x102) using the same TelAF taf\_dcs APIs: **.adef file of DCS application** executables: { dcExe= (dcComp) } processes: { run: { (dcExe) } } bindings: { dcExe.dcComp.taf_dcs -> .rpcServer_102_telaf_taf_dcs // Binding to remote DCS service on system 0x102 via RPC proxy }Copy to clipboard Then the DCS application can call `taf_dcs_XXX()` APIs to communicate with the remote DCS service on system 0x102. **Parent Topic:** [TelAF RPC](https://docs.qualcomm.com/doc/80-41102-1/topic/rpc.html) Last Published: Aug 06, 2026 [Previous Topic Service mapping](https://docs.qualcomm.com/bundle/publicresource/80-41102-1/topics/service-mapping.md) [Next Topic Bind the same service on both local and remote systems](https://docs.qualcomm.com/bundle/publicresource/80-41102-1/topics/bind-the-same-service-on-both-local-and-remote-systems.md)