A multi-garden SaaS-based intelligent cemetery tenant isolation and elastic scaling processing method and system

By implementing tenant isolation between the service layer and the data layer in the smart cemetery microservice system, and generating a lightweight prediction model by combining the tomb sweeping business calendar and historical traffic data, the problems of resource contention, data mixing, and fault propagation under the shared deployment of multiple cemeteries are solved. Tenant-level elastic scaling and rapid activation are achieved, improving system stability and data security.

CN123123383APending Publication Date: 2026-11-17WENZHOU XIAODAO TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611267556.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-20
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The existing smart cemetery microservice system lacks a tenant isolation mechanism in multi-cemetery SaaS shared deployment scenarios, which leads to resource contention, data mixing, fault propagation, complex and costly implementation, and difficulty in meeting the unified management needs of multiple parks. In particular, during peak tomb-sweeping periods, inaccurate traffic prediction can cause system lag and data leakage.

Method used

The system adopts a multi-park SaaS-based smart cemetery tenant isolation and elastic scaling approach. Through two-level tenant isolation at the service layer and data layer, and by combining the tomb sweeping business calendar and historical traffic data to generate a lightweight prediction model, it achieves tenant-level resource isolation, elastic scaling and fault isolation, and supports the rapid activation of new tenants.

Benefits of technology

It achieves data security and resource independence for multiple cemeteries, reduces the risk of system lag, improves platform stability and availability, supports the rapid opening of new cemeteries, adapts to the traffic characteristics of tomb sweeping business, and reduces the risk of system lag during peak periods.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123383A_ABST
    Figure CN123123383A_ABST
Patent Text Reader

Abstract

This invention discloses a method and system for tenant isolation and elastic scaling in a multi-park SaaS-based smart cemetery, belonging to the technical field of smart cemetery informatization and microservice SaaS cloud platform. Addressing the industry pain points of existing smart cemetery systems, such as high deployment costs across multiple parks, peak traffic contention during tomb-sweeping seasons, weak multi-tenant data isolation, and wide fault propagation, this invention constructs a two-level tenant isolation architecture at the service and data layers, assigning each cemetery an independent tenant ID and tenant metadata. Combining the tomb-sweeping business calendar and historical traffic data, a weighted time-series prediction model incorporating business calendar features is used to construct a tenant traffic prediction model, enabling independent elastic scaling at the tenant level. Simultaneously, it implements tenant-level fault circuit interruption isolation and a rapid new tenant activation mechanism. This invention can completely isolate business resources, data resources, and fault risks between multiple cemeteries, adapting to high-concurrency scenarios during Qingming Festival, Winter Solstice, and Ghost Festival, significantly reducing the deployment cost of group-based cemetery platforms, enabling the asset-light, large-scale replication of the smart cemetery SaaS model, and improving the overall security, stability, and maintainability of the platform.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the fields of smart cemetery informatization, microservice architecture, and SaaS multi-tenant cloud platform technology, specifically to a method and system for tenant isolation and elastic scaling in a multi-campus SaaS-based smart cemetery. Background Technology

[0002] With the rapid development of digitalization in funeral services and group-based operation of cemeteries, the traditional single-cemetery deployment model is costly, difficult to replicate, and cannot meet the unified management needs of multiple cemeteries. While existing smart cemetery microservice systems can achieve elastic scaling of traffic within a single cemetery, they have significant drawbacks in multi-cemetery SaaS shared deployment scenarios: First, the lack of a tenant isolation mechanism leads to multiple cemeteries sharing a resource pool, causing peak traffic congestion and resulting in system lag and response delays. Second, weak data isolation capabilities result in mixed storage of data from multiple cemeteries, posing risks of cross-tenant data leakage and data obfuscation, failing to meet funeral data security standards. Third, the deployment model is cumbersome; adding a new cemetery requires a complete system deployment, leading to long implementation cycles, high costs, and hindering rapid, asset-light replication. Fourth, the scope of fault propagation is wide; service anomalies in a single cemetery can easily affect the entire platform, resulting in poor system stability.

