Transforming V2X Knowledge into a Real Learning Experience

V2Xcast® & V2X Stack Software

  • 1. How does V2Xcast® work ?

    V2Xcast® is a highly integrated and user-friendly software development kit used by all Unex product family of SOM, OBU, and RSU, including standard compliant V2X stack, advanced IEEE and ETSI communication security, and sample applications in source code.

    V2Xcast® is structured in V2Xcast SDK and V2Xcast Service. V2Xcast SDK can be flexibly used together with V2Xcast Service as one embedded software in standalone V2X OBU and RSU, or installed separately at Linux OS host platform in typical using case of V2X SOM (system-on-module).

    V2Xcast SDK is all in user space, C99 and relied on POSIX APIs, so it is highly portable to most of operating system. It communicates and gets services from V2Xcast Service for V2X communication. The Services include V2X transmission and reception, packet encapsulation and decapsulation, message encoding and decoding, security for the packets over the air and certificate management cooperating with V2X PKI system. Just selects the profiles of V2X protocol defined in the local regulation to configure V2Xcast Service, such as channel number, PSID, TX power, … etc., the Services work automatically without any programming, the only thing should do is to configure the services to follow your demand and develop V2X application software in C language.

  • 2. What V2X protocol standards does V2Xcast® follow ?

    Technically, V2Xcast® will adapt to support evoluting V2X protocol standard (including candidate standards of C-V2X China and C-V2X Europe) per release maturity and market requirement at appropriate schedule.

    Currently, 3 protocol standards are implemented and the V2X packets over the air are fully compliant to latest SAE, IEEE and ETSI standards.

    • V2Xcast® for DSRC/WAVE includes IEEE 1609.2, IEEE 1609.3, IEEE 1609.4, SAE J2735 (including BSM, MAP, SPAT, RTCM, SRM, SSM, TIM and etc), IEEE 1609.2.1 (SCMS), PoTi (Fix, fix time, speed, errors of the data, skyview and etc.) on SOM-301U/OBU-301U/RSU-301U
    • V2Xcast® for ETSI ITS-G5 in Europe includes IEEE 802.11p, GN (ETSI EN 302 636-4-1, ETSI TS 102 636-4-2), BTP (ETSI EN 302 636-5-1), Facility (CAM: ETSI EN 302 637-2, DENM: ETSI EN 302 637-3, Messages for infrastructure services: ETSI TS 103 301 including SPATEM, MAPEM, IVIM and etc.), DCC (ETSI TS 103 175, ETSI TS 102 687), Security (ETSI TS 103 097), ETSI TS 102 941 (CCMS), PoTi (Fix, fix time, speed, errors of the data, skyview and etc.), CAR 2 CAR Communication Consortium – Basic System Profile (BSP) on SOM-301E/OBU-301E/RSU-301E.
    • V2Xcast® for C-V2X of USA standards includes IEEE 1609.2, IEEE 1609.3, SAE J2735 (including BSM, MAP, SPAT, RTCM, SRM, SSM, TIM and etc), IEEE 1609.2.1 (SCMS), PoTi (Fix, fix time, speed, errors of the data, skyview and etc.) on SOM-351U/OBU-351U/RSU-351U

    Unex will provide 12-months free software update and technical support after product received.

  • 3. What’s the OS in support of V2Xcast® SDK ?

    Technically, V2Xcast SDK should work on most of popular industrial platforms. The off-the-shelf package supports X86-32bit, and ARMv7-A with Linux 4.x OS.

    To be more specifically,

    • the platform of X86-32bit is defined the same as i386 in Debian system.
    • the platform of ARMv7-A is defined the same as armhf in Debian system. (Major parameters: arch=armv7-a, float-abi=hard, fpu=vfpv3-d16, thumb=Thumb2, EABI=Version5)
    • if the CPU of your platform is 64bit, the application built with V2Xcast SDK should still work with the Multi-Arch support, such as installing libc6 for i386 or armhf.

  • 4. Having development experience on V2Xcast®, is there extra work required if different V2X technology selected such as from DSRC-V2X to C-V2X or vice-versa?

    V2Xcast® adopts the hardware and software decoupling framework, the use of V2Xcast® SDK for DSRC-V2X or C-V2X technology during software development will be the same, only some API parameters and caster config. settings must be complied per DSRC-V2X or C-V2X configuration requirements.

    Per customers’ feedbacks worldwide, the transfer between DSRC-V2X & C-V2X are very smoothly without any hurdles.

  • 5. How Unex secures sustainable software performance and quality of V2Xcast® ?

    Unex adopts the V-model as the core of the V2Xcast development process. We compose and maintain the architecture, design documents, unit tests and integrated tests. In addition to this, a continuous development framework for V2X is designed and implemented by Unex as following:


    Unex secures sustainable software performance and quality of V2Xcast

    Through the solid and short cycles of feedbacks, Unex has confidence to serve, support and deliver software with low risk in time.

  • 6. Does V2Xcast® support the use of external GNSS, in addition to the onboard GNSS ?

    V2Xcast® is a very flexible software framework to support the use of external GNSS, in addition to the onboard GNSS.

    As the onboard GNSS is a major component in the Unex’s V2X system, it will serve to provide “position” and “timing” for both V2X protocol stacks and V2X applications. Depending on the application scenarios of external GNSS, 2 typical usages of Unex’s off-the-shelf V2X system are as following:

    1. If the external GNSS is connected to your host platform, V2Xcast® can support external GNSS as following application illustration:

      V2Xcast® can support external GNSS as following application illustration

      • The fields of messages (e.g. BSM or CAM) are filled by app. developers, so the position data could be fetched from GNSS devices connected to your host and filled by yourself.
      • It is similar in the reversed way. The data in the messages (e.g. RTCM) could be fed into GNSS devices connected to your host by yourself.
      • The pre-integrated GNSS is served for V2X protocol stacks to make all the functions work correctly.
    2. If the external GNSS is connected directly to Unex’s V2X system, V2Xcast® can support external GNSS as following application illustration:

      V2Xcast® can support external GNSS as following application illustration

      • The fields of messages (e.g. BSM or CAM) are filled by app. developers, so the position data could be fetched from GNSS devices connected to your host and filled by yourself.
      • It is similar in the reversed way. The data in the messages (e.g. RTCM) could be fed into GNSS devices connected to your host by yourself.
      • The pre-integrated GNSS is served for V2X protocol stacks to make all the functions work correctly.

    For future commercial q’ty deployment in case 1 scenario, Unex would highly recommend customizing hardware/software by project base and apply as following illustration:

    Unex would highly recommend customizing hardware/software by project base and apply as following illustration

  • 7. What is the V2Xcast® SDK development environment and update/upgrade flow ?

    1. The supported development environment is Linux system and Ubuntu 18.04 is suggested. Linux running on virtual machine on top of Win10 is a popular choice.
    2. A remote FW upgrade package in the official release is provided to update V2Xcast Service in the product. In addition to this, the corresponding V2Xcast SDK should be replaced to your development environment.

  • 8. Can we use proprietary message mixing in the SAE J2735 on SOM/OBU/RSU ?

    Basically, no special changes required on SOM/OBU/RSU series, can still use V2Xcast SDK on application host side. Your own proprietary message encoder and decoder could be integrated with V2Xcast SDK easily. The only thing which has to be noticed is to arrange the proprietary messages and standard ones with different PSID.

    Some examples:

    • Following scenario of mixing messages is ok (supported by off-the-shelf product),
      • Channel: 172, PSID: 0x20, BSM
      • Channel: 172, PSID: 0x304050, Proprietary_Msg 1
      • Channel: 172, PSID: 0x304052, Proprietary_Msg 3
      • Channel: 182, PSID: 0x304051, Proprietary_Msg 2

  • 9. Can the proprietary messages be delivered by V2Xcast® ?


    Yes, the message decoder and encoder are decoupled to other APIs of V2Xcast SDK. A proprietary message encoder and decoder could be integrated with V2Xcast SDK easily by you.

  • 10. Certificates, encryption, and signature in terms of V2X security ?

    Encryption is not popular in the current V2X pilot deployment because most applications are designed to share status to all nearby vehicles. Most of them utilize digital signature technology to prevent tampered or fake messages. Digital signature has following characteristics,

    1. Authentication
    2. Integrity
    3. Non-repudiation

    A message applied digital signature is not encrypted, so the content still can be read and you can decide to trust it or not through the verification of the signature included in the message. Besides, a certificate is the container of keys which could be used for encryption or digital signature, so certificates are always required no matter which one you choose finally.

  • 11. Any extra license fee or royalty required on V2Xcast® ?

    V2Xcast® is embedded in Unex’s V2X device and sold at one package price for PoC or deployment to quickly meet time-for-market. The V2X package price includes the right to use Unex’s V2X protocol stack, V2Xcast®, SDK per V2XCAST® SOFTWARE LICENSE AGREEMENT, no extra license or royalty required. In addition, Unex provides 12-months hardware warranty, free software update, and technical support.

  • V2X System-on-Module (SOM-series)

  • 1. Why Craton2/Pluton2, not Secton2 as other V2X modem module in the market ?

    It’s a question of priority per readiness of technologies, autonomous vehicle E/E architecture, gov. regulation, and user’s acceptance.

    The typical advantage of V2X sub-system (Unex’s SOM series) and V2X modem is as following:


    The typical advantage of V2X sub-system (Unex’s SOM series) and V2X modem

    As Unex is centered on V2X innovation and co-creation, to reduce the high system hardware design and V2X protocol stack development time and costs of our partners, Unex decided to adopt Craton2/Pluton2 to provide tested and certified system-on-modules with service-oriented V2Xcast® software that incorporate a V2X communication processor, V2X RF, power management, I/O connectivity, DRAM and Flash memories, as well as standard compliant V2X stack, security, and application example code, so that Unex’s partners can concentrate their own resources on developing their application’s key features and differentiators.

    This is especially beneficial when adding dedicated resources in regard to software development as well as V2X sensor fusion application to assist autonomous activity or used in intelligent transportation system. All Unex’s partners can then reduce the risk of development by focusing their work on their own field of expertise and not on complex PCB design issues, V2X stack developing, integrating, and maintaining, as well as facilitate the manufacturing or procurement phases.

    Whatever V2X application software implemented on Unex’s V2Xcast® and devices, Unex’s partners can easily migrate the field approved application software and investment on V2Xcast® to any of Unex’s now and future V2X devices using Craton2 or Secton2 or other chipsets per readiness of V2X chipsets and application requirement

  • 2. What’s the OS in support of V2Xcast® SDK ?

    Technically, V2Xcast SDK should work on most of popular industrial platforms. The off-the-shelf package supports X86-32bit, and ARMv7-A with Linux 4.x OS.

    To be more specifically,

    • the platform of X86-32bit is defined the same as i386 in Debian system.
    • the platform of ARMv7-A is defined the same as armhf in Debian system. (Major parameters: arch=armv7-a, float-abi=hard, fpu=vfpv3-d16, thumb=Thumb2, EABI=Version5 )
    • if the CPU of your platform is 64bit, the application built with V2Xcast SDK should still work with the Multi-Arch support, such as installing libc6 for i386 or armhf.

  • 3. Any option to use external GNSS in addition to the onboard GNSS of SOM-301x ?

    SOM is a very flexible off-the-shelf V2X system-on-module to support the use of external GNSS, in addition to the onboard GNSS.

    As the onboard GNSS is a major component in the Unex’s V2X system, it will serve to provide “position” and “timing” for both V2X protocol stacks and V2X applications. The illustrated application is as below:

    GNSS will serve to provide “position” and “timing” for both V2X protocol stacks and V2X applications

    • The fields of messages (e.g. BSM or CAM) are filled by app. developers, so the position data could be fetched from GNSS devices connected to your host and filled by yourself.
    • It is similar in the reversed way. The data in the messages (e.g. RTCM) could be fed into GNSS devices connected to your host by yourself.
    • The pre-integrated GNSS is served for V2X protocol stacks to make all the functions work correctly.

    Remarks:

    external 1PPS pins are exposed in both mPCIe interface pin 49 and I/O cable pin 5. To avoid back powering and latch-up, external 1PPS should be fed to SOM-301 at least 20ms later than SOM-301 power up.

    use external GNSS in addition to the onboard GNSS of SOM

  • 4. How to quickly verify whether the SOM-3xx V2X system-on-module is properly integrated on the Linux host platform ?


    The following descriptions are applicable for Unex software package only. For verifying the integration of Unex’s V2X system-on-module (SOM-3xx series) with a Linux host system, a user needs to follow the steps below:

    1. Check if the RNDIS driver has already been installed on the host system. If it has not been installed yet, install the RNDIS driver for the host system. The driver installation might include loading
      rndis_host.ko

      with

      modprobe

      command or enabling

      CONFIG_USB_NET_RNDIS_HOST
    2. when compiling the Linux kernel. The detailed instructions of installing the RNDIS driver are not included here because it may vary from one distribution to another.

      user@host:~$ lsmod | grep rndis
    3. Check if the Unex device has been registered as a RNDIS device with a network interface.
    4. user@host:~$ d mesg | grep i C4 unex
    5. Ping the RNDIS device IP of V2X system-on-module (SOM-3xx series) and check if it is alive.
    6. user@host:~$ ping 192.168.1.3
    7. Open a SSH terminal to V2X system-on-module (SOM-3xx series) and check if it works.
    8. user@host:~$ s sh keygen R 192.168.1.3 ; ssh root@ 192.168.1.3

  • 5. Can we upload custom firmware on the SOM-301 module ?

    Yes, it is possible to upload your software on SOM-301 module, but not suggest due to the reason mentioned below:

    The original purpose of V2Xcast Service and SOM-301 is to separate the V2X communications and applications in different hosts and have a clear responsibility of each party to integrate into a big system more easily. We suggest not to do it when you want to gain the whole advantages of the architecture.

  • 6. How can SOM-301U use external high accurate GNSS RTK from the host RSU platform ?


    If the using case is that the host platform with RTK generates RTK data as BASE role, and V2Xcast distributes RTK data by RTCM messages to the nearby OBUs which play ROVER role, then RTCM message provided by V2Xcast SDK could support the case. There is a sample application for this in the off-the-shelf SW package.

  • 7. How to use the Data from in-vehicle-network (ex. CAN) in (SOM + Vehicle PC) application ?


    Data from in-vehicle-network required for facility and application layers should be collected from the main computer system. Then, to fill them into messages (e.g. BSM) and broadcast in the air through V2Xcast SDK. Hence, to collect data from in-vehicle-network will rely on current CAN interface and SDK of your main system.

  • 8. Can we use proprietary message mixing in the SAE J2735 on SOM/OBU/RSU ?

    Basically, no special changes required on SOM/OBU/RSU series, can still use V2Xcast SDK on application host side. Your own proprietary message encoder and decoder could be integrated with V2Xcast SDK easily. The only thing which has to be noticed is to arrange the proprietary messages and standard ones with different PSID.

    Some examples:

    • Following scenario of mixing messages is ok (supported by off-the-shelf product),
      • Channel: 172, PSID: 0x20, BSM
      • Channel: 172, PSID: 0x304050, Proprietary_Msg 1
      • Channel: 172, PSID: 0x304052, Proprietary_Msg 3
      • Channel: 182, PSID: 0x304051, Proprietary_Msg 2

  • 9. What is the latency caused by inter-subsys. communication via Ethernet or USB/mPCIe ?

    When inter-subsys. communication is Ethernet, typically it is less than 1ms by an off-the-self solution. 1ms delay is about a distance of 3.89cm when a vehicle moves in 140km/h.

    When inter-subsys. communication is mPCIe (USB), typically it is less than 2ms by an off-the-self solution.

    The solutions provided above are the tradeoff between having acceptable performance and enabling V2X technology for different industries and on different platforms easily. If you have concerns about this, it is welcome to have a project to co-work with Unex.

  • 10. Certificates, encryption, and signature in terms of V2X security ?

    Encryption is not popular in the current V2X pilot deployment because most applications are designed to share status to all nearby vehicles. Most of them utilize digital signature technology to prevent tampered or fake messages. Digital signature has following characteristics,

    1. Authentication
    2. Integrity
    3. Non-repudiation

    A message applied digital signature is not encrypted, so the content still can be read and you can decide to trust it or not through the verification of the signature included in the message. Besides, a certificate is the container of keys which could be used for encryption or digital signature, so certificates are always required no matter which one you choose finally.

  • 11. Any extra license fee or royalty required on V2Xcast® ?


    V2Xcast® is embedded in Unex’s SOM and sold at one package price for PoC or deployment to quickly meet time-for-market. The V2X package price includes the right to use Unex’s V2X protocol stack, V2Xcast®, SDK per V2XCAST® SOFTWARE LICENSE AGREEMENT, no extra license or royalty required. In addition, Unex provides 12-months hardware warranty, free software update, and technical support.

  • V2X On-Board Unit (OBU-series)

  • 1. Is the power input of OBU-301x compliant to ISO 7637-2 and ISO 16750-2 ?

    The power of OBU-301x is designed to be compliant with ISO 7637-2v 24V and ISO 16750-2 24V standards.

    • ISO 7637-2: Severity level: III, Function performance status: status II
    • ISO 16750-2: Operating modes: according to each test item, Function performance classification: each test item has its own classification for compliance.

    Remarks:

    as Unex continues to effectively update V2X hardware to design per market competition and requirements, product spec. can be changed by time, suggest to re-confirm with Unex.

  • 2. What protection designs are implemented on the OBU-301x ?

    All I/O and power pins are protected according to CE EMC standard EN 301489-1

    • Reverse voltage protection: reverse polarity protection (a test item in ISO-16750-2) is already implemented in current design.
    • Over voltage protection: PMIC voltage clamping at 53V, with TVS and MOV for high energy ESD/surge protection.
    • 12/24V: OBU-301 provides 7-48V wide power input range. 12V or 24V power can be used directly without any detection/configuration.

    Remarks:

    as Unex continues to effectively update V2X hardware to design per market competition and requirements, product spec. can be changed by time, suggest to re-confirm with Unex.

  • 3. How can OBU-301U use external high accurate GNSS RTK if I connected the OBU onto the host platform through Ethernet ?


    If the using case is that the host platform with RTK generates RTK data as BASE role , and V2Xcast distributes RTK data by RTCM messages to the nearby OBUs which play ROVER role, then RTCM message provided by V2Xcast SDK could support the case. There is a sample application for this in the off-the-shelf SW package.

  • 4. How to use the Data from in-vehicle-network (ex. CAN) if I connected the OBU to the Vehicle PC through Ethernet ?


    Data from in-vehicle-network required for facility and application layers should be collected from the main computer system. Then, to fill them into messages (e.g. BSM) and broadcast in the air through V2Xcast SDK. Hence, to collect data from in-vehicle-network will rely on current CAN interface and SDK of your main system.

  • 5. Can we use proprietary message mixing in the SAE J2735 on SOM/OBU/RSU ?

    Basically, no special changes required on SOM/OBU/RSU series, can still use V2Xcast SDK on application host side. Your own proprietary message encoder and decoder could be integrated with V2Xcast SDK easily. The only thing which has to be noticed is to arrange the proprietary messages and standard ones with different PSID.

    Some examples:

    • Following scenario of mixing messages is ok (supported by off-the-shelf product),
      • Channel: 172, PSID: 0x20, BSM
      • Channel: 172, PSID: 0x304050, Proprietary_Msg 1
      • Channel: 172, PSID: 0x304052, Proprietary_Msg 3
      • Channel: 182, PSID: 0x304051, Proprietary_Msg 2

  • 6. What is the latency caused by inter-subsys. communication via Ethernet or USB/mPCIe ?

    When inter-subsys. communication is Ethernet, typically it is less than 1ms by an off-the-self solution. 1ms delay is about a distance of 3.89cm when a vehicle moves in 140km/h.

    When inter-subsys. communication is mPCIe (USB), typically it is less than 2ms by an off-the-self solution.

    The solutions provided above are the tradeoff between having acceptable performance and enabling V2X technology for different industries and on different platforms easily. If you have concerns about this, it is welcome to have a project to co-work with Unex.

  • 7. Certificates, encryption, and signature in terms of V2X security ?

    Encryption is not popular in the current V2X pilot deployment because most applications are designed to share status to all nearby vehicles. Most of them utilize digital signature technology to prevent tampered or fake messages. Digital signature has following characteristics,

    • Authentication
    • Integrity
    • Non-repudiation

    A message applied digital signature is not encrypted, so the content still can be read and you can decide to trust it or not through the verification of the signature included in the message. Besides, a certificate is the container of keys which could be used for encryption or digital signature, so certificates are always required no matter which one you choose finally.

  • 8. Any extra license fee or royalty required on V2Xcast® ?


    V2Xcast® is embedded in Unex’s OBU and sold at one package price for PoC or deployment to quickly meet time-for-market. The V2X package price includes the right to use Unex’s V2X protocol stack, V2Xcast®, SDK per V2XCAST® SOFTWARE LICENSE AGREEMENT, no extra license or royalty required. In addition, Unex provides 12-months hardware warranty, free software update, and technical support.

  • V2X Roadside Unit (RSU-series)

  • 1. Can we use proprietary message mixing in the SAE J2735 on SOM/OBU/RSU ?

    Basically, no special changes required on SOM/OBU/RSU series, can still use V2Xcast SDK on application host side. Your own proprietary message encoder and decoder could be integrated with V2Xcast SDK easily. The only thing which has to be noticed is to arrange the proprietary messages and standard ones with different PSID.

    Some examples:

    • Following scenario of mixing messages is ok (supported by off-the-shelf product),
      • Channel: 172, PSID: 0x20, BSM
      • Channel: 172, PSID: 0x304050, Proprietary_Msg 1
      • Channel: 172, PSID: 0x304052, Proprietary_Msg 3
      • Channel: 182, PSID: 0x304051, Proprietary_Msg 2

  • 2. Certificates, encryption, and signature in terms of V2X security ?

    Encryption is not popular in the current V2X pilot deployment because most applications are designed to share status to all nearby vehicles. Most of them utilize digital signature technology to prevent tampered or fake messages. Digital signature has following characteristics,

    • Authentication
    • Integrity
    • Non-repudiation

    A message applied digital signature is not encrypted, so the content still can be read and you can decide to trust it or not through the verification of the signature included in the message. Besides, a certificate is the container of keys which could be used for encryption or digital signature, so certificates are always required no matter which one you choose finally.

  • 3. Any extra license fee or royalty required on V2Xcast® ?


    V2Xcast® is embedded in Unex’s RSU and sold at one package price for PoC or deployment to quickly meet time-for-market. The V2X package price includes the right to use Unex’s V2X protocol stack, V2Xcast®, SDK per V2XCAST® SOFTWARE LICENSE AGREEMENT, no extra license or royalty required. In addition, Unex provides 12-months hardware warranty, free software update, and technical support.

  • V2X Starter Kit (EVK-series)

  • 1. How Unex can help on V2X development and deployment ?

    Today, V2X is at a pivotal moment, you need a concrete advantage:


    How can you explore and prove your idea and use-case viability with lowest resource investment and quickest time-to-market?

    We have seen great amount of successful stories by selecting Unex’s Starter Kit. It is a very effective way to explore V2X technologies and prototype them rapidly using unified V2Xcast®– from PoC through implementation.

    With software as the core value, you can develop the exact V2X applications you need directly on the V2Xcast®. Also, you can use the same V2X application software building blocks on a wide selection of V2X technologies and devices with V2Xcast® seamlessly.

    In addition, you can utilize Unex’s V2Xcast® ecosystem to accelerate V2X innovations. Unlike closed turnkey solutions, the V2Xcast® ecosystem offers a jump-start and open V2X experience, with the ability to customize and enhance your V2X applications as requirements evolve.

  • 2. Any extra license fee or royalty required on V2Xcast® in the Starter Kit ?


    V2Xcast® is embedded in Unex’s Starter Kit and sold at one price from PoC through implementation. The starter kit package price includes the right to use Unex’s V2X protocol stack, V2Xcast®, SDK per V2XCAST® SOFTWARE LICENSE AGREEMENT, no extra license fee or royalty required. In addition, Unex provides 12-months hardware warranty, free software update, and technical support.

  • V2X Co-Creation

  • 1. How Unex Can Help ?

    Today, V2X is at a pivotal moment, you need a concrete advantage.

    We have seen great amount of successful stories by joining Unex’s V2Xcast® eco-system; you can use the same V2X application software building blocks on V2Xcast® for your own systems and license to other non-conflict technology partners. in the automotive, traffic infrastructure, and all related cross-industries.

    Utilizing an ecosystem is critical to accelerate V2X innovations and create long-term mutual wins. Unlike closed turnkey solutions, the V2Xcast® ecosystem offers a jump-start and open V2X experience, with the ability to customize and enhance your V2X applications as requirements evolve.

  • 2. What’s the main business model of Unex ?

    Unex’s business model is centered on V2X innovation. Unique key elements includes off-the-shelf V2X system, service-oriented V2Xcast®, and V2Xcast® eco-system co-creation are designed to accelerate V2X adoption and provide V2X-sensor fusion flexibility to use sensor information with V2X system to assist autonomous activities and ensure superior functional safety and redundancy.

    To realize V2X innovation, our supplemented business model based on readiness of technology and market can be typical segmented as following:

  • 3. Any must-have criteria to join co-creation ?


    Unex welcome any entity who is interested in innovation from original domain and a believer of innovation through trusted partnership co-creation.

  • 4. Why the eco-system co-creation looks like a flywheel ?


    Identifying requirements to build innovative V2X applications for future E/E architecture of software-defined vehicle and smart traffic system are a challenge. If all related hormonal and vertical entities can team-up and co-create on a production ready V2X platform and relentlessly push the giant heavy V2X flywheel to build momentum till a point of breakthrough, it will automatically turn upon turn and beyond to a un-stoppable flywheel effect to realize everyone’s vision together.

  • V2X Shipping

  • 1. How to purchase Unex’s V2X devices for evaluation and developing long-term partnership?

    Unex provides series of ready-to-use V2X devices for V2X communication which contain all the essentials of service-oriented V2Xcast® software on the optimized V2X SOM/OBU/RSU devices. Customers can effectively develop applications and services for deployment immediately, no extra V2X stack license fee or royalty.

    As the V2X devices accompany embedded V2Xcast® software and software deliverables, execution of “V2Xcast® Software License Agreement” before product delivery is required. The typical operation flow is as following:


    On-line inquiry receive not receive No Yes Yes project feasibility quo. & license agreement alternative option P.O. to Unex or Unex issues P.I. 2 nd order onwards payment & delivery co-creation exploring send email: info1@unex.com.tw

  • 2. Does Unex’s V2X belong to Strategic High-Tech Commodity which requires special import permission? What is the ECCN, CCATS and HS codes of Unex’s V2X system?


    Unex’s V2X system is a wireless device, but NOT a Strategic High-Tech Commodity, thus, NO Export Control Commodity No. valid per verification report dated on 2021/10/18.


    To effectively manage the import and tariffs issues of V2X wireless devices from Unex, please refer to the export control classification number and the corresponding harmonized system code as following:

    Product ECCN CCATS HS Code COO
    V2X Device
    (including SOM/OBU/RSU/Starter Kit)
    5A992.c Z1669849 8517.69.00.92.7 Taiwan

    Remarks:

    • ECCN: Export Control Classification Number
    • CCATS: Commodity Classification Automoted Tracking System
    • HS Code: Harmonized System Code

    • Technical Desk

      Global Headquarters

      7F-2, No.100, Sec.1, Jiafeng 11th Road., Zhubei City, Hsinchu County 302052, Taiwan

      +886-3-6578188














      Fields marked with an * are required.
      Personal note:
      We’d like to keep you updated on our next generation V2X platform and provide you with the latest news, information and announcements. To opt-out of our mailing list, just uncheck the box above. Need more info? Check our Privacy Policy.

      Copyright © 2022 Unex Technology Corporation

      Follow Unex