ProSyst Remote Manager 6.1

Transcription

1 PrSyst Remte Manager 6.1 Features Bsch Sftware Innvatins Overview f revisins INST/PSY Anastas Chbanv Status: July 2017

2 Remte Manager 6.1 Overview f revisins Date Changes/Cmments Authr Migratin t the new layut /Naming changes. Anastas Chbanv Bsch Sftware Innvatins GmbH 2

3 Remte Manager 6.1 Cntent 1 REMOTE MANAGER FUNCTIONAL OVERVIEW DEVICE MANAGEMENT FEATURES Remte Manager Generic Device Management Framewrk Device Management Device Registratin and Initial Prvisining Remte Manager Management Prtcl Device Directry Retrieving and String f the Device Cnfiguratin Framewrk Settings Management Bundle Management Generic Sftware Management OS-Level Management and Mnitring Bundle Cnfiguratin (Settings) Management Preferences Data Management and Data Synchrnizatin Prviding f Custm Management Interfaces Hme Netwrk Devices Management Retrieving Device Lgs Fault Alerts Applicatin Mnitring TR-069 Device Management TR-069 Device Management Mbile (OMA DM-Based) Device Management Mbile Device Types Generic OMA DM Supprt Mbile Management Objects SOFTWARE REPOSITORY REMOTE MANAGER GUI MANAGEMENT CONSOLE API AND INTEGRATION INTERFACES SECURITY User Authenticatin and Authrizatin User Authenticatin User Authrizatin Secure Netwrk Cmmunicatin Bsch Sftware Innvatins GmbH 3

4 Remte Manager Certificate Management REMOTE MANAGER SCALABILITY AND HIGH AVAILABILITY Single-server cnfiguratin Dynamic-clustered cnfiguratin Mixed-clustered cnfiguratin PLATFORM REQUIREMENTS Hardware Requirements OS & JVM Requirements Supprted Framewrks fr Remte Manager Management Agents Database Requirements DB Strage Space Supprted Nn- Devices APPENDIX A: RESOURCES Bsch Sftware Innvatins GmbH 4

5 Remte Manager Remte Manager Functinal Overview PrSyst s IT platfrm prvides yu with a set f ready services that can be used as building blcks fr yur IT applicatins. Bsch Sftware Innvatins GmbH 5

6 Remte Manager Device Management Features PrSyst s Remte Manager is a backend management and mnitring system, supprting centralized cnfiguratin, sftware prvisining and service peratin supprt fr varius class f devices based n (but nt limited) t, OMA-DM and/r TR-069 standards. In shrt, the Remte Manager is applicable t realize these use cases: Platfrm, Applicatin & Service Lifecycle Management Firmware & File Update Remte Cnfiguratin & Sftware Prvisining Remte Diagnstics (life status checks, lgging, mnitring, etc.) Remte Security Administratin The Remte Manager is nt limited t these use cases as supprt fr additinal cases (standardized r custmized) can be added at any time. Remte Manager is unique in its penness, bsting rapid adptin f new requirements and integratin with 3 rd party systems. The pen design has the fllwing dimensins: Open fr additinal (i.e. custm) management prtcls Open fr custm business lgic extensins hsted n the Remte Manager Open fr integratin with 3rd party systems thrugh an extensive set f APIs (Java, REST/HTTP, SOAP r JEE JCA based APIs) Open fr custmized management cnsles (UIs) Remte Manager - the PrSyst Backend management system caches all the sensrs/actuatrs infrmatin. This allws autmatin f rules nt nly n the device itself r lcally in bridge devices but als in a clud. The Remte Manager als acts as a prxy fr cnnecting the end user devices like smart phnes r tablets t the gateways. The Remte Manager is in prductin use in many deplyments in varius vertical markets such as: Cnnected Hme, Fleet Management, ehealth Devices and IT scenaris. This dcument describes the main features f the Remte Manager system. 2.1 Remte Manager Generic Device Management Framewrk The fundatin f the Remte Manager system is a general mdel and framewrk fr management and mnitring f varius device types in a unifrm way. The Generic Device Management framewrk emplys a general abstractin fr device representatin and a number f basic features, which are cmmn fr management and mnitring f any device type - regardless f the cncrete device capabilities, the netwrk cmmunicatin prtcls and the management interfaces supprted by the device. The interface t the devices f particular type is prvided by a set f plugins (adapters), which adapt the cncrete device management interface (e.g. OMA DM, TR-069, etc) supprted by the devices t the cmmn device mdel f the Remte Manager. Bsch Sftware Innvatins GmbH 6

7 Remte Manager 6.1 This mdel allws extending f the Remte Manager with supprt f new device types with minimal effrt, leveraging the basic cmmn device management functinality. Remte Manager prvides build-in supprt fr the fllwing device classes: devices running cmpliant framewrks like residential gateways, hme device cntrllers, set-tp-bxes, Telematics head units, etc. mbile devices supprting Mbile R4 specificatin (JSR - 232) mbile devices supprting OMA Device Management prtcl (versin 1.1 and 1.2) devices supprting CPE WAN Management prtcl (TR-069) defined by Bradband Frum 2.2 Device Management Remte Manager supprts management f devices equipped with R5 cmpliant framewrk. In rder t enable an device t be managed by the Remte Manager, it has t be equipped with the Remte Manager Management Agent. The Remte Manager Management Agent represents a set f bundles installed n the target framewrk f the device. Bsch Sftware Innvatins GmbH 7

8 Remte Manager 6.1 The Remte Manager Agent cmmunicates with the management server ver PrSyst prprietary messaging prtcl. This apprach prvides rich and efficient management and mnitring functinality f the standard framewrk and applicatin resurces (bundles, cnfiguratin settings, lg messages, user preferences, security permissins), as well as management and mnitring f sme f the OS level elements, like prcesses, platfrm resurce utilizatin (RAM, CPU, netwrk interfaces) and applying f OS level sftware updates. The prtcl is pen fr extensins prviding management and mnitring capabilities t custm platfrm and/r applicatin specific resurces Device Registratin and Initial Prvisining Prsyst s Remte Manager keeps recrd f each manageable device. The prcess f inserting the recrd abut a particular device int the Remte Manager database is referred as device registratin. Remte Manager supprts tw general mdels fr device registratin: Explicit registratin infrmatin abut a new device is added thrugh the Remte Manager backend either by a custm applicatin (thrugh the Remte Manager API) r manually - by the peratr (thrugh the Remte Manager GUI cnsle). This methd implies that device is registered befre it cnnects t the Remte Manager fr the first time. Remte Manager supprts assigning f initial set f cnfiguratin settings t the registered device which will be applied upn first device cnnectin. Autmatic a new device is autmatically registered in the Remte Manager when it cnnects t the backend server fr the first time. Remte Manager autmatically retrieves the device identificatin and cnfiguratin infrmatin and stres it int the Remte Manager DB. This mdel can be disabled if there is such requirement (e.g. fr security reasns) and then nly explicitly registered devices are t be allwed t cnnect t the Remte Manager system. In rder t becme manageable by the Remte Manager, the device must be prvisined with the Remte Manager Management Agent bundles and suitable cnfiguratin settings fr establishing management sessin with the server. This prcess is called initial prvisining. Remte Manager supprts tw general ways fr initial prvisining: Pre-prvisined the Remte Manager Management Agent and the related cnfiguratin can be pre-installed n the device and/r manually prvided upn device deplyment. Dynamically prvisined the Remte Manager / mbs prducts supprt the standard Initial Prvisining mechanism, which defines the prvisining f the framewrk with the agent bundles and the related cnfiguratin settings needed fr cnnecting t a particular management system (frm arbitrary vendr). In rder t start the initial prvisining prcess, the Initial Prvisining Service has t be prvided with settings fr cnnecting t a prvisining server (e.g. URL, device ID, authenticatin parameters). These initial prvisining settings can be prvided either thrugh static cnfiguratin f the framewrk, r can be prvided dynamically by custm mdule/applicatin. Remte Manager can act as an Initial Prvisining server, but it is als pssible t use a separate prvisining server Remte Manager Management Prtcl The cmmunicatin between Remte Manager Management Agent running n the manageable devices and the Remte Manager server is based n PrSyst prprietary cmmunicatin mechanism - Remte Manager Message Service. The Remte Manager Bsch Sftware Innvatins GmbH 8

9 Remte Manager 6.1 Message Service utilizes a highly ptimized binary prtcl - in regards f netwrk data vlume, CPU and memry utilizatin (n device and n server side). Sme f the key features prvided by the Remte Manager Message Service are: Asynchrnus and synchrnus message-based cmmunicatin. Bi-directinal message exchange between the backend server and the devices - bth the server and device can instantly send messages t each ther. Cmmunicatin sessins the messages are carried ver an active management sessin. The netwrk cnnectin is always initiated by the device, but nce the sessin is pen the server can als send messages t the device (server push). Remte Manager supprts different mdels fr sessin establishment: Always nline mde in this mde, the Remte Manager Management Agent tries t maintain the management sessin permanently active - nce the sessin is pen, it is kept alive indefinitely and if it is clsed due t sme netwrk prblem - the agent peridically tries t re-establish it. Peridical cnnectin the cnnectin is pen at scheduled time intervals (e.g. nce per day r week) and after the device updates its status and executes any pending peratin fr it the sessin is clsed (r kept active nly fr sme cnfigured time interval f inactivity). Event-driven the cnnectin may be pen in result f fault alert r errr lg message generated n the device, which must be instantly sent t the backend. By user r applicatin request thrugh the Remte Manager Management Agent API. Remte Manager Message Service can perate ver varius netwrk transprt prtcls the design is based n pluggable transprt binding cmpnents, which handle underlying cmmunicatin mechanism. Remte Manager prvides build-in transprt bindings fr TCP, SSL/TLS, HTTP(S) and UDP netwrk prtcls. Bindings fr additinal transprt prtcls can als be added. Optinal secure transprt layer (in additin t the SSL/TLS based ne), which prvides secure certificate based authenticatin and data encryptin capabilities n tp f any f the available transprt bindings. The secure transprt layer is useful nly if the underlying transprt binding des nt prvide build-in security features (e.g. UDP) Device Directry Remte Manager prvides flexible and cnvenient mechanisms fr gruping, filtering and searching f the registered devices by varius built-in and user defined device characteristics and status. Remte Manager supprts tw appraches f device gruping (which can be cmbined): Static device gruping the devices can be statically rganized in user-defined grups. The grups can be rganized hierarchically, i.e. ne grup may have sub-grups, in arbitrary level f nesting. The devices can be mved by the peratr frm ne grup t anther - at any time. Dynamic device gruping The Remte Manager supprts defining f custm grups based n specified filtering cnditin. The members f such grups cnsist f the devices which satisfy the specified cnditin. The cnditin can be an arbitrary expressin based n any f the static and the dynamic characteristics f the device maintained by Remte Manager - e.g. nline status, device capabilities (e.g. HW, OS, parameters, etc.), available sftware cmpnents, their runtime status and cnfiguratin, etc. including additinally assciated custm prperties with the devices. Bsch Sftware Innvatins GmbH 9

