Patent classifications
H04L69/22
Delayed Preamble Detection for Bluetooth Receiver based on Interferer Metric
The present invention relates to a method and apparatus for reducing power consumption in a receiver of a time slotted communication system. An RF front end has power applied after the start of a preamble or after the start of a header, or upon the start of a packet payload based on connection status, signal level, and interference level. Where the signal level is constant, the communication system is in a connected state, and the interference level is low, the system bypasses packet header destination address matching, or optionally, uses only the least significant bits of the header destination address for matching purposes.
Delayed Preamble Detection for Bluetooth Receiver based on Interferer Metric
The present invention relates to a method and apparatus for reducing power consumption in a receiver of a time slotted communication system. An RF front end has power applied after the start of a preamble or after the start of a header, or upon the start of a packet payload based on connection status, signal level, and interference level. Where the signal level is constant, the communication system is in a connected state, and the interference level is low, the system bypasses packet header destination address matching, or optionally, uses only the least significant bits of the header destination address for matching purposes.
FRAME COMPATIBILITY ACROSS NETWORK PROTOCOL VERSION
One embodiment of the present invention sets forth a technique for processing packets transmitted within a network in accordance with a network protocol. The technique includes a network device in a mesh network receiving a type-length-value (TLV) element, determining, based on a type field of the TLV element, an expected length of a value field of the TLV element, and processing the value field up to the expected length.
FRAME COMPATIBILITY ACROSS NETWORK PROTOCOL VERSION
One embodiment of the present invention sets forth a technique for processing packets transmitted within a network in accordance with a network protocol. The technique includes a network device in a mesh network receiving a type-length-value (TLV) element, determining, based on a type field of the TLV element, an expected length of a value field of the TLV element, and processing the value field up to the expected length.
Network security system using statistical object identification
Apparatus to enforce network policy based on identity authentication at a network endpoint device by offloading the authentication to a network attached authentication devices is disclosed. The authentication device may use Statistical Object Identification to perform the authentication. The present disclosure greatly reduces the resources needed by the network endpoint device to perform the authentication and eliminates the topological restrictions found in traditional network appliance based approaches.
Network security system using statistical object identification
Apparatus to enforce network policy based on identity authentication at a network endpoint device by offloading the authentication to a network attached authentication devices is disclosed. The authentication device may use Statistical Object Identification to perform the authentication. The present disclosure greatly reduces the resources needed by the network endpoint device to perform the authentication and eliminates the topological restrictions found in traditional network appliance based approaches.
SECURE PRIVATE TRAFFIC EXCHANGE IN A UNIFIED NETWORK SERVICE
Traffic is received at an interface of a compute server. Identity information associated with the traffic is determined including an identifier of a customer to which the traffic is attributable. An egress policy configured for the first customer is used to determine whether the traffic is allowed to be transmitted to a destination where that destination is a resource of a second customer. If the traffic is allowed to be transmitted, the traffic and identity information is transmitted over a cross-customer GRE tunnel to a namespace of the second costumer on the compute server. An ingress policy configured for the second customer is used to determine whether the traffic is allowed to be transmitted to the destination, and if it is, then the traffic is transmitted.
Processing segment routing packets with two policy processing instructions in a segment routing domain
A network device may receive a packet and may determine whether a next header of the packet is an Internet protocol (IP) header, an Internet control message protocol (ICMP) header, or a segment routing header. The network device may determine, when the next header of the packet is the IP header, whether policy processing of the packet is set to ultimate segment decapsulation and may discard the packet when the policy processing of the packet is not set to ultimate segment decapsulation. The network device may decapsulate an outer header of the packet when the policy processing of the packet is set to ultimate segment decapsulation and may process the packet after decapsulating the outer header of the packet, to generate a processed packet. The network device may forward the processed packet toward a destination.
Processing segment routing packets with two policy processing instructions in a segment routing domain
A network device may receive a packet and may determine whether a next header of the packet is an Internet protocol (IP) header, an Internet control message protocol (ICMP) header, or a segment routing header. The network device may determine, when the next header of the packet is the IP header, whether policy processing of the packet is set to ultimate segment decapsulation and may discard the packet when the policy processing of the packet is not set to ultimate segment decapsulation. The network device may decapsulate an outer header of the packet when the policy processing of the packet is set to ultimate segment decapsulation and may process the packet after decapsulating the outer header of the packet, to generate a processed packet. The network device may forward the processed packet toward a destination.
Device-enabled access control in a mesh network
A method including receiving, by a first device in communication with a second device in a mesh network, an incoming packet from the second device; determining, by the first device, that the incoming packet is an initiation packet requesting information or a response from the first device or a response packet providing a response to an outgoing packet transmitted by the first device; and processing, by the first device, the incoming packet based at least in part on determining that the incoming packet is the initiation packet or the response packet. Various other aspects are contemplated.