1. Pirelli Management Platform Functional overview

2. Pirelli Proprietary 2005 - Strictly Confidential2 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Agenda  Device Monitoring  Service Activation – Self Configuration  Device Audit  Remote Actions  Firmware Download  Diagnostic  Remote Control  Backup & Restore  Groups Management

3. Pirelli Proprietary 2005 - Strictly Confidential3 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Device Monitoring PMP supports following device monitoring features: Presence The CPE availability is maintained in the DB. The operator can contact the CPE when needed. Assurance Configuration/monitoring parameters can be accessed by the operator via Web GUI Device Log CPE logs can be retrieved on operator request Events Log CPE spontaneous events are logged into DB and can be displayed on the Web GUI Activity Log Activities performed by the ACS on the CPE are logged into DB and can be displayed on the Web GUI

4. Pirelli Proprietary 2005 - Strictly Confidential4 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Device Monitoring – Assurance Configuration: PMP allows operator to access all configuration parameters for both monitoring and setting Diagnosis: PMP allows operator to activate diagnostic functionalities on the CPE

5. Pirelli Proprietary 2005 - Strictly Confidential5 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Device Monitoring – Device Log The log level can be configured by the operator (Assurance) if supported by the device PMP is able to retrieve the device log from the CPE on operator request (Assurance  Diagnosis) InternetGatewayDevice.DeviceInfo.DeviceLog parameter is retrieved for CWMP equipments Proprietary parameters (i.e. systemLogs for Pirelli AGv2) are retrieved for SNMP equipments

6. Pirelli Proprietary 2005 - Strictly Confidential6 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Device Monitoring – Events & Activities logs Events Log: PMP allows operator to monitor the CWMP informs, SNMP traps, HTTP post events Activities Log: PMP allows operator to monitor the activities performed on the CPE (provisioning, configuration,FW upgrade)

7. Pirelli Proprietary 2005 - Strictly Confidential7 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Device Monitoring Events Management Scalability Events filtering at protocol adapter modules level Protocol connections are accepted by configurable thread pools, thus avoiding system overload Adapter modules can have multiple instances on different ports or different servers A load balancer can be optionally deployed

8. Pirelli Proprietary 2005 - Strictly Confidential8 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Device Monitoring Enhancement – Log Pull 1.PMP is currently able to manage a catalogue of file servers on DB 2.CPEs can be addressed to upload log files via HTTP or FTP 3.The file servers accept file uploads. Load balancing is managed via file servers distribution 4.The operator can browse device log files and retrieve them via HTTP PMP 1 2 4 3 HTTP FTP PMP 3.0

9. Pirelli Proprietary 2005 - Strictly Confidential9 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Agenda  Device Monitoring  Service Activation – Self Configuration  Device Audit  Remote Actions  Firmware Download  Diagnostic  Remote Control  Backup & Restore  Groups Management  PMP Roadmap

10. Pirelli Proprietary 2005 - Strictly Confidential10 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Service Activation – Self Configuration Automatic Provisioning 1/3 The main goal of PMP is to simplify the process of device configuration and service activation for the final end customer (zero- touch model) Help Desk Pirelli PMP Plugin/ Protocol Adapter 1. CPE presence event 3. Store CPE service profile 4. Set CPE configuration OSS 2. Get CPE service profile 1. OSS presence event (e.g. Radius) Web GUI HD. Check provisioning status c. Return provisioning/ configuration status a.Retrieve stored config. b. Get CPE configuration DB OSS Interface The CPE presence event can be captured either by external sources or by OSS modules CPE

11. Pirelli Proprietary 2005 - Strictly Confidential11 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Scalability-Modularity-Flexibility 2. Get CPE service profile – an external OSS/AAA is queried for the service profile information for the customer/CPE. OSS interface manage these communication channel  Presence Event – CPE presence unsolicited events are captured from external sources by multi-instantiable protocol listener or device/OSS adapter modules. The Product’s modules framework allow implementation and deploy of the needed adapters, based on the IT infrastructure context. Service Activation – Self Configuration Automatic Provisioning 2/3 CPE

