Page 684 - Unleashing the potenti al of the Internet of Things

5 Unleashing the potential of the Internet of Things

Table 3 – EHM components and data storage capability of SSAS layer

EHM components Data storage
EHM end point None

EHM terminal The EHM application data stored in the SSAS layer of the EHM terminal
EHM gateway and EHM gateway are required to be marked with collection time.
IoT platform The EHM application data stored in the SSAS layer of the IoT platform and
EHM application server are required to be associated with time information,
EHM application server e.g., collection time and expiration time.

8.3.3 Time synchronization

According to the capability requirements described in clause 9.3.4 of [ITU-T Y.2065], the SSAS layer
of the EHM terminal, EHM gateway, IoT platform and EHM application server is required to be able
to retrieve time parameters from authoritative time servers or via other ways.

The SSAS layer of the IoT platform is required to be able to publish the time parameters to the EHM
gateway, EHM terminals and EHM application servers. It is recommended that the time parameters
be published periodically.

8.3.4 Location provisioning
According to the capability requirements described in clause 9.3.5 of [ITU-T Y.2065], the SSAS layer
of the EHM terminal and EHM gateway is required to collect the location information from the
network layer or device layer according to the collection strategy, such as event-triggered collection
or periodic collection.

According to the capability requirements described in clause 9.3.5 of [ITU-T Y.2065], the SSAS layer
of the EHM terminal and EHM gateway is required to report the location information required by the
application layer in standard format.

According to the capability requirements described in clause 9.3.5 of [ITU-T Y.2065], the SSAS layer
of the IoT platform and EHM application server is required to be able to collect the position of EHM
terminals and gateways according to the collection strategy, such as event-triggered collection.

8.3.5 Service accounting and charging
According to the capability requirements described in clause 9.3.1 of [ITU-T Y.2065], the SSAS layer
of the IoT platform is required to gather data about the usage of EHM services for charging purposes.
Different policies may be considered for service accounting and charging, e.g., the number of times
the service is used, the amount of time the service is used or the volume of used service data.
The service accounting and charging capability in the SSAS layer of the IoT platform has the
following requirements:
1) It is required that service accounting and charging be provided to EHM service users.
2) It is recommended that service accounting and charging be provided according to the QoS of
EHM services.
3) It is recommended that service accounting and charging also be provided in support of
roaming scenarios for EHM services among networks owned by different network providers.
4) It is recommended that service accounting and charging be provided according to the
frequency of access to EHM services.
5) As a user may use several EHM devices at the same time, it is recommended that unified
service charging per user be supported.

670 Rec. ITU-T Y.4408/Y.2075 (09/2015)