1
00:00:00,390 --> 00:00:08,670
In this lesson, we are going to introduce what is QCT protocol and why we need it.

2
00:00:09,810 --> 00:00:15,870
I'm here to protocol stands for message queen telemetry transport.

3
00:00:16,680 --> 00:00:24,480
Now it's a lightweight messaging protocol for small sensors and mobile devices optimized for high latency

4
00:00:24,990 --> 00:00:30,150
or unreliable networks, enabling a smarter projects and devices.

5
00:00:31,510 --> 00:00:34,510
And nudity is a simple messaging protocol.

6
00:00:35,320 --> 00:00:39,040
It's designed for constrained devices with low bandwidth.

7
00:00:39,460 --> 00:00:43,270
So it's the perfect solution for Internet of Things applications.

8
00:00:43,840 --> 00:00:50,710
And security allows you to send commands to control outputs, read and publish data from sensor loads

9
00:00:50,710 --> 00:00:51,610
and much more.

10
00:00:52,330 --> 00:00:57,670
Therefore, it makes it really easy to establish a communication between multiple devices.

11
00:00:58,420 --> 00:01:04,570
If you like home automation and you want to build a complete home automation system, you can easily

12
00:01:04,570 --> 00:01:06,460
do that using security.

13
00:01:07,270 --> 00:01:07,750
Now.

14
00:01:08,990 --> 00:01:14,210
In order to use NQT, you need to know that man commands.

15
00:01:16,280 --> 00:01:21,040
And these are publish messages, topics and brokers.

16
00:01:22,010 --> 00:01:26,360
Now let's start with the main concept of publish.

17
00:01:27,650 --> 00:01:34,970
The first concept is to publish and subscribe system and publish unsubscribe system advice can publish

18
00:01:34,970 --> 00:01:36,270
our message on our topic.

19
00:01:36,710 --> 00:01:44,030
Or it can be subscribed to a particular topic to receive messages so it can send a team to Charleston

20
00:01:44,030 --> 00:01:46,900
sort of value to a specific topic online.

21
00:01:48,110 --> 00:01:54,080
While the messages, which is a second concept, all of the information that you want to exchange between

22
00:01:54,080 --> 00:01:57,650
your devices, whether it's a command or debt.

23
00:01:58,970 --> 00:02:04,160
The third concept here is that topics it's another important concept.

24
00:02:05,270 --> 00:02:11,960
Topics are the way you register interest for incoming messages or how you specify where you want to

25
00:02:11,960 --> 00:02:12,950
publish that message.

26
00:02:13,460 --> 00:02:17,600
Topics are presented with strings separated by a forward slash.

27
00:02:18,290 --> 00:02:27,260
Each forward slash indicates atomic level, and you can easily take this as an example, if we added.

28
00:02:29,250 --> 00:02:30,030
I'll see you.

29
00:02:31,570 --> 00:02:38,860
And a forward slash, it means that we have this topic, if we add ESB after, that means that you are

30
00:02:38,910 --> 00:02:41,410
specifying another topic inside this one.

31
00:02:41,420 --> 00:02:46,700
So this is the main topic and this is the sub one, and we can't keep going like that.

32
00:02:47,680 --> 00:02:51,400
Now the Foxconn concept here is the broadcast.

33
00:02:52,600 --> 00:02:54,670
You also need to be aware of that.

34
00:02:55,300 --> 00:03:01,990
The broker is primarily responsible for receiving all messages, filtering their messages, decide who

35
00:03:01,990 --> 00:03:07,030
is interested in them and then publishing the message to all subscribed clients.

36
00:03:07,630 --> 00:03:15,140
So it's a very important concept when it comes to multi level and multi devices systems, but mainly

37
00:03:15,190 --> 00:03:16,450
we will use the publish.

38
00:03:18,120 --> 00:03:26,640
Concept, and we will publish data to that NQT online servers from the ISP, Bolt and ISP will receive

39
00:03:26,640 --> 00:03:28,410
the data from our Arduino board.

40
00:03:29,250 --> 00:03:29,730
That's it.

41
00:03:29,760 --> 00:03:30,930
This is the main concept.

42
00:03:31,080 --> 00:03:32,110
This is what is.

43
00:03:32,130 --> 00:03:34,680
I'm Kutty why it's important to use it.

44
00:03:34,710 --> 00:03:38,310
You can replace it with any other API like Google Firebase.

45
00:03:40,470 --> 00:03:47,010
Any other API can work, but you need some coding experience to adjust the code.

46
00:03:47,340 --> 00:03:48,150
Thanks for watching this.

47
00:03:48,150 --> 00:03:48,470
That's all.

48
00:03:48,570 --> 00:03:50,940
This is us far from educational engineering team.
