WEBVTT 1 00:00.000 --> 00:05.240 As part of our wireless designs, we might find that an organization desires to 2 00:05.240 --> 00:12.760 see the deployment of real-time location services, which Cisco abbreviates as 3 00:12.760 --> 00:21.760 RTLS. Real-time location services are RTLS. This is the desire for us to track 4 00:21.760 --> 00:26.520 wireless devices and potentially keep a historical record over time as far as 5 00:26.520 --> 00:32.280 where they went. So we can start to look at things such as foot traffic. There WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 5 00:26.520 --> 00:32.280 where they went. So we can start to look at things such as foot traffic. There 6 00:32.280 --> 00:37.960 might be a retail store that wants to track, "Hey, where are users or customers 7 00:37.960 --> 00:38.160 at 8 00:38.160 --> 00:42.740 that point going?" So if they have a wireless device in their pocket and they 9 00:42.740 --> 00:42.800 're 10 00:42.800 --> 00:46.400 walking around, we can kind of track, "Hey, which of those aisles do they go 11 00:46.400 --> 00:46.560 down 12 00:46.560 --> 00:50.400 the most? Which do they go down the least?" and try to figure out maybe an 13 00:50.400 --> 00:50.960 optimal 14 00:50.960 --> 00:57.600 way of organizing their inventory. We can also track missing devices. This is 15 00:57.600 --> 01:01.720 something that has made its way into the residential world. A lot of our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 15 00:57.600 --> 01:01.720 something that has made its way into the residential world. A lot of our 16 01:01.720 --> 01:07.360 mobile devices have kind of that "find my phone" feature and we'll hopefully 17 01:07.360 --> 01:11.960 track it down potentially using the cellular network, but some devices will 18 01:11.960 --> 01:16.280 use Bluetooth or Wi-Fi as well to help us locate them. We can also use the 19 01:16.280 --> 01:22.330 concept of geo-fencing, sort of creating a virtual fence for devices that they 20 01:22.330 --> 01:22.440 're 21 01:22.440 --> 01:27.400 not allowed to cross. So for example, we might have a hospital and they've got 22 01:27.400 --> 01:33.960 this hospital premise and then they've got the parking lot out here and they WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 01:27.400 --> 01:33.960 this hospital premise and then they've got the parking lot out here and they 23 01:33.960 --> 01:40.200 start to tag, add sensors to things like wheelchairs. So if a wheelchair goes 24 01:40.200 --> 01:45.640 out into the parking lot, well, it has crossed this virtual threshold that is 25 01:45.640 --> 01:45.880 built 26 01:45.880 --> 01:50.280 around the hospital and it will flag an admin to say that, "Hey, there's a 27 01:50.280 --> 01:50.760 wheelchair 28 01:50.760 --> 01:54.120 out here." Wheelchairs are not supposed to go out to the parking lot because 29 01:54.120 --> 01:54.400 they 30 01:54.400 --> 01:58.310 might get packed up into somebody's car and they take it home. Furthermore, 31 01:58.310 --> 01:58.400 there 32 01:58.400 --> 02:04.400 might be blood pumps that, you know, IVs, IV pumps, that we're trying to figure WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 01:58.400 --> 02:04.400 might be blood pumps that, you know, IVs, IV pumps, that we're trying to figure 33 02:04.400 --> 02:04.520 out 34 02:04.520 --> 02:07.920 where they are. We don't know where they are. Well, now an admin can pull up a 35 02:07.920 --> 02:11.820 map and very quickly find it. So that would maybe fall more under the missing 36 02:11.820 --> 02:16.640 devices, but hospitals take heavy advantage of real-time location services, at 37 02:16.640 --> 02:22.110 least in my experience. So how exactly does location work? I mean, can we just 38 02:22.110 --> 02:22.200 do 39 02:22.200 --> 02:26.840 it on any old wireless network? And as you might imagine, the answer is no. We 40 02:26.840 --> 02:27.080 do 41 02:27.080 --> 02:33.160 have to design the wireless network to support location services. Just like WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 02:27.080 --> 02:33.160 have to design the wireless network to support location services. Just like 42 02:33.160 --> 02:33.320 with 43 02:33.320 --> 02:38.680 real-time applications that we mentioned earlier, if I am deploying a data 44 02:38.680 --> 02:43.270 network, it's not necessarily going to support voice over IP. Same thing here. 45 02:43.270 --> 02:43.320 I 46 02:43.320 --> 02:47.720 might create a design and it doesn't actually support real-time location 47 02:47.720 --> 02:53.400 services. So to understand how our designs have to be adapted helps to 48 02:53.400 --> 02:53.800 understand 49 02:53.800 --> 02:59.680 how exactly location works. So at a high level, we want to talk about our 50 02:59.680 --> 03:07.800 location tracking methods. And there are a few to keep in mind. Now the first WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 50 02:59.680 --> 03:07.800 location tracking methods. And there are a few to keep in mind. Now the first 51 03:07.800 --> 03:12.560 one to talk about is triangulation. It's one that often gets cited. It's 52 03:12.560 --> 03:18.800 certainly the basis for basic location services, but at the same time it's not 53 03:18.800 --> 03:23.520 actually the best technique. But yeah, let's just start here. So the idea here 54 03:23.520 --> 03:29.280 is how can I track where device is? Well, if I have an access point here and I 55 03:29.280 --> 03:29.320 'll 56 03:29.320 --> 03:33.680 just star the access point. I've got a wireless station out here. I might see WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 03:29.320 --> 03:33.680 just star the access point. I've got a wireless station out here. I might see 57 03:33.680 --> 03:42.560 that this station has a signal strength of -75 dBm. So cool. I hear on my 58 03:42.560 --> 03:43.040 diagram 59 03:43.040 --> 03:49.360 I can see that it's right there relative to the access point. Except not really 60 03:49.360 --> 03:55.880 because if I think about that signal as being around the AP, it could have a 61 03:55.880 --> 04:00.940 -75 signal down here. It could have a -75 signal over here. It could be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 03:55.880 --> 04:00.940 -75 signal down here. It could have a -75 signal over here. It could be 62 04:00.940 --> 04:01.320 anywhere 63 04:01.320 --> 04:05.540 on that circle. And so that only tells me about where it is. I mean it's 64 04:05.540 --> 04:05.960 helpful to 65 04:05.960 --> 04:09.760 know that it's somewhere within the radius of this access point. This access 66 04:09.760 --> 04:13.400 point can see it. Maybe this access point over here can see it. That can be 67 04:13.400 --> 04:20.120 helpful, but it's not high accuracy location. And so from here what we'll say 68 04:20.120 --> 04:20.400 is 69 04:20.400 --> 04:26.840 let's compare it to another access point. So now this access point also sees 70 04:26.840 --> 04:27.440 this 71 04:27.440 --> 04:34.480 device and maybe it sees it at, you know, this is -75, but this access point WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 04:27.440 --> 04:34.480 device and maybe it sees it at, you know, this is -75, but this access point 72 04:34.480 --> 04:34.600 over 73 04:34.600 --> 04:40.120 here sees it at -78. So again we can kind of figure out that it's probably 74 04:40.120 --> 04:45.960 somewhere in this area. But again not highly accurate, not pinpointing where 75 04:45.960 --> 04:46.120 the 76 04:46.120 --> 04:52.640 device is. But now we add a third access point in here and I draw a circle 77 04:52.640 --> 04:52.920 around 78 04:52.920 --> 04:59.040 it because it sees it at -72. And now we're starting to get very highly 79 04:59.040 --> 04:59.640 accurate. 80 04:59.640 --> 05:04.040 I can say, okay, it's probably right in this area based on these three APs WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 80 04:59.640 --> 05:04.040 I can say, okay, it's probably right in this area based on these three APs 81 05:04.040 --> 05:04.680 seeing 82 05:04.680 --> 05:10.000 it at their specific signal strength levels. We call it triangulation because 83 05:10.000 --> 05:10.120 it 84 05:10.120 --> 05:15.440 forms this triangle. That was a really bad attempt at a triangle. And we as 85 05:15.440 --> 05:15.800 long as 86 05:15.800 --> 05:21.160 the device is somewhere inside of this triangle of access points in theory, we 87 05:21.160 --> 05:26.560 are able to figure out where exactly that AP is. Here's the problem with this 88 05:26.560 --> 05:35.920 technique. What if we have a very thick wall here? Well this access point might WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 88 05:26.560 --> 05:35.920 technique. What if we have a very thick wall here? Well this access point might 89 05:35.920 --> 05:41.920 say, okay, you're at -75, but the device is not this far away. It's actually 90 05:41.920 --> 05:42.120 right 91 05:42.120 --> 05:49.160 here against the wall. And as we add in more devices and or more obstacles to 92 05:49.160 --> 05:49.240 our 93 05:49.240 --> 05:54.160 wireless devices, it gets trickier and trickier to use this technique. Now in a 94 05:54.160 --> 05:57.720 lot of cases, we could say, well, let's add a fourth access point in the more 95 05:57.720 --> 05:58.160 APs 96 05:58.160 --> 06:03.000 that we have, the better off we are at comparing the different signals. But WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 96 05:58.160 --> 06:03.000 that we have, the better off we are at comparing the different signals. But 97 06:03.000 --> 06:03.280 this is 98 06:03.280 --> 06:09.160 not considered to be a high accuracy method because it relies entirely on 99 06:09.160 --> 06:15.280 signal strength. And signal strength is disrupted by obstacles. It depends on a 100 06:15.280 --> 06:20.560 lot of factors that can make it so it's not high accuracy. So what if we want 101 06:20.560 --> 06:26.000 better accuracy? What techniques do we use? Well there are several here. We're 102 06:26.000 --> 06:26.120 not 103 06:26.120 --> 06:30.120 going to go into the details of them, but let's understand sort of the concept WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 103 06:26.120 --> 06:30.120 going to go into the details of them, but let's understand sort of the concept 104 06:30.120 --> 06:38.320 behind them. So for example, we have the concept of time of arrival. And we 105 06:38.320 --> 06:38.560 also 106 06:38.560 --> 06:44.680 have a time of arrival that is a slight variation of this, which is the time 107 06:44.680 --> 06:54.960 difference of arrival. And lastly, we have angle of arrival. So these are 108 06:54.960 --> 07:05.240 typically abbreviated as T O A, T D O A and A O A. So we've got three different WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 108 06:54.960 --> 07:05.240 typically abbreviated as T O A, T D O A and A O A. So we've got three different 109 07:05.240 --> 07:09.600 techniques that we typically deploy to help us out with this. And essentially 110 07:09.600 --> 07:09.680 what 111 07:09.680 --> 07:14.660 we're trying to do is remove signal strength or that R SSI as we called it 112 07:14.660 --> 07:19.300 we're trying to remove signal strength from the equation. We don't want to rely 113 07:19.300 --> 07:19.320 on 114 07:19.320 --> 07:24.100 signal strength because it gets disrupted. What doesn't get disrupted is the 115 07:24.100 --> 07:24.340 speed 116 07:24.340 --> 07:30.230 of light as well as the trajectory in a lot of cases. And so what we can do is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 116 07:24.340 --> 07:30.230 of light as well as the trajectory in a lot of cases. And so what we can do is 117 07:30.230 --> 07:30.540 say 118 07:30.540 --> 07:36.660 okay, well I received this signal at a particular time and you received the 119 07:36.660 --> 07:43.300 signal at a particular time. And now we can compare those time and say well we 120 07:43.300 --> 07:47.380 know what the speed of light is. So we know about how far away it is from each 121 07:47.380 --> 07:51.830 access point. And so if we get that coming from a number of different access 122 07:51.830 --> 07:52.180 points, 123 07:52.180 --> 07:59.220 then we can figure out exactly where this device is. Now this relies on a very 124 07:59.220 --> 08:05.980 finely synced set of times on the access points. They have to know exactly what WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 124 07:59.220 --> 08:05.980 finely synced set of times on the access points. They have to know exactly what 125 08:05.980 --> 08:11.060 time it is. They have to be highly synchronized. So they can tell exactly when 126 08:11.060 --> 08:11.260 this 127 08:11.260 --> 08:16.620 signal arrived relative to when it was probably transmitted. And yeah, that is 128 08:16.620 --> 08:21.080 going to require us to be so highly synced that we're talking about microse 129 08:21.080 --> 08:21.540 conds 130 08:21.540 --> 08:25.500 at this point, which hey our network is capable of doing. We just have to make 131 08:25.500 --> 08:30.580 sure we have it. Angle of arrival is going to compare how the signal arrives on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 131 08:25.500 --> 08:30.580 sure we have it. Angle of arrival is going to compare how the signal arrives on 132 08:30.580 --> 08:36.700 one access point or one antenna compared to another antenna and try to say okay 133 08:36.700 --> 08:41.980 well based on this angle, it's probably this direction, which is another way 134 08:41.980 --> 08:42.220 that 135 08:42.220 --> 08:46.580 we can remove signal strength from the equation. So either way, these are our 136 08:46.580 --> 08:53.060 techniques and we aren't necessarily usually going to drill into the specifics 137 08:53.060 --> 08:53.140 of 138 08:53.140 --> 08:56.860 that within our designs and even our implementations, but it does help us to 139 08:56.860 --> 09:03.580 understand a little bit more of how we need to change our wireless designs when WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 139 08:56.860 --> 09:03.580 understand a little bit more of how we need to change our wireless designs when 140 09:03.580 --> 09:11.140 we have location as a requirement. So what are we going to do here? Well, again 141 09:11.140 --> 09:12.100 , we 142 09:12.100 --> 09:16.540 have some design changes that are going to be required. And here's the biggest 143 09:16.540 --> 09:24.540 one of them all. We need to deploy access points to the perimeter of a building 144 09:24.540 --> 09:24.540 . 145 09:24.540 --> 09:29.140 What do we mean by this? Well, typically a wireless design that's a little bit 146 09:29.140 --> 09:33.820 more focused on again coverage and it could even be capacity and coverage. But WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 146 09:29.140 --> 09:33.820 more focused on again coverage and it could even be capacity and coverage. But 147 09:33.820 --> 09:38.090 what do we do? We deploy the access points throughout the space like this and 148 09:38.090 --> 09:38.940 we 149 09:38.940 --> 09:43.980 find that hey this is great. We can cover the entire space. We can have good 150 09:43.980 --> 09:50.820 overlap and we're able to cover everything that we need except there's a 151 09:50.820 --> 09:55.300 problem with this from a location perspective, which is what if the device is 152 09:55.300 --> 10:01.420 here on the wall? What do we say about triangulation and just in general all of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 152 09:55.300 --> 10:01.420 here on the wall? What do we say about triangulation and just in general all of 153 10:01.420 --> 10:05.580 these other techniques? We need multiple access points to be involved with 154 10:05.580 --> 10:09.820 tracking down where it is. Now I do have two access points here that can 155 10:09.820 --> 10:10.260 probably 156 10:10.260 --> 10:15.500 see the device, but what we really need is for this to be in the middle of the 157 10:15.500 --> 10:20.050 access points. You know, we can form a triangle over here for example and we 158 10:20.050 --> 10:20.140 can 159 10:20.140 --> 10:24.740 leverage the high accuracy techniques as best we can, but the further away a 160 10:24.740 --> 10:30.380 device is the less accurate it's going to be. So instead of deploying our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 160 10:24.740 --> 10:30.380 device is the less accurate it's going to be. So instead of deploying our 161 10:30.380 --> 10:34.860 wireless design like this, it is going to require a change where we place 162 10:34.860 --> 10:40.180 access points around the perimeter of the building. Something we've never had 163 10:40.180 --> 10:40.340 to 164 10:40.340 --> 10:48.740 do in the past because it's considered a waste. I mean my cell is going to look 165 10:48.740 --> 10:52.900 like this and look at all of the signal that's bleeding out into the parking 166 10:52.900 --> 10:53.060 lot. 167 10:53.060 --> 10:58.020 We would never want to do this if location isn't on the table because again it 168 10:58.020 --> 10:58.100 's 169 10:58.100 --> 11:03.580 sort of a waste of wireless signal. And yet with location this is going to be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 169 10:58.100 --> 11:03.580 sort of a waste of wireless signal. And yet with location this is going to be 170 11:03.580 --> 11:11.520 required because now when I have a wireless device that's over here, well at 171 11:11.520 --> 11:17.060 least we've got a lot better chance of seeing where that device is. If it's 172 11:17.060 --> 11:17.300 over 173 11:17.300 --> 11:22.580 here, for example, we've got a triangle that can see it and so you know maybe 174 11:22.580 --> 11:22.780 we 175 11:22.780 --> 11:26.210 want to put this in the corner a little bit more and get a triangle that way, 176 11:26.210 --> 11:26.260 but 177 11:26.260 --> 11:32.700 we start to see where our access points need to go relative to a design that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 177 11:26.260 --> 11:32.700 we start to see where our access points need to go relative to a design that 178 11:32.700 --> 11:38.580 doesn't include location services. Now when it comes to deploying location 179 11:38.580 --> 11:42.700 services within the Cisco space, we should be aware that we're going to need 180 11:42.700 --> 11:42.940 the 181 11:42.940 --> 11:47.740 proper solutions in place. Now fortunately all of Cisco's access points in 182 11:47.740 --> 11:53.420 wireless LAN controllers are equipped to give us location services from a 183 11:53.420 --> 11:56.940 high accuracy perspective. They're capable of deploying all of these different 184 11:56.940 --> 12:03.060 methods, but we will need some software to aggregate all of this information WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 184 11:56.940 --> 12:03.060 methods, but we will need some software to aggregate all of this information 185 12:03.060 --> 12:03.260 and 186 12:03.260 --> 12:08.220 this takes the form of Cisco software that today is known as Cisco Spaces. I 187 12:08.220 --> 12:14.500 say today because it used to be known as DNA spaces and so the name has changed 188 12:14.500 --> 12:18.740 and Cisco likes to rebrand things and so be aware of that. Now you might find 189 12:18.740 --> 12:18.900 some 190 12:18.900 --> 12:23.860 documentation that refers to Cisco's mobility services engine, their connected 191 12:23.860 --> 12:29.300 mobile experiences, prime infrastructure. A lot of these are more legacy 192 12:29.300 --> 12:29.740 products 193 12:29.740 --> 12:34.900 that used to be required for location services. These have been retired or WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 193 12:29.740 --> 12:34.900 that used to be required for location services. These have been retired or 194 12:34.900 --> 12:39.500 otherwise on their way out the door and so instead we're going to see that we 195 12:39.500 --> 12:43.380 need to connect into this software package called Cisco Spaces which gives us 196 12:43.380 --> 12:47.940 the floor plans which can show us where devices potentially give us some 197 12:47.940 --> 12:53.220 historical tracking and when we're building out our wireless designs we would 198 12:53.220 --> 12:58.230 want to make sure that we're asking the question about licensing costs, 199 12:58.230 --> 12:58.620 whatever 200 12:58.620 --> 13:04.900 it takes to deploy this particular software package to go with the design, the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 200 12:58.620 --> 13:04.900 it takes to deploy this particular software package to go with the design, the 201 13:04.900 --> 13:08.020 access point design that we're creating that places them around the perimeter.