 Before beginning my session, I have a question to the audience. Do you have how many people familiar to VTX style and VTX standards? Maybe you want, okay. At this talk, I want to introduce my open source VTX related software. I want to introduce myself. I'm working more than 10 years working telecommunication industry and also working automotive side. It's a very long time to work with this kind of communication technology. The 80s is a startup company at South Korea. So we are mainly developing VTX hardware and software and some kind of testing tools. Let's start. First of all, I want to briefly introduce VTX technology. VTX technology introduced more than 10 years ago. Basic concept is very simple. Some vehicles send their own information to others. After that, their response or some kind of action. That's the basic concept. So very similar to IoT technology. Just information sharing technology. But some kind of reaction makes some good example and application. Some slow down information and low safety related information. And also now this technology will be using smart city. All devices are connected so vehicle can connect to infrastructure and cloud or whatever. And also this technology is adapting to autonomous driving because current autonomous driver vehicle has so many sensors that there are some limitations because it is a direct sensor. But this radio based sensor can help such kind of information more longer and some behind the building information behind the building such kind of information can help autonomous driving. So fully autonomous driving maybe will be adapt this kind of technology. Currently so many pilot site is working and ongoing now. US side, Europe side and Asia also. So now there is some problem because some radio technology issue. More than 10 years DSRC 5.9 gigahertz radio technology is used in this technology. But CVTX or 5G technology will be adapted. So now two radio technologies is debating now. But despite of this situation this kind of radio technology will be increased their market. So that's a market situation and some information. I want to show first this standard. This is focused on US side. US side is different to European side. But basically final message set decision is almost same. But middle layer is a little different. This is minimum set of standard. There are so many standard but minimum set. Some kind of bottom layer is a pion Mac side. It can be 8 or 11. It is DSRC and CVTX and 5G technology with 3G PPL is 14 and 15. So this layer is radio technology and some additional handling technology for DSRC. 1609.4. And after that there are some handling feature. Normally this communication does not use TCP IP. So it can be one option. It can be one option. So it's a little different technology protocol. So many safety related message will send WSMP. WSMP protocol is short tree WSMP. And there are some security mechanism and also there are some message set to use application side. So another we should consider there are some encoding. 1609.2 uses SN.1 canonical all year format. I'm not sure you are familiar SN.1. But normally 3G PPL and many multi-video technology use this as SN.1. So another thing is this is message set dictionary. SAJ2735 uses SN.1. U-PAL we call U-PAL. But it is an aligned factory encoding rule. Grammar is the same but they encoding or decoding different tree. So it are really different. So what's the problem in this situation? First thing is protocol is so complicated that that's similar to 3G PPL or other things. So SN.1 is one of key problem. Because this new encoding rule, this OER and PEL is a little new encoding rule. So there are no open source fully supported full features of SN.1. Some kind of parameterization class such kind of new features does not support open source. So that's the main key problem of VTX technology for SN open source. But many years they development such kind of encoding decoding open source. So it's not perfect but it will closer to commercial product other. So another one is you are not permanent maybe because there are no hardware publicly available. So many IoT devices are available on market. But it's not the reason they not exist publicly. VTX is a percussion vehicle. So automotive industry does not sell to consumer or some engineer. So that's the basic reason. So and this device and module has longer development time than consumer product because this vehicle is related to safety. So that's the key problem. You cannot buy this thing even if sample. Another one is this bottom layer. As there are no of source driver because it is the same reason there are no hardware and there's a own there are vendors on device developer. It cannot be open. So that's the key. I my point there's a key to problem is the ASN problem and some device and driver problem. So I want to handle these two things many so many times. So before mention about that I will show some message information and how to handle it. There are so many messages on SAJ 2735. Fundamental message. Most basic message is the basic safety message is send to 10 hertz for each second and other there are so many messages inside it. And normally ASN done message grammar will be compiled by ASN compiler and it will generate some encoding encoder and decoder for example .c and .header. And after that we programming with this encoding decoding source code. This is a basic function maybe similar. This is sample of ASN.1 from J2735. You can easily understand it. There are some constraints. So to check their data format or binary format. Similar to 16 or 9.2 is almost same format. I pretty sure after that I tried so many open source compiler ASN.1.1. One of the best option for C compiler is ASN.1.C. You can get some link. As I remember three years ago it does not support. So I a little hack, try, try. And after that I succeeded very small portion of this ASN.1 format. But nowadays it will be almost support. The morning inside this is ASN.1 parameterization issue. There are some issues but it can be handled by programming. So almost working. We need hard test but almost working now. Compiler is separate. So that's a good time to use this open source compiler. Another one. There are some Python based compiler. It's also available. They work in Uber but OER does not support now. So I think this compiler is one solution. The one solution, only one solution. My company uses normally three different compilers. The cost is very huge. There are some issues. This right side is an example called OER. And this is Uber. Very simple. But you need some additional code to check constraints. This ASN.1c supports this constraint. But they didn't develop holdings but almost can be usable. So that's ASN.1 is handled by open source. I'll be talking about hardware later. But my open source, the basic concept is two things. I want to develop end-to-end seamless connectivity. First thing. And another thing is low retention and high reliability. So I do these things from vehicle, VTX device, vehicle, SG node to cloud. I want to convert a standard of message to some kind of interface definition language. This is, for example, the bottom vehicle side is I use ROSE, mobile operating system. Maybe you are familiar. It is used by autonomous driving research topic. And some OEM vendors are also trying now. So ASN format will changeable. It is possible very easily on the bottom side. And also there are some idea. Most people are familiar and proper by Google. Preparation is almost similar. So we can convert to some different idea. So at the bottom side, and also this idea can be convert these things. So I want to make some code, idea code from ADL, as standard one. This is my concept. So easily convert data format, bottom to top, side to back end side. Another thing is this retention and reliability. This ROSE version 2 uses data distribution service and real-time publishing and subscriber technology of TCPIP. It is mainly focused on real-time traffic. So it is low retention and high reliability. There are so many QoS technology parameter. QoS parameter DDS has. So it can be possible. And also vehicle will use this technology now. So that's a good point. And my device also supports some service access point for standard to use using IDL. So it can be connected from cloud to even VTex device. And this side is we use, many people use MQTT or FSOCAP. So it can be a good data communication channel. So MQTT also have some QoS technology. So platform IDL can convert to so many other languages. Node.js, Python, whatever. So many languages. There are more than 20 languages support. So this side is focused on C or Python because ROSE 2 supports Python. And this side is available all language technology. So vehicle device, vehicle, HG, cloud nodes can easily connect. This is my goal and concept. So I developed vehicle device and VTex device and vehicle side. There are so many, four message type of ROSE 2 technology. But mainly I introduce two things. Publicate, publisher and subscriber. This is single path. And another one is request and response. For example, the client request to service some information and data response. This is one problem. So normally receive data can be implemented using publishing subscribing technology. So it's easy. So VTex device publishes some data to 609.3. This is almost bottom layer of protocol. So they publish an upper layer. This is secret layer. That's two. And it is one thing. And this one decoding three-day, three payloads to that two payloads decoding. And after that, it's similar. That is decoding after that publishing. I say J2735 and Rx application can get if they implemented subscription. So another thing is TX app. TX app should handle whole service. So they would cast some encoding to this service. Message service and some certification service for security and send TX that some confirm. So this is the basic concept. And it will be connected to internet. So this is the basic concept. Darker one is already implemented. And this TX is now developing. So another example. This is a service access point summary 609.3. And for example, this is a very fundamental. This is a request for sending and respond. And after they get that same result, indication means receiving. So this is very basic for TX and Rx. So for example, first request and confirm can be replaced to request the response message format for those for the second. So for example, this is a, you can get some parameter information from sender. So I made it and a little removable and added something. So this is a top side is a request. Bottom side is a response. And publish is simple just one top bottom top side only. This kind of a message I made it. And other thing will be same. But so this is example. I made some device emulator to send that three publisher. This is some sender packet and they subscribe and decoding and send it to other laws and subscribe and send other laws. And this is the final result. Maybe it will be similar Rx application. And this is the most topic echo. I use most command. This is a BSM message actually. But data is almost general because I tried to some sample. So they are receiving and they displaying some information. You can get, you can use this message for application. Okay. Now next thing. How about VTX device? We want to low cost. I presented this topic 2015. I made this device. This is a single board computer. I'm X6 at the time pre-scale. And I use this Wi-Fi module. This is now less than $10. So very low cost. But this device is a little cost. I remember around $300 maybe around that. So this Wi-Fi module supports 5.9 gigahertz pack. So there are some patch and modifications that exist. And so I adapted this whole thing to this device. I succeeded TXRX with general VTX device. Normally, contrary reference implementation of VTX device the cost is around the number. Minimum $4,000 and more than. And some vendor does not sell such kind of things to a very small company. And today, we use cheap VTX cell from Qualcomm. But Qualcomm wants some license first. So you cannot easily get some module and some boards. So that's a key problem. So this is 3D data. But I designed and developed already. So this is VTX module from Ublox. This is now production. It's not sample. Normally, reference device does not have production chipset. Normally, they use engineering sample. So we cannot sell to everybody. So this is not possible. So one possible solution is from Ublox. So I adapted some controller. Normally, they use Linux application process. But I adapted this driver to MCU and make some service access point. And it will connect to Ethernet. This harness is already different. We are now using autobahn to Ethernet now. So this is not RJ45. But connected will be changeable. So we fully designed now. But we are waiting high accuracy GPS. It will be available next month. And at that time, just engineering sample. So we are waiting now. So I hope this device has a role. Similar to this device. Price is similar to this device. And a little more. Less than with this enclosure. Less than 10,000 I hope. I want to develop. So other port side application will be open source. So everybody can handle VTX and VTX related application. Most people cannot. Not easy to handle functional basic safety message. Because it depends. It sends from vehicle to vehicle. So it is related to safety. But be accurate to infrastructure. And be accurate to cloud. Will be available. So that's the reason I made this kind of device. But I'm waiting. But production. I hopefully want to production this kind of device. But if the customer will be very small. But at that time cost will be a little higher. So I think that I want to know that cost. Now trying. So I will show some pictures and roadmap. End of this month. I will upload the first source code. Wave some message. This is Rx technology. I uploaded my GIF of GitHub. And after that trying to TX. Currently I made it by hand. This function. As standard one to most ideal. But I'm trying now. Using open source as one compiler. It will be possible I think. And after that another one. We will be trying. And this device is target release date is October. And another thing is we have some module license for CVTex. So this thing is not product. So production. So engineering sample will be available maybe. End of October I think. And we will try other chips that vendor next year. Currently we have two more vendors. Two more vendors and three chips as already. Three modules. Some Japanese company. Korean company. So but next year we will adapt this device also. So for engineering and testing tool. And another. This thing is will be support release this device. Device connectivity and management. And basic security. Actually it is developing. Driving the testing tool also. We have some product. So adapt this kind of testing tool also. This is loading app. So this is GITuburl. I just put some related compiler. As standard one compiler. I unload it. I unload all things at time frame. And this is another domain. But I have some domain. This kind of thing. If you have any question or some needs. Some picture. Please send to this email. And actually this project is my personal project. This software side is developed by me. And another guy. Free time. In my company we developed just hardware. And hardware inside of firmware and software. So we separate it. So this is final information. Okay. Thanks for visiting. Do you have any question?