Data offloading method, device, and storage medium

Abstract

The present application discloses a data offloading method, a device, and a storage medium. The method comprises: receiving cache status reporting information sent by an RLC component; determining a first air interface time slot for scheduling data to be offloaded corresponding to the cache status reporting information, and in the first air interface time slot, determining first scheduling priorities for scheduling candidate component carriers of said data, wherein the greater the scheduling capability of each candidate component carrier is, the higher the corresponding first scheduling priority is; on the basis of the first scheduling priorities, determining an offloading result of offloading said data to the candidate component carriers for scheduling; and sending the offloading result to the RLC component, so that the RLC component offloads and packetizes said data on the basis of the offloading result.

Description

Data diversion method, device and storage medium

[0001] Related applications

[0002] This application claims priority to Chinese patent application No. 202310747705.9 filed on June 21, 2023, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a data offloading method, device, and storage medium. Background Art

[0004] Carrier aggregation (CA) is the process of aggregating two or more component carriers (CCs) through carrier aggregation technology to support a larger transmission bandwidth. In other words, carrier aggregation can efficiently utilize fragmented spectrum and support a larger transmission bandwidth (that is, a UE that supports carrier aggregation can send and receive data with multiple cells simultaneously, thereby significantly improving the peak rate of a single user).

[0005] In the above process, the accuracy of data diversion is crucial. If the diversion is inaccurate, the data will not be scheduled and transmitted on the air interface in a timely manner, resulting in data backlog, which will ultimately affect the user experience.

[0006] Currently, the most common offload strategy in the industry is to allocate the data to candidate component carriers in proportion (the proportion takes into account the historical traffic and scheduling capabilities of the primary and secondary carriers). However, this offload strategy cannot guarantee that data is scheduled and transmitted on the most appropriate component carrier, making it difficult to reduce packet transmission latency and affecting the user's perceived speed experience.

[0007] Summary of the Invention

[0008] The embodiments of the present application provide a data offloading method, device, and storage medium, aiming to solve the technical problem of uplink and downlink user plane latency.

[0009] The present invention provides a data offloading method, which is applied to an offloading component. The method includes:

[0010] Receive buffer status reporting information sent by the RLC component;

[0011] determining a first air interface timeslot for scheduling the to-be-offloaded data corresponding to the buffer status reporting information, and determining, in the first air interface timeslot, a first scheduling priority of each candidate component carrier for scheduling the to-be-offloaded data, where a greater scheduling capability of each candidate component carrier corresponds to a higher first scheduling priority;

[0012] determining, according to the first scheduling priority, a diversion result of diverting the to-be-diverted data to the candidate component carriers for scheduling;

[0013] The diversion result is sent to the RLC component, so that the RLC component can divert and package the data to be diverted according to the diversion result.

[0014] The present application also provides a data distribution device, the data distribution device comprising:

[0015] A receiving module, configured to receive buffer status reporting information sent by the RLC component;

[0016] a first determining module, configured to determine a first air interface timeslot for scheduling the to-be-offloaded data corresponding to the buffer status reporting information, and determine, in the first air interface timeslot, a first scheduling priority of each candidate component carrier for scheduling the to-be-offloaded data, where a greater scheduling capability of each candidate component carrier corresponds to a higher first scheduling priority;

[0017] a second determining module, configured to determine, according to the first scheduling priority, a diversion result of diverting the to-be-diverted data to the candidate component carriers for scheduling;

[0018] The sending module is used to send the diversion result to the RLC component, so that the RLC component can divert and package the data to be diverted according to the diversion result.

[0019] The present application also provides a data diversion device, which is a physical node device. The data diversion device includes: a memory, a processor, and a program of the data diversion method stored on the memory and capable of running on the processor. When the program of the data diversion method is executed by the processor, the steps of the data diversion method described above can be implemented.

[0020] To achieve the above objectives, the present application also provides a storage medium, on which a data diversion program is stored. When the data diversion program is executed by a processor, the steps of any of the above-mentioned data diversion methods are implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1 is a flow chart of a first embodiment of the data diversion method of the present application;

[0022] FIG2 is a schematic diagram of a detailed flow chart of step S20 in the first embodiment of the data diversion method of the present application;

[0023] FIG3 is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present application;

[0024] FIG4 is a schematic diagram of a general architecture of carrier aggregation involved in the data offload method of the present application;

[0025] FIG5 is a schematic diagram of a frame structure ratio combination of carrier aggregation TDD+TDD involved in the first embodiment of the data offload method of the present application;

[0026] FIG6 is a schematic diagram of candidate component carriers in the first embodiment of the data offloading method of the present application;

[0027] FIG7 is a schematic diagram of the overall process of data diversion by the intelligent diversion component involved in the first embodiment of the data diversion method of the present application;

[0028] FIG8 is a schematic diagram showing the corresponding relationship between specific μ values ​​and SCS involved in the data diversion method of this application;

[0029] FIG9 is a schematic diagram of a first scenario of CA carrier timing configuration involved in the data offloading method of the present application;

[0030] FIG10 is a schematic diagram of a first scenario of the data offloading method of the present application, showing a downlink slot-level data offloading priority sequence;

[0031] FIG11 is an uplink slot-level data offloading priority sequence involved in the first embodiment of the data offloading method of the present application;

[0032] FIG12 is a schematic diagram of the working process of the intelligent diversion component involved in the first embodiment of the data diversion method of the present application;

[0033] FIG13 is a schematic diagram of a second scenario of CA carrier timing configuration involved in the data offloading method of the present application;

[0034] FIG14 is a schematic diagram of a second scenario of the data offloading method of the present application, showing a downlink slot-level data offloading priority sequence;

[0035] FIG15 is a schematic diagram of the uplink slot-level data diversion priority sequence involved in the second scenario of the data diversion method of the present application. DETAILED DESCRIPTION

[0036] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application.

[0037] The present application provides a data offloading method. In a first embodiment of the data offloading method of the present application, referring to FIG1 , the method is applied to a offloading component, and includes:

[0038] Step S10: receiving buffer status reporting information sent by the RLC component;

[0039] Step S20: Determine a first air interface timeslot for scheduling the to-be-offloaded data corresponding to the buffer status reporting information, and determine, in the first air interface timeslot, a first scheduling priority for each candidate component carrier for scheduling the to-be-offloaded data, where a greater scheduling capability of each candidate component carrier corresponds to a higher first scheduling priority.

