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

Unleashing the potential of the Internet of Things 3

MOC application requirements for the support of service integration and a delivery environment are
as follows:
1) MOC applications are recommended to be able to access service integration and delivery
environment capabilities provided by the network.
NOTE – Access to such an environment also provides access to application development and testing
capabilities.

8.7 Load balancing and robustness
In some application cases, e.g., in a river control application with the water level of the river
reaching the alert threshold, a large number of monitor points may send alert information to the
MOC capabilities in the NGN domain, including the possibility to send real-time video. Such
emergency scenarios require robustness of the network and MOC capabilities in the NGN domain.

The distribution of MOC devices across territories and the density of MOC devices in a certain area
may be high or low. This may cause an imbalance in the network and MOC capabilities in the NGN
domain for both signalling and data traffic.

In order to support network and MOC platform load balancing and robustness, the requirements are
as follows:
1) MOC applications require mechanisms in the network and MOC capabilities in the NGN
domain for load balancing.

2) MOC applications require a robust network and MOC capabilities in the NGN domain,
whilst also ensuring a sufficient level of QoS under given circumstances, e.g., emergency
scenarios.

8.8 Accounting and charging

Different charging and accounting requirements need to be addressed depending on the scenarios of
the MOC applications. For example, there are MOC applications with frequency data transmission
and small amounts of data, in this case charging and accounting may be based on the number of
communications. Some other MOC applications may rarely connect to the network but generate
large amounts of data for each communication, in this case charging and accounting may be based
on the amount of data. In other cases, charging and accounting may be based on the duration of
communications.

As an MOC application may use multiple devices for a single customer, charging per device by
MOC application providers or network providers would generate a lot of charging data records
(CDR) that impose a heavy load on some functions, e.g., the charging function. In these scenarios,
group-based accounting and charging instead of per device accounting and charging may be more
appropriate.

MOC applications have the following requirements:
1) MOC applications are required to support different charging and accounting methods, such
as charging based on the duration of communications, number of communications, amount
of transmitted data, etc.
2) MOC applications are recommended to support unified charging for customers.
3) When group-based support is enabled (see clause 8.12), MOC applications are required to
support online and offline accounting and charging based on groupings.

Rec. ITU-T Y.4109/Y.2061 (06/2012) 269