Abstract: The present disclosure relates to a system (108) and a method (600) for managing building data. The system (108) includes a user interface (UI) (206) configured to receive an application program interface (API) request containing viewport details and transmit the API request to one or more web servers (304) through a load balancer (402). The one or more web servers (304) are configured to forward the API request to a microservice server (306). The microservice server (306) is configured to extract viewport details from the API request, convert the viewport details into one or more tile identifiers (Tile IDs), and transmit the viewport details to a distributed data storage (308). The distributed data storage (308) is configured to retrieve building data using the one or more Tile IDs and transmit the retrieved building data to the microservice server (306). FIG. 3
WE CLAIM:
1. A method (600) for managing building data, the method (600) comprising
of steps:
5 receiving (602), by a user interface (UI) (206), an application
program interface (API) request, wherein the API request includes viewport
details;
transmitting (604), by the UI (206), the API request to one or more
web servers (304) through a load balancer (402);
10 forwarding (606), by the one or more web servers (304), the API
request to a microservice server (306);
extracting (608), by the microservice server (306), the viewport
details from the API request and converting the viewport details to one or
more tile identifiers (Tile IDs);
15 transmitting (610), by the microservice server (306), the viewport
details to a distributed data storage (308);
retrieving (612), by the distributed data storage (308), the building
data using the one or more Tile ID(s); and
transmitting (614), by the distributed data storage (308), the
20 retrieved building data to the microservice server (306).
2. The method (600) as claimed in claim 1, further comprising:
transmitting, by the microservice server (306), the retrieved building
data to the one or more application servers (404);
transmitting, by the one or more application servers (404), the
25 retrieved building data to the one or more web servers (304); and
33
transmitting, by the one or more web servers (304), the retrieved
building data to the user interface (UI) (206).
| # | Name | Date |
|---|---|---|
| 1 | 202421021577-STATEMENT OF UNDERTAKING (FORM 3) [21-03-2024(online)].pdf | 2024-03-21 |
| 2 | 202421021577-PROVISIONAL SPECIFICATION [21-03-2024(online)].pdf | 2024-03-21 |
| 3 | 202421021577-FORM 1 [21-03-2024(online)].pdf | 2024-03-21 |
| 4 | 202421021577-FIGURE OF ABSTRACT [21-03-2024(online)].pdf | 2024-03-21 |
| 5 | 202421021577-DRAWINGS [21-03-2024(online)].pdf | 2024-03-21 |
| 6 | 202421021577-FORM-26 [26-03-2024(online)].pdf | 2024-03-26 |
| 7 | 202421021577-ORIGINAL UR 6(1A) FORM 26-120624.pdf | 2024-06-20 |
| 8 | 202421021577-Proof of Right [24-07-2024(online)].pdf | 2024-07-24 |
| 9 | 202421021577-ORIGINAL UR 6(1A) FORM 1-090824.pdf | 2024-08-16 |
| 10 | 202421021577-Power of Attorney [12-02-2025(online)].pdf | 2025-02-12 |
| 11 | 202421021577-FORM-5 [12-02-2025(online)].pdf | 2025-02-12 |
| 12 | 202421021577-DRAWING [12-02-2025(online)].pdf | 2025-02-12 |
| 13 | 202421021577-Covering Letter [12-02-2025(online)].pdf | 2025-02-12 |
| 14 | 202421021577-CORRESPONDENCE-OTHERS [12-02-2025(online)].pdf | 2025-02-12 |
| 15 | 202421021577-COMPLETE SPECIFICATION [12-02-2025(online)].pdf | 2025-02-12 |
| 16 | Abstract.jpg | 2025-03-18 |
| 17 | 202421021577-FORM 18 [15-07-2025(online)].pdf | 2025-07-15 |