Communication method, communication device, and computer-readable storage medium

Abstract

Provided are a communication method, a communication device, and a computer-readable storage medium. The method comprises: in a multiple-user multiple-input multiple-output mode, determining that the proportion of terminal devices located at the edge of a cell exceeds a threshold. The method further comprises: on the basis of scheduling priorities and a first proportion, allocating available uplink frequency domain resources within a time unit to terminal devices to be scheduled within the time unit. By using the method, a user at an uplink coverage far point can obtain a power convergence gain, so that SINR is increased, and the uplink experience rate of the user is increased, achieving scheduling fairness.

Description

Communication method, communication device, and computer-readable storage medium Technical Field

[0001] The present application relates to the field of communications, and more particularly, to a communication method, a communication device, and a computer-readable storage medium. Background Art

[0002] During the uplink scheduling process, the network device determines the number of resource blocks (RBs) required by the terminal device within a transmission time interval (TTI) based on the buffer status, power margin, channel quality, product hardware information, etc. reported by the terminal device. The network device first allocates frequency domain or spatial domain resources and then allocates time domain resources based on the scheduling priority order of the terminal devices. When some terminal devices in a cell are in single-user multiple input multiple output (SU-MIMO) mode and other terminal devices are in multiple-user multiple input multiple output (MU-MIMO) mode, the network device cannot obtain the power aggregation gain of the terminal devices at the edge of the cell.

[0003] Summary of the Invention

[0004] An example possible implementation of the present application provides a solution for uplink frequency domain resource allocation.

[0005] In the first aspect of the present application, a communication method is provided. The method includes determining, in a multi-user multiple-input multiple-output mode, that the proportion of terminal devices located at the edge of a cell exceeds a threshold. The available uplink frequency domain resources within a time unit are allocated to the terminal devices to be scheduled within the time unit according to the scheduling priority and the first proportion. Using this method, users with far-reaching uplink coverage can obtain power aggregation gain, the signal to interference plus noise ratio (SINR) will be improved, the user uplink experience rate will increase, and scheduling fairness will be achieved.

[0006] In some implementations, the first ratio includes an equal ratio. In this way, a power aggregation gain of the terminal device can be obtained, satisfying scheduling fairness.

[0007] In some implementations, allocating available uplink frequency domain resources within a time unit to scheduled terminal devices according to the scheduling priority and the first ratio includes: determining a first number of uplink frequency domain resources to be allocated to a first terminal device among the scheduled terminal devices based on the number of available uplink frequency domain resources, the first ratio, and the number of terminal devices to be scheduled within the time unit. If the second number of uplink frequency domain resources required by the first terminal device is less than the first number, allocating the second number of uplink frequency domain resources to the first terminal device. If the second number is greater than the first number, allocating the first number of uplink frequency domain resources to the first terminal device.

[0008] In some implementations, the method further includes: determining a first ratio as a ratio between the numbers of uplink frequency domain resources required by the scheduled terminal devices within a time unit.

[0009] In some implementations, the first ratio is determined based on a scheduling priority of the scheduled terminal device.

[0010] In a second aspect of the present application, a communication device is provided, which includes a unit for executing the method according to the first aspect of the present application.

[0011] In a third aspect of the present application, a communication device is provided. The communication device includes at least one processor and at least one memory. The at least one memory is coupled to the at least one processor and stores instructions for execution by the at least one processor. When executed by the at least one processor, the instructions cause the communication device to implement the method according to the first aspect of the present application.

[0012] In a fourth aspect of the present application, a computer-readable storage medium is provided. The computer-readable medium stores a computer program. When the computer program is executed by a processor, the method according to the first aspect of the present application is implemented.

[0013] In a fifth aspect of the present application, a computer program product is provided. The computer program product includes machine-executable instructions. When executed by a communication device, the machine-executable instructions cause the communication device to perform the method according to the first aspect of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The features, advantages and other aspects of the various implementations of the present application will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Several implementations of the present application are shown here in an exemplary and non-limiting manner. In the accompanying drawings:

[0015] FIG1 shows a schematic block diagram of a communication system in which a possible implementation of the present application may be implemented;

[0016] FIG2A shows a schematic diagram of allocating RBs according to the scheduling priority order of terminal devices;

[0017] FIG2B shows a schematic diagram of RB allocation when all terminal devices are in SU-MIMO mode;

[0018] FIG2C is a schematic diagram showing RB allocation when some terminal devices are in SU-MIMO mode and another terminal devices are in MU-MIMO mode;

[0019] FIG2D is a schematic diagram showing that after the initial transmission scheduling of the terminal device fails, the retransmission scheduling also fails continuously;

[0020] FIG3 shows a flow chart of a communication method according to some implementations of the present application;

[0021] FIG4 shows a schematic diagram of uplink frequency domain resource allocation in MU-MIMO mode according to some possible implementations of the present application;

[0022] FIG5 is a schematic diagram showing uplink frequency domain resource allocation in MU-MIMO mode according to some other possible implementations of the present application; and

[0023] FIG6 shows a block diagram of an example communication device according to the implementation method of the present application.

[0024] In the various drawings, the same or similar reference numerals denote the same or similar elements. DETAILED DESCRIPTION

[0025] The following describes possible implementations of the present application in more detail with reference to the accompanying drawings. Although the accompanying drawings illustrate certain possible implementations of the present application, it should be understood that the present application can be implemented in various forms and should not be construed as being limited to the possible implementations described herein. Rather, these possible implementations are provided to provide a more thorough and complete understanding of the present application. It should be understood that the accompanying drawings and possible implementations of the present application are for illustrative purposes only and are not intended to limit the scope of protection of the present application.

[0026] In the description of possible implementations of the present application, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one possible implementation" or "the possible implementation" should be understood as "at least one possible implementation". The terms "first", "second", etc. may refer to different or the same objects. The following may also include other explicit and implicit definitions. Expressions similar to "at least one of A, B and C" or "at least one of A, B or C" should be understood as any of the following: at least one A; at least one B; at least one C; at least one A and at least one B; at least one A and at least one C; at least one B and at least one C; at least one A, at least one B and at least one C. The above is explained by taking A, B and C as an example. When there are more elements in the expression, the meaning of the expression can be obtained according to the above rules.

[0027] The possible implementation of the present application can be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols such as the fourth generation (4G) and the fifth generation (5G), wireless local area network communication protocols such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or developed in the future. The technical solutions of the possible implementation of the present application are applied to follow any appropriate communication system, such as: General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Frequency Division Duplex (FDD) system, Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), Narrowband Internet of Things (NB-IoT) communication system, future fifth generation (5G) system or new radio access technology (NR), etc.

[0028] For the purpose of illustration, the following describes possible implementations of the present application in the context of a 5G Third Generation Partnership Project (3GPP) communication system. However, it should be understood that the possible implementations of the present application are not limited to being applied to a 5G communication system, but can be applied to any other communication system with similar problems, as long as uplink scheduling exists in the communication system.

[0029] FIG1 shows a schematic block diagram of a communication system 100 in which a possible implementation of the present application may be implemented. As shown in the figure, the communication system 100 includes a network device 110 and terminal devices 120, 130, 140, 150, 160. The terminal devices 120, 130, 140, 150, 160 are located in a cell 112 provided by the network device 110. The transmission of control information and / or data from the network device 110 to the terminal devices 120, 130, 140, 150, 160 is referred to as downlink (DL) communication, and the transmission of control information and / or data from the terminal devices 120, 130, 140, 150, 160 to the network device 110 is referred to as uplink (UL) communication.

[0030] The network device 110 refers to any device capable of communicating with the terminal devices 120, 130, 140, 150, and 160. As an example, the network device 110 may include a NodeB, an evolved NodeB (eNodeB), a base station in a 5G mobile communication system, a next generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a Wi-Fi system.

[0031] Terminal devices 120, 130, 140, 150, and 160 are any devices capable of communicating with network device 110. Examples of terminal devices 120, 130, 140, 150, and 160 include mobile phones, cars, tablet computers, and sensors such as smart speakers, train detectors, and gas stations. The primary functions of terminal devices 120, 130, 140, 150, and 160 include, but are not limited to, collecting data, receiving control information and / or downlink data from network device 110, and transmitting electromagnetic waves and sending control information and / or uplink data to network device 110.

[0032] It is understood that the number of network devices and terminal devices shown in Figure 1 is merely an example and is not intended to impose any limitation. According to actual needs, the communication system 100 may include any appropriate number of network devices and terminal devices.

[0033] Network device 110 determines available uplink frequency domain resources within a time unit. In one possible implementation, the time unit may include, but is not limited to, a time interval (TTI), and the uplink frequency domain resources may include, but are not limited to, resource allocation (RBs). The following describes the uplink frequency domain resource allocation process using an example of a network device allocating RBs to a terminal device within a TTI.

