Data interaction method and system of Internet of Vehicles, terminal and storage medium
By predicting the vehicle's driving path and using blockchain authentication information, the vehicle can quickly establish a wireless communication connection with roadside equipment, solving the problem of delayed communication connection between the vehicle and roadside equipment, and achieving efficient and secure data interaction.
Patent Information
- Application Number
- CN202411109402.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-13
- Publication Date
- 2024-12-24
AI Technical Summary
It is difficult for vehicles to quickly establish a safe and reliable communication connection with roadside equipment during travel, resulting in delayed data interaction or inability to achieve.
By obtaining the positioning data of the on-board terminal, predicting the driving path, and recalling the device type and authentication information of the target roadside device from the blockchain, confirming that the communication connection is required based on the device type, and sending the authentication information to the on-board terminal to make it Establish a wireless communication connection with the roadside equipment on the driving path.
It ensures the timeliness and security of data interaction, improves the efficiency and reliability of communication connections, and realizes stable data exchange between vehicles and roadside equipment.
Smart Images

Figure CN119182799A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of vehicle networking, and specifically relates to a data interaction method, system, terminal and storage medium for vehicle networking. Background Art
[0002] Efficient and real-time data interaction between vehicles and roadside equipment is undoubtedly a core link in promoting intelligent driving technology to a new level. As vehicles travel in a constantly changing road environment, the real-time update of their location information becomes the basis for accurate interaction with surrounding infrastructure. Therefore, vehicles need to be able to establish and maintain stable data connections with various roadside equipment deployed along their path (such as traffic lights, smart parking systems, road condition monitoring stations, etc.) to achieve seamless exchange and sharing of information.
[0003] However, how vehicles can quickly establish a secure and reliable communication connection with roadside equipment in the direction of travel is a prerequisite for efficient communication. If a secure and reliable communication connection cannot be established quickly with roadside equipment, data interaction will be delayed or impossible to achieve. Summary of the invention
[0004] In view of the above-mentioned deficiencies in the prior art, the present invention provides a data interaction method, system, terminal and storage medium for an Internet of Vehicles to solve the above-mentioned technical problems.
[0005] In a first aspect, the present invention provides a data interaction method for an Internet of Vehicles, comprising: Acquiring positioning data of the vehicle-mounted terminal, and predicting a travel path of the vehicle-mounted terminal based on the positioning data; Retrieving the device type and authentication information of the target roadside device from the blockchain, the authentication information including the device identity and the public key, and the location information of the target roadside device is on the driving path; Confirming, based on the device type, that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal; The authentication information is sent to the vehicle-mounted terminal, so that the vehicle-mounted terminal establishes a wireless communication connection with a roadside device on the driving path based on the authentication information.
[0006] In an optional implementation, obtaining positioning data of the vehicle-mounted terminal and predicting the driving path of the vehicle-mounted terminal based on the positioning data includes: Arrange the positioning data of the vehicle-mounted terminal collected regularly within a specified period in the order of collection time to obtain a positioning data sequence; Matching the positioning data sequence with a pre-built path topology to obtain a current driving path and driving direction; Taking the latest positioning data as a positioning point, selecting from the path topology a road section whose distance from the positioning point is within a preset predicted distance range, and the road section is in the driving direction; The filtered road segments are output as the predicted driving route.
[0007] In an optional embodiment, the method further comprises: Obtaining the device location, public key certificate, and device data of the roadside device, wherein the device data includes device type, device code, and manufacturer information; Acquire a public key of the roadside device based on the public key certificate; Verifying the device data using pre-set verification rules, and generating a device identity after the verification passes; Applying for a block for the roadside device in the blockchain, and storing the device location, public key, device identity and device data of the roadside device in the block; The device identity is encrypted using the public key, and the encrypted device identity is sent to the roadside device; the roadside device decrypts the encrypted device identity using the private key and saves the device identity.
[0008] In an optional implementation, the device type and authentication information of the target roadside device are retrieved from the blockchain, the authentication information including the device identity and the public key, and the location information of the target roadside device on the driving path includes: Generate a location query request based on the coordinate set of the driving path, and send the location query request to the blockchain; The blockchain executes the smart contract, queries the device location that matches the coordinate set of the driving path, and outputs the queried device location as the target device location; The device type and authentication information of the target roadside device to which the target device position belongs are output as the query result.
[0009] In an optional implementation, confirming that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal based on the device type includes: Pre-set various specific device types that need to establish communication connections with the vehicle terminal; Determine whether the device type of the target roadside device belongs to a specific device type: If yes, confirming that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal; If not, it is confirmed that the target roadside device does not need to establish a communication connection with the vehicle-mounted terminal, and the target roadside device is ignored.
[0010] In an optional embodiment, the method further comprises: The vehicle terminal receives the authentication information and creates a folder in a specified directory to save the authentication information; The wireless communication search interface of the vehicle terminal searches for a new device; The vehicle-mounted terminal sends a request for obtaining an identity identifier to the new device; The vehicle terminal receives the response data of the new device to the request, and decrypts the response data using the public key in the folder to obtain the data to be verified; the response data is the device identity encrypted by the new device using its own private key; The vehicle terminal compares the consistency between the data to be verified and the device identity in the folder, and if the verification is successful, determines that the new device is a trusted device; The vehicle terminal establishes a wireless communication connection with the trusted device.
[0011] In a second aspect, the present invention provides a data interaction system for an Internet of Vehicles, comprising: A positioning processing module, used to obtain positioning data of the vehicle-mounted terminal and predict the driving path of the vehicle-mounted terminal based on the positioning data; A target query module, used to retrieve the device type and authentication information of the target roadside device from the blockchain, the authentication information including the device identity and public key, and the location information of the target roadside device is on the driving path; A type determination module, used to confirm that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal based on the device type; The communication establishment module is used to send the authentication information to the vehicle-mounted terminal so that the vehicle-mounted terminal establishes a wireless communication connection with the roadside equipment on the driving path based on the authentication information.
[0012] In an optional implementation, the positioning processing module includes: A sequence generating unit, used to arrange the positioning data of the vehicle-mounted terminal collected regularly within a specified period in the order of collection time to obtain a positioning data sequence; A path matching unit, used to match the positioning data sequence with a pre-built path topology to obtain a current driving path and driving direction; A target positioning unit, used to use the latest positioning data as a positioning point, and to select from the path topology a road section whose distance from the positioning point is within a preset predicted distance range, and the road section is in the driving direction; The prediction output unit is used to output the screened road sections as predicted driving routes.
[0013] In a third aspect, a terminal is provided, including: processor, memory, wherein: The memory is used to store computer programs. The processor is used to call and run the computer program from the memory, so that the terminal executes the above-mentioned terminal method.
[0014] According to a fourth aspect, a computer storage medium is provided, wherein the computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the computer executes the methods described in the above aspects.
[0015] The beneficial effect of the present invention lies in that the data interaction method, system, terminal and storage medium of the Internet of Vehicles provided by the present invention predict the driving position of the vehicle, and then send the authentication information of the roadside equipment at the corresponding position to the vehicle-mounted terminal. After entering the range of the wireless communication signal, the vehicle-mounted terminal immediately establishes a wireless communication connection with the corresponding roadside equipment based on the authentication information, thereby ensuring the timeliness and security of data interaction.
[0016] In addition, the invention has a reliable design principle, a simple structure and a very broad application prospect. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0018] Figure 1 is a schematic flow chart of a method according to an embodiment of the present invention.
[0019] Figure 2 is a schematic block diagram of a system according to an embodiment of the present invention.
[0020] Figure 3 A schematic diagram of the structure of a terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0021] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.
[0022] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used in the specification of the present invention herein are only for the purpose of describing specific embodiments and are not intended to limit the present invention.
[0023] The data interaction method of the Internet of Vehicles provided in the embodiment of the present invention is executed by a computer device, and accordingly, the data interaction system of the Internet of Vehicles runs in the computer device.
[0024] Figure 1 is a schematic flow chart of a method according to an embodiment of the present invention. Figure 1 The execution subject may be a data interaction system of a vehicle network. According to different requirements, the order of the steps in the flowchart may be changed, and some may be omitted.
[0025] like Figure 1 As shown, the method includes: Step 110, obtaining positioning data of the vehicle-mounted terminal, and predicting a travel path of the vehicle-mounted terminal based on the positioning data; Step 120, retrieve the device type and authentication information of the target roadside device from the blockchain, the authentication information includes the device identity and public key, and the location information of the target roadside device is on the driving path; Step 130, confirming that the target roadside device needs to establish a communication connection with the vehicle terminal based on the device type; Step 140: Send the authentication information to the vehicle-mounted terminal, so that the vehicle-mounted terminal establishes a wireless communication connection with a roadside device on the driving path based on the authentication information.
[0026] To facilitate understanding of the present invention, the data interaction method for the Internet of Vehicles provided by the present invention is further described below based on the principle of the data interaction method for the Internet of Vehicles of the present invention and in combination with the process of managing the data interaction for the Internet of Vehicles in the embodiment.
[0027] Specifically, the data interaction methods of the Internet of Vehicles include: S1. Acquire positioning data of a vehicle-mounted terminal, and predict a driving path of the vehicle-mounted terminal based on the positioning data.
[0028] The current location information is captured with high precision through the built-in GPS module of the vehicle terminal or in combination with other positioning technologies (such as Beidou, GLONASS, etc.). Subsequently, the collected positioning data is processed using advanced map matching algorithms and big data analysis technologies to eliminate noise and errors and ensure the accuracy of the data. Based on the processed positioning data, combined with historical driving records, real-time traffic conditions and road conditions, machine learning or deep learning models are used to predict the future driving path of the vehicle terminal, including possible turning points, estimated arrival time, etc.
[0029] In one embodiment, the positioning data of the vehicle-mounted terminal is obtained, and the driving path of the vehicle-mounted terminal is predicted based on the positioning data, including: arranging the positioning data of the vehicle-mounted terminal collected regularly within a specified period in the order of collection time to obtain a positioning data sequence; matching the positioning data sequence with a pre-constructed path topology to obtain the current driving path and driving direction; using the latest positioning data as a positioning point, filtering out from the path topology a road section whose distance from the positioning point is within a pre-set predicted distance range, and the road section is in the driving direction; and outputting the filtered road section as a predicted driving path.
[0030] The specific process includes: The positioning data collected regularly by the vehicle terminal within a specified period is arranged in a strict collection time sequence. This process ensures the timeliness and continuity of the data, thus forming a positioning data sequence. Each piece of positioning data records the precise location of the vehicle terminal at a certain moment. The collection of these location points provides a solid foundation for subsequent analysis.
[0031] Next, this ordered positioning data sequence is compared and matched with a pre-built, high-precision path topology map. The path topology map is an abstract representation of the actual road network, which contains key information such as the road geometry, nodes (such as intersections), road sections and their connection relationships. Through a complex matching algorithm, the driving trajectory represented by the positioning data sequence can be identified, and the current driving path and driving direction of the vehicle terminal can be determined accordingly.
[0032] In order to further predict the future driving path, the latest received positioning data is used as the current positioning point, which is the basis for prediction. Then, according to the pre-set prediction distance range, all possible road sections within this range from the current positioning point are searched in the path topology map. This prediction distance range is based on a comprehensive consideration of multiple factors, including the average driving speed of the vehicle, road conditions, traffic flow, etc., to ensure the rationality and accuracy of the prediction.
[0033] After selecting the qualified sections, it is necessary to further determine whether these sections are located in the current driving direction. This is achieved by comparing the angle between the extension direction of the section and the current driving direction of the vehicle terminal. Only when the angle is less than a preset threshold, the section is considered to be a possible future driving path.
[0034] Finally, all the road sections that meet the conditions are output as predicted driving paths. These prediction results not only help traffic management departments monitor traffic conditions in real time and optimize road planning and management, but also provide navigation services for vehicle terminals, helping drivers plan driving routes in advance to avoid congestion and delays. At the same time, by continuously updating positioning data and path topology maps, the prediction results can be adjusted in real time to ensure the accuracy and timeliness of the prediction.
[0035] S2. Retrieve the device type and authentication information of the target roadside device from the blockchain, where the authentication information includes a device identity and a public key, and the location information of the target roadside device is on the driving path.
[0036] Using the decentralized and tamper-proof characteristics of blockchain, a distributed ledger containing roadside equipment information is constructed. Based on the predicted driving path in step S1, the smart contract automatically triggers a query request to retrieve detailed information of all target roadside equipment located on the path from the blockchain network. This information includes but is not limited to the device type (such as charging piles, signal boosters, emergency rescue stations, etc.), device identity (unique identification code), public key, and the latest location coordinates. The public key is used for encryption verification of subsequent secure communications.
[0037] In one embodiment, authentication information is generated in advance for a roadside device, and the information of the roadside device is uploaded to the blockchain, specifically including: (1) Obtaining the device location, public key certificate, and device data of the roadside device, wherein the device data includes the device type, device code, and manufacturer information.
[0038] The device location (such as GPS coordinates), public key certificate (including the public key and the signature of the certificate issuer, used to verify the authenticity of the public key) and device data of roadside devices are obtained through physical connection or wireless communication. Device data usually includes device code (used to uniquely identify the device) and manufacturer information (such as manufacturer name, model, etc.), which is crucial for subsequent device management and maintenance.
[0039] (2) Obtaining the public key of the roadside device based on the public key certificate.
[0040] Based on the obtained public key certificate, a standard certificate verification algorithm (such as the certificate verification process in the PKI system) is used to verify the validity of the certificate and extract the public key of the roadside device from it. This step is key to ensuring the authenticity and reliability of the public key when communicating with the device.
[0041] (3) Verify the device data using pre-set verification rules and generate a device identity after the verification is successful.
[0042] The device data is strictly verified using pre-set verification rules (such as checking whether the length and format of the device code meet the specifications and whether the manufacturer information exists in the trusted list). After the verification is passed, a unique device identity token (DIT) is generated for the roadside device, which will serve as the device's identity credential in the network.
[0043] (4) Applying for a block for the roadside device in the first blockchain, and storing the device location, public key, and device identity of the roadside device in the block.
[0044] Apply for a block for the roadside device in the first blockchain (which may be a blockchain designed specifically for device registration and management). In this block, store the device location of the roadside device, the extracted public key, and the generated device identity. The immutability and decentralization of the blockchain ensure the security and credibility of this information.
[0045] (5) Encrypting the device identity using the public key and sending the encrypted device identity to the roadside device; the roadside device decrypting the encrypted device identity using the private key and saving the device identity.
[0046] (6) To ensure the security of the device identity during transmission, the device identity is encrypted using the public key extracted from the public key certificate. The encrypted device identity is sent to the roadside device through a secure channel (such as a TLS encrypted communication link). This step prevents the identity from being stolen or tampered with during transmission. After receiving the encrypted device identity, the roadside device uses its own private key to decrypt it. After successful decryption, the roadside device saves the device identity in a local secure storage area for use in subsequent communications with. This step completes the formal registration and identity authentication process of the roadside device in.
[0047] A location query request is generated based on the coordinate set of the driving path, and the location query request is sent to the blockchain; the blockchain executes the smart contract, queries the device location that matches the coordinate set of the driving path, and outputs the queried device location as the target device location; the device type and authentication information of the target roadside device to which the target device location belongs are output as the query result.
[0048] S3. Confirming that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal based on the device type.
[0049] Pre-set multiple specific device types that need to establish a communication connection with the vehicle-mounted terminal; determine whether the device type of the target roadside device belongs to the specific device type: if so, confirm that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal; if not, confirm that the target roadside device does not need to establish a communication connection with the vehicle-mounted terminal, and ignore the target roadside device.
[0050] Specifically, based on the type of target roadside equipment, the system evaluates the services or interactions that the vehicle terminal may need during driving. For example, if the predicted path includes a charging pile and the battery level of the vehicle is lower than the preset threshold, it is confirmed that a communication connection needs to be established with the roadside equipment of the charging pile type in order to make an appointment for charging service or obtain real-time charging status information. This step also involves an evaluation of the current status of the vehicle terminal (such as fuel level, power level, vehicle speed, etc.) to ensure the necessity and effectiveness of the communication connection.
[0051] S4. Send the authentication information to the vehicle-mounted terminal, so that the vehicle-mounted terminal establishes a wireless communication connection with a roadside device on the driving path based on the authentication information.
[0052] Under the premise of ensuring data security and privacy protection, the authentication information of the target roadside device (including device identity and public key) is securely sent to the vehicle terminal through an encrypted channel. After receiving this information, the vehicle terminal uses the public key for identity authentication and starts the corresponding communication protocol (such as Wi-Fi, Bluetooth, LoRa, etc.) to establish a stable wireless communication connection with the roadside device on the driving path. This process not only ensures the security of communication, but also improves the efficiency and reliability of the connection, providing the vehicle terminal with a one-stop intelligent service experience such as road condition information, service appointment, emergency rescue, etc.
[0053] The method for establishing a communication connection between a vehicle-mounted terminal and a roadside device includes: the vehicle-mounted terminal receives the authentication information, creates a folder in a specified directory to save the authentication information; the wireless communication search interface of the vehicle-mounted terminal searches for a new device; the vehicle-mounted terminal sends a request to the new device to obtain an identity identifier; the vehicle-mounted terminal receives response data from the new device to the request, decrypts the response data using the public key in the folder to obtain data to be verified; the response data is a device identity identifier encrypted by the new device using its own private key; the vehicle-mounted terminal compares the consistency between the data to be verified and the device identity identifier in the folder, and if the verification is successful, determines that the new device is a trusted device; and the vehicle-mounted terminal establishes a wireless communication connection with the trusted device.
[0054] Specifically, after receiving the authentication information sent by the background system, the vehicle terminal will first automatically create an encrypted folder (or a file storage area protected by other security measures) in a specified directory in its storage system to safely store these sensitive information. This folder uses access control mechanisms (such as permission settings, encryption protection, etc.) to ensure that only authorized applications or services can access the contents, thereby protecting the authentication information from unauthorized access or tampering.
[0055] Then, the wireless communication search interface of the vehicle terminal starts working, and it automatically scans the available wireless devices in the surrounding environment, including those roadside devices that may be located on the predicted driving path. When a new device is found, the vehicle terminal records its relevant information and prepares to establish a communication connection.
[0056] In order to verify the identity of the new device, the vehicle terminal will actively send a request to the new device, asking the other party to provide its device identity. This request is sent through a pre-set wireless communication protocol, ensuring the security and reliability of the request.
[0057] After receiving the request, the new device will use its own private key to encrypt the device identity, generate an encrypted response data, and send it back to the vehicle terminal through the wireless communication interface. This process utilizes the characteristics of asymmetric encryption technology, that is, only the entity with the corresponding public key can decrypt the data encrypted by the corresponding private key.
[0058] After receiving the response data from the new device, the vehicle terminal will first retrieve the public key corresponding to the new device from the previously created encrypted folder. Then, it will use this public key to decrypt the encrypted response data to obtain the decrypted data to be verified, that is, the device identity of the new device.
[0059] Next, the vehicle terminal will perform a critical comparison step: it will compare the decrypted data to be verified with the device identity stored in the folder and obtained in advance from the blockchain or other trusted sources. This comparison process is highly dependent on the accuracy and consistency of the data and is the core link in verifying the identity of a new device.
[0060] If the comparison result shows that the data to be verified is completely consistent with the device identity in the folder, the vehicle terminal will determine that the new device is a trusted device and continue to perform subsequent steps to establish a wireless communication connection. This connection will be based on a secure communication protocol to ensure the confidentiality, integrity and availability of data transmission.
[0061] Once the connection is successfully established, various data transmission and interaction operations can be carried out between the vehicle terminal and the trusted device, including but not limited to data transmission, service requests, status updates, etc., thereby providing the vehicle terminal with a richer and smarter service experience.
[0062] In some embodiments, the data interaction system of the Internet of Vehicles may include multiple functional modules composed of computer program segments. The computer programs of each program segment in the data interaction system of the Internet of Vehicles may be stored in a memory of a computer device and executed by at least one processor to perform (see Figure 1 Description) The function of data interaction in the Internet of Vehicles.
[0063] In this embodiment, the data interaction system of the Internet of Vehicles can be divided into multiple functional modules according to the functions it performs, such as Figure 2 As shown. The functional modules of the system 200 may include: a positioning processing module 210, a target query module 220, a type determination module 230 and a communication establishment module 240. The module referred to in the present invention refers to a series of computer program segments that can be executed by at least one processor and can complete fixed functions, which are stored in a memory. In this embodiment, the functions of each module will be described in detail in subsequent embodiments.
[0064] A positioning processing module, used to obtain positioning data of the vehicle-mounted terminal and predict the driving path of the vehicle-mounted terminal based on the positioning data; A target query module, used to retrieve the device type and authentication information of the target roadside device from the blockchain, the authentication information including the device identity and public key, and the location information of the target roadside device is on the driving path; A type determination module, used to confirm that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal based on the device type; The communication establishment module is used to send the authentication information to the vehicle-mounted terminal so that the vehicle-mounted terminal establishes a wireless communication connection with the roadside equipment on the driving path based on the authentication information.
[0065] Optionally, as an embodiment of the present invention, the positioning processing module includes: A sequence generating unit, used to arrange the positioning data of the vehicle-mounted terminal collected regularly within a specified period in the order of collection time to obtain a positioning data sequence; A path matching unit, used to match the positioning data sequence with a pre-built path topology to obtain a current driving path and driving direction; A target positioning unit, used to use the latest positioning data as a positioning point, and to select from the path topology a road section whose distance from the positioning point is within a preset predicted distance range, and the road section is in the driving direction; The prediction output unit is used to output the screened road sections as predicted driving routes.
[0066] Figure 3 The present invention is a schematic diagram of the structure of a terminal 300 provided in an embodiment of the present invention. The terminal 300 can be used to execute the data interaction method of the Internet of Vehicles provided in an embodiment of the present invention.
[0067] The terminal 300 may include: a processor 310, a memory 320 and a communication unit 330. These components communicate via one or more buses. Those skilled in the art will appreciate that the server structure shown in the figure does not limit the present invention, and it may be a bus structure or a star structure, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.
[0068] The memory 320 can be used to store the execution instructions of the processor 310, and the memory 320 can be implemented by any type of volatile or non-volatile storage terminal or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. When the execution instructions in the memory 320 are executed by the processor 310, the terminal 300 can perform some or all of the steps in the following method embodiments.
[0069] The processor 310 is the control center of the storage terminal, and uses various interfaces and lines to connect various parts of the entire electronic terminal. It runs or executes software programs and / or modules stored in the memory 320, and calls data stored in the memory to perform various functions of the electronic terminal and / or process data. The processor can be composed of an integrated circuit (IC), for example, it can be composed of a single packaged IC, or it can be composed of multiple packaged ICs with the same or different functions. For example, the processor 310 can only include a central processing unit (CPU). In the embodiment of the present invention, the CPU can be a single computing core or multiple computing cores.
[0070] The communication unit 330 is used to establish a communication channel so that the storage terminal can communicate with other terminals, receive user data sent by other terminals or send user data to other terminals.
[0071] The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and when the program is executed, the program may include some or all of the steps in each embodiment provided by the present invention. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM).
[0072] Therefore, the present invention predicts the vehicle's driving position, and then sends the authentication information of the roadside equipment at the corresponding position to the vehicle-mounted terminal. After entering the wireless communication signal range, the vehicle-mounted terminal immediately establishes a wireless communication connection with the corresponding roadside equipment based on the authentication information, thereby ensuring the timeliness and security of data interaction. The technical effects that can be achieved by this embodiment can be found in the description above and will not be repeated here.
[0073] Those skilled in the art can clearly understand that the technology in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution in the embodiments of the present invention, in essence or in other words, the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes, including several instructions for enabling a computer terminal (which can be a personal computer, a server, or a second terminal, a network terminal, etc.) to execute all or part of the steps of the methods described in each embodiment of the present invention.
[0074] In this specification, the same or similar parts between the various embodiments can be referred to each other. In particular, for the terminal embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description in the method embodiment.
[0075] In the several embodiments provided by the present invention, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of systems or modules, which can be electrical, mechanical or other forms.
[0076] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0077] In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.
[0078] Although the present invention has been described in detail with reference to the accompanying drawings and in combination with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, a person of ordinary skill in the art may make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions shall be within the scope of the present invention. Any person of ordinary skill in the art may easily think of changes or substitutions within the technical scope disclosed by the present invention, and these shall be within the scope of protection of the present invention.
Claims
1. A data interaction method for an Internet of Vehicles, characterized in that: include: Acquiring positioning data of the vehicle-mounted terminal, and predicting a travel path of the vehicle-mounted terminal based on the positioning data; Retrieving the device type and authentication information of the target roadside device from the blockchain, the authentication information including the device identity and the public key, and the location information of the target roadside device is on the driving path; Confirming, based on the device type, that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal; The authentication information is sent to the vehicle-mounted terminal, so that the vehicle-mounted terminal establishes a wireless communication connection with a roadside device on the driving path based on the authentication information.
2. The method according to claim 1, characterized in that Acquiring positioning data of a vehicle-mounted terminal and predicting a driving path of the vehicle-mounted terminal based on the positioning data, including: Arrange the positioning data of the vehicle-mounted terminal collected regularly within a specified period in the order of collection time to obtain a positioning data sequence; Matching the positioning data sequence with a pre-built path topology to obtain a current driving path and driving direction; Taking the latest positioning data as a positioning point, selecting from the path topology a road section whose distance from the positioning point is within a preset predicted distance range, and the road section is in the driving direction; The filtered road segments are output as the predicted driving route.
3. The method according to claim 1, characterized in that: The method further comprises: Obtaining the device location, public key certificate, and device data of the roadside device, wherein the device data includes device type, device code, and manufacturer information; Acquire a public key of the roadside device based on the public key certificate; Verifying the device data using pre-set verification rules, and generating a device identity after the verification passes; Applying for a block for the roadside device in the blockchain, and storing the device location, public key, device identity and device data of the roadside device in the block; The device identity is encrypted using the public key, and the encrypted device identity is sent to the roadside device; the roadside device decrypts the encrypted device identity using the private key and saves the device identity.
4. The method according to claim 3, characterized in that The device type and authentication information of the target roadside device are retrieved from the blockchain, wherein the authentication information includes the device identity and the public key, and the location information of the target roadside device is on the driving path, including: Generate a location query request based on the coordinate set of the driving path, and send the location query request to the blockchain; The blockchain executes the smart contract, queries the device location that matches the coordinate set of the driving path, and outputs the queried device location as the target device location; The device type and authentication information of the target roadside device to which the target device position belongs are output as the query result.
5. The method according to claim 1, characterized in that Confirming that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal based on the device type includes: Pre-set various specific device types that need to establish communication connections with the vehicle terminal; Determine whether the device type of the target roadside device belongs to a specific device type: If yes, confirming that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal; If not, it is confirmed that the target roadside device does not need to establish a communication connection with the vehicle-mounted terminal, and the target roadside device is ignored.
6. The method according to claim 1, characterized in that The method further comprises: The vehicle terminal receives the authentication information and creates a folder in a specified directory to save the authentication information; The wireless communication search interface of the vehicle terminal searches for a new device; The vehicle-mounted terminal sends a request for obtaining an identity identifier to the new device; The vehicle terminal receives the response data of the new device to the request, and decrypts the response data using the public key in the folder to obtain the data to be verified; the response data is the device identity encrypted by the new device using its own private key; The vehicle terminal compares the consistency between the data to be verified and the device identity in the folder, and if the verification is successful, determines that the new device is a trusted device; The vehicle terminal establishes a wireless communication connection with the trusted device.
7. A data interaction system for Internet of Vehicles, characterized in that: include: A positioning processing module, used to obtain positioning data of the vehicle-mounted terminal and predict the driving path of the vehicle-mounted terminal based on the positioning data; A target query module, used to retrieve the device type and authentication information of the target roadside device from the blockchain, the authentication information including the device identity and public key, and the location information of the target roadside device is on the driving path; A type determination module, used to confirm that the target roadside device needs to establish a communication connection with the vehicle-mounted terminal based on the device type; The communication establishment module is used to send the authentication information to the vehicle-mounted terminal so that the vehicle-mounted terminal establishes a wireless communication connection with the roadside equipment on the driving path based on the authentication information.
8. The system according to claim 7, characterized in that The positioning processing module includes: A sequence generating unit, used to arrange the positioning data of the vehicle-mounted terminal collected regularly within a specified period in the order of collection time to obtain a positioning data sequence; A path matching unit, used to match the positioning data sequence with a pre-built path topology to obtain a current driving path and driving direction; A target positioning unit, used to use the latest positioning data as a positioning point, and to select from the path topology a road section whose distance from the positioning point is within a preset predicted distance range, and the road section is in the driving direction; The prediction output unit is used to output the screened road sections as predicted driving routes.
9. A terminal, characterized in that: include: A memory, used to store data interaction programs of the Internet of Vehicles; A processor is used to implement the steps of the data interaction method for the Internet of Vehicles as described in any one of claims 1 to 6 when executing the data interaction program for the Internet of Vehicles.
10. A computer-readable storage medium storing a computer program, characterized in that: The readable storage medium stores a data interaction program for the Internet of Vehicles, and when the data interaction program for the Internet of Vehicles is executed by a processor, the steps of the data interaction method for the Internet of Vehicles as described in any one of claims 1 to 6 are implemented.
