{"id":38375,"date":"2019-10-31T22:23:21","date_gmt":"2019-10-31T19:23:21","guid":{"rendered":"https:\/\/prohoster.info\/blog\/iot-tuman-i-oblaka-pogovorim-pro-tehnologii\/"},"modified":"2019-10-31T22:23:21","modified_gmt":"2019-10-31T19:23:21","slug":"iot-tuman-i-oblaka-pogovorim-pro-tehnologii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/iot-tuman-i-oblaka-pogovorim-pro-tehnologii","title":{"rendered":"IoT, mjegull dhe reve: le t\u00eb flasim p\u00ebr teknologjit\u00eb?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"IoT, mjegull dhe reve: le t\u00eb flasim p\u00ebr teknologjit\u00eb?\" src=\"\/wp-content\/uploads\/2019\/09\/89eae3426589d2ed8041fd6dd26498cb.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i>Zhvillimi i teknologjive n\u00eb fush\u00ebn e softuer\u00ebve dhe harduer\u00ebve, shfaqja e protokolleve t\u00eb reja t\u00eb komunikimit ka \u00e7uar n\u00eb zgjerimin e internetit t\u00eb gj\u00ebrave (IoT). Numri i pajisjeve po rritet \u00e7do dit\u00eb, dhe ato gjenerojn\u00eb nj\u00eb volum t\u00eb madh t\u00eb dh\u00ebnash. Prandaj, ekziston nevoja p\u00ebr nj\u00eb arkitektur\u00eb t\u00eb p\u00ebrshtatshme t\u00eb sistemit, e cila \u00ebsht\u00eb n\u00eb gjendje t\u00eb p\u00ebrpunoj\u00eb, ruaj\u00eb dhe transmetoj\u00eb k\u00ebto t\u00eb dh\u00ebna.<\/p>\n<p>Aktualisht, p\u00ebr k\u00ebto q\u00ebllime p\u00ebrdoren sh\u00ebrbimet cloud. Megjithat\u00eb, paradigma gjithnj\u00eb e m\u00eb e njohur e llogaritjes n\u00eb re t\u00eb mjegull\u00ebs (Fog) \u00ebsht\u00eb n\u00eb gjendje t\u00eb plot\u00ebsoj\u00eb zgjidhjet cloud, duke zgjeruar dhe optimizuar infrastruktur\u00ebn e IoT. <\/i><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>\u00abRe\u00bb jan\u00eb n\u00eb gjendje t\u00eb mbulojn\u00eb shumic\u00ebn e k\u00ebrkesave t\u00eb IoT. P\u00ebr shembull, ato ofrojn\u00eb monitorimin e sh\u00ebrbimeve, p\u00ebrpunimin e shpejt\u00eb t\u00eb \u00e7do volumi t\u00eb dh\u00ebnash t\u00eb gjeneruara nga pajisjet, si dhe vizualizimin e tyre. Llogarit\u00eb e mjegull\u00ebs, nga ana tjet\u00ebr, jan\u00eb m\u00eb efikase n\u00eb zgjidhjen e detyrave n\u00eb koh\u00eb reale. Ato sigurojn\u00eb nj\u00eb p\u00ebrgjigje t\u00eb shpejt\u00eb ndaj k\u00ebrkesave dhe nj\u00eb vones\u00eb minimale gjat\u00eb p\u00ebrpunimit t\u00eb t\u00eb dh\u00ebnave. K\u00ebshtu, Fog plot\u00ebson \u00abre\u00bb duke zgjeruar mund\u00ebsit\u00eb e saj.<\/p>\n<p>Megjithat\u00eb, pyetja kryesore \u00ebsht\u00eb se si duhet t\u00eb nd\u00ebrveprojn\u00eb t\u00eb gjitha k\u00ebto n\u00eb kontekstin e IoT? Cil\u00ebt protokoll komunikimi do t\u00eb ishin m\u00eb t\u00eb efektsh\u00ebm p\u00ebr t\u00eb punuar n\u00eb nj\u00eb sistem t\u00eb integruar IoT-Fog-Cloud?<\/p>\n<p>Pavar\u00ebsisht dukshm\u00ebris\u00eb s\u00eb dominimit t\u00eb HTTP, n\u00eb sistemet IoT, Fog dhe Cloud p\u00ebrdoren shum\u00eb zgjidhje t\u00eb tjera. Kjo shpjegohet me faktin se IoT duhet t\u00eb kombinoj\u00eb funksionalitetin e sensor\u00ebve t\u00eb ndrysh\u00ebm t\u00eb pajisjeve me sigurin\u00eb, p\u00ebrputhshm\u00ebrin\u00eb dhe k\u00ebrkesa t\u00eb tjera q\u00eb p\u00ebrdoruesit kan\u00eb.<\/p>\n<p>Megjithat\u00eb, nuk ka nj\u00eb p\u00ebrkufizim t\u00eb vetme p\u00ebr nj\u00eb arkitektur\u00eb standarde dhe protokoll komunikimi. Prandaj, krijimi i nj\u00eb protokolli t\u00eb ri ose p\u00ebrmir\u00ebsimi i nj\u00eb ekzistenti p\u00ebr detyrat specifike t\u00eb IoT \u00ebsht\u00eb nj\u00eb nga sfidat m\u00eb t\u00eb r\u00ebnd\u00ebsishme q\u00eb p\u00ebrballet komuniteti IT.<\/p>\n<p>Cilat protokolle p\u00ebrdoren tani dhe \u00e7far\u00eb mund t\u00eb ofrojn\u00eb? Le t\u00eb shqyrtojm\u00eb. Por fillimisht, le t\u00eb diskutojm\u00eb parimet e ekosistemit, n\u00eb t\u00eb cilin nd\u00ebrveprojn\u00eb re, mjegulla dhe interneti i gj\u00ebrave.<\/p>\n<h3>Arkitektura IoT Fog-to-Cloud (F2C)<\/h3>\n<p>\nP\u00ebr sigur q\u00eb e keni v\u00ebn\u00eb re sa p\u00ebrpjekje t\u00eb m\u00ebdha b\u00ebhen p\u00ebr t\u00eb studiuar avantazhet dhe p\u00ebrfitimet q\u00eb lidhen me menaxhimin racional dhe t\u00eb koordinuar t\u00eb IoT, reve dhe mjegull\u00ebs. N\u00ebse jo, k\u00ebtu jan\u00eb tre nisma p\u00ebr standardizim: <noindex><a rel=\"nofollow\" href=\"https:\/\/www.openfogconsortium.org\/\">OpenFog Consortium<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"http:\/\/en.ecconsortium.org\/Uploads\/file\/20180328\/1522232376480704.pdf\">Edge Computing Consortium<\/a><\/noindex> dhe <noindex><a rel=\"nofollow\" href=\"http:\/\/www.mf2c-project.eu\/\">mF2C H2020 projekt n\u00eb BE<\/a><\/noindex>. <\/p>\n<p>N\u00ebse m\u00eb par\u00eb mirreshin parasysh vet\u00ebm 2 nivele, re dhe pajisjet fundore, arkitektura e propozuar sjell nj\u00eb nivel t\u00eb ri - llogarit\u00eb n\u00eb mjegull. Kjo \u00ebsht\u00eb n\u00eb gjendje t\u00eb ndahet n\u00eb disa n\u00ebnnivel, n\u00eb var\u00ebsi t\u00eb specifikave t\u00eb resurseve ose grupeve t\u00eb politikave q\u00eb p\u00ebrcaktojn\u00eb p\u00ebrdorimin e pajisjeve t\u00eb ndryshme n\u00eb k\u00ebto n\u00ebnnivela.<\/p>\n<p>Si mund t\u00eb duket kjo abstraksion? K\u00ebtu \u00ebsht\u00eb nj\u00eb ekosistem tipik IoT-Fog-Cloud. Pajisjet IoT d\u00ebrgojn\u00eb t\u00eb dh\u00ebnat n\u00eb servera dhe pajisje llogarit\u00ebse m\u00eb t\u00eb fuqishme, p\u00ebr t\u00eb zgjidhur probleme q\u00eb k\u00ebrkojn\u00eb nj\u00eb nivel t\u00eb ul\u00ebt vonese. N\u00eb k\u00ebt\u00eb sistem, re jan\u00eb p\u00ebrgjegj\u00ebse p\u00ebr zgjidhjen e problemeve q\u00eb k\u00ebrkojn\u00eb nj\u00eb volum t\u00eb madh burimesh llogaritet apo hap\u00ebsire p\u00ebr ruajtjen e t\u00eb dh\u00ebnave.<\/p>\n<p><img decoding=\"async\" alt=\"IoT, mjegull dhe reve: le t\u00eb flasim p\u00ebr teknologjit\u00eb?\" src=\"\/wp-content\/uploads\/2019\/09\/c78ea915ac4743a3def5651778e77873.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSmartfon\u00ebt, or\u00ebt inteligjente dhe pajisje t\u00eb tjera gjithashtu mund t\u00eb jen\u00eb pjes\u00eb e IoT. Por k\u00ebto pajisje, zakonisht, p\u00ebrdorin protokolle komunikimi private nga zhvillues t\u00eb m\u00ebdhenj. T\u00eb dh\u00ebnat e gjeneruara nga interneti i gj\u00ebrave d\u00ebrgohen n\u00eb nivelin e mjegull\u00ebs p\u00ebrmes protokollit REST HTTP, i cili siguron fleksibilitet dhe p\u00ebrputhshm\u00ebri funksionale gjat\u00eb krijimit t\u00eb sh\u00ebrbimeve RESTful. Kjo \u00ebsht\u00eb e r\u00ebnd\u00ebsishme n\u00eb drit\u00ebn e nevoj\u00ebs p\u00ebr t\u00eb siguruar p\u00ebrputhshm\u00ebrin\u00eb me infrastruktur\u00ebn ekzistuese t\u00eb llogaritjes, e cila punon n\u00eb kompjuter\u00eb lokal\u00eb, server\u00eb ose klaster\u00eb server\u00ebsh. Burimet lokale, q\u00eb quhen \u00abn\u00eb mjegull\u00bb, filtrojn\u00eb t\u00eb dh\u00ebnat e marra dhe i p\u00ebrpunojn\u00eb ato lokal ose i d\u00ebrgojn\u00eb n\u00eb re p\u00ebr llogaritje t\u00eb m\u00ebtejshme.<\/p>\n<p>Re p\u00ebrkrahim protokolle t\u00eb ndryshme komunikimi, nd\u00ebrmjet t\u00eb cilave m\u00eb t\u00eb zakonshmet jan\u00eb AMQP dhe REST HTTP. Duke qen\u00eb se HTTP \u00ebsht\u00eb i njohur dhe i p\u00ebrshtatur p\u00ebr internetin, mund t\u00eb lind pyetja: \u00aba nuk duhet ta p\u00ebrdorim at\u00eb p\u00ebr t\u00eb punuar me IoT dhe mjegull\u00ebn?\u00bb. Megjithat\u00eb, ky protokoll ka probleme me performanc\u00ebn. K\u00ebt\u00eb do ta shqyrtojm\u00eb m\u00eb von\u00eb.<\/p>\n<p>N\u00eb p\u00ebrgjith\u00ebsi, ekzistojn\u00eb 2 modele protokollesh t\u00eb komunikimit, t\u00eb p\u00ebrshtatshme p\u00ebr sistemin ton\u00eb. K\u00ebto jan\u00eb modeli k\u00ebrkes\u00eb-p\u00ebrgjigje dhe modeli publikim-pajtim. Modeli i par\u00eb \u00ebsht\u00eb m\u00eb i njohur, ve\u00e7an\u00ebrisht n\u00eb arkitektur\u00ebn server-klient. Klienti k\u00ebrkon informacion nga serveri, i cili merr k\u00ebrkes\u00ebn, e p\u00ebrpunon dhe kthen nj\u00eb p\u00ebrgjigje. K\u00ebto modele funksionojn\u00eb me protokollet REST HTTP dhe CoAP.<\/p>\n<p>Modeli i dyt\u00eb ka lindur p\u00ebr t\u00eb siguruar nj\u00eb lidhje asimetrike, t\u00eb shp\u00ebrndar\u00eb, t\u00eb dob\u00ebsuar midis burimeve q\u00eb gjenerojn\u00eb t\u00eb dh\u00ebna dhe marr\u00ebsve t\u00eb k\u00ebtyre t\u00eb dh\u00ebnave.<\/p>\n<p><img decoding=\"async\" alt=\"IoT, mjegull dhe reve: le t\u00eb flasim p\u00ebr teknologjit\u00eb?\" src=\"\/wp-content\/uploads\/2019\/09\/acf3b411fb9a0b7a61cf0188e4c29292.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nModeli p\u00ebrfshin tre pjes\u00ebmarr\u00ebs: botuesi (burimi i t\u00eb dh\u00ebnave), brokeri (dispe\u00e7er) dhe abonenti (pranuesi). K\u00ebtu klienti, i cili vepron si abonent, nuk duhet t\u00eb k\u00ebrkoj\u00eb informacion nga serveri. N\u00eb vend q\u00eb t\u00eb d\u00ebrgoj\u00eb k\u00ebrkesa, ai abonohet p\u00ebr ngjarje t\u00eb caktuara n\u00eb sistem p\u00ebrmes brokerit, i cili \u00ebsht\u00eb p\u00ebrgjegj\u00ebs p\u00ebr filtrimin e t\u00eb gjitha mesazheve hyr\u00ebse dhe ritransmetimin e tyre mes botuesve dhe abonent\u00ebve. Kur ndodh nj\u00eb ngjarje q\u00eb lidhet me nj\u00eb tem\u00eb t\u00eb caktuar, botuesi e publik\u00e7on at\u00eb te brokeri, i cili d\u00ebrgon t\u00eb dh\u00ebnat te abonenti p\u00ebr tem\u00ebn e k\u00ebrkuar.<\/p>\n<p>N\u00eb thelb, kjo arkitektur\u00eb bazohet n\u00eb ngjarje. Dhe nj\u00eb model i till\u00eb nd\u00ebrveprimi \u00ebsht\u00eb interesant p\u00ebr aplikacionet n\u00eb IoT, n\u00eb cloud, dhe n\u00eb fog p\u00ebr shkak t\u00eb aft\u00ebsis\u00eb s\u00eb saj p\u00ebr t\u00eb siguruar shkall\u00ebzueshm\u00ebri dhe p\u00ebr t\u00eb thjeshtuar marr\u00ebdh\u00ebniet midis pajisjeve t\u00eb ndryshme, duke mb\u00ebshtetur komunikimin dinamik \"mij\u00ebra me mij\u00ebra\" dhe komunikimin asinkron. Disa nga protokollet m\u00eb t\u00eb njohura t\u00eb standardizuara p\u00ebr shk\u00ebmbimin e mesazheve q\u00eb p\u00ebrdorin modelin \"publikim-abonim\" jan\u00eb MQTT, AMQP dhe DDS.<\/p>\n<p>\u00cbsht\u00eb e qart\u00eb se modeli \"publikim-abonim\" ka shum\u00eb p\u00ebrfitime:<\/p>\n<ul>\n<li>Botuesit dhe abonent\u00ebt nuk kan\u00eb nevoj\u00eb t\u00eb din\u00eb p\u00ebr ekzistenc\u00ebn e nj\u00ebri-tjetrit;<\/li>\n<li>Nj\u00eb abonent mund t\u00eb marr\u00eb informacion nga shum\u00eb botues t\u00eb ndrysh\u00ebm, nd\u00ebrsa nj\u00eb botues mund t\u00eb d\u00ebrgoj\u00eb t\u00eb dh\u00ebna shum\u00eb abonent\u00ebve t\u00eb ndrysh\u00ebm (principi \"mij\u00ebra me mij\u00ebra\");<\/li>\n<li>Botuesi dhe abonenti nuk jan\u00eb t\u00eb detyruar t\u00eb jen\u00eb aktiv\u00eb nj\u00ebkoh\u00ebsisht p\u00ebr shk\u00ebmbejn\u00eb t\u00eb dh\u00ebna, sepse brokeri (q\u00eb funksionon si nj\u00eb sistem radh\u00eb) mund t\u00eb ruaj\u00eb mesazhet p\u00ebr klient\u00ebt q\u00eb n\u00eb at\u00eb moment nuk jan\u00eb t\u00eb lidhur.<\/li>\n<\/ul>\n<p>\nMegjithat\u00eb, modeli \"k\u00ebrkes\u00eb-p\u00ebrgjigje\" ka gjithashtu pikat e tij t\u00eb forta. N\u00eb rastet kur kapacitetet e an\u00ebs s\u00eb serverit p\u00ebr t\u00eb p\u00ebrpunuar k\u00ebrkesat e shum\u00eb klient\u00ebve nuk jan\u00eb nj\u00eb problem, ka kuptim t\u00eb p\u00ebrdoren zgjidhje t\u00eb besueshme q\u00eb jan\u00eb provuar paraprakisht.<\/p>\n<p>Ka gjithashtu protokolle q\u00eb mb\u00ebshtesin t\u00eb dy modelet. P\u00ebr shembull, XMPP dhe HTTP 2.0, t\u00eb cilat mb\u00ebshtesin opsionin \"server push\". IETF gjithashtu ka l\u00ebshuar CoAP. N\u00eb p\u00ebrpjekje p\u00ebr t\u00eb zgjidhur problemin e shk\u00ebmbimit t\u00eb mesazheve, jan\u00eb krijuar disa zgjidhje t\u00eb tjera, si protokolli WebSockets ose p\u00ebrdorimi i protokollit HTTP p\u00ebrmes QUIC (Quick UDP Internet Connections).<\/p>\n<p>N\u00eb rastin e WebSockets, megjith\u00ebse p\u00ebrdoret p\u00ebr t\u00eb transmetuar t\u00eb dh\u00ebna n\u00eb koh\u00eb reale nga serveri n\u00eb klientin web dhe siguron lidhje t\u00eb q\u00ebndrueshme me komunikim t\u00eb dyansh\u00ebm, nuk \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm p\u00ebr pajisjet me burime t\u00eb kufizuara kompjuterike. QUIC gjithashtu meriton v\u00ebmendje, pasi protokolli i ri t\u00ebrheq shum\u00eb mund\u00ebsi t\u00eb reja. Por pasi q\u00eb QUIC ende nuk \u00ebsht\u00eb standardizuar, \u00ebsht\u00eb her\u00ebt t\u00eb parashikojm\u00eb aplikimin dhe ndikimin e tij n\u00eb zgjidhjet n\u00eb fush\u00ebn e IoT. Prandaj, WebSockets dhe QUIC i mbajm\u00eb n\u00eb mendje p\u00ebr t\u00eb ardhmen, por nuk do t'i shqyrtojm\u00eb m\u00eb tej tani.<\/p>\n<h3>Kush \u00ebsht\u00eb m\u00eb i dashur n\u00eb bot\u00eb: krahasojm\u00eb protokollet<\/h3>\n<p>\nTani le t\u00eb flasim p\u00ebr pikat e forta dhe t\u00eb dob\u00ebta t\u00eb protokolleve. P\u00ebrpara se t\u00eb fillojm\u00eb, le t\u00eb theksojm\u00eb se nuk ka nj\u00eb lider t\u00eb evidentuar. \u00c7do protokoll ka disa avantazhe dhe disavantazhe.<\/p>\n<p><b>Koha e p\u00ebrgjigjes<\/b><\/p>\n<p>Nj\u00eb nga karakteristikat m\u00eb t\u00eb r\u00ebnd\u00ebsishme t\u00eb protokolleve t\u00eb komunikimit, ve\u00e7an\u00ebrisht n\u00eb kontekstin e internetit t\u00eb objekteve, \u00ebsht\u00eb koha e p\u00ebrgjigjes. Por mes protokolleve ekzistues, nuk ka nj\u00eb fitues absolut, q\u00eb tregon nivelin m\u00eb t\u00eb ul\u00ebt t\u00eb vones\u00ebs n\u00eb kushte t\u00eb ndryshme. Por ka shum\u00eb k\u00ebrkime dhe krahasime t\u00eb mund\u00ebsive t\u00eb protokolleve.<\/p>\n<p>P\u00ebr shembull, <noindex><a rel=\"nofollow\" href=\"https:\/\/www.researchgate.net\/publication\/323943358_Performance_Analysis_of_Internet_of_Things_Protocols_Based_FogCloud_over_High_Traffic\">rezultatet <\/a><\/noindex>Krahasimi i eficienc\u00ebs s\u00eb HTTP dhe MQTT n\u00eb pun\u00ebn me IoT ka treguar se koha e p\u00ebrgjigjes p\u00ebr k\u00ebrkesat n\u00eb MQTT \u00ebsht\u00eb m\u00eb e ul\u00ebt se n\u00eb HTTP. Nd\u00ebrsa, <noindex><a rel=\"nofollow\" href=\"https:\/\/www.researchgate.net\/publication\/303188719_Comparison_of_two_lightweight_protocols_for_smartphone-based_sensing\">n\u00eb studimin <\/a><\/noindex>e koh\u00ebs s\u00eb marrjes-dergimit (RTT) MQTT dhe CoAP rezultoi se mesatarja e RTT p\u00ebr CoAP \u00ebsht\u00eb 20% m\u00eb e ul\u00ebt se ajo p\u00ebr MQTT.<\/p>\n<p>E tjera <noindex><a rel=\"nofollow\" href=\"https:\/\/ieeexplore.ieee.org\/document\/7740559\">eksperiment <\/a><\/noindex>me RTT t\u00eb protokolleve MQTT dhe CoAP \u00ebsht\u00eb realizuar n\u00eb dy skenar\u00eb: n\u00eb nj\u00eb rrjet lokal dhe n\u00eb nj\u00eb rrjet IoT. T\u00eb dh\u00ebnat treguan se mesatarja e RTT n\u00eb rrjetin IoT ishte 2-3 her\u00eb m\u00eb e lart\u00eb. MQTT me QoS0 tregoi rezultate m\u00eb t\u00eb ul\u00ebta n\u00eb krahasim me CoAP, nd\u00ebrsa MQTT me QoS1 demonstroi RTT m\u00eb t\u00eb lart\u00eb p\u00ebr shkak t\u00eb ACK n\u00eb nivelin aplikativ dhe transportues. P\u00ebr nivelet e ndryshme QoS, vonesat n\u00eb rrjetin pa mbingarkes\u00eb p\u00ebr MQTT ishin disa milisekonda, nd\u00ebrsa p\u00ebr CoAP ishin qindra mikrosekonda. Megjithat\u00eb, duhet t\u00eb mbani mend se n\u00eb rrjete m\u00eb pak t\u00eb besueshme MQTT, q\u00eb funksionon mbi TCP, do t\u00eb tregoj\u00eb rezultate krejt\u00ebsisht ndryshe.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/www.diva-portal.org\/smash\/get\/diva2:1092136\/FULLTEXT01.pdf\">Krahasimi <\/a><\/noindex>sa i p\u00ebrket koh\u00ebs s\u00eb p\u00ebrgjigjes t\u00eb protokolleve AMQP dhe MQTT, duke rritur ngarkes\u00ebn e t\u00eb dh\u00ebnave tregoi se n\u00eb ngarkes\u00eb t\u00eb vog\u00ebl niveli i vones\u00ebs ishte pothuajse i nj\u00ebjt\u00eb. Por gjat\u00eb transmetimit t\u00eb sasis\u00eb s\u00eb madhe t\u00eb t\u00eb dh\u00ebnave, MQTT tregon nj\u00eb koh\u00eb p\u00ebrgjigjeje m\u00eb t\u00eb ul\u00ebt. Nj\u00eb tjet\u00ebr <noindex><a rel=\"nofollow\" href=\"http:\/\/www.tfzr.rs\/esociety\/issues\/eSocietyVol3No1.pdf#page=26\">studim <\/a><\/noindex>CoAP u krahasuar me HTTP n\u00eb skenarin e komunikimit nd\u00ebrmjet makinave me pajisje t\u00eb vendosura n\u00eb mjete dhe t\u00eb pajisura me Sensore gazi, Sensore moti, pozicion (GPS) dhe nd\u00ebrfaqe t\u00eb rrjetit celular (GPRS). Koha e nevojshme p\u00ebr t\u00eb d\u00ebrguar nj\u00eb mesazh CoAP n\u00ebp\u00ebrmjet rrjetit mobil ishte pothuajse tre her\u00eb m\u00eb e shkurt\u00ebr se koha e nevojshme p\u00ebr t\u00eb p\u00ebrdorur mesazhe HTTP.<\/p>\n<p>U kryen studime ku u krahasuan jo dy, por tre protokolle. P\u00ebr shembull, <noindex><a rel=\"nofollow\" href=\"https:\/\/ieeexplore.ieee.org\/document\/7496622\">krahasimi <\/a><\/noindex>performanc\u00ebn e protokolleve IoT MQTT, DDS dhe CoAP n\u00eb nj\u00eb skenar mjek\u00ebsor duke p\u00ebrdorur nj\u00eb emulator rrjeti. DDS tejkaloi MQTT n\u00eb aspektin e vones\u00ebs s\u00eb provuar t\u00eb telemetris\u00eb n\u00eb kushte t\u00eb ndryshme t\u00eb k\u00ebqija t\u00eb rrjetit. CoAP n\u00eb baz\u00eb t\u00eb UDP punoi mir\u00eb p\u00ebr aplikacione q\u00eb k\u00ebrkonin nj\u00eb p\u00ebrgjigje t\u00eb shpejt\u00eb, megjithat\u00eb, p\u00ebr shkak se bazohet n\u00eb UDP, ndodhi humbje e konsiderueshme e paparashikueshme t\u00eb paketave.<\/p>\n<p><b>Kapaciteti i Kalimit<\/b><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/www.researchgate.net\/publication\/267636202_Performance_evaluation_of_MQTT_and_CoAP_via_a_common_middleware\">Krahasimi <\/a><\/noindex>MQTT dhe CoAP n\u00eb aspektin e efikasitetit t\u00eb p\u00ebrdorimit t\u00eb band\u00ebs jan\u00eb b\u00ebr\u00eb duke num\u00ebruar sasin\u00eb totale t\u00eb t\u00eb dh\u00ebnave t\u00eb d\u00ebrguara p\u00ebr nj\u00eb mesazh. CoAP tregoi nj\u00eb kapacitet m\u00eb t\u00eb ul\u00ebt se MQTT gjat\u00eb d\u00ebrgimit t\u00eb mesazheve t\u00eb vogla. Por kur u krahasua efikasiteti i protokolleve n\u00eb aspektin e raportit t\u00eb sasis\u00eb s\u00eb bajt\u00ebve t\u00eb dobish\u00ebm ndaj sasis\u00eb totale t\u00eb bajt\u00ebve t\u00eb d\u00ebrguar, CoAP rezultoi m\u00eb efikas.<\/p>\n<p>N\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/ieeexplore.ieee.org\/document\/7496622\">analiz\u00ebs <\/a><\/noindex>p\u00ebrdorimit t\u00eb band\u00ebs nga MQTT, DDS (me TCP si protokoll transporti) dhe CoAP u zbulua se CoAP, n\u00eb p\u00ebrgjith\u00ebsi, tregonte nj\u00eb konsum m\u00eb t\u00eb ul\u00ebt t\u00eb band\u00ebs q\u00eb nuk rritej me rritjen e humbjeve t\u00eb paketave t\u00eb rrjetit ose me vones\u00ebn n\u00eb rrjet, n\u00eb dallim nga MQTT dhe DDS, ku n\u00eb skenar\u00ebt e p\u00ebrmendur u vu re rritje e p\u00ebrdorimit t\u00eb kapacitetit t\u00eb kanalit. N\u00eb nj\u00eb skenar tjet\u00ebr u angazhuan nj\u00eb num\u00ebr i madh pajisjesh q\u00eb d\u00ebrgonin t\u00eb dh\u00ebna nj\u00ebkoh\u00ebsisht, e cila \u00ebsht\u00eb nj\u00eb rast tipik n\u00eb ambientet IoT. Rezultatet treguan se p\u00ebr ngarkes\u00eb m\u00eb t\u00eb lart\u00eb, CoAP ishte m\u00eb i p\u00ebrshtatsh\u00ebm.<\/p>\n<p>Me ngarkes\u00eb t\u00eb vog\u00ebl, CoAP p\u00ebrdori kapacitetin m\u00eb t\u00eb ul\u00ebt, pasuar nga MQTT dhe REST HTTP. Megjithat\u00eb, kur madh\u00ebsia e ngarkesave u rrit, rezultatet m\u00eb t\u00eb mira ishin nga REST HTTP.<\/p>\n<p><b>Konsum i energjis\u00eb<\/b><\/p>\n<p>\u00c7\u00ebshtja e konsumit t\u00eb energjis\u00eb gjithmon\u00eb ka r\u00ebnd\u00ebsi t\u00eb madhe, e sidomos n\u00eb sistemet IoT. N\u00ebse <noindex><a rel=\"nofollow\" href=\"https:\/\/ieeexplore.ieee.org\/document\/7899537\">krahasojm\u00eb <\/a><\/noindex>konsumimin e energjis\u00eb t\u00eb MQTT dhe HTTP, HTTP \"humb shum\u00eb m\u00eb tep\u00ebr. Nd\u00ebrsa CoAP \u00ebsht\u00eb m\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/www.mdpi.com\/1424-8220\/16\/12\/2044\/htm\">efikas n\u00eb energji <\/a><\/noindex>n\u00eb krahasim me MQTT, duke lejuar menaxhimin e energjis\u00eb. Megjithat\u00eb, n\u00eb skenar\u00ebt e thjesht\u00eb, MQTT \u00ebsht\u00eb m\u00eb i p\u00ebrshtatsh\u00ebm p\u00ebr shk\u00ebmbimin e informacionit n\u00eb rrjetet e internetit t\u00eb gj\u00ebrave, ve\u00e7an\u00ebrisht n\u00ebse nuk ka kufizime p\u00ebr fuqin\u00eb.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"http:\/\/cgweb1.northumbria.ac.uk\/SubjectAreaResources\/KF7046\/papers\/review\/iot\/lpb15.pdf\">E tjera <\/a><\/noindex>Eksperimenti, n\u00eb t\u00eb cilin u krahasuan aft\u00ebsit\u00eb e AMQP dhe MQTT n\u00eb nj\u00eb stend\u00eb provimi t\u00eb nj\u00eb rrjeti mobil ose t\u00eb paq\u00ebndruesh\u00ebm, tregoi se AMQP ofron m\u00eb shum\u00eb mund\u00ebsi n\u00eb aspektin e siguris\u00eb, nd\u00ebrsa MQTT \u00ebsht\u00eb m\u00eb efikas n\u00eb energji.<\/p>\n<p><b>Siguria<\/b><\/p>\n<p>Siguria \u00ebsht\u00eb nj\u00eb tjet\u00ebr \u00e7\u00ebshtje shum\u00eb e r\u00ebnd\u00ebsishme q\u00eb ngrithet gjat\u00eb studimit t\u00eb tem\u00ebs s\u00eb internetit t\u00eb gj\u00ebrave dhe llogaritjeve t\u00eb mjeteve\/cloud. Mekanizmi i siguris\u00eb zakonisht mb\u00ebshtetet n\u00eb TLS n\u00eb HTTP, MQTT, AMQP dhe XMPP, ose DTLS n\u00eb CoAP, si dhe mb\u00ebshtet\u00ebs i t\u00eb dy varianteve \u00ebsht\u00eb DDS.<\/p>\n<p>TLS dhe DTLS fillojn\u00eb me nj\u00eb proces negociate nd\u00ebrmjet pal\u00ebs klient dhe pal\u00ebs server p\u00ebr t\u00eb ndar\u00eb grupeve t\u00eb kodimit dhe \u00e7el\u00ebsat. T\u00eb dy pal\u00ebt bien dakord p\u00ebr grupet p\u00ebr t\u00eb garantuar q\u00eb komunikimi tjet\u00ebr zhvillohet n\u00eb nj\u00eb kanal t\u00eb sigurt. Diferenca midis tyre p\u00ebrb\u00ebhet nga modifikime t\u00eb vogla q\u00eb lejojn\u00eb DTLS-n\u00eb e bazuar n\u00eb UDP t\u00eb punoj\u00eb n\u00eb lidhje t\u00eb pasigurta.<\/p>\n<p>N\u00eb <noindex><a rel=\"nofollow\" href=\"http:\/\/www.isg.rhul.ac.uk\/tls\/lucky13.html\">sulmeve testuese<\/a><\/noindex> n\u00eb disa realizime t\u00eb ndryshme t\u00eb TLS dhe DTLS u zbulua se TLS e kaloi m\u00eb mir\u00eb k\u00ebt\u00eb detyr\u00eb. Sulmet ndaj DTLS ishin m\u00eb t\u00eb suksesshme p\u00ebr shkak t\u00eb toleranc\u00ebs s\u00eb tij ndaj gabimeve.<\/p>\n<p>Megjithat\u00eb, problemi m\u00eb i madh me k\u00ebto protokolle \u00ebsht\u00eb se ato fillimisht nuk ishin projektuar p\u00ebr p\u00ebrdorim n\u00eb IoT dhe nuk parashikonin pun\u00ebn n\u00eb mjete ose n\u00eb cloud. P\u00ebrmes shk\u00ebmbimit t\u00eb rregullt (handshaking) ata shtojn\u00eb nj\u00eb trafik t\u00eb shtuar me \u00e7do krijim t\u00eb lidhjes, \u00e7ka e shteron burimet kompjuterike. N\u00eb mesatarisht, v\u00ebrehet nj\u00eb rritje prej 6,5% p\u00ebr TLS dhe 11% p\u00ebr DTLS n\u00eb ngarkes\u00ebn sh\u00ebrbyese krahasuar me komunikimin pa nivel sigurie. N\u00eb ambientet e pasura me burime, t\u00eb cilat zakonisht gjenden n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/www.cloud4y.ru\/cloud-hosting\/cloud-server\/?utm_source=habr&amp;utm_medium=referral&amp;utm_campaign=article\">cloud <\/a><\/noindex>k\u00ebto nuk do t\u00eb jen\u00eb nj\u00eb problem, por n\u00eb lidhjen midis IoT dhe nivelit t\u00eb mjeteve, kjo b\u00ebhet nj\u00eb kufizim i r\u00ebnd\u00ebsish\u00ebm.<\/p>\n<p>\u00c7far\u00eb duhet t\u00eb zgjedhim? Nuk ka nj\u00eb p\u00ebrgjigje t\u00eb qart\u00eb. MQTT dhe HTTP duken si protokollet m\u00eb t\u00eb perspektiv\u00eb, pasi konsiderohen si zgjidhje relativisht m\u00eb t\u00eb pjekura dhe m\u00eb stabile p\u00ebr IoT n\u00eb krahasim me protokolle t\u00eb tjera.<\/p>\n<h3>Zgjidhjet e bazuara n\u00eb nj\u00eb protokoll komunikimi t\u00eb vet\u00ebm<\/h3>\n<p>\nPraktika e nj\u00eb zgjidhjeje me nj\u00eb protokoll ka shum\u00eb disavantazhe. P\u00ebr shembull, nj\u00eb protokoll q\u00eb \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm p\u00ebr nj\u00eb mjedis t\u00eb kufizuar mund t\u00eb mos funksionoj\u00eb n\u00eb nj\u00eb domene q\u00eb ka k\u00ebrkesa t\u00eb rrepta p\u00ebr siguri. Duke marr\u00eb parasysh k\u00ebt\u00eb, na mbetet t\u00eb heqim dor\u00eb nga pothuajse t\u00eb gjitha zgjidhjet e mundshme t\u00eb bazuara n\u00eb nj\u00eb protokoll n\u00eb ekosistemin Fog-to-Cloud n\u00eb IoT, p\u00ebrve\u00e7 MQTT dhe REST HTTP.<\/p>\n<p><b>REST HTTP si nj\u00eb zgjidhje me nj\u00eb protokoll<\/b><\/p>\n<p>Ka nj\u00eb shembull t\u00eb mir\u00eb t\u00eb nd\u00ebrveprimit t\u00eb k\u00ebrkesave dhe p\u00ebrgjigjeve REST HTTP n\u00eb fush\u00ebn e IoT-to-Fog: <noindex><a rel=\"nofollow\" href=\"https:\/\/dl.acm.org\/citation.cfm?doid=3152130.3152140\">ferma inteligjente<\/a><\/noindex>. Kafsh\u00ebt furnizohen me sensor\u00eb t\u00eb veshur (klienti IoT, C) dhe menaxhohen p\u00ebrmes llogaritjes n\u00eb cloud nga sistemi fermier inteligjent (serveri Fog, S).<\/p>\n<p>N\u00eb titullin e metod\u00ebs POST specifikohet burimi q\u00eb do t\u00eb ndryshohet (\/farm\/animals), si dhe versioni i HTTP dhe tipi i p\u00ebrmbajtjes, i cili n\u00eb k\u00ebt\u00eb rast \u00ebsht\u00eb nj\u00eb objekt JSON q\u00eb p\u00ebrfaq\u00ebson ferm\u00ebn e bag\u00ebtive q\u00eb duhet t\u00eb menaxhohet nga sistemi (Dulcin\u00e9a\/nostalgjia). P\u00ebrgjigja nga serveri tregon se k\u00ebrkesa ishte e suksesshme, duke d\u00ebrguar kodin e statusit HTTPS 201 (burimi \u00ebsht\u00eb krijuar). Metoda GET duhet t\u00eb specifikoj\u00eb vet\u00ebm burimin e k\u00ebrkuar n\u00eb URI (p\u00ebr shembull, \/farm\/animals\/1), q\u00eb kthen nj\u00eb p\u00ebrfaq\u00ebsim JSON t\u00eb kafsh\u00ebs me k\u00ebt\u00eb identifikues nga serveri. <\/p>\n<p>Metoda PUT p\u00ebrdoret kur \u00ebsht\u00eb e nevojshme t\u00eb p\u00ebrdit\u00ebsohet nj\u00eb rekord specifik t\u00eb burimit. N\u00eb k\u00ebt\u00eb rast, n\u00eb burim specifikohet URI p\u00ebr parametrin q\u00eb do t\u00eb ndryshohet dhe vlera aktuale (p\u00ebr shembull, q\u00eb do t\u00eb tregonte se lo\u00e7ka p\u00ebr momentin \u00ebsht\u00eb duke ecur, \/farm\/animals\/1?status=ecje). N\u00eb fund, metoda DELETE p\u00ebrdoret n\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme me metod\u00ebn GET, por thjesht fshin burimin si rezultat i operacionit. <\/p>\n<p><b>MQTT si nj\u00eb zgjidhje me nj\u00eb protokoll<\/b><\/p>\n<p><img decoding=\"async\" alt=\"IoT, mjegull dhe reve: le t\u00eb flasim p\u00ebr teknologjit\u00eb?\" src=\"\/wp-content\/uploads\/2019\/09\/529857b556ea5a186ac1519e2804d1b8.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nLe t\u00eb marrim po at\u00eb ferm\u00eb inteligjente, por n\u00eb vend t\u00eb REST HTTP t\u00eb p\u00ebrdorim protokollin MQTT. Nj\u00eb server lokal me bibliotek\u00ebn Mosquitto t\u00eb instaluar vepron si broker. N\u00eb k\u00ebt\u00eb shembull, nj\u00eb kompjuter i thjesht\u00eb (i quajtur si serveri i ferm\u00ebs) Raspberry Pi sh\u00ebrben si klient MQTT, i implementuar p\u00ebrmes instalimit t\u00eb bibliotek\u00ebs MQTT Paho, plot\u00ebsisht t\u00eb p\u00ebrshtatshme me brokerin Mosquitto.<\/p>\n<p>Ky klient i p\u00ebrgjigjet nivelit t\u00eb abstraksionit IoT q\u00eb p\u00ebrfaq\u00ebson nj\u00eb pajisje me aft\u00ebsi zbuluese dhe llogarit\u00ebse. Nd\u00ebrmjet\u00ebsi, nga ana tjet\u00ebr, i p\u00ebrgjigjet nj\u00eb niveli m\u00eb t\u00eb lart\u00eb abstraksioni, duke p\u00ebrfaq\u00ebsuar nj\u00eb nyje llogarit\u00ebse t\u00eb mjegull\u00ebs, e karakterizuar nga kapacitete m\u00eb t\u00eb m\u00ebdha n\u00eb procesim dhe ruajtje t\u00eb t\u00eb dh\u00ebnave.<\/p>\n<p>N\u00eb skenarin e propozuar t\u00eb 'ferm\u00eb inteligjente', Raspberry Pi lidhet me nj\u00eb akseleromet\u00ebr, GPS dhe sensor\u00eb temperature dhe publikojn\u00eb t\u00eb dh\u00ebnat nga k\u00ebta sensor\u00eb n\u00eb nyj\u00ebn e mjegull\u00ebs. Si\u00e7 e dini, MQTT e sheh temat si nj\u00eb hierarki. Nj\u00eb botues MQTT mund t\u00eb publikoj\u00eb mesazhe n\u00eb nj\u00eb grup t\u00eb caktuar temash. N\u00eb rastin ton\u00eb, ka tre. P\u00ebr sensorin q\u00eb mat temperatur\u00ebn n\u00eb stall\u00eb p\u00ebr kafsh\u00ebt, klienti zgjedh tem\u00ebn (animalfarm\/shed\/temperature). P\u00ebr sensor\u00ebt q\u00eb masin vendndodhjen GPS dhe l\u00ebvizjen e kafsh\u00ebve p\u00ebrmes akselerometrit, klienti publikon p\u00ebrdit\u00ebsime (animalfarm\/animal\/GPS) dhe (animalfarm\/animal\/movement).<\/p>\n<p>K\u00ebto informacione do t\u00eb transmetohen te brokeri, i cili mund ta ruaj\u00eb at\u00eb p\u00ebrkoh\u00ebsisht n\u00eb nj\u00eb baz\u00eb t\u00eb dh\u00ebnash lokale p\u00ebr rast se nj\u00eb abonues tjet\u00ebr shfaqet m\u00eb von\u00eb.<\/p>\n<p>P\u00ebrve\u00e7 serverit lokal q\u00eb vepron si broker MQTT n\u00eb mjegull\u00eb dhe t\u00eb cilit Raspberry Pi, q\u00eb vepron si klient\u00eb MQTT, d\u00ebrgon t\u00eb dh\u00ebnat nga sensor\u00ebt, n\u00eb nivelin e cloud-it mund t\u00eb ket\u00eb edhe nj\u00eb broker tjet\u00ebr MQTT. N\u00eb k\u00ebt\u00eb rast, informacioni q\u00eb d\u00ebrgohet te brokeri lokal mund t\u00eb ruhet p\u00ebrkoh\u00ebsisht n\u00eb nj\u00eb baz\u00eb t\u00eb dh\u00ebnash lokale dhe\/ose t\u00eb d\u00ebrgohet n\u00eb cloud. Brokeri MQTT mjegullor n\u00eb k\u00ebt\u00eb situat\u00eb p\u00ebrdoret p\u00ebr t\u00eb lidhur t\u00eb gjitha t\u00eb dh\u00ebnat me brokerin MQTT n\u00eb cloud. N\u00eb nj\u00eb arkitektur\u00eb t\u00eb till\u00eb, p\u00ebrdoruesi i aplikacionit mobil mund t\u00eb abonohet te t\u00eb dy broker\u00ebt.<\/p>\n<p>N\u00eb rast se ka nj\u00eb d\u00ebshtim t\u00eb lidhjes me nj\u00eb nga broker\u00ebt (p\u00ebr shembull, at\u00eb n\u00eb cloud), p\u00ebrdoruesi p\u00ebrfundimtar do t\u00eb marr\u00eb informacion nga tjetri (mjegullor). Kjo \u00ebsht\u00eb nj\u00eb ve\u00e7ori karakteristike e sistemeve t\u00eb kombinuara t\u00eb mjegull\u00ebs dhe llogaritjeve n\u00eb cloud. Pas skem\u00ebs, aplikacioni mobil mund t\u00eb konfigurohet t\u00eb lidh\u00ebt fillimisht me brokerin MQTT mjegullor, dhe n\u00eb rast d\u00ebshtimi, t\u00eb lidhet me brokerin MQTT n\u00eb cloud. Kjo zgjidhje \u00ebsht\u00eb vet\u00ebm nj\u00eb nga shum\u00eb n\u00eb sistemet IoT-F2C. <\/p>\n<h3>Zgjidhje me shum\u00eb protokolle<\/h3>\n<p>\nZgjidhjet me nj\u00eb protokoll jan\u00eb popullore p\u00ebr shkak t\u00eb leht\u00ebsis\u00eb s\u00eb implementimit t\u00eb tyre. Por \u00ebsht\u00eb e qart\u00eb se n\u00eb sistemet IoT-F2C ka kuptim t\u00eb kombinohen protokolle t\u00eb ndryshme. Ideja \u00ebsht\u00eb se n\u00eb nivele t\u00eb ndryshme mund t\u00eb operojn\u00eb protokolle t\u00eb ndryshme. Merrni p\u00ebr shembull tre abstraksione: nivelet IoT, mjegull dhe computing n\u00eb re. Pajisjet n\u00eb nivelin IoT zakonisht konsiderohen si t\u00eb kufizuara. P\u00ebr k\u00ebt\u00eb p\u00ebrmbledhje, le t\u00eb shqyrtojm\u00eb nivelet IoT si m\u00eb t\u00eb kufizuara, mjegullat si m\u00eb pak t\u00eb kufizuara dhe computing n\u00eb re si \"diku n\u00eb mes\". K\u00ebshtu, midis IoT dhe abstraksioneve t\u00eb mjegull\u00ebs, zgjidhjet aktuale t\u00eb protokollit p\u00ebrfshijn\u00eb MQTT, CoAP dhe XMPP. Nga ana tjet\u00ebr, midis mjegull\u00ebs dhe re, AMQP \u00ebsht\u00eb nj\u00eb nga protokollet kryesore q\u00eb p\u00ebrdoren s\u00eb bashku me REST HTTP, i cili p\u00ebr shkak t\u00eb fleksibilitetit t\u00eb tij gjithashtu p\u00ebrdoret midis IoT dhe shtresave t\u00eb mjegull\u00ebs. <\/p>\n<p>Problemi kryesor k\u00ebtu \u00ebsht\u00eb p\u00ebrputhshm\u00ebria funksionale e protokolleve dhe leht\u00ebsia e transferimit t\u00eb mesazheve nga nj\u00eb protokoll n\u00eb tjetrin. N\u00eb m\u00ebnyr\u00eb ideale, n\u00eb t\u00eb ardhmen, arkitektura e sistemit t\u00eb internetit t\u00eb gj\u00ebrave me burime n\u00eb re dhe mjegull do t\u00eb jet\u00eb e pavarur nga protokolli i komunikimit q\u00eb p\u00ebrdoret dhe do t\u00eb siguroj\u00eb bashk\u00ebpunim t\u00eb mir\u00eb mes protokolleve t\u00eb ndryshme.<\/p>\n<p><img decoding=\"async\" alt=\"IoT, mjegull dhe reve: le t\u00eb flasim p\u00ebr teknologjit\u00eb?\" src=\"\/wp-content\/uploads\/2019\/09\/cddc564cad572966002ae22eff8cb99d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nTani p\u00ebr tani, kjo nuk \u00ebsht\u00eb k\u00ebshtu, ka kuptim t\u00eb kombinohen protokolle pa dallime t\u00eb r\u00ebnd\u00ebsishme. Me k\u00ebt\u00eb q\u00ebllim, nj\u00eb zgjidhje e mundshme bazohet n\u00eb kombinimin e dy protokolleve q\u00eb ndjekin t\u00eb nj\u00ebjtin stil arkitekturor, REST HTTP dhe CoAP. Nj\u00eb tjet\u00ebr zgjidhje e propozuar \u00ebsht\u00eb bazuar n\u00eb kombinimin e dy protokolleve q\u00eb ofrojn\u00eb nd\u00ebrveprimin sipas modelit 'publikim-abonim', MQTT dhe AMQP. P\u00ebrdorimi i koncepteve t\u00eb ngjashme (t\u00eb dy MQTT dhe AMQP p\u00ebrdorin broker\u00eb, nd\u00ebrsa CoAP dhe HTTP p\u00ebrdorin REST), e leht\u00ebson implementimin e k\u00ebtyre kombinimeve dhe k\u00ebrkon m\u00eb pak p\u00ebrpjekje p\u00ebr integrimin.<\/p>\n<p><img decoding=\"async\" alt=\"IoT, mjegull dhe reve: le t\u00eb flasim p\u00ebr teknologjit\u00eb?\" src=\"\/wp-content\/uploads\/2019\/09\/395bc75880a154aeab7b61d043476802.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nN\u00eb figur\u00ebn (a) paraqiten dy modele t\u00eb bazuara n\u00eb k\u00ebrkesat-\u092a\u00ebrgjigjet, HTTP dhe CoAP, dhe mund\u00ebsia e vendosjes s\u00eb tyre n\u00eb zgjidhjen IoT-F2C. Duke qen\u00eb se HTTP \u00ebsht\u00eb nj\u00eb nga protokollet m\u00eb t\u00eb njohura dhe t\u00eb adaptuara n\u00eb rrjetet moderne, \u00ebsht\u00eb pak e mundur q\u00eb ai t\u00eb z\u00ebvend\u00ebsohet krejt\u00ebsisht nga protokolle t\u00eb tjera t\u00eb komunikimit. Nd\u00ebr grupe, q\u00eb p\u00ebrfaq\u00ebsojn\u00eb pajisje t\u00eb fuqishme, q\u00eb jan\u00eb midis re dhe mjegull\u00ebs, REST HTTP \u00ebsht\u00eb nj\u00eb zgjidhje e arsyeshme.<\/p>\n<p>Nga ana tjet\u00ebr, p\u00ebr pajisjet me burime t\u00eb kufizuara llogarit\u00ebse, q\u00eb lidhen midis niveleve t\u00eb mjegull\u00ebs dhe IoT, \u00ebsht\u00eb m\u00eb efikase t\u00eb p\u00ebrdoret CoAP. Nj\u00eb nga p\u00ebrfitimet e m\u00ebdha t\u00eb CoAP \u00ebsht\u00eb n\u00eb fakt p\u00ebrputhshm\u00ebria e tij me HTTP, pasi t\u00eb dy protokollet jan\u00eb t\u00eb bazuara n\u00eb principet e REST.<\/p>\n<p>N\u00eb figur\u00ebn (b) paraqiten dy modele nd\u00ebrveprimi 'publikim-abonim' n\u00eb nj\u00eb skenar, duke p\u00ebrfshir\u00eb MQTT dhe AMQP. Nd\u00ebrsa hipotetikisht t\u00eb dy protokollet mund t\u00eb p\u00ebrdoren p\u00ebr komunikimin midis nyjeve n\u00eb \u00e7do nivel abstraksioni, pozita e tyre duhet t\u00eb p\u00ebrcaktohet n\u00eb baz\u00eb t\u00eb performanc\u00ebs. MQTT \u00ebsht\u00eb zhvilluar si nj\u00eb protokoll i thjeshtuar p\u00ebr pajisje me burime t\u00eb kufizuara llogarit\u00ebse, k\u00ebshtu q\u00eb mund t\u00eb p\u00ebrdoret p\u00ebr komunikimin midis IoT dhe mjegull\u00ebs. AMQP \u00ebsht\u00eb m\u00eb i p\u00ebrshtatsh\u00ebm p\u00ebr pajisje m\u00eb t\u00eb fuqishme, q\u00eb do ta vendosnin at\u00eb midis nyjeve t\u00eb mjegull\u00ebs dhe re. N\u00eb vend t\u00eb MQTT n\u00eb IoT mund t\u00eb p\u00ebrdoret protokolli XMPP, pasi konsiderohet si i leht\u00eb. Por ai nuk p\u00ebrdoret aq gjer\u00ebsisht n\u00eb skenar\u00eb t\u00eb till\u00eb.<\/p>\n<h3>P\u00ebrfundimet<\/h3>\n<p>\n\u00cbsht\u00eb pak e mundur q\u00eb nj\u00eb nga protokollet e shqyrtuara t\u00eb jet\u00eb e mjaftueshme p\u00ebr t\u00eb mbuluar gjith\u00eb komunikimin n\u00eb sistem, duke filluar nga pajisjet me burime t\u00eb kufizuara deri te server\u00ebt e re. Studiimi ka treguar se dy opsionet m\u00eb premtuese, q\u00eb p\u00ebrdoren m\u00eb shpesh nga zhvilluesit, jan\u00eb MQTT dhe RESTful HTTP. K\u00ebto dy protokolle jan\u00eb jo vet\u00ebm m\u00eb t\u00eb pjekurat dhe t\u00eb q\u00ebndrueshmet, por p\u00ebrfshijn\u00eb gjithashtu shum\u00eb implementime t\u00eb dokumentuara mir\u00eb dhe burime online t\u00eb suksesshme.<\/p>\n<p>P\u00ebr shkak t\u00eb stabilitetit t\u00eb tij dhe konfigurimit t\u00eb leht\u00eb, MQTT \u00ebsht\u00eb protokolli q\u00eb me kalimin e koh\u00ebs ka treguar performanc\u00eb t\u00eb shk\u00eblqyer n\u00eb p\u00ebrdorimin n\u00eb nivelin IoT me pajisje t\u00eb kufizuara. N\u00eb pjes\u00ebt e sistemit, ku lidhja e kufizuar dhe konsumimi i bateris\u00eb nuk jan\u00eb problem, p\u00ebr shembull, n\u00eb disa fusha t\u00eb mjegull\u00ebs dhe n\u00eb shumic\u00ebn e llogaritjeve n\u00eb re, RESTful HTTP \u00ebsht\u00eb nj\u00eb zgjedhje e thjesht\u00eb. CoAP gjithashtu duhet t\u00eb merret parasysh, pasi po zhvillohet gjithashtu me shpejt\u00ebsi si nj\u00eb standard i shk\u00ebmbimit t\u00eb mesazheve IoT, dhe \u00ebsht\u00eb shum\u00eb e mundur q\u00eb n\u00eb t\u00eb ardhmen e af\u00ebrt t\u00eb arrij\u00eb nj\u00eb nivel stabiliteti dhe pjekurie t\u00eb ngjash\u00ebm me MQTT dhe HTTP. Por standardi tani \u00ebsht\u00eb duke u zhvilluar, \u00e7ka sjell problemet e shkall\u00ebzueshm\u00ebris\u00eb afatshkurtra.<\/p>\n<p><b>\u00c7far\u00eb tjet\u00ebr t\u00eb dobishme mund t\u00eb lexoni n\u00eb blog <noindex><a rel=\"nofollow\" href=\"https:\/\/www.cloud4y.ru\/?utm_source=habr&amp;utm_medium=referral&amp;utm_campaign=article\">Cloud4Y<\/a><\/noindex><\/b><\/p>\n<p>\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/cloud4y\/blog\/466755\/\">Kompiuteri do t'ju b\u00ebj\u00eb t\u00eb shijoni<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/464155\/\">AI ndihmon n\u00eb studimin e kafsh\u00ebve t\u00eb Afrik\u00ebs <\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/cloud4y\/blog\/465251\/\">Ver\u00ebra po p\u00ebrfundon. Pothuajse nuk ka t\u00eb dh\u00ebna t\u00eb pakthyer<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/461713\/\">4 m\u00ebnyra p\u00ebr t\u00eb kursyer n\u00eb kopjet rezerv\u00eb n\u00eb cloud<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/cloud4y\/blog\/467769\/\">P\u00ebr nj\u00eb burim t\u00eb vet\u00ebm informacioni federal q\u00eb p\u00ebrmban t\u00eb dh\u00ebna mbi popullsin\u00eb<\/a><\/noindex><\/p>\n<p>Regjistrohuni n\u00eb kanalin ton\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/t.me\/cloud4y\">Telegram<\/a><\/noindex>-kanali, p\u00ebr t\u00eb mos humbur artikujt tan\u00eb t\u00eb rinj! Shkruajm\u00eb jo m\u00eb shpesh se dy her\u00eb n\u00eb jav\u00eb dhe vet\u00ebm p\u00ebr \u00e7\u00ebshtje t\u00eb r\u00ebnd\u00ebsishme.<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/cloud4y\/blog\/467711\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0420\u0430\u0437\u0432\u0438\u0442\u0438\u0435 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439 \u0432 \u043e\u0431\u043b\u0430\u0441\u0442\u0438 \u0441\u043e\u0444\u0442\u0430 \u0438 \u0436\u0435\u043b\u0435\u0437\u0430, \u043f\u043e\u044f\u0432\u043b\u0435\u043d\u0438\u0435 \u043d\u043e\u0432\u044b\u0445 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u0441\u0432\u044f\u0437\u0438 \u043f\u0440\u0438\u0432\u0435\u043b\u0438 \u043a \u0440\u0430\u0441\u0448\u0438\u0440\u0435\u043d\u0438\u044e \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0430 \u0432\u0435\u0449\u0435\u0439 (IoT). \u041a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u043e \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432 \u0440\u0430\u0441\u0442\u0451\u0442 \u0434\u0435\u043d\u044c \u043e\u0442\u043e \u0434\u043d\u044f, \u0438 \u043e\u043d\u0438 \u0433\u0435\u043d\u0435\u0440\u0438\u0440\u0443\u044e\u0442 \u043e\u0433\u0440\u043e\u043c\u043d\u044b\u0439 \u043e\u0431\u044a\u0451\u043c \u0434\u0430\u043d\u043d\u044b\u0445. \u041f\u043e\u044d\u0442\u043e\u043c\u0443 \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u0435\u0442 \u043f\u043e\u0442\u0440\u0435\u0431\u043d\u043e\u0441\u0442\u044c \u0432 \u0443\u0434\u043e\u0431\u043d\u043e\u0439 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u0435 \u0441\u0438\u0441\u0442\u0435\u043c\u044b, \u0441\u043f\u043e\u0441\u043e\u0431\u043d\u043e\u0439 \u043e\u0431\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u0442\u044c, \u0445\u0440\u0430\u043d\u0438\u0442\u044c \u0438 \u043f\u0435\u0440\u0435\u0434\u0430\u0432\u0430\u0442\u044c \u044d\u0442\u0438 \u0434\u0430\u043d\u043d\u044b\u0435. \u0421\u0435\u0439\u0447\u0430\u0441 \u0434\u043b\u044f \u044d\u0442\u0438\u0445 \u0446\u0435\u043b\u0435\u0439 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0442 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0435 \u0441\u0435\u0440\u0432\u0438\u0441\u044b. \u041e\u0434\u043d\u0430\u043a\u043e \u0441\u0442\u0430\u043d\u043e\u0432\u044f\u0449\u0430\u044f\u0441\u044f \u0432\u0441\u0451 \u0431\u043e\u043b\u0435\u0435 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u043e\u0439 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28806,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-38375","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-novosti-interneta"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0420\u0430\u0437\u0432\u0438\u0442\u0438\u0435 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439 \u0432 \u043e\u0431\u043b\u0430\u0441\u0442\u0438 \u0441\u043e\u0444\u0442\u0430 \u0438.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/iot-tuman-i-oblaka-pogovorim-pro-tehnologii\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47IoT, \u0442\u0443\u043c\u0430\u043d \u0438 \u043e\u0431\u043b\u0430\u043a\u0430: \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043f\u0440\u043e \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0438? | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0420\u0430\u0437\u0432\u0438\u0442\u0438\u0435 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439 \u0432 \u043e\u0431\u043b\u0430\u0441\u0442\u0438 \u0441\u043e\u0444\u0442\u0430 \u0438.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/iot-tuman-i-oblaka-pogovorim-pro-tehnologii\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:23:21+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:23:21+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47IoT, re dhe mjegull: t\u00eb flasim p\u00ebr teknologjit\u00eb? | ProHoster","description":"Zhvillimi i teknologjive n\u00eb fush\u00ebn e softuer\u00ebve dhe.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/iot-tuman-i-oblaka-pogovorim-pro-tehnologii","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47IoT, \u0442\u0443\u043c\u0430\u043d \u0438 \u043e\u0431\u043b\u0430\u043a\u0430: \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043f\u0440\u043e \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0438? | ProHoster","og:description":"\u0420\u0430\u0437\u0432\u0438\u0442\u0438\u0435 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439 \u0432 \u043e\u0431\u043b\u0430\u0441\u0442\u0438 \u0441\u043e\u0444\u0442\u0430 \u0438.","og:url":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/iot-tuman-i-oblaka-pogovorim-pro-tehnologii","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:23:21+00:00","article:modified_time":"2019-10-31T19:23:21+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38375","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 21:45:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:10:24","updated":"2026-01-23 21:45:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/38375","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=38375"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/38375\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/28806"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=38375"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=38375"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=38375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}