Page 406 - 2015 Security in Telecommunications and Information Technology
P. 406

4                                     Unleashing the potential of the Internet of Things

            5)      It  is  recommended  that  specific  QoS  applications  intended  for  pledging  of  security  of
                    decisions be provided.
                    NOTE 2 – Clause 8.14 provides further information and requirements about pledging of security of
                    decisions.

            8.13    Management
            1)      SCN applications are required to allow the user to enable and disable the provided services.
            2)      SCN  applications  are  required  to  allow  the  user  to  apply  different  policies  concerning
                    allowing and denying specific commands to actuators.
            3)      SCN applications are recommended to provide the user with the ability to personalize the
                    services.

            8.14    Pledging of security of decisions

            The  decision-making  process  in  SCN  applications  includes  different  activities  on  different  SCN
            objects  and  can  be  very  complicated.  As  a  result,  there  are  a  number  of  sources  of  errors  in
            decisions including erroneous, outdated, incomplete data and object synchronization errors. Some
            erroneous decisions of SCN applications can entail considerable negative consequences.
            1)      SCN  applications  are  required  to  provide  measures  to  avoid  considerable  negative
                    consequences  of  their  decisions  on  condition  that  all  the  actuators  carry  out  commands
                    given by the SCN applications exactly.

            2)      SCN applications are required to provide all the necessary measures to identify the party
                    responsible for erroneous decision operations entailing considerable negative consequences.

            3)      SCN applications are required to  provide operational logging sufficient to  determine  the
                    source of errors entailing considerable negative consequences.


            8.15    Open service environment (OSE) support
            SCN applications can optionally support open service environment (OSE) capabilities as described
            in [ITU-T Y.2020] and [ITU-T Y.2234].
            In  case  of  SCN  applications'  support  of  OSE  capabilities,  SCN  applications,  services,  actuators,
            motes and mote groups are recommended to be registered beforehand in order to enable the ability
            to be discovered (by specifying one or more related attributes).
            It may be desirable for the user to use the same application in different SCN infrastructures. As the
            user  changes  his  location  and  moves  to  another  SCN  infrastructure,  service  discovery  is
            automatically  started  to  check  if  that  SCN  infrastructure  provides  the  required  services.  If  these
            services are not registered, the SCN application may try to use a service composition procedure to
            create  the  required  services  from  other  existing  services  based  on  the  capabilities  of  the  SCN
            infrastructure.  A  service  description  language  and  its  associated  execution  framework  are
            recommended to be provided to support service registration, discovery and composition.

            The  following  requirements  are  identified  in  the  case  of  SCN  applications'  support  of  OSE
            capabilities:
            1)      It  is  recommended  to  support  registration  and  discovery  of  SCN  applications,  services,
                    actuators, motes and mote groups.
            2)      It is recommended to support at least one service description language and its associated
                    execution framework.
            3)      Automatic service discovery and service composition can be optionally supported.







            392      Rec. ITU-T Y.4250/Y.2222 (04/2013)
   401   402   403   404   405   406   407   408   409   410   411