Cloud · 03 Editorial guide
Cloud, Internet Data Centre and CDN Services in China
Cloud is a product description, not a licence category. Map compute, storage, deployment, delivery, network and managed-service functions to the current catalogue, then identify who owns or controls infrastructure, contracts with customers and operates the service.
First job Draw the service, infrastructure, entity and data flows before selecting a licence or partner model.
Start here
Key considerations
The first questions are about urgency, governance and preservation — before collection expands or interviews begin.
- What compute, storage, delivery or managed functions are supplied?
- Where is infrastructure located and who controls it?
- Which entity contracts, invoices and supports customers?
Direct answer
What this page decides
02
Cloud is not a standalone exemption from China telecom licensing. Classification depends on what the provider supplies and controls. Hosting space, cabinets, bandwidth, server leasing, virtualised compute and storage can fall within internet data centre services; traffic acceleration through distributed nodes can fall within CDN services; internet connectivity can engage ISP rules; and application or transaction layers may trigger additional VATS items. Separate the physical facility owner, network carrier, licensed IDC or CDN operator, cloud technology provider, marketplace or reseller, contracting entity and customer-support entity. For every layer, verify the licence item, approved geography, infrastructure and resource rights, customer contract and actual service. A downstream party does not inherit an upstream provider's licence merely by buying capacity. Foreign providers must also test ownership restrictions, the licensed-partner model and any location-specific MIIT pilot route.
At a glance
Which fact changes the next route
Use the fact that changes ownership or urgency to decide the next move.
| Question | Why it matters | Next route |
|---|---|---|
| What cloud layer is supplied? | Colocation, virtual compute, storage, acceleration, connectivity and managed applications can map to different licence items. | Separate infrastructure, platform, software and managed-service functions. |
| Who controls the infrastructure and users? | Ownership of servers is not decisive if another entity provisions resources, sets terms, bills customers and manages accounts. | Map operational control and customer responsibility by entity. |
| Is capacity being resold? | Buying licensed capacity does not automatically authorise repackaging it as the buyer's own regulated service. | Test wholesale rights, branding, pricing, support and end-user contracting. |
| Where are facilities, nodes and customers? | Licence scope and approving authority depend on the regulated service's geographic coverage. | Plot data centres, CDN nodes, network resources and service territory. |
| Is there a foreign-provider model? | Technology licensing, branding or a partner arrangement cannot substitute for ownership and operating-permission analysis. | Compare partner, joint-venture and approved pilot routes. |
Scope
What this page owns — and what it does not
Practical workflow
Action, evidence, legal gate, output
| Action | Documents / evidence | Legal gate | Output |
|---|---|---|---|
| Decompose the service stack | Product catalogue, architecture, provisioning screens, SLAs, pricing and support model | Separate facility, network, compute, storage, acceleration, platform and application functions | Layered service inventory |
| Map assets, resources and control | Facility leases, server ownership, racks, bandwidth, IP resources, CDN nodes and orchestration rights | Identify who possesses, controls and may lawfully supply each resource | Infrastructure and control map |
| Classify licensed roles | Service flows, customer terms, upstream agreements and catalogue definitions | Test IDC, CDN, ISP, ICP and other VATS items separately | Entity-by-function licence matrix |
| Verify licences and geography | Licence copies, annexes, public records, facility and node list, customer coverage | Match business item, holder, territory and production deployment | Scope and gap report |
| Test partner and resale model | Wholesale, agency, reseller, branding, billing, support and audit terms | Ensure roles reflect reality and do not imply borrowed permission | Contract and responsibility allocation |
| Assess ownership and market access | Ultimate ownership, control rights, IP licence, JV or partner arrangements and pilot location | Apply national foreign-investment rules and any approved pilot conditions | Market-access route |
| Build operating and exit controls | Security schedule, incident plan, SLA, portability, backups, transition, reporting and change process | Preserve user service, regulator access and lawful transition | Launch and lifecycle control plan |
Documents
What to gather before the next call
These items help clarify the file; they are not a legal requirement list.
| Item | Why needed | Who holds it | Risk if missing |
|---|---|---|---|
| Layered architecture and service inventory | Shows which technical functions are actually supplied | Engineering, product and legal | Cloud branding hides IDC, CDN, ISP or platform activity |
| Asset and network-resource register | Identifies ownership, location, control and supply rights | Infrastructure and network teams | Resources are used outside provider or licence scope |
| Entity and licence matrix | Matches each function and geography to the responsible licensed operator | Regulatory and corporate teams | One licence is assumed to cover the whole stack |
| Upstream and reseller agreements | Defines capacity, resale, branding, customers, security and audit rights | Procurement, sales and legal | The contract label conflicts with actual operation |
| Customer terms and SLA | Allocates service, availability, data, support, suspension and remedy obligations | Commercial, operations and legal | Promises exceed infrastructure or licensed capability |
| Continuity and exit plan | Protects users and data through outage, licence change or provider transition | Operations, security and compliance | No lawful or practical migration path |
Common failure points
Where files usually break
Calling a service cloud or SaaS and skipping the underlying IDC, CDN, ISP or other VATS functions.
Assuming that ownership of hardware determines the operator while another entity provisions, contracts and bills the service.
Reselling licensed carrier or data-centre capacity under the reseller's own service without analysing its operating role.
Checking a vendor's licence item but not its holder, geographic coverage, facilities, nodes or current public record.
Using contracts that describe agency while pricing, branding, support and liability show independent service operation.
Treating a foreign technology or trademark licence as a substitute for telecommunications market-access approval.
Launching new nodes, regions or service layers without updating the licence, contracts, security allocation and exit plan.
FAQ
Narrow follow-ups owned by this page
Is every cloud service an IDC service?
No. Classification depends on the supplied layer and control. Infrastructure compute and storage may fall within IDC, while applications or transaction functions can engage other catalogue items.
Can a company resell a licensed provider's cloud capacity?
A genuine agency or resale model still requires analysis of who operates the service. Contracting, branding, pricing, provisioning, billing, support and responsibility all matter.
Does a national IDC licence cover CDN?
No. IDC and CDN are distinct catalogue items. The holder needs the correct approved business item and geography for the service actually supplied.
Can a foreign cloud provider operate through a local partner?
A compliant structure may allocate licensed operation to an eligible local entity, but the documents and technical reality must align. The 2024 pilot provides another route only within its approved scope and locations.
Decision map
Keep the question bounded.
- Draw the architectureShow facilities, compute, storage, CDN, network, control plane, support and data flows.
- Allocate operating rolesIdentify asset owner, licence holder, platform operator, contracting party and support provider.
- Classify regulated functionsTest IDC, internet resource collaboration, CDN and other supplied functions without relying on the cloud label.
- Control access and deploymentVerify ownership route, approved geography, contracts, data obligations and change triggers before launch.
Quick answers
Need the short version? Start with one narrow question.
These explainers answer one question. They do not replace this topic route or a deep guide.
Curated resources
Open the asset that matches this job.
Cloud Computing in China
IDC and internet-resource-collaboration licensing, foreign-provider routes, architecture, data and contracts.
China ICP, VATS & Telecom Licensing Guide
Service classification, ICP filing, VATS catalogue items, foreign-investment access and operating-route analysis.
Telecommunications Business Classification Catalogue
Official MIIT catalogue used to classify basic and value-added telecommunications service functions.
Foreign-invested telecommunications enterprise provisions
Official rules governing foreign-invested telecommunications operators, subject to current catalogue and pilot measures.
PRC Telecommunications Regulations
Official administrative regulation establishing telecom service classification, licensing, provincial and cross-regional approval routes, operating obligations and supervision.
Measures for Administration of Telecommunications Business Operating Licences
Official MIIT rules covering licence types, approving authorities, application evidence, use, changes, reporting, security duties and cessation.
MIIT Notice on the VATS Foreign-Investment Opening Pilot
Official 2024 pilot notice removing foreign-equity-ratio limits for specified VATS items in approved areas, subject to pilot scope and MIIT trial approval.
Helpful to prepare
Facts that make the next conversation clearer.
These items are orientation aids, not a legal requirement list.
Counsel hand-off
What to bring when you instruct
Bring the full cloud service catalogue, layered architecture, provisioning and account-control model, facility and node map, servers, racks, bandwidth, IP and network-resource records, customer geography, every operator licence and annex, upstream carrier and data-centre contracts, reseller and marketplace agreements, customer terms and SLAs, branding, pricing and billing flows, ultimate ownership and control chart, foreign IP and technology arrangements, data and security schedules, incident and continuity plans, rollout roadmap and exit or migration design.
Local context
Add location only when the filing or pilot route changes.
National service classification comes first; infrastructure location, filing practice and approved pilots follow.
Open city and province guidesCounsel hand-off
Need technology and telecom counsel?
This hub organises filing, catalogue and operating-route questions. It does not determine licence scope or foreign-investment access on your facts.
Find technology counselLegal review
Who reviewed this guide
Need qualified counsel?
Move carefully. Move with a record.
Use the portal to identify counsel for this practice and related China-side issues.