IP Library › Granted Patent US 12,737,329
Granted Patent B2
US 12,737,329 · App. 18/782,704 · Granted Sep 15, 2026

Scalable design of relational database for resource management

Inventors: Yuanyuan Du (Hangzhou, CN); Jingjin Xie (Hangzhou, CN)
Assignee: Zoom Communications, Inc.
G06F16/213G06F11/3409G06F16/2282G06F16/256
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,737,329
App. No.
18/782,704
Granted
Sep 15, 2026
Kind
B2
Abstract

Systems and methods for resource management using a scalable resource management database are provided. A resource management tool accesses a resource management database. The resource management tool determines a size of an attribute value corresponding to an attribute of a resource instance satisfies a predetermined size threshold. The resource management tool determines a query frequency associated with the attribute value satisfies a predetermined frequency threshold. The resource management tool creates a value index table based on a value table, the value index table excluding the attribute value satisfying the predetermined size threshold and the predetermined frequency threshold.

Claims (50)

1 . A method comprising:

accessing a resource management database, the resource management database comprising a value table storing one or more attribute values corresponding to one or more attributes for one or more resource instances, the one or more resources instance comprising one or more runtime objects representing one or more compute resources;

determining that a size of an attribute value corresponding to an attribute of a resource instance is greater than a predetermined size threshold;

determining that a query frequency associated with the attribute value of the resource instance is less than a predetermined query frequency threshold; and

creating a value index table based on the value table, the value index table excluding the attribute value of the resource instance.

2 . The method of claim 1 , further comprising:

updating the resource management database by adding the value index table.

3 . The method of claim 1 , further comprising:

querying resource instances based on the value index table.

4 . The method of claim 1 , wherein the resource management database further comprises a resource table, an instance table, and an attribute table, wherein the resource table is configured to record one or more resource types, wherein the instance table is configured to store the one or more resource instances corresponding to the one or more resource types, wherein the attribute table is configured to store the one or more attributes for the one or more resource instances.

5 . The method of claim 1 , wherein the resource instance is a Kubernetes pod instance, attributes for the Kubernetes pod instance comprises a unique identification attribute and a full information attribute, and wherein a value of the full information attribute for the Kubernetes pod instance is in a JSON string structure.

6 . The method of claim 5 , further comprising:

determining the size of the value of the full information attribute for the Kubernetes pod instance is greater than the predetermined size threshold;

determining the query frequency associated with the value of the full information attribute for the Kubernetes pod instance is less than the predetermined query frequency threshold; and

creating the value index table based on the value table, the value index table excluding the value of the full information attribute for the Kubernetes pod instance.

7 . The method of claim 1 , wherein the predetermined size threshold is 64 kilobytes, and wherein the predetermined query frequency threshold is 50 queries per second.

8 . A system comprising:

a communications interface;

a non-transitory computer-readable medium; and

one or more processors communicatively coupled to the communications interface and the non-transitory computer-readable medium, the one or more processors configured to execute processor-executable instructions stored in the non-transitory computer-readable medium to:

access a resource management database, the resource management database comprising a value table storing one or more attribute values corresponding to one or more attributes for one or more resource instances, the one or more resources instance comprising one or more runtime objects representing one or more compute resources;

determine that a size of an attribute value corresponding to an attribute of a resource instance is greater than a predetermined size threshold;

determine that a query frequency associated with the attribute value of the resource instance is less than a predetermined query frequency threshold; and

create a value index table based on the value table, the value index table excluding the attribute value of the resource instance.

9 . The system of claim 8 , wherein the one or more processors are configured to execute further processor-executable instructions stored in the non-transitory computer-readable medium to:

update the resource management database by adding the value index table.

10 . The system of claim 8 , wherein the one or more processors are configured to execute further processor-executable instructions stored in the non-transitory computer-readable medium to:

query resource instance based on the value index table.

11 . The system of claim 8 , wherein the resource management database comprises a resource table, an instance table, and an attribute table, wherein the resource table is configured to record one or more resource types, wherein the instance table is configured to store one or more resource instances corresponding to the one or more resource types, and wherein the attribute table is configured to store one or more attributes for the one or more resource instances.

12 . The system of claim 8 , wherein the resource instance is a Kubernetes pod instance, attributes for the Kubernetes pod instance comprises a unique identification attribute and a full information attribute, and wherein a value of the full information attribute for the Kubernetes pod instance is in a JSON string structure.

13 . The system of claim 12 , wherein the one or more processors are configured to execute further processor-executable instructions stored in the non-transitory computer-readable medium to:

determine the size of the value of the full information attribute for the Kubernetes pod instance is greater than the predetermined size threshold;

determine the query frequency associated with the value of the full information attribute for the Kubernetes pod instance is less than the predetermined query frequency threshold; and

