Abstract: Embodiments of a mobile device and method of communication are generally described herein. The mobile device may be configured to operate as a slave device for a Bluetooth link with a master device. The mobile device may transmit a packet in an ESCO interval. The mobile device may, in an ESCO retransmission slot of the ESCO interval: attempt to decode, from the slave device, a request for retransmission of the packet. If the request for retransmission is not successfully decoded, the mobile device may determine whether the request for retransmission was sent during the ESCO retransmission slot based at least partly on a channel energy level detected during the ESCO retransmission slot. If it is determined that the request for retransmission was not sent during the ESCO retransmission slot, the mobile device may refrain from monitoring subsequent ESCO retransmission slots of the ESCO interval.

Abstract: Technologies for improving enumeration of universal serial bus (USB) devices over a media agnostic USB (MAUSB) connection are disclosed. In the illustrative embodiment, an MAUSB device may send USB configuration data to a host compute device. The host compute device may then perform a virtual enumeration of the USB devices based on the USB configuration data without necessarily communicating with the USB devices. The MAUSB device may perform an enumeration of the USB devices on behalf of the host compute devices without necessarily communicating with the host compute device. The USB devices may not be aware or have any indication that the USB device is not communicating with the host compute device during the enumeration process. Such an approach may improve the latency of USB enumeration over an MAUSB connection.

Abstract: A source device for sending datagrams contained in an aggregated packet structure comprising transport containers each containing one or more datagram segments of the datagram, the source device comprising a feedback processor configured to receive feedback that a transmission of a transport container has failed or a detector unit that detects that a transmission of a transport container will fail; a disassembler unit that disassembles the failed transport container the transmission of which has failed or will fail; a creating unit that creates at least one new transport container from less than all of the failed transport containers without splitting datagrams; and a sending unit that sends sequence information indicating a conversion between a sequence of the transport containers of the failed datagram and a sequence of the transport containers of the new datagram, where the source device is configured to reformat and retransmit datagrams whose transmission has failed.

Abstract: Devices and techniques for reorder resilient transport are described herein. A device may store data packets in sequential positions of a flow queue in an order in which the data packets were received. The device may retrieve a first data packet from a first sequential position and a second data packet from a second sequential position that is next in sequence to the first sequential position in the flow queue. The device may store the first data packet and the second data packet in a buffer and refrain from providing the first data packet and the second data packet to upper layer circuitry if the packet order information for the first data packet and the second data packet indicate that the first data packet and the second data packet were received out of order. Other embodiments are also described.

Abstract: Snapshotting and instantiating a virtual topology are described. A virtual topology includes a set of virtual topology entities (VTEs), each associated with VTE characteristics. A snapshot engine traverses each VTE in a virtual topology instantiated on a physical topology. The snapshot engine stores the VTE characteristics of each traversed VTE in a virtual topology template. The virtual topology template may be used to deploy the same virtual topology onto another physical topology. Additionally or alternatively, a deployment engine receives a virtual topology template and/or user commands for instantiating a virtual topology. The deployment engine generates deployment commands based on the virtual topology template and/or user commands. The deployment engine identifies VTE characteristics of each VTE based on the deployment commands. The deployment engine instantiates each VTE onto a physical topology.

Abstract: Techniques for executing multiple Virtual Private Network (VPN) endpoints associated with an Endpoint Pool Address are disclosed. A VPN endpoint manager determines traffic attributes of traffic addressed to the Endpoint Pool Address. The VPN endpoint manager selects a quantity of VPN endpoints to be executed for processing the traffic based on the traffic attributes. The VPN endpoint manager causes execution of a plurality of VPN endpoints corresponding to the selected quantity. The VPN endpoint manager selects one VPN endpoint, from the VPN endpoint pool, to process each data packet addressed to the Endpoint Pool Address. The VPN endpoint manager may select different VPN endpoints to process data packets of different VPN sessions. The VPN endpoint manager may transfer a VPN session from one VPN endpoint to another VPN endpoint. The VPN endpoints in the VPN endpoint pool operate concurrently to process data packets addressed to the Endpoint Pool Address.

