H04L69/22

Systems and methods for managing streams of packets via intermediary devices

Virtual application and desktop delivery may be optimized by supplying application metadata and user intent to the device between a client and a server hosting resources for the delivery. The data packets used to deliver the virtual application or desktop may be also tagged with references to the application. By supplying the metadata and tagging packets with the metadata, an intermediary network device may provide streams of data packets at the target QoS. In addition, the device may apply network resource allocation rules (e.g., firewalls and QoS configuration) for redirected content retrieved by the client out of band relative to a virtual channel such as the Internet. The network resource allocation rules may differ for different types of resources accessed. The device may also control a delivery agent on the server to modify communication sessions established through the virtual channels based on network conditions.

Systems and methods for managing streams of packets via intermediary devices

Virtual application and desktop delivery may be optimized by supplying application metadata and user intent to the device between a client and a server hosting resources for the delivery. The data packets used to deliver the virtual application or desktop may be also tagged with references to the application. By supplying the metadata and tagging packets with the metadata, an intermediary network device may provide streams of data packets at the target QoS. In addition, the device may apply network resource allocation rules (e.g., firewalls and QoS configuration) for redirected content retrieved by the client out of band relative to a virtual channel such as the Internet. The network resource allocation rules may differ for different types of resources accessed. The device may also control a delivery agent on the server to modify communication sessions established through the virtual channels based on network conditions.

Implementing multi-table OpenFlow using a parallel hardware table lookup architecture

Techniques for implementing multi-table OpenFlow using a parallel hardware table lookup architecture are provided. In certain embodiments, these techniques include receiving, at a network device from a software-defined networking (SDN) controller, flow entries for installation into flow tables of the network device, where the flow entries are structured in a manner that assumes the flow tables can be looked-up serially by a packet processor of the network device, but where the flow tables are implemented using hardware lookup tables (e.g., TCAMs) that can only be looked-up in parallel by the packet processor. The techniques further include converting, by the network device, the received flow entries into a format that enables the packet processor to process ingress network traffic correctly using the flow entries, despite the packet processor's parallel lookup architecture, and installing the converted flow entries into the flow tables/hardware lookup tables.

Implementing multi-table OpenFlow using a parallel hardware table lookup architecture

Techniques for implementing multi-table OpenFlow using a parallel hardware table lookup architecture are provided. In certain embodiments, these techniques include receiving, at a network device from a software-defined networking (SDN) controller, flow entries for installation into flow tables of the network device, where the flow entries are structured in a manner that assumes the flow tables can be looked-up serially by a packet processor of the network device, but where the flow tables are implemented using hardware lookup tables (e.g., TCAMs) that can only be looked-up in parallel by the packet processor. The techniques further include converting, by the network device, the received flow entries into a format that enables the packet processor to process ingress network traffic correctly using the flow entries, despite the packet processor's parallel lookup architecture, and installing the converted flow entries into the flow tables/hardware lookup tables.

Distinguishing between quality of service management frames (QMFS) and non-QMFS in protocol version 1 (PV1)

A method by a wireless transmitting device for distinguishing between a quality of service (QoS) management frame and a non-QoS management frame is described. The method includes generating a frame that includes a frame header, wherein the frame header includes a frame control field, wherein the frame control field includes a partial traffic identifier or subtype (PTID/subtype) subfield, wherein the PTID/subtype subfield indicates whether the frame is a quality of service (QoS) management frame or a non-QoS management frame and transmitting the frame through a wireless medium.

Distinguishing between quality of service management frames (QMFS) and non-QMFS in protocol version 1 (PV1)

A method by a wireless transmitting device for distinguishing between a quality of service (QoS) management frame and a non-QoS management frame is described. The method includes generating a frame that includes a frame header, wherein the frame header includes a frame control field, wherein the frame control field includes a partial traffic identifier or subtype (PTID/subtype) subfield, wherein the PTID/subtype subfield indicates whether the frame is a quality of service (QoS) management frame or a non-QoS management frame and transmitting the frame through a wireless medium.

MESSAGING BETWEEN REMOTE CONTROLLER AND FORWARDING ELEMENT

Some embodiments of the invention provide a forwarding element that can be configured through in-band data-plane messages from a remote controller that is a physically separate machine from the forwarding element. The forwarding element of some embodiments has data plane circuits that include several configurable message-processing stages, several storage queues, and a data-plane configurator. A set of one or more message-processing stages of the data plane are configured (1) to process configuration messages received by the data plane from the remote controller and (2) to store the configuration messages in a set of one or more storage queues. The data-plane configurator receives the configuration messages stored in the set of storage queues and configures one or more of the configurable message-processing stages based on configuration data in the configuration messages.

MESSAGING BETWEEN REMOTE CONTROLLER AND FORWARDING ELEMENT

Some embodiments of the invention provide a forwarding element that can be configured through in-band data-plane messages from a remote controller that is a physically separate machine from the forwarding element. The forwarding element of some embodiments has data plane circuits that include several configurable message-processing stages, several storage queues, and a data-plane configurator. A set of one or more message-processing stages of the data plane are configured (1) to process configuration messages received by the data plane from the remote controller and (2) to store the configuration messages in a set of one or more storage queues. The data-plane configurator receives the configuration messages stored in the set of storage queues and configures one or more of the configurable message-processing stages based on configuration data in the configuration messages.

METHOD OF REPORTING RECEIVED SIGNAL STRENGTH ON PER FRAME BASIS IN WI-FI NETWORK
20230106424 · 2023-04-06 ·

Aspects of the present disclosure are drawn to a client device for use with an access point device. The client device includes: a memory; and a processor configured to execute instructions stored on the memory to cause the client device to: obtain a value associated with a capability of the client device, create a response including a header and a payload, the header including a reserved field including a bit reporting that the payload of the response includes the value associated with the capability, and transmit the response to the APD.

METHOD OF REPORTING RECEIVED SIGNAL STRENGTH ON PER FRAME BASIS IN WI-FI NETWORK
20230106424 · 2023-04-06 ·

Aspects of the present disclosure are drawn to a client device for use with an access point device. The client device includes: a memory; and a processor configured to execute instructions stored on the memory to cause the client device to: obtain a value associated with a capability of the client device, create a response including a header and a payload, the header including a reserved field including a bit reporting that the payload of the response includes the value associated with the capability, and transmit the response to the APD.