CN117580177A

CN117580177A - Resource allocation method, device, equipment and storage medium

Info

Publication number: CN117580177A
Application number: CN202210928884.1A
Authority: CN
Inventors: 刘瑾; 季建科
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2022-08-03
Filing date: 2022-08-03
Publication date: 2024-02-20

Abstract

The embodiment of the application relates to the technical field of communication and discloses a resource allocation method, a device, equipment and a storage medium. The method comprises the following steps: when a target UE needs to transmit data through a Physical Uplink Shared Channel (PUSCH), determining a first number of Resource Blocks (RBs) scheduled by the target UE; if the first number is inconsistent with the second number of all available RBs in the full bandwidth range, determining the type of the target UE based on a first channel quality index corresponding to all available RBs, and determining the target RB from all available RBs based on a scheduling strategy corresponding to the type of the target UE; wherein, all available RBs comprise RBs special for PUSCH, the types at least comprise a first type and a second type, and different types correspond to different scheduling strategies; and distributing the target RB to the target UE so that the target UE performs data transmission based on the target RB. By adopting the embodiment of the application, the data transmission stability of the UE of different types can be improved, and the applicability is high.

Description

Resource allocation method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for resource allocation.

Background

In the field of communications, when a UE needs to transmit through a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH), a network device allocates a Resource Block (RB) dedicated to the PUSCH to the UE, so that the UE performs data transmission based on the RB allocated by the network device.

In the existing mode, although the network device can allocate RBs at different positions for different UEs or avoid RBs with larger co-channel interference by the UEs, the existing mode is difficult to improve the data transmission stability of different types of UEs, and has poor applicability.

Disclosure of Invention

The embodiment of the application provides a resource configuration method, a device, equipment and a storage medium, which can improve the data transmission stability of different types of UE.

In one aspect, an embodiment of the present application provides a resource allocation method, which is applicable to a network device, where the method includes:

when a target UE needs to transmit data through a Physical Uplink Shared Channel (PUSCH), determining a first number of Resource Blocks (RBs) scheduled by the target UE;

if the first number is inconsistent with the second number of all available RBs in the full bandwidth range, determining the type of the target UE based on a first channel quality index corresponding to all available RBs, and determining target RBs from all available RBs based on a scheduling strategy corresponding to the type of the target UE;

Wherein, all available RBs comprise RBs special for the PUSCH, the types at least comprise a first type and a second type, and different types correspond to different scheduling strategies;

and distributing the target RB to the target UE so that the target UE performs data transmission based on the target RB.

In another aspect, an embodiment of the present application provides a resource allocation apparatus, where the apparatus includes:

a number determining unit, configured to determine a first number of resource blocks RBs scheduled by a target UE when the target UE needs to perform data transmission through a physical uplink shared channel PUSCH;

a resource determining unit, configured to determine, if the first number is inconsistent with the second number of all available RBs within the full bandwidth range, a type of the target UE based on a first channel quality indicator corresponding to all available RBs, and determine, based on a scheduling policy corresponding to the type of the target UE, a target RB from all available RBs;

and the resource allocation unit is used for allocating the target RB to the target UE so that the target UE performs data transmission based on the target RB.

On the other hand, the embodiment of the application also provides a computer readable storage medium, and the computer readable storage medium stores a computer program, and when the computer program is executed by a processor, the resource allocation method provided by the embodiment of the application is realized.

Based on the method provided by the embodiment of the application, when the UE needs to transmit data through the PUSCH, if the number of RBs scheduled by the UE is inconsistent with the number of RBs in the full bandwidth range, the type of the UE can be determined based on the first channel quality index of the UE in the full bandwidth range, and then different scheduling strategies can be adopted to determine the target RBs allocated to the UE according to different types of the UE, so that flexible adjustment of the scheduling strategy is realized. Meanwhile, the data transmission of the UE of different types can be performed based on different RBs, so that the stability of the data transmission of the UE of different types is improved, and the applicability is high.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic flow chart of a resource allocation method provided in an embodiment of the present application;

fig. 2 is a schematic flow chart of determining a target RB according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a resource allocation apparatus according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In the embodiment of the application, the term "and/or" describes the association relationship of the association objects, which means that three relationships may exist, for example, a and/or B may be represented: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

The term "plurality" in the embodiments of the present application means two or more, and other adjectives are similar thereto.

The following description of the technical solutions in the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

In addition, the technical scheme provided by the embodiment of the application can be suitable for various systems, especially 5G systems. For example, suitable systems may be global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) universal packet Radio service (general packet Radio service, GPRS), long term evolution (long term evolution, LTE), LTE frequency division duplex (frequency division duplex, FDD), LTE time division duplex (time division duplex, TDD), long term evolution-advanced (long term evolution advanced, LTE-a), universal mobile system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX), 5G New Radio (NR) access systems, and the like. Core network parts such as evolved packet system (Evolved Packet System, EPS), 5G system (5 GS) etc. may also be included in the system.

The UE according to the embodiments of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing device connected to a wireless modem, etc. In different systems, the names of the user equipments may also be different, e.g. the user equipments may be called radio terminals, which may communicate with one or more Core Networks (CN) via radio access networks (Radio Access Network, RAN), the radio terminals may be mobile terminals, e.g. mobile phones (or "cellular" phones) and computers with mobile terminals, e.g. the user equipments may also be portable, pocket, hand-held, computer-built-in or car-mounted mobile devices, which exchange speech and/or data with the radio access networks. Such as personal communication services (Personal Communication Service, PCS) phones, cordless phones, session initiation protocol (Session Initiated Protocol, SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal Digital Assistant, PDAs), and the like. A wireless terminal may also be referred to as a system, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile), remote station (remote station), access point (access point), remote terminal (remote terminal), access terminal (access terminal), user agent (user agent), user device (user device), and the embodiments of the present application are not limited.

The network device to which the embodiments of the present application relate may be a base station, which may include a plurality of cells serving the UE. A base station may also be called an access point, or may be a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminals, or other names, depending on the particular application. The network device may be configured to exchange received air frames with internet protocol (Internet Protocol, IP) packets as a router between the wireless terminal and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in a global system for mobile communications (Global System for Mobile communications, GSM) or code division multiple access (Code Division Multiple Access, CDMA), a network device (NodeB) in a wideband code division multiple access (Wide-band Code Division Multiple Access, WCDMA), an evolved network device (evolutional Node B, eNB or e-NodeB) in a long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), a home evolved base station (Home evolved Node B, heNB), a relay node (relay node), a home base station (femto), a pico base station (pico), and the like. In some network structures, the network device may include a Centralized Unit (CU) node and a Distributed Unit (DU) node, which may also be geographically separated.

Multiple-input Multiple-output (Multi Input Multi Output, MIMO) transmissions may each be made between a network device and a User device using one or more antennas, and the MIMO transmissions may be Single User MIMO (SU-MIMO) or Multiple User MIMO (MU-MIMO). The MIMO transmission may be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or may be diversity transmission, precoding transmission, beamforming transmission, or the like, depending on the form and number of the root antenna combinations.

Referring to fig. 1, fig. 1 is a schematic flow chart of a resource allocation method provided in an embodiment of the present application. Optionally, the resource allocation method provided in the embodiment of the present application may be applicable to a network device, and specifically may include the following steps:

step S11, when the target UE needs to transmit data through the PUSCH, determining a first number of RBs scheduled by the target UE.

The RB scheduled by the target UE is an RB required for the target UE to perform data transmission through the PUSCH, and the number of RBs scheduled by the target UE (for convenience of description, hereinafter referred to as the first number) may be determined by the network device based on related information such as the data amount reported by the target UE, which is not limited herein.

And step S12, if the first number is inconsistent with the second number of all available RBs in the full bandwidth range, determining the type of the target UE based on the first channel quality index corresponding to all the available RBs, and determining the target RB from all the available RBs based on the scheduling strategy corresponding to the type of the target UE.

In some possible embodiments, all available RBs within the full bandwidth range include PUSCH-specific RBs, i.e., all RBs within the full bandwidth range that may be used when the target UE may transmit data over PUSCH.

The number of all available RBs within the full bandwidth range (hereinafter referred to as the second number for convenience of description) may be preconfigured by the network device, and may specifically be determined based on the actual application scenario requirements, which is not limited herein.

In some possible embodiments, when the first number of RBs scheduled by the target UE is inconsistent with the second number of RBs available in the full bandwidth range, if the first number is less than the second number, it may be determined that the target UE is in a non-full bandwidth scheduling state, that is, it is determined that the target UE needs to schedule a portion of RBs from all available RBs in the full bandwidth range for data transmission.

In this case, the first channel quality index corresponding to all available RBs of the target UE in the full bandwidth range may be determined, and the type of the target UE may be determined based on the first channel quality index corresponding to all available RBs in the full bandwidth range.

The first channel quality index corresponding to all available RBs of the target UE in the full bandwidth range may be determined based on a feedback result of the measurement signal, or may be determined according to a related parameter actively reported by the target UE, specifically may be determined based on an actual application scenario requirement, which is not limited herein.

