IEEEwhitepaperIEEE802NetworksVerticalApplications(IEEE 802 网络垂直行业应用)

IEEESA

WHITEPAPER

IEEEP802.24

IEEE802®NETWORKSFORVERTICALAPPLICATIONS

Authoredby

MaxRiegelTimGodfrey

AmeliaAndersdotterAnnKrieger

Authorizedlicenseduselimitedto:IEEEXplore.DownloadedonJuly14,2025at08:00:52UTCfromIEEEXplore.Restrictionsapply.

PAGE

2

IEEESA

Copyright©2024IEEE.Allrightsreserved.

Authorizedlicenseduselimitedto:IEEEXplore.DownloadedonJuly14,2025at08:00:52UTCfromIEEEXplore.Restrictionsapply.

TRADEMARKSANDDISCLAIMERS

IEEEbelievestheinformationinthispublicationisaccurateasofitspublicationdate;suchinformationissubjecttochangewithoutnotice.IEEEisnotresponsibleforanyinadvertenterrors.

Theideasandproposalsinthisspecificationaretherespectiveauthor’sviewsanddonotrepresenttheviewsoftheaffiliatedorganization.

TheInstituteofElectricalandElectronicsEngineers,Inc.3ParkAvenue,NewYork,NY10016‐5997,USACopyright©2024byTheInstituteofElectricalandElectronicsEngineers,Inc.

Allrightsreserved.5April2024.PrintedintheUnitedStatesofAmerica.PDF: STDVA26897 979‐8‐8557‐0668‐0

IEEEisaregisteredtrademarkintheU.S.Patent&TrademarkOffice,ownedbyTheInstituteofElectricalandElectronicsEngineers,Incorporated.Allothertrademarksarethepropertyoftherespectivetrademarkowners.

IEEEprohibitsdiscrimination,harassment,andbullying.Formoreinformation,visit

/web/aboutus/whatis/policies/p9‐26.html.

Nopartofthispublicationmaybereproducedinanyform,inanelectronicretrievalsystem,orotherwise,withoutthepriorwrittenpermissionofthepublisher.

FindIEEEstandardsandstandards‐relatedproductlistingsat:

.

NOTICEANDDISCLAIMEROFLIABILITYCONCERNINGTHEUSEOFIEEESADOCUMENTS

ThisIEEEStandardsAssociation(“IEEESA”)publication(“Work”)isnotaconsensusstandarddocument.Specifically,thisdocumentisNOTANIEEESTANDARD.InformationcontainedinthisWorkhasbeencreatedby,orobtainedfrom,sourcesbelievedtobereliable,andreviewedbymembersoftheactivitythatproducedthisWork.IEEEandtheIEEEP802.24expresslydisclaimallwarranties(express,implied,andstatutory)relatedtothisWork,including,butnotlimitedto,thewarrantiesof:merchantability;fitnessforaparticularpurpose;non-infringement;quality,accuracy,effectiveness,currency,orcompletenessoftheWorkorcontentwithintheWork.Inaddition,IEEEandtheIEEEP802.24disclaimanyandallconditionsrelatingto:results;andworkmanlikeeffort.Thisdocumentissupplied“ASIS”and“WITHALLFAULTS.”

AlthoughtheIEEEP802.24memberswhohavecreatedthisWorkbelievethattheinformationandguidancegiveninthisWorkserveasanenhancementtousers,allpersonsmustrelyupontheirownskillandjudgmentwhenmakinguseofit.INNOEVENTSHALLIEEESAORIEEEP802.24MEMBERSBELIABLEFORANYERRORSOROMISSIONSORDIRECT,INDIRECT,INCIDENTAL,SPECIAL,EXEMPLARY,ORCONSEQUENTIALDAMAGES(INCLUDING,BUTNOTLIMITEDTO:PROCUREMENTOFSUBSTITUTEGOODSORSERVICES;LOSSOFUSE,DATA,ORPROFITS;ORBUSINESSINTERRUPTION)HOWEVERCAUSEDANDONANYTHEORYOFLIABILITY,WHETHERINCONTRACT,STRICTLIABILITY,ORTORT(INCLUDINGNEGLIGENCEOROTHERWISE)ARISINGINANYWAYOUTOFTHEUSEOFTHISWORK,EVENIFADVISEDOFTHEPOSSIBILITYOFSUCHDAMAGEANDREGARDLESSOFWHETHERSUCHDAMAGEWASFORESEEABLE.

