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

Unleashing the potential of the Internet of Things 3

The security capability provides encryption and integrity protection on data exchanged with the
NGN and MOC applications to ensure secure delivery.
The security capability performs key management based on the service keys generated in MOC
devices, and protects from unauthorized applications' access to MOC devices.

11.3.6 Communication
Based on the requirements identified in clauses 10.3, 10.6, 10.8 and 10.9, this capability performs
the generic communication functions in the MOC devices and gateway.
The communication capability provides application data transport functions, delivers and receives
data to/from MOC applications in accordance with the service criteria (e.g., daily network traffic
load, MOC device location, access time schedules and durations), and handles these data.

11.4 MOC service interfaces

The MOC service interfaces support:
– MOC applications hosted in MOC devices and gateways, which access NGNs via UNI;
– MOC applications hosted in MOC devices and gateways, which access the MOC
capabilities hosted in the MOC gateway via ACI;
– MOC applications hosted in MOC devices, which access the MOC capabilities hosted in
those same MOC devices via ACI;
– MOC applications hosted in the MOC service domain, which access the NGN via ANI.
– MOC applications hosted in the MOC service domain, which access the MOC capabilities
of other networks via NNI.
MOC applications hosted in MOC devices and gateways can be invoked by an MOC end user and
other MOC applications, e.g., MOC applications hosted in the MOC service domain.
MOC service interfaces are recommended to implement standardized APIs, protocols and
technologies to realize the service exposure towards MOC applications.

11.4.1 Service interface requirements across ACI

The service interface across the ACI is used to provide interaction in the MOC device domain
between the MOC capabilities of devices and gateways and MOC applications of devices and
gateways. The service interface across the ACI allows an application residing in an MOC device to
access MOC capabilities in the same MOC device or in an MOC gateway. It also allows an
application residing in an MOC gateway to access MOC capabilities in the same MOC gateway.

The ACI is required to enable the following functions:
– registration of the MOC devices and gateway to the MOC capabilities in the MOC device
and gateway (e.g., registration of a sensor or GPS in a car to the gateway in the car);
– MOC applications' execution requests of an MOC device-specific tasks by an MOC device
and gateway or group of MOC devices and gateways;
– subscription and notification to specific events (e.g., mutual subscription and notification to
specific events (e.g., connectivity of the MOC devices and gateway) between MOC
capabilities and applications);

– the MOC devices and gateway's requests of group creation, deletion and members' listing.
11.4.2 Service interface requirements across UNI

The service interface across the UNI is used to provide interaction between the MOC capabilities of
MOC devices and gateways and the MOC capabilities of the NGN. The UNI is recommended to

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