Service Insertion Architecture OAM with Service Headers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current operation, administration, and maintenance (OAM) approaches for service insertion architecture (SIA) lack service awareness, making it difficult to verify and manage service paths, especially when services are not in the normal IP forwarding path, and do not support new service-specific topologies effectively.
Innovation Solution
The implementation of SIA-specific OAM mechanisms, including OAM packets with service headers that allow for echo messaging, trace services, and continuity checks, enabling proactive connectivity monitoring, fault detection, and corrective actions within the SIA framework, which verifies service paths and configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional IP-based OAM approaches are used, then basic network path verification is possible, but service-aware monitoring and management of service paths is not achieved
Solution Approach 1:
The patent segments the OAM functionality by introducing service-specific OAM packets that are distinct from conventional IP-based OAM. Each service in the chain can be monitored independently through service-specific OAM packets, enabling service-aware verification while maintaining the ability to handle diverse service topologies through service-specific handling mechanisms.
Solution Approach 2:
The patent introduces service headers as intermediaries between the OAM packets and the service chain. These service headers carry service identification information and routing instructions, enabling OAM packets to be properly routed through complex service topologies while maintaining service-aware monitoring capabilities.
2Ease of operation
If services are inserted into data networks using SIA, then brokered service framework is established, but OAM becomes difficult to implement without service awareness
Solution Approach 1:
The patent makes OAM packets multi-functional by enabling them to serve both conventional IP-based OAM purposes and service-specific OAM purposes. The service headers within OAM packets can be processed by multiple service nodes in the chain, allowing a single OAM packet to perform verification across the entire service path without requiring separate OAM mechanisms for each service.
Solution Approach 2:
The patent implements feedback mechanisms through service-specific OAM packets that traverse the service chain and return verification results to the OAM entity. This feedback loop enables automatic detection of service path failures and provides information for operational management, simplifying service path management while maintaining implementability through standardized packet processing.
3Adaptability or versatility
If service-specific topologies are deployed, then new service capabilities are enabled, but conventional OAM cannot verify service paths effectively
Solution Approach 1:
The patent applies local quality by making OAM packets service-specific, where each service in the chain has its own OAM packet with service identification information. This allows precise verification of each service's operational status and path configuration, providing measurement precision tailored to each service's specific requirements while supporting diverse service topologies.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In one embodiment, a method can include: selecting an operation, administration, and maintenance (OAM) type for a destination, where the destination is enabled for a service insertion architecture (SIA); encapsulating an OAM packet with the OAM type indicated in a service header therein; and sending the OAM packet to the destination.