Further,informationcontainedinthisWorkmaybeprotectedbyintellectualpropertyrightsheldbythirdpartiesororganizations,andtheuseofthisinformationmayrequiretheusertonegotiatewithanysuchrightsholdersinordertolegallyacquiretherightstodoso,andsuchrightsholdersmayrefusetograntsuchrights.AttentionisalsocalledtothepossibilitythatimplementationofanyorallofthisWorkmayrequireuseofsubjectmattercoveredbypatentrights.BypublicationofthisWork,nopositionistakenbytheIEEEwithrespecttotheexistenceorvalidityofanypatentrightsinconnectiontherewith.TheIEEEisnotresponsibleforidentifyingpatentrightsforwhichalicensemayberequired,orforconductinginquiriesintothelegalvalidityorscopeofpatentsclaims.Usersareexpresslyadvisedthatdeterminationofthevalidityofanypatentrights,andtheriskofinfringementofsuchrights,isentirelytheirownresponsibility.Nocommitmenttograntlicensesunderpatentrightsonareasonableornon-discriminatorybasishasbeensoughtorreceivedfromanyrightsholder.

ThisWorkispublishedwiththeunderstandingthatIEEEandtheIEEEP802.24membersaresupplyinginformationthroughthisWork,notattemptingtorenderengineeringorotherprofessionalservices.Ifsuchservicesarerequired,theassistanceofanappropriateprofessionalshouldbesought.IEEEisnotresponsibleforthestatementsandopinionsadvancedinthisWork.

IEEE802NETWORKSFORVERTICALAPPLICATIONS 5

BACKGROUNDANDINTRODUCTION 5

TABLE

OF

CONTENTS

REQUIREMENTSOFVERTICALAPPLICATIONS 5

ECONOMICASPECTSFORVERTICALAPPLICATIONNETWORKS 7

MODULARITYANDINTERCHANGEABILITY,COMPETITIONECONOMICS 8

POSSIBILITYOFSMALLBUSINESSENTITIESDEPLOYINGSMALL‐SCALE

NETWORKS 8

KEYASPECTSOFTHEIEEE802TECHNOLOGIESFORVERTICALAPPLICATIONS 8

LAYERING 8

ROUTINGANDBRIDGING 9

MANAGEMENTANDCONTROL 9

COMMONNETWORKMODELFORVERTICALAPPLICATIONNETWORKS 10

NETWORKREFERENCEMODEL 10

GENERICIEEE802ACCESSNETWORKFUNCTIONALBEHAVIOR 12

NETWORKVIRTUALIZATION,INSTANTIATION,ANDSLICING 13

HIGHERLAYERFUNCTIONSANDSERVICEDESIGNINVERTICALAPPLICATION

NETWORKS 15

ARCHITECTURALAPPROACHES 17

GENERALPARADIGMS 17

PROVISIONING(PLANNINGANDINSTALLATION) 18

ADMINISTRATION 18

OPERATION 18

MAINTENANCE 19

TROUBLESHOOTING 19

CONCLUSION 20

REFERENCES 21

APPENDIXA

IEEE802STANDARDSAIMEDFORVERTICALAPPLICATIONS 22

IEEE802OVERVIEWANDARCHITECTURE 22

IEEE802.1BRIDGINGANDMANAGEMENT 22

IEEE802.3:ETHERNET 24

IEEE802.11:WIRELESSLAN 25

IEEE802.15:WIRELESSSPECIALTYNETWORKS 26

IEEE802.16:BROADBANDWIRELESSMANS 27

IEEE802.19:WIRELESSCOEXISTENCE 28

IEEE802.21:MEDIAINDEPENDENTHANDOVERSERVICES 28

IEEE802.22:WIRELESSREGIONALAREANETWORKS 28

APPENDIXB

GLOSSARY 30

Authorizedlicenseduselimitedto:IEEEXplore.DownloadedonJuly14,2025at08:00:52UTCfromIEEEXplore.Restrictionsapply.

PAGE

10

IEEESA

Copyright©2024IEEE.Allrightsreserved.

Authorizedlicenseduselimitedto:IEEEXplore.DownloadedonJuly14,2025at08:00:52UTCfromIEEEXplore.Restrictionsapply.

