A congestion control method, device, control apparatus, program product, and medium

Abstract

The application provides a congestion control method and device, a control equipment, a program product and a medium, and relates to the technical field of communication. The method comprises the following steps: acquiring first information of member nodes corresponding to a group head node, wherein the member nodes corresponding to the group head node comprise at least one node in a node group to which the group head node belongs except the group head node; and sending an allocation instruction to the member nodes according to the first information, wherein the allocation instruction is used for indicating service sending; and the first information comprises at least one of the following: a measured value of a channel busy ratio (CBR); a service type of a first target service, wherein the first target service is a service to be triggered; and a service priority of the first target service. The scheme of the application solves the problem that the prior art lacks a congestion control scheme suitable for a group head resource allocation scene.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a congestion control method, apparatus, control device, program product, and medium. Background Technology

[0002] In the group head resource allocation scenario, the group head node is responsible for uniformly allocating time and frequency resources to the group member vehicles, thereby avoiding resource competition between vehicles.

[0003] However, the congestion control schemes defined in the existing Long-Term Evolution (LTE) Vehicle-to-Everything (V2X) and New Radio (NR)-V2X standards are not applicable to the scenario of group head resource allocation, making it difficult to ensure the communication performance and resource utilization efficiency of group members under congestion conditions. Summary of the Invention

[0004] This invention provides a congestion control method, apparatus, control device, program product, and medium, which solves the problem that the prior art lacks a congestion control scheme adapted to the group head resource allocation scenario.

[0005] In a first aspect, embodiments of the present invention provide a congestion control method, comprising:

[0006] Obtain the first information of the member nodes corresponding to the group head node, wherein the member nodes corresponding to the group head node include at least one node in the node group to which the group head node belongs, excluding the group head node;

[0007] Based on the first information, an allocation instruction is sent to the member node, the allocation instruction being used to instruct the service to be sent;

[0008] The first information includes at least one of the following:

[0009] The measured value of Channel Busy Ratio (CBR);

[0010] The first target business is the business type of the business that is about to be triggered.

[0011] The service priority of the first target service.

[0012] Optionally, sending an allocation instruction to the member node based on the first information includes:

[0013] Based on the second information corresponding to each node in the node group, the user priority corresponding to each node is determined respectively, wherein the second information includes: vehicle type and / or vehicle location;

[0014] Based on the user priority corresponding to each node and the first information, the allocation information corresponding to each node is determined respectively, and the allocation information includes: service allocation information and resource allocation information;

[0015] The allocation instruction is sent to the member node, and the allocation instruction includes the allocation information corresponding to the member node.

[0016] Optionally, determining the allocation information corresponding to each node based on the user priority corresponding to each node and the first information includes:

[0017] Based on the first information corresponding to each node, the congestion information corresponding to each node and the congestion information corresponding to the node group are determined respectively. The congestion information includes: congestion status and / or congestion level.

[0018] Based on the congestion information corresponding to the node group and the priority information corresponding to each node, the allocation information corresponding to each node is determined respectively, wherein the priority information includes: the user priority and / or the service priority.

[0019] Optionally, if the first preset condition is met, determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node includes:

[0020] Determine whether the congestion status corresponding to the node group has changed and / or whether the decrease in the congestion level corresponding to the node group exceeds a first preset threshold.

[0021] If the congestion status of the node group changes and / or the reduction exceeds the first preset threshold, resources will be reallocated preferentially for the second target service that meets the second preset condition.

[0022] Based on the congestion information corresponding to each node, perform resource adjustments;

[0023] Repeat the step of prioritizing resource reallocation for the second target service that meets the second preset condition, until the step of performing resource adjustment based on the congestion information corresponding to each node is performed, until the third preset condition is met and the allocation information corresponding to each node is obtained;

[0024] The first preset condition includes: the congestion state corresponding to the node group is non-congested, and / or the congestion level corresponding to the node group is less than or equal to the first preset threshold.

[0025] The second preset condition includes: the business priority corresponding to the business is greater than or equal to the first priority, and / or, the user priority corresponding to the node associated with the business is greater than or equal to the second priority;

[0026] The third preset condition includes at least one of the following:

[0027] The congestion status corresponding to the node is non-congestion;

[0028] The congestion level corresponding to the node is less than or equal to the second preset threshold;

[0029] For the services that are about to be triggered, resources are allocated using pre-configured service parameters.

[0030] Optionally, the execution resource adjustment includes at least one of the following:

[0031] Increase the number of sub-channels occupied;

[0032] Reduce the modulation and coding scheme (MCS) level;

[0033] Shorten business cycles;

[0034] Increase the number of data transmissions.

[0035] Optionally, when the congestion state corresponding to the node group is partial congestion, determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node includes:

[0036] Based on the congestion information corresponding to the node group, at least one target node is determined, the target node including: a node whose congestion state is congested, and / or a node whose congestion level is greater than or equal to a third preset threshold;

[0037] Based on the priority information corresponding to the target node, resources are reallocated to the services corresponding to the target node;

[0038] Based on the congestion information corresponding to each node, perform resource adjustments;

[0039] Repeat the steps of reallocating resources for the services corresponding to the target node based on the priority information of the target node, until the steps of adjusting resources based on the congestion information of each node are performed, until the fourth preset condition is met and the allocation information of each node is obtained.

[0040] The fourth preset condition includes at least one of the following:

[0041] The congestion status corresponding to the target node is non-congested;

[0042] The congestion level corresponding to the target node is less than or equal to the second preset threshold;

[0043] The service uses the minimum allowed number of sub-channels.

[0044] The service adopts the maximum allowed MCS level;

[0045] The service uses the maximum allowed service period;

[0046] The service uses the minimum allowed number of transmissions;

[0047] End unnecessary business operations.

[0048] Optionally, when the congestion state corresponding to the node group is congested or fully congested, determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node includes:

[0049] Based on the priority information of each node, resources are reallocated to the services corresponding to each node;

[0050] Based on the congestion information corresponding to each node, perform resource adjustments;

[0051] Repeat the steps of reallocating resources for services corresponding to each node based on the priority information of each node, until the steps of adjusting resources based on the congestion information of each node are performed, until the fifth preset condition is met and the allocation information corresponding to each node is obtained.

[0052] The fifth preset condition includes at least one of the following:

[0053] The congestion status corresponding to the node group is non-congestion;

[0054] The congestion level corresponding to the node group is less than or equal to the second preset threshold;

[0055] The service uses the minimum allowed number of sub-channels.

[0056] The service adopts the maximum allowed MCS level;

[0057] The service uses the maximum allowed service period;

[0058] The service uses the minimum allowed number of transmissions;

[0059] End unnecessary business operations.

[0060] Optionally, based on the priority information corresponding to the node, resource reallocation is performed on the services corresponding to the node, including:

[0061] Based on the priority information corresponding to each node, the nodes are sorted according to a preset sorting rule to generate a resource redistribution sequence;

[0062] According to the resource reallocation sequence, the services corresponding to each node are reallocated;

[0063] The preset sorting rule includes at least one of the following:

[0064] Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the business priority from low to high. Then, within the same business priority level, the second level of sorting is performed according to the user priority corresponding to each node from low to high.

[0065] Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the user priority corresponding to each node from low to high. Then, within the same user priority level, the second level of sorting is performed according to the business priority from low to high.

[0066] Based on the comprehensive priority index ranking mechanism, a comprehensive priority index is first generated by weighting the business priority and the user priority corresponding to each node, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

[0067] Optionally, the execution resource adjustment includes at least one of the following:

[0068] Reduce the number of sub-channels occupied;

[0069] Increase MCS level;

[0070] Increase business cycle;

[0071] Reduce the number of data transmissions.

[0072] Optionally, determining the congestion information corresponding to each node and the congestion information corresponding to the node group based on the first information corresponding to each node includes:

[0073] Based on the current service allocation information and current resource allocation information corresponding to each node, the channel ratio CR value corresponding to each node is determined respectively;

[0074] Based on the CR value and CBR measurement value corresponding to each node, the congestion information corresponding to each node is determined by comparing them with the pre-configured threshold information. The threshold information includes: CBR threshold and CR threshold.

[0075] Based on the congestion information corresponding to each node, the congestion information corresponding to the node group is determined.

[0076] Optionally, determining the congestion information corresponding to each node and the congestion information corresponding to the node group based on the first information corresponding to each node includes:

[0077] Based on the current service allocation information and current resource allocation information corresponding to each node, the CR value corresponding to each node is determined respectively;

[0078] Based on the user priority corresponding to each node, the weighting factor corresponding to each node is determined respectively;

[0079] Based on the weighting factor corresponding to each node, the CR values ​​corresponding to each node are weighted and summed to obtain the first CR value;

[0080] Based on the weighting factor corresponding to each node, the measured CBR values ​​corresponding to each node are weighted and summed to obtain the first CBR value;

[0081] Based on the first CR value and the first CBR value, the congestion information corresponding to the node group is determined by comparing them with the pre-configured threshold information.

[0082] Optionally, obtaining the first information of the member nodes corresponding to the group head node includes at least one of the following:

[0083] According to the first triggering condition, a first request is sent to the member node, and the first information of the member node is received from the member node in response to the first request. The first request is used to request the sending of the first information of the member node.

[0084] Receive the first information of the member node reported by the member node according to the second triggering condition;

[0085] The first triggering condition includes at least one of the following:

[0086] Periodic triggering based on a first preset period;

[0087] The event is triggered based on the first event, which includes: the measured value of the CBR corresponding to the group head node is greater than or equal to the fourth preset threshold, and / or the group head node detects the start of a new service;

[0088] The second triggering condition includes at least one of the following:

[0089] Periodic triggering based on a second preset cycle;

[0090] The event is triggered based on a second event, which includes: the member node actively initiating a service request, and / or the member node receiving a trigger message from any node outside the node group to which the group head node belongs.

[0091] In a second aspect, embodiments of the present invention provide a congestion control device, comprising:

[0092] The information acquisition module is used to acquire the first information of the member nodes corresponding to the group head node. The member nodes corresponding to the group head node include at least one node in the node group to which the group head node belongs, excluding the group head node.

[0093] An instruction sending module is configured to send an allocation instruction to the member node based on the first information, wherein the allocation instruction is used to instruct the service to be sent.

[0094] The first information includes at least one of the following:

[0095] The measured value of Channel Busy Ratio (CBR);

[0096] The first target business is the business type of the business that is about to be triggered.

[0097] The service priority of the first target service.

[0098] Optionally, the instruction sending module includes:

[0099] The first processing submodule is used to determine the user priority corresponding to each node according to the second information corresponding to each node in the node group, wherein the second information includes: vehicle type and / or vehicle location;

[0100] The second processing submodule is used to determine the allocation information corresponding to each node based on the user priority corresponding to each node and the first information. The allocation information includes: service allocation information and resource allocation information.

[0101] The instruction sending submodule is used to send the allocation instruction to the member node, the allocation instruction including the allocation information corresponding to the member node.

[0102] Optionally, the second processing submodule includes:

[0103] The first processing unit is configured to determine the congestion information corresponding to each node and the congestion information corresponding to the node group based on the first information corresponding to each node. The congestion information includes: congestion status and / or congestion level.

[0104] The second processing unit is used to determine the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node, wherein the priority information includes: the user priority and / or the service priority.

[0105] Optionally, the second processing unit includes:

[0106] The first judgment subunit is used to determine whether the congestion state corresponding to the node group has changed and / or whether the reduction in the congestion level corresponding to the node group exceeds a first preset threshold.

[0107] The first reconfiguration subunit is used to prioritize resource reallocation for the second target service that meets the second preset condition when the congestion state corresponding to the node group changes and / or the reduction exceeds the first preset threshold.

[0108] The first adjustment subunit is used to perform resource adjustment based on the congestion information corresponding to each node;

[0109] The first processing subunit is used to repeatedly execute the step of prioritizing resource reallocation for the second target service that meets the second preset condition, up to the step of performing resource adjustment based on the congestion information corresponding to each node, until the third preset condition is met and the allocation information corresponding to each node is obtained.

[0110] The first preset condition includes: the congestion state corresponding to the node group is non-congested, and / or the congestion level corresponding to the node group is less than or equal to the first preset threshold.

[0111] The second preset condition includes: the business priority corresponding to the business is greater than or equal to the first priority, and / or, the user priority corresponding to the node associated with the business is greater than or equal to the second priority;

[0112] The third preset condition includes at least one of the following:

[0113] The congestion status corresponding to the node is non-congestion;

[0114] The congestion level corresponding to the node is less than or equal to the second preset threshold;

[0115] For the services that are about to be triggered, resources are allocated using pre-configured service parameters.

[0116] Optionally, the execution resource adjustment includes at least one of the following:

[0117] Increase the number of sub-channels occupied;

[0118] Reduce the MCS level of the modulation and coding scheme;

[0119] Shorten business cycles;

[0120] Increase the number of data transmissions.

[0121] Optionally, the second processing unit includes:

[0122] The second processing subunit is used to determine at least one target node based on the congestion information corresponding to the node group. The target node includes: a node whose congestion state is congested, and / or a node whose congestion level is greater than or equal to a third preset threshold.

[0123] The second reconfiguration subunit is used to reallocate resources for the services corresponding to the target node based on the priority information corresponding to the target node.

[0124] The second adjustment subunit is used to perform resource adjustment based on the congestion information corresponding to each node;

[0125] The third processing subunit is used to repeatedly execute the step of reallocating resources for the services corresponding to the target node based on the priority information corresponding to the target node, up to the step of adjusting resources based on the congestion information corresponding to each node, until the fourth preset condition is met and the allocation information corresponding to each node is obtained.

[0126] The fourth preset condition includes at least one of the following:

[0127] The congestion status corresponding to the target node is non-congested;

[0128] The congestion level corresponding to the target node is less than or equal to the second preset threshold;

[0129] The service uses the minimum allowed number of sub-channels.

[0130] The service adopts the maximum allowed MCS level;

[0131] The service uses the maximum allowed service period;

[0132] The service uses the minimum allowed number of transmissions;

[0133] End unnecessary business operations.

[0134] Optionally, the second processing unit includes:

[0135] The third subunit is used to reallocate resources for the services corresponding to each node according to the priority information of each node.

