Aspects of the present disclosure relate to systems and methods for syncing and propagating updated metadata across multiple endpoints. In one aspect, a request is sent from a client computing device to a service for updated metadata of a dataset. When updated metadata is identified at the service, updated metadata associated with a parent node of the dataset may be received at the client computing device without requiring the service to send updated metadata for one or more children nodes in the dataset. store the updated metadata associated with the parent node of the dataset may be stored in a local data store at the client computing device.

A method of utilizing the same hardware network interface card (NIC) in a gateway of a datacenter to communicate datacenter tenant packet traffic and packet traffic for a set of applications that execute in the user space of the gateway and utilize a network stack in the kernel space of the gateway. The method sends and receives packets for the datacenter tenant packet traffic through a packet datapath in the user space. The method sends incoming packets from the NIC to the set of applications through the datapath in the user space, a user-kernel transport driver connecting the kernel network stack to the datapath in the user space, and the kernel network stack. The method receives outgoing packets at the NIC from the set of applications through the kernel network stack, the user-kernel transport driver, and the data path in the user space.

The present invention faces the issues of re-selection of another NF Service instance (103, 201) for a subsequent request (S-520, S-535) with a same data consistency (Consistency 1) as a previously selected NF Service instance (101). To solve this issue, the present invention provides for identifying at configuration, based on the deployment and on the Storage solution for the Session/context data, which instances (101, 103, 201) of the same service type have access with strong consistency to the same data, and provide this information to the consumer (40), so it is allowed to prioritize selection of an alternative NF service instance that supports strong consistency, whenever possible.

Various example embodiments for supporting security in a communication system are presented. Various example embodiments for supporting security in a communication system may be configured to support stateful security redundancy in the communication system. Various example embodiments for supporting stateful security redundancy in a communication system may be configured to support stateful security redundancy for a set of client devices based on a set of security nodes arranged in a security redundancy architecture. Various example embodiments for supporting stateful security redundancy for a set of client devices based on a set of security nodes arranged in a security redundancy architecture may be configured to support stateful security redundancy for a client device based on a security redundancy domain including an active security node and one or more standby security nodes.

In an approach to improve the field of multi-cloud environments by detecting data corruption between storage systems. Embodiments perform information tunneling on data transferring between a source storage system and a target storage system. Further, embodiments determine a checksum data of a data payload does not match an Internet Protocol (IP) packet extracted checksum and a blockchain based checksum and compare the checksum data at the target storage system with the IP packet extracted checksum and the blockchain based checksum to identify one or more checksum mismatches. Additionally, embodiments identify a corruption in a data payload based on the comparison between the checksum data at the target storage system and the IP packet extracted checksum and the blockchain based checksum, validate the corruption in the data payload, and update respective entities of identified corruption in the data payload.

A system or method for managing an auxiliary data location and a secondary data location. A client computing device may have secondary copies of its primary data stored at a secondary storage device, as well as auxiliary copies of the secondary copies at an auxiliary storage device. The client computing device may move from one geographic location that is near the secondary storage device to a second geographic location that is far from the secondary storage device, but closer to the auxiliary storage device. A method is provided with input signals in response to the move, and outputs a probability value that the move is temporary or permanent. Based on the output, a storage manager that manages the client computing device may then direct the client computing device to use the auxiliary storage device for storing secondary copies.

A system or method for managing an auxiliary data location and a secondary data location. A client computing device may have secondary copies of its primary data stored at a secondary storage device, as well as auxiliary copies of the secondary copies at an auxiliary storage device. The client computing device may move from one geographic location that is near the secondary storage device to a second geographic location that is far from the secondary storage device, but closer to the auxiliary storage device. A method is provided with input signals in response to the move, and outputs a probability value that the move is temporary or permanent. Based on the output, a storage manager that manages the client computing device may then direct the client computing device to use the auxiliary storage device for storing secondary copies.

Techniques are disclosed for the sharing and transferring of user data in online network systems operating in multiple jurisdictions. The different jurisdictions may be, for example, different geo-partitions in an online network system. Various techniques are disclosed for providing cross-partition operational functionalities (e.g., cross-geo transactions) between geo-partitioned server systems through the sharing and transferring of data between the geo-partitions. The geo-partitions may have established permissions for data that can be shared between the geo-partitions. A server system in one geo-partition may generate an auxiliary account from a subset of data shared across the geo-partitions that complies with the data permissions. Complying with the established data permissions may inhibit overlapping between the different laws or regulations of the geo-partitions.

Examples described herein include systems and methods for performing email synchronization in situations where mobile-device connectivity is lacking. The mobile device can send an SMS message to an email notification server requesting email synchronization and the email notification server can request synchronization with the email server associated with the user's email account. After receiving an email from the email server, the email notification server can encrypt the email and break it into various chunks, with each chunk including a header having identifying information. The chunks can be transmitted as SMS messages to the mobile device. The email application can retrieve the SMS messages, decrypt them, and reconstruct the email. The email application can then display the email for the user.

Through a cloud-based centralized user interface, a federated compliance system presents a policy of interest and representations of disparate systems that match the policy of interest to a user. The disparate systems, which operate in a distributed network computing environment, can include cloud-based repositories and off-cloud repositories. The federated compliance system can pull the cloud-based repositories through a cloud orchestrator and the off-cloud repositories through an off-cloud orchestrator over a secure tunnel. The federated compliance system utilizes user-provided information on the policy of interest to determine various categories of attributes from different repository schemas employed by the disparate systems. A federated retention policy mapper, implemented as a compliance service, maps the attributes to a common schema, creates a federated retention policy, and stores it in a federated space in the distributed network computing environment. A policy change can be automatically propagated across the disparate systems using the federated retention policy.