IEEE802®NETWORKSFORVERTICALAPPLICATIONS

BACKGROUNDANDINTRODUCTION

IEEE802®technologiesareusedforawidevarietyofapplicationsandmarkets.DespitethewidespreadusageandoverwhelmingadoptionofPHYandLinklayertechnologiesforallkindsofinformationandcommunicationsolutions,acommonperceptionofthevalueanddifferentiationoftheIEEE802architectureinthecontextofverticalmarketsisnotestablished.TherearenoclearviewsaboutwhyIEEE802wouldbebettersuitedtodeploymentsinthecommunicationinfrastructureofprivateenterprise,industry,andtheindividualuser,andhowIEEE802comparestonetworkarchitecturesorientedtowardserviceproviders.

Inthefirststance,itcouldbeagreedthattheIEEE802architectureenablesnetworksthatarelikeIEEE802.3Ethernet—wellunderstood,mature,predictable,offeringa“cleaner”integrationofdisparatetechnologiesunderthecommonarchitectureandaddressing.

ThiswhitepaperaimstocollectandspelloutcommonalitiesofIEEE802technologiesandsetthesceneinrelationtootherwell-knowncommunicationstandardsofsimilarbehavior.

REQUIREMENTSOFVERTICALAPPLICATIONS

Thissectiondefinesthecharacteristicsofverticalapplicationsthatusuallyintegratevarioussystems,includingnetworkconnectivity,inordertoperformspecifictasksorenableusecasesfortheirindustry.

Inthecontextofthiswhitepaper,“verticalapplications”referstonetworksthatservespecificusecasesinspecificmarketsegments.Thenetworkisusedbytheentitytoenableitsbusinessprocesses.Thisisincontrasttoanaccessnetwork,wherethenetworkservicesaretheproduct.

Verticalmarketsinvolvethefollowingspecificusagemodels:

Industrialautomation

Buildingautomation

Smartcities

Smartgrid/utility

Automotive/transportation

Agriculture

Connectedsupplychain

Criticalinfrastructureprotectionandcontrol

Wideareagaming(includingAR/VR)

Thereareotherwaysoflookingat“vertical.”Verticalintegrationisreallyacompetition/antitrusttermratherthanatechnicalterm.Inthatcontext,itdescribesatechnicalsituationinthatsomesetoffunctionalitiesthatmaybeprovidedbythesamecompanycouldactuallyinpracticealsobeprovidedbydifferentcompanies.So,forinstance,“5G”is“verticallyintegrated”becauseitactuallyassumesinitstechnicalspecificationsthatasinglecommercialproviderwillberesponsibleforawholerangeofdifferentfeaturesthatarenotreallyseparable.Inthatsense,IEEE802technologiesarenot“verticallyintegrated”becausetheycanbedeployedbydifferentoperatorsofcompletelydifferentnetworks(e.g.,oneleverageswiredconnections,whileothersarebasedonwirelessconnectivity).Nevertheless,IEEE802playsaroleinverticalintegrationbyprovidingtheplainconnectivitylayer,e.g.,IEEE802.11inIEEE1609vehicle-to-vehiclecommunications,orIEEE802.15.4intheSEP.

Verticalmarketsoftenrequirehighlyengineerednetworkstoguaranteethequalityoftherequiredcommunicationservices.Quiteoften,verticalmarketsfollowextendedlifecycles;theverticalnetworkisexpectedtoremaininserviceforalongertimethanaservice-providernetwork.Verticalmarketsmayhavedifferentcostmodelscomparedwithusualpubliccommunicationnetworkswheresomeareopexaverseandothersaremorecapexaverse.

ECONOMICASPECTSFORVERTICALAPPLICATIONNETWORKS

IEEE802-basednetworksareusuallyaimedto“enablecreating/deliveringaproduct”insteadof“thenetworkistheproduct”definedbyanopenstandard:

AnIEEE802networkisdeployedinverticalmarkets,wherethenetworkisownedandoperatedbytheuseroftheservices.

Therearealsoothermodelsthansubscriptionsthatprovideancillaryeconomicvalue.

Aneconomyofscalecanbeaccomplishedbycreatinganetworkthatcanbeleveragedbymultipleentities.Thisissimilartocloudthinking—themodelofsharingtheinfrastructure(network)withoutneedingthemtobeindependentlyinstalledandmanaged.Itisasimilarconcepttoadatacenter,justprovidingcomputingresourcesbutnotdealingwithinstallingandrunningsoftwareforalltheservicesneeded.

ThetrendtowardmorevirtualizationisastrengthofIEEE802becauseitallowsthenetworktobebetterpreparedforthatvirtualization.Itprovidesacleanseparationbetweentheinfrastructureandtheservicerunningontheinfrastructure.IntheIEEE802case,thisisthelayer2tolayer3boundary.

TheIEEE802.3Ethernettransportisthemostwell-understoodtransportinexistence.ThisisanalogoustotheX86computerarchitecturethatbecamethebasisforthecomputingresourcesofdatacenters.

IEEE802andunlicensedspectrumenablefasterinnovation.

Manyofthebreakthroughinnovationswerenotasplanned.

ThestoryofwhyIEEE802complementseverythingelse,andeverythingelse(alone)isnotsufficient.

TheIoTisbuiltaroundmanyspecializedniches.Thechallengeismeetingtheirdiverserequirements.Nosinglestandardcanaddressallofthemwell.IEEE802providesmultiplestandardstoaddressmultipleIoTapplications(seeAppendixA).

Themodelfornetworkmanagementrequiresspecialattentionwhentheowner/operatorofthenetworkmayhavelessexpertiseinnetworkmanagement.Guidanceisdesiredonhowtomanageandoperateaprivatenetwork.Usually,thisissimplerbecausetheIEEE802networkissimpler(comparedto3GPP,forexample),butthedocumentationisoftennotreallymatureoravailable.Yangmodelingdescribestheinterface,butmoreknowledgeisneededtounderstandhowtousethenetworkmanagementdataavailablethroughtheinterface.

MODULARITYANDINTERCHANGEABILITY,COMPETITIONECONOMICS

Auserofaverticalapplicationmaywanttobeabletoreplacepartsoftheirverticalapplicationnetworkwithabetter,newerproductwhenonearrives(forinstance,installinganewAPwhenabetteroneisavailablefromadifferentvendor).IEEE802productslendthemselvestothisformofuser‐empoweredmodularity.

Buildingblockswithsmallerfunctionalcontentandbroadervariationofferthisflexibilitytotheverticalapplication.3GPP5G(orcellularnetworksingeneral)doesnothavethismodularfeature.AlthoughmanyUEvendorscanbecertifiedtothespecifications,itismuchharderforthenetworkownertomixmultiplevendorsintheRANandcoreofthenetwork.

POSSIBILITYOFSMALLBUSINESSENTITIESDEPLOYINGSMALL-SCALENETWORKS

ItwouldbepossibleforasmallutilityormunicipalitywithonlyafewemployeestosetupareasonablysecureWi‐Finetworkattheirworkplace,perhapswithtemporaryhelpfromaconsultantiftheyweremakingsureitwasreallysecure.However,theywouldfinditmuchmoredifficulttoacquireamunicipalspectrumlicenseforLTEtechnologiesandinstall,configure,andmaintaina3GPPprivatenetworkinfrastructure.

IEEE802alsoenablesagreaterdegreeofscalability.Anetworkthatstartssmallcaneasilybescaledtomorecomplexityandusersasthebusinessgrows.A3GPPaccessnetworkisdesignedfromthestartforalargescaleandismoredifficulttoapplyatasmallscale.

KEYASPECTSOFTHEIEEE802TECHNOLOGIESFORVERTICALAPPLICATIONS

LAYERING

IEEE802isatransportnetwork.

IEEE802islayer2.

IEEE802providesdirectandsimultaneoussupportofIPv4andIPv6orpurelayer-2protocols.

IEEE802offerstrade-offsandoptimizationsbetweenflexibility(L2)andscalability(L3).

ROUTINGANDBRIDGING

IEEE802enablesnetworkstoscalewithroutingandbridging.

IEEE802supportslayer-3protocolssuchasIP,whichenablesroutingtoenableIEEE802networkstoexpandtoahigherscale.

IEEE802networkscanbebuiltonasmallerscaletoprovidemoreflexibility.

Thesmallerscaleprovidesanopportunityforreal-time.

IEEE802standardscanemulateapoint-to-pointnetworkoverawirelesspoint-to-multipointnetworktoenablebridgingoverthewirelesslink.

IEEE802cansupportmultipledifferentL3andaboveprotocolsuites.

IEEE802canalsoofferL2routingwhenappropriate(e.g.,IEEE802.15.10).

Note:ThisisnotanalternativetoL3routing,butusedtoaddressadifferentproblem.

MANAGEMENTANDCONTROL

IEEE802doesnotprovideasmanymeansofcontrolforaspecificenddeviceanditstrafficonapath.

Therearesomemanagementfacilitieswithsomestandards.

ItiseasierforIEEE802tosupportan“unmanaged”network,suchasconsumerWi-Fi.

IEEE802provideslocalnetworksthatmaybe(butdonothavetobe)connectedtotheinternetorothernetworks.

Publicoperatornetworksarefocusedonservicesforsingledevices,whileIEEE802networkssupportandincludemultipledevices(networksofnetworks)—devicescancommunicatewitheachotheraswellaswithothernetworks.

COMMONNETWORKMODELFORVERTICALAPPLICATIONNETWORKS

AcommonfoundationofthenetworkarchitectureforavarietyofverticalapplicationsisprovidedbyIEEEStd802.1CF™-2019,IEEERecommendedPracticeforNetworkReferenceModelandFunctionalDescriptionofIEEE802AccessNetwork.

Allcommunicationnetworksprovidingthemeanstoconnectvariouscommunicationendpoints(terminals)tothesameordifferentinformationserversoverasharedinfrastructurefollowthesamearchitecturalprinciples.IEEE802technologiessupporttherealizationofanaccessnetwork,whichestablishesthesharedinfrastructure,allowingthemanagementoftheconnectionsofawidevarietyofterminalsthroughwiredorwirelessinterfacestotheircommunicationpeers,eitherthroughbridginginthelocalarea,orthroughroutingbyanaccessrouterinmorewidespreadnetworks.

NETWORKREFERENCEMODEL

Figure1

showsthemappingoftheIEEE802NRMtousualcommunicationnetworktopologies.ThecoreoftheNRMistheaccessnetworkthatconnectsterminallyeitherdirectlythroughbridgingorforwardtraffictotheaccessrouterwhenthecommunicationpeerisbehindthesameLayer2domain.Variouscontrolentitiessupporttheaccessnetworktoprovidesecuredandmanagedconnectivity.

FIGURE1 Networkreferencemodeldesign

NMSdenotesthenetworkmanagementsystemthatprovidesthefunctionstoconfigureandmonitorthecorrectoperationoftheaccessnetworkinfrastructure.Thesubscriptionserviceisthecontrolentitythatdealswiththecommunicationdemandoftheindividualterminals.Itprovidesauthenticationtorestricttheusageoftheaccessnetworktoonlyknownterminalsandprovidestotheaccessnetworktheconfigurationparametersthateachoftheterminalsexpectsforproperoperation.

Subscriptionserviceisageneraltermthatcanmeananyfunctionfromatraditionaloperatorsubscriptionservicetoaprivatenetwork’sauthenticationanddevicepolicycontrolfunction.

Figure2

furtherdetailstheNRMbyexposingtheinternalstructureoftheaccessnetworkaswellastheterminalandaccessrouter,andthroughthedefinitionofreferencepointslabeledR1–R12todenotecontrolanduserdatainterfacesoftheaccessnetwork.Solidlinesindicatethepathoftheuserdata,whiledottedlinesindicatetheflowofcontrolinformation.ThefigurealsoshowsanadditionalcontrolentitycalledCoordinationandInformationService,whichisonlyneededwhenmultipleaccessnetworksdynamicallysharethesamecommunicationresources,likeinthecaseofdynamicspectrummanagementordynamicresourcesharingofvirtualandvirtualizedaccessnetworks.

FIGURE2 IEEE802Networkreferencemodel

TheIEEE802NRMisaconceptualmodelthatallowsmanydifferentimplementationstoleveragethesamefoundationandnetworkfunctions,butitisnotintendedasanexactblueprintfortheinstallationofarealnetwork.Verticalapplicationshaveveryspecificnetworkingrequirements.Toaccommodatethevarietyofrequirements,IEEEStd802.1CFprovidesguidanceandacommonstructuretobuildpowerfulnetworksoutoftheuniversalIEEE802technologybuildingblocks.

