# RPC JSON configuration

Source: [https://docs.qualcomm.com/doc/80-41102-1/topic/rpc-json-configuration.html](https://docs.qualcomm.com/doc/80-41102-1/topic/rpc-json-configuration.html)

The following JSON file has the RPC configuration example mentioned earlier, where system
            0x102 offers DCS service as an RPC service and only allows system 0x101 to access. Note
            the same RPC JSON file must be loaded by both the local system (ID=0x101) and the remote
            system (ID0x102).

    {
        "systems" :
        [
            {
                "id" : "0x101",
                "name" : "ClientSystem"
            },
            {
                "id" : "0x102",
                "name" : "ServerSystem"
            }
        ],
        "rpc_services" :
        [
            {
                "name" : "taf_dcs",
                "user" : "telaf",
                "offer_systems" : [ "ServerSystem" ]
            }
        ]
    }Copy to clipboard

**JSON elements:**
- `systems`
                    *(array)*: Specifies all TelAF systems in the overall vehicle network. The
                    maximum system number supported is 4. Note that the JSON file must declare at
                    least two systems. One for the local system and one for a remote system.
    - `id`: System ID of a TelAF system. Because the system ID
                            is mapped to the SOME/IP client ID, it must be the same value as the
                            application\_id of `tafSomeipGWSvc` in
                                /legato/systems/current/appsWriteable/tafSomeipGWSvc/tafSomeipGWSvc.json.
                            Valid value range is 0x0001 to 0xFFFF.
    - `name`: System name. Supported maximum string length is
                            63 bytes with Aa-Zz 0-9 and \_.
- `rpc_services`
                    *(array)*: Declares all TelAF RPC services within the vehicle. Maximum
                    service number supported is 32. Note that the JSON file must declare at least
                    one RPC service.
    - `name`: TelAF IPC service interface name, for example
                                `taf_dcs`.
    - `user`: TelAF IPC service username, for example
                                `telaf`.
    - `version`
                            *(optional)*: Protocol ID of the service. Default is
                                `ANY_VERSION`, which means ignoring version check
                            when offering the service.
    - `connection_type`
                            *(optional)*: Valid types are `TCP` and
                                `UDP`. Default is `TCP`.
    - `response_timeout`
                            *(optional)*: Response timeout in seconds of an RPC call for the
                            RPC service. Default is 30.
    - `offer_systems`
                            *(array)*: System ID/Name list that offer this RPC service. Maximum
                            system number supported is 4.
- `base_service_id`
                    *(optional)*: Base SOME/IP service ID assigned to the RPC services. It
                    begins with `base_service_id+1`. For example, the first RPC
                    service in the `rpc_services` array has the SOME/IP service ID is
                        `base_service_id+1`, the second RPC service is
                        `base_service_id+2` etc. Default is 0xED00.
- `base_port_number`
                    *(optional)*: Base port number assigned to the RPC services. It begins with
                        `base_port_number+1`, such as
                        `base_service_id` for RPC services. Default is 40000.
- `response_timeout`
                    *(optional)* : Response timeout in seconds of an RPC call for all RPC
                    services. Default is 30.
- `routing_name`
                    *(optional)*: Specifies the routing manager on which the RPC proxy is
                    running. It maps to the device specified in one of the JSON files for
                    tafSomeipGWSvc. If not specified, the default routing manager in tafSomeipGWSvc
                    is used.

**Parent Topic:** [TelAF RPC](https://docs.qualcomm.com/doc/80-41102-1/topic/rpc.html)

Last Published: Aug 06, 2026

[Previous 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) [Next Topic
RPC configuration setup](https://docs.qualcomm.com/bundle/publicresource/80-41102-1/topics/rpc-configuration-setup.md)