Definition
Multi-tenant Parking SaaS and Card Pool Isolation refers to a set of parking cloud platform software serving multiple independent clients (property companies, subsidiaries of urban investment companies, franchisees, individual parking lot owners) simultaneously. Data and configurations are isolated at the application layer through tenant IDs; at the cellular IoT layer, IoT SIM cards, data pools, APNs, and billing accounts of different tenants need to be separated from each other to prevent A tenant's device call records and traffic from being counted under B tenant, or directed addresses incorrectly pointing to another tenant's MQTT cluster. Card pool isolation is multi-tenancy at the communication layer, equally important as application-level multi-tenancy; otherwise, issues such as cost transfer, compliance liability, and SLA disputes may arise.
Parking SaaS Often packaged as "software subscription + card procurement agent + operations and maintenance." On the operator side, a master pool can have multiple logical sub-pools attached. Sub-pools are bound to tenant contracts with capped traffic and unit prices. When new parking lots are connected, batch card issuance should record tenant tags, and when disconnecting, service suspension and recovery should prevent cards from entering the gray market. Under the white-label model, although the user interface shows a sub-brand, the ICCID ownership and real-name entity still need to be clarified in the contract.
Technical Features
Implementation methods include: tenant-resolved accounting using operator BSS customer codes, project/organizational trees on the IoT Connection Management Platform (CMP), including tenant filtering conditions when pulling CDRs via API, and enforcing non-empty ICCID and tenant_id fields in the platform CMDB. Dedicated APNs can be split by tenant to achieve network plane isolation; for shared APNs, TLS and tenant fields in device certificates are relied upon. Multinational or cross-provincial groups need to pay attention to roaming CDR ownership rules and whether sub-pools allow cross-region adjustments.
SimtoLink supports multi-project card pools, tenant-specific billing exports, and exception traffic aggregation alerts by tenant, helping SaaS vendors demonstrate verifiable communication gross margins during financing due diligence and audits. When combined with hardware SKUs such as barriers or parking locks, it is recommended to write tenant pre-binding information at factory programming to reduce configuration errors on-site.
Use Cases
Applicable to chain parking platforms, city-level parking internet operators, and hardware manufacturers transitioning to operation services — basically a business model of "one platform, thousands of parking lots." When card pool isolation is linked with tenant-level SLAs (availability, card replacement timeliness), it can be included as an attachment in the partnership contract.
During the product iteration phase, if the new tenant defaults to the activation of a 'shared test card pool,' it must be physically or logically isolated from the production pool to prevent debugging traffic from affecting production billing; in the event of mergers or tenant contract termination, a card recovery checklist and data export obligations should be carried out to avoid the original tenant's devices still pointing to an invalid platform domain, causing long-term invalid registrations.
When expanding internationally, differences in real-name verification and roaming regulations among various countries' operators will directly affect card pool design: if the domestic CMP unified procurement is followed, the contract must stipulate cross-border data compliance and call record currency conversion; customers with multi-currency settlement should require connected service providers to provide itemized reports by tenant and by country to prevent consolidated reports from obscuring losses in individual regions.
The security incident response process should specify: once a tenant is suspected of unauthorized access to another tenant's card management API, the relevant keys must be immediately frozen, certificates rotated, and both parties' data protection contacts notified, while retaining call records and audit logs for reference.