US20190245809A1 - System and method for message handling in a network device - Google Patents
System and method for message handling in a network device Download PDFInfo
- Publication number
- US20190245809A1 US20190245809A1 US16/384,074 US201916384074A US2019245809A1 US 20190245809 A1 US20190245809 A1 US 20190245809A1 US 201916384074 A US201916384074 A US 201916384074A US 2019245809 A1 US2019245809 A1 US 2019245809A1
- Authority
- US
- United States
- Prior art keywords
- message
- processing layer
- network
- implemented
- port
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/28—Flow control; Congestion control in relation to timing considerations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
- H04L49/3009—Header conversion, routing tables or routing tags
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/56—Routing software
- H04L45/566—Routing instructions carried by the data packet, e.g. active networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/122—Avoiding congestion; Recovering from congestion by diverting traffic away from congested entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/19—Flow control; Congestion control at layers above the network layer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/101—Access control lists [ACL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0272—Virtual private networks
Definitions
- the present disclosure relates to networking processing performance.
- the present disclosure relates to a system and method for achieving enhanced performance for application message handling in a network device.
- FIG. 1 is a block diagram of exemplary system architecture of a computing network.
- FIG. 2 illustrates exemplary architecture at multiple processing planes according to embodiments of the present disclosure.
- FIG. 3A is a diagram illustrating an exemplary application message network packet according to embodiments of the present disclosure.
- FIG. 3B is a diagram illustrating an exemplary translated application message network packet according to embodiments of the present disclosure.
- FIG. 4 is a flow diagram of a method for translating a network packet according to embodiments of the present disclosure.
- FIG. 5 is a block diagram illustrating a system of according to embodiments of the present disclosure.
- Embodiments of the present disclosure relate to enhancing message handling performance in a network device.
- the present disclosure relates to a system and method for achieving enhanced message handling performance by translation of one or mote addressing fields of an application network data packet in a first processing layer of the network device prior to forwarding of the application network packet to a second processing layer of the network device.
- the first processing layer may be a datapath, a networking operating system, or a secondary operating system executing on the device
- the second processing layer may be a control plane, a UNIXTM based operating system such as LINUXTM, a real-time operating system, or a primary operating system executing on the device.
- the network device may be a network controller that receives a message (e.g., the network data packet), the first processing layer may be the datapath, and the second processing layer may be a control plane.
- a message e.g., the network data packet
- the first processing layer may be the datapath
- the second processing layer may be a control plane.
- the techniques discussed herein need not be limited to a network controller executing a datapath processing layer and a control plane processing layer, as any network device, such as an access point, a network switch, a network router, a network server, a network controller, etc. may employ any combination of processing layers in accordance with the discussion herein.
- the remaining description will describe, but should not be limited to, a network controller with a datapath processing layer and a control plane processing layer.
- an application run by an access point may generate application data.
- the application provides the application data to a message handier at the access point, which encapsulates the application data in a network packet suitable for transmission over a computing network.
- the network packet is a user datagram protocol (UDF) network packet that is divided into a plurality of different fields.
- the different fields include an Ethernet header field, an internet protocol (IP) address header field, a UDP header field, a message passing protocol header field, and a message payload.
- IP internet protocol
- the message handler at the access point then transmits the message over the computing network to a destination device, such as a network controller.
- Network controllers receive the messages including the network packets in a datapath of the network controller, and then provide the network packets to a control plane of the network controller.
- a message handler operating in the control plane of the network controller receives the network packet on a UDP socket, and then delivers the network packet by reading the network packet, writing data to the network packet to enable a recipient application identify the data packet, and forwarding the network packet to the destination application on an operating system socket (e.g., a UNIX kernel socket). Then, the application on the network controller reads the network packet from the operating system socket and processes the application-specific data in the network packet.
- an operating system socket e.g., a UNIX kernel socket
- processes running in the datapath (i.e., first processing layer) of the network controller translate one or more addressing fields of the network packet.
- a destination application operating in the control plane i.e., second processing layer
- the network packet may then simply be read and processed by the application.
- the network 100 may run on one Local Area Network (LAN) and may be incorporated into the same physical or logical system, or different physical or logical systems. Alternatively, network 100 may reside on different LANs, wide area networks, etc. that may be coupled together via the internet but separated oy firewalls, routers, and/or other network devices. It should be noted that various other network configurations can be used including, for example, hosted configurations, distributed configurations, centralized configurations, etc.
- LAN Local Area Network
- the system architecture further includes one or more client computing devices 120 - 1 through 120 -N coupled to the network 100 via network switch 104 , and one or more client computing devices 125 - 1 through 125 -N coupled to the network 100 via wireless AP 108 .
- Client computing devices 120 connect to the network switch 104
- client computing devices 125 connect to the wireless AP 108 , to access services such as the Internet through controller 106 .
- the system architecture further includes one or more network management servers, such as network management server 110 , coupled to the network 100 .
- network management server 110 executes network management applications.
- network management server 110 may provide manual or automated network management services to manage various aspects affecting the network, such as managing the radio frequency environment, controllers, wired infrastructure, and access points.
- Network management server 110 may further provide a user interface to network administrators to provide charts, tables, diagnostic information and alerts.
- controller 106 , router 102 , network switch 104 , wireless AP 108 , and network management server 110 are purpose-made digital devices, each containing a processor, memory hierarchy, and input-output interfaces.
- a MIPS-class processor such as those from Cavium or RMI is used.
- Other suitable processors, such as those from Intel or AMD may also be used.
- the memory hierarchy traditionally comprises fast read/write memory for holding processor data and instructions while operating, and nonvolatile memory such as EEPROM and/or Flash for storing files and system startup information.
- Wired interfaces are typically IEEE 802-3 Ethernet interfaces, used for wired connections to other network devices such as switches, or to a controller.
- Wireless interfaces may be WiMAX, 3G, 4G, and/or IEEE 802.11 wireless interfaces.
- controllers, switches, and wireless APs operate under control of a LINUX® operating system, with purpose-built programs providing controller and access point functionality.
- Client computing devices 120 and 125 also contain a processor, memory hierarchy, and a number of interfaces including a wired and/or wireless interfaces for communicating with network switch 104 or wireless AP 108 .
- Typical client computing devices include personal computers, handheld and tablet computers, Wi-Fi phones, wireless barcode scanners, and the like.
- FIG. 2 illustrates a general architecture of a network device, such as controller 106 , which includes multiple processing planes according to embodiments of the present disclosure.
- FIG. 2 illustrates a controller 200 that includes at least a control plane process 210 , two or more datapath processors 220 , a network interface 250 . and one more applications, such as application 1 260 to application J 262 .
- FIG. 2 further illustrates an access point 270 that includes at least a network interface 278 , a message handier 276 , and one or more applications, such as application 1 272 to application K 274 .
- the controller 200 and the access point 270 are communicatively coupled via a computing network (not shown).
- there may be more than ore access point connected to controller 200 as well as other controllers connected to controller 200 .
- control plane process 210 may be running on one or more CPUs or CPU cores, such as CP CPU 1 212 , CP CPU 2 214 , . . . CP CPU M 218 . Furthermore, control plane process 210 typically handles applications that perform network control or management of traffic generated by and/or terminated at network devices as opposed to data traffic generated and/or terminated at client devices. In one embodiment, the control plane process 210 executes application 1 260 to application J 262 .
- datapath processors 220 include a single slowpath (SP) processor (e.g., SP CPU 230 ) and multiple fastpath (FP) processors (e.g., FP CPU 1 240 , FP CPU 2 242 , . . . FP CPU N 248 ). Only FP processors are able to receive data packets directly from network interface 250 . SP processor, on the other hand, only receives data packets from FP processors. Also, control plane process 210 is communicatively coupled to slowpath (SP) CPU 230 , but not fastpath (FP) processors (e.g., FP CPU 1 240 , FP CPU 2 242 , . . . FP CPU N 248 ). Thus, whenever control plane process 210 needs information from datapath processors 220 , control plane process 210 will communicate with SP processor (e.g., SP CPU 230 ).
- SP slowpath
- FP fastpath
- an application executed at access point 270 is in communication with an application executed at controller 200 .
- the communication is in the form of the exchange of network packets that contain application-specific data generated by corresponding applications.
- application K 274 of access point 270 may generate data for receipt by application J 262 of controller 200 .
- Application K 274 provides the application-specific data to message handler 276 which encapsulates the data in a network packet suitable for transmission to controller 200 .
- FIG. 3A illustrates one embodiment of a network packet 300 .
- the network packet is generated by an application and includes at least header fields 310 , UDP addressing data field 320 , a message passing protocol addressing data field 330 , and a message payload 340 .
- the header fields 310 contain standard fields, such as fields for an Ethernet header, an IP header, as well as other standard messaging fields (not illustrated).
- the UDP addressing data field 320 contains UDP source and UDP destination port addresses that enable the network packet 300 to be routed between appropriate devices as specified by the UDP source port and the UDP destination port addresses.
- the message passing protocol addressing data field 330 contains a message passing protocol source port addresses and a message passing protocol destination port address to enable the message payload within the network packet 300 to be provided to the intended destination application.
- the controller 200 addressing is specified as port 8211
- the application of access point 270 is identified by source port 8224
- the destination application of controller 200 is identified by destination port 8222 .
- the port addresses are illustrative, as other port addresses could be utilized.
- a data packet as illustrated in FIG. 3A is transmitted from network interface 278 of access point 270 over a computing network to network interface 250 of controller 200 .
- the received network packet is processed by at least one of FP processors.
- the FP processors perform a process, which is discussed in greater detail below in FIG. 4 , to translate addressing fields of the received network packet.
- the message passing protocol port address in field 380 which identifies the port of the intended recipient application, replaces the UDP destination port address in field 370 .
- the remaining header fields 360 and message payload 390 remain unchanged, except for the updated computation of a message checksum, which may be contained in the UDP addressing field 370 .
- the UDP destination port address 370 is updated to port 8222 .
- the translated network packet as illustrated in FIG. 3B , is provided to a kernel (not shown) that bridges the datapath processors 220 and the control plane process 210 .
- the applications e.g., application 1 260 to application J 262 ) listen to the kernel for network packets with corresponding port addresses in the UDP destination port address. When an application detects a network packet with the appropriate addressing data, the application reads the network packet and consumes the application-specific data in message payload 390 .
- controller 200 Because the applications of controller 200 listen for their corresponding port addresses, a message handler application need not be run in the control plane for managing the routing of network packets to appropriate applications. As a result, processing resources are freed on the control plane for applications 260 through 262 , as well as other processes on the control plane. Furthermore, when an application on controller 200 transmits application data to an application on access point 270 , the FP processors in the datapath 220 perform a complementary network packet translation process that changes the source UDP port address to the destination UDP port address. In one embodiment, the source UDP port address is translated to the destination UDP port address so that both the source and destination UDP ports are addressed to the destination device message handler port, such as port 8211 .
- FIG. 4 is a flow diagram of a method for translating a network packet according to embodiments of the present disclosure.
- the method 400 is performed by processing logic that may comprise hardware (circuitry, dedicated logic, etc.), software (such as is run on a general purpose computer system, networking device, or other dedicated machine), firmware, or a combination.
- the method 400 is performed by one or more datapath processors 220 of a network controller 200 .
- other network devices may perform the network packet translation in accordance with the techniques described herein.
- the process begins when a FP processor in a datapath of a network controller receives a message from an application (processing block 402 ).
- the message is a UDP network packet.
- processing logic receives the UDP network packet on a UDP socket, such as port 8211 or port 8209 .
- the application may be an application on a different network device, such as an access point, network server, bridge, router, etc. which has communicated the network packet to the network controller.
- the network packet may encapsulate application-specific data within the UDP network packet to be processes by a recipient application.
- Processing logic translates the UDP destination port address field in the message to a destination port address located in a message passing protocol destination address field of the network packet (processing block 404 ). In one embodiment, processing logic utilizes the destination application port address to overwrite the UDP port address field value in a network packet.
- Processing logic then provides the translated message to a control plane of the network controller (processing block 406 ).
- processing logic forwards a translated network packet to an operating system socket specified by the message passing protocol destination address field.
- the recipient application can detect when a network packet is available by monitoring the UDP destination port addresses.
- the intended destination application of the controller may then consume the application-specific data in the payload of the network packet.
- the process performed at processing block 406 may also include encapsulating the network packet into a transmission control protocol (TCP) session within the dataplane.
- processing logic can further convert the network packet to one or more UDP packets.
- the message passing protocol header data i.e., the destination port address
- the network packet(s) would be further modified by adding internet protocol (IP) header data to the network packet(s) for the corresponding TCP session.
- IP internet protocol
- FIG. 5 is a block diagram illustrating a network device according to embodiments of the present disclosure.
- Network device 500 includes at least a network interface 510 capable of communicating to a wired or wireless network, a memory 520 capable of storing data, a slowpath processor core 530 capable of processing network data packets, and one or more fastpath processor core,. including fastpath processor core 542 , fastpath processor core 544 , . . . , fastpath processor core 548 , which are capable of processing network data packets.
- network device 500 may be used as a network switch, network router, network controller, network server, etc. Further network device 500 may serve as a node in a distributed or a cloud computing environment.
- Network interface 510 can be any communication interface, which includes but is not limited to, a modem, token ring interface. Ethernet interface, wireless IEEE 802.11 interface (e.g., IEEE802.11n, IEEE 802.11ac, etc.), cellular wireless interface, satellite transmission interface, or any other interface for coupling network devices.
- network interface 510 may be software-defined and programmable, for example, via an Application Programming Interface (API), and thus allowing for remote control of the network device 600 .
- API Application Programming Interface
- Memory 520 can include storage components, such as, Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), etc.
- memory 520 is a flat structure that is shared by all datapath processors (including, e.g., slow path processor core 530 , fastpath processor core 542 , fastpath processor core 544 , . . . , fastpath processor core 548 , etc.), and not tied to any particular CPU or CPU cores.
- Any datapath processor can read any memory location within memory 520 .
- Memory 520 can be used to store various tables to assist software network packet forwarding.
- the tables may include, but are not limited to, a bridge table, a session table, a user table, a station table, a tunnel table, a route table and/or route cache, etc.
- Slowpath processor core 530 typically includes a networking processor core that is capable of processing network data traffic.
- Slowpath processor core 530 is a single dedicated CPU core that typically handles table managements. Note that, slowpath processor core 530 only receives data packets from one or more fastpath processor cores, such as fastpath processor core 542 , fastpath processor core 544 , . . . , fastpath processor core 543 . In other words, slowpath processor core 530 does not receive data packets directly from any tine cards or network interfaces.
- Fastpath processor cores 542 - 548 also include networking processor cores that are capable of processing network data traffic. However, by definition, fastpath processor cores 542 - 548 only performs “fast” packet processing. Thus, fastpath processor cores 542 - 549 do not block themselves and wait for other components or modules during the processing of network packets. Any packets requiring special handling or wait by a processor core will be handed over by fastpath processor cores 542 - 548 to slowpath processor core 530 .
- network services provided by network device 500 include, but are not limited to, an Institute of Electrical and Electronics Engineers (IEEE) 802.1x authentication to an internal and/or external Remote Authentication Dial-In User Service (RADIUS) server; an MAC authentication to an internal and/or external RADIUS server; a built-in Dynamic Host Configuration Protocol (DHCP) service to assign wireless client devices IP addresses; an internal secured management interface; Layer-3 forwarding; Network Address Translation (NAT) service between the wireless network and a wired network coupled to the network device; an internal and/or external captive portal; an external management system for managing the network devices in the wireless network; etc.
- IEEE Institute of Electrical and Electronics Engineers
- RADIUS Remote Authentication Dial-In User Service
- DHCP Dynamic Host Configuration Protocol
- NAT Network Address Translation
- the present disclosure may be realized in hardware, software, or a combination of hardware and software.
- the present disclosure may be realized in a centralized fashion in one computer system or in a distributed fashion where different elements are spread across several interconnected computer systems coupled to a network.
- a typical combination of hardware and software may be an access point, a network controller, etc. with a computer program that, when being loaded and executed, controls the device such that it carries out the methods described herein.
- the present disclosure also may be embedded in non-transitory fashion in a computer-readable storage medium (e.g., a programmable circuit; a semiconductor memory such as a volatile memory such as random access memory “RAM,” or non-volatile memory such as read-only memory, power-backed RAM. flash memory, phase-change memory or the like; a hard disk drive; an optical disc drive; or any connector for receiving a portable memory device such as a Universal Serial Bus “USB” flash drive), which comprises alt the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods.
- a computer-readable storage medium e.g., a programmable circuit; a semiconductor memory such as a volatile memory such as random access memory “RAM,” or non-volatile memory such as read-only memory, power-backed RAM. flash memory, phase-change memory or the like; a hard disk drive; an optical disc drive; or any connector for receiving a portable memory device such as a Universal Serial Bus “USB”
- Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
- digital device generally includes a device that is adapted to transmit and/or receive signaling and to process information within such signaling such as a station (e.g., any data processing equipment such as a computer, cellular phone, personal digital assistant, tablet devices, etc.), an access point, data transfer devices (such as network switches, routers, controllers, etc.) or the like.
- a station e.g., any data processing equipment such as a computer, cellular phone, personal digital assistant, tablet devices, etc.
- data transfer devices such as network switches, routers, controllers, etc.
- access point generally refers to receiving points for any known or convenient wireless access technology which may later become known. Specifically, the term AP is not intended to be limited to IEEE 802.11-based APs. APs generally function as an electronic device that is adapted to allow wireless devices to connect to a wired network via various communications standards.
- interconnect or used descriptively as “interconnected” is generally defined as a communication pathway established over an information-carrying medium.
- the “interconnect” may be a wired interconnect, wherein the medium is a physical medium (e.g., electrical wire, optical fiber, cable, bus traces, etc.), a wireless interconnect (e.g., air in combination with wireless signaling technology) or a combination of these technologies.
- information is generally defined as data, address, control, management (e.g., statistics) or any combination thereof.
- information may be transmitted as a message, namely a collection of bits in a predetermined format.
- One type of message namely a wireless message, includes a header and payload data having a predetermined number of bits of information.
- the wireless message may be placed in a format as one or more packets, frames or cells.
- wireless focal area network generally refers to a communications network links two or more devices using some wireless distribution method (for example, spread-spectrum or orthogonal frequency-division multiplexing radio), and usually providing a connection through an access point to the Internet; and thus, providing users with the mobility to move around within a local coverage area and still stay connected to the network.
- some wireless distribution method for example, spread-spectrum or orthogonal frequency-division multiplexing radio
- nism generally refers to a component of a system or device to serve one or more functions, including but not limited to, software components, electronic components, electrical components, mechanical components, electro-mechanical components, etc.
- the tern “embodiment” generally refers an embodiment that serves to illustrate by way of example but not limitation.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The present disclosure discloses a method and system for achieving enhanced performance for application message handling. The disclosed system includes a device and is configured to receive, at a first processing layer implemented by the device, a message addressed to a first port. The system is further configured to modify the message to be addressed to a second port indicated in a body of the message prior to forwarding the message to a second processing layer implemented by the device. Furthermore, the system is configured to forward, by the first processing layer to the second processing layer, the modified message addressed to the second port.
Description
- This application claims the benefit of priority on U.S. Provisional Patent Application 61/732,829, filed Dec. 3, 2012, the entire contents of which are incorporated by reference.
- Related patent applications to the subject application include the following: (1) U.S. Patent Application entitled System and Method for Achieving Enhanced Performance with Multiple Networking Central Processing Unit (CPU) Cores by Janakiraman, et al., U.S. application Ser. No. 13/692,622, filed Dec. 3, 2012, attorney docket reference no. 6259P186; (2) U.S. Patent Application entitled Ingress Traffic Classification and Prioritization with Dynamic Load Balancing by Janakiraman, et al., U.S. application Ser. No. 13/692,608, filed Dec. 3, 2012, attorney docket reference no. 6259P191; (3) U.S. Patent Application entitled Method and System for Maintaining Derived Data Sets by Gopalasetty, et al., U.S. application Ser. No. 13/692,920, filed Dec. 3, 2012, attorney docket reference no. 6259P192; (4) U.S. Patent Application entitled Session-Based Forwarding by Janakiraman, et at., U.S. Application No. ______, filed Jun. 14, 2013, attorney docket reference no. 6259P184; (5) U.S. Patent Application entitled Rate Limiting Mechanism Based on Device Load/Capacity or Traffic Content by Nambiar, et al., U.S. Application No. ______, filed Jun. 14, 2013, attorney docket reference no. 6259P185; (6) U.S. Patent Application entitled Control Plane Protection for Various Tables Using Storm Prevention Entries by Janakiraman, et al., U.S. Application No. ______, filed Jun. 14, 2013, attorney docket reference no. 6259P188.
- The present disclosure relates to networking processing performance. In particular, the present disclosure relates to a system and method for achieving enhanced performance for application message handling in a network device.
- Network devices, such as network controllers, access points, network servers, etc. exchange network packets. The network packets may be generated by applications run on a network device, and communicated to another network device for the purpose of processing of those network packages. For example, an application run by an access point may generate network packets that include application specific data. The access point then transmits the network packets to a network controller to enable an application run by the network controller to process the application specific data. Such applications may include security applications, network performance applications, data routing applications, etc.
- Because there are typically numerous network packets being transferred between network devices over a computing network simultaneously, the efficient handling of those network packets becomes increasingly important in order to avoid data bottlenecks at the destination network devices, as well as to enable the timely processing and exchange of application-specific data between applications on different network devices.
- The present disclosure may be best understood by referring to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure.
-
FIG. 1 is a block diagram of exemplary system architecture of a computing network. -
FIG. 2 illustrates exemplary architecture at multiple processing planes according to embodiments of the present disclosure. -
FIG. 3A is a diagram illustrating an exemplary application message network packet according to embodiments of the present disclosure. -
FIG. 3B is a diagram illustrating an exemplary translated application message network packet according to embodiments of the present disclosure. -
FIG. 4 is a flow diagram of a method for translating a network packet according to embodiments of the present disclosure. -
FIG. 5 is a block diagram illustrating a system of according to embodiments of the present disclosure. - In the following description, several specific details are presented to provide a thorough understanding. While the context of the disclosure is directed to performance enhancements for message handling in a network device, one skilled in the relevant art will recognize, however, that the concepts and techniques disclosed herein can be practiced without one or more of the specific details, or in combination with other components, etc. In other instances, well-known implementations or operations are not shown or described in details to avoid obscuring aspects of various examples disclosed herein. It should be understood that this disclosure covers all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure.
- Embodiments of the present disclosure relate to enhancing message handling performance in a network device. In particular, the present disclosure relates to a system and method for achieving enhanced message handling performance by translation of one or mote addressing fields of an application network data packet in a first processing layer of the network device prior to forwarding of the application network packet to a second processing layer of the network device. The first processing layer may be a datapath, a networking operating system, or a secondary operating system executing on the device, and the second processing layer may be a control plane, a UNIX™ based operating system such as LINUX™, a real-time operating system, or a primary operating system executing on the device. In the embodiments discussed herein, the network device may be a network controller that receives a message (e.g., the network data packet), the first processing layer may be the datapath, and the second processing layer may be a control plane. However, the techniques discussed herein need not be limited to a network controller executing a datapath processing layer and a control plane processing layer, as any network device, such as an access point, a network switch, a network router, a network server, a network controller, etc. may employ any combination of processing layers in accordance with the discussion herein. However, in order to avoid obscuring the invention, the remaining description will describe, but should not be limited to, a network controller with a datapath processing layer and a control plane processing layer.
- Applications run on different network devices communicate with one another via the exchange of messages, such as network routable data packets addressed to devices and/or applications executing on destination devices. As discussed herein, references to messages, data packets, and network packets are interchangeable. For example, an application run by an access point may generate application data. The application provides the application data to a message handier at the access point, which encapsulates the application data in a network packet suitable for transmission over a computing network. In one embodiment, the network packet is a user datagram protocol (UDF) network packet that is divided into a plurality of different fields. The different fields include an Ethernet header field, an internet protocol (IP) address header field, a UDP header field, a message passing protocol header field, and a message payload. The message handler at the access point then transmits the message over the computing network to a destination device, such as a network controller.
- Network controllers receive the messages including the network packets in a datapath of the network controller, and then provide the network packets to a control plane of the network controller. A message handler operating in the control plane of the network controller receives the network packet on a UDP socket, and then delivers the network packet by reading the network packet, writing data to the network packet to enable a recipient application identify the data packet, and forwarding the network packet to the destination application on an operating system socket (e.g., a UNIX kernel socket). Then, the application on the network controller reads the network packet from the operating system socket and processes the application-specific data in the network packet.
- In one embodiment, the approach of utilizing a message handler in the control plane of a network device, such as a network controller, is removed, in one embodiment, as discussed in greater detail below, processes running in the datapath (i.e., first processing layer) of the network controller translate one or more addressing fields of the network packet. After translating the network packet addressing fields in the datapath, a destination application operating in the control plane (i.e., second processing layer) monitors network packets on an operating system socket for packets addressed to the specific recipient application. When a network packet addressed to the application is detected by the application, the network packet may then simply be read and processed by the application. As a result, the consumption of processing resources consumed by the reading and writing of data to the network packets by a message handler in the control plane are avoided, which frees computing resources in the control plane for other purposes. Furthermore, bottlenecks caused by network packets being funneled into a message handier in the control plane are also avoided.
-
FIG. 1 is a block diagram of exemplary system architecture of acomputing network 100 in which the embodiment discussed herein may be deployed. System architecture illustrates anetwork 100 that includes a plurality of network devices, such ascontroller 106,router 102,network switch 104, wireless access point (AP) 108, andnetwork management server 110. Although only a single controller, router, network switch, wireless AP, and network management server are illustrated, thenetwork 100 illustrated by system architecture may include one or more of each of the different network devices consistent with the discussion herein. In one embodiment, thecontroller 106 supports devices such asrouter 102,network switch 104. wireless AP 108 to enable communication channels within thenetwork 100 that allow sharing of resources and information. In one embodiment,controller 106 provides networking across wireless and wired network connections, VPN connections, and remote services, and integrates networking and security functions into the network infrastructure and user experience. - The
network 100, as referred to and discussed herein, may run on one Local Area Network (LAN) and may be incorporated into the same physical or logical system, or different physical or logical systems. Alternatively,network 100 may reside on different LANs, wide area networks, etc. that may be coupled together via the internet but separated oy firewalls, routers, and/or other network devices. It should be noted that various other network configurations can be used including, for example, hosted configurations, distributed configurations, centralized configurations, etc. - The system architecture further includes one or more client computing devices 120-1 through 120-N coupled to the
network 100 vianetwork switch 104, and one or more client computing devices 125-1 through 125-N coupled to thenetwork 100 via wireless AP 108.Client computing devices 120 connect to thenetwork switch 104, andclient computing devices 125 connect to the wireless AP 108, to access services such as the Internet throughcontroller 106. - The system architecture further includes one or more network management servers, such as
network management server 110, coupled to thenetwork 100. In one embodiment,network management server 110 executes network management applications. Foe example,network management server 110 may provide manual or automated network management services to manage various aspects affecting the network, such as managing the radio frequency environment, controllers, wired infrastructure, and access points.Network management server 110 may further provide a user interface to network administrators to provide charts, tables, diagnostic information and alerts. - In one embodiment,
controller 106,router 102,network switch 104, wireless AP 108, andnetwork management server 110 are purpose-made digital devices, each containing a processor, memory hierarchy, and input-output interfaces. In one embodiment of the invention, a MIPS-class processor such as those from Cavium or RMI is used. Other suitable processors, such as those from Intel or AMD may also be used. The memory hierarchy traditionally comprises fast read/write memory for holding processor data and instructions while operating, and nonvolatile memory such as EEPROM and/or Flash for storing files and system startup information. Wired interfaces are typically IEEE 802-3 Ethernet interfaces, used for wired connections to other network devices such as switches, or to a controller. Wireless interfaces may be WiMAX, 3G, 4G, and/or IEEE 802.11 wireless interfaces. In one embodiment of the invention, controllers, switches, and wireless APs operate under control of a LINUX® operating system, with purpose-built programs providing controller and access point functionality. -
Client computing devices network switch 104 or wireless AP 108. Typical client computing devices include personal computers, handheld and tablet computers, Wi-Fi phones, wireless barcode scanners, and the like. -
FIG. 2 illustrates a general architecture of a network device, such ascontroller 106, which includes multiple processing planes according to embodiments of the present disclosure. Specifically,FIG. 2 illustrates acontroller 200 that includes at least acontrol plane process 210, two ormore datapath processors 220, anetwork interface 250. and one more applications, such asapplication 1 260 toapplication J 262.FIG. 2 further illustrates anaccess point 270 that includes at least anetwork interface 278, a message handier 276, and one or more applications, such asapplication 1 272 toapplication K 274. In one embodiment, thecontroller 200 and theaccess point 270 are communicatively coupled via a computing network (not shown). Furthermore, there may be more than ore access point connected tocontroller 200, as well as other controllers connected tocontroller 200. - In
controller 200,control plane process 210 may be running on one or more CPUs or CPU cores, such asCP CPU 1 212,CP CPU 2 214, . . .CP CPU M 218. Furthermore,control plane process 210 typically handles applications that perform network control or management of traffic generated by and/or terminated at network devices as opposed to data traffic generated and/or terminated at client devices. In one embodiment, thecontrol plane process 210 executesapplication 1 260 toapplication J 262. - According to embodiments of the present disclosure,
datapath processors 220 include a single slowpath (SP) processor (e.g., SP CPU 230) and multiple fastpath (FP) processors (e.g.,FP CPU 1 240,FP CPU 2 242, . . . FP CPU N 248). Only FP processors are able to receive data packets directly fromnetwork interface 250. SP processor, on the other hand, only receives data packets from FP processors. Also,control plane process 210 is communicatively coupled to slowpath (SP)CPU 230, but not fastpath (FP) processors (e.g.,FP CPU 1 240,FP CPU 2 242, . . . FP CPU N 248). Thus, whenevercontrol plane process 210 needs information fromdatapath processors 220,control plane process 210 will communicate with SP processor (e.g., SP CPU 230). - In one embodiment, an application executed at
access point 270 is in communication with an application executed atcontroller 200. The communication is in the form of the exchange of network packets that contain application-specific data generated by corresponding applications. For example,application K 274 ofaccess point 270 may generate data for receipt byapplication J 262 ofcontroller 200.Application K 274 provides the application-specific data tomessage handler 276 which encapsulates the data in a network packet suitable for transmission tocontroller 200. -
FIG. 3A illustrates one embodiment of anetwork packet 300. The network packet is generated by an application and includes at least header fields 310, UDP addressing data field 320, a message passing protocol addressingdata field 330, and a message payload 340. The header fields 310 contain standard fields, such as fields for an Ethernet header, an IP header, as well as other standard messaging fields (not illustrated). The UDP addressing data field 320 contains UDP source and UDP destination port addresses that enable thenetwork packet 300 to be routed between appropriate devices as specified by the UDP source port and the UDP destination port addresses. The message passing protocol addressingdata field 330 contains a message passing protocol source port addresses and a message passing protocol destination port address to enable the message payload within thenetwork packet 300 to be provided to the intended destination application. In the illustration ofFIG. 3A , thecontroller 200 addressing is specified asport 8211, the application ofaccess point 270 is identified bysource port 8224, and the destination application ofcontroller 200 is identified bydestination port 8222. The port addresses are illustrative, as other port addresses could be utilized. In one embodiment, a data packet as illustrated inFIG. 3A is transmitted fromnetwork interface 278 ofaccess point 270 over a computing network to networkinterface 250 ofcontroller 200. - In one embodiment, the received network packet is processed by at least one of FP processors. In one embodiment, the FP processors perform a process, which is discussed in greater detail below in
FIG. 4 , to translate addressing fields of the received network packet. In one embodiment, the message passing protocol port address infield 380, which identifies the port of the intended recipient application, replaces the UDP destination port address infield 370. The remaining header fields 360 and message payload 390, remain unchanged, except for the updated computation of a message checksum, which may be contained in theUDP addressing field 370. - As illustrated by the network packet of
FIG. 3B , the UDPdestination port address 370 is updated toport 8222. In one embodiment, the translated network packet, as illustrated inFIG. 3B , is provided to a kernel (not shown) that bridges thedatapath processors 220 and thecontrol plane process 210. The applications (e.g.,application 1 260 to application J 262) listen to the kernel for network packets with corresponding port addresses in the UDP destination port address. When an application detects a network packet with the appropriate addressing data, the application reads the network packet and consumes the application-specific data in message payload 390. - Because the applications of
controller 200 listen for their corresponding port addresses, a message handler application need not be run in the control plane for managing the routing of network packets to appropriate applications. As a result, processing resources are freed on the control plane forapplications 260 through 262, as well as other processes on the control plane. Furthermore, when an application oncontroller 200 transmits application data to an application onaccess point 270, the FP processors in thedatapath 220 perform a complementary network packet translation process that changes the source UDP port address to the destination UDP port address. In one embodiment, the source UDP port address is translated to the destination UDP port address so that both the source and destination UDP ports are addressed to the destination device message handler port, such asport 8211. -
FIG. 4 is a flow diagram of a method for translating a network packet according to embodiments of the present disclosure. Themethod 400 is performed by processing logic that may comprise hardware (circuitry, dedicated logic, etc.), software (such as is run on a general purpose computer system, networking device, or other dedicated machine), firmware, or a combination. In one embodiment, themethod 400 is performed by one ormore datapath processors 220 of anetwork controller 200. However, other network devices may perform the network packet translation in accordance with the techniques described herein. - In one embodiment, the process begins when a FP processor in a datapath of a network controller receives a message from an application (processing block 402). In one embodiment, the message is a UDP network packet. In one embodiment, processing logic receives the UDP network packet on a UDP socket, such as
port 8211 or port 8209. The application may be an application on a different network device, such as an access point, network server, bridge, router, etc. which has communicated the network packet to the network controller. As discussed above, the network packet may encapsulate application-specific data within the UDP network packet to be processes by a recipient application. - Processing logic translates the UDP destination port address field in the message to a destination port address located in a message passing protocol destination address field of the network packet (processing block 404). In one embodiment, processing logic utilizes the destination application port address to overwrite the UDP port address field value in a network packet.
- Processing logic then provides the translated message to a control plane of the network controller (processing block 406). In one embodiment, processing logic forwards a translated network packet to an operating system socket specified by the message passing protocol destination address field. By providing the network packet to the socket, the recipient application can detect when a network packet is available by monitoring the UDP destination port addresses. The intended destination application of the controller may then consume the application-specific data in the payload of the network packet.
- In one embodiment, the process performed at
processing block 406 may also include encapsulating the network packet into a transmission control protocol (TCP) session within the dataplane. Furthermore, in one embodiment, processing logic can further convert the network packet to one or more UDP packets. In this embodiment, the message passing protocol header data (i.e., the destination port address) is encapsulated into a TCP session identifier that can be utilized for tunneling the network packet(s) to the intended recipient application. In this embodiment, the network packet(s) would be further modified by adding internet protocol (IP) header data to the network packet(s) for the corresponding TCP session. Because the datapath manages the TCF session creation and packet transfer, a recipient application monitors for the converted UDP packets. -
FIG. 5 is a block diagram illustrating a network device according to embodiments of the present disclosure.Network device 500 includes at least anetwork interface 510 capable of communicating to a wired or wireless network, amemory 520 capable of storing data, aslowpath processor core 530 capable of processing network data packets, and one or more fastpath processor core,. includingfastpath processor core 542,fastpath processor core 544, . . . , fastpath processor core 548, which are capable of processing network data packets. Moreover,network device 500 may be used as a network switch, network router, network controller, network server, etc.Further network device 500 may serve as a node in a distributed or a cloud computing environment. -
Network interface 510 can be any communication interface, which includes but is not limited to, a modem, token ring interface. Ethernet interface, wireless IEEE 802.11 interface (e.g., IEEE802.11n, IEEE 802.11ac, etc.), cellular wireless interface, satellite transmission interface, or any other interface for coupling network devices. In someembodiments network interface 510 may be software-defined and programmable, for example, via an Application Programming Interface (API), and thus allowing for remote control of the network device 600. -
Memory 520 can include storage components, such as, Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), etc. In some embodiments,memory 520 is a flat structure that is shared by all datapath processors (including, e.g., slowpath processor core 530,fastpath processor core 542,fastpath processor core 544, . . . , fastpath processor core 548, etc.), and not tied to any particular CPU or CPU cores. Any datapath processor can read any memory location withinmemory 520.Memory 520 can be used to store various tables to assist software network packet forwarding. For example, the tables may include, but are not limited to, a bridge table, a session table, a user table, a station table, a tunnel table, a route table and/or route cache, etc. -
Slowpath processor core 530 typically includes a networking processor core that is capable of processing network data traffic.Slowpath processor core 530 is a single dedicated CPU core that typically handles table managements. Note that,slowpath processor core 530 only receives data packets from one or more fastpath processor cores, such asfastpath processor core 542,fastpath processor core 544, . . . , fastpath processor core 543. In other words,slowpath processor core 530 does not receive data packets directly from any tine cards or network interfaces. - Fastpath processor cores 542-548 also include networking processor cores that are capable of processing network data traffic. However, by definition, fastpath processor cores 542-548 only performs “fast” packet processing. Thus, fastpath processor cores 542-549 do not block themselves and wait for other components or modules during the processing of network packets. Any packets requiring special handling or wait by a processor core will be handed over by fastpath processor cores 542-548 to
slowpath processor core 530. - According to embodiments of the present disclosure, network services provided by
network device 500, solely or in combination with other wireless network devices, include, but are not limited to, an Institute of Electrical and Electronics Engineers (IEEE) 802.1x authentication to an internal and/or external Remote Authentication Dial-In User Service (RADIUS) server; an MAC authentication to an internal and/or external RADIUS server; a built-in Dynamic Host Configuration Protocol (DHCP) service to assign wireless client devices IP addresses; an internal secured management interface; Layer-3 forwarding; Network Address Translation (NAT) service between the wireless network and a wired network coupled to the network device; an internal and/or external captive portal; an external management system for managing the network devices in the wireless network; etc. - The present disclosure may be realized in hardware, software, or a combination of hardware and software. The present disclosure may be realized in a centralized fashion in one computer system or in a distributed fashion where different elements are spread across several interconnected computer systems coupled to a network. A typical combination of hardware and software may be an access point, a network controller, etc. with a computer program that, when being loaded and executed, controls the device such that it carries out the methods described herein.
- The present disclosure also may be embedded in non-transitory fashion in a computer-readable storage medium (e.g., a programmable circuit; a semiconductor memory such as a volatile memory such as random access memory “RAM,” or non-volatile memory such as read-only memory, power-backed RAM. flash memory, phase-change memory or the like; a hard disk drive; an optical disc drive; or any connector for receiving a portable memory device such as a Universal Serial Bus “USB” flash drive), which comprises alt the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
- As used herein, “digital device” generally includes a device that is adapted to transmit and/or receive signaling and to process information within such signaling such as a station (e.g., any data processing equipment such as a computer, cellular phone, personal digital assistant, tablet devices, etc.), an access point, data transfer devices (such as network switches, routers, controllers, etc.) or the like.
- As used herein, “access point” (AP) generally refers to receiving points for any known or convenient wireless access technology which may later become known. Specifically, the term AP is not intended to be limited to IEEE 802.11-based APs. APs generally function as an electronic device that is adapted to allow wireless devices to connect to a wired network via various communications standards.
- As used herein, the term “interconnect” or used descriptively as “interconnected” is generally defined as a communication pathway established over an information-carrying medium. The “interconnect” may be a wired interconnect, wherein the medium is a physical medium (e.g., electrical wire, optical fiber, cable, bus traces, etc.), a wireless interconnect (e.g., air in combination with wireless signaling technology) or a combination of these technologies.
- As used herein, “information” is generally defined as data, address, control, management (e.g., statistics) or any combination thereof. For transmission, information may be transmitted as a message, namely a collection of bits in a predetermined format. One type of message, namely a wireless message, includes a header and payload data having a predetermined number of bits of information. The wireless message may be placed in a format as one or more packets, frames or cells.
- As used herein, “wireless focal area network” (WLAN) generally refers to a communications network links two or more devices using some wireless distribution method (for example, spread-spectrum or orthogonal frequency-division multiplexing radio), and usually providing a connection through an access point to the Internet; and thus, providing users with the mobility to move around within a local coverage area and still stay connected to the network.
- As used herein, the term “mechanism” generally refers to a component of a system or device to serve one or more functions, including but not limited to, software components, electronic components, electrical components, mechanical components, electro-mechanical components, etc.
- As used herein, the tern “embodiment” generally refers an embodiment that serves to illustrate by way of example but not limitation.
- It will be appreciated to those skilled in the art that the preceding examples and embodiments are exemplary and not limiting to the scope of the present disclosure. It is intended that all permutations, enhancements, equivalents, and improvements thereto that are apparent to those skilled in the art upon a reading of the specification and a study of the drawings are included within the true spirit and scope of the present disclosure. It is therefore intended that the following appended claims include all such modifications, permutations and equivalents as fall within the true spirit and scope of the present disclosure.
- While the present disclosure has been described in terms of various embodiments, the present disclosure should not be limited to only those embodiments described, but can be practiced with modification and alteration within the spirit and scope of the appended claims. Likewise, where a reference to a standard is made in the present disclosure, the reference is generally made to the current version of the standard as applicable to the disclosed technology area. However, the described embodiments may be practiced under subsequent development of the standard within the spirit and scope of the description and appended claims. The description is thus to be regarded as illustrative rather than limiting.
Claims (20)
1. An article of manufacture having one or more non-transitory computer readable storage media storing executable instructions thereon which when executed cause a device to perform a method comprising:
receiving, at a first processing layer implemented by the device, a message addressed to a first port;
prior to forwarding the message to a second processing layer implemented by the device, the first processing layer modifying the message to be addressed to a second port indicated in a body of the message;
forwarding, by the first processing layer to the second processing layer, the modified message addressed to the second port.
2. The article of manufacture of claim 1 , wherein the first processing layer is a first operating system executing on the device and the second processing layer is a second operating system executing on the device.
3. The article of manufacture of claim 1 , wherein the first processing layer is a datapath implemented on the device and the second processing layer is a controlpath implemented on the device.
4. The article of manufacture of claim 1 , wherein the message is modified prior to the packet reaching a transmission control protocol/internet protocol (TCP/IP) stack implemented by the device.
5. The article of manufacture of claim 1 , wherein modifying further comprises:
modifying a user datagram protocol (UDP) header in the message.
6. The article of manufacture of claim 1 , wherein the first application in a user space to receive the message, and is an application associated with the second port.
7. The article of manufacture of claim 1 , wherein modifying further comprises:
converting the message to one or more UDP packets.
8. A system comprising:
a device including a hardware processor, the system being configured to
receive, at a first processing layer implemented by the device, a message addressed to a first port,
prior to forwarding the message to a second processing layer implemented by the device, the first processing layer to modify the message to be addressed to a second port indicated in a body of the message;
forward, by the first processing layer to the second processing layer, the modified message addressed to the second port.
9. The system of claim 8 , wherein the first processing layer is a first operating system executing on the device and the second processing layer is a second operating system executing on the device.
10. The system of claim 8 , wherein the first processing layer is a datapath implemented on the device and the second processing layer is a controlpath implemented on the device.
11. The system of claim 8 , wherein the message is modified prior to the packet reaching a transmission control protocol/internet protocol (TCP/IP) stack implemented by the device.
12. The system of claim 8 , wherein the system configured to modify the message further comprises the system configured lo modify a user datagram protocol (UDP) header in the message.
13. The system of claim 8 , wherein the first application in a user space to receive the message, and is an application associated with the second port.
14. The system of claim 8 , wherein the system configured to modify the message further comprises the system configured to convert the message to one or more UDP packets.
15. An article of manufacture having one or more non-transitory computer readable storage media storing executable instructions thereon which when executed cause one or more devices to perform a method comprising:
receiving, at a first processing layer implemented by a first device from a second processing layer implemented by the first device, a message indicating a first port as a source port;
prior to forwarding the message to a second device, modifying a source port indicated in the message;
forwarding, by the first processing layer, the modified message to the second device.
16. The article of manufacture of claim 15 , wherein the first processing layer is a datapath implemented on the first device and the second processing layer is a controlpath implemented on the first device.
17. The article of manufacture of claim 16 , wherein modifying further comprises: modifying a user datagram protocol (UDP) header in the message.
18. A system comprising:
at least one device including a hardware processor, the system being configured to
receive, at a first processing layer implemented by a first device from a second processing layer implemented by the first device, a message indicating a first port as a source port;
prior to forwarding the message to a second device, modify a source port indicated in the message;
forward, by the first processing layer, the modified message to the second device.
19. The system of claim 18 , wherein the first processing layer is a datapath implemented on the first device and the second processing layer is a controlpath implemented on the first device.
20. The system of claim 18 , wherein the system configured to modify a source port indicated in the message further comprises the system configured to modify a user datagram protocol (UDP) header in the message.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/384,074 US20190245809A1 (en) | 2012-12-03 | 2019-04-15 | System and method for message handling in a network device |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261732829P | 2012-12-03 | 2012-12-03 | |
US13/918,732 US10263916B2 (en) | 2012-12-03 | 2013-06-14 | System and method for message handling in a network device |
US16/384,074 US20190245809A1 (en) | 2012-12-03 | 2019-04-15 | System and method for message handling in a network device |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/918,732 Continuation US10263916B2 (en) | 2012-12-03 | 2013-06-14 | System and method for message handling in a network device |
Publications (1)
Publication Number | Publication Date |
---|---|
US20190245809A1 true US20190245809A1 (en) | 2019-08-08 |
Family
ID=50825368
Family Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/918,770 Active 2034-03-17 US9800503B2 (en) | 2012-12-03 | 2013-06-14 | Control plane protection for various tables using storm prevention entries |
US13/918,748 Abandoned US20140153577A1 (en) | 2012-12-03 | 2013-06-14 | Session-based forwarding |
US13/918,732 Active 2034-07-01 US10263916B2 (en) | 2012-12-03 | 2013-06-14 | System and method for message handling in a network device |
US13/918,760 Active 2033-12-01 US9467326B2 (en) | 2012-12-03 | 2013-06-14 | Rate limiting mechanism based on device load/capacity or traffic content |
US13/928,300 Active 2033-09-05 US9065701B2 (en) | 2012-12-03 | 2013-06-26 | Enhanced serialization mechanism |
US14/018,129 Active 2033-09-12 US9100242B2 (en) | 2012-12-03 | 2013-09-04 | System and method for maintaining captive portal user authentication |
US16/384,074 Abandoned US20190245809A1 (en) | 2012-12-03 | 2019-04-15 | System and method for message handling in a network device |
Family Applications Before (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/918,770 Active 2034-03-17 US9800503B2 (en) | 2012-12-03 | 2013-06-14 | Control plane protection for various tables using storm prevention entries |
US13/918,748 Abandoned US20140153577A1 (en) | 2012-12-03 | 2013-06-14 | Session-based forwarding |
US13/918,732 Active 2034-07-01 US10263916B2 (en) | 2012-12-03 | 2013-06-14 | System and method for message handling in a network device |
US13/918,760 Active 2033-12-01 US9467326B2 (en) | 2012-12-03 | 2013-06-14 | Rate limiting mechanism based on device load/capacity or traffic content |
US13/928,300 Active 2033-09-05 US9065701B2 (en) | 2012-12-03 | 2013-06-26 | Enhanced serialization mechanism |
US14/018,129 Active 2033-09-12 US9100242B2 (en) | 2012-12-03 | 2013-09-04 | System and method for maintaining captive portal user authentication |
Country Status (1)
Country | Link |
---|---|
US (7) | US9800503B2 (en) |
Families Citing this family (91)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9602404B2 (en) * | 2011-08-17 | 2017-03-21 | Nicira, Inc. | Last-hop processing for reverse direction packets |
US9203703B2 (en) * | 2011-08-17 | 2015-12-01 | Nicira, Inc. | Packet conflict resolution |
EP3373560B1 (en) | 2011-11-15 | 2022-08-10 | Nicira Inc. | Network control system for configuring middleboxes |
US9424159B2 (en) * | 2013-10-10 | 2016-08-23 | International Business Machines Corporation | Performance measurement of hardware accelerators |
EP2863597B1 (en) * | 2013-10-21 | 2016-01-06 | Accenture Global Services Limited | Computer-implemented method, computer system, computer program product to manage traffic in a network |
US10044612B2 (en) * | 2013-11-06 | 2018-08-07 | Citrix Systems, Inc. | Systems and methods for port allocation |
EP3072263B1 (en) * | 2013-11-18 | 2017-10-25 | Telefonaktiebolaget LM Ericsson (publ) | Multi-tenant isolation in a cloud environment using software defined networking |
US9480100B2 (en) * | 2014-01-15 | 2016-10-25 | Cisco Technology, Inc. | Wireless client device roaming among clustered access points |
US9973472B2 (en) | 2015-04-02 | 2018-05-15 | Varmour Networks, Inc. | Methods and systems for orchestrating physical and virtual switches to enforce security boundaries |
US10091238B2 (en) | 2014-02-11 | 2018-10-02 | Varmour Networks, Inc. | Deception using distributed threat detection |
US10264025B2 (en) | 2016-06-24 | 2019-04-16 | Varmour Networks, Inc. | Security policy generation for virtualization, bare-metal server, and cloud computing environments |
US9509603B2 (en) * | 2014-03-31 | 2016-11-29 | Arista Networks, Inc. | System and method for route health injection using virtual tunnel endpoints |
CN104980412B (en) | 2014-04-14 | 2018-07-13 | 阿里巴巴集团控股有限公司 | A kind of applications client, server-side and corresponding portal authentication method |
US9420607B1 (en) | 2014-05-28 | 2016-08-16 | Cisco Technology, Inc. | System and method for handling stray session requests in a network environment |
US10102019B2 (en) * | 2014-06-09 | 2018-10-16 | Verizon Patent And Licensing Inc. | Analyzing network traffic for layer-specific corrective actions in a cloud computing environment |
US9383989B1 (en) | 2014-06-16 | 2016-07-05 | Symantec Corporation | Systems and methods for updating applications |
US10021028B2 (en) * | 2014-06-16 | 2018-07-10 | International Business Machines Corporation | Controlling incoming traffic |
US9596164B1 (en) * | 2014-06-26 | 2017-03-14 | Juniper Networks, Inc. | Application visibility in layer 3 networks |
CN105900061B (en) | 2014-10-22 | 2018-01-16 | 华为技术有限公司 | Business method of flow control, controller and system in object storage system |
MX2017007253A (en) | 2014-12-05 | 2017-10-16 | Wal Mart Stores Inc | System and method for generating globally-unique identifiers. |
US9923814B2 (en) * | 2015-02-17 | 2018-03-20 | Huawei Technologies Co., Ltd. | Media access control address resolution using internet protocol addresses |
US10193929B2 (en) | 2015-03-13 | 2019-01-29 | Varmour Networks, Inc. | Methods and systems for improving analytics in distributed networks |
US9992223B2 (en) * | 2015-03-20 | 2018-06-05 | Nxp Usa, Inc. | Flow-based anti-replay checking |
US10078473B2 (en) * | 2015-03-23 | 2018-09-18 | Netapp, Inc. | Resource allocation in networked storage systems |
US10009381B2 (en) | 2015-03-30 | 2018-06-26 | Varmour Networks, Inc. | System and method for threat-driven security policy controls |
US9380027B1 (en) | 2015-03-30 | 2016-06-28 | Varmour Networks, Inc. | Conditional declarative policies |
US10797992B2 (en) | 2015-07-07 | 2020-10-06 | Cisco Technology, Inc. | Intelligent wide area network (IWAN) |
JP6332200B2 (en) * | 2015-08-26 | 2018-05-30 | 株式会社村田製作所 | Electronic components |
US10154062B2 (en) * | 2015-09-25 | 2018-12-11 | Nxp Usa, Inc. | Rule lookup using predictive tuples based rule lookup cache in the data plane |
JP2018536247A (en) * | 2015-09-28 | 2018-12-06 | ウォル−マート・ストアーズ・インコーポレイテッドWal−Mart Stores, Inc. | Cloud-based session management system |
US10594656B2 (en) * | 2015-11-17 | 2020-03-17 | Zscaler, Inc. | Multi-tenant cloud-based firewall systems and methods |
US10404778B2 (en) | 2015-12-09 | 2019-09-03 | Walmart Apollo, Llc | Session hand-off for mobile applications |
US10191758B2 (en) * | 2015-12-09 | 2019-01-29 | Varmour Networks, Inc. | Directing data traffic between intra-server virtual machines |
US10230633B2 (en) * | 2016-01-21 | 2019-03-12 | Red Hat, Inc. | Shared memory communication in software defined networking |
US10454897B1 (en) * | 2016-01-21 | 2019-10-22 | Amazon Technologies, Inc. | Proxy captive portal traffic for input-limited devices |
US9762599B2 (en) | 2016-01-29 | 2017-09-12 | Varmour Networks, Inc. | Multi-node affinity-based examination for computer network security remediation |
US9680852B1 (en) | 2016-01-29 | 2017-06-13 | Varmour Networks, Inc. | Recursive multi-layer examination for computer network security remediation |
US10348737B2 (en) * | 2016-03-08 | 2019-07-09 | International Business Machines Corporation | Login performance |
US9521115B1 (en) | 2016-03-24 | 2016-12-13 | Varmour Networks, Inc. | Security policy generation using container metadata |
US10601832B1 (en) | 2016-03-30 | 2020-03-24 | Amazon Technologies, Inc. | Proxy captive portal traffic for input-limited devices |
US10755334B2 (en) | 2016-06-30 | 2020-08-25 | Varmour Networks, Inc. | Systems and methods for continually scoring and segmenting open opportunities using client data and product predictors |
US10148576B2 (en) * | 2016-07-28 | 2018-12-04 | Fortinet, Inc. | Network processing unit (NPU) integrated layer 2 network device for layer 3 offloading |
WO2018038939A1 (en) | 2016-08-24 | 2018-03-01 | Viasat, Inc. | Device shaping in a communications network |
US10735954B2 (en) | 2016-09-02 | 2020-08-04 | Blackberry Limited | Method and device for facilitating authentication over a wireless network |
US10868737B2 (en) * | 2016-10-26 | 2020-12-15 | Arizona Board Of Regents On Behalf Of Arizona State University | Security policy analysis framework for distributed software defined networking (SDN) based cloud environments |
FR3059500A1 (en) * | 2016-11-29 | 2018-06-01 | Orange | LIGHTING AND OPTICAL COMMUNICATION DEVICE COMBINED WITH VISUALIZATION OF THE FIELD OF COMMUNICATION |
CN106714164B (en) * | 2016-12-09 | 2020-10-30 | 上海斐讯数据通信技术有限公司 | Acquisition method of resource file in Portal page, wireless AP and Portal server |
WO2018128528A1 (en) * | 2017-01-09 | 2018-07-12 | 엘지전자(주) | Method for managing pdu session in wireless communication system and apparatus therefor |
US10263859B2 (en) * | 2017-01-11 | 2019-04-16 | Sony Interactive Entertainment LLC | Delaying new session initiation in response to increased data traffic latency |
US10855616B2 (en) * | 2017-01-11 | 2020-12-01 | Sony Interactive Entertainment LLC | Predicting wait time for new session initiation during increased data traffic latency |
US10484263B2 (en) * | 2017-01-16 | 2019-11-19 | International Business Machines Corporation | Route-cost acquisition from routers |
US11405775B2 (en) * | 2017-04-28 | 2022-08-02 | Hewlett Packard Enterprise Development Lp | Three-address scheme for forwarding frames in a wireless mesh network |
US10834230B2 (en) | 2017-08-25 | 2020-11-10 | International Business Machines Corporation | Server request management |
US11593134B2 (en) * | 2018-01-26 | 2023-02-28 | Nicira, Inc. | Throttling CPU utilization by implementing a rate limiter |
GB2571576B (en) * | 2018-03-02 | 2022-06-15 | Ssh Communications Security Oyj | Processing packets in a computer system |
WO2019195086A1 (en) | 2018-04-03 | 2019-10-10 | Walmart Apollo, Llc | Customized service request permission control system |
US11063940B2 (en) * | 2018-04-27 | 2021-07-13 | Hewlett Packard Enterprise Development Lp | Switch authentication |
US10644970B2 (en) | 2018-07-11 | 2020-05-05 | Sony Interactive Entertainment LLC | Tracking application utilization of microservices |
US11329966B2 (en) | 2018-08-15 | 2022-05-10 | Juniper Networks, Inc. | System and method for transferring packets between kernel modules in different network stacks |
US11233778B2 (en) * | 2018-08-15 | 2022-01-25 | Juniper Networks, Inc. | Secure forwarding of tenant workloads in virtual networks |
US10942791B2 (en) * | 2018-09-17 | 2021-03-09 | Oracle International Corporation | Managing load in request processing environments |
EP3627343A1 (en) * | 2018-09-19 | 2020-03-25 | censhare AG | Efficient in-memory multi-version concurrency control for a trie data structure based database |
CN109347623B (en) * | 2018-10-18 | 2022-09-09 | 苏州盛科通信股份有限公司 | Method and device for session maintenance in link load balancing application |
CN111131044B (en) * | 2018-10-30 | 2021-10-22 | 华为技术有限公司 | Route management method and device |
CN109361714B (en) * | 2018-12-18 | 2021-11-16 | 中国移动通信集团江苏有限公司 | User login authentication method, device, equipment and computer storage medium |
US10880208B1 (en) | 2019-02-11 | 2020-12-29 | Google Llc | Offloads for multicast virtual network packet processing in a network interface card |
US11171961B2 (en) | 2019-05-09 | 2021-11-09 | Cisco Technology, Inc. | Secure captive portal remediation |
EP3977691A1 (en) * | 2019-05-30 | 2022-04-06 | Nokia Solutions and Networks Oy | Activation of pdu session and qos flows in 3gpp-based ethernet bridges |
US11863580B2 (en) | 2019-05-31 | 2024-01-02 | Varmour Networks, Inc. | Modeling application dependencies to identify operational risk |
US11711374B2 (en) | 2019-05-31 | 2023-07-25 | Varmour Networks, Inc. | Systems and methods for understanding identity and organizational access to applications within an enterprise environment |
US11290494B2 (en) | 2019-05-31 | 2022-03-29 | Varmour Networks, Inc. | Reliability prediction for cloud security policies |
US11290493B2 (en) | 2019-05-31 | 2022-03-29 | Varmour Networks, Inc. | Template-driven intent-based security |
US11575563B2 (en) | 2019-05-31 | 2023-02-07 | Varmour Networks, Inc. | Cloud security management |
US11310284B2 (en) | 2019-05-31 | 2022-04-19 | Varmour Networks, Inc. | Validation of cloud security policies |
US10922024B1 (en) * | 2019-06-28 | 2021-02-16 | Amazon Technologies, Inc. | Self-protection against serialization incompatibilities |
EP3771234B1 (en) * | 2019-07-18 | 2024-02-28 | neXenio GmbH | Method for broadcasting data |
US20220247719A1 (en) * | 2019-09-24 | 2022-08-04 | Pribit Technology, Inc. | Network Access Control System And Method Therefor |
US11483246B2 (en) | 2020-01-13 | 2022-10-25 | Vmware, Inc. | Tenant-specific quality of service |
CN111277518B (en) * | 2020-01-22 | 2022-04-01 | 苏州盛科通信股份有限公司 | Information processing method, Ethernet switching chip and storage medium |
US11599395B2 (en) | 2020-02-19 | 2023-03-07 | Vmware, Inc. | Dynamic core allocation |
US11539633B2 (en) * | 2020-08-31 | 2022-12-27 | Vmware, Inc. | Determining whether to rate limit traffic |
US11252084B1 (en) * | 2020-09-29 | 2022-02-15 | Palo Alto Networks, Inc. | Enhanced SD-WAN path quality measurement and selection |
CN112351250B (en) * | 2020-10-21 | 2023-05-26 | 杭州海康威视数字技术股份有限公司 | Coding parameter adjustment method, device and equipment and storage medium |
US11818152B2 (en) | 2020-12-23 | 2023-11-14 | Varmour Networks, Inc. | Modeling topic-based message-oriented middleware within a security system |
US11876817B2 (en) | 2020-12-23 | 2024-01-16 | Varmour Networks, Inc. | Modeling queue-based message-oriented middleware relationships in a security system |
US11777978B2 (en) | 2021-01-29 | 2023-10-03 | Varmour Networks, Inc. | Methods and systems for accurately assessing application access risk |
US11677717B2 (en) * | 2021-03-22 | 2023-06-13 | Cloudflare, Inc. | Unified network service that connects multiple disparate private networks and end user client devices operating on separate networks |
US11799784B2 (en) | 2021-06-08 | 2023-10-24 | Vmware, Inc. | Virtualized QoS support in software defined networks |
CN113422722B (en) * | 2021-06-16 | 2023-10-24 | 锐捷网络股份有限公司 | Routing processing method and device |
US11841871B2 (en) | 2021-06-29 | 2023-12-12 | International Business Machines Corporation | Managing extract, transform and load systems |
US11734316B2 (en) | 2021-07-08 | 2023-08-22 | Varmour Networks, Inc. | Relationship-based search in a computing environment |
Family Cites Families (91)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5400325A (en) * | 1993-06-29 | 1995-03-21 | Synoptics Communications, Inc. | Method and apparatus providing for hunt groups in an ATM network of the like |
JP2995496B2 (en) * | 1995-06-19 | 1999-12-27 | インターナシヨナル・ビジネス・マシーンズ・コーポレーシヨン | Method and system for receiving data packets in a unidirectional broadcast system |
JPH10154995A (en) * | 1996-11-20 | 1998-06-09 | Fujitsu Ltd | Gateway system and method for relaying packet |
US6118760A (en) | 1997-06-30 | 2000-09-12 | Sun Microsystems, Inc. | Management of entries in a network element forwarding memory |
US5920566A (en) * | 1997-06-30 | 1999-07-06 | Sun Microsystems, Inc. | Routing in a multi-layer distributed network element |
US6167450A (en) * | 1997-07-30 | 2000-12-26 | International Business Machines Corporation | Data communications management system and protocol replacement method for mobile communication environments |
US6098172A (en) * | 1997-09-12 | 2000-08-01 | Lucent Technologies Inc. | Methods and apparatus for a computer network firewall with proxy reflection |
US6158008A (en) | 1997-10-23 | 2000-12-05 | At&T Wireless Svcs. Inc. | Method and apparatus for updating address lists for a packet filter processor |
US6118765A (en) | 1998-01-13 | 2000-09-12 | Qualcomm Inc. | System method and computer program product for eliminating unnecessary retransmissions |
US6195688B1 (en) * | 1998-05-07 | 2001-02-27 | International Business Machines Corporation | Computer system, program product and method of communicating internetworking data over a master-slave communication link |
US6212195B1 (en) * | 1998-12-01 | 2001-04-03 | 3Com Corporation | Telecommunication apparatus and method for forwarding packets using separate collision domains |
US6535511B1 (en) * | 1999-01-07 | 2003-03-18 | Cisco Technology, Inc. | Method and system for identifying embedded addressing information in a packet for translation between disparate addressing systems |
US8321457B2 (en) | 2000-09-08 | 2012-11-27 | Oracle International Corporation | Techniques for automatically developing a web site |
US6651096B1 (en) | 1999-04-20 | 2003-11-18 | Cisco Technology, Inc. | Method and apparatus for organizing, storing and evaluating access control lists |
US6606316B1 (en) * | 1999-07-02 | 2003-08-12 | Cisco Technology, Inc. | Gathering network statistics in a distributed network service environment |
US6728265B1 (en) | 1999-07-30 | 2004-04-27 | Intel Corporation | Controlling frame transmission |
US20110258444A1 (en) | 1999-07-30 | 2011-10-20 | Intel Corporation | Network Controller Decryption |
JP3449326B2 (en) | 1999-12-08 | 2003-09-22 | 日本電気株式会社 | Data search system, packet processing apparatus, and control method |
US7120683B2 (en) | 2000-04-03 | 2006-10-10 | Zarlink Semiconductor V.N. Inc. | Single switch image for a stack of switches |
US20040213237A1 (en) * | 2000-06-29 | 2004-10-28 | Toshikazu Yasue | Network authentication apparatus and network authentication system |
US20020042875A1 (en) * | 2000-10-11 | 2002-04-11 | Jayant Shukla | Method and apparatus for end-to-end secure data communication |
US7031314B2 (en) * | 2001-05-16 | 2006-04-18 | Bytemobile, Inc. | Systems and methods for providing differentiated services within a network communication system |
US7117504B2 (en) | 2001-07-10 | 2006-10-03 | Microsoft Corporation | Application program interface that enables communication for a network software platform |
US6968389B1 (en) * | 2001-07-17 | 2005-11-22 | Cisco Technology, Inc. | System and method for qualifying requests in a network |
JP3990882B2 (en) | 2001-07-25 | 2007-10-17 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile packet communication system, mobile packet communication method, and radio control apparatus |
US20120027008A1 (en) * | 2001-10-12 | 2012-02-02 | Spice I2I Limited | Addressing Techniques For Voice Over Internet Protocol Router |
US7006436B1 (en) * | 2001-11-13 | 2006-02-28 | At&T Corp. | Method for providing voice-over-IP service |
KR100411446B1 (en) | 2001-12-24 | 2003-12-18 | 엘지전자 주식회사 | Method of Controlling Type 3 Packet in the AAL2 Signaling |
JP3878014B2 (en) * | 2001-12-28 | 2007-02-07 | 富士通株式会社 | Packet switch for interfacing LAN and WAN |
US6985479B2 (en) * | 2002-03-04 | 2006-01-10 | Qualcomm Incorporated | Method and apparatus for processing internet protocol transmissions |
CA2390348A1 (en) | 2002-06-10 | 2003-12-10 | Ibm Canada Limited-Ibm Canada Limitee | Systems, methods and computer programs for implementing and accessing webservices |
US7716725B2 (en) * | 2002-09-20 | 2010-05-11 | Fortinet, Inc. | Firewall interface configuration and processes to enable bi-directional VoIP traversal communications |
US7483980B2 (en) * | 2002-11-07 | 2009-01-27 | Hewlett-Packard Development Company, L.P. | Method and system for managing connections in a computer network |
US7701863B2 (en) * | 2002-12-12 | 2010-04-20 | Alcatel Lucent | Decentralized SLS monitoring for throughput in a differentiated service environment |
US20040125812A1 (en) * | 2002-12-25 | 2004-07-01 | Meng-Hua Kao | Adapter for internetworking wwan and wlan |
US20040170181A1 (en) | 2003-02-27 | 2004-09-02 | Padcom, Inc. | Prioritized alternate port routing |
US7245622B2 (en) * | 2003-03-27 | 2007-07-17 | Microsoft Corporation | Allowing IPv4 clients to communicate over an IPv6 network when behind a network address translator with reduced server workload |
US6985150B2 (en) | 2003-03-31 | 2006-01-10 | Sun Microsystems, Inc. | Accelerator control unit configured to manage multiple hardware contexts |
US7814310B2 (en) | 2003-04-12 | 2010-10-12 | Cavium Networks | IPsec performance optimization |
US7913294B1 (en) | 2003-06-24 | 2011-03-22 | Nvidia Corporation | Network protocol processing for filtering packets |
US7342916B2 (en) * | 2003-09-10 | 2008-03-11 | Intel Corporation | Method, apparatus and system for optimizing routing of mobile IP packets |
US20050105524A1 (en) * | 2003-11-17 | 2005-05-19 | Hughes Electronics Corporation | System and method for provisioning of route information in a meshed communications network |
TWI235572B (en) * | 2003-12-19 | 2005-07-01 | Inst Information Industry | Method of IPsec packet routing, NAPT device and storage medium using the same |
US20050193429A1 (en) * | 2004-01-23 | 2005-09-01 | The Barrier Group | Integrated data traffic monitoring system |
US8250150B2 (en) * | 2004-01-26 | 2012-08-21 | Forte Internet Software, Inc. | Methods and apparatus for identifying and facilitating a social interaction structure over a data packet network |
US20050201391A1 (en) * | 2004-03-11 | 2005-09-15 | Hung-Fang Ma | Network address translation router and related method |
US7474634B1 (en) * | 2004-03-12 | 2009-01-06 | West Corporation | System, methods, and computer-readable media for expedited access to conference calls |
US8176126B2 (en) | 2004-08-26 | 2012-05-08 | International Business Machines Corporation | System, method and program to limit rate of transferring messages from suspected spammers |
US20060069782A1 (en) | 2004-09-16 | 2006-03-30 | Michael Manning | Method and apparatus for location-based white lists in a telecommunications network |
US7624263B1 (en) | 2004-09-21 | 2009-11-24 | Advanced Micro Devices, Inc. | Security association table lookup architecture and method of operation |
ATE446635T1 (en) | 2004-12-03 | 2009-11-15 | Ericsson Telefon Ab L M | TECHNOLOGY FOR CONNECTING INTERMEDIATE NETWORK NODES |
JP4655903B2 (en) * | 2004-12-08 | 2011-03-23 | 株式会社日立製作所 | Packet transfer device |
US8787393B2 (en) * | 2005-04-11 | 2014-07-22 | International Business Machines Corporation | Preventing duplicate sources from clients served by a network address port translator |
KR20060117586A (en) * | 2005-05-11 | 2006-11-17 | 삼성전자주식회사 | Apparatus and method of packet processing in ipv4/ipv6 combination network |
US7313134B2 (en) * | 2005-05-12 | 2007-12-25 | Yahoo! Inc. | Proxy server for relaying VOIP messages |
US7505434B1 (en) | 2005-06-23 | 2009-03-17 | Autocell Laboratories, Inc. | VLAN tagging in WLANs |
US20060294588A1 (en) * | 2005-06-24 | 2006-12-28 | International Business Machines Corporation | System, method and program for identifying and preventing malicious intrusions |
US7808985B2 (en) * | 2006-11-21 | 2010-10-05 | Gigle Networks Sl | Network repeater |
US7619993B2 (en) * | 2005-11-01 | 2009-11-17 | International Business Machines Corporation | Efficient probabilistic duplicate packet detector in computer networks |
US9021134B1 (en) * | 2006-03-03 | 2015-04-28 | Juniper Networks, Inc. | Media stream transport conversion within an intermediate network device |
US7743094B2 (en) * | 2006-03-07 | 2010-06-22 | Motorola, Inc. | Method and apparatus for redirection of domain name service (DNS) packets |
US20070214265A1 (en) | 2006-03-07 | 2007-09-13 | Sbc Knowledge Ventures Lp | Scalable captive portal redirect |
GB0623101D0 (en) * | 2006-11-20 | 2006-12-27 | British Telecomm | Secure network architecture |
US8056115B2 (en) * | 2006-12-11 | 2011-11-08 | International Business Machines Corporation | System, method and program product for identifying network-attack profiles and blocking network intrusions |
JP4995590B2 (en) | 2007-02-14 | 2012-08-08 | 株式会社エヌ・ティ・ティ・ドコモ | Content distribution management device, communication terminal, program, and content distribution system |
US7864771B2 (en) | 2007-04-20 | 2011-01-04 | Cisco Technology, Inc. | Parsing out of order data packets at a content gateway of a network |
CN101689158B (en) | 2007-07-09 | 2012-06-06 | 惠普发展公司,有限责任合伙企业 | Data packet processing method for a multi core processor |
TW200931918A (en) | 2007-12-07 | 2009-07-16 | Interdigital Patent Holdings | Method and apparatus for supporting configuration and control of the RLC and PDCP sub-layers |
US8010522B2 (en) * | 2007-12-07 | 2011-08-30 | International Business Machines Corporation | System, method and program product for detecting SQL queries injected into data fields of requests made to applications |
DE102008020205B4 (en) | 2008-04-22 | 2010-01-07 | Schenck Rotec Gmbh | Filling bell for filling a tubeless tire |
US8544080B2 (en) * | 2008-06-12 | 2013-09-24 | Telefonaktiebolaget L M Ericsson (Publ) | Mobile virtual private networks |
US8055286B1 (en) * | 2008-08-27 | 2011-11-08 | Sprint Spectrum L.P. | Modification of en-route message to add destination port number selected based at least in part on message originator |
JP5632380B2 (en) | 2008-10-13 | 2014-11-26 | デバイススケープ・ソフトウェア・インコーポレーテッド | System and method for identifying a network |
US20100263022A1 (en) | 2008-10-13 | 2010-10-14 | Devicescape Software, Inc. | Systems and Methods for Enhanced Smartclient Support |
EP2273736B1 (en) | 2009-06-29 | 2011-09-21 | Alcatel Lucent | Method of managing a traffic load |
US20110023088A1 (en) * | 2009-07-23 | 2011-01-27 | Electronics And Telecommunications Research Institute | Flow-based dynamic access control system and method |
US8238244B2 (en) | 2009-08-10 | 2012-08-07 | Micron Technology, Inc. | Packet deconstruction/reconstruction and link-control |
JP5541293B2 (en) | 2009-12-03 | 2014-07-09 | 日本電気株式会社 | Packet receiving apparatus, packet communication system, and packet order control method |
US9137139B2 (en) | 2009-12-18 | 2015-09-15 | Cisco Technology, Inc. | Sender-specific counter-based anti-replay for multicast traffic |
US8452835B2 (en) | 2009-12-23 | 2013-05-28 | Citrix Systems, Inc. | Systems and methods for object rate limiting in multi-core system |
KR101670253B1 (en) * | 2010-02-16 | 2016-10-31 | 삼성전자 주식회사 | Method and device for controlling network access of ue in wireless communication system |
US8625458B2 (en) | 2010-05-26 | 2014-01-07 | Alcatel Lucent | Dynamic route cost adjustment of VRRP enabled subnets for routing protocols |
CN103621022B (en) | 2010-09-03 | 2016-11-02 | 华为技术有限公司 | For Virtual Private LAN Service to use influenza to know the system and method for pseudo-wire |
US20120281530A1 (en) * | 2010-11-08 | 2012-11-08 | Qualcomm Incorporated | System and method for radio access network overload control |
JP5630306B2 (en) * | 2011-02-10 | 2014-11-26 | 富士通株式会社 | Route generation method, relay device, and route generation program |
US8806573B2 (en) | 2011-08-09 | 2014-08-12 | Cisco Technology, Inc. | Authentication control in low-power lossy networks |
US20140010140A1 (en) | 2011-09-12 | 2014-01-09 | Intel Corporation | Group media access control message for machine-to-machine devices and method to update a group identifier |
US8767730B2 (en) * | 2012-02-10 | 2014-07-01 | Futurewei Technologies, Inc. | Virtual local area network identifier substitution as time to live method |
US9148343B2 (en) | 2012-03-27 | 2015-09-29 | Juniper Networks, Inc. | Methods and apparatus for improving compatibility between network devices |
US9071541B2 (en) * | 2012-04-25 | 2015-06-30 | Juniper Networks, Inc. | Path weighted equal-cost multipath |
US9258213B2 (en) * | 2012-05-30 | 2016-02-09 | Cisco Technology, Inc. | Detecting and mitigating forwarding loops in stateful network devices |
-
2013
- 2013-06-14 US US13/918,770 patent/US9800503B2/en active Active
- 2013-06-14 US US13/918,748 patent/US20140153577A1/en not_active Abandoned
- 2013-06-14 US US13/918,732 patent/US10263916B2/en active Active
- 2013-06-14 US US13/918,760 patent/US9467326B2/en active Active
- 2013-06-26 US US13/928,300 patent/US9065701B2/en active Active
- 2013-09-04 US US14/018,129 patent/US9100242B2/en active Active
-
2019
- 2019-04-15 US US16/384,074 patent/US20190245809A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
US20140156720A1 (en) | 2014-06-05 |
US9065701B2 (en) | 2015-06-23 |
US20140157376A1 (en) | 2014-06-05 |
US9467326B2 (en) | 2016-10-11 |
US20140153422A1 (en) | 2014-06-05 |
US9100242B2 (en) | 2015-08-04 |
US10263916B2 (en) | 2019-04-16 |
US9800503B2 (en) | 2017-10-24 |
US20140157365A1 (en) | 2014-06-05 |
US20140153577A1 (en) | 2014-06-05 |
US20140156765A1 (en) | 2014-06-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20190245809A1 (en) | System and method for message handling in a network device | |
US20180288179A1 (en) | Proxy for serving internet-of-things (iot) devices | |
JP6463839B2 (en) | System and method for flow-based addressing in a mobile environment | |
US8953621B2 (en) | Specifying priority on a virtual station interface discovery and configuration protocol response | |
US9264972B2 (en) | Home networking with integrated cellular communication | |
US11172054B2 (en) | Cross-device segmentation offload | |
WO2020019159A1 (en) | Method, device and computer readable medium for delivering data-plane packets by using separate transport service vnfc | |
US9455959B1 (en) | Method of connecting security gateway to mesh network | |
US9438555B2 (en) | Communicating with a distribution system via an uplink access point | |
WO2016062169A1 (en) | Message transmission method and apparatus | |
CN110505244B (en) | Remote tunnel access technology gateway and server | |
JP2023523048A (en) | Packet processing method and related device | |
CN111480320A (en) | Wireless mesh access point with user space tunnel | |
CN110768884B (en) | VXLAN message encapsulation and policy execution method, equipment and system | |
CN107733930B (en) | Method and system for forwarding Internet Protocol (IP) packets at multiple WAN network gateways | |
US20140056301A1 (en) | Network communication system, device, and method for reducing a network addressing header | |
US9015438B2 (en) | System and method for achieving enhanced performance with multiple networking central processing unit (CPU) cores | |
US20190036735A1 (en) | Data transmission | |
Cong et al. | Ceupf: Offloading 5g user plane function to programmable hardware base on co-existence architecture | |
WO2021121550A1 (en) | Methods and apparatus for multihoming sctp communication between a network entity and a remote host | |
US10320661B2 (en) | Communication device and communication method | |
CN113497767A (en) | Method and device for transmitting data, computing equipment and storage medium | |
US8811344B1 (en) | Methods and apparatus for assigning same sequence number to multiple GTP messages | |
WO2023078144A1 (en) | Message processing method, apparatus and system | |
US11706644B2 (en) | Access points with virtual clients |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |