Challenges in Reliability & Availability for Seamless Mobility

1. Challenges in Reliability & Availability for Seamless Mobility Michael Ketcham Motorola Networks Advanced Technology m.ketcham@motorola.com May, 2007

2. Starting Point • Motorola is delivering seamless mobility • All-IP Networks (AIPN) • Control via IP Multi-media Services (IMS) • Success of seamless services depends on subscribers’ total quality of experience • Seamless services over AIPN with new control elements will have challenging new behaviors • We have the responsibility of understanding the end-to-end problem and solution space so Seamless Mobility will succeed

3. Seamless Mobility, AIPN and IMS

4. What is a “Service”? • Services as perceived by the end-user • Services are inherently recursive – • Services embed services • Services connect to services • Services will change state in the middle of service delivery • New features will be triggered, spawning services • Services will be mobile and move between networks • Services will be data-driven • Machine-readable definition of a service is held in a database – Operators can create new services by adding a few data entries • Service behavior will change based on subscriber data and subscriber-specific preferences, all held in databases

5. Seamless Services will have New Behaviors • Operators will need to coordinate services carried across networks with different design targets, operations paradigms and user expectations. • Providers will have vastly more complex design and verification issues with converged networks than with traditional cellular networks • New difficulties in designing for specified availability targets, coordinating diagnostics, or verifying availability • Converged services are expected to be carried across all-IP architectures, which will have significantly different behaviors that today’s wireless infrastructures. • All-IP networks require understanding IP best practices for system design and selection of protocols for service survivability • New data-driven and policy-driven services will have new behaviors • New services can be created dynamically and invoke varying sets of applications • Service reliability will depend as much on the data architecture as on the physical architecture • Operations systems will need new techniques to identify services and monitor successful delivery of services for accurate statistics and fault management • Services will have new behaviors at both the edge and the core • Intelligent end devices will make complex service-impacting decisions • Service delivery will depend on residential and enterprise CPE networks not managed by the service provider • Users will configure service behavior with individualized device settings and preferences

6. Problem Space – User Devices • Complex logic at the edge • Device interoperability • Subscriber customization

7. Problem Space – Access Networks • Single Points of Failure in access networks • Optimal redundancy / cost trade off for edge devices • Status messaging, alarming and fault management in broadly distributed non-hierarchical networks • Complex logic at the edge • Device interoperability • Subscriber customization

8. Problem Space – Leverage IP Core • Single Points of Failure in access networks • Optimal redundancy / cost trade off for edge devices • Status messaging, alarming and fault management in broadly distributed non-hierarchical networks • Maximize capabilities for service resilience and differentiated svc resilience provided by the IP/MPLS core • Complex logic at the edge • Device interoperability • Subscriber customization

9. Problem Space – Control Core • Single Points of Failure in access networks • Optimal redundancy / cost trade off for edge devices • Status messaging, alarming and fault management in broadly distributed non-hierarchical networks • Maximize capabilities for service resilience and differentiated svc resilience provided by the IP/MPLS core • Managing IMS / Signaling / data query complexity • Complex interworking with CSF, Policy and Application Services • Network element and Functional Element R&A • Complex logic at the edge • Device interoperability • Subscriber customization

10. Problem Space – Server Core • Single Points of Failure in access networks • Optimal redundancy / cost trade off for edge devices • Status messaging, alarming and fault management in broadly distributed non-hierarchical networks • Dynamic, distributed databases • Potential inconsistency & delay in view of network state and databases holding dynamic sub and session state • Maximize capabilities for service resilience and differentiated svc resilience provided by the IP/MPLS core • Complex logic at the edge • Device interoperability • Subscriber customization • Managing IMS / Signaling / data query complexity • Complex interworking with CSF, Policy and Application Services • Network element and Functional Element R&A

11. Problem Space – Operations • Single Points of Failure in access networks • Optimal redundancy / cost trade off for edge devices • Status messaging, alarming and fault management in broadly distributed non-hierarchical networks • Dynamic, distributed databases • Potential inconsistency & delay in view of network state and databases holding dynamic sub and session state • Maximize capabilities for service resilience and differentiated svc resilience provided by the IP/MPLS core • Service verification and monitoring for dynamically defined services • Verification of service svc functionality • Automatic problem detection and handling • Manual fault mgt • Complex logic at the edge • Device interoperability • Subscriber customization • Managing IMS / Signaling / data query complexity • Complex interworking with CSF, Policy and Application Services • Network element and Functional Element R&A

12. Conclusion • Seamless Services across All-IP Networks introduce new quality, reliability & availability challenges • Leverage what we know from successes and solutions in Motorola’s existing capabilities