CN107508891B - Data transmission implementation method based on intelligent Internet of vehicles - Google Patents

Data transmission implementation method based on intelligent Internet of vehicles Download PDF

Info

Publication number
CN107508891B
CN107508891B CN201710750763.1A CN201710750763A CN107508891B CN 107508891 B CN107508891 B CN 107508891B CN 201710750763 A CN201710750763 A CN 201710750763A CN 107508891 B CN107508891 B CN 107508891B
Authority
CN
China
Prior art keywords
vehicle
subtask
address
task
data server
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
CN201710750763.1A
Other languages
Chinese (zh)
Other versions
CN107508891A (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 CN201710750763.1A priority Critical patent/CN107508891B/en
Publication of CN107508891A publication Critical patent/CN107508891A/en
Application granted granted Critical
Publication of CN107508891B publication Critical patent/CN107508891B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/604—Address structures or formats

Landscapes

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

Abstract

The invention discloses a data transmission implementation method based on an intelligent Internet of vehicles, wherein the Internet of vehicles comprises access nodes, data servers, vehicle nodes and the access nodes in the Internet of vehicles, the data servers and the vehicle nodes are located in a closed area, the number of the access nodes is equal to that of the data servers, and one data server and one access node are integrated together. The Internet of vehicles can rapidly acquire network services, shorten data communication delay, reduce data packet loss rate and improve service quality by the implementation method provided by the invention.

Description

Data transmission implementation method based on intelligent Internet of vehicles
Technical Field
The invention relates to an implementation method, in particular to a data transmission implementation method based on intelligent internet of vehicles.
Background
The internet of vehicles is used as a novel vehicle communication network, and multi-hop wireless communication between vehicles and roadside infrastructures can be achieved. With the continuous development of the car networking technology and the continuous emergence of various new applications, the car networking is urgently required to be capable of accessing the internet to meet the application requirements of users which are increased sharply.
The Internet of vehicles, as a special type of mobile ad hoc network, has the characteristics of high moving speed, large number of nodes, large coverage area and the like. The internet based on the IPv6 (hereinafter referred to as an IPv6 network) has the advantages of mobility support, rich address resources, strong extensibility, and the like. Therefore, the internet of vehicles accessing the IPv6 network becomes an ideal solution for meeting the requirements of user applications.
The current researchers have proposed a mode for obtaining network services by accessing the internet based on IPv6 in the internet of vehicles and defined a corresponding protocol stack, but the existing access method has some limitations because the architecture of the internet of vehicles is not compatible with the IPv6 network. Therefore, a data transmission implementation method for the internet of vehicles is needed, so that the data loss rate is reduced, and the service quality is improved.
Disclosure of Invention
The purpose of the invention is as follows: the invention aims to solve the technical problem of the prior art and provides a data transmission implementation method based on intelligent internet of vehicles.
The technical scheme is as follows: the invention discloses a data transmission implementation method based on an intelligent Internet of vehicles, wherein the Internet of vehicles comprises access nodes, data servers, vehicle nodes and the access nodes in the Internet of vehicles, the data servers and the vehicle nodes are positioned in a closed area such as a parking lot, the number of the access nodes is equal to that of the data servers, and one data server is integrated with one access node; all vehicle nodes in one vehicle internet form a vehicle-mounted cloud, the vehicle nodes are called cloud members, the vehicle nodes and access nodes in the vehicle internet can reach in a single hop or multiple hops, and the vehicle nodes are connected to the internet through the access nodes in the vehicle internet; an access node in the Internet of vehicles is uniquely identified by the geographic coordinates of the access node;
the user equipment is used as an internet node, and cloud members in a vehicle-mounted cloud jointly complete a task through shared resources, such as data collection;
the access node, the data server or the vehicle node realizes data communication through a unicast address, and the access node and the data server share the same unicast address; the unicast address of the data server is composed of a routing prefix and a link address, the link address of the data server comprises an address type part and a geographic coordinate part, the address type value of the unicast address of the data server is 1, the geographic coordinate value is the geographic coordinate of an access node integrated with the data server, the routing prefix is the routing prefix of the vehicle networking where the data server is located, and the routing prefix is preset, for example, 3ef8:1:1: 1; the unicast address of the vehicle node is composed of a routing prefix and a link address, the link address comprises an address type and a license plate number, the address type value of the unicast address of the vehicle node is 0, and the license plate number is the license plate number of the vehicle node;
in a vehicle networking, a data server maintains a vehicle cloud table, and each vehicle cloud table item comprises a link address domain, a state domain and a life cycle domain; one task is uniquely identified by one task ID, one task comprises more than two subtasks, and each subtask is uniquely identified by a subtask ID; the state domain of one vehicle-mounted cloud table entry comprises two states, namely an idle state or a busy state; one vehicle node can only execute one subtask at the same time; setting to a busy state if one vehicle node is executing one subtask, and setting to an idle state if one vehicle node is not executing any subtask;
a vehicle node in a vehicle networking regularly sends a beacon message, the source address of the beacon message is the unicast address of the beacon message, the routing prefix in the unicast address of the vehicle node is 0, and the load of the beacon message is the current state value and a random number; after receiving the beacon message of the vehicle node, the access node in the Internet of vehicles executes the following operations:
step 101: starting;
step 102: the access node checks whether a vehicle cloud table entry with a link address domain value equal to the link address of the source address of the received beacon message exists in the vehicle cloud table, if so, the step 103 is executed, otherwise, the step 104 is executed;
step 103: the access node sets the state domain value of the vehicle-mounted cloud table entry to the state value in the received beacon message load, sets the lifecycle of the vehicle-mounted cloud table entry to the maximum lifecycle value, for example, 1s, and executes step 105;
step 104: the access node creates a vehicle-mounted cloud table entry, the link address domain value of the vehicle-mounted cloud table entry is equal to the link address of the source address of the received beacon message, the state domain value is equal to the state value in the load of the received beacon message, and the life cycle domain value is set as the maximum life cycle value;
step 105: finishing;
a data server maintains a task table for each executed task, the table name of the task table is the task ID of the task, and each task table item comprises a link address field and a subtask ID field;
if an access node detects that the life cycle decay of an on-board cloud table entry E1 is 0, the following operations are performed:
step 201: starting;
step 202: the access node checks whether a task table item with a link address equal to that of the vehicle-mounted cloud table item E1 exists in the task table, if yes, step 203 is executed, and if not, step 204 is executed;
step 203: the access node deletes the task table entry with the link address equal to that of the vehicle-mounted cloud table entry E1;
step 204: the access node deletes the vehicle-mounted cloud table entry E1;
step 205: and (6) ending.
The above procedure can ensure that the user equipment acquires the data.
In the method, a task ID of a task T1 is TID1 and consists of M subtasks, wherein M is an integer greater than 0, one subtask runs on N vehicle nodes, N is an integer greater than 0, and the value of N is preset; the data server S1 is located in the vehicle networking VT1 and integrated with the access node AP1, and the vehicle nodes located in the vehicle networking VT1 form a vehicle cloud VC 1; if the internet user equipment U1 needs the data server S1 to execute a task T1, sending a task request message to the data server S1, wherein the source address of the task request message is the IPv6 address of the internet user equipment U1, the destination address is the unicast address of the data server S1, and the load is a task ID TID1, wherein the routing prefix of the unicast address of the data server S1 is the routing prefix of the internet VT1, and the geographic coordinate is the geographic coordinate of the access node AP 1; after receiving the task request message sent by the user equipment U1, the data server S1 checks the vehicle-mounted cloud table, and if the number of vehicle-mounted cloud table entries in the vehicle-mounted cloud table whose state domain values are in the idle state is not less than mxn, that is, is greater than or equal to mxn, the data server S1 executes the task T1 according to the following process:
step 301: starting;
step 302: the data server S1 creates a task table with the table name TID 1;
step 303: for each subtask ST of task T1, the data server S1 performs the following operations: selecting N vehicle-mounted cloud table entries with state domain values in an idle state from a vehicle-mounted cloud table, creating a unicast address by the data server S1 for each vehicle-mounted cloud table entry of the N vehicle-mounted cloud table entries, wherein a routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table entry, sending a subtask request message, the source address of the task request message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID of a subtask ST, the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to be in a busy state, creating a task table entry, the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, and the subtask ID is the subtask ID of the subtask ST;
step 304: after receiving the subtask request message, the destination vehicle node in the vehicle-mounted cloud VC1 executes step 313 if it leaves the vehicle-mounted cloud VC1 before completing the subtask identified by the subtask ID of the message, otherwise executes step 305;
step 305: the destination vehicle node returns a subtask response message, the source address of the subtask response message is the destination address of the received subtask request message, the destination address of the subtask response message is the source address of the received subtask request message, the load is the subtask ID and subtask execution result data in the received subtask request message, and then the destination vehicle sets the state value of the destination vehicle to be in an idle state;
step 306: after receiving the subtask response message, the data server S1 saves the execution result data in the subtask response message, and then performs the following operations: deleting the task table entry of the link address with the domain value equal to the source address of the received subtask response message, selecting the task table entry of which the domain value of the subtask ID is equal to the subtask ID in the load of the received subtask response message, and executing the following operations on each selected task table entry: the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the task table entry, a subtask cancellation message is sent, the source address of the task cancellation message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID field value of the task table entry, the data server S1 selects the vehicle-mounted cloud table entry of which the link address field value is equal to the link address field value of the task table entry, the state of the vehicle-mounted cloud table entry is set to be in an idle state, and the task table entry is deleted;
step 307: after receiving the subtask cancellation message, the destination vehicle node stops the currently executed subtask and sets the state value of the destination vehicle node to be an idle state;
step 308: the data server S1 checks the task table with the table name TID1, if the number N1 of the task table items with the subtask ID of STID1 is detected to be less than N, the step 309 is executed, otherwise, the step 311 is executed;
step 309: the data server S1 judges whether the number of task table items with state domain values in idle states in the task table is more than or equal to (N-N1), if yes, step 310 is executed, otherwise step 315 is executed;
step 310: the data server S1 selects (N-N1) vehicle-mounted cloud table items with state domain values in idle states from the vehicle-mounted cloud table; for each vehicle-mounted cloud table entry in the selected (N-N1) vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the vehicle-mounted cloud table entry, and sends a subtask request message, the source address of the task request message is the unicast address of the data server S1, the destination address is the created unicast address, and the load is the subtask ID STID 1; the data server S1 sets the status field value of the vehicle cloud table entry to be busy, creates a task table entry, the link address of the task table entry is the link address field value of the vehicle cloud table entry, the subtask ID is the subtask ID STID1, and executes step 304;
step 311: the data server S1 determines whether M subtask execution result data are received, if yes, step 312 is executed, otherwise step 304 is executed;
step 312: the data server S1 returns a task response message, where the source address of the task response message is the destination address of the received task request message, the destination address is the source address of the received task request message, the execution result data of M subtasks loaded with task T1 deletes the task table with table name TID1, and step 314 is executed;
step 313: the vehicle node leaving the vehicle cloud VC1 abandons the executed subtask, and step 315 is executed;
step 314: after receiving the task response message, the user equipment U1 stores the execution result data in the task response message;
step 315: and (6) ending.
The user can quickly and correctly acquire data through the process, so that the service quality is improved.
In the method of the invention, if the data server S1 detects that M1 subtasks are still not executed after executing steps 301-315 and M1 is an integer smaller than M and larger than 0, the value of N is increased by e, and e is an integer larger than 1; if the number of the vehicle-mounted cloud table entries with the state domain values in the idle states in the vehicle-mounted cloud table of the data server S1 is much larger than M1 × N, the data server S1 obtains the execution result of M1 subtasks according to the following process:
step 401: starting;
step 402: for each of the M1 subtasks ST1, the data server S1 performs the following operations: selecting N vehicle-mounted cloud table items with state domain values in an idle state from a vehicle-mounted cloud table, creating a unicast address by a data server S1 for each vehicle-mounted cloud table item in the N selected vehicle-mounted cloud table items, wherein the routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table item, sending a subtask request message, the source address of the subtask request message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID of a subtask ST1, the data server S1 sets the state domain value of the vehicle-mounted cloud table item to be in a busy state, and creating a task table item, the link address of the task table item is the link address domain value of the vehicle-mounted cloud table item, and the subtask ID is the subtask ID of the subtask ST 1;
step 403: after receiving the subtask request message, the destination vehicle node in the vehicle-mounted cloud VC1 executes step 411 if it leaves the vehicle-mounted cloud VC1 before completing the subtask identified by the subtask ID of the message, otherwise executes step 404;
step 404: the destination vehicle node returns a subtask response message, the source address of the subtask response message is the destination address of the received subtask request message, the destination address of the subtask response message is the source address of the received subtask request message, the load is the subtask ID and subtask execution result data in the received subtask request message, and then the state value of the destination vehicle node is set to be in an idle state;
step 405: after receiving the subtask response message, the data server S1 saves the execution result data in the subtask response message, and then performs the following operations: deleting the task table entry of the link address with the domain value equal to the source address of the received subtask response message, selecting the task table entry of the subtask ID with the domain value equal to the subtask ID loaded by the received subtask response message, and executing the following operations on each selected task table entry: the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the task table item, a subtask cancellation message is sent, the source address of the subtask cancellation message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID field value of the task table item, the data server S1 selects the vehicle-mounted cloud table item of which the link address field value is equal to the link address field value of the task table item, the state of the vehicle-mounted cloud table item is set to be in an idle state, and the task table item is deleted;
step 406: after receiving the subtask cancellation message, the destination vehicle node stops the currently executed subtask and sets the state value of the destination vehicle node to be an idle state;
step 407: the data server S1 looks at the task table with table name TID1, if it detects that the number N2 of task table entries with subtask ID2 is less than N, it executes step 408, otherwise, executes step 409;
step 408: the data server S1 selects (N-N2) vehicle-mounted cloud table entries with state domain values in an idle state from the vehicle-mounted cloud table, for each vehicle-mounted cloud table entry in the selected (N-N2) vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table entry, a subtask request message is sent, the source address of the message is the unicast address of the data server S1, the destination address is the created unicast address, the load is a subtask ID STID2, the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to be in a busy state, a task table entry is created, the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, the subtask ID is the subtask ID STID2, and the step 403 is executed;
step 409: the data server S1 determines whether the execution result data of the M1 subtasks is received, if yes, step 410 is executed, otherwise step 403 is executed;
step 410: the data server S1 returns a task response message, where the source address of the task response message is the destination address of the received task request message, the destination address is the source address of the received task request message, the execution result data of M1 subtasks loaded with task T1 deletes the task table with the table name TID1, and performs step 412;
step 411: the vehicle node leaving the vehicle cloud VC1 abandons the executed subtask, and step 413 is executed;
step 412: after receiving the task response message, the user equipment U1 stores the execution result data in the task response message;
step 413: and (6) ending.
The user can quickly and correctly acquire data through the process, so that the service quality is improved.
In the method, the task ID of the task T2 is TID2 and consists of M2 subtasks, and M2 is an integer larger than 0; the subtasks run in N vehicle nodes, wherein N is an integer larger than 0, the value of N is preset, a data server S1 is located in an Internet of vehicles VT1 and integrated with an access node AP1, and under the condition that vehicle nodes located in the Internet of vehicles VT1 form an Internet of vehicles VC1, if an Internet user equipment U1 needs a data server S1 to execute a task T2, a task request message is sent to the data server S1, the source address of the task request message is the IPv6 address of the user, the destination address is the unicast address of the data server S1, and the load is a task ID TID2, wherein the routing prefix of the unicast address of the data server S1 is the routing prefix of the Internet of the VT1, and the geographic coordinate is the geographic coordinate of the access node AP 1; after receiving the task request message sent by the user equipment U1, the data server S1 checks the vehicle-mounted cloud table, and if the number of vehicle-mounted cloud table entries with the state domain value in the idle state in the vehicle-mounted cloud table is less than M2 × N, the data server S1 selects the parameter x meeting the condition 1, and then executes the task T2 according to the following process:
condition 1: the number of the vehicle-mounted cloud table items with the state domain values in the idle states in the vehicle-mounted cloud table is more than M2/x multiplied by N;
step 501: starting;
step 502: the data server S1 creates a task table, the table name of the task table is TID2, the subtask IDs of M2 subtasks are divided into x subtask groups, and no repeated subtask ID exists in any two subtask groups; the data server S1 sets the value of parameter g to 0;
step 503: the data server S1 increments the value of the parameter g by 1, if the value of the parameter g is greater than the value of the parameter x, then step 512 is executed, otherwise step 504 is executed;
step 504: for each subtask ID STID3 in the g-th subtask group, the data server S1 performs the following operations: selecting N vehicle-mounted cloud table items with state domain values in idle states from the vehicle-mounted cloud table; for each vehicle-mounted cloud table entry in the selected N vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the vehicle-mounted cloud table entry, and sends a subtask request message, the source address of the subtask request message is the unicast address of the data server S1, the destination address is the created unicast address, and the load is the subtask id 3; the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to be in a busy state, and creates a task table entry, wherein the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, and the subtask ID is the subtask ID STID 3;
step 505: after receiving the subtask request message, the destination vehicle node in the vehicle-mounted cloud VC1 executes step 513 if it leaves the vehicle-mounted cloud VC1 before completing the subtask identified by the subtask ID of the message, otherwise executes step 506;
step 506: the destination vehicle node returns a subtask response message, the source address of the subtask response message is the destination address of the received subtask request message, the destination address of the subtask response message is the source address of the received subtask request message, the load is the subtask ID and subtask execution result data in the received subtask request message, and then the state value of the destination vehicle node is set to be in an idle state;
step 507: after receiving the subtask response message, the data server S1 saves the execution result data in the subtask response message, and then performs the following operations: deleting the task table entry of the link address with the domain value equal to the source address of the received subtask response message, selecting the task table entry of which the domain value of the subtask ID is equal to the subtask ID in the load of the received subtask response message, and executing the following operations on each selected task table entry: the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the task table item, a subtask cancellation message is sent, the source address of the subtask cancellation message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID field value of the task table item, the data server S1 selects the vehicle-mounted cloud table item of which the link address field value is equal to the link address field value of the task table item, the state of the vehicle-mounted cloud table item is set to be in an idle state, and the task table item is deleted;
step 508: after receiving the subtask cancellation message, the destination vehicle node stops the currently executed subtask and sets the state value of the destination vehicle node to be an idle state;
step 509: the data server S1 looks at the task table with table name TID2, if it detects that the number N4 of task table entries with subtask ID4 is less than N, it executes step 510, otherwise, executes step 511;
step 510: the data server S1 selects (N-N4) vehicle-mounted cloud table entries with state domain values in an idle state from the vehicle-mounted cloud table, for each vehicle-mounted cloud table entry in the selected (N-N4) vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table entry, a subtask request message is sent, the source address of the subtask request message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID STID4, the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to a busy state, creates a task table entry, the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, the subtask ID is the subtask ID STID4, and executes step 505;
step 511: the data server S1 determines whether the execution result data of all subtasks in the g-th subtask group is received, if yes, step 503 is executed, otherwise step 505 is executed;
step 512: the data server S1 returns a task response message, where the source address of the task response message is the destination address of the received task request message, the destination address is the source address of the received task request message, the execution result data of M2 subtasks loaded with task T2 deletes the task table with the table name TID2, and step 514 is executed;
step 513: the vehicle node leaving the vehicle cloud VC1 abandons the executed subtask, and step 515 is executed;
step 514: after receiving the task response message, the user equipment U1 stores the execution result data in the task response message;
step 515: and (6) ending.
Through the process, the user can quickly and correctly make the vehicle nodes execute the command, so that the intelligent vehicle networking is realized.
Has the advantages that: the invention provides a data transmission implementation method based on an intelligent Internet of vehicles, which can rapidly acquire network services, shorten data communication delay, reduce data packet loss rate and improve service quality.
Drawings
The foregoing and/or other advantages of the invention will become further apparent from the following detailed description of the invention when taken in conjunction with the accompanying drawings.
Fig. 1 is a schematic diagram illustrating a process of creating a vehicle-mounted cloud entry according to the present invention.
Fig. 2 is a schematic diagram illustrating a process of deleting a vehicle-mounted cloud entry according to the present invention.
Fig. 3 is a schematic diagram illustrating a task execution flow according to the present invention.
FIG. 4 is a flowchart illustrating the execution of subtasks according to the present invention.
Fig. 5 is a schematic diagram of a task execution flow of the data server according to the present invention.
The specific implementation mode is as follows:
the invention provides a data transmission implementation method based on an intelligent Internet of vehicles, which can rapidly acquire network services, shorten data communication delay, reduce data packet loss rate and improve service quality.
Fig. 1 is a schematic diagram illustrating a process of creating a vehicle-mounted cloud entry according to the present invention. A vehicle node in a vehicle networking regularly sends a beacon message, the source address of the beacon message is the unicast address of the beacon message, the routing prefix in the unicast address of the vehicle node is 0, and the load of the beacon message is the current state value and a random number; after receiving the beacon message of the vehicle node, the access node in the Internet of vehicles executes the following operations:
step 101: starting;
step 102: the access node checks whether a vehicle cloud table entry with a link address domain value equal to the link address of the source address of the received beacon message exists in the vehicle cloud table, if so, the step 103 is executed, otherwise, the step 104 is executed;
step 103: the access node sets the state domain value of the vehicle-mounted cloud table entry to the state value in the received beacon message load, sets the life cycle of the vehicle-mounted cloud table entry to the maximum life cycle value, and executes step 105;
step 104: the access node creates a vehicle-mounted cloud table entry, the link address domain value of the vehicle-mounted cloud table entry is equal to the link address of the source address of the received beacon message, the state domain value is equal to the state value in the load of the received beacon message, and the life cycle domain value is set as the maximum life cycle value;
step 105: and (6) ending.
Fig. 2 is a schematic diagram illustrating a process of deleting a vehicle-mounted cloud entry according to the present invention. A data server maintains a task table for each executed task, the table name of the task table is the task ID of the task, and each task table item comprises a link address field and a subtask ID field;
if an access node detects that the life cycle decay of an on-board cloud table entry E1 is 0, the following operations are performed:
step 201: starting;
step 202: the access node checks whether a task table item with a link address equal to that of the vehicle-mounted cloud table item E1 exists in the task table, if yes, step 203 is executed, and if not, step 204 is executed;
step 203: the access node deletes the task table entry with the link address equal to that of the vehicle-mounted cloud table entry E1;
step 204: the access node deletes the vehicle-mounted cloud table entry E1;
step 205: and (6) ending.
Fig. 3 is a schematic diagram illustrating a task execution flow according to the present invention. The task ID at task T1 is TID1, which is composed of M subtasks, M being an integer greater than 0, one subtask running on N vehicle nodes, N being an integer greater than 0; the data server S1 is located in the vehicle networking VT1 and integrated with the access node AP1, and the vehicle nodes located in the vehicle networking VT1 form a vehicle cloud VC 1; if the internet user equipment U1 needs the data server S1 to execute a task T1, sending a task request message to the data server S1, wherein the source address of the task request message is the IPv6 address of the internet user equipment U1, the destination address is the unicast address of the data server S1, and the load is a task ID TID1, wherein the routing prefix of the unicast address of the data server S1 is the routing prefix of the internet VT1, and the geographic coordinate is the geographic coordinate of the access node AP 1; after receiving the task request message sent by the user equipment U1, the data server S1 checks the vehicle-mounted cloud table, and if the number of vehicle-mounted cloud table entries with the state domain value in the idle state in the vehicle-mounted cloud table is not less than mxn, the data server S1 executes the task T1 according to the following process:
step 301: starting;
step 302: the data server S1 creates a task table with the table name TID 1;
step 303: for each subtask ST of task T1, the data server S1 performs the following operations: selecting N vehicle-mounted cloud table entries with state domain values in an idle state from a vehicle-mounted cloud table, creating a unicast address by the data server S1 for each vehicle-mounted cloud table entry of the N vehicle-mounted cloud table entries, wherein a routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table entry, sending a subtask request message, the source address of the task request message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID of a subtask ST, the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to be in a busy state, creating a task table entry, the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, and the subtask ID is the subtask ID of the subtask ST;
step 304: after receiving the subtask request message, the destination vehicle node in the vehicle-mounted cloud VC1 executes step 313 if it leaves the vehicle-mounted cloud VC1 before completing the subtask identified by the subtask ID of the message, otherwise executes step 305;
step 305: the destination vehicle node returns a subtask response message, the source address of the subtask response message is the destination address of the received subtask request message, the destination address of the subtask response message is the source address of the received subtask request message, the load is the subtask ID and subtask execution result data in the received subtask request message, and then the destination vehicle sets the state value of the destination vehicle to be in an idle state;
step 306: after receiving the subtask response message, the data server S1 saves the execution result data in the subtask response message, and then performs the following operations: deleting the task table entry of the link address with the domain value equal to the source address of the received subtask response message, selecting the task table entry of which the domain value of the subtask ID is equal to the subtask ID in the load of the received subtask response message, and executing the following operations on each selected task table entry: the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the task table entry, a subtask cancellation message is sent, the source address of the task cancellation message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID field value of the task table entry, the data server S1 selects the vehicle-mounted cloud table entry of which the link address field value is equal to the link address field value of the task table entry, the state of the vehicle-mounted cloud table entry is set to be in an idle state, and the task table entry is deleted;
step 307: after receiving the subtask cancellation message, the destination vehicle node stops the currently executed subtask and sets the state value of the destination vehicle node to be an idle state;
step 308: the data server S1 checks the task table with the table name TID1, if the number N1 of the task table items with the subtask ID of STID1 is detected to be less than N, the step 309 is executed, otherwise, the step 311 is executed;
step 309: the data server S1 judges whether the number of task table items with state domain values in idle states in the task table is more than or equal to (N-N1), if yes, step 310 is executed, otherwise step 315 is executed;
step 310: the data server S1 selects (N-N1) vehicle-mounted cloud table items with state domain values in idle states from the vehicle-mounted cloud table; for each vehicle-mounted cloud table entry in the selected (N-N1) vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the vehicle-mounted cloud table entry, and sends a subtask request message, the source address of the task request message is the unicast address of the data server S1, the destination address is the created unicast address, and the load is the subtask ID STID 1; the data server S1 sets the status field value of the vehicle cloud table entry to be busy, creates a task table entry, the link address of the task table entry is the link address field value of the vehicle cloud table entry, the subtask ID is the subtask ID STID1, and executes step 304;
step 311: the data server S1 determines whether M subtask execution result data are received, if yes, step 312 is executed, otherwise step 304 is executed;
step 312: the data server S1 returns a task response message, where the source address of the task response message is the destination address of the received task request message, the destination address is the source address of the received task request message, the execution result data of M subtasks loaded with task T1 deletes the task table with table name TID1, and step 314 is executed;
step 313: the vehicle node leaving the vehicle cloud VC1 abandons the executed subtask, and step 315 is executed;
step 314: after receiving the task response message, the user equipment U1 stores the execution result data in the task response message;
step 315: and (6) ending.
FIG. 4 is a flowchart illustrating the execution of subtasks according to the present invention. If the data server S1 detects that M1 subtasks are still not executed after executing steps 301-315 and M1 is an integer smaller than M and larger than 0, incrementing the value of N by e, wherein e is an integer larger than 1; if the number of the vehicle-mounted cloud table entries with the state domain values in the idle states in the vehicle-mounted cloud table of the data server S1 is much larger than M1 × N, the data server S1 obtains the execution result of M1 subtasks according to the following process:
step 401: starting;
step 402: for each of the M1 subtasks ST1, the data server S1 performs the following operations: selecting N vehicle-mounted cloud table items with state domain values in an idle state from a vehicle-mounted cloud table, creating a unicast address by a data server S1 for each vehicle-mounted cloud table item in the N selected vehicle-mounted cloud table items, wherein the routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table item, sending a subtask request message, the source address of the subtask request message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID of a subtask ST1, the data server S1 sets the state domain value of the vehicle-mounted cloud table item to be in a busy state, and creating a task table item, the link address of the task table item is the link address domain value of the vehicle-mounted cloud table item, and the subtask ID is the subtask ID of the subtask ST 1;
step 403: after receiving the subtask request message, the destination vehicle node in the vehicle-mounted cloud VC1 executes step 411 if it leaves the vehicle-mounted cloud VC1 before completing the subtask identified by the subtask ID of the message, otherwise executes step 404;
step 404: the destination vehicle node returns a subtask response message, the source address of the subtask response message is the destination address of the received subtask request message, the destination address of the subtask response message is the source address of the received subtask request message, the load is the subtask ID and subtask execution result data in the received subtask request message, and then the state value of the destination vehicle node is set to be in an idle state;
step 405: after receiving the subtask response message, the data server S1 saves the execution result data in the subtask response message, and then performs the following operations: deleting the task table entry of the link address with the domain value equal to the source address of the received subtask response message, selecting the task table entry of the subtask ID with the domain value equal to the subtask ID loaded by the received subtask response message, and executing the following operations on each selected task table entry: the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the task table item, a subtask cancellation message is sent, the source address of the subtask cancellation message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID field value of the task table item, the data server S1 selects the vehicle-mounted cloud table item of which the link address field value is equal to the link address field value of the task table item, the state of the vehicle-mounted cloud table item is set to be in an idle state, and the task table item is deleted;
step 406: after receiving the subtask cancellation message, the destination vehicle node stops the currently executed subtask and sets the state value of the destination vehicle node to be an idle state;
step 407: the data server S1 looks at the task table with table name TID1, if it detects that the number N2 of task table entries with subtask ID2 is less than N, it executes step 408, otherwise, executes step 409;
step 408: the data server S1 selects (N-N2) vehicle-mounted cloud table entries with state domain values in an idle state from the vehicle-mounted cloud table, for each vehicle-mounted cloud table entry in the selected (N-N2) vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table entry, a subtask request message is sent, the source address of the message is the unicast address of the data server S1, the destination address is the created unicast address, the load is a subtask ID STID2, the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to be in a busy state, a task table entry is created, the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, the subtask ID is the subtask ID STID2, and the step 403 is executed;
step 409: the data server S1 determines whether the execution result data of the M1 subtasks is received, if yes, step 410 is executed, otherwise step 403 is executed;
step 410: the data server S1 returns a task response message, where the source address of the task response message is the destination address of the received task request message, the destination address is the source address of the received task request message, the execution result data of M1 subtasks loaded with task T1 deletes the task table with the table name TID1, and performs step 412;
step 411: the vehicle node leaving the vehicle cloud VC1 abandons the executed subtask, and step 413 is executed;
step 412: after receiving the task response message, the user equipment U1 stores the execution result data in the task response message;
step 413: and (6) ending.
Fig. 5 is a schematic diagram of a task execution flow of the data server according to the present invention. The task ID of the task T2 is TID2, and the task T2 is composed of M2 subtasks, and M2 is an integer greater than 0; one subtask runs in N vehicle nodes, wherein N is an integer greater than 0, the data server S1 is located in an Internet of vehicles VT1 and integrated with an access node AP1, and under the condition that the vehicle nodes located in the Internet of vehicles VT1 form an onboard cloud VC1, if an Internet user equipment U1 needs the data server S1 to execute a task T2, a task request message is sent to the data server S1, the source address of the task request message is the own IPv6 address, the destination address is the unicast TID address of the data server S1, and the load is a task ID2, wherein the routing prefix of the unicast address of the data server S1 is the routing prefix of the Internet of vehicles VT1, and the geographic coordinate is the geographic coordinate of the access node AP 1; after receiving the task request message sent by the user equipment U1, the data server S1 checks the vehicle-mounted cloud table, and if the number of vehicle-mounted cloud table entries with the state domain value in the idle state in the vehicle-mounted cloud table is less than M2 × N, the data server S1 selects the parameter x meeting the condition 1, and then executes the task T2 according to the following process:
condition 1: the number of the vehicle-mounted cloud table items with the state domain values in the idle states in the vehicle-mounted cloud table is more than M2/x multiplied by N;
step 501: starting;
step 502: the data server S1 creates a task table, the table name of the task table is TID2, the subtask IDs of M2 subtasks are divided into x subtask groups, and no repeated subtask ID exists in any two subtask groups; the data server S1 sets the value of parameter g to 0;
step 503: the data server S1 increments the value of the parameter g by 1, if the value of the parameter g is greater than the value of the parameter x, then step 512 is executed, otherwise step 504 is executed;
step 504: for each subtask ID STID3 in the g-th subtask group, the data server S1 performs the following operations: selecting N vehicle-mounted cloud table items with state domain values in idle states from the vehicle-mounted cloud table; for each vehicle-mounted cloud table entry in the selected N vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the vehicle-mounted cloud table entry, and sends a subtask request message, the source address of the subtask request message is the unicast address of the data server S1, the destination address is the created unicast address, and the load is the subtask id 3; the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to be in a busy state, and creates a task table entry, wherein the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, and the subtask ID is the subtask ID STID 3;
step 505: after receiving the subtask request message, the destination vehicle node in the vehicle-mounted cloud VC1 executes step 513 if it leaves the vehicle-mounted cloud VC1 before completing the subtask identified by the subtask ID of the message, otherwise executes step 506;
step 506: the destination vehicle node returns a subtask response message, the source address of the subtask response message is the destination address of the received subtask request message, the destination address of the subtask response message is the source address of the received subtask request message, the load is the subtask ID and subtask execution result data in the received subtask request message, and then the state value of the destination vehicle node is set to be in an idle state;
step 507: after receiving the subtask response message, the data server S1 saves the execution result data in the subtask response message, and then performs the following operations: deleting the task table entry of the link address with the domain value equal to the source address of the received subtask response message, selecting the task table entry of which the domain value of the subtask ID is equal to the subtask ID in the load of the received subtask response message, and executing the following operations on each selected task table entry: the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the task table item, a subtask cancellation message is sent, the source address of the subtask cancellation message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID field value of the task table item, the data server S1 selects the vehicle-mounted cloud table item of which the link address field value is equal to the link address field value of the task table item, the state of the vehicle-mounted cloud table item is set to be in an idle state, and the task table item is deleted;
step 508: after receiving the subtask cancellation message, the destination vehicle node stops the currently executed subtask and sets the state value of the destination vehicle node to be an idle state;
step 509: the data server S1 looks at the task table with table name TID2, if it detects that the number N4 of task table entries with subtask ID4 is less than N, it executes step 510, otherwise, executes step 511;
step 510: the data server S1 selects (N-N4) vehicle-mounted cloud table entries with state domain values in an idle state from the vehicle-mounted cloud table, for each vehicle-mounted cloud table entry in the selected (N-N4) vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table entry, a subtask request message is sent, the source address of the subtask request message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID STID4, the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to a busy state, creates a task table entry, the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, the subtask ID is the subtask ID STID4, and executes step 505;
step 511: the data server S1 determines whether the execution result data of all subtasks in the g-th subtask group is received, if yes, step 503 is executed, otherwise step 505 is executed;
step 512: the data server S1 returns a task response message, where the source address of the task response message is the destination address of the received task request message, the destination address is the source address of the received task request message, the execution result data of M2 subtasks loaded with task T2 deletes the task table with the table name TID2, and step 514 is executed;
step 513: the vehicle node leaving the vehicle cloud VC1 abandons the executed subtask, and step 515 is executed;
step 514: after receiving the task response message, the user equipment U1 stores the execution result data in the task response message;
step 515: and (6) ending.
The invention provides the idea of a data transmission implementation method of an intelligent internet of vehicles, and a number of methods and ways for implementing the technical scheme are provided, the above description is only a preferred embodiment of the invention, it should be noted that, for those skilled in the art, a number 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.
Example 1
Based on the simulation parameters in table 1, the present embodiment simulates the data transmission implementation method of the intelligent internet of vehicles, and the performance analysis is as follows: when the number of the vehicle nodes is increased, the success rate of the vehicle nodes for executing tasks is improved, and the delay is reduced. The average mobile handover delay of the vehicle is 95ms, and the average packet loss rate is 0.5%.
TABLE 1 simulation parameters
Figure BDA0001391085010000171

Claims (4)

1. A data transmission implementation method based on an intelligent Internet of vehicles is characterized in that the Internet of vehicles comprises access nodes, data servers, vehicle nodes and the access nodes in the Internet of vehicles, wherein the data servers and the vehicle nodes are located in a closed area, the number of the access nodes is equal to that of the data servers, and one data server is integrated with one access node; all vehicle nodes in one vehicle internet form a vehicle-mounted cloud, the vehicle nodes are called cloud members, the vehicle nodes and access nodes in the vehicle internet can reach in a single hop or multiple hops, and the vehicle nodes are connected to the internet through the access nodes in the vehicle internet; an access node in the Internet of vehicles is uniquely identified by the geographic coordinates of the access node;
the user equipment is used as an internet node, and cloud members in a vehicle-mounted cloud jointly complete a task by sharing resources;
the access node, the data server or the vehicle node realizes data communication through a unicast address, and the access node and the data server share the same unicast address; the unicast address of the data server is composed of a routing prefix and a link address, the link address of the data server comprises an address type part and a geographic coordinate part, the address type value of the unicast address of the data server is 1, the geographic coordinate value is the geographic coordinate of an access node integrated with the data server, the routing prefix is the routing prefix of the internet of vehicles where the data server is located, and the routing prefix is preset; the unicast address of the vehicle node is composed of a routing prefix and a link address, the link address comprises an address type and a license plate number, the address type value of the unicast address of the vehicle node is 0, and the license plate number is the license plate number of the vehicle node;
in a vehicle networking, a data server maintains a vehicle cloud table, and each vehicle cloud table item comprises a link address domain, a state domain and a life cycle domain; one task is uniquely identified by one task ID, one task comprises more than two subtasks, and each subtask is uniquely identified by a subtask ID; the state domain of one vehicle-mounted cloud table entry comprises two states, namely an idle state or a busy state; one vehicle node can only execute one subtask at the same time; setting to a busy state if one vehicle node is executing one subtask, and setting to an idle state if one vehicle node is not executing any subtask;
a vehicle node in a vehicle networking regularly sends a beacon message, the source address of the beacon message is the unicast address of the beacon message, the routing prefix in the unicast address of the vehicle node is 0, and the load of the beacon message is the current state value and a random number; after receiving the beacon message of the vehicle node, the access node in the Internet of vehicles executes the following operations:
step 101: starting;
step 102: the access node checks whether a vehicle cloud table entry with a link address domain value equal to the link address of the source address of the received beacon message exists in the vehicle cloud table, if so, the step 103 is executed, otherwise, the step 104 is executed;
step 103: the access node sets the state domain value of the vehicle-mounted cloud table entry to the state value in the received beacon message load, sets the life cycle of the vehicle-mounted cloud table entry to the maximum life cycle value, and executes step 105;
step 104: the access node creates a vehicle-mounted cloud table entry, the link address domain value of the vehicle-mounted cloud table entry is equal to the link address of the source address of the received beacon message, the state domain value is equal to the state value in the load of the received beacon message, and the life cycle domain value is set as the maximum life cycle value;
step 105: finishing;
a data server maintains a task table for each executed task, the table name of the task table is the task ID of the task, and each task table item comprises a link address field and a subtask ID field;
if an access node detects that the life cycle decay of an on-board cloud table entry E1 is 0, the following operations are performed:
step 201: starting;
step 202: the access node checks whether a task table item with a link address equal to that of the vehicle-mounted cloud table item E1 exists in the task table, if yes, step 203 is executed, and if not, step 204 is executed;
step 203: the access node deletes the task table entry with the link address equal to that of the vehicle-mounted cloud table entry E1;
step 204: the access node deletes the vehicle-mounted cloud table entry E1;
step 205: and (6) ending.
2. The method for realizing data transmission based on the intelligent Internet of vehicles as claimed in claim 1, wherein task ID of task T1 is TID1, which is composed of M subtasks, M is an integer greater than 0, one subtask runs on N vehicle nodes, and N is an integer greater than 0; the data server S1 is located in an internet of vehicles VT1 and integrated with an access node AP1, vehicle nodes located in the internet of vehicles VT1 form an on-vehicle cloud VC1, if an internet user device U1 needs the data server S1 to execute a task T1, a task request message is sent to the data server S1, the source address of the task request message is the IPv6 address of the internet user device U1, the destination address is the unicast address of the data server S1, and the load is a task ID TID1, wherein the routing prefix of the unicast address of the data server S1 is the routing prefix of the internet of vehicles VT1, and the geographic coordinates are the geographic coordinates of the access node AP 1; after receiving the task request message sent by the user equipment U1, the data server S1 checks the vehicle-mounted cloud table, and if the number of vehicle-mounted cloud table entries with the state domain value in the idle state in the vehicle-mounted cloud table is not less than mxn, the data server S1 executes the task T1 according to the following process:
step 301: starting;
step 302: the data server S1 creates a task table with the table name TID 1;
step 303: for each subtask ST of task T1, the data server S1 performs the following operations: selecting N vehicle-mounted cloud table entries with state domain values in an idle state from a vehicle-mounted cloud table, creating a unicast address by the data server S1 for each vehicle-mounted cloud table entry of the N vehicle-mounted cloud table entries, wherein a routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table entry, sending a subtask request message, the source address of the task request message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID of a subtask ST, the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to be in a busy state, creating a task table entry, the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, and the subtask ID is the subtask ID of the subtask ST;
step 304: after receiving the subtask request message, the destination vehicle node in the vehicle-mounted cloud VC1 executes step 313 if it leaves the vehicle-mounted cloud VC1 before completing the subtask identified by the subtask ID of the message, otherwise executes step 305;
step 305: the destination vehicle node returns a subtask response message, the source address of the subtask response message is the destination address of the received subtask request message, the destination address of the subtask response message is the source address of the received subtask request message, the load is the subtask ID and subtask execution result data in the received subtask request message, and then the destination vehicle sets the state value of the destination vehicle to be in an idle state;
step 306: after receiving the subtask response message, the data server S1 saves the execution result data in the subtask response message, and then performs the following operations: deleting the task table entry of the link address with the domain value equal to the source address of the received subtask response message, selecting the task table entry of which the domain value of the subtask ID is equal to the subtask ID in the load of the received subtask response message, and executing the following operations on each selected task table entry: the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the task table entry, a subtask cancellation message is sent, the source address of the task cancellation message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID field value of the task table entry, the data server S1 selects the vehicle-mounted cloud table entry of which the link address field value is equal to the link address field value of the task table entry, the state of the vehicle-mounted cloud table entry is set to be in an idle state, and the task table entry is deleted;
step 307: after receiving the subtask cancellation message, the destination vehicle node stops the currently executed subtask and sets the state value of the destination vehicle node to be an idle state;
step 308: the data server S1 checks the task table with the table name TID1, if the number N1 of the task table items with the subtask ID of STID1 is detected to be less than N, the step 309 is executed, otherwise, the step 311 is executed;
step 309: the data server S1 judges whether the number of task table items with state domain values in idle states in the task table is more than or equal to (N-N1), if yes, step 310 is executed, otherwise step 315 is executed;
step 310: the data server S1 selects (N-N1) vehicle-mounted cloud table items with state domain values in idle states from the vehicle-mounted cloud table; for each vehicle-mounted cloud table entry in the selected (N-N1) vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the vehicle-mounted cloud table entry, and sends a subtask request message, the source address of the task request message is the unicast address of the data server S1, the destination address is the created unicast address, and the load is the subtask ID STID 1; the data server S1 sets the status field value of the vehicle cloud table entry to be busy, creates a task table entry, the link address of the task table entry is the link address field value of the vehicle cloud table entry, the subtask ID is the subtask ID STID1, and executes step 304;
step 311: the data server S1 determines whether M subtask execution result data are received, if yes, step 312 is executed, otherwise step 304 is executed;
step 312: the data server S1 returns a task response message, where the source address of the task response message is the destination address of the received task request message, the destination address is the source address of the received task request message, the execution result data of M subtasks loaded with task T1 deletes the task table with table name TID1, and step 314 is executed;
step 313: the vehicle node leaving the vehicle cloud VC1 abandons the executed subtask, and step 315 is executed;
step 314: after receiving the task response message, the user equipment U1 stores the execution result data in the task response message;
step 315: and (6) ending.
3. The method for realizing the data transmission based on the intelligent Internet of vehicles according to claim 2, wherein if the data server S1 detects that M1 subtasks are not executed after the steps 301-315 are executed, and M1 is an integer smaller than M and larger than 0, the value of N is increased by e, wherein e is an integer larger than 1; if the number of the vehicle-mounted cloud table entries with the state domain values in the idle states in the vehicle-mounted cloud table of the data server S1 is greater than M1 × N, the data server S1 obtains the execution result of M1 subtasks according to the following process:
step 401: starting;
step 402: for each of the M1 subtasks ST1, the data server S1 performs the following operations: selecting N vehicle-mounted cloud table items with state domain values in an idle state from a vehicle-mounted cloud table, creating a unicast address by a data server S1 for each vehicle-mounted cloud table item in the N selected vehicle-mounted cloud table items, wherein the routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table item, sending a subtask request message, the source address of the subtask request message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID of a subtask ST1, the data server S1 sets the state domain value of the vehicle-mounted cloud table item to be in a busy state, and creating a task table item, the link address of the task table item is the link address domain value of the vehicle-mounted cloud table item, and the subtask ID is the subtask ID of the subtask ST 1;
step 403: after receiving the subtask request message, the destination vehicle node in the vehicle-mounted cloud VC1 executes step 411 if it leaves the vehicle-mounted cloud VC1 before completing the subtask identified by the subtask ID of the message, otherwise executes step 404;
step 404: the destination vehicle node returns a subtask response message, the source address of the subtask response message is the destination address of the received subtask request message, the destination address of the subtask response message is the source address of the received subtask request message, the load is the subtask ID and subtask execution result data in the received subtask request message, and then the state value of the destination vehicle node is set to be in an idle state;
step 405: after receiving the subtask response message, the data server S1 saves the execution result data in the subtask response message, and then performs the following operations: deleting the task table entry of the link address with the domain value equal to the source address of the received subtask response message, selecting the task table entry of the subtask ID with the domain value equal to the subtask ID loaded by the received subtask response message, and executing the following operations on each selected task table entry: the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the task table item, a subtask cancellation message is sent, the source address of the subtask cancellation message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID field value of the task table item, the data server S1 selects the vehicle-mounted cloud table item of which the link address field value is equal to the link address field value of the task table item, the state of the vehicle-mounted cloud table item is set to be in an idle state, and the task table item is deleted;
step 406: after receiving the subtask cancellation message, the destination vehicle node stops the currently executed subtask and sets the state value of the destination vehicle node to be an idle state;
step 407: the data server S1 looks at the task table with table name TID1, if it detects that the number N2 of task table entries with subtask ID2 is less than N, it executes step 408, otherwise, executes step 409;
step 408: the data server S1 selects (N-N2) vehicle-mounted cloud table entries with state domain values in an idle state from the vehicle-mounted cloud table, for each vehicle-mounted cloud table entry in the selected (N-N2) vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table entry, a subtask request message is sent, the source address of the message is the unicast address of the data server S1, the destination address is the created unicast address, the load is a subtask ID STID2, the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to be in a busy state, a task table entry is created, the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, the subtask ID is the subtask ID STID2, and the step 403 is executed;
step 409: the data server S1 determines whether the execution result data of the M1 subtasks is received, if yes, step 410 is executed, otherwise step 403 is executed;
step 410: the data server S1 returns a task response message, where the source address of the task response message is the destination address of the received task request message, the destination address is the source address of the received task request message, the execution result data of M1 subtasks loaded with task T1 deletes the task table with the table name TID1, and performs step 412;
step 411: the vehicle node leaving the vehicle cloud VC1 abandons the executed subtask, and step 413 is executed;
step 412: after receiving the task response message, the user equipment U1 stores the execution result data in the task response message;
step 413: and (6) ending.
4. The method as claimed in claim 3, wherein the task ID at task T2 is TID2, and is composed of M2 subtasks, and M2 is an integer greater than 0; one subtask runs in N vehicle nodes, wherein N is an integer greater than 0, the data server S1 is located in an Internet of vehicles VT1 and integrated with an access node AP1, and under the condition that the vehicle nodes located in the Internet of vehicles VT1 form an onboard cloud VC1, if an Internet user equipment U1 needs the data server S1 to execute a task T2, a task request message is sent to the data server S1, the source address of the task request message is the own IPv6 address, the destination address is the unicast TID address of the data server S1, and the load is a task ID2, wherein the routing prefix of the unicast address of the data server S1 is the routing prefix of the Internet of vehicles VT1, and the geographic coordinate is the geographic coordinate of the access node AP 1; after receiving the task request message sent by the user equipment U1, the data server S1 checks the vehicle-mounted cloud table, and if the number of vehicle-mounted cloud table entries with the state domain value in the idle state in the vehicle-mounted cloud table is less than M2 × N, the data server S1 selects the parameter x meeting the condition 1, and then executes the task T2 according to the following process:
condition 1: the number of the vehicle-mounted cloud table items with the state threshold value in the idle state in the vehicle-mounted cloud table is more than that of the vehicle-mounted cloud table items
Figure FDA0002276853750000061
Step 501: starting;
step 502: the data server S1 creates a task table, the table name of the task table is TID2, the subtask IDs of M2 subtasks are divided into x subtask groups, and no repeated subtask ID exists in any two subtask groups; the data server S1 sets the value of parameter g to 0;
step 503: the data server S1 increments the value of the parameter g by 1, if the value of the parameter g is greater than the value of the parameter x, then step 512 is executed, otherwise step 504 is executed;
step 504: for each subtask ID STID3 in the g-th subtask group, the data server S1 performs the following operations: selecting N vehicle-mounted cloud table items with state domain values in idle states from the vehicle-mounted cloud table; for each vehicle-mounted cloud table entry in the selected N vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the vehicle-mounted cloud table entry, and sends a subtask request message, the source address of the subtask request message is the unicast address of the data server S1, the destination address is the created unicast address, and the load is the subtask ID 3; the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to be in a busy state, and creates a task table entry, wherein the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, and the subtask ID is the subtask ID STID 3;
step 505: after receiving the subtask request message, the destination vehicle node in the vehicle-mounted cloud VC1 executes step 513 if it leaves the vehicle-mounted cloud VC1 before completing the subtask identified by the subtask ID of the message, otherwise executes step 506;
step 506: the destination vehicle node returns a subtask response message, the source address of the subtask response message is the destination address of the received subtask request message, the destination address of the subtask response message is the source address of the received subtask request message, the load is the subtask ID and subtask execution result data in the received subtask request message, and then the state value of the destination vehicle node is set to be in an idle state;
step 507: after receiving the subtask response message, the data server S1 saves the execution result data in the subtask response message, and then performs the following operations: deleting the task table entry of the link address with the domain value equal to the source address of the received subtask response message, selecting the task table entry of which the domain value of the subtask ID is equal to the subtask ID in the load of the received subtask response message, and executing the following operations on each selected task table entry: the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address field value of the task table item, a subtask cancellation message is sent, the source address of the subtask cancellation message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID field value of the task table item, the data server S1 selects the vehicle-mounted cloud table item of which the link address field value is equal to the link address field value of the task table item, the state of the vehicle-mounted cloud table item is set to be in an idle state, and the task table item is deleted;
step 508: after receiving the subtask cancellation message, the destination vehicle node stops the currently executed subtask and sets the state value of the destination vehicle node to be an idle state;
step 509: the data server S1 looks at the task table with table name TID2, if it detects that the number N4 of task table entries with subtask ID4 is less than N, it executes step 510, otherwise, executes step 511;
step 510: the data server S1 selects (N-N4) vehicle-mounted cloud table entries with state domain values in an idle state from the vehicle-mounted cloud table, for each vehicle-mounted cloud table entry in the selected (N-N4) vehicle-mounted cloud table entries, the data server S1 creates a unicast address, the routing prefix of the unicast address is 0, the link address is equal to the link address domain value of the vehicle-mounted cloud table entry, a subtask request message is sent, the source address of the subtask request message is the unicast address of the data server S1, the destination address is the created unicast address, the load is the subtask ID STID4, the data server S1 sets the state domain value of the vehicle-mounted cloud table entry to a busy state, creates a task table entry, the link address of the task table entry is the link address domain value of the vehicle-mounted cloud table entry, the subtask ID is the subtask ID STID4, and executes step 505;
step 511: the data server S1 determines whether the execution result data of all subtasks in the g-th subtask group is received, if yes, step 503 is executed, otherwise step 505 is executed;
step 512: the data server S1 returns a task response message, where the source address of the task response message is the destination address of the received task request message, the destination address is the source address of the received task request message, the execution result data of M2 subtasks loaded with task T2 deletes the task table with the table name TID2, and step 514 is executed;
step 513: the vehicle node leaving the vehicle cloud VC1 abandons the executed subtask, and step 515 is executed;
step 514: after receiving the task response message, the user equipment U1 stores the execution result data in the task response message;
step 515: and (6) ending.
CN201710750763.1A 2017-08-28 2017-08-28 Data transmission implementation method based on intelligent Internet of vehicles Active CN107508891B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710750763.1A CN107508891B (en) 2017-08-28 2017-08-28 Data transmission implementation method based on intelligent Internet of vehicles

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710750763.1A CN107508891B (en) 2017-08-28 2017-08-28 Data transmission implementation method based on intelligent Internet of vehicles

Publications (2)

Publication Number Publication Date
CN107508891A CN107508891A (en) 2017-12-22
CN107508891B true CN107508891B (en) 2020-04-28

Family

ID=60694038

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710750763.1A Active CN107508891B (en) 2017-08-28 2017-08-28 Data transmission implementation method based on intelligent Internet of vehicles

Country Status (1)

Country Link
CN (1) CN107508891B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105373426A (en) * 2015-07-28 2016-03-02 哈尔滨工程大学 Method for memory ware real-time job scheduling of car networking based on Hadoop
CN106453640A (en) * 2016-11-25 2017-02-22 常熟理工学院 Communication method of intelligent Internet of Vehicles
CN106507429A (en) * 2016-11-25 2017-03-15 常熟理工学院 A kind of data communications method of car networking
CN107483607A (en) * 2017-08-28 2017-12-15 常熟理工学院 A kind of Internet of Things data Realization Method of Communication of low latency

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5886099B2 (en) * 2012-03-21 2016-03-16 日立オートモティブシステムズ株式会社 Electronic control unit for automobile

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105373426A (en) * 2015-07-28 2016-03-02 哈尔滨工程大学 Method for memory ware real-time job scheduling of car networking based on Hadoop
CN106453640A (en) * 2016-11-25 2017-02-22 常熟理工学院 Communication method of intelligent Internet of Vehicles
CN106507429A (en) * 2016-11-25 2017-03-15 常熟理工学院 A kind of data communications method of car networking
CN107483607A (en) * 2017-08-28 2017-12-15 常熟理工学院 A kind of Internet of Things data Realization Method of Communication of low latency

Also Published As

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

Similar Documents

Publication Publication Date Title
US10104040B2 (en) Wireless local area network WLAN user roaming method, apparatus, and system
CN109842643B (en) Session processing method, device and system
KR101692259B1 (en) Method and apparatus and computer readable record media for communication on Wi-Fi(wireless fidelity) direct multi-group network
CN101771931A (en) P2P (peer 2 peer) resource downloading method and identification device
CN109150723B (en) Routing communication implementation method of Internet of things
WO2019024650A1 (en) Resource configuration method and device
CN106535083B (en) It is a kind of for providing the method and apparatus of service for long-range UE
CN105247815A (en) Device-to-device contention management scheme for mobile broadband networks
WO2019221033A1 (en) A method for synchronizing status of ue in a communication network
CN113994751A (en) Method and apparatus for logical TSN bridge
Zheng et al. Architecture of heterogeneous vehicular networks
CN107508927B (en) Future Internet of vehicles data communication method based on cloud
CN114342332A (en) Communication method, device and system
CN103763750A (en) Method for fast achieving packet forwarding in wireless ad hoc network of TDMA protocol
CN110536359B (en) Network slice creation method, device, equipment and storage medium
CN102404192A (en) Message transmission method and network equipment
CN109089241B (en) Data communication implementation method for vehicle-mounted network
CN103167631B (en) A kind of mesh aggregation link method for building up and equipment
CN107508891B (en) Data transmission implementation method based on intelligent Internet of vehicles
CN109768893B (en) High-efficiency big data network data communication implementation method
CN108696838B (en) Vehicle-mounted data routing method based on position information
CN108494595B (en) High-efficiency new-generation big data network implementation method
CN108055204B (en) Big data network communication implementation method
US20210099913A1 (en) Method and apparatus for controlling traffic of network device in wireless communication network
Ren et al. System design of high speed ad hoc networking with directional antenna

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