IP Library Granted Patent US 12,682,097
Granted Patent B2
US 12,682,097 · App. 18/426,638 · Granted Jul 14, 2026

API model for as-a-service data resilience management

Inventors: Mladen Brajković (Ljubljana, SI); Antal Nemeš (Ljubljana, SI); Subbiah Sundaram (Boston, MA)
Assignee: HYCU, INC.
G06F21/6218G06F11/1448
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,682,097
App. No.
18/426,638
Filed
Jan 30, 2024
Granted
Jul 14, 2026
Kind
B2
Art Unit
2433
USPC
726/27
Abstract

A platform we call an R-Cloud Data Protection Platform supports the ability to recover anything “as-a-Service” at a specified level of granularity. The approach splits data catalog information between the R-Cloud platform and R-Cloud Modules. It provides the ability to describe every as-a-Service related configuration and data hierarchy, their attributes, associations, relevance to data resilience and the associated methods required to protect and recover the different parts of the service and data. This enables the unique approach to cover all as-a-Service, from the simple ones like Google CloudSQL to the most complex ones having millions of dynamic and unstructured objects within.

Claims (47)

1 . A method for automatic data protection for one or more resources provided by a service, wherein the service operates in a computing environment that deploys one or more access points to which Application Programming Interface (API)-based requests are directed, and wherein the service resources relate to data objects arranged at one or more levels of a hierarchy, the method comprising:

responsive to receipt of an API request for data protection,

discovering data objects accessed by the service resource, by operating a selected one of plurality of modules, each module corresponding to one of a plurality of different services, and each module executing at least some requests that are specific to the service resource,

discovering attributes specific to the data objects, including a data protection attribute that indicates whether a data protection method is accessible to protect the data objects via the service resource at one or more levels of a hierarchy;

obtaining information for use with another data protection method that is other than via the service resource;

storing, in a centralized catalog, information that describes a data protection workflow for the service, including whether the data protection method is provided by the service or whether it is an other data protection method external to the service;

and executing a granular data protection process, by accessing the centralized catalog to determine data protection attribute information for each data object, and

when the data protection attribute is true,

invoking the data protection method accessible via the service resource;

else when the data protection attribute is false,

invoking the other data protection method.

2 . The method of claim 1 wherein discovering attributes further comprises determining a workflow for invoking a data protection method that is other than via the service resource.

3 . The method of claim 1 wherein the step of discovering attributes is implemented in a plug-in operating within the service.

4 . The method of claim 1 wherein the step of executing the granular data protection process is implemented on a data processing platform outside of the service resource.

5 . The method of claim 1 wherein the service is a SaaS, PaaS, DBaaS, or IaaS.

6 . The method of claim 1 wherein the data protection attribute indicates whether the service provides backup for the data object.

7 . The method of claim 1 wherein the data protection attribute indicates whether the service provides recovery of the data object.

8 . An apparatus comprising:

a hardware processor; and

computer memory holding computer program instructions executed by the hardware processor for access control in a computing environment in which clients interact with an application deploying one or more access points to which application programming interface (API)-based requests are directed, the computer program instructions configured for:

responsive to receipt of an API request for data protection,

discovering data objects accessed by the service resource, by operating a selected one of plurality of modules, each module corresponding to one of a plurality of different services, and each module executing at least some requests that are specific to the service resource;

discovering attributes specific to the data objects, including a data protection attribute that indicates whether a data protection method is accessible to protect the data objects via the service resource at one or more levels of a hierarchy;

obtaining information for use with another data protection method that is other than via the service resource;

storing, in a centralized catalog, information that describes a data protection workflow for the service, including whether the data protection method is provided by the service or whether it is an other data protection method external to the service;

and executing a granular data protection process, by accessing the centralized catalog to determine data protection attribute information for each data object, and

when the data protection attribute is true,

invoking the data protection method accessible via the service resource;

else when the data protection attribute is false,

invoking the other data protection method.

9 . The apparatus of claim 8 wherein discovering attributes further comprises determining a workflow for invoking a data protection method that is other than via the service resource.

10 . The apparatus of claim 8 wherein the step of discovering attributes is implemented in a plug-in operating within the service.

11 . The apparatus of claim 8 wherein the step of executing the granular data protection process is implemented on a data processing platform outside of the service resource.

