0 00:00:00,000 --> 00:00:30,000 Dear viewer, these subtitles were generated by a machine via the service Trint and therefore are (very) buggy. If you are capable, please help us to create good quality subtitles: https://c3subtitles.de/talk/908 Thanks! 1 00:00:15,720 --> 00:00:16,720 So. 2 00:00:17,650 --> 00:00:19,659 For the next talk for this evening, this 3 00:00:19,660 --> 00:00:20,739 is a talk that is 4 00:00:22,000 --> 00:00:24,009 personally interesting to me and I hope 5 00:00:24,010 --> 00:00:25,629 to you as well. 6 00:00:25,630 --> 00:00:27,969 I'm very much looking forward to it. 7 00:00:27,970 --> 00:00:30,399 Our next two speakers will be talking 8 00:00:30,400 --> 00:00:32,949 to us about how we can deploy GSM 9 00:00:32,950 --> 00:00:35,229 base stations over a software defined 10 00:00:35,230 --> 00:00:36,939 radio hardware. 11 00:00:36,940 --> 00:00:38,769 So very interesting things that we'll 12 00:00:38,770 --> 00:00:40,179 hear from them. 13 00:00:40,180 --> 00:00:42,639 So please welcome Vladimir Nijinsky 14 00:00:42,640 --> 00:00:43,749 and Pyotr Chrissake. 15 00:00:43,750 --> 00:00:44,909 A big round of applause to them. 16 00:00:54,190 --> 00:00:56,859 Introduction, so everyone, 17 00:00:56,860 --> 00:00:58,809 this is, however, the first talk over at 18 00:00:58,810 --> 00:01:00,939 the Congress, so thanks for having us 19 00:01:00,940 --> 00:01:02,380 here. Let's start. 20 00:01:04,269 --> 00:01:05,229 My name is what do you mean? 21 00:01:05,230 --> 00:01:07,239 It's care? I'm a researcher from Positifs 22 00:01:07,240 --> 00:01:09,709 Technologies Company to the communication 23 00:01:09,710 --> 00:01:11,169 department. 24 00:01:11,170 --> 00:01:13,359 At the same time, I'm a 25 00:01:13,360 --> 00:01:15,159 smart home contributor. 26 00:01:15,160 --> 00:01:17,559 I had some background in web development, 27 00:01:17,560 --> 00:01:19,479 but this time is gone and now I am in 28 00:01:19,480 --> 00:01:21,369 telecommunications. 29 00:01:21,370 --> 00:01:23,739 Now I prefer to use C and Python. 30 00:01:23,740 --> 00:01:25,359 And this is Peter. 31 00:01:25,360 --> 00:01:27,429 Hello, everyone. I'm Chris. 32 00:01:27,430 --> 00:01:29,679 I'm, uh, working at Warsaw 33 00:01:29,680 --> 00:01:31,599 University of Technology. 34 00:01:31,600 --> 00:01:33,819 I'm generally a person that thinks that 35 00:01:33,820 --> 00:01:36,129 free software using free software 36 00:01:36,130 --> 00:01:38,409 is a good idea and the right 37 00:01:38,410 --> 00:01:40,209 thing is even better. 38 00:01:40,210 --> 00:01:42,429 So I created some small pieces 39 00:01:42,430 --> 00:01:44,649 of free software myself, and the 40 00:01:44,650 --> 00:01:46,839 one of them is GSM. 41 00:01:46,840 --> 00:01:49,029 I will introduce you to, 42 00:01:49,030 --> 00:01:50,679 uh, later. 43 00:01:50,680 --> 00:01:52,809 Another one is multi AI 44 00:01:52,810 --> 00:01:55,029 until it's software for 45 00:01:55,030 --> 00:01:57,289 synchronizing all of 46 00:01:57,290 --> 00:01:59,799 the devices in order to 47 00:01:59,800 --> 00:02:02,379 make, uh, from them multi-channel 48 00:02:02,380 --> 00:02:03,309 receivers. 49 00:02:03,310 --> 00:02:05,889 So this is OK. 50 00:02:05,890 --> 00:02:08,079 So we are going to 51 00:02:08,080 --> 00:02:09,189 introduce our work. 52 00:02:09,190 --> 00:02:12,009 We have been doing for some long time, 53 00:02:12,010 --> 00:02:14,259 and in a few words, we will show 54 00:02:14,260 --> 00:02:16,329 you how to run the GSM mobile 55 00:02:16,330 --> 00:02:19,449 phone on software defined radio. 56 00:02:19,450 --> 00:02:21,639 And as you probably already know, 57 00:02:21,640 --> 00:02:23,769 our project is based on mostly 58 00:02:23,770 --> 00:02:26,169 based on a smartphone project. 59 00:02:26,170 --> 00:02:28,389 So we will introduce it in a few words, 60 00:02:28,390 --> 00:02:30,459 and we will tell you what's wrong with 61 00:02:30,460 --> 00:02:32,979 the currently supported hardware 62 00:02:32,980 --> 00:02:35,109 and the way our work makes 63 00:02:35,110 --> 00:02:37,389 sense. And finally, we will show you some 64 00:02:37,390 --> 00:02:38,390 demonstration. 65 00:02:40,330 --> 00:02:42,549 So let me ask how many people 66 00:02:42,550 --> 00:02:43,509 here used to play. 67 00:02:43,510 --> 00:02:45,309 We so smart can be be Horacio, hence 68 00:02:45,310 --> 00:02:47,529 pleasing and not so 69 00:02:47,530 --> 00:02:49,799 much. But anyway, thanks. 70 00:02:49,800 --> 00:02:52,059 And so from my experience, when 71 00:02:52,060 --> 00:02:54,039 people hear about the smartphone TV, they 72 00:02:54,040 --> 00:02:56,349 basically amazing and of 73 00:02:56,350 --> 00:02:58,539 Motorola phone, a Motorola phone which 74 00:02:58,540 --> 00:03:00,699 is always hanging somewhere. 75 00:03:00,700 --> 00:03:02,350 So let's what is it? 76 00:03:03,440 --> 00:03:05,769 And it's not a secret for everyone 77 00:03:05,770 --> 00:03:07,989 that your phone actually 78 00:03:07,990 --> 00:03:10,149 has separate baseband processor that 79 00:03:10,150 --> 00:03:12,999 takes care about the network operation. 80 00:03:13,000 --> 00:03:15,009 No matter which operating system do you 81 00:03:15,010 --> 00:03:17,079 prefer to use when you're 82 00:03:17,080 --> 00:03:19,389 sending a short message for a call 83 00:03:19,390 --> 00:03:20,679 into your friend? 84 00:03:20,680 --> 00:03:22,929 Your operating system currently asks 85 00:03:22,930 --> 00:03:25,269 the second baseman processor 86 00:03:25,270 --> 00:03:27,459 to do that. 87 00:03:27,460 --> 00:03:29,649 So Baseband Processor is typically 88 00:03:29,650 --> 00:03:32,619 running some proprietary 89 00:03:32,620 --> 00:03:34,689 firmware and has many 90 00:03:34,690 --> 00:03:36,249 other people. We don't trust these 91 00:03:36,250 --> 00:03:38,619 firmware, so 92 00:03:38,620 --> 00:03:40,299 that's the main idea of us. 93 00:03:40,300 --> 00:03:42,459 My TV project is to 94 00:03:42,460 --> 00:03:44,769 provide the open source 95 00:03:44,770 --> 00:03:46,899 implementation of 96 00:03:46,900 --> 00:03:49,719 phone side stick of GSM 97 00:03:49,720 --> 00:03:51,879 and to the higher levels of 98 00:03:51,880 --> 00:03:54,099 this thicker they'd 99 00:03:54,100 --> 00:03:56,379 be represented by software running 100 00:03:56,380 --> 00:03:58,869 on your host side PC 101 00:03:58,870 --> 00:04:01,149 and to the lower layer is 102 00:04:01,150 --> 00:04:03,639 layer. One is firmware, 103 00:04:03,640 --> 00:04:05,559 which is running on some calypso based 104 00:04:05,560 --> 00:04:08,229 form and to the implementation 105 00:04:08,230 --> 00:04:10,059 is more or less complete so you can make 106 00:04:10,060 --> 00:04:12,159 some voice call and receive for some 107 00:04:12,160 --> 00:04:14,079 assistance and so on. 108 00:04:14,080 --> 00:04:16,268 But at the same time, this project is not 109 00:04:16,269 --> 00:04:18,459 actively maintained at the moment. 110 00:04:20,970 --> 00:04:23,219 So you might ask me, why 111 00:04:23,220 --> 00:04:25,009 do I need this project for food? 112 00:04:25,010 --> 00:04:26,939 What for is it since? 113 00:04:26,940 --> 00:04:29,069 Well, it depends on who you are if you 114 00:04:29,070 --> 00:04:31,499 are a student 115 00:04:31,500 --> 00:04:34,139 or just a beginner, here to me, 116 00:04:34,140 --> 00:04:36,089 became your best friend in practical 117 00:04:36,090 --> 00:04:38,069 learning of GSM Stick. 118 00:04:38,070 --> 00:04:39,899 If you are some kind of security 119 00:04:39,900 --> 00:04:42,029 researcher or doing something related 120 00:04:42,030 --> 00:04:44,309 in GSM networks, you probably already 121 00:04:44,310 --> 00:04:46,499 know about this project and I don't need 122 00:04:46,500 --> 00:04:48,779 to explain you. 123 00:04:48,780 --> 00:04:51,029 And of course, it mostly helps 124 00:04:51,030 --> 00:04:53,639 to debunk existing cosmic projects. 125 00:04:53,640 --> 00:04:54,640 So. 126 00:04:55,570 --> 00:04:57,740 Yeah, and, uh, 127 00:04:59,320 --> 00:05:01,659 a few years ago, there were a few 128 00:05:01,660 --> 00:05:04,299 weeks leaks of 129 00:05:04,300 --> 00:05:06,969 to eclipse source code and 130 00:05:06,970 --> 00:05:09,649 documentation, and these allowed 131 00:05:09,650 --> 00:05:11,769 some researchers to 132 00:05:11,770 --> 00:05:14,019 reverse engineer the firmware of 133 00:05:14,020 --> 00:05:16,599 some old Motorola phones. 134 00:05:16,600 --> 00:05:18,159 And uh, yeah. 135 00:05:18,160 --> 00:05:20,259 So the 136 00:05:20,260 --> 00:05:22,209 primary hardware for us going to be 137 00:05:22,210 --> 00:05:24,699 mostly Motorola Moto Calypso 138 00:05:24,700 --> 00:05:27,789 based phones, mostly Motorola C1, 139 00:05:27,790 --> 00:05:29,199 something like that. 140 00:05:29,200 --> 00:05:32,259 And such phones run custom firmware, 141 00:05:32,260 --> 00:05:34,419 which represents layer one of GSM 142 00:05:34,420 --> 00:05:36,699 stick, and these firmware interacts with 143 00:05:36,700 --> 00:05:39,609 the whole software via a serial link. 144 00:05:39,610 --> 00:05:42,009 And mostly the problem is that 145 00:05:42,010 --> 00:05:44,799 this phone were not doesn't 146 00:05:44,800 --> 00:05:46,569 do much of things. 147 00:05:46,570 --> 00:05:48,759 It mostly drives a proprietary 148 00:05:48,760 --> 00:05:49,870 DSP and. 149 00:05:51,190 --> 00:05:53,049 What, what was the problem, what is the 150 00:05:53,050 --> 00:05:55,299 problem is that such hardware is 151 00:05:55,300 --> 00:05:58,149 not manufactured anymore, mostly 152 00:05:58,150 --> 00:06:00,489 and to the DSP, which is digital 153 00:06:00,490 --> 00:06:02,709 signaling processor is not a fully 154 00:06:02,710 --> 00:06:03,789 researched. 155 00:06:03,790 --> 00:06:05,889 So you still rely on the black 156 00:06:05,890 --> 00:06:08,049 box running open 157 00:06:08,050 --> 00:06:09,659 source software. 158 00:06:09,660 --> 00:06:11,889 And finally, this is not 159 00:06:11,890 --> 00:06:13,779 fully open source implementation. 160 00:06:13,780 --> 00:06:15,999 And so the hardware at these 161 00:06:16,000 --> 00:06:18,189 limits you in some ways, for 162 00:06:18,190 --> 00:06:20,169 example, you cannot operate in superior 163 00:06:20,170 --> 00:06:22,359 small despite the hardware is capable to 164 00:06:22,360 --> 00:06:23,649 do that. 165 00:06:23,650 --> 00:06:25,839 So what happens if we try 166 00:06:25,840 --> 00:06:27,819 to replace some of the calypso based 167 00:06:27,820 --> 00:06:29,259 fuel? We use something else. 168 00:06:29,260 --> 00:06:31,059 For example, what about software defined 169 00:06:31,060 --> 00:06:33,219 radio and what 170 00:06:33,220 --> 00:06:34,629 is software defined radio? 171 00:06:34,630 --> 00:06:36,939 It is a general purpose radio 172 00:06:36,940 --> 00:06:38,079 hardware. 173 00:06:38,080 --> 00:06:40,089 It's not limited to any particular 174 00:06:40,090 --> 00:06:42,429 technology or software stack. 175 00:06:42,430 --> 00:06:44,559 And so this means that it could be 176 00:06:44,560 --> 00:06:46,959 used for different technologies 177 00:06:46,960 --> 00:06:48,610 and protocols like 178 00:06:50,170 --> 00:06:52,899 LTE, Bluetooth, GSM 179 00:06:52,900 --> 00:06:56,079 and of course, this system. 180 00:06:56,080 --> 00:06:58,179 So, you know, 181 00:06:58,180 --> 00:07:00,069 the good news here is that this is open 182 00:07:00,070 --> 00:07:01,299 source friendly. 183 00:07:01,300 --> 00:07:03,429 Many open source projects do support the 184 00:07:03,430 --> 00:07:05,859 smoke. Sorry is there 185 00:07:05,860 --> 00:07:07,989 and to many, as there are vendors who 186 00:07:07,990 --> 00:07:09,220 do support to 187 00:07:11,740 --> 00:07:13,809 open source, actually. 188 00:07:13,810 --> 00:07:15,879 And of course, software 189 00:07:15,880 --> 00:07:18,309 defined Storage A is popular 190 00:07:18,310 --> 00:07:20,409 in scope of mobile communications, so 191 00:07:20,410 --> 00:07:22,809 you can around your own LTE 192 00:07:22,810 --> 00:07:25,089 network, for example, or run 193 00:07:25,090 --> 00:07:26,409 your own GSM network. 194 00:07:26,410 --> 00:07:28,479 You can even run LTE mobile, 195 00:07:28,480 --> 00:07:30,039 said Stack. 196 00:07:30,040 --> 00:07:31,719 But what about GSM? 197 00:07:31,720 --> 00:07:34,119 Can we run a mobile 198 00:07:34,120 --> 00:07:36,519 phone on GSM actually 199 00:07:36,520 --> 00:07:37,890 and host? 200 00:07:39,340 --> 00:07:40,340 Yes. 201 00:07:41,390 --> 00:07:44,209 This is actually when our work 202 00:07:44,210 --> 00:07:45,210 comes to play. 203 00:07:48,010 --> 00:07:50,169 So to remember, this 204 00:07:50,170 --> 00:07:52,359 is general purpose hardware. 205 00:07:52,360 --> 00:07:54,459 So there is no screen, there is 206 00:07:54,460 --> 00:07:57,159 no keyboards, there's no scenery. 207 00:07:57,160 --> 00:07:59,109 Would your subsystem? 208 00:07:59,110 --> 00:08:01,089 But in general, we are not going to 209 00:08:01,090 --> 00:08:03,459 create another Open-Source user targeted 210 00:08:03,460 --> 00:08:04,460 form. 211 00:08:04,870 --> 00:08:06,609 So then you ask me, 212 00:08:07,690 --> 00:08:09,349 what is it for? 213 00:08:09,350 --> 00:08:11,679 And mostly this 214 00:08:11,680 --> 00:08:14,439 inherits some 215 00:08:14,440 --> 00:08:16,839 of the items from 216 00:08:16,840 --> 00:08:18,579 Michael Colombie project, and as 217 00:08:18,580 --> 00:08:20,019 mentioned before, it's mostly for 218 00:08:20,020 --> 00:08:22,419 education and research and development. 219 00:08:22,420 --> 00:08:24,669 And this allows you 220 00:08:24,670 --> 00:08:26,979 to implement absolutely open source 221 00:08:26,980 --> 00:08:29,019 layer one implementation. 222 00:08:29,020 --> 00:08:31,029 And this allows you to 223 00:08:32,710 --> 00:08:34,808 get another hardware platform for us, 224 00:08:34,809 --> 00:08:36,279 Michael MBB. 225 00:08:36,280 --> 00:08:38,379 And yeah, 226 00:08:38,380 --> 00:08:40,899 this let's turn back time and 227 00:08:40,900 --> 00:08:43,209 imagine that we are developing that 228 00:08:43,210 --> 00:08:45,159 software defined radio platform for us. 229 00:08:45,160 --> 00:08:46,419 More can be built from scratch. 230 00:08:48,150 --> 00:08:51,159 And from what did we start this 231 00:08:51,160 --> 00:08:53,199 here on the top of this picture? 232 00:08:53,200 --> 00:08:54,669 You can see the full smartphone 233 00:08:54,670 --> 00:08:56,799 application, which was previously used 234 00:08:56,800 --> 00:08:59,259 to connect to 235 00:08:59,260 --> 00:09:01,599 the higher level applications and to 236 00:09:01,600 --> 00:09:03,849 a lower level represented by firmware 237 00:09:03,850 --> 00:09:04,929 together. 238 00:09:04,930 --> 00:09:07,059 And so the higher 239 00:09:07,060 --> 00:09:08,949 applications you use to communicate, we 240 00:09:08,950 --> 00:09:09,950 are serial link. 241 00:09:11,020 --> 00:09:13,329 But in our case, we don't have firmware 242 00:09:13,330 --> 00:09:15,489 anymore. We don't have one and we need 243 00:09:15,490 --> 00:09:17,259 to communicate with software defined 244 00:09:17,260 --> 00:09:18,729 radios somehow. 245 00:09:18,730 --> 00:09:19,730 So. 246 00:09:20,810 --> 00:09:22,759 Yeah, after a quick look at the source 247 00:09:22,760 --> 00:09:25,639 code of a smoking baby, we found that the 248 00:09:25,640 --> 00:09:28,159 easy to do use 249 00:09:28,160 --> 00:09:30,409 layer one control protocol, which is 250 00:09:30,410 --> 00:09:33,079 a custom but pretty simple protocol. 251 00:09:33,080 --> 00:09:35,449 And the good news is that this protocol 252 00:09:35,450 --> 00:09:37,819 was already implemented in software 253 00:09:37,820 --> 00:09:39,889 of higher levels and in silver 254 00:09:39,890 --> 00:09:40,819 too. 255 00:09:40,820 --> 00:09:42,889 And so the problem is that 256 00:09:42,890 --> 00:09:44,959 smoking baby host applications do 257 00:09:44,960 --> 00:09:47,149 understand that layer two friends, 258 00:09:47,150 --> 00:09:49,399 but not the layer one bursts, 259 00:09:49,400 --> 00:09:51,739 so you need to 260 00:09:51,740 --> 00:09:54,319 implement some kind of burst coding 261 00:09:54,320 --> 00:09:55,759 from here. 262 00:09:55,760 --> 00:09:57,859 And so another problem is that 263 00:09:57,860 --> 00:10:00,379 her host applications 264 00:10:00,380 --> 00:10:02,449 don't care about time division multiple 265 00:10:02,450 --> 00:10:03,439 access. 266 00:10:03,440 --> 00:10:06,209 And this is one of some basic technology 267 00:10:06,210 --> 00:10:07,210 in GSM, 268 00:10:08,720 --> 00:10:11,179 so we need to implement some kind of TDMA 269 00:10:11,180 --> 00:10:12,679 scheduler here. 270 00:10:12,680 --> 00:10:14,419 And also why beauty has became so our 271 00:10:14,420 --> 00:10:16,489 source of inspiration because most 272 00:10:16,490 --> 00:10:18,439 Phenix already implemented here. 273 00:10:18,440 --> 00:10:20,629 So we separated the common 274 00:10:20,630 --> 00:10:22,759 part of What's My 275 00:10:22,760 --> 00:10:24,919 Beats, which is actually also my 276 00:10:24,920 --> 00:10:28,009 that base station project. 277 00:10:28,010 --> 00:10:30,559 And we created a separate 278 00:10:30,560 --> 00:10:32,749 shared library called Holebas my coding 279 00:10:33,800 --> 00:10:36,079 clean up and to clean up, 280 00:10:36,080 --> 00:10:38,269 and documented some parts of 281 00:10:38,270 --> 00:10:40,979 code and extent that we use accelerated 282 00:10:40,980 --> 00:10:43,249 Twitter. We decoder. 283 00:10:43,250 --> 00:10:45,499 And also we took some basic, 284 00:10:45,500 --> 00:10:47,539 simple structures like multi-frame 285 00:10:47,540 --> 00:10:49,459 structure or clock synchronization 286 00:10:49,460 --> 00:10:51,649 routines from OsmAnd 287 00:10:51,650 --> 00:10:52,650 betas as these. 288 00:10:53,900 --> 00:10:55,699 And finally, now we have to call an 289 00:10:55,700 --> 00:10:57,979 application and now we can communicate 290 00:10:57,980 --> 00:10:59,569 with quite level applications. 291 00:10:59,570 --> 00:11:01,969 But still, we cannot communicate 292 00:11:01,970 --> 00:11:03,439 with software defined radio each other. 293 00:11:03,440 --> 00:11:06,229 We can receive words 294 00:11:06,230 --> 00:11:08,389 transcode, perform, encoding and 295 00:11:08,390 --> 00:11:10,459 decoding for them, but we cannot 296 00:11:10,460 --> 00:11:11,539 directly communicate. 297 00:11:11,540 --> 00:11:13,010 It's off to a different event. 298 00:11:14,060 --> 00:11:16,189 There is two or six protocol, 299 00:11:16,190 --> 00:11:18,469 which was first introduced in Open Beta 300 00:11:18,470 --> 00:11:20,629 Project, and it's still used by us 301 00:11:20,630 --> 00:11:22,489 one betas to communicate with 302 00:11:22,490 --> 00:11:23,629 transceiver. 303 00:11:23,630 --> 00:11:25,669 And basically, it assumes three UDP 304 00:11:25,670 --> 00:11:27,949 sockets, one for resource management 305 00:11:27,950 --> 00:11:30,259 and other for full frame 306 00:11:30,260 --> 00:11:32,539 clock indications, and the 307 00:11:32,540 --> 00:11:34,969 other four have actually 308 00:11:34,970 --> 00:11:35,970 four beers. 309 00:11:37,340 --> 00:11:39,439 And so, okay, we implemented these 310 00:11:39,440 --> 00:11:41,689 two into applications and now 311 00:11:41,690 --> 00:11:43,369 a smart compose for Be Bibbins also 312 00:11:43,370 --> 00:11:45,499 ambitious projects to support 313 00:11:45,500 --> 00:11:47,749 your interface, so we will connect 314 00:11:47,750 --> 00:11:50,239 them together to for early development 315 00:11:50,240 --> 00:11:53,119 and testing without actual hardware. 316 00:11:53,120 --> 00:11:54,799 And yes, of course, we can do that. 317 00:11:54,800 --> 00:11:56,899 And so we will come fix your X 318 00:11:56,900 --> 00:11:58,979 toolkit to assist a set of tools written 319 00:11:58,980 --> 00:12:01,429 in Python and mostly 320 00:12:01,430 --> 00:12:03,679 used for debugging series interface. 321 00:12:03,680 --> 00:12:05,449 And the most interesting application here 322 00:12:05,450 --> 00:12:06,730 is fake Zurich's. 323 00:12:08,030 --> 00:12:09,619 It works. 324 00:12:09,620 --> 00:12:11,699 It allows you to connect to 325 00:12:11,700 --> 00:12:14,089 rescan directly to Cosmo and Beats 326 00:12:14,090 --> 00:12:14,989 application. 327 00:12:14,990 --> 00:12:17,329 It acts like a proxy on the 328 00:12:17,330 --> 00:12:19,609 level one, so you don't need 329 00:12:19,610 --> 00:12:20,939 any hardware to interact. 330 00:12:20,940 --> 00:12:23,329 To use your open source network from 331 00:12:23,330 --> 00:12:25,619 open source stack mobile sites 332 00:12:25,620 --> 00:12:27,679 stack and to what is 333 00:12:27,680 --> 00:12:29,929 the purpose of these tools. 334 00:12:29,930 --> 00:12:32,029 For example, you can learn whole juice 335 00:12:32,030 --> 00:12:33,829 and stack without hardware. 336 00:12:33,830 --> 00:12:35,809 You can perform simulation tests and 337 00:12:35,810 --> 00:12:38,239 stress testing without hardware hands. 338 00:12:38,240 --> 00:12:40,489 Of course, you can test and debug other 339 00:12:40,490 --> 00:12:41,490 projects. 340 00:12:42,470 --> 00:12:44,869 And yeah, so we need the last part which 341 00:12:44,870 --> 00:12:46,759 you should directly communicate with 342 00:12:46,760 --> 00:12:49,579 transceiver and see what these 343 00:12:49,580 --> 00:12:52,009 applications should do is to perform 344 00:12:52,010 --> 00:12:53,599 downlink, build detection and the 345 00:12:53,600 --> 00:12:54,829 modulation. 346 00:12:54,830 --> 00:12:57,049 It should be able to appear 347 00:12:57,050 --> 00:12:59,869 for uplink burst modulation. 348 00:12:59,870 --> 00:13:02,299 And uh, yeah, it should follow 349 00:13:02,300 --> 00:13:03,300 the TDMA 350 00:13:04,560 --> 00:13:07,099 today, many times system of GSM. 351 00:13:07,100 --> 00:13:09,079 And of course, finally, you should talk 352 00:13:09,080 --> 00:13:11,209 to Eric's interface, which is currently 353 00:13:11,210 --> 00:13:13,719 supported by Terex called application. 354 00:13:13,720 --> 00:13:14,720 So. 355 00:13:16,640 --> 00:13:18,829 Yeah, there are two programs, 356 00:13:18,830 --> 00:13:20,899 which my feet are requirements, 357 00:13:20,900 --> 00:13:22,999 and one of them is source materials, and 358 00:13:23,000 --> 00:13:26,069 he's still used in the smartkom project. 359 00:13:26,070 --> 00:13:28,429 Basically, it's designed, 360 00:13:28,430 --> 00:13:30,679 designed to act as a witness 361 00:13:30,680 --> 00:13:32,359 and it could be used. 362 00:13:32,360 --> 00:13:34,459 But the source code is having a mix 363 00:13:34,460 --> 00:13:36,409 of C and C++ and C. 364 00:13:36,410 --> 00:13:38,689 You need to understand 365 00:13:38,690 --> 00:13:40,849 the whole infrastructure to make 366 00:13:40,850 --> 00:13:43,339 some little modifications here, 367 00:13:43,340 --> 00:13:45,259 and probably we will take care about 368 00:13:45,260 --> 00:13:46,999 those maturities in the future. 369 00:13:47,000 --> 00:13:48,619 So also there is D.R. 370 00:13:48,620 --> 00:13:50,719 JSM, and so this is 371 00:13:50,720 --> 00:13:52,999 a new radio out of three model to 372 00:13:53,000 --> 00:13:54,109 play with GSM. 373 00:13:54,110 --> 00:13:56,659 So it's modular, easy to modify 374 00:13:56,660 --> 00:13:57,739 everything 'cause you need. 375 00:13:57,740 --> 00:13:59,959 So why not to try this too? 376 00:13:59,960 --> 00:14:00,960 And yeah, 377 00:14:02,120 --> 00:14:04,399 this is why I contacted 378 00:14:04,400 --> 00:14:06,529 my friend Peter to 379 00:14:06,530 --> 00:14:09,559 continue work on that direction together. 380 00:14:09,560 --> 00:14:10,560 So, yeah, 381 00:14:11,600 --> 00:14:13,759 and my, uh, the part of 382 00:14:13,760 --> 00:14:16,159 my work was, uh, implementing 383 00:14:16,160 --> 00:14:18,349 the birth transceiver for the 384 00:14:18,350 --> 00:14:19,789 GSM. 385 00:14:19,790 --> 00:14:21,979 And it is both, as Vadim 386 00:14:21,980 --> 00:14:24,049 said on GSM, which is 387 00:14:24,050 --> 00:14:26,449 relying on the radio. 388 00:14:26,450 --> 00:14:29,179 The Georgeson project was, 389 00:14:29,180 --> 00:14:31,459 uh, started from the part of 390 00:14:31,460 --> 00:14:33,649 April project that years ago 391 00:14:33,650 --> 00:14:36,139 in 2009. 392 00:14:36,140 --> 00:14:38,569 Other two April project it was called 393 00:14:38,570 --> 00:14:40,639 GSM receiver, but it is 394 00:14:40,640 --> 00:14:43,129 now much more from 395 00:14:43,130 --> 00:14:45,739 just a software from, uh, 396 00:14:45,740 --> 00:14:47,929 for passive receiving birth. 397 00:14:47,930 --> 00:14:50,019 It's also it also does 398 00:14:50,020 --> 00:14:52,159 the multiplexing the thing, 399 00:14:52,160 --> 00:14:54,289 uh, birth it because radio 400 00:14:54,290 --> 00:14:56,579 works for recording different 401 00:14:56,580 --> 00:14:58,789 logical channels for deterring 402 00:14:58,790 --> 00:15:00,889 birth and the there are 403 00:15:00,890 --> 00:15:03,559 also out of box applications 404 00:15:03,560 --> 00:15:05,719 and demonstrating how to compose 405 00:15:05,720 --> 00:15:07,909 these, uh, these blocks into working 406 00:15:07,910 --> 00:15:10,219 applications. There is application for 407 00:15:10,220 --> 00:15:12,769 life monitoring, uh, the GSM 408 00:15:12,770 --> 00:15:15,799 broadcast on the, uh, decoding 409 00:15:15,800 --> 00:15:17,959 different digital channels and analyzing 410 00:15:17,960 --> 00:15:20,059 them in Wireshark 411 00:15:20,060 --> 00:15:22,589 and also for searching bits 412 00:15:22,590 --> 00:15:24,649 is active, uh, in the 413 00:15:24,650 --> 00:15:25,969 area. 414 00:15:25,970 --> 00:15:28,339 So what was the initial project 415 00:15:28,340 --> 00:15:30,589 status? It was, uh, that 416 00:15:30,590 --> 00:15:33,319 we had the phone receiver, 417 00:15:33,320 --> 00:15:35,959 but what was missing was, of course, for 418 00:15:35,960 --> 00:15:37,639 trans transceiver training. 419 00:15:37,640 --> 00:15:39,829 And what was, uh 420 00:15:39,830 --> 00:15:42,139 to do was to implement GSM 421 00:15:42,140 --> 00:15:43,909 based modulator. 422 00:15:43,910 --> 00:15:46,129 Uh, then figure out how to 423 00:15:46,130 --> 00:15:48,679 synchronize the transmit the signal, 424 00:15:48,680 --> 00:15:51,859 uh, coming out from this modulator, 425 00:15:51,860 --> 00:15:54,169 uh, weave signal received from the 426 00:15:54,170 --> 00:15:55,759 base and base station. 427 00:15:55,760 --> 00:15:58,459 And then we actually had some 428 00:15:58,460 --> 00:16:00,529 constant the name of said that 429 00:16:00,530 --> 00:16:03,259 needed to be corrected. 430 00:16:03,260 --> 00:16:05,419 And in the end, we had to 431 00:16:05,420 --> 00:16:06,739 verify leave. 432 00:16:06,740 --> 00:16:09,019 If the signal transmitted to 433 00:16:09,020 --> 00:16:11,119 the, uh, radio, uh, 434 00:16:11,120 --> 00:16:13,849 radio output is is the right point. 435 00:16:13,850 --> 00:16:16,879 So we don't interfere with anyone's, 436 00:16:16,880 --> 00:16:18,980 uh, license, but. 437 00:16:20,740 --> 00:16:23,319 So very short introduction of a 438 00:16:23,320 --> 00:16:25,809 GSM signal, 439 00:16:25,810 --> 00:16:28,299 the uh um, interface, 440 00:16:28,300 --> 00:16:30,459 the radio interface 441 00:16:30,460 --> 00:16:31,869 of GSM. 442 00:16:31,870 --> 00:16:33,999 It uses the time division 443 00:16:34,000 --> 00:16:36,309 multiple access, uh, with 444 00:16:36,310 --> 00:16:38,709 frames containing eight 445 00:16:38,710 --> 00:16:39,729 time slots. 446 00:16:39,730 --> 00:16:41,949 Each time slot carries 447 00:16:41,950 --> 00:16:44,799 one GSM burst its kind of 448 00:16:44,800 --> 00:16:46,600 GSM packet 449 00:16:47,650 --> 00:16:50,199 and these packets are usually modulated. 450 00:16:50,200 --> 00:16:52,239 We've got on the minimum shift keying 451 00:16:52,240 --> 00:16:55,029 modulation and the the 452 00:16:55,030 --> 00:16:57,159 uh, position of each burst is 453 00:16:57,160 --> 00:16:58,809 precisely defined by 454 00:16:59,950 --> 00:17:02,139 the frame number and time slot 455 00:17:02,140 --> 00:17:04,659 number in which they should be 456 00:17:04,660 --> 00:17:06,009 transmitted. 457 00:17:06,010 --> 00:17:08,318 So the first task was to implement 458 00:17:08,319 --> 00:17:10,419 the modulator and 459 00:17:10,420 --> 00:17:12,729 uh, it was actually quite 460 00:17:12,730 --> 00:17:14,828 simple because all of the 461 00:17:14,829 --> 00:17:16,959 building blocks were, uh, 462 00:17:16,960 --> 00:17:19,959 already in the can radio. 463 00:17:19,960 --> 00:17:21,939 So I just had to figure out how to 464 00:17:21,940 --> 00:17:24,259 connect them together to make, uh, 465 00:17:24,260 --> 00:17:26,020 working GSM 466 00:17:27,310 --> 00:17:28,358 modulator. 467 00:17:28,359 --> 00:17:30,849 There is already GMA's came on later 468 00:17:30,850 --> 00:17:33,189 in the radio and then some 469 00:17:33,190 --> 00:17:35,139 with some blocks of cocaine, some blocks 470 00:17:35,140 --> 00:17:37,419 together. Uh, 471 00:17:37,420 --> 00:17:39,969 you can perform differential encoding, 472 00:17:39,970 --> 00:17:41,769 connecting together and hope that it 473 00:17:41,770 --> 00:17:43,959 would work. And uh, yeah, 474 00:17:43,960 --> 00:17:46,359 it's it should work, actually. 475 00:17:47,620 --> 00:17:49,749 And the 476 00:17:49,750 --> 00:17:51,909 other task was to synchronize 477 00:17:51,910 --> 00:17:54,549 the transmitter and receiver, 478 00:17:54,550 --> 00:17:57,609 it received signal. 479 00:17:57,610 --> 00:17:59,739 And this wasn't as 480 00:17:59,740 --> 00:18:00,939 easy. 481 00:18:00,940 --> 00:18:03,429 Uh, but in the end, the implementation 482 00:18:03,430 --> 00:18:05,589 isn't very large for 483 00:18:05,590 --> 00:18:07,959 this. So, uh, we have following task, 484 00:18:07,960 --> 00:18:10,179 we have, uh, burst, 485 00:18:10,180 --> 00:18:12,349 uh, coming from the upper layer, the 486 00:18:12,350 --> 00:18:14,589 cuff, uh, frame number and times 487 00:18:14,590 --> 00:18:15,909 and number. 488 00:18:15,910 --> 00:18:18,339 And then we have to somehow transmit 489 00:18:18,340 --> 00:18:21,069 them in precisely, uh, 490 00:18:21,070 --> 00:18:23,419 defined moment in the 491 00:18:23,420 --> 00:18:25,239 40 day structure. 492 00:18:25,240 --> 00:18:27,519 So for this, very helpful is the 493 00:18:27,520 --> 00:18:29,949 father clock that is in the, 494 00:18:29,950 --> 00:18:32,319 uh, inside of the software defined 495 00:18:32,320 --> 00:18:34,839 radios that we use is you SRP. 496 00:18:36,060 --> 00:18:38,219 It allows for transmitting at 497 00:18:38,220 --> 00:18:40,379 precisely defined 498 00:18:40,380 --> 00:18:42,719 moment, and to 499 00:18:42,720 --> 00:18:44,819 receive signal is also 500 00:18:44,820 --> 00:18:47,009 talked with for the 501 00:18:47,010 --> 00:18:49,589 current time. So you have the 502 00:18:49,590 --> 00:18:52,949 time attached to a sample 503 00:18:52,950 --> 00:18:55,409 and then the receiver 504 00:18:55,410 --> 00:18:57,599 based on this metadata 505 00:18:57,600 --> 00:18:59,009 can track current time. 506 00:19:00,390 --> 00:19:02,939 And if it receives a signal 507 00:19:02,940 --> 00:19:05,189 coming from from a base 508 00:19:05,190 --> 00:19:07,289 station, it can synchronize with 509 00:19:07,290 --> 00:19:09,899 this signal 510 00:19:09,900 --> 00:19:12,659 and to associate 511 00:19:12,660 --> 00:19:14,909 with reception time to frame 512 00:19:14,910 --> 00:19:16,679 and time slot number. 513 00:19:16,680 --> 00:19:18,749 So this pair of information 514 00:19:18,750 --> 00:19:21,599 is then used for, uh, 515 00:19:21,600 --> 00:19:23,939 for performing the conversion 516 00:19:23,940 --> 00:19:26,159 of frame numbers and types of numbers 517 00:19:26,160 --> 00:19:28,859 into, uh, transmit, 518 00:19:28,860 --> 00:19:31,109 uh, time box that are other 519 00:19:31,110 --> 00:19:33,629 to, uh, to the burst data 520 00:19:33,630 --> 00:19:37,139 for the, uh, for the transmitting. 521 00:19:37,140 --> 00:19:39,599 And based on this information, 522 00:19:39,600 --> 00:19:42,359 after the modulator, 523 00:19:42,360 --> 00:19:44,969 the bursts are transmitted 524 00:19:44,970 --> 00:19:47,429 by us p at precisely 525 00:19:47,430 --> 00:19:48,430 different moments. 526 00:19:51,280 --> 00:19:53,799 So after this, uh, 527 00:19:53,800 --> 00:19:55,899 finishing this task, we still 528 00:19:55,900 --> 00:19:58,629 get some unknown, but the 529 00:19:58,630 --> 00:20:01,659 constant delay caused mainly by 530 00:20:01,660 --> 00:20:03,879 signal processing algorithms like, for 531 00:20:03,880 --> 00:20:06,069 example, low pass filtering and 532 00:20:06,070 --> 00:20:08,619 also by as the hardware. 533 00:20:08,620 --> 00:20:10,819 So we needed to take it into account. 534 00:20:10,820 --> 00:20:12,969 And so we 535 00:20:12,970 --> 00:20:13,970 did. This is 536 00:20:15,220 --> 00:20:17,649 here. So we 537 00:20:17,650 --> 00:20:19,869 have a signal coming from the 538 00:20:19,870 --> 00:20:23,499 base station to the U.S.A., 539 00:20:23,500 --> 00:20:25,959 uh, the output of 540 00:20:25,960 --> 00:20:28,449 receive chain. We have birth, 541 00:20:28,450 --> 00:20:30,509 uh, this birth, we connect 542 00:20:30,510 --> 00:20:33,159 back to the transmitting, but we've 543 00:20:33,160 --> 00:20:36,459 added some non, uh, 544 00:20:36,460 --> 00:20:38,709 delay of some known 545 00:20:38,710 --> 00:20:40,659 number of frames. 546 00:20:40,660 --> 00:20:42,969 And then we transmit this signal 547 00:20:42,970 --> 00:20:45,699 at some frequency close to the 548 00:20:45,700 --> 00:20:47,559 received signal frequency. 549 00:20:47,560 --> 00:20:49,659 We then record both 550 00:20:49,660 --> 00:20:51,879 signals the received signal, 551 00:20:51,880 --> 00:20:54,429 which contains both signals to analyze, 552 00:20:54,430 --> 00:20:56,799 uh, to analyze the received 553 00:20:56,800 --> 00:20:59,229 and the right signal, 554 00:20:59,230 --> 00:21:01,359 remove, uh, no 555 00:21:01,360 --> 00:21:03,609 number of frames and the 556 00:21:03,610 --> 00:21:05,809 delay from the delayed signal and 557 00:21:05,810 --> 00:21:08,109 what is left is, uh, the, 558 00:21:08,110 --> 00:21:10,299 uh, unknown but 559 00:21:10,300 --> 00:21:12,579 constant delay between the, 560 00:21:12,580 --> 00:21:14,889 uh, the both 561 00:21:14,890 --> 00:21:17,559 signals the receiver then transmitted 562 00:21:17,560 --> 00:21:19,149 by, uh, by us. 563 00:21:19,150 --> 00:21:21,459 And this we can measure 564 00:21:21,460 --> 00:21:23,549 with the use of cross-correlation, 565 00:21:24,580 --> 00:21:27,159 uh, it's just, uh, 566 00:21:27,160 --> 00:21:29,559 yeah, uh, you can measure 567 00:21:29,560 --> 00:21:31,569 it through issues of cross correlation, 568 00:21:31,570 --> 00:21:34,119 which will give us the shift from the, 569 00:21:34,120 --> 00:21:35,439 uh, zero 570 00:21:36,490 --> 00:21:39,579 and this uh, this shift, 571 00:21:39,580 --> 00:21:41,649 this shift of the peak of the correlation 572 00:21:41,650 --> 00:21:44,379 from the zero position is actually 573 00:21:44,380 --> 00:21:46,420 our, uh, delay 574 00:21:47,470 --> 00:21:49,649 that we have to put into, 575 00:21:49,650 --> 00:21:52,029 uh, take into account, uh, 576 00:21:52,030 --> 00:21:54,099 in producing the transmitter tax. 577 00:21:56,010 --> 00:21:58,899 So then we had to verify 578 00:21:58,900 --> 00:22:01,409 and transmit the signal amplitude 579 00:22:01,410 --> 00:22:04,649 and the, uh, normally 580 00:22:04,650 --> 00:22:06,779 programs like all small bits or 581 00:22:06,780 --> 00:22:09,089 small to really excite 582 00:22:09,090 --> 00:22:11,339 the transmitting constant stream 583 00:22:11,340 --> 00:22:12,269 of samples. 584 00:22:12,270 --> 00:22:14,639 But the four mobile stations, 585 00:22:14,640 --> 00:22:16,799 it will be kind of lame to 586 00:22:16,800 --> 00:22:19,079 do that because we have to transmit 587 00:22:19,080 --> 00:22:21,389 the constant, uh, stream 588 00:22:21,390 --> 00:22:23,639 of samples when and mobile station 589 00:22:23,640 --> 00:22:25,799 has to transmit something on 590 00:22:25,800 --> 00:22:26,939 the from time to time. 591 00:22:28,490 --> 00:22:30,749 Uh, so uh, we actually 592 00:22:30,750 --> 00:22:32,819 used the usurps burst interface 593 00:22:32,820 --> 00:22:34,919 to transmit the burst for each, 594 00:22:34,920 --> 00:22:37,199 uh, for each GSM berth. 595 00:22:37,200 --> 00:22:39,569 And it's because many advantages 596 00:22:39,570 --> 00:22:42,239 like you transmit one minute 597 00:22:42,240 --> 00:22:44,409 and it's easier to re 598 00:22:44,410 --> 00:22:46,949 synchronize the, uh, the transmission. 599 00:22:46,950 --> 00:22:49,559 You can solve the transmission problems. 600 00:22:49,560 --> 00:22:51,959 But there are some drawbacks, and 601 00:22:51,960 --> 00:22:54,419 here is the how it signal amplitude 602 00:22:54,420 --> 00:22:56,669 should look like for the GSM. 603 00:22:56,670 --> 00:22:58,979 There are some, uh, 604 00:22:58,980 --> 00:23:01,349 guard periods when the signal amplitude 605 00:23:01,350 --> 00:23:03,569 goes down, but then 606 00:23:03,570 --> 00:23:06,269 it's kind of, uh, constant. 607 00:23:06,270 --> 00:23:07,859 But this is what we got. 608 00:23:07,860 --> 00:23:09,059 Where the hell? 609 00:23:09,060 --> 00:23:11,369 Three hundred microseconds of our 610 00:23:11,370 --> 00:23:13,020 best, we're gonna. 611 00:23:14,760 --> 00:23:16,889 So after some looking 612 00:23:16,890 --> 00:23:18,959 for the answer, it appeared that 613 00:23:18,960 --> 00:23:20,649 this problem appears on the on the US 614 00:23:20,650 --> 00:23:22,889 surface with 210, and 615 00:23:22,890 --> 00:23:24,239 it can be admitted into 616 00:23:25,530 --> 00:23:28,049 this that it only 617 00:23:28,050 --> 00:23:29,909 it appears only when we are transmitting 618 00:23:29,910 --> 00:23:32,069 and receiving on the same side of 619 00:23:32,070 --> 00:23:33,869 the device. 620 00:23:33,870 --> 00:23:35,969 Uh. And it also 621 00:23:35,970 --> 00:23:38,009 appears only when there is no connection 622 00:23:38,010 --> 00:23:40,229 between active pen 623 00:23:40,230 --> 00:23:42,479 of the transmit part and the signal 624 00:23:42,480 --> 00:23:43,379 grant. 625 00:23:43,380 --> 00:23:45,869 So we fully avoid 626 00:23:45,870 --> 00:23:48,809 this. We can have much better, 627 00:23:48,810 --> 00:23:51,029 uh, much better signal 628 00:23:51,030 --> 00:23:52,030 amplitude. But then 629 00:23:53,130 --> 00:23:55,379 what is the thing in front of my 630 00:23:55,380 --> 00:23:56,459 birth? 631 00:23:56,460 --> 00:23:58,649 So what is this? 632 00:23:58,650 --> 00:24:00,779 After some looking, it appears that this 633 00:24:00,780 --> 00:24:02,909 is the end of the previous birth. 634 00:24:02,910 --> 00:24:05,459 Uh, that appears at the beginning of the, 635 00:24:05,460 --> 00:24:07,559 uh, next birth, and 636 00:24:07,560 --> 00:24:09,659 it is probably the result of growth 637 00:24:09,660 --> 00:24:11,919 delays of the piece. 638 00:24:11,920 --> 00:24:14,069 Uh, FPGA 639 00:24:14,070 --> 00:24:15,479 processing chain. 640 00:24:15,480 --> 00:24:17,579 And uh, yeah, and it 641 00:24:17,580 --> 00:24:19,649 can be avoided by just having zero 642 00:24:19,650 --> 00:24:21,869 said then. So if I to know at 643 00:24:21,870 --> 00:24:24,169 the beginning I would just do that. 644 00:24:24,170 --> 00:24:26,819 It's not lost some time on this 645 00:24:26,820 --> 00:24:29,009 and in the end to what had to be done 646 00:24:29,010 --> 00:24:31,349 was, uh, uh, verifying 647 00:24:31,350 --> 00:24:33,359 transmit the signal spectrum with 648 00:24:33,360 --> 00:24:34,979 Spectrum Analyzer. 649 00:24:34,980 --> 00:24:37,489 And uh, when you are connecting 650 00:24:37,490 --> 00:24:39,809 the antenna to the of the device, 651 00:24:39,810 --> 00:24:42,119 you should, uh, take into 652 00:24:42,120 --> 00:24:44,249 account always the fact 653 00:24:44,250 --> 00:24:46,409 that it might, uh, not produce 654 00:24:46,410 --> 00:24:47,759 the ideal signal. 655 00:24:47,760 --> 00:24:49,949 And for example, here for SRP 656 00:24:49,950 --> 00:24:52,169 210, its 657 00:24:52,170 --> 00:24:55,139 there is, uh, signal relief 658 00:24:55,140 --> 00:24:57,389 amplitude of minus 13 659 00:24:57,390 --> 00:24:59,489 DBS from from the 660 00:24:59,490 --> 00:25:02,249 main signal on the third, uh, 661 00:25:02,250 --> 00:25:04,889 harmonic. So you should always 662 00:25:04,890 --> 00:25:07,199 put, uh, on our troposphere 663 00:25:07,200 --> 00:25:09,299 instead, especially in case you are 664 00:25:09,300 --> 00:25:10,919 using wideband antenna. 665 00:25:10,920 --> 00:25:12,989 So after applying the filter, you 666 00:25:12,990 --> 00:25:14,769 get something like this. 667 00:25:14,770 --> 00:25:17,099 So at this moment, my part 668 00:25:17,100 --> 00:25:19,889 was, uh, uh, was working, 669 00:25:19,890 --> 00:25:22,019 I think. But uh, to, 670 00:25:22,020 --> 00:25:24,179 uh, to check that we we have to wait 671 00:25:24,180 --> 00:25:26,459 for the demo done 672 00:25:26,460 --> 00:25:28,049 by Vadim. 673 00:25:28,050 --> 00:25:29,069 Yeah, thank you. 674 00:25:29,070 --> 00:25:31,289 So when we finished more or less work 675 00:25:31,290 --> 00:25:33,089 and implementation of that transceiver, 676 00:25:33,090 --> 00:25:35,369 we get something like that. 677 00:25:35,370 --> 00:25:37,469 So finally, we can now communicate 678 00:25:37,470 --> 00:25:39,809 with software defined radio through the 679 00:25:39,810 --> 00:25:42,659 application called dual gsm tier. 680 00:25:42,660 --> 00:25:44,819 So we can not only communicate 681 00:25:44,820 --> 00:25:46,949 with our open source stick 682 00:25:46,950 --> 00:25:48,959 represented by source materials and also 683 00:25:48,960 --> 00:25:50,609 bits, but also these different base 684 00:25:50,610 --> 00:25:52,049 stations. 685 00:25:52,050 --> 00:25:54,509 So, yeah, let's try to show some demo, 686 00:25:54,510 --> 00:25:56,879 but we have some limited 687 00:25:56,880 --> 00:25:59,249 time and 688 00:25:59,250 --> 00:26:00,420 I need to put this here. 689 00:26:05,690 --> 00:26:06,690 Yeah. 690 00:26:10,820 --> 00:26:12,889 So first thing we need to run 691 00:26:12,890 --> 00:26:14,960 is actually our transfer. 692 00:26:18,410 --> 00:26:20,540 Yeah, it will start 693 00:26:21,680 --> 00:26:23,239 and then we need to run our theater 694 00:26:23,240 --> 00:26:25,249 school, which actually acts like a bridge 695 00:26:25,250 --> 00:26:27,589 between a transparent or smoking 696 00:26:27,590 --> 00:26:28,590 B applications. 697 00:26:29,810 --> 00:26:31,939 And finally, we need to run some 698 00:26:31,940 --> 00:26:33,409 assessment on baby application, for 699 00:26:33,410 --> 00:26:35,729 example, mobile application. 700 00:26:35,730 --> 00:26:36,730 Yeah. 701 00:26:38,000 --> 00:26:39,859 And what's happening now that it's 702 00:26:39,860 --> 00:26:42,019 started to just synchronize 703 00:26:42,020 --> 00:26:44,269 to his base station of these now 704 00:26:44,270 --> 00:26:45,919 these local network? 705 00:26:45,920 --> 00:26:47,989 And now we can try to register 706 00:26:47,990 --> 00:26:49,970 here, for example. 707 00:26:53,610 --> 00:26:54,610 Yeah. 708 00:26:56,630 --> 00:26:58,009 This is classical things 709 00:26:59,180 --> 00:27:01,309 we need to put our beautiful SIM card, 710 00:27:01,310 --> 00:27:03,409 because at the moment we don't have any 711 00:27:03,410 --> 00:27:05,869 direct SIM card interface, 712 00:27:05,870 --> 00:27:06,870 so 713 00:27:08,850 --> 00:27:09,850 let's try 714 00:27:11,060 --> 00:27:12,109 and what's happening now. 715 00:27:12,110 --> 00:27:14,359 We just perform 716 00:27:14,360 --> 00:27:16,939 on location of data request in 717 00:27:16,940 --> 00:27:18,049 GSM network. 718 00:27:20,720 --> 00:27:21,720 And let's see. 719 00:27:25,230 --> 00:27:27,180 Yes, and we just got 720 00:27:28,490 --> 00:27:30,869 just registered on that network, and 721 00:27:30,870 --> 00:27:32,849 what we can do here is to perform some 722 00:27:32,850 --> 00:27:34,949 basic operations like we can request for 723 00:27:34,950 --> 00:27:36,269 our number. 724 00:27:36,270 --> 00:27:37,169 It was. 725 00:27:37,170 --> 00:27:38,249 It's simple. 726 00:27:42,360 --> 00:27:43,360 So, yes. 727 00:27:46,660 --> 00:27:49,359 The implementation is not so stable, 728 00:27:49,360 --> 00:27:52,119 so feel free to contribute 729 00:27:52,120 --> 00:27:54,309 our project, and to us this is 730 00:27:54,310 --> 00:27:56,379 our are extension so we can 731 00:27:56,380 --> 00:27:59,409 try to send a mixed message to ourself. 732 00:27:59,410 --> 00:28:02,109 It should be like 733 00:28:02,110 --> 00:28:04,359 we should receive it back for. 734 00:28:08,180 --> 00:28:09,320 For example, this way. 735 00:28:10,490 --> 00:28:12,020 So, yeah, we got a channel. 736 00:28:15,830 --> 00:28:16,830 Then. 737 00:28:17,490 --> 00:28:18,490 Oops! 738 00:28:18,810 --> 00:28:19,979 Let's try one more time. 739 00:28:30,420 --> 00:28:31,679 OK. Yeah. 740 00:28:31,680 --> 00:28:32,820 And they go to the back. 741 00:28:41,770 --> 00:28:44,139 Thank you. And finally, let's try to call 742 00:28:44,140 --> 00:28:46,299 somewhere because we have some basic 743 00:28:46,300 --> 00:28:48,009 sound integration. 744 00:28:48,010 --> 00:28:49,780 And I hope it shouldn't. 745 00:28:52,690 --> 00:28:54,789 Yes. Let's write this to 746 00:28:54,790 --> 00:28:55,749 call some testing. 747 00:28:55,750 --> 00:28:56,890 No, actually. 748 00:29:14,210 --> 00:29:15,210 Yeah, 749 00:29:16,730 --> 00:29:17,730 finally. 750 00:29:19,370 --> 00:29:21,439 So we need to 751 00:29:21,440 --> 00:29:23,300 switch back to our presentation. 752 00:29:24,370 --> 00:29:25,989 And yes, 753 00:29:27,670 --> 00:29:30,099 the current project status 754 00:29:30,100 --> 00:29:32,199 is here, and it's not so 755 00:29:32,200 --> 00:29:34,569 perfect as I would like to see. 756 00:29:34,570 --> 00:29:36,759 So what we what have 757 00:29:36,760 --> 00:29:38,919 we achieved is to know we 758 00:29:38,920 --> 00:29:41,059 have a full open source 759 00:29:41,060 --> 00:29:43,359 do a similar one implementation. 760 00:29:43,360 --> 00:29:45,699 And so you don't need to hunt for calypso 761 00:29:45,700 --> 00:29:47,469 phones anymore. You feel free to use 762 00:29:47,470 --> 00:29:49,449 software defined radio. 763 00:29:49,450 --> 00:29:51,879 You can use any frequency 764 00:29:51,880 --> 00:29:53,749 you want. For example, you can run your 765 00:29:53,750 --> 00:29:55,929 networking wife event and 766 00:29:55,930 --> 00:29:58,359 call in this network. 767 00:29:58,360 --> 00:30:00,429 We are close 768 00:30:00,430 --> 00:30:02,799 to the future Jupiter 769 00:30:02,800 --> 00:30:04,449 as implementation. 770 00:30:04,450 --> 00:30:07,269 And so, for example, we can do something 771 00:30:07,270 --> 00:30:09,339 like try to integrate non 772 00:30:09,340 --> 00:30:11,709 GSM Ojo codecs like Speakes or 773 00:30:11,710 --> 00:30:13,419 Corpus here. 774 00:30:13,420 --> 00:30:15,009 And of course, this is the wind of change 775 00:30:15,010 --> 00:30:16,329 for a on Bebe. 776 00:30:16,330 --> 00:30:18,549 This is in use for the hardware 777 00:30:18,550 --> 00:30:21,099 platform for the project. 778 00:30:21,100 --> 00:30:23,799 So, yeah, thanks for your attention and 779 00:30:23,800 --> 00:30:25,119 feel free to ask your questions. 780 00:30:36,250 --> 00:30:37,719 So thank you very much. 781 00:30:37,720 --> 00:30:39,819 Vadim, and the other unfortunately, 782 00:30:39,820 --> 00:30:41,739 we're out of time, so we don't have time 783 00:30:41,740 --> 00:30:43,029 to do a Q&A. 784 00:30:43,030 --> 00:30:44,919 Hopefully we can stick around and people 785 00:30:44,920 --> 00:30:46,539 can maybe approach you if they have any 786 00:30:46,540 --> 00:30:47,979 questions. 787 00:30:47,980 --> 00:30:49,299 So again, a big round of applause, too, 788 00:30:49,300 --> 00:30:50,529 but the on field of a great topic. 789 00:30:50,530 --> 00:30:51,530 Thank you very much. 790 00:31:15,140 --> 00:31:16,140 The.