The functions of the VE & IoT Service Monitoring FC are to assert static
associations, i.e. create a new static association between VE‘s and services
described by the provided association, discover dynamic associations, i.e.
create a new dynamic or monitored association between VE‘s and Services,
update the association and delete the association from the VE Resolution
framework.
Finally, the VE Service FC handles with entity services. An entity service
represents an overall access point to a particular entity, offering means to learn
and manipulate the status of the entity. Entity services provide access to an
entity via operations that enable reading and/or updating the value(s) of the
entities‘ attributes. The type of access to a particular attribute depends on the
specifics of that attribute (read only / write only or both).
A specific VE service can provide VE history storage functionality, to publish
integrated context information (VE context information - dynamic and static), VE
state information, VE capabilities.
The two functions currently defined for the VE Service FC are to read and set
an attribute value for the entity.
It is not required to have an explicit register for Virtual Entities, but the VE
Resolution FC could be extended in order to be used in that way. The important
aspect is to agree on how to assign identifiers to Virtual Entities.For modelling
any other aspect of the Virtual Entity, a Virtual Entity service can be used that
gives you access to all information about a Virtual Entity. This can be current
sensor information, as well as historic information. Historic information would
typically be stored in a database, which can be modelled as a Network
Resource (see Section 3.3.3).
4.2.2.5 IoT Service
The IoT Service FG (see Figure 36 ) contains IoT services as well as
functionalities for discovery, look-up, and name resolution of IoT Services. It
consists of two Functional Components:
IoT Service ; IoT Service Resolution.