WEBVTT - This file was automatically generated by VIMEO

0
00:00:10.300 --> 00:00:13.400
Hello everyone. Welcome to the section number eight where we're

1
00:00:13.400 --> 00:00:16.700
 going to talk about the cope, which is also another application layer

2
00:00:16.700 --> 00:00:19.200
 communication protocol same like mqtt.

3
00:00:21.300 --> 00:00:24.300
So this is video number 8.1 and we're going to talk about what

4
00:00:24.300 --> 00:00:27.300
 is scope and how it works. It's architecture and

5
00:00:27.300 --> 00:00:29.800
 it's feature. So guys, let's get started with that.

6
00:00:32.200 --> 00:00:36.200
So firstly we will know its abbreviation which is constrained application

7
00:00:35.200 --> 00:00:38.500
 protocol and it's a lightweight

8
00:00:38.500 --> 00:00:41.800
 application protocol just like mqtt but it

9
00:00:41.800 --> 00:00:44.600
 works in a different mod like request and

10
00:00:44.600 --> 00:00:47.100
 response communication protocol which is based on

11
00:00:47.100 --> 00:00:50.300
 the HTTP. It is used for

12
00:00:50.300 --> 00:00:53.900
 MTM communication runs over udp/ip stack

13
00:00:53.900 --> 00:00:57.200
 instead of tcp/ip Stack design for

14
00:00:56.200 --> 00:01:00.100
 interpretability with the web mqtt

15
00:00:59.100 --> 00:01:03.200
 doesn't interoperability works

16
00:01:02.200 --> 00:01:05.300
 with the existing web Technologies. So

17
00:01:05.300 --> 00:01:08.100
 copious designed to give a better

18
00:01:08.100 --> 00:01:11.500
 user experience with the existing web Technologies designed for

19
00:01:11.500 --> 00:01:14.900
 remote connections where they have a limited bandwidth

20
00:01:14.900 --> 00:01:16.800
 same like mqtt.

21
00:01:18.600 --> 00:01:21.400
And if we talk about the features then mqtt and

22
00:01:21.400 --> 00:01:24.200
 core feature resembles with each other just like lightweight and

23
00:01:24.200 --> 00:01:27.900
 efficient but one is a different as the asynchronous message

24
00:01:27.900 --> 00:01:30.500
 exchange nor the instant communication

25
00:01:30.500 --> 00:01:33.700
 because mqtt is an instant

26
00:01:33.700 --> 00:01:36.500
 and same like mqtt it scales

27
00:01:36.500 --> 00:01:37.700
 up to the million of devices.

28
00:01:38.600 --> 00:01:42.000
And the major difference is mqtt used

29
00:01:41.200 --> 00:01:44.600
 topic based but Cove uses URI and

30
00:01:44.600 --> 00:01:47.400
 the content type sport which is not available

31
00:01:47.400 --> 00:01:50.900
 in mqtt. So both are different from that perspective.

32
00:01:50.900 --> 00:01:53.200
 And this is the main perspective which

33
00:01:53.200 --> 00:01:57.400
 makes them different from each other security enable

34
00:01:57.400 --> 00:02:00.600
 same like an mqtt but the web interoperability is

35
00:02:00.600 --> 00:02:04.100
 available in this program communication protocol and

36
00:02:03.100 --> 00:02:05.500
 not available in mqtt.

37
00:02:07.700 --> 00:02:10.000
So now it's time to talk about how it works.

38
00:02:12.100 --> 00:02:12.300
so

39
00:02:13.500 --> 00:02:15.400
here is our server for

40
00:02:16.500 --> 00:02:19.800
Server. Okay, and if we see that URL it's

41
00:02:19.800 --> 00:02:22.600
 same like HTTP, but here we're mentioning

42
00:02:22.600 --> 00:02:26.400
 the cop instead of HTTP. And the

43
00:02:25.400 --> 00:02:28.800
 rest of things are the same as we

44
00:02:28.800 --> 00:02:31.300
 have a HTTP request. So how it's working

45
00:02:31.300 --> 00:02:34.400
 is there are cope client like one and this is a Coke line

46
00:02:34.400 --> 00:02:37.400
 2 server is sending the get request

47
00:02:37.400 --> 00:02:38.100
 to the client.

48
00:02:39.800 --> 00:02:42.300
and then the client is sending back the

49
00:02:42.300 --> 00:02:43.400
 response in the

50
00:02:44.400 --> 00:02:48.300
Cove format and this is the second device service

51
00:02:47.300 --> 00:02:50.200
 sending get request

52
00:02:50.200 --> 00:02:54.000
 and the device is sending response to the server. So

53
00:02:53.100 --> 00:02:56.200
 in this way, the things are

54
00:02:56.200 --> 00:02:59.500
 work and that's why this is the asynchronous not a synchronous.

55
00:03:01.200 --> 00:03:04.700
So if we talk about the application same like mqtt, we

56
00:03:04.700 --> 00:03:07.700
 have a lot of applications where we

57
00:03:07.700 --> 00:03:10.500
 can use that and specifically if you want to

58
00:03:10.500 --> 00:03:13.700
 make your applications interoperative with

59
00:03:13.700 --> 00:03:17.000
 the web. Then the cope is a good choice and

60
00:03:16.700 --> 00:03:19.200
 it's performance is a little

61
00:03:19.200 --> 00:03:22.700
 bit higher due to asynchronous communication and

62
00:03:22.700 --> 00:03:25.700
 I also saves battery as compared to the mqtt.

63
00:03:25.700 --> 00:03:28.800
 So there are different scenarios like remote assist

64
00:03:28.800 --> 00:03:31.600
 tracking for example if you want to track

65
00:03:32.500 --> 00:03:35.400
The assets where you want to get the

66
00:03:35.400 --> 00:03:38.700
 location then go up is a good choice and smart

67
00:03:38.700 --> 00:03:41.300
 building small Healthcare smart Agriculture and

68
00:03:41.300 --> 00:03:44.400
 the industrial iot. So it's all

69
00:03:44.400 --> 00:03:48.300
 up to you that which communication protocol

70
00:03:47.300 --> 00:03:51.900
 either mqtt https HTTP

71
00:03:50.900 --> 00:03:53.700
 or Coke. I totally

72
00:03:53.700 --> 00:03:56.600
 depends on your scenarios what type of application protocol you

73
00:03:56.600 --> 00:03:59.700
 are using because it depends on your requirements and

74
00:03:59.700 --> 00:04:03.200
 your infrastructure your devices capabilities and

75
00:04:02.200 --> 00:04:05.400
 main thing is how you

76
00:04:05.400 --> 00:04:08.700
 want to fight the data from your devices. So guys

77
00:04:09.800 --> 00:04:13.600
do some research and share. Where is

78
00:04:13.600 --> 00:04:16.500
 mqtt better as computer cope. And where

79
00:04:16.500 --> 00:04:18.500
 is cope is better as compared to mktt.

80
00:04:20.400 --> 00:04:23.600
So guys see you in our next video. We are going to work on

81
00:04:23.600 --> 00:04:25.300
 the cope client and

82
00:04:26.300 --> 00:04:27.900
see you next video. Have a good day. Bye.
