CN106792978B - Cloud-based intelligent Internet of vehicles data communication method - Google Patents

Cloud-based intelligent Internet of vehicles data communication method Download PDF

Info

Publication number
CN106792978B
CN106792978B CN201710196610.7A CN201710196610A CN106792978B CN 106792978 B CN106792978 B CN 106792978B CN 201710196610 A CN201710196610 A CN 201710196610A CN 106792978 B CN106792978 B CN 106792978B
Authority
CN
China
Prior art keywords
vehicle
cloud
node
data
domain
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
CN201710196610.7A
Other languages
Chinese (zh)
Other versions
CN106792978A (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 CN201710196610.7A priority Critical patent/CN106792978B/en
Publication of CN106792978A publication Critical patent/CN106792978A/en
Application granted granted Critical
Publication of CN106792978B publication Critical patent/CN106792978B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/20—Communication route or path selection, e.g. power-based or shortest path routing based on geographic position or location
    • 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
    • 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

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention provides a cloud-based intelligent data communication method for Internet of vehicles, wherein the Internet of vehicles comprises a backbone network and a sub-network; the backbone network comprises more than two routers; the sub-network comprises three types of nodes, namely an access router, an access node and a vehicle node, and the topological structures of the access router and the access node are tree structures; the vehicle node can rapidly and correctly acquire the service data from the nearest cloud member in a unicast mode through the implementation method provided by the invention, thereby shortening the delay and cost for acquiring the service data, improving the service quality.

Description

Cloud-based intelligent Internet of vehicles data communication method
Technical Field
The invention relates to a data communication method, in particular to an intelligent Internet of vehicles data communication method based on cloud.
Background
In recent years, much research effort has been devoted to the cloud in order to enable users to quickly acquire network services. With the development of network technology, the cloud will become a mode for providing services in the future. At present, the cloud implementation mode is realized through broadcasting, so that both delay and cost are large; the user is difficult to acquire data from the cloud member closest to the user, and data communication delay is further increased; in addition, the mobile switching of cloud members can cause inconsistency of a forwarding table, so that a user cannot acquire data correctly, and the user must apply for the data again to acquire required data, so that the network serviceability is further reduced, and the communication delay is increased.
Disclosure of Invention
The purpose of the invention is as follows: the invention aims to solve the technical problem of providing an intelligent Internet of vehicles data communication method based on cloud aiming at the defects of the prior art. According to the invention, the cloud is realized by replacing broadcast with unicast, and the user can obtain data from the nearest cloud member, so that the delay and cost of providing service by the cloud are reduced, and the network service performance is effectively improved.
The technical scheme is as follows: the invention discloses a cloud-based intelligent data communication method for Internet of vehicles, wherein the Internet of vehicles comprises a backbone network and a sub-network; the backbone network comprises more than two routers; the sub-network comprises three types of nodes, namely an access router, an access node and a vehicle node, and the topological structures of the access router and the access node are tree structures; wherein, the leaf node is an access node, and the root node and the intermediate node are access routers; in the tree structure, an access node or an access router is connected with a father node through an upstream interface of the access node or the access router, the father node is also called an upstream node, the access router is connected with a child node through a downstream interface of the access router, and the child node is also called a downstream node; the access node is provided with a wireless interface and a wired interface, the wired interface is used for connecting an upstream access router, namely a father node, the wireless interface is used for connecting the vehicle node, and the access node and the vehicle node can reach in a multi-hop manner; the upstream interface of the root node of the sub-network is connected with a backbone network, and the sub-network is communicated with another sub-network through the backbone network; the vehicle nodes realize communication through the access node closest to the vehicle nodes, and one access node and the vehicle nodes realizing communication through the access node form a name domain; one vehicle node can be used as a data provider or a data consumer;
a data related to geographic location is defined by a data name, a data name is formed by a name prefix and a name ID, the name prefix is divided into more than two layers and used for defining a geographic location, and the name ID is used for defining a data type; for example, in the data name sz.ks.st 1/identifier, the name prefix sz.ks.st1 is divided into three levels for defining a certain road, the name ID is identifier for indicating that the information type is traffic fault, and the overall meaning of the data name sz.ks.st 1/identifier is traffic fault data on the road;
an access router or an access node is uniquely identified by a name prefix, if the name prefix of the access router is formed by x layers, the downstream access router or the downstream access node, namely a child node, inherits the x-layer name prefix of the access router, and the name prefix is divided into y layers, wherein y > x, namely the front x-layer name prefix of the y-layer name prefix of the downstream access router or the downstream access node is equal to the front x-layer name prefix of the access router; for example, if an access router has a 2-layer name prefix sz.ks, then its downstream access node has a 3-layer name prefix sz.ks.st1, where the first two layers of name prefixes are the same as the name prefix of the access router;
a name domain is uniquely identified by a name prefix of an access node of the name domain;
the sub-networks and the backbone network realize communication through a routing table, and the table entry of the routing table is composed of two domains: a name prefix field and an interface field;
each vehicle node, access node and access router has a unique ID, such as a MAC address or hardware ID;
the message format sent by the vehicle node or the access node comprises 7 parts, namely a name domain, a message type domain, a source coordinate domain, a source ID domain, a target coordinate domain, a target ID domain and a load domain;
the message types are shown in the following table:
message type Message type field value
Sub-network publishing messages 1
Backbone network publishing messages 2
Vehicle-mounted cloud creation message 3
Vehicle-mounted cloud creation response message 4
Vehicle-mounted cloud creation confirmation message 5
Vehicle mountedCloud switching messages 6
Vehicle cloud deletion message 7
Vehicle-mounted cloud request message 8
Vehicle cloud response message 9
The routing table establishment procedure for a subnetwork is as follows:
step 101: starting;
step 102: the access node or the access router of the sub-network constructs a sub-network release message, the name prefix in the name domain of the sub-network release message is the name prefix of the access node or the access router, wherein the name ID is 0, the message type domain value is 1, and the source coordinate domain value, the source ID domain value, the destination coordinate domain value, the destination ID domain value and the load domain value are null;
step 103: judging whether the router is a root access router of the sub-network, if so, performing a step 106, otherwise, performing a step 104;
step 104: the access node or the access router sends the sub-network publishing message from the upstream interface;
step 105: the upstream access router receives the sub-network release message from an interface f connected with an access node or an access router which sends the sub-network release message, and then creates a table entry in a routing table, wherein the name prefix domain of the table entry is the name prefix in the name domain in the sub-network release message, and the interface domain value is f;
step 106: finishing;
the routing table establishment process of the backbone network is as follows:
step 201: starting;
step 202: a root access router of a subnetwork constructs a main network release message, a name prefix in a name domain of the main network release message is a name prefix for identifying the main network release message, wherein the name ID is 0, the message type is 2, and the source coordinate domain value, the source ID domain value, the destination coordinate domain value, the destination ID domain value and the load domain value are null; (ii) a
Step 203: the root access router sends the backbone network publishing message from the upstream interface;
step 204: after receiving a backbone network distribution message from an interface f1 connected with a root access router or a router which sends or forwards the backbone network distribution message, a router in the backbone network creates an entry in a routing table, wherein the name prefix domain of the entry is the name prefix in the backbone network distribution message, and the interface domain value is f 1;
step 205: the router in the backbone network checks each interface of itself, judges whether the routing table has an interface domain value as the interface and a name prefix domain value as the name prefix table entry in the received backbone network release message, if yes, executes step 207, otherwise executes step 206;
step 206: the router in the backbone network forwards the received backbone network distribution message from the interface, and executes step 204;
step 207: finishing;
after receiving the message, the access router or the access node firstly checks a routing table, if the matching degree of the name prefix domain value of at least one table entry and the name prefix in the message is higher than the matching degree of the name prefix of the access router or the access node and the name prefix in the message, the matching degree means that the two name prefixes are compared from the first position, the more continuous same bits are, the higher the matching degree of the two name prefixes is, the access router or the access node selects the table entry with the highest matching degree of the name prefix, and then the received message is forwarded from the interface domain of the table entry; otherwise, the received message is forwarded from the upstream interface.
The process can correctly and quickly establish the routing table in the sub-network and the backbone network, thereby ensuring that the vehicle nodes can quickly acquire required data.
In the method, data related to the geographic position is generated by a vehicle-mounted cloud, the vehicle-mounted cloud is defined by a data name defining the data, and a vehicle node or an access node capable of generating, storing and providing the data defined by the vehicle-mounted cloud is called a cloud member;
the access node broadcasts a beacon frame within a one-hop range regularly through a wireless interface, and the load of the beacon frame comprises the geographic coordinate, the ID value and the name prefix of the access node; after receiving the beacon frame from the access node, the vehicle node stores the geographic coordinate, the ID value and the name prefix of the access node, and then broadcasts the beacon frame within a one-hop range at regular intervals, wherein the load of the beacon frame is the stored geographic coordinate, the ID value and the name prefix of the access node;
after the vehicle node V1 receives the beacon frame from another vehicle node V2, if the vehicle node V1 detects that it is closest to the geographic coordinates in the beacon frame compared with other access nodes, it stores the geographic coordinates, ID value and name prefix in the beacon frame, and then broadcasts the beacon frame in a one-hop range periodically, and the beacon frame load is the stored geographic coordinates, ID value and name prefix of the access node; otherwise, the vehicle node V1 discards the received beacon frame;
the vehicle cloud adopts a cloud data table to store and provide data defined by the vehicle cloud, and one cloud data table item comprises three domains: a data name field, a data field, and a time-to-live field; wherein the data name field is used for defining data related to the geographic position, the data field is used for storing the data of the type, the life time is used for defining the life time of the data, and if the life time attenuation is 0, the table entry is automatically deleted from the cloud data table;
the data consumer adopts a cloud retrieval table and a cloud request table to acquire data; the cloud retrieval table is used for storing information of vehicle-mounted cloud members, and the cloud request table is used for realizing aggregation of cloud requests;
in a cloud retrieval table maintained by an access node, one table entry comprises a data name domain, a geographic coordinate domain of a cloud member, a node ID domain and a life cycle domain of the cloud member; accessing a cloud retrieval table maintained by a router, wherein one table item comprises a name domain, an interface domain and a life cycle domain;
in a cloud request table maintained by an access node, one table entry comprises a data name domain, a geographic coordinate domain of a data consumer, a node ID domain of the data consumer and an interface domain; in a cloud request table maintained by an access router, one table entry comprises a data name domain and an interface domain;
the name prefix of the data name N1 is NP1, the name ID is NID1, the data defined by the data name N1 is C1, the access node CAP1 is positioned in a name field ND1, and the access node CAP1 is identified by the name prefix NP 1;
the data C1 can be divided into n partial data, the union of which is equal to the data C1;
the access node CAP1 is the only access node having authority to generate data C1, the access node CAP1 creates data C1 by creating a vehicle-mounted cloud VC1, the vehicle-mounted cloud VC1 is defined by a data name N1, and the process of creating data C1 is as follows:
step 301: starting;
step 302: the access node CAP1 sends vehicle cloud creation information through a wireless interface, the name field of the vehicle cloud creation information is a data name N1, the information type field value is 3, the source coordinate field value and the source ID field value are the own geographic coordinate value and ID value of the access node CAP1, and the destination coordinate field value, the destination ID field value and the load field are null;
step 303: if the vehicle node receiving the vehicle-mounted cloud creation message is located in the name field ND1, forwarding the vehicle-mounted cloud creation message, otherwise, discarding the vehicle-mounted cloud creation message; if the vehicle node receiving the vehicle cloud creation message can provide the data C1 or part of the data C1, performing step 304, otherwise performing step 306;
step 304: the vehicle node receiving the vehicle-mounted cloud creation message constructs a vehicle-mounted cloud creation response message, the data name of the vehicle-mounted cloud creation response message is N1, the message type domain value is 4, the source coordinate domain value and the source ID domain value are the coordinate domain and the ID value of the vehicle node receiving the vehicle-mounted cloud creation message, the destination coordinate domain value and the destination ID domain value are the coordinate domain and the ID value of an access node CAP1, the load domain value is provided data, and then the vehicle-mounted cloud creation response message is forwarded to the neighbor vehicle node closest to the destination coordinate domain value;
step 305: after receiving the vehicle-mounted cloud creation response message, the neighbor vehicle node forwards the vehicle-mounted cloud creation response message to the neighbor vehicle node closest to the destination coordinate threshold value,
step 306: repeating the step 305 until the vehicle-mounted cloud creation response message finally reaches the access node CAP 1;
step 307: after receiving all returned vehicle-mounted cloud creation response messages with the data name domain value of N1, the access node CAP1 executes and operates the load domain values of all the vehicle-mounted cloud creation response messages to construct data C1, creates a table entry in a cloud data table, wherein in the cloud data table entry, the data name domain value is N1, the data domain value is C1, and the lifetime domain value is T1, then the access node CAP1 marks the access node as a cloud member of the vehicle-mounted cloud VC1, and simultaneously sends a vehicle-mounted cloud creation confirmation message through a wireless interface, wherein the data name of the vehicle-mounted cloud creation confirmation message is N1, the message type domain value is 5, the source coordinate domain value and the source ID domain value are the geographic coordinate value and the ID value of the access node, the destination coordinate domain value and the destination ID domain value are null, and the load domain values are data C1 and the lifetime T1;
step 308: if the vehicle node that received the vehicle-mounted cloud creation confirmation message is located in the name domain ND1, if so, executing step 309, otherwise executing step 310;
step 309: the vehicle node receiving the vehicle-mounted cloud creation confirmation message forwards the vehicle-mounted cloud creation confirmation message, meanwhile, a table entry is created in a cloud data table, the data name field value is N1, the data field value is C1, and the lifetime field value is the lifetime in the vehicle-mounted cloud creation confirmation message, then the vehicle node receiving the vehicle-mounted cloud creation confirmation message marks itself as a cloud member of the vehicle-mounted cloud VC1, and step 308 is executed;
step 310: the vehicle node receiving the vehicle-mounted cloud creation confirmation message discards the vehicle-mounted cloud creation confirmation message;
step 311: finishing;
if the lifetime decay of the data C1 is 0, then the entry with the data name field value N1 is deleted from the cloud data table and the access node CAP1 creates the data C1 again by performing the above process.
The above process can correctly establish data to ensure that the vehicle node can quickly acquire the required data.
In the method of the present invention, under the condition that the vehicle node V4 is a cloud member of the vehicle cloud VC1 and is capable of providing data C1, the access node of the name domain ND2 is CAP2, and the access node CAP2 is identified by the name prefix NP2, if the vehicle node V4 moves from the name domain ND1 to the name domain ND2, the vehicle node V4 performs the following movement switching operation:
step 401: starting;
step 402: the vehicle node V4 constructs a vehicle-mounted cloud switching message, the name domain value of the cloud switching message is N1, the message type domain value is 6, the source coordinate and the ID value are the geographic coordinate and the ID value of the vehicle node V4, the destination coordinate and the ID value are the geographic coordinate and the ID value of the access node CAP2, and the load domain value is the life cycle of the data C1; the vehicle node V4 transfers the vehicle-mounted cloud switching message to a neighbor vehicle node closest to the target coordinate;
step 403: the neighbor vehicle node receiving the vehicle-mounted cloud switching message transfers the vehicle-mounted cloud switching message to the own neighbor vehicle node closest to the target coordinate;
step 404: repeating the step 403 until the vehicle cloud switching message reaches the access node CAP 2;
step 405: after receiving the vehicle-mounted cloud switching message, the access node CAP2 creates a cloud retrieval table item, the data name domain value of the cloud retrieval table item is N1, the geographic coordinate domain and the ID domain value are respectively equal to the source coordinate domain value and the source ID value of the vehicle-mounted cloud switching message, and the life cycle is the life cycle of the received vehicle-mounted cloud switching message;
step 406: the access node CAP2 checks the cloud retrieval table to judge whether only one cloud retrieval table item with the data name domain value of N1 exists, if so, step 407 is carried out, otherwise, step 412 is carried out;
step 407: the access node CAP2 forwards the vehicle-mounted cloud switching message from an upstream interface;
step 408: the upstream access router receives the vehicle-mounted cloud switching message from an interface f2, the upstream access router is connected with an access router or an access node which forwards the vehicle-mounted cloud switching message through an interface f2, the upstream access router checks the cloud retrieval table to judge whether a cloud retrieval table item with a data name field value of N1 exists, if so, the step 409 is carried out, otherwise, the step 410 is carried out;
step 409: the upstream access router adds the interface f2 to the interface domain of the table entry with the data name domain value of N1, and executes the step 412;
step 410: the upstream access router creates a cloud retrieval table item, the data name domain value of the cloud retrieval table item is N1, the interface domain value is f2, and the survival time is the survival time in the received vehicle-mounted cloud switching message;
step 411: the upstream access router forwards the vehicle-mounted cloud switching message from the upstream interface, and executes step 408;
step 412: finishing;
after the vehicle node V4 executes mobile switching, a beacon frame is periodically sent to an access node CAP2, and the load of the beacon frame is the current geographic coordinate and the ID value of the vehicle node V4;
if the access node CAP2 does not receive the beacon frame of the vehicle node V4 within the specified time, the following cloud search table update procedure is performed:
step 501: starting;
step 502: the access node CAP2 deletes the cloud retrieval table item with the data name of N1 and the ID value of the vehicle node V4 from the cloud retrieval table, judges whether the cloud retrieval table item with the data name of N1 still exists, if so, executes step 508, otherwise, executes step 503;
step 503: the access node CAP2 sends vehicle-mounted cloud deletion information from an upstream interface, wherein a data name field is N1, an information type field is 7, and a source coordinate, a source ID, a destination coordinate, a destination ID and a load are all null;
step 504: the upstream access router receives the vehicle-mounted cloud deletion message from an interface f3 of the upstream access router, the upstream access router is connected with an access node or an access router which forwards the vehicle-mounted cloud deletion message through an interface f3, the upstream access router checks a cloud retrieval table item with a data name field value of N1 in a cloud retrieval table, and deletes f3 from an interface domain of the cloud retrieval table item, if the interface field value is null, the step 505 is carried out, otherwise, the step 508 is carried out;
step 505: the upstream access router judges whether the upstream access router is a root access router, if so, the step 506 is executed, otherwise, the step 507 is executed;
step 506: the upstream access router deletes the cloud retrieval table entry with the data name domain value of N1, and executes step 508;
step 507: the upstream access router forwards the vehicle cloud deletion message from the upstream interface, deletes the entry with the data name field value of N1, and executes step 504;
step 508: and (6) ending.
The process ensures that the vehicle node can still provide and acquire data correctly and quickly in the moving process, and reduces data communication delay.
In the method of the invention, under the condition that a vehicle node V6 is located in a name domain ND2, an access node of the name domain ND2 is CAP2, data C2 is defined by a data name N2, and a name prefix of the data name N2 is NP2, if the access node CAP2 is defined by a name prefix NP2 or the access node CAP2 has a cloud retrieval table entry with a data name domain value N2 in a cloud retrieval table, the vehicle node V6 acquires the data C2 according to the following process:
step 601: starting;
step 602: the vehicle node V6 creates a vehicle-mounted cloud request message, wherein the data name domain value is N2, the message type domain value is 8, the source coordinate domain and the source ID value are the geographic coordinate and the ID value of the vehicle node V6, the destination coordinate and the destination ID value are the geographic coordinate and the ID value of the access node CAP2, the load is empty, and then the vehicle-mounted cloud request message is forwarded to the vehicle node closest to the destination coordinate or the access node CAP 2;
step 603: if the vehicle node receives the vehicle-mounted cloud request message, executing a step 604, otherwise executing a step 607;
step 604: if the vehicle node receiving the vehicle-mounted cloud request message can provide the data C1, performing step 606, otherwise performing step 605;
step 605: the vehicle node receiving the vehicle-mounted cloud request message forwards the vehicle-mounted cloud request message to a vehicle node closest to the destination coordinate or an access node CAP2, and step 603 is executed;
step 606: the vehicle node receiving the vehicle cloud request message creates a vehicle cloud response message, wherein the data name domain value is N2, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate value and the ID value in the vehicle cloud request message, the load is data C2 and the life cycle, then the vehicle node receiving the vehicle cloud request message forwards the vehicle cloud response message to the vehicle node closest to the destination coordinate, and step 612 is executed;
step 607: after receiving the vehicle-mounted cloud request message, the access node CAP2 judges whether the access node is identified by a name prefix NP2, if so, the step 608 is carried out, otherwise, the step 609 is carried out;
step 608: if the access node CAP2 does not store the data C2 in the cloud data table, executing the steps 301-308 to create the data C2; then the access node CAP2 creates a vehicle cloud response message, wherein the data name domain value is N2, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate and the ID value in the vehicle cloud request message, the load is data C2 and the life cycle, then the access node CAP2 forwards the vehicle cloud response message to the vehicle node closest to the destination coordinate, and step 612 is executed;
step 609: the access node CAP2 selects a cloud retrieval table item with a data name domain value of N1, updates the destination coordinate and the ID value in the vehicle-mounted cloud request message into the geographic coordinate value and the ID value in the cloud retrieval table item, forwards the vehicle-mounted cloud request message to the vehicle node closest to the destination coordinate,
step 610: after receiving the vehicle-mounted cloud request message, the vehicle node forwards the vehicle-mounted cloud request message to the vehicle node closest to the target coordinate;
step 611: repeating the step 610 until the destination vehicle node receives the vehicle-mounted cloud request message, then creating a vehicle-mounted cloud response message by the destination vehicle node, wherein the data name domain value is N2, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate value and the ID value in the vehicle-mounted cloud request message, the load is the life cycle in the cloud data table entry of the data C2 and the stored data C2, then forwarding the vehicle-mounted cloud response message to the vehicle node closest to the destination coordinate by the destination vehicle node, and executing the step 612;
step 612: if the vehicle node V6 receives the vehicle-mounted cloud response message, executing step 613, otherwise executing step 614;
step 613: the vehicle node V6 creates an entry in the cloud data table, the data name field value of the entry is N2, the data field value is C2, the lifetime field value is the lifetime value in the vehicle cloud response message, the vehicle node V6 is converted into a cloud member, and step 615 is executed;
step 614: the vehicle node receiving the vehicle-mounted cloud response message forwards the vehicle-mounted cloud response message to the vehicle node closest to the destination coordinate, and step 612 is executed;
step 615: if the access node CAP2 is not identified by the name prefix NP2, the vehicle node V6 performs step 401 and 412;
step 616: and (6) ending.
The above process ensures that the vehicle node can correctly and quickly acquire data from the nearest cloud member, thereby effectively reducing data communication delay.
In the method of the invention, under the condition that a vehicle node V4 is located in a name domain ND2, an access node of the name domain ND2 is CAP2, data C1 is defined by a data name N1, a name prefix of the data name N1 is NP1, an access node CAP2 is defined by a name prefix NP2, and the access node CAP1 is defined by a name prefix NP1, if the access node CAP2 has no cloud retrieval table entry with a data name domain value of N1 in a cloud retrieval table, the vehicle node V4 acquires the data C1 according to the following process:
step 701: starting;
step 702: the vehicle node V4 creates a vehicle-mounted cloud request message, wherein the data name domain value is N1, the message type domain value is 8, the source coordinate domain and the source ID value are the geographic coordinate and the ID value of the vehicle node V4, the destination coordinate and the destination ID value are the geographic coordinate and the ID value of the access node CAP2, the load is empty, and then the vehicle-mounted cloud request message is forwarded to the vehicle node closest to the destination coordinate;
step 703: the vehicle node receiving the vehicle-mounted cloud request message forwards the vehicle-mounted cloud request message to the vehicle node closest to the target coordinate;
step 704: repeating the step 703 until the vehicle cloud request message reaches the access node CAP 2; after receiving the vehicle-mounted cloud request message from the wireless interface domain w, the access node CAP2 creates a cloud request table entry in the cloud request table, the data name domain value of the cloud request table entry is N1, the geographic coordinate domain value and the ID domain value are the source coordinate value and the ID value of the vehicle-mounted cloud request message, the interface domain is w, the access node CAP2 judges whether the cloud request table has only one cloud request table entry with the data name domain value of N1, if yes, step 705 is performed, otherwise step 720 is performed;
step 705: the access node CAP2 forwards the vehicle-mounted cloud request message from the upstream interface;
step 706: the access router or the access node receives the vehicle-mounted cloud request message from the interface f4, the access router or the access node is connected with the access node or the access router which forwards the vehicle-mounted cloud request message through the interface f4, the access router or the access node which receives the vehicle-mounted cloud request message creates a cloud request table entry in a cloud request table, the data name field value of the cloud request table entry is N1, and the interface field value is f4；
Step 707: if the access router receives the vehicle-mounted cloud request message from the interface f4, the geographic coordinate domain value and the ID domain value in the cloud request table entry created by the access router are null;
step 708: the access router or the access node which receives the vehicle-mounted cloud request message judges whether the cloud request table only has one cloud request table entry with the data name field value of N1, if so, the step 709 is carried out, otherwise, the step 720 is carried out;
step 709: if the access router receives the vehicle-mounted cloud request message and no cloud request table entry with the data name field value of N1 exists in the cloud retrieval table, executing step 710, otherwise executing step 711;
step 710: the access router receiving the vehicle-mounted cloud request message checks a routing table, if the matching degree of the name prefix domain value of at least one table entry and the name prefix NP1 is greater than the matching degree of the name prefix of the access router and the name prefix NP1, the access router selects the table entry with the maximum matching degree of the name prefix, and then the vehicle-mounted cloud request message is forwarded from the interface domain of the table entry; otherwise, forwarding the vehicle-mounted cloud request message from the upstream interface; finally, step 706 is performed; the matching degree refers to that the matching degree is higher as the number of continuous identical digits is larger from the highest digit;
step 711: if the access router receives the vehicle-mounted cloud request message and a cloud retrieval table entry with a data name domain value of N1 exists in the cloud retrieval table, executing step 712, otherwise executing step 713;
step 712: the access router receiving the vehicle cloud request message forwards the vehicle cloud request message from the interface domain of the cloud retrieval table entry with the data name domain value of N1, and step 706 is executed;
step 713: if the access node receives the vehicle-mounted cloud request message and a cloud retrieval table entry with a data name field value of N1 exists in the cloud retrieval table, executing step 714, otherwise executing step 719;
step 714: the access node receiving the vehicle-mounted cloud request message selects a cloud retrieval table item with a data name domain value of N1, updates a source coordinate and an ID value in the vehicle-mounted cloud request message into a geographical coordinate value and an ID value of the access node, updates a target coordinate and an ID value into a geographical coordinate value and an ID value in the table item, and forwards the vehicle-mounted cloud request message to a vehicle node closest to the target coordinate;
step 715: after receiving the vehicle-mounted cloud request message, the vehicle node forwards the vehicle-mounted cloud request message to the vehicle node closest to the target coordinate;
step 716: repeating the step 715 until the destination vehicle node receives the vehicle-mounted cloud request message, then creating a vehicle-mounted cloud response message by the destination vehicle node, wherein the data name domain value is N1, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate value and the ID value in the vehicle-mounted cloud request message, the load is data C2 and the life cycle, and then forwarding the vehicle-mounted cloud response message to the vehicle node closest to the destination coordinate;
step 717: after receiving the vehicle-mounted cloud response message, the vehicle node forwards the vehicle-mounted cloud response message to the vehicle node closest to the target coordinate;
step 718: repeating the step 717 until the destination access node receives the vehicle-mounted cloud request message, and executing the step 720;
step 719: if the access node receiving the vehicle-mounted cloud request message does not store the data C1 in the cloud data table, executing the steps 301-311 to create data C1; then the access node creates a vehicle cloud response message, wherein the data name domain value is N1, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate and the ID value in the vehicle cloud request message, the load is data C2 and the life cycle, then the vehicle cloud response message is forwarded to the vehicle node closest to the destination coordinate, and step 720 is executed;
step 720: if the access node creates or receives an on-board cloud response message, then step 721 is performed, otherwise step 722 is performed;
step 721: the access node performs the following operations for each entry with a data name domain value of N1 in the cloud request table: if the geographic coordinate domain value and the ID domain value of the table entry are null, forwarding the vehicle-mounted cloud response message from the interface domain of the table entry; if the geographic coordinate domain value and the ID domain value of the table entry are not null, updating the geographic coordinate domain value and the ID domain value in the vehicle-mounted cloud response message into the geographic coordinate domain value and the ID domain value in the table entry, and then sending the vehicle-mounted cloud response message from the wireless interface; finally, the access node deletes the entry from the cloud request table, and step 720 is executed;
step 722: if the access router receives the vehicle-mounted cloud response message, executing a step 723, otherwise executing a step 724;
step 723: the access router performs the following operations for each entry with a data name domain value of N1 in the cloud request table: forwarding the vehicle-mounted cloud response message from the interface domain of the table entry, deleting the table entry from the cloud request table, and executing step 720;
step 724: after receiving the vehicle cloud response message, the vehicle node V6 creates an entry in the cloud data table, where the data name domain value of the entry is N1, the data domain value is C1, the lifetime domain value is the lifetime value in the vehicle cloud response message, the vehicle node V4 is converted into a cloud member, and step 401 and step 411 are executed;
step 725: and (6) ending.
The above process ensures that the vehicle node can correctly and quickly acquire data from the nearest cloud member, thereby effectively reducing data communication delay.
Has the advantages that: the invention provides an intelligent Internet of vehicles data communication method based on cloud, vehicle nodes can rapidly and correctly acquire service data from the nearest cloud member in a unicast mode 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 big data acquisition, road condition monitoring and the like, and the method 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 view of a subnet routing table creation process according to the present invention.
Fig. 2 is a schematic diagram of a backbone network routing table creation process according to the present invention.
Fig. 3 is a schematic diagram of a data creation process according to the present invention.
Fig. 4 is a schematic diagram of a mobile handover procedure according to the present invention.
Fig. 5 is a schematic view of a cloud search table updating process according to the present invention.
Fig. 6 is a schematic diagram of a process for acquiring local data according to the present invention.
Fig. 7 is a schematic diagram illustrating a process of acquiring remote data according to the present invention.
The specific implementation mode is as follows:
the invention provides an intelligent Internet of vehicles data communication method based on cloud, vehicle nodes can rapidly and correctly acquire service data from the nearest cloud member in a unicast mode 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 big data acquisition, road condition monitoring and the like, and the method has wide application prospect.
Fig. 1 is a schematic view of a subnet routing table creation process according to the present invention. The car networking comprises a backbone network and a sub-network; the backbone network comprises more than two routers; the sub-network comprises three types of nodes, namely an access router, an access node and a vehicle node, and the topological structures of the access router and the access node are tree structures; wherein, the leaf node is an access node, and the root node and the intermediate node are access routers; in the tree structure, an access node or an access router is connected with a father node through an upstream interface of the access node or the access router, the father node is also called an upstream node, the access router is connected with a child node through a downstream interface of the access router, and the child node is also called a downstream node; the access node is provided with a wireless interface and a wired interface, the wired interface is used for connecting an upstream access router, namely a father node, the wireless interface is used for connecting the vehicle node, and the access node and the vehicle node can reach in a multi-hop manner; the upstream interface of the root node of the sub-network is connected with a backbone network, and the sub-network is communicated with another sub-network through the backbone network; the vehicle nodes realize communication through the access node closest to the vehicle nodes, and one access node and the vehicle nodes realizing communication through the access node form a name domain; one vehicle node can be used as a data provider or a data consumer;
a data related to geographic location is defined by a data name, a data name is formed by a name prefix and a name ID, the name prefix is divided into more than two layers and used for defining a geographic location, and the name ID is used for defining a data type; for example, in the data name sz.ks.st 1/identifier, the name prefix sz.ks.st1 is divided into three levels for defining a certain road, the name ID is identifier for indicating that the information type is traffic fault, and the overall meaning of the data name sz.ks.st 1/identifier is traffic fault data on the road;
an access router or an access node is uniquely identified by a name prefix, if the name prefix of the access router is formed by x layers, the downstream access router or the downstream access node, namely a child node, inherits the x-layer name prefix of the access router, and the name prefix is divided into y layers, wherein y > x, namely the front x-layer name prefix of the y-layer name prefix of the downstream access router or the downstream access node is equal to the front x-layer name prefix of the access router; for example, if an access router has a 2-layer name prefix sz.ks, then its downstream access node has a 3-layer name prefix sz.ks.st1, where the first two layers of name prefixes are the same as the name prefix of the access router;
a name domain is uniquely identified by a name prefix of an access node of the name domain;
the sub-networks and the backbone network realize communication through a routing table, and the table entry of the routing table is composed of two domains: a name prefix field and an interface field;
each vehicle node, access node and access router has a unique ID, such as a MAC address or hardware ID;
the message format sent by the vehicle node or the access node comprises 7 parts, namely a name domain, a message type domain, a source coordinate domain, a source ID domain, a target coordinate domain, a target ID domain and a load domain;
the message types are shown in the following table:
Figure GDA0002074905110000121
Figure GDA0002074905110000131
the routing table establishment procedure for a subnetwork is as follows:
step 101: starting;
step 102: the access node or the access router of the sub-network constructs a sub-network release message, the name prefix in the name domain of the sub-network release message is the name prefix of the access node or the access router, wherein the name ID is 0, the message type domain value is 1, and the source coordinate domain value, the source ID domain value, the destination coordinate domain value, the destination ID domain value and the load domain value are null;
step 103: judging whether the router is a root access router of the sub-network, if so, performing a step 106, otherwise, performing a step 104;
step 104: the access node or the access router sends the sub-network publishing message from the upstream interface;
step 105: the upstream access router receives the sub-network release message from an interface f connected with an access node or an access router which sends the sub-network release message, and then creates a table entry in a routing table, wherein the name prefix domain of the table entry is the name prefix in the name domain in the sub-network release message, and the interface domain value is f;
step 106: and (6) ending.
Fig. 2 is a schematic diagram of a backbone network routing table creation process according to the present invention. The routing table establishment process of the backbone network is as follows:
step 201: starting;
step 202: a root access router of a subnetwork constructs a main network release message, a name prefix in a name domain of the main network release message is a name prefix for identifying the main network release message, wherein the name ID is 0, the message type is 2, and the source coordinate domain value, the source ID domain value, the destination coordinate domain value, the destination ID domain value and the load domain value are null; (ii) a
Step 203: the root access router sends the backbone network publishing message from the upstream interface;
step 204: after receiving a backbone network distribution message from an interface f1 connected with a root access router or a router which sends or forwards the backbone network distribution message, a router in the backbone network creates an entry in a routing table, wherein the name prefix domain of the entry is the name prefix in the backbone network distribution message, and the interface domain value is f 1;
step 205: the router in the backbone network checks each interface of itself, judges whether the routing table has an interface domain value as the interface and a name prefix domain value as the name prefix table entry in the received backbone network release message, if yes, executes step 207, otherwise executes step 206;
step 206: the router in the backbone network forwards the received backbone network distribution message from the interface, and executes step 204;
step 207: finishing;
after receiving the message, the access router or the access node firstly checks a routing table, if the matching degree of the name prefix domain value of at least one table entry and the name prefix in the message is higher than the matching degree of the name prefix of the access router or the access node and the name prefix in the message, the matching degree means that the two name prefixes are compared from the first position, the more continuous same bits are, the higher the matching degree of the two name prefixes is, the access router or the access node selects the table entry with the highest matching degree of the name prefix, and then the received message is forwarded from the interface domain of the table entry; otherwise, the received message is forwarded from the upstream interface.
The process can correctly and quickly establish the routing table in the sub-network and the backbone network, thereby ensuring that the vehicle nodes can quickly acquire required data.
Fig. 3 is a schematic diagram of a data creation process according to the present invention. One type of data related to geographic location is generated by an on-board cloud defined by a data name defining the data, and vehicle nodes or access nodes capable of generating, storing and providing the data defined by the on-board cloud are called cloud members;
the access node broadcasts a beacon frame within a one-hop range regularly through a wireless interface, and the load of the beacon frame comprises the geographic coordinate, the ID value and the name prefix of the access node; after receiving the beacon frame from the access node, the vehicle node stores the geographic coordinate, the ID value and the name prefix of the access node, and then broadcasts the beacon frame within a one-hop range at regular intervals, wherein the load of the beacon frame is the stored geographic coordinate, the ID value and the name prefix of the access node;
after the vehicle node V1 receives the beacon frame from another vehicle node V2, if the vehicle node V1 detects that it is closest to the geographic coordinates in the beacon frame compared with other access nodes, it stores the geographic coordinates, ID value and name prefix in the beacon frame, and then broadcasts the beacon frame in a one-hop range periodically, and the beacon frame load is the stored geographic coordinates, ID value and name prefix of the access node; otherwise, the vehicle node V1 discards the received beacon frame;
the vehicle cloud adopts a cloud data table to store and provide data defined by the vehicle cloud, and one cloud data table item comprises three domains: a data name field, a data field, and a time-to-live field; wherein the data name field is used for defining data related to the geographic position, the data field is used for storing the data of the type, the life time is used for defining the life time of the data, and if the life time attenuation is 0, the table entry is automatically deleted from the cloud data table;
the data consumer adopts a cloud retrieval table and a cloud request table to acquire data; the cloud retrieval table is used for storing information of vehicle-mounted cloud members, and the cloud request table is used for realizing aggregation of cloud requests;
in a cloud retrieval table maintained by an access node, one table entry comprises a data name domain, a geographic coordinate domain of a cloud member, a node ID domain and a life cycle domain of the cloud member; accessing a cloud retrieval table maintained by a router, wherein one table item comprises a name domain, an interface domain and a life cycle domain;
in a cloud request table maintained by an access node, one table entry comprises a data name domain, a geographic coordinate domain of a data consumer, a node ID domain of the data consumer and an interface domain; in a cloud request table maintained by an access router, one table entry comprises a data name domain and an interface domain;
the name prefix of the data name N1 is NP1, the name ID is NID1, the data defined by the data name N1 is C1, the access node CAP1 is positioned in a name field ND1, and the access node CAP1 is identified by the name prefix NP 1;
the data C1 can be divided into n partial data, the union of which is equal to the data C1;
the access node CAP1 is the only access node having authority to generate data C1, the access node CAP1 creates data C1 by creating a vehicle-mounted cloud VC1, the vehicle-mounted cloud VC1 is defined by a data name N1, and the process of creating data C1 is as follows:
step 301: starting;
step 302: the access node CAP1 sends vehicle cloud creation information through a wireless interface, the name field of the vehicle cloud creation information is a data name N1, the information type field value is 3, the source coordinate field value and the source ID field value are the own geographic coordinate value and ID value of the access node CAP1, and the destination coordinate field value, the destination ID field value and the load field are null;
step 303: if the vehicle node receiving the vehicle-mounted cloud creation message is located in the name field ND1, forwarding the vehicle-mounted cloud creation message, otherwise, discarding the vehicle-mounted cloud creation message; if the vehicle node receiving the vehicle cloud creation message can provide the data C1 or part of the data C1, performing step 304, otherwise performing step 306;
step 304: the vehicle node receiving the vehicle-mounted cloud creation message constructs a vehicle-mounted cloud creation response message, the data name of the vehicle-mounted cloud creation response message is N1, the message type domain value is 4, the source coordinate domain value and the source ID domain value are the coordinate domain and the ID value of the vehicle node receiving the vehicle-mounted cloud creation message, the destination coordinate domain value and the destination ID domain value are the coordinate domain and the ID value of an access node CAP1, the load domain value is provided data, and then the vehicle-mounted cloud creation response message is forwarded to the neighbor vehicle node closest to the destination coordinate domain value;
step 305: after receiving the vehicle-mounted cloud creation response message, the neighbor vehicle node forwards the vehicle-mounted cloud creation response message to the neighbor vehicle node closest to the target coordinate threshold value;
step 306: repeating the step 305 until the vehicle-mounted cloud creation response message finally reaches the access node CAP 1;
step 307: after receiving all returned vehicle-mounted cloud creation response messages with the data name domain value of N1, the access node CAP1 executes and operates the load domain values of all the vehicle-mounted cloud creation response messages to construct data C1, creates a table entry in a cloud data table, wherein in the cloud data table entry, the data name domain value is N1, the data domain value is C1, and the lifetime domain value is T1, then the access node CAP1 marks the access node as a cloud member of the vehicle-mounted cloud VC1, and simultaneously sends a vehicle-mounted cloud creation confirmation message through a wireless interface, wherein the data name of the vehicle-mounted cloud creation confirmation message is N1, the message type domain value is 5, the source coordinate domain value and the source ID domain value are the geographic coordinate value and the ID value of the access node, the destination coordinate domain value and the destination ID domain value are null, and the load domain values are data C1 and the lifetime T1;
step 308: if the vehicle node that received the vehicle-mounted cloud creation confirmation message is located in the name domain ND1, if so, executing step 309, otherwise executing step 310;
step 309: the vehicle node receiving the vehicle-mounted cloud creation confirmation message forwards the vehicle-mounted cloud creation confirmation message, meanwhile, a table entry is created in a cloud data table, the data name field value is N1, the data field value is C1, and the lifetime field value is the lifetime in the vehicle-mounted cloud creation confirmation message, then the vehicle node receiving the vehicle-mounted cloud creation confirmation message marks itself as a cloud member of the vehicle-mounted cloud VC1, and step 308 is executed;
step 310: the vehicle node receiving the vehicle-mounted cloud creation confirmation message discards the vehicle-mounted cloud creation confirmation message;
step 311: finishing;
if the lifetime decay of the data C1 is 0, then the entry with the data name field value N1 is deleted from the cloud data table and the access node CAP1 creates the data C1 again by performing the above process.
The above process can correctly establish data to ensure that the vehicle node can quickly acquire the required data.
Fig. 4 is a schematic diagram of a mobile handover procedure according to the present invention. Under the condition that the vehicle node V4 is a cloud member of the on-vehicle cloud VC1, and is capable of providing data C1, the access node of the name domain ND2 is CAP2, and the access node CAP2 is identified by the name prefix NP2, if the vehicle node V4 moves from the name domain ND1 to the name domain ND2, then the vehicle node V4 performs the following movement switching operation:
step 401: starting;
step 402: the vehicle node V4 constructs a vehicle-mounted cloud switching message, the name domain value of the cloud switching message is N1, the message type domain value is 6, the source coordinate and the ID value are the geographic coordinate and the ID value of the vehicle node V4, the destination coordinate and the ID value are the geographic coordinate and the ID value of the access node CAP2, and the load domain value is the life cycle of the data C1; the vehicle node V4 transfers the vehicle-mounted cloud switching message to a neighbor vehicle node closest to the target coordinate;
step 403: the neighbor vehicle node receiving the vehicle-mounted cloud switching message transfers the vehicle-mounted cloud switching message to the own neighbor vehicle node closest to the target coordinate;
step 404: repeating the step 403 until the vehicle cloud switching message reaches the access node CAP 2;
step 405: after receiving the vehicle-mounted cloud switching message, the access node CAP2 creates a cloud retrieval table item, the data name domain value of the cloud retrieval table item is N1, the geographic coordinate domain and the ID domain value are respectively equal to the source coordinate domain value and the source ID value of the vehicle-mounted cloud switching message, and the life cycle is the life cycle of the received vehicle-mounted cloud switching message;
step 406: the access node CAP2 checks the cloud retrieval table to judge whether only one cloud retrieval table item with the data name domain value of N1 exists, if so, step 407 is carried out, otherwise, step 412 is carried out;
step 407: the access node CAP2 forwards the vehicle-mounted cloud switching message from an upstream interface;
step 408: the upstream access router receives the vehicle-mounted cloud switching message from an interface f2, the upstream access router is connected with an access router or an access node which forwards the vehicle-mounted cloud switching message through an interface f2, the upstream access router checks the cloud retrieval table to judge whether a cloud retrieval table item with a data name field value of N1 exists, if so, the step 409 is carried out, otherwise, the step 410 is carried out;
step 409: the upstream access router adds the interface f2 to the interface domain of the table entry with the data name domain value of N1, and executes the step 412;
step 410: the upstream access router creates a cloud retrieval table item, the data name domain value of the cloud retrieval table item is N1, the interface domain value is f2, and the survival time is the survival time in the received vehicle-mounted cloud switching message;
step 411: the upstream access router forwards the vehicle-mounted cloud switching message from the upstream interface, and executes step 408;
step 412: finishing;
after the vehicle node V4 executes mobile switching, a beacon frame is periodically sent to an access node CAP2, and the load of the beacon frame is the current geographic coordinate and the ID value of the vehicle node V4;
fig. 5 is a schematic view of a cloud search table updating process according to the present invention. If the access node CAP2 does not receive the beacon frame of the vehicle node V4 within the specified time, the following cloud search table update procedure is performed:
step 501: starting;
step 502: the access node CAP2 deletes the cloud retrieval table item with the data name of N1 and the ID value of the vehicle node V4 from the cloud retrieval table, judges whether the cloud retrieval table item with the data name of N1 still exists, if so, executes step 508, otherwise, executes step 503;
step 503: the access node CAP2 sends vehicle-mounted cloud deletion information from an upstream interface, wherein a data name field is N1, an information type field is 7, and a source coordinate, a source ID, a destination coordinate, a destination ID and a load are all null;
step 504: the upstream access router receives the vehicle-mounted cloud deletion message from an interface f3 of the upstream access router, the upstream access router is connected with an access node or an access router which forwards the vehicle-mounted cloud deletion message through an interface f3, the upstream access router checks a cloud retrieval table item with a data name field value of N1 in a cloud retrieval table, and deletes f3 from an interface domain of the cloud retrieval table item, if the interface field value is null, the step 505 is carried out, otherwise, the step 508 is carried out;
step 505: the upstream access router judges whether the upstream access router is a root access router, if so, the step 506 is executed, otherwise, the step 507 is executed;
step 506: the upstream access router deletes the cloud retrieval table entry with the data name domain value of N1, and executes step 508;
step 507: the upstream access router forwards the vehicle cloud deletion message from the upstream interface, deletes the entry with the data name field value of N1, and executes step 504;
step 508: and (6) ending.
The process ensures that the vehicle node can still provide and acquire data correctly and quickly in the moving process, and reduces data communication delay.
Fig. 6 is a schematic diagram of a process for acquiring local data according to the present invention. Under the condition that the vehicle node V6 is located in the name domain ND2, the access node of the name domain ND2 is CAP2, the data C2 is defined by a data name N2, and the name prefix of the data name N2 is NP2, if the access node CAP2 is defined by a name prefix NP2 or the access node CAP2 has a cloud retrieval entry with a data name domain value N2 in the cloud retrieval table, the vehicle node V6 acquires the data C2 according to the following procedure:
step 601: starting;
step 602: the vehicle node V6 creates a vehicle-mounted cloud request message, wherein the data name domain value is N2, the message type domain value is 8, the source coordinate domain and the source ID value are the geographic coordinate and the ID value of the vehicle node V6, the destination coordinate and the destination ID value are the geographic coordinate and the ID value of the access node CAP2, the load is empty, and then the vehicle-mounted cloud request message is forwarded to the vehicle node closest to the destination coordinate or the access node CAP 2;
step 603: if the vehicle node receives the vehicle-mounted cloud request message, executing a step 604, otherwise executing a step 607;
step 604: if the vehicle node receiving the vehicle-mounted cloud request message can provide the data C1, performing step 606, otherwise performing step 605;
step 605: the vehicle node receiving the vehicle-mounted cloud request message forwards the vehicle-mounted cloud request message to a vehicle node closest to the destination coordinate or an access node CAP2, and step 603 is executed;
step 606: the vehicle node receiving the vehicle cloud request message creates a vehicle cloud response message, wherein the data name domain value is N2, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate value and the ID value in the vehicle cloud request message, the load is data C2 and the life cycle, then the vehicle node receiving the vehicle cloud request message forwards the vehicle cloud response message to the vehicle node closest to the destination coordinate, and step 612 is executed;
step 607: after receiving the vehicle-mounted cloud request message, the access node CAP2 judges whether the access node is identified by a name prefix NP2, if so, the step 608 is carried out, otherwise, the step 609 is carried out;
step 608: if the access node CAP2 does not store the data C2 in the cloud data table, executing the steps 301-308 to create the data C2; then the access node CAP2 creates a vehicle cloud response message, wherein the data name domain value is N2, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate and the ID value in the vehicle cloud request message, the load is data C2 and the life cycle, then the access node CAP2 forwards the vehicle cloud response message to the vehicle node closest to the destination coordinate, and step 612 is executed;
step 609: the access node CAP2 selects a cloud retrieval table item with a data name domain value of N1, updates the destination coordinate and the ID value in the vehicle-mounted cloud request message into the geographic coordinate value and the ID value in the cloud retrieval table item, forwards the vehicle-mounted cloud request message to the vehicle node closest to the destination coordinate,
step 610: after receiving the vehicle-mounted cloud request message, the vehicle node forwards the vehicle-mounted cloud request message to the vehicle node closest to the target coordinate;
step 611: repeating the step 610 until the destination vehicle node receives the vehicle-mounted cloud request message, then creating a vehicle-mounted cloud response message by the destination vehicle node, wherein the data name domain value is N2, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate value and the ID value in the vehicle-mounted cloud request message, the load is the life cycle in the cloud data table entry of the data C2 and the stored data C2, then forwarding the vehicle-mounted cloud response message to the vehicle node closest to the destination coordinate by the destination vehicle node, and executing the step 612;
step 612: if the vehicle node V6 receives the vehicle-mounted cloud response message, executing step 613, otherwise, executing step 614;
step 613: the vehicle node V6 creates an entry in the cloud data table, the data name field value of the entry is N2, the data field value is C2, the lifetime field value is the lifetime value in the vehicle cloud response message, the vehicle node V6 is converted into a cloud member, and step 615 is executed;
step 614: the vehicle node receiving the vehicle-mounted cloud response message forwards the vehicle-mounted cloud response message to the vehicle node closest to the destination coordinate, and step 612 is executed;
step 615: if the access node CAP2 is not identified by the name prefix NP2, the vehicle node V6 performs step 401 and 412;
step 616: and (6) ending.
The above process ensures that the vehicle node can correctly and quickly acquire data from the nearest cloud member, thereby effectively reducing data communication delay.
Fig. 7 is a schematic diagram illustrating a process of acquiring remote data according to the present invention. Under the condition that the vehicle node V4 is located in the name domain ND2, the access node of the name domain ND2 is CAP2, the data C1 is defined by a data name N1, the name prefix of the data name N1 is NP1, the access node CAP2 is defined by a name prefix NP2, and the access node CAP1 is defined by a name prefix NP1, if the access node CAP2 does not have a cloud retrieval table entry with a data name domain value of N1 in the cloud retrieval table, the vehicle node V4 acquires the data C1 according to the following procedure:
step 701: starting;
step 702: the vehicle node V4 creates a vehicle-mounted cloud request message, wherein the data name domain value is N1, the message type domain value is 8, the source coordinate domain and the source ID value are the geographic coordinate and the ID value of the vehicle node V4, the destination coordinate and the destination ID value are the geographic coordinate and the ID value of the access node CAP2, the load is empty, and then the vehicle-mounted cloud request message is forwarded to the vehicle node closest to the destination coordinate;
step 703: the vehicle node receiving the vehicle-mounted cloud request message forwards the vehicle-mounted cloud request message to the vehicle node closest to the target coordinate;
step 704: repeating the step 703 until the vehicle cloud request message reaches the access node CAP 2; after receiving the vehicle-mounted cloud request message from the wireless interface domain w, the access node CAP2 creates a cloud request table entry in the cloud request table, the data name domain value of the cloud request table entry is N1, the geographic coordinate domain value and the ID domain value are the source coordinate value and the ID value of the vehicle-mounted cloud request message, the interface domain is w, the access node CAP2 judges whether the cloud request table has only one cloud request table entry with the data name domain value of N1, if yes, step 705 is performed, otherwise step 720 is performed;
step 705: the access node CAP2 forwards the vehicle-mounted cloud request message from the upstream interface;
step 706: the access router or the access node receives the vehicle-mounted cloud request message from the interface f4, the access router or the access node is connected with the access node or the access router which forwards the vehicle-mounted cloud request message through the interface f4, the access router or the access node which receives the vehicle-mounted cloud request message creates a cloud request table entry in a cloud request table, the data name field value of the cloud request table entry is N1, and the interface field value is f4；
Step 707: if the access router receives the vehicle-mounted cloud request message from the interface f4, the geographic coordinate domain value and the ID domain value in the cloud request table entry created by the access router are null;
step 708: the access router or the access node which receives the vehicle-mounted cloud request message judges whether the cloud request table only has one cloud request table entry with the data name field value of N1, if so, the step 709 is carried out, otherwise, the step 720 is carried out;
step 709: if the access router receives the vehicle-mounted cloud request message and no cloud request table entry with the data name field value of N1 exists in the cloud retrieval table, executing step 710, otherwise executing step 711;
step 710: the access router receiving the vehicle-mounted cloud request message checks a routing table, if the matching degree of the name prefix domain value of at least one table entry and the name prefix NP1 is greater than the matching degree of the name prefix of the access router and the name prefix NP1, the access router selects the table entry with the maximum matching degree of the name prefix, and then the vehicle-mounted cloud request message is forwarded from the interface domain of the table entry; otherwise, forwarding the vehicle-mounted cloud request message from the upstream interface; finally, step 706 is performed; the matching degree refers to that the matching degree is higher as the number of continuous identical digits is larger from the highest digit;
step 711: if the access router receives the vehicle-mounted cloud request message and a cloud retrieval table entry with a data name domain value of N1 exists in the cloud retrieval table, executing step 712, otherwise executing step 713;
step 712: the access router receiving the vehicle cloud request message forwards the vehicle cloud request message from the interface domain of the cloud retrieval table entry with the data name domain value of N1, and step 706 is executed;
step 713: if the access node receives the vehicle-mounted cloud request message and a cloud retrieval table entry with a data name field value of N1 exists in the cloud retrieval table, executing step 714, otherwise executing step 719;
step 714: the access node receiving the vehicle-mounted cloud request message selects a cloud retrieval table item with a data name domain value of N1, updates a source coordinate and an ID value in the vehicle-mounted cloud request message into a geographical coordinate value and an ID value of the access node, updates a target coordinate and an ID value into a geographical coordinate value and an ID value in the table item, and forwards the vehicle-mounted cloud request message to a vehicle node closest to the target coordinate;
step 715: after receiving the vehicle-mounted cloud request message, the vehicle node forwards the vehicle-mounted cloud request message to the vehicle node closest to the target coordinate;
step 716: repeating the step 715 until the destination vehicle node receives the vehicle-mounted cloud request message, then creating a vehicle-mounted cloud response message by the destination vehicle node, wherein the data name domain value is N1, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate value and the ID value in the vehicle-mounted cloud request message, the load is data C2 and the life cycle, and then forwarding the vehicle-mounted cloud response message to the vehicle node closest to the destination coordinate;
step 717: after receiving the vehicle-mounted cloud response message, the vehicle node forwards the vehicle-mounted cloud response message to the vehicle node closest to the target coordinate;
step 718: repeating the step 717 until the destination access node receives the vehicle-mounted cloud request message, and executing the step 720;
step 719: if the access node receiving the vehicle-mounted cloud request message does not store the data C1 in the cloud data table, executing the steps 301-311 to create data C1; then the access node creates a vehicle cloud response message, wherein the data name domain value is N1, the message type domain value is 9, the source coordinate value and the ID value are the own geographic coordinate value and ID value, the destination coordinate value and the ID value are the source coordinate and the ID value in the vehicle cloud request message, the load is data C2 and the life cycle, then the vehicle cloud response message is forwarded to the vehicle node closest to the destination coordinate, and step 720 is executed;
step 720: if the access node creates or receives an on-board cloud response message, then step 721 is performed, otherwise step 722 is performed;
step 721: the access node performs the following operations for each entry with a data name domain value of N1 in the cloud request table: if the geographic coordinate domain value and the ID domain value of the table entry are null, forwarding the vehicle-mounted cloud response message from the interface domain of the table entry; if the geographic coordinate domain value and the ID domain value of the table entry are not null, updating the geographic coordinate domain value and the ID domain value in the vehicle-mounted cloud response message into the geographic coordinate domain value and the ID domain value in the table entry, and then sending the vehicle-mounted cloud response message from the wireless interface; finally, the access node deletes the entry from the cloud request table, and step 720 is executed;
step 722: if the access router receives the vehicle-mounted cloud response message, executing a step 723, otherwise executing a step 724;
step 723: the access router performs the following operations for each entry with a data name domain value of N1 in the cloud request table: forwarding the vehicle-mounted cloud response message from the interface domain of the table entry, deleting the table entry from the cloud request table, and executing step 720;
step 724: after receiving the vehicle cloud response message, the vehicle node V6 creates an entry in the cloud data table, where the data name domain value of the entry is N1, the data domain value is C1, the lifetime domain value is the lifetime value in the vehicle cloud response message, the vehicle node V4 is converted into a cloud member, and step 401 and step 411 are executed;
step 725: and (6) ending.
The above process ensures that the vehicle node can correctly and quickly acquire data from the nearest cloud member, thereby effectively reducing data communication delay.
Example 1
Based on the simulation parameters in table 1, the present embodiment simulates the cloud-based intelligent internet of vehicles data communication method in the present invention, and the performance analysis is as follows: with the increase of the node density of the vehicle, the number of cloud members is increased, the distribution area is wider, and therefore the delay and the cost for acquiring service data are reduced. The average delay of the vehicle node for acquiring the service data is 100ms, and the average cost is 8.
TABLE 1 simulation parameters
Figure GDA0002074905110000221
The invention provides a thought of an intelligent cloud-based vehicle networking data communication method, and a plurality of methods and ways for realizing the technical scheme, and the above description is only a preferred embodiment of the invention, and 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 invention, and these improvements and decorations should also be regarded as the protection scope of the invention. The components not specified in this embodiment can be implemented by the prior art.

Claims (3)

1. A cloud-based intelligent data communication method for Internet of vehicles is characterized in that the Internet of vehicles comprises a backbone network and a sub-network; the backbone network comprises more than two routers; the sub-network comprises three types of nodes, namely an access router, an access node and a vehicle node, and the topological structures of the access router and the access node are tree structures; wherein, the leaf node is an access node, and the root node and the intermediate node are access routers; in the tree structure, an access node or an access router is connected with a father node through an upstream interface of the access node or the access router, the father node is also called an upstream node, the access router is connected with a child node through a downstream interface of the access router, and the child node is also called a downstream node; the access node is provided with a wireless interface and a wired interface, the wired interface is used for connecting an upstream access router, namely a father node, the wireless interface is used for connecting the vehicle node, and the access node and the vehicle node can reach in a multi-hop manner; the upstream interface of the root node of the sub-network is connected with a backbone network, and the sub-network is communicated with another sub-network through the backbone network; the vehicle nodes realize communication through the access node closest to the vehicle nodes, and one access node and the vehicle nodes realizing communication through the access node form a name domain; one vehicle node can be used as a data provider or a data consumer;
a data related to geographic location is defined by a data name, a data name is formed by a name prefix and a name ID, the name prefix is divided into more than two layers and used for defining a geographic location, and the name ID is used for defining a data type;
an access router or an access node is uniquely identified by a name prefix, if the name prefix of the access router is formed by x layers, the downstream access router or the downstream access node, namely a child node, inherits the x-layer name prefix of the access router, and the name prefix is divided into y layers, wherein y > x, namely the front x-layer name prefix of the y-layer name prefix of the downstream access router or the downstream access node is equal to the front x-layer name prefix of the access router;
a name domain is uniquely identified by a name prefix of an access node of the name domain;
the sub-networks and the backbone network realize communication through a routing table, and the table entry of the routing table is composed of two domains: a name prefix field and an interface field;
each vehicle node, access node and access router has a unique ID;
the message format sent by the vehicle node or the access node comprises 7 parts, namely a data name domain, a message type domain, a source coordinate domain, a source ID domain, a target coordinate domain, a target ID domain and a load domain;
the message types include: a sub-network issuing message, a backbone network issuing message, a vehicle-mounted cloud creation response message, a vehicle-mounted cloud creation confirmation message, a vehicle-mounted cloud switching message, a vehicle-mounted cloud deletion message, a vehicle-mounted cloud request message and a vehicle-mounted cloud response message; the message type domain values corresponding to the sub-network release message, the backbone network release message, the vehicle-mounted cloud creation response message, the vehicle-mounted cloud creation confirmation message, the vehicle-mounted cloud switching message, the vehicle-mounted cloud deletion message, the vehicle-mounted cloud request message and the vehicle-mounted cloud response message are respectively 1, 2, 3, 4, 5, 6, 7, 8 and 9;
the routing table establishment procedure for a subnetwork is as follows:
step 101: starting;
step 102: the access node or the access router of the sub-network constructs a sub-network release message, the name prefix in the data name domain of the sub-network release message is the name prefix of the access node or the access router, wherein the name ID is 0, the message type domain value is 1, and the source coordinate domain value, the source ID domain value, the destination coordinate domain value, the destination ID domain value and the load domain value are null;
step 103: judging whether the router is a root access router of the sub-network, if so, performing a step 106, otherwise, performing a step 104;
step 104: the access node or the access router sends the sub-network publishing message from the upstream interface;
step 105: the upstream access router receives the sub-network release message from an interface f connected with an access node or an access router which sends the sub-network release message, and then creates a table entry in a routing table, wherein the name prefix domain of the table entry is the name prefix in the data name domain in the sub-network release message, and the interface domain value is f;
step 106: finishing;
the routing table establishment process of the backbone network is as follows:
step 201: starting;
step 202: a root access router of a subnetwork constructs a main network release message, a name prefix in a data name domain of the main network release message is a name prefix for identifying the main network release message, wherein the name ID is 0, the message type is 2, and a source coordinate domain value, a source ID domain value, a destination coordinate domain value, a destination ID domain value and a load domain value are null;
step 203: the root access router sends the backbone network publishing message from the upstream interface;
step 204: after receiving a backbone network distribution message from an interface f1 connected with a root access router or a router which sends or forwards the backbone network distribution message, a router in the backbone network creates an entry in a routing table, wherein the name prefix domain of the entry is the name prefix in the backbone network distribution message, and the interface domain value is f 1;
step 205: the router in the backbone network checks each interface of itself, judges whether the routing table has an interface domain value as the interface and a name prefix domain value as the name prefix table entry in the received backbone network release message, if yes, executes step 207, otherwise executes step 206;
step 206: the router in the backbone network forwards the received backbone network distribution message from the interface, and executes step 204;
step 207: finishing;
after receiving the message, the access router or the access node firstly checks a routing table, if the matching degree of the name prefix domain value of at least one table entry and the name prefix in the message is higher than the matching degree of the name prefix of the access router or the access node and the name prefix in the message, the matching degree means that the two name prefixes are compared from the first position, the more continuous same bits are, the higher the matching degree of the two name prefixes is, the access router or the access node selects the table entry with the highest matching degree of the name prefix, and then the received message is forwarded from the interface domain of the table entry; otherwise, the received message is forwarded from the upstream interface.
2. A cloud-based intelligent vehicle networking data communication method according to claim 1, wherein a data related to geographical location is generated by a vehicle cloud defined by a data name defining the data, and vehicle nodes or access nodes capable of generating, storing and providing the data defined by the vehicle cloud are called cloud members;
the access node broadcasts a beacon frame within a one-hop range regularly through a wireless interface, and the load of the beacon frame comprises the geographic coordinate, the ID value and the name prefix of the access node; after receiving the beacon frame from the access node, the vehicle node stores the geographic coordinate, the ID value and the name prefix of the access node, and then broadcasts the beacon frame within a one-hop range at regular intervals, wherein the load of the beacon frame is the stored geographic coordinate, the ID value and the name prefix of the access node;
after the vehicle node V1 receives the beacon frame from another vehicle node V2, if the vehicle node V1 detects that it is closest to the geographic coordinates in the beacon frame compared with other access nodes, it stores the geographic coordinates, ID value and name prefix in the beacon frame, and then broadcasts the beacon frame in a one-hop range periodically, and the beacon frame load is the stored geographic coordinates, ID value and name prefix of the access node; otherwise, the vehicle node V1 discards the received beacon frame;
the vehicle cloud adopts a cloud data table to store and provide data defined by the vehicle cloud, and one cloud data table item comprises three domains: a data name field, a data field, and a time-to-live field; wherein the data name field is used for defining data related to the geographic position, the data field is used for storing the data of the type, the life time is used for defining the life time of the data, and if the life time attenuation is 0, the table entry is automatically deleted from the cloud data table;
the data consumer adopts a cloud retrieval table and a cloud request table to acquire data; the cloud retrieval table is used for storing information of vehicle-mounted cloud members, and the cloud request table is used for realizing aggregation of cloud requests;
in a cloud retrieval table maintained by an access node, one table entry comprises a data name domain, a geographic coordinate domain of a cloud member, a node ID domain and a life cycle domain of the cloud member; accessing a cloud retrieval table maintained by a router, wherein one table entry comprises a data name domain, an interface domain and a life cycle domain;
in a cloud request table maintained by an access node, one table entry comprises a data name domain, a geographic coordinate domain of a data consumer, a node ID domain of the data consumer and an interface domain; in a cloud request table maintained by an access router, one table entry comprises a data name domain and an interface domain;
the name prefix of the data name N1 is NP1, the name ID is NID1, the data defined by the data name N1 is C1, the access node CAP1 is positioned in a name field ND1, and the access node CAP1 is identified by the name prefix NP 1;
the data C1 can be divided into n partial data, the union of which is equal to the data C1;
the access node CAP1 is the only access node having authority to generate data C1, the access node CAP1 creates data C1 by creating a vehicle-mounted cloud VC1, the vehicle-mounted cloud VC1 is defined by a data name N1, and the process of creating data C1 is as follows:
step 301: starting;
step 302: the access node CAP1 sends vehicle cloud creation information through a wireless interface, the data name field of the vehicle cloud creation information is a data name N1, the information type field value is 3, the source coordinate field value and the source ID field value are the own geographic coordinate value and ID value of the access node CAP1, and the destination coordinate field value, the destination ID field value and the load field are null;
step 303: if the vehicle node receiving the vehicle-mounted cloud creation message is located in the name field ND1, forwarding the vehicle-mounted cloud creation message, otherwise, discarding the vehicle-mounted cloud creation message; if the vehicle node receiving the vehicle cloud creation message can provide the data C1 or part of the data C1, performing step 304, otherwise performing step 306;
step 304: the vehicle node receiving the vehicle-mounted cloud creation message constructs a vehicle-mounted cloud creation response message, the data name of the vehicle-mounted cloud creation response message is N1, the message type domain value is 4, the source coordinate domain value and the source ID domain value are the coordinate domain and the ID value of the vehicle node receiving the vehicle-mounted cloud creation message, the destination coordinate domain value and the destination ID domain value are the coordinate domain and the ID value of an access node CAP1, the load domain value is provided data, and then the vehicle-mounted cloud creation response message is forwarded to the neighbor vehicle node closest to the destination coordinate domain value;
step 305: after receiving the vehicle-mounted cloud creation response message, the neighbor vehicle node forwards the vehicle-mounted cloud creation response message to the neighbor vehicle node closest to the destination coordinate threshold value,
step 306: repeating the step 305 until the vehicle-mounted cloud creation response message finally reaches the access node CAP 1;
step 307: after receiving all returned vehicle-mounted cloud creation response messages with the data name domain value of N1, the access node CAP1 executes and operates the load domain values of all the vehicle-mounted cloud creation response messages to construct data C1, creates a table entry in a cloud data table, wherein in the cloud data table entry, the data name domain value is N1, the data domain value is C1, and the lifetime domain value is T1, then the access node CAP1 marks the access node as a cloud member of the vehicle-mounted cloud VC1, and simultaneously sends a vehicle-mounted cloud creation confirmation message through a wireless interface, wherein the data name of the vehicle-mounted cloud creation confirmation message is N1, the message type domain value is 5, the source coordinate domain value and the source ID domain value are the geographic coordinate value and the ID value of the access node, the destination coordinate domain value and the destination ID domain value are null, and the load domain values are data C1 and the lifetime T1;
step 308: if the vehicle node that received the vehicle-mounted cloud creation confirmation message is located in the name domain ND1, if so, executing step 309, otherwise executing step 310;
step 309: the vehicle node receiving the vehicle-mounted cloud creation confirmation message forwards the vehicle-mounted cloud creation confirmation message, meanwhile, a table entry is created in a cloud data table, the data name field value is N1, the data field value is C1, and the lifetime field value is the lifetime in the vehicle-mounted cloud creation confirmation message, then the vehicle node receiving the vehicle-mounted cloud creation confirmation message marks itself as a cloud member of the vehicle-mounted cloud VC1, and step 308 is executed;
step 310: the vehicle node receiving the vehicle-mounted cloud creation confirmation message discards the vehicle-mounted cloud creation confirmation message;
step 311: finishing;
if the lifetime decay of the data C1 is 0, then the entry with the data name field value N1 is deleted from the cloud data table and the access node CAP1 creates the data C1 again by performing the above process.
3. The cloud-based intelligent Internet of vehicles data communication method of claim 2,
under the condition that the vehicle node V4 is a cloud member of the on-vehicle cloud VC1, and is capable of providing data C1, the access node of the name domain ND2 is CAP2, and the access node CAP2 is identified by the name prefix NP2, if the vehicle node V4 moves from the name domain ND1 to the name domain ND2, then the vehicle node V4 performs the following movement switching operation:
step 401: starting;
step 402: the vehicle node V4 constructs a vehicle-mounted cloud switching message, the data name domain value of the cloud switching message is N1, the message type domain value is 6, the source coordinate and the ID value are the geographic coordinate and the ID value of the vehicle node V4, the destination coordinate and the ID value are the geographic coordinate and the ID value of the access node CAP2, and the load domain value is the life cycle of the data C1; the vehicle node V4 transfers the vehicle-mounted cloud switching message to a neighbor vehicle node closest to the target coordinate;
step 403: the neighbor vehicle node receiving the vehicle-mounted cloud switching message transfers the vehicle-mounted cloud switching message to the own neighbor vehicle node closest to the target coordinate;
step 404: repeating the step 403 until the vehicle cloud switching message reaches the access node CAP 2;
step 405: after receiving the vehicle-mounted cloud switching message, the access node CAP2 creates a cloud retrieval table item, the data name domain value of the cloud retrieval table item is N1, the geographic coordinate domain and the ID domain value are respectively equal to the source coordinate domain value and the source ID value of the vehicle-mounted cloud switching message, and the life cycle is the life cycle of the received vehicle-mounted cloud switching message;
step 406: the access node CAP2 checks the cloud retrieval table to judge whether only one cloud retrieval table item with the data name domain value of N1 exists, if so, step 407 is carried out, otherwise, step 412 is carried out;
step 407: the access node CAP2 forwards the vehicle-mounted cloud switching message from an upstream interface;
step 408: the upstream access router receives the vehicle-mounted cloud switching message from an interface f2, the upstream access router is connected with an access router or an access node which forwards the vehicle-mounted cloud switching message through an interface f2, the upstream access router checks the cloud retrieval table to judge whether a cloud retrieval table item with a data name field value of N1 exists, if so, the step 409 is carried out, otherwise, the step 410 is carried out;
step 409: the upstream access router adds the interface f2 to the interface domain of the table entry with the data name domain value of N1, and executes the step 412;
step 410: the upstream access router creates a cloud retrieval table item, the data name domain value of the cloud retrieval table item is N1, the interface domain value is f2, the life cycle domain is the survival time in the received vehicle-mounted cloud switching message, if the upstream access router is the root access router, the step 412 is executed, otherwise, the step 411 is executed;
step 411: the upstream access router forwards the vehicle-mounted cloud switching message from the upstream interface, and executes step 408;
step 412: finishing;
after the vehicle node V4 executes mobile switching, a beacon frame is periodically sent to an access node CAP2, and the load of the beacon frame is the current geographic coordinate and the ID value of the vehicle node V4;
if the access node CAP2 does not receive the beacon frame of the vehicle node V4 within the specified time, the following cloud search table update procedure is performed:
step 501: starting;
step 502: the access node CAP2 deletes the cloud retrieval table item with the data name of N1 and the ID value of the vehicle node V4 from the cloud retrieval table, judges whether the cloud retrieval table item with the data name of N1 still exists, if so, executes step 508, otherwise, executes step 503;
step 503: the access node CAP2 sends vehicle-mounted cloud deletion information from an upstream interface, wherein a data name field is N1, an information type field is 7, and a source coordinate, a source ID, a destination coordinate, a destination ID and a load are all null;
step 504: the upstream access router receives the vehicle-mounted cloud deletion message from an interface f3 of the upstream access router, the upstream access router is connected with an access node or an access router which forwards the vehicle-mounted cloud deletion message through an interface f3, the upstream access router checks a cloud retrieval table item with a data name field value of N1 in a cloud retrieval table, and deletes f3 from an interface domain of the cloud retrieval table item, if the interface field value is null, the step 505 is carried out, otherwise, the step 508 is carried out;
step 505: the upstream access router judges whether the upstream access router is a root access router, if so, the step 506 is executed, otherwise, the step 507 is executed;
step 506: the upstream access router deletes the cloud retrieval table entry with the data name domain value of N1, and executes step 508;
step 507: the upstream access router forwards the vehicle cloud deletion message from the upstream interface, deletes the entry with the data name field value of N1, and executes step 504;
step 508: and (6) ending.
CN201710196610.7A 2017-03-29 2017-03-29 Cloud-based intelligent Internet of vehicles data communication method Active CN106792978B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710196610.7A CN106792978B (en) 2017-03-29 2017-03-29 Cloud-based intelligent Internet of vehicles data communication method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710196610.7A CN106792978B (en) 2017-03-29 2017-03-29 Cloud-based intelligent Internet of vehicles data communication method

Publications (2)

Publication Number Publication Date
CN106792978A CN106792978A (en) 2017-05-31
CN106792978B true CN106792978B (en) 2021-03-16

Family

ID=58967843

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710196610.7A Active CN106792978B (en) 2017-03-29 2017-03-29 Cloud-based intelligent Internet of vehicles data communication method

Country Status (1)

Country Link
CN (1) CN106792978B (en)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107395758B (en) * 2017-08-28 2020-04-24 常熟理工学院 Intelligent vehicle-mounted network data communication implementation method based on geographic position
CN107395759B (en) * 2017-08-28 2020-04-21 常熟理工学院 Reliable intelligent Internet of vehicles data communication implementation method
CN107317890B (en) * 2017-08-28 2019-08-30 常熟理工学院 A kind of data transmission realizing method of intelligent vehicle support grid
CN107979645B (en) * 2017-12-06 2020-07-14 常熟理工学院 Internet of things implementation method
CN108011992B (en) * 2017-12-06 2020-08-25 常熟理工学院 Low-delay Internet of things implementation method
CN107995294B (en) * 2017-12-06 2020-07-03 常熟理工学院 Method for realizing multi-hop Internet of vehicles
CN109756546B (en) * 2018-01-24 2021-11-05 启迪云控(北京)科技有限公司 Intelligent networked automobile cloud control operating system
CN108418749B (en) * 2018-03-21 2020-08-18 常熟理工学院 High-efficiency network communication method
CN108494595B (en) * 2018-03-21 2021-03-26 常熟理工学院 High-efficiency new-generation big data network implementation method
CN108600393B (en) * 2018-05-30 2020-08-18 常熟理工学院 Internet of things data communication method based on named data
CN109257422B (en) * 2018-09-06 2022-01-07 桐乡市定邦信息技术有限公司 Method for reconstructing perception network information
CN109041164B (en) * 2018-09-14 2020-06-12 常熟理工学院 Road safety information real-time communication method based on Internet of vehicles
CN109257789B (en) * 2018-09-14 2020-06-30 常熟理工学院 Vehicle-mounted network data communication method based on multi-hop cluster
CN112073529B (en) * 2020-09-15 2021-09-21 常熟理工学院 Method for realizing intelligent medical system based on edge calculation

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106453640A (en) * 2016-11-25 2017-02-22 常熟理工学院 Communication method of intelligent Internet of Vehicles
CN106453081A (en) * 2016-10-19 2017-02-22 常熟理工学院 Data communication method based on vehicular cloud

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106453081A (en) * 2016-10-19 2017-02-22 常熟理工学院 Data communication method based on vehicular cloud
CN106453640A (en) * 2016-11-25 2017-02-22 常熟理工学院 Communication method of intelligent Internet of Vehicles

Also Published As

Publication number Publication date
CN106792978A (en) 2017-05-31

Similar Documents

Publication Publication Date Title
CN106792978B (en) Cloud-based intelligent Internet of vehicles data communication method
CN109257789B (en) Vehicle-mounted network data communication method based on multi-hop cluster
CN106993321B (en) Network data communication method based on cluster
CN102148756B (en) IPv6 over low power wireless personal area network (6LoWPAN) neighbor discovery-based tree routing method
EP2259504B1 (en) A method and node for notifying proxy updating in radio mesh network
CN107333313B (en) Reliable intelligent Internet of vehicles routing implementation method
CN105246118B (en) A kind of wireless communication implementation method based on location information
CN104869563B (en) A kind of Realization Method of Communication of city car networking of future generation
CN104270461A (en) Car network implementation method
CN110831104B (en) Routing method for linear topology wireless ad hoc network
CN105187529A (en) Internet of vehicles implementation method based on positioning information
CN107508927B (en) Future Internet of vehicles data communication method based on cloud
CN101640628B (en) Mesh network-based routing management and routing methods, node, device and system
CN103475752B (en) What the vehicle-mounted net address of a kind of next generation configured realizes method
CN105188104B (en) A kind of implementation method of wireless communication
CN107979645B (en) Internet of things implementation method
CN109089241B (en) Data communication implementation method for vehicle-mounted network
US20090316668A1 (en) Method for generating extented route message, method for generating an extended route reply message, extended route request message, extended route reply message and first and second nodes
CN110401911B (en) Vehicle-mounted cloud implementation method based on named data network
CN104869601A (en) Communication realization method of next-generation internet of vehicle
CN109803342A (en) A kind of unmanned plane method for self-organizing network routing towards balancing energy highly-reliable transmission
CN109089293B (en) Route communication realization method for future mobile network
CN109041164B (en) Road safety information real-time communication method based on Internet of vehicles
CN107360540B (en) Road safety information transmission method based on vehicle-mounted network
CN110719208B (en) Method for implementing new generation network based on shortest path

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