Automatically configuring boot sequence of container systems for disaster recovery
US-11416342-B2 · Aug 16, 2022 · US
US12481774B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12481774-B2 |
| Application number | US-202318321323-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 22, 2023 |
| Priority date | Jan 15, 2020 |
| Publication date | Nov 25, 2025 |
| Grant date | Nov 25, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods can allow for secure cross-device sharing of transient data using direct transient data sharing (“DTDS”). A source destination can share data using local DTDS with an agent on a first device. The agent can send the data to a hub server that runs a security control process and data formatting process. The hub server can determine risk scores for the source and destination devices and allow the sharing to occur if a safety threshold is met. Then an agent on the destination device can receive the transient data and use local DTDS to send the data to a destination application.
Opening claim text (preview).
What is claimed is: 1 . A method for sharing between user devices using direct transient data sharing (“DTDS”), comprising: receiving data at a server from a first device, wherein a source application on the first device shares the data with a first agent at the first device using DTDS, and wherein the first agent shares the data with the server; identifying, at the server, a second device associated with a same user as the first device, the second device including a destination application to receive the data; determining that security requirements are met based on the second device complying with a compliance policy provided from the server to the second device, wherein a second agent on the second device reports compliance status of the second device with the compliance policy to the server, and wherein the compliance status specifies a management status of the destination application, the management status indicating whether the destination application is managed by the server or not managed by the server; and in an instance where the security requirements are met, sending the data to the destination application or the second agent of the second device, wherein the security requirements are met if the management status of the destination application indicates that the destination application is managed by the server, and wherein the security requirements are not met when the management status of the destination application indicates that the destination application is not managed by the server. 2 . The method of claim 1 , further comprising: determining that the second device runs a different operating system (“OS”) compared to the first device; and translating the data for use with the different OS. 3 . The method of claim 2 , wherein the translating includes the server converting an image to a different image format. 4 . The method of claim 2 , wherein the translating includes converting the data to a different size. 5 . The method of claim 1 , wherein determining the security requirements are met includes determining risk scores for the first device and second device based on the management status of the source application and destination application, wherein the risk scores are compared against a threshold to determine whether to send the data to the destination application. 6 . The method of claim 1 , wherein determining the security requirements are met includes determining that the first device is also compliant with the compliance policy. 7 . The method of claim 1 , wherein sending the data to the destination application includes sending the data from the server to the second agent on the second device, and wherein the second agent sends the data to the destination application using DTDS. 8 . A non-transitory, computer-readable medium containing instructions that, when executed by a hardware-based processor, performs stages for sharing between user devices using direct transient data sharing (“DTDS”), the stages comprising: receiving data at a server from a first device, wherein a source application on the first device shares the data with a first agent at the first device using DTDS, and wherein the first agent shares the data with the server; identifying, at the server, a second device associated with a same user as the first device, the second device including a destination application to receive the data; determining that security requirements are met by the second device, wherein the security requirements are met if a management status of the destination application indicates that the destination application is managed by the server, and wherein the security requirements are not met when the management status of the destination application indicates that the destination application is not managed by the server; and in an instance where the security requirements are met: converting the data to a different size based on the second device running a different operating system (“OS”) compared to the first device; and sending the converted data to the second device. 9 . The non-transitory, computer-readable medium of claim 8 , wherein determining the security requirements are met includes verifying that both the first and second device meet compliance policies for the different respective operating systems. 10 . The non-transitory, computer-readable medium of claim 8 , wherein the converting includes the server converting an image to a different image format. 11 . The non-transitory, computer-readable medium of claim 8 , wherein the converting includes converting the data to a different size. 12 . The non-transitory, computer-readable medium of claim 8 , wherein determining the security requirements are met includes determining risk scores for the first device and second device based on the management status of the source application and destination application, wherein the risk scores are compared against a threshold to determine whether to send the data to the destination application. 13 . The non-transitory, computer-readable medium of claim 8 , wherein determining the security requirements are met is based on compliance of the first and second devices with a compliance policy provided from the server to the first and second devices, wherein a first agent on the first and a second agent on the second device report compliance statuses to the server. 14 . The non-transitory, computer-readable medium of claim 8 , wherein sending the data to the destination application includes sending the data from the server to the second agent on the second device, and wherein the second agent sends the data to the destination application using DTDS. 15 . A system for secure cross-device transient data sharing using direct transient data sharing (“DTDS”), comprising: a memory storage including a non-transitory, computer-readable medium comprising instructions; and a computing device including a hardware-based processor that executes the instructions to carry out stages comprising: receiving data at a server from a first device, wherein a source application on the first device shares the data with a first agent at the first device using DTDS, and wherein the first agent shares the data with the server, identifying, at the server, a second device associated with a same user as the first device, the second device including a destination application to receive the data; determining that security requirements are met based on the second device complying with a compliance policy provided from the server to the second device, wherein a second agent on the second device reports compliance status of the second device with the compliance policy to the server, and wherein the compliance status specifies a management status of the destination application, the management status indicating whether the destination application is managed by the server or not managed by the server; and in an instance where the security requirements are met, sending the data to the destination application or the second agent of the second device, wherein the security requirements are met if the management status of the destination application indicates that the destination application is managed by the server, and wherein the security requirements are not met when the management status of the destination application indicates that the destination application is not managed by the server. 16 . The system of claim 15 , the stages further comprising: determining that the second device runs a different operating system (“OS”) compared to the first device; and translating the data for use with t
Program or device authentication · CPC title
Data format conversion from or to a database · CPC title
Ensuring data consistency and integrity · CPC title
Protecting personal data, e.g. for financial or medical purposes · CPC title
to a system of files or objects, e.g. local or distributed file system or database · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.