1 / 22

dickroy@alum.mit

STATUS OF CALM IEEE 1609 Meeting – Los Angeles 29 April – 1 May 2008. dickroy@alum.mit.edu. Content. CALM Overview CALM Architecture CALM Standards Status. What is CALM?. CALM - Overall. C ommunications A ccess for L and M obiles Provide user transparent continuous communications

iolani
Download Presentation

dickroy@alum.mit

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. STATUS OF CALM IEEE 1609 Meeting – Los Angeles29 April – 1 May 2008 dickroy@alum.mit.edu

  2. Content • CALM Overview • CALM Architecture • CALM Standards Status

  3. What is CALM?

  4. CALM - Overall CommunicationsAccess forLandMobiles • Provide user transparent continuous communications • CALM is the first open way to combine GPRS with vehicle-optimized WLAN technology. - NOT a complicated collection of new, unproven radio technologies

  5. CALM – an overview GPS, Galileo Terrestrial Broadcast RDS, DAB Sat-Comm GSM-GPRS UMTS WiMAX • Beacon • CALM-M5 • CEN-DSRC • CALM-IR Hot-Spot (Wireless LAN) Roadsign broadcast PDA access Vehicle-to-Vehicle (M5, IR, MM) Info-Broadcaster

  6. Why do we need CALM? • ITS is cooperative and safety sensitive • Many actors spanning from authorities, via manufacturers to end users • Applications and services interact  they share data and functions • Technology must be interoperable across borders • Public safety services requires proven performance level • All interfaces must be fully open – no competing proprietary solutions • Test specifications required for guaranteed interoperability and performance • Formal standardization is needed!

  7. CALM Applications • Support of Internet services • Support of traditional ITS apps • Traffic info, Road Tolling, Route Guidance,… • New generation of applications: • Major push in Vehicle Safety Communication (C2C-CC/SAFESPOT) • New commercial applications made possible by high data rate & long range. • 300+ applications defined so far

  8. CALM Architecture

  9. Vehicle Architecture

  10. CALM OSI Reference Architecture

  11. CALM Architecture Details CALM-aware applications, and CALM non-aware applications being based on ISO 15628:2007. Integrated CALM FAST networking and transport layer protocol. Integrated CALM geo-routing and transport layer protocol. Optional FAST local port transport protocol. ISO 21217 Multiple wireless and wired CIs. One global CALM management with functionality of IME, NME, CME.

  12. CALM Stand-alone Example ISO 21217

  13. CALM - Basic Example

  14. CALM - Complex Example

  15. CVIS CALM M5 Architecture

  16. CALM M5 Radio(s) • Two miniPCI “European” Atheros radios • Modified version compared to (most) US tests • Additionally includes: • Synchronization to European DSRC Toll Collection systems according to ETSI requirements • European 5.9GHz spectrum plus 802.11abg • GPS time-slot sync for performance optimization • Full P1609.4 stack (US operation compatible)‏ • Full CALM management for parallel stacks • Open access to APIs and SAPs, both native code LINUX and OSGi/GST based portable services

  17. Status of CALM Standards

  18. CALM Standards CD 21210: CALM networking for Internet Connectivity CD 21212: CALM 2G medium CD 21213: CALM 3G medium IS 21214: CALM IR medium (already published)‏ CD 21215: CALM M5 medium (cf. IEEE 802.11 TGp) WD 21216: CALM MM medium CD 21217: CALM global architecture DIS 21218: CALM lower layer service access points CD 24101: CALM application management CD 24102: CALM station manager CD 29281: CALM non-IP networking (cf. IEEE 1609) WD 29282: CALM applications using satellite ... and others

  19. TC204/WG16 Cooperation • IEEE 802.11p and P1609 – Wireless Access in the Vehicular Environment (WAVE)- Cooperative agreement with WG16 • ETSI TC ITS – new actor for 2G/3G standards, European spectrum and test standards,… • IETF – Internet - IPv6 - Network Mobility (NEMO/MONAMI -> MEXT) • USA projects: VSCC and VII • Japan projects: CALM Proof-Of-Concept,… • Europe projects: C2C-CC, CVIS, SafeSpot,…

  20. Recent Standards Developments • ETSI TC ITS – new technical committee for ITS-related 2G/3G standards, European spectrum allocations, test standards,… • ISO TC204 WG17 – new working group developing standards for the use of nomadic and mobile wireless devices (eg., Bluetooth) to support ITS service and multimedia provision in vehicles

  21. Recent Standards Developments • ISO/IEEE Partner Standards Development Organization (PSDO) cooperation agreement recently signed • TC 204 ITS specifically called out • Joint standards development procedures are specified (cf. Section 5.2 ff.)

  22. References • CALM Official: www.calm.hu • CALM Developer: www.tc204wg16.de • ISO TC204: www.isotc204.com • C2C: www.car-to-car.org • ETSI: www.etsi.org • CEN TC278: www.nen.nl/cen278 • Michael.Noblett@SEICCS.com, Chairman ISO TC204 • Knut.Evensen@q-free.com, CVIS Chief Architect,Convenor WG16.0 - CALM

More Related