Optionally, the first channel quality indicator comprises one or more of a signal-to-noise ratio (Signal to Noise Ratio, SNR), a modulation and coding strategy (Modulation Coding Scheme, MCS), an initial block error rate (Initial Block Error Rate, IBLER), or a reference signal received power (Reference Signal Receiving Power, RSRP).

Where SNR is the ratio of the Power of Signal (SNR) to the Noise Power (Power of Noise), IBLER is the ratio of the data blocks with primary transmission errors to all the primary transmission data blocks, MCS is used to indicate the data transmission rate, and RSRP represents the Signal strength.

Optionally, the types of the target UE include at least a first type and a second type, that is, when the first channel quality index corresponding to all available RBs in the full bandwidth range meets a certain preset condition, the type corresponding to the preset condition may be determined as the type of the target UE.

Alternatively, the first type and the second type may be good point users and bad point users, respectively.

As an example, in the case where the first channel quality index is SNR, the SNR corresponding to all available RBs of the target UE in the full bandwidth range (hereinafter referred to as a first SNR for convenience of description) may be determined, a preset condition satisfied by the first SNR may be determined, and a type corresponding to the preset condition satisfied by the first SNR may be determined as the type of the target UE.

The target UE may be determined to be a good point user if the first SNR is greater than a first threshold and a bad point user if the first SNR is less than or equal to the first threshold.

Alternatively, the target UE may be determined to be a good point user when the first SNR is greater than a first threshold, and the target UE may be determined to be a bad point user when the first SNR is less than a second threshold. When the first SNR is less than or equal to the first threshold and greater than or equal to the second threshold, the type of the target UE may be determined to be a default type, or the type determined when the target UE last transmitted data is determined to be the type of the target UE when the target UE is not transmitting data for the first time, and the type of the target UE is determined to be a default type when the target UE is transmitting data for the first time.

The default type may be a good point user or a bad point user, and may be specifically determined based on the actual application scene requirement, which is not limited herein.

As an example, in the case where the first channel quality indicator is IBLER, IBLER corresponding to all available RBs of the target UE in the full bandwidth range (hereinafter referred to as first IBLER for convenience of description) may be determined, a preset condition satisfied by the first IBLER may be determined, and a type corresponding to the preset condition satisfied by the first IBLER may be determined as the type of the target UE.

The target UE may be determined to be a handicapped user if the first IBLER is greater than a first threshold, and may be determined to be a handicapped user if the first IBLER is less than or equal to the first threshold.

Alternatively, the target UE may be determined to be a handicapped user when the first IBLER is greater than the first threshold, and the target UE may be determined to be a handicapped user when the first IBLER is less than the second threshold. When the first IBLER is less than or equal to the first threshold and greater than or equal to the second threshold, the type of the target UE may be determined to be a default type, or the type determined when the target UE last performed data transmission is determined to be the type of the target UE when the target UE is not performing data transmission for the first time, and the type of the target UE is determined to be a default type when the target UE is performing data transmission for the first time.

In some possible embodiments, after determining the type of the target UE, the target RB may be determined from all available RBs within the full bandwidth based on a scheduling policy corresponding to the type of the target UE.

Wherein, different types correspond to different scheduling strategies, for example, when the type of the target UE is a good point user, an interference randomization (AllocRadom) scheduling strategy can be adopted to determine the target RB from all available RBs in the full bandwidth range, or when the type of the target UE is a bad point user, a frequency selection scheduling (FrequencySelectiveScheduling, FSS) strategy can be adopted to determine the target RB from all available RBs in the full bandwidth range.

In some possible embodiments, when the type of the target UE is the first type, the target RB may be determined from all available RBs within the full bandwidth based on a scheduling policy corresponding to the first type.

The scheduling policy corresponding to the first type may be an interference randomization scheduling policy.

Specifically, an RB interval (hereinafter referred to as a first RB interval for convenience of description) corresponding to a cell in which the target UE is located may be determined from all available RBs within the full bandwidth range.

Wherein different cells correspond to different bandwidth ranges, and the RB ranges of the different bandwidth ranges are different.

The physical cell identifier (Physical Cell Identifier, PCI) of the cell where the target UE is located can be determined, modulo-N operation is performed on the PCI, and the calculation result is determined as an index of the cell where the target UE is located, so that a first RB interval corresponding to the cell where the target UE is located is determined according to the index.

The N may be preconfigured by the network device, and may specifically be determined based on the actual application scenario requirement, which is not limited herein. And the RB interval corresponding to each cell can equally divide the full bandwidth into N blocks by means of PCI modulo N, so as to divide different RB intervals for each cell.

For example, when the bandwidth is 100MHz, the granularity of the resource block group (Resource Block Group, RBG) is 16 RBs, the RBs dedicated for PUSCH in the full bandwidth range is 30-272 RBs (i.e., RBs dedicated for PUCCH, PRACH, etc. are removed), and the starting position of each RBG is a 16 multiple position such as 32,48,64. When N is 3, each cell can contain at most 80 RBs according to the equal division, the RB interval corresponding to the modulo-0 cell is 32-111 RBs, the RB interval corresponding to the modulo-1 cell is 112-191 RBs, and the RB interval corresponding to the modulo-2 cell is 192-272 RBs.

Further, after determining a first RB interval corresponding to the cell in which the target UE is located, the target RB may be determined from the first RB interval based on the first number of RBs scheduled by the target UE.

Alternatively, any first number of RBs may be determined from the first RB interval as the target RBs, and the determined first number of RBs may be continuous RBs or discontinuous RBs, which is not limited herein.

Alternatively, a continuous first number of RBs may be determined as target RBs starting from a starting position within the first RB interval.

Alternatively, the priority of each available RB in the first RB interval may be determined, and further, the target RB is determined from the first RB interval based on the first number and the priority of each available RB in the first RB interval.

Each available RB in the full bandwidth range may be marked with its priority by a corresponding priority identifier (flag), for example, the priority of an available RB that is not scheduled is higher than the priority of an available RB that is scheduled by any UE, for example, the priority identifier of an available RB that is not scheduled may be 1, the priority identifier of an available RB that is scheduled by any UE may be marked with 0, and then the priorities of the available RBs may be differentiated according to the priority identifier.

Based on this, any first number of RBs may be determined as target RBs from available RBs having highest priority in the first RB interval, and the determined first number of RBs may be continuous RBs or discontinuous RBs, which is not limited herein. And determining a first number of RBs with highest priority from the initial RBs in the first RB interval, and determining the RBs as final target RBs.

That is, any first number of RBs not scheduled by other UEs in the first RB interval is determined as a target RB, e.g., the first number of RBs not scheduled by other UEs are sequentially determined from the starting RB in the first RB interval, and are determined as final target RBs.

For example, assuming that the RB interval corresponding to the modulo-0 cell is 32-111 RBs, the RB interval corresponding to the modulo-1 cell is 112-191 RBs, the RB interval corresponding to the modulo-2 cell is 192-272 RBs, if the type of the target UE is the first type and the first number of RBs scheduled by the target UE is 4, when the target UE is located in the modulo-0 cell and all RBs in the first RB interval corresponding to the cell are not scheduled, the RB corresponding to the 32-35 RBs is determined as the target RB. While the RBs corresponding to 32-35 may be identified to indicate that the RBs corresponding to 32-35 are scheduled, such as by changing their priority identification to reduce their priority to the priority corresponding to when scheduled by the UE. And if another first type UE exists in the cell and needs to carry out data transmission through the PUSCH, determining a target RB corresponding to the UE from RBs corresponding to 32-111 from RBs corresponding to 36.

Alternatively, if the number of available RBs having the highest priority within the first RB interval (hereinafter referred to as the third number for convenience of description) is smaller than the first number, a fourth number of RBs is determined from available RBs of the next priority in order of priority from high to low, and the third number of RBs and the fourth number of RBs are determined as target RBs. Wherein the sum of the third number and the fourth number is equal to the first number.

For example, if the third number of RBs not scheduled by other UEs in the first RB interval is smaller than the first number, the third number of RBs not scheduled by other UEs in the first RB interval is determined as the target RB. And determining a fourth number of RBs as target RBs from RBs scheduled by other UEs within the first RB interval, such that the third number of RBs and the fourth number of RBs are equal to the first number of RBs.

For non-PUSCH dedicated RBs such as PRACH, PUCCH, etc. within the full bandwidth range, the priority may be labeled by the priority identification as well, and the priority of the non-PUSCH dedicated RBs is always less than the priority of the RBs scheduled by the UE, to ensure that the non-PUSCH dedicated RBs are not allocated to the target UE.

Where, if an RB including a bandwidth overlapping portion in the full bandwidth range, its priority may be also marked by a priority identification, and the priority order of RBs of the bandwidth overlapping portion may be as follows:

the first RB > the second RB > the third RB > the fourth RB > the fifth RB.