[0040] Step S30: determining a diversion result of diverting the to-be-diverted data to each candidate component carrier for scheduling according to the first scheduling priority;

[0041] Step S40: Send the diversion result to the RLC component, so that the RLC component can divert and package the data to be diverted according to the diversion result.

[0042] In this embodiment, the corresponding technical terms are first explained:

[0043] CA: Carrier Aggregation, carrier aggregation;

[0044] PCC: Primary Carrier Component, primary carrier;

[0045] SCC: Secondary Carrier Component, auxiliary carrier;

[0046] Slot: time slot;

[0047] BSR: Buffer Status Report, buffer status reporting;

[0048] SCS: sub-carrier space, sub-carrier spacing;

[0049] LCH / LCG: Logical Channel / Logical Channel Group, logical channel / logical channel group;

[0050] RB: Resource Block, resource block.

[0051] In this embodiment, the research and development background is:

[0052] Carrier aggregation (CA) is the process of aggregating two or more component carriers (CCs) through carrier aggregation technology to support a larger transmission bandwidth. In other words, carrier aggregation can efficiently utilize fragmented spectrum and support a larger transmission bandwidth (that is, a UE that supports carrier aggregation can send and receive data with multiple cells simultaneously, thereby significantly improving the peak rate of a single user).

[0053] As an example, the base station selects respective modulation and coding schemes for different aggregated subcarriers according to the difference in link channel quality of different subcarriers.

[0054] As an example, the base station can select separate modulation and coding schemes for different aggregated subcarriers based on the differences in link channel quality between different subcarriers. This is because each component carrier in carrier aggregation (each unit forming carrier aggregation is its component carrier) occupies an independent L1 layer (physical layer) and L2 layer (data link layer). In other words, each component carrier can use independent link adaptation technology to transmit data without affecting each other.

[0055] As an example, the general architecture of carrier aggregation is shown in FIG4 , wherein DRB (Data Radio Bearer) is established only on the primary carrier.

[0056] As an example, as shown in Figure 4, in the related art, the MAC layer of the primary carrier is responsible for distributing data packets evenly, randomly, or proportionally (the proportion takes into account the historical traffic and historical scheduling capabilities of the primary and secondary carriers) to each component carrier for spectrum resource scheduling based on the downlink BSR (Buffer Status Report) sent by the RLC layer of the primary carrier, and sending the distributing results to the RLC layer of the primary carrier for packet processing. The RLC layer distributes the packetized messages to the PHY layer of each component carrier based on the distributing results, and the PHY layer completes the processing.

[0057] As an example, a typical TDD+TDD (carrier aggregation) method is currently used to achieve extremely low-latency service processing, wherein the frame structure ratio combination of the carrier aggregation TDD+TDD is shown in Figure 5 (D in Figure 5 represents a downlink subframe, U in Figure 5 represents an uplink subframe, and S represents an S special subframe). For the downlink data scheduled by the air interface in slot 0 (time slot), since slot 0 is a downlink subframe for both the main carrier and the auxiliary carrier, the data is randomly diverted to any main or auxiliary carrier; for the downlink data scheduled by the air interface in slot 4, since the main carrier of slot 4 is a downlink subframe and the auxiliary carrier is an uplink subframe, the downlink data of slot 4 is diverted to the main carrier, and the uplink data should be diverted to the auxiliary carrier to ensure that the data is scheduled and sent by the air interface in the most timely manner.

[0058] As an example, the above-mentioned offloading strategy cannot guarantee that data is offloaded to the most appropriate component carrier for scheduling and transmission (for downlink data scheduled in slot 0 (time slot) on the air interface, since slot 0 is a downlink subframe for both the primary carrier and the secondary carrier, data offloading is randomly offloaded to any primary or secondary carrier), making it difficult to reduce the data packet transmission delay, thereby affecting the user's perceived experience of the rate.

[0059] In other words, the currently common offload strategy in the industry mainly considers the scheduling capabilities of the primary and secondary carriers for periodic offload. This offload strategy results in insufficient refinement of data offload and cannot guarantee that data is offloaded to the most appropriate component carrier for scheduling and transmission (i.e., it cannot accurately perceive the primary and secondary frame structure configurations and air interface scheduling capabilities at the slot level). This affects the uplink and downlink user experience rate and the uplink and downlink user plane latency, making it difficult to achieve optimal results.

[0060] At present, if the TDD+TDD (carrier aggregation) method is used, it is difficult to achieve extremely low-latency service processing. In order to achieve extremely low or optimal delay, the usual method is based on carrier aggregation PDCP (Packet Data Convergence Protocol) Duplication technology. PDCP duplication is a function of PDCP, which is mainly a mechanism to improve transmission reliability to meet the reliability / delay requirements of URLLC scenarios. Specifically, when the signal conditions are relatively poor, the network side can configure PDCP duplication to send the same PDCP data through multiple RLCs, and achieve consistent low latency and reliability through repeated transmission. This method will cause a huge waste of spectrum resources and limit the capacity supported by the system. It is not suitable for scenarios with high capacity requirements.

[0061] In this embodiment, based on the slot-level data offload priority sequence and related generation rules, it is possible to avoid wasting spectrum resources and achieve extremely low-latency service processing.

[0062] As an example, the MAC layer of the primary carrier is responsible for offloading data packets to each component carrier for spectrum resource scheduling (determining the first scheduling priority of each candidate component carrier) based on the size of the downlink BSR (Buffer Status Report) sent by the RLC layer of the primary carrier, and sending the offloading result to the RLC layer of the primary carrier for packet processing. The RLC layer distributes the packetized message to the PHY layer of each component carrier for processing based on the offloading result and completes the sending.

[0063] As an example, for the downlink, the MAC layer of the primary carrier is responsible for offloading data packets to each component carrier for downlink spectrum resource scheduling (determining the first scheduling priority of each candidate component carrier) based on the size of the downlink BSR (Buffer Status Report) sent by the RLC layer of the primary carrier, and sending the downlink offload result to the RLC layer of the primary carrier for packet processing. The RLC layer distributes the packetized message to the PHY layer of each component carrier for processing based on the offload result, and completes the downlink transmission over the air interface.

[0064] For the uplink, the MAC layer of the primary carrier is responsible for offloading data packets to each component carrier for uplink spectrum resource scheduling (determining the first scheduling priority of each candidate component carrier) based on the uplink BSR size issued by the primary carrier's RLC layer. Based on the air interface resource authorization obtained by the terminal from the base station, each component carrier then sends the uplink data packets to the RLC layer of the primary carrier for aggregation and packetization.