Abstract: A novel fibrinogen-based tissue adhesive patch is disclosed. The patch comprises a backing made from a non-permeable biocompatible polymer film into which a fibrinogen-based sealant is incorporated. In preferred embodiments of the invention, the biocompatible polymer film comprises units of a biocompatible block copolymer such as a polyethylene glycol-polycaprolactone-DL-lactide copolymer connected by urethane linkages, and the fibrinogen-based sealant comprises fibrinogen, thrombin, and CaCl2. In contrast to similar patches known in the art, the polymer backing serves to seal the tissue to which the patch is applied, and the sealant acts only to bind the patch to the affected tissue. The patch does not include any mesh, woven, or non-woven component. Methods of production and use of the patch are also disclosed.

Abstract: Techniques for implementing a single-addressable virtual topology element (VTE) in a virtual topology. A VTE in a virtual topology may be distributed as multiple instantiated elements in a physical topology. However, the multiple instantiated elements are addressable as a single entity. Obtaining information associated with the VTE includes obtaining and aggregating information from each of the instantiated elements. Applying an overall configuration to the VTE includes determining a respective configuration for each instantiated element based on the overall configuration, and applying the respective configuration to each instantiated element.

Abstract: Techniques for implementing a virtual tap in a virtual topology are described. A request to tap a particular link between a set of virtual topology entities (VTEs) is received. The particular link between the set of VTEs is mapped to a link between a set of instantiated entities in a physical topology. One of the instantiated elements implements a tapping function. Additionally or alternatively, a tapping element is instantiated and the tapping element implements the tapping function. The tapping element is not one of the set of instantiated entities. The tapping function includes: applying a tap filter to a set of data; replicating the data that passes the tap filter; and transmitting the replicated data to a virtual endpoint. The replicated data may be referred to as “tapped data.” A user interface engine presents information regarding the particular link between the set of VTEs based on the tapped data.

Abstract: Some demonstrative embodiments include apparatuses, devices, systems and methods of triggering a wireless docking session between a mobile device and a wireless docking device. For example, an apparatus may include circuitry and logic configured to cause a mobile device to detect a wireless charging of the mobile device by a wireless docking device; and to, upon detection of the wireless charging, trigger a wireless docking session between the mobile device and the wireless docking device.

Abstract: Techniques for managing a wireless network are described. An example of an electronic device configured to managing a wireless network includes a radio transceiver to enable the electronic device to communicate wirelessly with a plurality of stations over a shared channel. The electronic device also includes one or more processors to generate data frames and control the radio transceiver to transmit the data frames to the plurality of stations. The one or more processors are configured to monitor operating conditions of the wireless network and compute an awake window duration based on the operating conditions. The awake window duration describes a period of time during which stations in a power save mode are required to monitor the shared channel for an Announcement Traffic Indication Message (ATIM). The one or more processors are also configured to control the radio transceiver to transmit the awake window duration to the stations.

Abstract: An apparatus comprises a memory and processing circuitry that are configured to implement a first network control protocol (NCP) MAC layer configured to handle MAC layer communications of the first NCP, and sniffer edge circuitry. The sniffer edge circuitry is configured to communicate with the first NCP MAC layer and a second NCP MAC layer and to capture events related to second NCP (WiGig) communications. These captured events are communicated over a dedicated sniffer network, and packet contents communicated between the second NCP MAC layer and the second NCP stack are secure from the sniffer edge circuitry. The apparatus receives a distributed common time reference and uses this to timestamp the captured events.

Abstract: Devices and techniques for reorder resilient transport are described herein. A device may store data packets in sequential positions of a flow queue in an order in which the data packets were received. The device may retrieve a first data packet from a first sequential position and a second data packet from a second sequential position that is next in sequence to the first sequential position in the flow queue. The device may store the first data packet and the second data packet in a buffer and refrain from providing the first data packet and the second data packet to upper layer circuitry if the packet order information for the first data packet and the second data packet indicate that the first data packet and the second data packet were received out of order. Other embodiments are also described.

