Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A network element for a software-defined network, the network element comprising a data transfer interface for receiving and transmitting data and a processing system adapted to: construct, in accordance with configuration data received from a controller of the software-defined network, a software-defined data path for managing first data to be forwarded, the software-defined data path comprising look-up tables for selecting software-defined actions and one or more of the software-defined actions modifying first metadata associated with the first data; configure, in accordance with forwarding-parameter data received at the network element, a fixed-functionality data path for managing second data to be forwarded, the fixed-functionality data path defining fixed-functionality actions and one or more of the fixed-functionality actions modifying second metadata associated with the second data; convert the first metadata associated with the first data being managed by the software-defined data path to a data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions in conjunction with forwarding the first data; determine a first one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the first data; and control the determined first one of the fixed-functionality actions to be carried out so as to initiate the needed one or more fixed-functionality actions to be carried out at least partly in accordance with the converted first metadata.
In software-defined networking (SDN), network elements must efficiently handle data forwarding while supporting flexible, programmable control. Traditional fixed-functionality data paths lack the adaptability of software-defined data paths, which use configurable look-up tables and actions to manage metadata. This invention addresses the challenge of integrating these two approaches by providing a network element that combines both types of data paths. The network element includes a data transfer interface for receiving and transmitting data and a processing system. The processing system constructs a software-defined data path based on configuration data from an SDN controller. This path uses look-up tables to select software-defined actions that modify metadata associated with incoming data. Additionally, the processing system configures a fixed-functionality data path, which performs predefined actions on data metadata. When data managed by the software-defined path requires fixed-functionality actions, the network element converts the metadata to a format compatible with the fixed-functionality path. It then determines the appropriate fixed-functionality action based on the most recently accessed look-up table in the software-defined path. The selected action is executed, allowing seamless integration of software-defined and fixed-functionality processing. This hybrid approach enhances flexibility while maintaining efficient data forwarding.
2. The network element according to claim 1 , wherein the processing system is further adapted to: convert the second metadata associated with the second data being managed by the fixed-functionality data path to a data format suitable for the software-defined data path in response to a need to carry out one or more of the software-defined actions in conjunction with forwarding the second data, determine a first one of the look-up tables of the software-defined data path at least partly on the basis of which one of the fixed-functionality actions was most recently carried out when managing the second data, and carry out a look-up from the determined first one of the look-up tables so as to initiate the one or more needed software-defined actions to be carried out at least partly in accordance with the converted second metadata.
A network element integrates fixed-functionality and software-defined data paths to manage data traffic. The fixed-functionality data path performs predefined actions on data, while the software-defined data path allows flexible, programmable actions. The network element converts metadata from the fixed-functionality path to a format compatible with the software-defined path when additional processing is needed. It selects a specific look-up table in the software-defined path based on the most recent fixed-functionality action applied to the data. The network element then performs a look-up in the selected table to determine and initiate the required software-defined actions, using the converted metadata as input. This approach enables seamless integration between rigid, high-performance fixed-functionality operations and adaptable, software-defined processing, improving flexibility without sacrificing efficiency. The system dynamically bridges the two paths, ensuring consistent data handling while allowing for customizable actions when needed.
3. The network element according to claim 1 , wherein the processing system is further adapted to: convert the converted first metadata back to a data format suitable for the software-defined data path in response to a need to carry out one or more of the software-defined actions after carrying out the needed one or more fixed-functionality actions; determine a second one of the look-up tables of the software-defined data path at least partly on the basis of which one of the one or more needed fixed-functionality actions was most recently carried out when managing the first data by the fixed-functionality data path; and carry out a look-up from the determined second one of the look-up tables so as to initiate the one or more software-defined actions needed to be carried out after the one or more needed fixed-functionality actions and at least partly in accordance with the back converted first metadata.
This invention relates to a network element that integrates fixed-functionality and software-defined data paths to optimize packet processing. The problem addressed is the inefficiency of traditional network elements that either rely solely on fixed-functionality hardware for high-speed processing or software-defined approaches for flexibility, but lack seamless integration between the two. The network element includes a processing system that manages data by first converting metadata associated with incoming data into a format compatible with the fixed-functionality data path. This allows the system to perform necessary fixed-functionality actions, such as packet classification or forwarding, at high speed. After these actions, the metadata is converted back to a format suitable for the software-defined data path. The processing system then determines which of the software-defined data path's look-up tables to use based on the most recently executed fixed-functionality action. A look-up is performed in this table to initiate the required software-defined actions, such as dynamic routing or policy enforcement, using the restored metadata. This hybrid approach ensures efficient processing while maintaining flexibility for software-defined operations. The invention improves performance by leveraging hardware acceleration where possible while dynamically adapting to software-defined requirements.
4. The network element according to claim 2 , wherein the processing system is further adapted to: convert the converted second metadata back to the data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions after carrying out the needed one or more software-defined actions; determine a second one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the second data by the software-defined data path; and control the determined second one of the fixed-functionality actions to be carried out so as to initiate the one or more fixed-functionality actions needed to be carried out after the one or more needed software-defined actions and at least partly in accordance with the back converted second metadata.
A network element includes a processing system that manages data using both a software-defined data path and a fixed-functionality data path. The software-defined data path performs actions based on configurable software logic, while the fixed-functionality data path executes predefined, hardware-optimized actions. The processing system converts metadata associated with data from a format suitable for the fixed-functionality data path to a format usable by the software-defined data path when software-defined actions are required. After performing these actions, the processing system converts the metadata back to the original format for further fixed-functionality processing. The system determines which fixed-functionality action to execute next based on which look-up table was most recently accessed during software-defined processing. This ensures seamless transition between software-defined and fixed-functionality operations, optimizing performance and flexibility. The solution addresses the challenge of efficiently integrating programmable software logic with high-speed, hardware-accelerated functions in network elements.
5. The network element according to claim 1 , wherein the processing system is adapted to construct the software-defined data path in accordance with at least one of the following: the OpenFlow protocol, the Forwarding and Control Element Separation ForCES protocol.
This invention relates to network elements designed to construct and manage software-defined data paths in communication networks. The primary problem addressed is the need for flexible and programmable network control, where traditional hardware-based routing is inflexible and lacks dynamic adaptability. The network element includes a processing system that constructs a software-defined data path, enabling centralized control of packet forwarding decisions. This allows for dynamic reconfiguration of network behavior without manual hardware adjustments. The processing system is specifically adapted to construct the software-defined data path using either the OpenFlow protocol or the Forwarding and Control Element Separation (ForCES) protocol. OpenFlow is a widely adopted protocol that enables software-defined networking (SDN) by separating the control plane from the data plane, allowing a centralized controller to manage forwarding rules. ForCES, on the other hand, provides a standardized way to separate forwarding and control functions, enabling more granular control over network elements. By supporting both protocols, the network element ensures compatibility with different SDN architectures and deployment scenarios. This flexibility allows network operators to choose the most suitable protocol based on their specific requirements, such as scalability, performance, or integration with existing infrastructure. The invention enhances network agility, simplifies management, and improves efficiency in modern communication networks.
6. The network element according to claim 1 , wherein the processing system is adapted to configure the fixed-functionality data path in accordance with at least one of the following: one or more L3 network layer routing protocols, one or more L2 data link layer control protocols, one or more MultiProtocol Label Switching MPLS signaling protocols.
A network element includes a processing system and a fixed-functionality data path. The processing system configures the data path to handle network traffic based on specific protocols. The configuration supports one or more L3 network layer routing protocols, such as OSPF or BGP, for routing decisions at the network layer. It also supports one or more L2 data link layer control protocols, such as STP or LACP, for managing data link layer operations. Additionally, the configuration includes support for one or more MultiProtocol Label Switching (MPLS) signaling protocols, such as LDP or RSVP-TE, for label switching and traffic engineering. The fixed-functionality data path is optimized for high-speed processing of network traffic in accordance with these protocols, reducing the need for software-based processing and improving efficiency. This approach allows the network element to dynamically adapt its data path configuration to different network protocols, enhancing flexibility and performance in various network environments. The solution addresses the challenge of efficiently handling diverse network protocols while maintaining high throughput and low latency.
7. The network element according to claim 6 , wherein: the one or more L3 network layer routing protocols comprise at least one of the following: the Open Shortest Path First OSPF, the Intermediate system-Intermediate system ISIS, the Border Gateway Protocol BGP, the Protocol Independent multicast Sparse Mode PIM-SM; the one or more L2 data link layer control protocols comprise at least one of the following: the Spanning Tree Protocol STP, the Rapid Spanning Tree Protocol RSTP, the multiple Spanning Tree Protocol MSTP, the Transparent Interconnection of Lots of Links TRILL, the Link Aggregation Control Protocol LACP; and the one or more MultiProtocol Label Switching MPLS signaling protocols comprise at least one of the following: Label Distribution Protocol LDP, Resource Reservation Protocol-Traffic Engineering RSVP-TE, the Bor-der Gateway Protocol BGP.
This invention relates to a network element designed to manage and optimize network traffic across multiple layers of the network stack. The problem addressed is the complexity of integrating and coordinating various routing, control, and signaling protocols across different network layers, which can lead to inefficiencies, scalability issues, and suboptimal traffic management. The network element is configured to support one or more Layer 3 (L3) network layer routing protocols, including Open Shortest Path First (OSPF), Intermediate System-to-Intermediate System (ISIS), Border Gateway Protocol (BGP), and Protocol Independent Multicast Sparse Mode (PIM-SM). These protocols are used for dynamic routing and path selection in IP networks. Additionally, the network element supports one or more Layer 2 (L2) data link layer control protocols, such as Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), Transparent Interconnection of Lots of Links (TRILL), and Link Aggregation Control Protocol (LACP). These protocols manage network topology, redundancy, and link aggregation to enhance reliability and performance. Furthermore, the network element supports one or more MultiProtocol Label Switching (MPLS) signaling protocols, including Label Distribution Protocol (LDP), Resource Reservation Protocol-Traffic Engineering (RSVP-TE), and BGP. These protocols enable efficient label switching and traffic engineering in MPLS networks. By integrating these protocols, the network element provides a unified approach to traffic management, improving scalability, efficiency, and reliability in modern network architectures.
8. The network element according to claim 1 , wherein the software-defined data path comprises at least one of the following: a look-up table suitable for selecting between the software-defined data path and the fixed-functionality data path, a look-up table suitable for quality-of-service QoS management, a look-up table suitable for MultiProtocol Label Switching MPLS, a look-up table suitable for Access Control List ACL filtering, a look-up table suitable for Internet Protocol IP routing, a look-up table suitable for Ethernet switching, a look-up table suitable for load balancing, a look-up table suitable for flow protection.
In the field of network routing and switching, traditional network elements rely on fixed-functionality data paths, which lack flexibility and programmability. This limits their ability to adapt to evolving network requirements, such as dynamic traffic patterns, quality-of-service (QoS) demands, and security policies. A network element with a software-defined data path addresses these limitations by incorporating programmable look-up tables that enable flexible routing and switching decisions. The software-defined data path includes at least one look-up table for selecting between the software-defined and fixed-functionality data paths, ensuring efficient traffic management. Additional look-up tables support QoS management, MultiProtocol Label Switching (MPLS), Access Control List (ACL) filtering, Internet Protocol (IP) routing, Ethernet switching, load balancing, and flow protection. These tables allow the network element to dynamically adjust to different network conditions, optimize traffic flow, enforce security policies, and balance workloads across network resources. By integrating these programmable components, the network element provides greater adaptability and control over data forwarding, improving overall network performance and efficiency.
9. The network element according to claim 1 , wherein the fixed-functionality data path is capable of carrying out at least one of the following: Virtual Local Access Network VLAN management, Virtual Router Redundancy Protocol VRRP destination Media Access Control MAC filtering, quality-of-service management, MultiProtocol Label Switching MPLS, Access Control List ACL filtering, Internet Protocol IP routing, Ethernet switching, load balancing, flow protection, link aggregation, Outgoing Media Access Control MAC imposition.
This invention relates to network elements designed to enhance data processing and forwarding in communication networks. The primary problem addressed is the need for efficient, high-performance data path operations in network devices, particularly those handling diverse traffic management tasks. The network element includes a fixed-functionality data path optimized for specific network operations, ensuring predictable performance and reduced latency compared to general-purpose processing. The fixed-functionality data path is capable of performing at least one of several key network functions. These include Virtual Local Access Network (VLAN) management for segmenting network traffic, Virtual Router Redundancy Protocol (VRRP) destination Media Access Control (MAC) filtering for failover redundancy, and quality-of-service (QoS) management to prioritize traffic. Additionally, it supports MultiProtocol Label Switching (MPLS) for efficient packet forwarding, Access Control List (ACL) filtering for security, Internet Protocol (IP) routing for path determination, and Ethernet switching for frame forwarding. Other functions include load balancing to distribute traffic, flow protection to prevent congestion, link aggregation to combine multiple links, and Outgoing MAC imposition to modify MAC addresses before transmission. This specialized hardware acceleration ensures high throughput and low-latency processing for these critical network operations.
10. A method for managing data in a network element of a software-defined network, the method comprising: maintaining, in accordance with configuration data received from a controller of the software-defined network, a software-defined data path for managing first data to be forwarded, the software-defined data path comprising look-up tables for selecting software-defined actions and one or more of the software-defined actions modifying first metadata associated with the first data; maintaining, in accordance with forwarding-parameter data received at the network element, a fixed-functionality data path for managing second data to be forwarded, the fixed-functionality data path defining fixed-functionality actions and one or more of the fixed-functionality actions modifying second metadata associated with the second data; converting the first metadata associated with the first data being managed by the software-defined data path to a data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions in conjunction with forwarding the first data; determining a first one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the first data; and controlling the determined first one of the fixed-functionality actions to be carried out so as to initiate the needed one or more fixed-functionality actions to be carried out at least partly in accordance with the converted first metadata.
In the domain of software-defined networking (SDN), managing data flows efficiently while integrating both programmable and fixed-functionality data paths presents challenges. This invention addresses the need to seamlessly transition data between a software-defined data path and a fixed-functionality data path within a network element, ensuring consistent metadata handling and action execution. The method involves maintaining two distinct data paths: a software-defined data path and a fixed-functionality data path. The software-defined data path operates based on configuration data from an SDN controller, using look-up tables to select software-defined actions that modify metadata associated with incoming data. The fixed-functionality data path, governed by forwarding-parameter data, performs predefined actions that also modify metadata but lacks the programmability of the software-defined path. When data managed by the software-defined path requires processing by the fixed-functionality path, the metadata is converted into a compatible format. The system determines which fixed-functionality action to execute based on the most recently accessed look-up table in the software-defined path. This action is then triggered, ensuring the necessary fixed-functionality operations are performed in accordance with the converted metadata. This approach enables efficient integration of programmable and fixed-functionality data processing within an SDN environment.
11. The method according to claim 10 , wherein the method further comprises: converting the second metadata associated with the second data being managed by the fixed-functionality data path to a data format suitable for the software-defined data path in response to a need to carry out one or more of the software-defined actions in conjunction with forwarding the second data, determining a first one of the look-up tables of the software-defined data path at least partly on the basis of which one of the fixed-functionality actions was most recently carried out when managing the second data, and carrying out a look-up from the determined first one of the look-up tables so as to initiate the one or more needed software-defined actions to be carried out at least partly in accordance with the converted second metadata.
This invention relates to data processing systems that combine fixed-functionality and software-defined data paths. The problem addressed is efficiently integrating software-defined actions with fixed-functionality operations in a way that minimizes latency and processing overhead. The system manages data using a fixed-functionality data path, which performs predefined actions, while also supporting software-defined actions through a separate software-defined data path. When software-defined actions are needed in conjunction with forwarding data, the system converts metadata associated with the data from a fixed-functionality format to one suitable for the software-defined data path. The conversion ensures compatibility between the two paths. The system then determines which look-up table in the software-defined data path to use based on the most recent fixed-functionality action performed on the data. A look-up is performed in this table to initiate the required software-defined actions, which are executed in accordance with the converted metadata. This approach allows seamless integration of fixed and software-defined operations, improving flexibility and efficiency in data processing.
12. The method according to claim 10 , wherein the method further comprises: converting the converted first metadata back to a data format suitable for the software-defined data path in response to a need to carry out one or more of the software-defined actions after carrying out the needed one or more fixed-functionality actions; determining a second one of the look-up tables of the software-defined data path at least partly on the basis of which one of the one or more needed fixed-functionality actions was most recently carried out when managing the first data by the fixed-functionality data path; and carrying out a look-up from the determined second one of the look-up tables so as to initiate the one or more software-defined actions needed to be carried out after the one or more needed fixed-functionality actions and at least partly in accordance with the back converted first metadata.
This invention relates to a method for managing data in a system that combines fixed-functionality and software-defined data paths. The problem addressed is efficiently transitioning between these paths to perform a sequence of actions, ensuring compatibility and continuity of data processing. The method involves converting metadata associated with data from a format suitable for a software-defined data path to a format compatible with a fixed-functionality data path. This conversion allows the fixed-functionality data path to perform one or more required actions on the data. After these actions, the metadata is converted back to its original format for further processing by the software-defined data path. The method also determines a specific look-up table in the software-defined data path based on the most recently executed fixed-functionality action, then uses this table to initiate subsequent software-defined actions. This ensures seamless integration between the two processing paths, optimizing performance and maintaining data integrity throughout the workflow. The approach is particularly useful in systems where certain operations must be handled by fixed-functionality hardware, while others are managed by programmable software components.
13. The method according to claim 11 , wherein the method further comprises: converting the converted second metadata back to the data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions after carrying out the needed one or more software-defined actions; determining a second one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the second data by the software-defined data path; and controlling the determined second one of the fixed-functionality actions to be carried out so as to initiate the one or more fixed-functionality actions needed to be carried out after the one or more needed software-defined actions and at least partly in accordance with the back converted second metadata.
This invention relates to data processing systems that combine software-defined and fixed-functionality data paths. The problem addressed is efficiently managing data flow between these two types of processing paths, particularly when transitioning between them. The system processes data using a software-defined data path, which involves accessing look-up tables to determine actions. After performing these software-defined actions, the system may need to revert to fixed-functionality actions. To facilitate this, the system converts metadata associated with the data into a format suitable for the fixed-functionality data path. When fixed-functionality actions are required, the system converts the metadata back to its original format. The system then determines which fixed-functionality action to perform based on which look-up table was most recently accessed during the software-defined processing. This ensures continuity and efficiency in data processing. The determined fixed-functionality action is then executed, using the back-converted metadata to guide the process. This approach optimizes the transition between software-defined and fixed-functionality processing, improving overall system performance.
14. The method according to claim 10 , wherein the software-defined data path is maintained in accordance with at least one of the following: the OpenFlow protocol, the Forwarding and Control Element Separation ForCES protocol.
This invention relates to software-defined networking (SDN) and addresses the challenge of dynamically managing data paths in network systems. The method involves maintaining a software-defined data path using standardized protocols to enhance flexibility and control over network traffic flow. The data path is configured and managed through a centralized controller, allowing for real-time adjustments to routing and forwarding rules. The invention ensures compatibility with multiple protocols, including OpenFlow and the Forwarding and Control Element Separation (ForCES) protocol, enabling interoperability across different network environments. By leveraging these protocols, the system can dynamically update forwarding rules, optimize traffic distribution, and improve network performance. The method supports seamless integration with existing network infrastructure while providing scalable and programmable control over data flow. This approach simplifies network management, reduces operational complexity, and enhances adaptability to changing network conditions. The use of standardized protocols ensures consistency and reliability in network operations, making it suitable for various applications, including data centers, enterprise networks, and service provider environments. The invention provides a robust framework for implementing software-defined networking solutions that are both flexible and efficient.
15. The method according to claim 10 , wherein the fixed-functionality data path is maintained in accordance with at least one of the following: one or more L3 network layer routing protocols, one or more L2 data link layer control protocols, one or more MultiProtocol Label Switching MPLS signaling protocols.
This invention relates to network communication systems, specifically methods for managing data paths in network devices. The problem addressed is the need for efficient and reliable data path management in network devices, particularly in handling routing, control, and signaling protocols across different network layers. The method involves maintaining a fixed-functionality data path in a network device. This data path is configured to process network traffic according to predefined rules and protocols, ensuring consistent and predictable behavior. The data path is maintained in compliance with at least one of several network protocols, including L3 network layer routing protocols (such as OSPF or BGP), L2 data link layer control protocols (such as STP or LACP), or MultiProtocol Label Switching (MPLS) signaling protocols (such as LDP or RSVP-TE). These protocols govern how data is routed, switched, or labeled within the network, ensuring proper traffic flow and network stability. The fixed-functionality data path is designed to handle specific tasks without requiring dynamic reconfiguration, which improves performance and reduces complexity. By adhering to standardized protocols, the method ensures interoperability with other network devices and maintains network reliability. This approach is particularly useful in high-performance networking environments where predictable and efficient data handling is critical.
16. The method according to claim 15 , wherein: the one or more L3 network layer routing protocols comprise at least one of the following: the Open Shortest Path First OSPF, the Intermediate system-Intermediate system ISIS, the Border Gateway Protocol BGP, the Protocol Independent multicast Sparse Mode PIM-SM, the one or more L2 data link layer control protocols comprise at least one of the following: the Spanning Tree Protocol STP, the Rapid Spanning Tree Protocol RSTP, the multiple Spanning Tree Protocol MSTP, the Transparent Interconnection of Lots of Links TRILL, the Link Aggregation Control Protocol LACP, and the one or more MultiProtocol Label Switching MPLS signaling protocols comprise at least one of the following: Label Distribution Protocol LDP, Resource Reservation Protocol-Traffic Engineering RSVP-TE, the Border Gateway Protocol BGP.
This invention relates to network management systems that monitor and analyze network protocols to detect and mitigate potential security threats. The system collects and processes data from multiple network layers, including Layer 3 (L3) routing protocols, Layer 2 (L2) data link layer control protocols, and MultiProtocol Label Switching (MPLS) signaling protocols. The L3 routing protocols monitored include Open Shortest Path First (OSPF), Intermediate System-to-Intermediate System (ISIS), Border Gateway Protocol (BGP), and Protocol Independent Multicast Sparse Mode (PIM-SM). The L2 control protocols monitored include Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), Transparent Interconnection of Lots of Links (TRILL), and Link Aggregation Control Protocol (LACP). The MPLS signaling protocols monitored include Label Distribution Protocol (LDP) and Resource Reservation Protocol-Traffic Engineering (RSVP-TE), in addition to BGP. The system analyzes protocol behavior to identify anomalies, misconfigurations, or malicious activities that could compromise network security or performance. By continuously monitoring these protocols, the system provides early detection of potential threats and supports proactive mitigation strategies to maintain network integrity.
17. The method according to claim 10 , wherein the software-defined data path comprises at least one of the following: a look-up table suitable for selecting between the software-defined data path and the fixed-functionality data path, a look-up table suitable for quality-of-service QoS management, a look-up table suitable for MultiProtocol Label Switching MPLS, a look-up table suitable for Access Control List ACL filtering, a look-up table suitable for Internet Protocol IP routing, a look-up table suitable for Ethernet switching, a look-up table suitable for load balancing, a look-up table suitable for flow protection.
A method for managing data traffic in a network device involves a software-defined data path that can be dynamically configured to handle various networking functions. The software-defined data path includes multiple look-up tables, each optimized for specific tasks such as selecting between the software-defined and fixed-functionality data paths, managing quality-of-service (QoS) parameters, supporting MultiProtocol Label Switching (MPLS), enforcing Access Control List (ACL) filtering, performing Internet Protocol (IP) routing, facilitating Ethernet switching, distributing traffic for load balancing, and providing flow protection. These look-up tables enable flexible and programmable control over data traffic, allowing the network device to adapt to different networking requirements without relying solely on fixed hardware functions. The approach enhances network performance, security, and efficiency by dynamically adjusting traffic handling based on real-time conditions and predefined policies. This method is particularly useful in modern networking environments where adaptability and programmability are critical for optimizing data flow and resource utilization.
18. The method according to claim 10 , wherein the fixed-functionality data path is capable of carrying out at least one of the following: Virtual Local Access Network VLAN management, Virtual Router Redundancy Protocol VRRP destination Media Access Control MAC filtering, quality-of-service management, MultiProtocol Label Switching MPLS, Access Control List ACL filtering, Internet Protocol IP routing, Ethernet switching, load balancing, flow protection, link aggregation, Outgoing Media Access Control MAC imposition.
This invention relates to network processing systems, specifically methods for implementing fixed-functionality data paths in network devices to enhance performance and efficiency. The technology addresses the need for specialized hardware acceleration in network devices to handle high-speed data processing tasks that are typically performed by software-based solutions, which can introduce latency and reduce throughput. The method involves configuring a fixed-functionality data path within a network device to perform specific network operations without requiring software intervention. This data path is designed to execute at least one of several key network functions, including Virtual Local Area Network (VLAN) management, Virtual Router Redundancy Protocol (VRRP) destination Media Access Control (MAC) filtering, quality-of-service (QoS) management, MultiProtocol Label Switching (MPLS), Access Control List (ACL) filtering, Internet Protocol (IP) routing, Ethernet switching, load balancing, flow protection, link aggregation, and outgoing MAC imposition. By offloading these tasks to a dedicated hardware path, the system improves processing speed and reduces the burden on the device's central processing unit (CPU), leading to more efficient network operations. The fixed-functionality data path operates independently of the main processing unit, allowing for real-time handling of network traffic with minimal delay. This approach is particularly beneficial in high-performance networking environments where low latency and high throughput are critical. The method ensures that network devices can manage complex traffic flows efficiently while maintaining scalability and reliability.
19. A non-transitory computer readable medium encoded with a computer program recorded thereon comprising computer executable instructions for, upon execution by a programmable processing system of a network element of a software-defined network controlling the network element to: construct, in accordance with configuration data received from a controller of the software-defined network, a software-defined data path for managing first data to be forwarded, the software-defined data path comprising look-up tables for selecting software-defined actions and one or more of the software-defined actions modifying first metadata associated with the first data; configure, in accordance with forwarding-parameter data received at the network element, a fixed-functionality data path for managing second data to be forwarded, the fixed-functionality data path defining fixed-functionality actions and one or more of the fixed-functionality actions modifying second metadata associated with the second data; convert the first metadata associated with the first data being managed by the software-defined data path to a data format suitable for the fixed-functionality data path in response to a need to carry out one or more of the fixed-functionality actions in conjunction with forwarding the first data; determine one of the fixed-functionality actions from among the fixed-functionality actions at least partly on the basis of which one of the look-up tables was most recently accessed when managing the first data; and control the determined one of the fixed-functionality actions to be carried out so as to initiate the needed one or more fixed-functionality actions to be carried out at least partly in accordance with the converted first metadata.
In the domain of software-defined networking (SDN), managing data forwarding efficiently while integrating both programmable and fixed-functionality data paths presents challenges. This invention addresses the need for seamless interaction between a software-defined data path and a fixed-functionality data path within a network element of an SDN. The solution involves a computer program stored on a non-transitory medium that, when executed, enables a network element to construct a software-defined data path based on configuration data from an SDN controller. This path includes look-up tables for selecting software-defined actions, which modify metadata associated with the data being forwarded. Additionally, the network element configures a fixed-functionality data path using forwarding-parameter data, defining fixed actions that also modify metadata. When the software-defined data path requires fixed-functionality actions, the system converts the metadata from the software-defined format to one compatible with the fixed-functionality path. The selection of a fixed-functionality action is determined based on the most recently accessed look-up table in the software-defined path. The system then executes the selected action, ensuring the necessary fixed-functionality operations are performed using the converted metadata. This approach optimizes data forwarding by dynamically integrating programmable and fixed-functionality components, enhancing flexibility and efficiency in SDN environments.
Unknown
September 3, 2019
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.