[0136] The third adjustment subunit is used to perform resource adjustment based on the congestion information corresponding to each node;

[0137] The fourth processing subunit is used to repeatedly execute the step of reallocating resources for services corresponding to each node based on the priority information of each node, up to the step of adjusting resources based on the congestion information of each node, until the fifth preset condition is met and the allocation information corresponding to each node is obtained.

[0138] The fifth preset condition includes at least one of the following:

[0139] The congestion status corresponding to the node group is non-congestion;

[0140] The congestion level corresponding to the node group is less than or equal to the second preset threshold;

[0141] The service uses the minimum allowed number of sub-channels.

[0142] The service adopts the maximum allowed MCS level;

[0143] The service uses the maximum allowed service period;

[0144] The service uses the minimum allowed number of transmissions;

[0145] End unnecessary business operations.

[0146] Optionally, the device includes:

[0147] The fifth processing subunit is used to sort the nodes according to the priority information corresponding to each node and according to a preset sorting rule to generate a resource redistribution sequence;

[0148] The fourth redistribution subunit is used to redistribute resources for the services corresponding to each node according to the resource redistribution sequence.

[0149] The preset sorting rule includes at least one of the following:

[0150] Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the business priority from low to high. Then, within the same business priority level, the second level of sorting is performed according to the user priority corresponding to each node from low to high.

[0151] Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the user priority corresponding to each node from low to high. Then, within the same user priority level, the second level of sorting is performed according to the business priority from low to high.

[0152] Based on the comprehensive priority index ranking mechanism, a comprehensive priority index is first generated by weighting the business priority and the user priority corresponding to each node, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

[0153] Optionally, the execution resource adjustment includes at least one of the following:

[0154] Reduce the number of sub-channels occupied;

[0155] Increase MCS level;

[0156] Increase business cycle;

[0157] Reduce the number of data transmissions.

[0158] Optionally, the first processing unit includes:

[0159] The sixth processing subunit is used to determine the channel ratio CR value corresponding to each of the nodes based on the current service allocation information and the current resource allocation information corresponding to each node.

[0160] The first comparison subunit is used to compare the CR value and CBR measurement value corresponding to each node with the pre-configured threshold information to determine the congestion information corresponding to each node. The threshold information includes: CBR threshold and CR threshold.

[0161] The seventh processing subunit is used to determine the congestion information corresponding to the node group based on the congestion information corresponding to each of the nodes.

[0162] Optionally, the first processing unit includes:

[0163] The eighth processing subunit is used to determine the CR value corresponding to each node based on the current service allocation information and current resource allocation information corresponding to each node.

[0164] The ninth processing subunit is used to determine the weighting factor corresponding to each node according to the user priority corresponding to each node.

[0165] The tenth processing subunit is used to perform a weighted summation of the CR values ​​corresponding to each node according to the weighting factor corresponding to each node, and obtain the first CR value;

[0166] The eleventh processing subunit is used to perform weighted summation of the CBR measurement values ​​corresponding to each node according to the weighting factor corresponding to each node, so as to obtain the first CBR value.

[0167] The second comparison subunit is used to compare the first CR value and the first CBR value with pre-configured threshold information to determine the congestion information corresponding to the node group.

[0168] Optionally, the information acquisition module includes:

[0169] The first sending submodule is configured to send a first request to the member node according to a first triggering condition, and receive the first information of the member node fed back by the member node according to the first request, wherein the first request is used to request the sending of the first information of the member node;

[0170] The first receiving submodule is used to receive the first information of the member node reported by the member node according to the second triggering condition;

[0171] The first triggering condition includes at least one of the following:

[0172] Periodic triggering based on a first preset period;

[0173] The event is triggered based on the first event, which includes: the measured value of the CBR corresponding to the group head node is greater than or equal to the fourth preset threshold, and / or the group head node detects the start of a new service;

[0174] The second triggering condition includes at least one of the following:

[0175] Periodic triggering based on a second preset cycle;

[0176] The event is triggered based on a second event, which includes: the member node actively initiating a service request, and / or the member node receiving a trigger message from any node outside the node group to which the group head node belongs.

[0177] Thirdly, embodiments of the present invention provide a control device, including: a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the congestion control method as described in the first aspect.

[0178] Fourthly, embodiments of the present invention provide a computer program product including computer instructions that, when executed by a processor, implement the steps of the method described above.

[0179] Fifthly, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the congestion control method as described in the first aspect.

[0180] The beneficial effects of the above-mentioned technical solution of the present invention are:

[0181] In embodiments of the present invention, the group head node can obtain first information about the member nodes corresponding to the group head node, and send allocation instructions to the member nodes based on the first information, thereby instructing the member nodes to send services. This enables congestion control applicable to group head resource allocation scenarios. Attached Figure Description

[0182] Figure 1 One of the flowcharts illustrating the congestion control method according to an embodiment of the present invention;

[0183] Figure 2 A second flowchart illustrating the congestion control method according to an embodiment of the present invention;

[0184] Figure 3 One of the schematic diagrams illustrating the interaction process between nodes in an embodiment of the present invention;

[0185] Figure 4 This is the second schematic diagram illustrating the interaction process between nodes in an embodiment of the present invention.

[0186] Figure 5 The third schematic diagram illustrating the interaction process between nodes in an embodiment of the present invention;

[0187] Figure 6 A structural block diagram illustrating the congestion control device according to an embodiment of the present invention;

[0188] Figure 7 This is a structural block diagram illustrating the control device according to an embodiment of the present invention. Detailed Implementation

[0189] To make the technical problems, technical solutions, and advantages of this invention clearer, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments. In the following description, specific details such as particular configurations and components are provided merely to aid in a comprehensive understanding of the embodiments of this invention. Therefore, those skilled in the art should understand that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this invention. Furthermore, for clarity and brevity, descriptions of known functions and structures have been omitted.

[0190] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the invention. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0191] In various embodiments of the present invention, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0192] In addition, the terms "system" and "network" are often used interchangeably in this article.

[0193] In the embodiments provided in this application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0194] In this embodiment of the invention, the form of the access network is not limited, and can include access networks such as macro base stations, micro base stations, Node Bs (a term for 3G mobile base stations), enhanced base stations (eNBs), home enhanced base stations (Femto eNBs, Home eNode Bs, Home eNBs, or HeNBs), relay stations, access points, RRUs (Remote Radio Units), and RRHs (Remote Radio Heads). The user terminal can be a mobile phone (or cell phone), or other devices capable of sending or receiving wireless signals, including user equipment, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptops, cordless phones, wireless local loop (WLL) stations, CPEs (Customer Premise Equipment) or mobile smart hotspots capable of converting mobile signals into WiFi signals, smart home appliances, or other devices that can spontaneously communicate with the mobile communication network without human intervention.

[0195] Currently, vehicle-to-everything (V2X) technology, through wireless communication between vehicles, between vehicles and roadside infrastructure, and between vehicles and pedestrians, can perceive the surrounding conditions of vehicles in real time, share road information, and provide timely warnings. It has become a research hotspot for countries around the world to solve road safety problems.

[0196] In existing LTE V2X technology (Rel-14 LTE V2X technology), the PC5 interface (also known as the direct link, protocol-described as Sidelink) for data transmission between User Equipment (UE) and UE can already support basic road safety-based service transmission. This primarily targets service packets with a size between 50-1200 bytes, requiring a transmission reliability of greater than 95% within the specified coverage area.

[0197] With the further development of vehicle-to-everything (V2X) technology, new application scenarios are emerging, such as vehicle platooning, advanced driver assistance systems (ADAS), sensor information sharing, and remote control. Some of these applications require communication between UEs within a group, or unicast communication between two UEs. Therefore, V2X systems need to consider unicast and multicast scenarios. However, existing technologies lack congestion control schemes adapted to group head resource allocation scenarios (i.e., multicast methods).

[0198] The relevant technologies are introduced below:

[0199] The LTE V2X congestion control process (standard process) is as follows:

[0200] Currently, in the 3rd Generation Partnership Project (3GPP) protocol version, LTE V2X transmits services on a single carrier, does not support carrier aggregation, and congestion control is performed at the resource pool level.

[0201] From the receiving perspective, pool-specific CBR measurements are defined for the sending pool (including the transmission pool and the exception pool), illustrating the resource occupancy of each sending pool as perceived by the receiving node.

[0202] If the transmitting UE has a Transmission Block (TB) to transmit in subframe n+4, then CBR measurement needs to be performed in subframe n. The time window for CBR measurement is [n-100, n-1], with a fixed duration of 100ms. During CBR processing, each subframe is a physical subframe.

[0203] For the Physical Sidelink Shared Channel (PSSCH), a Sounding Reference Signal Received Signal Strength Indicator (S-RSSI) threshold for CBR measurement can be configured (or pre-configured), with a value range of [-112, -22] dBm and a granularity of 2 dB. Based on the configured (or pre-configured) S-RSSI threshold at the sub-channel granularity, the S-RSSI of the sub-channels in the transmission pool including the PSSCH is measured within a time window of [n-100, n-1]. The proportion of sub-channels exceeding the threshold relative to the total number of sub-channels within 100 ms is calculated, and this proportion is recorded as the CBR result for the PSSCH of that transmission pool.

[0204] When CBR exceeds the threshold, the following actions can be performed: adjust transmit power; adjust retransmission count; adjust the number of PSSCH sub-channels; adjust MCS Range; and adjust the maximum value of CRlimit.

[0205] From the sender's perspective, by evaluating the transmission pool and exceptional pool CR within 1000ms, the proportion of the node's transmission resources in the transmission pool or exceptional pool can be understood. Based on the measured CR, it can be determined whether the configured CR limit has been exceeded, and the transmission parameters can be adjusted accordingly.

[0206] If the transmitting UE has a TB to transmit in subframe n+4, then CR measurement needs to be performed in subframe n. The time window for CR measurement is [na, n+b], with a fixed duration of 1000ms. The time window is divided into two parts: [na, n-1] corresponds to the subchannels already occupied by the current node, and [n, n+b] corresponds to the subchannels to be occupied by the current node. 'a' is a positive integer, and 'b' is 0 or a positive integer; 'a' and 'b' are determined by the UE implementation, and a+b+1=1000, a>=500, and n+b cannot exceed the reservation time for this transmission from the previous transmission opportunity. Then, the number of subchannels occupied by the current node in these two parts is calculated as a proportion of the total number of subchannels in the entire time window [na, n+b], and this proportion is recorded as the CR result for this transmission pool. In CR processing, each subframe is a physical subframe.

[0207] CR processing can be measured at the per-PPP granularity. Based on per-PPP, the measured CR must satisfy the following relationship:

[0208]

[0209] Where k is the PPPP of the current service package, and i is the PPPP with higher priority than the PPPP of the current service package (i takes a value smaller than k).

[0210] How to handle CRlimit compliance during transmission depends on the UE implementation. For example, packet loss can be implemented during transmission to meet CRlimit.

[0211] The NR V2X congestion control process (standard process) is as follows:

[0212] NR V2X congestion control follows the LTE congestion control process in its standard, meaning the basic framework is consistent, except for a few minor differences. However, the specific algorithm implementation depends on the individual vendors. These differences mainly include: CBR and CR measurement windows (both periodic and aperiodic); measurement timing requirements (related to UE capabilities); the Physical Sidelink Feedback Channel (PSFCH) caused by the frame structure; and different subcarrier spacing (SCS) configurations.

[0213] NR multicast scenario (application description):

[0214] In formation scenarios, there are three types of vehicles: lead vehicle, formation members, and independent vehicles.

[0215] The lead vehicle is the vehicle in the leading position in the convoy's direction of travel, guiding the entire convoy in terms of speed, acceleration, and direction of travel, and is also responsible for allocating communication resources among the convoy members. In addition, the lead vehicle must communicate with other vehicles within its broadcast range to prevent collisions between convoy members and between vehicles, ensuring the safety of the entire convoy and the traffic situation.

[0216] Formation members obtain basic safety information such as position, speed, and acceleration from the lead vehicle and the single-hop leading vehicle, and follow the lead vehicle's movement (this information may not necessarily need to be sent, depending on the length of the convoy, i.e., the non-standard part of message transmission within the specific multicast), thereby maintaining a stable cooperative relationship with the formation.

[0217] An independent vehicle is a vehicle that travels alone without belonging to any convoy and does not have a cooperative relationship with other vehicles. It maintains a normal and safe driving status through periodic communication with other vehicles.

[0218] Current standards do not provide specific guidelines for congestion control in NR multicast scenarios. While LTE congestion control is relatively well-defined (only regular BSM messages are controlled, other messages are not), the control objects for NR services are still undefined.

[0219] Below is an analysis of the potential differences between LTE Basic Safety Message (BSM) and NR multicast congestion control algorithms:

[0220] First, let's make some necessary inferences from the perspective of LTE congestion control: Compared with the roadside unit (RSU) resource pool, the resource pool of the On-Board Unit (OBU) in the LTE system is relatively more limited. Furthermore, the LTE OBU only sends a single BSM message, and the object of LTE congestion control is only the regular BSM broadcast message, that is, there is only one PPP for the corresponding message. The division of the NR resource pool is not yet determined, that is, it is still possible that RSU / OBU use different transmission resource pools, and the NR OBU has various types of messages, increasing the types and categories of service messages (in addition to text messages, there are video messages; in addition to broadcast messages, there are multicast and unicast messages). Although the object of congestion control and the message perspective are not yet determined, it is certain that congestion control of messages other than OBU node BSM messages also needs to be considered.

[0221] Secondly, from another perspective, LTE systems primarily use broadcast applications, while NR systems, in addition to broadcast, also include unicast and multicast applications. Even with admission control, unicast and multicast services differ from calls in cellular networks. Some multicast services may have short connection times, while others may last for extended periods (similar to platooning). During the duration of these services, the surrounding environment can change significantly, making it impossible to manage them through admission control alone. Therefore, congestion control also needs to be considered for NR multicast applications.

[0222] Furthermore, for congestion control of NR multicast communication, the differences between NR multicast message and BSM message mechanisms need to be further considered: LTE congestion control only targets regular BSM broadcast messages, that is, there is only one PPPP for the corresponding message, and since they are all broadcast, it is equivalent to the node detecting the CBR itself and then making corresponding adjustments to the CR (CR is the transmission resource and the transmission parameters of the transmission resource) based on the CBR measurement.

[0223] For multicast communication, the specific resource allocation method has not yet been determined, and the following methods may exist: (1) UE selects autonomously; (2) group head allocates resources; (3) gNB allocates resources; (4) UE is the main user, and the group head or gNB assists in resource allocation. Among them, for method (2), that is, the group head allocates resources, the congestion control process specified by the LTE V2X and NR-V2X standards may not be applicable.

[0224] Specifically, NR multicast has the following characteristics:

[0225] (1) There may be multiple types of services within the NR group, which may correspond to different PPPPs; for congestion control, the corresponding Channel Busy Ratio-Channel Ratio (CBR-CR) mapping for different PPPPs will be different.

[0226] (2) NR multicast services may be non-perfectly asymmetrical, that is, the traffic volume between members and group heads, and even between individual members, is different.

[0227] (3) In the case of a shared resource pool (OBU resource pool), some PPP may correspond to the CR decision made by itself (non-multicast services, or the resource pool determined for a certain UE), while some PPPP may correspond to the CR decision determined by the group header.

[0228] (4) CR is essentially the control of transmission parameters. Under the multicast allocation method, members cannot decide their own transmission resources and transmission parameters (under the group head allocation method, members in the group cannot perform CR processing independently based on the existing process, that is, CR processing needs to be uniformly managed and processed by the group head).

[0229] In summary, the existing BSM message congestion mechanism is not suitable for direct migration to NR multicast messages and has limitations. For example:

[0230] Node A is an independent vehicle, measured by CBR, currently possessing its own CR and the corresponding CRlimit under this CBR; Node B is the group head node, measured by CBR, possessing its own service CR, the CR corresponding to all resources allocated to it, and the corresponding CRlimit under this CBR; Nodes C, D, and E are all group nodes, their resources controlled by the group head node B. Assuming node A is an independent vehicle near node B, and node B's own transmission resource chance is similar to node A's (number of skipped subframes), from this perspective, the CBR measured by nodes A and B are similar, and if node B only considers itself, its corresponding CRlimit is similar. However, for nodes C, D, and E, transmission resources are determined by the group head node B. CR control itself is a form of transmission resource control; transmission parameter control can be HARQ off or transmission parameter control. If the head vehicle does not perform any processing and allocates resources to group members, the group members have no other means of processing besides disabling retransmission (and changing transmission parameters actually affects sensing). In other words, there is currently a lack of congestion control technology for resource allocation by group heads, and corresponding research is needed.

[0231] Specifically, embodiments of the present invention provide a congestion control method, apparatus, control device, program product, and medium, which solves the problem that the prior art lacks a congestion control scheme adapted to the group head resource allocation scenario.

[0232] First Embodiment

[0233] like Figure 1 As shown, an embodiment of the present invention provides a congestion control method, specifically including the following steps:

[0234] Step 11: Obtain the first information of the member nodes corresponding to the group head node. The member nodes corresponding to the group head node include at least one node in the node group to which the group head node belongs, excluding the group head node itself.

[0235] In other words, the group head node can obtain the first information calculated by the group members (i.e., the member nodes corresponding to the group head node). This first information includes at least one of the following:

[0236] (1) The measured value of the channel busy ratio (CBR), which is the current CBR measurement value of the group member.

[0237] (2) The business type of the first target business, which is the business that is about to be triggered, that is, the business type of the business that the group member is about to trigger.

[0238] (3) The business priority of the first target business, that is, the business priority of the business that the group member is about to trigger.

[0239] Step 12: Based on the first information, send an allocation instruction to the member node, the allocation instruction being used to instruct the service to be sent.

[0240] In this embodiment, the group head node can obtain the first information of the member nodes corresponding to the group head node, and send allocation instructions to the member nodes according to the first information, thereby instructing the member nodes to send services. In this way, congestion control applicable to group head resource allocation scenarios can be achieved.

[0241] In some embodiments, obtaining the first information of the member nodes corresponding to the group head node includes at least one of the following:

[0242] (i) Based on a first triggering condition, a first request is sent to the member node, and the first information of the member node is received from the member node in response to the first request. The first request is used to request the sending of the first information of the member node. Wherein, the first triggering condition includes at least one of the following: (1) periodic triggering based on a first preset period; (2) event triggering based on a first event, the first event including: the measured value of the CBR corresponding to the group head node is greater than or equal to a fourth preset threshold, and / or, the group head node detects the start of a new service.

[0243] Specifically, the group head (i.e., the group head node mentioned above) can request first information from group members on demand or periodically. For example, periodic triggering based on a first preset period can be achieved by the group head sending configuration information to group members during business / resource configuration, configuring group members (i.e., the member nodes mentioned above) to report first information (CBR information, i.e., the measured value of CBR) to the group head at the first preset period (e.g., every 100ms). The on-demand request triggering mechanism is event triggering based on the first event. Specifically, when the group head determines that its calculated CBR value exceeds the threshold (i.e., the fourth preset threshold), it can request first information (such as CBR information) from each group member (that is, send a first request to the group member to request the group member to report first information to the group head), or the group head can request first information (such as CBR information) from each group member when it determines that a new business is triggered.

[0244] (ii) Receive the first information of the member node reported by the member node according to the second triggering condition. Wherein, the second triggering condition includes at least one of the following: (1) periodic triggering based on a second preset period; (2) event triggering based on a second event, the second event including: the member node actively initiates a service request, and / or, the member node receives a trigger message sent by any node outside the node group to which the group head node belongs.

[0245] Specifically, group members (i.e., the member nodes mentioned above) report the first piece of information to the group head on demand or periodically. Here, the triggering mechanism for on-demand reporting is based on the event triggering of the second event, which can include active triggering (e.g., the second event is triggered by a group member actively initiating a business) and / or passive triggering (e.g., the second event is triggered when a group member receives a message from an external node; here, an external node is any node outside the node group to which the group head node belongs, such as a vehicle or RSU).

[0246] In some embodiments, step 12, sending an allocation instruction to the member node based on the first information, includes:

[0247] Step 1201: Determine the user priority corresponding to each node according to the second information corresponding to each node in the node group. The second information includes: vehicle type and / or vehicle location.

[0248] It should be noted that in step 1201, the group head determines the user priority of each node (i.e., the group head and group members) in ways including but not limited to the following:

[0249] Method 1: The group leader determines the user priority of a node based on its position within the convoy. For example, the user priority corresponding to the group leader is set to the highest priority, the user priority of nodes corresponding to edge members of the convoy (such as vehicles at the rear, leftmost, or rightmost positions) is set to the second highest priority, and the user priority of nodes corresponding to the remaining vehicles is set to the lowest priority.

[0250] Method 2: The group head determines the user priority corresponding to the node based on the vehicle type (that is, the vehicle type corresponding to the node). For example, large vehicles have high priority, medium vehicles have the second highest priority, and small vehicles have low priority.

[0251] Step 1202: Based on the user priority corresponding to each node and the first information, determine the allocation information corresponding to each node. The allocation information includes: service allocation information and resource allocation information.

[0252] Here, the service allocation information includes at least one of the following: the number of services sent by members within the group (i.e., nodes including the group head node and member nodes); the application layer transmission cycle for each service; the service priority; and the service's maximum transmission rate. The maximum transmission rate is equal to the ratio of the maximum transport block size (TBS) to the application layer transmission cycle.

[0253] Resource allocation information includes at least one of the following: the number of services sent by members within the group; the service transmission parameters for each service; and the time-frequency resources for each service. Here, the service transmission parameters may include at least one of the following: MCS, occupied resource block (RB), TBS, and number of transmissions.

[0254] It should be noted that each node in step 1202 includes a group head (i.e., the group head node) and group members (the group head and group members). The first information corresponding to the group head may specifically include at least one of the following: the current CBR measurement value calculated by the group head; the service type of the service that the group head is about to trigger; and the service priority of the service that the group head is about to trigger.

[0255] In step 1202 above, such as Figure 2 As shown, the group head can make congestion control decisions (that is, determine the allocation information corresponding to each node) based on one or more pieces of information such as the current service allocation information of each node, the current resource allocation information, the first information (such as the current CBR measurement value calculated by the group head and group members, the service type and service priority of the service that the group head and / or group members are about to trigger, and the user priority of the group head and / or group members).

[0256] Step 1203: Send the allocation instruction to the member node, the allocation instruction including the allocation information corresponding to the member node.

[0257] Here, after the group leader sends the allocation information (i.e., service allocation information and resource allocation information) after the congestion control decision to each group member through the allocation instruction, the group leader and each group member can send services according to the new service allocation information and resource allocation information.

[0258] It should be noted that when a certain service of a member in the group (including the group head and group members) is completed, the group head can determine whether the group congestion status and / or group congestion level has changed based on the current CBR measurement value obtained, thereby triggering the congestion control decision of the group head and group members again.

[0259] In some embodiments, step 1202, determining the allocation information corresponding to each node based on the user priority corresponding to each node and the first information, includes:

[0260] (i) Based on the first information corresponding to each node, determine the congestion information corresponding to each node and the congestion information corresponding to the node group, wherein the congestion information includes: congestion status and / or congestion level.

[0261] Here, in the congestion information corresponding to a node, the congestion state of the node can also be called the member congestion state, and the congestion level of the node can also be called the member congestion level. Among them, the member congestion state can include congestion and no congestion; the member congestion level can be a number from 1 to 7, with 1 being the lowest level and 7 being the highest level.

[0262] In the congestion information corresponding to a node group, the congestion state of the node group can also be called the group congestion state, and the congestion level of the node group can also be called the group congestion level. Specifically, the group congestion state can include: no congestion, partial congestion, and full congestion; the group congestion level can be represented by numbers 1 to 7, where 1 is the lowest level and 7 is the highest level.

[0263] In some specific examples, group congestion status and / or group congestion level can be determined in the following ways:

[0264] Method 1:

[0265] The group head node first determines the member congestion status (i.e., the congestion status corresponding to the node) and / or member congestion level (i.e., the congestion level corresponding to the node) of each member in the group, and then determines the group congestion status (i.e., the congestion status corresponding to the node group) and / or group congestion level (i.e., the congestion level corresponding to the node group).

[0266] In one specific embodiment, the process of determining the congestion information corresponding to each node and the congestion information corresponding to the node group based on the first information corresponding to each node includes:

[0267] Step (1): Determine the channel ratio (CR) value corresponding to each node based on the current service allocation information and current resource allocation information corresponding to each node.

[0268] In other words, the group head can determine the CR value of each member in the group based on the current business allocation information and current resource allocation information of the members in the group (i.e., each node in the node group to which the group head node belongs). It should be noted that if there are multiple businesses (including businesses that are about to be initiated), the CR value of all businesses needs to be calculated.

[0269] Step (2): Based on the CR value and CBR measurement value corresponding to each node, compare them with the pre-configured threshold information to determine the congestion information corresponding to each node. The threshold information includes: CBR threshold and CR threshold.

[0270] The group head determines the member congestion status and / or member congestion level of each member in each group based on the calculated CR value of the members in the group, the current CBR measurement value calculated by the members in the group, the pre-configured CBR threshold and CR-limit threshold (that is, CR threshold).

[0271] Specifically, the congestion level of a member can be determined by comparing the CBR measurement value of the node with the CBR threshold.

[0272] For example, in a specific example, the mapping relationship between Index (representing the congestion level), CBR threshold, and CR-limit threshold (i.e., the CR threshold mentioned above) is shown in the table below:

[0273] 1 0.3 0.3 2 0.5 0.1 3 0.6 0.06 4 0.7 0.03 5 0.8 0.008 6 1 0.004

[0274] If a node has a CBR value of 0.48 and a CR value of 0.042, since the CBR value (0.48) ≤ 0.5 (that is, it is within the range of thresholds 0.3 and 0.5), the node's Index is determined to be 2 (that is, the member congestion level is 2), and the corresponding CR threshold is 0.1. Since the node's CR value (0.042) is lower than 0.1, the member congestion state is non-congested.

[0275] Step (3): Determine the congestion information corresponding to the node group based on the congestion information corresponding to each node.

[0276] In other words, the group head can determine the group congestion status and / or group congestion level based on the congestion status and / or congestion level of all group members. Specifically, as an optional example, if all group members are in a non-congested state, the group congestion status is determined to be non-congested; if some group members are in a congested state, the group congestion status is determined to be partially congested; if all group members are in a congested state, the group congestion status is determined to be congested.

[0277] In one alternative example, the group congestion level can be determined as the lowest among the member congestion levels corresponding to each node; in another alternative example, the group congestion level can be determined as the highest among the member congestion levels corresponding to each node; in yet another alternative example, the average of the member congestion levels corresponding to each node can be calculated, and this average can be used as the group congestion level. It is understood that if this average is not an integer, it can be rounded up or down to obtain the final group congestion level.

[0278] Method 2:

[0279] The group head determines a unique CR value and a unique CBR measurement value based on the information of all members in the group, and then performs weighted processing based on the user priority of the members in the group to finally determine the group congestion status and / or group congestion level.

[0280] In some embodiments, the process of determining the congestion information corresponding to each node and the congestion information corresponding to the node group based on the first information corresponding to each node specifically includes:

[0281] Step (1): Determine the CR value corresponding to each node based on the current service allocation information and current resource allocation information corresponding to each node.

[0282] In other words, the group leader can determine the CR value of each member within the group based on their current business allocation and resource allocation information. It should be noted that if there are multiple businesses (including those about to be initiated), the CR value for all businesses needs to be calculated.

[0283] Step (2): Determine the weighting factor for each node according to the user priority corresponding to each node.

[0284] In this step, the group head determines the weighting factor for each member within the group based on the group member priority (i.e., the user priority corresponding to the node). It should be noted that the sum of all weighting factors is 1.

[0285] Step (3): Based on the weighting factor corresponding to each node, perform a weighted summation of the CR values ​​corresponding to each node to obtain the first CR value.

[0286] In this step, the group head performs a weighted summation of the CR values ​​of each member in the group (i.e., summing the CR values ​​by multiplying them by a weighting factor) to obtain a unique CR value (i.e., the first CR value).

[0287] Step (4): Based on the weighting factor corresponding to each node, the measured CBR values ​​corresponding to each node are weighted and summed to obtain the first CBR value.

