top of page

Malaysia MCMC SRD Specifications & Baseline Code Update

  • 1 day ago
  • 4 min read

Malaysia MCMC Updates SRD Specifications and Issues New Communications Equipment Baseline Code


Malaysia has refreshed one of the most consequential documents in its radio equipment type approval regime. The Malaysian Communications and Multimedia Commission (MCMC) has registered MCMC MTSFB TC T007:2026 – Short Range Devices (SRDs) Specifications (3rd Revision), alongside a brand-new companion document, MCMC MTSFB TC T022:2026 – Communications Equipment – Baseline Requirements. Both were published on 5 May 2026.


For manufacturers, importers and regulatory affairs teams placing wireless products on the Malaysian market, this is a structural change, not a cosmetic one. The revision opens the 6 GHz band to short range devices, broadens Ultra-Wideband (UWB) operation, reorganizes the 5 GHz WLAN/RLAN rules, and critically moves the common baseline requirements (safety, EMC, marking and power supply) out of T007 and into the new T022 code. Any product family certified against the old SRD specification will need to be re-mapped to two documents instead of one.


Regulatory background


In Malaysia, technical codes are developed by the Malaysian Technical Standards Forum Bhd (MTSFB) and registered by MCMC under the Communications and Multimedia Act 1998 (CMA 1998). Once registered, a technical code becomes the recognized basis for certifying communications equipment under the Communications and Multimedia (Technical Standards) Regulations 2000, the framework that underpins SIRIM type approval.


The SRD specification (TC T007) defines the technical requirements frequency bands, maximum transmit power, and test-standard references, for short range devices operating under the relevant Standard Radio System Plans (SRSPs) and Class Assignments. The previous edition, TC T007:2020 (2nd Revision), has governed the market since May 2020. The 2026 third revision modernizes that framework to reflect 6 GHz adoption, expanded UWB use cases, and harmonization with the latest ETSI standards.


What changed in the MCMC SRD specifications (TC T007:2026)


The third revision introduces the following principal changes:


  • Baseline requirements relocated. Safety, Electromagnetic Compatibility (EMC), marking and power-supply requirements that previously sat inside T007 have migrated to the new MCMC MTSFB TC T022:2026 baseline code. T007 now focuses on RF/spectrum parameters and points to T022 for the common horizontal requirements.

  • 6 GHz SRD/RLAN added. The 5925–6425 MHz band is now included for short range / radio local area network (RLAN) operation, Malaysia's formal opening of the lower 6 GHz band to license-exempt Wi-Fi-class devices.

  • Expanded UWB operation. UWB Road and Rail Devices are added, and 8500–10600 MHz UWB operation is now covered within the SRD framework.

  • 5 GHz WLAN/RLAN reorganized. The 5 GHz WLAN/RLAN bands have been restructured, with new indoor/outdoor power restrictions.

  • ETSI standards adopted. ETSI EN 303 687 (6 GHz WAS/RLAN access to radio spectrum) and ETSI EN 303 883 (UWB measurement techniques) are now referenced test/harmonized standards.

  • 3400–3700 MHz UWB allocation removed. This allocation has been removed from the previous UWB structure, simplifying the lower-frequency UWB framework.


An infographic summarizing Malaysia's May 2026 MCMC regulatory updates for communications equipment. The top section illustrates the structural shift from a single technical code (TC T007:2020) to a two-document compliance model (TC T007:2026 and TC T022:2026) against a background featuring the Petronas Twin Towers. The middle section highlights key changes, including relocated baseline requirements, the addition of 6 GHz Wi-Fi 6E/7, expanded UWB operation, and reorganized 5 GHz WLAN restrictions. The bottom section outlines required actions for manufacturers and a timeline from publication through portfolio gap analysis, document re-mapping, and re-testing.

The new baseline code: TC T022:2026


The companion document, MCMC MTSFB TC T022:2026, Communications Equipment, Baseline Requirements, consolidates the horizontal "baseline" requirements that apply across many equipment categories product marking, electrical safety and health, power supply, and EMC into a single referenceable code. Rather than repeating these clauses inside every product-specific technical code, MCMC's framework now points equipment codes (including the SRD specification) to T022 for the common baseline.


For certification, the practical effect is a two-document compliance model: the product-specific code (e.g., T007 for SRDs) for RF/spectrum parameters, plus T022 for the shared safety/EMC/marking/power baseline.


What this means for manufacturers


The change is most significant for anyone whose product roadmap touches 6 GHz Wi-Fi, UWB, or 5 GHz WLAN but the baseline restructuring affects nearly every wireless device class.


  • 6 GHz Wi-Fi (Wi-Fi 6E / Wi-Fi 7) is now in scope. Products operating in 5925–6425 MHz can be certified for Malaysia under the SRD framework, with ETSI EN 303 687 as the reference standard. Confirm your device's default power and indoor/outdoor configuration match the new limits and cannot be altered by the end user.

  • UWB roadmaps expand. New road and rail use cases and 8500–10600 MHz operation are covered, with ETSI EN 303 883 as the measurement-technique reference. Verify your UWB EIRP masks against the updated band entries.

  • Re-check your 5 GHz configurations. The reorganized 5 GHz WLAN/RLAN bands carry new indoor/outdoor power restrictions. Existing 5 GHz products may need configuration statements or re-testing to confirm compliance.

  • Update your compliance documentation to two codes. Test reports, declarations and technical files should now reference both T007:2026 (RF/spectrum) and T022:2026 (baseline safety/EMC/marking/power). Files that cite only the old T007 baseline clauses will be out of date.

  • Watch frequency-range mismatches. Under MCMC practice, if a product's specification range is wider than what is authorized, you must submit a configuration statement proving the default settings are compliant and locked against user modification. Align datasheets, test reports and firmware defaults before submission.

  • Re-map discontinued allocations. If any of your products relied on the 3400–3700 MHz UWB allocation, that structure has been removed; reassess the affected SKUs.


Certification impact summary


Area

Previous position (T007:2020)

New position (T007:2026 + T022:2026)

Action for manufacturers

Baseline (safety, EMC, marking, power)

Contained within T007

Moved to new T022:2026

Reference both codes; update technical files

6 GHz SRD/RLAN (5925–6425 MHz)

Not included

Added (ETSI EN 303 687)

Certify 6 GHz Wi-Fi; lock indoor/outdoor power defaults

UWB road & rail / 8500–10600 MHz

Limited UWB scope

Added (ETSI EN 303 883)

Verify UWB EIRP masks against new entries

5 GHz WLAN/RLAN

Prior band/power structure

Reorganized with new indoor/outdoor power limits

Re-check 5 GHz configs; re-test if needed

3400–3700 MHz UWB

Allocated in UWB structure

Removed

Reassess affected SKUs

Reference standards

EN 300 440 / EN 301 893 / EN 302 065 etc.

+ ETSI EN 303 687, EN 303 883

Update test plans to cited editions


Timeline and required actions


  1. 5 May 2026: Codes published. MCMC MTSFB TC T007:2026 (3rd Revision) and TC T022:2026 are registered. (Verify exact date against the official PDFs.)

  2. Immediately: Gap-analyze your portfolio. Identify every product certified against T007:2020 and flag those touching 6 GHz, UWB, or 5 GHz WLAN/RLAN.

  3. Short term: Re-map documentation to two codes. Update declarations, technical files and test reports to cite both T007:2026 and T022:2026.

  4. Short term: Validate configurations. Confirm indoor/outdoor power defaults (6 GHz and 5 GHz) and UWB EIRP masks meet the new limits and are locked against user modification.

  5. Before new submissions: Re-test where required. Arrange testing against the newly cited ETSI standards (EN 303 687, EN 303 883) for affected device families.

  6. Ongoing: Monitor any grace period. Check the official codes for any transition/grace window before existing certificates must conform, and plan re-certification accordingly.



bottom of page