Standards Development
The 3rd Party HBES IoT API consists of:
• Required restful access methods to read or write Endpoints, to set or retrieve Installation state data.
• Required Endpoints hosting concepts such as Functions and Datapoints comprising the Runtime communication of an (HBES) Installation.
• Required methods to authorize from an IoT 3rd Party Client, additionally, such as the security methods to be used to access the API.
• Required access permission control types: for security reasons the actual access to Functions or Datapoints is gated by the IoT 3rd Party Server, this access will be granted as part of the authorization.
• Endpoints allowing to setup notifications on changes of Installation state data, provided to subscribers that are clients to the Installation.
• For all Endpoints, their expected request/ response document formats, and their content. Moreover, their mandatory and optional parts
The HBES protocol as enshrined in the EN50090 series is a well described protocol that is used by many manufacturers worldwide. Interfacing to an installation containing EN50090 compliant products requires the support of the EN50090 protocol. In order to allow 3rd Parties access to the data of EN 50090 compliant installations, an IoT 3rd Party API is defined, which allows to fetch the data without needing the full support of the EN50090 protocol by the products accessing the data.
You are now following this standard. Weekly digest emails will be sent to update you on the following activities:
You can manage your follow preferences from your Account. Please check your mailbox junk folder if you don't receive the weekly email.
You have successfully unsubscribed from weekly updates for this standard.
Comment on proposal
Required form fields are indicated by an asterisk (*) character.