ISO TC204 WG 16: The CALM Architecture. INRIA IMARA project-team / JRU LARA.

Transcription

1 ISO TC204 WG 16: The CALM Architecture INRIA IMARA project-team / JRU LARA

2 ISO TC204 WG16: CALM ISO Technical Committee 204: Currently 12 active WGs WG 16: Wide Area Communications Since Y 2000 / Led by Russell Shields (Ygomi) CALM: Communication Architecture for Land Mobile Renamed from Communications Air-interface, Long and Medium range Docs: Web: CALM Handbook 7 sub-wgs SWG 16.0: CALM Architecture SWG 16.1: CALM Media SWG 16.2: CALM Network SWG 16.3: Probe Data SWG 16.4: Application Management SWG 16.5: Emergency notifications (ecall) SWG 16.6: CALM ad-hoc subsystem 2

3 ISO TC204 WG16: 7 Sub Working Groups 3

4 ISO TC204 WG16: CALM Communication Media Communication architecture allowing V2V, V2I and continuous Internet access through multiple radio technologies (potentially used simultaneously) Media: Cellular (CALM 2G/3G) cf CD & CD Infrared light (IR) cf CD Microwave (CALM M5) cf CD IEEE a/b/g (WIFI) IEEE p (mobile WIFI) Millimeter waves (CALM MM) cf CD Microwaves CEN DSRC IPv6: Internet connectivity Unification layer of underlying technologies Standardized at the IETF to replace IPv4 (current version) available global addresses (instead of 2 32 ) 4

5 ISO TC204 WG16: CALM Communication Media The generic Comm Architecture is CALM GPS, Galileo Terrestrial Broadcast RDS, DAB Sat-Comm GSM-GPRS UMTS Broadcast Transmitter Beacon CALM-M5 CEN-DSRC CALM-IR WiMAX Hot-Spot (Wireless LAN) PDA, SmartPhone Variable Message Sign Info-Broadcaster Vehicle-to-Vehicle (M5, IR, MM) 5

6 ISO TC204 WG16: Communication Scenarios 6

7 ISO TC204 WG16: CALM Architecture ALL ITS App. 1 App. 2 APPLICATIONS App. 3 Service QoS HTTP/ SMTP Proprietary Protocols Protocol Stream & Realtime Proprietary Protocols Protocol ISO DSRC Proprietary L7 Protocol Interface Selection A B C TCP UDP L2/UDP Handover Interface QoS Proprietary Init Hnd- or ovrdedicated Secur MAC Radio p Interface WAVE IPv6 layer Proprietary Init Hnd- or ovrdedicated Secur MAC Radio 2G/3G Interface GSM InitProprietary Hndor ovrdedicated Secur MAC Radio Interface IR 7

8 ISO TC204 WG16: CALM Architecture CALM ARCHITECTURE CALM system Management Entity (CME) ISO SAP Directory Services ISO Non-CALM-aware Point-to-point APPLICATI ONS Non-CALM-aware IP (Internet) APPLICATI ONS SAP SAP Convergence Layer ISO 15628/ SAPISO SAP SAP Networking Management SAP Convergence Layer IP socket/ SAPISO CALM-Aware APPLICATI ONS SAP SAP Layer 5-7 INTERNET ST ANDARDS SAP SAP NETWORK INTERF ACE Routing andmedia Switching based on IPv6 ISO ISO SAP SAP SAP SAP SAP SAP CALM 2G ManagerCALM 3G Manager CALM IR Manager CALM M5 Manager CALM MM Manager SAP Common Station, PHY, MAC, LLC Managers ISO ISO ISO G cellular std by reference 3G cellular std by reference ISO ISO CALM IR CALM M5 ISO CALM MM SAP In-Vehicle Net Convergence ISO 212?? In- Vehicle Network Lower Layers Media Function blocks shown above may be part SAP - Service Access Point of a more comprehensive communications device. Management - Standards that are outside CALM scope SAP - Service Access Point Data Transfer 8

9 CALM M5: C2C-CC & WAVE Geoaddressed applications (e.g. active safety) IP Applications (Deployment) WAVE Short Message Apps WSMP TCP / UDP CVIS protocol different? IPv6 B C2C-CC Network Layer A C2C MAC B LLC/MAC (IEEE p) C P PHY (IEEE p) 9

10 ISO TC204 WG16: CALM Stack 10

