Abstract: Disclosed are the methods and systems for enabling interworking between RCS and non RCS networks in a completely seamless and transparent manner in which there will be no need to update or develop a new RCS end device or a client software and still achieving the interworking with non RCS networks only by network specific deployments and configurations. Proposed systems and methods shall extend all the RCS services to the non RCS contacts of the RCS users (subject to subscription to particular non RCS network that offers RCS kind of services) retaining the end client devices or end client applications used both by the RCS user and non RCS user.

Abstract: Disclosed is a system and method for enabling a SNMP based Network Management System in cooperation with at least one SDN Controller to control sequence of recovery actions and dynamically change the recovery action sequence for a given fault based on the feedback received from an SNMP Agent/Open flow based devices across various systems/platforms for recovering a business service which is achieved by way of Open flow stack enhancements and OF-CONFIG enhancements at the controller end and device end. The present invention is essentially about extending the ability to initiate and perform dynamic recovery actions in a network supporting both the traditional SNMP based management systems & Open flow based SDN Control.

Abstract: The present disclosure relates to a system and method for enabling SNMP (Simple Network Management Protocol) based Network Management System to correlate and control sequence of recovery actions to be performed and dynamically change the recovery action sequence across various systems/platforms/devices. Disclosed is a system for taking sequence of dynamic recovery actions in network management system upon occurrence of a fault, in one aspect of the present invention. The system includes an action definition repository containing a sequence of recovery actions for the fault in a particular business scenario. The action definition repository is initialized and updated for every new scenario. The system further includes an action sequence engine being capable of reading the recovery sequence listed in the action definition repository for the fault in the particular business scenario.