[0065] As an example, FIG7 shows a schematic diagram of the overall process of the intelligent diversion component diversion, wherein the diversion process includes:

[0066] Step 1: The MAC layer intelligent offload component of the primary carrier is responsible for slot-level offload of the primary and secondary carriers for each CA (carrier aggregation) user. The intelligent offload component receives the data BSR transmitted by the primary carrier user from the RLC layer;

[0067] Step 2: The intelligent offload component is responsible for generating or obtaining a slot-level offload priority sequence for a CA (carrier aggregation) configuration combination, interacting and negotiating scheduling capabilities with the resource scheduling component of each component carrier, and distributing the BSR to each component carrier according to the offload priority.

[0068] Step 3: Notify each component carrier of the user's offload result in the slot, completing slot-level scheduling and resource allocation;

[0069] Step 4: The RLC layer of the primary carrier is notified of the user's traffic offload result for that slot. The RLC layer of the primary carrier is responsible for packetizing the uplink and downlink data for that slot. The difference between uplink and downlink packetization is that in the downlink, the RLC completes downlink packetization based on the traffic offload BSR of each component carrier, distributes it to the physical layer of each component carrier for processing, and then transmits it over the air interface. In the uplink, each component carrier completes uplink transmission in the corresponding slot based on the uplink traffic offload BSR and, through uplink air interface authorization, the UE completes uplink transmission. The RLC layer of the base station's primary carrier receives the uplink data packets from each component carrier, completes uplink packetization, and transmits it to the PDCP layer.

[0070] The specific steps are as follows:

[0071] Step S10: receiving buffer status reporting information sent by the RLC component;

[0072] As an example, it is applied to the diversion component of base station measurement;

[0073] As an example, the buffer status reporting information sent by the RLC component is received through the MAC layer of the primary carrier;

[0074] As an example, the intelligent offload component of the primary carrier MAC layer receives the buffer status reporting information sent by the RLC component;

[0075] As an example, the intelligent offload component may interact and negotiate scheduling capabilities with the resource scheduling component of each component carrier.

[0076] As an example, the intelligent offloading component offloads the scheduling capabilities of corresponding candidate component carriers (including the slot level of the primary and secondary carriers) for each CA (carrier aggregation) user.

[0077] As an example, the intelligent offloading component also performs offloading work of the scheduling capability of each candidate component carrier (including the slot level of the primary and secondary carriers) for non-CA (carrier aggregation) users.

[0078] The following specifically describes the work of the intelligent offloading component offloading the scheduling capability (slot level of primary and secondary carriers) of each candidate component carrier for each CA (carrier aggregation) user as an example.

[0079] As an example, the intelligent offload component receives BSR data (buffer status reporting information) transmitted by the primary carrier user from the RLC layer.

[0080] As an example, BSR data is not substantial data that needs to be split.

[0081] As an example, BSR data carries information on scheduling resource requirements.

[0082] As an example, the BSR data carries the required scheduling resources and the data priority of each user, etc., which are not specifically limited.

[0083] As an example, the BSR data includes uplink BSR data, or the BSR data includes downlink BSR data.

[0084] Step S20: Determine a first air interface timeslot for scheduling the to-be-offloaded data corresponding to the buffer status reporting information, and determine, in the first air interface timeslot, a first scheduling priority for each candidate component carrier for scheduling the to-be-offloaded data, where a greater scheduling capability of each candidate component carrier corresponds to a higher first scheduling priority.

[0085] As an example, there may be two or more candidate component carriers, as shown in FIG6 .

[0086] As an example, the intelligent offloading component determines a first air interface timeslot for scheduling the to-be-offloaded data corresponding to the cache status reporting information.

[0087] As an example, the intelligent diversion component determines the first air interface time slot for scheduling the data to be diverted corresponding to the cache status reporting information based on a preset algorithm for determining the air interface time slot (for example, by reading whether there is an occupied identifier in the time slot to determine the air interface time slot).

[0088] As an example, the intelligent offload component determines, in the first air interface timeslot (such as slot 0), a first scheduling priority of each candidate component carrier for scheduling the data to be offloaded. The greater the scheduling capability of each candidate component carrier, the higher the corresponding first scheduling priority.

[0089] As an example, the intelligent offload component determines, in the first air interface timeslot (such as slot 0), based on a pre-stored first scheduling priority, a first scheduling priority (most frequently used) of each candidate component carrier for scheduling the data to be offloaded;

[0090] That is, at the scheduling start time of slot n, the generated uplink and downlink scheduling candidate component carriers of slot n collectively carry the corresponding offload priority.

[0091] As an example, the scheduling start time of air interface slot n may be a certain time ahead of air interface slot n (therefore, the priorities of different component carriers may be determined first, and then scheduling may be performed based on the priorities to avoid delay).

[0092] As an example, based on the first scheduling priority calculated or determined in real time, the first scheduling priority of each candidate component carrier for scheduling the to-be-offloaded data is determined.

[0093] As an example, the greater the scheduling capability of each candidate component carrier, the higher the corresponding first scheduling priority.

[0094] As an example, candidate component carriers with higher priorities are allocated to the data to be offloaded first, and candidate component carriers with lower priorities are allocated later, so as to reduce the delay.

[0095] As an example, for a certain slot n, activated CA users and non-CA users having BSR in this slot n are summarized.

[0096] As an example, in slot n, there are BSR-activated CA users and non-CA users, and the corresponding data that needs to be scheduled is the corresponding data to be offloaded.

[0097] As an example, it is necessary to first determine the priority of the LCH / LCG (logical channel / logical channel group) of all users (including non-CA users and CA users) participating in the scheduling, and then sort the LCH / LCG (logical channel / logical channel group) of all users (including non-CA users and CA users) according to their priority, and then allocate spectrum resources RB (resource block) according to the sorting results of LCH / LCG.

[0098] After determining the allocation of spectrum resources RB (resource blocks), it is possible to determine which activated CA users and non-CA users need to be allocated in a certain slot n (slot n needs to be a determined air interface timeslot).

[0099] As an example, if the data to be offloaded is downlink data, for a certain slot n, all activated CA users and non-CA users with downlink BSR in the slot n are summarized (to determine the data to be offloaded).

