Use separate decisions for telecom network access, radio equipment, radio station deployment and preinstalled apps. A connected product can trigger more than one route.
Start with the finished model's public-network function, transmitters, frequency bands, antenna, power, deployment and software. Then use the focused answers below to build the required evidence.
There is no single China approval for every connected device. A review covers separate decisions for a telecom equipment , for transmitting equipment, any tied to deployment, and app duties. These routes use different scope tests, and a product can need several of them. Start with the finished model and China build, record each conclusion separately, and reopen the review when hardware, software, antenna, power, network function or deployment changes.
Browse sub-FAQs
Choose the question set you need
These focused FAQ modules break this artifact into narrower answer sets so teams can move straight to the right source-backed guidance.
For network access, ask whether the finished product connects to a public telecom network, falls within telecom terminal, radio communication or interconnection equipment, and appears in MIIT's current equipment directory. MIIT's reforms effective 1 March 2023 removed 11 named legacy equipment types from new permit approval and added satellite internet and functional-virtualization equipment.
For radio management, inventory every transmitter, band, output power, antenna and intended use. Model approval generally applies to radio transmitting equipment unless a specific exception is met. A requires an exact match to MIIT Announcement 2019 No. 52 and compliance with its technical and use conditions; it does not waive unrelated network-access or product duties.
For deployment, check a station licence separately from model approval. Under the 2400/5800 MHz notice, a provincial licence is triggered for specified access-point, central-station or point-to-point deployments only when the station is outdoors and its EIRP exceeds the stated band threshold.
For preinstalled apps, first decide whether the product is a : it connects to a public mobile communications network, has an operating system, and lets users install and uninstall apps. The terminal manufacturer controls the preinstalled build and sales channel; an app-distribution platform has review and traceability duties; a billing provider keeps confirmation and source billing data.
Public-network route: current equipment-directory classification, permit or trial-approval route, applicant, testing and approved-model controls.
Radio equipment route: bands, RF and antenna configuration, technical limits, model approval or exact micro-power rationale.
Deployment route: indoor or outdoor use, station type, EIRP, location and any .
Software route: scope, controlled app inventory, disclosure and consent, uninstallability, upgrade behavior and platform records where applicable.
Use one route matrix to show the status of each decision, but keep the supporting evidence separate. The matrix should identify the product and configuration, source version, conclusion, responsible owner, open questions, approval identifier, expiry or review date, and change triggers.
For a covered network-access application, the current MIIT guide requires Chinese application and corporate records, quality and after-sales evidence, a product description, and an accepted test report or product certificate. Wireless communication, interconnection and new telecom equipment also require a technical plan and at least three months of network-trial evidence. Foreign manufacturers apply through a Chinese agent. A permit is generally valid for three years; the 2023 reform gives a trial approval a two-year validity period, and continued production and sale require a renewal application three months before permit expiry.
For mobile smart terminals, keep the app inventory and disclosure, consent, uninstall and upgrade tests tied to the approved software build. The manufacturer must keep preinstalled software consistent before and after network approval and report a newly added preinstalled app or major functional change to MIIT in a timely manner.
Network access file: directory decision, application materials, test and trial evidence, correspondence, permit or trial approval, new network-access mark and change filings.
Radio file: block diagram, bands, power, antenna and firmware configuration, technical tests, model approval or micro-power rationale, and station-licence decision.
App file: controlled preinstalled-app inventory, user disclosures, consent flows, uninstall and upgrade tests, network-access consistency, platform traceability and billing records only where those roles exist.
Change control: reassess modifications to main functions, core components, transmitter parameters, antenna, software build, preinstalled apps, network connection or deployment.
Establishes manufacturer, platform and billing evidence, including software consistency, at least 60 days of platform traceability and five months of billing records where applicable.