Upload
vokhuong
View
216
Download
0
Embed Size (px)
Citation preview
Thierry Ernst – February 2008
ISO TC204 WG 16: The CALM Architecture
[email protected] INRIA
IMARA project-team / JRU LARA http://www.lara.prd.fr
Thierry Ernst – February 2008 2
ISO TC204 WG16: CALMISO Technical Committee 204: Currently 12 active WGs
http://www.sae.org/technicalcommittees/tc204wg16.htm
WG 16: Wide Area CommunicationsSince Y 2000 / Led by Russell Shields (Ygomi)CALM: Communication Architecture for Land Mobile
Renamed from Communications Air-interface, Long and Medium rangeDocs:
Web: http://www.calm.huCALM Handbook
7 sub-WGs SWG 16.0: CALM ArchitectureSWG 16.1: CALM MediaSWG 16.2: CALM Network SWG 16.3: Probe DataSWG 16.4: Application ManagementSWG 16.5: Emergency notifications (eCall)SWG 16.6: CALM ad-hoc subsystem
Thierry Ernst – February 2008 3
ISO TC204 WG16: 7 Sub Working Groups
Thierry Ernst – February 2008 4
ISO TC204 WG16: CALM Communication MediaCommunication architecture allowing V2V, V2I and continuous Internet access through multiple radio technologies (potentially used simultaneously)
Media:Cellular (CALM 2G/3G) – cf CD 21212 & CD 21213Infrared light (IR) – cf CD 21214Microwave (CALM M5) – cf CD 21215
IEEE 802.11 a/b/g (WIFI)IEEE 802.11p (mobile WIFI)
Millimeter waves (CALM MM) – cf CD 21216Microwaves CEN DSRC
IPv6:Internet connectivityUnification layer of underlying technologiesStandardized at the IETF to replace IPv4 (current version)2128 available global addresses (instead of 232)
Thierry Ernst – February 2008 5
Variable Message Sign
Hot-Spot(Wireless LAN)
Terrestrial BroadcastRDS, DAB
UMTSWiMAX
Beacon•CALM-M5•CEN-DSRC•CALM-IR
GPS, Galileo
Info-Broadcaster
BroadcastTransmitter
Vehicle-to-Vehicle (M5, IR, MM)
GSM-GPRS
Sat-Comm
PDA, SmartPhone
The generic Comm ArchitectureThe generic Comm Architectureis CALMis CALM
ISO TC204 WG16: CALM Communication Media
Thierry Ernst – February 2008 6
ISO TC204 WG16: Communication Scenarios
Thierry Ernst – February 2008 7
ProprietaryProtocol
B
Proprietaryor
DedicatedRadio
Interface
ProprietaryProtocol
C
Proprietaryor
DedicatedRadio
Interface
ProprietaryProtocol
A
Proprietaryor
DedicatedRadio
Interface
App. 1 App. 2 App. 3ALL ITS
APPLICATIONS
TCP UDP
Stream &RealtimeProtocols
ISODSRC
L7
HTTP/SMTP
Protocols
MAC
802.11pWAVE
InitHnd-ovr
Secur
MAC
2G/3GGSM
InitHnd-ovr
Secur
MAC
IR
InitHnd-ovr
Secur
L2/UDP
…
IPv6 layer
ServiceQoS
Interface Selection
Handover
InterfaceQoS
ISO TC204 WG16: CALM Architecture
Thierry Ernst – February 2008 8
ISO TC204 WG16: CALM Architecture
CALM ARCHITECTURECALM ARCHITECTURE
- Standards that are outside CALM scope- Standards that are outside CALM scope SAP - Service Access Point –Data Transfer
SAP - Service Access Point –Management
Media Function blocks shown above may be partof a more comprehensive communications device.
2G cellular std by reference
CALM 2G ManagerISO 21212
SAP
2G cellular std by reference
CALM 2G ManagerISO 21212
SAP
NetworkingManagementISO 21210-3
CALMsystem
ManagementEntity(CME)
ISO 21210-2
NETWORK INTERFACERouting and Media Switching based on IPv6
ISO 21210-1
Non-CALM-awarePoint-to-point APPLICATIONS
Convergence LayerISO 15628/
ISO 21210-5SAP
CALM-AwareAPPLICATIONS
Layer 5-7INTERNET STANDARDS
SAP
SAP SAP
Common Station,PHY, MAC, LLC
Managers ISO 21210-4
SAP
SAP
SAP
SAP
Directory ServicesISO 21210-5 SAP
SAP
Non-CALM-awareIP (Internet)
APPLICATIONS
Convergence LayerIP socket/
ISO 21210-5SAP
SAPSAP
SAP
CALM MM
CALM MM ManagerISO 21216
SAP
CALM MM
CALM MM ManagerISO 21216
SAP
CALM M5
CALM M5 ManagerISO 21215
SAP
CALM M5
CALM M5 ManagerISO 21215
SAP
CALM IR
CALM IR ManagerISO 21214
SAP
CALM IR
CALM IR ManagerISO 21214
SAP
3G cellular std by reference
CALM 3G ManagerISO 21213
SAP
3G cellular std by reference
CALM 3G ManagerISO 21213
SAP
In- Vehicle Network
Lower Layers
In-Vehicle NetConvergence
ISO 212??
SAP
Thierry Ernst – February 2008 9
Geoaddressed applications
(e.g. active safety)
IPv6
TCP / UDP
IP Applications (Deployment)
C2C-CC Network Layer
PHY (IEEE 802.11p)
LLC/MAC (IEEE 802.11p)
B
A C
WSMP
CVIS protocol different?
B
C2C MAC P1609.4
WAVE Short Message Apps
CALM M5: C2C-CC & WAVE
Thierry Ernst – February 2008 10
ISO TC204 WG16: CALM Stack
Thierry Ernst – February 2008 11
ISO TC204 WG16: CALM Architecture
Combined Antenna Pod
ITS In-Vehicle Network
RESOURCE MANAGER, ISO14906
CALM NETWORK LAYER – FMIPv6
ITS INTERNETAPPLICATION
SocketTCP/UDP
ApplicationInterfaceISO15628
PACKETHOP
(RUDP)
CALM Routing
IN-VEHICLE NETWORK DATA LINK LAYER
IN-VEHICLE NETWORK PHYSICAL LAYER
VEHICLECOMPUTER
CME
Vehicle-Vehicle
Apllication
Network
IVN DLL
IVN PHY
Network
IVN DLL
IVN PHY
CALM OBU
CALM M5 PHY
CALM MAC
CALM LLC
Network
CALM M5 PHY
CALM MAC
CALM LLC
Network
CALM M5 PHY
CALM MAC
CALM LLC
Network
CME
MLMEPLCP/PLME
NME
CME
MLMEPLCP/PLME
NME
GPRS PHY
GPRS Stack
GPRSConvergence
Network
GPRS PHY
GPRS Stack
GPRSConvergence
Network
GPRS PHY
GPRS Stack
GPRSConvergence
Network
DSRC L1
DSRC L2/L7
DSRCConvergence
Network
DSRC L1
DSRC L2/L7
DSRCConvergence
Network
DSRC L1
DSRC L2/L7
DSRCConvergence
Network
GPS PHY
GPS Stack
GPSConvergence
Network
GPS PHY
GPS Stack
GPSConvergence
Network
GPS PHY
GPS Stack
GPSConvergence
Network
CALM Routing
Implementation Architecture Implementation Architecture -- ExampleExample
Thierry Ernst – February 2008 12
ISO TC204 WG16: CALM NetworkingCALM Networking: ISO 21210
21210-1: Internet Connectivity (Committee Draft)21210-2: Fast Application (draft)
Medium Selection & SwitchingHorizontal handover: between access points using the same mediaVertical handover: heterogeneous handovers Purpose: Continuous communication during handoffSelect the most appropriate media based on application needs
IP & non-IP services Based on IPv6 and mobility features (NEMO, MIPv6, etc)IPv6 not considered for time critical applications (collision avoidance)
Thierry Ernst – February 2008 13
InterfaceManagementEntity (IME)
IPv6
CALM Management Entity (CME)
OEM
FAST /FAST only
transceivers
M-S
AP
SNMP
T-SAPM
-SAP
Broadcastreceivers,
positioning,others
C-SAP
CALM Communications Kernel
NetworkManagementEntity (NME) S
AP
Managem
ent In
form
atio
n B
ase
(M
IB) &
Managem
ent In
trac
om
mun
icatio
ns
FASTInitializationManagement
Cable LANModem
PredictedFAST / IPv6
FAST
C-SAP
SAP
Network / Transport Layer
Physical / Data Link Layer
UDP
WAVE ...
IPv6
internet
T-SAP T-SAP T-SAP
T-SAP
Non-FASTonly
transceiversIE
EE P
1609
Non-F
ast
CA
LM
app
licatio
ns
T-SAP
CALM
FAS
Tapp
licatio
ns
Virtual Interfaces
Networking
Applications
Management
ISO TC204 WG16: CALM Lower Layers Architecture
Thierry Ernst – February 2008 14
InterfaceManagementEntity (IME)
IPv6
CALM Management Entity (CME)
OEM
FAST /FAST only
transceivers
M-S
AP
SNMP
T-SAPM
-SAP
Broadcastreceivers,
positioning,others
C-SAP
CALM Communications Kernel
NetworkManagementEntity (NME) S
AP
Managem
ent In
form
atio
n B
ase
(M
IB) &
Managem
ent In
trac
om
mun
icatio
ns
FASTInitializationManagement
Cable LANModem
PredictedFAST / IPv6
FAST
C-SAP
SAP
Network / Transport Layer
Physical / Data Link Layer
UDP
WAVE ...
IPv6
internet
T-SAP T-SAP T-SAP
T-SAP
Non-FASTonly
transceiversIE
EE P
1609
Non-F
ast
CA
LM
app
licatio
ns
T-SAP
CALM
FAS
Tapp
licatio
ns
ISO CD 21218
ISO CD 24102
ISO CD 29281
IEEE 802.2
ISO TC204 WG16: CALM Standards
Thierry Ernst – February 2008 15
TC204 WG16: CALM Architecture
Thierry Ernst – February 2008 16
TC204 WG16: CALM Architecture
Thierry Ernst – February 2008 17
TC204 WG16: CALM Architecture
Thierry Ernst – February 2008
FP6 CVIS European Project-
A proof of concept of CALM
Thierry Ernst – February 2008 19
Coordinator: Fiat Research Centre
Total budget: € 38 Million
EC contribution: € 20,5 Million
Consortium: 51 partners - 12 countries
Coordinator: AustriaTech
Total budget: € 16,8 Million
EC contribution: € 9,6 Million
Consortium: 37 partners - 14 countries
Coordinator: ERTICO
Total budget: € 41 Million
EC contribution: € 22 Million
Consortium: 61 partners - 12 countries
Cooperation links to: SISTER (EC-Proposal), SEVECOM, COMeSafetyCar-2-Car Communications Consortium (C2C-CC), Network on Wheels (NoW), INVENTACTIV (Germany), CVHS (UK), IVSS (Sweden)
Core Technologies
Car<->Car
Car<->Infrastructure
Cooperative Vehicle-Infrastructure System ITS Usage: EC Projects around CALM
Thierry Ernst – February 2008 20
CVIS: FP6 Integrated Project (IP)Cooperative Vehicle-Infrastructure System
http://www.cvisproject.orgFrom Feb. 2006 till Feb. 201061 partners / 12 countries / Total Budget: 41 Millions Euros
ObjectivesDevelop, trial & demonstrate
Inter-operable architecture for vehicular communicationsNovel applications for:
Cooperative traffic and road network monitoringCooperative road & traffic network management & controlCooperative logistics & fleet managementCooperative public transport & intermodality
VisionUse and extend existing standardsProduce open design and softwareOutput intended to be reused by other EC projects
CVIS: FP6 Integrated Project (IP)
Thierry Ernst – February 2008 21
Centers
RoadsideVehicles
Personal(Handheld)
Devices
CentersPersonal
(Handheld)Devices
Personal space(Handheld
Devices)
VehiclesVehicles RoadsideRoadside andLocal area
Centers(Control, Service,
Data providers)
The (IPv6) ITS Network
European ITS Architecture
Thierry Ernst – February 2008 22
Roadside System
Vehicle System
CVIS: IPv6 Communications between subsystems
Internet
Central System
TunneledIPv6
(MNN)
Vehicle Host
MobileRouter
Antenna
VehicleGateway
SENS
SENS
CtrlCtrl
Service
Centre
Control
Centre
Internet
Authority
Databases
Home Agent
CentralHost
Gate-way
BorderRouter
CentralHost
Gate-way
BorderRouter
CentralHost
Gate-way
BorderRouter
VMS Ant
SENSCtrl
AccessRouter
RoadsideHost
RoadsideGateway
BorderRouter
Thierry Ernst – February 2008 23
CVIS: FP6 Integrated Project (IP)Communication Sub-Project (SP 2.1 COMM): Vehicle-Infrastructure communications
± 23 partnersApprox 23% of CVIS overall budgetSpecify & Implement communication architectureLiaison with other EU-funded projects / ISO / IETF / C2C-CC
Communication architecture inspired from ISO TC 204 WG16 'CALM' architecture
CALM is adapted and simplified
CALM: Communications Architecture for Land MobileCALM Handbook: http://www.calm.hu
Thierry Ernst – February 2008 24
CVISHost
CVISRouter
Antenna
OEMGateway
SENS
SENS
CtrlCtrl
CVIS: Vehicle ConfigurationIn-vehicle IPv6 subnet
CVIS Router: Mobile Router maintaining Internet Access through several physical interfacesCVIS Host: run dedicated ITS applicationsOEM: Gateway between IP and CAN
Thierry Ernst – February 2008 25
VMS Ant
SENSCtrl
AccessRouter
RoadsideHost
RoadsideGateway
BorderRouter
IPv6
CVIS: Roadside Configuration
Thierry Ernst – February 2008
CALM: NEMO RO and Multihoming needs for deployment
Thierry Ernst – February 2008 27
CALM: IP-Layer Mobility: Various communication medium
Internet
HA
V2V & V2I communication crucial for ITSIn-vehicle devices will require (continuous) Internet connectivity Internet connectivity will be provided transparently to the applications through a range of access technologies
GPRS/3G, IEEE 802.11 a/b/g, IEEE 802.11p, DSRC, ...
Thierry Ernst – February 2008 28
CALM: IP-layer Mobility: In-vehicle network
Internet
HA
Vehicles will be fully networkedIn-vehicle networkPrefix (MNP: Mobile Network Prefix) is assigned to the mobile networkOn-board units (MNNs) have their addresses taken from MNP
Thierry Ernst – February 2008 29
CALM: Communication Architecture Key FeaturesNEMO: Maintain Internet access
Continuous communication during handoffHorizontal handover: between access points using the same mediaVertical handover: heterogeneous handovers
MonAmi6: Mobile Edge multihomingManage simultaneous access to the Internet (multiple interfaces)
Medium Selection & Switching Select the most appropriate media based on application needs
IPv4-IPv6 TransitionAllow IPv6 communications over IPv4 access networksAllow CVIS nodes to communicate with IPv4
IP & non-IP servicesIP not considered for time critical applications (e.g. collision avoidance)
Thierry Ernst – February 2008 30
CALM: Mobility Management with NEMO (NEtwork MObility)
HA
NEMO Basic Support manages mobility of the entire network.Only the Mobile Router manages mobilityCurrent address recorded at the HA (dedicated server)Nodes inside the moving network do not need to participate in mobility management
Thierry Ernst – February 2008 31
CALM: V2V via the infrastructureDirect V2V is not always possibleIssue: NEMO RO between two NEMOs
HA HA
Thierry Ernst – February 2008 32
CALM: V2I with destination on the roadside
HA
Service provided by the roadside through a number of ARs on the roadIssue: NEMO RO with CN topologically close to MR
AR
Thierry Ernst – February 2008 33
CALM: V2I via another vehicleDirect V2I is not always possibleIssue: RO with CN in the infrastructure over a multihop adhoc network (MANEMO ?)
HA
Thierry Ernst – February 2008 34
CALM: nested NEMO (VMNs)
HA
VMNs: Hand-held devices should be allowed in the architectureMight be operating MIPv6 (or not)
Issue: RO between MR and VMN's HA
HA
Thierry Ernst – February 2008 35
CALM: Multiple HAs
HA
Owned by distinct institutions depending on servicesVehicle may switch to a more local HA (agreement between operators)Issue: Switching HAs (multihoming [RFC 4980] and RO)
HA
Thierry Ernst – February 2008 36
CALM: Multiple MRsOne default in-vehicle embedded MROther MRs could be brought in
e.g. personal hand-held devices acting as MRIssue: MRs coordination (multihoming: [RFC 4980])
Thierry Ernst – February 2008 37
CALM: Multiple MNPsMultiple in-vehicle networks and purposes => specific addressing requirements
1 MNP for in-vehicle embedded sensors1 MNP for multimédia
Issue: multihoming [RFC 4980]ingress filteringaddress selection
Thierry Ernst – February 2008 38
Via the access network or via another vehicleIssues: Multihoming [RFC 4980], QoS
HA
CALM: Multiple types of V2I routes
Thierry Ernst – February 2008 39
CALM Needs: ConclusionAll scenarios may not be deployed at once, but the communication architecture should not prevent them (e.g. Multiple MRs, nested NEMO)A RO and multihoming solution may not be provided to accommodate all needsWhile RO is challenging, multihoming issues are easier to fix (multiple HAs, multiple MRs):
Focus MEXT work on this first ?
Didn't mention about security, location privacy, etc. and non-MEXT related features since the above discussion is related to the IETF MEXT Working Group only
We may need to look at this from a wider angle
Thierry Ernst – February 2008
General Conclusion
Thierry Ernst – February 2008 41
ConclusionsISO is defining the CALM architecture
Uses IETF standards (IPv6, NEMO, etc)CVIS is validating the CALM architecture conceptCVIS know-how can improve ISO standards and help the IETF to develop new standards needed for ITS communications
IP is the convergence layer will allow interoperability between V2V and V2I architectureswill allow interoperability between dedicated ITS applications and other Internet usageswill save costs and boost innovation
IPv6 is the recommended version for ITSNot an option for wide development of IP-based ITS applicationsITS needs the advanced features provided by IPv6 (NEMO, etc)Millions of vehicles, each require several addressesToo many IP addresses needed for NAT
Thierry Ernst – February 2008 42
Conclusions: Next Steps & ChallengesImprove the communication architecture
Communication security User privacy Reliability / Performance
Non-Technical challengesUrgent to develop IPv6 awareness within the ITS communityEnforce participation to standardization bodies and establish liaison between ITS bodies and the IETF
Open questions:Who is going to provide the IPv6 address space ?Who is going to operate the IPv6 access network(s) ?Who is going to define policies ?Who will be liable in case of miss-use ?
Thierry Ernst – February 2008 43
Conclusions: More about IPv6 and CALMISO TC 204 WG 16: CALM Standard: http://www.calm.huIPv6 applicability to ITS: http://lara.inria.fr/ipv6/
Next ISO TC204 WG 16 meetings2008 March 10-14: Jeju, Korea2008 June 9-13: Paris, France (hosted by AFNOR)
Cooperative Vehicle-Infrastructure Systemhttp://www.cvisproject.org
Thierry Ernst – February 2008
Merci pour votre attention
Questions ?
[email protected] Rocquencourt – IMARA / LARA
http://www-rock.inria.fr/imara
http://www.lara.prd.fr