CN107508927B - Future Internet of vehicles data communication method based on cloud - Google Patents

Future Internet of vehicles data communication method based on cloud Download PDF

Info

Publication number
CN107508927B
CN107508927B CN201710752169.6A CN201710752169A CN107508927B CN 107508927 B CN107508927 B CN 107508927B CN 201710752169 A CN201710752169 A CN 201710752169A CN 107508927 B CN107508927 B CN 107508927B
Authority
CN
China
Prior art keywords
data
cloud
address
node
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201710752169.6A
Other languages
Chinese (zh)
Other versions
CN107508927A (en
Inventor
王晓喃
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Changshu Institute of Technology
Original Assignee
Changshu Institute of Technology
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Changshu Institute of Technology filed Critical Changshu Institute of Technology
Priority to CN201710752169.6A priority Critical patent/CN107508927B/en
Publication of CN107508927A publication Critical patent/CN107508927A/en
Application granted granted Critical
Publication of CN107508927B publication Critical patent/CN107508927B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/604—Address structures or formats
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/122—Shortest path evaluation by minimising distances, e.g. by selecting a route with minimum of number of hops
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/69—Types of network addresses using geographic information, e.g. room number

Abstract

The invention provides a future vehicle networking data communication method based on cloud, wherein the vehicle networking comprises an access node and a vehicle node; the vehicle node has a route forwarding function, and the access node is connected with the Internet; the geographic coordinates of each access node are unique; the vehicle nodes realize communication through the access node closest to the vehicle nodes, and one access node and all the vehicle nodes realizing communication through the access node form a sub-network. The vehicle node can acquire the service data from the nearest cloud member through the implementation method provided by the invention, thereby shortening the delay and cost for acquiring the service data, improving the service quality.

Description

Future Internet of vehicles data communication method based on cloud
Technical Field
The invention relates to a data communication method, in particular to a future vehicle networking data communication method based on cloud.
Background
The cloud is a service mode which is built on the internet of vehicles and can provide local services. In recent years, much research has been devoted to the internet of vehicles in order to enable vehicle drivers to quickly obtain network services. With the development of the car networking technology, car networking will become a mode for providing services in the future.
At present, the implementation mode of the internet of vehicles is realized through broadcasting, so that both delay and cost are large, and the network service performance is reduced. Therefore, how to reduce the delay and cost of providing services through the internet of vehicles becomes a hot issue of research in recent years.
Disclosure of Invention
The purpose of the invention is as follows: the invention aims to solve the technical problem of providing a future vehicle networking data communication method based on cloud aiming at the defects of the prior art. According to the invention, data communication of the Internet of vehicles is realized through the cloud, so that data communication delay and cost are reduced, and network service performance is effectively improved.
The technical scheme is as follows: the invention discloses a future vehicle networking data communication method based on cloud, wherein the vehicle networking comprises an access node and a vehicle node; the vehicle node has a route forwarding function, and the access node is connected with the Internet; the geographic coordinates of each access node are unique; the vehicle nodes realize communication through the access node closest to the vehicle nodes, and one access node and all the vehicle nodes realizing communication through the access node form a sub-network;
the vehicle node and the access node are collectively called as equipment nodes;
each access node maintains an access node table, each access node table entry comprises a geographic location coordinate domain and a network prefix domain, and the access node table is configured in advance, for example, the network prefix of the access node with geographic coordinates (x1, y1) is 3FEC:1:1: 1/64;
a geographical range related data is defined by a data name, a data name comprising four parts: geographic abscissa, geographic ordinate, subnet identification, and data ID; the geographic abscissa, the geographic ordinate and the subnet identification of the data name define a geographic range, and the data ID defines a data type; when the subnet identification is 1, the geographic range is the subnet where the geographic coordinate is located, and when the subnet identification is 0, the geographic range is a one-hop range where the geographic coordinate is located, namely a circle with the geographic coordinate as a center and the radius as a transmission radius; the maximum lifetime of the data relating to the geographical range is preset, typically with a set value range of, for example, 60 min;
the unicast addresses of the vehicle node and the access node are composed of a network prefix and a link address, and the link address is composed of a geographic abscissa, a geographic ordinate and a node ID; the node ID of the vehicle node is the hardware ID of the vehicle node, such as an MAC address; the unicast address of the access node is preset, and the node ID is 0; the node ID of the vehicle node is kept unchanged, if the geographic coordinate of the vehicle node changes, the link address of the unicast address also changes, the node ID in the link address is the node ID of the vehicle node, and the geographic coordinate is the current geographic abscissa and geographic ordinate of the vehicle node;
the cloud is composed of more than two vehicle nodes, each vehicle node is called a cloud member, the cloud members cooperate with each other to create data related to a geographic range, and the cloud is defined by a data name defining the data; the vehicle node acquires data by adopting a cloud address, wherein the cloud address is composed of a network prefix and a link address, and the link address is composed of a geographic horizontal coordinate, a geographic vertical coordinate, a subnet identifier and a data ID; the link address of the cloud address corresponds to a data name;
each cloud member stores a cloud data table for storing data which can be provided by the cloud member, and each cloud data table is composed of three fields: a data name field, a data field, and a lifecycle field; if the life cycle attenuation of one cloud data table entry is 0, deleting the table entry from the cloud data table by the cloud member;
each vehicle node stores a cloud index table used for storing information of the members of the sub-network cloud where the vehicle node is located, and each cloud index table is composed of three domains: a data name field, a link address field of a unicast address and a life cycle field; if the life cycle attenuation of one cloud index table entry is 0, deleting the table entry from the cloud index table;
if the data C1 is composed of the data name CN1, the geographic abscissa and the geographic ordinate (xCN1, yCN1) of the data name CN1 are located within the subnet S1, the subnet identification of the data name CN1 is 0, and the data ID is CID1, the device node D1 located at (xCN1, yCN1) constructs a cloud VC1 and creates data C1 by:
step 101: starting;
step 102: the device node D1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the device node D1, in the cloud address, the network prefix is 0, and the link address is the data name CN1, and then the device node D1 sends a constructed cloud message, wherein the source address of the constructed cloud message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 103: after receiving the constructed cloud message, if a part of the data C1 or the data C1 can be generated or provided, constructing a unicast address, wherein the network prefix is 0, the link address is the link address of the neighbor device node, then the neighbor device node sends a cloud response message, the source address of the cloud response message is the constructed unicast address, the destination address is the source address of the cloud message, and the load is the generated or provided data;
step 104: within a specified time, for example, 1s, the device node D1 checks all received cloud response messages, constructs a load in the cloud response messages as data C1, and then sends a cloud sharing message, where a source address of the cloud sharing message is a unicast address constructed in step 102, a destination address is the cloud address constructed in step 102, and the load is data C1; the device node D1 creates a cloud data entry, where the data name domain value of the cloud data entry is CN1, the data domain value is data C1, and the lifetime is the maximum lifetime of the data type, for example, 10 mins; the device node D1 creates a cloud index table entry, the data name domain value of the cloud index table entry is CN1, the link address value is the link address of the unicast address of the device node D1, the survival time is the maximum survival time of the data type, for example 10mins, and the device node D1 identifies itself as a member of the cloud VC 1;
step 105: after receiving the cloud sharing message, the neighbor device node creates a cloud data table entry, the data name domain value of the cloud data table entry is CN1, the data domain value is data C1, the lifetime is the maximum lifetime of the data type, and meanwhile, a cloud index table entry is created, the data name domain value of the cloud index table entry is CN1, the link address value is the link address of the unicast address of the neighbor device node, the lifetime is the maximum lifetime of the data type, and the neighbor device node identifies the neighbor device node as a member of the cloud VC 1;
step 106: and (6) ending.
The process can construct the cloud and the data, so that the user can be ensured to acquire the data from the cloud member quickly.
In the method of the present invention, if the data C2 is composed of a data name CN2, the geographic abscissa and geographic ordinate (xCN2, yCN2) of the data name CN2 are located in the subnet S1, the subnet identifier of the data name CN1 is 1, and the data ID is CID2, the device node D1 located at (xCN2, yCN2) constructs a cloud VC2 and creates data C2 by the following procedures:
step 201: starting;
step 202: the device node D1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the device node D1, in the cloud address, the network prefix is 0, the link address is the data name CN2, the device node D1 sends a constructed cloud message, the source address of the constructed cloud message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 203: after receiving the build cloud message, if the neighbor device node is located in the subnet S1, the neighbor device node executes step 205, otherwise, executes step 204:
step 204: the neighbor device node discards the received constructed cloud message, and executes step 206;
step 205: if the neighbor device node can generate or provide a part of the data C2 or the data C2, a unicast address is constructed, the network prefix is 0, the link address is the link address of the neighbor device node, then the neighbor device node sends a cloud response message, the source address of the cloud response message is the constructed unicast address, the destination address is the source address of the cloud message, and the load is the generated or provided data; the neighbor device node forwards the received constructed cloud message, and executes step 203;
step 206: within a specified time, for example, 1s, the device node D1 checks all received cloud response messages, constructs a load in the cloud response messages as data C2, and then sends a cloud sharing message, where a source address of the cloud sharing message is the unicast address constructed in step 202, a destination address is the cloud address constructed in step 202, and the load is data C2; the device node D1 creates a cloud data entry, where the data name domain value of the cloud data entry is CN2, the data domain value is data C2, and the lifetime is the maximum lifetime of the data type, for example, 10 mins; the device node D1 creates a cloud index table entry, the data name domain value of the cloud index table entry is CN2, the link address value is the link address of the unicast address of the device node D, the survival time is the maximum survival time of the data type, for example, 10mins, and the device node D1 identifies the device node D as a member of cloud VC 2;
step 207: after receiving the cloud sharing message, if the neighbor device node is located in the subnet S1, executing step 209, otherwise executing step 208;
step 208: the neighbor device node discards the received cloud sharing message, and executes step 210;
step 209: the neighbor device nodes create a cloud data table entry, the data name field value of the cloud data table entry is CN2, the data field value is C2, the lifetime is the maximum lifetime of the data type, and meanwhile, a cloud index table entry is created, the data name field value of the cloud index table entry is CN2, the link address value is the link address of the unicast address of the neighbor device node, the lifetime is the maximum lifetime of the data type, and the neighbor device nodes identify the neighbor device node as a member of the cloud VC 2; the neighbor device node forwards the received cloud sharing message, and executes step 207;
step 210: finishing;
the process can construct the cloud and the data, so that the user can be ensured to acquire the data from the cloud member quickly.
In the method, each equipment node regularly broadcasts a beacon message, the source address of the beacon message is the unicast address of the equipment node, and the network prefix in the unicast address is 0; if the geographic coordinate of the cloud member changes, the cloud index table item of which the node ID of the link address domain value is equal to the node ID of the cloud index table item is searched, and the geographic horizontal coordinate and the geographic vertical coordinate of the link address domain value of the cloud index table item are updated to the current geographic horizontal coordinate and the current geographic vertical coordinate of the cloud index table item;
if the device node detects that the cloud index table entry in the cloud index table of the device node is updated, the updated cloud index table entry is used as the load content of the next beacon message;
after the device node D1 located in the subnet S1 and having geographic coordinates (x1, y1) receives the beacon message of the neighboring device node under the conditions that the access node of the subnet S1 is AP1, the geographic coordinates are (xAP1, yAP1), the access node of the subnet S2 is AP2, and the geographic coordinates are (xAP2, yAP2), if the beacon message includes the cloud index table, the device node D1 updates the cloud index table as follows:
step 301: starting;
step 302: the device node D1 looks at the cloud index table in the beacon message payload, and for each cloud index entry E in the cloud index table, performs the following operations: if the data name domain value equal to the data name domain value of the cloud index table entry E and the node ID of the link address domain value equal to the node ID of the link address domain value of the cloud index table entry E exist in the cloud index table of the device node D1, executing step 303, otherwise executing step 304;
step 303: the device node D1 updates the cloud index table entry whose data name domain value is equal to the data name domain value of the cloud index table entry E and whose node ID of the link address domain value is equal to the node ID of the link address domain value of the table entry E, that is, the geographic abscissa and the geographic ordinate in the link address domain value of the cloud index table entry are updated to the geographic abscissa and the geographic ordinate of the cloud index table entry E; if the updated cloud index entry neither satisfies condition 1 nor condition 2, the device node D1 deletes the updated cloud index entry, and performs step 305;
condition 1: the geographic abscissa and the geographic ordinate of the link address domain value of the cloud index table entry are located in the subnet S1;
condition 2: the geographical abscissa and the geographical ordinate of the link address domain value of the cloud index table entry are located in the subnet S2 and satisfy the formula (1), x2 is the geographical abscissa of the link address domain value of the cloud index table entry, and y2 is the geographical ordinate of the link address domain value of the cloud index table entry;
Figure GDA0002421027280000051
step 304: if the cloud index table entry E meets the conditions 1 and 2, the device node D1 adds the cloud index table entry E into the cloud index table of the device node D1;
step 305: and (6) ending.
The process can ensure the correctness of the cloud index table, so that a user can acquire data correctly and quickly.
In the method, under the condition that a vehicle node V1 is located in a subnet S1, data C3 is defined by a data name CN3, geographic abscissa and geographic ordinate of the data name CN3 are (xCN3, yCN3), and geographic abscissa and geographic ordinate are (xCN3, yCN3) located in a subnet S1, if the vehicle node V1 needs to obtain the data C3, first, the cloud index table is checked, and if there is no cloud index entry whose data name domain value is equal to the data name CN3, the vehicle node V1 obtains the data C3 by the following process:
step 401: starting;
step 402: the vehicle node V1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the vehicle node V1, in the cloud address, the network prefix is 0, the link address is the data name CN3, the vehicle node V1 sends a request data message, the source address of the request data message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 403: after the device node receives the data request message, if the device node is located in the subnet S1, step 405 is executed, otherwise step 404 is executed:
step 404: the device node receiving the request data message discards the received request data message, and executes step 410;
step 405: the device node receiving the request data message judges whether the subnet identification of the link address of the destination address of the request data message is 0, if so, step 406 is executed, otherwise, step 409 is executed;
step 406: if the geographical coordinates of the equipment node receiving the request data message are equal to the geographical coordinates of the link address of the destination address of the request data message, executing step 408, otherwise, executing step 407;
step 407: the device node receiving the request data message forwards the request data message to the device node closer to the geographical coordinate of the link address of the destination address of the request data message, and step 403 is executed;
step 408: the equipment node receiving the data request message executes the steps 101-106 to create a cloud VC3 and data C3; the device node that receives the request data message sends a response data message, the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request message, the load is data C3, execute step 410;
step 409: if the device node receiving the request data message can generate or provide the data C3 or a part of the data C3, sending a response data message, wherein the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request message, and the load is the generated or provided data; the device node receiving the request data message forwards the request data message, and executes step 403;
step 410: the vehicle node V1 checks all received response data messages, constructs loads in the response data messages into data C3, creates a cloud data table entry, the data name field value of the cloud data table entry is CN3, the data field value is data C3, the survival time is the maximum survival time of the data type, creates a cloud index table entry at the same time, the data name field value of the cloud index table entry is CN3, the link address value is the link address of the unicast address of the vehicle node V, and the survival time is the maximum survival time of the data type, and identifies the vehicle node V1 as a member of the cloud VC 3;
step 411: and (6) ending.
The above process can ensure that the user can acquire data correctly and quickly.
In the method, under the condition that the data C3 is defined by a data name CN3 and is created by a cloud VC3, if a vehicle node V2 needs to acquire the data C3, the vehicle node V2 firstly checks a cloud index table, and if a cloud index table entry with a data name domain value equal to the data name CN3 exists, the vehicle node V1 selects to acquire the data C3 from a nearest cloud VC3 cloud member V1:
step 501: starting;
step 502: the vehicle node V2 constructs a unicast address of the vehicle node V2 and a unicast address of the cloud member V1, in the unicast address of the vehicle node V2, a network prefix is 0, the link address is a link address of the vehicle node V2, in the unicast address of the cloud member V1, the network prefix is 0, the link address is a link address in a cloud index table entry of the cloud member V1, the vehicle node V2 sends a request data message, the source address of the request data message is the unicast address of the vehicle node V1, the destination address is the unicast address of the cloud member V1, and the load is the data name CN 3;
step 503: after receiving the request data message, the cloud member V1 sends a response data message, where the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request message, and the load is data defined by the data name in the request data message load, that is, data C3;
step 504: after receiving the response data message, the vehicle node V2 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN3, the data domain value is C3, the lifetime is the maximum lifetime of the data type, and meanwhile, creates a cloud index table entry, the data name domain value of the cloud index table entry is CN3, the link address value is the link address of the unicast address of the vehicle node V, the lifetime is the maximum lifetime of the data type, and the vehicle node V2 identifies the vehicle node V as a member of the cloud VC 3;
step 505: and (6) ending.
The above process can ensure that the user can acquire data correctly and quickly.
In the method of the present invention, under the condition that the vehicle node V1 is located in the subnet S1, the data C4 is defined by the data name CN4 and is created by the cloud VC4, the geographic abscissa and the geographic ordinate of the data name CN4 are (xCN4, yCN4), the geographic abscissa and the geographic ordinate are (xCN4, yCN4) located in the subnet S2, the network prefix of the access node AP1 of the subnet S1 is GRP1, and the network prefix of the access node AP2 of the subnet S2 is GRP2, if the vehicle node V1 needs to obtain the data C4, it first looks at the cloud index table, and if there is no cloud index table entry whose data name domain value is equal to the data name CN4, the vehicle node V1 obtains the data C4 by the following process:
step 601: starting;
step 602: the vehicle node V1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the vehicle node V1, in the cloud address, the network prefix is 0, the link address is the data name CN4, the vehicle node V1 sends a request data message, the source address of the request data message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 603: after receiving the request data message, the device node forwards the request data message to the device node closest to the access node AP 1;
step 604: repeating the step 603, and finally the access node AP1 receives the request data message; the access node AP1 judges that the geographic coordinates (xCN4, yCN4) in the destination address of the request data message are located in the subnet S2 through the geographic coordinates of the access node AP2, queries an access node table to obtain a table entry of which the geographic coordinate domain value is the geographic coordinates of the access node AP2 and obtains a network prefix domain value of the table entry, namely a network prefix GRP2, the access node AP1 updates the network prefix of the source address in the request data message to the network prefix GRP1 and the network prefix of the destination address to the network prefix GRP2, the access node AP1 sends the request data message to the Internet, and the request data message finally reaches the access node AP2 through the Internet;
step 605: judging whether a cloud data table item with a data name of CN4 exists in a cloud data table of the access node AP2, if so, performing step 606, otherwise, performing step 607:
step 606: the access node AP2 sends a response data message, where the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, and the load is data C4, and performs step 615;
step 607: judging whether a cloud index table item with the data name of CN4 exists in a cloud data table of the access node AP2, if so, executing step 608, otherwise, executing step 609:
step 608: the access node AP2 selects a cloud VC4 cloud member with a data name of CN4 and a closest geographical coordinate of a link address to the access node AP, updates a target link address in a request data message to a unicast link address of the VC4 cloud member, updates a load to a data name of CN4, and then sends the request data message; after receiving the request data message, the VC4 cloud member sends a response data message, where the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, and the load is data C4, and performs step 615;
step 609: if the subnet identification of the destination link address in the request data message is 1, performing step 610, otherwise performing step 611;
step 610: the access node AP2 executes the steps 201-210 to create the data C4, the access node AP2 sends a response data message, the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, the load is the data C4, and executes the step 615;
step 611: if the geographic coordinates of the access node AP2 are equal to the geographic coordinates of the destination link address in the request data message, then step 612 is performed, otherwise step 613 is performed;
step 612: the access node AP2 executes the steps 101-106 to create the data C4, the access node AP2 sends a response data message, the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, the load is the data C4, and the step 615 is executed;
step 613: the access node AP2 forwards the request data message to the device node closest to the geographical coordinates of the destination link address in the request data message;
step 614: finally, the request data message reaches the equipment node with the geographic position equal to the geographic coordinate of the destination link address in the request data message; after receiving the request data message, the device node executes steps 101-106 to create data C4, then sends a response data message, wherein the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, the load is data C4, and executes step 615;
step 615: after receiving the response data message, the vehicle node V1 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN4, the data domain value is C4, the lifetime is the maximum lifetime of the data type, and meanwhile, creates a cloud index table entry, the data name domain value of the cloud index table entry is CN4, the link address value is the link address of the unicast address of the vehicle node V, the lifetime is the maximum lifetime of the data type, and the vehicle node V1 identifies the vehicle node V as a member of the cloud VC 4;
step 616: and (6) ending.
The above process can ensure that the user can acquire data correctly and quickly.
Has the advantages that: the invention provides a cloud-based future Internet of vehicles data communication method, a vehicle node can acquire service data from a nearest cloud member through the implementation method provided by the invention, the delay and cost for acquiring the service data are reduced, the service quality is improved, the method can be applied to the fields of road condition monitoring, vehicle management and the like, and has wide application prospect.
Drawings
The foregoing and/or other advantages of the invention will become further apparent from the following detailed description of the invention when taken in conjunction with the accompanying drawings.
Fig. 1 is a schematic diagram of a cloud creation process according to the present invention.
Fig. 2 is a schematic diagram of a data creation process according to the present invention.
Fig. 3 is a schematic flow diagram of updating a cloud index table according to the present invention.
Fig. 4 is a schematic diagram of a flow of acquiring data in a subnet according to the present invention.
Fig. 5 is a schematic flow chart of the local data acquisition according to the present invention.
Fig. 6 is a schematic diagram of a remote data acquisition process according to the present invention.
The specific implementation mode is as follows:
the invention provides a cloud-based future Internet of vehicles data communication method, a vehicle node can acquire service data from a nearest cloud member through the implementation method provided by the invention, the delay and cost for acquiring the service data are reduced, the service quality is improved, the method can be applied to the fields of road condition monitoring, vehicle management and the like, and has wide application prospect.
Fig. 1 is a schematic diagram of a cloud creation process according to the present invention. The Internet of vehicles comprises two nodes, namely an access node and a vehicle node; the vehicle node has a route forwarding function, and the access node is connected with the Internet; the geographic coordinates of each access node are unique; the vehicle nodes realize communication through the access node closest to the vehicle nodes, and one access node and all the vehicle nodes realizing communication through the access node form a sub-network;
the vehicle node and the access node are collectively called as equipment nodes;
each access node stores an access node table, each access node table item comprises a geographical position coordinate domain and a network prefix domain, and the access node table is configured in advance;
a geographical range related data is defined by a data name, a data name comprising four parts: geographic abscissa, geographic ordinate, subnet identification, and data ID; the geographic abscissa, the geographic ordinate and the subnet identification of the data name define a geographic range, and the data ID defines a data type; when the subnet identification is 1, the geographic range is the subnet where the geographic coordinate is located, and when the subnet identification is 0, the geographic range is a one-hop range where the geographic coordinate is located, namely a circle with the geographic coordinate as a center and the radius as a transmission radius; the maximum survival time of the data related to the geographical range is preset;
the unicast addresses of the vehicle node and the access node are composed of a network prefix and a link address, and the link address is composed of a geographic abscissa, a geographic ordinate and a node ID; the node ID of the vehicle node is the hardware ID of the vehicle node; the unicast address of the access node is preset, and the node ID is 0; the node ID of the vehicle node is kept unchanged, if the geographic coordinate of the vehicle node changes, the link address of the unicast address also changes, the node ID in the link address is the node ID of the vehicle node, and the geographic coordinate is the current geographic abscissa and geographic ordinate of the vehicle node;
the cloud is composed of more than two vehicle nodes, each vehicle node is called a cloud member, the cloud members cooperate with each other to create data related to a geographic range, and the cloud is defined by a data name defining the data; the vehicle node acquires data by adopting a cloud address, wherein the cloud address is composed of a network prefix and a link address, and the link address is composed of a geographic horizontal coordinate, a geographic vertical coordinate, a subnet identifier and a data ID; the link address of the cloud address corresponds to a data name;
each cloud member stores a cloud data table for storing data which can be provided by the cloud member, and each cloud data table is composed of three fields: a data name field, a data field, and a lifecycle field; if the life cycle attenuation of one cloud data table entry is 0, deleting the table entry from the cloud data table by the cloud member;
each vehicle node stores a cloud index table used for storing information of the members of the sub-network cloud where the vehicle node is located, and each cloud index table is composed of three domains: a data name field, a link address field of a unicast address and a life cycle field; if the life cycle attenuation of one cloud index table entry is 0, deleting the table entry from the cloud index table;
if the data C1 is composed of the data name CN1, the geographic abscissa and the geographic ordinate (xCN1, yCN1) of the data name CN1 are located within the subnet S1, the subnet identification of the data name CN1 is 0, and the data ID is CID1, the device node D1 located at (xCN1, yCN1) constructs a cloud VC1 and creates data C1 by:
step 101: starting;
step 102: the device node D1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the device node D1, in the cloud address, the network prefix is 0, and the link address is the data name CN1, and then the device node D1 sends a constructed cloud message, wherein the source address of the constructed cloud message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 103: after receiving the constructed cloud message, if a part of the data C1 or the data C1 can be generated or provided, constructing a unicast address, wherein the network prefix is 0, the link address is the link address of the neighbor device node, then the neighbor device node sends a cloud response message, the source address of the cloud response message is the constructed unicast address, the destination address is the source address of the cloud message, and the load is the generated or provided data;
step 104: in a specified time, the device node D1 checks all received cloud response messages, constructs the load in the cloud response messages as data C1, and then sends a cloud sharing message, where the source address of the cloud sharing message is the unicast address constructed in step 102, the destination address is the cloud address constructed in step 102, and the load is data C1; the device node D1 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN1, the data domain value is data C1, and the survival time is the maximum survival time of the data type; the device node D1 creates a cloud index table entry, the data name domain value of the cloud index table entry is CN1, the link address value is the link address of the unicast address of the device node D1, the survival time is the maximum survival time of the data type, and the device node D1 identifies the device node D as a member of the cloud VC 1;
step 105: after receiving the cloud sharing message, the neighbor device node creates a cloud data table entry, the data name domain value of the cloud data table entry is CN1, the data domain value is data C1, the lifetime is the maximum lifetime of the data type, and meanwhile, a cloud index table entry is created, the data name domain value of the cloud index table entry is CN1, the link address value is the link address of the unicast address of the neighbor device node, the lifetime is the maximum lifetime of the data type, and the neighbor device node identifies the neighbor device node as a member of the cloud VC 1;
step 106: and (6) ending.
Fig. 2 is a schematic diagram of a data creation process according to the present invention. If the data C2 is composed of the data name CN2, the geographic abscissa and the geographic ordinate (xCN2, yCN2) of the data name CN2 are located within the subnet S1, the subnet identification of the data name CN1 is 1, and the data ID is CID2, the device node D1 located at (xCN2, yCN2) constructs a cloud VC2 and creates data C2 by:
step 201: starting;
step 202: the device node D1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the device node D1, in the cloud address, the network prefix is 0, the link address is the data name CN2, the device node D1 sends a constructed cloud message, the source address of the constructed cloud message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 203: after receiving the build cloud message, if the neighbor device node is located in the subnet S1, the neighbor device node executes step 205, otherwise, executes step 204:
step 204: the neighbor device node discards the received constructed cloud message, and executes step 206;
step 205: if the neighbor device node can generate or provide a part of the data C2 or the data C2, a unicast address is constructed, the network prefix is 0, the link address is the link address of the neighbor device node, then the neighbor device node sends a cloud response message, the source address of the cloud response message is the constructed unicast address, the destination address is the source address of the cloud message, and the load is the generated or provided data; the neighbor device node forwards the received constructed cloud message, and executes step 203;
step 206: in a specified time, the device node D1 checks all received cloud response messages, constructs the load in the cloud response messages as data C2, and then sends a cloud sharing message, where the source address of the cloud sharing message is the unicast address constructed in step 202, the destination address is the cloud address constructed in step 202, and the load is data C2; the device node D1 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN2, the data domain value is data C2, and the survival time is the maximum survival time of the data type; the device node D1 creates a cloud index table entry, the data name domain value of the cloud index table entry is CN2, the link address value is the link address of the unicast address of the device node D, the survival time is the maximum survival time of the data type, and the device node D1 identifies the device node D as a member of the cloud VC 2;
step 207: after receiving the cloud sharing message, if the neighbor device node is located in the subnet S1, executing step 209, otherwise executing step 208;
step 208: the neighbor device node discards the received cloud sharing message, and executes step 210;
step 209: the neighbor device nodes create a cloud data table entry, the data name field value of the cloud data table entry is CN2, the data field value is C2, the lifetime is the maximum lifetime of the data type, and meanwhile, a cloud index table entry is created, the data name field value of the cloud index table entry is CN2, the link address value is the link address of the unicast address of the neighbor device node, the lifetime is the maximum lifetime of the data type, and the neighbor device nodes identify the neighbor device node as a member of the cloud VC 2; the neighbor device node forwards the received cloud sharing message, and executes step 207;
step 210: and (6) ending.
Fig. 3 is a schematic flow diagram of updating a cloud index table according to the present invention. Each equipment node broadcasts a beacon message periodically, the source address of the beacon message is the unicast address of the equipment node, and the network prefix in the unicast address is 0; if the geographic coordinate of the cloud member changes, the cloud index table item of which the node ID of the link address domain value is equal to the node ID of the cloud index table item is searched, and the geographic horizontal coordinate and the geographic vertical coordinate of the link address domain value of the cloud index table item are updated to the current geographic horizontal coordinate and the current geographic vertical coordinate of the cloud index table item;
if the device node detects that the cloud index table entry in the cloud index table of the device node is updated, the updated cloud index table entry is used as the load content of the next beacon message;
after the device node D1 located in the subnet S1 and having geographic coordinates (x1, y1) receives the beacon message of the neighboring device node under the conditions that the access node of the subnet S1 is AP1, the geographic coordinates are (xAP1, yAP1), the access node of the subnet S2 is AP2, and the geographic coordinates are (xAP2, yAP2), if the beacon message includes the cloud index table, the device node D1 updates the cloud index table as follows:
step 301: starting;
step 302: the device node D1 looks at the cloud index table in the beacon message payload, and for each cloud index entry E in the cloud index table, performs the following operations: if the data name domain value equal to the data name domain value of the cloud index table entry E and the node ID of the link address domain value equal to the node ID of the link address domain value of the cloud index table entry E exist in the cloud index table of the device node D1, executing step 303, otherwise executing step 304;
step 303: the device node D1 updates the cloud index table entry whose data name domain value is equal to the data name domain value of the cloud index table entry E and whose node ID of the link address domain value is equal to the node ID of the link address domain value of the table entry E, that is, the geographic abscissa and the geographic ordinate in the link address domain value of the cloud index table entry are updated to the geographic abscissa and the geographic ordinate of the cloud index table entry E; if the updated cloud index entry neither satisfies condition 1 nor condition 2, the device node D1 deletes the updated cloud index entry, and performs step 305;
condition 1: the geographic abscissa and the geographic ordinate of the link address domain value of the cloud index table entry are located in the subnet S1;
condition 2: the geographical abscissa and the geographical ordinate of the link address domain value of the cloud index table entry are located in the subnet S2 and satisfy the formula (1), x2 is the geographical abscissa of the link address domain value of the cloud index table entry, and y2 is the geographical ordinate of the link address domain value of the cloud index table entry;
Figure GDA0002421027280000141
step 304: if the cloud index table entry E meets the conditions 1 and 2, the device node D1 adds the cloud index table entry E into the cloud index table of the device node D1;
step 305: and (6) ending.
Fig. 4 is a schematic diagram of a flow of acquiring data in a subnet according to the present invention. Under the condition that the vehicle node V1 is located in the subnet S1, the data C3 is defined by the data name CN3, the geographic abscissa and the geographic ordinate of the data name CN3 are (xCN3, yCN3), and the geographic abscissa and the geographic ordinate are (xCN3, yCN3) located in the subnet S1, if the vehicle node V1 needs to acquire the data C3, first, the cloud index table is checked, and if there is no cloud index entry whose data name domain value is equal to the data name CN3, the vehicle node V1 acquires the data C3 by the following procedure:
step 401: starting;
step 402: the vehicle node V1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the vehicle node V1, in the cloud address, the network prefix is 0, the link address is the data name CN3, the vehicle node V1 sends a request data message, the source address of the request data message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 403: after the device node receives the data request message, if the device node is located in the subnet S1, step 405 is executed, otherwise step 404 is executed:
step 404: the device node receiving the request data message discards the received request data message, and executes step 410;
step 405: the device node receiving the request data message judges whether the subnet identification of the link address of the destination address of the request data message is 0, if so, step 406 is executed, otherwise, step 409 is executed;
step 406: if the geographical coordinates of the equipment node receiving the request data message are equal to the geographical coordinates of the link address of the destination address of the request data message, executing step 408, otherwise, executing step 407;
step 407: the device node receiving the request data message forwards the request data message to the device node closer to the geographical coordinate of the link address of the destination address of the request data message, and step 403 is executed;
step 408: the equipment node receiving the data request message executes the steps 101-106 to create a cloud VC3 and data C3; the device node that receives the request data message sends a response data message, the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request message, the load is data C3, execute step 410;
step 409: if the device node receiving the request data message can generate or provide the data C3 or a part of the data C3, sending a response data message, wherein the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request message, and the load is the generated or provided data; the device node receiving the request data message forwards the request data message, and executes step 403;
step 410: the vehicle node V1 checks all received response data messages, constructs loads in the response data messages into data C3, creates a cloud data table entry, the data name field value of the cloud data table entry is CN3, the data field value is data C3, the survival time is the maximum survival time of the data type, creates a cloud index table entry at the same time, the data name field value of the cloud index table entry is CN3, the link address value is the link address of the unicast address of the vehicle node V, and the survival time is the maximum survival time of the data type, and identifies the vehicle node V1 as a member of the cloud VC 3;
step 411: and (6) ending.
Fig. 5 is a schematic flow chart of the local data acquisition according to the present invention. Under the condition that the data C3 is defined by a data name CN3 and created by a cloud VC3, if the vehicle node V2 needs to acquire the data C3, it first looks at the cloud index table, and if there is a cloud index table entry whose data name domain value is equal to the data name CN3, selects to acquire the data C3 from the nearest cloud VC3 cloud member V1:
step 501: starting;
step 502: the vehicle node V2 constructs a unicast address of the vehicle node V2 and a unicast address of the cloud member V1, in the unicast address of the vehicle node V2, a network prefix is 0, the link address is a link address of the vehicle node V2, in the unicast address of the cloud member V1, the network prefix is 0, the link address is a link address in a cloud index table entry of the cloud member V1, the vehicle node V2 sends a request data message, the source address of the request data message is the unicast address of the vehicle node V1, the destination address is the unicast address of the cloud member V1, and the load is the data name CN 3;
step 503: after receiving the request data message, the cloud member V1 sends a response data message, where the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request message, and the load is data defined by the data name in the request data message load, that is, data C3;
step 504: after receiving the response data message, the vehicle node V2 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN3, the data domain value is C3, the lifetime is the maximum lifetime of the data type, and meanwhile, creates a cloud index table entry, the data name domain value of the cloud index table entry is CN3, the link address value is the link address of the unicast address of the vehicle node V, the lifetime is the maximum lifetime of the data type, and the vehicle node V2 identifies the vehicle node V as a member of the cloud VC 3;
step 505: and (6) ending.
Fig. 6 is a schematic diagram of a remote data acquisition process according to the present invention. Under the condition that the vehicle node V1 is located in the subnet S1, the data C4 is defined by the data name CN4, created by the cloud VC4, the geographic abscissa and the geographic ordinate of the data name CN4 are (xCN4, yCN4), the geographic abscissa and the geographic ordinate are (xCN4, yCN4) are located in the subnet S2, the network prefix of the access node AP1 of the subnet S1 is GRP1, and the network prefix of the access node AP2 of the subnet S2 is GRP2, if the vehicle node V1 needs to acquire the data C4, it first looks at the cloud index table, and if there is no cloud index entry whose data name domain value is equal to the data name CN4, the vehicle node V1 acquires the data C4 by:
step 601: starting;
step 602: the vehicle node V1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the vehicle node V1, in the cloud address, the network prefix is 0, the link address is the data name CN4, the vehicle node V1 sends a request data message, the source address of the request data message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 603: after receiving the request data message, the device node forwards the request data message to the device node closest to the access node AP 1;
step 604: repeating the step 603, and finally the access node AP1 receives the request data message; the access node AP1 judges that the geographic coordinates (xCN4, yCN4) in the destination address of the request data message are located in the subnet S2 through the geographic coordinates of the access node AP2, queries an access node table to obtain a table entry of which the geographic coordinate domain value is the geographic coordinates of the access node AP2 and obtains a network prefix domain value of the table entry, namely a network prefix GRP2, the access node AP1 updates the network prefix of the source address in the request data message to the network prefix GRP1 and the network prefix of the destination address to the network prefix GRP2, the access node AP1 sends the request data message to the Internet, and the request data message finally reaches the access node AP2 through the Internet;
step 605: judging whether a cloud data table item with a data name of CN4 exists in a cloud data table of the access node AP2, if so, performing step 606, otherwise, performing step 607:
step 606: the access node AP2 sends a response data message, where the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, and the load is data C4, and performs step 615;
step 607: judging whether a cloud index table item with the data name of CN4 exists in a cloud data table of the access node AP2, if so, executing step 608, otherwise, executing step 609:
step 608: the access node AP2 selects a cloud VC4 cloud member with a data name of CN4 and a closest geographical coordinate of a link address to the access node AP, updates a target link address in a request data message to a unicast link address of the VC4 cloud member, updates a load to a data name of CN4, and then sends the request data message; after receiving the request data message, the VC4 cloud member sends a response data message, where the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, and the load is data C4, and performs step 615;
step 609: if the subnet identification of the destination link address in the request data message is 1, performing step 610, otherwise performing step 611;
step 610: the access node AP2 executes the steps 201-210 to create the data C4, the access node AP2 sends a response data message, the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, the load is the data C4, and executes the step 615;
step 611: if the geographic coordinates of the access node AP2 are equal to the geographic coordinates of the destination link address in the request data message, then step 612 is performed, otherwise step 613 is performed;
step 612: the access node AP2 executes the steps 101-106 to create the data C4, the access node AP2 sends a response data message, the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, the load is the data C4, and the step 615 is executed;
step 613: the access node AP2 forwards the request data message to the device node closest to the geographical coordinates of the destination link address in the request data message;
step 614: finally, the request data message reaches the equipment node with the geographic position equal to the geographic coordinate of the destination link address in the request data message; after receiving the request data message, the device node executes steps 101-106 to create data C4, then sends a response data message, wherein the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, the load is data C4, and executes step 615;
step 615: after receiving the response data message, the vehicle node V1 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN4, the data domain value is C4, the lifetime is the maximum lifetime of the data type, and meanwhile, creates a cloud index table entry, the data name domain value of the cloud index table entry is CN4, the link address value is the link address of the unicast address of the vehicle node V, the lifetime is the maximum lifetime of the data type, and the vehicle node V1 identifies the vehicle node V as a member of the cloud VC 4;
step 616: and (6) ending.
Example 1
Based on the simulation parameters in table 1, the present embodiment simulates the future cloud-based data communication method in the present invention, and the performance analysis is as follows: when the speed of the vehicle node is increased, the distribution area of the cloud members is wider, so that the nodes of the user and the cloud members are reduced, and the cost for acquiring data is reduced. The average cost of the vehicle node for obtaining service data is 6.5.
TABLE 1 simulation parameters
Figure GDA0002421027280000191
The present invention provides a concept of a future car networking data communication method based on cloud, and a method and a way for implementing the technical scheme are many, the above description is only a preferred embodiment of the present invention, it should be noted that, for those skilled in the art, a plurality of improvements and decorations can be made without departing from the principle of the present invention, and these improvements and decorations should also be regarded as the protection scope of the present invention. The components not specified in this embodiment can be implemented by the prior art.

Claims (6)

1. A future Internet of vehicles data communication method based on cloud is characterized in that the Internet of vehicles comprises an access node and a vehicle node; the vehicle node has a route forwarding function, and the access node is connected with the Internet; the geographic coordinates of each access node are unique; the vehicle nodes realize communication through the access node closest to the vehicle nodes, and one access node and all the vehicle nodes realizing communication through the access node form a sub-network;
the vehicle node and the access node are collectively called as equipment nodes;
each access node stores an access node table, each access node table item comprises a geographical position coordinate domain and a network prefix domain, and the access node table is configured in advance;
a geographical range related data is defined by a data name, a data name comprising four parts: geographic abscissa, geographic ordinate, subnet identification, and data ID; the geographic abscissa, the geographic ordinate and the subnet identification of the data name define a geographic range, and the data ID defines a data type; when the subnet identification is 1, the geographic range is the subnet where the geographic coordinate is located, and when the subnet identification is 0, the geographic range is a one-hop range where the geographic coordinate is located, namely a circle with the geographic coordinate as a center and the radius as a transmission radius; the maximum survival time of the data related to the geographical range is preset;
the unicast addresses of the vehicle node and the access node are composed of a network prefix and a link address, and the link address is composed of a geographic abscissa, a geographic ordinate and a node ID; the node ID of the vehicle node is the hardware ID of the vehicle node; the unicast address of the access node is preset, and the node ID is 0; the node ID of the vehicle node is kept unchanged, if the geographic coordinate of the vehicle node changes, the link address of the unicast address also changes, the node ID in the link address is the node ID of the vehicle node, and the geographic coordinate is the current geographic abscissa and geographic ordinate of the vehicle node;
the cloud is composed of more than two vehicle nodes, each vehicle node is called a cloud member, the cloud members cooperate with each other to create data related to a geographic range, and the cloud is defined by a data name defining the data; the vehicle node acquires data by adopting a cloud address, wherein the cloud address is composed of a network prefix and a link address, and the link address is composed of a geographic horizontal coordinate, a geographic vertical coordinate, a subnet identifier and a data ID; the link address of the cloud address corresponds to a data name;
each cloud member stores a cloud data table for storing data which can be provided by the cloud member, and each cloud data table is composed of three fields: a data name field, a data field, and a lifecycle field; if the life cycle attenuation of one cloud data table entry is 0, deleting the table entry from the cloud data table by the cloud member;
each vehicle node stores a cloud index table used for storing information of the members of the sub-network cloud where the vehicle node is located, and each cloud index table is composed of three domains: a data name field, a link address field of a unicast address and a life cycle field; if the life cycle attenuation of one cloud index table entry is 0, deleting the table entry from the cloud index table;
if the data C1 is composed of the data name CN1, the geographic abscissa and the geographic ordinate (xCN1, yCN1) of the data name CN1 are located within the subnet S1, the subnet identification of the data name CN1 is 0, and the data ID is CID1, the device node D1 located at (xCN1, yCN1) constructs a cloud VC1 and creates data C1 by:
step 101: starting;
step 102: the device node D1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the device node D1, in the cloud address, the network prefix is 0, and the link address is the data name CN1, and then the device node D1 sends a constructed cloud message, wherein the source address of the constructed cloud message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 103: after receiving the constructed cloud message, if a part of the data C1 or the data C1 can be generated or provided, constructing a unicast address, wherein the network prefix is 0, the link address is the link address of the neighbor device node, then the neighbor device node sends a cloud response message, the source address of the cloud response message is the constructed unicast address, the destination address is the source address of the cloud message, and the load is the generated or provided data;
step 104: in a specified time, the device node D1 checks all received cloud response messages, constructs the load in the cloud response messages as data C1, and then sends a cloud sharing message, where the source address of the cloud sharing message is the unicast address constructed in step 102, the destination address is the cloud address constructed in step 102, and the load is data C1; the device node D1 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN1, the data domain value is data C1, and the survival time is the maximum survival time of the data type; the device node D1 creates a cloud index table entry, the data name domain value of the cloud index table entry is CN1, the link address value is the link address of the unicast address of the device node D1, the survival time is the maximum survival time of the data type, and the device node D1 identifies the device node D as a member of the cloud VC 1;
step 105: after receiving the cloud sharing message, the neighbor device node creates a cloud data table entry, the data name domain value of the cloud data table entry is CN1, the data domain value is data C1, the lifetime is the maximum lifetime of the data type, and meanwhile, a cloud index table entry is created, the data name domain value of the cloud index table entry is CN1, the link address value is the link address of the unicast address of the neighbor device node, the lifetime is the maximum lifetime of the data type, and the neighbor device node identifies the neighbor device node as a member of the cloud VC 1;
step 106: and (6) ending.
2. A cloud-based future vehicle networking data communication method according to claim 1, wherein if the data C2 is composed of a data name CN2, the geographic abscissa and the geographic ordinate (xCN2, yCN2) of the data name CN2 are located within the subnet S1, the subnet identification of the data name CN1 is 1, and the data ID is CID2, the device node D1 located at (xCN2, yCN2) constructs a cloud VC2 and creates the data C2 by:
step 201: starting;
step 202: the device node D1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the device node D1, in the cloud address, the network prefix is 0, the link address is the data name CN2, the device node D1 sends a constructed cloud message, the source address of the constructed cloud message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 203: after receiving the build cloud message, if the neighbor device node is located in the subnet S1, the neighbor device node executes step 205, otherwise, executes step 204:
step 204: the neighbor device node discards the received constructed cloud message, and executes step 206;
step 205: if the neighbor device node can generate or provide a part of the data C2 or the data C2, a unicast address is constructed, the network prefix is 0, the link address is the link address of the neighbor device node, then the neighbor device node sends a cloud response message, the source address of the cloud response message is the constructed unicast address, the destination address is the source address of the cloud message, and the load is the generated or provided data; the neighbor device node forwards the received constructed cloud message, and executes step 203;
step 206: in a specified time, the device node D1 checks all received cloud response messages, constructs the load in the cloud response messages as data C2, and then sends a cloud sharing message, where the source address of the cloud sharing message is the unicast address constructed in step 202, the destination address is the cloud address constructed in step 202, and the load is data C2; the device node D1 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN2, the data domain value is data C2, and the survival time is the maximum survival time of the data type; the device node D1 creates a cloud index table entry, the data name domain value of the cloud index table entry is CN2, the link address value is the link address of the unicast address of the device node D, the survival time is the maximum survival time of the data type, and the device node D1 identifies the device node D as a member of the cloud VC 2;
step 207: after receiving the cloud sharing message, if the neighbor device node is located in the subnet S1, executing step 209, otherwise executing step 208;
step 208: the neighbor device node discards the received cloud sharing message, and executes step 210;
step 209: the neighbor device nodes create a cloud data table entry, the data name field value of the cloud data table entry is CN2, the data field value is C2, the lifetime is the maximum lifetime of the data type, and meanwhile, a cloud index table entry is created, the data name field value of the cloud index table entry is CN2, the link address value is the link address of the unicast address of the neighbor device node, the lifetime is the maximum lifetime of the data type, and the neighbor device nodes identify the neighbor device node as a member of the cloud VC 2; the neighbor device node forwards the received cloud sharing message, and executes step 207;
step 210: and (6) ending.
3. The cloud-based future vehicle networking data communication method according to claim 2, wherein each device node periodically broadcasts a beacon message, the source address of the beacon message is its own unicast address, and the network prefix in the unicast address is 0; if the geographic coordinate of the cloud member changes, the cloud index table item of which the node ID of the link address domain value is equal to the node ID of the cloud index table item is searched, and the geographic horizontal coordinate and the geographic vertical coordinate of the link address domain value of the cloud index table item are updated to the current geographic horizontal coordinate and the current geographic vertical coordinate of the cloud index table item;
if the device node detects that the cloud index table entry in the cloud index table of the device node is updated, the updated cloud index table entry is used as the load content of the next beacon message;
after the device node D1 located in the subnet S1 and having geographic coordinates (x1, y1) receives the beacon message of the neighboring device node under the conditions that the access node of the subnet S1 is AP1, the geographic coordinates are (xAP1, yAP1), the access node of the subnet S2 is AP2, and the geographic coordinates are (xAP2, yAP2), if the beacon message includes the cloud index table, the device node D1 updates the cloud index table as follows:
step 301: starting;
step 302: the device node D1 looks at the cloud index table in the beacon message payload, and for each cloud index entry E in the cloud index table, performs the following operations: if the data name domain value equal to the data name domain value of the cloud index table entry E and the node ID of the link address domain value equal to the node ID of the link address domain value of the cloud index table entry E exist in the cloud index table of the device node D1, executing step 303, otherwise executing step 304;
step 303: the device node D1 updates the cloud index table entry whose data name domain value is equal to the data name domain value of the cloud index table entry E and whose node ID of the link address domain value is equal to the node ID of the link address domain value of the table entry E, that is, the geographic abscissa and the geographic ordinate in the link address domain value of the cloud index table entry are updated to the geographic abscissa and the geographic ordinate of the cloud index table entry E; if the updated cloud index entry neither satisfies condition 1 nor condition 2, the device node D1 deletes the updated cloud index entry, and performs step 305;
condition 1: the geographic abscissa and the geographic ordinate of the link address domain value of the cloud index table entry are located in the subnet S1;
condition 2: the geographical abscissa and the geographical ordinate of the link address domain value of the cloud index table entry are located in the subnet S2 and satisfy the formula (1), x2 is the geographical abscissa of the link address domain value of the cloud index table entry, and y2 is the geographical ordinate of the link address domain value of the cloud index table entry;
Figure FDA0002421027270000041
step 304: if the cloud index table entry E meets the conditions 1 and 2, the device node D1 adds the cloud index table entry E into the cloud index table of the device node D1;
step 305: and (6) ending.
4. A cloud-based future vehicle networking data communication method according to claim 2, wherein under the condition that the vehicle node V1 is located in the subnet S1, the data C3 is defined by the data name CN3, the geographic abscissa and the geographic ordinate of the data name CN3 are (xCN3, yCN3), the geographic abscissa and the geographic ordinate are (xCN3, yCN3) are located in the subnet S1, if the vehicle node V1 needs to obtain the data C3, the vehicle node V1 first checks the cloud index table, if there is no cloud index entry whose data name domain value is equal to the data name CN3, then the vehicle node V1 obtains the data C3 by:
step 401: starting;
step 402: the vehicle node V1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the vehicle node V1, in the cloud address, the network prefix is 0, the link address is the data name CN3, the vehicle node V1 sends a request data message, the source address of the request data message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 403: after the device node receives the data request message, if the device node is located in the subnet S1, step 405 is executed, otherwise step 404 is executed:
step 404: the device node receiving the request data message discards the received request data message, and executes step 410;
step 405: the device node receiving the request data message judges whether the subnet identification of the link address of the destination address of the request data message is 0, if so, step 406 is executed, otherwise, step 409 is executed;
step 406: if the geographical coordinates of the equipment node receiving the request data message are equal to the geographical coordinates of the link address of the destination address of the request data message, executing step 408, otherwise, executing step 407;
step 407: the device node receiving the request data message forwards the request data message to the device node closer to the geographical coordinate of the link address of the destination address of the request data message, and step 403 is executed;
step 408: the equipment node receiving the data request message executes the steps 101-106 to create a cloud VC3 and data C3; the device node that receives the request data message sends a response data message, the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request message, the load is data C3, execute step 410;
step 409: if the device node receiving the request data message can generate or provide the data C3 or a part of the data C3, sending a response data message, wherein the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request message, and the load is the generated or provided data; the device node receiving the request data message forwards the request data message, and executes step 403;
step 410: the vehicle node V1 checks all received response data messages, constructs loads in the response data messages into data C3, creates a cloud data table entry, the data name field value of the cloud data table entry is CN3, the data field value is data C3, the survival time is the maximum survival time of the data type, creates a cloud index table entry at the same time, the data name field value of the cloud index table entry is CN3, the link address value is the link address of the unicast address of the vehicle node V, and the survival time is the maximum survival time of the data type, and identifies the vehicle node V1 as a member of the cloud VC 3;
step 411: and (6) ending.
5. A cloud-based future vehicle networking data communication method according to claim 3, wherein under the condition that data C3 is defined by data name CN3 and created by cloud VC3, if vehicle node V2 needs to obtain data C3, it first looks at the cloud index table, and if there is a cloud index entry whose data name domain value is equal to data name CN3, then chooses to obtain data C3 from nearest cloud VC3 cloud member V1:
step 501: starting;
step 502: the vehicle node V2 constructs a unicast address of the vehicle node V2 and a unicast address of the cloud member V1, in the unicast address of the vehicle node V2, a network prefix is 0, the link address is a link address of the vehicle node V2, in the unicast address of the cloud member V1, the network prefix is 0, the link address is a link address in a cloud index table entry of the cloud member V1, the vehicle node V2 sends a request data message, the source address of the request data message is the unicast address of the vehicle node V1, the destination address is the unicast address of the cloud member V1, and the load is the data name CN 3;
step 503: after receiving the request data message, the cloud member V1 sends a response data message, where the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request message, and the load is data defined by the data name in the request data message load, that is, data C3;
step 504: after receiving the response data message, the vehicle node V2 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN3, the data domain value is C3, the lifetime is the maximum lifetime of the data type, and meanwhile, creates a cloud index table entry, the data name domain value of the cloud index table entry is CN3, the link address value is the link address of the unicast address of the vehicle node V, the lifetime is the maximum lifetime of the data type, and the vehicle node V2 identifies the vehicle node V as a member of the cloud VC 3;
step 505: and (6) ending.
6. A cloud-based future vehicle networking data communication method according to claim 3, wherein, on condition that the vehicle node V1 is located in the subnet S1, the data C4 is defined by the data name CN4 and is created by the cloud VC4, the geographic abscissa and the geographic ordinate of the data name CN4 are (xCN4, yCN4), the geographic abscissa and the geographic ordinate are (xCN4, yCN4) located in the subnet S2, the network prefix of the access node AP1 of the subnet S1 is GRP1, and the network prefix of the access node AP2 of the subnet S2 is GRP2, if the vehicle node V1 needs to acquire the data C4, it first looks at the cloud index table, if there is no cloud index entry whose data name domain value is equal to the data name CN4, then the vehicle node V1 acquires the data C4 by the following process:
step 601: starting;
step 602: the vehicle node V1 constructs a unicast address and a cloud address, wherein in the unicast address, the network prefix is 0, the link address is the link address of the vehicle node V1, in the cloud address, the network prefix is 0, the link address is the data name CN4, the vehicle node V1 sends a request data message, the source address of the request data message is the constructed unicast address, the destination address is the constructed cloud address, and the load is empty;
step 603: after receiving the request data message, the device node forwards the request data message to the device node closest to the access node AP 1;
step 604: repeating the step 603, and finally the access node AP1 receives the request data message; the access node AP1 judges that the geographic coordinates (xCN4, yCN4) in the destination address of the request data message are located in the subnet S2 through the geographic coordinates of the access node AP2, queries an access node table to obtain a table entry of which the geographic coordinate domain value is the geographic coordinates of the access node AP2 and obtains a network prefix domain value of the table entry, namely a network prefix GRP2, the access node AP1 updates the network prefix of the source address in the request data message to the network prefix GRP1 and the network prefix of the destination address to the network prefix GRP2, the access node AP1 sends the request data message to the Internet, and the request data message finally reaches the access node AP2 through the Internet;
step 605: judging whether a cloud data table item with a data name of CN4 exists in a cloud data table of the access node AP2, if so, performing step 606, otherwise, performing step 607:
step 606: the access node AP2 sends a response data message, where the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, and the load is data C4, and performs step 615;
step 607: judging whether a cloud index table item with the data name of CN4 exists in a cloud data table of the access node AP2, if so, executing step 608, otherwise, executing step 609:
step 608: the access node AP2 selects a cloud VC4 cloud member with a data name of CN4 and a closest geographical coordinate of a link address to the access node AP, updates a target link address in a request data message to a unicast link address of the VC4 cloud member, updates a load to a data name of CN4, and then sends the request data message; after receiving the request data message, the VC4 cloud member sends a response data message, where the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, and the load is data C4, and performs step 615;
step 609: if the subnet identification of the destination link address in the request data message is 1, performing step 610, otherwise performing step 611;
step 610: the access node AP2 executes the steps 201-210 to create the data C4, the access node AP2 sends a response data message, the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, the load is the data C4, and executes the step 615;
step 611: if the geographic coordinates of the access node AP2 are equal to the geographic coordinates of the destination link address in the request data message, then step 612 is performed, otherwise step 613 is performed;
step 612: the access node AP2 executes the steps 101-106 to create the data C4, the access node AP2 sends a response data message, the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, the load is the data C4, and the step 615 is executed;
step 613: the access node AP2 forwards the request data message to the device node closest to the geographical coordinates of the destination link address in the request data message;
step 614: finally, the request data message reaches the equipment node with the geographic position equal to the geographic coordinate of the destination link address in the request data message; after receiving the request data message, the device node executes steps 101-106 to create data C4, then sends a response data message, wherein the source address of the response data message is the destination address in the received request data message, the destination address is the source address in the request data message, the load is data C4, and executes step 615;
step 615: after receiving the response data message, the vehicle node V1 creates a cloud data table entry, the data name domain value of the cloud data table entry is CN4, the data domain value is C4, the lifetime is the maximum lifetime of the data type, and meanwhile, creates a cloud index table entry, the data name domain value of the cloud index table entry is CN4, the link address value is the link address of the unicast address of the vehicle node V, the lifetime is the maximum lifetime of the data type, and the vehicle node V1 identifies the vehicle node V as a member of the cloud VC 4;
step 616: and (6) ending.
CN201710752169.6A 2017-08-28 2017-08-28 Future Internet of vehicles data communication method based on cloud Active CN107508927B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710752169.6A CN107508927B (en) 2017-08-28 2017-08-28 Future Internet of vehicles data communication method based on cloud

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710752169.6A CN107508927B (en) 2017-08-28 2017-08-28 Future Internet of vehicles data communication method based on cloud

Publications (2)

Publication Number Publication Date
CN107508927A CN107508927A (en) 2017-12-22
CN107508927B true CN107508927B (en) 2020-05-05

Family

ID=60694096

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710752169.6A Active CN107508927B (en) 2017-08-28 2017-08-28 Future Internet of vehicles data communication method based on cloud

Country Status (1)

Country Link
CN (1) CN107508927B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108768846B (en) * 2018-05-08 2020-09-29 常熟理工学院 High-efficiency big data network implementation method
CN108933657B (en) * 2018-08-13 2021-02-05 常熟理工学院 Safe and reliable future network communication implementation method
CN109039906B (en) * 2018-10-24 2020-10-30 常熟理工学院 Routing implementation method of intelligent Internet of vehicles
CN110213359B (en) * 2019-05-24 2021-09-03 南京邮电大学 Internet of vehicles networking data pushing system and method based on D2D

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104717307A (en) * 2015-04-07 2015-06-17 常熟理工学院 Implementation method of vehicle-mounted cloud communication
CN106131126A (en) * 2016-06-23 2016-11-16 广州亿程交通信息有限公司 Vehicle management system based on car networking cloud platform service
CN106408929A (en) * 2015-07-27 2017-02-15 青岛慧能利生自动门安全技术有限公司 Expressway vehicle intelligent management system based on vehicle networking technology
CN106647723A (en) * 2017-02-08 2017-05-10 宝沃汽车（中国）有限公司 Vehicle condition monitoring method based on Internet of vehicles, vehicle condition monitoring system based on Internet of vehicles, and vehicle
CN106971583A (en) * 2017-03-27 2017-07-21 宁波吉利汽车研究开发有限公司 A kind of traffic information shared system and sharing method based on vehicle-mounted networking equipment

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9373200B2 (en) * 2014-06-06 2016-06-21 Vivint, Inc. Monitoring vehicle usage
US9659494B2 (en) * 2014-09-26 2017-05-23 Intel Corporation Technologies for reporting and predicting emergency vehicle routes

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104717307A (en) * 2015-04-07 2015-06-17 常熟理工学院 Implementation method of vehicle-mounted cloud communication
CN106408929A (en) * 2015-07-27 2017-02-15 青岛慧能利生自动门安全技术有限公司 Expressway vehicle intelligent management system based on vehicle networking technology
CN106131126A (en) * 2016-06-23 2016-11-16 广州亿程交通信息有限公司 Vehicle management system based on car networking cloud platform service
CN106647723A (en) * 2017-02-08 2017-05-10 宝沃汽车（中国）有限公司 Vehicle condition monitoring method based on Internet of vehicles, vehicle condition monitoring system based on Internet of vehicles, and vehicle
CN106971583A (en) * 2017-03-27 2017-07-21 宁波吉利汽车研究开发有限公司 A kind of traffic information shared system and sharing method based on vehicle-mounted networking equipment

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
基于IPv6 的车载网络移动切换研究;王晓喃;《计算机应用研究》;20120228;全文 *
王晓喃，钱焕延.车载网移动切换方案.《电子科技大学学报》.2013, *

Also Published As

Publication number Publication date
CN107508927A (en) 2017-12-22

Similar Documents

Publication Publication Date Title
CN106792978B (en) Cloud-based intelligent Internet of vehicles data communication method
CN107508927B (en) Future Internet of vehicles data communication method based on cloud
CN107333313B (en) Reliable intelligent Internet of vehicles routing implementation method
CN106993321B (en) Network data communication method based on cluster
CN105246118A (en) Wireless network communication realization method based on positioning information
CN109257789B (en) Vehicle-mounted network data communication method based on multi-hop cluster
CN109246785B (en) Method for realizing future mobile network
CN107071010B (en) A kind of network data communication method based on vehicle-mounted cloud
CN102333118A (en) Automatic Internet protocol version 6 (IPv6) address configuration method for vehicular network
CN105187529A (en) Internet of vehicles implementation method based on positioning information
CN104869563A (en) Communication realization method of next-generation city internet of vehicle
CN109462549B (en) Method for implementing new generation wireless mobile network
CN106453640B (en) A kind of communication means of intelligence car networking
CN103312811A (en) Method for connecting vehicle-mounted network into IPv6 internet
CN105188104B (en) A kind of implementation method of wireless communication
CN109089241B (en) Data communication implementation method for vehicle-mounted network
CN104869601A (en) Communication realization method of next-generation internet of vehicle
CN110401911B (en) Vehicle-mounted cloud implementation method based on named data network
CN110769479B (en) High-efficiency new-generation wireless network communication method
CN109768893B (en) High-efficiency big data network data communication implementation method
CN109089293B (en) Route communication realization method for future mobile network
CN107484110B (en) Data communication implementation method based on intelligent vehicle-mounted sensor network
CN108055204B (en) Big data network communication implementation method
CN108769138B (en) Efficient data communication method for Internet of vehicles
CN107484109B (en) Data communication method for vehicle-mounted sensor network

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant