Wilamowski B.M., Irwin J.D. The Industrial Electronics Handbook. Second Edition: Industrial Communication Systems

Подождите немного. Документ загружается.

Multimedia Service Convergence 14-9

Discovery

Query

Identication

Invocation

PLUGIN ID

Lookup proxy

Description

Initialise

Entry point

Terminate

Identity properties

Available services

Voice plugin

Identity properties

Available services

Name

Description

Initialise

Entry point

Terminate

…

Name

FIGURE 14.6 Voice.plugin.

At home

At work

Driving PDA

Out and about

Desktop computer

Media convergence centre (MC

)

In a meeting

Notebook vNews

vWeather

vStocks

vFinance

E-mail server

Finance DB

Australian Stock

Exchange

Bureau of

meterology

News feed

RSS

vE-mail

Mobile phone

Telephone

FIGURE 14.5 Converged.voice.access.to.data.solution.

14-10 Industrial Communication Systems

number.or.unique.serial..Upon.activation.and.during.execution,.each.voice.plugin.governs.user.interac-

tion

.and.the.provision.of.its.convergence.services.

.plugin.architecture.denes.the.following.component.interfaces:

•

. Plugin Discovery—Plugin.discovery.is.used.to.nd,.identify,.describe,.and.use.available.voice.

plugins..In.order.to.locate.plugins,.the.MC

.Interact.server.broadcasts.a.request.for.a.voice.plugin.

lookup.service..Each.voice.plugin.responds.to.this.request.with.a.lookup.proxy.

•

. Plugin Query— e.MC

.Interact.host.is.able.to.query.the.voice.plugin.lookup.service.for.avail-

able

.services.

•

. Plugin Identication— e. voice. plugin. lookup. service. is. used. to. dene. voice. plugin.

characteristics.

•

. Plugin Invocation—When.a.voice.plugin.is.selected.via.the.IVR,.the.MC

.Interact.host.dynami-

cally

.binds.to.the.voice.plugin.and.invokes.its.entrypoint.. e.voice.plugin.then.takes.over.inter-

action

.control.and.performs.its.identied.services.

Figure

.14.7.illustrates.a.high-level.composition.of.the.MC

.Interact.system.with.sample.voice.plugin.

services.(vE-mail,.vFinance,.vStocks,.vWeather,.and.vNews).

.Interact.is.constructed.from.a.number.of.lower.level.voice.plugins.(Figure.14.7).that.are.fully.

composed.business.modules.. e.diagram.below.illustrates.the.high-level.RVAD.application.solution.

with.a.set.of.sample.business.modules.

Business

.modules.(Figure.14.8).represent.voice.plugins.that.typically.perform.a.single.converged.ser-

vice.

.Such.business.modules.utilize.groups.of.component.compositions.. e.high-level.diagram.below.

illustrates.the.vE-mail.business.module.that.is.constructed.from.multiple.lower-level.generic.compo-

nents

.that.are.reused.in.other.business.module.compositions.

Customized

.voice.plugins.are.constructed.by.mixing.and.matching.hierarchically.interconnected.

components.

14.5.3 Converged Voice Plugins

•. vE-Mail Service—E-mails.can.be.accessed.at.any.time.and.followed.up.instantly.. e.vE-mail.

voice.plugin.hosts.a.post.oce.protocol.(POP).e-mail.service.where.high-priority.e-mails.can.be.

forwarded.for.voice.access.. e.vE-mail.voice.plugin.reads.out.each.e-mail.using.a.clear.voice..

 e.user.may.interact.with.the.vE-mail.voice.plugin.by.telephone.key.tones..MC

.Interact.allows.

vE-mail

module

vFinance

module

Enterprise java beans

Voice access to data

application solution

vStocks

module

vWeather

module

vNews

module

FIGURE 14.7 Application.solution.

Multimedia Service Convergence 14-11

the.automatic.browsing.of.e-mails.without.user.intervention..It.is.possible.to.reply.to.e-mails.with.

predened.e-mail.templates.and.forward.messages.to.predened.contacts.immediately..Users.

may.manage.their.e-mail.messages.by.saving,.moving,.and.deleting.selected.items..It.is.also.pos-

sible

.to.customize.the.way.that.the.system.performs.and.to.manage.e-mail.contacts.and.template.

