CN111356073A

CN111356073A - Task processing method, device and equipment

Info

Publication number: CN111356073A
Application number: CN201811573701.9A
Authority: CN
Inventors: 殷佳欣
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-12-21
Filing date: 2018-12-21
Publication date: 2020-06-30
Also published as: WO2020125356A1

Abstract

The application provides a task processing method, a task processing device and a task processing device, wherein the method comprises the following steps: acquiring task information of a downlink task of the mobile equipment and state information of the mobile equipment, wherein the task information comprises a task type of the downlink task, the task type is used for indicating whether a step of finishing the downlink task is a determination step, and the state information is used for indicating a driving state of the mobile equipment; and sending the subtasks corresponding to the first road side units to at least one first road side unit according to the task information and the state information, wherein the downlink task comprises the subtasks corresponding to at least one road side unit. The reliability of downlink task processing is improved.

Description

Task processing method, device and equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a device for processing a task.

Background

In the car networking system, a vehicle is usually provided with a vehicle-mounted device having a wireless communication function, and the vehicle-mounted device may communicate with a core network device (e.g., a remote server) at a remote location through a Road Side Unit (RSU).

In an actual application process, when the core network device detects a downlink task corresponding to a vehicle (for example, the downlink task may be a fault diagnosis task, a software update task, or the like), the core network device sends the downlink task to an RSU closest to the vehicle, and the RSU closest to the vehicle processes the downlink task. However, the coverage of the RSU is usually limited, when the vehicle is in a driving state, the vehicle can only access the RSU for a short time, and when the task amount of the downlink task is large, the RSU cannot complete the downlink task processing, so that the downlink task processing fails, and the reliability of the downlink task processing is low.

Disclosure of Invention

The application provides a task processing method, a task processing device and a task processing device, and the reliability of downlink task processing is improved.

In a first aspect, the present application provides a task processing method, including: task information of a downlink task of the mobile equipment and state information of the mobile equipment are obtained, and subtasks corresponding to the first path side units are sent to the at least one first path side unit according to the task information and the state information. The task information comprises a task type of the downlink task, the task type is used for indicating whether the step of completing the downlink task is a determining step, the state information is used for indicating the driving state of the mobile equipment, and the downlink task comprises at least one subtask corresponding to the roadside unit.

In the above process, after the downlink task corresponding to the vehicle is obtained, the core network device may divide the downlink task into a plurality of subtasks according to the state information of the vehicle, and send the subtasks to the corresponding first route side unit, and the first route side unit processes the subtasks. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

In a possible implementation manner, sending a subtask corresponding to a first route edge unit to at least one first route edge unit according to task information and state information includes: and sending the subtasks corresponding to the first path side units to at least one first path side unit according to the task type indicated by the task information and whether the state information comprises the path information of the mobile equipment.

In the process, the task type indicates the actual condition of the downlink task, and whether the state information includes the path information of the mobile device indicates the actual driving condition of the mobile device, so that the downlink task can be accurately processed according to the task type indicated by the task information and whether the state information includes the path information of the mobile device, and the reliability of downlink task processing is improved.

In a possible implementation manner, when the step of indicating the task type of the downlink task to complete the downlink task is a determination step and the state information includes path information, the subtasks corresponding to each first path side unit may be sent to at least one first path side unit according to the task information and the state information in a feasible implementation manner as follows:

determining at least one first path edge unit according to the task information and the state information, and determining a subtask corresponding to each first path edge unit; and sending the corresponding subtasks to each first road edge unit.

In the feasible implementation manner, when the task information further includes the total task amount of the downlink task and the state information further includes the traveling speed and the position information of the mobile device, at least one second roadside unit to be accessed by the mobile device can be determined according to the position information and the path information; determining the time length of the mobile equipment accessing each second road side unit according to the coverage range and the driving speed of the second road side unit; and determining at least one first road side unit in at least one second road side unit according to the processing capacity of each second road side unit, the time length of accessing each second road side unit by the mobile equipment and the total task quantity of the downlink tasks, and determining the subtask corresponding to each first road side unit, wherein one first road side unit corresponds to one subtask.

In the above process, when the task type of the downstream task indicates that the step of completing the downstream task is the determining step and the state information includes the path information, the core network device may determine at least one first path edge unit according to the task information and the state information, determine a subtask corresponding to each first path edge unit, and send the corresponding subtask to each first path edge unit. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

In a possible implementation manner, when the step of indicating the task type of the downlink task to complete the downlink task is a determining step and the state information includes the location information of the mobile device, the subtasks corresponding to the first route edge units may be sent to the at least one first route edge unit according to the task information and the state information in a feasible implementation manner as follows:

according to the position information of the mobile equipment and unprocessed tasks in the downlink tasks, executing a first subtask issuing operation, wherein the first subtask issuing operation comprises the following steps: determining N roadside units on a predicted path of the mobile equipment according to the position information, determining subtasks corresponding to the N roadside units according to unprocessed tasks in the downlink tasks and the processing capacity of the N roadside units, and sending the subtasks to the N roadside units, wherein N is an integer greater than 1; and repeating the first subtask issuing operation until the downlink task is processed.

In this possible implementation manner, when the state information further includes the traveling speed of the mobile device, the time duration for the mobile device to access each roadside unit may be determined according to the traveling speed and the coverage area of each roadside unit in the N roadside units; determining the processable task quantity of each roadside unit according to the processing capacity of each roadside unit and the time length of each roadside unit accessed by the mobile equipment; and determining subtasks corresponding to the N roadside units according to the processable task amount of each roadside unit and unprocessed tasks in the downlink tasks.

In the above process, when the task type of the downstream task indicates that the step of completing the downstream task is a non-determination step and the state information includes the path information, the core network device repeatedly executes a second subtask issuing operation (determines a next accessed roadside unit according to the position information and the path information of the vehicle, determines a first subtask according to response information of the last subtask issuing operation, and sends the first subtask to the next accessed roadside unit) until the downstream task is processed. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

In a possible implementation manner, when the task type of the downlink task indicates that the step of completing the downlink task is a non-determination step and the state information includes the location information and the path information of the mobile device, the subtasks corresponding to each first route side unit may be sent to at least one first route side unit according to the task information and the state information in a feasible implementation manner as follows:

executing a second subtask issuing operation according to the position information, the path information and the response information of the last subtask issuing operation of the mobile equipment, wherein the second subtask issuing operation comprises the following steps: determining a next accessed roadside unit according to the position information and the path information of the mobile equipment, determining a first subtask according to response information of the last subtask issuing operation, and sending the first subtask to the next accessed roadside unit; and repeating the second subtask issuing operation until the downlink task is processed.

In the above process, when the task type of the downstream task indicates that the step of completing the downstream task is the determining step and the state information does not include the path information, the core network device repeatedly executes the first subtask issuing operation (determining N roadside units on the predicted path of the vehicle according to the position information, determining subtasks corresponding to the N roadside units according to the unprocessed tasks in the downstream task and the processing capabilities of the N roadside units, and sending the subtasks to the N roadside units) until the downstream task is processed. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

In a possible implementation manner, when the task type of the downlink task indicates that the step of completing the downlink task is a non-determination step and the state information includes the location information of the mobile device, the subtasks corresponding to each first route edge unit may be sent to at least one first route edge unit according to the task information and the state information in a feasible implementation manner as follows:

executing a third subtask issuing operation according to the position information of the mobile equipment and the response information of the last subtask issuing operation, wherein the third subtask issuing operation comprises the following steps: determining M roadside units on a predicted path of the mobile equipment according to the position information, determining a second subtask according to response information of last subtask issuing operation, and sending the second subtask to the M roadside units, wherein M is an integer greater than 1; and repeating the third subtask issuing operation until the downlink task is processed.

In the above process, when the task type of the downstream task indicates that the step of completing the downstream task is a non-determination step and the state information does not include path information, the core network device repeatedly executes a third subtask issuing operation (determining M roadside units on the predicted path of the vehicle according to the position information, determining a second subtask according to response information of the last subtask issuing operation, and sending the second subtask to the M roadside units) until the downstream task is processed. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