[0034] Figure 2A shows a schematic diagram of RB allocation according to the scheduling priority order of terminal devices. In the following, for the sake of simplicity, terminal devices are also referred to as "UEs". In the example of Figure 2A, the network device first performs frequency domain or spatial domain resource allocation and then time domain resource allocation according to the scheduling priority order of the UEs. For example, the scheduling priority order of the UEs is: UE#1>UE#2>UE#3>UE#4>UE#5. The number of RBs required by UE#1 in TTI0 is greater than or equal to the number of RBs corresponding to the full bandwidth (i.e., system bandwidth), and the network device will allocate RBs corresponding to the full bandwidth to UE#1 according to the scheduling priority order. Therefore, the network device can only schedule UE#2 and UE#3 in the next TTI (i.e., TTI1), and the total number of RBs required by UE#2 and UE#3 is less than or equal to the number of RBs corresponding to the full bandwidth. The number of RBs required by UE#4 and UE#5 is greater than the number of RBs corresponding to the full bandwidth, so only UE#4 is scheduled in TTI2, and only UE#5 is scheduled in TTI3.

[0035] Figure 2B shows a schematic diagram of RB allocation when all terminal devices are in SU-MIMO mode. In the example of Figure 2B, all UEs in the cell are in SU-MIMO mode, and the network device distributes the RBs corresponding to the full bandwidth evenly among the UEs in one TTI according to the scheduling priority order of the UEs. For example, the scheduling priority order of the UEs is: UE#1>UE#2>UE#3>UE#4>UE#5. In TTI0, the network device simultaneously schedules four terminal devices UE#1, UE#2, UE#3 and UE#4, and distributes the RBs corresponding to the full bandwidth evenly among these four terminal devices. In TTI1 and TT2, UE#3 has no data packet transmission, so the network device simultaneously schedules UE#1, UE#2, UE#4 and UE#5, and distributes the RBs corresponding to the full bandwidth evenly among these four terminal devices. In TTI3, UE#2 and UE#3 have no data packet transmission, so the network device only schedules UE#1, UE#4 and UE#5. In TTI3, since the number of RBs required by UE#1 is less than the number of RBs evenly distributed among the three UEs, the network device allocates the required number of RBs to UE#1 and then evenly distributes the remaining RBs between UE#4 and UE#5.

[0036] Figure 2C shows a schematic diagram of RB allocation when some UEs are in SU-MIMO mode and others are in MU-MIMO mode. When some UEs in a cell are in SU-MIMO mode and others are in MU-MIMO mode, the network device first allocates frequency or spatial resources, then time domain resources, based on the UE scheduling priority order. For example, the UE scheduling priority order is: UE#1 > UE#2 > UE#3 > UE#4 > UE#5. In TTI0, the number of RBs required by UE#1 is greater than or equal to the number of RBs corresponding to the full bandwidth, so the network device allocates RBs corresponding to the full bandwidth to UE#1. The network device can only schedule UE#2 and UE#3 in the next TTI (i.e., TTI1), and the total number of RBs required by UE#2 and UE#3 is less than or equal to the number of RBs corresponding to the full bandwidth. The number of RBs required by UE#4 and UE#5 is greater than the number of RBs corresponding to the full bandwidth, so only UE#4 is scheduled in TTI2, and only UE#5 is scheduled in TTI3.

[0037] Network equipment is usually set up at the center of a cell. The center of the cell is called the near point, the edge of the cell is called the far point, and the area between the near point and the far point is called the midpoint. The Reference Signal Received Power (RSRP) and SINR of the UE located at the midpoint and far point of the cell are poor and the power is easily limited. If the network device first allocates frequency domain or spatial domain resources and then allocates time domain resources according to the scheduling priority order of the UE, the network device cannot obtain the power aggregation gain of these UEs. For example, as shown in Figure 2C, within TTI0, the network device allocates RBs corresponding to the full bandwidth to UE#1. If UE#1 is located at the edge of the cell and is power-limited, then according to the following calculation method of Power Spectral Density (PSD), the network device will not be able to obtain the power aggregation gain of UE#1: PSD = actual transmit power / number of actually allocated RBs (1)

[0038] Figure 2D shows a schematic diagram of a situation in which retransmission scheduling fails after the initial transmission scheduling of the UE fails. In the example of Figure 2D, the network device first performs frequency domain or spatial domain resource allocation and then time domain resource allocation according to the scheduling priority order of the UE. For example, the scheduling priority order of the UE is: UE#1>UE#2>UE#3>UE#4>UE#5. In TTI0, since UE#1 has the highest scheduling priority and the number of RBs required by UE#1 is greater than or equal to the number of RBs corresponding to the full bandwidth, the network device allocates RBs corresponding to the full bandwidth to UE#1. However, the initial transmission scheduling of UE#1 fails in TTI0, so the network device will continue to perform retransmission scheduling for UE#1 in TTI1, TTI2 and TTI3. Since the retransmission scheduling priority of UE#1 is higher than the initial transmission scheduling priority of UE#1, the network device cannot schedule other UEs in TTI1, TTI2 and TTI3.

[0039] To address at least the aforementioned issues and potentially other related issues, the implementation of the present application proposes a solution for uplink frequency domain resource allocation. According to this solution, when a UE is in MU-MIMO mode, it is determined that the proportion of UEs located at the edge of the cell exceeds a threshold, and the available RBs within a TTI are allocated to the UEs scheduled within the TTI according to a first proportion. The following describes in detail possible implementations of the present application with reference to Figures 3 and 4.

[0040] FIG3 illustrates a flow chart of a communication method 300 according to some implementations of the present application. In some implementations, the method 300 may be implemented by the network device 110 in the example communication system 100, for example, by a processor or processing unit of the network device 110 in conjunction with other components (e.g., a transceiver). In other implementations, the method 300 may also be implemented by other communication devices independent of the example communication system 100. For ease of explanation, the example method 300 will be described with reference to FIG1.

[0041] At 310, in MU-MIMO mode, network device 110 determines whether the proportion of terminal devices located at the edge of cell 112 exceeds a threshold. In other words, network device 110 determines whether the proportion of terminal devices located at the edge of cell 112 is greater than or equal to the threshold. Hereinafter, this threshold is also referred to as a "proportion threshold."

[0042] In some possible implementations, if the network device 110 enables the uplink MU-MIMO function, the cell 112 is in the MU-MIMO mode.

[0043] In some possible implementations, if the network device 110 detects that the RSRP from one terminal device in the cell 112 is lower than the RSRP threshold, the network device 110 may determine that the terminal device is at the edge of the cell 112. For example, in FIG1 , if the network device 110 detects that the RSRP from the terminal devices 120 and 160 in the cell 112 are both lower than the RSRP threshold, the network device 110 may determine that the terminal devices 120 and 160 are at the edge of the cell 112.

[0044] Alternatively, in a possible implementation, if the network device 110 detects that the SNR from a terminal device in the cell 112 is lower than the SINR threshold, the network device 110 may determine that the terminal device is located at the edge of the cell 112 .

[0045] In some possible implementations, the RSRP threshold may be predefined.

[0046] In some possible implementations, the SINR threshold may be predefined.

[0047] In some possible implementations, the ratio threshold may be predefined.

[0048] As an example, the ratio threshold may be 30%. If the maximum number of terminal devices to be scheduled within one time unit is 4, and network device 110 determines that terminal devices 120 and 160 are at the edge of cell 112 (i.e., the number of terminal devices located at the edge of cell 112 is 2), then the ratio of terminal devices located at the edge of cell 112 is 50% (greater than 30%). Therefore, network device 110 may determine that the ratio of terminal devices located at the edge of cell 112 exceeds the ratio threshold.

[0049] It is understood that the ratio threshold may take any appropriate value, which may include but is not limited to 30%. The scope of protection of the present application is not limited in this respect.

[0050] If the proportion of terminal devices located at the edge of the cell 112 exceeds the proportion threshold, the method 300 proceeds to 320 .

[0051] At 320 , the network device 110 allocates available uplink frequency domain resources within a time unit to the terminal devices to be scheduled within the time unit according to the scheduling priority and the first ratio.

[0052] In some possible implementations, the time unit may include but is not limited to TTI.

[0053] In some possible implementations, uplink frequency domain resources may include but are not limited to RBs.

[0054] For example, the available uplink frequency domain resources within a time unit may include available RBs within a TTI. The available RBs within a TTI may include RBs corresponding to the full bandwidth.

