Congestion control method and device, control equipment, program product and medium

Abstract

The invention provides a congestion control method and device, control equipment, a program product and a medium, and relates to the technical field of communication, and the method comprises the steps: obtaining first information of a member node corresponding to a group head node, the member nodes corresponding to the group head node comprise at least one node except the group head node in a node group to which the group head node belongs; according to the first information, sending an allocation indication to the member node, the allocation indication being used for indicating service sending; wherein the first information comprises at least one of the following items: a measurement value of a channel busy ratio (CBR); the service type of the first target service, wherein the first target service is a service to be triggered; the service priority of the first target service is obtained. According to the scheme of the invention, the problem of lack of a congestion control scheme adaptive to a group header resource allocation scene in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a congestion control method, device, control equipment, program product and medium. Background Art

[0002] In the group head resource allocation scenario, the group head node is responsible for uniformly allocating time and frequency resources to group member vehicles, thereby avoiding resource competition among 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 suitable for the scenario of group head resource allocation, and it is difficult to ensure the communication performance and resource utilization efficiency of group members under congestion in this scenario. Summary of the invention

[0004] The present invention provides a congestion control method, apparatus, control equipment, program product and medium, which solve the problem that the prior art lacks a congestion control solution adapted to the group head resource allocation scenario.

[0005] In a first aspect, an embodiment of the present invention provides a congestion control method, including:

[0006] Acquire first information of a member node corresponding to a group head node, where the member node corresponding to the group head node includes: at least one node other than the group head node in a node group to which the group head node belongs;

[0007] Sending an allocation indication to the member node according to the first information, where the allocation indication is used to indicate service sending;

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

[0009] Channel Busy Ratio (CBR) measurement value;

[0010] A service type of a first target service, where the first target service is a service to be triggered;

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

[0012] Optionally, sending an allocation indication to the member node according to the first information includes:

[0013] Determine the user priority corresponding to each node in the node group according to the second information corresponding to each node, wherein the second information includes: vehicle type and / or vehicle location;

[0014] According to the user priority corresponding to each of the nodes and the first information, respectively determine the allocation information corresponding to each of the nodes, the allocation information including: service allocation information and resource allocation information;

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

[0016] Optionally, determining allocation information corresponding to each of the nodes respectively according to the user priority corresponding to each of the nodes and the first information includes:

[0017] Determine, according to the first information corresponding to each of the nodes, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group, respectively, wherein the congestion information includes: a congestion state and / or a congestion level; and the congestion information includes: a congestion state and / or a congestion level;

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

[0019] Optionally, when the first preset condition is met, determining allocation information corresponding to each of the nodes according to congestion information corresponding to the node group and priority information corresponding to each of the nodes includes:

[0020] Determine whether the congestion state corresponding to the node group has changed and / or whether the reduction range of the congestion level corresponding to the node group exceeds a first preset threshold;

[0021] When the congestion state corresponding to the node group changes and / or the reduction exceeds the first preset threshold, resource reallocation is performed preferentially for a second target service that meets a second preset condition;

[0022] Perform resource adjustment according to congestion information corresponding to each of the nodes;

[0023] Repeat the step of preferentially reallocating resources for the second target service that meets the second preset condition, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until the third preset condition is met, and the allocation information corresponding to each of the nodes is obtained;

[0024] 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 a first preset threshold;

[0025] 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;

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

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

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

[0029] For the service to be triggered, resources are allocated using preconfigured service parameters.

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

[0031] Increase the number of sub-channel occupancy;

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

[0033] Shorten business cycle;

[0034] Increase the number of data transfers.

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

[0036] Determine at least one target node according to the congestion information corresponding to the node group, 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] reallocating resources for the services corresponding to the target node according to the priority information corresponding to the target node;

[0038] Perform resource adjustment according to congestion information corresponding to each of the nodes;

[0039] Repeat the step of reallocating resources for the services corresponding to the target node according to the priority information corresponding to the target node, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until the fourth preset condition is met, and the allocation information corresponding to each of the nodes is obtained;

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

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

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

[0043] The service adopts the minimum allowed number of sub-channel occupancy;

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

[0045] The business adopts the maximum business cycle allowed;

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

[0047] End unnecessary business.

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

[0049] reallocating resources for services corresponding to each of the nodes according to priority information corresponding to each of the nodes;

[0050] Perform resource adjustment according to congestion information corresponding to each of the nodes;

[0051] Repeat the step of reallocating resources for services corresponding to each of the nodes according to the priority information corresponding to each of the nodes, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until a fifth preset condition is met, and allocation information corresponding to each of the nodes is obtained;

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

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

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

[0055] The service adopts the minimum allowed number of sub-channel occupancy;

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

[0057] The business adopts the maximum business cycle allowed;

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

[0059] End unnecessary business.

[0060] Optionally, reallocating resources for a service corresponding to the node according to the priority information corresponding to the node includes:

[0061] According to the priority information corresponding to each of the nodes, the nodes are sorted according to a preset sorting rule to generate a resource reallocation sequence;

[0062] According to the resource reallocation sequence, reallocate resources for services corresponding to each of the nodes;

[0063] The preset sorting rules include at least one of the following:

[0064] Based on the dual-dimensional priority sorting mechanism, the first-level sorting is performed in the order of the business priority from low to high, and then the second-level sorting is performed in the order of the user priority corresponding to each node from low to high within the same business priority level;

[0065] Based on the dual-dimensional priority sorting mechanism, the first level sorting is performed in the order of user priority corresponding to each node from low to high, and then the second level sorting is performed in the order of service priority from low to high within the same user priority level;

[0066] Based on the comprehensive priority index sorting mechanism, a weighted calculation is first performed according to the business priority and the user priority corresponding to each node to generate a comprehensive priority index, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

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

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

[0069] Increase the MCS level;

[0070] Increase business cycle;

[0071] Reduce the number of data transfers.

[0072] Optionally, determining, according to the first information corresponding to each of the nodes, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group, respectively, includes:

[0073] Determine the channel ratio CR value corresponding to each of the nodes according to the current service allocation information and the current resource allocation information corresponding to each of the nodes;

[0074] According to the CR value and the CBR measurement value corresponding to each of the nodes, the congestion information corresponding to each of the nodes is determined respectively with the pre-configured threshold information, wherein the threshold information includes: a CBR threshold and a CR threshold;

[0075] Congestion information corresponding to the node group is determined according to the congestion information corresponding to each of the nodes.

[0076] Optionally, determining, according to the first information corresponding to each of the nodes, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group, respectively, includes:

[0077] Determine the CR value corresponding to each of the nodes according to the current service allocation information and the current resource allocation information corresponding to each of the nodes;

[0078] Determine the weighting factors corresponding to the nodes respectively according to the user priorities corresponding to the nodes;

[0079] According to the weighting factors corresponding to the nodes, weighted sum is performed on the CR values ​​corresponding to the nodes to obtain a first CR value;

[0080] According to the weighting factors corresponding to the nodes, weighted summation is performed on the CBR measurement values ​​corresponding to the nodes to obtain a first CBR value;

[0081] The first CR value and the first CBR value are compared with preconfigured threshold information to determine congestion information corresponding to the node group.

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

[0083] According to a first trigger condition, sending a first request to the member node, and receiving 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 sending the first information of the member node;

[0084] receiving first information of the member node reported by the member node according to a second trigger condition;

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

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

[0087] An event trigger based on a first event, wherein the first event includes: a measured value of a 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;

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

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

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

[0091] In a second aspect, an embodiment of the present invention provides a congestion control device, including:

[0092] An information acquisition module, configured to acquire first information of a member node corresponding to a group head node, wherein the member node corresponding to the group head node includes: at least one node other than the group head node in a node group to which the group head node belongs;

[0093] an indication sending module, configured to send an allocation indication to the member node according to the first information, wherein the allocation indication is used to indicate service sending;

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

[0095] The measurement value of the channel busy ratio CBR;

[0096] A service type of a first target service, where the first target service is a service to be triggered;

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

[0098] Optionally, the instruction sending module includes:

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

[0100] A second processing submodule, configured to determine allocation information corresponding to each of the nodes according to the user priority corresponding to each of the nodes and the first information, wherein the allocation information includes: service allocation information and resource allocation information;

[0101] The indication sending submodule is used to send the allocation indication to the member node, where the allocation indication includes the allocation information corresponding to the member node.

[0102] Optionally, the second processing submodule includes:

[0103] A first processing unit, configured to determine, according to the first information corresponding to each of the nodes, congestion information corresponding to the node group, respectively, wherein the congestion information includes: a congestion state and / or a congestion level; and the congestion information includes: a congestion state and / or a congestion level;

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

[0105] Optionally, the second processing unit includes:

[0106] A first judgment subunit, used to judge whether the congestion state corresponding to the node group has changed and / or whether the reduction range of the congestion level corresponding to the node group exceeds a first preset threshold;

[0107] A first reconfiguration subunit is used to preferentially reallocate resources for a second target service that meets a second preset condition when the congestion state corresponding to the node group changes and / or the reduction exceeds the first preset threshold;

[0108] A first adjustment subunit, configured to perform resource adjustment according to congestion information corresponding to each of the nodes;

[0109] The first processing subunit is used to repeatedly execute the step of preferentially reallocating resources for the second target service that meets the second preset condition, to the step of performing resource adjustment according to the congestion information corresponding to each of the nodes, until the third preset condition is met, and the allocation information corresponding to each of the nodes is obtained;

[0110] 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 a first preset threshold;

[0111] 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;

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

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

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

[0115] For the service to be triggered, resources are allocated using preconfigured service parameters.

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

[0117] Increase the number of sub-channel occupancy;

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

[0119] Shorten business cycle;

[0120] Increase the number of data transfers.

[0121] Optionally, the second processing unit includes:

[0122] A second processing subunit is used to determine at least one target node according to the congestion information corresponding to the node group, wherein 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] A second reconfiguration subunit, configured to reallocate resources for the service corresponding to the target node according to the priority information corresponding to the target node;

[0124] A second adjustment subunit, configured to perform resource adjustment according to congestion information corresponding to each of the nodes;

[0125] a third processing subunit, configured to repeatedly execute the step of reallocating resources for the services corresponding to the target node according to the priority information corresponding to the target node, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until a fourth preset condition is met, and allocation information corresponding to each of the nodes is obtained;

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

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

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

[0129] The service adopts the minimum allowed number of sub-channel occupancy;

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

[0131] The business adopts the maximum business cycle allowed;

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

[0133] End unnecessary business.

[0134] Optionally, the second processing unit includes:

[0135] A third reconfiguration subunit, configured to reallocate resources for services corresponding to each of the nodes according to priority information corresponding to each of the nodes;

[0136] A third adjustment subunit, configured to perform resource adjustment according to congestion information corresponding to each of the nodes;

[0137] a fourth processing subunit, configured to repeatedly execute the step of reallocating resources for services corresponding to each of the nodes according to the priority information corresponding to each of the nodes, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until a fifth preset condition is met, and allocation information corresponding to each of the nodes is obtained;

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

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

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

[0141] The service adopts the minimum allowed number of sub-channel occupancy;

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

[0143] The business adopts the maximum business cycle allowed;

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

[0145] End unnecessary business.

[0146] Optionally, the device comprises:

[0147] A fifth processing subunit, configured to sort the nodes according to the priority information corresponding to each of the nodes and a preset sorting rule, and generate a resource reallocation sequence;

[0148] A fourth reconfiguration subunit, configured to reallocate resources for services corresponding to each of the nodes according to the resource reallocation sequence;

[0149] The preset sorting rules include at least one of the following:

[0150] Based on the dual-dimensional priority sorting mechanism, the first-level sorting is performed in the order of the business priority from low to high, and then the second-level sorting is performed in the order of the user priority corresponding to each node from low to high within the same business priority level;

[0151] Based on the dual-dimensional priority sorting mechanism, the first level sorting is performed in the order of user priority corresponding to each node from low to high, and then the second level sorting is performed in the order of service priority from low to high within the same user priority level;

[0152] Based on the comprehensive priority index sorting mechanism, a weighted calculation is first performed according to the business priority and the user priority corresponding to each node to generate a comprehensive priority index, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

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

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

[0155] Increase the MCS level;

[0156] Increase business cycle;

[0157] Reduce the number of data transfers.

[0158] Optionally, the first processing unit includes:

[0159] a sixth processing subunit, configured to determine a channel ratio CR value corresponding to each of the nodes according to current service allocation information and current resource allocation information corresponding to each of the nodes;

[0160] A first comparison subunit is used to compare the CR value and the CBR measurement value corresponding to each of the nodes with the pre-configured threshold information to determine the congestion information corresponding to each of the nodes, wherein the threshold information includes: a CBR threshold and a CR threshold;

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

[0162] Optionally, the first processing unit includes:

[0163] an eighth processing subunit, configured to determine the CR value corresponding to each of the nodes according to the current service allocation information and the current resource allocation information corresponding to each of the nodes;

[0164] A ninth processing subunit, configured to determine a weighting factor corresponding to each of the nodes according to a user priority corresponding to each of the nodes;

[0165] a tenth processing subunit, configured to perform weighted summation on the CR values ​​corresponding to the nodes according to the weighting factors corresponding to the nodes, to obtain a first CR value;

[0166] an eleventh processing subunit, configured to perform weighted summation on the CBR measurement values ​​corresponding to the nodes according to the weighting factors corresponding to the nodes, to obtain a first CBR value;

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

[0168] Optionally, the information acquisition module includes:

[0169] a first sending submodule, configured to send a first request to the member node according to a first trigger condition, and receive 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 to send the first information of the member node;

[0170] A first receiving submodule, configured to receive first information of the member node reported by the member node according to a second trigger condition;

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

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

[0173] An event trigger based on a first event, wherein the first event includes: a measured value of a 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;

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

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

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

[0177] In a third aspect, an embodiment of the present invention provides a control device, comprising: a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the congestion control method as described in the first aspect when executing the computer program.

[0178] In a fourth aspect, an embodiment of the present invention provides a computer program product, comprising computer instructions, which implement the steps of the above method when executed by a processor.

[0179] In a fifth aspect, an embodiment of the present invention provides 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 technical solution of the present invention are:

[0181] In an embodiment of the present invention, a group head node can obtain first information of a member node corresponding to the group head node, and send an allocation instruction to the member node according to the first information, thereby instructing the member node to send a service. In this way, congestion control applicable to the group head resource allocation scenario can be implemented. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0184] Figure 3 One of the schematic diagrams showing the interaction flow between nodes according to an embodiment of the present invention;

[0185] Figure 4 A second schematic diagram showing the interaction flow between nodes according to an embodiment of the present invention;

[0186] Figure 5 A third schematic diagram showing the interaction flow between nodes according to an embodiment of the present invention;

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

[0188] Figure 7 A structural block diagram showing a control device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0189] In order to make the technical problems, technical solutions and advantages to be solved by the present invention clearer, the following will be described in detail in conjunction with the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided only to help fully understand the embodiments of the present invention. Therefore, it should be clear to those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. In addition, for clarity and brevity, the description of known functions and structures is omitted.

[0190] It should be understood that the references to "one embodiment" or "an embodiment" throughout the specification mean that the specific features, structures, or characteristics associated with the embodiment are included in at least one embodiment of the present invention. Therefore, the references to "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may 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 size of the serial numbers of the following processes does not mean 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] Additionally, the terms "system" and "network" are often used interchangeably herein.

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

[0194] In the embodiment of the present invention, the form of the access network is not limited, and may be an access network including a macro base station (Macro Base Station), a micro base station (Pico Base Station), a Node B (the name of a 3G mobile base station), an enhanced base station (eNB), a home enhanced base station (Femto eNB or Home eNode B or Home eNB or HeNB), a relay station, an access point, an RRU (Remote Radio Unit), an RRH (Remote Radio Head), etc. The user terminal may be a mobile phone (or mobile phone), or other equipment capable of sending or receiving wireless signals, including user equipment, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a CPE (Customer Premise Equipment) capable of converting a mobile signal into a WiFi signal, or a mobile smart hotspot, a smart home appliance, or other equipment that can spontaneously communicate with a mobile communication network without human operation.

[0195] At present, vehicle to everything (V2X) technology uses wireless communications between vehicles, vehicles and roadside infrastructure, and vehicles and pedestrians to 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 the existing LTE V2X technology (Rel-14 LTE V2X technology), the PC5 interface (also called direct link, described as Sidelink in the protocol) for transmitting data between user equipment (UE) and UE can already support the transmission of basic road safety-based services. Among them, it is mainly aimed at service packets with a data packet size of 50-1200 bytes, and the transmission reliability of the service packets is required to be greater than 95% within the specified coverage.

[0197] With the further development of Internet of Vehicles technology, some new application scenarios have emerged, such as vehicle platooning, advanced driving, sensor information sharing, and remote control. Some of these applications require communication between UEs in a group, or unicast communication between two UEs. Therefore, the V2X system needs to consider scenarios such as unicast and multicast. However, the existing technology lacks a congestion control solution suitable for the group head resource allocation scenario (i.e., multicast mode).

[0198] The following is an introduction to the relevant technologies:

[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 performs service transmission on a single carrier, does not support carrier aggregation, and congestion control is performed at the granularity of resource pools.

[0201] From the receiving perspective, a pool-specific CBR measurement is defined for the sending pool (including the transmission pool and the exceptional pool), which describes the resource occupancy of each sending pool perceived by the receiving node.

[0202] If the sending UE has a transmission block (TB) to send in subframe n+4, it needs to perform CBR measurement in subframe n. The time window for CBR measurement is [n-100, n-1], and the duration is fixed at 100ms. In CBR processing, each subframe is a physical subframe.

[0203] For the Physical Sidelink Shared Channel (PSSCH), the 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. According to the configured (or pre-configured) S-RSSI threshold of the subchannel granularity, the S-RSSI of the subchannels of the transmission pool including the PSSCH in the [n-100, n-1] time window is measured, and the ratio of the number of subchannels exceeding the threshold to the total number of subchannels within 100 ms is calculated, and the ratio is recorded as the CBR result of the PSSCH of the transmission pool.

[0204] When the CBR exceeds the threshold, the following actions can be performed: adjust the transmit power; adjust the number of retransmissions; adjust the number of PSSCH subchannels; adjust the MCS Range; adjust the maximum value of CRlimit.

[0205] From the perspective of the sender, by evaluating the CR of the transmission pool and exceptional pool within 1000ms, the sender can understand the proportion of the send resources of the local node to the transmission pool or exceptional pool. Based on the measured CR, it can be determined whether it exceeds the configured CRlimit and the send parameters can be adjusted.

[0206] If the sending UE has a TB to send in the n+4 subframe, it is necessary to perform CR measurement in the n subframe. The time window for CR measurement is [na,n+b], and the duration is fixed at 1000ms. The time window is divided into two parts, where [na,n-1] corresponds to the statistics of the subchannels that have been sent by this node, and [n,n+b] corresponds to the statistics of the subchannels that this node will occupy. 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 in the last transmission opportunity. Then, calculate the number of subchannels occupied by this node in these two parts, and the proportion of the total number of subchannels in the entire time window [na,n+b], and record this proportion as the CR result of the sending pool. In CR processing, each subframe is a physical subframe.

[0207] CR processing can be measured at the granularity of Per PPPP. Based on per PPPP, the measured CR needs to satisfy the following relationship:

[0208]

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

[0210] How to handle the CRlimit when sending depends on the UE implementation. For example, in order to meet the CRlimit, packets can be dropped when sending.

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

[0212] NR V2X congestion control follows the LTE congestion control process in the standard, that is, the basic framework is the same, except for the following minor differences, but the specific algorithm implementation depends on the implementation of each manufacturer. The differences mainly include: CBR and CR measurement windows (both periodic and non-periodic); measurement timing requirements (related to UE capabilities); Physical Sidelink Feedback Channel (PSFCH) caused by the frame structure; different subcarrier spacing (SCS) configurations.

[0213] NR multicast scenario (application description):

[0214] In the platooning scenario, there are three types of vehicles: lead vehicle, platoon member, and independent vehicle.

[0215] The lead vehicle is the vehicle in the leading position in the direction of the formation, guiding the entire formation in terms of speed, acceleration and direction of travel, and is responsible for the allocation of communication resources for formation members. In addition, the lead vehicle must communicate with other vehicles within the broadcast range to avoid collisions between formations and vehicles, so as to ensure the driving safety of the entire formation and traffic scene.

[0216] The formation members obtain the basic safety information sent by the lead vehicle and the basic safety information such as position, speed, acceleration, etc. sent by the single-hop front vehicle, and follow the driving of the front vehicle (this information does not necessarily need to be sent, depending on the length of the convoy, that is, the non-standard part of the message sending in the specific multicast), so as to maintain a consistent and stable collaborative relationship with the formation.

[0217] An independent vehicle is a single vehicle that does not belong to any formation and has no cooperative relationship with other vehicles. It maintains a normal and safe driving state through periodic communication with other vehicles.

[0218] The existing standards do not provide corresponding instructions for congestion control of services in NR multicast scenarios. Currently, LTE congestion control is relatively certain (it is certain that only conventional BSM is controlled, and other messages are not controlled), while the control objects of NR services have not yet been determined.

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

[0220] First, we make necessary inferences from the perspective of LTE congestion control: in the LTE system, the On-Board Unit (OBU) resource pool is compared with the Roadside Unit (RSU) resource pool, and the resources are relatively limited; further, the LTE OBU only sends a single BSM message, and the object of LTE congestion control is only the conventional BSM broadcast message, that is, there is only one PPP for the corresponding message; how the NR resource pool is divided has not yet been determined, that is, it is still possible that RSU / OBU uses different sending resource pools, and there are various types of messages in the NR OBU, and the types of business messages have increased, and the types of business messages have also increased (in addition to text messages, there are also video and other types of messages; in addition to broadcast messages, there are multicast and unicast messages); although the object of congestion control and the message perspective have not yet been determined, it is certain that congestion control of messages other than OBU node BSM messages needs to be considered.

[0221] Secondly, from another perspective, LTE systems are all broadcast applications, while NR systems have unicast and multicast applications in addition to broadcast applications. Even with admission control, there are still differences between unicast and multicast services and calls in cellular networks. Some multicast services may have a short connection time, but some multicast services may last for a long time (similar to platnoon services). During the service, the surrounding environment may be very different, which means that it is impossible to solve it through admission control. From this perspective, congestion control also needs to be considered for NR multicast applications.

[0222] In addition, for congestion control of NR multicast communication, it is necessary to further consider the differences between NR multicast messages and BSM message mechanisms: the object of LTE congestion control is only conventional BSM broadcast messages, that is, there is only one PPPP for the corresponding message, and because they are all broadcast, it is equivalent to the node detecting the CBR by itself, and then making corresponding adjustments to the CR based on the CBR measurement (CR is the sending resources and the transmission parameters of the sending resources).

[0223] For multicast communication, the specific resource allocation method has not yet been determined. There may be the following methods: (1) UE autonomous selection; (2) group head allocation of resources; (3) gNB allocation of resources; (4) UE-led, group head or gNB assisted in resource allocation. Among them, for method (2), that is, the group head allocation of resources, the congestion control process specified in 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 different types of services in the NR group, which may correspond to different PPPPs. For congestion control, the corresponding channel busy ratio-channel ratio (CBR-CR) mapping of different PPPPs will be different.

[0226] (2) NR multicast services may not be completely symmetrical, that is, the traffic between members and group heads, and even between members, is different.

[0227] (3) In the case of a shared resource pool (OBU resource pool), some PPPPs may correspond to making their own CR decisions (non-multicast services, or a resource pool determined for a certain UE), and some PPPPs may correspond to the CR decisions determined by the group head.

[0228] (4) CR is essentially the control of sending parameters. In the multicast allocation mode, members cannot determine their own sending resources and transmission parameters of sending resources (in the group head allocation mode, group members 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, it can be seen that the existing BSM message congestion mechanism is not suitable for direct migration to NR multicast messages and has the problem of inapplicability. For example:

[0230] Node A is an independent vehicle, and CBR measures its current CR and the corresponding CRlimit under this CBR; Node B is the group head node, and CBR measures the CR of its own business, the CR corresponding to all resources allocated by itself, and the corresponding CRlimit under this CBR; Nodes C, D, and E are all nodes in the group, and their resources are controlled by the group head node B. Assume that node A is an independent vehicle near node B, and node B's own transmission resource opportunities are similar to those of node A (number of skip subframes). From this perspective, the CBRs measured by nodes A and B are similar. If node B only considers itself, its corresponding CRlimit is similar. However, for nodes C, D, and E, the transmission resources are determined by the group head node B. The control of CR itself is a control of transmission resources. The control of transmission parameters can be HARQ off or transmission parameter control. If the head vehicle does not do anything and gives resources to the team members, the team members have no other means of processing except turning off retransmission (and once the transmission parameters are changed, it actually affects sensing). In other words, there is currently a lack of congestion control technology under group head allocation resources, and corresponding research is needed.

[0231] Specifically, the embodiments of the present invention provide a congestion control method, apparatus, control device, program product and medium, which solve the problem that the prior art lacks a congestion control solution 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, which specifically includes the following steps:

[0234] Step 11: Acquire first information of a member node corresponding to a group head node, where the member node corresponding to the group head node includes: at least one node other than the group head node in the node group to which the group head node belongs.

[0235] That is, the group head node can obtain the first information calculated by the group member (that is, the member node corresponding to the group head node). The first information includes at least one of the following:

[0236] (1) The measured value of the channel busy rate (CBR), that is, the current CBR measured value of the group members.

[0237] (2) A service type of a first target service, where the first target service is a service to be triggered, that is, a service type of a service to be triggered by a group member.

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

[0239] Step 12: Send an allocation indication to the member node according to the first information, where the allocation indication is used to indicate service sending.

[0240] In this embodiment, the group head node can obtain the first information of the member node corresponding to the group head node, and send an allocation instruction to the member node according to the first information, thereby instructing the member node to send services. In this way, congestion control suitable for group head resource allocation scenarios can be implemented.

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

[0242] (1) According to a first trigger condition, a first request is sent to the member node, and the first information of the member node fed back by the member node according to the first request is received, wherein the first request is used to request to send the first information of the member node. The first trigger condition includes at least one of the following: (1) a periodic trigger based on a first preset period; (2) an event trigger based on a first event, wherein the first event includes: a 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 (that is, the group head node mentioned above) can request the first information from the group members on demand or periodically. For example: the periodic trigger based on the first preset period is that the group head can send configuration information to the group members when configuring the service / resources to configure the group members (that is, the member nodes mentioned above) to report the first information (CBR information, that is, the measured value of CBR) to the group head according to the first preset period (such as every 100ms); the trigger mechanism of the on-demand request is an event trigger based on the first event. Specifically, when the group head determines that the CBR value calculated by itself exceeds the threshold value (that is, the fourth preset threshold), it can request the first information (such as CBR information) from each group member (that is, send a first request to the group members to request the group members to report the first information to the group head), or, when the group head determines that a new service is triggered, it requests the first information (such as CBR information) from each group member.

[0244] (ii) receiving first information of the member node reported by the member node according to a second trigger condition. The second trigger condition includes at least one of the following: (1) a periodic trigger based on a second preset period; (2) an event trigger based on a second event, wherein the second event includes: 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, the group members (that is, the member nodes mentioned above) report the first information to the group head on demand or periodically. Here, the trigger mechanism for on-demand reporting is an event trigger based on the second event, which can specifically include active triggering (for example, the second event is: the group member actively initiates the service to trigger) and / or passive triggering (for example, the second event is: the group member receives a message from an external node, here, the external node is any node outside the node group to which the group head node belongs, such as a vehicle or RSU, etc.).

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

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

[0248] It should be noted that in step 1201, the manner in which the group head determines the user priority of each node (ie, the group head and group members) includes but is not limited to the following manners:

[0249] Method 1: The group leader determines the user priority corresponding to the node according to the position of the vehicle (that is, the node) in the fleet. For example, the user priority corresponding to the group leader is determined as the highest priority, the user priority of the node corresponding to the edge members of the fleet (such as the rear, leftmost, rightmost, etc.) is determined as the second highest priority, and the user priority of the node corresponding to the remaining vehicles is determined as the low priority.

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

[0251] Step 1202: Determine allocation information corresponding to each of the nodes according to the user priority corresponding to each of the nodes and the first information, wherein 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 the group members (that is, the nodes including the group head node and the member nodes) (that is, the number of services corresponding to the node); the application layer sending period of each service; the service priority of the service; the service maximum transmission rate of the service. Among them, the service maximum transmission rate is equal to the ratio of the maximum transport block size (Transport Block Size, TBS) to the application layer sending period.

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

[0254] It should be noted that each node in step 1202 includes a group head (that is, a group head node) and group members (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 the above step 1202, if Figure 2 As shown, the group head can make congestion control decisions for the group head and group members (that is, determine the allocation information corresponding to each node) based on one or more 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 to be triggered by the group head and / or group members), and the user priority of the group head and / or group members).

[0256] Step 1203: Send the allocation indication to the member node, where the allocation indication includes allocation information corresponding to the member node.

[0257] Here, after the group head sends the allocation information (ie, service allocation information and resource allocation information) after the congestion control decision to each group member through an allocation indication, the group head 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 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 state 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 allocation information corresponding to each of the nodes according to the user priority corresponding to each of the nodes and the first information, includes:

[0260] (i) determining, according to the first information corresponding to each of the nodes, congestion information corresponding to each of the nodes and congestion information corresponding to the node group, respectively, wherein the congestion information includes: a congestion state and / or a congestion level, and the congestion information includes: a congestion state and / or a congestion level.

[0261] Here, in the congestion information corresponding to the node, the congestion state corresponding to the node can also be called the member congestion state, and the congestion level corresponding to the node can also be called the member congestion level. The member congestion state can include congestion and non-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 the node group, the congestion state corresponding to the node group may also be referred to as the group congestion state, and the congestion level corresponding to the node group may also be referred to as the group congestion level. Specifically, the group congestion state may include: no congestion, partial congestion, and full congestion; the group congestion level may be represented by numbers 1 to 7, where 1 is the lowest level and 7 is the highest level.

[0263] In some specific examples, the group congestion state and / or the group congestion level may be determined in the following manner:

[0264] Method 1:

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

[0266] In a specific embodiment, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group are determined respectively according to the first information corresponding to each of the nodes, and the specific process includes:

[0267] Step (1): According to the current service allocation information and current resource allocation information corresponding to each of the nodes, the channel ratio CR value corresponding to each of the nodes is determined respectively.

[0268] That is to say, the group head can determine the CR value of each group member according to the current service allocation information and current resource allocation information of the group members (i.e., each node in the node group to which the group head node belongs). It should be noted that if there are multiple services (including the services to be initiated), the CR values ​​of all services need to be calculated.

[0269] Step (2): According to the CR value and CBR measurement value corresponding to each of the nodes, the congestion information corresponding to each of the nodes is determined respectively with the pre-configured threshold information, wherein the threshold information includes: CBR threshold and CR threshold.

[0270] The group head determines the member congestion state and / or member congestion level of each member in each group according to the calculated CR value of the group members, the current CBR measurement value calculated by the group members, the preconfigured CBR threshold and the CR-limit threshold (ie, the CR threshold).

[0271] Specifically, the member congestion level can be determined by comparing the measured CBR value corresponding to the node with the CBR threshold.

[0272] For example, in a specific example, the mapping relationship between Index (indices, indicating congestion levels), CBR thresholds, and CR-limit thresholds (ie, the above-mentioned CR thresholds) is shown in the following table:

[0273] Index CBR Threshold CR limit threshold 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 the CBR value of a node is 0.48 and the CR value is 0.042, since the CBR value (0.48) is ≤ 0.5 (that is, it is within the range between the threshold 0.3 and the threshold 0.5), the index of the node is determined to be 2 (that is, the member congestion level is 2), and the corresponding CR threshold is 0.1. Since the CR value of the node (0.042) is lower than 0.1, the member congestion state is not congested.

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

[0276] That is, the group head may determine the group congestion state and / or the group congestion level according to the member congestion states and / or member congestion levels of all group members. Specifically, as an optional example, if the congestion states of all group members are not congested, the group congestion state is determined to be not congested; if the congestion states of some group members are congested, the group congestion state is determined to be partially congested; if the congestion states of all group members are congested, the group congestion state is determined to be congested.

[0277] In an optional example, the group congestion level can be determined as the lowest one among the member congestion levels corresponding to each node; in another optional example, the group congestion level can be determined as the highest one among the member congestion levels corresponding to each node; in yet another optional example, the average value of the member congestion levels corresponding to each node can be calculated and used as the group congestion level. It can be understood that if the average value 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 group members, and then performs weighted processing based on the user priorities of the group members to ultimately determine the group congestion state and / or group congestion level.

[0280] In some embodiments, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group are determined respectively according to the first information corresponding to each of the nodes, and the specific process includes:

[0281] Step (1): Determine the CR value corresponding to each of the nodes according to the current service allocation information and current resource allocation information corresponding to each of the nodes.

[0282] That is, the group head can determine the CR value of each group member according to the current service allocation information and current resource allocation information of the group member. It should be noted that if there are multiple services (including services to be initiated), the CR values ​​of all services need to be calculated.

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

[0284] In this step, the group head determines the weighting factor of each member in the group according to the priority of the group member (ie, the user priority corresponding to the node). It should be noted that the sum of the weighting factors is 1.

[0285] Step (3): According to the weighting factors corresponding to the nodes, weighted sum is performed on the CR values ​​corresponding to the nodes to obtain a first CR value.

[0286] In this step, the group head performs weighted summation on the CR value of each member in the group (ie, CR value*weighting factor and sums them up) to obtain a unique CR value (ie, the first CR value).

[0287] Step (4): performing weighted summation on the CBR measurement values ​​corresponding to each of the nodes according to the weighting factors corresponding to each of the nodes to obtain a first CBR value.

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

[0289] Step (5): According to the first CR value and the first CBR value, compare 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 state and / or group congestion level according to the unique CR value (ie, the first CR value), the unique CBR measurement value (ie, the first CBR value), the preconfigured CBR threshold and the CR-limit threshold (ie, 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 up 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] (2) 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 an allocation instruction 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 the first preset condition is met, determining allocation information corresponding to each of the nodes according to congestion information corresponding to the node group and priority information corresponding to each of the nodes includes:

[0298] (1) Determining whether the congestion state corresponding to the node group has changed and / or whether the reduction of 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) when the congestion state corresponding to the node group changes and / or the reduction exceeds the first preset threshold, resource reallocation is performed preferentially 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 business allocation and the current resource allocation, congestion control may not be performed and the current business allocation information and the current resource allocation information may continue to be used; if congestion control has been performed on the current business allocation and the current resource allocation, it is necessary to determine whether the congestion state corresponding to the node group (that is, the group congestion state) has changed and / or whether the congestion level corresponding to the node group (that is, the group congestion level) has decreased by more than a first preset threshold. If the group congestion state has changed and / or the decrease in the group congestion level has exceeded the first preset threshold, resources are reallocated preferentially to the second target business of the second preset condition (that is, business with high business priority or business of group members with high user priority).

[0301] (iii) performing resource adjustment according to the congestion information corresponding to each of the nodes.

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

[0303] (iv) Repeat the step of reallocating resources preferentially for the second target service that meets the second preset condition, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until the third preset condition is met and the allocation information corresponding to each of the nodes 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-congested.

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

[0307] It should be noted that the congestion state and / or congestion level corresponding to the node in the third preset condition is determined according to the newly allocated service allocation information and resource allocation information.

[0308] (3) For the service 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 are normally allocated to the service according to pre-configured parameters.

[0310] In this embodiment, when performing congestion control, the group head can take one or more actions including increasing sub-channel occupancy, lowering MCS, reducing service cycle, and increasing the number of transmissions based on the congestion information corresponding to the node (i.e., member congestion level and / or member congestion status) until it is determined that 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 partially congested, determining allocation information corresponding to each of the nodes according to the congestion information corresponding to the node group and the priority information corresponding to each of the nodes includes:

[0312] (i) determining at least one target node according to the congestion information corresponding to the node group, wherein the target node includes: a node whose congestion status is congested, and / or a node whose congestion level is greater than or equal to a third preset threshold.

[0313] That is to say, if the group congestion state (i.e., the congestion state corresponding to the node group) is partial congestion, the group head can choose to perform congestion control only on one or more group members (i.e., target nodes) that are in the "congested" 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) reallocating resources for the service corresponding to the target node according to the priority information corresponding to the target node.

[0315] It should be noted that the services here include triggered services and services that are about to be triggered. That is to say, if there is a service that is about to be triggered by a member in the group, congestion control is also required when allocating resources to this service, that is, the resource adjustment in the following step (three) needs to be executed until the fourth preset condition is met.

[0316] (iii) performing resource adjustment according to the congestion information corresponding to each of the nodes.

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

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

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

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

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

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

[0323] (5) the business adopts the maximum service cycle allowed;

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

[0325] (7)Terminate unnecessary business.

[0326] That is to say, when the group head performs congestion control on the members within the group, it can reallocate resources for the service according to the priority information corresponding to the target node, and according to the congestion information corresponding to the node (that is, the member congestion level and / or the member congestion status), take one or more actions including reducing the number of sub-channel occupancy, increasing the MCS level, increasing the service cycle, and reducing the number of transmissions (that is, the number of data transmissions) until it is determined that the fourth preset condition has been met based on the newly allocated service allocation information and resource allocation information.

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

[0328] In some embodiments, when the congestion state corresponding to the node group (that is, the group congestion state) is congested or fully congested, determining the allocation information corresponding to each of the nodes according to the congestion information corresponding to the node group and the priority information corresponding to each of the nodes includes:

[0329] (i) reallocating resources for services corresponding to each of the nodes according to priority information corresponding to each of the nodes.

[0330] It should be noted that the services corresponding to the nodes here include triggered services and services that are about to be triggered. That is to say, if there is a service that is about to be triggered by a member in the group, congestion control is also required when allocating resources to this service, that is, the resource adjustment in the following step (two) needs to be executed until the fifth preset condition is met.

[0331] It should be noted that, when the congestion state corresponding to the above node group is partially congested, and when the congestion state corresponding to the node group is congested or fully congested, it can be implemented as follows:

[0332] In some specific embodiments, reallocating resources for services corresponding to the nodes according to the priority information corresponding to the nodes includes:

[0333] Step 1: sort the nodes according to the priority information corresponding to each of the nodes and a preset sorting rule to generate a resource reallocation sequence.

[0334] It should be noted that, when the congestion state corresponding to the above-mentioned node group is partial congestion, the group head can only perform congestion control on the selected target node. Therefore, in this case, in step 1, only each target node can be sorted according to the preset sorting rule to generate a corresponding resource reallocation sequence. It can be understood that if the congestion state corresponding to the node group is congestion or full congestion, step 1 can be performed for all members in the group, that is, for the group head node and all member nodes, the nodes are sorted according to the preset sorting rule to generate a resource reallocation sequence.

[0335] The preset sorting rules include at least one of the following:

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

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

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

[0339] Step 2: reallocate resources for services corresponding to each of the nodes according to the resource reallocation sequence.

[0340] In this embodiment, the group head performs congestion control on all members in the group. The congestion control sequence can be any of the following:

[0341] Method 1: First, reallocate resources to the services of group members in order of service priority from low to high, and then in order of user priority of group members from low to high;

[0342] Method 2: First, reallocate resources to the services of group members in descending order of user priority, and then in descending order of service priority;

[0343] Method 3: Determine a new priority based on the service priority and the user priority of the group members, and reallocate resources to the services of the group members in descending order of the new priority.

[0344] (ii) performing resource adjustment according to the congestion information corresponding to each of the nodes.

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

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

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

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

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

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

[0351] (5) the business adopts the maximum service cycle allowed;

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

[0353] (7) Terminate unnecessary business (terminate one or more unnecessary business).

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

[0355] In this embodiment, the group head reallocates resources for the services of the group members. Specifically, based on the congestion information corresponding to the node (i.e., the member congestion level and / or the member congestion status), one or more actions are taken including reducing the number of sub-channel occupancy, increasing the MCS level, increasing the service cycle, and reducing the number of transmissions, until it is determined that the fifth preset condition has been met based on the newly allocated service / resource information.

[0356] The following is a specific example of the solution provided in the embodiment of the present invention.

[0357] Embodiment 1:

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

[0359] First, after the vehicle formation is established, in order to ensure the safety and order of the formation, the group head needs to determine the basic services that each member in the group should trigger. Specifically, the group head (that is, the group head node) should trigger at least one of the following messages: basic vehicle safety message, formation management message, formation control message, and group service resource allocation indication message; group members (that is, the member nodes corresponding to the group head node, such as the first group member / the second group member / the third group member / the fourth group member) should trigger at least one of the following messages: formation management message, formation control message, and service resource status reporting message.

[0360] Then, the group head performs initial service allocation and / or resource allocation for the basic services of each group member (that is, each node). Specifically, the group head can perform service allocation and resource allocation according to pre-configured parameters. At the same time, in order to avoid the impact of half-duplex, the group head needs to allocate different time-frequency resources to each group member. In a specific example, the service allocation information and resource allocation information after the group head performs the allocation are as follows:

[0361] Group header: the number of services is 4; among them, service 1 (vehicle basic safety message): the application layer sending period is 100ms, the service priority is 2, the MCS is 7, the occupied RB is 27, the TBS is 3368, the number of transmissions is 2, and the time-frequency resource is time-frequency resource 1; service 2 (formation management message): the application layer sending period is 200ms, the service priority is 3, 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 2; service 3 (formation control message): the application layer sending period is 50ms, the service priority is 3, the MCS is 12, the occupied RB is 48, the TBS is 9528, the number of transmissions 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 200ms, the service priority is 3, 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 4.

[0362] The first group of members: the number of services is 3; among them, service 1 (formation management message): the application layer sending period is 200ms, the service priority is 3, 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 5 time-frequency resource; service 2 (formation control message): the application layer sending period is 100ms, the service priority is 3, the MCS is 12, the occupied RB is 48, the TBS is 9528, the number of transmissions is 2, and the time-frequency resource is 6 time-frequency resource; service 3 (service resource status reporting message): the application layer sending period is 100ms, the service priority is 5, the MCS is 7, the occupied RB is 27, the TBS is 3368, the number of transmissions is 2, and the time-frequency resource is 7 time-frequency resource.

[0363] The second group of members: the number of services is 3; among them, service 1 (formation management message): the application layer sending period is 200ms, the service priority is 3, 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 8; service 2 (formation control message): the application layer sending period is 100ms, the service priority is 3, the MCS is 12, the occupied RB is 48, the TBS is 9528, the number of transmissions is 2, and the time-frequency resource is time-frequency resource 9; service 3 (service resource status reporting message): the application layer sending period is 100ms, the service priority is 5, the MCS is 7, the occupied RB is 27, the TBS is 3368, the number of transmissions is 2, and the time-frequency resource is time-frequency resource 10.

[0364] Members of the third group: the number of services is 3; among them, service 1 (formation management message): the application layer sending period is 200ms, the service priority is 3, 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 11; service 2 (formation control message): the application layer sending period is 100ms, the service priority is 3, the MCS is 12, the occupied RB is 48, the TBS is 9528, the number of transmissions is 2, and the time-frequency resource is 12; service 3 (service resource status reporting message): the application layer sending period is 100ms, the service priority is 5, the MCS is 7, the occupied RB is 27, the TBS is 3368, the number of transmissions is 2, and the time-frequency resource is 13.

[0365] Members of the fourth group: the number of services is 3; among them, service 1 (formation management message): the application layer sending period is 200ms, the service priority is 3, 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 14 time-frequency resources; service 2 (formation control message): the application layer sending period is 100ms, the service priority is 3, the MCS is 12, the occupied RB is 48, the TBS is 9528, the number of transmissions is 2, and the time-frequency resource is 15 time-frequency resources; service 3 (service resource status reporting message): the application layer sending period is 100ms, the service priority is 5, the MCS is 7, the occupied RB is 27, the TBS is 3368, the number of transmissions is 2, and the time-frequency resource is 16 time-frequency resources.

[0366] Finally, the group head may send service allocation information and resource allocation information of the basic service of each group member to each group member through an intra-group service resource allocation indication message.

[0367] Embodiment 2:

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

[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 leader. Among them, each group member reports the CBR measurement value to the group leader every 100 ms. After receiving the current CBR measurement value reported by the group member, the group leader can determine the Index (index) based on the current service allocation information, current resource allocation information, current CBR measurement value calculated by the group member, pre-configured CBR threshold, CR-limit threshold, etc., and then determine the CR limit threshold. In addition, the group leader 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 of the group member (i.e., the congestion state corresponding to the node) and / or the member congestion level (i.e., the congestion level corresponding to the node).

[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] Index CBR Threshold CR limit threshold 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 specifically set according to actual needs.

[0373] Group leader: 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 Index as 2, determine the CR limit threshold as 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 leader is non-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 Index as 2, determine the CR limit threshold as 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 non-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 member congestion status of the second group members 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 member congestion status of the third group members 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 member congestion status of the fourth group members 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 vehicle travels to the suburban intersection, the group head receives the current CBR measurement value 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 of the group members, the current resource allocation information, the current CBR measurement value calculated by the group members, the pre-configured CBR threshold, and the CR-limit threshold, 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] 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] 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] 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] 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, based on the member congestion status and member congestion level of each group member, the group head determines that the group congestion status is partially congested, determines the group congestion level to be 3, 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 status of the group head changes to non-congested, and at the same time, the group congestion status changes to non-congested. The group head sends the formation control message according to the new service allocation information of Service 3.

[0386] When the formation vehicles drive to the urban intersection and 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 status 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, etc., 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, determine Index to be 4, determine the CR limit threshold to be 0.03, and judge that the calculated CR value (0.052) exceeds the CR limit threshold. Therefore, the member congestion status 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, determine Index to be 4, determine the CR limit threshold to be 0.03, and judge that the calculated CR value (0.042) exceeds the CR limit threshold. Therefore, the member congestion status 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, determine Index to be 4, determine the CR limit threshold to be 0.03, and judge that the calculated CR value (0.042) exceeds the CR limit threshold. Therefore, the member congestion status is congested, and the member congestion level is 4.

[0390] Members of the third group: 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, the 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: The CBR value is 0.62; 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.62) within the range of 0.6 < CBR ≤ 0.7, the 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] In this way, the group head determines that the group congestion status is full congestion and the group congestion level is 4 based on the member congestion status and member congestion level of each group member, and determines that congestion control needs to be performed accordingly.

[0393] The group head performs congestion control on all group members. Since the user priority of the group head 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, the MCS is 7, the occupied RB is 27, the TBS is 3368, the number of transmissions 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 number of transmissions 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, the MCS is 15, the occupied RB is 36, the TBS is 10296, the number of transmissions 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, the MCS is 14, the occupied RB is 27, the TBS is 6968, the number of transmissions 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 member congestion status of the group head changes to non-congestion.

[0396] Members of the first group: the number of services is 3; service 1 (formation management message): the application layer sending period is 500ms, the service priority is 3, the MCS is 14, the occupied RB is 27, the TBS is 6968, the number of transmissions is 2, and the time-frequency resource is 5; service 2 (formation control message): the application layer sending period is 200ms, the service priority is 3, the MCS is 15, the occupied RB is 36, the TBS is 10296, the number of transmissions is 2, and the time-frequency resource is 6; service 3 (service resource status reporting message): the application layer sending period is 500ms, the service priority is 5, the MCS is 12, the occupied RB is 18, the TBS is 3624, the number of transmissions is 2, and the time-frequency resource is 7.

[0397] The CR value of the first group of 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 state of the first group of members is changed to non-congested.

[0398] Members of the second group: the number of services is 3; service 1 (formation management message): the application layer sending period is 500ms, the service priority is 3, the MCS is 14, the occupied RB is 27, the TBS is 6968, the number of transmissions is 2, and the time-frequency resource is 8; service 2 (formation control message): the application layer sending period is 200ms, the service priority is 3, the MCS is 15, the occupied RB is 36, the TBS is 10296, the number of transmissions is 2, and the time-frequency resource is 9; service 3 (service resource status reporting message): the application layer sending period is 500ms, the service priority is 5, the MCS is 12, the occupied RB is 18, the TBS is 3624, the number of transmissions is 2, and the time-frequency resource is 10.

[0399] The CR value of the second group of 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 state of the second group of members is changed to non-congested.

[0400] Members of the third group: the number of services is 3; service 1 (formation management message): the application layer sending period is 500ms, the service priority is 3, the MCS is 14, the occupied RB is 27, the TBS is 6968, the number of transmissions is 2, and the time-frequency resource is 11; service 2 (formation control message): the application layer sending period is 200ms, the service priority is 3, the MCS is 15, the occupied RB is 36, the TBS is 10296, the number of transmissions is 2, and the time-frequency resource is 12; service 3 (service resource status reporting message): the application layer sending period is 500ms, the service priority is 5, the MCS is 12, the occupied RB is 18, the TBS is 3624, the number of transmissions is 2, and the 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 member congestion state of the third group member is changed to non-congested.

[0402] Members of the fourth group: the number of services is 3; service 1 (formation management message): the application layer sending period is 500ms, the service priority is 3, the MCS is 14, the occupied RB is 27, the TBS is 6968, the number of transmissions is 2, and the time-frequency resource is time-frequency resource 14; service 2 (formation control message): the application layer sending period is 200ms, the service priority is 3, the MCS is 15, the occupied RB is 36, the TBS is 10296, the number of transmissions is 2, and the time-frequency resource is time-frequency resource 15; service 3 (service resource status reporting message): the application layer sending period is 500ms, the service priority is 5, the MCS is 12, the occupied RB is 18, the TBS is 3624, the number of transmissions is 2, and the time-frequency resource is 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 member congestion state of the fourth group member is changed to non-congested.

[0404] In this way, the group head determines that the group congestion state is changed to non-congestion according to the changed member congestion state of each group member.

[0405] Finally, the group head sends the new service allocation information and resource allocation information of each group member to each group member through an allocation instruction (i.e., an intra-group service resource allocation instruction message). After each group member receives the allocation instruction, each group member sends services according to the new service allocation information and resource allocation information.

[0406] Embodiment 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 within the group.

[0407] like Figure 5 As shown in the figure, the first group member, as the tail member of the team, finds that there are many free vehicles approaching the team during the platoon driving process. The first group member needs to send the perceived information to the group head and trigger the perception data sharing service. At this time, the first group member can send a service trigger request message to the group head, which carries the service type to be triggered and the currently calculated CBR information value (such as 0.4); the group head sends a service resource status request to other group members to request to report CBR information; the group members send a service resource status report to the group head, reporting the currently calculated CBR information, which is 0.36, 0.42 and 0.4 respectively; the group head determines the CR value of each member in the group according to the current service allocation information, current resource allocation information and the service to be initiated (if any) of the group members, 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 member is (5*2 / 200+5*2 / 100+5*2 / 100) / 5=0.05;

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

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

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

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

[0414] The group header 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 header linearly averages the current CBR measurement values of each group member, where the calculated CBR value of the group header is 0.45, to obtain a unique CBR measurement value of 0.406. The group header determines the group congestion state 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 in the table:

[0416] Index CBR Threshold CR limit threshold 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 header 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 state is non-congested, determines that the group congestion level is 2, and accordingly determines not to perform congestion control. And according to the pre-configured parameters of the sensed data sharing service, it performs service allocation and resource allocation for new services. The specific allocation is as follows:

[0418] The first group member: The number of new services is 1; New service 1 - sensed 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 header 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 to be 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 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 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 according to 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. After judging that the calculated CR value (0.047) exceeds the CR limit threshold, it is determined that the group congestion status is congested and the group congestion level is 4, and congestion control is required.

[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, MCS is 7, the occupied RB is 27, TBS is 3368, the number of transmissions 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 number of transmissions 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, MCS is 15, the occupied RB is 36, TBS is 10296, the number of transmissions 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] Members of the first group: the number of services is 3; service 1 (formation management message): the application layer sending period is 500ms, the service priority is 3, the MCS is 14, the occupied RB is 27, the TBS is 6968, the number of transmissions is 2, and the time-frequency resource is 4; service 2 (formation control message): the application layer sending period is 200ms, the service priority is 3, the MCS is 15, the occupied RB is 36, the TBS is 10296, the number of transmissions is 2, and the time-frequency resource is 5; service 3 (perception data sharing message): the application layer sending period is 200ms, the service priority is 2, the MCS is 14, the occupied RB is 27, the TBS is 6968, the number of transmissions is 2, and the time-frequency resource is 6.

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

[0426] Members of the second group: the number of services is 2; service 1 (formation management message): the application layer sending period is 500ms, the service priority is 3, the MCS is 14, the occupied RB is 27, the TBS is 6968, the number of transmissions is 2, and the time-frequency resource is the time-frequency resource 7; service 2 (formation control message): the application layer sending period is 200ms, the service priority is 3, the MCS is 15, the occupied RB is 36, the TBS is 10296, the number of transmissions is 2, and the time-frequency resource is the time-frequency resource 8;

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

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

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

[0430] Members of the fourth group: the number of services is 2; service 1 (formation management message): the application layer sending period is 500ms, the service priority is 3, the MCS is 14, the occupied RB is 27, the TBS is 6968, the number of transmissions is 2, and the time-frequency resource is 11; service 2 (formation control message): the application layer sending period is 500ms, the service priority is 3, the MCS is 15, the occupied RB is 36, the TBS is 10296, the number of transmissions is 2, and the time-frequency resource is 12.

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

[0432] Afterwards, the group head performs a weighted summation (CR value*weighting factor) on the CR value of each group member and obtains a unique CR value of 0.02075, which is lower than the CR limit threshold (0.03). It is determined that the group congestion state is changed to non-congested.

[0433] Finally, the group head sends the new service allocation information and resource allocation information of each group member to each group member through an allocation instruction (i.e., an intra-group service resource allocation instruction message). After each group member receives the allocation instruction, each group member sends services according to the new service allocation information and resource allocation information.

[0434] In the embodiment of the present invention, the group head node can obtain the first information of the member node corresponding to the group head node, and send an allocation instruction to the member node according to the first information, thereby instructing the member node to send services. In this way, congestion control suitable for the group head resource allocation scenario can be implemented.

[0435] Second embodiment

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

[0437] The information acquisition module 601 is used to acquire first information of a member node corresponding to a group head node, where the member node corresponding to the group head node includes: at least one node other than the group head node in the node group to which the group head node belongs;

[0438] An indication sending module 602 is used to send an allocation indication to the member node according to the first information, where the allocation indication is used to indicate service sending;

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

[0440] The measurement value of the channel busy ratio CBR;

[0441] A service type of a first target service, where the first target service is a service 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 node corresponding to the group head node, and send an allocation instruction to the member node according to the first information, thereby instructing the member node to send services. In this way, congestion control suitable for group head resource allocation scenarios can be implemented.

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

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

[0446] A second processing submodule, configured to determine allocation information corresponding to each of the nodes according to the user priority corresponding to each of the nodes and the first information, wherein the allocation information includes: service allocation information and resource allocation information;

[0447] The indication sending submodule is used to send the allocation indication to the member node, where the allocation indication includes the allocation information corresponding to the member node.

[0448] Optionally, the second processing submodule includes:

[0449] A first processing unit, configured to determine, according to the first information corresponding to each of the nodes, congestion information corresponding to the node group, respectively, wherein the congestion information includes: a congestion state and / or a congestion level; and the congestion information includes: a congestion state and / or a congestion level;

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

[0451] Optionally, the second processing unit includes:

[0452] A first judgment subunit, used to judge whether the congestion state corresponding to the node group has changed and / or whether the reduction range of the congestion level corresponding to the node group exceeds a first preset threshold;

[0453] A first reconfiguration subunit is used to preferentially reallocate resources for a second target service that meets a second preset condition when the congestion state corresponding to the node group changes and / or the reduction exceeds the first preset threshold;

[0454] A first adjustment subunit, configured to perform resource adjustment according to congestion information corresponding to each of the nodes;

[0455] The first processing subunit is used to repeatedly execute the step of preferentially reallocating resources for the second target service that meets the second preset condition, to the step of performing resource adjustment according to the congestion information corresponding to each of the nodes, until the third preset condition is met, and the allocation information corresponding to each of the nodes is obtained;

[0456] 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 a first preset threshold;

[0457] 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;

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

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

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

[0461] For the service to be triggered, resources are allocated using preconfigured service parameters.

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

[0463] Increase the number of sub-channel occupancy;

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

[0465] Shorten business cycle;

[0466] Increase the number of data transfers.

[0467] Optionally, the second processing unit includes:

[0468] A second processing subunit is used to determine at least one target node according to the congestion information corresponding to the node group, wherein 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] A second reconfiguration subunit, configured to reallocate resources for the service corresponding to the target node according to the priority information corresponding to the target node;

[0470] A second adjustment subunit, configured to perform resource adjustment according to congestion information corresponding to each of the nodes;

[0471] a third processing subunit, configured to repeatedly execute the step of reallocating resources for the services corresponding to the target node according to the priority information corresponding to the target node, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until a fourth preset condition is met, and allocation information corresponding to each of the nodes is obtained;

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

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

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

[0475] The service adopts the minimum allowed number of sub-channel occupancy;

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

[0477] The business adopts the maximum business cycle allowed;

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

[0479] End unnecessary business.

[0480] Optionally, the second processing unit includes:

[0481] A third reconfiguration subunit, configured to reallocate resources for services corresponding to each of the nodes according to priority information corresponding to each of the nodes;

[0482] A third adjustment subunit, configured to perform resource adjustment according to congestion information corresponding to each of the nodes;

[0483] a fourth processing subunit, configured to repeatedly execute the step of reallocating resources for services corresponding to each of the nodes according to the priority information corresponding to each of the nodes, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until a fifth preset condition is met, and allocation information corresponding to each of the nodes is obtained;

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

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

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

[0487] The service adopts the minimum allowed number of sub-channel occupancy;

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

[0489] The business adopts the maximum business cycle allowed;

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

[0491] End unnecessary business.

[0492] Optionally, the device comprises:

[0493] A fifth processing subunit, configured to sort the nodes according to the priority information corresponding to each of the nodes and a preset sorting rule, and generate a resource reallocation sequence;

[0494] A fourth reconfiguration subunit, configured to reallocate resources for services corresponding to each of the nodes according to the resource reallocation sequence;

[0495] The preset sorting rules include at least one of the following:

[0496] Based on the dual-dimensional priority sorting mechanism, the first-level sorting is performed in the order of the business priority from low to high, and then the second-level sorting is performed in the order of the user priority corresponding to each node from low to high within the same business priority level;

[0497] Based on the dual-dimensional priority sorting mechanism, the first level sorting is performed in the order of user priority corresponding to each node from low to high, and then the second level sorting is performed in the order of service priority from low to high within the same user priority level;

[0498] Based on the comprehensive priority index sorting mechanism, a weighted calculation is first performed according to the business priority and the user priority corresponding to each node to generate a comprehensive priority index, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

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

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

[0501] Increase the MCS level;

[0502] Increase business cycle;

[0503] Reduce the number of data transfers.

[0504] Optionally, the first processing unit includes:

[0505] a sixth processing subunit, configured to determine a channel ratio CR value corresponding to each of the nodes according to current service allocation information and current resource allocation information corresponding to each of the nodes;

[0506] A first comparison subunit is used to compare the CR value and the CBR measurement value corresponding to each of the nodes with the pre-configured threshold information to determine the congestion information corresponding to each of the nodes, wherein the threshold information includes: a CBR threshold and a CR threshold;

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

[0508] Optionally, the first processing unit includes:

[0509] an eighth processing subunit, configured to determine the CR value corresponding to each of the nodes according to the current service allocation information and the current resource allocation information corresponding to each of the nodes;

[0510] A ninth processing subunit, configured to determine a weighting factor corresponding to each of the nodes according to a user priority corresponding to each of the nodes;

[0511] a tenth processing subunit, configured to perform weighted summation on the CR values ​​corresponding to the nodes according to the weighting factors corresponding to the nodes, to obtain a first CR value;

[0512] an eleventh processing subunit, configured to perform weighted summation on the CBR measurement values ​​corresponding to the nodes according to the weighting factors corresponding to the nodes, to obtain a first CBR value;

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

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

[0515] a first sending submodule, configured to send a first request to the member node according to a first trigger condition, and receive 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 to send the first information of the member node;

[0516] A first receiving submodule, configured to receive first information of the member node reported by the member node according to a second trigger condition;

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

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

[0519] An event trigger based on a first event, wherein the first event includes: a measured value of a 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;

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

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

[0522] Event triggering based on a second event, the second event includes: the member node actively initiating a service request, and / or the member node receiving a trigger message sent by 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. All implementation means in the first embodiment are applicable to the embodiment of the congestion control device and can achieve the same technical effect.

[0524] Third embodiment

[0525] In order to better achieve the above goals, Figure 7 As shown, the third embodiment of the present invention further provides a control device, including:

[0526] A processor 700; and a memory 720 connected to the processor 700 via a bus interface, wherein the memory 720 is used to store programs and data used by the processor 700 when performing operations, and the processor 700 calls and executes the programs and data stored in the memory 720.

[0527] The transceiver 710 is connected to the 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 to perform the following steps:

[0528] Acquire first information of a member node corresponding to a group head node, where the member node corresponding to the group head node includes: at least one node other than the group head node in a node group to which the group head node belongs;

[0529] Sending an allocation indication to the member node according to the first information, where the allocation indication is used to indicate service sending;

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

[0531] The measurement value of the channel busy ratio CBR;

[0532] A service type of a first target service, where the first target service is a service 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 node corresponding to the group head node, and send an allocation instruction to the member node according to the first information, thereby instructing the member node to send services. In this way, congestion control suitable for group head resource allocation scenarios can be implemented.

[0535] Among them, Figure 7 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 700 and various circuits of the memory represented by the memory 720 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 710 may be a plurality of components, namely, a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium. For different terminals, the user interface 730 may also be an interface capable of externally connecting or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 may store data used by the processor 700 when performing operations.

[0536] Optionally, when the processor 700 sends an allocation indication to the member node according to the first information, it is specifically configured to:

[0537] Determine the user priority corresponding to each node in the node group according to the second information corresponding to each node, wherein the second information includes: vehicle type and / or vehicle location;

[0538] According to the user priority corresponding to each of the nodes and the first information, respectively determine the allocation information corresponding to each of the nodes, the allocation information including: service allocation information and resource allocation information;

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

[0540] Optionally, when the processor 700 determines allocation information corresponding to each of the nodes according to the user priority corresponding to each of the nodes and the first information, it is specifically configured to:

[0541] Determine, according to the first information corresponding to each of the nodes, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group, respectively, wherein the congestion information includes: a congestion state and / or a congestion level; and the congestion information includes: a congestion state and / or a congestion level;

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

[0543] Optionally, when the first preset condition is met, the processor 700, when determining allocation information corresponding to each of the nodes according to the congestion information corresponding to the node group and the priority information corresponding to each of the nodes, is specifically configured to:

[0544] Determine whether the congestion state corresponding to the node group has changed and / or whether the reduction range of the congestion level corresponding to the node group exceeds a first preset threshold;

[0545] When the congestion state corresponding to the node group changes and / or the reduction exceeds the first preset threshold, resource reallocation is performed preferentially for a second target service that meets a second preset condition;

[0546] Perform resource adjustment according to congestion information corresponding to each of the nodes;

[0547] Repeat the step of preferentially reallocating resources for the second target service that meets the second preset condition, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until the third preset condition is met, and the allocation information corresponding to each of the nodes is obtained;

[0548] 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 a first preset threshold;

[0549] 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;

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

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

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

[0553] For the service to be triggered, resources are allocated using preconfigured service parameters.

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

[0555] Increase the number of sub-channel occupancy;

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

[0557] Shorten business cycle;

[0558] Increase the number of data transfers.

[0559] Optionally, when the congestion state corresponding to the node group is partial congestion, the processor 700, when determining allocation information corresponding to each of the nodes according to the congestion information corresponding to the node group and the priority information corresponding to each of the nodes, is specifically configured to:

[0560] Determine at least one target node according to the congestion information corresponding to the node group, 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] reallocating resources for the services corresponding to the target node according to the priority information corresponding to the target node;

[0562] Perform resource adjustment according to congestion information corresponding to each of the nodes;

[0563] Repeat the step of reallocating resources for the services corresponding to the target node according to the priority information corresponding to the target node, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until the fourth preset condition is met, and the allocation information corresponding to each of the nodes is obtained;

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

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

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

[0567] The service adopts the minimum allowed number of sub-channel occupancy;

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

[0569] The business adopts the maximum business cycle allowed;

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

[0571] End unnecessary business.

[0572] Optionally, when the congestion state corresponding to the node group is full congestion, the processor 700, when determining allocation information corresponding to each of the nodes according to the congestion information corresponding to the node group and the priority information corresponding to each of the nodes, is specifically configured to:

[0573] reallocating resources for services corresponding to each of the nodes according to priority information corresponding to each of the nodes;

[0574] Perform resource adjustment according to congestion information corresponding to each of the nodes;

[0575] Repeat the step of reallocating resources for services corresponding to each of the nodes according to the priority information corresponding to each of the nodes, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until a fifth preset condition is met, and allocation information corresponding to each of the nodes is obtained;

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

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

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

[0579] The service adopts the minimum allowed number of sub-channel occupancy;

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

[0581] The business adopts the maximum business cycle allowed;

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

[0583] End unnecessary business.

[0584] Optionally, when the processor 700 reallocates resources for services corresponding to each of the nodes according to the priority information corresponding to each of the nodes, it is specifically configured to:

[0585] According to the priority information corresponding to each of the nodes, the nodes are sorted according to a preset sorting rule to generate a resource reallocation sequence;

[0586] According to the resource reallocation sequence, reallocate resources for services corresponding to each of the nodes;

[0587] The preset sorting rules include at least one of the following:

[0588] Based on the dual-dimensional priority sorting mechanism, the first-level sorting is performed in the order of the business priority from low to high, and then the second-level sorting is performed in the order of the user priority corresponding to each node from low to high within the same business priority level;

[0589] Based on the dual-dimensional priority sorting mechanism, the first level sorting is performed in the order of user priority corresponding to each node from low to high, and then the second level sorting is performed in the order of service priority from low to high within the same user priority level;

[0590] Based on the comprehensive priority index sorting mechanism, a weighted calculation is first performed according to the business priority and the user priority corresponding to each node to generate a comprehensive priority index, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

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

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

[0593] Increase the MCS level;

[0594] Increase business cycle;

[0595] Reduce the number of data transfers.

[0596] Optionally, when the processor 700 determines, according to the first information corresponding to each of the nodes, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group, the processor 700 is specifically configured to:

[0597] Determine the channel ratio CR value corresponding to each of the nodes according to the current service allocation information and the current resource allocation information corresponding to each of the nodes;

[0598] According to the CR value and the CBR measurement value corresponding to each of the nodes, the congestion information corresponding to each of the nodes is determined respectively with the pre-configured threshold information, wherein the threshold information includes: a CBR threshold and a CR threshold;

[0599] Congestion information corresponding to the node group is determined according to the congestion information corresponding to each of the nodes.

[0600] Optionally, when the processor 700 determines, according to the first information corresponding to each of the nodes, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group, the processor 700 is specifically configured to:

[0601] Determine the CR value corresponding to each of the nodes according to the current service allocation information and the current resource allocation information corresponding to each of the nodes;

[0602] Determine the weighting factors corresponding to the nodes respectively according to the user priorities corresponding to the nodes;

[0603] According to the weighting factors corresponding to the nodes, weighted sum is performed on the CR values ​​corresponding to the nodes to obtain a first CR value;

[0604] According to the weighting factors corresponding to the nodes, weighted summation is performed on the CBR measurement values ​​corresponding to the nodes to obtain a first CBR value;

[0605] The first CR value and the first CBR value are compared with preconfigured threshold information to determine congestion information corresponding to the node group.

[0606] Optionally, when acquiring the first information of the member node corresponding to the group head node, the processor 700 is specifically configured to perform at least one of the following:

[0607] According to a first trigger condition, sending a first request to the member node, and receiving 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 sending the first information of the member node;

[0608] receiving first information of the member node reported by the member node according to a second trigger condition;

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

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

[0611] An event trigger based on a first event, wherein the first event includes: a measured value of a 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;

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

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

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

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

[0616] The present application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the above Figure 1 The various processes of the method embodiment 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 to implement the above embodiments may be accomplished by hardware, or may be accomplished by instructing relevant hardware through a computer program, wherein the computer program includes instructions for executing part or all of the steps of the above method; and the computer program may be stored in a readable storage medium, and the storage medium may be any form of storage medium.

[0618] In addition, a specific embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the method in the first embodiment described above are implemented. The same technical effect can be achieved, and to avoid repetition, it will not be described here.

[0619] In addition, it should be noted that in the apparatus and method of the present invention, it is obvious that each component or each step can be decomposed and / or recombined. These decompositions and / or recombinations should be regarded as equivalent schemes of the present invention. Moreover, the steps of performing the above-mentioned series of processing can naturally be performed in chronological order according to the order of description, but it is not necessary to perform them in chronological order, and some steps can be performed in parallel or independently of each other. For those of ordinary skill in the art, it is understood that all or any steps or components of the method and apparatus of the present invention can be implemented in any computing device (including processors, storage media, etc.) or a network of computing devices in hardware, firmware, software or a combination thereof, which can be achieved by those of ordinary skill in the art using their basic programming skills after reading the description of the present invention.

[0620] Therefore, the purpose of the present invention can also be achieved by running a program or a group of programs on any computing device. The computing device can be a well-known general device. Therefore, the purpose of the present invention can also be achieved by simply providing a program product containing a program code that implements the method or device. That is to say, 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 well-known storage medium or any storage medium developed in the future. It should also be pointed out that in the device and method of the present invention, it is obvious that each component or each step can be decomposed and / or recombined. These decompositions and / or recombinations should be regarded as equivalent schemes of the present invention. In addition, the steps of performing the above-mentioned series of processing can naturally be performed in chronological order according to the order of description, but it is not necessary to perform them in chronological order. Some steps can be performed in parallel or independently of each other.

[0621] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A congestion control method, characterized in that: include: Acquire first information of a member node corresponding to a group head node, where the member node corresponding to the group head node includes: at least one node other than the group head node in a node group to which the group head node belongs; Sending an allocation indication to the member node according to the first information, where the allocation indication is used to indicate service sending; The first information includes at least one of the following: The measurement value of the channel busy ratio CBR; A service type of a first target service, where the first target service is a service to be triggered; The service priority of the first target service.

2. The method according to claim 1, characterized in that: The sending an allocation indication to the member node according to the first information includes: Determine the user priority corresponding to each node in the node group according to the second information corresponding to each node, wherein the second information includes: vehicle type and / or vehicle location; According to the user priority corresponding to each of the nodes and the first information, respectively determine the allocation information corresponding to each of the nodes, the allocation information including: service allocation information and resource allocation information; The allocation indication is sent to the member node, where the allocation indication includes allocation information corresponding to the member node.

3. The method according to claim 2, characterized in that The determining, according to the user priority corresponding to each of the nodes and the first information, the allocation information corresponding to each of the nodes comprises: Determine, according to the first information corresponding to each of the nodes, congestion information corresponding to each of the nodes and congestion information corresponding to the node group, respectively, wherein the congestion information includes: congestion state and / or congestion level; According to the congestion information corresponding to the node group and the priority information corresponding to each of the nodes, the allocation information corresponding to each of the nodes is determined respectively, and the priority information includes: the user priority and / or the service priority.

4. The method according to claim 3, characterized in that In the case where the first preset condition is met, determining allocation information corresponding to each of the nodes according to the congestion information corresponding to the node group and the priority information corresponding to each of the nodes, respectively, includes: Determine whether the congestion state corresponding to the node group has changed and / or whether the reduction range of the congestion level corresponding to the node group exceeds a first preset threshold; When the congestion state corresponding to the node group changes and / or the reduction exceeds the first preset threshold, resource reallocation is performed preferentially for a second target service that meets a second preset condition; Perform resource adjustment according to congestion information corresponding to each of the nodes; Repeat the step of preferentially reallocating resources for the second target service that meets the second preset condition, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until the third preset condition is met, and the allocation information corresponding to each of the nodes is obtained; 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 a first preset threshold; 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; The third preset condition includes at least one of the following: The congestion state corresponding to the node is non-congested; The congestion level corresponding to the node is less than or equal to a second preset threshold; For the service to be triggered, resources are allocated using preconfigured service parameters.

5. The method according to claim 4, characterized in that: The execution resource adjustment includes at least one of the following: Increase the number of sub-channel occupancy; Reduce the modulation and coding scheme MCS level; Shorten business cycle; Increase the number of data transfers.

6. The method according to claim 3, characterized in that In a case where the congestion state corresponding to the node group is partial congestion, determining allocation information corresponding to each of the nodes according to the congestion information corresponding to the node group and the priority information corresponding to each of the nodes, respectively, includes: Determine at least one target node according to the congestion information corresponding to the node group, 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; reallocating resources for the services corresponding to the target node according to the priority information corresponding to the target node; Perform resource adjustment according to congestion information corresponding to each of the nodes; Repeat the step of reallocating resources for the services corresponding to the target node according to the priority information corresponding to the target node, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until the fourth preset condition is met, and the allocation information corresponding to each of the nodes is obtained; The fourth preset condition includes at least one of the following: The congestion state corresponding to the target node is non-congested; The congestion level corresponding to the target node is less than or equal to a second preset threshold; The service adopts the minimum allowed number of sub-channel occupancy; The service uses the maximum allowed MCS level; The business adopts the maximum business cycle allowed; The service uses the minimum number of transmissions allowed; End unnecessary business.

7. The method according to claim 3, characterized in that When the congestion state corresponding to the node group is congested or fully congested, determining allocation information corresponding to each of the nodes according to the congestion information corresponding to the node group and the priority information corresponding to each of the nodes, respectively, includes: reallocating resources for services corresponding to each of the nodes according to priority information corresponding to each of the nodes; Perform resource adjustment according to congestion information corresponding to each of the nodes; Repeat the step of reallocating resources for services corresponding to each of the nodes according to the priority information corresponding to each of the nodes, to the step of adjusting resources according to the congestion information corresponding to each of the nodes, until a fifth preset condition is met, and allocation information corresponding to each of the nodes is obtained; The fifth preset condition includes at least one of the following: The congestion state corresponding to the node group is non-congested; The congestion level corresponding to the node group is less than or equal to a second preset threshold; The service adopts the minimum allowed number of sub-channel occupancy; The service uses the maximum allowed MCS level; The business adopts the maximum business cycle allowed; The service uses the minimum number of transmissions allowed; End unnecessary business.

8. The method according to claim 6 or 7, characterized in that: According to the priority information corresponding to the node, reallocating resources for the service corresponding to the node includes: According to the priority information corresponding to each of the nodes, the nodes are sorted according to a preset sorting rule to generate a resource reallocation sequence; According to the resource reallocation sequence, reallocate resources for services corresponding to each of the nodes; The preset sorting rules include at least one of the following: Based on the dual-dimensional priority sorting mechanism, the first-level sorting is performed in the order of the business priority from low to high, and then the second-level sorting is performed in the order of the user priority corresponding to each node from low to high within the same business priority level; Based on the dual-dimensional priority sorting mechanism, the first level sorting is performed in the order of user priority corresponding to each node from low to high, and then the second level sorting is performed in the order of service priority from low to high within the same user priority level; Based on the comprehensive priority index sorting mechanism, a weighted calculation is first performed according to the business priority and the user priority corresponding to each node to generate a comprehensive priority index, and then the nodes are sorted in order from low to high according to the comprehensive priority index.

9. The method according to claim 6 or 7, characterized in that: The execution resource adjustment includes at least one of the following: Reduce the number of sub-channel occupancy; Increase the MCS level; Increase business cycle; Reduce the number of data transfers.

10. The method according to claim 3, characterized in that: The determining, according to the first information corresponding to each of the nodes, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group respectively includes: Determine the channel ratio CR value corresponding to each of the nodes according to the current service allocation information and the current resource allocation information corresponding to each of the nodes; According to the CR value and the CBR measurement value corresponding to each of the nodes, the congestion information corresponding to each of the nodes is determined respectively with the pre-configured threshold information, wherein the threshold information includes: a CBR threshold and a CR threshold; Congestion information corresponding to the node group is determined according to the congestion information corresponding to each of the nodes.

11. The method according to claim 3, characterized in that The determining, according to the first information corresponding to each of the nodes, the congestion information corresponding to each of the nodes and the congestion information corresponding to the node group respectively includes: Determine the CR value corresponding to each of the nodes according to the current service allocation information and the current resource allocation information corresponding to each of the nodes; Determine the weighting factors corresponding to the nodes respectively according to the user priorities corresponding to the nodes; According to the weighting factors corresponding to the nodes, weighted sum is performed on the CR values ​​corresponding to the nodes to obtain a first CR value; According to the weighting factors corresponding to the nodes, weighted summation is performed on the CBR measurement values ​​corresponding to the nodes to obtain a first CBR value; The first CR value and the first CBR value are compared with preconfigured threshold information to determine congestion information corresponding to the node group.

12. The method according to claim 1, characterized in that The obtaining of first information of a member node corresponding to the group head node includes at least one of the following: According to a first trigger condition, sending a first request to the member node, and receiving 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 sending the first information of the member node; receiving first information of the member node reported by the member node according to a second trigger condition; The first trigger condition includes at least one of the following: Periodic triggering based on a first preset period; An event trigger based on a first event, wherein the first event includes: a measured value of a 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; The second trigger condition includes at least one of the following: Periodic triggering based on a second preset period; Event triggering based on a second event, the second event includes: the member node actively initiating a service request, and / or the member node receiving a trigger message sent by any node outside the node group to which the group head node belongs.

13. A congestion control device, characterized in that: include: An information acquisition module, configured to acquire first information of a member node corresponding to a group head node, wherein the member node corresponding to the group head node includes: at least one node other than the group head node in a node group to which the group head node belongs; an indication sending module, configured to send an allocation indication to the member node according to the first information, wherein the allocation indication is used to indicate service sending; The first information includes at least one of the following: The measurement value of the channel busy ratio CBR; A service type of a first target service, where the first target service is a service to be triggered; The service priority of the first target service.

14. A control device comprising: A transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the congestion control method according to any one of claims 1 to 12 when executing the computer program.

15. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps of the method according to any one of claims 1 to 12.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the congestion control method according to any one of claims 1 to 12 are implemented.

Images