[0100] As an example, if the data to be offloaded is uplink data, for a certain slot n, all activated CA users and non-CA users with uplink BSR in the slot n are summarized (to determine the data to be offloaded).

[0101] As an example, the data to be distributed also has a priority. Therefore, a carrier with the highest priority needs to be preferentially allocated to the data to be distributed corresponding to the user with the highest priority.

[0102] As an example, slot n is an air interface time slot that needs to be scheduled. The data to be diverted includes a, b, and c data, and the priorities of a, b, and c data decrease step by step. Then slot n is first allocated to a data, and then allocated to b and c data step by step.

[0103] As an example, the first scheduling priority is determined based on a preset uplink and downlink time slot level splitting priority sequence, the uplink and downlink time slot level splitting priority sequence is determined based on configuration information of each component carrier, and the configuration information is associated with the scheduling capability.

[0104] As an example, for a CA configuration combination (carrier aggregation configuration combination), the configuration information of each component carrier is obtained, including the frame structure ratio of each component carrier, the uplink and downlink combined bandwidth, the symbol-level scheduling configuration, such as the mini-slot configuration information, etc. The configuration information is associated with the scheduling capability.

[0105] Step 2: Generate uplink and downlink slot-level data offload priority sequences based on the configuration information of the component carriers in the CA combination, as shown in Figure 6.

[0106] As an example, in a CA combination, when the SCS (subcarrier spacing) of each component carrier is different, resulting in different slot lengths, the slot of the carrier with the largest SCS (subcarrier spacing) μ value is used as the granularity. According to the 3GPP standard, the specific correspondence between the μ value and the SCS is shown in Figure 8 (the table also involves the number of time slots corresponding to each subframe).

[0107] 2 , the step of determining, in the first air interface timeslot, a first scheduling priority of each candidate component carrier for scheduling the data to be offloaded includes:

[0108] Step S21, determining a candidate component carrier for scheduling the data to be offloaded;

[0109] In this embodiment, before determining the first scheduling priority, candidate component carriers need to be determined first. That is, candidate component carriers for scheduling the data to be offloaded (uplink data or downlink data) are first determined. As shown in FIG5 (D represents a downlink subframe, U represents an uplink subframe, and S represents a special subframe), for downlink data scheduled by the air interface in slot 0 (time slot), since slot 0 is a downlink subframe (D) for both the primary carrier and the secondary carrier, data offload is randomly offloaded to any primary or secondary carrier (in slot 0, any primary or secondary carrier is D). For downlink data scheduled by the air interface in slot 4, since the primary carrier in slot 4 is a downlink subframe (D) and the secondary carrier is an uplink subframe (U), the downlink data in slot 4 is offloaded to the primary carrier (PCC).

[0110] Step S22: In the first air interface timeslot, determine the initial scheduling priority of each candidate component carrier based on the last symbol index value of the fastest available carrier resource of each candidate component carrier, where a smaller symbol index value corresponds to a higher initial scheduling priority.

[0111] In the first air interface timeslot, an initial scheduling priority of each candidate component carrier is determined based on a last symbol index value of the fastest available carrier resource of each candidate component carrier (the fastest available is determined according to the order in which slot n is divided in the resource block, or according to a preset order in which slot n is mobilized). A smaller symbol index value corresponds to a higher initial scheduling priority (a preset association exists between the symbol index value and the scheduling priority).

[0112] As an example, component carriers corresponding to slot n and having downlink schedulable symbols are listed as downlink candidate component carriers. In the first air interface timeslot, an initial scheduling priority of each candidate component carrier is determined based on the last symbol index value of the fastest available carrier resource of each candidate component carrier (in the downlink candidate component carrier set, a preliminary sorting is performed based on the last symbol index value of the fastest available downlink resource in the corresponding slot; a smaller index value indicates a higher priority for the component carrier).

[0113] As an example, component carriers corresponding to slot n and having uplink schedulable symbols are listed as uplink candidate component carriers. In the first air interface timeslot, an initial scheduling priority of each candidate component carrier is determined based on the last symbol index value of the fastest available carrier resource of each candidate component carrier (in the uplink candidate component carrier set, a preliminary sorting is performed based on the last symbol index value of the fastest available uplink resource in the corresponding slot; a smaller index value indicates a higher priority for the component carrier).

[0114] After the step of determining the initial scheduling priority of each candidate component carrier based on the last symbol index value of the fastest available carrier resource of each candidate component carrier, the method further includes:

[0115] Step B1: If the last symbol index value of different candidate component carriers is the same, further sort the candidate component carriers according to available spectrum resources to ultimately obtain the first scheduling priority of each candidate component carrier;

[0116] The more available spectrum resources there are, the higher the scheduling priority of the corresponding candidate component carrier is. The available spectrum resources are associated with spectrum bandwidth, the proportion of available symbols, and the historical utilization rate of resource blocks.

[0117] As an example, the more available spectrum resources there are, the higher the scheduling priority of the corresponding candidate component carrier. Therefore, if the last symbol index value of different candidate component carriers (candidate component carriers) is the same, the candidate component carriers are further sorted according to the available spectrum resources to ultimately obtain the first scheduling priority of each candidate component carrier.

[0118] As an example, candidate component carriers with the same priority are further sorted according to uplink available spectrum resources, and the more available spectrum resources, the higher the priority.

[0119] As an example, candidate component carriers with the same priority are further sorted according to available downlink spectrum resources. The more available spectrum resources, the higher the priority.

[0120] As an example, if the candidate component carrier is a candidate component carrier for scheduling uplink data, the available spectrum resources are associated with the uplink spectrum bandwidth, the proportion of available symbols, and the historical utilization rate of resource blocks.

[0121] As an example, uplink available spectrum resources = uplink spectrum bandwidth * proportion of uplink available symbols * (1-uplink PRB historical utilization rate).

[0122] As an example, the uplink PRB historical utilization is the historical uplink PRB occupancy rate of the corresponding component carrier within a certain period;

[0123] As an example, the proportion of uplink available symbols is the ratio of the number of available consecutive symbols of the fastest available uplink resource of slot n to the total number of uplink symbols.

[0124] As an example, if the candidate component carrier is a candidate component carrier for scheduling downlink data, the available spectrum resources are associated with the downlink spectrum bandwidth, the proportion of available symbols, and the historical utilization rate of resource blocks.

[0125] As an example, downlink available spectrum resources = downlink spectrum bandwidth * downlink available symbol ratio * (1-downlink PRB historical utilization ratio);

