UNIT-5 IoT Reference Architecture.pdf

IoT Reference Architecture including,
Functional view, Component View

1. Unit5Review
IoT Reference Architecture
Introduction,FunctionalView,InformationView,
DeploymentandOperationalView,OtherRelevant
architecturalviews.
Real-World Design Constraints
Introduction,TechnicalDesignconstraints-hardwareis
popularagain,Datarepresentationandvisualization,
Interactionandremotecontrol.
Industrial Automation
Service-orientedarchitecture-baseddeviceintegration,
SOCRADES:realizingtheenterpriseintegratedWebof
Things,IMC-AESOP:fromtheWebofThingstothe
CloudofThings,
1

2. IoTReferenceArchitecture
TheReferenceArchitectureisastartingpointfor
generatingconcretearchitecturesandactualsystems.
Aconcretearchitectureaddressestheconcernsof
multiplestakeholdersoftheactualsystem,anditis
typicallypresentedasaseriesofviewsthataddress
differentstake-holderconcerns.
Viewsareusefulforreducingthecomplexityofthe
ReferenceArchitectureblueprintsbyaddressing
groupstheconcernsofonegroupatatime.
2

3. Views
ThestakeholdersforaconcreteIoTsystemarethepeoplewhousethe
system(HumanUsers);thepeoplewhodesign,build,andtestthe
Resources,Services,ActiveDigitalArtifacts,andApplications;
ThepeoplewhodeployDevicesandattachthemtoPhysicalEntities;the
peoplewhointegrateIoTcapabilitiesoffunctionswithanexistingICT
system(e.g.ofanenterprise);
Thepeoplewhooperate,maintain,andtroubleshootthePhysicaland
VirtualInfrastructure;
ThepeoplewhobuyandownanIoTsystemorpartsthereof
InordertoaddresstheconcernsofmainlytheconcreteIoTarchitect,
andsecondlytheconcernsofmostoftheabovestakeholders,the
ReferenceArchitectureispresentedasasetofarchitecturalviews
FunctionalView:Descriptionofwhatthesystemdoes,anditsmain
functions.
InformationView:Descriptionofthedataandinformationthatthe
systemhandles.
DeploymentandOperationalView:Descriptionofthemainreal
worldcomponentsofthesystemsuchasdevices,networkrouters,
servers,etc.
3

4. IoTFunctionalView
4

5. DeviceandApplicationfunctionalgroup
DeviceFGcontainstheSensing,Actuation,Tag,
Processing,StorageFCs,orsimplycomponents.
Thesecomponentsrepresenttheresourcesofthe
deviceattachedtothePhysicalEntitiesofinterest.The
ApplicationFGcontainseitherstandaloneapplications
(e.g.foriOS,Android,Windowsphone),orBusiness
ApplicationsthatconnecttheIoTsystemtoan
Enterprisesystem.
5

6. Communicationfunctionalgroup
TheCommunicationFGcontainstheEnd-to-End
Communication,NetworkCommunication,andHop-
by-Hopcommunicationcomponents:
TheHop-by-HopCommunicationisapplicableinthe
casethatdevicesareequippedwithmeshradio
networkingtechnologiessuchasIEEE802.15.4for
whichmessageshavetotraversethemeshfromnode-
to-node(hop-by-hop)untiltheyreachagatewaynode
whichforwardsthemessage(ifneeded)furthertothe
Internet.
6

7. NetworkFC
TheNetworkFCisresponsibleformessagerouting&
forwardingandthenecessarytranslationsofvarious
identifiersandaddresses.
Thetranslationscanbe(a)betweennetworklayer
identifierstoMACand/orphysicalnetworkidentifiers,
(b)betweenhigh-levelhumanreadablehost/node
identifierstonetworklayeraddresses(e.g.FullyQualified
DomainNames(FQDN)toIPaddresses,afunction
implementedbyaDomainNameSystem(DNS)server),
(c)translationbetweennode/serviceidentifiersand
networklocatorsincasethehigherlayersabovethe
networkinglayerusenodeorserviceidentifiersthatare
decoupledfromthenodeaddressesinthenetwork(e.g.
HostIdentityProtocol)
7

8. EndtoEndCommunication
TheEnd-to-EndCommunicationFCisresponsiblefor
end-to-endtransportofapplicationlayermessages
throughdiversenetworkandMAC/PHYlayers.
Inturn,thismeansthatitmayberesponsibleforend-
to-endretransmissionsofmissingframesdepending
ontheconfigurationoftheFC.
Forexample,iftheEnd-to-EndCommunicationFCis
mappedinanactualsystemtoacomponent
implementingtheTransmissionControlProtocol(TCP)
protocol,reliabletransferofframesdictatesthe
retransmissionofmissingframes
8

9. IoTServicefunctionalgroup-TheIoTServiceFC
IoTServicefunctionalgroupTheIoTServiceFG
consistsoftwoFCs:
TheIoTServiceFCandtheIoTServiceResolutionFC:
TheIoTServiceFCisacollectionofservice
implementations,whichinterfacetherelatedand
associatedResources.
ForaSensortypeofaResource,theIoTServiceFC
includesServicesthatreceiverequestsfromaUserand
returnstheSensorResourcevalueinsynchronousor
asynchronous(e.g.subscription/notification)fashion.
9

10. IoTServicefunctionalgroup-TheIoTService
ResolutionFC
TheIoTServiceResolutionFCcontainsthenecessary
functionstorealizeadirectoryofIoTServicesthat
allowsdynamicmanagementofIoTService
descriptionsanddiscovery/lookup/resolutionofIoT
ServicesbyotherActiveDigitalArtifacts.
Dynamicmanagementincludesmethodssuchas
creation/update/deletion(CUD)ofServicedescription,
andcanbeinvokedbyboththeIoTServices
themselves,orfunctionsfromtheManagementFG.
Thediscovery/lookupandresolutionfunctionsallow
otherServicesorActiveDigitalArtifactstolocateIoT
Servicesbyprovidingdifferenttypesofinformationto
theIoTServiceResolutionFC.
10

11. VirtualEntityfunctionalgroup
TheVirtualEntityFGcontainsfunctionsthatsupportthe
interactionsbetweenUsersandPhysicalThingsthroughVirtual
Entityservices.
AnexampleofsuchaninteractionisthequerytoanIoTsystem
oftheform,“Whatisthetemperatureintheconferenceroom
Titan?”
TheVirtualEntityistheconferenceroom“Titan,”andthe
conferenceroomattributeofinterestis“temperature.”
TheVirtualEntityServiceFCenablestheinteractionbetween
UsersandVirtualEntitiesbymeansofreadingandwritingthe
VirtualEntityattributes(simpleorcomplex),whichcanberead
orwritten.
TheVirtualEntityRegistryFCmaintainstheVirtualEntitiesof
interestforthespecificIoTsystemandtheirassociations.The
component offers services such as
creating/reading/updating/deletingVirtualEntitydescriptions
andassociations.
11

12. VirtualEntityfunctionalgroup
TheVirtualEntityResolutionFCmaintainstheassociations
betweenVirtualEntitiesandIoTServices,andoffers
servicessuchascreating/reading/updating/deleting
associationsaswellaslookupanddiscoveryofassociations.
TheVirtualEntityandIoTServiceMonitoringFCincludes:
(a)functionalitytoassertstaticVirtualEntity-IoTService
associations,
(b)functionalitytodiscovernewassociationsbasedon
existingassociationsorVirtualEntityattributessuchas
locationorproximity,and
(c)continuousmonitoringofthedynamicassociations
betweenVirtualEntitiesandIoTServicesandupdatesof
theirstatusincaseexistingassociationsarenotvalidany
more.
12