In a possible implementation manner, if it is determined that the roadside unit in the path indicated by the path information cannot process and complete the downlink task, a path switching request is sent to the mobile device, and the path switching request is used for requesting the mobile device to switch the driving path.

In the process, the roadside unit in the driving path after the driving path is switched can process and complete the downlink task, so that the reliability of the downlink task processing can be improved by the method.

In a second aspect, the present application provides a task processing device, comprising a processing module and a sending module, wherein,

the processing module is used for acquiring task information of a downlink task of the mobile equipment and state information of the mobile equipment, wherein the task information comprises a task type of the downlink task, the task type is used for indicating whether a step of completing the downlink task is a determination step, and the state information is used for indicating a running state of the mobile equipment;

the sending module is configured to send a subtask corresponding to each first road side unit to at least one first road side unit according to the task information and the state information, where the downlink task includes a subtask corresponding to the at least one road side unit.

In a possible implementation manner, the sending module is specifically configured to:

and sending the subtasks corresponding to the first path edge units to at least one first path edge unit according to the task type indicated by the task information and whether the state information comprises the path information of the mobile equipment.

In a possible implementation manner, the processing module is further configured to determine the at least one first road side unit according to the task information and the state information, and determine a sub-task corresponding to each first road side unit; wherein the step of the task type indication of the downlink task to complete the downlink task is a determination step, and the state information includes the path information

The sending module is specifically configured to send the corresponding subtask to each first road side unit.

In a possible implementation manner, the task information further includes a total task amount of the downlink tasks, and the state information further includes traveling speed and position information of the mobile device; the processing module is specifically configured to:

determining at least one second route unit to be accessed by the mobile equipment according to the position information and the route information;

determining the time length of the mobile equipment accessing each second roadside unit according to the coverage area and the driving speed of the second roadside unit;

and determining at least one first road side unit in the at least one second road side unit according to the processing capacity of each second road side unit, the time length of accessing each second road side unit by the mobile equipment and the total task quantity of the downlink tasks, and determining the subtask corresponding to each first road side unit, wherein one first road side unit corresponds to one subtask.

In a possible implementation manner, the processing module and the sending module are configured to repeatedly execute a first subtask issuing operation according to the location information of the mobile device and an unprocessed task of the downlink tasks until the downlink tasks are processed;

wherein, the first subtask issuing operation includes: the processing module is used for determining N roadside units on a predicted path of the mobile equipment according to the position information, and determining subtasks corresponding to the N roadside units according to unprocessed tasks in the downlink tasks and the processing capacity of the N roadside units; the sending module is used for sending the subtasks to the N roadside units, wherein N is an integer greater than 1; wherein the step of the task type indication of the downlink task completing the downlink task is a determination step, and the state information includes location information of the mobile device.

In one possible embodiment, the status information further includes a travel speed of the mobile device; the processing module is specifically configured to:

determining the time length of the mobile equipment accessing each roadside unit according to the driving speed and the coverage area of each roadside unit in the N roadside units;

determining the processable task quantity of each roadside unit according to the processing capacity of each roadside unit and the time length of each roadside unit accessed by the mobile equipment;

and determining the subtasks corresponding to the N roadside units according to the processable task quantity of each roadside unit and the unprocessed tasks in the downlink tasks.

In a possible implementation manner, the processing module and the sending module are configured to repeatedly execute a second subtask sending operation according to the location information of the mobile device, the path information, and response information of a last subtask sending operation until the downlink task is processed;

wherein, the second subtask issuing operation includes: the processing module is used for determining a next accessed roadside unit according to the position information and the path information of the mobile equipment, determining a first subtask according to response information of the last subtask issuing operation, and the sending module is used for sending the first subtask to the next accessed roadside unit; wherein the task type of the downlink task indicates that the step of completing the downlink task is a non-determination step, and the state information includes location information and path information of the mobile device.

In a possible implementation manner, the processing module and the sending module are configured to repeatedly execute a third subtask issue operation according to the location information of the mobile device and the response information of the last subtask issue operation until the downlink task is processed;

wherein, the third subtask issuing operation includes: the processing module is configured to determine, according to the location information, M roadside units on a predicted path of the mobile device, and determine a second subtask according to response information of the last subtask issuing operation, and the sending module is configured to send the second subtask to the M roadside units, where M is an integer greater than 1; the task type of the downlink task indicates that the step of completing the downlink task is a non-determination step, and the state information includes location information of the mobile device.

In a possible implementation manner, the sending module is further configured to send a path switching request to the mobile device if it is determined that the roadside unit in the path indicated by the path information cannot process and complete the downlink task, where the path switching request is used to request the mobile device to switch a driving path.

In a second aspect, the present application provides a task processing apparatus, including: a memory for storing program instructions, a processor for invoking the program instructions in the memory to perform the task processing method according to any of the first aspect, and a communication interface.

In a second aspect, the present application provides a readable storage medium, wherein a computer program is stored on the readable storage medium; the computer program is for implementing a task processing method according to any one of the first aspect.

According to the task processing method, the device and the equipment, after the downlink task corresponding to the vehicle is obtained, the core network equipment can divide the downlink task into a plurality of subtasks according to the state information of the vehicle, send the subtasks to the corresponding first route side unit, and process the subtasks through the first route side unit. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

Drawings

FIG. 1 is a system architecture diagram provided herein;

fig. 2 is a schematic diagram illustrating an interaction flow of the device according to the embodiment of the present invention;

FIG. 3 is a schematic flow chart of a task processing method provided in the present application;

FIG. 4 is a task step diagram of a first task type provided herein;

FIG. 5 is a task step diagram of a second task type provided herein;

FIG. 6 is a schematic flow chart diagram of another task processing method provided in the present application;

FIG. 7 is a schematic diagram of one path provided herein;

FIG. 8 is a schematic diagram of another path provided by the present application;

FIG. 9 is a schematic flow chart diagram illustrating another task processing method provided herein;

FIG. 10 is a schematic illustration of yet another path provided by the present application;

FIG. 11 is a schematic illustration of yet another route provided by the present application;

FIG. 12 is a schematic flow chart diagram illustrating another task processing method provided herein;

FIG. 13A is a schematic view of a road provided herein;

FIG. 13B is a schematic illustration of another embodiment of the present application;

FIG. 13C is a further schematic view of a roadway provided herein;

FIG. 14 is a schematic illustration of yet another path provided by the present application;

FIG. 15 is a schematic flow chart diagram of another task processing method provided herein;

FIG. 16 is a schematic diagram of a task processing device according to the present application;

fig. 17 is a schematic diagram of a hardware structure of a task processing device provided in the present application.

Detailed Description

The technical solution shown in The present application can be applied to a fifth generation mobile communication technology (5G) system, for example, a vehicle network (V2X) system in a 5G communication system. The present invention can also be applied to a Long Term Evolution (LTE) System, for example, a V2X System in the LTE communication System, and can also be applied to a Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) System, or a Radio Access Network (GERAN) architecture of a Global System for mobile communications (GSM)/Enhanced Data Rate GSM Evolution (Enhanced Data Rate for GSM communication, EDGE) System. The technical solution shown in the present application may also be applied to other communication systems, such as a Public Land Mobile Network (PLMN) system, and the like, which is not limited in the present application.

Fig. 1 is a system architecture diagram provided herein. Referring to fig. 1, the system includes a mobile device 101, a roadside unit 102, and a core network device 103.

Optionally, the mobile device 101 is a device that can be moved. For example, the mobile device 101 may include a vehicle, an aircraft with a low flying height, an industrial robot, and the like. Optionally, a communication Unit is disposed in the mobile device 101, for example, the communication Unit may be an On Board Unit (OBU), and the mobile device 101 may communicate with a roadside Unit through the communication Unit. For example, the mobile device 101 may receive data from the roadside unit through the communication unit, or the mobile device 101 may transmit data to the roadside unit through the communication unit. Alternatively, the mobile device 101 may broadcast a signal in real time so that the roadside unit 102 may discover the mobile device 101, and after the roadside unit 102 discovers the mobile device 101, the roadside unit 102 may establish a communication connection with the mobile device 101.

Alternatively, the roadside units 102 are typically located at the roadsides. The coverage of a wayside unit is typically limited, for example, the coverage of a wayside unit may be 300 meters, 500 meters, etc. The roadside units 102 may communicate with core network devices, as well as with mobile devices 101 within their coverage area. For example, the roadside unit 102 may receive data from the core network device 103 and forward the received data to the corresponding mobile device 101 within its coverage area, or the roadside unit 102 may also receive data from the mobile device 101 within its coverage area and forward the received data to the core network device 103. The roadside units 102 may also perform tasks for the mobile device 101, e.g., the roadside units 102 may perform fault detection for the mobile device 101, process response messages sent by the mobile device 101, etc. Alternatively, the roadside unit 102 may broadcast a signal in real time so that the mobile device 101 may discover the roadside unit 102, and after the mobile device 101 discovers the roadside unit 102, the mobile device 101 may establish a communication connection with the roadside unit 102.

It is only necessary that one of the mobile device 101 and the roadside unit 102 transmits a broadcast signal, and for example, the mobile device 101 may transmit a broadcast signal, or the roadside unit 102 may transmit broadcast information.

Optionally, the core network device 103 may manage the mobile device 101, for example, the core network device 103 may determine a downlink task corresponding to the mobile device. For example, the downstream tasks may include software upgrade tasks, failure detection tasks, and the like. The core network device 103 may also distribute the downlink tasks to the corresponding roadside units 102, and the roadside units 102 process the downlink tasks.

In the present application, after the core network device obtains the downlink task corresponding to the mobile device, the core network device may divide the downlink task into a plurality of subtasks according to the state information (e.g., location information, driving speed, etc.) of the mobile device, and send the subtasks to the corresponding roadside units, and the roadside units process the subtasks. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

The technical means shown in the present application will be described in detail below with reference to specific examples. It should be noted that the following embodiments may be combined with each other, and the description of the same or similar contents in different embodiments is not repeated.

Alternatively, the mobile device shown in the present application may be a vehicle. In the embodiment of the present invention, a mobile device is taken as an example of a vehicle.

For the convenience of understanding the present application, the following describes in detail the overall interaction flow of the core network device, the roadside unit and the vehicle with reference to fig. 2.

Fig. 2 is a schematic diagram of an interaction flow of a device according to an embodiment of the present invention. Referring to fig. 2, the method may include:

s201, the roadside unit sends a registration request message to the core network equipment, and the registration request message comprises parameters of the roadside unit.

Optionally, the parameters of the roadside unit may include: the information of the communication address of the roadside unit, the position information of the roadside unit, the communication distance of the roadside unit, the bandwidth of the roadside unit, the processing capacity of the roadside unit and the coverage of the roadside unit.

Of course, the parameters of the roadside unit may include others, and the present application is not limited thereto.

Alternatively, the identification of the roadside unit is typically identified using a string of characters that uniquely identifies the roadside unit. The identification of the roadside unit may be in Uniform Resource Identifier (URI) format, Uniform Resource Name (URN) format, or the like. For example, the identifier of the roadside unit may be a subscription Identity (ID) assigned to the roadside unit by the core network device.

Alternatively, the communication address of the roadside unit may be an Internet Protocol (IP) address, a Media Access Control (MAC) address, and the like of the roadside unit.

Alternatively, the location of the roadside unit may be a geographical location of the roadside unit. The position of the road sign unit can be represented by longitude and latitude coordinates (absolute coordinates); alternatively, the location of the roadside unit may be expressed in combination (relative coordinates) of the road segment name and distance, for example, at a high speed of 100 km at G40.

Optionally, the communication distance of the roadside unit refers to an effective coverage area of the roadside unit, and vehicles within the effective coverage area can receive information transmitted by the roadside unit. The communication distance of a wayside unit is typically related to the transmit power of the wayside unit. For example, the effective coverage of a roadside unit may be a circle of 300 meters radius, a circle of 500 meters radius, or the like.

Alternatively, the bandwidth of the roadside unit may be the speed at which the roadside unit transmits data to vehicles within its coverage area. For example, the bandwidth may be 3Mbps (Mega Bit Per second).

Optionally, the processing capability of the roadside unit may be the number of sessions that the roadside unit can process in a unit time, where one session is a request response. For example, the roadside unit may have a processing capacity of 5TPS (5 TransactionsPeer Second)

It should be noted that the parameters of the roadside unit can be modified according to actual needs. For example, the transmission power of the roadside units may be adjusted to achieve an adjustment of the communication distances of the roadside units.

S202, the core network equipment sends a registration response message to the roadside unit.

S203, broadcasting the discovery message in real time by the vehicle in the driving process of the vehicle.

Wherein the vehicle broadcast discovery message is used to cause the roadside unit to discover the vehicle.

Alternatively, the discovery Message may be a Cooperative Awareness Message (CAM), and the CAM Message is a Message type defined by the European Telecommunications Standards Institute (ITSI) Intelligent Transportation Systems (ITS).

And S204, the roadside unit establishes communication connection with the vehicle according to the received discovery message sent by the vehicle.

S205, the vehicle sends the state information of the vehicle to the roadside unit.

Optionally, the state information of the vehicle may include one or more of a position of the vehicle, a speed of the vehicle, path information of the vehicle, and a driving state of the vehicle.

Alternatively, the location of the vehicle may be the same as the location of the roadside unit to which the vehicle is currently accessing.

Alternatively, the route information of the vehicle may include one or more of a start position, an end position of the vehicle, and a route between the vehicle traveling from the start position to the end position. The route information of the vehicle can be generally represented in combination with a map, for example, turning left at three intersections ahead, driving out from a third exit to a roundabout; or the vehicle is driven out at the 43A exit after running 80km along the highway.

Alternatively, the running state of the vehicle may include a forward state, a parking state, a reverse state, and the like.

It should be noted that, during the driving process of the vehicle, the vehicle may continuously pass through different roadside units, and the vehicle may send the status information to each passing roadside unit.

And S206, the roadside unit sends the state information of the vehicle to the core network equipment.

And S207, the core network equipment acquires the downlink task of the vehicle.

And S208, the core network equipment sends corresponding subtasks to at least one roadside unit according to the task information of the downlink task and the state information of the vehicle.

And S209, the roadside unit processes the corresponding subtasks.

Optionally, when the roadside unit determines that the vehicle reaches the coverage area of the roadside unit, the roadside unit processes the corresponding sub-task.

It should be noted that, in the embodiment shown in fig. 3, the process of S207 to S208 is described in detail, and is not described again here.

It should be noted that the roadside units shown in S201-S202, the roadside units shown in S204-S206, and the roadsides shown in S208-S209 may be the same roadside unit or different roadside units.

Based on the embodiment shown in fig. 2, the following describes in detail the task processing method shown in the present application with reference to the embodiments shown in fig. 3 to fig. 15.

Fig. 3 is a schematic flowchart of a task processing method provided in the present application. Referring to fig. 3, the method may include:

s301, acquiring task information of a downlink task of the vehicle and state information of the vehicle.

Optionally, an execution main body of the technical solution shown in the present application may be a core network device, and may also be a task processing device disposed in the core network device. Alternatively, the task processing device may be implemented by software, or may be implemented by a combination of software and hardware.

Optionally, the core network device may be a server, a cloud service platform, or the like.

Optionally, the downlink task may be a task preset in the core network device. For example, the downlink tasks preset in the core network device may include upgrade packets periodically sent to the vehicle, information sent to the vehicle at preset time, and the like.

