| Business Structure | B2B → B2C (e.g., Fujitsu or Toshiba → NTT Docomo → End Users) | B2B → B2B → B2C (e.g., Panasonic, Denso, LG → Toyota → End Users) |
| Key Stakeholders | - Smartphone manufacturers (e.g., Fujitsu, Toshiba)- Mobile network operators (e.g., NTT Docomo, KDDI) | - DCM/IVI developers (e.g., Panasonic, LG, Denso)- Automotive OEMs (e.g., Toyota)- Mobile network operators (e.g., AT&T, Verizon) |
| Main Deliverables | Smartphone devices | In-vehicle infotainment (IVI) systems with built-in DCM |
| Relationship with Carrier | Direct: collaboration with mobile carriers for feature requirements, integration, and testing | Indirect: connectivity validation and certification done through automotive OEMs, not direct with carriers |
| Development Flow | Two-party collaboration: Manufacturer ↔ Mobile Operator | Three-party collaboration: DCM/IVI Vendor ↔ OEM ↔ Mobile Operator |
| Carrier Connectivity Testing | Conducted after product development: includes voice and data service testing | Performed after vehicle system integration: focuses on DCM network communication and connectivity verification |
| Regulatory & Conformance Testing | - PTCRB / GCF- FCC certification (USA) | - PTCRB / GCF- FCC certification (USA) |