12. Pirelli Proprietary 2005 - Strictly Confidential12 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV  Store CPE service profile – customer/CPE service profile information is stored in the Product’s DB and can be easily managed (created/changed by Configurator). 4. Set CPE configuration – The multi-instantiable device/protocol adapter modules are instructed to perform service provisioning via the Product’s bus Service Activation – Self Configuration Automatic Provisioning 3/3 Scalability-Modularity-Flexibility CPE

13. Pirelli Proprietary 2005 - Strictly Confidential13 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV HD. Check provisioning status – Concurrently, an operator could check the status of current provisioning activities, or the result of past provisioning activities a.Retrieve stored configuration – The GUI module retrieve from the Product’s DB the expected CPE configuration b.Get CPE configuration – The multi-instantiable device/protocol adapter modules are activated on the Product’s bus and retrieve at runtime the current CPE configuration Service Activation – Self Configuration Check Provisioning Result Scalability-Modularity-Flexibility c.Return provisioning/ configuration status - CPE on-board configuration and DB stored configuration are presented to the operator on the GUI, allowing provisioning result check. CPE

14. Pirelli Proprietary 2005 - Strictly Confidential14 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV 1.Service update request from external OSS 2.Connection request to CPE 3.PMP retrieves from external OSS the data related to the new service profile subscripted by the end user 4.PMP stores the service profile in its DB 5.PMP transfers to the CPE the configuration parameters associated to device type and user service profile PMP is able to manage the service update requests generated from an external OSS: Service Activation – Self Configuration Service Update Pirelli PMP Plugin/ Protocol Adapter 2. Connection request 4. Store CPE service profile 5. Set CPE config. OSS 3. Get CPE service profile 1. OSS service update request Web GUI a.Retrieve stored config. DB OSS Interface CPE

15. Pirelli Proprietary 2005 - Strictly Confidential15 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Authentication: CPE –> ACS: PMP supports CPE authentication based on shared secret (SNMP, TR-069). Username and password must be configured on the CPE to allow authenticated access to PMP ACS -> CPE: for TR-069 devices PMP supports certificate based authentication. Identification: HG is identified via IP-CLI association Terminals are associated to the same CLI of the HG, thus defining a Home Network Registry table devoted to the home network identification CPE is identified by CLI, Device category, Progressive code CPE type is identified via data retrieved from spontaneous notification or requested to the device after presence message reception (OUI, HW version, SW version,...) Extended management of customer home network is foreseen for PMP 3.0 release (presentation of connected devices, list of MAC addresses,...) PMP 3.0 Service Activation – Self Configuration Authentication & Identification

16. Pirelli Proprietary 2005 - Strictly Confidential16 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Agenda  Device Monitoring  Service Activation – Self Configuration  Device Audit  Remote Actions  Firmware Download  Diagnostic  Remote Control  Backup & Restore  Groups Management

17. Pirelli Proprietary 2005 - Strictly Confidential17 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV PMP allows operator to access the CPE to verify the device configuration and the service related parameters Device Audit Customer Care Use Case 1/3 DB 1. help desk phone call Web GUI 5. Check CPE status Plugin / Protocol Adapter 4. Retrieve actual status from CPE 3. retrieve stored status for DB User Help Desk CPE 2. Target CPE selection Pirelli PMP

18. Pirelli Proprietary 2005 - Strictly Confidential18 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Client ID Target CPE selection by client id Target CPE is contacted Retrieval of CPE status information, both from device and from DB READING DEVICE INFORMATION Device Audit Customer Care Use Case 2/3

19. Pirelli Proprietary 2005 - Strictly Confidential19 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Client ID Check for Provisioning, FW Upgrade and Assurance tasks (running, enqueued or logged) Current FW version Current provisioned service profile CHECKING DEVICE STATUS Target CPE selection by client id Target CPE is contacted Device Audit Customer Care Use Case 2/3

20. Pirelli Proprietary 2005 - Strictly Confidential20 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Agenda  Device Monitoring  Service Activation – Self Configuration  Device Audit  Remote Actions  Firmware Download  Diagnostic  Remote Control  Backup & Restore  Groups Management

21. Pirelli Proprietary 2005 - Strictly Confidential21 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV CPE DB 1. help desk phone call Web GUI 5. Check CPE configuration Plugin / Protocol Adapter 4. CPE configuration retrieval 3. retrieve stored configuration 6. Reconfiguration request 7. CPE reconfiguration User Help Desk Pirelli PMP 2. CPE selection PMP allows operator to access the CPE to modify the device configuration as requested by the subscripted services Remote Actions Customer Care Use Case 1/3

22. Pirelli Proprietary 2005 - Strictly Confidential22 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV CLI Target CPE selection by client id Target CPE contacted Retrieval of CPE information, both from device and from DB READING DATA DEVICE Remote Actions Customer Care Use Case 2/3

23. Pirelli Proprietary 2005 - Strictly Confidential23 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Error detection Manual fault correction WRITING DATA ON DEVICE Check new device configuration Check result activity Remote Actions Customer Care Use Case 3/3

24. Pirelli Proprietary 2005 - Strictly Confidential24 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Maximum number of concurrent operations Time window Recovery policy ACTIVITY CONFIGURATION Display of the result of activities Manual recovery ACTIVITY RESULT Display of running activities MONITORING PMP supports reliability and scalability on assurance operations at different levels: Remote Actions Reliability And Scalability

25. Pirelli Proprietary 2005 - Strictly Confidential25 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Agenda  Device Monitoring  Service Activation – Self Configuration  Device Audit  Remote Actions  Firmware Download  Diagnostic  Remote Actions  Remote Control  Backup & Restore  Groups Management 

26. Pirelli Proprietary 2005 - Strictly Confidential26 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Firmware Download PMP supports the following firmware download configuration criteria: Single download A firmware download on a specific CPE can be configured from the PMP GUI via the Firmware -> Download menu Download campaign A firmware download campaign on a set of CPEs can be configured from the PMP GUI via the Firmware -> Campaign menu Automatic download at provisioning time A firmware download can be configured for the automatic execution during the Service Provisioning phase (e.g. when an updated firmware version is needed to support the requested service)

27. Pirelli Proprietary 2005 - Strictly Confidential27 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Firmware files are stored on a pool of servers Download parameters (e.g. FTP server URL, FTP server account) are configured by PMP on the CPEs via the management protocol Dowload is performed by the CPEs (e.g via HTTP protocol for TR-069 devices. via FTP protocol for SNMP devices) PMP HTTP FTP Pool of Download servers Firmware Download – Protocols PMP is able to manage different protocols to support Firmware Downloads feature:

28. Pirelli Proprietary 2005 - Strictly Confidential28 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV The Download procedure is performed accordingly to the TR-069 specifications: PMP calls the RPC Download method The CPE receives the download parameters and starts a new HTTP session with the server specfied in the RPC Download request If needed, the CPE performs a reboot after download The CPE sends a TransferComplete message to PMP PMP sends a TransferComplete response NOTE: the HTTP server can be different from PMP. Firmware Download - TR-069 Protocol

29. Pirelli Proprietary 2005 - Strictly Confidential29 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV This schema shows an SNMP download operation flow: PMP configures the download parameters on the CPE PMP commands the CPE to start the download The CPE downloads the new firmware from the configured server using the FTP protocol PMP checks the download status on the CPE. After download completion a CPE reboot can be configured After CPE restarts PMP checks the firmware consistency NOTE: the FTP server can be different from the ACS. Firmware Download - SNMP Protocol

30. Pirelli Proprietary 2005 - Strictly Confidential30 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Firmware Download allows the configuration of: Firmware Change to be performed (based on the CPE currently installed firmware) Firmware Campaing allows the configuration of: A set of CPEs to be downloaded Both allow the configuration of: Start Date End Date Time Window Firmware Download Configuration From GUI

31. Pirelli Proprietary 2005 - Strictly Confidential31 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Running download operations can be monitored in the Firmware -> Tasks -> Running Tasks menu Failed download operations are listed in the Firmware -> Tasks -> Recovery menu All terminated dowload activities (completed or failed) are listed in the Firmware -> Tasks -> History menu Firmware Download Results Tracking

32. Pirelli Proprietary 2005 - Strictly Confidential32 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV The Hardware/Firmware Catalog Menu allows the configuration of: Firmware versions Hardware versions Firmware Changes (associations between compatible Firmwares) Vendors HW/FW Association FW/Modules Association (association between a FW version and its components) FW/Profiles Association (association between Service Types, or Profiles, and compatible FW versions) Product Classes Firmware Download Hardware/Firmware Catalog

33. Pirelli Proprietary 2005 - Strictly Confidential33 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV A Pool of Download servers is configurable on PMP DB in order to: share the traffic when download campaigns are performed to improve performance move downloads on other servers when one of them is unavailable Each server is identified by an IP-Address, a Protocol type (http / ftp) and a Port Servers are collected in groups; each group is associated to a rule determined by: Device type, class or category Area Device Identifier (e.g. CLI) Distribution algorithms (e.g. Simple Round Robin, Weighted Round Robin) for the servers in each group are configurable Statistics on servers availability and operations are stored in a Statistics DB table Server Configuration Enhancements Show server statistics on GUI Configure servers from GUI PMP 3.2 Firmware Download Servers Configuration

34. Pirelli Proprietary 2005 - Strictly Confidential34 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Agenda  Device Monitoring  Service Activation – Self Configuration  Device Audit  Remote Actions  Firmware Download  Diagnostic  Remote Actions  Remote Control  Backup & Restore  Groups Management

35. Pirelli Proprietary 2005 - Strictly Confidential35 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Diagnostic PMP supports access to configuration parameters and is able to activate self-diagnostic tasks on the devices to allow customer care activities: Assurance -> Configuration Access to device inventory Access to device configuration data Assurance -> Diagnosis Access to self-test functionalities exported by the CPE Activation of remote PING on the CPE CPE reboot CPE factory reset

36. Pirelli Proprietary 2005 - Strictly Confidential36 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Diagnostic – CPE Configuration Inventory: PMP allows the operator to display all the CPE identification data Configuration: PMP allows the operator to display all the CPE configuration data. Differences between device and PMP’s DB values are red highligted

37. Pirelli Proprietary 2005 - Strictly Confidential37 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Diagnostic – CPE Diagnosis Self Test: PMP allows the operator to activate self-test tasks for the CPEs supporting this feature. Results are displayed immediately after test execution Diagnostic Commands: PMP allows the operator to execute Reboot, Reset To Factory Default and additional diagnostic commands (e.g remote ping) supported by the CPE for customer care purposes

38. Pirelli Proprietary 2005 - Strictly Confidential38 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Agenda  Device Monitoring  Service Activation – Self Configuration  Device Audit  Remote Actions  Firmware Download  Diagnostic  Remote Control  Backup & Restore  Groups Management

39. Pirelli Proprietary 2005 - Strictly Confidential39 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Remote Control 1/3 OSS External Systems DMZ Network External Network Operators LAN Access Operators Network Public Network Sonic Cluster SUN Cluster FW PMP PLATFORM First scenario: HTTP web page access Step 1: Enable HTTP proxy server Step 2: Configure web browser to use PMP server as HTTP proxy PMP 3.0

40. Pirelli Proprietary 2005 - Strictly Confidential40 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Remote Control 2/3 OSS External Systems DMZ Network External Network Operators LAN Access Operators Network Public Network Sonic Cluster SUN Cluster FW PMP PLATFORM Second scenario: telnet access Step 2: provide and configure a telnet client application Step 1: Install telnet proxy PMP 3.0

41. Pirelli Proprietary 2005 - Strictly Confidential41 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Remote Control 3/3 Implementation easiness Only additional network routing rules needed Additional firewall allowed ports depending on CPE management protocol (HTTP-based, telnet, ssh, SNMP,...) Reliability & scalability Each operator accesses sequentially targeted CPEs, so load is linear with the number of operators Resources needed by the remote control feature are of an order of magnitude lower than those required by other operations (e.g. provisioning. download), so they are neglectable and architectural changes are not required. Integration PMP server host can be used as proxy for most protocols PMP 3.0

42. Pirelli Proprietary 2005 - Strictly Confidential42 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Agenda  Device Monitoring  Service Activation – Self Configuration  Device Audit  Remote Actions  Firmware Download  Diagnostic  Remote Control  Backup & Restore  Groups Management

43. Pirelli Proprietary 2005 - Strictly Confidential43 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Backup & Restore – Configuration Backup PMP stores in its DB the complete configuration of each managed CPE The CPE configuration is saved on PMP’s DB automatically after first provisioning or on operator request Differences between saved configuration and CPE configuration are highlited in red color on Web GUI

44. Pirelli Proprietary 2005 - Strictly Confidential44 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Backup & Restore – Configuration Restore At present PMP is able to restore the device configuration: On parameters aggregation On service aggregation (manual provisioning) Device configuration can be restored via configuration file download process for devices supporting this feature (e.g. Livebox on PMP 2.1.3 release)

45. Pirelli Proprietary 2005 - Strictly Confidential45 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Backup & Restore - Multiple Backups Support to multiple backup/restore device configurations is planned for PMP 4.0 release Scalability of backups up to millions (<10) relies on the used RDBMS (Oracle). Improvements of scalability may be achieved through Oracle DB partitioning feature PMP 4.0 At present PMP is able to backup/restore a CPE configuration from its device inventory to a backup DB table (one backup for each CPE)

46. Pirelli Proprietary 2005 - Strictly Confidential46 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Agenda  Device Monitoring  Service Activation – Self Configuration  Device Audit  Remote Actions  Firmware Download  Diagnostic  Remote Control  Backup & Restore  Groups Management

47. Pirelli Proprietary 2005 - Strictly Confidential47 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Group Management - Firmware Campaign PMP is able to activate the firmware download process on a pool of CPEs. The group definition is valid till completion of the activity. Available group selection criteria are: Device Id (wild cards are allowed) Regional area Device Category, Class or Type Current firmware version Service Type

48. Pirelli Proprietary 2005 - Strictly Confidential48 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Group Management - Livebox Support PMP allows the configuration of group filters (stored in its DB) to support download management on devices not exporting an information model (e.g. Livebox) Available group selection criteria are: Serial Number Manufacturer Hardware Version Firmware Version

49. Pirelli Proprietary 2005 - Strictly Confidential49 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Group Management - Enhancements Extension of the devices groups support toward additional functional areas (provisioning, assurance) is planned Groups will be created by reading a list of CPEs from a file or by configuring selection criteria via GUI: Firmware version Hardware version Service Profile Device Id Geographical area And more... Group definition rules will be stored in PMP DB to allow later association to the required activity (firmware download, provisioning, assurance) PMP Roadmap

50. Pirelli Proprietary 2005 - Strictly Confidential50 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV 3. Check information report DB Web GUI 2. retrieve stored information Pirelli PMP 1. Group filter selection Marketing Serial numberIdServiceHDFW Group Management – Devices Audit Marketing Use Case 1/2 PMP Roadmap

51. Pirelli Proprietary 2005 - Strictly Confidential51 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV Group management feature supports massive audit: An already configured group is selected, or A new group is defined Device fleet statistical reports grouped by: FW versions HW versions Service profiles Geographical area And more... DEVICE GROUP INFORMATION IS RETRIEVED FROM INVENTORY PMP Roadmap Group Management – Devices Audit Marketing Use Case 2/2

52. Pirelli Proprietary 2005 - Strictly Confidential52 CORPORATE PRESENTATION NEW rel_0.2 date_20.06.2005 Conf_ADV DB Web GUI Plugin / Protocol Adapter 2. Service activation on a specific group 3. CPE configuration PMP operator 1. Group filter selection Pirelli PMP Serial numberIdServiceHDFW PMP Roadmap Group Management – Remote Action Service Activation Use Case

53. Thank You