Optionally, the downlink task may be a task generated by the core network device in real time. For example, the core network device may acquire relevant information of a vehicle (for example, a software version in the vehicle, a driving condition of the vehicle, and the like) and generate a task corresponding to the vehicle according to the relevant information of the vehicle, or the core network device may receive report information of another vehicle to the vehicle and detect the vehicle according to the report information, and the like.

The task information comprises a task type of the downlink task, and the task type is used for indicating whether the step of completing the downlink task is a determination step.

For convenience of description, a task type indicating whether a step of the downstream task is a determination step is referred to as a first task type, and a task type indicating whether a step of the downstream task is a determination step is referred to as a second task type.

Hereinafter, the task of the first task type and the task of the second task type will be described in detail with reference to fig. 4 to 5, respectively.

Fig. 4 is a task step diagram of a first task type provided in the present application. Referring to fig. 4, the step of the downstream task of the first task type is determined. That is, to complete the downlink task, step 1, step 2, step 3, and step 4 need to be executed.

Optionally, in the downlink task shown in fig. 4, step 1, step 2, step 3, and step 4 may be executed serially or in parallel.

Optionally, in the downlink task shown in fig. 4, steps may have a dependency relationship, for example, the processing of step 2 depends on the processing result of step 1, the processing of step 3 depends on the processing result of step 2, and the like. The steps can be independent of each other, namely, the processing result of other steps is not needed in the processing of each step.

It should be noted that, for a part of the downstream tasks of the first task type, the number of steps may be variable. For example, assuming that the downlink task of the first task type is to issue a data packet of a preset size, the data packet may be divided into 3 sub-data packets, and the data packet is issued through 3 steps, where each step issues one sub-data packet; or, the data packet may be divided into 5 sub-data packets, and the data packet is issued through 5 steps, each step issuing one sub-data packet.

Fig. 5 is a task step diagram of a second task type provided in the present application. Referring to fig. 5, the steps of the downstream task of the second task type are uncertain.

Referring to fig. 5, the downlink task can be completed by performing step 1 and step 3; alternatively, the downlink task may be completed by performing step 1, step 2, step 4, and step 5; alternatively, the downstream task may be completed by performing step 1, step 2, step 6, step 7, and step 8.

Optionally, for the downlink task shown in fig. 5, the next step to be executed needs to depend on the processing result of the current step. For example, for step 1, when the processing result of step 1 is different, the next step may execute step 2, and may also execute step 3. When the response of the roadside unit after performing step 1 is response 11, the next step is determined to be performed step 2, and when the response of the roadside unit after performing step 1 is response 12, the next step is determined to be performed step 3.

Optionally, the task information may also include others. For example, the task information may also include a total task amount of the downstream tasks, and the like.

Optionally, a corresponding relationship between the task and the type of the task may be preset, and correspondingly, the type of the downlink task may be determined according to the downlink task and the corresponding relationship.

For example, if the downstream task is to send a data packet (such as a software upgrade packet, an information data packet, etc.) of a predetermined size, the type of the downstream task is the first task type. Assuming that the downlink task is a detection task (e.g., detecting a fault of a vehicle, detecting a running condition of the vehicle, etc.), the type of the downlink task is a second task type.

Wherein the state information is used to indicate a driving state of the vehicle.

Note that the state information of the vehicle may be referred to as S205. The process of acquiring the state information of the vehicle by the core network device may refer to the processes of S205-S206, and details are not described here.

S302, according to the task information and the state information, sub-tasks corresponding to the first path side units are sent to at least one first path side unit.

The downlink task comprises a subtask corresponding to at least one roadside unit.

Optionally, the subtask corresponding to the at least one roadside unit forms a downlink task, that is, sending the subtask corresponding to each first roadside unit to the at least one first roadside unit may implement sending the downlink task.

For example, referring to fig. 4 and 5, one subtask in the downstream task may be one or more steps.

Optionally, the subtasks corresponding to the first road side units may be sent to at least one first road side unit according to the task type indicated by the task information and whether the state information includes the path information of the vehicle.

It should be noted that, when the task types indicated by the task information are different, the processes of sending the subtasks corresponding to the first route edge units to at least one first route edge unit are different. The process of sending the subtasks corresponding to the first road side units to the at least one first road side unit when the state information includes the path information of the vehicle is different from the process of sending the subtasks corresponding to the first road side units to the at least one first road side unit when the state information does not include the path information of the vehicle. In the embodiments shown in fig. 6-15, these various situations will be described in detail, and will not be described again here.

Optionally, when the vehicle is driven manually and the navigation is not started, the state information of the vehicle does not include the path information of the vehicle. When the vehicle is automatically driven or the navigation is started, the state information of the vehicle comprises the path information of the vehicle.

According to the task processing method provided by the embodiment of the invention, after the downlink task corresponding to the vehicle is obtained, the core network device can divide the downlink task into a plurality of subtasks according to the state information of the vehicle, and send the subtasks to the corresponding first route side unit, and the first route side unit processes the subtasks. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

Fig. 6 is a flowchart illustrating another task processing method provided in the present application. In the embodiment shown in fig. 6, the step of indicating that the downstream task is completed by the task type of the downstream task is a determination step, and the state information includes path information. Referring to fig. 6, the method may include:

s601, acquiring task information of a downlink task of the vehicle and state information of the vehicle.

It should be noted that the execution process of S601 may refer to S301, and is not described herein again.

S602, determining at least one first path side unit according to the task information and the state information, and determining a subtask corresponding to each first path side unit.

Optionally, the task information further includes a total task amount of the downlink tasks, and the state information further includes a driving speed and position information of the vehicle.

Optionally, at least one first road edge unit may be determined by the following feasible implementation manners, and a sub-task corresponding to each first road edge unit is determined:

determining at least one second roadside unit to be accessed by the vehicle according to the position information and the path information; determining the time length of the vehicle accessing each second road side unit according to the coverage range and the running speed of the second road side unit; and determining at least one first road side unit in at least one second road side unit according to the processing capacity of each second road side unit, the time length of the vehicle accessing each second road side unit and the total task amount of the downlink tasks, and determining the subtask corresponding to each first road side unit, wherein one first road side unit corresponds to one subtask.

Optionally, the at least one second roadside unit is a roadside unit in the path indicated by the path information.

Optionally, the number of the at least one second roadside unit may be preset. For example, the number of second roadside units is 5, 10, etc.

Optionally, for any one of the second roadside units, the length of the road segment of the path indicated by the path information within the coverage area of the second roadside unit may be acquired, and the duration for the vehicle to access the second roadside unit is determined according to the running speed of the vehicle and the length of the path.

Next, the time period for which the vehicle accesses the second roadside unit will be described with reference to fig. 7.

Fig. 7 is a schematic diagram of a path provided by the present application. Referring to fig. 7, the route includes 3 roadside units, which are respectively denoted as roadside unit R1, roadside unit R2 and roadside unit R3. The coverage area of the roadside unit R1 is X1, the coverage area of the roadside unit R2 is X2, and the coverage area of the roadside unit R3 is X3.

Referring to fig. 7, for the roadside unit R1, the road segments of the route within the coverage area X1 of the roadside unit R1 are position a to position B. The length of time that the vehicle has accessed the roadside unit R1 is the ratio of the length of the road segment from location a to location B to the speed of the vehicle.

Referring to fig. 7, for the roadside unit R2, the road segments of the route within the coverage area X2 of the roadside unit R2 are position C to position D. The length of time that the vehicle has accessed the roadside unit R2 is the ratio of the length of the road segment from location C to location D to the speed of the vehicle.

Referring to fig. 7, for the roadside unit R3, the road segments of the route within the coverage area X3 of the roadside unit R3 are position E to position F. The length of time that the vehicle has accessed the roadside unit R3 is the ratio of the length of the road segment from location E to location F to the speed of the vehicle.

And S603, sending the corresponding subtasks to each first path edge unit.

Optionally, after the first roadside unit receives the subtasks, the first roadside unit detects whether the vehicle travels into the coverage area of the first roadside unit according to the discovery message sent by the vehicle, and when the first roadside unit determines that the vehicle travels into the coverage area of the first roadside unit, the first roadside unit executes the corresponding subtasks.

For example, after the first roadside unit receives the discovery message sent by the vehicle, the first roadside unit determines that the vehicle is traveling into its coverage area.

Optionally, after the first edge unit determines that the sub-task is completed, the first edge unit may send a success response message to the core network device. Optionally, if the core network device does not receive the successful response message sent by the first route edge unit, the core network device sends the subtask corresponding to the first route edge unit to another first route edge unit, and the other first route edge unit completes the subtask.

Optionally, the corresponding subtasks may be sent to at least one first road side unit in parallel.

For example, suppose that 3 first roadside units are determined and are respectively denoted as roadside unit 1, roadside unit 2 and roadside unit 2, the roadside unit 1 corresponds to subtask 1, the roadside unit 2 corresponds to subtask 2, and the roadside unit 3 corresponds to subtask 3. After determining that the three first roadside units and the corresponding subtasks are obtained, the method may perform sending the subtask 1 to the roadside unit 1, sending the subtask 2 to the roadside unit 2, and sending the subtask 3 to the roadside unit 3 in parallel.

Optionally, after receiving a response message sent by one first edge unit, the corresponding sub-task may be sent to the next first edge unit.

For example, suppose that 3 first roadside units are determined and are respectively denoted as roadside unit 1, roadside unit 2 and roadside unit 2, the roadside unit 1 corresponds to subtask 1, the roadside unit 2 corresponds to subtask 2, and the roadside unit 3 corresponds to subtask 3. After the three first road side units and the corresponding subtasks are determined to be obtained, the subtask 1 may be first sent to the road side unit 1, the subtask 2 is then sent to the road side unit 2 after a successful response message sent by the road side unit 1 is received, and the subtask 3 is then sent to the road side unit 3 after a successful response message sent by the road side unit 2 is received.

The method shown in the embodiment of fig. 6 will be described in detail below by way of specific examples with reference to fig. 8.

Fig. 8 is a schematic diagram of another path provided by the present application. Referring to fig. 8, the driving path of the vehicle is shown in the curve of fig. 8, and the current position of the vehicle is the position M. Assume that the downstream task is to send 100M size packets to the vehicle.

The core network device may determine, according to the position information of the vehicle and the path shown in fig. 8, that the second road side unit to be accessed by the vehicle includes a road side unit R2, a road side unit R3, a road side unit R4, a road side unit R5, and a road side unit R6. Assuming that the parameters of the 5 RSUs, the calculated time duration for accessing each RSU, and the data amount that each RSU can handle are shown in table 1:

TABLE 1

Roadside unit	Bandwidth of	Duration of vehicle access	Processable data volume
				Roadside unit R2	1M/s	15s	15M
Roadside unit R3	1M/s	5min	300M
				Roadside unit R4	1M/s	30s	30M
Roadside unit R5	1M/s	50s	30M
				Roadside unit R6	1M/s	6s	6M

Since the total task amount of the downstream tasks is 100M-sized packets, 15M-sized packets can be transmitted to the roadside unit R2, and the remaining 85M-sized packets can be transmitted to the roadside unit R3.

During the running of the vehicle, after the roadside unit R2 receives the transmission signal transmitted by the vehicle, the roadside unit R2 transmits the data packet of the size of 15M to the vehicle. After the roadside unit R3 receives the transmission signal transmitted by the vehicle, the roadside unit R3 transmits the 85M-sized data packet to the vehicle.

In the above process, if the core network device does not receive the successful response message sent by the roadside unit R2, which indicates that the roadside unit R2 has failed to successfully send the data packet with the size of 15M to the vehicle, the core network device sends the data packet with the size of 15M to the roadside unit R3 or the roadside unit R4, and the roadside unit R3 or the roadside unit R4 sends the data packet with the size of 15M to the vehicle.

In the embodiments shown in fig. 6 to 8, when the step of indicating that the task type of the downlink task is to complete the downlink task is a determination step and the state information includes path information, the core network device may determine at least one first path edge unit according to the task information and the state information, determine a sub-task corresponding to each first path edge unit, and send the corresponding sub-task to each first path edge unit. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

Fig. 9 is a flowchart illustrating another task processing method provided in the present application. In the embodiment shown in fig. 9, the task type of the descending task indicates that the step of completing the descending task is a non-determination step, and the status information includes the path information of the vehicle. Referring to fig. 9, the method may include:

and S901, acquiring task information of a downlink task of the vehicle and state information of the vehicle.

It should be noted that the execution process of S901 may refer to S301, and is not described herein again.

And S902, determining the next accessed roadside unit according to the position information and the path information of the vehicle.

Alternatively, when the vehicle does not currently access any roadside unit, the next roadside unit that is accessed may be the roadside unit that is closest to the position of the vehicle along the traveling direction of the vehicle in the path indicated by the path information.

Alternatively, when the vehicle is currently accessing any of the roadside units, then the next accessed roadside unit may be the next roadside unit of the roadside unit currently accessed by the vehicle along the traveling direction of the vehicle in the path indicated by the path information.

And S903, determining the first subtask according to the response information of the last subtask issuing operation.

Optionally, a next step to be executed is determined according to response information of the last subtask issuing operation and the downlink task, and the first subtask is determined in the next step.

Optionally, if the next step is a non-detachable step, the next step is determined as the first sub-task. Non-detachable steps refer to steps that need to be completed by a roadside unit in a single process. For example, the step of not-splitting may comprise a detection step or the like.

It should be noted that, if the next step is an undetachable step and the processable task amount of the next roadside unit accessed by the vehicle is smaller than the data amount of the next step (i.e., the next roadside unit accessed by the vehicle cannot process and complete the next step), S902 may be executed again to determine a new next roadside unit accessed.

Optionally, if the next step is an undetachable step, the time length for the vehicle to access the next accessed roadside unit may be determined according to the coverage area of the next accessed roadside unit and the driving speed of the vehicle, the processable task amount of the next accessed roadside unit may be determined according to the processing capability of the next accessed roadside unit and the time length, and the first subtask may be determined in the next step according to the processable task amount of the next accessed roadside unit. When the data amount of the next step is larger than the processable task amount of the next accessed roadside unit, a part of the next step can be determined as the first subtask. When the data amount of the next step is less than or equal to the processable task amount of the next accessed roadside unit, the next step can be determined as the first subtask.

For example, referring to fig. 5, assuming that the last subtask is step 1 and the response information of step 1 is response 11, it is determined that the next step to be executed is step 2. Assuming that the processable task amount of the next roadside unit accessed by the vehicle is 100M and the data amount of the step 2 is 80M, the step 2 is determined as a first subtask.

And S904, sending the first subtask to the next accessed roadside unit.

And S905, judging whether the downlink task is completely issued.

And if so, finishing the downlink task issuing.

If not, go to S902.

The method shown in the embodiment of fig. 9 will be described in detail below by specific examples with reference to fig. 5 and 10.

Fig. 10 is a schematic diagram of another path provided by the present application. Referring to fig. 10, the driving path of the vehicle is shown by the curve of fig. 10. Suppose the downstream tasks are as shown in fig. 5.

And at the time T1, determining that the next roadside unit accessed by the vehicle is the roadside unit R1, determining the step 1 as a first subtask, and sending the first subtask to the roadside unit R1. After the roadside unit R1 receives the discovery message transmitted by the vehicle, the roadside unit R1 performs step 1 on the vehicle.

At time T2, when the core network device receives the response 11 sent by the roadside unit R1, the core network device determines that the next roadside unit is the roadside unit R2, determines step 2 as the first subtask, and sends the first subtask to the roadside unit R2. After the roadside unit R2 receives the discovery message transmitted by the vehicle, the roadside unit R2 performs step 2 on the vehicle.

