Abstract: Systems, methods, and software described herein provide enhancements for the deployment and management of sensor resources across spaceborne, airborne, and ground-based physical nodes. In one implementation, a method includes collecting sensor data from physical sensors distributed over a geographic region, and establishing logical sensors based at least on requirements indicated by data requestors. The method includes allocating selected portions of the sensor data to the logical sensors to form composite sensor data based on locations monitored by the physical sensors that correspond to the requirements, and providing the composite data in one or more data streams to the data requestors as originating from the logical sensors.

Abstract: Systems, methods, and software described herein manage data from spaceborne and airborne nodes. In one implementation, a control system may obtain sensor data from sensors of spaceborne or airborne nodes. Once obtained, the control system may process the sensor data to determine metadata associated with the sensor data. Once processed, the sensor data may be stored in one or more data stores, such that applications may access the data based at least in part on the metadata.

Abstract: Systems, methods, and software described herein provide enhancements for the deployment and management of sensor resources across spaceborne, airborne, and ground-based physical nodes. In one implementation, a method includes collecting sensor data from physical sensors distributed over a geographic region, and establishing logical sensors based at least on requirements indicated by data requestors. The method includes allocating selected portions of the sensor data to the logical sensors to form composite sensor data based on locations monitored by the physical sensors that correspond to the requirements, and providing the composite data in one or more data streams to the data requestors as originating from the logical sensors.

Abstract: Systems, methods, and software described herein manage data from spaceborne and airborne nodes. In one implementation, a control system may obtain sensor data from sensors of spaceborne or airborne nodes. Once obtained, the control system may process the sensor data to determine metadata associated with the sensor data. Once processed, the sensor data may be stored in one or more data stores, such that applications may access the data based at least in part on the metadata.

Abstract: Systems, methods, and software described herein manage the initiation of applications in a system of physical nodes. In one example, a control system may identify a triggering event to initiate an application in the system based on sensor data obtained from at least a subset of the physical nodes. In response to the triggering event, the control system may identify a physical node with an image to support the execution of the application, initiate execution of the application associated with the image, and allocate or provide state information to the executing application.

Abstract: Systems, methods, and software described herein provide enhancements for the deployment of applications in an airborne and spaceborne system. In one implementation, when an application is to be deployed to the system, the system identifies a subset of physical nodes with sensor data associated with the application. Once identified, the system determines accessibility data for the physical nodes of the system to access the sensor data associated with the application and deploys the application to at least one physical node based on the accessibility data.

Abstract: Systems, methods, and software described herein provide enhancements for the deployment of applications in an airborne and spaceborne system. In one implementation, when an application is to be deployed to the system, the system identifies a subset of physical nodes with sensor data associated with the application. Once identified, the system determines accessibility data for the physical nodes of the system to access the sensor data associated with the application and deploys the application to at least one physical node based on the accessibility data.

Abstract: Systems, methods, and software described herein provide enhancements for the deployment and management of resources across spaceborne, airborne, and ground-based physical nodes to perform user tasks and applications. In one implementation, physical nodes of a system collect sensor data from physical sensors. Once collected, the physical nodes apportion the sensor data among logical sensors associated with the physical sensors and provides data streams to data requestors as originating from the logical sensors.

Abstract: Systems, methods, and software described herein provide enhancements for the deployment and management of converged resources across satellites, aircraft, and ground-based nodes to perform user tasks and applications. In one implementation, a method includes identifying a request for a logical node and identifying physical requirements of the logical node. The method further includes selecting physical nodes from a plurality of physical nodes to support the physical requirements of the logical node and distributing configuration data to the physical nodes to implement the logical node.

Abstract: A method for managing persistent file handles includes starting an expiry timer and creating a Persistent File Handle (PHDL) container for storing extended file attributes including, a generation number (GN), a share GN (SGN), a previous SGN, and a timeout max value for an expiry timer, where a SGN is a timestamp of a volume migration or an online creation in relation to the expiry timer. The method additionally includes creating a PHDL iterator to update the SGNs for every volume exported to clients, volumes created online or for a restarting of a network-share service on a server. The method further includes triggering a clean-up of stale PHDL containers from a server memory based on a difference of the new SGN and the previous SGN being greater than the timeout maximum number else preserving the PHDL object container and updating the well-known key value.

