Switching method based on IEEE80211p in VANET

Abstract

The invention belongs to the technical field of mobile communication, and discloses a switching method based on IEEE80211p in a VANET. The method comprises the steps of firstly, only considering the RSSI of an RSU to decide whether switching is carried out or not, and dividing the switching into hard switching and soft switching; then in the soft switching, conducting analysis through a Stackelberg game to decide whether a vehicle is switched or not; finally, after a first application of the vehicle for switching fails, conducting a repeated application for switching through a BEB, and completing the switching by applying a game method again. According the method, the switching situation of the vehicle in the overlapping region of the RSU under the real environment can be simulated, the vehicle can select the right time slice to conduct the switching, the probability of congestion of the switching is reduced, the delivery rate of the network is improved, the vehicle can obtain better handling capacity, the whole performance of a VANET subnet is improved, and the user experience degree is improved.

Description

technical field [0001] The invention belongs to the technical field of mobile communication, and relates to a method for switching vehicles in overlapping coverage areas of Road Side Units (RSUs) by using Steinberg game and binary exponential backoff algorithm; In (Vehicular Ad-hoc Network, VANET), a specific mobile communication switching method is given. The vehicle can select according to factors such as the number of vehicles that need to be switched, the speed of the vehicle, the signal strength received by the vehicle, and the urgency of the data packet. Appropriate time slice for switching; Background technique [0002] In VANET based on IEEE802.11p protocol, a complete handover process is divided into two parts: MAC layer handover and network layer handover; Established between the mobile node and the new access point; for complete MAC layer handover, different handover protocols may be applied based on different wireless technologies; in network layer handover, the...

AI Technical Summary

Problems solved by technology

[0003] At present, the research on handover methods in VANET based on IEEE802.11p protocol mainly has the following problems. The process of vehicle handover from one RSU to another RSU is to improve the process of scanning and authentication to ensure seamless handover. It is based on IEEE802.11a/b/g and other protocol ideas; but IEEE802.11p cancels the process of identity authentication and association of Wi-Fi and other networks, and IEEE1609.3 stipulates that WSA (WAVE protocol service announcement) can inform vehicles about RSU in advance Channel and service information, that is, the method of ensuring seamless handover by reducing handover congestion probability during scanning, authentication, etc. is not suitable for IEEE802.11p-based VANET; for example: vehicles are divided into different sets, and one is selected in each set The mobile routing vehicle and an assisting vehicle, these two cannot be the same vehicle, the assisting vehicle scans and discovers new RSUs for the mobile routing vehicle, collects and caches the adjacent RSU information through the assisting vehicle, and then analyzes the information in the assisting vehicle for mobile routing Deciding whether to perform handover (reducing handoff delay based on NEMO in VANET, Azzedine Boukerche, Zhenxia Zhang, XinFei. Reducing Handoff Latency for NEMO-based Vehicular Ad Hoc Networks. Proc. of IEEE Global Communications Conference (Globecom). Houston, TX, USA, 2011.1-5.); MIPv6 ignores the throughput, especially for multimedia applications, which will lead to long handover delay and packet loss; the fast mobile IPv6 (FMIPv6) mechanism tries to solve these problems of MIPv6, it is solved by handover prediction Yes, but the characteristics of high-speed movement and sudden change of direction of the vehicle make the prediction uncertain; the advance prediction mechanism of FMIPv6 does not necessarily

Images