At time T3, when the core network device receives the response 21 sent by the roadside unit R2, the core network device determines that the next roadside unit is the roadside unit R3, determines step 4 as the first subtask, and sends the first subtask to the roadside unit R3. After the roadside unit R3 receives the discovery message transmitted by the vehicle, the roadside unit R3 performs step 4 on the vehicle.

At time T4, when the core network device receives the successful response message sent by the roadside unit R3, the core network device determines that the next roadside unit is the roadside unit R4, determines step 5 as the first subtask, and sends the first subtask to the roadside unit R4. After the roadside unit R4 receives the discovery message transmitted by the vehicle, the roadside unit R4 performs step 5 on the vehicle. After the step 5 is completed, the downlink task is completed.

In the embodiments shown in fig. 9 to 10, when the task type of the downstream task indicates that the step of completing the downstream task is a non-determination step and the state information includes the path information, the core network device repeatedly executes the second subtask issuing operation (determines the next accessed roadside unit according to the position information and the path information of the vehicle, determines the first subtask according to the response information of the last subtask issuing operation, and sends the first subtask to the next accessed roadside unit) until the downstream task is processed. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

In the embodiments shown in fig. 6 to fig. 10, optionally, before the core network device processes the downlink task, the core network device may further determine whether the roadside unit in the path indicated by the path information can process and complete the downlink task. And if the roadside unit in the path indicated by the path information cannot process and complete the downlink task, sending a path switching request to the vehicle, wherein the path switching request is used for requesting the vehicle to switch the driving path.

Optionally, for the task of the first task type, it may be determined whether the downlink task can be processed and completed according to the total task amount of the first task type and the processable task amounts of all roadside units in the path indicated by the path information. And when the total task quantity of the first task type is less than or equal to the sum of the processable task quantities of all roadside units in the path indicated by the path information, determining that the downlink task can be processed and completed, otherwise, determining that the downlink task cannot be processed and completed.

Optionally, for the task of the second task type, the maximum task amount and the minimum task amount of the second task type may be obtained, and whether the downlink task can be processed and completed is determined according to the maximum task amount, the minimum task amount, and the processable task amounts of all roadside units in the path indicated by the path information. And when the sum of the processable task quantities of all the roadside units in the path indicated by the path information is greater than or equal to the maximum task quantity of the first task type, determining that the downlink task can be processed and completed. And when the sum of the processable task quantities of all roadside units in the path indicated by the path information is less than the minimum task quantity of the first task type, determining that the downlink task cannot be completed. When the sum of the processable task amounts of all roadside units in the path indicated by the path information is between the minimum task amount and the maximum task amount, it cannot be determined whether the downlink task can be completed.

Optionally, for the task of the second task type, the maximum step number and the minimum step number of the second task type may be obtained, and whether the downlink task can be processed and completed is determined according to the maximum step number, the minimum step number, and the number of all roadside units in the path indicated by the path information. And when the number of all roadside units in the path indicated by the path information is greater than or equal to the maximum step number of the first task type, determining that the downlink task can be processed and completed. And when the number of all roadside units in the path indicated by the path information is less than the minimum step number of the first task type, determining that the downlink task cannot be completed. When the number of all roadside units in the path indicated by the path information is between the minimum step number and the maximum step number, it cannot be determined whether the downlink task can be completed.

Optionally, the handover request may include new path information, and the roadside unit in the path indicated by the new path information may complete the downlink task.

Next, a process of switching the travel path will be described in detail with reference to fig. 11.

Fig. 11 is a schematic diagram of another route provided by the present application. Referring to fig. 1, it is assumed that the starting position indicated by the path information of the vehicle is position M and the ending position is position N.

Assuming that the path indicated by the current path information of the vehicle is a route a, and assuming that the core network device determines that the roadside unit R4 and the roadside unit R5 in the route a cannot complete the downlink task, the core network device replans the path information to obtain a route B, and the roadside unit R1, the roadside unit R2 and the roadside unit R3 in the route B can complete the downlink task.

The core network device may send a path switching message to the vehicle, and switch the vehicle from route a to route B after receiving a path switching response message sent by the vehicle.

Fig. 12 is a flowchart illustrating another task processing method provided in the present application. In the embodiment shown in fig. 12, the task type of the descending task indicates that the step of completing the descending task is the determination step, and the status information includes the position information of the vehicle (i.e., the route information of the vehicle is not included in the status information). Referring to fig. 12, the method may include:

s1201, task information of a downlink task of the vehicle and state information of the vehicle are obtained.

It should be noted that the execution process of S1201 may refer to S301, and details are not described here.

And S1202, determining N roadside units on the predicted path of the vehicle according to the position information.

Alternatively, the predicted path refers to a path that the vehicle may travel at a future time.

Optionally, the N roadside units are next roadside units that may be accessed by the vehicle.

Next, N roadside units on the predicted path will be described with reference to fig. 13A to 13C.

Fig. 13A is a schematic view of a road according to the present application. Referring to fig. 13A, according to the current position of the vehicle and the current road condition, the predicted path of the vehicle may be determined as a straight path, and N (N ═ 1) roadside units may be determined as roadside units R1.

Fig. 13B is another schematic road diagram provided in the present application. Referring to fig. 13B, according to the current position of the vehicle and the current road condition, the predicted path of the vehicle may be determined to include a straight path, a left-turn path, and a right-turn path, and N (N ═ 3) roadside units may be determined as the roadside units R1, R2, and R3.

Fig. 13C is a schematic view of another road provided by the present application. Referring to fig. 13C, assuming that it can be located that the vehicle is on a right-turn lane according to the current position of the vehicle, the predicted path of the vehicle can be determined to be a right-turn path, and N (N ═ 1) roadside units can be determined to be roadside units R1.

S1203, determining subtasks corresponding to the N roadside units according to the unprocessed tasks in the downlink tasks and the processing capacities of the N roadside units.

Wherein N is an integer greater than 1.

Optionally, the time length for the vehicle to access each roadside unit may be determined according to the driving speed and the coverage area of each roadside unit in the N roadside units; determining the processable task quantity of each roadside unit according to the processing capacity of each roadside unit and the time length of each roadside unit accessed by the vehicle; and determining subtasks corresponding to the N roadside units according to the processable task amount of each roadside unit and unprocessed tasks in the downlink tasks.

Optionally, the minimum processable task amount may be determined among the processable task amounts determined by the N roadside units, and the subtasks corresponding to the N roadside units may be determined according to the minimum processable task amount and the unprocessed task in the downlink tasks.

For example, assume that N is determined to be 3 roadside units, which are respectively denoted as roadside unit 1, roadside unit 2, and roadside unit 3. Assuming that the processable task amount of the roadside unit 1 is 30M, the processable task amount of the roadside unit 2 is 80M, and the processable task amount of the roadside unit 1 is 120M. Assuming that the unprocessed task includes 300M, 30M of 300M is determined as a subtask corresponding to 3 roadside units.

And S1204, sending the subtasks to the N roadside units.

Optionally, the subtasks may be sent to the N roadside units at the same time, or may be sent to the N roadside units in sequence.

And S1205, judging whether the downlink task is issued completely.

And if so, finishing the downlink task issuing.

If not, go to S1202.

Next, the method shown in the embodiment of fig. 12 will be described in detail by specific examples with reference to fig. 14.

Fig. 14 is a schematic diagram of another path provided by the present application. Assume that the downstream task is to send 100M size packets to the vehicle.

At time T1, the roadside units on the predicted path of the vehicle are determined to be roadside unit R1, roadside unit R2 and roadside unit R3, and assuming that the processable task amount of the roadside unit R1 is 30M, the processable task amount of the roadside unit R2 is 40M and the processable task amount of the roadside unit 3 is 80M, the task amount of the subtasks corresponding to the 3 roadside units is determined to be 30M and sent to the roadside unit R1, the roadside unit R2 and the roadside unit R3 via 30M in a 100M-sized data packet. Assuming that the vehicle travels straight at the intersection, after the roadside unit R3 receives the discovery message sent by the vehicle, it sends the 30M-sized data packet to the vehicle and sends a success response message to the core network device.

