Chiun Mai Communication System, Inc. — 6 MA-L blocks; a Foxconn-group wireless-module & healthcare-IoT maker
Summary
- // what this is
- Chiun Mai Communication System is registered to MAC prefix
58:C9:35and 5 more in the IEEE OUI database. When a device's MAC address begins with58:C9:35, that block was registered by Chiun Mai Communication System — the OUI identifies the maker of the network hardware, which is not always the brand on the device. - // analyst note
- Treat a Chiun Mai OUI as 'built by a Foxconn-group OEM supplier' — most likely a BLE/Wi-Fi IoT node or an embedded module inside someone else's equipment. Classify by hostname, model strings, or traffic behavior, not by the OUI.
About this vendor.
Chiun Mai Communication System, Inc. holds six MA-L (24-bit) OUI blocks — 58:C9:35, CC:9F:7A, E8:97:B8, 24:AF:CC, 98:C8:54, and 5C:57:9E — all registered to the same Tucheng District / New Taipei City, Taiwan address (No. 4, Minsheng St.). The IEEE source data spells the street and district inconsistently across rows ("Minsheng"/"MingSheng", "Tucheng"/"TuCheng"/"TUCheng") and carries two postal codes, 23678 on the two older blocks and 23679 on the four later ones; that drift lives in the registry, not in any one device. Chiun Mai is an international member company of the Foxconn Technology Group (Hon Hai), which is the key triage fact: like its parent, it is a contract/OEM supplier, so a Chiun Mai OUI tells you who built the radio, not whose logo is on the box. Its current product focus is embedded wireless modules (dual-band Wi-Fi 802.11b/g/n plus BLE for OEM integration) and "Fusion"-branded smart-healthcare IoT — indoor-positioning tags, patient and infant monitoring, smart nurse-call, equipment tracking, and air-quality sensing — alongside a contract-manufacturing heritage in mobile phones. An FCC-certified example is the FusionAir-MRT module (model BTWIM-FURM99, FCC ID 2AZ9NBTWIM-FURM99), a Wi-Fi+BLE OEM component meant to be embedded in a host device rather than sold standalone. The practical consequence: a device showing a Chiun Mai OUI on an enterprise or hospital network is most likely a BLE/Wi-Fi IoT node or an embedded module inside someone else's equipment, so classify it by hostname, model strings, or traffic behavior rather than by the OUI alone.
- IEEE assignment
- 6 MA-L blocks — 58:C9:35, CC:9F:7A, E8:97:B8, 24:AF:CC, 98:C8:54, 5C:57:9E → "Chiun Mai Communication System, Inc" [Confirmed] — IEEE the IEEE MA-L registry (rows 325, 8266, 24001, 31340, 31981, 38244); corroborated by maclookup.app/vendors/chiun-mai-communication-system-inc
- Registry / block size
- MA-L (24-bit OUI) only; 6 blocks (~100.7M addresses). Not present in MA-M (the IEEE MA-M registry) or MA-S (the IEEE MA-S registry) [Confirmed] — IEEE the IEEE MA-L registry / the IEEE MA-M registry / the IEEE MA-S registry
- HQ / country
- No. 4, Minsheng St. (also "MingSheng St."), Tucheng District (also "TuCheng"/"TUCheng"), New Taipei City, Taiwan; postal code 23678 on the two older blocks and 23679 on the four later ones — spelling/postal variation is in the IEEE source data[Confirmed] — IEEE the IEEE MA-L registry; fccid.io/2AZ9N
- Country
- TW (Taiwan) [Confirmed] — IEEE the IEEE MA-L registry; www-onepage.taiwantrade.com/company/chiun-mai-communication-systems-inc-168819.html
- Company name variants
- registered to IEEE as "Chiun Mai Communication System, Inc" (singular "System"); appears as "Chiun Mai Communication Systems, Inc." (plural) in FCC filings and trade registries — same entity [Confirmed] — fccid.io/2AZ9N, taiwantrade.com/suppliers/detail.html?companyid=168819
- Parent group
- Foxconn Technology Group (Hon Hai Precision Industry) — Chiun Mai is an international member company of the Foxconn group [Confirmed] — expo.bioasiataiwan.com/en/visitorExhibitorDetail.asp?comNo=291246&sno=173644, ict.teema.org.tw/ebookqr/eprofile.asp?id=1856
- Company status
- active [Confirmed] — fccid.io/2AZ9N (recent FCC grantee activity), taiwantrade supplier listing
- Established
- 2001, per company exhibition materials (self-report, not an IEEE/government-registry fact) [Likely] — expo.bioasiataiwan.com/en/visitorExhibitorDetail.asp?comNo=291246&sno=173644
- Device types
- embedded wireless modules (Wi-Fi 802.11b/g/n + BLE, dual-band, OEM); "Fusion"-branded healthcare IoT (indoor-positioning tags, patient/infant monitoring, smart nurse-call, equipment tracking, air-quality sensing); historic mobile-phone contract manufacturing [Confirmed] — fccid.io/2AZ9NBTWIM-FURM99, expo.bioasiataiwan.com/en/visitorExhibitorDetail.asp?comNo=291246&sno=173644, taiwan-pavilion.taitra.org.tw/twhealthcaresi/Smart_Healthcare/CHIUNMAI?product=33636
- Notable products
- FusionAir-MRT Wi-Fi+BLE OEM module (model BTWIM-FURM99, FCC ID 2AZ9NBTWIM-FURM99) — designed for integration into host devices, not a standalone consumer product [Confirmed] — fccid.io/2AZ9NBTWIM-FURM99
- Primary use context
- predominantly enterprise/healthcare IoT (BLE/Wi-Fi positioning beacons, monitoring sensors, embedded OEM modules); consumer-device assignment possible given the Foxconn mobile-phone heritage but not the current product focus[Likely] — expo.taiwan-healthcare.org/en/news_detail.php?REFDOCID=0qgdxioaqq31t745, fccid.io/2AZ9NBTWIM-FURM99
- Registration date
- Unknown — IEEE publishes no OUI assignment/registration dates; "date registered" values on third-party MAC databases (e.g. maclookup.app) are aggregator artifacts, not IEEE facts [Unknown] — (no IEEE date exists)
- Security
- no CVEs, advisories, or known exploits attributable to Chiun Mai or its Fusion-branded products were found in available sources. (Note the easily-confused, unrelated "Xiongmai" DVR vendor, which does have CVEs — not this company.)[Likely negative] — open-source search (negative finding); name-disambiguation note
- Related vendors
- Foxconn / Hon Hai (parent group) and the broader Foxconn member-company family
- Analyst note
- Treat a Chiun Mai OUI as "built by a Foxconn-group OEM supplier" — most likely a BLE/Wi-Fi IoT node or an embedded module inside someone else's equipment. The OEM-module use case means one block can appear across many different host devices, so OUI-alone device-type inference is unreliable; classify by hostname, model strings, or traffic behavior.