HSTP Operation
An HSTP compatible-system sends an HSTP message to another HSTP compatible system in the form of an HSTP OPERATION, passed over some transport protocol.
HSTP OPERATION requests and responses are encoded using profile encoding formats defined by the HSTP Implementation Specification, e.g., JSON, OData, JSON-LD, GraphQL. The system that sends an HSTP OPERATION request is the “requester”, and the system that is meant to receive the message is the “target”
For more detail, see section 7.3.3.1. HSTP OPERATIONs in the IEEE P2874 system specification, and the DRAFT HSTP Implementation Specification.
Default Operations
The HSTP.d node is configured to handle a set of default HSTP OPERATIONs, which provide the functionality needed to discover and execute activities, and to perform CRUD operations on the UDG
The operation type to be executed is specified in the hstp_v1:request_type field
Activity Operations
An activity is a behavior or logic that can be executed by HSML-compliant systems.
For more detail, see section 6.4.4. ACTIVITIES in detail in the IEEE P2874 system specification.
EXECUTE_ACTIVITY This operations executes an activity by name on a node that supports that activity
REGISTER_ACTIVITY_EXECUTOR This operations registers an activity on a node, binding the activity name with its SWID and network address
FIND_ACTIVITY_EXECUTOR This operation returns all the registered activity executors (SWID and address) bound to a given activity name
CRUD Operations
CREATE_ENTITY
QUERY_ENTITY
UPDATE_ENTITY
DELETE_ENTITY
Discovery
GET_SUPPORTED_OPERATIONS This operation returns a list of all the operations supported by the HSTP.d node
GET_SUPPORTED_ACTIVITIES This operation returns a list of all the activities supported by the HSTP.d node
HSTP Request
For more detail, see section 7.3.3.2. HSTP OPERATION request in the IEEE P2874 system specification.
HSTP Response
For more detail, see section 7.3.3.3. HSTP OPERATION response in the IEEE P2874 system specification.
Last updated