Abstract: Some demonstrative embodiments include apparatuses, devices, systems and methods of triggering a wireless docking session between a mobile device and a wireless docking device. For example, an apparatus may include circuitry and logic configured to cause a mobile device to detect a wireless charging of the mobile device by a wireless docking device; and to, upon detection of the wireless charging, trigger a wireless docking session between the mobile device and the wireless docking device.

Abstract: A novel docking process introduces a new handshake scheme between a first device (referred to herein as the “Dockee”) and a docking device (referred to simply as the “Dock”) to communicate a user's intention to connect the Dockee and the Dock (i.e., dock the Dockee to the Dock). The handshake consists of two steps: 1) establish a connection over a near field communication (NFC) link to convey information about the docking event; and 2) establish a second connection over the Wireless Channel to connect the Dockee and the Dock. The first step delivers a one-time secure connection token to the Dock over the NFC channel. Further, the presence of the NFC channel establishes the physical proximity of the user to the Dock. During step 2, a new Information Element is introduced to deliver the token back to the Dockee to allow for authentication and “closure” of the handshake.

Abstract: A communication system comprises a transmission controller configured to send transmissions to one or more transceivers; a device performance analyzer configured to receive feedback about the reception of transmissions at said transceivers, and to analyze such feedback to estimate the quality of communication with an existing ATW and to output a quality information; an ATW performance analyzer configured to receive the quality information of the device performance analyzer and to perform further analysis to estimate whether the ATW should be retained as in current operation or modified based on feedback received from said transceivers and to output an estimate information; or ATW feedback analyzer configured to receive feedback about the ATW from said other transceivers, and to estimate based on such feedback whether the ATW should be retained as in current operation or modified based on feedback received from said transceivers; and an ATW estimator configured to receive the estimate information of the ATW pe

Abstract: Techniques for snapshotting and instantiating a virtual topology are described. A virtual topology includes a set of virtual topology entities (VTEs), each associated with VTE characteristics. A snapshot engine traverses each VTE in a virtual topology instantiated on a particular physical topology. The snapshot engine stores the VTE characteristics of each traversed VTE in a virtual topology template. The virtual topology template may be used to deploy the same virtual topology onto another physical topology. A deployment engine receives a virtual topology template and/or user commands for instantiating a virtual topology. The deployment engine generates deployment commands based on the virtual topology template and/or user commands. The deployment engine identifies VTE characteristics of each VTE based on the deployment commands. The deployment engine instantiates each VTE onto one or more physical topologies.

Abstract: Techniques for executing multiple Virtual Private Network (VPN) endpoints associated with an Endpoint Pool Address are disclosed. A VPN endpoint manager determines traffic attributes of traffic addressed to the Endpoint Pool Address. The VPN endpoint manager selects a quantity of VPN endpoints to be executed for processing the traffic based on the traffic attributes. The VPN endpoint manager causes execution of a plurality of VPN endpoints corresponding to the selected quantity. The VPN endpoint manager selects one VPN endpoint, from the VPN endpoint pool, to process each data packet addressed to the Endpoint Pool Address. The VPN endpoint manager may select different VPN endpoints to process data packets of different VPN sessions. The VPN endpoint manager may transfer a VPN session from one VPN endpoint to another VPN endpoint. The VPN endpoints in the VPN endpoint pool operate concurrently to process data packets addressed to the Endpoint Pool Address.

Abstract: Techniques for transforming data based on a virtual topology are disclosed. A computer network is associated with a physical topology and a virtual topology. A physical topology is a particular arrangement of digital devices. A virtual topology is a description of a particular arrangement of virtual topology entities (VTEs). VTEs of the virtual topology are instantiated on digital devices of the physical topology. A processing component associated with a particular VTE processes data to perform one or more functions of the particular VTE. An emulation component associated with the particular VTE modifies the data to emulate performance of the functions by the particular VTE.

Abstract: This disclosure describes systems, methods, and devices related to unauthorized users notification. A device may identify a request from a first device to establish a direct connection. The device may determine a connection status based at least in part on information included in the request. The device may generate a response frame including a connection status information element (IE). The device may cause to send the response frame to the first device.