Device Management Deployments In oneM2m Group Name: MAS Working Group Source: Timothy Carey, Alcatel-Lucent, Meeting Date: Agenda Item: MAS Working Group

Scope Device management considerations for oneM2M Focus is on underlaying network (including cellular) connected devices Device Management refers to – A. Application software and firmware management – B. Configuration management – C. Fault and performance management In the remaining of this slide-set the terms Device Management is used to refer to A+B+C unless otherwise stated

Device Management (Phones) Network operators operate the communications infrastructure that underlay M2M Services Network operator resources are sandboxed by the network operator approved firmware Typically devices have 1 Management Client that connects to the network operator’s management server

Device Management (M2M) Network operators operate the communications infrastructure that underlay M2M Services Network operator resources are controlled through firmware certification by the network operator Service Provider can deploy new firmwares OTA after network operator approval and certification

Device Management (M2M-alt0) Network operators operate the communications infrastructure that underlay M2M Services Network operator resources are sandboxed by the network operator approved firmware The network operator exposes capabilities to the M2M Service Layer The network operator restricts access rights to network operator resources within the M2M Service Layer by exposing accounts/capabilities to the M2M Service Platform.

Device Management (M2M-alt1) Network operators operate the communications infrastructure that underlay M2M Services Network operator resources are sandboxed by the network operator approved firmware The network operator permits access rights to application resources to the Service Provider Mgmt Server from the Network Operator Mgmt Server This deployment scenario exists in some implementations (e.g., OMA-DM) but not others (e.g., TR-069)

Device Management (M2M-alt2) Network operators operate the communications infrastructure that underlay M2M Services Network operator resources are sandboxed by the network operator approved firmware The Service Provider Mgmt Server and Network Operator Mgmt Server expose the capabilities to the M2M Service Platform. The Mgmt Client uses ACLs to authorize access to resources within the Device. The Network Operator is the owner of the ACLs. The Service Provider Mgmt Server and Network Operator Management expose their capabilities to the M2M Service Platform The Network Operator and M2M Service Provide agree on the ACLs out-of-band.

Device Management (M2M-memc) Network operators operate the communications infrastructure that underlay M2M Services Network operator resources are sandboxed by the network operator approved firmware within its own environment Application resources are sandboxed by the service provider approved firmware within its own environment

Device Management Principles When Network Operator and Application Resources share the same operating environment: – Network Operator resources are sandboxed by the Network Operator approved firmware – Network Operator (Underlying Network Layer Provider) delegates access rights to the upper layers (Service, Application) When Network Operator and Application Resources have different operating environments – Resources are sandboxed by the respective operator/provider approved firmware