11 ISO TC204 WG16: CALM Architecture Implementation Architecture - Example RESOURCE MANAGER, ISO14906 ITS INTERNET APPLICATION Vehicle- Vehicle Apllication CME Application Interface ISO15628 Socket TCP/UDP CALM Routing CALM NETWORK LAYER FMIPv6 PACKET HOP (RUDP) VEHICLE COMPUTER IN-VEHICLE NETWORK DATA LINK LAYER IN-VEHICLE NETWORK PHYSICAL LAYER ITS In-Vehicle Network CALM OBU CALM Routing CME Network Network Network Network Network IVN DLL IVN PHY CALM LLC CALM MAC CALM M5 PHY GPRS Convergence GPRS Stack GPRS PHY DSRC Convergence DSRC L2/L7 DSRC L1 GPS Convergence GPS Stack GPS PHY NME MLME PLCP/ PLME Combined Antenna Pod 11

12 ISO TC204 WG16: CALM Networking CALM Networking: ISO : Internet Connectivity (Committee Draft) : Fast Application (draft) Medium Selection & Switching Horizontal handover: between access points using the same media Vertical handover: heterogeneous handovers Purpose: Continuous communication during handoff Select 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) 12

13 ISO TC204 WG16: CALM Lower Layers Architecture Management T-SAP Non-Fast CALM applications T-SAP T-SAP T-SAP T-SAP SAP internet FAST Applications T-SAP UDP SAP Network Management Entity (NME) IEEE P1609 FAST Initialization Management CALM FAST applications SNMP OEM WAVE... IPv6 IPv6 Networking Network / Transport Layer C-SAP CALM Communications Kernel C-SAP Interface Management Entity (IME) M-SAP Physical / Data Link Layer M-SAP Management Information Base (MIB) & Management Intracommunications CALM Management Entity (CME) Broadcast FAST / Non-FAST receivers, FAST only only positioning, transceivers transceivers others Cable LAN Modem Virtual Interfaces Predicted FAST / IPv6 13

14 ISO TC204 WG16: CALM Standards T-SAP Non-Fast CALM applications T-SAP T-SAP T-SAP T-SAP T-SAP SAP UDP SAP Network Management Entity (NME) IEEE P1609 FAST Initialization Management CALM FAST applications SNMP internet FAST OEM WAVE... IPv6 ISO CD ISO CD ISO CD IEEE IPv6 Network / Transport Layer C-SAP CALM Communications Kernel C-SAP Interface Management Entity (IME) M-SAP Physical / Data Link Layer M-SAP Management Information Base (MIB) & Management Intracommunications CALM Management Entity (CME) Broadcast FAST / Non-FAST receivers, FAST only only positioning, transceivers transceivers others Cable LAN Modem Predicted FAST / IPv6 14

15 TC204 WG16: CALM Architecture 15

16 TC204 WG16: CALM Architecture 16

17 TC204 WG16: CALM Architecture 17

18 FP6 CVIS European Project - A proof of concept of CALM

19 ITS Usage: EC Projects around CALM Cooperative Vehicle-Infrastructure System Coordinator: ERTICO Total budget: 41 Million EC contribution: 22 Million Consortium: 61 partners - 12 countries Core Technologies Coordinator: Fiat Research Centre Total budget: 38 Million EC contribution: 20,5 Million Consortium: 51 partners - 12 countries Car<->Car Coordinator: AustriaTech Total budget: 16,8 Million EC contribution: 9,6 Million Consortium: 37 partners - 14 countries Car<->Infrastructure Cooperation links to: SISTER (EC-Proposal), SEVECOM, COMeSafety Car-2-Car Communications Consortium (C2C-CC), Network on Wheels (NoW), INVENT ACTIV (Germany), CVHS (UK), IVSS (Sweden) 19

20 CVIS: FP6 Integrated Project (IP) Cooperative Vehicle-Infrastructure System From Feb till Feb partners / 12 countries / Total Budget: 41 Millions Euros Objectives Develop, trial & demonstrate Inter-operable architecture for vehicular communications Novel applications for: Cooperative traffic and road network monitoring Cooperative road & traffic network management & control Cooperative logistics & fleet management Cooperative public transport & intermodality Vision Use and extend existing standards Produce open design and software Output intended to be reused by other EC projects 20

21 European ITS Architecture Personal Personal space (Handheld (Handheld) Devices) Devices Centers (Control, Centers Centers Service, Data providers) The (IPv6) ITS Network Vehicles Vehicles Vehicles Roadside and Local area 21

22 CVIS: IPv6 Communications between subsystems Roadside System VMS Ant Internet Tunneled IPv6 Roadside Gateway Ctrl Access Router Roadside Host Border Router SENS Antenna Central System Vehicle System Gateway Central Host Internet Border Router Service Centre (MNN) Mobile Router Vehicle Host Gateway Vehicle Gateway Ctrl Central Host Border Router Home Agent Ctrl SENS SENS Gateway Authority Databases Central Host Border Router Control Centre 22

