Service Node Packet Encapsulation for External Layer-4 to Layer-7 Service Application
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Communications networks face challenges in efficiently applying Layer-4 to Layer-7 services to packets without requiring extensive integration and development within packet switching devices, which is costly and complex.
Innovation Solution
A method and apparatus where a packet switching device sends request packets to application nodes for service application, receiving response packets with applied services, allowing services to be applied externally without integrating service capabilities into the packet switching device, using Multiprotocol Label Switching (MPLS) label stacks and Type-Length-Value (TLV) elements for service identification and VPN association.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If services are applied within the packet switching device, then service delivery is integrated and reliable, but development and testing costs increase and device complexity increases
Solution Approach 1:
The patent extracts service application functionality from the packet switching device and relocates it to external application nodes. The service node forwards packets to application nodes for service processing, then receives the serviced packets back. This separation reduces device complexity while maintaining service delivery reliability through the structured request-response protocol between service nodes and application nodes.
Solution Approach 2:
The patent introduces a service node as an intermediary between the packet switching device and application nodes. The service node manages the forwarding of packets to application nodes and receives serviced packets back, acting as a mediator that coordinates service delivery without requiring the packet switching device to have built-in service capabilities.
2Ease of manufacture
If services are applied externally to packet switching devices, then development and testing costs are reduced, but service application efficiency may be affected
Solution Approach 1:
The patent segments the network service architecture into distinct functional components: packet switching devices for high-speed packet forwarding, service nodes for service orchestration, and application nodes for service processing. This segmentation allows each component to be developed and optimized independently, reducing overall development costs while maintaining service application efficiency through specialized functionality.
Solution Approach 2:
The patent creates a universal service application framework that can be applied to multiple different services across multiple application nodes. The standardized request packet format with service identification fields and VPN identification fields enables a single service node architecture to support diverse services, reducing development costs through reuse while maintaining efficiency through standardized protocols.
3Ease of operation
If packet switching devices integrate service capabilities, then service application is straightforward, but adaptability to new services decreases
Solution Approach 1:
The patent implements a dynamic service application architecture where service capabilities are not fixed within the packet switching device but can be dynamically added or modified by deploying new application nodes. The service node receives service identification in request packets and forwards to appropriate application nodes, enabling dynamic adaptation to new services without changing the core packet switching device infrastructure.
Solution Approach 2:
The patent uses a standardized request packet template that is copied and sent to application nodes for service processing. The request packet format with service identification fields and VPN identification fields serves as a universal template that can be replicated for different services, simplifying service application while maintaining adaptability through the flexibility of the identification fields.
Data Source
AI summary
Packets are encapsulated and sent from a service node to an application node for applying one or more Layer-4 to Layer-7 services to the packets, with service-applied packets being returned to the service node. An identification of a virtual private network (VPN) may be carried within a request packet, encapsulating a particular packet, sent by a service node to an application node for applying a service to the particular packet; with the corresponding response packet sent to the service node including an identification of the VPN for use by the service node in forwarding the services-applied packet. Additionally, parameters may be included in a request packet to identify a particular service of a general service to be applied to a particular packet encapsulated in the request packet.