Ci gaban fasaha a fagen software da hardware, bullar sabbin ka'idojin sadarwa sun haifar da fadada Intanet na Abubuwa (IoT). Yawan na'urori na karuwa kowace rana kuma suna samar da adadi mai yawa. Don haka, akwai buƙatar ingantaccen tsarin gine-ginen da zai iya sarrafawa, adanawa da watsa wannan bayanai.
Yanzu ana amfani da sabis na girgije don waɗannan dalilai. Koyaya, sanannen ƙirar ƙira mai hazo (Fog) na iya haɓaka mafita ga girgije ta hanyar haɓakawa da haɓaka kayan aikin IoT.
Gajimare suna da ikon rufe yawancin buƙatun IoT. Misali, don samar da sa ido kan ayyuka, da sauri sarrafa kowane adadin bayanai da na'urori ke samarwa, da kuma ganinsu. Ƙididdigar fog yana da tasiri yayin magance matsalolin lokaci-lokaci. Suna ba da amsa da sauri ga buƙatun da ƙarancin jinkiri a sarrafa bayanai. Wato, Fog ya cika "girgije" kuma yana faɗaɗa iyawarsa.
Koyaya, babbar tambayar ta bambanta: ta yaya duk waɗannan zasu yi hulɗa a cikin mahallin IoT? Wadanne ka'idojin sadarwa za su fi tasiri yayin aiki a cikin tsarin haɗin IoT-Fog-Cloud?
Duk da kasancewar ikon HTTP, akwai adadi mai yawa na sauran hanyoyin da ake amfani da su a cikin tsarin IoT, Fog da Cloud. Wannan saboda dole ne IoT ya haɗa ayyukan firikwensin na'urori iri-iri tare da tsaro, dacewa, da sauran buƙatun masu amfani.
Amma babu kawai ra'ayi ɗaya game da gine-ginen tunani da ma'aunin sadarwa. Don haka, ƙirƙira sabuwar yarjejeniya ko gyaggyara wacce ke akwai don takamaiman ayyuka na IoT ɗaya ne daga cikin mahimman ayyuka da ke fuskantar al'ummar IT.
Wadanne ka'idoji ne ake amfani da su a halin yanzu kuma menene zasu iya bayarwa? Bari mu gane shi. Amma da farko, bari mu tattauna ƙa’idodin yanayin yanayin da girgije, hazo da Intanet na abubuwa ke hulɗa.
IoT Fog-to-Cloud (F2C) Gine-gine
Wataƙila kun lura da ƙoƙarin da ake yi don bincika fa'idodi da fa'idodin da ke tattare da wayo da haɗin kai na IoT, girgije da hazo. Idan ba haka ba, to, ga matakan daidaitawa guda uku: , и .
Idan a baya an yi la'akari da matakan 2 kawai, gajimare da na'urori masu ƙarewa, to, tsarin gine-ginen da aka tsara ya gabatar da sabon matakin - ƙididdiga na hazo. A wannan yanayin, za a iya raba matakin hazo zuwa nau'i-nau'i da yawa, dangane da ƙayyadaddun kayan aiki ko tsarin manufofin da ke ƙayyade amfani da na'urori daban-daban a cikin waɗannan sublevels.
Menene wannan abstraction zai yi kama? Anan akwai yanayin yanayin yanayin IoT-Fog-Cloud. Na'urorin IoT suna aika bayanai zuwa sabar masu sauri da na'urorin kwamfuta don magance matsalolin da ke buƙatar rashin jinkiri. A cikin wannan tsarin, girgije ne ke da alhakin warware matsalolin da ke buƙatar babban adadin albarkatun kwamfuta ko sararin ajiyar bayanai.
Wayoyin hannu, agogo masu wayo da sauran na'urori kuma na iya zama wani ɓangare na IoT. Amma irin waɗannan na'urori, a matsayin mai mulkin, suna amfani da ka'idojin sadarwa na mallakar mallaka daga manyan masu haɓakawa. Ana canza bayanan IoT da aka samar zuwa layin hazo ta hanyar ka'idar HTTP ta REST, wacce ke ba da sassauci da ma'amala yayin ƙirƙirar sabis na RESTful. Wannan yana da mahimmanci bisa la'akari da buƙatar tabbatar da dacewa ta baya tare da kayan aikin kwamfuta da ke gudana akan kwamfutoci na gida, sabar ko tarin uwar garke. Albarkatun gida, da ake kira "nodes na hazo," tace bayanan da aka karɓa kuma a sarrafa su a gida ko aika zuwa gajimare don ƙarin ƙididdiga.
Gajimare suna goyan bayan ka'idojin sadarwa daban-daban, mafi yawanci shine AMQP da REST HTTP. Tun da HTTP sananne ne kuma an keɓance shi don Intanet, tambayar na iya tasowa: "Shin ba za mu yi amfani da shi don yin aiki da IoT da hazo ba?" Koyaya, wannan ka'ida tana da matsalolin aiki. Karin bayani kan wannan daga baya.
Gabaɗaya, akwai nau'ikan ka'idojin sadarwa guda 2 waɗanda suka dace da tsarin da muke buƙata. Waɗannan su ne amsa-buƙatu da buga-biyan kuɗi. Samfurin farko an fi saninsa sosai, musamman a gine-ginen uwar garken abokin ciniki. Abokin ciniki yana buƙatar bayani daga uwar garken, kuma uwar garken yana karɓar buƙatar, sarrafa shi kuma ya mayar da saƙon amsawa. Ka'idojin REST HTTP da CoAP suna aiki akan wannan ƙirar.
Samfurin na biyu ya taso ne daga buƙatar samar da asynchronous, rarraba, sako-sako da haɗin kai tsakanin hanyoyin samar da bayanai da masu karɓar wannan bayanan.
Samfurin yana ɗaukar mahalarta uku: mai wallafa (tushen bayanai), dillali (mai aikawa) da mai biyan kuɗi (mai karɓa). Anan, abokin ciniki yana aiki azaman mai biyan kuɗi ba dole ba ne ya nemi bayani daga uwar garken. Maimakon aika buƙatun, yana biyan kuɗi zuwa wasu abubuwan da ke faruwa a cikin tsarin ta hanyar dillali, wanda ke da alhakin tace duk saƙonnin da ke shigowa da kuma tura su tsakanin masu wallafa da masu biyan kuɗi. Kuma mawallafin, idan wani lamari ya faru game da wani batu, ya buga shi ga dillali, wanda ke aika bayanai game da abin da ake bukata ga mai biyan kuɗi.
Ainihin, wannan gine-ginen ya dogara ne akan aukuwa. Kuma wannan ƙirar hulɗar yana da ban sha'awa ga aikace-aikace a cikin IoT, girgije, hazo saboda ikonsa na samar da scalability da sauƙaƙe haɗin kai tsakanin na'urori daban-daban, tallafawa sadarwa mai ƙarfi-zuwa-da yawa da sadarwar asynchronous. Wasu sanannun ƙa'idodin saƙon saƙon da ke amfani da ƙirar buga-biyan kuɗi sun haɗa da MQTT, AMQP, da DDS.
Babu shakka, samfurin buga-biyan kuɗi yana da fa'idodi da yawa:
- Masu bugawa da masu biyan kuɗi ba sa buƙatar sanin kasancewar juna;
- Mai biyan kuɗi ɗaya zai iya karɓar bayanai daga wallafe-wallafe daban-daban, kuma mawallafin ɗaya zai iya aika bayanai ga masu biyan kuɗi daban-daban (ka'idodin da yawa-zuwa-yawa);
- Mai bugawa da mai biyan kuɗi ba dole ba ne su kasance masu aiki a lokaci guda don sadarwa, saboda dillali (aiki a matsayin tsarin layi) zai iya adana saƙon ga abokan ciniki waɗanda ba a haɗa su da hanyar sadarwa a halin yanzu ba.
Koyaya, samfurin amsa buƙatar kuma yana da ƙarfinsa. A lokuta inda ikon gefen uwar garken don ɗaukar buƙatun abokin ciniki da yawa ba batun bane, yana da ma'ana a yi amfani da ingantattun mafita, amintattu.
Hakanan akwai ka'idoji waɗanda ke goyan bayan samfuran biyu. Misali, XMPP da HTTP 2.0, waɗanda ke goyan bayan zaɓin “tuɓawar uwar garken”. IETF kuma ta fitar da CoAP. A yunƙurin warware matsalar saƙon, an ƙirƙiri wasu mafita da yawa, kamar ƙa'idar WebSockets ko amfani da ka'idar HTTP akan QUIC (Haɗin Intanet na gaggawa na UDP).
A cikin yanayin WebSockets, ko da yake ana amfani da shi don canja wurin bayanai a cikin ainihin lokaci daga uwar garken zuwa abokin ciniki na yanar gizo kuma yana ba da haɗin kai tare da sadarwar bidirectional lokaci guda, ba a yi nufin na'urori masu iyakacin albarkatun kwamfuta ba. QUIC kuma ya cancanci kulawa, tunda sabuwar ka'idar sufuri tana ba da sabbin damammaki da yawa. Amma tun da har yanzu ba a daidaita QUIC ba, bai daɗe ba don hasashen yiwuwar aikace-aikacensa da tasirinsa akan hanyoyin IoT. Don haka muna kiyaye WebSockets da QUIC a hankali tare da ido ga nan gaba, amma ba za mu yi nazarinsa dalla-dalla ba a yanzu.
Wanene ya fi kowa kyau a duniya: kwatanta ladabi
Yanzu bari muyi magana game da ƙarfi da raunin ladabi. Idan muka dubi gaba, bari mu yi ajiyar wuri cewa babu wani shugaba mai haske. Kowace yarjejeniya tana da wasu fa'idodi / rashin amfani.
Lokacin amsawa
Ɗaya daga cikin mahimman halayen ƙa'idodin sadarwa, musamman dangane da Intanet na Abubuwa, shine lokacin amsawa. Amma a cikin ƙa'idodin da ke akwai, babu wani bayyanannen nasara wanda ke nuna ƙaramin matakin latency yayin aiki a ƙarƙashin yanayi daban-daban. Amma akwai cikakken gungun bincike da kwatancen iyawar yarjejeniya.
Alal misali, kwatancen tasirin HTTP da MQTT lokacin aiki tare da IoT ya nuna cewa lokacin amsa buƙatun MQTT bai kai na HTTP ba. Kuma yaushe Lokacin tafiye-tafiye (RTT) na MQTT da CoAP sun bayyana cewa matsakaicin RTT na CoAP shine 20% ƙasa da na MQTT.
Sauran tare da RTT don MQTT da ka'idojin CoAP an aiwatar da su a cikin yanayi guda biyu: cibiyar sadarwar gida da cibiyar sadarwa ta IoT. Ya juya cewa matsakaicin RTT shine sau 2-3 mafi girma a cikin hanyar sadarwar IoT. MQTT tare da QoS0 ya nuna ƙananan sakamako idan aka kwatanta da CoAP, kuma MQTT tare da QoS1 ya nuna RTT mafi girma saboda ACKs a aikace-aikace da kuma jigilar kayayyaki. Don matakan QoS daban-daban, jinkirin hanyar sadarwa ba tare da cunkoso ba shine millise seconds don MQTT, da ɗaruruwan microseconds don CoAP. Duk da haka, yana da daraja tunawa cewa lokacin aiki akan cibiyoyin sadarwa marasa aminci, MQTT da ke gudana a saman TCP zai nuna sakamako daban-daban.
lokacin mayar da martani ga ka'idojin AMQP da MQTT ta hanyar ƙara yawan kuɗin da aka biya ya nuna cewa tare da nauyin nauyi matakin latency kusan iri ɗaya ne. Amma lokacin canja wurin bayanai masu yawa, MQTT yana nuna gajeren lokacin amsawa. a cikin daya kuma An kwatanta CoAP da HTTP a yanayin sadarwa na inji-zuwa-na'ura tare da na'urorin da aka sanya a saman motocin sanye take da na'urori masu auna iskar gas, na'urori masu auna yanayi, na'urori masu auna wuri (GPS) da cibiyar sadarwar wayar hannu (GPRS). Lokacin da ake buƙata don isar da saƙon CoAP akan hanyar sadarwar wayar hannu ya kusan sau uku ya fi guntu lokacin da ake buƙata don amfani da saƙon HTTP.
An gudanar da bincike wanda idan aka kwatanta ba biyu ba, amma ka'idoji guda uku. Misali, aikin IoT ka'idojin MQTT, DDS da CoAP a cikin yanayin aikace-aikacen likita ta amfani da kwayi na hanyar sadarwa. DDS ya zarce MQTT dangane da gwajin latency na telemetry a ƙarƙashin yanayi mara kyau iri-iri. CoAP na tushen UDP yayi aiki da kyau don aikace-aikacen da ke buƙatar lokutan amsawa da sauri, duk da haka, saboda kasancewarsa na tushen UDP, an sami asarar fakitin da ba za a iya faɗi ba.
Bandwidth
MQTT da CoAP dangane da ingancin bandwidth an aiwatar da su azaman ƙididdige adadin adadin bayanan da aka watsa ta kowane saƙo. CoAP ya nuna ƙananan kayan aiki fiye da MQTT lokacin aika ƙananan saƙonni. Amma lokacin da aka kwatanta ingancin ka'idoji dangane da rabon adadin bytes masu amfani zuwa jimillar adadin bytes da aka canjawa wuri, CoAP ya zama mafi inganci.
a ta yin amfani da MQTT, DDS (tare da TCP a matsayin ka'idar sufuri) da kuma bandwidth na CoAP, an gano cewa CoAP gabaɗaya ya nuna ƙarancin amfani da bandwidth, wanda bai karu ba tare da karuwar fakitin fakitin cibiyar sadarwa ko haɓakar latency na cibiyar sadarwa, sabanin MQTT da DDS, inda akwai. karuwa a cikin amfani da bandwidth a cikin abubuwan da aka ambata. Wani yanayin ya haɗa da ɗimbin na'urori masu watsa bayanai lokaci guda, wanda ke da alaƙa a cikin mahallin IoT. Sakamakon ya nuna cewa don amfani mai girma yana da kyau a yi amfani da CoAP.
Ƙarƙashin nauyi mai sauƙi, CoAP yayi amfani da mafi ƙarancin bandwidth, sannan MQTT da REST HTTP suka biyo baya. Koyaya, lokacin da girman abubuwan biyan kuɗi ya ƙaru, REST HTTP yana da sakamako mafi kyau.
Yawan amfani
Batun amfani da makamashi koyaushe yana da mahimmanci, musamman a cikin tsarin IoT. Idan Yayin da MQTT da HTTP ke cinye wutar lantarki, HTTP yana cinyewa da yawa. Kuma CoAP yana da ƙari idan aka kwatanta da MQTT, ba da damar sarrafa wutar lantarki. Koyaya, a cikin yanayi masu sauƙi, MQTT ya fi dacewa don musayar bayanai a cikin hanyoyin sadarwar Intanet na Abubuwa, musamman idan babu ƙuntatawar wuta.
Gwajin da aka kwatanta da damar AMQP da MQTT akan wayar hannu ko maras ƙarfi gwajin cibiyar sadarwa ta gano cewa AMQP yana ba da ƙarin damar tsaro yayin da MQTT ya fi ƙarfin kuzari.
Tsaro
Tsaro wani lamari ne mai mahimmanci da aka taso lokacin nazarin batun Intanet na Abubuwa da hazo/girgije. Tsarin tsaro yawanci ya dogara ne akan TLS a cikin HTTP, MQTT, AMQP da XMPP, ko DTLS a cikin CoAP, kuma yana goyan bayan bambance-bambancen DDS duka.
TLS da DTLS suna farawa da tsarin samar da sadarwa tsakanin abokin ciniki da ɓangarorin uwar garken don musayar goyan bayan suites da maɓallai. Bangarorin biyu sun yi shawarwari kan saiti don tabbatar da cewa ƙarin sadarwa ta faru akan amintacciyar tashoshi. Bambanci tsakanin su biyu ya ta'allaka ne a cikin ƙananan gyare-gyare waɗanda ke ba da damar DTLS na tushen UDP suyi aiki akan haɗin da ba a dogara ba.
a Yawancin aiwatarwa daban-daban na TLS da DTLS sun gano cewa TLS ya yi aiki mafi kyau. Hare-hare kan DTLS sun fi samun nasara saboda jurewar kuskuren sa.
Koyaya, babbar matsalar waɗannan ƙa'idodin ita ce ba a tsara su ta asali don amfani a cikin IoT ba kuma ba a yi nufin yin aiki a cikin hazo ko gajimare ba. Ta hanyar mu'amala da hannu, suna ƙara ƙarin zirga-zirga tare da kowace kafa haɗin gwiwa, wanda ke kwashe albarkatun kwamfuta. A matsakaita, ana samun karuwar 6,5% na TLS da 11% na DTLS a sama idan aka kwatanta da sadarwa ba tare da tsaro ba. A cikin mahalli masu wadatar albarkatu, waɗanda galibi ke kan su matakin, wannan ba zai zama matsala ba, amma a cikin haɗin kai tsakanin IoT da matakin hazo, wannan ya zama iyakance mai mahimmanci.
Me za a zaba? Babu cikakkiyar amsa. MQTT da HTTP da alama sune mafi kyawun ka'idoji yayin da ake ɗaukar su kwatankwacin mafi girma da kwanciyar hankali na IoT mafita idan aka kwatanta da sauran ka'idoji.
Hanyoyin warwarewa bisa ƙa'idar sadarwar haɗin kai
Ayyukan mafita na yarjejeniya guda ɗaya yana da illoli da yawa. Misali, ƙa'idar da ta dace da ƙayyadaddun yanayi maiyuwa ba zata yi aiki a yankin da ke da ƙaƙƙarfan buƙatun tsaro ba. Tare da wannan a zuciya, an bar mu don watsar da kusan dukkanin hanyoyin magance yarjejeniya guda ɗaya a cikin yanayin yanayin Fog-to-Cloud a cikin IoT, ban da MQTT da REST HTTP.
REST HTTP azaman hanyar yarjejeniya guda ɗaya
Akwai kyakkyawan misali na yadda buƙatun HTTP na REST da martani suke hulɗa a cikin sararin IoT-to-Fog: . Dabbobin suna sanye da na'urori masu auna firikwensin sawa (abokin ciniki na IoT, C) kuma ana sarrafa su ta hanyar lissafin gajimare ta tsarin aikin gona mai wayo (Sabar Fog, S).
Shugaban hanyar POST yana ƙayyadad da albarkatun don gyara (/ gona / dabbobi) da kuma nau'in HTTP da nau'in abun ciki, wanda a cikin wannan yanayin wani abu ne na JSON wanda ke wakiltar gonar dabbar da tsarin zai sarrafa (Dulcinea / saniya) . Amsa daga uwar garken yana nuna cewa buƙatar ta yi nasara ta hanyar aika lambar matsayi na HTTPS 201 (an ƙirƙira albarkatun). Hanyar GET dole ne ta ƙayyade albarkatun da ake buƙata kawai a cikin URI (misali, / farm/animals/1), wanda ke dawo da wakilcin JSON na dabba tare da wannan ID daga uwar garken.
Ana amfani da hanyar PUT lokacin da ake buƙatar sabunta wasu takamaiman rikodin bayanai. A wannan yanayin, albarkatun suna ƙayyade URI don canza ma'auni da darajar yanzu (misali, yana nuna cewa saniya tana tafiya a halin yanzu, / gona / dabbobi / 1? jiha = tafiya). A ƙarshe, ana amfani da hanyar DELETE daidai da hanyar GET, amma kawai tana share albarkatun sakamakon aikin.
MQTT azaman mafita guda ɗaya
Bari mu ɗauki gona mai wayo iri ɗaya, amma maimakon REST HTTP muna amfani da ka'idar MQTT. Sabar gida mai shigar da ɗakin karatu na Mosquitto yana aiki azaman dillali. A cikin wannan misali, kwamfuta mai sauƙi (wanda ake magana da ita azaman uwar garken gona) Raspberry Pi tana aiki azaman abokin ciniki na MQTT, wanda aka aiwatar ta hanyar shigar da ɗakin karatu na Paho MQTT, wanda ya dace da dillalan sauro.
Wannan abokin ciniki ya yi daidai da Layer Abstraction IoT wanda ke wakiltar na'ura mai iya fahimta da ƙididdigewa. Mai shiga tsakani, a gefe guda, yayi daidai da matakin mafi girma na abstraction, yana wakiltar kumburin ƙididdiga na hazo wanda ke da girman sarrafawa da ƙarfin ajiya.
A cikin yanayin gona mai wayo da aka tsara, Rasberi Pi yana haɗi zuwa na'urar accelerometer, GPS, da na'urori masu auna zafin jiki kuma yana buga bayanai daga waɗannan firikwensin zuwa kumburin hazo. Kamar yadda wataƙila kuka sani, MQTT tana ɗaukar batutuwa azaman matsayi. Mawallafin MQTT guda ɗaya na iya buga saƙonni zuwa takamaiman saƙon batutuwa. A wajenmu akwai uku daga cikinsu. Don na'urar firikwensin da ke auna zafin jiki a cikin rumbun dabba, abokin ciniki ya zaɓi jigo (animmal farm/shed/zazzabi). Don na'urori masu auna firikwensin da ke auna wurin GPS da motsin dabba ta hanyar accelerometer, abokin ciniki zai buga sabuntawa zuwa ( Animalfarm/ Animal/GPS) da ( Animalfarm/ Animal/movement).
Za a mika wannan bayanin ga dillali, wanda zai iya adana shi na ɗan lokaci a cikin bayanan gida idan wani mai biyan kuɗi mai sha'awar ya zo daga baya.
Baya ga uwar garken gida, wanda ke aiki a matsayin dillali na MQTT a cikin hazo kuma wanda Raspberry Pis, yana aiki azaman abokan ciniki na MQTT, aika bayanan firikwensin, ana iya samun wani dillali na MQTT a matakin girgije. A wannan yanayin, ana iya adana bayanan da aka aika zuwa dillalin gida na ɗan lokaci a cikin bayanan gida da/ko aika zuwa gajimare. Ana amfani da dillali na MQTT hazo a cikin wannan yanayin don haɗa duk bayanan tare da dillalin MQTT na girgije. Tare da wannan gine-gine, mai amfani da aikace-aikacen hannu za a iya yin rajista ga dillalai biyu.
Idan haɗin da ɗaya daga cikin dillalai (misali, girgije) ya gaza, mai amfani na ƙarshe zai karɓi bayanai daga ɗayan (hazo). Wannan siffa ce ta haɗin hazo da tsarin sarrafa girgije. Ta hanyar tsohuwa, ana iya saita app ɗin wayar hannu don haɗawa da hazo mai kulla MQTT da farko, kuma idan hakan ya gaza, don haɗawa da dillalin MQTT. Wannan mafita ɗaya ce daga cikin da yawa a cikin tsarin IoT-F2C.
Multi-protocol mafita
Maganganun yarjejeniya guda ɗaya sun shahara saboda sauƙin aiwatar da su. Amma a bayyane yake cewa a cikin tsarin IoT-F2C yana da ma'ana don haɗa ka'idoji daban-daban. Manufar ita ce ka'idoji daban-daban na iya aiki a matakai daban-daban. Dauki, alal misali, abstractions guda uku: yadudduka na IoT, hazo da ƙididdigar girgije. Na'urori a matakin IoT gabaɗaya ana ɗaukar iyaka. Don wannan bayyani, bari mu yi la'akari da matakan IoT a matsayin mafi ƙuntatawa, gajimare mafi ƙarancin ƙuntatawa, da lissafin hazo a matsayin "wani wuri a tsakiya." Ya bayyana a lokacin cewa tsakanin IoT da hazo abstractions, mafita na yanzu sun haɗa da MQTT, CoAP da XMPP. Tsakanin hazo da gajimare, a daya bangaren, AMQP na daya daga cikin manyan ka'idojin da ake amfani da su, tare da REST HTTP, wanda saboda sassaucinsa kuma ana amfani da shi tsakanin IoT da hazo.
Babban matsala a nan ita ce haɗin kai na ka'idoji da sauƙi na aika saƙonni daga wannan yarjejeniya zuwa wani. Da kyau, a nan gaba, gine-ginen tsarin Intanet na Abubuwa tare da girgije da albarkatun hazo za su kasance masu zaman kansu daga ka'idar sadarwar da ake amfani da su kuma za su tabbatar da kyakkyawar hulɗar tsakanin ka'idoji daban-daban.
Tun da ba haka lamarin yake a halin yanzu ba, yana da ma'ana don haɗa ƙa'idodin da ba su da bambance-bambance masu mahimmanci. Don wannan, mafita ɗaya mai yuwuwa ta dogara ne akan haɗakar ka'idoji guda biyu waɗanda ke bin salon gine-gine iri ɗaya, REST HTTP da CoAP. Wani bayani da aka ba da shawarar ya dogara ne akan haɗakar ka'idoji guda biyu waɗanda ke ba da sadarwar buga-biyan kuɗi, MQTT da AMQP. Yin amfani da irin wannan ra'ayi (duka MQTT da AMQP suna amfani da dillalai, CoAP da HTTP suna amfani da REST) suna sanya waɗannan haɗin gwiwar sauƙi don aiwatarwa kuma suna buƙatar ƙarancin haɗin kai.
Hoto (a) yana nuna nau'ikan tushen amsa buƙatu guda biyu, HTTP da CoAP, da yuwuwar sanya su a cikin maganin IoT-F2C. Tunda HTTP ɗaya ce daga cikin sanannun ƙa'idodin ƙa'idodi na zamani akan hanyoyin sadarwa na zamani, ba zai yuwu a maye gurbinsa gaba ɗaya da sauran ka'idojin aika saƙon ba. Daga cikin nodes da ke wakiltar na'urori masu ƙarfi waɗanda ke zaune tsakanin gajimare da hazo, REST HTTP shine mafita mai wayo.
A gefe guda, don na'urori masu iyakacin albarkatun ƙididdiga waɗanda ke sadarwa tsakanin matakan Fog da IoT, ya fi dacewa don amfani da CoAP. Ɗaya daga cikin manyan fa'idodin CoAP shine ainihin dacewarsa tare da HTTP, tunda duka ƙa'idodin sun dogara ne akan ka'idodin REST.
Hoto (b) yana nuna nau'ikan sadarwar buga-biyan kuɗi biyu a cikin yanayi iri ɗaya, gami da MQTT da AMQP. Ko da yake ana iya amfani da duka ka'idojin biyu don sadarwa tsakanin nodes a kowane Layer na abstraction, yakamata a ƙayyade matsayinsu dangane da aiki. An tsara MQTT azaman ƙa'idar nauyi don na'urori masu iyakacin albarkatun kwamfuta, don haka ana iya amfani da shi don sadarwar IoT-Fog. AMQP ya fi dacewa da na'urori masu ƙarfi, wanda zai fi dacewa sanya shi tsakanin hazo da gajimare. Madadin MQTT, ana iya amfani da ka'idar XMPP a cikin IoT kamar yadda ake ɗaukar nauyi. Amma ba a ko'ina amfani da shi a irin waɗannan al'amuran.
binciken
Yana da wuya cewa ɗaya daga cikin ka'idojin da aka tattauna zai isa ya rufe dukkan hanyoyin sadarwa a cikin tsarin, daga na'urori masu iyakacin albarkatun kwamfuta zuwa sabar girgije. Binciken ya gano cewa mafi kyawun zaɓuɓɓuka biyu waɗanda masu haɓakawa ke amfani da su sune MQTT da RESTful HTTP. Waɗannan ka'idoji guda biyu ba wai kawai mafi girma da kwanciyar hankali ba ne, har ma sun haɗa da yawancin rubuce-rubuce masu kyau da aiwatarwa masu nasara da albarkatun kan layi.
Saboda kwanciyar hankali da sauƙi mai sauƙi, MQTT yarjejeniya ce wadda ta tabbatar da aikinta mafi girma a tsawon lokaci lokacin da aka yi amfani da shi a matakin IoT tare da na'urori masu iyaka. A cikin sassan tsarin inda ƙarancin sadarwa da amfani da baturi ba matsala ba ne, kamar wasu wuraren hazo da yawancin ƙididdigar girgije, RESTful HTTP zaɓi ne mai sauƙi. Hakanan ya kamata a yi la'akari da CoAP kamar yadda kuma yana haɓaka cikin sauri azaman daidaitaccen saƙon IoT kuma yana yiwuwa ya kai matakin kwanciyar hankali da balaga mai kama da MQTT da HTTP nan gaba kaɗan. Amma ma'aunin a halin yanzu yana haɓakawa, wanda ya zo tare da batutuwan dacewa na ɗan gajeren lokaci.
Me kuma za ku iya karantawa akan blog?
→
→
→
→
→
Kuyi subscribing din mu - tashar, don kada ku rasa labarin na gaba! Ba mu rubuta fiye da sau biyu a mako ba kuma akan kasuwanci kawai.
source: www.habr.com