10 Remte Manager 6.1 Device gruping helps peratr t mnitr and lcate devices thrugh the Remte Manager GUI cnsle and can be als used fr targeting f Tasks and Rules (e.g. perfrm particular task r rule ver the devices belnging t a given grup). The Remte Manager als prvides features fr direct searching f devices either by unique identifier r by mre cmplex filtering cnditin (as fr the dynamic grups). The Remte Manager supprts assciating f additinal custm prperties with each single device r with whle device grup. When such prperty is assciated with a device grup it is inherited by all sub-grups and devices belnging t that grup. Example fr such prperties can be: lcatin, custmer-related data, address, prperties fr integratin with external systems, etc. These prperties are in the frm f key-value pairs, where the keys are strings and the values can be f type: string, integer, blean, byte, duble r arrays f the abve mentined. Manipulating f these prperties can be dne either manually - thrugh the Remte Manager GUI cnsle, r by custm applicatins thrugh the Remte Manager APIs Retrieving and String f the Device Cnfiguratin Remte Manager cllects, retrieves and stres in the database cnfiguratin and status infrmatin abut each device it manages. The cnfiguratin data retrieved and stred by the Remte Manager includes: Device capabilities the characteristics f the device hardware (e.g. CPU mdel, RAM, Flash/HDD size, etc.) and sftware platfrm (OS name and versin, JVM vendr and versin, framewrk vendr, supprted specificatin versin, available sftware cmpnent/mdules, etc). framewrk and JVM cnfiguratin settings and status. Available bundles and applicatins, their status and cnfiguratin, registered services and bundle security permissins. OS packages, prcesses, and platfrm resurce utilizatin statistics. Fault alerts, errr/warning lg messages the type and cntent pattern f the lg messages that are sent autmatically t the server can be cnfigured, but the peratr is able t explicitly retrieve any type f lg messages n demand. Hme netwrk devices cnfiguratin and status this includes the data frm the devices in the hme netwrk accessible thrugh the framewrk acting as residential gateway r hme device cntrller. Cnfiguratin f the additinal custm resurces. Custm mnitrable data. The infrmatin is cllected and transferred t the management server by the Remte Manager Management Agent either autmatically (implicitly) r n-demand (upn explicit request). The exact type f data which is subject f autmatic synchrnizatin can be cnfigured, while the infrmatin that is nt synchrnized autmatically - is delivered t the backend n demand. Device cnfiguratin synchrnizatin is an ptimized prcess it des nt lead t transferring f full infrmatin abut the cnfiguratin and status every time (unless the device cnnects fr the first time t the Remte Manager), but nly checksums and changes. The mechanism can be described briefly as fllws: Bsch Sftware Innvatins GmbH 10

11 Remte Manager When the device cnnects t the backend (Remte Manager server) the changes in the device cnfiguratin are transferred t the server and updated in the Remte Manager database. If the device cnnects fr the first time, this step effectively retrieves and stres full device cnfiguratin data (which is subject f autmatic synchrnizatin). 2. Once the sessin is established the device (Remte Manager Management Agent) instantly sends update events fr changes ccurred in the device cnfiguratin and state (the data which is subject t autmatic synchrnizatin e.g. applicatin started/stpped, changed prperties, fault alerts and applicatin alarms, errr/warning lg messages, etc). This data is updated in the Remte Manager database and apprpriate ntificatins are sent t the interested applicatins. The device cnfiguratin data is available t system peratrs thrugh the Remte Manager GUI management cnsle, and t the custm backend applicatins thrugh the Remte Manager API Framewrk Settings Management Remte Manager supprts retrieval and remte manipulatin f the glbal framewrk parameters: Framewrk start level cmpatible with Start Level specificatin /JVM system prperties Framewrk security plicy includes management f default bundle permissins and cnditinal permissins, cmpatible with the Permissin Admin and Cnditinal Permissin Admin specificatins Bundle Management Remte Manager supprts management f based sftware n tw alternative levels f granularity: Lw-level bundle management prvides management f separate bundles n the target device: Cllects infrmatin abut installed bundles fr each device installed thrugh either the Remte Manager r via any ther surce (r preinstalled in the framewrk). Prvides infrmatin abut static prperties and runtime status fr each bundle manifest headers, ID, lcatin, start level, state (STARTED, RESOLVED, INSTALLED, etc.) as well as registered services at runtime. Prvides means fr remte life-cycle management f bundles installing f new bundles and starting/stpping/updating/uninstalling f the existing bundles. High-level service applicatin management supprts lgical gruping f a set f (ne r mre) sftware cmpnents (e.g. bundles, Deplyment Packages) and pssibly additinal resurces and cntent files and prvides ability t prvisin and manage their lifecycle (update, start/stp, uninstall) tgether as a whle applicatin, handling issues like dependency and cmpatibility reslving, sharing f cmpnents between applicatins, etc. bundle management features described in this pint perate directly ver the standard API f the framewrk. Bsch Sftware Innvatins GmbH 11

