Title Page
ABSTRACT
국문 초록
Contents
NOMENCLATURE 20
CHAPTER 1. INTRODUCTION 25
1.1. Background of VANET environments 27
1.2. Organization of the Thesis 28
CHAPTER 2. Related Works 29
2.1. IEEE WAVE 1609 Standard 29
2.2. ETSI C-ITS 32
2.3. IETF IPWAVE Standard 34
2.3.1. IPWAVE Architecture 34
2.3.2. Network Attachment Procedure 35
2.3.3. Problems of Network Attachment Procedure 36
2.3.4. Mobility Management Procedure 38
2.3.5. Problems of Mobility Management Procedure 40
2.4. Vehicular Mobility Management Schemes 41
2.5. Route Optimization Schemes 43
2.5.1. Route Optimization in Mobile IPv4 44
2.5.2. Localized Routing for Proxy Mobile IPv6 44
CHAPTER 3. A Vehicular Mobility Management Scheme for a Shared-Prefix Model over IEEE WAVE IPv6 Networks 46
3.1. Introduction 46
3.2. Architecture Design 47
3.2.1. Network Architecture 47
3.2.2. Vehicle 49
3.2.3. Road Side Unit (RSU) 49
3.2.4. The WAVE access network 51
3.2.5. Link Border Router (LBR) 51
3.2.6. Correspondent Node (CN) 52
3.3. Proposed Vehicular Mobility Management Scheme 52
3.3.1. Message Format 52
3.3.2. Network Attachment Procedure 54
3.3.3. V2N Communication 59
3.3.4. Vehicular Mobility Management for V2N Communication 62
3.4. Comparative Analysis 72
3.5. Security Consideration 74
3.6. Simulation 75
1) Vehicle belongs to RSU1 79
2) Vehicle belongs to RSU2 80
3) Vehicle belongs to RSU3 81
CHAPTER 4. A Localized Forwarding Scheme for a Shared-Prefix Model based Vehicular Mobility Management over IEEE WAVE IPv6 Networks 84
4.1. Introduction 84
4.2. Architecture Design 87
4.2.1. Network Architecture 87
4.2.2. Vehicle 88
4.2.3. Road Side Unit (RSU) 90
4.2.4. The WAVE access network 92
4.2.5. Link Border Router (LBR) 92
4.3. Proposed Localized Forwarding Scheme 93
4.3.1. Message Format 93
4.3.2. Overview of Localized Forwarding 96
4.3.3. Intra-RSU Localized Forwarding 100
4.3.4. Inter-RSU Localized Forwarding 103
4.3.5. Handling the destination vehicle's movement 105
4.4. Performance Analysis 108
4.5. Simulation 111
1) V1 belongs to RSU1 and V2 belongs to RSU4 115
2) V1 belongs to RSU1 and V2 belongs to RSU3 117
3) V1 belongs to RSU1 and V2 moves to RSU2 118
4) V1 belongs to RSU1 and V2 moves to RSU1 119
CHAPTER 5. A SDN-based Vehicular Mobility Management for Shared-Prefix Model over IEEE WAVE IPv6 Networks 122
5.1. Introduction 122
5.2. Architecture Design 124
5.2.1. Network Architecture 124
5.2.2. Vehicle 125
5.2.3. Egress OpenVSwitch (Egress OVS) 125
5.2.4. Ingress OpenVSwitch (Ingress OVS) 126
5.2.5. Intermediate OpenVSwitch (Intermediate OVS) 126
5.2.6. SDN Controller 126
5.2.7. Correspondent Node (CN) 128
5.3. Proposed SDN-based Vehicular Mobility Management Scheme 128
5.3.1. Network Attachment Procedure 128
5.3.2. Communication Procedure after Network Attachment 131
5.3.3. Intra-domain Handover Procedure 136
5.3.4. Inter-domain Handover Procedure 140
5.4. Performance Analysis 142
5.5. Comparison between E-VMM and SDN-based VMM scheme 148
5.5.1. Component that handles control messages 149
5.5.2. Location to store vehicle information 149
5.5.3. Method to route packets and IPv6 address conversion 151
5.6. Simulation 151
1) Vehicle belongs to OVS1's coverage 152
2) Vehicle belongs to OVS2's coverage 154
3) Vehicle belongs to OVS3's coverage 155
CHAPTER 6. Conclusion 158
CHAPTER 7. Discussion 159
REFERENCES 160
Table 1. Characteristics of MANET and VANET 27
Table 2. IEEE WAVE standards 30
Table 3. Comparative table between our scheme and existing schemes 72
Table 4. Each case according to the matching result 98
Table 5. Symbols for the performance analysis 108
Table 6. IPv6 address of each vehicle 112
Table 7. Symbols for the performance analysis 142
Table 8. Comparision between proposed SDN-based VMM and E-VMM scheme 149
Figure 1. IEEE 1609 (WAVE) architecture 30
Figure 2. IEEE 1609 channel assignment 31
Figure 3. WSA format 32
Figure 4. WRA format 32
Figure 5. ETSI protocol stack for C-ITS with standards 33
Figure 6. IPWAVE architecture 34
Figure 7. Message flow of a vehicle's network attachment 36
Figure 8. Message flow of a vehicle's mobility management using PMIPv6 38
Figure 9. Message flow of the mobility management using DMM 39
Figure 10. NetworkArchetecture of the proposed scheme 48
Figure 11. Entry of RSU-RVL 50
Figure 12. Entry of ILPL 50
Figure 13. Entry of LBR-RVL 51
Figure 14. Message format of UDP-NS 53
Figure 15. Message format of UDP-NA 53
Figure 16. Message flow of the network attachment 54
Figure 17. Message flow of V2N communication 59
Figure 18. Message flow of mobility management within a vehicular link 63
Figure 19. Message flow of mobility management between vehicular links 68
Figure 20. Simulation Topology 76
Figure 21. Packet capture of the vehicle's WAVE CCH interface 78
Figure 22. Packet capture of the vehicle's WAVE SCH1 interface 78
Figure 23. Packet capture of the LBR1's interface which is connected with the regular router in the WAVE access network. 79
Figure 24. UDP-NS Message (Packet 4135 in Figure 22) 81
Figure 25. Packet sequence with the overlapped case 83
Figure 26. Packet sequence with the disjoint case 83
Figure 27. Triangular data path 85
Figure 28. NetworkArchitecture of the proposed LF scheme 87
Figure 29. Entry of Vehicle-Destination Cache Entry (DCE) 89
Figure 30. Entry of Vehicle-Neighbor Cache Entry (NCE) 89
Figure 31. Entry of RSU-Registered Vehicle List (RSU-RVL) 90
Figure 32. Entry of RSU-Inter Link Prefix List (RSU-ILPL) 90
Figure 33. Entry of RSU-Localized Forwarding Table (RSU-LFT) 91
Figure 34. Entry of RSU-Suppress Localized Forwading Table (RSU-SLFT) 91
Figure 35. Entry of LBR-Registered Vehicle List (LBR-RVL) 93
Figure 36. Entry of LBR-Localized Forwarding Table (LBR-LFT) 93
Figure 37. Message format of UDP-Redirect 94
Figure 38. Message format of UDP-LFI and UDP-LFA 94
Figure 39. Message format of UDP-NS 95
Figure 40. Message Format of UDP-NA 95
Figure 41. Overview of localized forwarding 97
Figure 42. Intra-RSU localized forwarding 102
Figure 43. Inter-RSU localized forwarding 105
Figure 44. Handover with localized forwarding 107
Figure 45. Decrease rate in messages that LBR has to process 110
Figure 46. Simulation topology 112
Figure 47. Packet trace at V2's WAVE CCH interface 113
Figure 48. Packet trace at V2's WAVE SCH interface 114
Figure 49. Packet trace at RSU1's wired interface 115
Figure 50. UDP-LFI message (Packet 4 in Figure 49) 116
Figure 51. UDP-Redirect message (Packet 5 in Figure 49) 117
Figure 52. UDP-Redirect message (Packet 449 in Figure 49) 118
Figure 53. Delay of each UDP data packet 120
Figure 54. Summary about delay of each UDP data packet 120
Figure 55. NetworkArchitecutre of the proposed SDN-based VMM scheme 124
Figure 56. Vehicle Information Database (VI-DB) 127
Figure 57. Link-layer and device ID Matching Table (LDT) 127
Figure 58. Default Routing Table (DRT) 127
Figure 59. Network attachment procedure 129
Figure 60. Communication procedure between a vehicle and a CN 132
Figure 61. Intra-domain handover procedure 137
Figure 62. Total UDP-NS messages (Nudpns) graph[이미지참조] 146
Figure 63. Nv·v graph[이미지참조] 146
Figure 64. Memory used for a VI-DB (Msdn)[이미지참조] 148
Figure 65. Memory usage comparison between proposed scheme and E-VMM scheme 150
Figure 66. Network topology in simulation 152
Figure 67. Captured packet trace 153
Figure 68. Flow rules installed to Egress OVS (OVS1) 154
Figure 69. Flow rules installed to Ingress OVS (OVS6) 154
Figure 70. Flow rules installed to Egress OVS (OVS2) 155
Figure 71. Flow rules installed to Ingress OVS (OVS6) 155
Figure 72. Flow rules installed to Egress OVS (OVS3) 156
Figure 73. Flow rules installed to Ingress OVS (OVS6) 157