[0055] In some possible implementations, the network device 110 may determine the terminal devices to be scheduled within a time unit based on the scheduling priorities of the terminal devices. For example, if the scheduling priorities of the terminal devices 120, 130, 140, 150, and 160 (hereinafter referred to as UE#1, UE#2, UE#3, UE#4, and UE#5, respectively) are in the order of UE#1>UE#2>UE#3>UE#4>UE#5, and within a time unit, UE#1, UE#2, UE#3, UE#4, and UE#5 all have uplink data to send and the maximum number of terminal devices to be scheduled within a time unit is 4, then the network device 110 may determine that the terminal devices to be scheduled within a time unit are UE#1, UE#2, UE#3, and UE#4 based on the scheduling priorities. For another example, if the scheduling priority order is: UE#1>UE#2>UE#3>UE#4>UE#5, only UE#1, UE#2, and UE#3 have uplink data to send and the maximum number of terminal devices to be scheduled within one time unit is 4, then the network device 110 can determine that the terminal devices to be scheduled within one time unit are UE#1, UE#2, and UE#3 according to the scheduling priority.

[0056] On the other hand, if the proportion of terminal devices located at the edge of the cell 112 exceeds the proportion threshold, the method 300 proceeds to 330 .

[0057] At 330, the network device 110 may allocate the available uplink frequency domain resources within a time unit to the terminal devices to be scheduled within the time unit according to the scheduling priority. For example, the network device 110 may use the method described above with reference to FIG. 2C to allocate the available uplink frequency domain resources within a time unit to the terminal devices to be scheduled within the time unit according to the scheduling priority.

[0058] By using the method 300 , users at far-flung points in uplink coverage can obtain power aggregation gain, SINR can be improved, and the user uplink experienced rate can be increased, thereby achieving scheduling fairness.

[0059] In some possible implementations, the first ratio includes an equal ratio. In this possible implementation, the network device 110 can determine the first number of uplink frequency domain resources to be allocated to the first terminal device among the scheduled terminal devices based on the number of available uplink frequency domain resources, the first ratio (i.e., an equal ratio) and the number of terminal devices to be scheduled within the time unit. If the second number of uplink frequency domain resources required by the first terminal device is less than the first number, the second number of uplink frequency domain resources is allocated to the first terminal device. If the second number is greater than the first number, the first number of uplink frequency domain resources is allocated to the first terminal device. This will be described with reference to Figure 4.

[0060] Figure 4 shows a schematic diagram of uplink frequency domain resource allocation in MU-MIMO mode according to some possible implementations of the present application. In the example of Figure 4, in MU-MIMO mode, the network device 110 allocates the available RBs within a TTI to the UEs to be scheduled within the TTI in equal proportions. The available RBs within a TTI include RBs corresponding to the full bandwidth (for example, 273 RBs), and the maximum number of UEs to be scheduled within a TTI is 4. The scheduling priority order of UE#1, UE#2, UE#3, UE#4 and UE#5 is: UE#1>UE#2>UE#3>UE#4>UE#5.

[0061] In TTI0, UE#1, UE#2, UE#3, UE#4, and UE#5 all have uplink data to send. Network device 110 determines, based on the scheduling priority, that the UEs to be scheduled in TTI0 are UE#1, UE#2, UE#3, and UE#4. Therefore, network device 110 allocates RBs corresponding to the full bandwidth to UE#1, UE#2, UE#3, and UE#4 in equal proportions. That is, network device 110 may determine the number of RBs to be allocated to each of UE#1, UE#2, UE#3, and UE#4 (e.g., 273 / 4≈68) based on the number of RBs corresponding to the full bandwidth (e.g., 273), the first ratio (i.e., 1:1:1:1), and the number of UEs to be scheduled in TTI0 (e.g., 4).

[0062] UE#3 has no uplink data to send during TTI1 and TTI2. Therefore, network device 110 determines, based on scheduling priorities, that UEs to be scheduled during TTI1 and TTI2 are UE#1, UE#2, UE#4, and UE#5. Consequently, network device 110 allocates RBs corresponding to the full bandwidth to UE#1, UE#2, UE#4, and UE#5 in equal proportions.

[0063] In TTI3, UE#2 and UE#3 have no uplink data to send, so network device 110 determines, based on the scheduling priority, that UEs to be scheduled in TTI3 are UE#1, UE#4, and UE#5. Therefore, network device 110 can allocate RBs corresponding to the full bandwidth to UE#1, UE#4, and UE#5 in equal proportions. That is, network device 110 can determine the number of RBs to be allocated to each of UE#1, UE#4, and UE#5 (e.g., 273 / 3≈91) based on the number of RBs corresponding to the full bandwidth (e.g., 273), the first ratio (i.e., 1:1:1), and the number of UEs to be scheduled in TTI3 (e.g., 3). In TTI3, because the number of RBs required by UE#1 (i.e., the second number, e.g., 68) is less than the number of RBs allocated in equal proportion among UE#1, UE#4, and UE#5 (i.e., the first number), network device 110 allocates the required number of RBs (e.g., 68 RBs) to UE#1 and then allocates the remaining RBs (e.g., 205 RBs) in equal proportion among UE#4 and UE#5. In TTI3, for example, the number of RBs required by UE#4 (i.e., the second number, e.g., 120) is greater than the number of RBs allocated in equal proportion among UE#4 and UE#5 (i.e., the first number, e.g., 102), network device 110 allocates the number of RBs determined in equal proportion (e.g., 102 RBs) to UE#4.

[0064] By using the possible implementation method shown in FIG4 , users at far-end uplink coverage can obtain power aggregation gain, SINR will be improved, and the user uplink experienced rate will increase, thus achieving scheduling fairness.

[0065] Alternatively, in some possible implementations, the network device 110 may determine the ratio between the numbers of uplink frequency domain resources required by the scheduled terminal devices within one time unit as the first ratio. This will be described with reference to FIG5 .

[0066] Figure 5 shows a schematic diagram of uplink frequency domain resource allocation in MU-MIMO mode according to some other possible implementations of the present application. In the example of Figure 5, in MU-MIMO mode, the network device 110 determines the ratio between the number of RBs required by the scheduled UEs within one TTI as a first ratio. Furthermore, the network device 110 allocates the available RBs within a TTI to the UEs to be scheduled within the TTI according to the first ratio. The available RBs within a TTI include RBs corresponding to the full bandwidth (for example, 273 RBs), and the maximum number of UEs to be scheduled within a TTI is 4. The scheduling priority order of UE#1, UE#2, UE#3, UE#4 and UE#5 is: UE#1>UE#2>UE#3>UE#4>UE#5.

[0067] In TTI0, UE#1, UE#2, UE#3, UE#4, and UE#5 all have uplink data to send. Network device 110 determines, based on scheduling priority, that UE#1, UE#2, UE#3, and UE#4 will be scheduled in TTI0. The number of RBs required by UE#1, UE#2, UE#3, and UE#4 in TTI0 is 200, 100, 100, and 100, respectively. Therefore, the ratio of the number of RBs required by UE#1, UE#2, UE#3, and UE#4 in TTI0 is 2:1:1:1. Therefore, network device 110 allocates RBs corresponding to the full bandwidth to UE#1, UE#2, UE#3, and UE#4 in a ratio of 2:1:1:1. That is, the network device 110 can determine that the number of RBs to be allocated to UE#1, UE#2, UE#3, and UE#4 are 109, 54, 54, and 54, respectively, based on the number of RBs corresponding to the full bandwidth (e.g., 273), the first ratio (i.e., 2:1:1:1), and the number of UEs to be scheduled within TTI0 (e.g., 4).

[0068] In TTI1, UE#1, UE#2, UE#4, and UE#5 all have uplink data to send, while UE#3 has no uplink data to send. Network device 110 determines, based on scheduling priority, that UE#1, UE#2, UE#4, and UE#5 will be scheduled in TTI1. The number of RBs required by UE#1, UE#2, UE#4, and UE#5 in TTI1 is 200, 100, 100, and 100, respectively. Therefore, the ratio of the number of RBs required by UE#1, UE#2, UE#4, and UE#5 in TTI1 is 2:1:1:1. Therefore, network device 110 allocates RBs corresponding to the full bandwidth to UE#1, UE#2, UE#4, and UE#5 in a ratio of 2:1:1:1. That is, the network device 110 can determine that the number of RBs to be allocated to UE#1, UE#2, UE#4, and UE#5 are 109, 54, 54, and 54, respectively, based on the number of RBs corresponding to the full bandwidth (e.g., 273), the first ratio (i.e., 2:1:1:1), and the number of UEs to be scheduled within TTI1 (e.g., 4).

[0069] In TTI2, UE#1, UE#2, UE#3, and UE#4 all have uplink data to send, while UE#5 has no uplink data to send. Network device 110 determines, based on scheduling priority, that UE#1, UE#2, UE#3, and UE#4 will be scheduled in TTI2. The number of RBs required by UE#1, UE#2, UE#3, and UE#4 in TTI2 is 200, 100, 100, and 100, respectively. Therefore, the ratio of the number of RBs required by UE#1, UE#2, UE#3, and UE#4 in TTI2 is 2:2:1:1. Therefore, network device 110 allocates RBs corresponding to the full bandwidth to UE#1, UE#2, UE#3, and UE#4 in a ratio of 2:2:1:1. That is, the network device 110 can determine that the number of RBs to be allocated to UE#1, UE#2, UE#3, and UE#4 are 91, 91, 45, and 45, respectively, based on the number of RBs corresponding to the full bandwidth (e.g., 273), the first ratio (i.e., 2:2:1:1), and the number of UEs to be scheduled within TTI2 (e.g., 4).

[0070] Similarly, within TTI3, the network device 110 can determine that the number of RBs to be allocated to UE#1, UE#3, UE#4, and UE#5 are 91, 91, 45, and 45, respectively, based on the number of RBs corresponding to the full bandwidth (e.g., 273), the first ratio (i.e., 2:2:1:1), and the number of UEs to be scheduled within TTI3 (e.g., 4).

[0071] By using the possible implementation method shown in FIG5 , users at distant points in uplink coverage can obtain power aggregation gain, SINR can be improved, and the user uplink experienced rate can be increased.

[0072] Alternatively, in some possible implementations, the first ratio can be determined based on the scheduling priority of the scheduled terminal device. In other words, the scheduling priority of the terminal device can be quantified as a fixed ratio (i.e., the first ratio), and the network device 110 can allocate the corresponding uplink frequency domain resources to the terminal device according to this fixed ratio. In this possible implementation, the first ratio can be predefined or predetermined. For example, the scheduling priority order of UE#1, UE#2, UE#3, UE#4 and UE#5 is: UE#1>UE#2>UE#3>UE#4>UE#5. Based on the scheduling priority, the first ratio can be predefined as 2:1:1:1:1. Therefore, in MU-MIMO mode, the network device 110 can allocate the available RBs within a TTI to the UEs to be scheduled within the TTI according to the ratio. In this way, users with far-reaching uplink coverage can obtain power aggregation gain, the SINR will be improved, the user uplink experience rate will increase, and scheduling fairness will be achieved.

[0073] It can be understood that in the examples of Figures 4 and 5, if there are special types of terminal devices such as control planes in cell 112, then such terminal devices will not participate in the uplink frequency domain resource allocation according to the first ratio. For example, the network device 110 can determine the RBs required by such terminal devices in the RBs corresponding to the full bandwidth and allocate them to such terminal devices on demand. Furthermore, the network device 110 can allocate the remaining RBs to the terminal devices to be scheduled within one TTI according to the first ratio. In this way, users with far-reaching uplink coverage can obtain power aggregation gain, the SINR will be improved, the user uplink experienced rate will increase, and scheduling fairness will be achieved.

[0074] FIG6 shows a block diagram of an example communication device 600 according to an implementation of the present application. The example communication device 600 can be used to implement a communication device, such as the network device 110 in FIG1 . Therefore, the example communication device 600 may also be referred to herein as the example communication device 600. As shown in FIG6 , the example communication device 600 may include a processor 610 and a memory 620 coupled to the processor 610. The memory 620 stores computer program instructions 625. In addition, the example communication device 600 may also include a communication module 630 coupled to the processor 610. The communication module 630 may be configured for bidirectional communication and may have at least one cable, optical cable, wireless interface, etc., to facilitate communication. A communication interface may represent any interface for communicating with other devices.

[0075] The processor 610 may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The example communication device 600 may have multiple processors, such as application-specific integrated circuit chips that are driven in time by a clock synchronized with a main processor. The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memories (ROMs), electrically erasable programmable read-only memories (EPROMs), flash memory, hard disks, compressed disks (CDs), digital versatile disks (DVDs), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memories (RAMs) or other volatile memories that are not persistent during power outages. The computer program instructions 625 may include computer executable instructions that are executable by the associated processor 610. In some embodiments, the computer program instructions 625 may be stored in a ROM of the memory 620. The processor 610 may perform various appropriate actions and processes by loading the memory 620 into the RAM of the memory 620. Implementations of the present disclosure may be implemented by the computer program instructions 625 to cause the example communication device 600 to perform any method or process of the present disclosure as discussed above with reference to FIG5. Of course, implementations of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0076] In some implementations, the computer program instructions 625 may be tangibly embodied in a computer-readable medium. Such a computer-readable medium may be included in the example communication device 600 (e.g., the memory 620) or in other storage devices accessible to the example communication device 600. The example communication device 600 may read the computer program instructions 625 from the computer-readable medium into the RAM of the memory 620 for execution. The computer-readable medium may include various tangible non-volatile storage devices, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0077] In general, the various example implementations of the present application can be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Certain aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be performed by a controller, microprocessor or other computing device. For example, in some implementations, the various examples of the present application (such as methods, devices or equipment) can be implemented in part or in whole on a computer-readable medium. When various aspects of the implementation of the present application are illustrated or described as block diagrams, flow charts or using some other graphical representations, it will be understood that the blocks described herein, devices, systems, techniques or methods can be implemented as non-limiting examples in hardware, software, firmware, dedicated circuits or logic, general hardware or controller or other computing device, or some combination thereof.

