# US 2025/0094069 A1 · Metrics data storage and access > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0094069 A1 - Document ID: US20250094069A1 - Status: Published application - Kind: A1 - Application number: 18/469,650 - Filed: 2023-09-19 - Published: 2025-03-20 - Earliest claimed: 2023-09-19 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Hui Li; Xia Yu; Zhen Zhang - Web page: https://patentgrep.com/patent/US20250094069A1 ## CPC - G06F 3/064: {Management of blocks} - G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]} - G06F 3/0622: {in relation to access} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Methods, systems, and computer-readable storage media for receiving metric data of a cloud system periodically; transforming the metric data of each type into a byte array using mapping tables, wherein the byte array is an encoded format of the metric data, where each field of the metric data is encoded as a field ID and a field type ID that are short integer variables; merging and storing the byte arrays of multiple metric data into a binary file, wherein the binary file comprises multiple blocks with each block comprising multiple byte arrays; generating indexes for common fields of different metric data in the binary file; receiving a retrieval request requesting metric records including a common field of a particular value; determining storage locations of one or more metric records satisfying the retrieval request; and obtaining the one or more metric records from the binary file using the corresponding storage locations. ## Claims ### Claim 1 A computer-implemented method for metric data management, the method being executed by one or more processors and comprising: receiving metric data of a cloud system periodically, wherein the metric data comprises a plurality of fields; transforming the metric data of each type into a byte array using mapping tables, wherein the byte array is an encoded format of the metric data, where each field of the metric data is encoded as a field ID and a field type ID that are short integer variables; merging and storing the byte arrays of multiple metric data into a binary file, wherein the binary file comprises multiple blocks with each block comprising multiple byte arrays; generating indexes for common fields of different metric data in the binary file; receiving a retrieval request requesting metric records including a common field of a particular value; determining storage locations of one or more metric records satisfying the retrieval request using the index of the common field; and obtaining the one or more metric records satisfying the retrieval request from the binary file using the corresponding storage locations. ### Claim 2 (depends on 1) The method of claim 1, further comprising: redefining each field included in the metric data in the mapping tables. ### Claim 3 (depends on 2) The method of claim 2, wherein redefining each field comprises: mapping a field name of the field into a field ID in a first mapping table; and mapping a data type of the field into a field type ID in a second mapping table. ### Claim 4 (depends on 3) The method of claim 3, wherein the field ID is a short integer variable representing the field name, and the field type ID is a second short integer variable representing the data type of the field. ### Claim 5 (depends on 1) The method of claim 1, wherein the byte arrays in the binary file are ordered by corresponding time stamps. ### Claim 6 (depends on 1) The method of claim 1, wherein the index of a common field is included in i) an offset table comprising a position offset of each matching metric record in the binary file, and ii) a key table indicating a number of matching metric records for each particular value and a stating location of the number of metric records in the offset table. ### Claim 7 (depends on 1) The method of claim 1, wherein the index of a common field indicates a storage location of a metric record included in the binary file that matches the particular value of the common field. ### Claim 8 A non-transitory computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for metric data management, the operations comprising: receiving metric data of a cloud system periodically, wherein the metric data comprises a plurality of fields; transforming the metric data of each type into a byte array using mapping tables, wherein the byte array is an encoded format of the metric data, where each field of the metric data is encoded as a field ID and a field type ID that are short integer variables; merging and storing the byte arrays of multiple metric data into a binary file, wherein the binary file comprises multiple blocks with each block comprising multiple byte arrays; generating indexes for common fields of different metric data in the binary file; receiving a retrieval request requesting metric records including a common field of a particular value; determining storage locations of one or more metric records satisfying the retrieval request using the index of the common field; and obtaining the one or more metric records satisfying the retrieval request from the binary file using the corresponding storage locations. ### Claim 9 (depends on 8) The non-transitory computer-readable storage medium of claim 8, wherein the operations further comprise: redefining each field included in the metric data in the mapping tables. ### Claim 10 (depends on 9) The non-transitory computer-readable storage medium of claim 9, wherein redefining each field comprises: mapping a field name of the field into a field ID in a first mapping table; and mapping a data type of the field into a field type ID in a second mapping table. ### Claim 11 (depends on 10) The non-transitory computer-readable storage medium of claim 10, wherein the field ID is a short integer variable representing the field name, and the field type ID is a second short integer variable representing the data type of the field. ### Claim 12 (depends on 8) The non-transitory computer-readable storage medium of claim 8, wherein the byte arrays in the binary file are ordered by corresponding time stamps. ### Claim 13 (depends on 8) The non-transitory computer-readable storage medium of claim 8, wherein the index of a common field is included in i) an offset table comprising a position offset of each matching metric record in the binary file, and ii) a key table indicating a number of matching metric records for each particular value and a stating location of the number of metric records in the offset table. ### Claim 14 (depends on 8) The non-transitory computer-readable storage medium of claim 8, wherein the index of a common field indicates a storage location of a metric record included in the binary file that matches the particular value of the common field. ### Claim 15 A system, comprising: a computing device; and a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations for metric data management, the operations comprising: receiving metric data of a cloud system periodically, wherein the metric data comprises a plurality of fields; transforming the metric data of each type into a byte array using mapping tables, wherein the byte array is an encoded format of the metric data, where each field of the metric data is encoded as a field ID and a field type ID that are short integer variables; merging and storing the byte arrays of multiple metric data into a binary file, wherein the binary file comprises multiple blocks with each block comprising multiple byte arrays; generating indexes for common fields of different metric data in the binary file; receiving a retrieval request requesting metric records including a common field of a particular value; determining storage locations of one or more metric records satisfying the retrieval request using the index of the common field; and obtaining the one or more metric records satisfying the retrieval request from the binary file using the corresponding storage locations. ### Claim 16 (depends on 15) The system of claim 15, wherein the operations further comprise: redefining each field included in the metric data in the mapping tables. ### Claim 17 (depends on 16) The system of claim 16, wherein redefining each field comprises: mapping a field name of the field into a field ID in a first mapping table; and mapping a data type of the field into a field type ID in a second mapping table. ### Claim 18 (depends on 17) The system of claim 17, wherein the field ID is a short integer variable representing the field name, and the field type ID is a second short integer variable representing the data type of the field. ### Claim 19 (depends on 15) The system of claim 15, wherein the byte arrays in the binary file are ordered by corresponding time stamps. ### Claim 20 (depends on 15) The system of claim 15, wherein the index of a common field is included in i) an offset table comprising a position offset of each matching metric record in the binary file, and ii) a key table indicating a number of matching metric records for each particular value and a stating location of the number of metric records in the offset table.