12 Remte Manager Generic Sftware Management Remte Manager supprts remte sftware cmpnents deplyment and lifecycle management based n the Sftware Admin service f the PrSyst mbs Runtime and mbs SDK. The Sftware Admin service prvides universal facade fr installatin and life-cycle management f sftware cmpnents f different types e.g. bundles, deplyment packages, midlets, widgets, OS mdules (Debian Packages, IPKGs, etc), Andrid applicatins (APK). The Sftware Admin emplys a pluggable mdel which allws adding supprt fr new sftware cmpnent types t be achieved by develping and installing f crrespnding plugins (in the frm f bundles) n the framewrk. The mdel can be used fr manipulatin f the sftware nt nly n the lcal device running the framewrk / Sftware Admin service but als t ther hme devices cnnected t the device OS-Level Management and Mnitring System mnitring prvides infrmatin abut the current hardware cnfiguratin and current utilizatin f the platfrm resurces CPU lad, free/ccupied RAM, netwrk interfaces utilized bandwidth and traffic statistics, strage (HDD, flash) free ccupied space. OS prcess management prvides infrmatin abut the currently running OS prcesses n the target device and status infrmatin abut each prcess PID, cmmand line, status, used memry, pririty. Prvides the means t start new and stp f the running OS prcesses. Native sftware deplyment and update prvides supprt t retrieve infrmatin abut installed native packages n devices as well as ability t uninstall/update/uninstall these packages remtely. Remte Manager supprts management f Debian and ipkg packages, as well as a ZIP based package frmat - fr devices that d nt have build-in package management capabilities. Distributin f sftware as ZIP Packages prvides generic way fr sftware distributin. The ZIP package may cntain arbitrary file/dir cntent, which is extracted t a specified directry n the target device. The ZIP package may ptinally cntain tw OS shell scripts install.sh and uninstall.sh, which are executed by the Remte Manager Management Agent upn ZIP package installatin and uninstallatin respectively Bundle Cnfiguratin (Settings) Management Remte Manager supprts retrieving and remte manipulatin f the bundle cnfiguratin settings thugh the standard Cnfiguratin Admin service. Cnfiguratin settings management is applicable t bth system level and applicatin bundles installed n the target framewrk Preferences Data Management and Data Synchrnizatin Remte Manager Preferences service is a data strage service cmpatible with Preference Service specificatin. It allws string f applicatin data assciated it particular device r user f the Remte Manager system. The data is maintained persistently in the Remte Manager backend database, but can be als replicated lcally n the target devices, where it can be accessed and pssibly changed thrugh the Preferences service APIs. In this way the preferences data can be accessed/manipulated either by backend-side applicatins (including Remte Manager GUI cnsle) r by device-side applicatins. The Remte Manager Preferences service prvides efficient bi-directinal data synchrnizatin Bsch Sftware Innvatins GmbH 12

13 Remte Manager 6.1 mechanism fr replicating changes in the preferences data between the device-side preferences strage and the central backend data base Prviding f Custm Management Interfaces Remte Manager and mbs SDK prvide a pwerful mechanism fr extending the management capabilities f the system, by exprting management interface t custm resurces. The mechanism is based n the s called Cntrl Unit mdel. The cntrl unit data mdel allws unified representatin f diverse type f resurces (devices, sftware r hardware cmpnents, etc.) alng with a cmmn way t manage and mnitr these resurces. The key characteristics f the cntrl unit data mdel are: State variables represent the status and cnfiguratin infrmatin f the mdeled resurce Actins determine the peratins which can be perfrmed ver the mdeled resurce Type and identifier f cntrl units identifies uniquely the cntrl unit instances Hierarchy f cntrl units cntrl units can be rganized hierarchically, allwing mdeling f mre cmplex systems (by decmpsing them in sub-subsystem mdel as separate subcntrl units) Cntrl Unit Meta-data prvide infrmatin abut the state variables and actins supprted by particular cntrl unit as well as infrmatin t the user Custm bundles may prvide cntrl unit cmpliant interface t a particular resurce by implementing a dedicated java interface and registering it as an service n the target platfrm. The Remte Manager agent autmatically discvers the exprted cntrl units and makes them available fr management thrugh the Remte Manager server, including: Retrieving f the cntrl unit state (cntrl unit instances and their state variables) String cntrl unit data in the Remte Manager database Viewing and manipulating cntrl units thrugh the Remte Manager GUI cnsle and thrugh the Remte Manager API Invking f the cntrl unit actins either n a single cncrete device r in the scpe f the tasks executin r rule Hme Netwrk Devices Management The Cntrl Unit mdel described in the previus paragraph can als be used fr prviding remte mnitring and cntrl interface t the hme netwrk devices (e.g. ZigBee devices) cnnected t the device (when it acts as a residential gateway / hme cntrller). Prviding a cntrl unit cmpliant interface t such devices in the framewrk makes them accessible and manageable thrugh the Remte Manager Retrieving Device Lgs Remte Manager prvides remte interface fr retrieving f lg messages generated n the managed devices. The interface is cmpatible with standard Lg Service and supprts bth autmatic and n-demand retrieval f the device lgs. Autmatic lg transfer the Remte Manager Lg Agent can be cnfigured t autmatically send lg messages satisfying particular criteria based n severity level, surce and/r lg Bsch Sftware Innvatins GmbH 13

