The GeoNet project: Combination of IPv6 & GeoNetworking

Transcription

1 The GeoNet project: Combination of IPv6 & GeoNetworking Geographic addressing and routing for vehicular communications Dr. Thierry Ernst INRIA Mines ParisTech (LaRA) GeoNet Technical Coordinator The Fully Networked Car March Geneva 1

2 Why IPv6 GeoNetworking? IPv6: Internet Protocol version 6 S A-SA P S A-SA P M A-SA P M A-SA P S ta t io n m a n a g e m e n t O ther A pplications N F -SAP Networking & Transport IPv M obility E xtensions S N-SA P ITS GeoOther N etw ork R outing protocols S I- S A P TC P/U D P S N-SA P M N-SA P M N-SA P ITS Transport IN -SAP S e c u r it y I n fo r m a ti o n B a s e ( Id e n ti ty, C r y p to K e y a n d C e rt if ic a t e M a n a g m e n t ) S e c u r it y N F -SAP F ir e w a ll a n d I n tr u s i o n M a n a g e m e n t S F -S A P Session Support S F -S A P M F-S A P M F-S A P Application Support Inform ation Support A u t h e n t ic a t io n, A u t h o ri z a t io n, P r o f ile M a n a g e m e n t F A-SAP S I- S A P support Traffic E fficiency Facilities IN -SAP Access Technologies (PHY & DLL ) M I- S A P ITS Architectures must also Internet-based communications R oad Safety F A-SAP M I- S A P SM -SAP A pplications M anagem ent SM -SAP N e tw o r k i n g M a n a g e m e n t C2C-CC COMeSafety ETSI TC ITS ISO TC204 WG16 (CALM) ITS S tation R eference A rchitecture C r o s s - In te r fa c e M a n a g e m e n t M a n a g e m e n t I n f o rm a t io n B a s e ( M I B ) V2V: GeoNetworking is the addressing & routing packet forwarding approach favored in ITS communication architectures Station-External Interfaces e.g. 5.9G H z Station -Internal Interfaces e.g. e.g. e.g. e.g. e.g. W if i G P S B luetooth 2G /3G /... Ethernet H ardw are Security M odule (H S M ) ITS Station GeoNet: IPv6 and GeoNetworking must be combined in a common architecture IPv6 expands the capabilities of GeoNetworking GeoNetworking expands the capabilities of IPv6 2

3 Why IPv6 GeoNetworking? 3

4 Why IPv6? IPv4 does not fit to ITS requirements 232 = 4,294,967,296 addresses only IPv4 address exhausted by 2011 / 2012 IPv6: an evolution of IP New IP header Fully specified, implemented - operational deployment started IPv6 addressing 128 bits instead of 32 (2128 addresses instead of 232) Up to addresses / m2 An address for everything on the network IPv6 comprises new features absolutely needed for ITS Auto-configuration IP session continuity (NEMO) Multiple wireless media supported at once (McoA) Enhanced security Embedded multicast 4

5 GeoNet: Scope 5

6 GeoNet: Functional Modules 6

7 GeoNet: C2CNet Layer 7

8 GeoNet: C2CNet GeoNetworking Packet forwarding GeoUnicast: from one node to a single node GeoAnycast: from one node to any node in area GeoBroadcast: from one node to all nodes in area TopoBroadcast: from one node to all nodes n-hop away Message buffering (with GeoNetwork triggered re-evaluation) GeoUnicast GeoBroadcast / GeoAnycast Location management Beaconing (periodic single-hop broadcast) Location Table Location Service (lookup of unknown destinations) 8

9 GeoNet: IP Layer 9

10 IPv6 over C2CNet IPv6 C2CNet link: viewed as virtual link with GeoNetworking capabilities 10

11 GeoNet: Management Layer 11

12 GeoNet: Workshop Demo 12

13 GeoNet: Summary IPv6 + GeoNetworking = Enabling technology for better: Well supported at time of set-up C2C-CC, SafeSpot, Coopers, CVIS Status Road safety Traffic efficiency Value added services 1 reference specification 2 prototype implementations (Linux 2.6 / UMIP) Experimentation on a fleet of 4 vehicles Conformance tests: TTCN-3 Emulation with NCTUns CVIS selected as the target platform Effective dissemination in SDOs (ISO, ETSI, IETF) 13

