• Management of single and multiple CPE’s per user.
  • CPE and customer profile management.
  • Users managment.
  • Mass Update / CPE Group Update.
  • Software/Firmware Image Management.
  • CPE Policy Management.
  • CPE based events triggering.
  • Supported of devices connected to the router (TR-111).
  • Full support of the TR-69 specs.
  • Complete API/NBI to external applications.
  • Enables provisioning and delivery of value-added services.
  • Supports all routers, set-top boxes (STBs), ATAs, cameras, IP phones with no .additional development.
  • Improve subscriber’s QoS.
  • Reduces the cost of provisioning new subscribers and new services.
  • Reduces on-going support costs.

Monitor CPEs and user's experience while taking proactive actions

  • The CPE devices installed at the customer end constantly generates events that provide clues regarding potential problems.
  • TR-069 Events Management System (FEMS) allows service providers to gather and analyze these events, generate alarms on potential problems and low QoS levels, and take proactive measures that address these alerts.
  • The system automates problem resolution with predefined scripts, reducing support costs, increasing customer satisfaction, and thereby avoiding churn. 
  • The scripts are automatically triggered by events, which are generated by the device, and include automated problem resolution as well notification to external systems and applications.

Gathering and Analysis of Events from the Device End

FEMS gathers events from the device concerning QoS levels, changes to the settings, and other potential problems and produces alerts which may be brought to the attention of the service provider and/or trigger various problem resolution scenarios.Alerts may include the following types:

  • QoS is reduces under a certain level
  • User is connected the first time
  • User changed important setting on the device
  • CPE was rebooted more than once in a short time frame

Seamles Creation of

FEMS' Workflow Editor allows business users to easily create what-if scenarios while visualizing the workflows on screen. The scenarios may include automated proactive actions. Common scenarios include:

  • Implementation of complex provisioning scenario/workflow, involving external systems
  • Diagnostics and resolution of potential problems before they occur
  • Diagnostics and resolution of potential problems upon user request
  • Monitoring QoS and executing corrective actions if needed
  • Notify external system (XML message / SNMP/ Email
  • Run an Executable / Application
  • On screen message
  • Write to a Log file

Open Interface to External Systems

  • Based on web services and SOAP, FEMS offers an open interface to external systems, including TR-69 ACS, Self-support Portal, Support Center Application, PC Client applications and back office systems, such as Billing, CRM, OSS, and more.
  • These interfaces can be incorporated into the system's workflows.

A Myriad of Interactions During the Workflow Process

  • The workflow process can involve interaction with the user's CPEs, user's PC, the carrier's back-office system, and more.
  • FEMS can invoke any executable file with any combination of parameters that are received from the trigger.
  • FEMS can also use SNMP Traps to monitor relevant network-attached devices and incorporate the results in the executed workflow.
  • Combining the Web Service Call, the Executable Call and the SNMP Trap call enables the user to develop powerful and complex workflows, leveraging the full potential of available back-office systems.

Leave a Reply

Your email address will not be published. Required fields are marked *