[0126] As an example, the downlink PRB historical utilization rate is the historical downlink PRB occupancy rate of the component carrier within a certain period;

[0127] As an example, the proportion of downlink available symbols is the ratio of the number of available consecutive symbols of the fastest available downlink resource of slot n to the total number of downlink symbols.

[0128] Step S30: determining a diversion result of diverting the to-be-diverted data to each candidate component carrier for scheduling according to the first scheduling priority;

[0129] After determining the first scheduling priority, a diversion result of diverting the to-be-diverted data to each candidate component carrier for scheduling is determined according to the first scheduling priority.

[0130] As an example, the diversion result is a plan for determining how to schedule the data to be diverted.

[0131] As an example, the diversion result may be:

[0132] For uplink slot 8, PCC has a higher priority, so PCC is used first to schedule uplink data.

[0133] For downlink slot 2, the downlink priority SCC1 is higher than that of PCC, so SCC1 is used first to schedule downlink data.

[0134] Step S40: Send the diversion result to the RLC component, so that the RLC component can divert and package the data to be diverted according to the diversion result.

[0135] As an example, the diversion result is a diversion plan, not that the diversion has actually been completed. Therefore, in this embodiment, after determining the diversion result, the diversion result is sent to the RLC component so that the RLC component can divert and package the data to be diverted according to the diversion result.

[0136] As an example, as shown in FIG9 , a whole embodiment of data offloading (involving CA carrier timing configuration) is provided, and the specific steps involved include:

[0137] Step 1: Obtain configuration information for each candidate component carrier, including:

[0138] PCC (primary carrier): TDD (time division duplex) 100M bandwidth, 30kHz SCS (subcarrier spacing), frame structure is DDDDDDDSUU, and the corresponding μ value is 2;

[0139] For the PCC (primary carrier), symbols 2 and 3 of DL (downlink) slot 3 configure a downlink mini-slot;

[0140] The DL (downlink): GAP (interval between uplink and downlink symbols): UL (uplink) symbol ratio of S slot is 2:4:8; among them, symbols 2 and 3 of UL (uplink) slot 8 configure an uplink mini-slot.

[0141] SCC1 (secondary carrier): TDD 60M bandwidth, 30kHz SCS, frame structure DDDDDDDSUU, corresponding μ value is 2;

[0142] For SCC1 (secondary carrier), the symbol ratio of DL:GAP:UL in S slot is 6:4:4; symbols 10 and 11 of UL slot 9 configure an uplink mini-slot.

[0143] SCC2: TDD 40M bandwidth, 30kHz SCS, frame structure is UUUDSUUUDS, and the corresponding μ value is 2;

[0144] For SCC1 (secondary carrier), the symbol ratio of DL:GAP:UL of the two S slots is 10:2:2; symbols 2 and 3 of DL slot3 configure a downlink mini-slot.

[0145] The SCS of the three component carriers is 30 kHz, and the corresponding μ values ​​are all 1, so the total length of the table is 1 frame (10 ms) / 2=5 ms. Each corresponding slot occupies 0.5 ms, and there are a total of 10 slots.

[0146] Step 2: Generate uplink and downlink slot-level data offload priority sequences based on the configuration information of the component carriers in the corresponding CA combination, as shown in Figure 10 (downlink slot-level data offload priority sequence) and Figure 11 (uplink slot-level data offload priority sequence).

[0147] For downlink slot 2, the initial sorting priority of PCC and SCC1 is the same. As an example,

[0148] PCC downlink available spectrum resources = downlink spectrum bandwidth * downlink available symbol ratio * (1 - downlink PRB historical utilization rate) = 100 * 1 * (1 - 60%) = 40;

[0149] SCC1 downlink available spectrum resources = downlink spectrum bandwidth * downlink available symbol ratio * (1 - downlink PRB historical utilization rate) = 60 * 1 * (1 - 20%) = 48;

[0150] Therefore, for slot 2, the downlink priority of SCC1 is higher than that of PCC.

[0151] As an example, for downlink slot 3, PCC and SCC2 both have downlink mini-slot configurations on symbols 2 and 3. In the initial sorting, PCC and SCC2 have the same priority.

[0152] PCC downlink available spectrum resources = downlink spectrum bandwidth * downlink available symbol ratio * (1 - downlink PRB historical utilization rate) = 100 * (2 / 14) * (1 - 40%) = 8.57;

[0153] SCC2 downlink available spectrum resources = downlink spectrum bandwidth * downlink available symbol ratio * (1 - downlink PRB historical utilization rate) = 60 * (2 / 14) * (1 - 50%) = 4.28;

[0154] Therefore, for slot 3, the downlink priority of PCC is higher than that of SCC2.

[0155] For uplink slot 8, PCC has a 2-symbol mini-slot. The last symbol index of the fastest available uplink resource is 3, while the last symbol index of the fastest available uplink resource of SCC1 is 13. Therefore, for uplink slot 8, PCC has a higher priority. The same applies to slot 9.

[0156] Step 3: After determining the priority sequence, the intelligent offload component implements multi-carrier polling scheduling and completes uplink and downlink data offload according to the uplink and downlink slot-level data offload priority sequence.

[0157] The present application provides a data offloading method, apparatus, device, and storage medium. Compared to the prior art method of offloading data to be offloaded to candidate component carriers for scheduling and distribution in proportion, which results in extended data packet transmission time and reduced user perceived rate experience, the present application comprises receiving buffer status report information sent by an RLC component; determining a first air interface timeslot for scheduling the data to be offloaded corresponding to the buffer status report information; determining, in the first air interface timeslot, a first scheduling priority for each candidate component carrier for scheduling the data to be offloaded, wherein a greater scheduling capability of each candidate component carrier corresponds to a higher first scheduling priority; determining, based on the first scheduling priority, a offloading result for offloading the data to be offloaded to each candidate component carrier for scheduling; and sending the offloading result to the RLC component, so that the RLC component offloads and packages the data to be offloaded according to the offloading result.