[0078] The present application also provides at least one computer program product stored on a non-transient computer-readable storage medium. The computer program product includes computer-executable instructions, such as computer-executable instructions included in a program module executed in a device on a physical or virtual processor of the target, to perform the example method or example process 300 described above with respect to FIG. In general, program modules may include routines, programs, libraries, objects, classes, components, data structures, etc., which perform specific tasks or implement specific abstract data structures. In various implementations, the functions of the program modules may be merged or split between the described program modules. The computer-executable instructions for the program modules may be executed in a local or distributed device. In a distributed device, the program modules may be located in both local and remote storage media.

[0079] The program code for realizing the method for the present application can be written in one or more programming languages.These computer program codes can be provided to the processor of general-purpose computer, special-purpose computer or other programmable data processing device, make program code when being executed by computer or other programmable data processing device, cause the function / operation of stipulating in flow chart and / or block diagram to be implemented.Program code can be fully on computer, partly on computer, as independent software package, partly on computer and partly on remote computer or fully on remote computer or server and execute.In the context of the present application, computer program code or related data can be carried by any suitable carrier, so that equipment, device or processor can perform various processes and operation described above.The example of carrier comprises signal, computer readable medium, etc.

[0080] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More detailed examples of machine-readable storage media include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0081] In addition, although the operations are depicted in a particular order, this should not be understood as requiring that such operations be completed in the particular order shown or in a sequential order, or that all illustrated operations be performed to obtain the desired result. In some cases, multitasking or parallel processing can be beneficial. Similarly, although the above discussion includes certain specific implementation details, this should not be interpreted as limiting the scope of any application or claim, but rather as a description of a specific implementation that can be directed to a particular application. Certain features described in the context of separate implementations in this specification may also be integrated and implemented in a single implementation. Conversely, the various features described in the context of a single implementation may also be implemented separately in multiple implementations or in any suitable subcombination.