[0003] Meanwhile, general internet traffic prediction models are not adapted to the characteristics of funeral and memorial services. Memorial services traffic has a strong characteristic of bursts during holidays, and general models have large prediction errors, making it difficult to support the pre-expansion scheduling of memorial services. Therefore, there is an urgent need for a SaaS-based smart cemetery processing solution that supports multi-tenant isolation, tenant-level elastic scaling, rapid activation, fault isolation, and is adapted to the traffic characteristics of memorial services. Summary of the Invention

[0004] The purpose of this invention is to overcome the defects of the existing technology and provide a method and system for tenant isolation and elastic scaling of multi-park SaaS-based smart cemeteries, which solves the technical problems of resource contention, data insecurity, high replication costs, serious fault propagation, and inaccurate prediction of tomb sweeping traffic in multiple cemeteries.

[0005] To achieve the above objectives, the present invention adopts the following technical solution: A method for tenant isolation and elastic scaling in a multi-park SaaS-based smart cemetery includes the following steps: S1: Receive cemetery tenant registration requests, assign an independent tenant ID to each cemetery park, and configure tenant metadata; the tenant metadata includes at least basic park information, a tomb-sweeping business calendar, and tenant resource quotas; S2: Construct a two-level tenant isolation architecture consisting of a service layer and a data layer; the service layer performs routing authentication for different tenant requests; the data layer uses a shared database and independent data tables to complete tenant data isolation; S3: Collect historical tomb-sweeping traffic data for each tenant, combine it with the tomb-sweeping business calendar to mark peak business periods, and use a weighted time-series algorithm that integrates business calendar features to generate a tenant traffic prediction model, outputting the predicted access traffic for future periods; S4: Receive business access requests, parse the tenant ID carried in the request, and route it to the corresponding tenant service instance; based on the traffic prediction model and real-time access metrics, perform elastic scaling scheduling at the tenant level; S5: Monitor the service operation status of each tenant, and when a tenant service anomaly is detected, perform tenant-level fault isolation and high-availability switching.

[0006] Furthermore, the memorial service calendar includes Qingming Festival, Winter Solstice, Ghost Festival, and the park's customized memorial service times.

[0007] Furthermore, the elastic scaling scheduling includes: scaling up microservice instances for target tenants during peak tomb-sweeping periods; reclaiming idle computing resources from tenants during off-peak periods; isolating resource pools of different tenants from each other and prohibiting cross-tenant preemption of computing resources.

[0008] Furthermore, the data layer isolation further includes: each piece of business data carries a tenant ID field, and the tenant ID is forcibly included as a filtering condition during data query to prevent cross-tenant data leakage.

[0009] Furthermore, it also includes a quick activation process for new tenants: after entering the new cemetery tenant's metadata, the tenant's routing configuration and data table set are automatically generated, without the need to completely redeploy the entire system.

[0010] This invention also provides a multi-campus SaaS-based smart cemetery tenant isolation and elastic scaling processing system to implement the above-mentioned methods, including: a tenant management module for receiving cemetery tenant registrations and maintaining tenant IDs and tenant metadata; a tenant isolation module for implementing service layer request routing authentication and data layer tenant data isolation; a traffic prediction module for generating tenant traffic prediction results based on historical traffic and the tomb sweeping business calendar; an elastic scaling scheduling module for executing tenant-level microservice instance scaling based on real-time indicators and traffic predictions; and a tenant fault isolation module for monitoring tenant service status and executing tenant-level fault isolation and switching.

[0011] Furthermore, the system also includes a tenant quick activation submodule, which is used to automatically generate tenant routing configurations and tenant data tables.

[0012] The present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method. Beneficial effects

[0013] Compared with existing technologies, this invention has the following outstanding advantages: 1. It achieves dual tenant isolation at the service layer and data layer, completely eliminating data confusion, data leakage, and resource contention among multiple cemeteries, and meeting the requirements for funeral data security and compliance; 2. It enables tenant-level elastic scaling, allowing a single cemetery to expand independently during peak hours and shrink during off-peak hours without interference, completely solving the problem of mutual congestion and lag during peak periods for shared platforms across multiple cemeteries; 3. It supports tenants to quickly activate their services within minutes, eliminating the need for repeated system deployment and enabling asset-light, replicable, and scalable implementation of cemetery services; 4. It achieves tenant-level fault isolation, preventing single-cemetery faults from spreading and affecting the overall platform, significantly improving the stability and availability of the SaaS platform; 5. It adopts a lightweight calendar-historical time-series fusion prediction model, customizing features for funeral and memorial service scenarios, eliminating the need for high-computing-power deep learning, enabling tenant-level traffic prediction, supporting pre-expansion during peak memorial service periods, and reducing the risk of system lag during peak periods. Detailed Implementation

