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

3 Unleashing the potential of the Internet of Things

Based on the time controlled network communication requirements defined in clause 8.2, the
following additional requirements are placed on NGNs:
1) An NGN is required to allow MOC end users' access (e.g., attachment to the network or
establishment of a data connection) during a defined granted network communication
access time interval.

2) An NGN is required to reject MOC end users' access (e.g., attachment to the network or
establishment of a data connection), or allow it with different charging parameters, during a
defined forbidden network communication access time interval.
3) An NGN is required to allow the modification of granted network communication access
time intervals based on service criteria (e.g., daily network traffic load, MOC device
location).
4) An NGN is required to communicate granted network communication access time
schedules and durations to MOC devices and gateways.
5) An NGN is required to terminate MOC end users' access (e.g., detachment from the
network or release of a data connection) when a network communication access time
duration has ended.
6) An NGN can optionally support the communication of granted network communication
access time schedules and durations to other MOC end users than the MOC devices and
gateway (e.g., MOC application server).

Based on the resource usage requirements in clauses 8.3 and 8.16, the following additional
requirements are placed on NGNs:

7) An NGN is required to page the target MOC devices and gateways before service
interaction when the network needs to initiate a service.

8) An NGN is required to establish communication resources only when data transmission is
required.

Based on the requirements in clause 8.12, in addition to the existing NGN traffic control
capabilities, an NGN is required to support:
9) optimized handling of group communications in order to save network resources and to
prevent network congestion;

10) per group level traffic control in parallel with, or instead of, per device level traffic control.
NOTE – Per group level traffic parameters include, but are not limited to:
– maximum allowed packet size
– data rate and the bucket size
– peak rate and peak bucket size
– sustainable rate and sustainable bucket size.

9.1.3 Accounting and charging
Based on the service requirements in clause 8.8, the following additional requirements are placed on
NGNs [ITU-T Y.2233]:
1) An NGN is required to support group-based accounting and charging for either or both
online charging and offline charging in parallel with, or instead of, per device level
charging.
9.1.4 Mobility

NGNs provide mobility support for end users, MOC devices and gateways [ITU-T Y.2201]
[ITU-T Q.1706].

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