[0288] In this step, the group head performs a weighted summation of the current CBR measurements calculated by each member of the group (i.e., summing the current CBR measurements by multiplying the weighting factor), or calculates the linear average of the current CBR measurements to obtain a unique CBR measurement (i.e., the first CBR value).

[0289] Step (5): Based on the first CR value and the first CBR value, compare them with the pre-configured threshold information to determine the congestion information corresponding to the node group.

[0290] In this step, the group head determines the group congestion status and / or group congestion level based on the unique CR value (i.e., the first CR value), the unique CBR measurement value (i.e., the first CBR value), the pre-configured CBR threshold and CR-limit threshold (i.e., the CR threshold).

[0291] In a specific optional example, the first CBR value can be compared with the CBR threshold to determine the group congestion level, and then the group congestion status can be determined according to the CR threshold corresponding to the group congestion level.

[0292] For example, in a specific example, the current CBR measurement values corresponding to the group members are 0.65, 0.64, 0.63, and 0.63 respectively. The group head calculates the linear average of these CBR measurement values to obtain a unique CBR measurement value (i.e., the first CBR value) of 0.646; the group head determines the CR value of each group member according to the current service allocation information and current resource allocation information within the group, multiplies the CR value of each group member by the weighting factor and sums them to obtain a unique CR value (i.e., the first CR value) of 0.047. Since the first CBR value ≤ 0.7 (i.e., 0.6 < CBR ≤ 0.7, that is, the first CBR value is within the range between the threshold 0.6 and the threshold 0.7), according to the mapping relationship among the congestion level, CBR threshold, and CR threshold, the group congestion level (Index) can be determined to be 4, and then the corresponding CR threshold is determined to be 0.03. Since the first CR value (0.047) exceeds 0.03, the group congestion status is determined to be congested.

[0293] It should be noted that the group congestion status in this second method only includes congested and non-congested.

[0294] (II) According to the congestion information corresponding to the node group and the priority information corresponding to each node, the allocation information corresponding to each node is determined respectively, and the priority information includes: the user priority and / or the service priority.

[0295] It should be noted that the group head can make congestion control decisions for the group head and group members, so as to determine the allocation information corresponding to each node, and send allocation instructions to the member nodes accordingly. Specifically, the group head can determine the basic services that the group head and group members need to trigger according to the group service requirements and road safety considerations, and configure the allocation service information and resource information for the basic services according to the pre-configured parameters. The group head sends the service allocation information and resource allocation information of the basic services to the corresponding group members; after the group head receives the current CBR measurement values reported by the group members, it can determine the group congestion status and / or group congestion level according to one or more information such as the current service allocation information, current resource allocation information, current CBR measurement values calculated by the group head and group members, pre-configured CBR threshold and CR-limit threshold, and user priorities of the group head and group members, and further make congestion control decisions based on this.

[0296] Next, the congestion control process in different situations will be described in detail.

[0297] In some embodiments, when a first preset condition is met, determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node includes:

[0298] (i) Determine whether the congestion state corresponding to the node group has changed and / or whether the decrease in the congestion level corresponding to the node group exceeds a first preset threshold. The first preset condition includes: the congestion state corresponding to the node group is not congested, and / or the congestion level corresponding to the node group is less than or equal to the first preset threshold.

[0299] (ii) If the congestion status of the node group changes and / or the reduction exceeds the first preset threshold, resource reallocation shall be prioritized for the second target service that meets the second preset condition. The second preset condition includes: the service priority corresponding to the service is greater than or equal to the first priority, and / or, the user priority corresponding to the node associated with the service is greater than or equal to the second priority.

[0300] It should be noted that if congestion control has not been performed on the current service allocation and current resource allocation, then congestion control can be omitted, and the current service allocation information and current resource allocation information can continue to be used. If congestion control has been performed on the current service allocation and current resource allocation, it is necessary to determine whether the congestion status (i.e., group congestion status) corresponding to the node group has changed and / or whether the reduction in the congestion level (i.e., group congestion level) corresponding to the node group exceeds the first preset threshold. If the group congestion status has changed and / or the reduction in the group congestion level exceeds the first preset threshold, then resources will be reallocated to the second target service under the second preset condition (i.e., high service priority service or service of group members with high user priority).

[0301] (iii) Perform resource adjustments based on the congestion information corresponding to each node.

[0302] In some specific embodiments, the execution resource adjustment includes at least one of the following: (1) increasing the number of sub-channels occupied; (2) reducing the modulation and coding scheme (MCS) level; (3) shortening the service cycle; and (4) increasing the number of data transmissions.

[0303] (iv) Repeat the step of prioritizing resource reallocation for the second target service that meets the second preset condition, until the step of performing resource adjustment based on the congestion information corresponding to each node is performed, until the third preset condition is met and the allocation information corresponding to each node is obtained.

[0304] The third preset condition includes at least one of the following:

[0305] (1) The congestion state corresponding to the node is non-congestion.

[0306] (2) The congestion level corresponding to the node is less than or equal to the second preset threshold (i.e., the congestion threshold).

[0307] It should be noted that the congestion status and / or congestion level of the node in the third preset condition are determined based on the newly allocated service allocation information and resource allocation information.

[0308] (3) For the services that are about to be triggered, resources are allocated using pre-configured service parameters.

[0309] It should be noted that if there is a service that is about to be triggered, resources will be allocated normally for this service according to the pre-configured parameters.

[0310] In this embodiment, when performing congestion control, the group head can take one or more actions based on the congestion information corresponding to the node (i.e., member congestion level and / or member congestion status), such as increasing sub-channel occupancy, reducing MCS, reducing service cycle, and increasing transmission count, until the third preset condition is met based on the newly allocated service allocation information and resource allocation information.

[0311] In some embodiments, when the congestion state corresponding to the node group is partial congestion, determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node includes:

[0312] (i) Based on the congestion information corresponding to the node group, at least one target node is determined, the target node including: the node whose congestion state is congested, and / or the node whose congestion level is greater than or equal to a third preset threshold.

[0313] In other words, if the group congestion state (i.e. the congestion state corresponding to the node group) is partially congested, the group head can choose to perform congestion control only on one or more group members (i.e., target nodes) that are in the "congestion" state (i.e., the congestion state is congested), and / or perform congestion control on one or more group members (i.e., target nodes) with a higher congestion level (i.e., the congestion level is greater than or equal to the third preset threshold).

[0314] (ii) Based on the priority information corresponding to the target node, resources are reallocated to the services corresponding to the target node.

[0315] It should be noted that the business here includes both triggered business and business that is about to be triggered. That is to say, if there is a business that is about to be triggered by a member of the group, congestion control is also required when allocating resources for this business. In other words, the resource adjustment in step (iii) below needs to be performed until the fourth preset condition is met.

[0316] (iii) Perform resource adjustments based on the congestion information corresponding to each node.

[0317] In some specific examples, the performance resource adjustment includes at least one of the following: (1) reducing the number of sub-channels occupied; (2) increasing the MCS level; (3) increasing the service cycle; and (4) reducing the number of data transmissions.

[0318] (iv) Repeat the step of reallocating resources for the services corresponding to the target node based on the priority information of the target node, until the step of adjusting resources based on the congestion information of each node is executed, until the fourth preset condition is met and the allocation information corresponding to each node is obtained. The fourth preset condition includes at least one of the following:

[0319] (1) The congestion state corresponding to the target node is non-congestion;

[0320] (2) The congestion level corresponding to the target node is less than or equal to the second preset threshold (i.e., the congestion threshold);

[0321] (3) The service adopts the minimum allowed number of sub-channels;

[0322] (4) The service adopts the maximum allowed MCS level;

[0323] (5) The service shall use the maximum permitted service period;

[0324] (6) The service uses the minimum number of allowed transmissions;

[0325] (7) End unnecessary business.

[0326] In other words, when the group head performs congestion control on the members within the group, it can reallocate resources for services based on the priority information corresponding to the target node, and take one or more actions based on the congestion information corresponding to the node (i.e., member congestion level and / or member congestion status), such as reducing the number of sub-channels occupied, increasing the MCS level, increasing the service cycle, and reducing the number of transmissions (i.e., data transmission times), until the fourth preset condition is met based on the newly allocated service allocation information and resource allocation information.

[0327] It should be noted that the congestion status and / or congestion level corresponding to the target node in the fourth preset condition are determined based on the newly allocated service allocation information and resource allocation information.

[0328] In some embodiments, when the congestion state (i.e., group congestion state) corresponding to the node group is congested or fully congested, the step of determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node includes:

[0329] (i) Based on the priority information of each node, resources are reallocated to the services corresponding to each node.

[0330] It should be noted that the business corresponding to the node here includes both triggered business and business that is about to be triggered. In other words, if there is a business that is about to be triggered in a member of the group, congestion control is also required when allocating resources for this business. That is, the resource adjustment in step (II) below needs to be performed until the fifth preset condition is met.

[0331] It should be noted that when the congestion status of the above node group is partial congestion, or when the congestion status of the node group is congested or fully congested, the following method can be used:

[0332] In some specific embodiments, resource reallocation is performed on the services corresponding to the nodes based on the priority information corresponding to the nodes, including:

[0333] Step 1: Based on the priority information of each node, sort the nodes according to the preset sorting rules to generate a resource redistribution sequence.

[0334] It should be noted that when the congestion state of the aforementioned node group is partial congestion, the group head can only perform congestion control on the selected target nodes. Therefore, in this case, step 1 can only be performed on each target node, sorting them according to a preset sorting rule to generate the corresponding resource redistribution sequence. It can be understood that if the congestion state of the node group is congested or fully congested, step 1 can be performed on all members of the group, that is, on the group head node and all member nodes, sorting the nodes according to the preset sorting rule to generate the resource redistribution sequence.

[0335] The preset sorting rule includes at least one of the following:

[0336] (1) Based on the dual-dimensional priority sorting mechanism, the first level of sorting is performed according to the business priority from low to high, and then the second level of sorting is performed according to the user priority corresponding to each node from low to high within the same business priority level.

[0337] (2) Based on the dual-dimensional priority sorting mechanism, the first level of sorting is performed according to the user priority of each node from low to high, and then the second level of sorting is performed according to the business priority from low to high within the same user priority level.

[0338] (3) Based on the comprehensive priority index sorting mechanism, firstly, a weighted calculation is performed according to the business priority and the user priority corresponding to each node to generate a comprehensive priority index, and then the comprehensive priority index is sorted in order from low to high.

[0339] Step 2: According to the resource redistribution sequence, perform resource redistribution on the services corresponding to each node.

[0340] In this embodiment, the group head performs congestion control on all members within the group, and the congestion control order can be any of the following methods:

[0341] Method 1: First, reallocate resources to the group members according to their business priority from low to high, and then according to the user priority of the group members from low to high.

[0342] Method 2: First, reallocate resources to the group members according to their user priority from low to high, and then according to their business priority from low to high.

[0343] Method 3: Determine new priorities based on business priorities and user priorities within the group, and reallocate resources to the business of group members in ascending order of the new priorities.

[0344] (ii) Perform resource adjustments based on the congestion information corresponding to each node.

[0345] In some specific examples, the performance resource adjustment includes at least one of the following: (1) reducing the number of sub-channels occupied; (2) increasing the MCS level; (3) increasing the service cycle; and (4) reducing the number of data transmissions.

[0346] (III) Repeat the step of reallocating resources for services corresponding to each node based on the priority information of each node, until the step of adjusting resources based on the congestion information of each node is executed, until the fifth preset condition is met and the allocation information corresponding to each node is obtained. The fifth preset condition includes at least one of the following:

[0347] (1) The congestion state corresponding to the node group is non-congestion;

[0348] (2) The congestion level corresponding to the node group is less than or equal to the second preset threshold (i.e., the congestion threshold);

[0349] (3) The service adopts the minimum allowed number of sub-channels;

[0350] (4) The service adopts the maximum allowed MCS level;

[0351] (5) The service shall use the maximum permitted service period;

[0352] (6) The service uses the minimum number of allowed transmissions;

[0353] (7) End unnecessary business (end one or more unnecessary business).

[0354] It should be noted that the congestion status and / or congestion level corresponding to the node group in the fifth preset condition are determined based on the newly allocated service allocation information and resource allocation information.

[0355] In this embodiment, the group head reallocates resources for the services of the members within the group. Specifically, based on the congestion information corresponding to the node (i.e., the member's congestion level and / or member's congestion status), it takes one or more actions, such as reducing the number of sub-channels occupied, increasing the MCS level, increasing the service cycle, and reducing the number of transmissions, until the fifth preset condition is met based on the newly allocated service / resource information.

[0356] The following provides specific examples illustrating the solutions provided in the embodiments of the present invention.

[0357] Example 1:

[0358] like Figure 3 As shown, the group head determines the basic business of each node (that is, the members in the group, including the group head and the members) and performs the initial business / resource allocation process.

[0359] First, after the vehicle platoon is established, to ensure the safe and orderly operation of the platoon, the platoon leader needs to determine the basic business processes that each member of the platoon should trigger. Specifically, the platoon leader (i.e., the platoon leader node) should trigger at least one of the following messages: basic vehicle safety message, platoon management message, platoon control message, and platoon business resource allocation instruction message; the platoon members (i.e., the member nodes corresponding to the platoon leader node, such as members of the first / second / third / fourth platoon) should trigger at least one of the following messages: platoon management message, platoon control message, and business resource status reporting message.

[0360] Then, the group head performs initial service allocation and / or resource allocation for the basic services of each member within the group (i.e., each node). Specifically, the group head can allocate services and resources according to pre-configured parameters. To avoid the impact of half-duplex operation, the group head needs to allocate different time-frequency resources to each member within the group. In a specific example, the service allocation information and resource allocation information after the group head's allocation are as follows:

[0361] Group Header: Number of services: 4; Among them, Service 1 (Vehicle Basic Safety Message): Application layer transmission period is 100ms, service priority is 2, MCS is 7, RB occupied is 27, TBS is 3368, transmission count is 2, and time-frequency resource is time-frequency resource 1; Service 2 (Formation Management Message): Application layer transmission period is 200ms, service priority is 3, MCS is 8, RB occupied is 48, TBS is 6712, transmission count is 2, and time-frequency resource is time-frequency resource 2; Service 3 (Formation Control Message): Application layer transmission period is 50ms, service priority is 3, MCS is 12, RB occupied is 48, TBS is 9528, transmission count is 2, and time-frequency resource is time-frequency resource 3; Service 4 (Intra-group Service Resource Allocation Indication Message): Application layer transmission period is 200ms, service priority is 3, MCS is 8, RB occupied is 48, TBS is 6712, transmission count is 2, and time-frequency resource is time-frequency resource 4.

[0362] Group 1: Number of services: 3; Service 1 (Flag Management Message): Application layer sending period is 200ms, service priority is 3, MCS is 8, RB occupied is 48, TBS is 6712, number of transmissions is 2, and time-frequency resource is 5; Service 2 (Flag Control Message): Application layer sending period is 100ms, service priority is 3, MCS is 12, RB occupied is 48, TBS is 9528, number of transmissions is 2, and time-frequency resource is 6; Service 3 (Service Resource Status Reporting Message): Application layer sending period is 100ms, service priority is 5, MCS is 7, RB occupied is 27, TBS is 3368, number of transmissions is 2, and time-frequency resource is 7.

[0363] The second group consists of 3 services: Service 1 (Flag Management Message): Application layer sending period is 200ms, service priority is 3, MCS is 8, RB usage is 48, TBS is 6712, transmission count is 2, and time-frequency resource is 8; Service 2 (Flag Control Message): Application layer sending period is 100ms, service priority is 3, MCS is 12, RB usage is 48, TBS is 9528, transmission count is 2, and time-frequency resource is 9; Service 3 (Service Resource Status Reporting Message): Application layer sending period is 100ms, service priority is 5, MCS is 7, RB usage is 27, TBS is 3368, transmission count is 2, and time-frequency resource is 10.

[0364] The third group consists of 3 services: Service 1 (Flag Management Message): Application layer sending period is 200ms, service priority is 3, MCS is 8, RB usage is 48, TBS is 6712, transmission count is 2, and time-frequency resource is 11; Service 2 (Flag Control Message): Application layer sending period is 100ms, service priority is 3, MCS is 12, RB usage is 48, TBS is 9528, transmission count is 2, and time-frequency resource is 12; Service 3 (Service Resource Status Reporting Message): Application layer sending period is 100ms, service priority is 5, MCS is 7, RB usage is 27, TBS is 3368, transmission count is 2, and time-frequency resource is 13.

[0365] The fourth group consists of 3 services: Service 1 (Flag Management Message): Application layer sending period is 200ms, service priority is 3, MCS is 8, RB usage is 48, TBS is 6712, transmission count is 2, and time-frequency resource is 14; Service 2 (Flag Control Message): Application layer sending period is 100ms, service priority is 3, MCS is 12, RB usage is 48, TBS is 9528, transmission count is 2, and time-frequency resource is 15; Service 3 (Service Resource Status Reporting Message): Application layer sending period is 100ms, service priority is 5, MCS is 7, RB usage is 27, TBS is 3368, transmission count is 2, and time-frequency resource is 16.

[0366] Finally, the group leader can send the basic business allocation information and resource allocation information of each group member to each group member through the group's business resource allocation instruction message.

[0367] Example 2:

[0368] After the initial business allocation process and the initial resource allocation process are completed, group members report the CBR measurement value to the group head every 100ms.

[0369] Specifically, as Figure 4 shown, after the initial service / resource allocation process is completed, each group member sends services according to the service allocation information and resource allocation information assigned by the group head. Among them, each group member reports the CBR measurement value to the group head every 100 ms. After receiving the current CBR measurement value reported by the group member, the group head can determine the Index (index) based on the current service allocation information, current resource allocation information, and the calculated current CBR measurement value, pre-configured CBR threshold, and CR-limit threshold of this group member, and then determine the CR limit threshold. In addition, the group head can also calculate the CR value of the group member, and determine whether the calculated CR value exceeds the CR limit threshold, so as to determine the congestion state (i.e., the congestion state corresponding to the node) and / or member congestion level (i.e., the congestion level corresponding to the node) of this group member.

[0370] Among them, in a specific example, the mapping relationship among Index, CBR threshold, and CR-limit threshold (i.e., the above-mentioned CR threshold) is shown in the following table:

[0371] 1 0.3 0.3 2 0.5 0.1 3 0.6 0.06 4 0.7 0.03 5 0.8 0.008 6 1 0.004

[0372] It should be noted that the specific values of the CBR threshold and CR limit threshold in this table can be set according to actual needs.

[0373] Group head: The CBR value is 0.36; the CR value is equal to (3 * 2 / 100 + 5 * 2 / 200 + 5 * 2 / 50 + 5 * 2 / 200) / 5 = 0.072; according to the current CBR measurement value (0.36) within the range of 0.3 < CBR ≤ 0.5, determine that Index is 2, determine the CR limit threshold is 0.1, and judge that the calculated CR value (0.072) is lower than the CR limit threshold. Therefore, the member congestion state of the group head is not congested, and the member congestion level is 2.

[0374] The first group member: The CBR value is 0.34; the CR value is equal to (5 * 2 / 200 + 5 * 2 / 100 + 3 * 2 / 100) / 5 = 0.042; according to the current CBR measurement value (0.34) within the range of 0.3 < CBR ≤ 0.5, determine that Index is 2, determine the CR limit threshold is 0.1, and judge that the calculated CR value (0.042) is lower than the CR limit threshold. Therefore, the member congestion state of the first group member is not congested, and the member congestion level is 2.

[0375] Members of the second group: The CBR value is 0.33; the CR value is equal to (5 * 2 / 200 + 5 * 2 / 100 + 3 * 2 / 100) / 5 = 0.042; according to the current CBR measurement value (0.33) within the range of 0.3 < CBR ≤ 0.5, Index is determined to be 2, the CR limit threshold is determined to be 0.1, and it is judged that the calculated CR value (0.042) is lower than the CR limit threshold. Therefore, the congestion status of the members of the second group is non-congested, and the member congestion level is 2.

[0376] Members of the third group: The CBR value is 0.35; the CR value is equal to (5 * 2 / 200 + 5 * 2 / 100 + 3 * 2 / 100) / 5 = 0.042; according to the current CBR measurement value (0.35) within the range of 0.3 < CBR ≤ 0.5, Index is determined to be 2, the CR limit threshold is determined to be 0.1, and it is judged that the calculated CR value (0.042) is lower than the CR limit threshold. Therefore, the congestion status of the members of the third group is non-congested, and the member congestion level is 2.

[0377] Members of the fourth group: The CBR value is 0.34; the CR value is equal to (5 * 2 / 200 + 5 * 2 / 100 + 3 * 2 / 100) / 5 = 0.042; according to the current CBR measurement value (0.34) within the range of 0.3 < CBR ≤ 0.5, Index is determined to be 2, the CR limit threshold is determined to be 0.1, and it is judged that the calculated CR value (0.042) is lower than the CR limit threshold. Therefore, the congestion status of the members of the fourth group is non-congested, and the member congestion level is 2.

[0378] In this way, the group head determines the group congestion status as non-congested and the group congestion level as 2 based on the member congestion status and member congestion level of each group member, and accordingly determines not to perform congestion control.

[0379] When the formation vehicles drive to the suburban intersection, the group head receives the current CBR measurement values reported by the group members again. At this time, the group head re-determines the member congestion status and member congestion level of the group members based on information such as the current service allocation information, current resource allocation information, current CBR measurement values calculated by the group members, pre-configured CBR thresholds, and CR-limit thresholds, as follows:

[0380] Group header: The CBR value is 0.52; the CR value is equal to (3*2 / 100 + 5*2 / 200 + 5*2 / 50 + 5*2 / 200) / 5 = 0.072; according to the current CBR measurement value (0.52) within the range of 0.5 < CBR ≤ 0.6, the Index is determined to be 3, the CR limit threshold is determined to be 0.06, and it is judged that the calculated CR value (0.072) exceeds the CR limit threshold. Therefore, the member congestion status is congested and the member congestion level is 3.

[0381] The first group member: The CBR value is 0.46; the CR value is equal to (5*2 / 200 + 5*2 / 50 + 3*2 / 100) / 5 = 0.042; according to the current CBR measurement value (0.46) within the range of 0.3 < CBR ≤ 0.5, the Index is determined to be 2, the CR limit threshold is determined to be 0.1, and it is judged that the calculated CR value (0.042) is lower than the CR limit threshold. Therefore, the member congestion status is non-congested and the member congestion level is 2.

[0382] The second group member: The CBR value is 0.48; the CR value is equal to (5*2 / 200 + 5*2 / 50 + 3*2 / 100) / 5 = 0.042; according to the current CBR measurement value (0.48) within the range of 0.3 < CBR ≤ 0.5, the Index is determined to be 2, the CR limit threshold is determined to be 0.1, and it is judged that the calculated CR value (0.042) is lower than the CR limit threshold. Therefore, the member congestion status is non-congested and the member congestion level is 2.

[0383] The third group member: The CBR value is 0.45; the CR value is equal to (5*2 / 200 + 5*2 / 50 + 3*2 / 100) / 5 = 0.042; according to the current CBR measurement value (0.45) within the range of 0.3 < CBR ≤ 0.5, the Index is determined to be 2, the CR limit threshold is determined to be 0.1, and it is judged that the calculated CR value (0.042) is lower than the CR limit threshold. Therefore, the member congestion status is non-congested and the member congestion level is 2.

[0384] The fourth group member: The CBR value is 0.46; the CR value is equal to (5*2 / 200 + 5*2 / 50 + 3*2 / 100) / 5 = 0.042; according to the current CBR measurement value (0.46) within the range of 0.3 < CBR ≤ 0.5, the Index is determined to be 2, the CR limit threshold is determined to be 0.1, and it is judged that the calculated CR value (0.042) is lower than the CR limit threshold. Therefore, the member congestion status is non-congested and the member congestion level is 2.

[0385] In this way, the group head determines that the group congestion state is partially congested and the group congestion level is 3 based on the member congestion state and member congestion level of each group member, and accordingly determines that congestion control needs to be performed. Among them, congestion control is performed on the group head in the "congested" state. In this congestion control, the application layer sending period of service 3 (formation control message) is increased to 100 ms. The recalculated CR value is equal to (3*2 / 100 + 5*2 / 200 + 5*2 / 100 + 5*2 / 200) / 5 = 0.052, which is lower than the CR-limit threshold of 0.06. Therefore, the member congestion state of the group head changes to non-congested, and at the same time the group congestion state changes to non-congested. The group head sends a formation control message according to the new service allocation information of service 3.

[0386] When the formation vehicles drive to the urban intersection, after the group head receives the current CBR measurement values reported by the group members again, at this time, the group head determines the member congestion state and member congestion level of the group members according to the current service allocation information, current resource allocation information, current CBR measurement values calculated by the group members, pre-configured CBR threshold and CR-limit threshold and other information, as follows:

[0387] Group head: The CBR value is 0.68; (3*2 / 100 + 5*2 / 200 + 5*2 / 100 + 5*2 / 200) / 5 = 0.052; According to the current CBR measurement value (0.68) within the range of 0.6 < CBR ≤ 0.7, Index is determined to be 4, the CR limit threshold is determined to be 0.03, and it is judged that the calculated CR value (0.052) exceeds the CR limit threshold. Therefore, the member congestion state is congested and the member congestion level is 4.

[0388] The first group member: The CBR value is 0.63; The CR value is equal to (5*2 / 200 + 5*2 / 50 + 3*2 / 100) / 5 = 0.042; According to the current CBR measurement value (0.63) within the range of 0.6 < CBR ≤ 0.7, Index is determined to be 4, the CR limit threshold is determined to be 0.03, and it is judged that the calculated CR value (0.042) exceeds the CR limit threshold. Therefore, the member congestion state is congested and the member congestion level is 4.

[0389] The second group member: The CBR value is 0.64; The CR value is equal to (5*2 / 200 + 5*2 / 50 + 3*2 / 100) / 5 = 0.042; According to the current CBR measurement value (0.64) within the range of 0.6 < CBR ≤ 0.7, Index is determined to be 4, the CR limit threshold is determined to be 0.03, and it is judged that the calculated CR value (0.042) exceeds the CR limit threshold. Therefore, the member congestion state is congested and the member congestion level is 4.

[0390] Members of the third group: CBR value is 0.63; CR value is equal to (5*2 / 200 + 5*2 / 50 + 3*2 / 100) / 5 = 0.042; According to the current CBR measurement value (0.63) within the range of 0.6 < CBR ≤ 0.7, Index is determined to be 4, the CR limit threshold is determined to be 0.03, and it is judged that the calculated CR value (0.042) exceeds the CR limit threshold. Therefore, the congestion status of the member is congestion, and the member congestion level is 4.

[0391] Members of the fourth group: CBR value is 0.62; CR value is equal to (5*2 / 200 + 5*2 / 50 + 3*2 / 100) / 5 = 0.042; According to the current CBR measurement value (0.62) within the range of 0.6 < CBR ≤ 0.7, Index is determined to be 4, the CR limit threshold is determined to be 0.03, and it is judged that the calculated CR value (0.042) exceeds the CR limit threshold. Therefore, the congestion status of the member is congestion, and the member congestion level is 4.

[0392] Thus, based on the member congestion status and member congestion level of each group member, the group head determines that the group congestion status is full congestion, determines that the group congestion level is 4, and accordingly determines that congestion control needs to be carried out.

[0393] The group head performs congestion control on all group members. Since the priority of the group head user is the highest, it preferentially controls the services of other non-group head members during congestion control. The results of this congestion control are as follows:

[0394] Group head: The number of services is 4; Service 1 (Vehicle Basic Safety Message): The application layer sending period is 100 ms, the service priority is 2, MCS is 7, the occupied RB is 27, TBS is 3368, the transmission times is 2, and the time-frequency resource is time-frequency resource 1; Service 2 (Formation Management Message): The application layer sending period is 200 ms, the service priority is 3, MCS is 14, the occupied RB is 27, TBS is 6968, the transmission times is 2, and the time-frequency resource is time-frequency resource 2; Service 3 (Formation Control Message): The application layer sending period is 200 ms, the service priority is 3, MCS is 15, the occupied RB is 36, TBS is 10296, the transmission times is 2, and the time-frequency resource is time-frequency resource 3; Service 4 (Intra-group Service Resource Allocation Indication Message): The application layer sending period is 500 ms, the service priority is 3, MCS is 14, the occupied RB is 27, TBS is 6968, the transmission times is 2, and the time-frequency resource is time-frequency resource 4.