The first RB is an RB that is not scheduled by other UEs and corresponds to a non-bandwidth overlapping portion in all available RBs within a full bandwidth range, the second RB is an RB that is not scheduled by other UEs and corresponds to a bandwidth overlapping portion in all available RBs within the full bandwidth range, the third RB is an RB that is not scheduled by any UE and corresponds to a non-bandwidth overlapping portion in all available RBs within the full bandwidth range, the fourth RB is an RB that is not PUSCH-specific (e.g., PUCCH or PRACH-specific) and corresponds to a bandwidth overlapping portion in all available RBs within the full bandwidth range.

In some possible embodiments, when the type of the target UE is the second type, the target RB may be determined from all available RBs within the full bandwidth based on a scheduling policy corresponding to the second type.

The scheduling policy corresponding to the second type may be a frequency selection scheduling policy.

Specifically, all second RB intervals among all available RBs within the full bandwidth range may be determined.

Wherein each second RB interval includes at least one available RB, and the number of available RBs of each second RB interval is less than or equal to the first number.

Wherein, RBs in any two second RB intervals are not identical.

The available RBs in each second RB interval may be continuous RBs or discontinuous RBs, which may be specifically determined based on the actual application scenario requirements, and are not limited herein.

For example, when the bandwidth is 100MHz, the PUSCH-dedicated RBs within the full bandwidth range are RBs corresponding to 30 to 272. If the first number of RBs scheduled by the target UE is 20, then all second RB intervals may be determined from all available RBs within the full bandwidth range. If the RB corresponding to 30 is started, the RBs corresponding to 30-49 and the RBs corresponding to 31-50 are determined, and the RBs corresponding to …,253-272 are determined.

Alternatively, the priority of each available RB within each second RB interval may be the highest priority. That is, in determining each second RB section, a plurality of second RB sections may be determined from all available RBs having highest priority in the full bandwidth range, and each second RB section includes at least not more than the first number of available RBs, and RBs in any two second RB sections are not exactly the same.

The available RBs with the highest priority in each second RB interval may be continuous or discontinuous, which is not limited herein.

As an example, at least one available RB that is not scheduled in succession may be determined as one second RB section starting from the starting RBs of all available RBs within the full bandwidth range, and the starting RBs of each second RB section may be different, so that at least one second RB section is determined from all non-scheduled RBs.

For example, when the bandwidth is 100MHz, the PUSCH-dedicated RBs within the full bandwidth range are RBs corresponding to 30 to 272. If the first number of RBs scheduled by the target UE is 20 and RBs corresponding to 51-59 are scheduled by other UEs, the RB section corresponding to 30-49 and the RB section corresponding to 31-50 can be respectively determined as one second RB section from the RB corresponding to 30. Further, the RBs corresponding to 60-79 and 61-90 and the RBs corresponding to …,253-272 may be determined as a second RB section.

Among the RBs corresponding to 30 to 50 and RBs corresponding to 60 to 272, which are not scheduled by other UEs, other continuous RB sections having the number of RBs less than 20 may be used as the second RB section, and the present invention is not limited thereto.

the first RB > the second RB > the third RB > the fourth RB > the fifth RB.

Further, after determining each second RB interval, a second channel quality indicator corresponding to each second RB interval may be determined, and an available RB in the second RB interval corresponding to the optimal second channel quality indicator may be determined as the target RB.

The second channel quality indicator may be any one of SNR, IBLER, or RSRP.

After determining the target RB, the priority identification corresponding to the target RB may be changed to reduce its priority to the priority corresponding to when scheduled by the UE.

In some possible embodiments, the target UE may be determined to be in the full bandwidth scheduling state if the first number of RBs scheduled by the target UE is consistent with the second number of all available RBs within the full bandwidth range.

In this case, at least one third RB interval may be determined from all available RBs within the full bandwidth range, and the number of available RBs within each third RB interval may be different from the above-mentioned second number by a preset amount.

The preset number may be preconfigured by the network device, and may specifically be determined based on the actual application scenario requirement, which is not limited herein.

The RBs in each third RB interval may be continuous or discontinuous, and may specifically be determined based on the actual application scenario requirements, which is not limited herein.

The available RBs in any two third RB intervals are not identical, that is, all the determined third RB intervals do not have identical RB intervals.

For example, when the bandwidth is 100MHz, the PUSCH-dedicated RBs within the full bandwidth range are RBs corresponding to 30 to 272. If the preset number is 4, the number of RBs in each third RB interval is 239, and if the RBs corresponding to 34 th to 272 th are determined as the third RB interval.

Further, a third channel quality index corresponding to each third RB interval of the target UE and third channel quality indexes corresponding to all available RBs of the target UE in the full bandwidth range may be determined, and then the available RBs in the RB range corresponding to the optimal third channel quality index are determined as target RBs.

The second channel quality indicator may be any one of SNR, IBLER, or RSRP.

The second channel quality index and the third channel quality index may be determined based on the feedback result of the measurement signal, or may be determined according to related parameters actively reported by the target UE, specifically may be determined based on the actual application scenario requirement, which is not limited herein.

And step S13, distributing the target RB to the target UE so that the target UE performs data transmission based on the target RB.

In some possible embodiments, after determining the target RB, the network device may determine the target RB as an RB scheduled when the target UE performs data transmission on the PUSCH and allocate the target RB to the target UE. So that the target UE can realize data transmission through PUSCH based on the target RB.

It should be noted that, in the embodiment of the present application, the RB is a physical resource block (Physical Resource Block, PRB).

The manner in which the target RB according to the embodiments of the present application is determined is further described below with reference to fig. 2. Fig. 2 is a schematic flow chart of determining a target RB according to an embodiment of the present application. As shown in fig. 2, when the target UE needs to perform data transmission through the PUSCH, a first number of RBs scheduled by the target UE may be determined, and a scheduling state of the target UE may be determined based on the first number.

Wherein the first number of RBs scheduled by the target UE may be represented by ul_prbs.

Further, a second number of all available RBs dedicated to PUSCH within the full bandwidth range may be determined, and if the first number is inconsistent with the second number, the target UE is determined to be in a non-full bandwidth scheduling state, and if the first number is consistent with the second number, the target UE is determined to be in a full bandwidth scheduling state.

When the target UE is in the full bandwidth scheduling state, the target RB can be determined from all available RBs in the full bandwidth range based on a preset scheduling strategy, namely at least one third RB section is determined from all available RBs in the full bandwidth range, a third channel quality index of all available RBs in the full bandwidth range of the target UE and a third channel quality index of the target UE in each third RB section are determined, and then the available RBs in the RB range corresponding to the optimal third channel quality index are determined as target RBs.

The number of available RBs in each third RB interval is different from the second number by a preset number, and the number of available RBs in any two third RB intervals is not completely the same.

When the target UE is in a non-full bandwidth scheduling state, a first channel quality indicator of all available RBs of the target UE within the full bandwidth range may be determined to determine whether the type of the target UE is a first type (good point user) or a second type (bad point user) based on the first channel quality indicator of all available RBs of the target UE within the full bandwidth range.

For example, the first channel quality index may be an SNR, and the first channel quality index corresponding to all available RBs of the target UE in the full bandwidth range may be expressed as prb_snr. And when the PRB_SNR is smaller than the FreqSelect_threshold, determining the type of the target UE as a difference user. When the PRB_SNR is less than or equal to rand_threshold and greater than or equal to FreqSelect_threshold, determining the type of the target UE when the target UE last transmits data as the type of the target UE. If the target UE is the first data transmission, determining the default type as the type of the target UE, where the default type may be a handicapped user or a good-point user.

When the PRB_SNR is greater than the rand_threshold (i.e. the type of the target UE is a good point user), determining a target RB from a first RB interval corresponding to a cell in which the target UE is located based on an interference randomization scheduling policy.

When the prb_snr is smaller than the freqselect_threshold (i.e., the type of the target UE is a difference user), determining the target RB from all available RBs in the full bandwidth based on the tone scheduling policy.

The scheduling policy may be represented by uefs_type, for example, when uefs_type is 1, the scheduling policy is a frequency selection scheduling policy, and when uefs_type is 0, the scheduling policy is an interference randomization scheduling policy.

Before implementing the resource allocation method provided by the embodiment of the application, the network device may determine that the interference randomization scheduling policy switch and the frequency selection scheduling policy switch remain in an on state in advance, so as to support that the interference randomization scheduling policy or the frequency selection scheduling policy is adopted to determine the target RB.

The interference randomization scheduling policy switch may be expressed as ul_randswitch, where ul_randswitch=0 indicates that the network device does not support the interference randomization scheduling policy, and ul_randswitch=1 indicates that the network device supports the interference randomization scheduling policy.

The tone allocation policy switch may be represented as ul_ FreqSelectSwitch, UL _freqselect switch=0, where ul_freqselect switch=1 indicates that the network device does not support the tone allocation policy.

That is, the network device determines in advance whether ul_randswitch and ul_freqselectswitch are in an open state, and if any switch is in a closed state, it needs to be changed to an open state.

Based on the implementation manner, when the good point User (UE) is in the non-full bandwidth scheduling state, the channel quality corresponding to the target UE is higher, and at the moment, the target RB can be determined from the first RB interval corresponding to the cell where the target UE is located and allocated to the target UE, so that the flexibility in determining the target RB is improved. If the target RB is determined from within the first RB interval based on the priority of each RB, stability when the good point User (UE) performs data transmission can be further enabled. If the target RB is determined from the starting RB of the first RB section based on the priority of each RB, the RBs scheduled by the good point User (UE) may be concentrated near the starting RB of the respective corresponding first RB section, thereby reserving more RB resources for the bad point User (UE).

When a difference point User (UE) is in a non-full bandwidth scheduling state, a target RB can be determined from all available RBs in a full bandwidth range, and flexibility in determining the target RB is improved. If the target RB is determined from all available RBs in the full bandwidth range based on the priority of each RB, the poor-quality RBs of the channel can be prevented from being scheduled by the difference point User (UE), the interference of the good point user on the difference point user is avoided, and the stability of the difference point user in data transmission is improved.

Meanwhile, the target RBs are determined based on the RB priorities, so that the repeatability between target RBs corresponding to good point users and bad point users can be reduced, and the stability of each User (UE) in data transmission is effectively improved.

When any User (UE) is in a full bandwidth scheduling state, by determining at least one third RB interval and determining the RB range with the optimal third channel quality index in all available RBs in each third RB interval and the full bandwidth range as a target RB, the target RB with the best channel quality can be determined from all available RBs in the full bandwidth range, so that the UE has higher data transmission stability.

The method for determining the target RB shown in fig. 2 is merely an example, and is not limited in the embodiment of the present application.

Based on the resource allocation method provided by the embodiment of the application, different scheduling strategies can be adopted for the types and the scheduling states of the UE, RBs with good channel quality can be allocated to the UEs with different types as much as possible, so that the uplink performance during UR data transmission is improved, the UE disconnection rate is reduced, and the reconstruction rate is optimized.

The embodiment of the application also provides a resource allocation device, as shown in fig. 3, fig. 3 is a schematic structural diagram of the resource allocation device provided in the embodiment of the application, where the device includes:

a number determining unit 31, configured to determine, when a target UE needs to perform data transmission through a physical uplink shared channel PUSCH, a first number of resource blocks RBs scheduled by the target UE;

A resource determining unit 32, configured to determine, if the first number is inconsistent with the second number of all available RBs within the full bandwidth range, a type of the target UE based on a first channel quality indicator corresponding to all available RBs, and determine, based on a scheduling policy corresponding to the type of the target UE, a target RB from all available RBs;

and a resource allocation unit 33, configured to allocate the target RB to the target UE, so that the target UE performs data transmission based on the target RB.

In some possible embodiments, the first channel quality indicator includes one or more of a signal-to-noise ratio SNR, an initial block error rate IBLER, a modulation and coding scheme MCS, or a reference signal received power RSRP.

In some possible embodiments, the type of the target UE is the first type, and the resource determining unit 32 is configured to:

determining a first RB interval corresponding to a cell where the target UE is located from all available RBs;

and determining a target RB from the first RB section based on the first number.

In some possible embodiments, the resource determining unit 32 is configured to:

determining the priority of each available RB in the first RB interval;

and determining a target RB from the first RB section based on the first number and the priority of each available RB in the first RB section.

In some possible embodiments, the type of the target UE is the second type, and the resource determining unit 32 is configured to:

determining all second RB intervals in all available RBs, wherein each second RB interval comprises at least one available RB, the number of the available RBs in each second RB interval is smaller than or equal to the first number, and the RBs in any two second RB intervals are not identical;

and determining a second channel quality index corresponding to each second RB section, and determining available RBs in the second RB section corresponding to the optimal second channel quality index as target RBs.

In some possible embodiments, the priority of each available RB in each of the second RB intervals is the highest priority.

In some possible embodiments, the above-mentioned resource determining unit 32 is further configured to:

if the first number is consistent with the second number, determining at least one third RB section from all the available RBs, wherein the number of the available RBs in each third RB section is different from the second number by a preset number, and the available RBs in any two third RB sections are not identical;

And determining a third channel quality index corresponding to all the available RBs and a third channel quality index corresponding to each third RB section, and determining available RBs in an RB range corresponding to the optimal third channel quality index as target RBs.

In some possible embodiments, the second channel quality indicator and the third channel quality indicator include any one of SNR, IBLER, or RSRP.

In some possible embodiments, the priority of the available RBs scheduled by any UE is lower than the priority of the available RBs not scheduled by the UE.