Abstract: A method for managing persistent file handles includes starting an expiry timer and creating a Persistent File Handle (PHDL) container for storing extended file attributes including, a generation number (GN), a share GN (SGN), a previous SGN, and a timeout max value for an expiry timer, where a SGN is a timestamp of a volume migration or an online creation in relation to the expiry timer. The method additionally includes creating a PHDL iterator to update the SGNs for every volume exported to clients, volumes created online or for a restarting of a network-share service on a server. The method further includes triggering a clean-up of stale PHDL containers from a server memory based on a difference of the new SGN and the previous SGN being greater than the timeout maximum number else preserving the PHDL object container and updating the well-known key value.

Abstract: Long distance cloud migration (LDCM) to overcome the limitations faced by the cloud migration techniques over long distance, high speed WAN infrastructures. LDCM overcomes the negative effects of existing TCP/IP mechanisms on the efficient use of available bandwidth. LDCM also acts as an acceleration engine to optimize various hypervisor, storage and security applications.

Abstract: One embodiment of the present invention provides a switch system. The switch includes one or more ports on the switch configured to transmit packets encapsulated based on a first protocol. The switch further includes a control mechanism. During operation, the control mechanism forms a logical switch based on a second protocol, receives an automatically assigned identifier for the logical switch without requiring manual configuration of the identifier, and joins a virtual cluster switch.

Abstract: Long distance cloud migration (LDCM) to overcome the limitations faced by the cloud migration techniques over long distance, high speed WAN infrastructures. LDCM overcomes the negative effects of existing TCP/IP mechanisms on the efficient use of available bandwidth. LDCM also acts as an acceleration engine to optimize various hypervisor, storage and security applications.

Abstract: Long distance cloud migration (LDCM) to overcome the limitations faced by the cloud migration techniques over long distance, high speed WAN infrastructures. LDCM overcomes the negative effects of existing TCP/IP mechanisms on the efficient use of available bandwidth. LDCM also acts as an acceleration engine to optimize various hypervisor, storage and security applications.

Abstract: One embodiment of the present invention provides a wireless network controller. The wireless network controller includes a data structure, a tunnel management scheme, an encapsulation mechanism, and a forwarding mechanism. The data structure stores a TRILL RBridge identifier associated with a remote wireless network controller. The tunnel management mechanism maintains a tunnel with a local access point, and the encapsulation mechanism encapsulates a packet received from the tunnel with a TRILL header which includes the RBridge identifier of the remote wireless network controller. The forwarding mechanism forwards the encapsulated packet.

Abstract: Long distance cloud migration (LDCM) to overcome the limitations faced by the cloud migration techniques over long distance, high speed WAN infrastructures. LDCM overcomes the negative effects of existing TCP/IP mechanisms on the efficient use of available bandwidth. LDCM also acts as an acceleration engine to optimize various hypervisor, storage and security applications.

Abstract: Long distance cloud migration (LDCM) to overcome the limitations faced by the cloud migration techniques over long distance, high speed WAN infrastructures. LDCM overcomes the negative effects of existing TCP/IP mechanisms on the efficient use of available bandwidth. LDCM also acts as an acceleration engine to optimize various hypervisor, storage and security applications.

Abstract: One embodiment of the present invention provides a switch. The switch includes a first port configured to receive Transparent Interconnection of Lots of Links (TRILL) traffic; a second port configured to receive Fiber Channel (FC) traffic; and a third port configured to transmit received TRILL or FC traffic based on a Fiber Channel over IP (FCIP) protocol.

Abstract: An IP gateway device establishes distinct TCP sessions within a single FCIP tunnel, each TCP session being designated for a different priority of service (e.g., high, medium, low), plus a control stream. Each TCP session has its own TCP stack and its own settings for VLAN Tagging (IEEE 802.1Q), quality of service (IEEE 802.1P) and Differentiated Services Code Point (DSCP). By distributing data streams assigned to different priorities of service into different TCP sessions within the FCIP tunnel, an IP gateway device can preserve the distinctions between the data stream priorities while the data traffic is within the IP network.