Skip to content

SubsystemControl API

Version: 1.0.0

Status: ⚫⚪⚪

SubsystemControl interface for Thunder framework.

(Defined with ISubsystemControl in ISubsystemControl.h)

Table of Contents

Introduction

Scope

This document describes purpose and functionality of the SubsystemControl interface (version 1.0.0). It includes detailed specification about its methods provided.

Case Sensitivity

All identifiers of the interfaces described in this document are case-sensitive. Thus, unless stated otherwise, all keywords, entities, properties, relations and actions should be treated as such.

Acronyms, Abbreviations and Terms

The table below provides and overview of acronyms used in this document and their definitions.

Acronym Description
API Application Programming Interface
HTTP Hypertext Transfer Protocol
JSON JavaScript Object Notation; a data interchange format
JSON-RPC A remote procedure call protocol encoded in JSON

The table below provides and overview of terms and abbreviations used in this document and their definitions.

Term Description
callsign The name given to an instance of a plugin. One plugin can be instantiated multiple times, but each instance the instance name, callsign, must be unique.

References

Ref ID Description
HTTP HTTP specification
JSON-RPC JSON-RPC 2.0 specification
JSON JSON specification
Thunder Thunder API Reference

Description

SubsystemControl JSON-RPC interface.

This interface uses legacy lowercase naming convention. With the next major release the naming convention will change to camelCase.

Methods

The following methods are provided by the SubsystemControl interface:

Built-in methods:

Method Description
exists Checks if a JSON-RPC method or property exists

SubsystemControl interface methods:

Method Description
activate Activates a subsystem

exists method

Checks if a JSON-RPC method or property exists.

Description

This method will return True for the following methods/properties: exists, activate.

Parameters

Name Type M/O Description
params object mandatory ...
params.method string mandatory Name of the method or property to look up

Result

Name Type M/O Description
result boolean mandatory Denotes if the method exists or not

Example

Request

{
  "jsonrpc": "2.0",
  "id": 42,
  "method": "<callsign>.1.exists",
  "params": {
    "method": "methodName"
  }
}

Response

{
  "jsonrpc": "2.0",
  "id": 42,
  "result": false
}

activate method

Activates a subsystem.

Parameters

Name Type M/O Description
params object mandatory ...
params.subsystem string mandatory Subsystem to activate (must be one of the following: Bluetooth, Cryptography, Decryption, Graphics, Identifier, Installation, Internet, Location, Network, Platform, Provisioning, Security, Streaming, Time, WebSource)
params?.configuration opaque object optional A JSON string that holds the information applicable to the subsystem to be activated

Result

Name Type M/O Description
result null mandatory Always null

Errors

Message Description
ERROR_BAD_REQUEST Setting a subsystem to disabled is not supported

Example

Request

{
  "jsonrpc": "2.0",
  "id": 42,
  "method": "<callsign>.1.activate",
  "params": {
    "subsystem": "network",
    "configuration": {}
  }
}

Response

{
  "jsonrpc": "2.0",
  "id": 42,
  "result": null
}