[0014] The present invention will now be described in further detail with reference to the accompanying drawings.

[0015] like Figure 1 As shown, the method of the present invention includes sequentially executed process modules: 1-tenant registration configuration, 2-two-level tenant isolation, 3-tenant traffic prediction, 4-request routing distribution, 5-tenant granular elastic scaling, and 6-tenant fault isolation switching.

[0016] After a tenant registers in the park, the system assigns a unique tenant ID and binds it to the tomb-sweeping calendar and resource quotas; the system establishes a service layer routing isolation mechanism and a data layer table partitioning isolation mechanism; it combines historical access data and the tomb-sweeping calendar to predict peak traffic; requests are accurately routed based on the tenant ID and scaled up and down independently; in case of anomalies, faulty tenants are individually circuit-broken to ensure the stable operation of the overall platform.

[0017] like Figure 2 As shown, the system architecture of this invention consists of a multi-layered structure, including: 10-Access Layer, 11-Gateway & Tenant Management Module, 12-Tenant Isolation Module, 13-Business Microservice Cluster, 14-Scheduling Module, and 15-Data Storage Layer. External requests enter the gateway through the access layer, where tenant identification and authentication are completed. After isolation by the tenant isolation module, they enter the microservice cluster. The scheduling module uniformly completes traffic prediction, elastic scaling, and fault isolation management. Finally, the data is securely stored in independent data tables for each tenant.

[0018] Step S1: Receive cemetery tenant registration requests, assign a unique tenant ID to each cemetery area, and configure tenant metadata. Specifically, each cemetery area is managed as an independent SaaS tenant. Upon tenant registration, the system assigns a unique tenant ID and establishes tenant metadata. Tenant metadata may include information such as the area name, address, contact person, tomb-sweeping calendar, resource quotas, and service activation status. The tomb-sweeping calendar may include traditional tomb-sweeping events such as Qingming Festival, Winter Solstice, and Ghost Festival, or it may include custom tomb-sweeping event times for the area. Resource quotas may include the maximum configuration of CPU, memory, storage, and the number of microservice instances that the tenant can use.

[0019] Step S2: Construct a two-tiered tenant isolation architecture with service and data layers. This step implements tenant isolation at both the service and data layers. At the service layer, the gateway or unified access module intercepts external requests, parses the tenant ID carried in the request, performs authentication and verification, and routes the request to the corresponding tenant service instance. If the tenant ID is invalid or lacks access permissions, the system can directly intercept the request. At the data layer, tenant data isolation is achieved using a shared database and independent data tables. Each business data record carries a tenant ID field, and all data query operations are forced to include tenant ID filtering conditions, thereby preventing cross-tenant data queries and data leakage.

[0020] Step S3: Collect historical tomb-sweeping traffic data for each tenant, and combine it with the tomb-sweeping business calendar to mark peak business periods, generating a tenant traffic prediction model. The tenant traffic prediction model is a weighted time-series prediction model that integrates business calendar features. The model input feature set includes two types of features: 1) Time business features: tomb-sweeping business calendar tags (ordinary dates / Qingming peak / Winter Solstice peak / Ghost Festival peak / customized sacrificial activity days), number of days offset from the tomb-sweeping node, weekday, and holidays; 2) Historical traffic features: the tenant's past QPS peak, average daily visits, number of booked tomb-sweeping orders, and number of online tomb-sweeping visits during the same tomb-sweeping period.

[0021] The model calculation logic is as follows: The predicted access traffic of a tenant at time t is equal to the calendar feature weight multiplied by the business calendar baseline traffic coefficient, plus the historical time series traffic weight multiplied by the arithmetic mean of the actual traffic at time t of N historical same period tomb sweeping periods.