14 Thank you for your attention Most deliverables are public and will be available on Dr. Thierry Ernst INRIA Mines ParisTech (LaRA) GeoNet Technical Coordinator ETSI ITS Workshop February 2010 Sophia-Antipolis 14

15 GeoNet Fact Sheet Feb Jan Budget: 3 M Funding: 1.9 M 7 partners Web: 2 Research Institutes (INRIA and IMDEA) 1 SME (Broadbit) 4 industrial partners (Hitachi, NEC, Lesswire & Efkon) News, deliverables, presentations Objective: Design the concepts linking geographic addressing and routing with IPv6 mobility mechanisms (IPv6 GeoNetworking) 15

16 GeoNet: Scope 3 main axes: Knowledge: elaborate a unified IPv6 GeoNetworking architecture compliant with best practices in vehicular communications; Standards: produce a reference IPv6 GeoNetworking specification and push it to SDOs (ISO, ETSI, IETF); Software: produce two prototype implementations and disseminate it to existing consortia (particularly SafeSpot, CVIS, COOPERS and C2C-CC). 16

17 Why GeoNetworking? 17

18 Why IPv6 GeoNetworking? GeoNet: scenarios geonetworking requiring both IPv6 and Scenario Type 1: sender is in the Internet Packets are transmitted in IPv6 until the RSUs serving the geographic area where they are GeoRouted through intermediate vehicles to the final destination(s). Scenario type 2: receiver is in the Internet Packets are GeoRouted through intermediate vehicles (using GeoUnicast) until a RSU where they are transmitted in IPv6 to the final destination. Scenario type 3: sender and receiver(s) are only reachable through the Internet Combination of Scenarios Type 1 & 2 where source and destination(s) are out of multi-hop wireless range 18

19 GeoNet: Design Goals (D1.2) Architecture combining IPv6 and GeoNetworking Communication modes Vehicle-based: without infrastructure (V2V) Roadside-based: with roadside infrastructure (V2I) Internet-based: with the Internet Destination set Single destination Multiple destinations Preserve security and location privacy Compatibility and interoperability 19

20 Why IPv6: address requirements Vehicles will be connected to the Internet In-vehicle IP network => Several IP addresses / vehicle Number of cars worldwide 1997: 600 millions 2030: 1200 millions (at present trend) IPv4 does not fit to ITS requirements 232 = 4,294,967,296 addresses only IPv4 address exhausted by 2011 /

21 GeoNet: Documents Most deliverables are public and will be uploaded as soon as they are completed (this month) Check D1.2 Final GeoNet Architecture Design D2.2 Final GeoNet Specification GeoNet Final Workshop 21

22 GeoNet: IPv6 Layer IPv6 is not Geo-Aware How IPv6 packets could be transmitted to a destination(s) in a specific geographic location? GeoNet relies on IPv6 multicast Several GeoDestination IP Group ID encoding approaches GeoNet hides GeoNetworking from the IP layer Enhancements required at the IP layer for location privacy (pseudonyms) & direct V2V (MNP exchange) GeoNet complies with ETSI and ISO architectures NEMO is used to guarantee reachability at a permanent address and maintaining sessions The Mobile Router entity at the OBU manages the connectivity on behalf of all the in-vehicle nodes 22

23 GeoNet: Work Ahead Progress work items in SDOs ETSI: GeoNetworking (TS ) ETSI: IPv6 GeoNetworking (TS ) ISO CALM Validation in Field Operational Tests (FOTs) needed Expand the architecture / specification Tighter integration of IPv6 & GeoNetworking: Position aware IP applications / GeoDestination encoding within IPv6 multicast IP-layer security & QoS Transport layer Congestion control 23

24 Why IPv6? IPv6: Internet Protocol version 6 Designed by the IETF since 1995 as a replacement of IPv4 IPv6 is an evolution of IP New IP header Fully specified, implemented - operational deployment started IPv6 addressing 128 bits instead of 32 (2128 addresses instead of 232) Up to addresses / m2 An address for everything on the network IPv6 comprises new features absolutely needed for ITS Auto-configuration IP session continuity (NEMO) Multiple wireless media supported at once (McoA) Enhanced security Embedded multicast 24