12 . The apparatus of claim 8 wherein the service is a SaaS, PaaS, DBaaS, or IaaS.

13 . The apparatus of claim 8 wherein the data protection attribute indicates whether the service provides backup for the data object.

14 . The apparatus of claim 8 wherein the data protection attribute indicates whether the service provides recovery of the data object.

15 . A computer program product in a non-transitory computer readable medium for access control in a computing environment in which clients interact with an application deploying one or more access points to which application programming interface (API)-based requests are directed, the computer program product holding computer program instructions that, when executed by a data processing system, is configured to:

responsive to receipt of an API request for data protection,

discovering data objects accessed by the service resource, by operating a selected one of plurality of modules, each module corresponding to one of a plurality of different services, and each module executing at least some requests that are specific to the service resource;

discovering attributes specific to the data objects, including a data protection attribute that indicates whether a data protection method is accessible to protect the data objects via the service resource at one or more levels of a hierarchy;

obtaining information for use with another data protection method that is other than via the service resource;

storing, in a centralized catalog, information that describes a data protection workflow for the service, including whether the data protection method is provided by the service or whether it is an other data protection method external to the service;

and executing a granular data protection process, by accessing the centralized catalog to determine data protection attribute information for each data object, and

when the data protection attribute is true,

invoking the data protection method accessible via the service resource;

else when the data protection attribute is false,

invoking the other data protection method.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2026
From: BRAJKOVIC, MLADEN
To: HYCU, INC.
Reel/Frame 075014/0579 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2026
From: NEMEŠ, ANTAL; SUNDARAM, SUBBIAH
To: HYCU, INC.
Reel/Frame 074978/0939 →
SECURITY INTEREST Recorded Oct 4, 2024
From: HYCU, INC.
To: FIRST-CITIZENS BANK & TRUST COMPANY
Reel/Frame 068805/0695 →
Continuity (2)
Provisional Application 63442140 · Jan 31, 2023
Related Publication 20240273226A1 · Aug 15, 2024
References Cited (31)
US 10402090B1 · Tsaur · 2019 [cited by examiner]
US 11303659B2 · Yu et al. · 2022 [cited by applicant]
US 11416641B2 · Narayanaswamy · 2022 [cited by applicant]
US 12314430B1 · Hardt · 2025 [cited by examiner]
US 20070168715A1 · Herz et al. · 2007 [cited by applicant]
US 20100332401A1 · Prahlad et al. · 2010 [cited by applicant]
US 20130152047A1 · Moorthi et al. · 2013 [cited by applicant]
US 20150135302A1 · Cohen et al. · 2015 [cited by applicant]
US 20160019033A1 · Ebner et al. · 2016 [cited by applicant]
US 20160072831A1 · Rieke · 2016 [cited by applicant]
US 20160330080A1 · Bhatia et al. · 2016 [cited by applicant]
US 20170149624A1 · Chitti et al. · 2017 [cited by applicant]
US 20170185488A1 · Kumarasamy et al. · 2017 [cited by applicant]
US 20180040256A1 · Alvarez et al. · 2018 [cited by applicant]
US 20180314457A1 · Bender et al. · 2018 [cited by applicant]
US 20180341666A1 · Lee et al. · 2018 [cited by applicant]
US 20190036910A1 · Choyi et al. · 2019 [cited by applicant]
US 20190140914A1 · Maes · 2019 [cited by applicant]
US 20190207968A1 · Heckman et al. · 2019 [cited by applicant]
US 20190303961A1 · Patankar et al. · 2019 [cited by applicant]
US 20190319860A1 · Seed et al. · 2019 [cited by applicant]
US 20190332485A1 · Gill et al. · 2019 [cited by applicant]
US 20190342307A1 · Gamble et al. · 2019 [cited by applicant]
US 20200137097A1 · Zimmermann et al. · 2020 [cited by applicant]
US 20200244673A1 · Stockdale et al. · 2020 [cited by applicant]
US 20210203684A1 · Maor et al. · 2021 [cited by applicant]
US 20220191230A1 · Morgan · 2022 [cited by applicant]
US 20220318059A1 · Cook et al. · 2022 [cited by applicant]
EP 3528454A1 · 2019 [cited by applicant]
WO 2020106973A1 · 2020 [cited by applicant]
PCT/US24/13443 Search Report and Written Opinion, dated Jun. 24, 2024 (13 pages). [cited by applicant]