create the value index table based on the value table, the value index table excluding the value of the full information attribute for the Kubernetes pod instance.

14 . The system of claim 8 , wherein the predetermined size threshold is 64 kilobytes, and wherein the predetermined query frequency threshold is 50 queries per second.

15 . A non-transitory computer-readable medium comprising processor-executable instructions configured to cause one or more processors to:

access a resource management database, the resource management database comprising a value table storing one or more attribute values corresponding to one or more attributes for one or more resource instances, the one or more resources instance comprising one or more runtime objects representing one or more compute resources;

determine that a size of an attribute value corresponding to an attribute of a resource instance is greater than a predetermined size threshold;

determine that a query frequency associated with the attribute value of the resource instance is less than a predetermined query frequency threshold; and

create a value index table based on the value table, the value index table excluding the attribute value of the resource instance.

16 . The non-transitory computer-readable medium of claim 15 , further comprising processor-executable instructions configured to cause one or more processors to:

update the resource management database by adding the value index table.

17 . The non-transitory computer-readable medium of claim 15 , further comprising processor-executable instructions configured to cause one or more processors to:

query the value index table for the resource instance.

18 . The non-transitory computer-readable medium of claim 15 , wherein the resource management database comprises a resource table, an instance table, and an attribute table, wherein the resource table is configured to record one or more resource types, wherein the instance table is configured to store one or more resource instances corresponding to the one or more resource types, and wherein the attribute table is configured to store one or more attributes for the one or more resource instances.

19 . The non-transitory computer-readable medium of claim 15 , wherein the resource instance is a Kubernetes pod instance, attributes for the Kubernetes pod instance comprises a unique identification attribute and a full information attribute, and wherein a value of the full information attribute for the Kubernetes pod instance is in a JSON string structure.

20 . The non-transitory computer-readable medium of claim 19 , further comprising processor-executable instructions configured to cause one or more processors to:

determine the size of the value of the full information attribute for the Kubernetes pod instance is greater than the predetermined size threshold;

determine the query frequency associated with the value of the full information attribute for the Kubernetes pod instance is less than the predetermined query frequency threshold; and

create the value index table based on the value table, the value index table excluding the value of the full information attribute for the Kubernetes pod instance.

Assignments (2)
CHANGE OF NAME Recorded Jul 14, 2026
From: ZOOM VIDEO COMMUNICATIONS, INC.
To: ZOOM COMMUNICATIONS, INC.
Reel/Frame 075971/0418 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 24, 2024
From: DU, YUANYUAN; XIE, JINGJIN
To: ZOOM VIDEO COMMUNICATIONS, INC.
Reel/Frame 068071/0839 →
Continuity (1)
Related Publication 20260030222A1 · Jan 29, 2026
References Cited (18)
US 6513041B2 · Tarin · 2003 [cited by applicant]
US 11262728B2 · Zhang et al. · 2022 [cited by applicant]
US 12032634B1 · Chen · 2024 [cited by examiner]
US 20120166277A1 · Gnanamani · 2012 [cited by examiner]
US 20150220327A1 · Poon et al. · 2015 [cited by applicant]
US 20170337210A1 · Boehme · 2017 [cited by examiner]
US 20210034598A1 · Arye et al. · 2021 [cited by applicant]
US 20220027335A1 · Bo · 2022 [cited by examiner]
US 20220269656A1 · Verma · 2022 [cited by applicant]
US 20240289993A1 · Liang · 2024 [cited by examiner]
US 20250021231A1 · Gangadhar · 2025 [cited by examiner]
Invitation to Pay Additional Fees for PCT/US2025/036752 mailed Nov. 7, 2025. [cited by applicant]
JovanPop, “Designing Product Catalogs in SQL Server Blog using JSON”, https://techcommunity.microsoft.com/blog/sqlserver/designing-product-catalogs-in-sql-server-using-json/384594, Mar. 23, 2019; pp. 1-5. [cited by applicant]
Anonymous, “Entity-attribute-value model—Wikipedia”, https://en.wikipedia.org/w/index.php?title=Entity-attribute-value_ model&oldid=623968433, Sep. 3, 2014; pp. 1-17. [cited by applicant]
Lesigang, “Read any JSON into list of key-value pairs (EAV format) in SQL Server”, https://stackoverflow.com/questions/61800927/read-any-Json-into-list-of-key-value-pairs-eav-format-in-sql-server, Jun. 20, 2020; pp. 1-7. [cited by applicant]
Final Office Action for U.S. Appl. No. 18/782,704 mailed Nov. 7, 2025. [cited by applicant]
U.S. Appl. No. 18/782,582 , Final Office Action, Mailed on Jan. 15, 2026, 18 pages. [cited by applicant]
Application No. PCT/US2025/036752 , International Search Report and Written Opinion, Mailed on Jan. 8, 2026, 17 pages. [cited by applicant]