[0082] Although the subject matter has been described in language specific to structural features and / or methodological acts, it should be understood that the subject matter defined in the appended claims is not limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A communication method, characterized in that: The method comprises: In a multi-user multiple-input multiple-output mode, determining that a proportion of terminal devices located at an edge of a cell exceeds a threshold; and The available uplink frequency domain resources within a time unit are allocated to the terminal devices to be scheduled within the time unit according to the scheduling priority and the first ratio.

2. The method according to claim 1, characterized in that The first ratio includes an equal ratio.

3. The method according to claim 1 or 2, characterized in that: The allocating the available uplink frequency domain resources in a time unit to the terminal devices to be scheduled in the time unit according to the scheduling priority and the first ratio includes: Determine, based on the number of available uplink frequency domain resources, the first ratio, and the number of terminal devices to be scheduled within the time unit, a first number of uplink frequency domain resources to be allocated to a first terminal device among the scheduled terminal devices; If the second number of uplink frequency domain resources required by the first terminal device is less than the first number, allocating the second number of uplink frequency domain resources to the first terminal device; and If the second number is greater than the first number, the first number of uplink frequency domain resources is allocated to the first terminal device.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: The ratio between the numbers of uplink frequency domain resources required by the scheduled terminal devices within the time unit is determined as the first ratio.

5. The method according to any one of claims 1 to 4, characterized in that: The first ratio is determined based on the scheduling priority of the scheduled terminal device.

6. A communication device, characterized in that: The method comprises means for performing the method according to any one of claims 1 to 5.

7. A communication device, characterized in that: include: at least one processor; as well as At least one memory, the at least one memory is coupled to the at least one processor and stores instructions for execution by the at least one processor, the instructions causing the communication device to implement the method according to any one of claims 1 to 5 when executed by the at least one processor.

8. A computer-readable storage medium, characterized in that: Computer program instructions are stored; when the computer program instructions are executed by a processor, the method according to any one of claims 1 to 5 is implemented.

9. A computer program product, characterized in that The computer program product comprises computer instructions, and when the computer instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 5.

10. A system, characterized in that: The method comprises at least one communication device, wherein the at least one communication device is configured to execute the method according to any one of claims 1 to 5.

Images