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

3                                     Unleashing the potential of the Internet of Things

            8.9     Management

            8.9.1   Device management
            MOC devices cover a large area, exist for a long time and could be "on the move", so it may be
            difficult for operators or subscribers to manage these devices manually. Thus, MOC devices and
            gateways  should  be  managed  and  monitored  remotely  (for  example,  updating  the  firmware  to
            correct faults).
            MOC devices with a universal integrated circuit card (UICC) may be deployed outdoors without
            human  supervision  and  it  might  happen  that  a  given  UICC  is  put  into  another  device  without
            permission  of  the  UICC  owner.  Thus,  in  order  to  avoid  such  issues,  the  change  of  association
            between  an  MOC  device  and  UICC  should  be  accessible  by  MOC  applications  interacting  with
            those MOC devices.
            When MOC devices and gateways provide service logic, the MOC devices and gateways provide
            support capabilities for both the customer and the service. MOC devices and gateways are required
            to be managed in terms of both network and service management.
            The requirements of MOC device management are as follows:

            1)      MOC  applications  are required to  support mechanisms for managing  gateways acting as
                    traffic aggregators (a gateway aggregates traffic and acts as a channel).
            2)      MOC applications are required to monitor the state of various aspects of MOC devices and
                    gateways including:
                    a)  abnormal behaviour of MOC devices and gateways, such as an active service not being
                        aligned with the subscribed feature;
                    b)  the association between the MOC devices and gateways and the UICC;

                    c)  the attachment information of MOC devices and gateways, such as attachment location;
                    d)  the connectivity of MOC devices and gateways.
            3)      MOC applications are required to support mechanisms to perform simple and scalable pre-
                    provisioning of MOC devices and gateways, enable and disable features, report errors from
                    devices, and query device status.
            4)      MOC  applications  are  required  to  support  mechanisms  to  perform  software  upgrades
                    (e.g., provisioning of new service logic and/or bug  fixes  to  be loaded on devices and/or
                    gateways, including applications and system software).
            5)      MOC applications are required to manage low capability MOC devices using lightweight
                    mechanisms.

            8.9.2   Service profile management
            The service profile of a specific MOC application is composed by a set of information specific to
            that MOC application. It may include, but it is not limited to, the MOC application identifier, MOC
            application provider identifier and application data types.
            MOC applications have the following requirements:
            1)      MOC applications are recommended to use standard service profiles for registration and
                    discovery.
            2)      MOC applications are required to support mechanisms to perform service profile updates.

            8.9.3   Device profile management

            The MOC device profile is a set of information related to MOC devices and MOC gateways. As
            there are various types of MOC devices and MOC gateways, the device profiles are helpful in the
            management of large numbers of heterogeneous devices and gateways.



            270      Rec. ITU-T Y.4109/Y.2061 (06/2012)
   279   280   281   282   283   284   285   286   287   288   289