messages.via.an.easy-to-use.Web.interface.

•

. vStocks Service—Live.Australian.Stock.Exchange.(ASX).values.can.be.heard.at.the.user’s.conve-

nience.

. e.vStocks.service.reads.out.detailed.information.on.each.user’s.individually.predened.

stocks..Stock.list.navigation.is.performed.using.telephone.key.tones..MC

.Interact.allows.the.

browsing.of.stock.data.without.user.intervention.. e.vStocks.service.is.able.to.announce.each.

stock’s.trade.date,.time,.change,.previous.close,.day.high,.day.low,.and.volume..Users.may.cus-

tomize

.the.stock.properties.they.wish.to.hear.to.suit.their.individual.preferences.

•

. vWeather Service—Live.Bureau.of.Meteorology.(BOM).weather.forecasts.can.be.accessed.at.any.

time.. e.vWeather.service.reads.out.detailed.weather.information.for.a.user’s.predened.city.or.

town..Weather.forecasts.are.read.out.for.up.to.one.week.in.advance..Forecast.information,.days.

high,.and.days.low.are.given.for.each.day..Users.may.customize.their.city.to.suit.their.individual.

preferences.and.travel.arrangements..MC

.Interact.allows.the.weekly.weather.forecast.to.be.read.

out.without.user.intervention.

•

. vNews Service—Live.Rich.Site.Summary.(RSS).news.feeds.can.be.heard.at.a.preferred.occasion.

based.on.a.user’s.preference.. e.vNews.service.reads.out.each.news.item.as.requested.by.the.user’s.

telephone.key.tone.interaction.or.automatically.

14.6 Conclusion

Widespread.use.of.mobile.computing.devices,.telephones.along.with.Internet.services.has.resulted.in.a.

broad.range.of.ways.to.access.information.and.to.communicate..However,.true.voice.and.data.conver-

gence

.has.been.isolated.to.the.use.of.various.soware.tools.that.simulate.a.pseudo-converged.environ-

ment.

.Converged.services.that.are.accessible.anywhere.and.anyhow.promise.increased.productivity,.

Web interface

Composition layer L

Composition layer 2

Composition layer 1

Component layer

E-mail

manager

Database

interface

Session

manager

Voice

interface

Audio encoding/

decoding

AT&T TTS

vE-mail

module

FIGURE 14.8 Business.module.

14-12 Industrial Communication Systems

reduced.costs,.and.new.opportunities.and.revenues.for.enterprises..A.versatile.approach.is.required.to.

pro

duce

.a.sol

ution

.to.thi

.pro

blem.

. is.cha

pter

.pre

sents

.an.MC

-driven.proposal.and.MC

.Interact.

imp

lementation

.tha

.use

.a.rec

ongurable

.plu

.and.pla

.so

ware

.arc

hitecture

.and.pla

tform

.to.dyn

ami-

cally

.com

pose,

.int

egrate,

.and.tai

lor

.con

vergence

.app

lications.

. is.comb

ination

.red

uces

.dev

elopment

and.int

egration

.com

plexity,

.eo

rt,

.and.cos

.whi

.enh

ancing

.int

eraction

.ee

ctiveness,

.ex

ibility,

.and.

con

venience

.fo

.pr

ofessionals

.on.th

.mo

ve.

references

. 1.. C..R..Strathmeyer,.An.introduction.to.computer.telephony,.IEEE Communications Magazine,.35(5),.

May.1996,.106–111.

. 2.. B..Benner

. Com

puter

. Telep

hony

. Int

egration

. (CTI). Ind

ustry,

. On-line. at:.htt

p://faculty.ed.umuc.

edu/~meinkej/inss690/benner/CTIpaper.htm

.(2009).

. 3.. R..Dar

lington,

.Wha

.is.mul

timedia

.conv

ergence

.and.why.is.it.so.impo

rtant,

.On-line.at:.htt

p://www.

rogerdarlington.co.uk/Multimediaconvergence.html

.(2007).

. 4.. S..Phi

.an

.F..Ca

ry,

.Yo

.Do

n’t

.Kn

.Jac

.Ab

out

.VoIP

.Qu

eue,

.2(6),.2004,.30–38.

. 5.. W..Sta

llings,

.Dat

