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

3 Unleashing the potential of the Internet of Things

Due to the limited capabilities of the MOC devices with no support of authentication and
authorization functionalities, MOC applications have the following requirements:
1) Before MOC device resources can be used by MOC end users and MOC applications,
MOC applications are required to support mechanisms for the authentication and
authorization of MOC end users and MOC applications for their access to MOC device
resources.

8.15 Device association and interaction with multiple applications
In some application scenarios, a single MOC device may be required to communicate with different
MOC applications simultaneously. For example, when a traffic accident happens, the damaged
vehicle may be required to provide information to both the health service centre and the department
for traffic control.

MOC applications have the following requirements:
1) MOC applications are required to not prevent the delivery of information to other MOC
applications by an MOC device or gateway associated with that MOC application.
2) MOC applications are required to not prevent an MOC device or gateway associated with
that MOC application to receive information from other MOC applications.
NOTE – In this Recommendation, it is assumed that the capability of an MOC device or gateway to
communicate with multiple applications is controlled by the network (i.e., NGN). Requirements of an MOC
device or gateway with "network control independent capability" to communicate with multiple applications
are for further study.

8.16 Communication with sleeping device
In the case of offline status for a given period of time, MOC devices enter or stay in sleep mode in
order to:
– save power, especially for devices using a battery
– save network resources, especially for devices with wireless network access.
NOTE – Sleep mode is an energy-saving mode. It normally refers to an MOC device in a situation when,
traffic is not being generated for a period of time, device sessions and related traffic channels are released to
save resources, and all unnecessary components are shut down. According to certain criteria, an MOC device
in offline status can enter sleep mode.

MOC applications have the following requirements:
1) MOC applications are recommended to be able to send instructions to a sleeping MOC
device to wake it up.

2) MOC applications are required to support network-initiated communications towards a
sleeping MOC device.

8.17 Differentiation and handling of collected data
With the large variety of data collected by MOC devices being transmitted in the network, it is
expected that the network be able to differentiate particular collected data from other data, and then
trigger the relevant processes based on their category. For example, the network may cache and
only later forward data which are collected in non-network performance sensitive applications. On
the other hand, the network is required to immediately transmit high priority data which are
collected in network performance sensitive applications.
MOC applications requirements for collected data differentiation and related handling are as
follows:
1) MOC applications are required to enable the identification and categorization of the data
collected by MOC devices according to relevant policies.

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