Abstract: A Management-as-a-Service (MaaS) agent running on a client network creates a reverse session-origination (RSO) tunnel between the client network and a MaaS server. The MaaS agent collects client statistics at and regarding the client network and transmits the client statistics to the MaaS server. The MaaS server analyzes the client data and sends alerts or other messages to a user, who may be outside the client network, in the event certain conditions are met.

Abstract: A remote user sends a user request to a relay server that, in turn, forwards the user request (modified or unmodified) through a reverse session-origination (RSO) tunnel to an on-premises network client. In other words, while the user requests flow from outside the client network to the client network, the requests of the delivery protocol for the tunnel flow in the reverse direction, i.e., from the client network toward the relay server and/or the remote user. A server agent, executing client side, generates delivery-protocol requests so that the server can wrap user requests in delivery-protocol responses. In addition, the server agent unwraps user requests and forwards them to their intended destination in the client network. To minimize any time the server would have to wait for a delivery-protocol request, the server agent can generate dummy requests whenever no delivery-protocol request is pending at the server.

Abstract: A remote user sends a user request to a relay server that, in turn, forwards the user request (modified or unmodified) through a reverse session-origination (RSO) tunnel to an on-premises network client. In other words, while the user requests flow from outside the client network to the client network, the requests of the delivery protocol for the tunnel flow in the reverse direction, i.e., from the client network toward the relay server and/or the remote user. A server agent, executing client side, generates delivery-protocol requests so that the server can wrap user requests in delivery-protocol responses. In addition, the server agent unwraps user requests and forwards them to their intended destination in the client network. To minimize any time the server would have to wait for a delivery-protocol request, the server agent can generate dummy requests whenever no delivery-protocol request is pending at the server.

Abstract: A Management-as-a-Service (MaaS) agent running on a SOPS creates collecting management statistics relating to the health, utilization, and performance of a subscriber on-premises system (SOPS). The MaaS agent forwards the collected data to a MaaS server, which stores the data in association with a tenant identifier (TID) in a multi-tenant database. The MaaS server tags user queries with the TID, so that the query result is based on management data for the respective SOPS, to the exclusion of SOPS associated with different TIDs. The use of multi-tenant techniques with non-multi-tenant SOPS allows one MaaS to manage plural SOPS while maintaining isolation of the management data for the respective SOPS. In addition, the use of multi-tenant techniques allows SOPS to be managed together with cloud-based subscriber applications, facilitating common management of hybrid cloud and on-premises systems.

Abstract: A remote user sends a user request to a relay server that, in turn, forwards the user request (modified or unmodified) through a reverse session-origination (RSO) tunnel to an on-premises network client. In other words, while the user requests flow from outside the client network to the client network, the requests of the delivery protocol for the tunnel flow in the reverse direction, i.e., from the client network toward the relay server and/or the remote user. A server agent, executing client side, generates delivery-protocol requests so that the server can wrap user requests in delivery-protocol responses. In addition, the server agent unwraps user requests and forwards them to their intended destination in the client network. To minimize any time the server would have to wait for a delivery-protocol request, the server agent can generate dummy requests whenever no delivery-protocol request is pending at the server.

Abstract: A Management-as-a-Service (MaaS) agent running on a SOPS creates collecting management statistics relating to the health, utilization, and performance of a subscriber on-premises system (SOPS). The MaaS agent forwards the collected data to a MaaS server, which stores the data in association with a tenant identifier (TID) in a multi-tenant database. The MaaS server tags user queries with the TID, so that the query result is based on management data for the respective SOPS, to the exclusion of SOPS associated with different TIDs. The use of multi-tenant techniques with non-multi-tenant SOPS allows one MaaS to manage plural SOPS while maintaining isolation of the management data for the respective SOPS. In addition, the use of multi-tenant techniques allows SOPS to be managed together with cloud-based subscriber applications, facilitating common management of hybrid cloud and on-premises systems.

Abstract: A Management-as-a-Service (MaaS) agent running on a client network creates a reverse session-origination (RSO) tunnel between the client network and a MaaS server. The MaaS agent collects client statistics at and regarding the client network and transmits the client statistics to the MaaS server. The MaaS server analyzes the client data and sends alerts or other messages to a user, who may be outside the client network, in the event certain conditions are met.