TheapplicabilityandflexibilityoftheapproacharedemonstratedinIEEEStd802.1CFthroughthemappingoftheNRMtoanumberofdeploymentscenariosfromasimpleWLANrouter,homenetworks,simpleandmorecomplexenterprisenetworks,industrialnetworks,publicWLANhotspotstovirtualizedWLANaccessnetworksforin-buildingIoTservicesandnetworksforfogcomputing.

GENERICIEEE802ACCESSNETWORKFUNCTIONALBEHAVIOR

InadditiontoacommonNRMintroducedabove,thespecificationalsoprovidesagenericfunctionaldescriptionoftheoperationofanaccessnetworkbuiltthroughIEEE802technologies.

Figure3

showsthefunctionalphasesofanaccessnetworkduringasessionofanIEEE802terminal.Thesessionbeginswiththeterminalsearchingforpotentialaccesstoanetworkandendswitheithertheterminalornetworktearingdowntheconnectivity.

FIGURE3 Lifecycleofausersession

Therearemanynetworkfunctionsinvokedbetweenthebeginningandtheendofasession,and

Figure3

showsatypicalexamplemainlyalignedtotheIEEE802.11airinterface.Thefunctionaldescriptionprovidesacomprehensivereferenceofthemanagementandcontrolinformationconveyedoverthereferencepointsbetweentheaccessnetworkandexternalcontrolandmanagemententities.SuchreferenceisnotonlyhelpfulforeducationalpurposesbutalsofosterscommonalitiesinthedesignofthecontrolgearofIEEE802accessnetworksandprovidesadevelopmentbaseforthevirtualizationofIEEE802accessnetworks.

NETWORKVIRTUALIZATION,INSTANTIATION,ANDSLICING

Whilewell-knownmodelslikeVLANsinIEEE802orthenetworkslicingsolutionof3GPPprovideseveralisolateduserdataplanesinacommoninfrastructure,whichcanbeeitherassignedtodifferentservicesordifferenttenantsofthenetwork,thenetworkfunctionalmodelingprovidestheprerequisitesforsettingupmultipleinstancesnotonlyfortheuserdatapathbutalsoforallthecontrolassociatedwithauserdatapath.Separatingnotonlythedatapathsofmultipletenantsbutalsoallthecontrolsassociatedwithadatapathallowstoaddressoneofthemainprerequisitesofthedeploymentofverticalapplicationnetworks—theneedforindependentoperationaldomainsforeachoftheverticals.VirtualizedIEEE802accessnetworksbehaveexactlythesamewayasdedicatedaccessnetworksbuthavethecostandscalabilitybenefitsofmakinguseofacommoninfrastructure.ItisthesameapproachthatwastakenthroughVMs,leadingtotheestablishmentofcloudcomputing.

Figure4

displaystheconceptofvirtualizationoftheIEEE802accessnetwork.Threeinstancesareshownbasedonacommoninfrastructure,eachwithitsowncontrolentitiesandinterfacestowardsterminalsandapplicationserversreachablethroughtheaccessrouter.Asinfrastructureresourcescanbedynamicallysharedamongthevirtualizednetworks,theCISactsasacontrolentitymanagingthedynamicassignmentofinfrastructureresources.

Thevirtualizedaccessnetworkexampleshownaboveisdirectedintopotentialnetworkevolutionbeyondthecurrentunderstandingofnetworkslicing.However,IEEEStd802.1CFalreadyprovidesthemodelandconceptsofvirtualizedaccessnetworks,whichcanbefullybuiltbasedonexistingIEEE802protocolspecifications.ItisshownthattherealizationofsuchpowerfulnetworkingconceptswithIEEE802technologiesisamatterofimplementationwithouttheneedforlengthystandardizationactivities.

FIGURE4 MultipleinstancesofvirtualizedIEEE802accessnetwork

HIGHERLAYERFUNCTIONSANDSERVICEDESIGNINVERTICALAPPLICATIONNETWORKS

IEEE802providesahighvarietyofwiredandwirelesssolutionsforthePhysicalandLinklayerfunctionsofcommunicationlinkstoserveaverywiderangeofrequirementsofapplications.EachoftheapplicationscanchoosefromthecommonIEEE802communicationtoolboxthefeaturesthatbestfititsparticularneedswithoutcompromisesorexaggeratedcomplexitiesduetoacommonhigherlayerarchitecture.

