CN110933643B - Method for sharing urban road vehicle-to-vehicle network resources - Google Patents
Method for sharing urban road vehicle-to-vehicle network resources Download PDFInfo
- Publication number
- CN110933643B CN110933643B CN201910855976.XA CN201910855976A CN110933643B CN 110933643 B CN110933643 B CN 110933643B CN 201910855976 A CN201910855976 A CN 201910855976A CN 110933643 B CN110933643 B CN 110933643B
- Authority
- CN
- China
- Prior art keywords
- rsu
- resource
- vehicle node
- vehicle
- requester
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
- H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Abstract
The invention discloses a method for sharing urban road vehicle-to-vehicle network resources, which comprises the following steps: step 1, vehicle node work flow; step 2, RSU work flow; and step 3, managing the work flow of the center. The invention aims to obtain and use the shared entertainment resource stored in another vehicle node in the network by any vehicle node in the vehicle networking through the method. The entertainment resource sharing method is adopted, all sharable resources are supposed to be stored in vehicle nodes in the network, no shared data is stored in a management center or an RSU, and the invention is supposed that the data communication of the nodes in the network can be reliably realized, namely the method does not relate to the routing selection among the nodes and the bottom layer physical communication method.
Description
Technical Field
The invention belongs to the field of application of an internet of vehicles network, and particularly relates to a method for sharing entertainment resources among vehicle nodes in the internet of vehicles network.
Background
The vehicle-mounted equipment on the vehicle can communicate with each other to form a network through a wireless communication technology. In order to fully share data resources stored on vehicle-mounted equipment, particularly entertainment resources with low security level and sensitivity and improve driving comfort of drivers and passengers, the invention designs a vehicle-mounted data resource sharing method suitable for an urban road vehicle-to-vehicle network (a node-dense scene).
Disclosure of Invention
The purpose of the invention is as follows: in order to solve the defects of the prior art, the invention provides a method for sharing urban road vehicle-to-vehicle network resources.
The technical scheme is as follows: a method for sharing urban road vehicle-to-vehicle network resources comprises the following steps:
step 1, vehicle node work flow:
step 1.1, a vehicle node is started to drive on the road, firstly, one of the discovered RSUs is selected as a registered RSU of the road section, and the registration work is completed; the RSU is a Road Side Unit, is a Road Side fixed facility, is used as a wireless access point for accessing a vehicle node into a data cloud in an Internet of vehicles or a vehicle-mounted cloud, is mainly used for forwarding data between the vehicle node and a cloud center, and can also bear other specified light functions;
step 1.2, the vehicle nodes which finish the registration work can apply for using the sharable entertainment resources in the network;
step 1.3, the vehicle node which completes the registration work can respond to the request of the resource user and provide the shared resource for the resource user;
step 1.4, when the vehicle node is about to drive out of the coverage area of the current registered RSU, namely, when the vehicle node is about to drive into the next road section, a new RSU is selected again, and the registration work is completed again; after the new registration is completed, the original registration RSU deletes the registration information of the vehicle node, including a sharable resource list provided by the node;
step 1.5, the vehicle node finishes the driving, informs the current registered RSU that the vehicle is about to be off-line before stopping and extinguishing the vehicle, and finishes related logout work by the current registered RSU;
step 2, RSU work flow:
step 2.1, the RSU broadcasts a heartbeat message periodically to inform all vehicle nodes driving in the coverage road section of the RSU of relevant information. The heartbeat message is broadcast, and the vehicle node receiving the heartbeat message does not forward the heartbeat message. Comprehensively considering the vehicle running speed and limiting the data volume transmitted by the network, the heartbeat message broadcasting period can be set to be not less than 10s;
the format of the heartbeat message is:
| RSU ID | road sectionID |
Step 2.2, the RSU receives a certain vehicle node registration message, adds a relevant record in a local record list and reports the relevant record to a management center;
step 2.3, the RSU receives a certain vehicle node driving-away message or a vehicle node stopping logout message, deletes relevant records in a local record list and reports the relevant records to a management center;
step 2.4, the RSU receives the resource request message of a certain vehicle node in the covered road section, searches the requested resource for the RSU and responds;
step 2.5, the RSU receives the resource storage position information from the neighbor RSU, if the ID of the requester in the information is registered in the RSU, the information is forwarded to the requester, otherwise, the information is ignored;
step 2.6, the RSU receives the resource data required to be forwarded by the resource supplier in the coverage area of the RSU, and forwards the data to the RSU indicated in the RSU ID of the requester;
step 2.6, the RSU receives the resource data required to be forwarded by other RSUs, and forwards the resource data to the RSU which is not indicated by the RSU ID where the requester is located; the RSU is indicated by 'RSU ID where the requester is located', and the RSU forwards the data to the requester;
step 3, management center work flow:
step 3.1, recording and updating the information of the entertainment resources which can be shared in the whole network, wherein the format of the list record is as described above;
and 3.2, responding to the resource request forwarded by the RSU, searching the entertainment resource information list, and feeding back the query result to the requesting RSU.
As an optimization: in the vehicle node work flow, in step 1.1, the vehicle node selects to register the RSU, and the specific method is as follows:
step 1.1.1, the vehicle node receives heartbeat messages issued by a plurality of RSUs, and selects one RSU which is in front of the traveling direction of the vehicle node and has the strongest signal as a registered RSU of the vehicle node on the road section;
step 1.1.2 vehicle node issues available shared resource list of this node to this registered RSU, list item suggested format is:
| entertainment resource number (Main key) | Resource name | Vehicle node ID |
As an optimization: in the vehicle node work flow, in step 1.2, the vehicle node applies for using the sharable resource in the network, and the specific method is as follows:
step 1.2.1, the vehicle node applies for checking the shared resources available in the road section to the registered RSU, and the road section has the interested resources and is to be used, and the step 1.2.3 is switched to;
step 1.2.2 the vehicle node does not find that the road section has the resources to be interested, and can directly send the names of the interested resources to the RSU to request to inquire in the whole network instead. If the query result is yes, the resource is used across RSUs, and the step 1.2.3 is switched to; if the query result is no, giving up the request;
step 1.2.3 after the vehicle node obtains the relevant information of the requested resource, if the requested resource is in the current road section, the vehicle node issues a use request to the resource vehicle node, receives data and uses the data; if the requested resource is not in the current road section, the resource message is sent to the RSU of the current road section, and the RSU requests the resource vehicle node and forwards data instead;
step 1.2.4 if the vehicle node leaves the currently registered RSU before the end of the resource usage, the following options may be selected to execute:
(1) terminating the resource use, and executing the step 1.2.1 to search new sharable resources;
(2) and continuing to use the resource, after finishing the registration of the new RSU, reporting the resource which is being used by the RSU to the new registered RSU, and performing data transfer instead of the new RSU, wherein the report resource use message format is as follows:
and simultaneously reporting the updated RSU ID to the resource provider, wherein the report message format is as follows:
as an optimization: in the vehicle node work flow, in step 1.3, the vehicle node responds to the application and provides the sharable resource, and the specific method is as follows:
step 1.3.1, the resource requested by the requester exists in the node, and the step 1.3.2 is continuously executed, otherwise, the resource non-existence error prompt message is returned to the requester;
step 1.3.2, the resource data applied by the requester is sent to the requester, the resource data can be divided into a plurality of messages for transmission, and the header format of each message is as follows:
if the sent message is the first message of the resource, a connection number needs to be created, and the connection number is unique in the whole network and remains unchanged in the subsequent message for transmitting the resource; in order to ensure the uniqueness of the whole network, the format of the connection number is as follows:
requester ID + supplier is the number of this connection;
wherein, the 'supplier is the number of the connection' adopts a self-increment method, and the number is increased by 1 when a new connection is built;
and 1.3.3, the node is about to leave the coverage range of the current RSU and enter the coverage range of the next RSU, and after the registration of a new RSU is finished, the ID of the RSU where the supplier is located is changed according to the message format given in the step 1.3.2, and then the resource data transmission is continued.
As an optimization: in the RSU workflow, in step 2.4, the RSU responds to the resource request of the vehicle node within its coverage area, and the specific method is as follows:
step 2.4.1, searching a local resource list, releasing a resource storage position (resource supplier ID) to a requester when the requested resource exists in the coverage range of the RSU, wherein the release message format is as follows:
step 2.4.2, if the request resource is not in the local resource list, the request is forwarded to the management center, and after the returned result of the management center is received, if the requester is still in the coverage range of the RSU, the result is forwarded to the requester; if the requester has driven out of the coverage of the present RSU, the "RSU ID where the requester is located" in the result message is set to NULL (NULL), and then forwarded to the neighboring RSU (RSU directly connected to the present RSU cable).
As an optimization: the method is as follows.
Has the advantages that: the invention aims to ensure that any vehicle node in the vehicle networking can obtain and use the shared entertainment resource stored in another vehicle node in the network through the method. The entertainment resource sharing method is adopted, all sharable resources are supposed to be stored in vehicle nodes in the network, no shared data is stored in a management center or an RSU, and the invention is supposed that the data communication of the nodes in the network can be reliably realized, namely the method does not relate to the routing selection among the nodes and the bottom layer physical communication method.
Drawings
FIG. 1 is a schematic diagram of the Internet of vehicles architecture of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below so that those skilled in the art can better understand the advantages and features of the present invention, and thus the scope of the present invention will be more clearly defined. The embodiments described herein are only a few embodiments of the present invention, rather than all embodiments, and all other embodiments that can be derived by one of ordinary skill in the art without inventive faculty based on the embodiments described herein are intended to fall within the scope of the present invention.
Examples
1. The architecture of the present invention is as follows:
the car networking architecture used by the present invention is shown in fig. 1. The main entity objects involved in the architecture are: a management center, RSU (Road Side Unit), vehicle node. The entertainment resources available for sharing within the network may also be considered one entity. The RSU is a Road Side Unit, particularly a roadside fixed facility, is used as a wireless access point for accessing a vehicle node into a data cloud in an Internet of vehicles or a vehicle-mounted cloud, is mainly used for data forwarding between the vehicle node and a cloud center, and can also bear other specified light functions.
1 entertainment resource and its number.
In order to protect intellectual property, each entertainment resource that can be used for sharing is self-numbered. The number is set by the copyright owner of the resource. The resource number format is: copyright person number-resource type number-number. Since different copyright owners have different copyright owner numbers, the copyright owners can ensure that the resource numbers are not repeated when the copyright owners number the owned resources. Therefore, the resource number given in the format is unique in the whole network. In order to prevent the resource number from being forged, when the copyright owner releases the sharable entertainment resource, the resource number is encrypted by using a private key of the copyright owner, and the copyright number and the encrypted ciphertext are arranged in the sharable resource. When verifying, the verifier needs to use the public key of the copyright owner to decrypt the resource number and confirm the resource number. Entertainment resources that cannot be numbered are not shared. For simplicity of description, this step is omitted below, and the encrypted resource number is directly replaced with the resource number.
2 management center.
The management center is provided with a network-wide sharable entertainment resource list which is updated in real time. The suggested format for each record in the list is as follows:
| entertainment resource number (Main key) | Resource name | RSU 1 ID | ...... | RSU n ID |
RSU in recording i Indicates that the entertainment resource corresponding to the recorded entertainment resource number is in the RSU i Vehicle nodes within a coverage area. An entertainment resource may have copies on multiple vehicle nodes, so an entertainment resource record may correspond to multiple RSUs. As vehicle nodes with the specified entertainment resources move into and out of the coverage of a RSU, the corresponding RSU entry in the record is added and deleted.
3RSU(Road Side Unit)
The RSUs may communicate wirelessly with vehicle nodes traveling within their covered road segments, assuming that data communication is possible between the RSUs in a wired manner. The RSU is responsible for several tasks, including: (1) periodically broadcasting heartbeat messages of the vehicle, and receiving the registration of the vehicle nodes for entering and leaving; (2) relaying data communication between the vehicle node and the management center, the vehicle node and other RSUs; (3) responding to the resource request of the vehicle node.
4 vehicle node
The vehicle node runs in the road, continuously enters the coverage range of one RSU, and exits the coverage range of the previous RSU, and only can belong to one RSU at one time. Vehicle nodes are providers of entertainment resources and are also requestors and consumers of resources.
2. The method of the invention has the following working procedures:
the entertainment resource sharing method provided by the invention assumes that all sharable resources are stored in vehicle nodes in the network, and no shared data is stored in the management center or the RSU. In addition, the invention assumes that the data communication of nodes in the network can be reliably realized, i.e. the method does not relate to the routing selection among the nodes and the bottom layer physical communication method.
1. The working process of the vehicle nodes in the method is as follows:
step 1.1, the vehicle node is started to drive on the road, and firstly, one of the discovered RSUs is selected as a registered RSU of the road section, and the registration work is completed.
Step 1.2 the vehicle node that completed the registration can apply for the use of sharable entertainment resources in the network.
Step 1.3 the vehicle node that completed the registration may respond to the resource user request and provide shared resources to it.
Step 1.4, when the vehicle node is about to drive out of the coverage area of the current registered RSU, namely, when the vehicle node is about to drive into the next road section, a new RSU is selected again, and the registration work is completed again; after the new registration is completed, the original registration RSU deletes the vehicle node registration information, including the sharable resource list provided by the node.
Step 1.5, the vehicle node finishes the driving, notifies the current registered RSU that the vehicle is about to be off-line before stopping and extinguishing, and finishes the relevant logout work by the current registered RSU.
2. The RSU workflow in the method is as follows:
step 2.1, the RSU broadcasts a heartbeat message periodically to inform all vehicle nodes driving in the coverage road section of the RSU of relevant information. The heartbeat message is broadcast, and the vehicle node receiving the heartbeat message does not forward the heartbeat message. The heartbeat message broadcasting period can be set to be not less than 10s by comprehensively considering the vehicle running speed and limiting the data volume transmitted by the network.
The heartbeat message suggested format is:
| RSU ID | road section ID |
And 2.2, the RSU receives a certain vehicle node registration message, adds a relevant record in the local record list and reports the relevant record to the management center.
And 2.3, the RSU receives a vehicle node driving-away message or a vehicle node stopping logout message, deletes relevant records in the local record list and reports the relevant records to the management center.
And 2.4, the RSU receives the resource request message of a certain vehicle node in the covered road section, searches the requested resource for the RSU and responds.
And 2.5, the RSU receives the resource storage position information from the neighbor RSU, if the requester ID in the information is registered in the RSU, the information is forwarded to the requester, and otherwise, the information is ignored.
Step 2.6 the RSU receives the resource data requested to be forwarded from the resource provider in its coverage area and forwards the data to the RSU indicated in the "RSU ID where requester is located".
Step 2.6, the RSU receives the resource data required to be forwarded by other RSUs, and forwards the resource data to the RSU which is not indicated by the RSU ID where the requester is located; it is the RSU indicated by "RSU ID of requester", and forwards this data to the requester.
3. The management center in the method has the following working procedures:
step 3.1, recording and updating the information of the shared entertainment resources in the whole network, wherein the format of the list record is as described above;
and 3.2, responding to the resource request forwarded by the RSU, searching the entertainment resource information list, and feeding back the query result to the requesting RSU.
In step 1.1, the vehicle node selects and registers the RSU, and the specific method is as follows:
step 1.1.1, the vehicle node receives heartbeat messages issued by a plurality of RSUs, and selects one RSU which is in front of the traveling direction of the vehicle node and has the strongest signal as a registered RSU of the vehicle node on the road section;
step 1.1.2 vehicle node issues available shared resource list of this node to this registered RSU, and the suggested format of list item is:
in step 1.2, the vehicle node applies for using the sharable resource in the network, and the specific method is as follows:
step 1.2.1, the vehicle node applies for checking the shared resources available in the road section to the registered RSU, and the road section has the interested resources and is to be used, and the step 1.2.3 is switched to;
step 1.2.2 the vehicle node does not find that the road section has the resources to be interested, and can directly send the names of the interested resources to the RSU to request to inquire in the whole network instead. If the query result is yes, the resource is used across RSUs, and the step 1.2.3 is switched to; if the query result is none, the request is abandoned;
step 1.2.3 after the vehicle node obtains the relevant information of the requested resource, if the requested resource is in the current road section, the vehicle node issues a use request to the resource vehicle node, receives data and uses the data; if the requested resource is not in the current road section, the resource message is sent to the RSU of the current road section, and the RSU requests the resource vehicle node and forwards data instead;
step 1.2.4 if the vehicle node leaves the currently registered RSU before the end of the resource usage, the following options may be selected to execute:
(1) terminating the resource use, and executing the step 1.2.1 to search new sharable resources;
(2) and continuously using the resource, after finishing the registration of the new RSU, reporting the resource which is used by the RSU to the new registered RSU, carrying out data transfer instead of the new RSU, wherein the report resource use message format suggestion is as follows:
and simultaneously reporting the updated RSU ID to the resource provider, wherein the report message format suggestion is as follows:
in step 1.3, the vehicle node responds to the application and provides the sharable resource, and the specific method is as follows:
step 1.3.1, the resource requested by the requester exists in the node, and the step 1.3.2 is continuously executed, otherwise, the resource non-existence error prompt message is returned to the requester;
step 1.3.2 is to send the resource data applied by the requester to the requester, the resource data can be divided into several messages for transmission, and the head format suggestion of each message is:
if the sent message is the first message of the resource, a connection number needs to be created, and the connection number is unique in the whole network and remains unchanged in the subsequent messages for transmitting the resource. In order to ensure the uniqueness of the whole network, the proposed connection number format is as follows:
requester ID + supplier ID as the number of this connection
Wherein, the 'supplier is the number of the connection' adopts a self-increment method, and the number is increased by 1 every time a connection is newly built.
And 1.3.3, the node is about to leave the coverage range of the current RSU and enter the coverage range of the next RSU, and after the registration of a new RSU is finished, the ID of the RSU where the supplier is located is changed according to the message format given in the step 1.3.2, and then the resource data transmission is continued.
In step 2.4, the RSU responds to the vehicle node resource request within its coverage area, and the specific method is as follows:
step 2.4.1, searching a local resource list, wherein the requested resource exists in the coverage range of the RSU, and the resource storage position (resource supplier ID) is issued to the requester, and the issuing message format suggestion is as follows:
step 2.4.2, if the request resource is not in the local resource list, the request is forwarded to the management center, and after the returned result of the management center is received, if the requester is still in the coverage range of the RSU, the result is forwarded to the requester; if the requester has driven out of the coverage of the present RSU, the "RSU ID of the requester is" in the result message is set to NULL (NULL), and then forwarded to the neighboring RSU (RSU directly connected to the present RSU cable).
Claims (1)
1. A method for sharing urban road vehicle-to-vehicle network resources is characterized in that: the method comprises the following steps: step 1, vehicle node work flow:
step 1.1, a vehicle node is started to drive on the road, firstly, one of the discovered RSUs is selected as a registered RSU of the road section, and the registration work is completed; the RSU is a Road Side Unit, is a Road Side fixed facility, is used as a wireless access point for accessing a vehicle node into a data cloud in an Internet of vehicles or a vehicle-mounted cloud, and is used for forwarding data between the vehicle node and a cloud center;
step 1.2, the vehicle node which completes the registration work can apply for using the sharable entertainment resource in the network;
step 1.3, the vehicle node which completes the registration work can respond to the request of the resource user and provide the shared resource for the resource user;
step 1.4, when the vehicle node is about to drive out of the coverage area of the current registered RSU, namely, when the vehicle node is about to drive into the next road section, a new RSU is selected again, and the registration work is completed again; after the new registration is completed, the original registration RSU deletes the registration information of the vehicle node, including a sharable resource list provided by the node;
step 1.5, the vehicle node finishes the driving, notifies the current registered RSU that the RSU is about to be off-line before stopping and extinguishing, and finishes the relevant logout work by the current registered RSU;
step 2, RSU work flow:
step 2.1, the RSU periodically broadcasts heartbeat messages per se to inform all vehicle nodes driving in the coverage road section of the RSU of relevant information, the heartbeat messages are spread in a broadcasting mode, the vehicle nodes receiving the messages do not forward the heartbeat messages, the vehicle driving rate and the limitation of network transmission data volume are comprehensively considered, and the broadcasting period of the heartbeat messages can be set to be not less than 10s;
the format of the heartbeat message is as follows:
Step 2.2, the RSU receives a certain vehicle node registration message, adds a relevant record in a local record list and reports the relevant record to a management center;
step 2.3, the RSU receives a certain vehicle node driving-away message or a vehicle node stopping logout message, deletes relevant records in a local record list and reports the relevant records to a management center;
step 2.4, the RSU receives the resource request message of a certain vehicle node in the covered road section, searches the requested resource for the RSU and responds;
step 2.5, the RSU receives the resource storage position information from the neighbor RSU, if the ID of the requester in the information is registered in the RSU, the information is forwarded to the requester, otherwise, the information is ignored;
step 2.6, the RSU receives the resource data required to be forwarded by the resource supplier in the coverage area of the RSU, and forwards the data to the RSU indicated in the RSU ID of the requester;
step 2.6, the RSU receives the resource data required to be forwarded by other RSUs, and forwards the resource data to the RSU which is not indicated by the RSU ID where the requester is located; the RSU is indicated by 'RSU ID where the requester is located', and the RSU forwards the data to the requester;
step 3, management center work flow:
step 3.1, recording and updating the information of the entertainment resources which can be shared in the whole network;
step 3.2, responding to the resource request forwarded by the RSU, searching the entertainment resource information list, and feeding back the query result to the requesting RSU;
in the vehicle node work flow, in step 1.1, the vehicle node selects to register the RSU, and the specific method is as follows:
step 1.1.1, the vehicle node receives heartbeat messages issued by a plurality of RSUs, and selects one RSU which is in front of the traveling direction of the vehicle node and has the strongest signal as a registered RSU of the vehicle node on the road section;
step 1.1.2 vehicle node issues available shared resource list of this node to this registered RSU, and the suggested format of list item is:
In the vehicle node work flow, in step 1.2, the vehicle node applies for using the sharable resource in the network, and the specific method is as follows:
step 1.2.1, the vehicle node applies for checking the shared resources available in the road section to the registered RSU, and the road section has the interested resources and is to be used, and the step 1.2.3 is switched to;
step 1.2.2, the vehicle node does not find that the road section has the resources to be interested, the name of the interested resources can be directly sent to the RSU, the query is requested to be carried out in the whole network, if the query result is yes, the resources are used across the RSU, and the step 1.2.3 is turned to; if the query result is no, giving up the request;
step 1.2.3 after the vehicle node obtains the relevant information of the requested resource, if the requested resource is in the current road section, the vehicle node issues a use request to the resource vehicle node, receives data and uses the data; if the requested resource is not in the current road section, the resource message is sent to the RSU of the current road section, and the RSU requests the resource vehicle node and forwards data instead;
step 1.2.4 if the vehicle node leaves the currently registered RSU before the end of the resource usage, the following options may be selected to execute:
(1) terminating the resource use, and executing the step 1.2.1 to search new sharable resources;
(2) and continuing to use the resource, after finishing the registration of the new RSU, reporting the resource which is being used by the RSU to the new registered RSU, and performing data transfer instead of the new RSU, wherein the report resource use message format is as follows:
and simultaneously reporting the updated RSU ID to the resource provider, wherein the report message format is as follows:
in the vehicle node work flow, in step 1.3, the vehicle node responds to the application and provides the sharable resource, and the specific method is as follows:
step 1.3.1, the resource requested by the requester exists in the node, and the step 1.3.2 is continuously executed, otherwise, the resource non-existence error prompt message is returned to the requester;
step 1.3.2, the resource data applied by the requester is sent to the requester, the resource data can be divided into a plurality of messages for transmission, and the header format of each message is as follows:
if the sent message is the first message of the resource, a connection number needs to be created, the connection number is unique in the whole network, and the connection number is kept unchanged in the subsequent messages for transmitting the resource; in order to ensure the uniqueness of the whole network, the format of the connection number is as follows:
requester ID + supplier is the number of this connection;
wherein, the 'supplier is the number of the connection' adopts a self-increment method, and the number is increased by 1 when a new connection is built;
step 1.3.3 this node will leave the coverage of the current RSU, and enter the coverage of the next RSU, after finishing the registration of the new RSU, according to the message format given in step 1.3.2, after changing the RSU ID of the supplier, continue the resource data transmission;
in the RSU workflow, in step 2.4, the RSU responds to the resource request of the vehicle node within its coverage area, and the specific method is as follows:
step 2.4.1, searching a local resource list, wherein the requested resource exists in the coverage range of the RSU, and the resource storage position is released to the requester, and the release message format is as follows:
step 2.4.2, if the request resource is not in the local resource list, the request is forwarded to the management center, and after the returned result of the management center is received, if the requester is still in the coverage range of the RSU, the result is forwarded to the requester; if the requester leaves the coverage of the RSU, the result message 'RSU ID where the requester is located' is set to be null, and then the result message is forwarded to the adjacent RSU.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910855976.XA CN110933643B (en) | 2019-09-11 | 2019-09-11 | Method for sharing urban road vehicle-to-vehicle network resources |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910855976.XA CN110933643B (en) | 2019-09-11 | 2019-09-11 | Method for sharing urban road vehicle-to-vehicle network resources |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110933643A CN110933643A (en) | 2020-03-27 |
| CN110933643B true CN110933643B (en) | 2023-03-14 |
Family
ID=69848762
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910855976.XA Active CN110933643B (en) | 2019-09-11 | 2019-09-11 | Method for sharing urban road vehicle-to-vehicle network resources |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110933643B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114124979A (en) * | 2020-08-10 | 2022-03-01 | 中国移动通信有限公司研究院 | Method and device for resource sharing between nodes and nodes |
| CN112231721B (en) * | 2020-09-23 | 2022-11-08 | 南京邮电大学 | Context-aware trusted security sharing method and system for WoT resources |
| CN115426614A (en) * | 2021-05-31 | 2022-12-02 | 索尼集团公司 | Electronic device, method and storage medium for communication system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104767798A (en) * | 2015-03-18 | 2015-07-08 | 广东工业大学 | Car networking car state inspection method based on MP2P |
| WO2017041521A1 (en) * | 2015-09-07 | 2017-03-16 | 中兴通讯股份有限公司 | Internet of vehicle communication method and device |
| CN108848062A (en) * | 2018-05-23 | 2018-11-20 | 华东师范大学 | The data safety sharing method of controllable anonymity in vehicle-mounted net based on block chain |
-
2019
- 2019-09-11 CN CN201910855976.XA patent/CN110933643B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104767798A (en) * | 2015-03-18 | 2015-07-08 | 广东工业大学 | Car networking car state inspection method based on MP2P |
| WO2017041521A1 (en) * | 2015-09-07 | 2017-03-16 | 中兴通讯股份有限公司 | Internet of vehicle communication method and device |
| CN108848062A (en) * | 2018-05-23 | 2018-11-20 | 华东师范大学 | The data safety sharing method of controllable anonymity in vehicle-mounted net based on block chain |
Non-Patent Citations (1)
| Title |
|---|
| 车联网中一种有效的资源共享方法;邓左祥等;《计算机应用研究》;20180408(第06期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110933643A (en) | 2020-03-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110933643B (en) | Method for sharing urban road vehicle-to-vehicle network resources | |
| Zhao et al. | VADD: Vehicle-assisted data delivery in vehicular ad hoc networks | |
| Liu et al. | The sharing at roadside: Vehicular content distribution using parked vehicles | |
| CN105723753A (en) | Information interaction method between on-board terminals, and on-board terminal | |
| CN106603658B (en) | Internet of vehicles data transmission method and device based on software defined network | |
| KR101209197B1 (en) | Vehicle group management method and vehicle group registration method for providing vehicle location service | |
| CN109788515A (en) | A kind of data collaborative method, MEC equipment and server | |
| WO2018010083A1 (en) | Vehicle external communication method, device and terminal | |
| US20200327806A1 (en) | Connected vehicle platform assisted v2x communications | |
| CN109600715B (en) | Internet of vehicles V2X communication auxiliary file downloading method | |
| CN107274713A (en) | A kind of parking induction method based on cluster | |
| Mershad et al. | Crown: Discovering and consuming services in vehicular clouds | |
| CN110264758B (en) | Vehicle information processing and interaction method and system based on micro cloud | |
| Wongdeethai et al. | Collecting road traffic information using vehicular ad hoc networks | |
| Chua et al. | Delivering of live video streaming for vehicular communication using peer-to-peer approach | |
| CN108882150B (en) | Information center vehicle-mounted network routing method based on clustering and encounter sensing | |
| CN113114735B (en) | Data forwarding method and device for intersection in urban social networking service | |
| Morales et al. | An adaptable destination-based dissemination algorithm using a publish/subscribe model in vehicular networks | |
| Vaghela et al. | Vehicular parking space discovery with agent approach | |
| Cao et al. | ETCS: An efficient traffic congestion scheduling scheme combined with edge computing | |
| Allani et al. | Towards a smarter directional data aggregation in VANETs | |
| CN109285386A (en) | A kind of city vehicle-mounted net network data transmission mechanism towards intelligent transportation | |
| CN106304237B (en) | Terminal vehicle communication method based on wireless protocol | |
| CN113810851B (en) | Vehicle track privacy protection method for Internet of vehicles | |
| EP1919164B1 (en) | Method for collecting data in a requestor vehicle from other vehicles in a network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |