WO2018171712A1 - Method for establishing and updating vehicle group, apparatus and device thereof, and storage medium - Google Patents

Abstract

Embodiments of the present application provide a method for establishing and updating a vehicle group, an apparatus and device thereof, and a storage medium. The method for establishing a vehicle group comprises: obtaining vehicle information of vehicles within a preset range; if the vehicle information satisfies a preset condition, determining group information of a vehicle group; and sending the group information of the vehicle group.

Description

Method for establishing and updating vehicle group, device, device and storage medium thereof

Cross-reference to related applications

The present application is filed on the basis of the Chinese Patent Application No. PCT Application No. PCT Application No. .

Technical field

The present invention relates to the field of wireless communication technologies, and in particular, to a method for establishing and updating a vehicle group, an apparatus, a device, and a storage medium.

Background technique

With the rapid development of economy and society, China's automobile ownership has grown rapidly, and road traffic accidents have occurred frequently. It has become one of the important factors affecting China's public security in recent years. Road traffic safety has become a basic problem affecting social harmony and improving people's livelihood. one. China urgently needs to improve traffic safety from various aspects such as technology, policy and education. Among them, improving vehicle safety design is an important part of it.

The technologies to improve vehicle safety are mainly divided into passive safety technology and active safety technology. Passive safety technology is used to protect people inside and outside the vehicle after accidents. Active safety technology is used to prevent and reduce accidents in vehicles and avoid injuries. Active safety technology is the focus of modern vehicle safety technology development. And trends.

According to a survey conducted by the National Highway Traffic Safety Administration, 80% of road traffic accidents are caused by the driver's negligence within 3 seconds before the accident. An experiment by Daimler-Benz showed that if the driver is warning 0.5 seconds ahead, 60% of the rear-end collision accident can be avoided; if the driver can get the warning and take measures 1.5 seconds earlier, 90% of the rear-end collision accident can be avoided. . Communication-based collision warning system, through the use of advanced wireless cellular communication technology, real-time information interaction between vehicle and vehicle, vehicle and roadside infrastructure, and inform each other's current status (including vehicle position, speed, acceleration, driving path) ) and the knowledge of road environment information, collaboratively aware of road hazard conditions, timely provision of multiple types of collision warning information to prevent road traffic safety accidents, and become a new way of thinking for countries to solve road traffic safety problems.

At the same time, with the development of wireless multimedia services, people's demand for high data rates and user experience is increasing, which puts high demands on the system capacity and coverage of traditional cellular networks. On the other hand, application scenarios such as public safety, social networking, close-range data sharing, and local advertising have led to an increasing demand for understanding and communicating with nearby people or things, that is, Proximity Services. The traditional base station-centric cellular network has obvious limitations in supporting high data rates and proximity services. In the context of this demand, Device-to-Device, which represents a new direction for future communication technologies, D2D) technology came into being. The application of D2D technology can reduce the burden of cellular networks, reduce the battery power consumption of user equipment, increase the data rate, and improve the robustness of the network infrastructure, which satisfies the requirements of the above high data rate services and proximity services.

Based on the above characteristics and advantages of D2D technology, the prior art has proposed the use of cellular wireless communication and D2D technology to realize the possibility of vehicle networking applications. The main scenarios supporting communication include instant communication and vehicle warning. Vehicle warnings may include collision warning, lane change warning, etc. However, the delay requirements in this scenario are very high, and the existing D2D technology cannot be realized.

In vehicle networking communication, communication between vehicles and vehicles in many scenarios (referred to as: Vehicle to Vehicle (V2V) needs to meet the requirements of low delay and high reliability. Therefore, in the application scenario related to vehicle safety V2V communication is more suitable. Further, V2V communication can adopt the D2D technology defined by the 3rd Generation Partnership Project (3GPP). In order to realize V2V communication, each vehicle supporting V2V communication needs to be obtained. Resources required for communication (such as the frequency of communication and physical resources such as time slots). When V2V communication adopts the D2D technology defined by 3GPP, the resources required for V2V communication can be obtained in a competitive manner, such as: Use, but this method may cause resource congestion and collision in a large area of the vehicle. For example, there is a resource block allocated in advance, but multiple vehicles use the same resources (such as: the same frequency resource and time slot) Resources) can cause these vehicles to be unable to use the resources, so that the information of these vehicles can not be sent out. Therefore, in V2V communication, such as The way to get a competitive car pool resources resources, can easily lead to vehicle collision information can not be sent out in a timely manner.

For the above reasons, in a region, if there are many vehicles, in order to avoid congestion caused by competing resources of these vehicles, resources can be allocated and scheduled for each vehicle by the network, so that when V2V communication, multiple vehicles will not appear at the same time. With the same resources, the information for each car can be sent out in a timely manner. On the one hand, in the vehicle safety related vehicle networking application scenario, it is necessary to adopt V2V communication, and on the other hand, it is necessary to avoid resource collision when the vehicle V2V communication is in a vehicle-intensive area.

At present, there is only a technical solution for V2V communication in the related art, and there is no technical solution for providing fleet establishment, fleet renewal, and fleet disbanding.

Summary of the invention

Embodiments of the present invention provide a method for establishing and updating a vehicle group, a device, a device, and a storage medium, which can reduce the probability of resource collision, thereby improving communication efficiency.

The technical solution of the embodiment of the present invention is implemented as follows:

An embodiment of the present invention provides a method for establishing a vehicle group, where the method includes:

Obtaining vehicle information of the vehicle within the preset range;

Determining group information of the vehicle group if the vehicle information satisfies a preset condition;

Send group information of the vehicle group.

An embodiment of the present invention provides a method for updating a vehicle group, where the method includes:

Receiving a join request message sent by the vehicle other than the member in the vehicle group; wherein the join request message carries vehicle information requesting to join the vehicle;

Sending a join response message to the requesting joining vehicle according to the vehicle information of the request to join the vehicle.

An embodiment of the present invention provides a device for establishing a vehicle group, where the device includes:

a first acquiring module configured to acquire vehicle information of a vehicle within a preset range;

a first determining module, configured to determine group information of the vehicle group if the vehicle information satisfies a preset condition;

The first sending module is configured to send group information of the vehicle group.

An embodiment of the present invention provides an apparatus for updating a vehicle group, where the apparatus includes:

a first receiving module, configured to receive a join request message sent by the vehicle other than the member in the vehicle group, wherein the join request message carries vehicle information requesting to join the vehicle;

The second sending module sends a join response message to the requesting joining vehicle according to the vehicle information of the request to join the vehicle.

Embodiments of the present invention provide a device for establishing a group of vehicles, including a memory and a processor, the memory storing a computer program executable on a processor, wherein the processor implements the vehicle when the program is executed The steps in the group creation method.

Embodiments of the present invention provide an apparatus for updating a vehicle group, including a memory and a processor, where the memory stores a computer program executable on a processor, and the processor implements the vehicle group when the program is executed The steps in the group's update method.

Embodiments of the present invention provide a computer readable storage medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement steps in a method for establishing a vehicle group; or the computer program is processed The steps in the method of updating the vehicle group described are implemented when the device is executed.

In the embodiment of the present invention, first, acquiring vehicle information of a vehicle within a preset range; then determining whether the vehicle information meets a preset condition, and determining group information of the vehicle group when the vehicle information satisfies a preset condition; The group information of the vehicle group is transmitted again. In this way, a vehicle group can be established for a vehicle in which the vehicle information meets the preset condition within the preset range, and the direct communication between the members of the vehicle group in the vehicle group is different from the vehicle group member and the vehicle group. The resources of the group external vehicles are dedicated communication resources allocated for the vehicle group, which improves the reliability of the internal communication of the fleet, and also reduces the probability of resource collision, thereby improving the communication efficiency.

DRAWINGS

In the drawings, which are not necessarily to scale, the Like reference numerals with different letter suffixes may indicate different examples of similar components. The drawings generally illustrate the various embodiments discussed herein by way of example and not limitation.

1 is a schematic diagram of an application scenario of device direct-through system discovery/communication in the prior art;

2 is a schematic diagram of vehicle traffic in the prior art;

3 is a schematic diagram of vehicle networking communication in the prior art;

4 is a schematic flowchart of implementing a method for establishing a vehicle group according to an embodiment of the present invention;

5-1 is a schematic flowchart of an implementation process of establishing and updating a fleet within a network coverage according to an embodiment of the present invention;

5-2 is a schematic flowchart of an implementation process of establishing and updating a network coverage external fleet according to an embodiment of the present invention;

6 is a schematic flowchart of an implementation process of a method for establishing a fleet of eighteenth embodiments according to an embodiment of the present invention;

7 is a schematic diagram showing an implementation flow of a method for establishing a fleet of a vehicle according to Embodiment 19 of the present invention;

8 is a schematic flowchart of an implementation process of a vehicle fleet establishing method according to Embodiment 20 of the present invention;

FIG. 9 is a schematic flowchart of an implementation process of a twenty-first vehicle fleet updating method according to an embodiment of the present invention; FIG.

10 is a schematic diagram showing an implementation process of a twenty-two-vehicle update method according to an embodiment of the present invention;

11 is a schematic flowchart showing an implementation process of a twenty-third vehicle fleet updating method according to an embodiment of the present invention;

12 is a schematic flowchart of an implementation process of a twenty-fourth vehicle fleet updating method according to an embodiment of the present invention;

13 is a schematic structural diagram of a composition of a twenty-fifth fleet building device according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of a hardware entity of a device according to an embodiment of the present invention.

detailed description

The specific technical solutions of the present invention will be further described in detail below with reference to the accompanying drawings in the embodiments of the present invention. The following examples are intended to illustrate the invention but are not intended to limit the scope of the invention.

Because of the application scenarios related to vehicle safety, it is more appropriate to use V2V communication. Further, the V2V communication can adopt the D2D technology defined by 3GPP. For ease of understanding, the application scenarios of D2D technology and D2D technology are described in more detail.

D2D technology can work in licensed or unlicensed bands, allowing multiple D2D-enabled user equipment (D2D User Equipment, D2D UE) to directly discover without network infrastructure or network infrastructure. / Direct communication. FIG. 1 is a schematic diagram of an application scenario of device direct communication system discovery/communication in the prior art. As shown in FIG. 1 , there are three main application scenarios of D2D:

The first type, User Equipment (UE) 1 and UE2 perform data interaction under the coverage of the cellular network, and the user plane data does not pass through the network infrastructure, as shown in FIG. 1;

Second, the UE relay transmission in the weak/uncovered area, as shown in mode 2 of FIG. 1, allows the UE4 with poor signal quality to communicate with the network through the UE3 with network coverage nearby, which can help the operator to expand. Cover and increase capacity;

Third, in the event of an earthquake or emergency, the cellular network is not working properly, allowing direct communication between devices, as shown in Figure 3, mode 3, UE5, UE6 and UE7 control plane and user plane are not passed One-hop or multi-hop data communication for network infrastructure.

The D2D technology generally includes a D2D discovery technology and a D2D communication technology, wherein the D2D discovery technology refers to a technology for determining/determining whether the first user equipment is adjacent to the second user equipment. Generally, D2D user equipment can discover each other by transmitting or receiving discovery signals/information; D2D communication technology refers to a technology in which some or all communication data between D2D user equipments can communicate directly without using a network infrastructure.

Based on the above characteristics and advantages of D2D technology, the prior art has proposed the use of cellular wireless communication and D2D technology to realize the possibility of vehicle networking applications. The main scenarios supporting communication include instant communication and vehicle warning. Vehicle warnings may include collision warning, lane change warning, etc. However, the delay requirements in this scenario are very high, and the existing D2D technology cannot be realized.

In the Internet of Vehicles communication, communication between vehicles and vehicles in many scenarios (referred to as: V2V, vehicle to vehicle) needs to meet the requirements of low delay and high reliability. 2 is a schematic diagram of vehicle traffic in the prior art. In FIG. 2, the distance between two vehicles (eg, car A and car B) is too close, and it is necessary to pay attention to driving safety between the vehicles. If: Car A first reports its own position/vehicle speed and other information to the network, and then the vehicle B informs the vehicle B, then the information obtained by the vehicle B to obtain the position/speed of the vehicle A is delayed, which may result in the vehicle B not being able to quickly avoid the vehicle A. .

FIG. 3 is a schematic diagram of vehicle networking communication in the prior art. As shown in FIG. 3, in the vehicle network communication, the communication between the vehicle and the network is referred to as V2I (Vehicle to Infrastructure). In the embodiment of the present invention, V2I communication is also called V2R communication, R is RSU (Radio Side unit), V2I and V2R communication refers to communication between Vehicle and network, and the network can be: RSU, Infrastructure, eNB (Node B), relay (relay), etc.

Embodiment 1

The embodiment of the present invention provides a method for establishing a vehicle group, which is applied to a device for establishing a vehicle group. The device may be, for example, a UE or a network side device, where the network side device may be a base station, and FIG. 4 is a vehicle according to an embodiment of the present invention. A schematic diagram of an implementation process of a group establishment method, as shown in FIG. 4, the method includes the following steps:

Step S401, acquiring vehicle information of a vehicle within a preset range;

Here, step S401 is discussed in two scenarios:

The first case: in the case of network coverage, step S401 may be implemented by a processor in a network side device (such as a base station or a core network device), or may be processed in a terminal device carried in the vehicle. Implemented.

The second case: in the case of no network coverage, step S401 can only be implemented by a processor in the terminal device carried in the vehicle.

It should be noted that when the step S401 is implemented by a processor in the terminal device carried in the vehicle, the vehicle is the manager of the vehicle group to be established, that is, the vehicle head in the embodiment of the present invention and other embodiments.

The vehicle information includes, but is not limited to, one or more of the following information: vehicle status information, vehicle identification information, vehicle capability information, vehicle willing information, vehicle private information, and application layer group identification.

The vehicle status information, also referred to as UE status information, refers to the status of a certain vehicle, including one or more of the following information: position, speed, acceleration, and direction of motion. (heading), front destination (direction), etc.

The vehicle identification information, also referred to as UE identity, refers to a unique identifier of the Vehicle UE in the network. In a specific implementation process, the vehicle identification information may be a UE identification (ID), a Public Land Mobile Network (PLMN) PLMN ID, and a ProSe UE ID (Proximity based Services, UE). ID) and so on.

The vehicle private information is also referred to as member identification information, or private information called a fleet of vehicles (that is, a vehicle group in the embodiment of the present invention), or group private information, also referred to as fleet restriction information, which refers to a certain The identity of a unit, enterprise, or company to which a vehicle/fleet belongs, such as the logo of a transportation company. The fleet private information of a fleet is the same as the vehicle private information of the front (the vehicle members in the vehicle group used to manage the vehicle group), that is, the network or the front of the vehicle uses the vehicle private information of the front as the fleet's private information. In some scenarios, only vehicles of the same unit, company or company are allowed to form a fleet, that is to say, vehicles of other units, companies or companies are not allowed in the fleet. Under such restrictions, nearby vehicles determine whether to allow participation in the fleet based on the fleet's private information. The front/network can also join the vehicle's nearby vehicle's private information on request to determine whether to allow the nearby vehicle to join the fleet. In this restricted scenario, nearby vehicles determine whether to join the fleet based on the vehicle private information broadcasted by the front. The head of a fleet can also determine whether to allow the vehicle to join the team based on the vehicle's private information of nearby vehicles. Similarly, under network coverage, when there is a network to determine whether to allow a nearby vehicle to join a certain fleet, the network decides whether to allow the nearby vehicle to join the fleet based on the vehicle's private information and the vehicle's private information of nearby vehicles.

The vehicle capability information is also referred to as member capability information, and is used to indicate which communication modes are supported by the UE, and which services are supported, such as V2V communication, V2I communication, V2X application, V2V application, and the like. In general, a vehicle needs at least the ability to support V2V communication and V2I communication to allow it to be used as a front.

The vehicle willing information, also referred to as the member's willing information, is used to indicate whether the UE is willing to be the head of a certain fleet, whether it is willing to be a member of a certain fleet, and whether it is willing to withdraw from a fleet. In the process of establishing and updating a fleet, based on the vehicle's willingness information, the network or the vehicle itself can determine whether it is possible to construct a fleet and become a front, or can determine whether the vehicle is willing to join or exit a fleet. The premise of the network's judgment is that the network has been informed of the vehicle's willingness information.

Step S402, if the vehicle information meets a preset condition, determining group information of the vehicle group;

Here, first, it is necessary to determine the number of vehicles in the preset range; if the number of vehicles in the preset range is equal to 1, the preset condition is that the vehicle capability information of the vehicle in the preset range satisfies a preset head The vehicle capacity required, wherein the vehicle capacity required for the front end includes at least V2V communication capability and V2I communication capability;

If the number of vehicles in the preset range is greater than 1, the preset condition includes at least the same vehicle state information of the vehicle within the preset range, and the vehicle capability of at least one vehicle in the vehicle within the preset range is satisfied The preset vehicle head needs to have the vehicle capability, and the vehicle capability information of the vehicle within the preset range satisfies the support V2V communication.

The same vehicle status information means that the distance between the vehicles is within a certain range, the running direction is the same, the speed is similar, and the destinations are the same.

In the case of network coverage, step S402 may be implemented by a processor in a network side device (such as a base station), or may be implemented by a processor in a terminal device carried in the vehicle. When the step S402 is implemented by a processor in the terminal device carried in the vehicle, the step S402 further includes:

Step S402a, if the vehicle information satisfies a preset condition, a setup request message sent to a network establishing a connection with itself;

Here, the setup request message carries its own vehicle information.

Step S402b, receiving an establishment response message that the network is allowed to establish a vehicle group based on the establishment request message;

Here, the setup response message carries group information of a vehicle group. The group information includes at least one or more of the following information: vehicle group identification information, vehicle group security information, vehicle head internal identification, and vehicle group private information.

The vehicle group private information is the vehicle private information of the front. When the network agrees to establish a vehicle group, the vehicle private information sent by the front head becomes the vehicle group private information, and then the vehicle private information of the nearby vehicle requesting to join the vehicle group must be the same as the vehicle group private information.

The interior identification of the front end refers to the internal identification of the first fleet members in a group of vehicles, which is unique among a group of vehicles. Since the number of vehicle group members in a vehicle group is not too large (for example, a vehicle group has a maximum of 32 vehicle group members), a vehicle group can be uniquely identified by 5 bits. Each vehicle in the group. The byte/bit required for the existing UE ID is very long, and the internal identification of the fleet can be identified with few bits, which is relatively efficient. Further, for the front of the car can be identified by member = 0, other team members for member = 1, 2, ... 31 to identify in turn. In order to preserve future scalability, up to 64 team members can use 6 bits to uniquely identify a unique identity of a vehicle group.

Using the vehicle group internal identification in addition to the above-described savings in identifying the byte/bit overhead of a certain vehicle, it is also possible to make direct communication between vehicles within the vehicle group without considering the influence between multiple PLMNs. In particular, when direct communication between members of various vehicle groups within a group of vehicles is performed using dedicated communication resources within the group of vehicles, ie, direct communication between members of the various vehicle groups in the group of vehicles is employed The resources are different from the resources of the vehicle group members and the vehicle outside the vehicle group, and each vehicle group member adopts the vehicle group internal identifier.

Step S402c: Determine group information of the vehicle group according to the setup response message.

In the case of network coverage, when step S402 is implemented by a processor in a network side device (such as a base station), step S402 further includes:

Step S402a', if the vehicle information satisfies the preset condition, determining a vehicle whose vehicle information meets the preset condition is determined as a vehicle group;

That is to say, the processor on the network side judges which vehicles meet the conditions for establishing a vehicle group based on the acquired vehicle information, and determines the eligible vehicle as a vehicle group.

Step S402b', determining group information of the vehicle group based on the vehicle information.

Here, after the network side processor determines the vehicle group, a vehicle group member is selected from the vehicle group as the front of the vehicle group, and the group information of the vehicle group is determined according to the vehicle information of the vehicle head.

In the case of no network coverage, step S402 can only be implemented by a processor in the terminal device carried in the vehicle. In this case, step S402 is specifically: if the vehicle information meets the preset condition, the vehicle is pre-configured by itself. The group information of the group is determined as the group information of the vehicle group.

That is to say, in the case of no network coverage, it is judged according to its own vehicle information that when it is willing to act as a front, then it is required to have group information of the vehicle group. The group information may be pre-configured by the front end of the vehicle, or it may be obtained from a network (eg, a V2X control function) when there is network coverage.

Step S403, sending group information of the vehicle group.

Here, in the case of network coverage, step S403 may be implemented by a processor in a network side device (such as a base station), or may be implemented by a processor in a terminal device carried in the vehicle.

In the case of no network coverage, step S403 can only be implemented by a processor in the terminal device carried in the vehicle.

Further, sending the group information of the vehicle group includes the following two situations:

Transmitting first group information to vehicle members in the group of vehicles, wherein the first group information includes at least one of: fleet identification information, fleet status information, fleet opening information, fleet ownership Information and fleet safety information;

Transmitting second group information to a vehicle other than the group of vehicles, wherein the second group information includes at least one of: fleet identification information, fleet status information, fleet opening information, and fleet ownership information.

That is to say, the information transmitted to the vehicle members in the vehicle group is different from the information transmitted to the vehicles outside the vehicle group, and the vehicle safety information is not transmitted to the vehicles other than the vehicle group, so that the fleet can be avoided. Safety information is obtained by vehicles that do not want to join the vehicle group, thus ensuring the safety of the fleet.

In the method for establishing a vehicle group according to an embodiment of the present invention, first, acquiring vehicle information of a vehicle within a preset range; and then determining whether the vehicle information meets a preset condition, and when the vehicle information meets a preset condition, Determining group information of the vehicle group; and transmitting the group information of the vehicle group to the vehicle within the preset range. In this way, a vehicle group can be established for a vehicle in which the vehicle information meets the preset condition within the preset range, and the direct communication between the members of the vehicle group in the vehicle group is different from the vehicle group member and the vehicle group. The resources of the group external vehicles are dedicated communication resources allocated for the vehicle group, which reduces the probability of resource collisions, thereby improving communication efficiency.

Embodiment 2

Based on the foregoing embodiments, an embodiment of the present invention provides a method for updating a group of vehicles. The update of the vehicle group includes the joining of vehicles near the vehicle group, the exit of the vehicle group members, the disbanding of the vehicle group, and the like. Embodiments of the present invention are an update process for a vehicle to be joined in the vicinity of a vehicle group. The method for updating a vehicle group provided by the embodiment of the present invention includes the following steps:

Step 21: Receive a join request message sent by the vehicle other than the member in the vehicle group;

Here, the join request message carries vehicle information requesting to join the vehicle, and the vehicle information includes at least one of the following information: vehicle identification information, vehicle status information, vehicle private information, and application layer group identification information.

It should be noted that the message of the join request message, the exit request message, and the like in the embodiment and the other embodiments are all for the group, that is, the join request message is a request message for joining the group, and the exit request message is used. The request message for exiting the group.

In the case of network coverage, the first step may be implemented by a processor in a network side device (such as a base station) or in a terminal device carried by a first vehicle member (front head) in the vehicle group. The processor is implemented.

In the absence of network coverage, the first step can only be implemented by a processor in the terminal device carried by the first vehicle member (the front) of the vehicle group.

After the nearby vehicle of the vehicle group acquires the group information sent by the vehicle member in the vehicle group, it is determined according to the group information whether the vehicle group allows other vehicle members to join and whether it is willing to join the vehicle group; , the nearby vehicle sends a join request message.

Step 22: Send a join response message to the requesting joining vehicle according to the vehicle information of the request to join the vehicle.

Here, in the case of network coverage, the second step of the step may be implemented by a processor in a network side device (such as a base station), or may be implemented by a processor in a terminal device carried by the vehicle head in the vehicle group. In the absence of network coverage, the second step can only be implemented by a processor in the terminal device carried in the front of the vehicle group.

The sending a join response message to the requesting join vehicle further includes:

If the vehicle information requesting to join the vehicle satisfies a preset joining condition, sending a join response message to the requesting joining vehicle to allow joining;

Here, the preset joining condition includes at least one of the following conditions: whether the vehicle private information requesting to join the vehicle is consistent with the fleet private information, the application layer group identification information of the joining vehicle and the fleet application layer identification information of the fleet are requested. Is it consistent whether the vehicle status information of the requested vehicle is consistent with the fleet status information of the vehicle group, and whether the vehicle group's fleet opening information allows the vehicle to join

If the vehicle information requesting to join the vehicle does not satisfy the preset joining condition, then the joining vehicle is sent to the request to send a join response message rejecting the joining.

When the second step is implemented by a processor in a network side device (such as a base station) in the case of network coverage, the method further includes:

Step 23A: If the join response message is a join response message that is allowed to join, send a group update message to the first vehicle member in the vehicle group for managing the vehicle group;

Here, the group update message carries the vehicle information of the request to join the vehicle.

Step 24A, determining whether a group update confirmation message sent by the first vehicle member is received;

Step 25A, if the group update confirmation message sent by the first vehicle member is not received, sending a group update message to the first vehicle member again;

Step 26A: Send first group information to the vehicle members in the vehicle group, wherein the first group information includes at least one of the following information: fleet identification information, fleet status information, and fleet opening information. , fleet private information and fleet safety information;

Step 27A: Send second group information to a vehicle other than the vehicle group, wherein the second group information includes at least one of the following information: fleet identification information, fleet status information, and fleet opening information. And private information about the team.

When the network is covered, the second step is implemented by a processor in the terminal device carried by the first vehicle member (the front) of the vehicle group, the method further includes:

Step 23B: Send a group update message to a network that establishes a connection with itself;

Here, the group update message carries the vehicle information of the request to join the vehicle.

Step 24B, determining whether a group update confirmation message sent by the network is received;

Step 25B, if the group update confirmation message sent by the network is not received, sending a group update message to the network again;

Step 26B, sending first group information to the vehicle members in the vehicle group, wherein the first group information includes at least one of the following information: fleet identification information, fleet status information, fleet open information. , fleet private information and fleet safety information;

Step 27B: Send second group information to the vehicle outside the vehicle group, wherein the second group information includes at least one of the following information: fleet identification information, fleet status information, and fleet opening information. And private information about the team.

When there is no network coverage, the method further includes:

Step 23C: Send first group information to the vehicle members in the vehicle group, wherein the first group information includes at least one of the following information: fleet identification information, fleet status information, and fleet opening information. , fleet private information and fleet safety information;

Step 24C: Send second group information to a vehicle other than the vehicle group, wherein the second group information includes at least one of the following information: fleet identification information, fleet status information, and fleet open information. And private information about the team.

Embodiment 3

Based on the foregoing embodiments, an embodiment of the present invention provides a method for updating a vehicle group. Specifically, the embodiment of the present invention is an update process for a vehicle group member exiting in a vehicle group, and the method includes the following steps:

Step 31: Receive an exit request message requesting to exit the vehicle in the group of vehicles;

Here, in the case of network coverage, the step may be implemented by a processor in a network side device (such as a base station), or may be in a terminal device carried by a first vehicle member (a vehicle head) in the vehicle group. The processor is implemented. In the absence of network coverage, this step can only be implemented by a processor in the terminal device carried by the first vehicle member (the front) of the vehicle group.

The request to exit the vehicle must meet the following three conditions: the vehicle member is not the first vehicle member, the vehicle group allows the vehicle member to exit the fleet, and the vehicle member himself wants to exit the fleet. When all three conditions are met, the exit request message can be sent, and the exit request message carries the vehicle information requesting to exit the vehicle.

Step 32: Send an exit response message to the requesting exit vehicle according to the vehicle information of the request to exit the vehicle.

Here, in the case of network coverage, the step 32 may be implemented by a processor in a network side device (such as a base station or a core network device), or may be a first vehicle member (front) in the vehicle group. Implemented by a processor in the terminal device that is carried. In the absence of network coverage, this step can only be implemented by a processor in the terminal device carried by the first vehicle member (the front) of the vehicle group.

Sending an exit response message to the requesting exit vehicle according to the requesting to exit the vehicle information of the vehicle, including:

Determining whether the vehicle information requesting to exit the vehicle meets a preset exit condition;

If the vehicle information requesting to exit the vehicle satisfies a preset exit condition, sending an exit response message allowing the exit to the request to exit the vehicle;

If the vehicle information requesting to exit the vehicle does not satisfy the preset exit condition, an exit response message rejecting the exit is sent to the requesting exit vehicle.

When the step 32 is implemented by the processor on the network side in the case of network coverage, the method further includes:

Step 33A: Send a group update message to a first vehicle member in the group of vehicles for managing the group of vehicles;

Here, the group update message carries the vehicle information requesting to exit the vehicle.

Step 34A, determining whether a group update confirmation message sent by the first vehicle member is received;

Step 35A: If the group update confirmation message sent by the first vehicle member is not received, the group update message is sent to the first vehicle member again.

When the step 32 is implemented by a processor of the terminal carried by the first vehicle member in the case of network coverage, the method further includes:

Step 33B: Send a group update message to a network that establishes a connection with itself;

Here, the group update message carries the vehicle information requesting to exit the vehicle.

Step 34B, determining whether a group update confirmation message sent by the network is received;

Step 35B: If the group update confirmation message sent by the network is not received, the group update message is sent to the network again.

Step 36: Send first group information to the vehicle members in the vehicle group, wherein the first group information includes at least one of the following information: fleet identification information, fleet status information, and fleet opening information. , fleet private information and fleet safety information;

Here, in the case of network coverage, step 36 may be implemented by a processor in a network side device (such as a base station), or may be a terminal device carried by a first vehicle member (front) in the vehicle group. The processor is implemented. In the absence of network coverage, this step can only be implemented by a processor in the terminal device carried by the first vehicle member (the front) of the vehicle group.

Step 37: Send second group information to a vehicle other than the vehicle group, wherein the second group information includes at least one of the following information: fleet identification information, fleet status information, and fleet opening information. And private information about the team.

Here, in the case of network coverage, the step 37 may be implemented by a processor in a network side device (such as a base station), or may be in a terminal device carried by a first vehicle member (a vehicle head) in the vehicle group. The processor is implemented. In the absence of network coverage, this step can only be implemented by a processor in the terminal device carried by the first vehicle member (the front) of the vehicle group.

Embodiment 4

Based on the foregoing embodiments, the embodiment of the present invention further provides a method for updating a vehicle group. Specifically, the embodiment of the present invention provides a process for dissolving a vehicle group in the case of network coverage, and the process includes the following steps. step:

Step 41: The first vehicle member sends a dissolving request message for dissolving the vehicle group to a network establishing a connection with itself;

Here, when a vehicle group no longer has a vehicle group use (such as all vehicles arrive at the destination, in a stationary state), or no vehicle group members are willing/have the responsibility of the front, a vehicle group can be disbanded.

Step 42: The first vehicle member receives a disbanding response message sent by the network;

Here, after the network receives the dissolving request message, it is determined according to the group information of the vehicle group whether to allow the vehicle group to be dismissed; if the vehicle group is allowed to be dismissed, the first vehicle member is sent a dissolving response that allows dissolution. a message; if the vehicle group is not allowed to be dismissed, a disbanding response message rejecting dissolution is sent to the first vehicle member.

Step 43: If the dissolving response message is a dissolving response message that allows disbanding, the first vehicle member sends a dissolving indication message to the vehicle in the group of vehicles.

Here, after the vehicle group is allowed to be disbanded, the first vehicle member informs the vehicle member of the vehicle group that the vehicle group is disbanded by the vehicle member other than the first vehicle member through the V2V message.

Embodiment 5

The embodiment of the present invention further provides a method for updating a vehicle group. Specifically, the embodiment of the present invention provides a process for dissolving a vehicle group without network coverage, and the process includes the following steps:

Step 51: The first vehicle member determines whether to allow dissolving the vehicle group according to the group information of the vehicle group.

Here, the first vehicle member itself makes a determination as to whether or not it is permitted to disband the vehicle group.

Step 52: If the vehicle group is allowed to be disbanded, a dismissal indication message is sent to the vehicle in the group of vehicles.

Here, after the vehicle group is allowed to be disbanded, the first vehicle member informs the vehicle member of the vehicle group that the vehicle group is disbanded by the vehicle member other than the first vehicle member through the V2V message.

Embodiment 6

The embodiment of the present invention describes the process of establishing, updating, and dissolving a vehicle group. For a better understanding of the embodiments of the present invention, the terms used in the embodiments of the present invention are first defined as follows:

Vehicle team: Also referred to as a group or group in the embodiment of the present invention, English is Platoning, Platoon, or group.

The front part of the invention is also referred to as the first team member, also referred to as the first member, the manager of the first group member team, and the front is responsible for direct V2I communication between the team and the RSU. English: group manager, or group leader. The front of the car needs to have V2I and V2V communication capabilities, need to support V2X application (V2X application) and support V2X communication (V2X communication)

The second team member: also known as the second member, second group member, refers to a team other than the first team members, the second team members need to have V2V communication capabilities, need to support V2X applications (V2X Application) and support V2X communication (V2X communication).

Team members: Also known as group members, group members refer to all vehicles in a fleet, including first team members and second team members.

Other team members: Also known as other group members, refer to all other second team members in a team other than the first team members.

Vehicle: Vehicle UE, also known as UE, also known as member, member, includes: nearby vehicles outside the fleet and vehicles within the fleet.

Network: V2X control function, or V2X Application server, or core network (CN, core network), or radio access network (RAN), or roadside Unit (RSU, road site unit). When fleet management is completed by the application layer, the network refers to the V2Xcontrol Function or V2X Application server or RSU or core network; when the fleet management is completed by layer 2, the network refers to the RAN.

PC5 interface: A direct communication interface between the UE and the UE, that is, an interface of D2D communication defined by 3GPP LTE. In the present invention, direct communication between the vehicle and the vehicle (V2V communication) can be through the PC5 interface.

Vehicle status information: also referred to as member status information, refers to the status of a certain vehicle, including one or more of the following information: position, speed, acceleration, heading, Forward direction, etc.

Vehicle identification information: also referred to as member identification information, UE identity, refers to the unique identifier of the Vehicle UE in the network. Such as: UE ID, PLMN ID, ProSe UE ID, etc.

Vehicle private information, also known as member identification information, or fleet private information, or group private information, also known as fleet restriction information, refers to a certain unit, enterprise, company to which a certain vehicle/fleet belongs. The logo, such as: the shipping company logo. The private information of a team's fleet is the same as the private information of the vehicle at the front, which means that the vehicle or the front of the vehicle uses the vehicle's private information as the fleet's private information. In some scenarios, only vehicles of the same unit, company or company are allowed to form a fleet, that is to say, vehicles of other units, companies or companies are not allowed in the fleet. Under such restrictions, nearby vehicles determine whether to allow participation in the fleet based on the fleet's private information. The front/network can also join the vehicle's nearby vehicle's private information on request to determine whether to allow the nearby vehicle to join the fleet. In this restricted scenario, nearby vehicles determine whether to join the fleet based on the vehicle private information broadcasted by the front. The head of a fleet can also determine whether to allow the vehicle to join the team based on the vehicle's private information of nearby vehicles. Similarly, under network coverage, when a network determines whether a nearby vehicle is allowed to join a certain fleet, the network determines whether the fleet can be based on the vehicle's private information and the nearby vehicle's private information.

Vehicle capability information: Also known as member capability information, it is used to indicate which communication modes are supported by the UE, and which services are supported, such as V2V communication, V2I communication, V2X application, V2V application, and the like. In general, a vehicle needs at least the ability to support V2V communication and V2I communication to allow it to be used as a front.

Vehicle Willing Information: Also known as the member's willingness information, it is used to indicate whether the UE is willing to be the head of a certain team, whether it is willing to be a member of a certain team, and whether it is willing to withdraw from a team. In the process of establishing and updating a fleet, based on the vehicle's willingness information, the network or the vehicle itself can determine whether it is possible to construct a fleet and become a front, or can determine whether the vehicle is willing to join or exit a fleet. The premise of the network's judgment is that the network has been informed of the vehicle's willingness information.

Fleet-related information: Also known as group-related information, including one or more of the following information: fleet identification information, fleet status information, fleet member information, fleet open information, fleet safety information, fleet internal identification.

The team identification information: also referred to as group identification information, this identification information may be pre-stored in the Vehicle UE (such as the UE's Universal Integrated Circuit Card (UICC)), or may be sent to the vehicle by the network. Includes one or more of the following information:

Application Layer Group ID: Uniquely identifies a group. Typically, each fleet has a different Application layer group ID within a PLMN. The same Application layer group ID is allowed in different PLMNs.

Layer 2 group ID (ProSe Layer-2 Group ID) for D2D communication

ProSe Group IP multicast address for D2D communication

The source IPv4 or IPv6 for that group used by the UE (Indication whether the UE should use IPv4 or IPv6 for that group)

Fleet status information: Also referred to as group status information, including one or more of the following information: direction, speed, acceleration, forward destination, etc. of the fleet.

Fleet safety information: Also known as group security information, group security related content required for group communication, such as security key for group communication. The content of the group communication can be encrypted with the security key, which can be used for application layer encryption of V2V message packets for direct communication between the fleet members within the fleet.

Fleet open information: Also known as group development information, whether the team allows vehicles outside the fleet to join, the front can open information to nearby broadcast fleets, and nearby vehicles can determine whether they are allowed to join the fleet after receiving the information. For example, if the team open information is set to off, nearby vehicles will not request to join the team.

Team member information: also referred to as group member information, including the identification of the first team member (ie, vehicle identification information) and the identification of all second team members (ie, vehicle identification information), and may also include: first team members The corresponding internal identification of the team and the internal identification of the team corresponding to the second team member.

The internal logo of the team: also known as the internal logo of the group, refers to the unique identification of the members of the team within a fleet. Since the number of team members in a fleet is not too large (eg, a team of up to 32 team members), 5 bits can be used to uniquely identify each vehicle in a fleet. The byte/bit required for the existing UE ID is very long, and the internal identification of the fleet can be identified with few bits, which is relatively efficient. Further, for the front of the car can be identified by member = 0, other team members for member = 1, 2, ... 31 to identify in turn. In order to preserve future scalability, up to 64 team members can use 6 bits to uniquely identify a unique identity of a fleet. The use of fleet internal identification in addition to the above mentioned savings in identifying the byte/bit overhead of a particular vehicle also allows for direct communication between individual fleets within the fleet without having to consider the effects between multiple PLMNs. In particular, when direct communication between the various fleet members within the fleet takes advantage of dedicated communications resources within the fleet, that is, the direct communication between the various fleet members in the fleet is different from the resources of the fleet members and the outside vehicles of the fleet. Resources, at which point each team member uses the team's internal logo.

Nearby vehicles: Also known as nearby members, vehicles near a certain fleet. When a fleet is established, the front of the vehicle can broadcast the status information and fleet identification information of the fleet nearby. After receiving the above information from the front of the vehicle, the nearby vehicle can determine that there is a fleet near it and the vehicle becomes a nearby vehicle. When a team is established, if the team is within the network coverage, the network can also know the presence of the team and notify the vehicle near the team. When a vehicle judges that it is a nearby vehicle of a certain fleet, that is, after the vehicle is in the vicinity of a fleet, it can evade the fleet while it is driving, and can also request to join the fleet.

The establishment process of the fleet can be understood to include the initial establishment process of the fleet and the joining process of the first nearby vehicle. After the team's establishment process is completed, a fleet consists of a single head and at least one team member. And then the second second, third... nearby vehicles joined the team to become a team member can be considered as the team's update process.

The formation process of the team can also be understood as including only the initial establishment process of the team. At this time, although the team has been established, there is only one head but no team members. Subsequently, joining the team from the first nearby vehicle to become a member of the team to the second, third... nearby vehicles joining the team to become a team member can be considered a renewal process for the team.

There is a team that includes a front and one or more team members. The status information of the front-end broadcast fleet, all the cars broadcast their own status information (meaning: the front-end broadcast fleet and its own status information, the front also broadcasts navigation information), all cars receive V2V messages from the front and team members.

After the team is established or updated, the first team member or the second team member sends a message to the surrounding, including one or more of the following information: fleet identification information, fleet status information, fleet open information, fleet private information, and the like.

After the team is established or updated, the first team member sends a message to the second team member, which includes one or more of the following information: fleet identification information, fleet status information, fleet safety information, fleet member information, and may also include: the fleet Open information and private information about the team.

The team's exit process is: When a team has a team member leaving the team, or a nearby vehicle joins the team, or the team's speed is increased, resulting in an increase in the distance between the cars, so that one or more team members must leave the team. The join/exit triggered by the team members needs to be allowed by the front/network.

The team joins the process: the team (the front or a car, or the rear of the car) broadcasts the fleet status information (V2V, delay requirements are not high), including: the location, speed, direction of the team, the team allows new cars to join, the front Destination, etc. After receiving a nearby car, it is judged that there is a team nearby and the new car is allowed to join, and it is also willing to join the team itself. After the car communicates with the front of the car, the car head decides whether to allow it.

Vehicles in the vicinity of the fleet broadcast their own status information. The front of the fleet can be (directly or indirectly) or there is a vehicle in the vicinity of the fleet that matches the team. After the vehicle head communicates with the vehicle, the front of the vehicle decides whether to allow it.

The management of the team mainly includes the establishment of the team, the update process of the nearby vehicles joining the team and the renewal process of the team members leaving the team. It is mainly completed by the application layer or by the layer 2. The management of the team includes the following steps:

First, a vehicle builds a fleet and becomes a member of the first team;

Here, under the network coverage, a vehicle requests to establish a fleet from the network. After the network agrees to establish a fleet, the team establishes the vehicle to become the first team member. Outside the network coverage, a vehicle builds a fleet through the interior of the vehicle based on pre-configured information or information obtained from the network as it is covered by the network and becomes a front.

When a fleet is established, the front of the car broadcasts a message to the surrounding, including information about the fleet (eg, fleet status information and/or fleet identification information).

Secondly, nearby vehicles joined the team and became members of the second team;

Here, the nearby vehicle determines whether or not to join the fleet by receiving a broadcast message sent by the front of the vehicle or by receiving the fleet information transmitted by the network under the network coverage.

If a nearby vehicle decides to join the fleet, the nearby vehicle sends a request message to join the fleet to the front or network (only for network coverage), and the front or network sends a response/reject message to the vehicle that allows/denies to join the fleet.

Under network coverage, when a nearby vehicle joins the fleet, the vehicle head interacts with the network information to update the fleet's fleet members information simultaneously, and the fleet's fleet safety information can also be updated.

Again, a second team member withdraws from the team;

Here, if the second team member judges that he is allowed to exit the team and is willing to withdraw from the team (according to the team status information, the vehicle status information of the second team member, the willingness information of the second team member), to the front or the network (only for Under the network coverage, a request message to exit the fleet is sent, and the front or network sends a response/reject message to the vehicle to allow/reject to exit the fleet.

Under network coverage, when a nearby vehicle exits the fleet, or after the vehicle head interacts with the network information to update the fleet's fleet members information, the fleet's fleet safety information can also be updated.

It should be noted that the process of joining or withdrawing the vehicle from the vehicle can also be completed through communication within the fleet. This is because within a fleet, the front of the vehicle is responsible for the group management of the team (eg, member joining/exiting and head replacement). ) and the team's navigation, driving, etc.

When the network is a V2X control Function, the team members (including the first team member and the second team member) interact with the network (the information interaction means that the team members send messages to the network, and the team members receive the network to send the message. The message) can be implemented via the PC3 interface.

The following describes the process of establishing and updating a fleet under network coverage and the process of establishing and updating a fleet without network coverage.

Under the network coverage, during the team's establishment/update process, the vehicle interacts with the network to form a fleet. When a vehicle has the ability to act as a front (according to its own vehicle capability information) and the vehicle is willing to establish a fleet (according to its own vehicle willing information), the vehicle interacts with the network to establish a fleet. After the establishment of a fleet, the vehicle became the first team member of the team. Nearby vehicles are informed that the team can apply to join the team. 5-1 is a schematic flowchart of an implementation process of establishing and updating a fleet within a network coverage according to an embodiment of the present invention. As shown in FIG. 5-1, the process of establishing and updating a fleet under network coverage includes the following steps:

In step S511, the UE1 sends a setup fleet group message to the V2X Function.

Here, the premise is that UE1 is willing to act as a platoon manager. UE1 first sends a create platoon group message to the V2X Function through the PC3 interface through the user plane message, wherein the create platoon group message includes an willing to form a platoon, and is willing to become a manager (intention) To be a leader).

Step S512, the V2X sends the fleet group configuration information to the UE1.

Here, after receiving the create platoon group message, the V2X Function authenticates the UE1 and determines whether the platform is allowed to be established. If allowed, the application layer group identifier, ProSe layer-2 group ID, and ProSe Group IP multicast address are assigned to the UE1. The source IPv4 or IPv6 address used by the UE (optional, it is possible that the core network has been allocated before the UE accesses the network), and the group security related content required for group communication.

Step S513, the UE1 broadcasts the fleet group information to the nearby vehicle according to the received fleet group configuration information;