23 CVIS: FP6 Integrated Project (IP) Communication Sub-Project (SP 2.1 COMM): Vehicle- Infrastructure communications ± 23 partners Approx 23% of CVIS overall budget Specify & Implement communication architecture Liaison 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 Mobile CALM Handbook: 23

24 CVIS: Vehicle Configuration In-vehicle IPv6 subnet CVIS Router: Mobile Router maintaining Internet Access through several physical interfaces CVIS Host: run dedicated ITS applications OEM: Gateway between IP and CAN Antenna CVIS Router CVIS Host OEM Gateway Ctrl Ctrl SENS SENS 24

25 CVIS: Roadside Configuration VMS Ant Roadside Gateway Access Router Roadside Host Border Router IPv6 Ctrl SENS 25

26 CALM: NEMO RO and Multihoming needs for deployment

27 CALM: IP-Layer Mobility: Various communication medium V2V & V2I communication crucial for ITS In-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 a/b/g, IEEE p, DSRC,... HA Internet 27

28 CALM: IP-layer Mobility: In-vehicle network Vehicles will be fully networked In-vehicle network Prefix (MNP: Mobile Network Prefix) is assigned to the mobile network On-board units (MNNs) have their addresses taken from MNP HA Internet 28

29 CALM: Communication Architecture Key Features NEMO: Maintain Internet access Continuous communication during handoff Horizontal handover: between access points using the same media Vertical handover: heterogeneous handovers MonAmi6: Mobile Edge multihoming Manage simultaneous access to the Internet (multiple interfaces) Medium Selection & Switching Select the most appropriate media based on application needs IPv4-IPv6 Transition Allow IPv6 communications over IPv4 access networks Allow CVIS nodes to communicate with IPv4 IP & non-ip services IP not considered for time critical applications (e.g. collision avoidance) 29

30 CALM: Mobility Management with NEMO (NEtwork MObility) NEMO Basic Support manages mobility of the entire network. Only the Mobile Router manages mobility Current address recorded at the HA (dedicated server) Nodes inside the moving network do not need to participate in mobility management HA 30

31 CALM: V2V via the infrastructure Direct V2V is not always possible Issue: NEMO RO between two NEMOs HA HA 31

32 CALM: V2I with destination on the roadside Service provided by the roadside through a number of ARs on the road Issue: NEMO RO with CN topologically close to MR HA AR 32

33 CALM: V2I via another vehicle Direct V2I is not always possible Issue: RO with CN in the infrastructure over a multihop adhoc network (MANEMO?) HA 33

34 CALM: nested NEMO (VMNs) VMNs: Hand-held devices should be allowed in the architecture Might be operating MIPv6 (or not) Issue: RO between MR and VMN's HA HA HA 34

35 CALM: Multiple HAs Owned by distinct institutions depending on services Vehicle may switch to a more local HA (agreement between operators) Issue: Switching HAs (multihoming [RFC 4980] and RO) HA HA 35

36 CALM: Multiple MRs One default in-vehicle embedded MR Other MRs could be brought in e.g. personal hand-held devices acting as MR Issue: MRs coordination (multihoming: [RFC 4980]) 36

37 CALM: Multiple MNPs Multiple in-vehicle networks and purposes => specific addressing requirements 1 MNP for in-vehicle embedded sensors 1 MNP for multimédia Issue: multihoming [RFC 4980] ingress filtering address selection 37

38 CALM: Multiple types of V2I routes Via the access network or via another vehicle Issues: Multihoming [RFC 4980], QoS HA 38

39 CALM Needs: Conclusion All 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 needs While 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 39

40 General Conclusion

41 Conclusions ISO is defining the CALM architecture Uses IETF standards (IPv6, NEMO, etc) CVIS is validating the CALM architecture concept CVIS 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 architectures will allow interoperability between dedicated ITS applications and other Internet usages will save costs and boost innovation IPv6 is the recommended version for ITS Not an option for wide development of IP-based ITS applications ITS needs the advanced features provided by IPv6 (NEMO, etc) Millions of vehicles, each require several addresses Too many IP addresses needed for NAT 41

42 Conclusions: Next Steps & Challenges Improve the communication architecture Communication security User privacy Reliability / Performance Non-Technical challenges Urgent to develop IPv6 awareness within the ITS community Enforce 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? 42

43 Conclusions: More about IPv6 and CALM ISO TC 204 WG 16: CALM Standard: IPv6 applicability to ITS: Next ISO TC204 WG 16 meetings 2008 March 10-14: Jeju, Korea 2008 June 9-13: Paris, France (hosted by AFNOR) Cooperative Vehicle-Infrastructure System 43

44 Merci pour votre attention Questions? INRIA Rocquencourt IMARA / LARA