Malaysia 5G Technical Codes: MTSFB Consultation 2026
Malaysia 5G Technical Codes: MTSFB Opens Public Consultation on Revised Base Station, Cellular Booster, User Equipment and IoT Requirements
The Malaysian Technical Standards Forum Bhd (MTSFB) has opened public consultations on four draft Technical Codes. Three are first revisions of the existing IMT-2020 (5G) codes for base stations, cellular booster equipment and user equipment, which are used for equipment certification in Malaysia. The fourth is a new code setting syntactic data interoperability requirements for Internet of Things (IoT) systems.
The comment windows are short. Feedback on the three 5G drafts is due by 14 October 2026, and feedback on the IoT draft is due by 30 October 2026.
Regulatory Background
MTSFB is the technical standards forum designated by the Malaysian Communications and Multimedia Commission (MCMC) under Section 184 of the Communications and Multimedia Act 1998 (Act 588). It prepares Technical Codes under Section 185 of the Act. A Technical Code only takes effect once MCMC registers it under Section 95.
Codes carrying a "T" designation are developed for certifying communications equipment under the Communications and Multimedia (Technical Standards) Regulations 2000. Codes carrying a "G" designation cover other matters such as architecture, security and interoperability. The three 5G drafts are "T" codes and therefore feed directly into type approval. The IoT draft is a "G" code.
The current 5G equipment codes (MCMC MTSFB TC T016:2021, T017:2021 and T019:2021) were registered on 24 August 2021. Public comment is a formal milestone in the MTSFB development process, and all comments received are deliberated by the responsible Working Group.
Malaysia 5G Technical Codes Under Consultation: Scope of the Update
Project No. | Draft Technical Code | Proposed designation | Status | Working Group | Comment period |
MTSFB2602R1 | IMT-2020 (5G) Base Station (First Revision) | MCMC MTSFB TC T017:2026 | Replaces T017:2021 | Communications Terminal (WG8) | 15 September to 14 October 2026 |
MTSFB2603R1 | IMT-2020 (5G) Cellular Booster Equipment (First Revision) | MCMC MTSFB TC T019:2026 | Replaces T019:2021 | Communications Terminal (WG8) | 15 September to 14 October 2026 |
MTSFB2604R1 | IMT-2020 (5G) User Equipment (First Revision) | MCMC MTSFB TC T016:2026 | Replaces T016:2021 | Communications Terminal (WG8) | 15 September to 14 October 2026 |
MTSFB2605R0 | Internet of Things: Syntactic Data Interoperability Requirement | Number to be assigned (G series) | New | IoT and Smart Sustainable Cities (WG1) | 1 October to 30 October 2026 |
Key Proposed Changes
Changes common to the three 5G drafts
All three revisions share the same core modifications:
Additional frequency bands. The 3300 MHz, 3600 MHz and 4700 MHz bands are added, together with the applicable technical requirements.
Baseline requirements moved to a separate code. Requirements for marking, interoperability, electromagnetic compatibility (EMC) and electrical safety are removed from the 5G codes. They are now addressed in MCMC MTSFB TC T022, Communications Equipment: Baseline Requirements, which was registered on 5 May 2026. Equipment must comply with both the product code and T022.
Updated spectrum plan references. Editorial updates align the codes with the latest MCMC Standard Radio System Plans (SRSPs).
SRSP precedence. Where a Technical Code and the corresponding SRSP differ, the SRSP prevails.
Band plan in the revised drafts
Band | Frequency range | Duplex | Band plan reference | Intended use |
n28 (700 MHz) | 703 to 743 MHz uplink, 758 to 798 MHz downlink | FDD | MCMC SRSP MS 700 | Public 5G networks |
n78 (3500 MHz) | 3300 to 3500 MHz | TDD | Not yet available | Public 5G networks |
n78 (3500 MHz) | 3400 to 3600 MHz | TDD | MCMC SRSP MS 3500 | Public 5G networks |
n78 (3600 MHz) | 3600 to 3650 MHz | TDD | MCMC SRSP MS 3600 | Private and non-public networks only |
n79 (4700 MHz) | 4700 to 4800 MHz | TDD | MCMC SRSP MS 4700 | Private and non-public networks only |
n257 (28 GHz) | 26.5 to 28.1 GHz | TDD | MCMC SRSP MS 28000 | Millimetre wave, high capacity applications |
The drafts state that use of the 3600 MHz and 4700 MHz bands for public IMT services is strictly prohibited.
IMT-2020 (5G) User Equipment (First Revision)
Scope. Cellular mobile terminals, handheld, portable and vehicle-mounted equipment, and RF interface cards and modems.
Output power. 23 dBm (Power Class 3) for 700 MHz. 26 dBm (Power Class 2) or 23 dBm (Power Class 3) for the 3300 to 4800 MHz ranges. Equipment exceeding the table limits must comply with the limits for its declared power class.
Test references. 3GPP TS 38.101-1 and TS 38.521-1 (or ETSI equivalents), or ETSI EN 301 908-25. For 28 GHz, 3GPP TS 38.101-2.
RF parameters. Maximum and minimum transmitter output power, spectrum emission mask, spurious emissions, adjacent channel leakage ratio, receiver spurious response and emissions, and reference sensitivity.
Voice. Equipment supporting VoNR or Vo5G must comply with 3GPP TS 34.229-5 or an equivalent standard.
Multi-technology devices. Suppliers must show that LTE, GSM/EDGE, WLAN, Bluetooth and NFC functions are tested and certified against the related Technical Codes or Class Assignments. Network priority must be configured as 5G first, followed by LTE and GSM/EDGE.
Architecture. Support for both Non-Standalone and Standalone operation is recommended.
IMT-2020 (5G) Base Station (First Revision)
Radiated power limits. 64 dBm per 5 MHz EIRP per antenna at 700 MHz. For 3300 to 3600 MHz and 4700 to 4800 MHz: 65 dBm per 5 MHz EIRP for non-AAS base stations and 44 dBm per 5 MHz TRP for AAS base stations. For 3600 to 3650 MHz: 18 dBm per 5 MHz EIRP per cell (low power) and 38 dBm per 5 MHz EIRP per cell (medium power). For 28 GHz: 62 dBm EIRP.
Conformity standards. 3GPP TS 38.104, TS 38.141-1 and TS 38.141-2 for NR base stations. TS 37.141 for multi-standard radio. TS 37.145-1 and TS 37.145-2 for active antenna systems. All at Release 15 or later, with ETSI equivalents accepted.
Multi-technology base stations. LTE and GSM/EDGE functions must be certified under the relevant Technical Codes.
IMT-2020 (5G) Cellular Booster Equipment (First Revision)
This draft goes further than the other two and revises the technical requirements themselves.
Mandatory functional controls. Automatic gain control, anti-oscillation detection and mitigation, automatic self-monitoring against noise and gain limits, and a transmit power-off mode that activates when limits cannot be met or when a nearby base station becomes operational.
Test references. 3GPP TS 38.106 (NR repeater radio transmission and reception) and TS 38.115-1 and TS 38.115-2 (NR repeater conformance testing), or ETSI equivalents.
Multi-band boosters. Each supported band must independently comply with the applicable requirements.
Operating conditions. The operating range must follow the spectrum assigned by MCMC to the network operator, and use is subject to successful coordination with that operator.
Internet of Things: Syntactic Data Interoperability Requirement (new)
The new IoT draft targets vendor-specific data formats that prevent multi-vendor interoperability in Malaysian smart city and industrial IoT deployments. It applies to data exchange between IoT devices, edge gateways and central platforms, and is independent of the transport protocol. It does not cover transport protocols, communications security or semantic interoperability.
Main requirement areas:
Data modelling and schema. Every payload must conform to a documented schema. Required data elements include a device identifier, data identifier, measured property, value, time reference, unit of measurement and schema version.
Timestamps and units. Time values in UTC or local time with an explicit offset, in a format conforming to ISO 8601-1. Units must be declared explicitly using a recognised unit identification system.
Payload structure and validation. Documented field naming rules, declared message types, and structural validation of every payload before its content is used.
Serialisation and encoding. JSON for general-purpose integration, CBOR for constrained devices and LPWAN links such as NB-IoT, LTE-M and LoRaWAN, with SenML and XML supported. Text payloads must use UTF-8.
Messaging patterns. A documented messaging profile per interface covering telemetry, events, commands, acknowledgements and errors. Commands that could be unsafe if delayed must carry an expiry time.
Certification Impact Summary
Area | Current framework (2021 codes) | Proposed framework (2026 drafts) | Impact on type approval |
Frequency bands | 2021 band plan | Adds 3300, 3600 and 4700 MHz | Test reports must cover every supported band listed in the code |
Marking, EMC, safety, interoperability | Contained in each 5G code | Moved to MCMC MTSFB TC T022 | Two-document compliance: product code plus T022 |
Spectrum plan references | Earlier SRSP titles | Updated SRSP references, SRSP prevails | SRSP limits must be checked alongside the code |
User equipment | T016:2021 | T016:2026, VoNR conformance, multi-RAT certification evidence | Additional evidence for VoNR and for each non-5G radio |
Base stations | T017:2021 | T017:2026, 3GPP Release 15 or later conformity | Band-specific EIRP and TRP limits, including private network power classes |
Cellular boosters | T019:2021 | T019:2026, NR repeater standards and new functional controls | New functional tests and updated test standards |
IoT data interoperability | No dedicated code | New G-series code | Not a type approval requirement, expected to influence platform and tender specifications |
Certification of communications equipment in Malaysia is carried out by SIRIM QAS International, the certifying agency registered with MCMC. The drafts note that the certifying agency may assess the relevance of alternative standards through a suitability study and gap analysis, subject to MCMC approval.
Each revised code will replace its 2021 predecessor from the date of registration. The drafts do not set out a transition period or the treatment of existing certificates.
What This Means for Manufacturers
5G device and module manufacturers. Review each product's supported NR bands against the revised band table. Devices supporting n78 across 3300 to 3650 MHz or n79 at 4700 to 4800 MHz should have test data covering those ranges. Confirm that VoNR conformance evidence is available where the feature is enabled, and that every additional radio in the device holds its own valid certification basis.
Infrastructure vendors. Confirm that base station test reports reference 3GPP Release 15 or later and that declared power levels fit the band-specific limits, particularly the low and medium power classes at 3600 to 3650 MHz.
Private network suppliers. The 3600 MHz and 4700 MHz bands are reserved for non-public networks. Equipment marketed for enterprise 5G in Malaysia will now have a defined certification basis in these bands, with a clear prohibition on public network use.
Booster and repeater manufacturers. This group faces the most substantive change. Product designs should be checked for automatic gain control, anti-oscillation, self-monitoring and automatic shutdown behaviour, and test plans should move to the NR repeater standards.
IoT device, gateway and platform vendors. The IoT code is not an equipment certification requirement. Once registered, it is likely to be referenced in smart city procurement and platform integration requirements. Vendors should compare current payload formats, schema versioning and messaging behaviour against the draft.
All applicants. Compliance documentation should be restructured around two references: the product-specific code and the T022 baseline requirements.
Timeline and Required Actions
Timeline
Date | Milestone |
24 August 2021 | Current 5G codes T016:2021, T017:2021 and T019:2021 registered |
5 May 2026 | MCMC MTSFB TC T022 (Baseline Requirements) registered |
15 September 2026 | Public comment opens for the three 5G drafts |
1 October 2026 | Public comment opens for the IoT draft |
14 October 2026 | Public comment closes for the three 5G drafts |
30 October 2026 | Public comment closes for the IoT draft |
After consultation | Working Group deliberation and submission to MCMC |
To be announced | Registration by MCMC under Section 95, at which point each code takes effect |
Required actions
Action | Who | When |
Download and review the relevant draft codes | Regulatory and RF engineering teams | Immediately |
Submit comments on the 5G drafts through the MTSFB online form | Device, infrastructure and booster manufacturers | By 14 October 2026 |
Submit comments on the IoT draft | IoT device, gateway and platform vendors | By 30 October 2026 |
Run a gap analysis of existing test reports against the new bands and test standards | Compliance teams | Before registration |
Review T022 and align marking, EMC and safety documentation | All applicants | Before registration |
Confirm transition arrangements and treatment of existing certificates with SIRIM QAS International | Certificate holders and local representatives | After the consultation closes |
Monitor MCMC and MTSFB for the registration announcement | All stakeholders | Ongoing |
How to Submit Comments
Comments are submitted through the Public Comments form on the MTSFB Technical Code page. Each comment must identify the relevant clause, table, figure or page number, provide a justification and, where possible, propose alternative wording. Submitters can request a response to their comments.
