BUSINESS PROPOSAL · CONFIDENTIAL IOT CLOUD SERVICE

Global Device Cloud Service Business Proposal

Device Control Commands · Streaming Media · Alarm Cloud Storage

TABLE OF CONTENTS

  1. Overview & Service Modules — Value proposition & core modules
  2. Global Infrastructure — Four public cloud regions & special markets
  3. Deployment Modes — Public cloud integration / private deployment
  4. Modular Combinations — Four typical scenarios
  5. Commercial Model — Pricing dimensions & Africa market strategy
  6. Engagement & Commitment — End-to-end engagement path
01

Overview & Service Modules

OVERVIEW & MODULES

This proposal provides IoT device cloud services to customers worldwide, covering three core capabilities — device remote control, audio/video streaming delivery, and alarm event cloud storage — helping customers rapidly build a stable, compliant, and scalable device cloud service system.

Based on their business scale, data security requirements, and compliance needs, customers can flexibly choose between Public Cloud Integration or Private Deployment. The three service modules are fully decoupled, allowing customers to independently select the deployment mode for each module and combine them freely — "one proposal, deployed globally."

Service Modules

Service ModuleDescriptionDeployment Options
Device Control Commands Remote device control, state synchronization, and command delivery, supporting control scenarios with strict real-time requirements. Public Cloud  Private
Streaming Media Server Real-time audio/video streaming, transcoding, and distribution, adapting to different terminals and bandwidths while supporting massive concurrency. Public Cloud  Private
Alarm Cloud Storage Alarm event recording, snapshot/video storage, search and playback, meeting security event traceability and retention requirements. Public Cloud  Private
The three modules are fully decoupled — customers can independently choose the deployment mode for each module and combine them freely without mutual impact.
02

Global Infrastructure

GLOBAL INFRASTRUCTURE

2.1 Standard Public Cloud Nodes (Four Regions)

RegionNode LocationCoverageCompliance
Chinese Mainlandlocal data centerMainland China & compliant overseas businessData Security Law & Personal Information Protection Law
North AmericaNorth America data centerUSA, Canada, MexicoUS data compliance requirements
EuropeFrankfurt, GermanyAll EU countriesGDPR compliance
Southeast AsiaSingapore / SEA nodesSoutheast Asian countriesLocal data protection regulations

2.2 Special Markets (Private Deployment)

For special markets with mandatory data localization regulations or data sovereignty requirements (e.g., Korea's PIPC requirements and Iran's data non-export requirement), private deployment is adopted — the customer bears the one-time deployment fee and provides server hardware. For details on applicable conditions, service scope, and responsibility allocation, see Section 3: Deployment Modes.

03

Deployment Modes

DEPLOYMENT MODES
Mode 1: Public Cloud Integration (Default)
Target Customers
  • No mandatory data localization compliance requirements
  • Seek fast time-to-market with low initial investment
  • Accept data stored in the corresponding regional public cloud node
Service Scope
  • All three modules onboarded to our public cloud
  • Data stored at the node of the customer's region
  • Strict isolation between regions — no cross-border data transfer
  • Automatic version updates, security patches, and O&M support
Key Advantages
  • Zero infrastructure investment
  • Fast onboarding(integration within days)
  • Fully managed O&M — no IT burden for the customer
Mode 2: Private Deployment
Target Customers
  • Subject to mandatory data localization compliance regulations (e.g., special markets like Korea and Iran)
  • Extremely high data security requirements — no data may leave the country
  • Willing to bear server hardware and independent deployment costs
Service Scope
  • Complete software package deployed on customer-designated servers
  • Private deployment scope selectable per module (all or partial)
  • Customer retains full control of the data
  • Deployment documentation, interface specifications, and technical support
Responsibility Allocation
  • Customer: provide servers and network environment meeting performance requirements; bear the one-time deployment fee; maintain underlying hardware and network
  • Us: software deployment and configuration; version upgrade packages; remote technical support and troubleshooting; periodic security patches
04

Modular Combinations

MODULAR COMBINATIONS

Four typical combinations are shown below; customers can customize freely based on their actual business scenarios.

ScenarioDevice ControlStreamingAlarm StorageDescription
Standard Public Cloud Public Public Public Default option, most cost-effective
Hybrid Mode A Public Private Public Streaming localized only; ideal for bandwidth-constrained scenarios
Hybrid Mode B Private Public Private Control and data local; streaming distributed via public cloud
Fully Private Private Private Private Data never leaves the country — highest security level
05

Commercial Model

COMMERCIAL MODEL

5.1 Public Cloud Integration Pricing Dimensions

Billing DimensionDescription
Number of Connected DevicesTiered pricing based on active device count
Concurrent Streaming SessionsBilled by simultaneous online streaming channels
Alarm Storage CapacityBilled by retention period and storage capacity
Value-added ServicesOptional add-ons such as CDN acceleration and AI analytics

5.2 Private Deployment Pricing Dimensions

Fee ItemDescription
Independent Deployment FeeOne-time fee covering software license and deployment implementation
Annual Maintenance FeeCharged as a percentage of the deployment fee, covering upgrades and technical support
Customization FeeCustom requirements are quoted separately by project
Travel ExpensesOn-site implementation is reimbursed at cost

Note: For private deployment, the specific responsibility boundary between customer and vendor is defined in Section 3: Deployment Modes.

5.3 Africa Market Strategy

Customer ProfileRecommended OptionService NodeUpgrade Path
Small volume + public cloud acceptable Public Cloud Allocated to SEA or North America nodes based on geography Upgradeable anytime
Small volume + high security needs Private Deployment Customer's local servers —
Large volume (reaches build threshold) Trigger Africa Node Build New local Africa node Long-term operation
Node allocation principle: SEA nodes give priority to East and Central Africa customers; North America nodes give priority to West and South Africa customers. Final allocation is determined dynamically based on network routing quality in the customer's country and existing capacity.
Node build triggers: Local node construction starts when any of the following is met by cumulative Africa customers: ① total connected devices reaches the agreed threshold; ② total contract value reaches the agreed threshold; ③ a single customer commits a minimum purchase volume. Specific thresholds are determined through commercial negotiation and are flexible.
06

Engagement & Commitment

ENGAGEMENT & COMMITMENT

6.1 Engagement Process

1
Requirement Discovery
Business scale, compliance needs, deployment mode
→
2
Solution Confirmation
Module mix, node allocation, commercial quote
→
3
Contract Signing
SLA, responsibility boundary, delivery scope
→
4
Onboarding & Go-Live
Public cloud in days / private deployment delivery
→
5
Operations & Support
Monitoring, upgrades, scaling optimization

6.2 Service Commitments

✔ Data compliance: Strict isolation between regions with no cross-border transfer; private deployment data never leaves the country.
✔ Fast onboarding: Public cloud integration completed within days; standard deployment documentation and remote support for private deployment.
✔ Sustained support: Regular version updates and security patches, 7×24 technical support and troubleshooting.
✔ Flexible scaling: Clear upgrade paths for module combinations and nodes, evolving elastically with business scale.