14 Remte Manager 6.1 message text template. Such messages are instantly delivered t the Remte Manager server, where they are stred and made available: t the peratr thrugh Remte Manager GUI r fr custm applicatins thrugh the Remte Manager APIs. Enabling/disabling f the autmatic lg transfer feature and the criteria fr autmatically transferred lg messages can be cnfigured at runtime thrugh the Remte Manager. Explicit lg retrieval the peratr can request explicit retrieval f the lg files generated n a particular device Fault Alerts Remte Manager prvides a mechanism thrugh which device applicatins can raise ntificatins abut sme tempral r permanent malfunctins, specific fr the cncrete applicatin. The alert ntificatins are transferred t the Remte Manager and made available t the system peratrs thugh the Remte Manager GUI cnsle. They can be als received by custm applicatin mdules (thrugh the Remte Manager API) which can generate apprpriate ntificatins, e.g. SMS, s, etc. Similarly t the lg messages, the alerts have severity level, surce, and text descriptin. The main difference between alerts and lg messages is that the alarms reflect the current status f the system malfunctins, i.e. the alert is autmatically clsed when the fault situatin is reslved Applicatin Mnitring Remte Manager supprts retrieving f mnitring data prvided thrugh the standard Mnitr Admin service. The Mnitr Admin service can be used by any applicatin running in the framewrk t exprt arbitrary runtime status infrmatin, which can change dynamically. 2.3 TR-069 Device Management Remte Manager supprts cnfiguratin and firmware update f custmer devices (CPEs) ver TR-069 prtcl standardized by the Bradband Frum. The basic features f the Remte Manager TR-069 based device management are: Supprt fr TR-69 Amendment 5 (including Annexes F and G) Supprt fr Sftware Mdule Management as specified in TR-069 Amendment 5 and TR-157 Amendment 3 Supprt fr TR-069 based management f devices cmpliant with the Residential Management Tree specificatin Remte mnitring and cntrl f hme netwrk appliances (e.g. ZigBee, Z-Wave devices) thrugh an based gateway (based n the Hme Device Management layer f the mbs Smart Hme) Supprt f custm data mdels and vendr specific methds - sphisticated device mdeling framewrk, allwing representatin f the manageable elements f the devices as dmain-riented bjects, e.g. bundles, sftware mdules, prcesses, etc. This allws cnvenient and intuitive mnitring and manipulatin f the devices by the peratrs. Remte Manager prvides built-in bject data mdels fr devices, as well as fr sme f the standard (Bradband Frum defined) Bsch Sftware Innvatins GmbH 14