Here, after UE1 receives the fleet group configuration information, UE1 acts as a platoon manager, periodically broadcasts a platoon advertisement (ie, Mode1 discovery), or according to the received fleet discovery request of the surrounding UE (platoon discovery) Request), by replies to the platoon discovery response (Mode 2 discovery). In the platform advertisement or the platoon discovery response, the UE1 (that is, the platoon manager UE) may carry the application layer group identifier, the platoon indication, the manager indication, the current state of the platoon, and the PLMN corresponding to the platform manager.

Step S514, after the UE (UE2) who is willing to join the platoon receives the platoon advertisement or the platoon discovery response, it determines that it is willing to join the team group;

Step S515, the UE2 sends a join platoon group request message to the V2X Function.

Here, the UE2 sends a join platoon group request message to the V2X Function through the PC3 interface, which includes the application layer group identification information obtained by the UE2 from the platoon advertisement or the platoon discovery response message, and whether the UE2's own ProSe UE ID supports the relay to the RSU. , RSU's ProSe Layer-2 UE ID, etc.

Step S516, the V2X Function sends the fleet group configuration information to the UE2.

Here, after receiving the join platoon group request message, the V2X Function performs authorization authentication on the UE2. If it is confirmed that the UE2 can join the platoon group corresponding to the application layer group identifier, the V2X Function sends the join team to the UE (UE2) that wishes to be called the platoon member. A join platoon group response message, where the join platoon group response message includes a ProSe layer-2 group ID corresponding to the platoon group, a ProSe Group IP multicast address, a source IPv4 or an IPv6 address used by the UE2 (optional, It is possible that the core network has been allocated before UE2 accesses the network), and the group security related content required for group communication. In addition, optionally, the V2X Function may send a platoon update message containing the ProSe UE ID of the newly added member to the UE2 (platoon manager UE), indicating that a new member joins.

Step S517, UE1 and UE2 perform D2D multicast communication.

Here, after receiving the join platoon group response message, the UE2 (the UE that wants to join the Platoon) can use the ProSe layer-2 group ID, the ProSe Group IP multicast address, and the group security related content to be secure with the UE1. D2D multicast communication. Correspondingly, once the UE1 (platoon manager) finds that a member has joined the platoon, it can start to adopt a unified exercise decision, such as which way to go, whether to brake or accelerate.

If a platoon member wants to leave, you can send a leave platoon group message to the V2X Function. The V2X Function updates the member information in the platoon group, and sends the platoon configuration update information to the platoon manager and other platoon members through the PC3 interface. Further, if the UE executing the platoon manager wants other UEs to act as the platoon manager, the platoon manager may also send an update indication to the V2X Function for replacement of the platoon manager.

Outside the network coverage (ie no network coverage), the vehicle builds a fleet based on pre-configured information to become a first team member or a second team member. FIG. 5-2 is a schematic flowchart of an implementation process of establishing and updating a network coverage external fleet according to an embodiment of the present invention. As shown in FIG. 5-2, the process of establishing and updating a network coverage external fleet includes the following steps:

Step S521, the UE1 establishes a fleet group according to the pre-configured fleet group related information;

Here, it is first necessary to ensure that UE1 itself is willing to act as a platoon manager. The UE1 can perform the information distribution of the platoon group according to the pre-configured platoon group information or the UE according to the built-in V2X AS Server function, such as the application layer group identifier, the ProSe layer-2 group ID, the ProSe Group IP multicast address, and the UE1. Source IPv4 is also an IPv6 address, group security related content required for group communication.

Step S522, the UE1 periodically broadcasts the platoon advertisement information;

Step S523, after receiving the message, the surrounding UE2 decides to join the group,

Step S524, UE2 sends a unicast message to UE1 (reusable direct communication request message), indicating that it wishes to join the platoon group;

Step S525, after receiving the message, the UE1 performs the fleet joining control;

Here, the UE1 determines whether the fleet group can also accept the platoon member UE2.

In step S526, if admission is allowed, a one-to-one secure connection is first established between the UE1 and the UE2, and then the UE1 sends the configuration information of the platoon group to the UE2 through the secure connection.

In step S527, UE1 and UE2 can exchange platoon related information through group communication, and can perform unicast side link communication.

The prerequisite for establishing a fleet is that there are two or more vehicles, and one of these vehicles has the willingness to be the front and the vehicle has the capability of V2I and V2V communication, and the other vehicles have at least V2V communication capability. All vehicles in the fleet (including the front and team members) need to support V2X applications (V2X applications) and support V2X communication (V2X communication). When these vehicles are very close and running in the same direction and at the same speed, a fleet of vehicles can be established by interacting with each other's information (in the case of network coverage, with the help of the network).

A vehicle with a V2X application and supporting V2X communication transmits its own status information to nearby vehicles and receives status information of nearby vehicles. Within the network coverage, these vehicles also maintain communication with the network and can obtain status information of nearby fleets and/or vehicles via the network, and obtain help information for establishing/joining/exiting the fleet through the network.

The prerequisites for establishing a fleet include at least the following conditions:

1) There are 2 or more vehicles, and the vehicle status information of these vehicles is the same (distance, same running direction, similar speed, same destination in front), these vehicles support V2X application (V2X application) and support V2X Communication (V2X communication);

2) All vehicles have at least V2V communication capability, and vehicles that are willing to become the front of the vehicle have V2V communication capability and V2I communication capability;

3) At least one of these vehicles has the ability to have a front and is willing to be the front;

4) These vehicles have the willingness to establish or join a fleet.

5) The establishment of the fleet includes three methods: network decision, network assistance and no network coverage.

Example 7

The embodiment of the present invention provides a method for initial establishment of a fleet of vehicles. The scenario for initial establishment of a fleet of vehicles provided by the network in the case of a network coverage and a network-controlled initial establishment process includes the following steps:

Step 1. The first team member sends a request message to the network, and the request message is used to establish a fleet;

Here, the request message includes one or more of the following information: vehicle state information, vehicle identification information, vehicle capability information, vehicle willing information, vehicle private information, and application layer group identification.

The application layer group identifier is used to notify the network of the application layer group identifier of the fleet that the UE wants to establish. That is to say, the network uses the application layer group identifier sent by the UE as the application layer group identifier of the fleet.

When the vehicle private information is included, it means that the subsequent vehicle requesting to join the fleet needs to have the same vehicle private information as the first team member.

When the vehicle's willingness information in a request message sent by a certain vehicle to the network indicates that the vehicle is willing to be the front of the vehicle, the vehicle is the first team member.

Step 2: The network sends a response message or a rejection message to the first team member;

Here, after receiving the request message from the first team member, the network authenticates the first team member according to the request message, determines whether to allow the team to be established, and if so, sends a response message to the first team member, agreeing Create a fleet; otherwise send a rejection message and refuse to establish a fleet.

It should be noted that the authentication is performed by information exchange between network elements of the network to determine whether the vehicle is allowed to establish a fleet.

The response message includes one or more of the following information: fleet identification information, fleet safety information, front interior identification, fleet private information.

The team's private information is the vehicle's private information for the first team members. When the network agrees to establish a fleet, the vehicle's private information sent by the front is the team's private information, and the vehicle's private information for the nearby vehicles requesting to join the team must be the same as the fleet's private information.

Step 3, the first team member sends a message, including information about the team;

Here, when the first team member receives the response message from the network, it knows that it has become the head of a certain team, and knows the relevant information of the team, and then the first team member sends a message.

The message includes the first team member sending the team related information to the surrounding vehicle/pedest (in the embodiment of the present invention, the message 1), and may also include the first team member sending the team related information to the nearby RSU (abbreviated in the embodiment of the present invention) Message 2).

Message 1 is sent for the purpose of notifying nearby vehicles of the presence of the fleet and notifying nearby vehicles whether or not to join the fleet. Message 1 includes one or more of the following information: fleet identification information, fleet status information, fleet private information, fleet open information. But generally, it does not include: fleet member information and fleet safety information. The purpose of message 2 is to let RSU know the existence of the team, generally including: fleet identification information, fleet status information, fleet private information, fleet open information, fleet member information, fleet safety information. In general, however, fleet safety information will not be included. The message 1 includes at least two parts from the content. One part includes fleet status information so that nearby vehicles know the presence of the fleet and avoid the fleet while driving, and the other part includes fleet identification information and fleet opening information to help nearby vehicles know whether the fleet allows nearby vehicles to join the fleet and Whether the nearby vehicle itself can join the fleet.

For example, as shown in the figure, the message may also be that after the first fleet member receives the platoon discovery request message sent by the nearby vehicle (Vehicle UE), the repoon discovery response is broadcasted by the broadcast, similar to the D2D Mode2 discovery in the existing LTE technology. .

Message 1 is generally a V2V message, which can be sent in broadcast mode or in unicast mode. Generally, it is transmitted in a broadcast mode.

The network can decide whether or not the message 1 is sent, and the period when the message 1 is transmitted in the broadcast mode. Specifically, the network may decide whether the first fleet member needs to send the fleet message based on whether there is a vehicle near the fleet. That is, when the network determines that there are no vehicles/pedestrians near the fleet, the network can notify the first team member not to send the fleet message. In summary, the network can instruct the first member to send or stop sending the fleet message, as well as the period when the broadcast transmission mode is employed.

After the initial establishment of the team, a team has been initially established, but only one of the team has no other team members. Subsequently, the team can have a second team member through the joining process of nearby vehicles, at which time the team is completed.

After the team is established, the first team member and/or the second team member sends a message to the surrounding, including one or more of the following information: fleet identification information, fleet status information, fleet open information, fleet private information, and the like.

After the team is established, the first team member sends a message to the second team member, which includes one or more of the following information: fleet identification information, fleet status information, fleet safety information, fleet member information, and may include: fleet open information And private information about the team.

Example eight

The embodiment of the present invention further provides a method for initial establishment of a fleet, which is applied to a scenario of an initial establishment process of a fleet without network coverage. The initial establishment method of the fleet provided by the embodiment of the present invention includes the following steps:

Step 1. The first team member sends a message to the surrounding area.

Here, the message is generally transmitted in a broadcast mode or in a unicast mode; the message includes one or more of the following information: fleet identification information, fleet status information, fleet open information, fleet private information.

In the absence of network coverage scenarios, the vehicle's private information for the first team members is the fleet's private information.

In the absence of coverage, the UE that is willing to act as the front (ie: the first team member) needs to have pre-configured fleet identification information, which may be pre-configured by the first fleet member or when it has network coverage. The network (eg, the vehicle networking application server, V2X control Function) is obtained.

The first team member periodically broadcasts the platoon advertisement message, and the period may be a fixed value applicable to the network coverage, or it may be obtained from the network under the network coverage.

The first team members may also not send the above message, for example, when the first team member knows that there is no vehicle nearby.

The method for establishing a fleet provided by the embodiment of the present invention is applicable to a fleet establishment process outside the network coverage. Compared with the vehicle establishment and update in the network coverage, the initial establishment process of the network coverage team is very simple, that is, a certain vehicle is completed by the internal implementation of the vehicle according to the pre-configured fleet identification information, and does not need to be completed with other Information exchange of vehicles. Once a vehicle itself determines that it is a member of the first fleet, it broadcasts fleet information to the perimeter.

Example nine

Embodiments of the present invention provide a method for updating a fleet of vehicles, which is applied to a vehicle that has network coverage and is controlled by a network to join a process scenario. The fleet updating method provided by the embodiment of the present invention includes the following steps:

Step 1. The nearby vehicle knows the fleet information and sends a request message to the network to join the team;

Here, a nearby vehicle refers to one or some vehicles in the vicinity of the fleet. After receiving the platoon advertisement or platoon discovery response, the nearby vehicle judges whether the team allows the new car to join and whether it joins the team. If so, the nearby vehicle sends a join platoon group request message to the network.

