A method and system are disclosed, for using Intermediate System to Intermediate System, IS-IS, as control plane for Shortest Path Bridging, SPB, in a network comprising at least a Service Provider Network, SPN (101), and at least two Backbone Edge Bridges, BEBs (121.sub.i), connected to the SPN (101). The method comprises, and the BEBs are configured to: forming adjacency between BEBs through LAN Hellos, electing one of the BEBs as a Designated IS, DIS, and an emulated pseudonode, all BEBs creating and flooding non-pseudonode level-1 LSPs, the DIS creating and flooding a Pseudonode level-1 ESP, and periodically sending Complete Sequence Number PDUs, CSNPs, to the other BEBs, and running Shortest Path First, SPF, to calculate the shortest path in the network between BEBs.

A mechanism to facilitate a private network (VPN)-as-a-service, preferably within the context of an overlay IP routing mechanism implemented within an overlay network. A network-as-a-service customer operates endpoints that are desired to be connected to one another securely and privately using the overlay IP (OIP) routing mechanism. The overlay provides delivery of packets end-to-end between overlay network appliances positioned at the endpoints. During such delivery, the appliances are configured such that the data portion of each packet has a distinct encryption context from the encryption context of the TCP/IP portion of the packet. By establishing and maintaining these distinct encryption contexts, the overlay network can decrypt and access the TCP/IP flow. This enables the overlay network provider to apply one or more TCP optimizations. At the same time, the separate encryption contexts ensure the data portion of each packet is never available in the clear at any point during transport.

An example method includes exchanging targeted hello messages to establish a targeted neighbor connection between a first routing device and a second routing device, wherein one of the routing devices comprises a central routing device, and wherein another one of the routing devices comprises an ingress routing device. The example method further includes processing a source-active register message that specifies a source address and an identifier that are collectively associated with a multicast stream, and wherein the source-active register message further indicates whether the multicast stream is active or withdrawn. After processing the source-active register message, the example method further includes processing a list-of-receivers register message that specifies an egress routing device and at least the identifier that is associated with the multicast stream, wherein the list-of-receivers register message further indicates whether or not the egress routing device requests receipt of data associated with the multicast stream.

The present invention relates to IoT devices existing in a deployed ecosystem. The various computers in the deployed ecosystem are able to respond to requests from a device directly associated with it in a particular hierarchy, or it may seek a response to the request from a high order logic/data source (parent). The logic/data source parent may then repeat the understanding process to either provide the necessary response to the logic/data source child who then replies to the device or it will again ask a parent logic/data sources for the appropriate response. This architecture allows for a single device to make one request to a single known source and potentially get a response back from the entire ecosystem of distributed servers.

Some demonstrative embodiments include apparatuses, systems and/or methods of establishing a mesh data path. For example, a first Neighbor Awareness Networking (NAN) device may be configured to transmit a NAN data path request to a second NAN device to request to establish a NAN data path between the first NAN device and the second NAN device, the NAN data path request including a first path information attribute corresponding to a mesh data path; and to process a NAN data path response from the second NAN device, the NAN data path response including a second path information attribute corresponding to the mesh data path, the second path information attribute including a path status indicator to indicate whether mesh data path routing to the destination address of the mesh data path is successful.

A network includes at least one node to communicate with at least one other node via a wireless network protocol. The node includes a network configuration module to periodically switch a current node function of the node between an intermediate node function and a leaf node function. The switch of the current node function enables automatic reconfiguration of the wireless network based on detected communications between the at least one node and at least one intermediate node or at least one leaf node via the wireless network protocol.

An apparatus stores connection information indicating connection relationship among topological structures in a network, in which first-type topological structures are coupled to second-type topological structures. The apparatus stores first transfer-patterns each indicating a combination of input and output ports for performing all-to-all communication without path conflict in each of the first-type topological structures, and second transfer-patterns each indicating a combination of input and output ports for performing all-to-all communication without path conflict in each of the second-type topological structures. The apparatus identifies paths from transmission sources to transmission destinations for a combination of the first and second transfer-patterns, and determines, based on the identified paths, a transfer-pattern with which to perform all-to-all communication without path conflict from the transmission sources to the transmission destinations, and determines output ports in each of the first- and second-type topological structures, corresponding to the identified paths.

A method and apparatus are described for negotiating “keep-alive” message frequencies of applications running on a wireless transmit/receive unit (WTRU). A node may include a negotiation and synchronization function (NSF) configured to collect information including frequencies of keep-alive messages required by application servers for different applications running on the WTRU, and send a keep-alive message frequency negotiation request message to the application servers to negotiate for a more proper frequency for each application on behalf of the WTRU. The node may further include a buffering and caching function (BCF) configured to cache and buffer application specific attributes including an indication of whether each of the applications needs to send periodic keep-alive messages to an associated application server. The node may be a packet data network gateway, a negotiation and caching gateway, or a serving gateway.

A method is implemented by a network device for improving availability of network component using multi-chassis redundancy by efficiently re-routing data traffic intended for the network component in the event of a link or node failure. The network device is in a set of network devices hosting the network component each network device in the set of network devices having a shared cluster identifier and a separate node identifier. The set of network devices hosting the network component share a virtual internet protocol address.

In various embodiments, methods and systems for measuring load-balancer responsiveness in a cloud computing infrastructure are provided. A plurality of requests is transmitted to a data center virtual IP (VIP), where the data center VIP is configured to receive inbound traffic for a service. A load-balancing component associated with the VIP distributes the requests to a DIP pool comprised of one or more machines, each associated with a private direct IP (DIP). Each of the machines includes a DIP node-monitoring component including a keep-alive URL for receiving keep-alive probes and a dummy service URL for receiving the plurality of requests. A latency of exclusion or inclusion of a first DIP of a first machine in the DIP pool is determined based on at least some of the requests received by the DIP node-monitoring component from the load-balancing component.