[0022] The parameters in the formula are as follows: F(t): the tenant's predicted access traffic at time t; Scal(t): the business calendar baseline traffic coefficient; the value is 1 for ordinary dates; the amplification coefficient for peak tomb-sweeping nodes is set according to historical statistics, with the value range of 4 to 8 for Qingming and Winter Solstice peaks, 2 to 4 for Ghost Festival, and 1.5 to 3 for custom tomb-sweeping activities; Wcal: calendar feature weight, with a value range of 0.4 to 0.7; Whis: historical time-series traffic weight, with a value range of 0.3 to 0.6; the sum of the calendar feature weight and the historical time-series traffic weight equals 1; Vi(t): the actual traffic at time t of the i-th historical tomb-sweeping period; N: the number of historical tomb-sweeping period samples selected, generally the most recent 2 to 4 tomb-sweeping periods.

[0023] The model outputs the predicted peak QPS for tenants in future time windows, predicting resource level thresholds in advance. When the predicted QPS is higher than the tenant's preset expansion threshold, a pre-expansion command is triggered; when the predicted QPS is lower than the reduction threshold, a resource reclamation command is triggered.

[0024] Furthermore, the model sets a dynamic correction factor, using the error of the actual traffic over the past 7 days to iteratively correct the calendar feature weights and historical time-series traffic weights. The error equals the absolute value of the predicted traffic and the actual traffic. If the prediction error exceeds 20% for three consecutive time windows, the weight parameters are automatically fine-tuned to allow the model to adapt to the traffic behavior of different cemetery tenants. This model does not require complex deep learning inference, is lightweight, and can be deployed in a microservice scheduling module, making it suitable for low-computing-cost scenarios on cemetery SaaS platforms. A set of weight parameters is configured independently for different cemetery tenants, enabling tenant-level traffic prediction.

[0025] Step S4: Receive business access requests, parse the tenant ID carried in the request, and route it to the corresponding tenant service instance; based on the traffic prediction model and real-time access metrics, perform elastic scaling scheduling at the tenant level. Specifically, after a user request enters the system, it is first routed to the corresponding tenant service instance. The system collects the tenant's access metrics in real time, including but not limited to QPS, request latency, CPU utilization, memory utilization, and the number of microservice instances. When a peak period for tomb sweeping is predicted to arrive, or when real-time access metrics exceed a preset threshold, the system can scale up microservice instances for that tenant. When traffic subsides, the system can reclaim the tenant's idle computing resources. The resource pools of different tenants are isolated from each other; scaling up tenant A will not consume resources from tenant B, thus avoiding the impact of a peak period for tomb sweeping in one cemetery on the business of other cemeteries.

[0026] Step S5: Monitor the operational status of each tenant's service. When a tenant service anomaly is detected, perform tenant-level fault isolation and high-availability switching. Specifically, the system continuously monitors the operational status of each tenant's service instance. If a tenant service experiences an anomaly, timeout, excessively high error rate, or abnormal resource consumption, the system can trigger tenant-level fault isolation. Fault isolation can include handling methods such as circuit breaking the abnormal tenant service, switching to a standby instance, limiting abnormal traffic, and logging abnormal information. Through tenant-level fault isolation, the impact of a fault can be limited to a single tenant, preventing it from affecting other cemetery tenants.

[0027] Furthermore, this method can also include a rapid activation step for new tenants. When a new cemetery tenant is added, the operations staff enters the new cemetery tenant's metadata, and the system automatically generates the tenant ID, routing configuration, tenant data table, and basic business configuration. This eliminates the need for a complete redeployment of the entire system, thus enabling the new cemetery tenant to go live quickly.

[0028] This embodiment also provides a multi-campus SaaS-based smart cemetery tenant isolation and elastic scaling processing system, including a tenant management module, a tenant isolation module, a traffic prediction module, an elastic scaling scheduling module, and a tenant fault isolation module. The tenant management module receives cemetery tenant registrations and maintains tenant IDs and tenant metadata. The tenant isolation module implements service layer request routing authentication and data layer tenant data isolation. The traffic prediction module generates tenant traffic prediction results based on historical traffic and the cemetery's business calendar. The elastic scaling scheduling module performs tenant-level microservice instance scaling based on real-time metrics and traffic predictions. The tenant fault isolation module monitors tenant service status and performs tenant-level fault isolation and failover. Furthermore, the system may also include a tenant quick activation submodule for automatically generating tenant routing configurations and tenant data tables.

