Page 289 - Unleashing the potenti al of the Internet of Things
P. 289

Unleashing the potential of the Internet of Things                         3


            2)      If  the  network  can  handle  data  collected  by  MOC  devices  according  to  relevant  data
                    categorization, MOC applications are required to manage these data accordingly.


            9       Requirements of NGN capabilities

            9.1     Requirements for extensions or additions to NGN capabilities
            This clause identifies extensions or additions to NGN capabilities defined in [ITU-T Y.2201] for the
            support of MOC applications.

            9.1.1   Numbering, naming and addressing
            NGN  provides  addressing  and  identification  capabilities.  The  service  requirements  specified  in
            clause 8.10 are supported by the existing capabilities of NGN [ITU-T Y.2201] [ITU-T Y.2702].

            Based  on  the  service  requirements  in  clause  8.12,  NGN  is  required  to  support  the  following
            additional numbering, naming and addressing requirements.

            1)      An  NGN  is  required  to  provide  group  based  addressing  mechanisms  for  the  support  of
                    MOC applications according to the NGN provider's policy.

            2)      An NGN is required to support a static MOC grouping capability.
            NOTE 1 – A static MOC group contains the members of the MOC devices and gateway which are pre-
            configured.
            3)      An NGN is required to support a dynamic MOC grouping capability.

            NOTE 2 – A dynamic MOC group may be generated upon request using specific criteria, such as location,
            status of MOC devices and gateway, etc.
            4)      An  NGN  is  required  to  support  the  MOC  grouping  capability  in  both  cases  of  groups
                    constituted by MOC devices and gateway directly or indirectly connected to NGNs.
            5)      An  NGN  is  required  to  map  the  MOC  group  identifier  to  network  addresses  of  MOC
                    devices and gateways of a static MOC group.
            6)      An NGN is required to identify the list of MOC devices and gateways and their network
                    addresses matching the specified criteria for a dynamic MOC group.

            9.1.2   Quality of service
            The differentiated quality of service and data prioritization requirements, specified in clause 8.13
            are supported by the existing capabilities of NGN [ITU-T Y.2201] [ITU-T Y.2221]. The following
            subclauses identify the requirements for extensions to NGNs.
            9.1.2.1    Per group QoS policy

            Based on the service requirements in clause 8.12, the following additional requirements are placed
            on NGNs:

            1)      An NGN is required to support a per group level QoS policy, in parallel with, or instead of,
                    a per device level QoS policy.

            NOTE – Per group QoS policy parameters include, but are not limited to:
            –       packet transfer delay
            –       packet delay variation
            –       packet loss ratio
            –       packet error ratio.

            9.1.2.2    Traffic control
            NGNs provide processing and traffic management capabilities. The service requirements specified
            in clause 8.7 are supported by the existing capabilities of NGN [ITU-T Y.2201].


                                                                  Rec. ITU-T Y.4109/Y.2061 (06/2012)     275
   284   285   286   287   288   289   290   291   292   293   294