[0395] Recalculate the CR value of the group head to be: (3*2 / 100 + 3*2 / 200 + 4*2 / 200 + 3*2 / 500) / 5 = 0.0284, which is lower than the CR-limit threshold value of 0.03. Therefore, the congestion status of the group head member changes to non-congestion.

[0396] Group 1 members: Number of services: 3; Service 1 (Group Management Message): Application layer sending period: 500ms, service priority: 3, MCS: 14, RB occupied: 27, TBS: 6968, number of transmissions: 2, time-frequency resource: 5; Service 2 (Group Control Message): Application layer sending period: 200ms, service priority: 3, MCS: 15, RB occupied: 36, TBS: 10296, number of transmissions: 2, time-frequency resource: 6; Service 3 (Service Resource Status Reporting Message): Application layer sending period: 500ms, service priority: 5, MCS: 12, RB occupied: 18, TBS: 3624, number of transmissions: 2, time-frequency resource: 7.

[0397] The CR value of the first group member is recalculated as (3*2 / 500+4*2 / 200+2*2 / 500) / 5=0.012, which is lower than the CR-limit threshold of 0.03. Therefore, the congestion status of the first group member is changed to non-congestion.

[0398] The second group consists of 3 services: Service 1 (Flag Management Message): Application layer sending period is 500ms, service priority is 3, MCS is 14, RB usage is 27, TBS is 6968, transmission count is 2, and time-frequency resource is 8; Service 2 (Flag Control Message): Application layer sending period is 200ms, service priority is 3, MCS is 15, RB usage is 36, TBS is 10296, transmission count is 2, and time-frequency resource is 9; Service 3 (Service Resource Status Reporting Message): Application layer sending period is 500ms, service priority is 5, MCS is 12, RB usage is 18, TBS is 3624, transmission count is 2, and time-frequency resource is 10.

[0399] The CR value of the second group members is recalculated as (3*2 / 500+4*2 / 200+2*2 / 500) / 5=0.012, which is lower than the CR-limit threshold of 0.03. Therefore, the congestion status of the second group members is changed to non-congestion.

[0400] The third group consists of 3 services: Service 1 (Flag Management Message): Application layer sending period is 500ms, service priority is 3, MCS is 14, RB occupied is 27, TBS is 6968, number of transmissions is 2, and time-frequency resource is 11; Service 2 (Flag Control Message): Application layer sending period is 200ms, service priority is 3, MCS is 15, RB occupied is 36, TBS is 10296, number of transmissions is 2, and time-frequency resource is 12; Service 3 (Service Resource Status Reporting Message): Application layer sending period is 500ms, service priority is 5, MCS is 12, RB occupied is 18, TBS is 3624, number of transmissions is 2, and time-frequency resource is 13.

[0401] The CR value of the third group member is recalculated as (3*2 / 500+4*2 / 200+2*2 / 500) / 5=0.012, which is lower than the CR-limit threshold of 0.03. Therefore, the congestion status of the third group member is changed to non-congestion.

[0402] Group 4 members: Number of services: 3; Service 1 (Group Management Message): Application layer sending period: 500ms, service priority: 3, MCS: 14, RB occupied: 27, TBS: 6968, number of transmissions: 2, time-frequency resource: 14; Service 2 (Group Control Message): Application layer sending period: 200ms, service priority: 3, MCS: 15, RB occupied: 36, TBS: 10296, number of transmissions: 2, time-frequency resource: 15; Service 3 (Service Resource Status Reporting Message): Application layer sending period: 500ms, service priority: 5, MCS: 12, RB occupied: 18, TBS: 3624, number of transmissions: 2, time-frequency resource: 16.

[0403] The CR value of the fourth group member is recalculated as (3*2 / 500+4*2 / 200+2*2 / 500) / 5=0.012, which is lower than the CR-limit threshold of 0.03. Therefore, the congestion status of the fourth group member is changed to non-congestion.

[0404] In this way, the group head determines that the group congestion status has changed to non-congestion based on the changed congestion status of each group member.

[0405] Finally, the group leader sends the new service allocation information and resource allocation information of each group member to each group member through allocation instructions (i.e., intra-group service and resource allocation instruction messages). After receiving the allocation instructions, each group member sends services according to the new service allocation information and resource allocation information.

[0406] Example 3: When a group member determines that a new service needs to be created, the group member reports the current CBR measurement value and the new service information to the group head, and requests other group members to report the current CBR measurement value.

[0407] like Figure 5 As shown, the first group members, acting as the rear members of the convoy, detect a significant number of independent vehicles approaching the convoy during convoy travel. The first group members need to send this perceived information to the group leader, triggering a perception data sharing service. At this point, the first group members can send a service trigger request message to the group leader, carrying the type of service to be triggered and the currently calculated CBR value (e.g., 0.4). The group leader then sends service resource status requests to other group members, requesting them to report CBR information. The group members then send service resource status reports to the group leader, reporting their currently calculated CBR values, which are 0.36, 0.42, and 0.4 respectively. Based on the current service allocation information, current resource allocation information, and the upcoming service (if any), the group leader determines the CR value for each member within the group, as follows:

[0408] The CR value of the group head is (3*2 / 100+5*2 / 200+5*2 / 50) / 5=0.062;

[0409] The CR value of the first group of members is (5*2 / 200+5*2 / 100+5*2 / 100) / 5=0.05;

[0410] The CR value of the second group of members is (5*2 / 200+5*2 / 100) / 5=0.03;

[0411] The CR value of the third group of members is (5*2 / 200+5*2 / 100) / 5=0.03;

[0412] The CR value of the fourth group members is (5*2 / 200+5*2 / 100) / 5=0.03.

[0413] The group leader determines the weighting factor for each member in the group based on their user priority (where the group leader has the highest priority of 3, the first group members have the second highest priority of 2, and the second, third, and fourth group members have the lowest priority of 1). The weighting factor for each member in the group is as follows: the group leader's weighting factor is 0.375, the first group members' weighting factor is 0.25, the second group members' weighting factor is 0.125, the third group members' weighting factor is 0.125, and the fourth group members' weighting factor is 0.125.

[0414] The group head multiplies the CR value of each group member by the *weighting factor* and sums them up to obtain a unique CR value of 0.047. The group head linearly averages the current CBR measurement values of each group member, where the calculated CBR value of the group head is 0.45, to obtain a unique CBR measurement value of 0.406. The group head determines the group congestion status and group congestion level based on the unique CR value (0.047), the unique CBR measurement value (0.406), the pre-configured CBR threshold, and the CR-limit threshold.

[0415] Among them, the CBR threshold, the CR-limit threshold (i.e., the above-mentioned CR threshold), and their mapping relationships are as follows:

[0416] 1 0.3 0.3 2 0.5 0.1 3 0.6 0.06 4 0.7 0.03 5 0.8 0.008 6 1 0.004

[0417] Based on the current CBR measurement value (0.406) within the range of 0.3 < CBR ≤ 0.5, the group head determines that the Index is 2, and then determines that the CR limit threshold is 0.1. It judges that the calculated CR value (0.047) does not exceed the CR limit threshold, determines that the group congestion status is non-congested, determines that the group congestion level is 2, and accordingly determines not to perform congestion control, and performs service allocation and resource allocation for new services according to the pre-configured parameters of the perception data sharing service. The specific allocation is as follows:

[0418] The first group member: The number of new services is 1; New service 1 - Perception data sharing message: The application layer sending period is 100 ms, the service priority is 2, the MCS is 8, the occupied RB is 48, the TBS is 6712, the number of transmissions is 2, and the time-frequency resource is time-frequency resource 12.

[0419] The group head sends a group internal service resource allocation indication message to the first group member, indicating the new service and carrying the service allocation information and resource allocation information of new service 1.

[0420] When the formation travels to the urban intersection, the group leader calculates the current CBR measurement value as 0.68, and then sends a service resource status request to each group member, requesting the reporting of CBR information; the group members send service resource status reports to the group leader, reporting the currently calculated CBR information, which are 0.65, 0.64, 0.63, and 0.63 respectively; the group leader determines the CR value of each group member based on the current service allocation information and current resource allocation information within the group, multiplies the CR value of each group member by the weighting factor and sums them up to obtain a unique CR value of 0.047; the group leader linearly averages the current CBR measurement values of each group member to obtain a unique CBR measurement value of 0.646; the group leader determines the group congestion status and group congestion level based on the unique CR value (0.047), the unique CBR measurement value (0.646), the pre-configured CBR threshold, and the CR-limit threshold. The group leader determines that Index is 4 based on the current CBR measurement value (0.646) within the range of 0.6 < CBR ≤ 0.7, and then determines that the CR limit threshold is 0.03. It is judged that the calculated CR value (0.047) exceeds the CR limit threshold, determines that the group congestion status is congested, determines that the group congestion level is 4, and congestion control needs to be carried out.

[0421] During congestion control, the group leader performs congestion control on all group members. Since the user priority of the group leader is the highest at 3, the user priority of the first group member is the second highest at 2, and the user priorities of the second group member, the third group member, and the fourth group member are the lowest at 1, the services of the second group member, the third group member, and the fourth group member are preferentially controlled during congestion control. The results of this congestion control are as follows:

[0422] Group leader: The number of services is 3; Service 1 (Vehicle Basic Safety Message): The application layer sending period is 100 ms, the service priority is 2, the MCS is 7, the occupied RB is 27, the TBS is 3368, the transmission times is 2, and the time-frequency resource is time-frequency resource 1; Service 2 (Formation Management Message): The application layer sending period is 200 ms, the service priority is 3, the MCS is 14, the occupied RB is 27, the TBS is 6968, the transmission times is 2, and the time-frequency resource is time-frequency resource 2; Service 3 (Formation Control Message): The application layer sending period is 100 ms, the service priority is 3, the MCS is 15, the occupied RB is 36, the TBS is 10296, the transmission times is 2, and the time-frequency resource is time-frequency resource 3.

[0423] The group leader recalculates the CR value of the group leader as: (3 * 2 / 100 + 3 * 2 / 200 + 4 * 2 / 100) / 5 = 0.034.

[0424] Group 1 members: Number of services: 3; Service 1 (Group Management Message): Application layer sending period: 500ms, service priority: 3, MCS: 14, RB occupied: 27, TBS: 6968, number of transmissions: 2, time-frequency resource: 4; Service 2 (Group Control Message): Application layer sending period: 200ms, service priority: 3, MCS: 15, RB occupied: 36, TBS: 10296, number of transmissions: 2, time-frequency resource: 5; Service 3 (Perception Data Sharing Message): Application layer sending period: 200ms, service priority: 2, MCS: 14, RB occupied: 27, TBS: 6968, number of transmissions: 2, time-frequency resource: 6.

[0425] The group leader recalculates the CR value of the first group member as: (3*2 / 500+4*2 / 200+3*2 / 200) / 5=0.0164.

[0426] The second group consists of 2 services; Service 1 (array management message): application layer transmission period is 500ms, service priority is 3, MCS is 14, RB usage is 27, TBS is 6968, transmission count is 2, and time-frequency resource is 7; Service 2 (array control message): application layer transmission period is 200ms, service priority is 3, MCS is 15, RB usage is 36, TBS is 10296, transmission count is 2, and time-frequency resource is 8.

[0427] The group leader recalculates the CR value of the second group member as: (3*2 / 500+4*2 / 200) / 5=0.0104.

[0428] The third group of members has 2 services; Service 1 (array management message): application layer sending period is 500ms, service priority is 3, MCS is 14, RB occupied is 27, TBS is 6968, number of transmissions is 2, and time-frequency resource is 9; Service 2 (array control message): application layer sending period is 500ms, service priority is 3, MCS is 15, RB occupied is 36, TBS is 10296, number of transmissions is 2, and time-frequency resource is 10.

[0429] The group leader recalculates the CR value of the third group member as: (3*2 / 500+4*2 / 200) / 5=0.0104.

[0430] Group 4 members: Number of services: 2; Service 1 (Group Management Message): Application layer sending period: 500ms, service priority: 3, MCS: 14, RB occupied: 27, TBS: 6968, number of transmissions: 2, time and frequency resource: 11; Service 2 (Group Control Message): Application layer sending period: 500ms, service priority: 3, MCS: 15, RB occupied: 36, TBS: 10296, number of transmissions: 2, time and frequency resource: 12.

[0431] The group leader recalculates the CR value of the fourth group member as: (3*2 / 500+4*2 / 200) / 5=0.0104.

[0432] Then, the group head performs a weighted summation of the CR values ​​of each member in the group (CR value * weighting factor and summation), obtaining a unique CR value of 0.02075. This value is lower than the CR limit threshold (0.03), thus determining that the group congestion status has changed to non-congestion.

[0433] Finally, the group leader sends the new service allocation information and resource allocation information of each group member to each group member through allocation instructions (i.e., intra-group service and resource allocation instruction messages). After receiving the allocation instructions, each group member sends services according to the new service allocation information and resource allocation information.

[0434] In this embodiment of the invention, the group head node can obtain the first information of the member nodes corresponding to the group head node, and send allocation instructions to the member nodes according to the first information, thereby instructing the member nodes to send services. In this way, congestion control applicable to group head resource allocation scenarios can be achieved.

[0435] Second Embodiment

[0436] like Figure 6 As shown, an embodiment of the present invention provides a congestion control device 600, comprising:

[0437] The information acquisition module 601 is used to acquire the first information of the member nodes corresponding to the group head node, wherein the member nodes corresponding to the group head node include at least one node in the node group to which the group head node belongs, excluding the group head node.

[0438] The instruction sending module 602 is used to send an allocation instruction to the member node according to the first information, wherein the allocation instruction is used to instruct the service to be sent;

[0439] The first information includes at least one of the following:

[0440] The measured value of Channel Busy Ratio (CBR);

[0441] The first target business is the business type of the business that is about to be triggered.

[0442] The service priority of the first target service.