It should be noted that, in the embodiment of the present application, the division of the modules (units) is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in software functional modules.

The integrated modules described above, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application, or a part contributing to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

It should be noted that, the above device provided in this embodiment of the present application can implement all the method steps implemented in the method embodiment and achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those of the method embodiment in this embodiment are omitted.

As shown in fig. 4, an embodiment of the present application further provides an electronic device, including a memory 402, a transceiver 404, and a processor 401;

a memory 402 for storing a computer program;

a transceiver 404 for receiving and transmitting data under the control of the processor 401;

the processor 401 is configured to read the computer program in the memory 402 and perform the following operations:

In some possible embodiments, the type of the target UE is the first type, and the processor 401 is configured to:

In some possible embodiments, the processor 401 is configured to:

determining the priority of each available RB in the first RB interval;

In some possible embodiments, the type of the target UE is the second type, and the processor 401 is configured to:

In some possible embodiments, the above processor 401 is further configured to:

Wherein in fig. 4, a bus architecture may comprise any number of interconnected buses and bridges, with one or more processors 401, represented in particular by processor 401, and various circuits of memory 402, represented by memory 402, being linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. Bus interface 403 provides an interface. The transceiver 404 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over transmission media, including wireless channels, wired channels, optical cables, and the like. The processor 401 is responsible for managing the bus architecture and general processing, and the memory 402 may store data used by the processor 401 in performing operations. When the electronic device is used as a terminal, the user interface 405 may also be an interface capable of being externally connected to a device in need of connection, and the connected device includes, but is not limited to, a keypad, a display, a speaker, a microphone, a joystick, and the like.

Processor 401 may be a Central Processing Unit (CPU), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field-Programmable Gate Array, FPGA) or complex programmable logic device (Complex Programmable Logic Device, CPLD), and processor 401 may also employ a multi-core architecture.

The processor 401 is configured to execute any of the resource allocation methods provided in the embodiments of the present application according to the obtained executable instructions by calling a computer program stored in the memory 402. The processor 401 and the memory 402 may also be physically separated.

Embodiments of the present application also provide a computer readable storage medium storing a computer program for causing the above processor to execute any of the resource allocation methods provided in the embodiments of the present application.

The computer readable storage medium may be any available medium or data storage device that can be accessed by a processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, tapes, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile storage (NANDFLASH), solid State Disk (SSD), etc.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.

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

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

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

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims

1. A method of resource allocation, for use with a network device, the method comprising:

if the first number is inconsistent with the second number of all available RBs in the full bandwidth range, determining the type of the target UE based on a first channel quality index corresponding to all available RBs, and determining a target RB from all available RBs based on a scheduling strategy corresponding to the type of the target UE;

wherein, the all available RBs comprise RBs special for the PUSCH, the types at least comprise a first type and a second type, and different types correspond to different scheduling strategies;

2. The method of claim 1, wherein the first channel quality indicator comprises one or more of a signal-to-noise ratio, SNR, initial block error rate, IBLER, modulation and coding scheme, MCS, or reference signal received power, RSRP.

3. The method of claim 1, wherein the type of the target UE is the first type, wherein determining the target RB from the all available RBs based on the scheduling policy corresponding to the first type comprises:

4. The method of claim 3, wherein the determining a target RB from the first RB interval based on the first number comprises:

determining the priority of each available RB in the first RB interval;

5. The method of claim 1, wherein the type of the target UE is the second type, wherein determining the target RB from the all available RBs based on the scheduling policy corresponding to the second type comprises:

determining all second RB intervals in all available RBs, wherein each second RB interval comprises at least one available RB, the number of the available RBs in each second RB interval is smaller than or equal to the first number, and RBs in any two second RB intervals are not identical;

6. The method of claim 5, wherein the priority of each available RB within each of the second RB intervals is a highest priority.

7. The method according to claim 1, wherein the method further comprises:

and determining third channel quality indexes corresponding to all the available RBs and third channel quality indexes corresponding to all the third RB intervals, and determining available RBs in an RB range corresponding to the optimal third channel quality indexes as target RBs.

8. The method according to claim 5 or 7, wherein the second channel quality indicator and the third channel quality indicator comprise any one of SNR, IBLER or RSRP.

9. The method of claim 4, 6 or 7 wherein the available RBs scheduled by any UE have a lower priority than the available RBs not scheduled by the UE.

10. A resource allocation apparatus, the apparatus comprising:

11. An electronic device comprising a memory, a transceiver, and a processor:

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

12. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for causing the computer to execute the method of any one of claims 1 to 9.