[0158] In the present application, rather than distributing the data to be distributed proportionally, a first air interface timeslot for scheduling the data to be distributed is first determined based on buffer status reporting information (data demand) (avoiding allocation to component carriers that currently do not have air interface timeslots). Then, within this first air interface timeslot, the data to be distributed is distributed according to the first scheduling priority of each candidate component carrier (the greater the scheduling capability of each candidate component carrier, the higher the corresponding first scheduling priority, thus minimizing delay and maximizing speed). Because the first scheduling priority accurately perceives the scheduling capability at the timeslot level, it ensures that data is distributed to the most appropriate component carrier for scheduling and transmission (rather than randomly allocating data to component carriers, or even to component carriers that currently do not have air interface timeslots). Therefore, based on the first scheduling priority, a distribution result is determined for distributing the data to be distributed to each candidate component carrier for scheduling. This distribution result is then transmitted to the RLC component, which then distributes and packets the data to be distributed based on the distribution result. This reduces data packet transmission latency and improves the user's perceived speed experience.

[0159] Based on the first embodiment of the present application, another embodiment of the present application is provided. In this embodiment, the step of determining, based on the first scheduling priority, a diversion result of diverting the to-be-diverted data to each candidate component carrier for scheduling includes:

[0160] Step C1: determining, according to the first scheduling priority, a first offloading result of preferentially offloading the to-be-offloaded data to the candidate component carrier with the highest priority for scheduling;

[0161] Step C2: If undivided data still exists among the data to be diverted in the first diversion result, determine, according to the first scheduling priority, to divert the undivided first data to other candidate component carriers in a round-robin manner until the diversion of the data to be diverted is completed or a second diversion result is obtained in which all candidate component carriers are polled to complete the diversion.

[0162] As an example, as shown in FIG12 , the data to be offloaded is first preferentially offloaded to the candidate component carrier with the highest priority for scheduling. If there is still unoffloaded data in the data to be offloaded in the first offloading result, it is determined that the unoffloaded first data is offloaded to other candidate component carriers in a round-robin manner according to the first scheduling priority (no need to re-determine the scheduling priority) until the offloading of the data to be offloaded is completed or the second offloading result is obtained in which all candidate component carriers are polled and completed.

[0163] As an example, after the data to be offloaded is preferentially offloaded to the candidate component carrier (PCC) with the highest priority for scheduling, there is still unoffloaded data. According to the first scheduling priority (no need to re-determine the scheduling priority), it is determined to poll and offload the unoffloaded first data to other candidate component carriers (such as SCC1, where the priority of SCC1 is greater than that of SCC2) until the offloading of the data to be offloaded is completed (if there is still unoffloaded data after offloading to SCC1, it is offloaded to SCC2) or the second offloading result of polling all candidate component carriers is completed.

[0164] After the step of determining to offload the unoffloaded first data to other candidate component carriers by polling until offloading of the to-be-offloaded data is completed or polling of all candidate component carriers completes the second offloading result, the method includes:

[0165] Step B1: If the first data has not yet been split, determine a second air interface timeslot for the second data that has not yet been split;

[0166] Step B2: determining a second scheduling priority for scheduling the second data in the second air interface timeslot;

[0167] Step B3: Determine, according to the second scheduling priority, a third offloading result of offloading the second data to each candidate component carrier for scheduling.

[0168] As an example, if the first data is still not offloaded after polling and offloading to other candidate component carriers, the second air interface time slot corresponding to the unoffloaded second data is required (such as the second air interface time slot is slot1, the second air interface time slot is slot3), and the second scheduling priority for scheduling the second data is determined (for example, for slot1, the downlink priority (first scheduling priority) PCC is higher than SCC2, and for slot3, the downlink priority (second scheduling priority) SCC2 may be higher than PCC).

[0169] A third offloading result of offloading the second data to the candidate component carriers for scheduling is determined according to the second scheduling priority (until offloading of the data to be offloaded is completed or polling of all candidate component carriers is completed).

[0170] That is, in this embodiment, all activated CA users with (uplink or downlink) BSRs in slot n are aggregated and participate in unified (uplink or downlink) scheduling and resource allocation together with non-CA users on the (uplink or downlink) highest priority carrier.

[0171] After scheduling of the highest priority carrier (uplink or downlink) is completed, the BSR size (uplink or downlink) of scheduled CA users is updated. Users whose BSRs have been cleared do not participate in scheduling of the next-level carrier. Users whose BSRs have not been cleared continue to participate in unified (uplink or downlink) scheduling and resource allocation on the next-priority carrier together with non-CA users.

[0172] Correspondingly, for each candidate component carrier in the current slot, the offloading result of each candidate component carrier in the current slot is determined and packetized through the RLC layer.

[0173] After polling all candidate component carriers, if the BSR has not yet scheduled all users, it will continue to participate in the offloading and scheduling of the next slot.

[0174] As an example, as shown in FIG13 , a whole embodiment of data offloading (involving CA carrier timing configuration) is provided, and the specific steps involved include:

[0175] Step 1: Obtain configuration information for each component carrier, including:

[0176] PCC: FDD 40M bandwidth, 15kHz SCS, the corresponding μ value is 1;

[0177] Symbols 2 and 3 of DL slot 1 of the PCC configure a downlink mini-slot; symbol 4 of UL slot 4 configures an uplink mini-slot;

[0178] SCC1: TDD 100M bandwidth, 30kHz SCS, frame structure DDDDDDDSUU, corresponding μ value is 2;

[0179] The symbol ratio of DL:GAP:UL in S slot is 2:4:8; symbols 2 and 3 in UL slot 8 configure an uplink mini-slot.

[0180] SCC1 has the largest μ value, so the total length of the table is 1frame(10ms) / 2=5ms, and each corresponding slot occupies 0.5ms, with a total of 10 slots.

[0181] Step 2: Based on the configuration information of the component carriers of the CA combination, generate the uplink and downlink slot-level data offload priority sequences, as shown in Figures 14 and 15:

[0182] For downlink slot 7, the SCC is an S special subframe, the last symbol index value of the fastest available downlink resource is 1, and the last symbol index value of the fastest available downlink resource of the PCC is 13, so for downlink slot 7, the SCC has a higher priority.

[0183] For uplink slot 9, the PCC has a mini-slot with 1 symbol (the symbol index values ​​mapped to slot 9 of SCC1 are 2 and 3). Therefore, the last symbol index value of the fastest available uplink resource is 3, while the last symbol index value of the fastest available uplink resource of SCC1 is 13. Therefore, for uplink slot 9, the PCC has a higher priority.

[0184] Step 3: The intelligent offload component implements multi-carrier polling scheduling and completes uplink and downlink data offload according to the uplink and downlink slot-level data offload priority sequence.

[0185] In this embodiment, based on the first scheduling priority, a first diversion result is determined to preferentially divert the to-be-diverted data to the candidate component carrier with the highest priority for scheduling. If undiverted data still exists in the to-be-diverted data in the first diversion result, a second diversion result is determined to round-robin the undiverted first data to other candidate component carriers according to the first scheduling priority until the diversion of the to-be-diverted data is completed or all candidate component carriers are polled. In this embodiment, after the scheduling of the high-priority candidate component carrier is completed, the user's BSR is updated, and the user continues to participate in the scheduling of the lower-priority carrier until all candidate component carriers are polled. If the user's BSR is still not fully scheduled, the BSR is updated to continue participating in the scheduling of the next slot.

[0186] Based on the first and second embodiments of the present application, another embodiment of the present application is provided. In this embodiment, the data offloading method is applied to a client and includes:

[0187] Step D1: the buffer status reporting information includes uplink buffer status reporting information. When the buffer status reporting information is uplink buffer status reporting information, each candidate component carrier is an uplink candidate scheduling carrier, and the offload component is a terminal offload component.

[0188] In this embodiment, the intelligent offloading method is applicable not only to the base station side but also to the terminal side. That is, on the terminal side, intelligent uplink offloading can also be implemented by using the corresponding slot-level data offloading priority sequence. That is, when multiple candidate component carriers have uplink grants at the same time, multi-carrier polling scheduling can be performed according to the priority sequence to implement intelligent uplink offloading.

[0189] That is, when the buffer status reporting information is uplink buffer status reporting information, each candidate component carrier is an uplink candidate scheduling carrier, and the offload component is a offload component of the terminal.

[0190] Before the step of determining the first scheduling priority of each candidate component carrier for scheduling the data to be offloaded, the method includes:

[0191] Step E1: receiving authorization information sent by a base station, wherein the authorization information includes an uplink and downlink time slot level splitting priority sequence;

[0192] The step of determining a first scheduling priority of each candidate component carrier for scheduling the data to be offloaded includes:

[0193] Based on the uplink and downlink timeslot-level offloading priority sequence, a first scheduling priority of each candidate component carrier for scheduling the to-be-offloaded data is determined.

[0194] In this embodiment, the difference between uplink and downlink packetization is that, in the downlink, RLC completes downlink packetization according to the offload BSR of each component carrier and distributes it to the physical layer of each component carrier, and then completes air interface transmission after corresponding physical layer processing.

[0195] If the corresponding uplink air interface authorization is obtained, the UE completes uplink transmission in the corresponding slot (each candidate component carrier according to the uplink traffic splitting BSR). The base station's primary carrier RLC layer receives the uplink data messages of each candidate component carrier, completes the uplink packetization and sends it to the PDCP layer.

[0196] Based on the first embodiment of the present application, another embodiment of the present application is provided, which is applied to URLLC and eMBB multi-frequency networking scenarios.

[0197] In this embodiment, it can be applied to URLLC (ultra-reliable low-latency communication) in vertical industries, and extremely low-latency services can be achieved through carrier aggregation, that is, by configuring service priorities, optimal user plane latency can be achieved; in this embodiment, it can also be applied to eMBB multi-frequency networking scenarios, especially in large-capacity scenarios. This method can effectively reduce the data packet sending delay and improve the user's uplink and downlink perceived rate.

[0198] Refer to Figure 3, which is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present application.

[0199] As shown in FIG3 , the data distribution device may include: a processor 1001 , a memory 1005 , and a communication bus 1002 . The communication bus 1002 is used to implement connection and communication between the processor 1001 and the memory 1005 .

[0200] As an example, the data diversion device may also include a user interface, a network interface, a camera, an RF (Radio Frequency) circuit, a sensor, a WiFi module, and the like. The user interface may include a display screen and an input submodule such as a keyboard. The user interface may also include a standard wired interface and a wireless interface. The network interface may include a standard wired interface and a wireless interface (such as a WiFi interface).

[0201] Those skilled in the art will understand that the data splitting device structure shown in FIG3 does not constitute a limitation on the data splitting device, and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

[0202] As shown in Figure 3, memory 1005, a storage medium, may include an operating system, a network communication module, and a data diversion program. The operating system is a program that manages and controls the hardware and software resources of the data diversion device and supports the operation of the data diversion program and other software and / or programs. The network communication module is used to enable communication between the various components within memory 1005, as well as communication with other hardware and software in the data diversion system.

[0203] In the data offloading device shown in FIG3 , the processor 1001 is configured to execute the data offloading program stored in the memory 1005 to implement the steps of any of the above-mentioned data offloading methods.

[0204] The specific implementation of the data diversion device of the present application is basically the same as the various embodiments of the above-mentioned data diversion method, and will not be repeated here.

[0205] The present application also provides a data diversion device, which is applied to a diversion component. The data diversion device includes:

[0206] A receiving module, configured to receive buffer status reporting information sent by the RLC component;

[0207] a first determining module, configured to determine a first air interface timeslot for scheduling the to-be-offloaded data corresponding to the buffer status reporting information, and determine, in the first air interface timeslot, a first scheduling priority of each candidate component carrier for scheduling the to-be-offloaded data, where a greater scheduling capability of each candidate component carrier corresponds to a higher first scheduling priority;

[0208] a second determining module, configured to determine, according to the first scheduling priority, a diversion result of diverting the to-be-diverted data to the candidate component carriers for scheduling;

[0209] The sending module is used to send the diversion result to the RLC component, so that the RLC component can divert and package the data to be diverted according to the diversion result.

[0210] In a possible implementation of the present application, the first scheduling priority is determined based on a preset uplink and downlink timeslot-level splitting priority sequence, the uplink and downlink timeslot-level splitting priority sequence is determined based on configuration information of each component carrier, and the configuration information is associated with the scheduling capability.

[0211] In a possible implementation manner of the present application, the first determining module is configured to implement:

[0212] determining a candidate component carrier for scheduling the data to be offloaded;

[0213] In the first air interface timeslot, an initial scheduling priority of each candidate component carrier is determined based on a last symbol index value of the fastest available carrier resource of each candidate component carrier, where a smaller symbol index value corresponds to a higher initial scheduling priority.

[0214] In a possible implementation manner of the present application, the first determining module is further configured to implement:

[0215] If the last symbol index values ​​of different candidate component carriers are the same, further sorting the candidate component carriers according to available spectrum resources to ultimately obtain the first scheduling priority of each candidate component carrier;

