Abstract: In response to at least one message received by a processor of a gateway server from a user device wherein each message requests that an encryption key be downloaded to the user device, the processor generates at least one unique encryption key for each message and sends the at least one generated encryption key to the user device, but does not store any of the generated encryption keys in the cloud. For each encryption key having been sent to the user device, the processor receives each encryption key returned from the user device. For each encryption key received from the user device, the processor stores each received encryption key in the cloud.

Abstract: In response to at least one message received by a processor of a gateway server from a user device wherein each message requests that an encryption key be downloaded to the user device, the processor generates at least one unique encryption key for each message and sends the at least one generated encryption key to the user device, but does not store any of the generated encryption keys in the cloud. For each encryption key having been sent to the user device, the processor receives each encryption key returned from the user device. For each encryption key received from the user device, the processor stores each received encryption key in the cloud.

Abstract: In response to at least one message received by a processor of a gateway server from a user device wherein each message requests that an encryption key be downloaded to the user device, the processor generates at least one unique encryption key for each message and sends the at least one generated encryption key to the user device, but does not store any of the generated encryption keys in the cloud. For each encryption key having been sent to the user device, the processor receives each encryption key returned from the user device. For each encryption key received from the user device, the processor stores each received encryption key in the cloud.

Abstract: In response to at least one message received by a processor of a gateway server from a user device wherein each message requests that an encryption key be downloaded to the user device, the processor generates at least one unique encryption key for each message and sends the at least one generated encryption key to the user device, but does not store any of the generated encryption keys in the cloud. For each encryption key having been sent to the user device, the processor receives each encryption key returned from the user device. For each encryption key received from the user device, the processor stores each received encryption key in the cloud.

Abstract: A method and system for managing data security in a computing environment. A processor at the gateway server receives, from a user device, at least one message. Each message requests that an encryption key be downloaded to the user device. The gateway server interfaces between the user device and a cloud that includes interconnected computing systems external to the user device. In response to the received at least one message, the processor generates at least one unique encryption key for each message and sends the at least one generated encryption key to the user device, but does not store any of the generated encryption keys in the cloud. For each encryption key having been sent to the user device, the processor receives each encryption key returned from the user device. For each encryption key received from the user device, the processor stores each received encryption key in the cloud.

Abstract: A method and system for managing data security in a computing environment. A processor at the gateway server receives, from a user device, at least one message. Each message requests that an encryption key be downloaded to the user device. The gateway server interfaces between the user device and a cloud that includes interconnected computing systems external to the user device. In response to the received at least one message, the processor generates at least one unique encryption key for each message and sends the at least one generated encryption key to the user device, but does not store any of the generated encryption keys in the cloud. For each encryption key having been sent to the user device, the processor receives each encryption key returned from the user device. For each encryption key received from the user device, the processor stores each received encryption key in the cloud.

Abstract: A system and associated method for optimizing usage of a clustered-network attached storage (NAS). An administration module of the clustered NAS calculates a number of nodes in the clustered NAS necessary to service a required amount of load for a specific number of client systems, and a number of addresses associated with the nodes through which the client systems accesses the clustered NAS. The load is evenly shared by all client systems and uniformly serviced by the nodes of the clustered NAS. When a node fails, the rest of operating nodes in the clustered NAS take over addresses associated with the failed node and evenly share additional load associated with an address taken from the failed node to provide seamless services for the production by the client systems.

Abstract: A system and associated method for optimizing usage of a clustered-network attached storage (NAS). An administration module of the clustered NAS calculates a number of nodes in the clustered NAS necessary to service a required amount of load for a specific number of client systems, and a number of addresses associated with the nodes through which the client systems accesses the clustered NAS. The load is evenly shared by all client systems and uniformly serviced by the nodes of the clustered NAS. When a node fails, the rest of operating nodes in the clustered NAS take over addresses associated with the failed node and evenly share additional load associated with an address taken from the failed node to provide seamless services for the production by the client systems.

Abstract: A flow control mechanism for use in a high speed packet switching network where calls are multiplexed on network trunks with each connection using a reserved amount of the total bandwidth. Data terminal equipments access the network via access nodes. Each access node includes a Leaky Bucket component which maintains a refillable token pool. Each time an incoming packet is received by the leaky bucket component, the number of available tokens is compared to two predetermined threshold values. If the number of tokens is less than the low threshold, acknowledgments of received packets are stopped, inducing an interruption of packets transmitted by the emitting terminals. Interrupting packet transmission will lead to a regeneration of the number of tokens in the token pool. If the number of tokens reaches the high threshold, acknowledgments are again generated to restore packet transmissions.

Abstract: A flow control mechanism for use in a high speed packet switching network where calls are multiplexed on network trunks with each connection using a reserved amount of the total bandwidth. Data terminal equipments access the network via access nodes. Each access node includes a Leaky Bucket component which maintains a refillable token pool. Each time an incoming packet is received by the leaky bucket component, the number of available tokens is compaired to two predetermined threshold values. If the number of tokens is less than the low threshold, acknowledgments of received packets are stopped, inducing an interruption of packets transmitted by the emitting terminals. Interrupting packet transmission will lead to a regeneration of the number of tokens in the token pool. If the number of tokens reaches the high threshold, acknowledgments are again generated to restore packet transmissions.

Abstract: A preventive X.25 flow control mechanism for use in a high speed packet switching network where calls are multiplexed on network trunks with each connection using a reserved amount of the total bandwidth. X.25 data terminal equipments access the network via access nodes. Each access node includes a Leaky Bucket component which maintains a refillable token pool. Each time an incoming packet is received by the leaky bucket component, the number of available tokens is compared to two predetermined threshold values. If the number of tokens is less than the low threshold, acknowledgments of received packets are stopped, inducing an interruption of packets transmitted by the emitting attached X.25 terminals. Interrupting packet transmission will lead to a regeneration of the number of tokens in the token pool. If the number of tokens reaches the high threshold, acknowledgments are again generated to restore packet transmissions.