13. IoTprocessmanagementfunctionalgroup
TheIoTProcessManagementFGaimsatsupporting
theintegrationofbusinessprocesseswithIoT-related
services.
ItconsistsoftwoFCs:
TheProcessModelingFCprovidesthatrighttoolsfor
modelingabusinessprocessthatutilizesIoT-related
services.
TheProcessExecutionFCcontainstheexecution
environmentoftheprocessmodelscreatedbythe
ProcessModellingFCandexecutesthecreated
processesbyutilizingtheServiceOrganizationFGin
ordertoresolvehigh-levelapplicationrequirementsto
specificIoTservices.
13

14. ServiceOrganizationfunctionalgroup
TheServiceOrganizationFGactsasacoordinatorbetween
differentServicesofferedbythesystem.
ItconsistsofthefollowingFCs:
TheServiceCompositionFCmanagesthedescriptions
andexecutionenvironmentofcomplexservicesconsisting
ofsimplerdependentservices.
Anexampleofacomplexcomposedserviceisaservice
offeringtheaverageofthevaluescomingfromanumberof
simpleSensorServices.
TheServiceOrchestrationFCresolvestherequests
comingfromIoTProcessExecutionFCorUserintothe
concreteIoTservicesthatfulfiltherequirements.
TheServiceChoreographyFCisabrokerforfacilitating
communication among Servicesusing the
Publish/Subscribepattern.
14

15. Securityfunctionalgroup
TheSecurityFGcontainsthenecessaryfunctionsforensuringthesecurityand
privacyofanIoTsystem.ItconsistsofthefollowingFCs:
TheIdentityManagementFCmanagesthedifferentidentitiesoftheinvolved
ServicesorUsersinanIoTsysteminordertoachieveanonymity.
TheAuthenticationFCverifiestheidentityofaUserandcreatesanassertion
uponsuccessfulverification.
Italsoverifiesthevalidityofagivenassertion.
TheAuthorizationFCmanagesandenforcesaccesscontrolpolicies.Itprovides
servicestomanagepolicies(CUD),aswellastakingdecisionsandenforcing
themregardingaccessrightsofrestrictedresources.Theterm“resource”here
isusedasarepresentationofanyiteminanIoTsystemthatneedsarestricted
access.
Suchanitemcanbeadatabaseentry(PassiveDigitalArtifact),aService
interface,aVirtualEntityattribute(simpleorcomplex),a
Resource/Service/VirtualEntitydescription,etc.
TheKeyExchange&Managementisusedforsettingupthenecessary
securitykeysbetweentwocommunicatingentitiesinanIoTsystem.This
involvesasecurekeydistributionfunctionbetweencommunicatingentities.
TheTrust&ReputationFCmanagesreputationscoresofdifferentinteracting
entitiesinanIoTsystemandcalculatestheservicetrustlevels.
15

16. Managementfunctionalgroup
TheManagementFGcontainssystem-widemanagementfunctionsthatmayuseindividualFC
managementinterfaces.Itisnotresponsibleforthemanagementofeachcomponent,ratherforthe
managementofthesystemasawhole.
ItconsistsofthefollowingFCs:
TheConfigurationFCmaintainstheconfigurationoftheFCsandtheDevicesinanIoTsystem(a
subsetoftheonesincludedintheFunctionalView).
ThecomponentcollectsthecurrentconfigurationofalltheFCsanddevices,storesitinahistorical
database,andcomparescurrentandhistoricalconfigurations.
Thecomponentcanalsosetthesystem-wideconfiguration(e.g.uponinitialization),whichinturn
translatestoconfigurationchangestoindividualFCsanddevices.
TheFaultFCdetects,logs,isolates,andcorrectssystem-widefaultsifpossible.Thismeansthat
individualcomponentfaultreportingtriggersfaultdiagnosisandfaultrecoveryproceduresintheFault
FC.
TheMemberFCmanagesmembershipinformationabouttherelevantentitiesinanIoTsystem.
ExamplerelevantentitiesaretheFGs,FCs,Services,Resources,Devices,Users,andApplications.
Membershipinformationistypicallystoredinadatabasealongwithotherusefulinformationsuchas
capabilities,ownership,andaccessrules&rights,whichareusedbytheIdentityManagementand
AuthorizationFCs.
TheStateFCissimilartotheConfigurationFC,andcollectsandlogsstateinformationfromthe
currentFCs,whichcanbeusedforfaultdiagnosis,performanceanalysisandprediction,aswellas
billingpurposes.ThiscomponentcanalsosetthestateoftheotherFCsbasedonsystem-wisestate
information.
TheReportingFCisresponsibleforproducingcompressedreportsaboutthesystemstatebasedon
inputfromFCs.
16

17. Informationview
Theinformationviewconsistsof
(a)thedescriptionoftheinformationhandledinthe
IoTSystem,and
(b)thewaythisinformationishandledinthesystem;
inotherwords,theinformationlifecycleandflow(how
informationiscreated,processed,anddeleted),andthe
informationhandlingcomponents.
17

18. ThepiecesofinformationhandledbyanIoTsystemitcan
be
VirtualEntitycontextinformation,i.e.theattributes(simple
orcomplex)asrepresentedbypartsoftheIoTInformation
model.
IoTServiceoutputitselfisanotherimportantpartof
informationgeneratedbyanIoTsystem.Forexample,this
istheinformationgeneratedbyinterrogatingaSensorora
TagService
VirtualEntitydescriptionsingeneral,whichcontainnot
onlytheattributescomingfromIoTDevices(e.g.ownership
information).
AssociationsbetweenVirtualEntitiesandrelatedIoT
Services.
18

19. Informationflowandlifecycle
Onahighlevel,theflowofinformationinanIoT
systemfollowstwomaindirections.
Fromdevicesthatproduceinformationsuchassensors
andtags,informationfollowsacontext-enrichment
processuntilitreachestheconsumerapplicationor
partofthelargersystem,andfromtheapplicationor
partofalargersysteminformationitfollowsacontext-
reductionprocessuntilitreachestheconsumertypes
ofdevices.
19

20. Cont..
TheenrichmentprocessisshowninFigure.Devices
equippedwithsensorstransformchangesinthe
physicalpropertiesofthePhysicalEntitiesofInterest
intoelectricalsignals.
Theseelectricalsignalsaretransformedinoneor
multiplevalues(Figure8.2a)onthedevicelevel.
Thesevaluesarethenenrichedwithmetadata
informationsuchasunitsofmeasurement,timestamp,
andpossiblylocationinformation(Figure8.2b).
Theseenrichedvaluesareofferedbyasoftware
component(Resource)eitheronthedeviceorthe
network.TheResourceexposescertainIoTServicesto
formalizeaccesstothisenrichedinformation(Figure
8.2c).
20

21. 21