15 Remte Manager 6.1 prfiles, and it supprts adding f additinal custm prvided bject mdels fr cncrete device classes/mdels Secure cmmunicatin - cnnectins ver HTTP/HTTPS with Digest and Basic Authenticatin Supprt dwnlading f firmware updates and sftware mdules frm the Remte Manager Sftware Repsitry Cnfigurable (data mdel-based) retrieval/synchrnizatin f device parameters - cntrllable (rule-based) way fr initial retrieving and subsequent refreshing f the device parameters, based n the knwledge prvided by system integratr/peratr abut data mdel (prfiles) supprted by cncrete classes f devices. This prvides significant imprvement in the perfrmance and scalability f the system and reduces the netwrk bandwidth utilizatin 2.4 TR-069 Device Management PrSyst als prvides a management slutin fr TR-069 enabled devices running r prxying platfrms. It is cmpliant with Residential Management Tree specificatin, which defines a TR-069 cmpliant management interface t the framewrk and its resurces. The Remte Manager executes TR-069 methds ver the parameter bjects defined in the mdel. These bjects prvide access t functinality related t the essence f an service platfrm, i.e. t dynamic deplyment and management f bundles, setting up bundles by means f cnfiguratin dictinaries, etc. The key feature f the TR-069 Device Management Package is the user-friendly cntrl ver TR-069 devices running an envirnment. T prvide cnvenient management f the features, Remte Manager uses the fllwing -related parameter ndes with Supprt: Device.Services. NumberOfEntries Represents the number f platfrms n the device.<instance_id> The server-side stack f the Remte Manager and the client-side stack f the mbs are nt strictly bund t each ther i.e. due t the standard and the general implementatin, it is pssible t use Remte Manager fr management f any TR-069 device (nt just based n mbs//java), and it is pssible t use ther TR-069 cmpliant DM systems fr remte management f the mbs. 2.5 Mbile (OMA DM-Based) Device Management Remte Manager supprts management f devices ver the OMA DM prtcl. OMA DM prtcl is defined by Open Mbile Alliance ( mbilealliance.rg) and is widely used in mbile devices. With the means f the flexible and pluggable architecture f the Remte Manager it is quite easy t implement any kind f management bject (available n the device) t be managed frm the backend. Yet the Remte Manager als prvides built in management f sme f the cmmn management bjects n an OMA DM enabled devices. Bsch Sftware Innvatins GmbH 15

16 Remte Manager 6.1 The device manager f Remte Manager's OMA device management system ffers means fr cntrl f OMA DM devices thrugh the Remte Manager generic mdel fr management f arbitrary device types. The mdel is based n the Cntrl Unit abstractin, and allws representing miscellaneus devices and their resurces as hierarchies f cntrl unit bjects sharing a cmmn interface fr cntrl. The Remte Manager btains a device's cnfiguratin by inspecting the cntrl unit structure and querying the values f the exprted state variables and is able t change the device cnfiguratin by invking the crrespnding actins. The Mbile Device Manager prvides a generic representatin f OMA DM enabled devices as cntrl units by implementing Cntrl Unit Prviders respnsible fr the fllwing features: Cmmunicatin with devices ver the OMA DM prtcl - The system uses Remte Manager's implementatin f the server-side part f the OMA DM Prtcl (including SyncML Representatin Prtcl) and several netwrk transprt bindings. Representing OMA DM enabled devices as hierarchical sets f cntrl unit bjects - This impses the need f creating a flexible way fr mapping between the data mdels supprted by OMA DM and by Remte Manager DMT and the cntrl unit mdels, respectively. Such a mapping mechanism is achieved by means f cntrl unit t DMT Mapping (CU-DMTM) files. Yu can define such a file by using a dedicated XML frmat fr describing the DMT structure f a particular class f devices r their specific management bjects as a set f cntrl units. 2.6 Mbile Device Types As ther device classes supprted by Remte Manager, the OMA DM devices are als identified by their type and unique ID. The unique ID usually crrespnds t the IMEI f the device and is prvided by the device during the initializatin f the OMA DM management sessin. The ID is retrieved frm the DevInf management bject (./DevInf/DevId). The Remte Manager assigns type Remte Manager.generic.ma-dm.device (Generic Mbile Device) t each device, which is nt recgnized as a mre cncrete custm r built-in Remte Manager mbile type (such as Mbile Device) Generic OMA DM Supprt OMA DM Specificatin defines several cmmn management bjects fr every OMA DM enabled device. These include:./devinf Management Object with infrmatin abut the device./devdetail Management Object with details n the device sftware./dmacc Management Object fr device precnfigured OMA DM accunt Remte Manager prvides a build-in supprt fr these cmmn managements bjects. There are sme differences in the structure f the OMA DM standard bjects between versins 1.1. and 1.2 f the OMA DM prtcl. The Remte Manager autmatically handles the differences and prvides adequate representatin f the standard management bjects. Bsch Sftware Innvatins GmbH 16

17 Remte Manager Mbile Management Objects Alliance has released Mbile Specificatin R4 that intends t unify the management bjects n enabled devices t be managed via OMA DM prtcl. This specificatin includes the fllwing management bjects fr devices that are supprted by the Remte Manager: Deplyment fr deplying and managing sftware cmpnents n enabled devices Plicy fr managing device security plicies Cnfiguratin fr cnfiguring devices Lg fr extracting device lgs Mnitr mnitring different mnitrable indicatrs n the device Applicatin fr lifecycle management f installed n the device applicatins Management Objects intrduced by the Remte Manager are: Bundle (./<path_t_sgi_rt>/remte Manager) Prvides supprt fr getting infrmatin abut -cmpliant bundles and fr executing basic lifecycle peratins n them as such a feature is nt accessible ver the -defined management bjects. Services (./<path_t_sgi_rt>/services) Prvides supprt fr viewing service applicatins and fr managing their lifecycle. Management Objects intrduced by the OMA Alliance are: SCOMO (./SCM) Stands fr Sftware COmpnent Management Object. Prvides supprt fr installing different types f sftware cmpnents in accrdance with the target device features. Presently, the mbs Mbile Runtimes by PrSyst implement the SCOMO. FUMO (./FUMO) Stands fr Firmware Update Management Object. Prvides supprt fr the DwnladAndUpdate actin n existing FUMO nde. Lck and Wipe (./LAWMO) Prvides a sub-tree fr lcking a device frm unauthrized use and fr wiping data. Scripting and Rule-Based Management The scripting language, adpted in Remte Manager, fr runtime prgramming and appinting management tasks ver the system is Grvy a multi-faceted language fr the Java platfrm. Grvy scripts may access dedicated APIs that are part f the Remte Manager functinality, therefre rganizing arbitrary management scenaris. Scripting can be used t appint varius management actins upn devices managed by Remte Manager (install sftware, cnfigure devices), as well as t perate the backend Remte Manager system itself (perate system cnfiguratin, generate alert ntificatins and reprts). A Grvy script may be used fr a: Task, when launched as a single executin. Script executins are called Scripting Tasks. Once a script is launched it will be turned int a Task. Bsch Sftware Innvatins GmbH 17

18 Remte Manager 6.1 Rule, when used fr defining management autmatin. A Rule as a general cncept has tw basic parts: Cnditin Actin When the Cnditin is satisfied, its Actin (a Task r a set f Tasks) will be executed. The system that rganizes scripting in Remte Manager, launching f Tasks and Rules ut f Grvy scripts, prvides executin statistics and detailed executin mnitring is called Remte Manager Rule Engine. Cntrl Unit Filters are used generically fr searching and filtering f devices and cmpnents in the Remte Manager system. They can be used: t appint extensive searches in the system in the scpes f Tasks and Rules t identify the set f devices t be invlved in mass executins and autmatins in the GDM Script Service as methd arguments fr cntrlling the filtered set f tweaked devices cmpnents via Remte Manager Scripting in the GDM Java API as methd arguments fr prgramming f java applicatins and Remte Manager plugins There are scripts that are already generated and available in the system: DM Script Service Alert Script Service Lg Script Service Device Grups Script Service Sftware Repsitry Script Service The Remte Manager maintains a persistent queue fr management/cntrl cmmands sent t each device. If the device is nt currently cnnected t the Remte Manager these cmmands are sent when the device is cnnected again. Bsch Sftware Innvatins GmbH 18

19 Remte Manager Sftware Repsitry Remte Manager Sftware Repsitry is a backend sftware and cntent database cmpliant with J2EE Client Prvisining specificatin (JSR-124), which maintains the meta-infrmatin and cntent files f the sftware cmpnents (applicatins, system mdules/drivers, firmware update files, etc.). It can be remtely prvisined n the target devices thrugh the Remte Manager. The main features f the Sftware Repsitry are: Supprt fr varius sftware cmpnents The Sftware Repsitry maintains the functinal characteristics f Bundles, Bundle Grups, Deplyment Packages, Prvisining Archives and MIDlet Suites. A pwerful characteristic f the extensible Sftware Repsitry mdel is the ability t widen the range f supprted sftware cmpnent types. Cmmn persistent strage The sftware resurces and all additinal prperties ensuring the successful delivery and deplyment n the client devices are stred persistently in the database. Dependency management The Sftware Repsitry intrduces mechanisms fr manual and autmatic definitin f the dependencies and the cmpatibility relatins between the sftware cmpnents and their versins. Sftware requirement management Required device capabilities can be defined autmatically r by the system administratr. Dependency slving and capability matching The Sftware Repsitry determines the sftware cmpnents and versins which are suitable fr the different devices. Device Platfrm Capabilities Maintenance f platfrm prperties including cmpatibility relatins between them. Bsch Sftware Innvatins GmbH 19

20 Remte Manager Remte Manager GUI Management Cnsle Remte Manager prvides system peratrs with rich and interactive GUI tls fr perfrming f system administratin and remte device management and mnitring tasks. The Management Cnsle is available in tw frms: Stand-alne (Windws-like) GUI applicatins cnnecting remtely t the Remte Manager server. Web-based interface prvides GUI t the Remte Manager accessible thrugh a web brwser. Bth versins f the Remte Manager Management Cnsle prvide access t the full functinality f the Remte Manager. The Management Cnsle is based n the Eclipse RPC and RAP technlgies and is pen fr custmizatin and extensin with custm mdules and functinality. Bsch Sftware Innvatins GmbH 20

21 Remte Manager API and Integratin Interfaces Remte Manager prvides an extensive and pen API t its full functinality allwing extending, custmizatin and integratin f the system with custm applicatins and backend systems. The Remte Manager API is available in the fllwing frms: Remte Manager API Remte Manager servers are based n technlgy, which allws deplyment f custm applicatins inside the Remte Manager framewrk. These custm bundles may use the Remte Manager API in the frm f services. Remte Manager Remte Java API API in the frm f Java library prviding any external Java based applicatin/system with remte interface t the Remte Manager. Remte Manager JEE Resurce Adapter Java Cnnectr Architecture cmpliant API prviding JEE applicatins with standard interface t the Remte Manager. Web Service API prvides SOAP 1.2 and REST-based API t either nn-java (.NET, C++, thers) r Java-based applicatins. Bsch Sftware Innvatins GmbH 21

22 Remte Manager Security 6.1 User Authenticatin and Authrizatin Remte Manager User Management package prvides rich functinality fr creating user accunts and user grups and fr assigning the access rights n a user and/r user grup level. The user accunts are used fr getting access t the Remte Manager thrugh the Remte Manager GUI cnsle applicatins and als fr accessing (by external systems and applicatins) the remte backend APIs f the Remte Manager described in the previus paragraph User Authenticatin Remte Manager supprts basic (username/passwrd based) and secure (based n persnal user certificates) authenticatin methds. The Remte Manager prvides pluggable hk mechanism fr authenticating cnnectins cming frm an device. This mechanism is an additinal guarantee that nly authenticated devices will be cnnected t the Remte Manager, because the device ID can be btained cmparatively easy and it is nt enugh t cnnect the device t the backend securely. The authenticatin can be bidirectinal - the device can als verify sme credentials sent frm the Remte Manager t prevent cntrl frm unauthrized management system. The Remte Manager prvides tw ready-t-use verifiers: Basic Authenticatin Verifier the Remte Manager can be cnfigured t require username/passwrd-based authenticatin and check the prvided client credentials. Client Certificate Verifier the Remte Manager can be cnfigured t verify that the client certificate Cmmn Name is equal t the device identifier. If the users need their wn device Remte Manager authenticatin, a custm Authenticatin Verifier can be added User Authrizatin Remte Manager utilizes flexible and fine-grained access cntrl mdel based n rles. The cntrl can be dne either n specific user level, as well as n a defined grup f users, such as system administratrs, service prviders, end users. The access cntrl restrictins t the prtected resurces and functinality maintained by the Remte Manager is enfrced n all backend interfaces prvided by the Remte Manager GUI tls and remte APIs prvided fr integratin with external systems and applicatins. Belw are sme f the build-in Remte Manager rles, which can be assigned r nt t the users/user grups (thus allwing r denying user access t particular resurces): Bundle-Imprt grants rights t imprt new bundles int the Remte Manager repsitry Bundle-View(<bundle_id>) parameterized rle granting rights t view/use the client bundle available in the Remte Manager Sftware Repsitry, with the specified Bsch Sftware Innvatins GmbH 22

23 Remte Manager 6.1 <bundle_id>. This ID may crrespnd either t single bundle r cmpsitin (applicatin/service). Bundle-Manager(<bundle_id>) parameterized rle granting rights t edit (e.g. rules, prperties, etc) the client bundle available in the Remte Manager Sftware Repsitry, with the specified <bundle_id>. This ID may crrespnd either t single bundle r cmpsitin (applicatin/service). Device-View(<device_nde_path>) parameterized rle granting rights t view/mnitr a specified device registered in the Remte Manager. The <device_nde_path> may refer either t cncrete device r t a grup f devices (in the Remte Manager device tree). Device-Manager(<nde_path>) parameterized rle granting rights t manipulate (e.g. install/upgrade sftware, change settings, etc.) a specified device registered in the Remte Manager. The <device_nde_path> may refer either t cncrete device r t a grup f devices (in the Remte Manager device tree). There are als ther rles supprted by the Remte Manager e.g. related t scripting and rule-based management, tasks, certificates, user management, etc. Additinal custm rles can als be defined in the Remte Manager and used by applicatins t guard access t their prtected resurces. The rles can be defined and assigned t the users and user grups thrugh the mcnsle GUI r thrugh the Remte Manager API. 6.2 Secure Netwrk Cmmunicatin Remte Manager supprts secure (SSL r HTTPS based) cmmunicatin ver its remte interfaces with the devices and the backend interface with the Remte Manager GUI cnsle applicatins and external systems. 6.3 Certificate Management Remte Manager prvides cmmn certificate management mdule, which maintain Remte Manager wn private key and certificates, as well as trusted certificates. There can be different certificates (wn and trusted) specified fr the different interfaces f the Remte Manager e.g. fr Remte Manager Message service, fr HTTP server, fr backend API access, fr user authenticatin. Remte Manager Certificate Manager supprts all f the mst widely used frmats fr imprting and exprting f the certificate and private key data. It als supprt certificate revcatin lists (CRL). Bsch Sftware Innvatins GmbH 23

24 Remte Manager Remte Manager Scalability and High Availability Remte Manager supprts bth vertical (achieved by using mre pwerful server hardware - number f CPUs/CPU cres and amunt f RAM) and hrizntal (using a cluster f multiple Remte Manager servers, which number can be increased with increasing lad) scalability appraches. Remte Manager Cluster ensures high scalability and availability f the Remte Manager system, by allwing a number f backend servers t act as a single management server. Remte Manager supprts different clustering mdels: Static lad distributin every management server manages a different sub-set f explicitly specified devices Dynamic mre than ne backend server instance is managing the same subset f devices, distributing the lad autmatically and dynamically Mixed the system may cntain multiple clustered servers, each f them respnsible fr a different sub-set f devices, and every cluster cntains multiple backend servers, which distribute the crrespnding device sub-set dynamically The diagrams belw shw three Remte Manager example deplyment cnfiguratins: 7.1 Single-server cnfiguratin The figure depicts the simplest Remte Manager cnfiguratin, suitable fr develpment and evaluatin purpses. It cnsists f nly ne backend server, which hsts Remte Manager Cntrl Center (CC), Management Server (MS) and Remte Access Server (RAS). Bsch Sftware Innvatins GmbH 24

25 Remte Manager Dynamic-clustered cnfiguratin mcnsle mcnsle Backend Service Supprt System LAN / Internet LAN / Internet DB LAN CC RAS RAS RAS RAS Clustered RAS framewrk LAN framewrk DB MS MS framewrk framewrk Clustered MS LAN / Internet/Wireless framewrk... framewrk The figure shws a Remte Manager multi-server cnfiguratin with a single clustered Management Server and a single RDBMS (which in turn can be clustered). The Clustered Management Server manages all registered devices and distributes the lad between the server ndes. RAS servers are deplyed n every Remte Manager hst and distribute requests frm the ther external backend systems. Bsch Sftware Innvatins GmbH 25

26 Remte Manager Mixed-clustered cnfiguratin mcnsle mcnsle Backend Service Supprt System LAN / Internet LAN / Internet CC framewrk LAN DB LAN RAS framewrk.. LAN RAS framewrk Clustered RAS LAN / Internet DB LAN MS framewrk MS MS MS LAN framewrk framewrk LAN framewrk LAN DB Clustered MS1 Clustered MSn LAN / Internet/Wireless LAN / Internet/Wireless framewrk... framewrk framewrk... framewrk This figure shws a multi-hst cnfiguratin, with several clustered Management Servers, each f them wrking with a separate database server fr string f the device cnfiguratin data. This multi-hst cnfiguratin is suitable fr distributed system deplyments. Hsts f ne MS cluster and the crrespnding DB server are cnnected in a lcal area netwrk (fast speed). Different MS clusters, CC and RAS cluster cmmunicate via Internet. Bsch Sftware Innvatins GmbH 26

27 Remte Manager Platfrm Requirements 8.1 Hardware Requirements Remte Manager Backend Server RAM 1024 MB minimum 2048 MB r mre recmmended Disk space, required fr Installatin 400 MB fr the Develpment Editin. The space fr the Prductin Editin depends n selected cmpnents Recmmended free space - at least 500 MB Remte Manager Management Cnsle RAM Disk space, required fr Installatin 1024 MB 50 MB 8.2 OS & JVM Requirements Fr Remte Manager Server(s) a Java SE VM equivalent t Oracle/Sun JDK 1.7 r higher is required. Any OS equipped with such JVM can be used (Linux, Windws, Slaris, etc.). Fr Remte Manager Management Agents the system requirements are J2ME CDC 1.0/Fundatin 1.0 cmpatible JVM. Fr the Remte Manager Management Cnsle it is required t have Java SE VM equivalent t Oracle/Sun JDK 1.7 r higher. 8.3 Supprted Framewrks fr Remte Manager Management Agents The supprted framewrks are: PrSyst mbs SDK 6.1 r higher Apache Felix 2.0, and Equinx 3.5.1, and The Remte Manager shuld be cmpatible with any ther framewrk cmpatible with the Specificatins Release 5 r higher. 8.4 Database Requirements The Remte Manager requires an external (3rd party) SQL RDBMS. The supprted DB servers are: Oracle Database 9i, 10g, 11g, 12c (recmmended fr large scale deplyments) Bsch Sftware Innvatins GmbH 27

28 Remte Manager 6.1 MySQL 5.1 r higher H an embedded Java RDBMS, which is included in the Remte Manager distributin fr develpment purpses nly and nt recmmended fr prductin deplyments. DB Strage Space The fllwing general guideline can be used fr determine needed DB strage space fr Oracle DB: 500 MB data space MB transactinal space MB f additinal data space fr every 1000 devices registered in the system. 8.5 Supprted Nn- Devices OMA DM cmpatible devices Remte Manager supprts OMA DM devices cmpatible with OMA DM prtcl versin 1.1 & 1.2 TR-069 devices Remte Manager supprts management f TR-069 prtcl (TR-069, TR- 069 Amendment 1, TR-069 Amendment 2 and TR-069 Amendment 3) cmpliant devices. Bsch Sftware Innvatins GmbH 28

29 Remte Manager Appendix A: Resurces Yu can find mre resurces abut the Remte Manager at: - PrSyst Develper s Zne Bsch Sftware Innvatins GmbH 29