At time T2, the roadside units on the predicted path of the vehicle are determined to be roadside unit R4 and roadside unit R5, and assuming that the processable task amount of the roadside unit R4 is 70M and the processable task amount of the roadside unit R2 is 60M, the task amount of the subtask corresponding to the 2 roadside units is determined to be 60M, and the tasks are sent to the roadside unit R4 and the roadside unit R5 via 60M of the remaining 70M-sized data packets. Assuming that the vehicle turns left at the intersection, after the roadside unit R5 receives the discovery message sent by the vehicle, it sends the 60M size data packet to the vehicle and sends a success response message to the core network device.

At time T3, the roadside unit on the predicted path of the vehicle is determined to be the roadside unit R6, and assuming that the processable task amount of the roadside unit R6 is 30M, since the unprocessed task amount is 10M, the task amount of the sub-task corresponding to the roadside unit R6 is determined to be 10M, and the remaining data packet with the size of 10M is sent to the roadside unit R6. After the roadside unit R6 receives the discovery message sent by the vehicle, it sends the 10M-sized packet to the vehicle and sends a success response message to the core network device. After the roadside unit R6 transmits a 10M-sized packet to the vehicle, the downstream task execution is completed.

In the embodiments shown in fig. 12 to 14, when the task type of the downstream task indicates that the step of completing the downstream task is the determining step and the state information does not include the path information, the core network device repeatedly executes the first subtask issuing operation (determining N roadside units on the predicted path of the vehicle according to the position information, determining subtasks corresponding to the N roadside units according to the unprocessed task in the downstream task and the processing capabilities of the N roadside units, and sending the subtasks to the N roadside units) until the processing of the downstream task is completed. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

Fig. 15 is a flowchart illustrating another task processing method provided in the present application. In the embodiment shown in fig. 15, the task type of the descending task indicates that the step of completing the descending task is a non-determination step, and the status information does not include the path information of the vehicle. Referring to fig. 15, the method may include:

s1501, acquiring task information of a downlink task of the vehicle and state information of the vehicle.

It should be noted that the execution process of S1501 may refer to S301, and is not described herein again.

And S1502, determining M roadside units on the predicted path of the vehicle according to the position information.

Wherein M is an integer greater than 1.

It should be noted that the execution process of S1502 may refer to the execution process of S1202, and details are not described here.

And S1503, determining a second subtask according to the response information of the last subtask issuing operation.

It should be noted that the execution process of S1503 may refer to the execution process of S903, and details are not described here.

S1504, sending a second subtask to the M roadside units.

Optionally, the second subtasks may be sent to the M roadside units at the same time, or the second subtasks may be sent to the M roadside units sequentially.

S1505, judging whether the downlink task is delivered and completed.

And if so, finishing the downlink task issuing.

If not, go to S1502.

Next, the method shown in the embodiment of fig. 15 will be described in detail by specific examples with reference to fig. 14.

For example, assume that the road condition of the vehicle is as shown in fig. 14 and the downstream task is as shown in fig. 5.

And at the time T1, determining that the roadside units of the vehicle on the predicted path are the roadside unit R1, the roadside unit R2 and the roadside unit R3, determining the step 1 as a second subtask, and sending the second subtask corresponding to the step 1 to the roadside unit R1, the roadside unit R2 and the roadside unit R3. Assuming that the vehicle is traveling straight at the intersection, after the roadside unit R3 receives the discovery message transmitted by the vehicle, the roadside unit R3 performs step 1 on the vehicle.

At time T2, the core network device receives the response 12 sent by the roadside unit R3, and determines step 3 as the second subtask according to the response 12. And determining the roadside units of the vehicle on the predicted path as the roadside unit R4 and the roadside unit R5, sending the second subtask corresponding to the step 3 to the roadside unit R4 and the roadside unit R5, and if the vehicle turns left at the intersection, executing the step 3 on the vehicle by the roadside unit R5 after the roadside unit R5 receives the discovery message sent by the vehicle. After the step 3 is completed, the downlink task is completed.

In the embodiment shown in fig. 15, when the task type of the downstream task indicates that the step of completing the downstream task is a non-determination step and the state information does not include path information, the core network device repeatedly executes a third subtask issuing operation (determining M roadside units on the predicted path of the vehicle according to the position information, determining a second subtask according to response information of the last subtask issuing operation, and sending the second subtask to the M roadside units) until the downstream task is processed. Therefore, when the task amount of the downlink task is large, the downlink task can still be processed, and the reliability of downlink task processing is improved.

Fig. 16 is a schematic structural diagram of a task processing device according to the present application. Referring to fig. 16, the task processing device 10 may include a processing module 11 and a transmitting module 12, wherein,

the processing module 11 is configured to obtain task information of a downlink task of a mobile device and state information of the mobile device, where the task information includes a task type of the downlink task, the task type is used to indicate whether a step of completing the downlink task is a determination step, and the state information is used to indicate a driving state of the mobile device;

the sending module 12 is configured to send a subtask corresponding to each first route edge unit to at least one first route edge unit according to the task information and the state information, where the downlink task includes a subtask corresponding to the at least one route edge unit.

Optionally, the processing module 11 may execute S301 in the embodiment of fig. 3, S601-S602 in the embodiment of fig. 6, S901-S903 and S905 in the embodiment of fig. 9, S1201-S1203 and S1205 in the embodiment of fig. 12, and S1501-S1503 and S1505 in the embodiment of fig. 15.

Optionally, the sending module 12 may execute S302 in the embodiment of fig. 3, S603 in the embodiment of fig. 6, S904 in the embodiment of fig. 9, S1204 in the embodiment of fig. 12, and S1504 in the embodiment of fig. 15.

The task processing device provided by the present application can execute the technical solutions shown in the above method embodiments, and the implementation principles and beneficial effects thereof are similar, and are not described herein again.

In a possible implementation manner, the sending module 12 is specifically configured to:

In a possible implementation manner, the processing module 11 is further configured to determine the at least one first road side unit according to the task information and the state information, and determine a sub-task corresponding to each first road side unit; wherein the step of the task type indication of the downlink task to complete the downlink task is a determination step, and the state information includes the path information

In a possible implementation manner, the task information further includes a total task amount of the downlink tasks, and the state information further includes traveling speed and position information of the mobile device; the processing module 11 is specifically configured to:

In a possible implementation manner, the processing module 11 and the sending module 12 are configured to repeatedly execute a first subtask issuing operation according to the location information of the mobile device and an unprocessed task in the downlink tasks until the downlink tasks are processed;

wherein, the first subtask issuing operation includes: the processing module 11 is configured to determine, according to the location information, N roadside units on a predicted path of the mobile device, and determine, according to an unprocessed task in the downlink tasks and processing capabilities of the N roadside units, subtasks corresponding to the N roadside units; the sending module 12 is configured to send the subtasks to the N roadside units, where N is an integer greater than 1; wherein the step of the task type indication of the downlink task completing the downlink task is a determination step, and the state information includes location information of the mobile device.

In one possible embodiment, the status information further includes a travel speed of the mobile device; the processing module 11 is specifically configured to:

In a possible implementation manner, the processing module 11 and the sending module 12 are configured to repeatedly execute a second subtask sending operation according to the location information of the mobile device, the path information, and the response information of the last subtask sending operation until the downlink task is processed;

wherein, the second subtask issuing operation includes: the processing module 11 is configured to determine a next accessed roadside unit according to the location information of the mobile device and the path information, determine a first subtask according to response information of the last subtask issuing operation, and the sending module 12 is configured to send the first subtask to the next accessed roadside unit; wherein the task type of the downlink task indicates that the step of completing the downlink task is a non-determination step, and the state information includes location information and path information of the mobile device.