a and Computer Communications

.(7t

.Ed.

.Pea

rson

.Edu

cational

.Int

ernational,

.200

. 6.. Delo

itte,

.Gett

ing

.o.the.gro

und:

.Why.the.mov

.to.VoIP.is.a.decisio

.for.all.CXOs,.On-line.at:.htt

p://

www.deloitte.com/dtt/budget/0,1004,cid%253D67263,00.html

.(2009).

. 7.. M..Gra

nt,

.Voi

ce Quality Monitoring for VoIP Networks,

.Cal

yptech

.Pty

.Ltd

.Mel

bourne,

.Aus

tralia,

.200

. 8.. M..C..Hui.and.H..S..Mat

thews,

.Com

parative

.ana

lysis

.of.tra

ditional

.tel

ephone

.and.voi

ce-over-Internet

pro

tocol

.(Vo

IP)

.sys

tems,

.in.Pro

ceedings of the IEEE International Symposium on Electronics and the

Environment,

.200

. 9.. ATP. FOCUSED. PRO

GRAM:

. Com

ponent-Based

. So

ware,

. On-line. at:. htt

p://www.atp.nist.gov/

focus/cbs.htm

.(2009).

. 10.. M..Doa

ne,

. e.Over

whelming

.Fai

lure

.of.Go-It-A

lone

.CRM,.Meta.Gro

up,

.On-line.at:.htt

p://www.

metagroup.com/us/displayArticle.do?oid=35932

.(2002).

. 11.. I..Somm

erville,

.G..Dewsb

ury,

.K..Cla

rke,

.and.M..Roun

ceeld,

.Depen

dability

.and.tru

.in.orga

nisa-

tional

.and.domestic.computer.systems,.in.Trust in Technology: A Socio-technical Perspective,.Kluwer,.

2004.

. 12.. D..Par

nas,

. e.inuence.of.so

ware

.str

ucture

.on.reli

ability,

.in.Cur

rent Trends in Programming

Methodology: Soware Specication and Design,

.Pr

entice-Hall,

.Eng

lewood

.Clis,.NJ,.1977.

. 13.. G..Boo

ch,

.Obje

ct-Oriented Analysis and Design with Applications

.(2nd.Ed.),.Benj

amin/Cummings,

Red

wood

.Cit

.CA,.1994.

. 14.. A..Tale

vski,

.E..Cha

ng,

.and.T..Dillo

.Re-congura

ble

.web.serv

ices

.for.extende

.logis

tics

.enter

prise,

IEEE Tra

nsaction on Industrial Informatics,

.1(2),.74–84,.Ma

.2005.

. 15.. A..Mor

ch,

.re

e Levels of End-User Tailoring: Customisation, Integration, and Extension, Computers

and Design in Context,

. e.MIT.Pr

ess,

.Ca

mbridge,

.MA,.pp

.51–76,.1997.

. 16.. A..Tal

evski,

.E..Cha

ng,

.and.T..Dil

lon,

.Con

verged

.voi

.acc

ess

.to.dat

.(CV

AD),

.in.Pro

ceedings of the

International Conference on Convergence Information Technology,

.Gye

ongju,

.Kor

ea,

.Nov

ember

.200

15-1

15.1 Introduction

Various.tendencies.inuence.the.development.of.industrial.communications:

•

. Indu

strial

.auto

mation

.pro

jects

.bec

ome

.mor

.com

plex

•

. e.oe

red

.com

munication

.tec

hnologies

.bec

ome

.mor

.com

prehensive

•

. Stron

ger

.int

egration

.of.ent

erprise

.(bu

siness)

.and.pla

.auto

mation

•

. Striv

ing

.for.non

-interrupted

.eng

ineering

.and.tool.cha

ins

Future

.scena

rios

.of.dist

ributed

.auto

mation

.lead.to.desi

red

.mecha

nisms

.for.geog

raphically

.dist

ributed

auto

mation

.func

tions

.due.to.vario

.reaso

ns:

•

. Cent

ralized

.sup

ervisory

.and.con

trol

.of.(ma

ny)

.dec

entralized

.(sm

all)

.tec

hnological

.pla

nts

•

. Remote.control,.commissioning,.parameterization,.and.maintenance.of.distributed.automation.

syst

ems

•

. Incl

usion

.of.remo

.expe

rts

.or.exte

rnal

.mach

ine-readable

.know

ledge

.for.the.plan

.oper

ation

.and.

main

tenance

Since

.the.infr

astructure

.for.the.oce.autom

ation

.as.well.as.for.the.facto

.and.proc

ess

.autom

ation

are.merg

ing,

.all.the.adva

ntages

.but.also.draw

backs

.of.Ether

net-TCP/IP

.have.to.be.take

.unde

.consi

der-

ation.

. e.comm

unication

.infr

astructure

.is.beco

ming

.more.and.more.hete

rogeneous.

. us,.this.can.be.

char

acterized

.by.the.expr

ession

.“het

erogeneous

.netw

orking.”

. e.end-

to-end

.comm

unication

.betw

een

geog

raphically

.dist

ributed

.autom

ation

.func

tions,

.perf

ormed

.in.devi

ces

.with.larg

.dist

ances

.betw

een

them,.is.becoming.increasingly.important.. e.data.has.to.pass.through.a.chain.of.very.dierent.types.

of.comm

unication

.tech

nologies

.(cir

cuit

.or.pack

.swit

ched,

.wire

.or.wire

less,

.prov

ider

.orie

nted

.or.pro-

ider

.less

.publ

.or.priv

ate,

.etc.

. e.grow

ing

.comp

lexity

.of.the.nece

ssary

.indu

strial

.comm

unications

led.in.the.past.to.die

rent

.tech

nical

.appr

oaches.

.In.the.eld

bus

.tech

nology,

.die

rent

.eld

bus

.netw

orks

Virtual Automation

Networks

15.1. Introduction.....................................................................................15-1

15.2

. Virt

ual

.Auto

mation

.Net

work:

.Basi

cs...........................................15-3

Domains. •. Components. •. VAN.System.Architecture

15.3. Name-Based.Addressing.and.Routing,.Runtime.Tunnel.

Esta

blishment...................................................................................15-7

15.4

. Main

tenance

.of.the.Run

time

.Tun

nel

.Bas

onQua

lity-of-Service

.Mon

itoring

.and.Pro

vider

.Swi

tching.....15-9

15.5

. VAN.Tel

econtrol

.Pro

le...............................................................15-11

Abbreviations.............................................................................................15-13

References................................................................................................... 15-14

Peter Neumann

Institute for Automation

and Com

munication

Ralf Messerschmidt

Institute for Automation

and Com

munication

15-2 Industrial Communication Systems

have.been.coupled.by.specic.link.devices.. us,.dierent.transmission.technologies,.particularly.for.

various.application.areas,.could.be.used.in.a.complex.application..For.example,.as.shown.in.Figure.15.1,.

PROFIBUS-PA.using. intrinsic-safe.and.non-intrinsic-safe. eldbus. parts,. coupled.via.link. devices.

(DP/PA.segment.coupler),.mapping.dierent.stack.layers.and.application.object.models.

.Ethernet-based.eldbus.technology.(e.g.,.PROFINET.[IEC61158,IEC61784]).opened.the.oppor-

tunity

.to.integrate.real-time.Ethernet.approaches.into.Oce.and.Internet.applications,.and.thereby.the.

real-time.Ethernet.approaches.opened.the.possibility.to.integrate.dierent.eldbus.technologies..As.a.

result,.PROFINET.network.serves.as.an.automation.backbone.and.enables.the.connection.of.various.

eldbus.systems.with.dierent.eldbus.technologies.and.the.exchange.of.data.between.the.eldbus-

specic

.application.objects.[PIP].(Figure.15.2).

 ere

.are.various.integration.concepts.(e.g.,.in.terms.of.PROFINET).and.integration.mechanisms.

(mapping. of. layer. functions,. proxy. concept,. mapping. of. application. objects. between. eldbus. and.

PROFINET,.and.architecture.of.necessary.link.devices):

•

. Transparent integration:.Each.eldbus.device.(including.its.data.objects).will.be.mapped.to.one.

PROFINET-IO.device.

•

. Modular integration:.Each.eldbus.device.(including.its.data.objects).will.be.mapped.to.a.module.

of.a.PROFINET-IO.device.

•

. Compact integration:.A.complete.eldbus.system.(including.its.data.objects).will.be.mapped.to.

a.module.of.a.PROFINET-IO.device.

 ese

.integration.concepts.have.been.focused.on.locally.concentrated.industrial.communications.

and.include.the.opportunity.to.integrate.the.plant.automation.world.into.the.oce.automation.and.

Internet.application.world.

.next.step.to.handle.the.growing.complexity.of.automation.systems.(geographically.distributed.

applications)

.requires.the.use.of.heterogeneous.wide.area.networks.(WANs).[CPP06].

Host/FPLC

Standard-I/O

Actuator

PROFIBUS-PA physics

Field deviceField deviceField device

Sensor

PROFIBUS DP physics

DP/PA

segment

coupler

Engineering

Host/PLC

Repe

ater

FIGURE 15.1 Coupling.of.dierent.eldbus.technologies.(physics).using.link.devices.

Virtual Automation Networks 15-3

A.heterogeneous.network.has.to.handle.dierent.classes.of.application.data.(application.classes):

•

. Decentralized.periphery.applications

•

. Real-time.applications/control.loops.(networked.control)

•

. Component-based.applications

•

. Telecontrol.(TC).applications

•

. Teleservices

For

.these.application.classes,.different.requirements.and.opportunities.exist..Limitations.are,.

e.g.,.regarding.isochronous.and.hard.real-time.communication.caused.by.the.performance.of.het-

erogeneous

.networks..The.next.sections.give.an.introduction.into.the.problems.to.be.solved.and.

into.the.developed.concept..The.main.idea.is.to.connect.the.local.industrial.communication.sys-

tems

.(e.g.,.PROFINET.as.automation.backbone.connected.with.different.fieldbus.systems.following.

the.mentioned.integration.concept).via.tunnel.through.the.heterogeneous.WAN.with.one.or.more.

remote.industrial.communication.system.

15.2 Virtual automation Network: Basics

In.a.geographically.distributed.automation.project,.various.local.and.remote.installations.based.on.

eldbus.communication,.connected.by.a.heterogeneous.WAN,.exist..In.virtual.automation.networks.

(VANs),.the.distributed.automation.function.(local.and.remote.parts).forms.a.domain.(Figure.15.3),.

containing.all.installed.equipment.to.realize.these.automation.functions.. us,.a.VAN.domain.covers.

all.devices.that.shall.be.grouped.together.on.a.logical.or.virtual.basis.to.represent.a.complex.application..

Depending.on.the.complexity.of.the.automation.function,.a.hierarchical.domain.approach.makes.sense..

It.means.that.there.are.also.domains.and.subdomains.that.can.consist.of.subdomains,.etc..Consequently,.

IO device

Controller

IO device

proxy

master

PROFINET

engineering

proxy

master

FB slave

PROFIBUS

slave

PROFIBUS

slave

PROFIBUS

slave

PROFIBUS

slave

PROFINET

Fieldbus

PROFIBUS DP

Linking

device

Linking

device

GSDML

FIGURE 15.2 Integration.of.eldbus.systems.by.PROFINET.(IO,.input/output;.FB,.eldbus;.PB,.PROFIBUS;.DP,.

decentral.periphery).

15-4 Industrial Communication Systems

within.a.domain.(or.subdomain),.one.or.more.automation.devices.(ADs),.eldbus.systems,.and.infra-

structure

.components.exist..A.domain.keeps.track.of.engineered.relations.between.VAN.devices.that.

are.the.end.points.of.a.congured.communication.line.between.the.local.domain.and.the.related.other.

domain.[DHH08].. e.connected.end.points.are.linked.via.a.tunnel,.which.seems.to.be.a.(virtual).

communication.line.between.the.distributed.application.objects.(runtime.objects)..Once.the.tunnel.has.

been.established,.the.data.exchange.between.the.distributed.runtime.objects.follows.the.rules.of.the.

used.eldbus.system.(e.g.,.PROFINET.with.connected.PROFIBUS.or.other.connected.eldbus.systems)..

 ese.rules.are.well.known.by.the.automation.engineer.

All

.devices.with.the.same.object.model.can.interact.by.using.the.VAN.infrastructure..As.an.example,.

the.standardized.runtime.object.model.of.PROFINET.[IEC61158,IEC61784].can.be.used.as.a.common.

object.denition..Within.the.VAN.device.architecture.also,.other.object.models.can.be.used.if.they.are.

based.on.the.VAN.communication.stack..Devices.with.other.object.models.can.be.connected.through.a.

VAN.proxy.device.(VAN-PD).

15.2.1 Domains

To.connect.distributed.application.objects,.a.VAN.infrastructure,.which.oers.VAN.characteristics,.is.nec-

essary.

. e.VAN.characteristics.are.dened.for.domains.[PNO05,N07].. e.expression.“domain”.is.widely.

used.to.address.areas.and.devices.with.common.application.purposes.(Figure.15.3)..A.domain.is.a.logical.

group.of.VAN.devices.. e.devices.related.to.a.VAN.domain.may.reside.in.a.homogeneous.network.domain.

(e.g.,.local.industrial.domain)..However,.depending.on.the.application,.additional.VAN-relevant.devices.may.

be.only.reached.by.crossing.other.network.types.(e.g.,.by.WAN.type.communication).or.they.need.to.use.

proxy.technology.to.be.represented.in.the.VAN.domain.view.of.a.complex.application.

.VAN.domain.can.include.given.industrial.domains.(equipped.with.ADs.and.connected.via.indus-

trial

.communications,.e.g.,.eldbus),.completely.or.partially.. us,.an.industrial.domain.can.consist.of.

segments.related.to.a.VAN.domain.(VAN.segment).or.of.segments.that.are.not.related.to.a.VAN.domain.

(Figure.15.3).[N08].

Remote industrial domains/subsidiary/customer sites

Office subdomains

Office domain

Industrial domain

Intrinsic safety

domain

Individual industrial subdomains

Remark

All systems are shown generally as a bus. Depending on the real system

it may be any type of topology including a ring.

Public and private

telecommunication

networks/Iinternet

Real-time domain

Mobile devices

Industrial backbone

Single device integration

(e.g., tele control)

Industrial WLAN domain

Real-time domain

Mobile devices

VAN domain C

Industrial

WLAN domain

Industrial segment

Domain

converted

via ra

Van domain B

VAN domain A

FIGURE 15.3 Dierent.VAN.domains.related.to.dierent.automation.applications..(From.Specication.of.the.

Open. Platform.for.Automation.Infrastructure,.Deliverable.D02.2-1.. Topology. Architecture. for.the. VAN..Virtual.

Automation. Domain..European.Integrated. Project. VAN.FP6/2004/IST/NMP/2-016969.VAN. Virtual.Automation.

Networks,.2006..With.permission.)

Virtual Automation Networks 15-5

15.2.2 Components

 ere.are.two.groups.of.VAN.components.[NPM08,SOP06]:

•

. VAN infrastructure components:.VAN.access.point.(VAN-AP),.VAN.gateway.(VAN-GW),.VAN.

server.device.(VAN-SVD),.VAN. security.infrastructure.device. (VAN-SID),.VAN.engineering.

station.

•

. Automation-specic VAN components:.VAN.automation.device.(VAN-AD),.VAN-PD,.VAN.virtual.

device.(VAN-VD).

.infrastructure.components.enable.the.establishment.and.maintenance.of.the.tunnel.between.distrib-

uted

.application.objects.(runtime.objects).. e.automation-specic.components.are.VAN-enabled.ADs.

.VAN-AP,.the.most.important.infrastructure.component,.connects.VAN.network.segments..It.does.

not.contain.an.automation.function.or.an.automation.application.process..It.can.work.as.a.gateway.or.

a.router.to.ADs.that.are.members.in.a.VAN.application.context.(VAN.domain).. us,.a.VAN-AP.may.

handle.dierent.transmission.technologies,.contains.all.relevant.administration.functions.(necessary.

for.conguration.and.parameter.setting.in.connected.subnetworks)..It.enables.the.switching.between.

available.communication.paths.and.nds.the.best.transmission.technology.and.the.best.route.through.

the.dierent.subnetworks.of.the.heterogeneous.network.

Within

.a.VAN.domain,.there.are.dierent.opportunities.how.any.AD.can.participate.in.a.VAN.network.

(Figure.15.4):

•

. By.integrating.the.VAN.communication.capabilities.at.the.AD.itself.(VAN-AD)

•

. By.connecting.a.single.device.via.a.separate.VAN.gateway.device

•

. By.connecting.the.whole.network.segment.(e.g.,.connecting.the.ADs.using.any.industrial.com-

munication

.system/eldbus).through.a.VAN-PD.and.mapping.its.application.objects.to.the.VAN.

object.pool.that.its.parts.(VAN-VD).can.be.exchanged.within.the.VAN.domain

Fieldbus

network with

several devices

FD1

FD2

FD3

FD5

FD4

FD1

FD2

FD5

FD1, 2, 5 are VAN-virtual devices (VAN aware)

FD3, 4 are not visible in VAN (VAN independent)

VAN-VDs

VAN-PD

VAN

VAN-AD

Automation

function

Industrial comm.

capability

Automation

function

VAN network

capability

VAN network

capability

FIGURE 15.4 Automation-specic.components.(AD,.automation.device;.PD,.proxy.device;.VD,.virtual.device;.

FD,.eld.device).

15-6 Industrial Communication Systems

 e.proxy.functionality.enables.the.representation.of.the.eld.device.(FD).application.data.in.context.

of.the.object.model.used.in.the.VAN.domain.. is.mechanism.also.allows.all.relevant.devices’.data.of.a.

certain.physical.device.without.VAN.capabilities.to.be.represented.as.a.VAN-VD.. is.device.is.visible.

within.the.VAN.domain,.although.it.has.not.been.connected.to.the.VAN.directly.

.can.be.seen.that.the.VAN-AD.and.the.VAN-PD.oer.an.integration.path.to.combine.dierent.

communication.technologies.in.a.given.automation.application,.thus.to.handle.the.heterogeneity.of.

participating.communication.networks.

15.2.3 VaN System architecture

 e.properties.of.a.VAN.can.be.represented.by.a.block.scheme.(Figure.15.5)..Blocks.are.logical.components.

oering.specic.VAN.functionality.

Single

.devices.do.not.oer.all.possible.properties,.since.they.are.context.specic.. us,.only.the.necessary.

blocks.have.to.be.allocated.to.a.VAN.device,.depending.on.the.device.type.and.communication.prole.

.classify.the.block.functions,.one.can.distinguish

•

. Used.standards.(communication.technologies,.Internet.protocol.suite,.adopted.safety,.security,.

and.time.synchronization.standards)

•

. VAN-specic.functions;.the.conguration.of.these.functions.is.stored.in.application.service.ele-

ments

.(ASEs)

Since

.the.object-oriented.ASEs.contain.the.data.for.the.VAN.functionality,.they.are.crucial.com-

ponents

.of.the.VAN.system.architecture..All.attributes.of.an.ASE.can.be.accessed.via.Web.services.by.

uniformly.dened.Get.and.Set.services.. e.access.rights.are.dened.in.the.access.control.list.(ACL).

VAN system

management

app. proc.

Tunnel

VAN

MIB

Native

VAN common communication

Application service elements (ASEs)

VAN heterogeneous network technologies adaptation layer

VAN network technology layer

To access points, automation- or proxy devices (AP, AD, PD)

VAN communication stack

VAN specic services communication

Technology

standards

AS-Interface,

ZigBee.......

INTERBUS

PROFIBUS

Security

Time

sync.

Web services over virtual

automation networks

Access control list (ACL)

Internet protocolsuite

To Virtual Devices

(VD)

VAN

runtime

object

tunnel

Web

application

VAN autom.

app. proc. 1-n

VAN safety

app. proc.

VAN runtime

object

dispatcher

VAN device- and

network management

VAN

proxy

app. proc.

VAN routing

Routing

Safety layer

Runtime

object model

Runtime

object model

Runtime

object model

object mode

IP address

mapping

Address

mapping

Web server

VAN

PnP

VAN

security

AP 1-n

Param.

Cong.

FIGURE 15.5 VAN.system.architecture.(AP,. application. process;.MIB,.management. information.base)..(From.

Specication.of.the.Open.Platform.for.Automation.Infrastructure,.Deliverable.D02.2-2:.VAN.Open.Platform.API-

Specication,

.European.Integrated.Project.VAN.FP6/2004/IST/NMP/2-016969.VAN.Virtual.Automation.Networks,.

2006..With.permission.)