The request message includes one or more of the following information: vehicle identification information (eg, platoon group ID, UE's own ProSe UE ID), vehicle status information, vehicle private information, and application layer of the vehicle. Group ID, whether to support relay to RSU, RSU ProSe Layer-2 UE ID.

Step 2: The network sends a response message or a rejection message to the nearby vehicle to join the team;

Here, after receiving the join platoon group request message sent by the nearby vehicle, the network determines whether, if it is allowed to join the fleet, sends a join platoon group response message to the nearby vehicle, otherwise the sending refuses to join. Join platoon group reject message

The network determines whether the nearby vehicle is allowed to join the vehicle with one or more of the following conditions: whether the vehicle private identification of the nearby vehicle is consistent with the vehicle private identification, the application layer group identification information of the vehicle of the nearby vehicle, and the fleet application layer of the fleet Whether the identification information is consistent, whether the vehicle status information of the nearby vehicle is consistent with the fleet status information of the fleet, and whether the fleet open information of the fleet allows nearby vehicles to join.

For example, the network judges whether the application layer group identification of the fleet and nearby vehicles is consistent.

When the network determines that a nearby vehicle is allowed to join the fleet, the network sends a response message to the nearby vehicle that is allowed to join the fleet. The message includes one or more of the following information: fleet identification information, fleet status information, fleet member information, fleet private information, fleet safety information.

After the nearby vehicle was allowed to join the team, it became the second team member of the team. The second team member refers to a team member other than the front of the car.

Step 3: The network sends a platoon update indication message to the first team member;

Here, the network sends a fleet update indication message to the first fleet member when the network allows nearby vehicles to join the fleet.

The fleet update indication message includes a vehicle identification information identifier of the second team member (a nearby vehicle newly joined to the fleet), and further includes: status information of the second team member.

Step 4: The first team member sends a platoon update indication acknowledge message to the network;

Here, if the network does not receive the update indication confirmation message sent by the first team member, the network needs to continuously perform step 3 until the network receives the confirmation message to ensure that the first team member receives the fleet update indication message.

It should be noted that the foregoing step 2 and step 3/4 may be that the network first informs the front of the vehicle to update the fleet (for example, the team member updates), and then sends a join confirmation message to the nearby vehicle. In doing so, at least one advantage is to let the front of the car know that the nearby vehicles are about to join the team, so that the front of the team can update the team members' information and adjust the new team navigation instructions as soon as possible.

After the fleet is updated, the first team member and/or the second team member sends a message to the surrounding, including one or more of the following information: fleet identification information, fleet status information, fleet open information, fleet private information, and the like.

After the fleet is updated, the first team member sends a message to the second team member, which includes one or more of the following information: fleet identification information, fleet status information, fleet safety information, fleet member information, and may include: fleet open information And private information about the team.

Example ten

The embodiment of the present invention further provides a method for updating a fleet, which is applied to a scenario in which a vehicle coverage is controlled by a first team member (a vehicle head). The vehicle renewal method provided by the embodiment of the present invention includes the following steps:

Step 101: The nearby vehicle knows the fleet information, and sends a request message to the front of the vehicle to join the team;

Here, a nearby vehicle refers to one or some vehicles in the vicinity of the fleet. After receiving the platoon advertisement or the platoon discovery response, it is judged whether the team allows the new car (nearby vehicle) to join and whether or not to join the team, and if so, the nearby vehicle sends a join platoon request message to the front of the vehicle (join platoon group request message)

The request message includes one or more of the following information: vehicle identification information (eg, platoon group ID, UE's own ProSe UE ID), vehicle status information, vehicle private information, whether to support relay to RSU, RSU ProSe Layer-2 UE ID.

Step 102: The front end sends a response message or a rejection message to the nearby vehicle to join the vehicle fleet;

Here, after the front of the vehicle receives the join platoon group request message sent from the nearby vehicle, it is judged that if the team is allowed to join the team, a join platoon group response message is sent to the nearby vehicle; otherwise, the message is sent. Refuse to join the team's join platoon group reject message.

The determination condition that the front head determines whether the nearby vehicle is allowed to join the vehicle has one or more of the following conditions: whether the private identification of the vehicle of the nearby vehicle is consistent with the private identification of the vehicle, and whether the application layer group identifier of the nearby vehicle is consistent with the identification of the fleet application layer group. Whether the vehicle status information of the nearby vehicle is consistent with the fleet status information of the fleet, and whether the fleet open information of the fleet allows nearby vehicles to join.

For example, the front end is judged based on the platoon group corresponding to the application layer group identification of the fleet and nearby vehicles. For example, does the platoon group ID of the vehicle match the platoon group ID of the fleet.

When the front of the vehicle judges that the nearby vehicle is allowed to join the fleet, the front of the vehicle sends a response message to the nearby vehicle that is allowed to join the fleet. The message includes one or more of the following information: fleet identification information, fleet status information, fleet member information, fleet private information, fleet safety information.

The acknowledgment message includes one or more of the following information: ProSe layer-2 group ID, ProSe Group IP multicast address, source IPv4 or IPv6 address used by the UE (optional, it is possible that the core network has been allocated before the UE accesses the network) Over), fleet safety information.

After the nearby vehicle was allowed to join the team, it became the second team member of the team. The second team member refers to a team member other than the front of the car.

Step 103, the front end sends a platoon update indication message to the network;

When the front of the car allows nearby vehicles to join the fleet, the front of the car sends a fleet update indication message to the network.

The fleet update indication message includes a vehicle identification information identifier of the second team member (a nearby vehicle newly joined to the fleet), and further includes: status information of the second team member.

Step 104: The network sends a platoon update indication acknowledge message to the front of the vehicle.

If the front end does not receive the update indication confirmation message sent by the network, the front end needs to continuously perform step 103 until the network receives the confirmation message to ensure that the first fleet member receives the fleet update indication message.

It should be noted that the foregoing step 102 and step 103/104 may be that the network first informs the front of the vehicle to update the fleet (eg, the team member updates), and then sends a join confirmation message to the nearby vehicle. In doing so, at least one advantage is to let the front of the car know that the nearby vehicles are about to join the team, so that the front of the team can update the team members' information and adjust the new team navigation instructions as soon as possible.

When a nearby vehicle joins the team, a fleet can be established with only one front and at least one team member.

Embodiment 11

The embodiment of the present invention provides a method for updating a fleet, which is applied to a scenario in which the vehicle participation process is controlled by the first team member (the front). The vehicle fleet updating method provided by the embodiment of the present invention includes the following steps:

Step 111, the nearby vehicle sends a request message to the first team member to join the team;

Here, the nearby nearby vehicle receives the message sent by the first team member, decides to join the team, and then sends a join team request message to the first team member.

The request message may be sent to the first fleet member in a unicast transmission mode; the request message may also be in the form of a direct communication request message.

The request message includes one or more of the following information: vehicle identification information, vehicle status information, application layer group identification, vehicle private information.

The premise that the nearby vehicle sends the request message is that the nearby vehicle thinks that it can obtain the permission to join the front of the vehicle, and the judgment condition has one or more of the following conditions: the fleet allows nearby vehicles to join, and the vehicle state of the nearby vehicle is similar to the fleet status, and the nearby vehicle There is a willingness to join the team, and nearby vehicles determine that their vehicle private information is the same as the fleet's private information.

Step 112: The first team member sends a response message or a rejection message to the nearby vehicle to join the team;

Here, the first team member receives a join request message from a nearby vehicle to determine whether the vehicle is allowed to join. If so, a response message allowing admission to the fleet is sent to the nearby vehicle, otherwise a rejection message not allowed to join the fleet is sent.

The first team member judges whether to allow nearby vehicles to join the team. The judgment condition has one or more of the following conditions: whether the vehicle identification information of the nearby vehicle and the vehicle private information have the same application layer group identification and fleet private information as the fleet (eg: Whether it is the same transportation company, whether it is the same application layer group identification), whether the vehicle status information of the nearby vehicles is similar or identical to the fleet status information, whether the fleet allows nearby vehicles to join (ie: the fleet allows nearby vehicles to join).

When the first team member allows the nearby vehicle to join, a response message to the nearby vehicle is allowed to join the fleet, the message being sent via a one-to-one (P2P) point to point unicast message. And the response message includes fleet member information and fleet safety information.

Optionally, after receiving the response message, the nearby vehicle becomes a second team member and sends a confirmation message to the first team member to join the team.

Optionally, after the first team member sends the response message, the broadcast message of step 1 needs to be updated, such as: the open state of the fleet.

Example twelve

Embodiments of the present invention provide a method for updating a fleet of vehicles, which is applied to a scenario in which a network coverage is controlled by a network and a second team member exits the process. When the vehicle within the fleet wishes to exit the fleet, the second team member in the fleet exits the fleet. The fleet updating method provided by the embodiment of the present invention includes the following steps:

Step 121: The second team member sends a request message to the network to exit the team;

Here, the second team member communicates internally with the first team member and other second team members, and the second team member communicates with the network. When the second team member knows that the team allows the vehicle to leave and wants to leave the fleet (ie, exit the team), a request message to exit the fleet is sent to the network.

In some special circumstances, such as: the team is driving on a one-way street or on a road that is prohibited from overtaking, the front or the network does not allow the team members to withdraw from the team. At this time, the second team member can know from the front or the network that the team is not allowed to withdraw. The team.

When the second team member can learn from the front of the car or from the network that the team is allowed to exit the team and leave the team itself, such as: the second team member changed the original forward destination.

It should be noted that the team members requesting to quit must be members of the second team, not the first team members. If the team member is the first team member, they need to interact with other second team members (and also have network participation), making it a second team member to allow the team to exit. Otherwise, once the first team member exits the team, it means the team's disbandment.

In short, the second team member sent a message to the network to withdraw from the team, must meet three conditions: the team members are not the first team members, the team allows the team members to withdraw from the team, the team members themselves want to exit the team.

For example, the second team can send a leave platoon group message to the V2X Function, the V2X Function updates the member information in the platoon group, and sends the platoon configuration update information to the platoon manager and other platoon members through the PC3 interface.

Step 122: The network sends a response message or a rejection message to the second team member to withdraw from the fleet;

Here, it should be noted that steps 123 and 124 are performed when step 122 is a response message allowing the exit of the fleet; and in step 122, the rejection message of the vehicle is refused to exit, the flow is terminated.

Step 123: The network sends the fleet update indication information to the first team member.

Here, the fleet update indication message is used to indicate that a fleet member has exited in the fleet. The fleet update indication message includes at least a vehicle identification information identifier (ProSe UE ID) of the exited second team member.

In step 124, the first team member sends a fleet update indication confirmation message to the network.

Here, if the network does not receive the update indication confirmation message sent by the first team member, the network needs to continuously perform step 123 until the network receives the confirmation message to ensure that the first team member receives the fleet update indication information.

It should be noted that the order of execution of the above step 122 and steps 123 and 124 may be interchanged. That is to say, it may be that the network first informs the front of the vehicle to update the fleet (for example, the team member updates), and then sends a join confirmation message to the nearby vehicle. In doing so, at least one advantage is to let the front of the car know that a team member is about to leave the team, so that the front of the team can update the team members information and adjust the new team navigation instructions as soon as possible.

After the fleet is updated, the first team member/second team member sends a message to the surrounding, including one or more of the following information: fleet identification information, fleet status information, fleet open information, fleet private information, and the like.

After the fleet is updated, the first team member sends a message to the second team member, which includes one or more of the following information: fleet identification information, fleet status information, fleet safety information, fleet member information, and may include: fleet open information And private information about the team.

Example thirteen

Embodiments of the present invention provide a method for updating a fleet of vehicles, which is applied to a scenario in which a network coverage is covered by a first team member (a vehicle head) to control a second team member exit process, and when the vehicle within the fleet wishes to exit the vehicle fleet, the vehicle fleet is executed. The second team member exits the fleet process. The fleet update method provided by the embodiment of the present invention includes the following steps:

Step 131, the second team member sends a request message to the first team member to withdraw from the team.

Here, the second team member sends out the team request message, the preconditions are the same as those in the other embodiments, and will not be described here.

Step 132: The first team member sends a response message or a rejection message to the second team member to withdraw from the team;

Here, in steps 131 and 132, communication between the first fleet member and the second fleet member can be directly communicated using V2V. Similar to the prior art PC5 interface, the first fleet member and the second fleet member can communicate using the fleet internal identity.

It should be noted that steps 133 and 134 are performed when step 132 is to allow the response message to exit the fleet; when the rejection message of the team is refused to exit in step 2, the process ends.

Step 133: The first team member sends the fleet update indication information to the network;

Step 134: The network sends the fleet update indication confirmation information to the first team member;

Here, if the first team member does not receive the update indication confirmation message sent by the network, the first team member needs to continuously perform step 133 until the network receives the confirmation message to ensure that the network receives the fleet update indication information.

When a second team member withdraws from a team, the team safety information may also need to be updated.

Embodiment 14

Embodiments of the present invention provide a method for updating a fleet of vehicles, which is applied to a scenario in which no network coverage is covered by a first team member (a vehicle head) to control a second team member exit process, and when the vehicle within the fleet wishes to exit the fleet, the first team is executed. The second team member exits the fleet process. The fleet update method provided by the embodiment of the present invention includes the following steps:

Step 141, the second team member sends a request message to the first team member to withdraw from the team;

Here, the second team member sends the exiting fleet request message, and the preconditions are the same as those in the other embodiments, and are not described herein again.

Step 142: The first team member sends a response message or a rejection message to the second team member to withdraw from the team;

Here, the first team member can allow or deny the exit of a certain second team member based on the judgment (the judgment process is the same as the other embodiments).

When a second team member exits a fleet, the team's fleet status message, fleet open information, etc. may change, so that, subsequently, the first team member sends an updated message to the perimeter. When a second team member withdraws from a team, the team's team safety information also needs to be updated, so the first team members also need to send new team safety information to the other members of the team.

Example fifteen

Embodiments of the present invention provide a method for updating a fleet, which is applied to a scenario in which a network coverage and a network-controlled fleet disbanding process is used, when a fleet no longer has a fleet use, or no team members are willing/have the responsibility of the front, Can disband a team. One or more of the following conditions are required to disband a team: the current first team member is unwilling/cannot assume the head duties and no other team members (second team members) are willing/can afford the head duties, ie no in the team The front of the car; there is no second team member in a team, that is: there is only one front; the team that the front/network itself judges is disbanded. The fleet updating method provided by the embodiment of the present invention includes the following steps:

Step 151: The first team member sends a request message for dissolving the team to the network;

Here, in some specific scenarios, such as one-way streets, the first team members are not allowed to send a request message to disband the team. When the front of the car thinks that the team members do not have the same forward destination, or there is no identical vehicle willing information, the front can send a request message.

In the request message, one or more of the following information is included: fleet identification information, fleet member information

Step 152: The network sends a response message or a rejection message of the disbanding team to the first team member;

Here, when the network does not allow the front to disband a fleet, such as a one-way street, a rejection message is sent; when the network allows the front to disband a fleet, a response message is sent, with the vehicle identification information carried in the response message.

In step 153, the network or the first team member sends an instruction message to the team member to disband the team.

Here, when the fleet is allowed to disband, the message is sent, including the fleet identification information. The message may be sent by the network or by the first team member.

When a fleet is allowed to disband, it may be notified by the network through point-to-point special signaling that each second team member is disbanded; or the second team member may be notified by the front of the second V2V message that the team is Disbanded.

Example sixteen

The embodiment of the present invention provides a method for updating a fleet of vehicles, which is applied to a scenario of a vehicle fleet disbanding process with network coverage and controlled by a first team member. The fleet updating method provided by the embodiment of the present invention includes the following steps:

Step 161, the first team member sends an instruction message to the team members and the network to disband the team;

Here, the first team members themselves determine whether or not they want to disband a team. The judgment conditions are the same as those of the other embodiments. The instruction message for disbanding the fleet includes at least: fleet identification information.

When a fleet is allowed to disband, the front of the car informs the network that the team is disbanded through point-to-point private signaling; when a fleet is allowed to disband, the front of the car passes the V2V message informing each second team member that the team is disbanded.

Example seventeen

The embodiment of the present invention provides a method for updating a fleet, which is applied to a scenario of a fleet disarming process that is not covered by the network and is controlled by the first team member. The fleet updating method provided by the embodiment of the present invention includes the following steps:

Step 171: The first team member sends an instruction message to the second team member to disband the team;

Here, the first team members themselves determine whether or not they want to disband a team. The judgment conditions are the same as those in the other embodiments, and are not described herein again. The instruction message for disbanding the fleet includes at least: fleet identification information.

When a team was allowed to disband, the front of the car passed the V2V message, informing each second team member that the team was disbanded.

In the no-network coverage scenario, each vehicle (Vehicle UE) has no communication with the network, and each vehicle continuously broadcasts its own vehicle status information and vehicle identification information to the periphery. Each vehicle can receive vehicle status messages and vehicle identification information for nearby vehicles.

Just as each UE has a set of factory equipment parameters, each vehicle (Vehicle UE) is pre-configured with a set of vehicle equipment parameters (such as: UE ID, ProSe ID, PLMN ID, V2X Application ID). After the vehicle enters the network coverage, the vehicle can obtain new configuration parameters from the V2X Application server or V2X control Function, and use this parameter to override the factory configuration parameters of the vehicle UE.

In summary, each vehicle has a set of vehicle equipment parameters that can be used after the vehicle leaves the network coverage.

The messages mentioned in the team establishment and update in the no-network coverage scenario refer to V2V messages for direct communication between the vehicle and the vehicle.

Example 18

Embodiments of the present invention provide a method for establishing a fleet of vehicles, which is applied to a network-covered and network-controlled setup process. The vehicle fleet in the embodiment of the present invention includes a front end and at least one second fleet member.

Under the network coverage, each vehicle (Vehicle UE) maintains communication with the network, and the vehicle continuously reports its status information (such as location, speed, direction), and the network can grasp a certain area (such as: a certain highway) On the status information of all vehicles, the network will form a fleet of vehicles with similar distances, speeds and directions (similar), and designate one vehicle (usually the first one) as the front.

There are a number of cars in a location area, and the process of establishing a network coverage and network-controlled fleet is as follows:

First, the network knows the subscription information/status information/capability information of two or more vehicles in the location area;

Here, the network mentioned in the embodiment of the present invention and other embodiments may be a V2X control function, a V2X application server, or a core network.

The location area refers to a similar distance, such as a section of highway. When there are multiple cars in this area, these cars may form a fleet.

The signing information of the car means that the network can know whether the car supports V2X Application, PLMN information (such as: register PLMN, Equivalent Public Land Mobile Network (EPLMN), etc.).

The state information of the car means that the network can know the location, direction, speed and destination of the car.

The ability information of the car means that the network can know the V2I capability and the V2V capability of the car.

Second, these cars are willing to build/join a fleet, and one or more of these vehicles are capable and willing to be the front;

Here, the Vehicle UE that is willing to establish and join a team (Platoon) sends a create platoon group message to the network (eg, V2X Function) through the user interface message through the user plane message, which includes the interest to form a platoon message.

A Vehicle UE that is willing to establish and join a team (Platoon) and is willing to be the front of the vehicle sends a create platoon group message to the network (eg, V2X Function) via the PC3 interface, which includes an indication of interest to form a platoon, intention to be a leader.

Third, the network will constitute a fleet of vehicles that are consistent with the establishment of a fleet based on the preconditions for the establishment of the fleet;

Here, the network chooses a car as the front. After that, the network or the front of the team informs the team members of the team's fleet information.

FIG. 6 is a schematic diagram of an implementation process of a method for establishing a fleet of eighteenth embodiments according to an embodiment of the present invention. As shown in FIG. 6, the method includes the following steps:

Step S601, the network acquires related information of multiple vehicles,

Here, the related information of the vehicle may include: status information and capability information of the vehicle, and whether the vehicles are willing to establish/join the team, and whether the car is willing to be the front.

All vehicles report the vehicle's own status information, the vehicle's own capability information (including: V2I and V2V communication capabilities), and the vehicle's own willing information (whether it is willing to establish/join the fleet).

Vehicles with V2I and V2V communication capabilities report to the network whether they are willing to be the front.

Step S602, according to the preconditions for establishing the fleet, the network determines which vehicles meet the conditions for establishing a fleet;

Step S603, the network forms a vehicle with the qualified vehicle and selects a vehicle as the front, notifying the relevant vehicle,

Here, the network sends a message to a vehicle indicating that it becomes the front of the vehicle (optionally, the vehicle is required to move to the location of the first vehicle); the network sends fleet-related information to all vehicles.

Alternatively, in step S603, after the network constructs a fleet, the network may also notify the front of the vehicle, and the vehicle head transmits information about the fleet to all vehicles.

Vehicle-related information, mainly one or more of the following information: front information (such as: head ID), fleet information (such as: team logo), fleet member information (such as: ID of each team member), fleet key information , resource allocation for the internal communication of the team, driving information, etc.

Example 19

Embodiments of the present invention provide a method for establishing a fleet of vehicles, which is applied to a fleet building process with network coverage and being dominated by a vehicle. The vehicle fleet in the embodiment of the present invention includes a front end and at least one second fleet member.

Under the network coverage, each vehicle (Vehicle UE) maintains communication with the network, and the vehicle continuously reports its status information (such as location, speed, direction), and the network can grasp a certain area (such as: a certain highway) The status information of all the vehicles, the network informs each of the vehicles of the information, and the vehicle itself constitutes a fleet and selects a team member as the front.

There are a number of cars in a location area where the network coverage and vehicle-led establishment of the fleet is as follows:

First, the network knows the status/capability information of two or more vehicles in the location area;

Here, these cars are willing to build/join a team. One or more of these cars are capable and willing to be the front.

Second, the network knows that one or more vehicles in the location area are capable and willing to be the front;

Third, according to the preconditions for establishing a fleet, the network will notify the relevant vehicles of the vehicle information that meets the establishment of the fleet;

Fourth, all or part of these vehicles form a fleet and select a vehicle as the front;

Fifth, the front of the car informs the relevant vehicle about the team's information (the relevant vehicle is the second team member).

FIG. 7 is a schematic flowchart of an implementation process of a vehicle fleet establishment method according to Embodiment 19 of the present invention. As shown in FIG. 7, the method includes the following steps:

Step S701, the network acquires status information and capability information of the vehicle, and whether there is a car that is willing to become the front of the vehicle;

Step S702, according to the preconditions for establishing the fleet, the network determines which vehicles meet the conditions for establishing a fleet;

Step S703, the network notifies the relevant vehicle of the two or more vehicle information that meets the condition;

Here, in a certain location area, the network determines that several of the vehicles meet the conditions for establishing a fleet based on the reported information of the plurality of vehicles. The network informs these related vehicles of these information in accordance with the vehicles that make up a fleet.

Step S704, all or part of the vehicles constitute a fleet, and a vehicle head is generated autonomously;

Here, the vehicles that constitute a fleet are exchanged information with each other, such as the V2I capability of the vehicle, the willingness to join the team, all or part of these vehicles constitute a fleet, and one of the team members is selected as the front.

Step S705, the front of the vehicle informs the relevant vehicle of the vehicle related information;

Here, the relevant vehicle is a member of the fleet, and the front of the vehicle sends fleet information (including but not limited to the fleet identification ID, the front logo ID, the fleet member ID) to all team members.

Vehicle-related information, mainly one or more of the following information: front information (such as: head ID), fleet information (such as: team logo), fleet member information (such as: ID of each team member), fleet key information , resource allocation for the internal communication of the team, driving information, etc.

Example twenty

Embodiments of the present invention provide a method for establishing a fleet of vehicles, which is applied to a process of establishing a fleet without a network coverage. The vehicle fleet in the embodiment of the present invention includes a front end and at least one second fleet member.

In the no-network coverage scenario, each vehicle (Vehicle UE) does not communicate with the network, and each vehicle continuously broadcasts its own status information (location, speed, direction, etc.) to the periphery. Each vehicle receives a V2V message from a nearby vehicle and knows the status information of the nearby vehicle. The vehicles constituting a fleet are exchanged information with each other, all or part of which constitute a fleet, and a team member is selected as the head of the vehicle.

There are many cars in a certain location area, and there is no network coverage in the location area. The process of the vehicle building its own fleet is as follows:

Each vehicle sends its own status information to nearby vehicles;

Each vehicle receives status information of nearby vehicles;

Meet these vehicles in the formation of the team and exchange information with each other;

All or part of these vehicles form a fleet and select a front;

The front of the vehicle will inform the relevant vehicles of the relevant information of the team;

The updated related information mainly includes: front information (such as: head ID), fleet information (such as: team logo), fleet member information (such as: ID of each team member), fleet key information, fleet internal communication Resource allocation, driving information, etc.

FIG. 8 is a schematic flowchart of an implementation process of a vehicle fleet establishment method according to Embodiment 20 of the present invention. As shown in FIG. 8, the method includes the following steps:

Step S801, each vehicle transmits its own state information to the periphery; meanwhile, each vehicle receives state information of the surrounding vehicle;

Step S802, according to the preconditions for establishing the fleet, each vehicle determines whether it can form a fleet with the nearby vehicles;

Step S803, the vehicles constituting a fleet are mutually interacted with each other, and all or part of the vehicles constitute a fleet, and one team member is selected as the front of the vehicle;

Step S804, the front end notifies the relevant vehicle of the vehicle team related information;

Here, the fleet-related information mainly includes one or more of the following information: head information (eg: head ID), fleet information (eg, fleet logo), fleet member information (eg: ID of each team member), fleet confidentiality Key information, resource allocation for fleet internal communication, driving information, etc.

Embodiment 21

Embodiments of the present invention provide a method for updating a fleet of vehicles, which is applied to a scenario of exiting a fleet triggered by a second team member. FIG. 9 is a schematic flowchart of an implementation process of a twenty-first vehicle fleet updating method according to an embodiment of the present invention. As shown in FIG. 9, the method includes:

In step S901, a second team member determines that he or she meets the conditions for exiting the team;

Here, if the exiting fleet condition is satisfied, the process proceeds to step S902, otherwise, the process proceeds to step S907.

A team member decides to withdraw from the team according to preset conditions, such as: changing speed, direction, willingness, etc.

Step S902, the second team member sends a request message to the front of the vehicle to exit the team;

Here, the request message to exit the fleet does not require the participation of other team members, but only the communication interaction between the member of the second team and the front.

Step S903, the front of the vehicle determines whether the second team member is allowed to withdraw;

Here, if the second team member is allowed to exit, the process proceeds to step S904, and if the second team member is not allowed to exit, the process proceeds to step S906.

Some places are one-way streets, or no overtaking lanes are allowed. At this time, the team is not allowed to exit, so the front of the car can allow or disallow the team members to withdraw from the team.

Step S904, the front of the vehicle sends a confirmation message to the second team member that the vehicle is allowed to exit the vehicle;

Step S905, the front end sends the updated fleet related information to the team members other than the second team member;

Here, the updated related information includes at least: front information (such as: head ID), fleet information (such as: team logo), fleet member information (such as: ID of each team member), fleet key information, inside the fleet Communication resource configuration, driving information, etc.

Step S906: The front of the vehicle sends a rejection message to the team member that refuses to exit the fleet.

Example twenty two

Embodiments of the present invention provide a method for updating a fleet of vehicles, which is applied to a scene of an exiting fleet that is triggered by a vehicle head. FIG. 10 is a schematic flowchart of an implementation process of a twenty-two-vehicle update method according to an embodiment of the present invention. As shown in FIG. 10, the method includes the following steps:

Step S1001, the front of the vehicle determines that a second team member meets the conditions for exiting the team;

Step S1002, the front of the vehicle sends an instruction to the second team member to withdraw from the team;

Step S1003, if the second team member receives the indication information, then proceeds to step S1004, otherwise proceeds to step S1002;

Step S1004, the second team member sends a confirmation message to the front of the vehicle to exit the team;

In step S1005, the front end sends the updated fleet related information to the second team member.

Here, the updated related information includes at least: front information (such as: head ID), fleet information (such as: team logo), fleet member information (such as: ID of each team member), fleet key information, inside the fleet Communication resource configuration, driving information, etc.

Example twenty-three

Embodiments of the present invention provide a method for updating a fleet of vehicles, which is applied to a scenario in which a fleet of vehicles triggered by a nearby vehicle is joined. FIG. 11 is a schematic flowchart of an implementation process of a twenty-third vehicle fleet updating method according to an embodiment of the present invention. As shown in FIG. 11, the method includes the following steps:

Step S1101: a nearby vehicle receives status information of the fleet;

Here, the fleet status information includes: whether the team allows new cars to join, the team's position, speed, direction, forward destination, etc.

Step S1102, the vehicle determines whether it satisfies the condition of joining the team;

Here, if the vehicle satisfies the condition of joining the fleet, the process proceeds to step S1103, otherwise the flow is ended.

The vehicle determines whether it satisfies the conditions for joining the team based on its own state, that is, its own position, speed, direction, and forward destination.

Step S1103, the vehicle sends a request message to the fleet to join the team;

Here, the request message belongs to the communication between the vehicle and the front of the vehicle, and does not need to be known to other team members of the fleet, and can be connected through the Uu interface or the PC5 interface.

Step S1104, the front of the vehicle determines whether the vehicle is allowed to join the fleet;

Here, the vehicle is allowed to join the fleet to proceed to step S1105, otherwise to step S1107.

Step S1105, the front of the vehicle sends a message to the vehicle that allows the vehicle to join the fleet;

Step S1106, the front end sends updated team related information to the team members;

Here, the updated related information includes at least: front information (such as: head ID), fleet information (such as: team logo), fleet member information (such as: ID of each team member), fleet key information, inside the fleet Communication resource configuration, driving information, etc.

In step S1107, the front end sends a message to the vehicle rejecting the vehicle joining the fleet.

Example twenty four

Embodiments of the present invention provide a method for updating a fleet of vehicles, which is applied to a scenario in which a fleet of vehicles triggered by a vehicle head is joined. FIG. 12 is a schematic flowchart of an implementation process of a twenty-fourth vehicle fleet updating method according to an embodiment of the present invention. As shown in FIG. 12, the method includes the following steps:

Step S1201, the front end receives status information of the nearby vehicle;

In step S1202, the front of the vehicle determines whether a nearby vehicle meets the conditions for joining the team;

Here, when the nearby vehicle meets the condition of joining the team, the process proceeds to step S1203; otherwise, the process ends.

Step S1203, the front end sends a request message to the vehicle to join the fleet;

Here, the request message to join the team belongs to the communication between the car and the front of the car. It does not need to be known to other team members of the team, and can pass the Uu interface or the PC5 interface.

Step S1204, the vehicle determines whether to join the fleet;

Here, if the vehicle is to join the fleet, the process proceeds to step S1205; otherwise, the process proceeds to step S1207.

Step S1205, the vehicle sends a join fleet confirmation message to the front of the vehicle;

Step S1206, the front end sends updated team related information to the team members;

Here, the updated related information includes at least: front information (such as: head ID), fleet information (such as: team logo), fleet member information (such as: ID of each team member), fleet key information, inside the fleet Communication resource configuration, driving information, etc.

In step S1207, the vehicle sends a join fleet rejection message to the front.

Example twenty five

The embodiment of the present invention provides a vehicle fleet establishing device. FIG. 13 is a schematic structural diagram of a twenty-fifth fleet building device according to an embodiment of the present invention. As shown in FIG. 13, the device 1300 includes: a first acquiring module 1301, a first determining The module 1302, the first sending module 1303, wherein:

The first obtaining module 1301 is configured to acquire vehicle information of a vehicle within a preset range;

The first determining module 1302 is configured to determine group information of the vehicle group if the vehicle information satisfies a preset condition;

Here, the first determining module 1302 further includes:

a first sending unit, configured to send a setup request message to a network that establishes a connection with itself if the vehicle information satisfies a preset condition;

a first receiving unit, configured to receive, by the network, a setup response message that is allowed to establish a vehicle group, where the network is sent, where the setup response message carries group information of the vehicle group;

The first determining unit is configured to determine group information of the vehicle group according to the setup response message.

The first sending module 1303 is configured to send group information of the vehicle group.

Here, the first sending module 1303 further includes:

a sixth sending unit, configured to send the first group information to the vehicle members in the vehicle group, wherein the first group information includes at least one of the following information: fleet identification information, fleet status information , fleet open information, fleet private information and fleet safety information;

a seventh sending unit, configured to send second group information to a vehicle other than the group of vehicles, wherein the second group information includes at least one of the following information: fleet identification information, fleet status information , fleet open information and fleet private information.

In other embodiments of the present invention, the first determining module 1302 may further include:

The second determining unit is configured to determine the group information of the pre-configured vehicle group as the group information of the vehicle group if the vehicle information satisfies the preset condition.

Alternatively, in other embodiments of the present invention, the first determining module may further include:

a third determining unit, configured to determine, if the vehicle information satisfies the preset condition, a vehicle that satisfies the preset condition as a vehicle group;

And a fourth determining unit configured to determine group information of the vehicle group according to the vehicle information. The first sending module is configured to send group information of the vehicle group to the vehicle within the preset range.

In a practical application, the first obtaining module 1301 and the first determining module 1302 may be a central processing unit (CPU, Central Processing Unit), a microprocessor (MCU, Micro Control Unit) in a device (network side device or terminal), Digital Signal Processor (DSP) or Field-Programmable Gate Array (FPGA) implementation.

The first sending module 1303, the sixth sending unit, and the seventh sending unit may be implemented by a CPU, an MCU, a DSP, or an FPGA in combination with a transmitter in a device (network side device or terminal).

The first sending unit may be implemented by a CPU, MCU, DSP or FPGA in combination with a transmitter in a device (base station or core network device).

The first receiving unit may be implemented by a CPU, MCU, DSP or FPGA in combination with a receiver in a device (base station or core network device).

The first determining unit, the third determining unit, and the third determining unit may be implemented by a CPU, an MCU, a DSP, or an FPGA in a device (base station or core network device).

The second determining unit may be implemented by a CPU, an MCU, a DSP, or an FPGA in the device (terminal).

It should be noted that the interaction process between the units and the modules in this embodiment can be referred to the interaction process in the method for establishing a vehicle group according to the first embodiment of the present invention, and details are not described herein again. The description of the embodiment of the above vehicle group is similar to the description of the above method embodiment, and has similar advantages to the method embodiment, and therefore will not be described again. For technical details not disclosed in the embodiment of the apparatus for establishing a vehicle group of the present invention, please refer to the description of the method embodiment of the present invention.

Example twenty six

Based on the foregoing embodiments, an embodiment of the present invention provides an apparatus for updating a fleet of vehicles, the updating apparatus comprising: a first receiving module, a second sending module, a third sending module, a fourth sending module, a seventh sending module, and The seventeenth transmission module, wherein:

The first receiving module is configured to receive a join request message sent by the vehicle other than the member in the vehicle group;

Here, the join request message carries vehicle information requesting to join the vehicle. The vehicle information requesting to join the vehicle includes at least one of the following information: vehicle identification information, vehicle status information, vehicle private information, and application layer group identification information.

The second sending module is configured to send a join response message to the requesting joining vehicle according to the requested vehicle information of the joining vehicle.

Here, the second sending module further includes:

a second sending unit, configured to: if the vehicle information requested to join the vehicle meets a preset joining condition, send a join response message to the requesting joining vehicle, wherein the preset joining condition includes the following condition At least one of: whether the private information of the vehicle requesting to join the vehicle is consistent with the private information of the fleet, whether the application layer group identification information of the requesting joining vehicle is consistent with the fleet application layer identification information of the fleet, and requesting to join the vehicle state information and the vehicle of the vehicle Whether the group's fleet status information is consistent, and whether the vehicle group's fleet open information allows the vehicle to join;

And a third sending unit, configured to send a join response message rejecting the join to the requesting vehicle if the vehicle information of the request to join the vehicle does not satisfy the preset joining condition.

a third sending module, configured to send a group update message to a first vehicle member in the vehicle group for managing the vehicle group if a join response message is allowed to be sent to the requesting joining vehicle;

Here, the group update message carries the vehicle information of the request to join the vehicle.

And a fourth sending module, configured to send the group update message to the first vehicle member again if the group update confirmation message sent by the first vehicle member is not received.

The seventh sending module is configured to send first group information to a vehicle member in the vehicle group, wherein the first group information includes at least one of the following information: fleet identification information, a fleet Status information, fleet open information, fleet private information and fleet safety information;

The seventeenth sending module is configured to send second group information to a vehicle other than the vehicle group, wherein the second group information includes at least one of the following information: fleet identification information, Fleet status information, fleet open information, and fleet private information.

In a practical application, the second sending module, the third sending module, the fourth sending module, the seventh sending module, and the seventeenth sending module may be a CPU, an MCU, a DSP, or an FPGA in a device (base station or core network device). Combined with the transmitter implementation.

The first receiving module may be implemented by a CPU, MCU, DSP or FPGA in combination with a receiver in a device (base station or core network device).

It should be noted that the interaction process between the units and the modules in this embodiment may refer to the interaction process in the method for updating the vehicle group provided by the second embodiment of the present invention, and details are not described herein again. The description of the embodiment of the updating device of the above vehicle group is similar to the description of the above method embodiment, and has similar advantageous effects as the method embodiment, and therefore will not be described again. For technical details not disclosed in the embodiment of the updating device of the vehicle group of the present invention, please refer to the description of the method embodiment of the present invention.

Example twenty seven

Based on the foregoing embodiments, an embodiment of the present invention provides an apparatus for updating a fleet of vehicles, the updating apparatus comprising: a first receiving module, a second sending module, a fifth sending module, a sixth sending module, a seventh sending module, and The seventeenth transmission module, wherein:

The first receiving module is configured to receive a join request message sent by the vehicle other than the member in the vehicle group;

Here, the join request message carries vehicle information requesting to join the vehicle; the vehicle information requesting to join the vehicle includes at least one of the following information: vehicle identification information, vehicle status information, vehicle private information, and application layer group identifier. information.

The second sending module is configured to send a join response message to the requesting joining vehicle according to the requested vehicle information of the joining vehicle.

Here, the second sending module further includes:

a second sending unit, configured to: if the vehicle information requested to join the vehicle meets a preset joining condition, send a join response message to the requesting joining vehicle, wherein the preset joining condition includes the following condition At least one of: whether the private information of the vehicle requesting to join the vehicle is consistent with the private information of the fleet, whether the application layer group identification information of the requesting joining vehicle is consistent with the fleet application layer identification information of the fleet, and requesting to join the vehicle state information and the vehicle of the vehicle Whether the group's fleet status information is consistent, and whether the vehicle group's fleet open information allows the vehicle to join;

And a third sending unit, configured to send a join response message rejecting the join to the requesting vehicle if the vehicle information of the request to join the vehicle does not satisfy the preset joining condition.

The fifth sending module is configured to send a group update message to a network that establishes a connection with itself if the join request message sent to the requesting device is sent to the vehicle; wherein the group update message carries The request to join the vehicle information of the vehicle;

The sixth sending module is configured to send a group update message to the network again if the group update confirmation message sent by the network is not received.

The seventh sending module is configured to send first group information to a vehicle member in the vehicle group, wherein the first group information includes at least one of the following information: fleet identification information, a fleet Status information, fleet open information, fleet private information and fleet safety information;

The seventeenth sending module is configured to send second group information to a vehicle other than the vehicle group, wherein the second group information includes at least one of the following information: fleet identification information, Fleet status information, fleet open information, and fleet private information.

In practical applications, the second sending module, the fifth sending module, the sixth sending module, the seventh sending module, and the seventeenth sending module may be implemented by a CPU, an MCU, a DSP, or an FPGA in combination with a transmitter in a device (terminal). of.

The first receiving module may be implemented by a CPU, MCU, DSP or FPGA in the device (terminal) in combination with the receiver.

It should be noted that the interaction process between the units and the modules in this embodiment may refer to the interaction process in the method for updating the vehicle group provided by the second embodiment of the present invention, and details are not described herein again. The description of the embodiment of the updating device of the above vehicle group is similar to the description of the above method embodiment, and has the same advantageous effects as the method embodiment, and therefore will not be described again. For technical details not disclosed in the embodiment of the updating device of the vehicle group of the present invention, please refer to the description of the method embodiment of the present invention.

Example twenty eight

An embodiment of the present invention provides an apparatus for updating a vehicle group, where the updating apparatus includes: a second receiving module, an eighth sending module, a ninth sending module, a tenth sending module, a thirteenth sending module, and an eighteenth sending Module, where:

The second receiving module is configured to receive an exit request message requesting to exit the vehicle in the group of vehicles;

The eighth sending module is configured to send an exit response message to the requesting exit vehicle.

Here, the eighth sending module further includes:

a fourth sending unit, configured to send an exit response message that allows the exit to the requesting exit vehicle if the vehicle information requesting to exit the vehicle satisfies a preset exit condition;

And a fifth sending unit configured to send an exit response message rejecting the exit to the requesting exit vehicle if the vehicle information requesting to exit the vehicle does not satisfy the preset exit condition.

The ninth sending module is configured to send a group update message to a first vehicle member of the vehicle group for managing the vehicle group; wherein the group update message carries the request to exit Vehicle information of the vehicle;

The tenth sending module is configured to send a group update message to the first vehicle member again if the group update confirmation message sent by the first vehicle member is not received.

The thirteenth sending module is configured to send first group information to a vehicle member in the vehicle group, where the first group information includes at least one of the following information: fleet identification information, Fleet status information, fleet open information, fleet private information and fleet safety information;

The eighteenth sending module is configured to send second group information to a vehicle other than the vehicle group, wherein the second group information includes at least one of the following information: fleet identification information, Fleet status information, fleet open information, and fleet private information.

In an actual application, the eighth sending module, the ninth sending module, the tenth sending module, the thirteenth sending module, and the eighteenth sending module may be a CPU, an MCU, a DSP, or a device (a base station or a core network device). The FPGA is implemented in conjunction with the transmitter.

The second receiving module may be implemented by a CPU, MCU, DSP or FPGA in combination with a receiver in a device (base station or core network device).

It should be noted that the interaction process between the units and the modules in this embodiment may refer to the interaction process in the method for updating the vehicle group provided by the third embodiment of the present invention, and details are not described herein again. The description of the embodiment of the updating device of the above vehicle group is similar to the description of the above method embodiment, and has the same advantageous effects as the method embodiment, and therefore will not be described again. For technical details not disclosed in the embodiment of the updating device of the vehicle group of the present invention, please refer to the description of the method embodiment of the present invention.

Example twenty nine

An embodiment of the present invention provides an apparatus for updating a vehicle group, where the updating apparatus includes: a second receiving module, an eighth sending module, an eleventh sending module, a twelfth sending module, a thirteenth sending module, and a tenth Eight send modules, where:

The second receiving module is configured to receive an exit request message requesting to exit the vehicle in the group of vehicles;

The eighth sending module is configured to send an exit response message to the requesting exit vehicle.

Here, the eighth sending module further includes:

a fourth sending unit, configured to send an exit response message that allows the exit to the requesting exit vehicle if the vehicle information requesting to exit the vehicle satisfies a preset exit condition;

And a fifth sending unit configured to send an exit response message rejecting the exit to the requesting exit vehicle if the vehicle information requesting to exit the vehicle does not satisfy the preset exit condition.

The eleventh sending module is configured to send a group update message to a network that establishes a connection with itself; wherein the group update message carries the vehicle information that requests to exit the vehicle;

The twelfth sending module is configured to send a group update message to the network again if the group update confirmation message sent by the network is not received.

The thirteenth sending module is configured to send first group information to a vehicle member in the vehicle group, where the first group information includes at least one of the following information: fleet identification information, Fleet status information, fleet open information, fleet private information and fleet safety information;

The eighteenth sending module is configured to send second group information to a vehicle other than the vehicle group, wherein the second group information includes at least one of the following information: fleet identification information, Fleet status information, fleet open information, and fleet private information.

In an actual application, the eighth sending module, the eleventh sending module, the twelfth sending module, the thirteenth sending module, and the eighteenth sending module may be combined by a CPU, an MCU, a DSP, or an FPGA in a device (terminal). Transmitter implemented.

The second receiving module may be implemented by a CPU, an MCU, a DSP or an FPGA in a device (terminal) in combination with a receiver.

It should be noted that the interaction process between the units and the modules in this embodiment may refer to the interaction process in the method for updating the vehicle group provided by the third embodiment of the present invention, and details are not described herein again. The description of the embodiment of the updating device of the above vehicle group is similar to the description of the above method embodiment, and has the same advantageous effects as the method embodiment, and therefore will not be described again. For technical details not disclosed in the embodiment of the updating device of the vehicle group of the present invention, please refer to the description of the method embodiment of the present invention.

Example thirty

An embodiment of the present invention provides an apparatus for updating a vehicle group, where the updating apparatus includes: a fourteenth transmitting module, a third receiving module, and a fifteenth transmitting module, where:

The fourteenth sending module is configured to send, to the network establishing the connection by itself, a dissolving request message for dissolving the vehicle group;

The third receiving module is configured to receive a dissolving response message sent by the network.

The fifteenth transmitting module is configured to send a dissolving indication message to a vehicle in the group of vehicles if the dissolving response message is a dissolving response message allowing dissolving.

In practical applications, the fourteenth transmitting module and the fifteenth transmitting module may be implemented by a CPU, an MCU, a DSP, or an FPGA in combination with a transmitter in a device (terminal).

The third receiving module may be implemented by a CPU, an MCU, a DSP or an FPGA in a device (terminal) in combination with a receiver.

It should be noted that the interaction process between the units and the modules in this embodiment can refer to the interaction process in the method for updating the vehicle group provided by the fourth embodiment of the present invention, and details are not described herein again. The description of the embodiment of the updating device of the above vehicle group is similar to the description of the above method embodiment, and has the same advantageous effects as the method embodiment, and therefore will not be described again. For technical details not disclosed in the embodiment of the updating device of the vehicle group of the present invention, please refer to the description of the method embodiment of the present invention.

Embodiment 31

An embodiment of the present invention provides an apparatus for updating a vehicle group, where the updating apparatus includes: a judging module and a sixteenth transmitting module, where:

The determining module is configured to determine, according to the group information of the vehicle group, whether to dismiss the vehicle group;

The sixteenth transmitting module is configured to send a dissolving indication message to the vehicle in the group of vehicles if the vehicle group is allowed to be disbanded.

In practical applications, the sixteenth transmission module may be implemented by a CPU, an MCU, a DSP, or an FPGA in combination with a transmitter in a device (terminal).

The judgment can be implemented by a CPU, MCU, DSP or FPGA in the device (terminal).

It should be noted that the interaction process between the units and the modules in this embodiment can refer to the interaction process in the method for updating the vehicle group provided by the fifth embodiment of the present invention, and details are not described herein again. The description of the embodiment of the updating device of the above vehicle group is similar to the description of the above method embodiment, and has the same advantageous effects as the method embodiment, and therefore will not be described again. For technical details not disclosed in the embodiment of the updating device of the vehicle group of the present invention, please refer to the description of the method embodiment of the present invention.

It should be noted that, in the embodiment of the present invention, if the foregoing method for establishing a vehicle group or a method for updating a vehicle group is implemented in the form of a software function module, and is sold or used as an independent product, it may also be stored in one The computer can read the storage medium. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. One device (which may be a terminal or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention. The foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.

Correspondingly, an embodiment of the present invention provides a device for establishing a group of vehicles, including a memory and a processor, where the memory stores a computer program executable on a processor, where the processor implements the program The steps in the method of establishing a vehicle group.

Correspondingly, an embodiment of the present invention provides an update device for a vehicle group, including a memory and a processor, where the memory stores a computer program executable on a processor, where the processor implements the program The steps in the method of updating the vehicle group.

Correspondingly, the embodiment of the present invention provides a computer readable storage medium, where the computer program is stored, where the computer program is executed by the processor to implement the steps in the method for establishing a vehicle group; or the computer The steps in the method of updating the vehicle group described are implemented when the program is executed by the processor.

The above description of the storage medium and device embodiments is similar to the description of the above method embodiments, and has similar advantageous effects as the method embodiments. For technical details not disclosed in the storage medium and device embodiments of the present invention, please refer to the description of the method embodiments of the present invention.

It is to be noted that FIG. 14 is a schematic diagram of a hardware entity of a device (which may be a terminal or a network device, etc.) according to an embodiment of the present invention. As shown in FIG. 14 , the hardware entity of the device 1400 includes: a processor 1401 and a communication interface. 1402 and memory 1403, wherein

The processor 1401 typically controls the overall operation of the device 1400.

Communication interface 1402 may enable devices to communicate with other terminals or servers over a network.

The memory 1403 is configured to store instructions and applications executable by the processor 1401, and may also cache data to be processed or processed by the processor 1401 and each module in the device 1400, and may be flash memory (FLASH) or random access memory (Random Access). Memory, RAM) implementation.

It is to be understood that the phrase "one embodiment" or "an embodiment" or "an" Thus, "in one embodiment" or "in an embodiment" or "an" In addition, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention. The implementation process constitutes any limitation. The serial numbers of the embodiments of the present invention are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.

The units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units; they may be located in one place or distributed on multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; The unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

It will be understood by those skilled in the art that all or part of the steps of implementing the foregoing method embodiments may be performed by hardware related to program instructions. The foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium includes: a removable storage device, a read only memory (ROM), a magnetic disk, or an optical disk, and the like, which can store program codes.

Alternatively, the above-described integrated unit of the present invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. One device (which may be a terminal or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention. The foregoing storage medium includes various media that can store program codes, such as a mobile storage device, a ROM, a magnetic disk, or an optical disk.

The above is only the embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. It is intended to be covered by the scope of the invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Industrial applicability

In the embodiment of the present invention, first, acquiring vehicle information of a vehicle within a preset range; then determining whether the vehicle information meets a preset condition, and determining group information of the vehicle group when the vehicle information satisfies a preset condition; The group information of the vehicle group is transmitted again. In this way, a vehicle group can be established for a vehicle in which the vehicle information meets the preset condition within the preset range, and the direct communication between the members of the vehicle group in the vehicle group is different from the vehicle group member and the vehicle group. The resources of the group external vehicles are dedicated communication resources allocated for the vehicle group, which improves the reliability of the internal communication of the fleet, and also reduces the probability of resource collision, thereby improving the communication efficiency.

Claims (40)

A method for establishing a vehicle group, wherein the method includes: Obtaining vehicle information of the vehicle within the preset range; Determining group information of the vehicle group if the vehicle information satisfies a preset condition; Send group information of the vehicle group. The method according to claim 1, wherein the vehicle information includes at least vehicle state information and vehicle capability information, and correspondingly, if the number of vehicles within the preset range is equal to 1, the preset condition is the preset The vehicle capability information of the vehicle in the range satisfies the vehicle capability required by the preset vehicle head, wherein the vehicle capability required by the vehicle head includes at least vehicle-to-vehicle V2V communication capability and vehicle-to-network V2I communication capability; If the number of vehicles in the preset range is greater than 1, the preset condition includes at least the same vehicle state information of the vehicle within the preset range, and the vehicle capability of at least one vehicle in the vehicle within the preset range is satisfied The preset vehicle head needs to have the vehicle capability, and the vehicle capability information of the vehicle within the preset range satisfies the support V2V communication. The method according to claim 1, wherein if the vehicle information satisfies a preset condition, determining group information of the vehicle group comprises: If the vehicle information satisfies a preset condition, a setup request message is sent to a network that establishes a connection with itself; Receiving, by the network, a setup response message that is required to establish a vehicle group, where the setup request message is sent; the setup response message carries group information of a vehicle group; Determining group information of the vehicle group according to the setup response message. The method according to claim 1, wherein if the vehicle information satisfies a preset condition, determining group information of the vehicle group further comprises: If the vehicle information satisfies a preset condition, the group information of the vehicle group that is pre-configured by itself is determined as the group information of the vehicle group. The method according to claim 1, wherein the determining the group information of the vehicle group if the vehicle information satisfies the preset condition further comprises: If the vehicle information satisfies the preset condition, determining a vehicle in which the vehicle information meets the preset condition is determined as a vehicle group; The group information of the vehicle group is determined according to the vehicle information. The method of claim 1, wherein the transmitting the group information of the vehicle group comprises: Transmitting first group information to vehicle members in the group of vehicles, wherein the first group information includes at least one of: fleet identification information, fleet status information, fleet opening information, fleet ownership Information and fleet safety information; Transmitting second group information to a vehicle other than the group of vehicles, wherein the second group information includes at least one of: fleet identification information, fleet status information, fleet opening information, and fleet ownership information. A method for updating a group of vehicles, wherein the method comprises: Receiving a join request message sent by the vehicle other than the member in the vehicle group; wherein the join request message carries vehicle information requesting to join the vehicle; Sending a join response message to the requesting joining vehicle according to the vehicle information of the request to join the vehicle. The method according to claim 7, wherein the vehicle information requested to join the vehicle includes at least one of the following information: vehicle identification information, vehicle state information, vehicle private information, and application layer group identification information, correspondingly, The sending a join response message to the requesting join vehicle includes: If the vehicle information requested to join the vehicle satisfies a preset joining condition, send a join response message to the requesting joining vehicle, wherein the preset joining condition includes at least one of the following conditions: requesting to join Whether the vehicle private information of the vehicle is consistent with the private information of the fleet, whether the application layer group identification information of the requesting joining vehicle is consistent with the fleet application layer identification information of the fleet, and whether the vehicle state information of the joining vehicle and the fleet status information of the vehicle group are requested Consistent, whether the fleet open information of the vehicle group allows the vehicle to join; If the vehicle information requesting to join the vehicle does not satisfy the preset joining condition, then the joining vehicle is sent to the request to send a join response message rejecting the joining. The method of claim 8 wherein the method further comprises: Sending a group update message to a first vehicle member in the group of vehicles for managing the group of vehicles; wherein the group update message carries vehicle information of the request to join the vehicle; If the group update confirmation message sent by the first vehicle member is not received, the group update message is sent to the first vehicle member again. The method of claim 8 wherein the method further comprises: Sending a group update message to a network that establishes a connection with itself; wherein the group update message carries the vehicle information of the request to join the vehicle; If the group update confirmation message sent by the network is not received, the group update message is sent to the network again. The method of claim 9 or 10, wherein the method further comprises: Transmitting first group information to vehicle members in the group of vehicles, wherein the first group information includes at least one of: fleet identification information, fleet status information, fleet opening information, fleet ownership Information and fleet safety information; Transmitting second group information to a vehicle other than the group of vehicles, wherein the second group information includes at least one of: fleet identification information, fleet status information, fleet opening information, and fleet ownership information. The method of claim 7 wherein the method further comprises: Receiving an exit request message requesting to exit the vehicle in the group of vehicles; An exit response message is sent to the requesting exit vehicle. The method of claim 12 wherein said sending an exit response message to said requesting exit vehicle comprises: If the vehicle information requesting to exit the vehicle satisfies a preset exit condition, sending an exit response message allowing the exit to the request to exit the vehicle; If the vehicle information requesting to exit the vehicle does not satisfy the preset exit condition, an exit response message rejecting the exit is sent to the requesting exit vehicle. The method of claim 13 wherein the method further comprises: Sending a group update message to a first vehicle member in the group of vehicles for managing the group of vehicles; wherein the group update message carries the vehicle information requesting to exit the vehicle; If the group update confirmation message sent by the first vehicle member is not received, the group update message is sent to the first vehicle member again. The method of claim 13 wherein the method further comprises: Sending a group update message to a network that establishes a connection with itself; wherein the group update message carries the vehicle information requesting to exit the vehicle; If the group update confirmation message sent by the network is not received, the group update message is sent to the network again. The method of claim 14 or 15, wherein the method further comprises: Transmitting first group information to vehicle members in the group of vehicles, wherein the first group information includes at least one of: fleet identification information, fleet status information, fleet opening information, fleet ownership Information and fleet safety information; Transmitting second group information to a vehicle other than the group of vehicles, wherein the second group information includes at least one of: fleet identification information, fleet status information, fleet opening information, and fleet ownership information. The method of claim 7 wherein the method further comprises: Transmitting a disbanding request message of the vehicle group to a network that establishes a connection to itself; Receiving a disbanding response message sent by the network. The method of claim 17 wherein the method further comprises: If the dissolving response message is a dissolving response message that allows disbanding, a dismissal indication message is sent to the vehicle in the group of vehicles. The method of claim 7 wherein the method further comprises: Determining, according to the group information of the vehicle group, whether to dismiss the vehicle group; If the vehicle group is allowed to be disbanded, a dismissal indication message is sent to the vehicle in the group of vehicles. A device for establishing a group of vehicles, wherein the device comprises: a first acquiring module configured to acquire vehicle information of a vehicle within a preset range; a first determining module, configured to determine group information of the vehicle group if the vehicle information satisfies a preset condition; The first sending module is configured to send group information of the vehicle group. The apparatus according to claim 20, wherein said first determining module comprises: a first sending unit, configured to send a setup request message to a network that establishes a connection with itself if the vehicle information satisfies a preset condition; a first receiving unit, configured to receive, by the network, a setup response message that is required to establish a vehicle group, where the setup response message carries the group information of the vehicle group; The first determining unit is configured to determine group information of the vehicle group according to the setup response message. The apparatus according to claim 20, wherein the first determining module further comprises: And a second determining unit configured to determine the group information of the pre-configured vehicle group as the group information of the vehicle group if the vehicle information satisfies the preset condition. The apparatus according to claim 20, wherein the first determining module further comprises: a third determining unit configured to satisfy the preset condition of the vehicle information if the vehicle information satisfies the preset condition Vehicle is determined to be a group of vehicles; And a fourth determining unit configured to determine group information of the vehicle group according to the vehicle information. The apparatus according to claim 20, wherein said first transmitting module comprises: a sixth sending unit, configured to send the first group information to the vehicle members in the vehicle group, wherein the first group information includes at least one of the following information: fleet identification information, fleet status information , fleet open information, fleet private information and fleet safety information; a seventh sending unit, configured to send second group information to a vehicle other than the group of vehicles, wherein the second group information includes at least one of the following information: fleet identification information, fleet status information , fleet open information and fleet private information. An apparatus for updating a group of vehicles, wherein the apparatus comprises: a first receiving module, configured to receive a join request message sent by the vehicle other than the member in the vehicle group, wherein the join request message carries vehicle information requesting to join the vehicle; The second sending module is configured to send a join response message to the requesting joining vehicle according to the requested vehicle information of the joining vehicle. The apparatus according to claim 25, wherein said vehicle information requested to join the vehicle includes at least one of the following information: vehicle identification information, vehicle state information, vehicle private information, and application layer group identification, correspondingly, The second sending module includes: a second sending unit, configured to: if the vehicle information requested to join the vehicle meets a preset joining condition, send a join response message to the requesting joining vehicle, wherein the preset joining condition includes the following condition At least one of: whether the private information of the vehicle requesting to join the vehicle is consistent with the private information of the fleet, whether the application layer group identification information of the requesting joining vehicle is consistent with the fleet application layer identification information of the fleet, and requesting to join the vehicle state information and the vehicle of the vehicle Whether the group's fleet status information is consistent, and whether the vehicle group's fleet open information allows the vehicle to join; And a third sending unit, configured to send a join response message rejecting the join to the requesting vehicle if the vehicle information of the request to join the vehicle does not satisfy the preset joining condition. The device of claim 26, wherein the device further comprises: a third sending module, configured to send a group update message to a first vehicle member in the group of vehicles for managing the group of vehicles; wherein the group update message carries the request to join a vehicle Vehicle Information; And a fourth sending module, configured to send the group update message to the first vehicle member again if the group update confirmation message sent by the first vehicle member is not received. The device of claim 26, wherein the device further comprises: a fifth sending module, configured to send a group update message to a network that establishes a connection with itself, where the group update message carries the vehicle information of the request to join the vehicle; The sixth sending module is configured to send the group update message to the network again if the group update confirmation message sent by the network is not received. The device of claim 27 or 28, wherein the device further comprises: a seventh sending module, configured to send first group information to a vehicle member in the group of vehicles, wherein the first group information includes at least one of the following information: fleet identification information, fleet status information , fleet open information, fleet private information and fleet safety information; a seventeenth sending module, configured to send second group information to a vehicle other than the group of vehicles, wherein the second group information includes at least one of the following information: fleet identification information, fleet status Information, fleet open information and fleet private information. The device of claim 25, wherein the device further comprises: a second receiving module, configured to receive an exit request message requesting to exit the vehicle in the group of vehicles; The eighth sending module is configured to send an exit response message to the requesting exit vehicle. The apparatus according to claim 30, wherein said eighth transmitting module comprises: a fourth sending unit, configured to send an exit response message that allows the exit to the requesting exit vehicle if the vehicle information requesting to exit the vehicle satisfies a preset exit condition; And a fifth sending unit configured to send an exit response message rejecting the exit to the requesting exit vehicle if the vehicle information requesting to exit the vehicle does not satisfy the preset exit condition. The device of claim 31, wherein the device further comprises: a ninth sending module, configured to send a group update message to a first vehicle member in the group of vehicles for managing the group of vehicles; wherein the group update message carries the request to exit the vehicle Vehicle Information; The tenth sending module is configured to send the group update message to the first vehicle member again if the group update confirmation message sent by the first vehicle member is not received. The device of claim 31, wherein the device further comprises: An eleventh sending module, configured to send a group update message to a network that establishes a connection with itself; wherein the group update message carries the vehicle information that requests to exit the vehicle; The twelfth sending module is configured to send the group update message to the network again if the group update confirmation message sent by the network is not received. The device of claim 32 or 33, wherein the device further comprises: a thirteenth sending module, configured to send first group information to a vehicle member in the vehicle group, wherein the first group information includes at least one of the following information: fleet identification information, fleet status Information, fleet open information, fleet private information and fleet safety information; The eighteenth sending module is configured to send the second group information to the vehicle outside the vehicle group, wherein the second group information includes at least one of the following information: fleet identification information, fleet status Information, fleet open information and fleet private information. The device of claim 25, wherein the device further comprises: a fourteenth sending module, configured to send, to the network establishing the connection by itself, a dissolving request message for dissolving the vehicle group; The third receiving module is configured to receive a disbanding response message sent by the network. The device of claim 35, wherein the device further comprises: The fifteenth transmitting module is configured to send a dissolving indication message to the vehicle in the group of vehicles if the dissolving response message is a disbanding response message allowing dissolving. The device of claim 25, wherein the device further comprises: a determining module, configured to determine, according to the group information of the vehicle group, whether to dismiss the vehicle group; And a sixteenth transmitting module configured to send a dissolving indication message to the vehicle in the group of vehicles if the vehicle group is allowed to be disbanded. A device for establishing a group of vehicles, comprising a memory and a processor, the memory storing a computer program executable on a processor, wherein the processor executes the program to implement any one of claims 1 to 6 The steps in the method of establishing a vehicle group. An update device for a group of vehicles, comprising a memory and a processor, the memory storing a computer program executable on a processor, wherein the processor executes the program to implement any one of claims 7 to 19 The steps in the method of updating the vehicle group. A computer readable storage medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement the steps of the method for establishing a vehicle group according to any one of claims 1 to 6; or The steps in the method of updating a vehicle group according to any one of claims 7 to 19 when the program is executed by the processor.

Images