[0216] The more available spectrum resources there are, the higher the scheduling priority of the corresponding candidate component carrier is. The available spectrum resources are associated with spectrum bandwidth, the proportion of available symbols, and the historical utilization rate of resource blocks.

[0217] In a possible implementation manner of the present application, the second determining module is configured to implement:

[0218] determining, according to the first scheduling priority, a first offloading result of preferentially offloading the to-be-offloaded data to the candidate component carrier with the highest priority for scheduling;

[0219] If undivided data still exists among the data to be diverted in the first diversion result, determining, according to the first scheduling priority, to divert the undivided first data to other candidate component carriers in a round-robin manner until diversion of the data to be diverted is completed or a second diversion result is obtained in which polling of all candidate component carriers is completed.

[0220] In a possible implementation manner of the present application, the second determining module is further configured to implement:

[0221] If the first data has not yet been split, determining a second air interface timeslot for the second data that has not been split;

[0222] In the second air interface timeslot, determining a second scheduling priority for scheduling the second data;

[0223] A third offloading result of offloading the second data to the candidate component carriers for scheduling is determined according to the second scheduling priority.

[0224] In a possible implementation manner of the present application, the buffer status reporting information includes uplink buffer status reporting information. When the buffer status reporting information is uplink buffer status reporting information, each of the candidate component carriers is an uplink candidate scheduling carrier, and the offload component is a offload component of a terminal.

[0225] In a possible implementation manner of the present application, the buffer status reporting information includes downlink buffer status reporting information. When the buffer status reporting information is downlink buffer status reporting information, each of the candidate component carriers is a downlink candidate scheduling carrier, and the offload component is a offload component of a base station.

[0226] In a possible implementation of the present application, it is applied to URLLC and eMBB multi-frequency networking scenarios.

[0227] The specific implementation of the data diversion device of the present application is basically the same as the various embodiments of the above-mentioned data diversion method, and will not be repeated here.

[0228] An embodiment of the present application provides a storage medium, and the storage medium stores one or more programs, and the one or more programs can also be executed by one or more processors to implement the steps of any of the above-mentioned data diversion methods.

[0229] The specific implementation of the storage medium of the present application is basically the same as the embodiments of the above-mentioned data offloading method, and will not be repeated here.

[0230] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned data diversion method when executed by a processor.

[0231] The specific implementation of the computer program product of the present application is basically the same as the various embodiments of the above-mentioned data diversion method, and will not be repeated here.

[0232] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0233] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0234] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus hardware platform, or by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0235] The above are merely optional embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A data diversion method, applied to a diversion component, wherein: The method comprises: Receiving buffer status reporting information sent by the RLC component; determining a first air interface timeslot for scheduling the to-be-offloaded data corresponding to the buffer status reporting information, and determining, in the first air interface timeslot, a first scheduling priority of each candidate component carrier for scheduling the to-be-offloaded data, wherein a greater scheduling capability of each candidate component carrier has a higher corresponding first scheduling priority; Determine, according to the first scheduling priority, a diversion result of diverting the to-be-diverted data to each of the candidate component carriers for scheduling; The diversion result is sent to the RLC component, so that the RLC component performs diversion and packetization on the data to be diverted according to the diversion result.

2. The data splitting method according to claim 1, wherein: The first scheduling priority is determined based on a preset uplink and downlink time slot level splitting priority sequence, the uplink and downlink time slot level splitting priority sequence is determined based on configuration information of each component carrier, and the configuration information is associated with the scheduling capability.

3. The data splitting method according to claim 2, wherein: The step of determining, in the first air interface timeslot, a first scheduling priority of each candidate component carrier for scheduling the data to be offloaded comprises: Determining a candidate component carrier for scheduling the data to be offloaded; In the first air interface time slot, the initial scheduling priority of each candidate component carrier is determined based on the last symbol index value of the fastest available carrier resource of each candidate component carrier, wherein the smaller the symbol index value is, the higher the corresponding initial scheduling priority is.

4. The data distribution method according to claim 3, wherein: After the step of determining the initial scheduling priority of each candidate component carrier based on the last symbol index value of the fastest available carrier resource of each candidate component carrier, the method further includes: If the last symbol index values ​​of different candidate component carriers are the same, further sorting the candidate component carriers according to available spectrum resources to finally obtain the first scheduling priority of each candidate component carrier; The more available spectrum resources there are, the higher the scheduling priority of the corresponding candidate component carrier is, and the available spectrum resources are associated with the spectrum bandwidth, the proportion of available symbols, and the historical utilization rate of resource blocks.

5. The data distribution method according to claim 1, wherein: The step of determining, according to the first scheduling priority, a diversion result of diverting the to-be-diverted data to each candidate component carrier for scheduling includes: Determine, according to the first scheduling priority, a first offloading result of preferentially offloading the to-be-offloaded data to a candidate component carrier with a highest priority for scheduling; If there is still undivided data in the data to be diverted in the first diversion result, determine to divert the undivided first data to other candidate component carriers in round-robin fashion according to the first scheduling priority until the diversion of the data to be diverted is completed or a second diversion result is reached in which polling of all candidate component carriers is completed.

6. The data distribution method according to claim 5, wherein: The step of determining to distribute the undivided first data to other candidate component carriers by polling until the distribution of the data to be distributed is completed or the second distribution result of polling all candidate component carriers is completed includes: If the first data has not been split yet, determining a second air interface time slot of the second data that has not been split; In the second air interface timeslot, determining a second scheduling priority for scheduling the second data; A third splitting result of splitting the second data to each of the candidate component carriers for scheduling is determined according to the second scheduling priority.

7. The data offloading method according to claim 1, wherein: The buffer status reporting information includes uplink buffer status reporting information. When the buffer status reporting information is uplink buffer status reporting information, each candidate component carrier is an uplink candidate scheduling carrier, and the offload component is a offload component of a terminal.

8. The data offloading method according to claim 1, wherein: The buffer status reporting information includes downlink buffer status reporting information. When the buffer status reporting information is downlink buffer status reporting information, each candidate component carrier is a downlink candidate scheduling carrier, and the offload component is a offload component of a base station.

9. A data diversion device, comprising a memory, a processor, and a data diversion program stored in the memory and executable on the processor, wherein the processor implements the steps of the data diversion method described in any one of claims 1 to 8 when executing the data diversion program.

10. A storage medium, wherein: The storage medium stores a data diversion program, which, when executed by a processor, implements the steps of the data diversion method according to any one of claims 1 to 8.

Images