In a possible implementation manner, the processing module 11 and the sending module 12 are configured to repeatedly execute a third subtask issuing operation according to the location information of the mobile device and the response information of the last subtask issuing operation until the downlink task is processed;

wherein, the third subtask issuing operation includes: the processing module 11 is configured to determine, according to the location information, M roadside units on a predicted path of the mobile device, and determine a second subtask according to response information of the last subtask issuing operation, and the sending module 12 is configured to send the second subtask to the M roadside units, where M is an integer greater than 1; the task type of the downlink task indicates that the step of completing the downlink task is a non-determination step, and the state information includes location information of the mobile device.

In a possible implementation manner, the sending module 12 is further configured to send a path switching request to the mobile device if it is determined that the roadside unit in the path indicated by the path information cannot process and complete the downlink task, where the path switching request is used to request the mobile device to switch a driving path.

Fig. 17 is a schematic diagram of a hardware structure of a task processing device provided in the present application. Referring to fig. 17, the task processing device 20 may include: a processor 21, a memory 22 and a communication interface 23, wherein the processor 21, the memory 22 and the communication interface 23 are communicable; illustratively, the processor 21, the memory 22 and the communication interface 23 communicate via a communication bus 24, the memory 22 being configured to store program instructions, the processor 21 being configured to invoke the program instructions in the memory to perform the task processing methods illustrated in any of the above-described method embodiments.

Optionally, the communication interface 23 may comprise a transmitter and/or a receiver.

Alternatively, the processor 21 may implement the functions of the processing module 11 in the embodiment shown in fig. 16.

Alternatively, the communication interface 23 may implement the function of the transmission module 12 in the embodiment shown in fig. 16. Alternatively, the communication interface 23 may be a transmitter.

Optionally, the Processor may be a Central Processing Unit (CPU), or may be another general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor, or in a combination of the hardware and software modules in the processor.

A storage medium having a computer program stored thereon; the computer program is for implementing a method of task processing as described in any of the embodiments above.

All or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The aforementioned program may be stored in a readable memory. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state disk, magnetic tape (magnetic tape), floppy disk (floppy disk), optical disk (optical disk), and any combination thereof.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.

In the present application, the terms "include" and variations thereof may refer to non-limiting inclusions; the term "or" and variations thereof may mean "and/or". The terms "first," "second," and the like in this application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. In the present application, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

Claims

1. A task processing method, comprising:

acquiring task information of a downlink task of a mobile device and state information of the mobile device, wherein the task information comprises a task type of the downlink task, the task type is used for indicating whether a step of completing the downlink task is a determination step, and the state information is used for indicating a driving state of the mobile device;

and sending the subtasks corresponding to the first road side units to at least one first road side unit according to the task information and the state information, wherein the downlink task comprises the subtasks corresponding to the at least one road side unit.

2. The method according to claim 1, wherein the sending, according to the task information and the state information, the subtask corresponding to the first route edge unit to at least one first route edge unit includes:

3. The method according to claim 2, wherein the task type of the downstream task indicates that the step of completing the downstream task is a determination step, and the state information includes the path information; the sending, according to the task information and the state information, a subtask corresponding to each first route edge unit to at least one first route edge unit includes:

determining the at least one first path side unit according to the task information and the state information, and determining a subtask corresponding to each first path side unit;

and sending the corresponding subtasks to each first road edge unit.

4. The method of claim 3, wherein the task information further includes a total task volume of the downstream tasks, and the status information further includes travel speed and location information of the mobile device; the determining at least one first road side unit according to the task information and the state information, and determining a subtask corresponding to each first road side unit, includes:

5. The method of claim 2, wherein the task type of the downlink task indicates that the step of completing the downlink task is a determination step, and the status information comprises location information of the mobile device; the sending, according to the task information and the state information, a subtask corresponding to each first route edge unit to at least one first route edge unit includes:

executing a first subtask issuing operation according to the position information of the mobile equipment and the unprocessed task in the downlink task, wherein the first subtask issuing operation comprises the following steps: determining N roadside units on a predicted path of the mobile equipment according to the position information, determining subtasks corresponding to the N roadside units according to unprocessed tasks in the downlink tasks and the processing capacity of the N roadside units, and sending the subtasks to the N roadside units, wherein N is an integer greater than 1;

and repeating the first subtask issuing operation until the downlink task is processed.

6. The method of claim 5, wherein the status information further comprises a travel speed of the mobile device; the determining the subtasks corresponding to the N roadside units according to the unprocessed tasks in the downlink tasks and the processing capabilities of the N roadside units includes:

7. The method of claim 2, wherein the task type of the downlink task indicates that the step of completing the downlink task is a non-deterministic step, and wherein the status information comprises location information and path information of the mobile device; the sending, according to the task information and the state information, a subtask corresponding to each first route edge unit to at least one first route edge unit includes:

executing a second subtask issuing operation according to the position information of the mobile equipment, the path information and the response information of the last subtask issuing operation, wherein the second subtask issuing operation comprises the following steps: determining a next accessed roadside unit according to the position information and the path information of the mobile equipment, determining a first subtask according to response information of the last subtask issuing operation, and sending the first subtask to the next accessed roadside unit;

and repeating the second subtask issuing operation until the downlink task is processed.

8. The method of claim 2, wherein the task type of the downlink task indicates that the step of completing the downlink task is a non-deterministic step, and wherein the status information comprises location information of the mobile device; the sending, according to the task information and the state information, a subtask corresponding to each first route edge unit to at least one first route edge unit includes:

executing a third subtask issuing operation according to the position information of the mobile equipment and the response information of the last subtask issuing operation, wherein the third subtask issuing operation comprises the following steps: determining M roadside units on a predicted path of the mobile equipment according to the position information, determining a second subtask according to response information of the last subtask issuing operation, and sending the second subtask to the M roadside units, wherein M is an integer greater than 1;

and repeating the third subtask issuing operation until the downlink task is processed.

9. The method of claim 3, 4 or 7, further comprising:

and if the roadside unit in the path indicated by the path information cannot process and complete the downlink task, sending a path switching request to the mobile equipment, wherein the path switching request is used for requesting the mobile equipment to switch a driving path.

10. A task processing device is characterized by comprising a processing module and a sending module, wherein,

11. The apparatus of claim 10, wherein the sending module is specifically configured to:

12. The apparatus of claim 11,

the processing module is further configured to determine the at least one first road side unit according to the task information and the state information, and determine a sub-task corresponding to each first road side unit; wherein the step of the task type indication of the downlink task to complete the downlink task is a determination step, and the state information includes the path information

13. The apparatus of claim 12, wherein the task information further comprises a total task volume of the downstream tasks, and the status information further comprises travel speed and location information of the mobile device; the processing module is specifically configured to:

14. The apparatus of claim 11,

the processing module and the sending module are used for repeatedly executing a first subtask issuing operation according to the position information of the mobile equipment and the unprocessed task in the downlink task until the downlink task is processed;

15. The apparatus of claim 14, wherein the status information further comprises a travel speed of the mobile device; the processing module is specifically configured to:

16. The apparatus of claim 11,

the processing module and the sending module are used for repeatedly executing a second subtask issuing operation according to the position information of the mobile equipment, the path information and the response information of the last subtask issuing operation until the downlink task is processed;

17. The apparatus of claim 11,

the processing module and the sending module are used for repeatedly executing a third subtask issuing operation according to the position information of the mobile equipment and the response information of the last subtask issuing operation until the downlink task is processed;

18. The apparatus of claim 12 or 13 or 16,

the sending module is further configured to send a path switching request to the mobile device if it is determined that the roadside unit in the path indicated by the path information cannot process and complete the downlink task, where the path switching request is used to request the mobile device to switch a driving path.

19. A task processing apparatus, comprising: a memory for storing program instructions, a processor for calling the program instructions in the memory to perform the task processing method of any of claims 1-9, and a communication interface.

20. A readable storage medium, characterized in that the readable storage medium has stored thereon a computer program; the computer program is for implementing a method for task processing according to any one of claims 1-9.