[0443] In this embodiment, the group head node can obtain the first information of the member nodes corresponding to the group head node, and send allocation instructions to the member nodes according to the first information, thereby instructing the member nodes to send services. In this way, congestion control applicable to group head resource allocation scenarios can be achieved.

[0444] Optionally, the instruction sending module 602 includes:

[0445] The first processing submodule is used to determine the user priority corresponding to each node according to the second information corresponding to each node in the node group, wherein the second information includes: vehicle type and / or vehicle location;

[0446] The second processing submodule is used to determine the allocation information corresponding to each node based on the user priority corresponding to each node and the first information. The allocation information includes: service allocation information and resource allocation information.

[0447] The instruction sending submodule is used to send the allocation instruction to the member node, the allocation instruction including the allocation information corresponding to the member node.

[0448] Optionally, the second processing submodule includes:

[0449] The first processing unit is configured to determine the congestion information corresponding to each node and the congestion information corresponding to the node group based on the first information corresponding to each node. The congestion information includes: congestion status and / or congestion level.

[0450] The second processing unit is used to determine the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node, wherein the priority information includes: the user priority and / or the service priority.

[0451] Optionally, the second processing unit includes:

[0452] The first judgment subunit is used to determine whether the congestion state corresponding to the node group has changed and / or whether the reduction in the congestion level corresponding to the node group exceeds a first preset threshold.

[0453] The first reconfiguration subunit is used to prioritize resource reallocation for the second target service that meets the second preset condition when the congestion state corresponding to the node group changes and / or the reduction exceeds the first preset threshold.

[0454] The first adjustment subunit is used to perform resource adjustment based on the congestion information corresponding to each node;

[0455] The first processing subunit is used to repeatedly execute the step of prioritizing resource reallocation for the second target service that meets the second preset condition, up to the step of performing resource adjustment based on the congestion information corresponding to each node, until the third preset condition is met and the allocation information corresponding to each node is obtained.

[0456] The first preset condition includes: the congestion state corresponding to the node group is non-congested, and / or the congestion level corresponding to the node group is less than or equal to the first preset threshold.

[0457] The second preset condition includes: the business priority corresponding to the business is greater than or equal to the first priority, and / or, the user priority corresponding to the node associated with the business is greater than or equal to the second priority;

[0458] The third preset condition includes at least one of the following:

[0459] The congestion status corresponding to the node is non-congestion;

[0460] The congestion level corresponding to the node is less than or equal to the second preset threshold;

[0461] For the services that are about to be triggered, resources are allocated using pre-configured service parameters.

[0462] Optionally, the execution resource adjustment includes at least one of the following:

[0463] Increase the number of sub-channels occupied;

[0464] Reduce the MCS level of the modulation and coding scheme;

[0465] Shorten business cycles;

[0466] Increase the number of data transmissions.

[0467] Optionally, the second processing unit includes:

[0468] The second processing subunit is used to determine at least one target node based on the congestion information corresponding to the node group. The target node includes: a node whose congestion state is congested, and / or a node whose congestion level is greater than or equal to a third preset threshold.

[0469] The second reconfiguration subunit is used to reallocate resources for the services corresponding to the target node based on the priority information corresponding to the target node.

[0470] The second adjustment subunit is used to perform resource adjustment based on the congestion information corresponding to each node;

[0471] The third processing subunit is used to repeatedly execute the step of reallocating resources for the services corresponding to the target node based on the priority information corresponding to the target node, up to the step of adjusting resources based on the congestion information corresponding to each node, until the fourth preset condition is met and the allocation information corresponding to each node is obtained.

[0472] The fourth preset condition includes at least one of the following:

[0473] The congestion status corresponding to the target node is non-congested;

[0474] The congestion level corresponding to the target node is less than or equal to the second preset threshold;

[0475] The service uses the minimum allowed number of sub-channels.

[0476] The service adopts the maximum allowed MCS level;

[0477] The service uses the maximum allowed service period;

[0478] The service uses the minimum allowed number of transmissions;

[0479] End unnecessary business operations.

[0480] Optionally, the second processing unit includes:

[0481] The third subunit is used to reallocate resources for the services corresponding to each node according to the priority information of each node.

[0482] The third adjustment subunit is used to perform resource adjustment based on the congestion information corresponding to each node;

[0483] The fourth processing subunit is used to repeatedly execute the step of reallocating resources for services corresponding to each node based on the priority information of each node, up to the step of adjusting resources based on the congestion information of each node, until the fifth preset condition is met and the allocation information corresponding to each node is obtained.

[0484] The fifth preset condition includes at least one of the following:

[0485] The congestion status corresponding to the node group is non-congestion;

[0486] The congestion level corresponding to the node group is less than or equal to the second preset threshold;

[0487] The service uses the minimum allowed number of sub-channels.

[0488] The service adopts the maximum allowed MCS level;

[0489] The service uses the maximum allowed service period;

[0490] The service uses the minimum allowed number of transmissions;

[0491] End unnecessary business operations.

[0492] Optionally, the device includes:

[0493] The fifth processing subunit is used to sort the nodes according to the priority information corresponding to each node and according to a preset sorting rule to generate a resource redistribution sequence;

[0494] The fourth redistribution subunit is used to redistribute resources for the services corresponding to each node according to the resource redistribution sequence.

[0495] The preset sorting rule includes at least one of the following:

[0496] Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the business priority from low to high. Then, within the same business priority level, the second level of sorting is performed according to the user priority corresponding to each node from low to high.

[0497] Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the user priority corresponding to each node from low to high. Then, within the same user priority level, the second level of sorting is performed according to the business priority from low to high.

[0498] Based on the comprehensive priority index ranking mechanism, a comprehensive priority index is first generated by weighting the business priority and the user priority corresponding to each node, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

[0499] Optionally, the execution resource adjustment includes at least one of the following:

[0500] Reduce the number of sub-channels occupied;

[0501] Increase MCS level;

[0502] Increase business cycle;

[0503] Reduce the number of data transmissions.

[0504] Optionally, the first processing unit includes:

[0505] The sixth processing subunit is used to determine the channel ratio CR value corresponding to each of the nodes based on the current service allocation information and the current resource allocation information corresponding to each node.

[0506] The first comparison subunit is used to compare the CR value and CBR measurement value corresponding to each node with the pre-configured threshold information to determine the congestion information corresponding to each node. The threshold information includes: CBR threshold and CR threshold.

[0507] The seventh processing subunit is used to determine the congestion information corresponding to the node group based on the congestion information corresponding to each of the nodes.

[0508] Optionally, the first processing unit includes:

[0509] The eighth processing subunit is used to determine the CR value corresponding to each node based on the current service allocation information and current resource allocation information corresponding to each node.

[0510] The ninth processing subunit is used to determine the weighting factor corresponding to each node according to the user priority corresponding to each node.

[0511] The tenth processing subunit is used to perform a weighted summation of the CR values ​​corresponding to each node according to the weighting factor corresponding to each node, and obtain the first CR value;

[0512] The eleventh processing subunit is used to perform weighted summation of the CBR measurement values ​​corresponding to each node according to the weighting factor corresponding to each node, so as to obtain the first CBR value.

[0513] The second comparison subunit is used to compare the first CR value and the first CBR value with pre-configured threshold information to determine the congestion information corresponding to the node group.

[0514] Optionally, obtaining the first information of the member nodes corresponding to the group head node includes at least one of the following:

[0515] The first sending submodule is configured to send a first request to the member node according to a first triggering condition, and receive the first information of the member node fed back by the member node according to the first request, wherein the first request is used to request the sending of the first information of the member node;

[0516] The first receiving submodule is used to receive the first information of the member node reported by the member node according to the second triggering condition;

[0517] The first triggering condition includes at least one of the following:

[0518] Periodic triggering based on a first preset period;

[0519] The event is triggered based on the first event, which includes: the measured value of the CBR corresponding to the group head node is greater than or equal to the fourth preset threshold, and / or the group head node detects the start of a new service;

[0520] The second triggering condition includes at least one of the following:

[0521] Periodic triggering based on a second preset cycle;

[0522] The event is triggered based on a second event, which includes: the member node actively initiating a service request, and / or the member node receiving a trigger message from any node outside the node group to which the group head node belongs.

[0523] The second embodiment of the present invention corresponds to the method of the first embodiment described above. All the implementation means in the first embodiment described above are applicable to the embodiments of the congestion control device and can achieve the same technical effect.

[0524] Third Embodiment

[0525] To better achieve the above objectives, such as Figure 7 As shown, a third embodiment of the present invention also provides a control device, including:

[0526] The processor 700; and the memory 720 connected to the processor 700 via a bus interface, the memory 720 being used to store programs and data used by the processor 700 during operation, and the processor 700 calling and executing the programs and data stored in the memory 720.

[0527] The transceiver 710 is connected to a bus interface and is used to receive and send data under the control of the processor 700; the processor 700 is used to read the program in the memory 720 and execute the following steps:

[0528] Obtain the first information of the member nodes corresponding to the group head node, wherein the member nodes corresponding to the group head node include at least one node in the node group to which the group head node belongs, excluding the group head node;

[0529] Based on the first information, an allocation instruction is sent to the member node, the allocation instruction being used to instruct the service to be sent;

[0530] The first information includes at least one of the following:

[0531] The measured value of Channel Busy Ratio (CBR);

[0532] The first target business is the business type of the business that is about to be triggered.

[0533] The service priority of the first target service.

[0534] In this embodiment, the group head node can obtain the first information of the member nodes corresponding to the group head node, and send allocation instructions to the member nodes according to the first information, thereby instructing the member nodes to send services. In this way, congestion control applicable to group head resource allocation scenarios can be achieved.

[0535] Among them, Figure 7 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 700) and memory (memory 720). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 710 can be multiple elements, including transmitters and transceivers, providing a unit for communicating with various other devices over a transmission medium. For different terminals, the user interface 730 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 can store data used by the processor 700 during operation.

[0536] Optionally, when the processor 700 sends an allocation instruction to the member node based on the first information, it is specifically used for:

[0537] Based on the second information corresponding to each node in the node group, the user priority corresponding to each node is determined respectively, wherein the second information includes: vehicle type and / or vehicle location;

[0538] Based on the user priority corresponding to each node and the first information, the allocation information corresponding to each node is determined respectively, and the allocation information includes: service allocation information and resource allocation information;

[0539] The allocation instruction is sent to the member node, and the allocation instruction includes the allocation information corresponding to the member node.

[0540] Optionally, when the processor 700 determines the allocation information corresponding to each node based on the user priority corresponding to each node and the first information, it is specifically used for:

[0541] Based on the first information corresponding to each node, the congestion information corresponding to each node and the congestion information corresponding to the node group are determined respectively. The congestion information includes: congestion status and / or congestion level.

[0542] Based on the congestion information corresponding to the node group and the priority information corresponding to each node, the allocation information corresponding to each node is determined respectively, wherein the priority information includes: the user priority and / or the service priority.

[0543] Optionally, when the first preset condition is met, the processor 700, in determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node, specifically performs the following:

[0544] Determine whether the congestion status corresponding to the node group has changed and / or whether the decrease in the congestion level corresponding to the node group exceeds a first preset threshold.

[0545] If the congestion status of the node group changes and / or the reduction exceeds the first preset threshold, resources will be reallocated preferentially for the second target service that meets the second preset condition.

[0546] Based on the congestion information corresponding to each node, perform resource adjustments;

[0547] Repeat the step of prioritizing resource reallocation for the second target service that meets the second preset condition, until the step of performing resource adjustment based on the congestion information corresponding to each node is performed, until the third preset condition is met and the allocation information corresponding to each node is obtained;

[0548] The first preset condition includes: the congestion state corresponding to the node group is non-congested, and / or the congestion level corresponding to the node group is less than or equal to the first preset threshold.

[0549] The second preset condition includes: the business priority corresponding to the business is greater than or equal to the first priority, and / or, the user priority corresponding to the node associated with the business is greater than or equal to the second priority;

[0550] The third preset condition includes at least one of the following:

[0551] The congestion status corresponding to the node is non-congestion;

[0552] The congestion level corresponding to the node is less than or equal to the second preset threshold;

[0553] For the services that are about to be triggered, resources are allocated using pre-configured service parameters.

[0554] Optionally, the execution resource adjustment includes at least one of the following:

[0555] Increase the number of sub-channels occupied;

[0556] Reduce the MCS level of the modulation and coding scheme;

[0557] Shorten business cycles;

[0558] Increase the number of data transmissions.

[0559] Optionally, when the congestion state corresponding to the node group is partial congestion, the processor 700, when determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node, specifically uses the following methods:

[0560] Based on the congestion information corresponding to the node group, at least one target node is determined, the target node including: a node whose congestion state is congested, and / or a node whose congestion level is greater than or equal to a third preset threshold;

[0561] Based on the priority information corresponding to the target node, resources are reallocated to the services corresponding to the target node;

[0562] Based on the congestion information corresponding to each node, perform resource adjustments;

[0563] Repeat the steps of reallocating resources for the services corresponding to the target node based on the priority information of the target node, until the steps of adjusting resources based on the congestion information of each node are performed, until the fourth preset condition is met and the allocation information of each node is obtained.

[0564] The fourth preset condition includes at least one of the following:

[0565] The congestion status corresponding to the target node is non-congested;

[0566] The congestion level corresponding to the target node is less than or equal to the second preset threshold;

[0567] The service uses the minimum allowed number of sub-channels.

[0568] The service adopts the maximum allowed MCS level;

[0569] The service uses the maximum allowed service period;

[0570] The service uses the minimum allowed number of transmissions;

[0571] End unnecessary business operations.

[0572] Optionally, when the congestion state corresponding to the node group is full congestion, the processor 700, when determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node, specifically uses the following methods:

[0573] Based on the priority information of each node, resources are reallocated to the services corresponding to each node;

[0574] Based on the congestion information corresponding to each node, perform resource adjustments;

[0575] Repeat the steps of reallocating resources for services corresponding to each node based on the priority information of each node, until the steps of adjusting resources based on the congestion information of each node are performed, until the fifth preset condition is met and the allocation information corresponding to each node is obtained.

[0576] The fifth preset condition includes at least one of the following:

[0577] The congestion status corresponding to the node group is non-congestion;

[0578] The congestion level corresponding to the node group is less than or equal to the second preset threshold;

[0579] The service uses the minimum allowed number of sub-channels.

[0580] The service adopts the maximum allowed MCS level;

[0581] The service uses the maximum allowed service period;

[0582] The service uses the minimum allowed number of transmissions;

[0583] End unnecessary business operations.

[0584] Optionally, when the processor 700 reallocates resources for services corresponding to each node based on the priority information corresponding to each node, it specifically performs the following:

[0585] Based on the priority information corresponding to each node, the nodes are sorted according to a preset sorting rule to generate a resource redistribution sequence;

[0586] According to the resource reallocation sequence, the services corresponding to each node are reallocated;

[0587] The preset sorting rule includes at least one of the following:

[0588] Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the business priority from low to high. Then, within the same business priority level, the second level of sorting is performed according to the user priority corresponding to each node from low to high.

[0589] Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the user priority corresponding to each node from low to high. Then, within the same user priority level, the second level of sorting is performed according to the business priority from low to high.

[0590] Based on the comprehensive priority index ranking mechanism, a comprehensive priority index is first generated by weighting the business priority and the user priority corresponding to each node, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

[0591] Optionally, the execution resource adjustment includes at least one of the following:

[0592] Reduce the number of sub-channels occupied;

[0593] Increase MCS level;

[0594] Increase business cycle;

[0595] Reduce the number of data transmissions.

[0596] Optionally, when the processor 700 determines the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group based on the first information corresponding to each node, it specifically performs the following:

[0597] Based on the current service allocation information and current resource allocation information corresponding to each node, the channel ratio CR value corresponding to each node is determined respectively;

[0598] Based on the CR value and CBR measurement value corresponding to each node, the congestion information corresponding to each node is determined by comparing them with the pre-configured threshold information. The threshold information includes: CBR threshold and CR threshold.

[0599] Based on the congestion information corresponding to each node, the congestion information corresponding to the node group is determined.

[0600] Optionally, when the processor 700 determines the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group based on the first information corresponding to each node, it specifically performs the following:

[0601] Based on the current service allocation information and current resource allocation information corresponding to each node, the CR value corresponding to each node is determined respectively;

[0602] Based on the user priority corresponding to each node, the weighting factor corresponding to each node is determined respectively;

[0603] Based on the weighting factor corresponding to each node, the CR values ​​corresponding to each node are weighted and summed to obtain the first CR value;

[0604] Based on the weighting factor corresponding to each node, the measured CBR values ​​corresponding to each node are weighted and summed to obtain the first CBR value;

[0605] Based on the first CR value and the first CBR value, the congestion information corresponding to the node group is determined by comparing them with the pre-configured threshold information.

[0606] Optionally, when the processor 700 obtains the first information of the member nodes corresponding to the group head node, it specifically performs at least one of the following:

[0607] According to the first triggering condition, a first request is sent to the member node, and the first information of the member node is received from the member node in response to the first request. The first request is used to request the sending of the first information of the member node.

[0608] Receive the first information of the member node reported by the member node according to the second triggering condition;

[0609] The first triggering condition includes at least one of the following:

[0610] Periodic triggering based on a first preset period;

[0611] The event is triggered based on the first event, which includes: the measured value of the CBR corresponding to the group head node is greater than or equal to the fourth preset threshold, and / or the group head node detects the start of a new service;

[0612] The second triggering condition includes at least one of the following:

[0613] Periodic triggering based on a second preset cycle;

[0614] The event is triggered based on a second event, which includes: the member node actively initiating a service request, and / or the member node receiving a trigger message from any node outside the node group to which the group head node belongs.

[0615] It should be noted that the control device provided in this embodiment of the invention can implement all the method steps implemented in the above-mentioned congestion control method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0616] This application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the above-described... Figure 1 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0617] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a computer program instructing the relevant hardware to implement them. The computer program includes instructions to perform some or all of the steps of the above methods; and the computer program can be stored in a readable storage medium, which can be any form of storage medium.

[0618] In addition, specific embodiments of the present invention also provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the method as described in the first embodiment above. And it achieves the same technical effect; to avoid repetition, it will not be described again here.

[0619] Furthermore, it should be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of the present invention. Moreover, the steps performing the above-described series of processes can naturally be executed in the order described, but are not necessarily required to be executed in chronological order; some steps can be executed in parallel or independently of each other. Those skilled in the art will understand that all or any step or component of the method and apparatus of the present invention can be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or a combination thereof. This is something that those skilled in the art can achieve by using their basic programming skills after reading the description of the present invention.

[0620] Therefore, the object of the present invention can also be achieved by running a program or a set of programs on any computing device. The computing device can be a known general-purpose device. Therefore, the object of the present invention can also be achieved simply by providing a program product containing program code implementing the method or apparatus. That is, such a program product also constitutes the present invention, and the storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium can be any known storage medium or any storage medium developed in the future. It should also be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent to the present invention. Furthermore, the steps performing the above series of processes can naturally be performed in the order described, but are not necessarily required to be performed in chronological order. Some steps can be performed in parallel or independently of each other.

[0621] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A congestion control method, characterized in that, include: Obtain the first information of the member nodes corresponding to the group head node, wherein the member nodes corresponding to the group head node include at least one node in the node group to which the group head node belongs, excluding the group head node; Based on the first information, an allocation instruction is sent to the member node, the allocation instruction being used to instruct the service to be sent; The first information includes at least one of the following: The measured value of Channel Busy Ratio (CBR); The first target business is the business type of the business that is about to be triggered. The service priority of the first target service; The step of sending an allocation instruction to the member node based on the first information includes: Based on the second information corresponding to each node in the node group, the user priority corresponding to each node is determined respectively, wherein the second information includes: vehicle type and / or vehicle location; Based on the user priority corresponding to each node and the first information, the allocation information corresponding to each node is determined respectively, and the allocation information includes: service allocation information and resource allocation information; Send the allocation instruction to the member node, the allocation instruction including the allocation information corresponding to the member node; The step of determining the allocation information corresponding to each node based on the user priority corresponding to each node and the first information includes: Based on the first information corresponding to each node, the congestion information corresponding to each node and the congestion information corresponding to the node group are determined respectively. The congestion information includes: congestion status and / or congestion level. Based on the congestion information corresponding to the node group and the priority information corresponding to each node, the allocation information corresponding to each node is determined respectively, wherein the priority information includes: the user priority and / or the service priority.

2. The method according to claim 1, characterized in that, Under the condition of satisfying the first preset condition, the step of determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node includes: Determine whether the congestion status corresponding to the node group has changed and / or whether the decrease in the congestion level corresponding to the node group exceeds a first preset threshold. If the congestion status of the node group changes and / or the reduction exceeds the first preset threshold, resources will be reallocated preferentially for the second target service that meets the second preset condition. Based on the congestion information corresponding to each node, perform resource adjustments; Repeat the step of prioritizing resource reallocation for the second target service that meets the second preset condition, until the step of performing resource adjustment based on the congestion information corresponding to each node is performed, until the third preset condition is met and the allocation information corresponding to each node is obtained; The first preset condition includes: the congestion state corresponding to the node group is non-congested, and / or the congestion level corresponding to the node group is less than or equal to the first preset threshold. The second preset condition includes: the business priority corresponding to the business is greater than or equal to the first priority, and / or, the user priority corresponding to the node associated with the business is greater than or equal to the second priority; The third preset condition includes at least one of the following: The congestion status corresponding to the node is non-congestion; The congestion level corresponding to the node is less than or equal to the second preset threshold; For the services that are about to be triggered, resources are allocated using pre-configured service parameters.

3. The method according to claim 2, characterized in that, The execution resource adjustments include at least one of the following: Increase the number of sub-channels occupied; Reduce the MCS level of the modulation and coding scheme; Shorten business cycles; Increase the number of data transmissions.

4. The method according to claim 1, characterized in that, When the congestion state corresponding to the node group is partial congestion, the step of determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node includes: Based on the congestion information corresponding to the node group, at least one target node is determined, the target node including: a node whose congestion state is congested, and / or a node whose congestion level is greater than or equal to a third preset threshold; Based on the priority information corresponding to the target node, resources are reallocated to the services corresponding to the target node; Based on the congestion information corresponding to each node, perform resource adjustments; Repeat the steps of reallocating resources for the services corresponding to the target node based on the priority information of the target node, until the steps of adjusting resources based on the congestion information of each node are performed, until the fourth preset condition is met and the allocation information of each node is obtained. The fourth preset condition includes at least one of the following: The congestion status corresponding to the target node is non-congested; The congestion level corresponding to the target node is less than or equal to the second preset threshold; The service uses the minimum allowed number of sub-channels. The service adopts the maximum allowed MCS level; The service uses the maximum allowed service period; The service uses the minimum allowed number of transmissions; End unnecessary business operations.

5. The method according to claim 1, characterized in that, When the congestion state corresponding to the node group is congested or fully congested, the step of determining the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node includes: Based on the priority information of each node, resources are reallocated to the services corresponding to each node; Based on the congestion information corresponding to each node, perform resource adjustments; Repeat the steps of reallocating resources for services corresponding to each node based on the priority information of each node, until the steps of adjusting resources based on the congestion information of each node are performed, until the fifth preset condition is met and the allocation information corresponding to each node is obtained. The fifth preset condition includes at least one of the following: The congestion status corresponding to the node group is non-congestion; The congestion level corresponding to the node group is less than or equal to the second preset threshold; The service uses the minimum allowed number of sub-channels. The service adopts the maximum allowed MCS level; The service uses the maximum allowed service period; The service uses the minimum allowed number of transmissions; End unnecessary business operations.

6. The method according to claim 4 or 5, characterized in that, Based on the priority information corresponding to the node, resource reallocation is performed on the services corresponding to the node, including: Based on the priority information corresponding to each node, the nodes are sorted according to a preset sorting rule to generate a resource redistribution sequence; According to the resource reallocation sequence, the services corresponding to each node are reallocated; The preset sorting rule includes at least one of the following: Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the business priority from low to high. Then, within the same business priority level, the second level of sorting is performed according to the user priority corresponding to each node from low to high. Based on a two-dimensional priority sorting mechanism, the first level of sorting is performed according to the user priority corresponding to each node from low to high. Then, within the same user priority level, the second level of sorting is performed according to the business priority from low to high. Based on the comprehensive priority index ranking mechanism, a comprehensive priority index is first generated by weighting the business priority and the user priority corresponding to each node, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

7. The method according to claim 4 or 5, characterized in that, The execution resource adjustments include at least one of the following: Reduce the number of sub-channels occupied; Increase MCS level; Increase business cycle; Reduce the number of data transmissions.

8. The method according to claim 1, characterized in that, The step of determining the congestion information corresponding to each node and the congestion information corresponding to the node group based on the first information corresponding to each node includes: Based on the current service allocation information and current resource allocation information corresponding to each node, the channel ratio CR value corresponding to each node is determined respectively; Based on the CR value and CBR measurement value corresponding to each node, the congestion information corresponding to each node is determined by comparing them with the pre-configured threshold information. The threshold information includes: CBR threshold and CR threshold. Based on the congestion information corresponding to each node, the congestion information corresponding to the node group is determined.

9. The method according to claim 1, characterized in that, The step of determining the congestion information corresponding to each node and the congestion information corresponding to the node group based on the first information corresponding to each node includes: Based on the current service allocation information and current resource allocation information corresponding to each node, the CR value corresponding to each node is determined respectively; Based on the user priority corresponding to each node, the weighting factor corresponding to each node is determined respectively; Based on the weighting factor corresponding to each node, the CR values ​​corresponding to each node are weighted and summed to obtain the first CR value; Based on the weighting factor corresponding to each node, the measured CBR values ​​corresponding to each node are weighted and summed to obtain the first CBR value; Based on the first CR value and the first CBR value, the congestion information corresponding to the node group is determined by comparing them with the pre-configured threshold information.

10. The method according to claim 1, characterized in that, The step of obtaining the first information of the member nodes corresponding to the group head node includes at least one of the following: According to the first triggering condition, a first request is sent to the member node, and the first information of the member node is received from the member node in response to the first request. The first request is used to request the sending of the first information of the member node. Receive the first information of the member node reported by the member node according to the second triggering condition; The first triggering condition includes at least one of the following: Periodic triggering based on a first preset period; The event is triggered based on the first event, which includes: the measured value of the CBR corresponding to the group head node is greater than or equal to the fourth preset threshold, and / or the group head node detects the start of a new service; The second triggering condition includes at least one of the following: Periodic triggering based on a second preset cycle; The event is triggered based on a second event, which includes: the member node actively initiating a service request, and / or the member node receiving a trigger message from any node outside the node group to which the group head node belongs.

11. A congestion control device, characterized in that, include: The information acquisition module is used to acquire the first information of the member nodes corresponding to the group head node. The member nodes corresponding to the group head node include at least one node in the node group to which the group head node belongs, excluding the group head node. An instruction sending module is configured to send an allocation instruction to the member node based on the first information, wherein the allocation instruction is used to instruct the service to be sent. The first information includes at least one of the following: The measured value of Channel Busy Ratio (CBR); The first target business is the business type of the business that is about to be triggered. The service priority of the first target service; The instruction sending module includes: The first processing submodule is used to determine the user priority corresponding to each node according to the second information corresponding to each node in the node group, wherein the second information includes: vehicle type and / or vehicle location; The second processing submodule is used to determine the allocation information corresponding to each node based on the user priority corresponding to each node and the first information. The allocation information includes: service allocation information and resource allocation information. An instruction sending submodule is used to send the allocation instruction to the member node, the allocation instruction including allocation information corresponding to the member node; The second processing submodule includes: The first processing unit is configured to determine the congestion information corresponding to each node and the congestion information corresponding to the node group based on the first information corresponding to each node. The congestion information includes: congestion status and / or congestion level. The second processing unit is used to determine the allocation information corresponding to each node based on the congestion information corresponding to the node group and the priority information corresponding to each node, wherein the priority information includes: the user priority and / or the service priority.

12. A control device, comprising: A transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, when the processor executes the computer program, it implements the steps of the congestion control method as described in any one of claims 1 to 10.

13. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 10.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the congestion control method as described in any one of claims 1 to 10.

Images