Application-specificprotocolstacksfornetworklayer,transportlayer,andapplicationlayerfunctionshavebeenmostlyreplacedthroughIPprotocolsinthepastdecadestoleveragethehugebenefitsofthecommonIPprotocolregardingflexibility,performance,availability,andcost.IEEE802technologiesplayedahugeroleinthetransformationtoIPprotocolsastheprotocolsandtechnologiesprovidedexcellentsupportforthetransportofIPpackets,andtheywereabletocopewiththegrowthofIPtrafficthroughsteadyenhancements.

Therefore,usually,theGenericIPprotocolstackisusedforrealizingverticalapplications,leveragingIPv4/IPv6intheNetworklayer,TCPorUDPintheTransportlayer,andwell-knownIPprotocolssuchasHTTP,CoAP,orMQTTintheApplicationlayer.

However,theIEEE802technologiesallowformorespecificnetworksolutionswhenspecialrequirementsorconditionsarise.LegacynetworkingprotocolstackscanbeoperatedfortransitionandinteroperabilityasidefromIPprotocolsolutionsonthesamecommunicationinfrastructure.

Figure5

illustratesafewexamplesoftheapproachestorealizeverticalapplicationnetworksontopofIEEE802technologies.

FIGURE5 ExamplesofverticalapplicationsbasedonIEEE802networking

VerticalapplicationnetworksoftennotonlydeploytheIP-basedprotocolsuitebutleveragemorespecializedtransportsolutions.

TheSmartEnergyProfile2(SEP2)standardwasinitiallyspecifiedbytheZigBeeAllianceinconjunctionwiththeHomePlugAllianceandlateradoptedbyIEEEthroughIEEEStd2030.5

[4].

ItprovidesaRESTfulmessagingprotocolforinformationandcontrolforenergymanagementinhomeareanetworksforbothwiredandwirelessnetworks.ItcanbeappliedtotransportbasedonIETFIPprotocolsorotherspecializedtransportprotocolsforparticularlinktechnologieslikeIEEE802.15.4.

Matterisasmart-homeconnectivitystandardthatoriginatedfromtheformerCHIPproject.ItaimstoprovideinteroperabilityamongsmarthomedevicesandIoTplatformsofdifferentvendorsandproviders.Matterprovidesamultilayerapplicationprotocolsuitethatisprovidedasopensourceforeasyadoption.InadditiontoplainIP-basedconnectivityoveranykindoflinktechnology,italsosupportsthread-basedconnectivityoverIEEE802.15.4.

WAVEisspecifiedthroughIEEEStd1609,leveragingIEEEStd802.11aswirelesslinktechnology.VariousoptimizationsintheupperpartoftheDataLinklayerandabovewereappliedtocopewiththeparticularitiesofarapidlychangingwirelessenvironment.TheIEEE1609seriesofstandardsdescribesthearchitectureandservicesnecessaryfordevicestocommunicateinamobilevehicularenvironment.ItfollowstheopensysteminterconnectmodelandprovidessupportfortheIPanditstransportprotocols.Inaddition,securingWAVEmanagementmessagesandapplicationmessagesisaddressed,aswellasadministrativefunctionsnecessarytosupportthecoresecurityfunctions.

ARCHITECTURALAPPROACHES

AnIEEE802networkcouldbeconsideredasasetofbuildingblocksoraheapofstones,representinganopenarchitecture.The3GPParchitectureisalreadydefinedasaCastle.IEEE802issomewhatdifferentasitdoesnothavepre-conceivedideasabouttheresultingnetwork,makingitbetterabletosupportdiverseverticalapplications.

IEEE802

Others,e.g.,3GPP

Openarchitecture

Definedarchitecture

IEEE802isdevelopingprofilesfordifferentdomainstoprovidetheabilitytospecifyamoredefinedarchitecturefromthebuildingblocks.Toextendthepreviousanalogy,theprofilescoulddefineseveralbuildingtypesoutofthebuildingblocks,notjustacastle.

GENERALPARADIGMS

Aim

Simplicityfirst

Perfectsolutions

Approach

Divideandconquer

Strictlyhierarchical

Goal

Commonsolutions

Extremeoptimization

Purpose

U