22. Atthispoint,theinformationisannotatedwithsimple
attributessuchaslocationandtime,andoftenthistype
ofmetadataissufficientforcertainIoTapplicationsor
fortheuseincertainlargersystems.
Thisenrichedinformationbecomescontext
informationassoonasitisfurtherassociatedwith
certainPhysicalEntitiesintheformofVirtualEntity
attributes(simpleorcomplex,staticordynamic).
FurthersupportinformationsuchasAssociations
betweencertainattributesandIoTServicesfurther
enrichesthecontextinformationoftheVirtualEntity
(Figure8.2d
22

23. enrichmentoccursinapplicationsorlargersystems
thatemploy,
forexample,dataanalytics,machinelearning,and
knowledgemanagement,whichproducesactionable
information.
Partsofthecontextandactionableinformationmaybe
storedtoaninformationstoreforfutureuse.
Actionableinformationflowsintobusinessprocesses
thatimplementanactionplan.
ActionplanspushcontextinformationaboutVirtual
EntitiestoassociatedIoTServices,tocorresponding
ActuationResources,andfinallytotherealactuators
thatperformthechangesinthephysicalworld
23

24. Informationhandling
AnIoTsystemistypicallydeployedtomonitorand
controlPhysicalEntities.
MonitoringandcontrollingPhysicalEntitiesisinturn
performedbymainlytheDevices,Communication,IoT
Services,andVirtualEntityFGsinthefunctionalview.
ThepresentationofinformationhandlinginanIoT
systemassumesthatFCsexchangeandprocess
information.
TheexchangeofinformationbetweenFCsfollowsthe
interactionpatternsasshowninnextslide
24

25. InformationHandling
25

26. InformationHandling
Push:AnFCApushestheinformationtoanotherFCB
providedthatthecontactinformationofthecomponentBis
alreadyconfiguredincomponentA,andcomponentB
listensforsuchinformationpushes.
Request/Response:AnFCAsendsarequesttoanotherFC
BandreceivesaresponsefromBafterAservestherequest.
TypicallytheinteractionissynchronousinthesensethatA
mustwaitforaresponsefromBbeforeproceedingtoother
tasks,butinpracticethislimitationcanberealizedwith
partsofcomponentAwaiting,andotherpartsperforming
othertasks.
ComponentBmayneedtohandleconcurrentrequestsand
responsesfrommultiplecomponents,whichimposes
certainrequirementsonthecapabilitiesforthedeviceor
thenetworkthathoststheFC.
26

27. InformationHandling
Subscribe/Notify:Multiplesubscribercomponents(SA,SB)can
subscribeforinformationtoacomponentC,andCwillnotifythe
relevantsubscriberswhentherequestedinformationisready.
Thisistypicallyanasynchronousinformationrequestafterwhicheach
subscribercanperformothertasks.
Nevertheless,asubscriberneedstohavesomelisteningcomponentsfor
receivingtheasynchronousresponse.
ThetargetcomponentCalsoneedstomaintainstateinformationabout
whichsubscribersrequestedwhichinformationandtheircontact
information.
TheSubscribe/Notifypatternisapplicablewhentypicallyone
componentisthehostoftheinformationneededbymultipleother
components.
ThenthesubscribersneedonlyestablishaSubscribe/Notify
relationshipwithonecomponent.
Ifmultiplecomponentscanbeinformationproducersorinformation
hosts,thePublish/Subscribepatternisamorescalablesolutionfrom
thepointofviewofthesubscribers.
27

28. InformationHandling
Publish/Subscribe:InthePublish/Subscribe(also
knownasaPub/Subpattern),thereisathird
componentcalledthebrokerB,whichmediates
subscriptionandpublicationsbetweensubscribers
(informationconsumers)andpublishers(or
informationproducers).
SubscriberssuchasS
AandS
Bsubscribetothebroker
abouttheinformationtheyareinterestedinby
describingthedifferentpropertiesoftheinformation.
Publisherspublishinformationandmetadatatothe
broker,andthebrokerpushesthepublished
informationto(notification)thesubscriberswhose
interestsmatchthepublishedinformation.
28

29. Real-WorldDesignConstraints
TheIoTallowsforthedevelopmentofnovelapplicationsin
allimaginablescenarios.
ThetechnicaldesignofanyM2MorIoTsolutionrequiresa
fundamentalunderstandingofthespecificityofthe
intendedapplicationandbusinessproposition,inaddition
toheterogeneityofexistingsolutions.
Developinganend-to-endinstanceofanM2MorIoT
solutionrequiresthecarefulselection,andinmostcases,
developmentofanumberofcomplementarytechnologies.
Thiscanbebothadifficultconceptualproblemand
integrationchallenge,andrequirestheinvolvementofthe
keystakeholder(s)onanumberofconceptualand
technologicallevels.
29

30. Devicesandnetworks
devicesthatformnetworksintheM2MAreaNetwork
domainmustbeselected,ordesigned,withcertain
functionalityinmind.
Ataminimum,theymusthaveanenergysource(e.g.
batteries,increasinglyEH),computationalcapability
(e.g.anMCU),appropriatecommunicationsinterface
(e.g.aRadioFrequencyIntegratedCircuit(RFIC)and
frontendRFcircuitry),memory(programanddata),
andsensing(and/oractuation)capability.
Thesemustbeintegratedinsuchawaythatthe
functionalrequirementsofthedesiredapplicationcan
besatisfied
30

31. Functionalrequirements
Specificsensingandactuatingcapabilitiesarebasicfunctional
requirements.
Ineverycasewiththeexceptionofdevicesthatmightbe
deployedasaroutingdeviceinthecaseofrangeissuesbetween
sensingand/oractuatingdevicesthedevicemustbecapableof
sensingorperceivingsomethinginterestingfromthe
environment.
Thisisthebasisoftheapplication.Sensors,broadlyspeaking,are
difficulttocategorizeeffectively.
Selectingasensorthatiscapableofdetectingaparticular
phenomenonofinterestisessential.Thesensormaydirectly
measurethephenomenonofinterest(e.g.temperature),ormay
beusedtoderivedataorinformationaboutthephenomenonof
interest,basedonadditionalknowledge(e.g.alevelofcomfort).
Sensorsmaysenseaphenomenonthatislocal(i.e.ameter
detectingtotalelectricityconsumptionofaspace)ordistributed
(e.g.theweather).
31

32. Sensingandcommunicationsfield
Thesensingfieldisofimportancewhenconsideringboth
thephenomenontobesensed(i.e.Isitlocalordistributed?)
andthedistancebetweensensingpoints.
Thephysicalenvironmenthasanimplicationonthe
communicationstechnologiesselectedandthereliabilityof
thesysteminoperationthereafter.
Devicesmustbeplacedincloseenoughproximityto
communicate.
Wherethedistanceistoogreat,routingdevicesmaybe
necessary.
Devicesmaybecomeintermittentlydisconnectedduetothe
timevarying,stochasticnatureofthewirelessmedium.
Certainenvironmentsmaybefundamentallymoresuitedto
wirelesspropagationthanothers
32

33. Programmingandembeddedintelligence
DevicesintheIoTarefundamentallyheterogeneous.
Anapplicationprogrammermustconsiderthe
hardwareselectedordesigned,anditscapabilities.
Theabilitytoreconfigureandreprogramdevicesisstill
anunresolvedissuefortheresearchcommunityin
sensornetworks,M2M,andtheIoT.
33

34. Power
PowerisessentialforanyembeddedorIoTdevice.
Dependingontheapplication,powermaybeprovided
bythemains,batteries,orconversionfromenergy
scavengers(oftenimplementedashybridpower
sources).
Thepowersourcehasasignificantimplicationonthe
designoftheentiresystem.
34

35. Non-functionalrequirements
Thereareanumberofnon-functionalrequirementsthatneedtobe
satisfiedforeveryapplication.Thesearetechnicalandnon-
technical:
Regulations
Forapplicationsthatrequireplacingnodesinpublicplaces,
planningpermissionoftenbecomesanissue.
RadioFrequency(RF)regulationslimitthepowerwithwhich
transmitterscanbroadcast.
Easeofuse,installation,maintenance,accessibility
Physicalconstraints
Cantheadditionalelectronicsbeeasilyintegratedintothe
existingsystem?
Aretherephysicalsizelimitationsonthedeviceasaresultofthe
deploymentscenario?
WhatkindandsizeofantennacanIuse?
WhatkindofpowersupplycanIusegivensizerestrictions
35

36. Non-functionalrequirements
Financialcost
Financialcostconsiderationsareasfollows:
ComponentSelection:Typically,theuseofthese
devicesintheM2MAreaNetworkdomainisseento
reducetheoverallcostburdenbyusingnon-leased
communicationsinfrastructure.
IntegratedDeviceDesign:Oncetheenergy,sensors,
actuators,computation,memory,power,connectivity,
physical,andotherfunctionalandnon-functional
requirementsareconsidered,itislikelythatan
integrateddevicemustbeproduced.
36

37. M2MServiceOrientedArchitecture(SOA)-
basedintegration
TheService-OrientedArchitecture(SOA)paradigmcan
actasaunifyingtechnologythatspansseverallayers,
fromsensorsandactuatorsusedformonitoringand
controlatshop-floorlevel,uptoenterprisesystems
andtheirprocessesasenvisionedinthediagram.
Thiscommon“backbone”meansthatM2Misnot
limitedtodirect(e.g.proximity)deviceinteraction,but
includesawiderangeofinteractionsinacross-layer
waywithavarietyofheterogeneousdevices,aswellas
systemsandtheirservices.
Thisyieldsmultiplebenefitsforallstakeholders
involved.
37

38. M2MServiceOrientedArchitecture
(SOA)-basedintegration
38

39. M2MServiceOrientedArchitecture
(SOA)-basedintegration
InternetProtocol(IP)-based,andmorespecificallyweb
technologiesandprotocols(e.g.OPC-UA,DPWS,REST,
WebServices(WS),etc.),constituteapromising
approachtowardsthefundamentalgoalofenabling
easyintegrationofdevice-levelserviceswith
enterprisesystemsovercomingtheheterogeneityand
specificimplementationofhardwareandsoftwareof
thedevice.
Surelyindustryspecificrequirementsforsecurity,
resilience,andavailabilityofnearreal-timeevent
informationneedstobeeffectivelytackled.
39

40. M2MServiceOrientedArchitecture
(SOA)-basedintegration
TheSOA-basedvisionisnotexpectedtoberealized
overnight,butmaytakeaconsiderabletimedepending
onthelifecycleprocessesofthespecificindustry,and
maybeimpactedbymicro-andmacro-economic
aspects.
Hence,itisimportantthatmigrationcapabilitiesare
providedsothatwecanharvestsomeofthebenefits
todayandprovideastepwiseprocesstowards
achievingthevision.
40

41. Socrades: realizing the enterprise integrated Web of Things
TheSOCRADESprojectisaEuropeanresearchandadvanced
developmentproject.Itsprimaryobjectiveistodevelopadesign,
executionandmanagementplatformfornext-generationindustrial
automationsystems,exploitingtheServiceOrientedArchitecture
paradigmbothatthedeviceandattheapplicationlevel.
SOCRADESisapartoftheInformationSocietyTechnologies
(IST)initiativeoftheEuropeanUnion's6thFrameworkProgramme.
Socradesisdrivenbythekeyneedforcross-layerM2Mcollaboration
(i.e.atshop-floorlevelamongvariousheterogeneousdevicesaswellas
amongsystemsandservicesuptotheEnterprise(ERP)level),
SOCRADESproposedandrealizedSOA-basedintegration,including
migrationofexistinginfrastructureviagatewaysandservicemediators
TheSOCRADESIntegrationArchitecture(SIA),enablesenterprise-level
applicationstointeractwithandconsumedatafromawiderangeof
networkeddevicesusingahigh-level,abstractinterfacethatfeatures
WebServicesstandards.
41

42. Socrades
VariouslevelsinSocradesare:
ApplicationInterface:Thispartenablestheinteraction
withtraditionalenterprisesystemsandotherapplications.
Itactsastheglueforintegratingtheindustrialdevices,and
theirdataandfunctionalitieswithenterprisereposand
traditionalinformationstores.
ServiceManagement:Functionalitiesofferedbythe
devicesaredepictedasservicesheretoeasetheintegration
intraditionalenterpriselandscapes.
Toolsfortheirmonitoringareprovided.
DeviceManagement:Includesmonitoringandinventory
ofdevices,includingservicelifecyclemanagement.
42

43. 43

44. Socrades
PlatformAbstraction:Thislayerenablesthe
abstractionofalldevicesindependentofwhetherthey
nativelysupportWSornot,tobewrappedand
representedasservicesonthehighersystems.
Inadditiontoservice-enablingthecommunication
withdevices,thislayeralsoprovidesaunifiedviewon
remotelyinstallingorupdatingthesoftwarethatruns
ondevices.
Devices&Protocols:Theselayersincludetheactual
devicesthatconnectovermultipleprotocolstothe
infrastructure.
Therespectivepluginsofcourseneedtobeinplaceso
thattheycanbeseamlesslyintegratedtoSIA.
44