[0029] This embodiment also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, can implement the above-described method steps. Attached Figure Description

[0030] Figure 1 This is a flowchart of the multi-campus SaaS-based smart cemetery tenant isolation and elastic scaling processing method of the present invention; Figure 2 This is an architecture diagram of the multi-campus SaaS-based smart cemetery tenant isolation and elastic scaling processing system of the present invention. Figure 1 Corresponding numbers in the text: 1-Tenant registration configuration; 2-Two-tier tenant segregation; 3-Tenant traffic prediction; 4-Request routing and distribution; 5- Tenant granularity elastic scaling; 6- Tenant fault isolation and handover. Figure 2 Corresponding numbers in the text: 10-Access Layer; 11-Gateway & Tenant Management Module; 12-Tenant isolation module; 13-Business microservice cluster; 14-Scheduling Module; 15-Data storage layer.

Claims

1. A method for tenant isolation and elastic scaling in a multi-campus SaaS-based smart cemetery, characterized in that, Includes the following steps: S1: Receive cemetery tenant registration requests, assign a unique tenant ID to each cemetery area, and configure tenant metadata; the tenant metadata includes at least basic area information, memorial service calendar, and tenant resource quota; S2: Construct a two-tier tenant isolation architecture consisting of a service layer and a data layer; the service layer performs routing authentication for requests from different tenants; the data layer uses a shared database and independent data tables to achieve tenant data isolation; S3: Collect historical tomb-sweeping traffic data for each tenant, combine it with the tomb-sweeping business calendar to mark peak business periods, and generate a tenant traffic prediction model; S4: Receive business access requests, parse the tenant ID carried in the request, and route it to the corresponding tenant service instance; based on the traffic prediction model and real-time access metrics, perform elastic scaling scheduling at the tenant level; S5: Monitors the operational status of each tenant's service. When an abnormality is detected in a tenant's service, it performs tenant-level fault isolation and high-availability switching.

2. The method for tenant isolation and elastic scaling in a multi-campus SaaS-based smart cemetery according to claim 1, characterized in that: The memorial service calendar includes Qingming Festival, Winter Solstice, Ghost Festival, and the park's customized memorial service times.

3. The method for tenant isolation and elastic scaling in a multi-campus SaaS-based smart cemetery according to claim 1, characterized in that: The elastic scaling scheduling includes: scaling up microservice instances for target tenants during peak tomb-sweeping periods; reclaiming idle computing resources from tenants during off-peak periods; isolating resource pools of different tenants and prohibiting cross-tenant preemption of computing resources.

4. The method for tenant isolation and elastic scaling in a multi-campus SaaS-based smart cemetery according to claim 1, characterized in that: The data layer isolation further includes: each piece of business data carries a tenant ID field, and the tenant ID is forcibly included as a filtering condition when querying data to prevent cross-tenant data leakage.

5. The method for tenant isolation and elastic scaling in a multi-campus SaaS-based smart cemetery according to claim 1, characterized in that: It also includes a quick activation process for new tenants: after entering the new cemetery tenant's metadata, the tenant's routing configuration and data table set are automatically generated, without the need to completely redeploy the entire system.

6. A multi-campus SaaS-based smart cemetery tenant isolation and elastic scaling system, characterized in that: The method for implementing any one of claims 1 to 5 comprises: a tenant management module for receiving cemetery tenant registrations and maintaining tenant IDs and tenant metadata; a tenant isolation module for implementing service layer request routing authentication and data layer tenant data isolation; a traffic prediction module for generating tenant traffic prediction results based on historical traffic and the tomb sweeping business calendar; an elastic scaling scheduling module for performing tenant-level microservice instance scaling based on real-time metrics and traffic predictions; and a tenant fault isolation module for monitoring tenant service status and performing tenant-level fault isolation and switching.

7. The multi-campus SaaS-based smart cemetery tenant isolation and elastic scaling processing system according to claim 6, characterized in that: It also includes a tenant quick activation submodule, which is used to automatically generate tenant routing configurations and tenant data tables.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.