WEBVTT NOTE This file was exported by MacCaption version 7.0.06 to comply with the WebVTT specification dated March 27, 2017. 00:00:00.417 --> 00:00:04.671 align:center line:-1 position:50% size:57% We've heard from our industry experts on the current state of the C-V2X standard 00:00:04.671 --> 00:00:08.842 align:center line:-1 position:50% size:64% and some of what to expect as we move into more commercial applications. 00:00:08.842 --> 00:00:12.387 align:center line:-1 position:50% size:49% In this lesson, Bill is going to give us a more hands-on look 00:00:12.387 --> 00:00:17.643 align:center line:-1 position:50% size:52% at how to do test validation on the performance of C-V2X designs. 00:00:17.643 --> 00:00:22.606 align:center line:-1 position:50% size:60% Today, I'm going to give you an overview and a demonstration of our C-V2X solutions. 00:00:22.606 --> 00:00:26.652 align:center line:-1 position:50% size:54% Let me quickly go over the configuration that we have today. 00:00:26.652 --> 00:00:30.447 align:center line:-1 position:50% size:54% We have our UXM 5G network emulator 00:00:30.447 --> 00:00:36.036 align:center line:-1 position:50% size:50% running various applications that will test our cellular-V2X module. 00:00:36.036 --> 00:00:42.125 align:center line:-1 position:50% size:57% The module that we're testing today is a Qualcomm Roadrunner Evaluation Kit. 00:00:42.125 --> 00:00:44.878 align:center line:-1 position:50% size:43% What we have also is our MXG. 00:00:44.878 --> 00:00:48.340 align:center line:-1 position:50% size:41% The MXG is a GNSS emulator. 00:00:48.340 --> 00:00:52.886 align:center line:-1 position:50% size:53% As you know, GNSS is critical for cellular-V2X testing. 00:00:52.886 --> 00:00:58.767 align:center line:-1 position:50% size:48% Not only does it give geolocation but also is used for synchronization. 00:00:58.767 --> 00:01:00.269 align:center line:-1 position:50% size:45% Let me give you a quick overview. 00:01:00.269 --> 00:01:03.689 align:center line:-1 position:50% size:53% We have the GNSS going into the EVK. 00:01:03.689 --> 00:01:10.195 align:center line:-1 position:50% size:51% We have the transmission for the PC5 connected to the UXM 5G. 00:01:10.195 --> 00:01:15.325 align:center line:-1 position:50% size:48% What I have running at the moment, we have our C-V2X test application. 00:01:15.325 --> 00:01:17.661 align:center line:-1 position:50% size:43% Here, we see we have two tabs. 00:01:17.661 --> 00:01:21.915 align:center line:-1 position:50% size:50% The first tab is for our LTE connection for mode 3. 00:01:21.915 --> 00:01:25.168 align:center line:-1 position:50% size:59% The second tab here, which we have active, is our sidelink tab. 00:01:25.168 --> 00:01:30.507 align:center line:-1 position:50% size:44% We can see, it's highlighted, we have the sidelink channel on. 00:01:30.507 --> 00:01:35.971 align:center line:-1 position:50% size:58% We can see here that we are able to control and setup the channel, as well as GNSS. 00:01:35.971 --> 00:01:46.106 align:center line:-1 position:50% size:59% The UXM 5G controls the MXG for GNSS, so we are in full control right now for GNSS. 00:01:46.106 --> 00:01:49.985 align:center line:-1 position:50% size:49% A couple of tabs I'd like to show you, here, we're working on the sidelink, 00:01:49.985 --> 00:01:55.115 align:center line:-1 position:50% size:63% and we can set up what we call our schedulers, both transmission and received scheduler. 00:01:55.115 --> 00:02:00.370 align:center line:-1 position:50% size:50% These set up the channel parameters for allowing the channel allocations, 00:02:00.370 --> 00:02:06.001 align:center line:-1 position:50% size:54% the resource blocks, to be set for testing in a real-world environment. 00:02:06.001 --> 00:02:09.254 align:center line:-1 position:50% size:46% The other graph I'm going to show is our BLER throughput. 00:02:09.254 --> 00:02:12.632 align:center line:-1 position:50% size:39% When I start this scenario, we will see the transmission, 00:02:12.632 --> 00:02:17.679 align:center line:-1 position:50% size:43% the packets being transmitted and received as part of the test. 00:02:17.679 --> 00:02:21.266 align:center line:-1 position:50% size:57% What are we going to do here, we're going to set up a real-world scenario 00:02:21.266 --> 00:02:25.187 align:center line:-1 position:50% size:45% using an application that we have from our partner, NORDSYS. 00:02:25.187 --> 00:02:27.230 align:center line:-1 position:50% size:33% Let me show you it here. 00:02:27.230 --> 00:02:30.776 align:center line:-1 position:50% size:51% This is our waveBEE creator software. 00:02:30.776 --> 00:02:37.115 align:center line:-1 position:50% size:54% You can see we have created a scenario based in Germany. 00:02:37.115 --> 00:02:43.246 align:center line:-1 position:50% size:61% When we run this scenario, we will see these simulated vehicles in action. 00:02:43.246 --> 00:02:46.958 align:center line:-1 position:50% size:55% The other software I'm going to show you is our waveBEE touch. 00:02:46.958 --> 00:02:48.543 align:center line:-1 position:50% size:37% Once we start the scenario, 00:02:48.543 --> 00:02:52.964 align:center line:-1 position:50% size:44% we're going to see this scenario play out in real time on this map. 00:02:52.964 --> 00:02:59.888 align:center line:-1 position:50% size:60% The third piece of software I'm going to show is our director application. 00:02:59.888 --> 00:03:05.185 align:center line:-1 position:50% size:62% Now, this director application essentially controls the whole scenario testing. 00:03:05.185 --> 00:03:11.066 align:center line:-1 position:50% size:39% It synchronizes the scenario, the GNSS, and the UXM 5G 00:03:11.066 --> 00:03:15.028 align:center line:-1 position:50% size:36% to measure and to play out the scenario of interest. 00:03:15.028 --> 00:03:19.491 align:center line:-1 position:50% size:53% What I'm going to do now, I'm going to use the director application, 00:03:19.491 --> 00:03:23.036 align:center line:-1 position:50% size:34% which is going to initiate the whole test sequence. 00:03:23.036 --> 00:03:28.625 align:center line:-1 position:50% size:55% If I press start, we can see the whole start-up sequence. 00:03:28.625 --> 00:03:31.962 align:center line:-1 position:50% size:38% First, the director application tests the connection 00:03:31.962 --> 00:03:39.302 align:center line:-1 position:50% size:71% between the UXM 5G, and the MXG GNSS scenario, and the ITS stacks. 00:03:39.302 --> 00:03:44.099 align:center line:-1 position:50% size:56% Once it's confirmed that the connections have been validated, 00:03:44.099 --> 00:03:47.269 align:center line:-1 position:50% size:41% it loads the ITS stack scenario. 00:03:47.269 --> 00:03:52.399 align:center line:-1 position:50% size:70% Now, this scenario is from the waveBEE creator application we showed before. 00:03:52.399 --> 00:03:55.819 align:center line:-1 position:50% size:42% It takes the information from all the simulated vehicles, 00:03:55.819 --> 00:04:01.992 align:center line:-1 position:50% size:61% loads that scenario into instances of the stack running inside the UXM 5G. 00:04:01.992 --> 00:04:05.871 align:center line:-1 position:50% size:50% It then will create the GNSS scenario. 00:04:05.871 --> 00:04:13.378 align:center line:-1 position:50% size:64% This GNSS scenario is a dynamic scenario taking from the maps from the creator software. 00:04:13.378 --> 00:04:17.340 align:center line:-1 position:50% size:43% The maps will generate a geolocation dynamic scenario 00:04:17.340 --> 00:04:23.889 align:center line:-1 position:50% size:65% that we load into the GNSS emulator, which will be played out to the device under test. 00:04:23.889 --> 00:04:27.184 align:center line:-1 position:50% size:37% The module considers itself driving around Germany 00:04:27.184 --> 00:04:31.313 align:center line:-1 position:50% size:59% because it's going to be part of this scenario that we created. 00:04:31.313 --> 00:04:33.148 align:center line:-1 position:50% size:37% Here we've run through, and we're going to execute. 00:04:33.148 --> 00:04:38.778 align:center line:-1 position:50% size:68% If I look at the waveBEE touch, we can see the scenario that has been playing out. 00:04:38.778 --> 00:04:42.240 align:center line:-1 position:50% size:43% Let me zoom in a little bit here, and we can look in. 00:04:42.240 --> 00:04:44.993 align:center line:-1 position:50% size:32% We have a junction, we have some vehicles. 00:04:44.993 --> 00:04:48.246 align:center line:-1 position:50% size:65% At the moment, two vehicles are going to collide. 00:04:48.246 --> 00:04:51.583 align:center line:-1 position:50% size:55% Okay, so, the scenario has then stopped. 00:04:51.583 --> 00:04:55.545 align:center line:-1 position:50% size:51% We see the vehicles that were created in the creator application 00:04:55.545 --> 00:04:57.589 align:center line:-1 position:50% size:40% have played out the scenario. 00:04:57.589 --> 00:05:00.884 align:center line:-1 position:50% size:39% The scenario was a crash, an emergency vehicle came. 00:05:00.884 --> 00:05:04.304 align:center line:-1 position:50% size:58% We can zoom in, and we can see the situation in the junction 00:05:04.304 --> 00:05:08.225 align:center line:-1 position:50% size:49% where we have the crashed vehicles and the emergency vehicle. 00:05:08.225 --> 00:05:12.812 align:center line:-1 position:50% size:68% Let me zoom out again because one of the questions that we get asked is, 00:05:12.812 --> 00:05:18.235 align:center line:-1 position:50% size:56% "Can we test a scenario being played out, but in a congested environment?" 00:05:18.235 --> 00:05:22.155 align:center line:-1 position:50% size:56% In other words, a stress test for the device 00:05:22.155 --> 00:05:26.535 align:center line:-1 position:50% size:57% because we need to make sure the device receives the highest priority messages 00:05:26.535 --> 00:05:29.329 align:center line:-1 position:50% size:48% in the presence of multiple vehicles. 00:05:29.329 --> 00:05:32.916 align:center line:-1 position:50% size:35% I'm going to then go back to my director application, 00:05:32.916 --> 00:05:37.462 align:center line:-1 position:50% size:55% and I'm going to go to the Congestion tab, and I'm going to start congestion. 00:05:37.462 --> 00:05:43.134 align:center line:-1 position:50% size:60% We're going to create 100 simulated vehicles in the area of the scenario. 00:05:43.134 --> 00:05:44.886 align:center line:-1 position:50% size:23% I'm going to start. 00:05:44.886 --> 00:05:50.642 align:center line:-1 position:50% size:46% If I go back to my waveBEE touch, and I expand out, 00:05:50.642 --> 00:05:55.355 align:center line:-1 position:50% size:42% we can see here's the scenario in the center of our image. 00:05:55.355 --> 00:06:02.070 align:center line:-1 position:50% size:67% We're seeing that we have 100 simulated vehicles all transmitting over the PC5 link. 00:06:02.070 --> 00:06:08.618 align:center line:-1 position:50% size:64% The test would be, "Does my module under test still receive the highest priority messages 00:06:08.618 --> 00:06:12.247 align:center line:-1 position:50% size:58% in the presence of all these other vehicles?" 00:06:12.247 --> 00:06:16.918 align:center line:-1 position:50% size:60% Finally, let me go back to my test application. 00:06:16.918 --> 00:06:22.924 align:center line:-1 position:50% size:54% I'm going to look at the BLER throughput from our transmissions. 00:06:22.924 --> 00:06:31.182 align:center line:-1 position:50% size:48% I'm going to go local here, I'm going to start the measurement. 00:06:31.182 --> 00:06:36.479 align:center line:-1 position:50% size:64% When I start this BLER measurement, here I can see transmissions from the scenario. 00:06:36.479 --> 00:06:42.152 align:center line:-1 position:50% size:39% If I go back to my scenario, I'm going to start congestion. 00:06:42.152 --> 00:06:46.448 align:center line:-1 position:50% size:55% What we should see is the transmissions from the congested vehicles. 00:06:46.448 --> 00:06:50.744 align:center line:-1 position:50% size:46% We can see over the PC5 link the packets that are being created 00:06:50.744 --> 00:06:54.039 align:center line:-1 position:50% size:49% looking at these congested vehicles. 00:06:54.039 --> 00:06:58.293 align:center line:-1 position:50% size:58% This gives you some idea of the flexibility we have of our test solution. 00:06:58.293 --> 00:07:00.128 align:center line:-1 position:50% size:34% We can create scenarios. 00:07:00.128 --> 00:07:05.091 align:center line:-1 position:50% size:46% We can download these scenarios into our UXM 5G GNSS emulator. 00:07:05.091 --> 00:07:07.177 align:center line:-1 position:50% size:46% We can test if our vehicle receives 00:07:07.177 --> 00:07:10.972 align:center line:-1 position:50% size:39% and reacts appropriately to highest priority messages. 00:07:10.972 --> 00:07:12.724 align:center line:-1 position:50% size:44% Then, we can add in congestion. 00:07:12.724 --> 00:07:16.561 align:center line:-1 position:50% size:47% We can carry out those same tests in a congested environment 00:07:16.561 --> 00:07:20.482 align:center line:-1 position:50% size:41% to make sure that your module truly is ready for the market. 00:07:20.482 --> 00:07:21.316 align:center line:-1 position:50% size:30% Thank you very much.