{"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\/ro\/blog\/news\/iot-tuman-i-oblaka-pogovorim-pro-tehnologii","title":{"rendered":"IoT, cea\u021b\u0103 \u0219i nori: s\u0103 vorbim despre tehnologii?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"IoT, cea\u021b\u0103 \u0219i nori: s\u0103 vorbim despre tehnologii?\" src=\"\/wp-content\/uploads\/2019\/09\/89eae3426589d2ed8041fd6dd26498cb.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i>Dezvoltarea tehnologiilor \u00een domeniul software-ului \u0219i hardware-ului, apari\u021bia unor noi protocoale de comunicare a dus la extinderea internetului lucrurilor (IoT). Num\u0103rul dispozitivelor cre\u0219te zi de zi, gener\u00e2nd un volum uria\u0219 de date. Prin urmare, exist\u0103 o nevoie de o arhitectur\u0103 sistemic\u0103 convenabil\u0103, capabil\u0103 s\u0103 proceseze, s\u0103 stocheze \u0219i s\u0103 transmit\u0103 aceste date.<\/p>\n<p>\u00cen prezent, pentru aceste scopuri se folosesc servicii cloud. Totu\u0219i, paradigma de calcul pe nori (Fog) care devine din ce \u00een ce mai popular\u0103 poate completa solu\u021biile cloud, scal\u00e2nd \u0219i optimiz\u00e2nd infrastructura IoT. <\/i><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>\u00abNori\u00bb pot r\u0103spunde majorit\u0103\u021bii cerin\u021belor IoT. De exemplu, pot asigura monitorizarea serviciilor, procesarea rapid\u0103 a oric\u0103ror volume de date generate de dispozitive, precum \u0219i vizualizarea acestora. Calculul pe nori este \u00eens\u0103 mai eficient \u00een rezolvarea unor sarcini \u00een timp real. Acesta asigur\u0103 un r\u0103spuns rapid la solicit\u0103ri \u0219i o \u00eent\u00e2rziere minim\u0103 \u00een procesarea datelor. Cu alte cuvinte, Fog completeaz\u0103 exact \u00abnori\u00bb, extinz\u00e2ndu-le capacit\u0103\u021bile.<\/p>\n<p>Cu toate acestea, \u00eentrebarea principal\u0103 este alta: cum ar trebui s\u0103 interac\u021bioneze toate acestea \u00een contextul IoT? Ce protocoale de comunicare vor fi cele mai eficiente \u00een cadrul sistemului integrat IoT-Fog-Cloud?<\/p>\n<p>\u00cen ciuda aparentei domin\u0103ri a HTTP, \u00een sistemele IoT, Fog \u0219i Cloud sunt utilizate o multitudine de alte solu\u021bii. Aceasta se datoreaz\u0103 faptului c\u0103 IoT trebuie s\u0103 combine capacit\u0103\u021bile func\u021bionale ale diverselor senzori de dispozitive cu cerin\u021bele de securitate, compatibilitate \u0219i alte cerin\u021be impuse de utilizatori.<\/p>\n<p>Numai c\u0103 nu exist\u0103 o viziune unitar\u0103 asupra arhitecturii de referin\u021b\u0103 \u0219i standardului de comunicare. Prin urmare, crearea unui nou protocol sau adaptarea celui existent pentru sarcini specifice IoT reprezint\u0103 una dintre cele mai importante provoc\u0103ri cu care se confrunt\u0103 comunitatea IT.<\/p>\n<p>Ce protocoale sunt utilizate \u00een prezent \u0219i ce pot oferi acestea? S\u0103 vedem. Dar mai \u00eent\u00e2i s\u0103 discut\u0103m principiile ecosistemului \u00een care interac\u021bioneaz\u0103 nori, cea\u021b\u0103 \u0219i internetul lucrurilor.<\/p>\n<h3>Arhitectura IoT Fog-to-Cloud (F2C)<\/h3>\n<p>\nCu siguran\u021b\u0103 a\u021bi observat c\u00e2t de multe eforturi sunt depuse pentru a studia avantajele \u0219i beneficiile asociate cu managementul ra\u021bional \u0219i coordonat al IoT, norilor \u0219i ce\u021bii. Dac\u0103 nu, iat\u0103 trei ini\u021biative de standardizare: <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> \u0219i <noindex><a rel=\"nofollow\" href=\"http:\/\/www.mf2c-project.eu\/\">mF2C H2020 EU project<\/a><\/noindex>. <\/p>\n<p>Dac\u0103 anterior erau considerate doar 2 niveluri, cloud \u0219i dispozitive finale, arhitectura propus\u0103 introduce un nou nivel \u2014 calculul fog. \u00cen acest context, nivelul fog poate fi \u00eemp\u0103r\u021bit \u00een mai multe subniveluri, \u00een func\u021bie de specificul resurselor sau de setul de politici care definesc utilizarea diferitelor dispozitive \u00een aceste subniveluri.<\/p>\n<p>Cum poate ar\u0103ta aceast\u0103 abstrac\u021bie? Iat\u0103 un ecosistem tipic IoT-Fog-Cloud. Dispozitivele IoT trimit date c\u0103tre servere \u0219i dispozitive de calcul mai performante, pentru a rezolva sarcini care necesit\u0103 un nivel sc\u0103zut de laten\u021b\u0103. \u00cen acelea\u0219i sisteme, cloud-ul este responsabil pentru rezolvarea sarcinilor care necesit\u0103 un volum mare de resurse de calcul sau spa\u021biu pentru stocarea datelor.<\/p>\n<p><img decoding=\"async\" alt=\"IoT, cea\u021b\u0103 \u0219i nori: s\u0103 vorbim despre tehnologii?\" src=\"\/wp-content\/uploads\/2019\/09\/c78ea915ac4743a3def5651778e77873.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSmartphone-urile, ceasurile inteligente \u0219i alte gadgeturi pot fi, de asemenea, parte a IoT. Dar astfel de dispozitive, de obicei, folosesc protocoale de comunicare proprietare de la mari dezvoltatori. Datele generate de internetul obiectelor sunt transmise la nivelul fog prin protocolul REST HTTP, care asigur\u0103 flexibilitate \u0219i compatibilitate func\u021bional\u0103 \u00een crearea serviciilor RESTful. Acest aspect este important av\u00e2nd \u00een vedere nevoia de a asigura compatibilitatea invers\u0103 cu infrastructura de calcul existent\u0103, care func\u021bioneaz\u0103 pe computere locale, servere sau clustere de servere. Resursele locale, denumite \u201enodi fog\u201d, filtreaz\u0103 datele primite \u0219i le proceseaz\u0103 local sau le trimit \u00een cloud pentru calcule suplimentare.<\/p>\n<p>Cloud-urile suport\u0103 diferite protocoale de comunicare, dintre care cele mai \u00eent\u00e2lnite sunt AMQP \u0219i REST HTTP. Deoarece HTTP este bine cunoscut \u0219i este optimizat pentru internet, s-ar putea pune \u00eentrebarea: \u201ede ce s\u0103 nu-l folosim pentru a lucra cu IoT \u0219i fog?\u201d. Totu\u0219i, acest protocol are probleme de performan\u021b\u0103. Despre aceast\u0103 problem\u0103 vom discuta mai \u00een detaliu ulterior.<\/p>\n<p>\u00cen general, exist\u0103 2 modele de protocoale de comunicare adecvate pentru sistemul nostru. Acestea sunt cerere-r\u0103spuns \u0219i publicare-abonare. Primul model este mai cunoscut, \u00een special \u00een arhitectura client-server. Clientul solicit\u0103 informa\u021bii de la server, iar serverul prime\u0219te solicitarea, o proceseaz\u0103 \u0219i returneaz\u0103 un mesaj de r\u0103spuns. Protocoalele REST HTTP \u0219i CoAP func\u021bioneaz\u0103 dup\u0103 acest model.<\/p>\n<p>A doua model a ap\u0103rut din necesitatea de a asigura o comunicare asincron\u0103, distribuit\u0103, cu conexiune slab\u0103 \u00eentre sursele care genereaz\u0103 date \u0219i destinatarii acestor date.<\/p>\n<p><img decoding=\"async\" alt=\"IoT, cea\u021b\u0103 \u0219i nori: s\u0103 vorbim despre tehnologii?\" src=\"\/wp-content\/uploads\/2019\/09\/acf3b411fb9a0b7a61cf0188e4c29292.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nModelul presupune trei participan\u021bi: editorul (sursa de date), brokerul (dispecerul) \u0219i abonatul (destinatarul). Aici clientul, care ac\u021bioneaz\u0103 ca abonat, nu trebuie s\u0103 solicite informa\u021bii de la server. \u00cen loc s\u0103 trimit\u0103 solicit\u0103ri, el se aboneaz\u0103 la anumite evenimente din sistem prin intermediul brokerului, responsabil cu filtrarea tuturor mesajelor primite \u0219i cu rutarea acestora \u00eentre editori \u0219i abona\u021bi. Iar editorul, atunci c\u00e2nd are loc un eveniment referitor la un anumit subiect, \u00eel public\u0103 brokerului, care trimite abonatului datele referitoare la subiectul solicitat.<\/p>\n<p>\u00cen esen\u021b\u0103, aceast\u0103 arhitectur\u0103 se bazeaz\u0103 pe evenimente. \u0218i un astfel de model de interac\u021biune este interesant pentru aplica\u021biile din IoT, cloud, fog datorit\u0103 capacit\u0103\u021bii sale de a oferi scalabilitate \u0219i de a simplifica interac\u021biunea dintre diferite dispozitive, sus\u021bin\u00e2nd o conectivitate dinamic\u0103 \u201emul\u021bi la mul\u021bi\u201d \u0219i o comunicare asincron\u0103. Printre cele mai cunoscute protocoale de schimb de mesaje standardizate, care utilizeaz\u0103 modelul \u201epublicare-abonare\u201d, se num\u0103r\u0103 MQTT, AMQP \u0219i DDS.<\/p>\n<p>Este evident c\u0103 modelul \u201epublicare-abonare\u201d are multe avantaje:<\/p>\n<ul>\n<li>Editorii \u0219i abona\u021bii nu trebuie s\u0103 \u0219tie de existen\u021ba celuilalt;<\/li>\n<li>Un abonat poate primi informa\u021bii de la multe publica\u021bii diferite, iar un editor poate trimite date c\u0103tre mul\u021bi abona\u021bi diferi\u021bi (principiul \u201emul\u021bi la mul\u021bi\u201d);<\/li>\n<li>Editorul \u0219i abonatul nu trebuie s\u0103 fie activi simultan pentru a schimba date, deoarece brokerul (care func\u021bioneaz\u0103 ca un sistem de cozi) va putea stoca mesajul pentru clien\u021bii care nu sunt conecta\u021bi la re\u021bea \u00een acel moment.<\/li>\n<\/ul>\n<p>\nCu toate acestea, modelul \u201esolicitare-r\u0103spuns\u201d are \u0219i el propriile sale avantaje. \u00cen cazurile \u00een care capacit\u0103\u021bile p\u0103r\u021bii serverului pentru a gestiona solicit\u0103rile mai multor clien\u021bi nu reprezint\u0103 o problem\u0103, are sens s\u0103 se utilizeze solu\u021bii fiabile deja verificate.<\/p>\n<p>Exist\u0103, de asemenea, protocoale care sus\u021bin ambele modele. De exemplu, XMPP \u0219i HTTP 2.0, care suport\u0103 op\u021biunea \u201eserver push\u201d. IETF a lansat \u0219i CoAP. \u00cen \u00eencercarea de a rezolva problema schimbului de mesaje, au fost create c\u00e2teva alte solu\u021bii, cum ar fi protocolul WebSockets sau utilizarea protocolului HTTP prin QUIC (Quick UDP Internet Connections).<\/p>\n<p>\u00cen cazul WebSockets, de\u0219i este folosit pentru transmiterea datelor \u00een timp real de la server la clientul web \u0219i asigur\u0103 conexiuni permanente cu comunicare bidirec\u021bional\u0103 simultan\u0103, nu este destinat dispozitivelor cu resurse computa\u021bionale limitate. QUIC merit\u0103, de asemenea, men\u021bionat, deoarece acest nou protocol de transport ofer\u0103 o mul\u021bime de noi oportunit\u0103\u021bi. Dar, deoarece QUIC nu este \u00eenc\u0103 standardizat, este prematur s\u0103 prezicem aplicarea sa posibil\u0103 \u0219i impactul asupra solu\u021biilor \u00een domeniul IoT. A\u0219adar, WebSockets \u0219i QUIC r\u0103m\u00e2n \u00een memorie cu perspectiva asupra viitorului, dar nu le vom studia mai \u00een detaliu pentru moment.<\/p>\n<h3>Cine este cel mai dr\u0103gu\u021b din lume: compar\u0103m protocoalele<\/h3>\n<p>\nAcum s\u0103 discut\u0103m despre punctele forte \u0219i slabe ale protocoalelor. \u00cenaint\u00e2nd, trebuie s\u0103 spunem c\u0103 nu exist\u0103 un lider evident. Fiecare protocol are propriile sale avantaje \u0219i dezavantaje.<\/p>\n<p><b>Timpul de r\u0103spuns<\/b><\/p>\n<p>Una dintre cele mai importante caracteristici ale protocoalelor de comunicare, \u00een special \u00een ceea ce prive\u0219te internetul obiectelor, este timpul de r\u0103spuns. \u00cens\u0103, printre protocoalele existente, nu exist\u0103 un c\u00e2\u0219tig\u0103tor indiscutabil care s\u0103 demonstreze cel mai sc\u0103zut nivel de \u00eent\u00e2rziere \u00een diverse condi\u021bii. Totu\u0219i, exist\u0103 o mul\u021bime de cercet\u0103ri \u0219i compara\u021bii ale capacit\u0103\u021bilor protocoalelor.<\/p>\n<p>De exemplu, <noindex><a rel=\"nofollow\" href=\"https:\/\/www.researchgate.net\/publication\/323943358_Performance_Analysis_of_Internet_of_Things_Protocols_Based_FogCloud_over_High_Traffic\">rezultatele <\/a><\/noindex>Compara\u021biile eficien\u021bei HTTP \u0219i MQTT \u00een contextul IoT au ar\u0103tat c\u0103 timpul de r\u0103spuns pentru cereri este mai mic la MQTT dec\u00e2t la HTTP. Iar la <noindex><a rel=\"nofollow\" href=\"https:\/\/www.researchgate.net\/publication\/303188719_Comparison_of_two_lightweight_protocols_for_smartphone-based_sensing\">analiza <\/a><\/noindex>timpului de transmisie (RTT) pentru MQTT \u0219i CoAP s-a descoperit c\u0103 RTT-ul mediu pentru CoAP este cu 20% mai mic dec\u00e2t cel pentru MQTT.<\/p>\n<p>Altele <noindex><a rel=\"nofollow\" href=\"https:\/\/ieeexplore.ieee.org\/document\/7740559\">un experiment <\/a><\/noindex>Analiza RTT-ului pentru protocoalele MQTT \u0219i CoAP s-a desf\u0103\u0219urat \u00een dou\u0103 scenarii: re\u021bea local\u0103 \u0219i re\u021bea IoT. S-a constatat c\u0103 RTT-ul mediu este de 2-3 ori mai mare \u00een re\u021beaua IoT. MQTT cu QoS0 a avut rezultate mai slabe comparativ cu CoAP, iar MQTT cu QoS1 a ar\u0103tat un RTT mai mare datorit\u0103 ACK-urilor la nivelurile aplica\u021biei \u0219i transportului. Pentru diferite niveluri de QoS, \u00eent\u00e2rzierile \u00een re\u021bea f\u0103r\u0103 suprasarcin\u0103 pentru MQTT au fost de c\u00e2teva milisecunde, iar pentru CoAP \u2014 sute de microsecunde. Totu\u0219i, trebuie s\u0103 ne amintim c\u0103 \u00een re\u021bele mai pu\u021bin fiabile, MQTT, care func\u021bioneaz\u0103 pe TCP, va ar\u0103ta rezultate complet diferite.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/www.diva-portal.org\/smash\/get\/diva2:1092136\/FULLTEXT01.pdf\">Comparare <\/a><\/noindex>Timpul de r\u0103spuns al protocoalelor AMQP \u0219i MQTT a ar\u0103tat c\u0103, sub o sarcin\u0103 mic\u0103, nivelul de \u00eent\u00e2rziere este aproape identical. \u00cens\u0103, atunci c\u00e2nd se transmit volume mari de date, MQTT demonstreaz\u0103 un timp de r\u0103spuns mai scurt. Exist\u0103 \u0219i un alt <noindex><a rel=\"nofollow\" href=\"http:\/\/www.tfzr.rs\/esociety\/issues\/eSocietyVol3No1.pdf#page=26\">cercetare <\/a><\/noindex>CoAP a fost comparat cu HTTP \u00eentr-un scenariu de comunicare \u00eentre ma\u0219ini, utiliz\u00e2nd dispozitive desf\u0103\u0219urate pe vehicule dotate cu senzori de gaz, senzori de vreme, localizare (GPS) \u0219i interfa\u021b\u0103 de re\u021bea mobil\u0103 (GPRS). Timpul necesar pentru transmiterea mesajului CoAP prin re\u021beaua mobil\u0103 a fost de aproape trei ori mai scurt dec\u00e2t timpul necesar pentru utilizarea mesajelor HTTP.<\/p>\n<p>S-au realizat studii \u00een care au fost comparate nu dou\u0103, ci trei protocoale. De exemplu, <noindex><a rel=\"nofollow\" href=\"https:\/\/ieeexplore.ieee.org\/document\/7496622\">compara\u021bia <\/a><\/noindex>performan\u021bei protocoalelor IoT MQTT, DDS \u0219i CoAP \u00eentr-un scenariu medical utiliz\u00e2nd un emulator de re\u021bea. DDS a dep\u0103\u0219it MQTT \u00een ceea ce prive\u0219te \u00eent\u00e2rzierea testat\u0103 a telemetriei \u00een diverse condi\u021bii proaste de re\u021bea. CoAP bazat pe UDP a func\u021bionat bine pentru aplica\u021biile care necesitau un r\u0103spuns rapid, totu\u0219i, din cauza bazei sale pe UDP, a existat o pierdere semnificativ\u0103 \u0219i imprevizibil\u0103 de pachete.<\/p>\n<p><b>L\u0103\u021bimea de band\u0103<\/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\">Comparare <\/a><\/noindex>MQTT \u0219i CoAP \u00een ceea ce prive\u0219te eficien\u021ba utiliz\u0103rii l\u0103\u021bimii de band\u0103 s-a f\u0103cut prin num\u0103rarea totalului de date transmise \u00eentr-un mesaj. CoAP a ar\u0103tat o l\u0103\u021bime de band\u0103 mai mic\u0103 dec\u00e2t MQTT la transmiterea mesajelor mici. Cu toate acestea, c\u00e2nd s-a comparat eficien\u021ba protocoalelor \u00een ceea ce prive\u0219te raportul dintre datele utile \u0219i totalul de bi\u021bi transmi\u0219i, CoAP s-a dovedit a fi mai eficient.<\/p>\n<p>Upon <noindex><a rel=\"nofollow\" href=\"https:\/\/ieeexplore.ieee.org\/document\/7496622\">analiz\u0103 <\/a><\/noindex>utiliz\u0103rii l\u0103\u021bimii de band\u0103 MQTT, DDS (cu TCP ca protocol de transport) \u0219i CoAP s-a constatat c\u0103, \u00een general, CoAP a ar\u0103tat un consum de l\u0103\u021bime de band\u0103 relativ mai sc\u0103zut, care nu a crescut odat\u0103 cu cre\u0219terea pierderilor de pachete de re\u021bea sau a \u00eent\u00e2rzierii re\u021belei, spre deosebire de MQTT \u0219i DDS, unde \u00een scenariile men\u021bionate s-a observat o cre\u0219tere a utiliz\u0103rii l\u0103\u021bimii de band\u0103. \u00cen alt scenariu, a fost implicat un num\u0103r mare de dispozitive care transmit date simultan, ceea ce este un caz tipic \u00een medii IoT. Rezultatele au ar\u0103tat c\u0103 pentru o \u00eenc\u0103rcare mai mare, este mai bine s\u0103 se foloseasc\u0103 CoAP.<\/p>\n<p>\u00cen condi\u021bii de \u00eenc\u0103rcare redus\u0103, CoAP a utilizat cea mai mic\u0103 capacitate de band\u0103, urmat de MQTT \u0219i REST HTTP. Cu toate acestea, atunci c\u00e2nd dimensiunea sarcinilor utile a crescut, cele mai bune rezultate au fost ob\u021binute de REST HTTP.<\/p>\n<p><b>Consumul de energie<\/b><\/p>\n<p>Problema consumului de energie este \u00eentotdeauna important\u0103, iar \u00een sistemul IoT - \u00een mod special. Dac\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/ieeexplore.ieee.org\/document\/7899537\">comparam <\/a><\/noindex>consumul de energie \u00eentre MQTT \u0219i HTTP, atunci HTTP \"consum\u0103\" mult mai mult. Iar CoAP este mai <noindex><a rel=\"nofollow\" href=\"https:\/\/www.mdpi.com\/1424-8220\/16\/12\/2044\/htm\">eficient din punct de vedere energetic <\/a><\/noindex>comparativ cu MQTT, permi\u021b\u00e2nd gestionarea aliment\u0103rii. \u00cen acest context, \u00een scenarii simple, MQTT este mai potrivit pentru schimbul de informa\u021bii \u00een re\u021belele Internetului Lucrurilor, mai ales atunci c\u00e2nd nu exist\u0103 constr\u00e2ngeri de putere.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"http:\/\/cgweb1.northumbria.ac.uk\/SubjectAreaResources\/KF7046\/papers\/review\/iot\/lpb15.pdf\">Altele <\/a><\/noindex>experimentul \u00een cadrul c\u0103ruia s-au comparat capacit\u0103\u021bile AMQP \u0219i MQTT pe un stand de testare a unei re\u021bele mobile sau instabile f\u0103r\u0103 fir a ar\u0103tat c\u0103 AMQP ofer\u0103 mai multe posibilit\u0103\u021bi \u00een privin\u021ba securit\u0103\u021bii, \u00een timp ce MQTT este mai eficient din punct de vedere energetic.<\/p>\n<p><b>Securitate<\/b><\/p>\n<p>Securitatea este o alt\u0103 problem\u0103 esen\u021bial\u0103, ridicat\u0103 c\u00e2nd se studiaz\u0103 subiectul Internetului Lucrurilor \u0219i al calculului de tip fog\/cloud. Mecanismul de securitate se bazeaz\u0103 de obicei pe TLS \u00een HTTP, MQTT, AMQP \u0219i XMPP, sau DTLS \u00een CoAP, sus\u021bin\u00e2nd ambele op\u021biuni DDS.<\/p>\n<p>TLS \u0219i DTLS \u00eencep cu un proces de stabilire a conexiunii \u00eentre partea client \u0219i partea server pentru a schimba seturile de criptare \u0219i cheile acceptate. Ambele p\u0103r\u021bi convin asupra seturilor pentru a asigura c\u0103 comunicarea ulterioar\u0103 se desf\u0103\u0219oar\u0103 \u00eentr-un canal sigur. Diferen\u021ba dintre ele const\u0103 \u00een modific\u0103rile minore care permit DTLS, bazat pe UDP, s\u0103 func\u021bioneze \u00eentr-o conexiune nesigur\u0103.<\/p>\n<p>Upon <noindex><a rel=\"nofollow\" href=\"http:\/\/www.isg.rhul.ac.uk\/tls\/lucky13.html\">atacuri de testare<\/a><\/noindex> \u00eempotriva mai multor implement\u0103ri diferite ale TLS \u0219i DTLS a ar\u0103tat c\u0103 TLS a f\u0103cut fa\u021b\u0103 mai bine provoc\u0103rii. Atacurile asupra DTLS au fost mai reu\u0219ite datorit\u0103 toleran\u021bei sale la erori.<\/p>\n<p>Cu toate acestea, cea mai mare problem\u0103 a acestor protocoale este c\u0103 nu au fost concepute ini\u021bial pentru utilizarea \u00een IoT \u0219i nu au anticipat func\u021bionarea \u00een fog sau cloud. Printr-un schimb convenit (handshaking) ele adaug\u0103 trafic suplimentar cu fiecare stabilire a conexiunii, ceea ce epuizeaz\u0103 resursele computa\u021bionale. \u00cen medie, se observ\u0103 o cre\u0219tere de 6,5% pentru TLS \u0219i 11% pentru DTLS \u00een \u00eenc\u0103rc\u0103tura de control comparativ cu comunica\u021bia f\u0103r\u0103 nivel de securitate. \u00cen medii bogate \u00een resurse, care se afl\u0103 de obicei \u00een <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>la nivel, nu va fi o problem\u0103, dar \u00een leg\u0103tura dintre IoT \u0219i nivelul de cea\u021b\u0103, aceasta devine o limitare important\u0103.<\/p>\n<p>Ce s\u0103 alegem? Nu exist\u0103 un r\u0103spuns clar. MQTT \u0219i HTTP par a fi cele mai promi\u021b\u0103toare protocoale, deoarece sunt considerate solu\u021bii relativ mature \u0219i mai stabile pentru IoT \u00een compara\u021bie cu alte protocoale.<\/p>\n<h3>Solu\u021bii bazate pe un singur protocol de comunica\u021bie<\/h3>\n<p>\nPracticile solu\u021biilor cu un singur protocol au multe dezavantaje. De exemplu, un protocol care se dovede\u0219te eficient \u00eentr-un mediu restric\u021bionat poate s\u0103 nu func\u021bioneze \u00eentr-un domeniu cu cerin\u021be stricte de securitate. Av\u00e2nd \u00een vedere acest lucru, trebuie s\u0103 elimin\u0103m aproape toate solu\u021biile posibile bazate pe un singur protocol \u00een ecosistemul Fog-to-Cloud \u00een IoT, cu excep\u021bia MQTT \u0219i REST HTTP.<\/p>\n<p><b>REST HTTP ca solu\u021bie cu un singur protocol<\/b><\/p>\n<p>Exist\u0103 un exemplu bun de interac\u021biune \u00eentre cereri \u0219i r\u0103spunsuri REST HTTP \u00een domeniul IoT-to-Fog: <noindex><a rel=\"nofollow\" href=\"https:\/\/dl.acm.org\/citation.cfm?doid=3152130.3152140\">ferma inteligent\u0103<\/a><\/noindex>. Animalele sunt echipate cu senzori purtabili (client IoT, C) \u0219i sunt gestionate de c\u0103tre un sistem de ferm\u0103 inteligent\u0103 prin cloud computing (server Fog, S).<\/p>\n<p>\u00cen antetul metodei POST se specific\u0103 resursa de modificat (\\\/farm\\\/animals), precum \u0219i versiunea HTTP \u0219i tipul de con\u021binut, care \u00een acest caz este un obiect JSON reprezent\u00e2nd ferma de animale pe care sistemul ar trebui s\u0103 o gestioneze (Dulcineea\\\/vac\u0103). R\u0103spunsul de la server indic\u0103 faptul c\u0103 cererea a fost succes, trimi\u021b\u00e2nd codul de stare HTTPS 201 (resource created). Metoda GET ar trebui s\u0103 indice doar resursa solicitat\u0103 \u00een URI (de exemplu, \\\/farm\\\/animals\\\/1), care returneaz\u0103 o reprezentare JSON a animalului cu acest identificator de pe server. <\/p>\n<p>Metoda PUT este utilizat\u0103 atunci c\u00e2nd este necesar s\u0103 se actualizeze o anumit\u0103 \u00eenregistrare a resursei. \u00cen acest caz, resursa indic\u0103 URI-ul pentru parametrul care urmeaz\u0103 s\u0103 fie modificat \u0219i valoarea curent\u0103 (de exemplu, indic\u00e2nd c\u0103 vaca este \u00een prezent la p\u0103scut, \\\/farm\\\/animals\\\/1?stare=plimbare). \u00cen cele din urm\u0103, metoda DELETE este utilizat\u0103 \u00een mod similar cu metoda GET, dar pur \u0219i simplu \u0219terge resursa ca rezultat al opera\u021biei. <\/p>\n<p><b>MQTT ca solu\u021bie cu un singur protocol<\/b><\/p>\n<p><img decoding=\"async\" alt=\"IoT, cea\u021b\u0103 \u0219i nori: s\u0103 vorbim despre tehnologii?\" src=\"\/wp-content\/uploads\/2019\/09\/529857b556ea5a186ac1519e2804d1b8.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nS\u0103 lu\u0103m aceea\u0219i ferm\u0103 inteligent\u0103, dar \u00een loc de REST HTTP, vom folosi protocolul MQTT. Un server local cu biblioteca Mosquitto instalat\u0103 ac\u021bioneaz\u0103 ca broker. \u00cen acest exemplu, un computer simplu (denumit serverul fermei) Raspberry Pi serve\u0219te ca client MQTT, implementat prin instalarea bibliotecii MQTT Paho, complet compatibil\u0103 cu brokerul Mosquitto.<\/p>\n<p>Acest client corespunde nivelului de abstractizare IoT, reprezent\u00e2nd un dispozitiv cu capacit\u0103\u021bi de detectare \u0219i calcul. Pe de alt\u0103 parte, mediatorul corespunde unui nivel mai \u00eenalt de abstractizare, reprezent\u00e2nd un nod de calcul la margine, caracterizat prin resurse mai mari \u00een ceea ce prive\u0219te procesarea \u0219i stocarea datelor.<\/p>\n<p>\u00cen scenariul propus al \u201eferm\u0103 inteligente\u201d, Raspberry Pi se conecteaz\u0103 la un accelerometru, GPS \u0219i senzori de temperatur\u0103, public\u00e2nd date de la ace\u0219ti senzori \u00eentr-un nod de margine. A\u0219a cum \u0219ti\u021bi, MQTT consider\u0103 subiectele ca o ierarhie. Un editor MQTT poate publica mesaje \u00eentr-un anumit set de subiecte. \u00cen cazul nostru, sunt trei. Pentru senzorul care m\u0103soar\u0103 temperatura din ad\u0103postul animalelor, clientul alege subiectul (animalfarm\/shed\/temperature). Pentru senzorii care m\u0103soar\u0103 loca\u021bia GPS \u0219i mi\u0219carea animalelor prin accelerometru, clientul public\u0103 actualiz\u0103ri (animalfarm\/animal\/GPS) \u0219i (animalfarm\/animal\/movement).<\/p>\n<p>Aceast\u0103 informa\u021bie va fi transmis\u0103 brokerului, care poate s\u0103 o stocheze temporar \u00eentr-o baz\u0103 de date local\u0103 \u00een cazul \u00een care mai t\u00e2rziu apare un alt abonat interesat.<\/p>\n<p>Pe l\u00e2ng\u0103 serverul local care ac\u021bioneaz\u0103 ca broker MQTT la margine \u0219i c\u0103ruia Raspberry Pi, ac\u021bion\u00e2nd ca clien\u021bi MQTT, \u00eei trimite datele de la senzori, la nivelul cloud poate exista un alt broker MQTT. \u00cen acest caz, informa\u021biile transmise brokerului local pot fi stocate temporar \u00eentr-o baz\u0103 de date local\u0103 \u0219i\/sau trimise \u00een cloud. Brokerul MQTT de margine \u00een aceast\u0103 situa\u021bie este utilizat pentru a lega toate datele cu brokerul MQTT din cloud. Cu o astfel de arhitectur\u0103, utilizatorul aplica\u021biei mobile poate fi abonat la ambele brokere.<\/p>\n<p>\u00cen cazul \u00een care conexiunea cu unul dintre brokeri (de exemplu, cloud) e\u0219ueaz\u0103, utilizatorul final va primi informa\u021bii de la un alt broker (de tip fog). Aceasta este o caracteristic\u0103 tipic\u0103 a sistemelor combinate de fog \u0219i cloud computing. Implicit, aplica\u021bia mobil\u0103 poate fi configurat\u0103 s\u0103 se conecteze mai \u00eent\u00e2i la un broker MQTT de tip fog, \u0219i, \u00een cazul unui e\u0219ec, s\u0103 se conecteze la brokerul MQTT din cloud. Aceasta este doar una dintre numeroasele solu\u021bii \u00een sistemele IoT-F2C. <\/p>\n<h3>Solu\u021bii multi-protocol<\/h3>\n<p>\nSolu\u021biile cu un singur protocol sunt populare datorit\u0103 implement\u0103rii lor mai simple. Dar este evident c\u0103 \u00een sistemele IoT-F2C are sens s\u0103 combin\u0103m diferite protocoale. Ideea este c\u0103 la diferite niveluri pot func\u021biona protocoale diferite. S\u0103 lu\u0103m, de exemplu, trei abstrac\u021bii: nivelurile IoT, fog \u0219i cloud computing. Dispozitivele de la nivelul IoT sunt de obicei considerate limitate. \u00cen aceast\u0103 revizuire, s\u0103 consider\u0103m nivelurile IoT ca fiind cele mai limitate, cele de cloud cele mai pu\u021bin limitate \u0219i calculele de fog ca fiind \u201eundeva la mijloc\u201d. Astfel, \u00eentre IoT \u0219i abstrac\u021biile de fog, solu\u021biile protocolare actuale includ MQTT, CoAP \u0219i XMPP. \u00centre fog \u0219i cloud, pe de alt\u0103 parte, AMQP este unul dintre protocoalele principale utilizate \u00eempreun\u0103 cu REST HTTP, care, datorit\u0103 flexibilit\u0103\u021bii sale, este de asemenea utilizat \u00eentre IoT \u0219i straturile de fog. <\/p>\n<p>Principala problem\u0103 aici const\u0103 \u00een compatibilitatea func\u021bional\u0103 a protocolilor \u0219i \u00een u\u0219urin\u021ba conversiei mesajelor dintr-un protocol \u00een altul. \u00cen mod ideal, \u00een viitor, arhitectura sistemului de internet al lucrurilor cu resurse cloud \u0219i fog va fi independent\u0103 de protocolul de comunicare utilizat \u0219i va asigura o bun\u0103 interac\u021biune \u00eentre diferitele protocoale.<\/p>\n<p><img decoding=\"async\" alt=\"IoT, cea\u021b\u0103 \u0219i nori: s\u0103 vorbim despre tehnologii?\" src=\"\/wp-content\/uploads\/2019\/09\/cddc564cad572966002ae22eff8cb99d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nDeoarece, \u00een prezent, acest lucru nu se \u00eent\u00e2mpl\u0103, are sens s\u0103 combin\u0103m protocoalele care nu au diferen\u021be semnificative. \u00cen acest sens, o solu\u021bie poten\u021bial\u0103 se bazeaz\u0103 pe combinarea a dou\u0103 protocoale care respect\u0103 acela\u0219i stil arhitectural, REST HTTP \u0219i CoAP. O alt\u0103 solu\u021bie propus\u0103 se bazeaz\u0103 pe combinarea a dou\u0103 protocoale care ofer\u0103 interac\u021biune prin modelul \u201epublicare-abonare\u201d, MQTT \u0219i AMQP. Utilizarea conceptelor apropiate (\u0219i MQTT, \u0219i AMQP folosesc brokeri, CoAP \u0219i HTTP folosesc REST), simplific\u0103 implementarea acestor combina\u021bii \u0219i necesit\u0103 mai pu\u021bin efort pentru integrare.<\/p>\n<p><img decoding=\"async\" alt=\"IoT, cea\u021b\u0103 \u0219i nori: s\u0103 vorbim despre tehnologii?\" src=\"\/wp-content\/uploads\/2019\/09\/395bc75880a154aeab7b61d043476802.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u00cen figura (a) sunt reprezentate dou\u0103 modele bazate pe cereri-r\u0103spunsuri, HTTP \u0219i CoAP, \u0219i posibilitatea lor de integrare \u00een solu\u021bia IoT-F2C. Deoarece HTTP este unul dintre cele mai cunoscute \u0219i adaptabile protocoale din re\u021belele moderne, este pu\u021bin probabil s\u0103 fie complet \u00eenlocuit de alte protocoale de mesagerie. Dintre nodurile care reprezint\u0103 dispozitive puternice, ce se afl\u0103 \u00eentre cloud \u0219i fog, REST HTTP reprezint\u0103 o solu\u021bie rezonabil\u0103.<\/p>\n<p>Pe de alt\u0103 parte, pentru dispozitive cu resurse computa\u021bionale limitate, care se conecteaz\u0103 \u00eentre nivelurile de fog \u0219i IoT, este mai eficient s\u0103 se utilizeze CoAP. Unul dintre principalele avantaje ale CoAP este, de fapt, compatibilitatea sa cu HTTP, deoarece ambele protocoale se bazeaz\u0103 pe principiile REST.<\/p>\n<p>\u00cen figura (b) sunt prezentate dou\u0103 modele de interac\u021biune \u201epublicare-abonare\u201d \u00eentr-un scenariu, incluz\u00e2nd MQTT \u0219i AMQP. De\u0219i, pe h\u00e2rtie, ambele protocoale ar putea fi utilizate pentru comunicarea \u00eentre noduri la fiecare nivel de abstractizare, amplasarea lor ar trebui s\u0103 fie determinat\u0103 pe baza performan\u021bei. MQTT a fost dezvoltat ca un protocol simplificat pentru dispozitive cu resurse computa\u021bionale limitate, astfel c\u0103 poate fi folosit pentru comunicarea \u00eentre IoT \u0219i fog. AMQP este mai bine adaptat pentru dispozitive mai puternice, care ar plasa perfect \u00eentre nodurile de fog \u0219i cloud. \u00cen loc de MQTT, \u00een IoT poate fi utilizat protocolul XMPP, deoarece acesta este considerat u\u0219or. Totu\u0219i, acesta nu este la fel de utilizat \u00een astfel de scenarii.<\/p>\n<h3>Conclusions<\/h3>\n<p>\nEste pu\u021bin probabil ca unul dintre protocoalele discutate s\u0103 fie suficient pentru a acoperi toat\u0103 comunicarea din sistem, \u00eencep\u00e2nd cu dispozitivele cu resurse computa\u021bionale limitate \u0219i termin\u00e2nd cu serverele cloud. Studiul a ar\u0103tat c\u0103 cele dou\u0103 op\u021biuni cele mai promi\u021b\u0103toare, utilizate frecvent de dezvoltatori, sunt MQTT \u0219i RESTful HTTP. Aceste dou\u0103 protocoale sunt nu doar cele mai mature \u0219i stabile, ci includ, de asemenea, numeroase implement\u0103ri bine documentate \u0219i resurse online de succes.<\/p>\n<p>Datorit\u0103 stabilit\u0103\u021bii \u0219i configura\u021biei sale simple, MQTT este un protocol care, \u00een timp, \u0219i-a dovedit performan\u021ba superioar\u0103 la nivelul IoT cu dispozitivele limitate. \u00cen p\u0103r\u021bile sistemului unde comunica\u021bia limitat\u0103 \u0219i consumul de energie nu sunt o problem\u0103, cum ar fi \u00een unele domenii de fog \u0219i majoritatea calculilor \u00een cloud, RESTful HTTP este o alegere simpl\u0103. CoAP ar trebui, de asemenea, luat \u00een considerare, deoarece se dezvolt\u0103 rapid ca standard de comunicare IoT, iar este foarte posibil ca \u00een viitorul apropiat s\u0103 ating\u0103 un nivel de stabilitate \u0219i maturitate similar cu MQTT \u0219i HTTP. \u00cens\u0103 standardul este \u00een prezent \u00een dezvoltare, ceea ce aduce probleme de compatibilitate pe termen scurt.<\/p>\n<p><b>Ce altceva util se poate citi \u00een 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\/\">Computerul \u00ee\u021bi va face pl\u0103cere<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/464155\/\">AI ajut\u0103 la studierea animalelor din Africa <\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/cloud4y\/blog\/465251\/\">Vara s-a terminat aproape. Datele ne\u00eent\u0103rite aproape c\u0103 nu au mai r\u0103mas<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/461713\/\">4 modalit\u0103\u021bi de a economisi pe backup-urile din cloud<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/cloud4y\/blog\/467769\/\">Despre un singur resurs\u0103 informa\u021bional\u0103 federal\u0103 care con\u021bine date despre popula\u021bie<\/a><\/noindex><\/p>\n<p>Abona\u021bi-v\u0103 la canalul nostru <noindex><a rel=\"nofollow\" href=\"https:\/\/t.me\/cloud4y\">Telegram<\/a><\/noindex>-canal pentru a nu rata urm\u0103torul articol! Scriem nu mai des de dou\u0103 ori pe s\u0103pt\u0103m\u00e2n\u0103 \u0219i doar lucruri importante.<br \/>\n<br \/>Sursa: <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-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.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\/ro\/blog\/news\/iot-tuman-i-oblaka-pogovorim-pro-tehnologii\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\/ro\/blog\/news\/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, fog \u0219i cloud: s\u0103 discut\u0103m despre tehnologii? | ProHoster","description":"Dezvoltarea tehnologiilor \u00een domeniul software-ului \u0219i.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/news\/iot-tuman-i-oblaka-pogovorim-pro-tehnologii","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/blog\/news\/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\/ro\/wp-json\/wp\/v2\/posts\/38375","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=38375"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/38375\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/28806"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=38375"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=38375"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=38375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}