Resource Scheduling Method and Usage Method, Network Device, Terminal Device, and Medium
The proposed resource scheduling method optimizes resource allocation in 5G networks by using resource occupancy identifier information to improve the utilization of resource blocks within each resource block group, addressing the issue of resource waste in conventional methods.
Patent Information
- Application Number
- JP2024570858
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-06-24
- Filing Date
- 2023-05-06
- Publication Date
- 2025-06-12
- Estimated Expiration
- 2043-05-06
AI Technical Summary
Conventional resource scheduling methods in 5G networks fail to fully utilize resource blocks within each resource block group, leading to resource waste when terminal devices from different application scenarios share the same network.
A resource scheduling method that involves obtaining resource setting information for different types of terminal devices, generating resource occupancy identifier information, and transmitting it to the terminal devices to execute resource scheduling based on the occupancy status, thereby optimizing resource allocation within overlapping resource block groups.
This method ensures full utilization of resource blocks within each resource block group, reduces resource waste, and improves the overall resource block utilization rate.
Smart Images

Figure 2025518256000001_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate to the field of communication technologies, and in particular, to a resource scheduling method, a resource usage method, a network device, a terminal device, and a storage medium.
Background Art
[0002] With the wide use of the fifth-generation wireless communication network New Radio (5G NR), the industrial application fields of 5G are also expanding more and more. 5G is generally divided into three application scenarios: Enhanced Mobile Broadband (eMBB), Ultra-reliable and Low Latency Communications (uRLLC), and Massive Machine Type Communication (mMTC). In addition, in order to better meet the specific requirements of intermediate Internet of Things applications such as industrial wireless sensors, video monitors, and wearable devices for reducing device complexity and cost, reducing size, and reducing energy consumption, 3GPP (registered trademark) defines a Reduced Capability (RedCap) application scenario.
[0003] In the process of deploying a 5G network, when terminal devices applied to the above different application scenarios are deployed in the same 5G network and the terminal devices applied to different application scenarios are different types of terminal devices, the conventional resource scheduling method cannot fully utilize the resource blocks within each resource block group, and further causes resource waste.
Summary of the Invention
Problems to be Solved by the Invention
[0004] Embodiments of the present disclosure mainly aim to provide a resource scheduling method, a resource usage method, a network device, a terminal device, and a storage medium that fully utilize resource blocks within each resource block group and improve the utilization rate of resource blocks within the resource block group.
Means for Solving the Problems
[0005] An embodiment of the present disclosure is a resource scheduling method applied to a network device, including: obtaining resource setting information corresponding to a first type of terminal device and a second type of terminal device; generating resource occupancy identifier information based on the obtained resource setting information, and transmitting the resource occupancy identifier information to the first type of terminal device, so that the first type of terminal device executes resource scheduling based on the resource occupancy identifier information, where the resource occupancy identifier information indicates the resource block occupancy status within a resource block group that overlaps between the first type of terminal device and the second type of terminal device.
[0006] An embodiment of the present disclosure is a resource usage method applied to a terminal device, including: receiving resource occupancy identifier information transmitted by a network device, where the resource occupancy identifier information is generated by the network device based on resource setting information corresponding to a first type of terminal device and a second type of terminal device, and indicates the resource block occupancy status within a resource block group that overlaps between the first type of terminal device and the second type of terminal device; and using resources based on the resource occupancy identifier information.
[0007] An embodiment of the present disclosure provides a network device including a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection communication between the processor and the memory. When the computer program is executed by the processor, steps of a resource scheduling method applicable to the network device according to any one of the descriptions in the specification of the present disclosure are realized.
[0008] An embodiment of the present disclosure provides a terminal device including a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection communication between the processor and the memory. When the computer program is executed by the processor, steps of a resource scheduling method applicable to the terminal device according to any one of the descriptions in the specification of the present disclosure are realized.
[0009] An embodiment of the present disclosure provides a storage medium readable by a computer, in which one or more programs are stored. The one or more programs are executed by one or more processors to realize steps of a resource scheduling method applicable to the network device according to any one of the descriptions in the specification of the present disclosure or steps of a resource usage method applicable to the terminal device according to any one of the descriptions.
[0010] To more clearly explain the technical means in the embodiments of the present application, the drawings required for use in the following description of the embodiments are briefly described below. Obviously, the drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings based on these drawings without creative labor.
Brief Description of the Drawings
[0011]
Figure 1
Figure 2a
Figure 2b
Figure 2c
Figure 2d
Figure 3
Figure 4
Figure 5
Figure 6
Embodiments for Carrying Out the Invention
[0012] Hereinafter, with reference to the drawings in the embodiments of the present disclosure, the technical means in the embodiments of the present disclosure will be clearly and completely described. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, not all of them. Based on the embodiments of the present disclosure, all other embodiments obtained on the premise that those skilled in the art do not perform creative labor belong to the protection scope of the present disclosure.
[0013] The flowchart shown in the drawings is only an illustrative explanation and does not necessarily include all contents and operations / steps, nor does it necessarily execute in the described order. For example, some operations / steps can be decomposed, combined, or partially combined, so the actual execution order may vary according to the actual situation.
[0014] Note that the terms used in the specification of this disclosure are for the purpose of describing specific embodiments only and are not intended to limit this disclosure. As used in the specification of this disclosure and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "one", and "the" are intended to include the plural forms as well.
[0015] First, to better understand the technical means of the embodiments of this application, the technical problems existing in the prior art are introduced below.
[0016] 5G includes multiple application scenarios such as eMBB, uRLLC, mMTC, and RedCap. Generally, the types of terminal devices operating in different application scenarios are also different. In the existing resource scheduling method, since multiple terminal devices with different functional characteristics operate on the same 5G network, even if different carrier bandwidth parts (Bandwidth Part, BWP) are used by each type of terminal device, the resource blocks within each resource block group cannot be fully utilized. That is, due to the problem of resource allocation fragmentation, the resource blocks within the resource block group cannot be fully utilized, resulting in waste of resources.
[0017] Taking the operation of eMBB UE and RedCap UE on the same 5G network as an example, peak rate is an important indicator of the performance of terminal devices. Since the channel bandwidth supported by eMBB UE can reach 100MHz, it can support a high peak rate. When RedCap UE and eMBB UE share the same carrier resources, if the BWP of RedCap UE is in the middle of the carrier, the maximum continuously allocable resources of eMBB UE will decrease from 100MHz to 40MHz, and the peak rate may decrease by up to 60%. Considering the bandwidth limitation of RedCap UE, the impact of resource fragmentation, and the avoidance of resource congestion, an independent initial uplink BWP is introduced for RedCap.
[0018] The network device may be configured such that the RedCap UE and the non-RedCap UE share the same initial uplink BWP, or one independent initial uplink BWP may be configured for the RedCap UE in the system information block (SIB1). The independent initial uplink BWP may be used in the initial access process or after the initial access process. On the other hand, since the bandwidth of the RedCap UE is narrow, when sharing the initial uplink BWP with the non-RedCap UE, the problem that the BWP bandwidth of the non-RedCap UE can only be set to be equal to or less than the bandwidth of the RedCap UE can be avoided. On the other hand, the network device can alleviate the problem of fragmentation caused by RedCap to a certain extent by setting the BWP of the RedCap UE at a position close to the edge of the carrier, but still cannot completely solve the problem of fragmentation of resource allocation, and the resources in the fragments cannot be used by any terminal device, resulting in a certain amount of resource waste.
[0019] Embodiments of the present disclosure provide a resource scheduling method, a terminal device, and a storage medium. The method may be applied to a network device, thereby making full use of the resource blocks in each resource block group, avoiding waste of resources, and improving the utilization rate of the resource blocks in the resource block group.
[0020] FIG. 1 is a flowchart of a resource scheduling method according to an embodiment of the present disclosure. As shown in FIG. 1, the resource scheduling method can make full use of the resource blocks in each resource block group and avoid waste of resources. Specifically, the resource scheduling method may be applied to a network device, and the network device may be a device such as a base station or a gateway.
[0021] As shown in FIG. 1, the resource scheduling method may include steps S101 to S102.
[0022] In step S101, resource setting information corresponding to the first type of terminal device and the second type of terminal device is obtained.
[0023] The resource setting information may include the bandwidth of the carrier bandwidth portion and the resource usage status of the carrier bandwidth portion. The first type of terminal device is a terminal device that performs resource scheduling. There are overlapping resource blocks between the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device and the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device. The bandwidth of the carrier bandwidth portion may be determined by the resource block range supported by the carrier bandwidth portion. In one specific embodiment, the larger the resource block range supported by the carrier bandwidth portion, the wider the corresponding carrier bandwidth portion bandwidth.
[0024] In one specific embodiment, the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device may be wider than the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device, or may be narrower than the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device. As long as there are overlapping resource blocks between the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device and the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device. Generally, in order to perform resource scheduling, it is necessary to send resource occupancy identifier information to the first type of terminal device. Therefore, the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device is wide. Preferably, the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device is wider than the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device.
[0025] Exemplarily, when there are a first terminal device and a second terminal device, resource configuration information corresponding to the first terminal device and the second terminal device may be obtained first. The resource configuration information includes the bandwidth of the carrier bandwidth portion, and it is determined whether there are resource blocks where the bandwidth of the carrier bandwidth portion of the first terminal device overlaps with the bandwidth of the carrier bandwidth portion of the second terminal device. When there are resource blocks where the bandwidth of the carrier bandwidth portion of the first terminal device overlaps with the bandwidth of the carrier bandwidth portion of the second terminal device, the types of the first terminal device and the second terminal device are determined. When there are no resource blocks where the bandwidth of the carrier bandwidth portion of the first terminal device overlaps with the bandwidth of the carrier bandwidth portion of the second terminal device, there is no need to use the resource scheduling method according to the embodiments of the present application to perform resource scheduling.
[0026] Exemplarily, generally, since the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device is wider than the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device, first, resource configuration information corresponding to the first terminal device and the second terminal device can be obtained. The resource configuration information includes the bandwidth of the carrier bandwidth portion, and it is determined whether the bandwidth of the carrier bandwidth portion of the first terminal device is wider than the bandwidth of the carrier bandwidth portion of the second terminal device. When the bandwidth of the carrier bandwidth portion of the first terminal device is wider than the bandwidth of the carrier bandwidth portion of the second terminal device, it is determined that the first terminal device is the first type of terminal device and the second terminal device is the second type of terminal device. When the bandwidth of the carrier bandwidth portion of the first terminal device is not wider than the bandwidth of the carrier bandwidth portion of the second terminal device, it is determined that the second terminal device is the first type of terminal device and the first terminal device is the second type of terminal device.
[0027] Exemplarily, the first type of terminal device and the second type of terminal device respectively correspond to terminal devices applied to different application scenarios. The peak rate is an important indicator of the performance of the terminal device. Since the channel bandwidth supported by the eMBB UE can reach 100 MHz, it can support a high peak rate. The bandwidth of the carrier bandwidth portion corresponding to the eMBB UE is wide. Therefore, the first type of terminal device may generally be an eMBB UE. Since the first type of terminal device is an eMBB UE, the second type of terminal device may include one or more of RedCap UE, uRLLC UE, and mMTC UE.
[0028] Exemplarily, the first type of terminal device may be a RedCap UE, a uRLLC UE, or an mMTC UE. In this case, the second type of terminal device may be determined based on the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device. When the first type of terminal device is a uRLLC UE and the bandwidth of the carrier bandwidth portion corresponding to the uRLLC UE is wider than the bandwidth of the carrier bandwidth portion corresponding to the RedCap UE, the second type of terminal device is a RedCap UE.
[0029] In S102, based on the obtained resource configuration information, resource occupancy identifier information is generated, and by sending the resource occupancy identifier information to the first type of terminal device, the first type of terminal device executes resource scheduling based on the resource occupancy identifier information. The resource occupancy identifier information indicates the resource block occupancy status within the overlapping resource block group of the first type of terminal device and the second type of terminal device.
[0030] The resource occupancy identifier information indicates the resource block occupancy status within the overlapping resource block groups of the first type of terminal device and the second type of terminal device. The resource block occupancy status indicates whether there are resource blocks that are not occupied within the overlapping resource block groups. A resource block (RB) is a unit in which service resources occupy bandwidth. A resource block group (RBG) includes a plurality of resource blocks. Specifically, the granularity size of each RBG may be determined based on the size of the entire BWP bandwidth resource. Generally, the wider the bandwidth, the coarser the granularity. In the prior art, the resource blocks within a resource block group are either all allocated to the same type of UE or not allocated at all. If a certain resource block within the resource block group is not allocated for some reason, all resources are not allocated.
[0031] In this embodiment, obtain the resource configuration information corresponding to the first type of terminal device and the second type of terminal device, generate resource occupancy identifier information based on the resource configuration information, and send the resource occupancy identifier information to the first type of terminal device. As a result, the first type of terminal device executes resource scheduling based on the resource occupancy identifier information, thereby fully utilizing the resource blocks within each resource block group, avoiding waste of resources, and improving the utilization rate of the resource blocks within the resource block group.
[0032] In one specific embodiment, fill the resource occupancy identifier information into downlink control information (DCI), and send the downlink control information to the first type of terminal device. Thereby, the first type of terminal device analyzes the downlink control information to obtain the resource occupancy identifier information, and executes resource scheduling based on the resource occupancy identifier information.
[0033] In some embodiments, the resource configuration information further includes the resource usage status of the carrier bandwidth portion. Based on the resource usage status of the carrier bandwidth portion, it is determined whether the first type of terminal device and the second type of terminal device use the same resource block group. When the first type of terminal device and the second type of terminal device use the same resource block group, based on the bandwidth of the carrier bandwidth portion, the resource block occupancy status within the same resource block group is determined, and resource occupancy identifier information is generated based on the resource block occupancy status within the same resource block group. Thereby, the resource block occupancy status within each resource block group can be accurately determined, and the first type of terminal device can execute resource scheduling based on the resource block occupancy status within each resource block group.
[0034] The resource usage status of the carrier bandwidth portion indicates the resource block group required by the first type of terminal device.
[0035] Exemplarily, as shown in FIGS. 2a and 2b, assuming that two BWPs with a total of 24 RBs are configured, each RBG contains 4 RBs, the RB range of BWP0 is 0 to 23 (a total of 24 RBs), and the eMBB UE operates on BWP0. The RB range of BWP1 is 7 to 17 (a total of 11 RBs), and the RedCap UE operates on BWP1. As shown in FIG. 2a, at time T1, in this case, the RB ranges of the resource block groups required by the eMBB UE are 0 to 3 and 16 to 19. As shown in FIG. 2b, at time T2, in this case, the RB ranges of the resource block groups required by the eMBB UE are 0 to 3, 8 to 11, and 16 to 19. Specifically, bits can be used to indicate the resource block groups required by the terminal device (when it is indicated that the terminal device needs to use the resource block group, the information bit corresponding to the resource block group indicates 1, and when it is indicated that the terminal device does not need to use the resource block group, the information bit corresponding to the resource block group indicates 0).
[0036] In one specific embodiment, based on the resource usage status of the carrier bandwidth part, it is determined whether the first type of terminal device and the second type of terminal device use the same resource block group. When the first type of terminal device and the second type of terminal device use the same resource block group, based on the bandwidth of the carrier bandwidth part, the resource block occupancy status within the same resource block group is determined. When the first type of terminal device and the second type of terminal device do not use the same resource block group, the first type of terminal device and the second type of terminal device can use the resource blocks within the resource block groups corresponding to them respectively, without wasting resources.
[0037] Exemplarily, as shown in FIG. 2a, in this case, the RB range of the resource block group required for the eMBB UE is 0 to 3 and 16 to 19, and the RB range of the RedCap UE is 7 to 17. That is, the RB range of the resource block group used is 4 to 7, 8 to 11, 12 to 15, and 16 to 19. Therefore, the eMBB UE and the RedCap UE need to use the same resource block group. That is, in this case, there is an overlapping resource block group between the first type of terminal device and the second type of terminal device. As shown in FIG. 2c, at time T3, in this case, the RB range of the resource block group required for the eMBB UE is 0 to 3 and 20 to 23, and the RB range of the RedCap UE is 7 to 17. Therefore, the eMBB UE and the RedCap UE do not need to use the same resource block group. That is, in this case, there is no overlapping resource block group between the first type of terminal device and the second type of terminal device.
[0038] In some embodiments, based on the bandwidth of the carrier bandwidth portion, it is determined whether there are resource blocks not occupied in the same resource block group. If there are resource blocks not occupied in the same resource block group, the unoccupied resource blocks are determined as target resource blocks, and based on the target resource blocks, the resource block occupancy status within the same resource block group is determined. Thereby, the target resource blocks can be accurately determined so that the first type of terminal device can execute resource scheduling using the target resource blocks.
[0039] The target resource blocks are resource blocks not occupied in the overlapping resource block group between the first type of terminal device and the second type of terminal device.
[0040] In one specific embodiment, based on the bandwidth of the carrier bandwidth portion, it is determined whether there are resource blocks that are not occupied in the same resource block group. If there are no resource blocks that are not occupied in the same resource block group, it indicates that all the resource blocks in the overlapping resource block group are occupied and there are no unoccupied resource blocks. In this case, by setting the bit to 0, it indicates that there are no target resource blocks in each resource block group at this time. If there are resource blocks that are not occupied in the same resource block group, it indicates that the resource blocks in the overlapping resource block group are partially occupied, and the unoccupied resource blocks are determined as target resource blocks. In this case, by setting the bit to 1, it indicates that there are target resource blocks in each resource block group at this time.
[0041] Exemplarily, as shown in FIG. 2a, in this case, the eMBB UE and the RedCap UE need to use a resource block group with an RB range of 16 to 19. In the prior art, since all the resource blocks in the resource block group can only be assigned to the same type of UE, in this case, the resource block group with an RB range of 16 to 19 can only be assigned to the RedCap UE. However, since the RedCap UE does not use two RBs of 18 and 19, it causes waste of resources. Therefore, based on the bandwidth of the carrier bandwidth portion, the resource block occupancy status in the overlapping resource block group can be determined. Since the RB range corresponding to the bandwidth indication of the carrier bandwidth portion of the RedCap UE is 7 to 17, the resource block occupancy status in the overlapping resource block group can be determined. Specifically, the RedCap UE actually only occupies two RBs of 16 and 17 and does not occupy two RBs of 18 and 19. That is, since the two RBs of 18 and 19 are target resource blocks, resource occupancy identifier information is generated based on the resource block occupancy status in the overlapping resource block group.
[0042] In some embodiments, when the second type of terminal device includes two or more types of terminals, it is equivalent to further including a third type of terminal device, and the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device is wider than the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device and the bandwidth of the carrier bandwidth portion corresponding to the third type of terminal device.
[0043] In one specific embodiment, obtain the resource configuration information corresponding to the first type of terminal device, the second type of terminal device, and the third type of terminal device, generate resource occupancy identifier information based on the resource configuration information, and send the resource occupancy identifier information to the first type of terminal device, so that the first type of terminal device executes resource scheduling based on the resource occupancy identifier information, and the resource occupancy identifier information indicates the resource block occupancy status in the overlapping resource block group of the first type of terminal device and the second type of terminal device and / or the third type of terminal device.
[0044] Exemplarily, as shown in FIG. 2d, assuming that three BWPs and a total of 24 RBs are set, each RBG includes 4 RBs, the RB range of BWP0 is 0 to 23 (a total of 24 RBs), the eMBB UE operates on BWP0, the RB range of BWP1 is 7 to 17 (a total of 11 RBs), the RedCap UE operates on BWP1, the RB range of BWP2 is 3 to 6 (a total of 4 RBs), and the uRLLC UE operates on BWP2.
[0045] As shown in Fig. 2d, at time T4, in this case, the RB ranges of the resource block groups required for eMBB UEs are 0 - 3, 16 - 19, and 20 - 23, the RB range of the RedCap UE is 7 - 17, and the RB range of the uRLLC UE is 3 - 6. Therefore, eMBB UEs, RedCap UEs, and uRLLC UEs all need to use the same resource block group, that is, there are overlapping resource block groups among the first type of terminal device, the second type of terminal device, and the third type of terminal device. Therefore, based on the bandwidth of the carrier bandwidth portion, the resource block occupancy status within the overlapping resource block group can be determined. Since the RB range corresponding to the bandwidth indication of the carrier bandwidth portion of the RedCap UE is 7 - 17, the resource block occupancy status within the overlapping resource block group can be determined. Specifically, the RedCap UE actually occupies only two RBs, 16 and 17, and does not occupy the two RBs, 18 and 19. That is, the two RBs, 18 and 19, are the target resource blocks. Similarly, the uRLLC UE actually occupies only two RBs, 2 and 3, and does not occupy the two RBs, 0 and 1. That is, since the two RBs, 0 and 1, are the target resource blocks, resource occupancy identifier information is generated based on the resource block occupancy status within the overlapping resource block group.
[0046] In one specific embodiment, referring to FIGS. 2a to 2d, as shown in FIG. 2a, at time T1, in this case, the presence of a target resource block in each resource block group can be indicated by a bit being 1. At the same time, since the BWP corresponding to the target resource block is BWP1, the bit being 10 can indicate that at time T1, the BWP corresponding to the target resource block is BWP1. As shown in FIG. 2b, at time T2, in this case, the absence of a target resource block in each resource block group can be indicated by a bit being 0. In this case, since there is no target resource block in each resource block group, the bit being 00 can indicate that at time T2, there is no target resource block. As shown in FIG. 2c, at time T3, in this case, the absence of a target resource block in each resource block group can be indicated by a bit being 0. In this case, since there is no target resource block in each resource block group, the bit being 00 can indicate that at time T3, there is no target resource block. As shown in FIG. 2d, at time T4, in this case, the presence of a target resource block in each resource block group can be indicated by a bit being 1. In this case, since there is a target resource block in each resource block group, the bit being 11 can indicate that at time T4, the BWP corresponding to the target resource block is BWP1 and BWP2.
[0047] As shown in Table 1, the corresponding resource occupancy identifier information at each time can be generated.
[0048]
Table 1
[0049] Finally, the resource occupancy identifier information is transmitted to the first type of terminal device so that the first type of terminal device executes resource scheduling based on the resource occupancy identifier information.
[0050] FIG. 3 is a flowchart of a resource usage method according to an embodiment of the present disclosure. As shown in FIG. 3, the resource usage method can fully utilize the resource blocks within each resource block group and avoid waste of resources. Specifically, the resource usage method can be applied to a terminal device, and the terminal device may be, but is not limited to, a smartphone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc.
[0051] As shown in FIG. 3, the resource usage method includes steps S201 to S202.
[0052] In step S201, resource occupancy identifier information transmitted by a network device is received. The resource occupancy identifier information is generated by the network device based on resource setting information corresponding to a first type of terminal device and a second type of terminal device, and indicates the resource block occupancy status in an overlapping resource block group of the first type of terminal device and the second type of terminal device.
[0053] The resource usage method may be applied to a first type of terminal device. There are overlapping resource blocks between the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device and the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device. In one specific embodiment, the resource occupancy identifier information may be generated by steps S101 to S102.
[0054] In step S202, resources are used based on the resource occupancy identifier information.
[0055] Since the resource occupancy identifier information is usually set in the downlink control information, first, it is necessary to analyze and obtain the resource occupancy identifier information from the downlink control information so that the first type of terminal device can use the resources based on the resource occupancy identifier information.
[0056] In some embodiments, the resource occupancy identifier information is analyzed to obtain a target resource block. The target resource block is a resource block that is not occupied in the overlapping resource block group of the first type of terminal device and the second type of terminal device. Based on the target resource block, resources are used. Thereby, the first type of terminal device can use the resources by utilizing the target resource block, and for example, the target resource block can be accurately analyzed and obtained so that operations such as data processing can be performed.
[0057] In one specific embodiment, after receiving the resource occupancy identifier information, based on the resource occupancy identifier information, it is determined whether the bit corresponding to the indication of whether the resource is partially occupied is 1, and it is determined whether there is a target resource block. If there is a target resource block, the BWP position indication of the occupied resource is determined, and it is determined whether the BWP corresponding to the target resource block is BWP1 or BWP2, and then analyzed to obtain the target resource block. Based on the target resource block, resources are used.
[0058] Exemplarily, as shown in FIG. 2d, at time T4, the bit corresponding to the indication of whether the resource is partially occupied is 1. In this case, it is determined that there is a target resource block in each resource block group. Further, since the bit corresponding to the BWP position indication of the occupied resource is 11, it is determined that the BWP corresponding to the target resource block is BWP1 and BWP2, and the corresponding target resource blocks are found, and the resources are used by utilizing these target resource blocks.
[0059] FIG. 4 is a schematic configuration block diagram of a network device according to an embodiment of the present disclosure. As shown in FIG. 4, the network device 300 may include a processor 301 and a memory 302, and the processor 301 and the memory 302 are connected by a bus 303, and the bus is, for example, an I2C (Inter-integrated Circuit) bus.
[0060] In one exemplary embodiment, the processor 301 provides computing and control capabilities and can support the operation of the entire terminal device. The processor 301 may be a central processing unit (CPU), and the processor 301 may be another general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or another programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or any general processor, etc.
[0061] In one specific embodiment, the memory 302 may be a Flash chip, a read-only memory (ROM), a magnetic disk, an optical disk, a USB memory or a removable hard disk, etc.
[0062] Those skilled in the art will understand that the structure shown in FIG. 4 is only a block diagram of a part of the structure related to the technical means according to the embodiment of the present disclosure, and does not limit the terminal device to which the technical means according to the embodiment of the present disclosure is applied. A specific server may include more or fewer components than those shown in the figure, may be a combination of some components, or may have a different component layout.
[0063] The processor 301 executes a computer program stored in the memory, and when executing the computer program, realizes a resource scheduling method applicable to the network device according to any one of the embodiments of the present disclosure.
[0064] In one embodiment, the processor 301 executes a computer program stored in the memory, and when executing the computer program, includes steps of obtaining resource setting information corresponding to the first type of terminal device and the second type of terminal device; generating resource occupancy identifier information based on the obtained resource setting information, and transmitting the resource occupancy identifier information to the first type of terminal device, so that the first type of terminal device executes resource scheduling based on the resource occupancy identifier information, where the resource occupancy identifier information indicates the resource block occupancy status in the overlapping resource block group of the first type of terminal device and the second type of terminal device.
[0065] In one embodiment, the resource setting information includes the bandwidth of the carrier bandwidth portion, and there are overlapping resource blocks between the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device and the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device.
[0066] In one embodiment, the resource configuration information further includes the resource usage status of the carrier bandwidth portion. When the processor 301 realizes generating resource occupancy identifier information based on the resource configuration information, it includes the steps of determining, based on the resource usage status of the carrier bandwidth portion, whether the first type of terminal device and the second type of terminal device use the same resource block group; when the first type of terminal device and the second type of terminal device use the same resource block group, determining the resource block occupancy status within the same resource block group based on the bandwidth of the carrier bandwidth portion; and generating resource occupancy identifier information based on the resource block occupancy status within the same resource block group.
[0067] In one embodiment, when the processor 301 realizes the step of determining the resource block occupancy status within the overlapping resource block group based on the bandwidth of the carrier bandwidth portion, it includes the steps of determining, based on the bandwidth of the carrier bandwidth portion, whether there is an unoccupied resource block in the same resource block group; when there is an unoccupied resource block in the same resource block group, determining the unoccupied resource block as the target resource block; and determining the resource block occupancy status within the same resource block group based on the target resource block.
[0068] In one embodiment, the first type of terminal device includes an eMBB terminal device, and the second type of terminal device includes one or more of a RedCap terminal device, a uRLLC terminal device, and an mMTC terminal device.
[0069] FIG. 5 is a schematic configuration block diagram of a terminal device according to an embodiment of the present disclosure. As shown in FIG. 5, the terminal device 400 may include a processor 401 and a memory 402. The processor 401 and the memory 402 are connected by a bus 403, which is, for example, an I2C (Inter - integrated Circuit) bus.
[0070] In one exemplary embodiment, the processor 401 provides computing and control capabilities and can support the operation of the entire terminal device. The processor 401 may be a central processing unit (CPU), or the processor 401 may be another general - purpose processor, a digital signal processor (DSP), an application - specific integrated circuit (ASIC), a field - programmable gate array (FPGA), or another programmable logic device, discrete gate, or transistor logic device, discrete hardware component, etc. The general - purpose processor may be a microprocessor or any general processor, etc.
[0071] In one specific example, the memory 402 may be a Flash chip, a read - only memory (ROM), a magnetic disk, an optical disk, a USB memory, or a removable hard disk, etc.
[0072] Those skilled in the art will understand that the structure shown in FIG. 5 is only a block diagram of some of the structures related to the technical means according to the embodiments of the present disclosure, and does not limit the terminal device to which the technical means according to the embodiments of the present disclosure is applied. A specific server may include more or fewer components than those shown in the figure, may be a combination of some components, or may have a different component layout.
[0073] The processor 404 executes a computer program stored in the memory, and when executing the computer program, realizes a resource usage method applicable to the terminal device according to any one of the embodiments of the present disclosure.
[0074] In one embodiment, the processor 401 executes a computer program stored in the memory, and when executing the computer program, receives resource occupancy identifier information transmitted by a network device, where the resource occupancy identifier information is generated by the network device based on resource setting information corresponding to a first type of terminal device and a second type of terminal device, and indicates the resource block occupancy status in a resource block group where the first type of terminal device and the second type of terminal device overlap; and executes resource scheduling based on the resource occupancy identifier information.
[0075] In one embodiment, when the processor 401 realizes the step of executing resource scheduling based on the resource occupancy identifier information, it includes the step of analyzing the resource occupancy identifier information to obtain a target resource block, where the target resource block is a resource block not occupied in the resource block group where the first type of terminal device and the second type of terminal device overlap; and executes resource scheduling based on the target resource block.
[0076] It should be clear to those skilled in the art that for the sake of convenience and brevity of description, they can refer to the corresponding process in the embodiment of the above-mentioned resource scheduling method for the specific working process of the above terminal device, and the description is omitted here.
[0077] FIG. 6 is an application scenario diagram of a resource scheduling method and a usage method according to an embodiment of the present disclosure. As shown in FIG. 6, the resource scheduling method and the usage method may be applied to a scenario in which a network device, a first type of terminal device, and a second type of terminal device are networked. Thereby, the resource blocks in each resource block group are fully utilized, and waste of resources is avoided.
[0078] In one specific embodiment, the network access method may include steps S501 to S505.
[0079] In S501, the first type of terminal device transmits resource setting information to the network device.
[0080] In S502, the second type of terminal device transmits resource setting information to the network device.
[0081] In S503, the network device generates resource occupancy identifier information based on the acquired resource setting information.
[0082] In S504, the network device transmits the resource occupancy identifier information to the first type of terminal device.
[0083] In S505, the first type of terminal device uses resources based on the resource occupancy identifier information.
[0084] Embodiments of the present disclosure further provide a computer-readable storage medium, in which one or more programs are stored. The one or more programs are executed by one or more processors to implement the steps of the resource scheduling method applied to the network device according to any one of the embodiments of the present disclosure or the steps of the resource usage method applied to the terminal device according to any one of the embodiments of the present disclosure.
[0085] The memory medium may be an internal memory unit of the terminal device described in the foregoing embodiments, for example, a hard disk or a memory of the terminal device. The memory medium may also be an external storage device of the terminal device, for example, a plug-in hard disk provided in the terminal device, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc.
[0086] A person skilled in the art can understand that all or some of the steps of the method disclosed above, the functional modules / units within the system and the device may be implemented by software, firmware, hardware, and their appropriate combinations. In the example of hardware implementation, the division between the functional modules / units described in the above description does not necessarily correspond to the division of physical components. For example, one physical component may have multiple functions, or one function or step may be jointly executed by several physical components. Some physical components or all physical components may be implemented as software executed by a processor such as a central processing unit, a digital signal processor, or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). The computer storage medium includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic tape cartridge, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that stores the desired information and is accessible by a computer. Furthermore, as known to those skilled in the art, the communication medium generally includes computer-readable instructions, data structures, program modules, or other data such as a modulated data signal like a carrier or other transmission mechanism, and may include any information distribution medium.
[0087] As used in the specification and the appended claims of the present disclosure, the term "and / or" refers to any and all possible combinations of one or more of the associated listed items, including these combinations. In this specification, the terms "comprising," "including," or any other variation thereof cover non-exclusive inclusion, such that a process, method, article, or system that includes a series of elements includes not only those elements but also other elements not expressly listed, or includes elements inherent to such a process, method, article, or system. Without further limitation, an element limited by the phrase "comprising one..." does not exclude the presence of another identical element in a process, method, article, or system that includes the element.
[0088] The numbers of the above embodiments of the present disclosure are for illustrative purposes only and do not indicate the superiority or inferiority of the embodiments. The above are only specific embodiments of the present disclosure, and the protection scope of the present disclosure is not limited thereto. Those skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present disclosure, and all of these modifications or substitutions should be included within the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.
Claims
1. A resource scheduling method applied to network devices, comprising: obtaining resource setting information corresponding to a first type of terminal device and a second type of terminal device; generating resource occupancy identifier information based on the obtained resource setting information, and transmitting the resource occupancy identifier information to the first type of terminal device, so that the first type of terminal device executes resource scheduling based on the resource occupancy identifier information, wherein the resource occupancy identifier information indicates the resource block occupancy status in the overlapping resource block group of the first type of terminal device and the second type of terminal device.
2. The method according to claim 1, wherein the resource setting information includes the bandwidth of a carrier bandwidth portion, and there are overlapping resource blocks between the bandwidth of the carrier bandwidth portion corresponding to the first type of terminal device and the bandwidth of the carrier bandwidth portion corresponding to the second type of terminal device.
3. The resource setting information further includes the resource usage status of a carrier bandwidth portion, and the step of generating resource occupancy identifier information based on the resource setting information includes: determining whether the first type of terminal device and the second type of terminal device use the same resource block group based on the resource usage status of the carrier bandwidth portion; when the first type of terminal device and the second type of terminal device use the same resource block group, determining the resource block occupancy status in the same resource block group based on the bandwidth of the carrier bandwidth portion; generating resource occupancy identifier information based on the resource block occupancy status in the same resource block group.
4. The step of determining the resource block occupancy status in the same resource block group based on the bandwidth of the carrier bandwidth portion includes: determining whether there are unoccupied resource blocks in the same resource block group based on the bandwidth of the carrier bandwidth portion; when there are unoccupied resource blocks in the same resource block group, determining the unoccupied resource blocks as target resource blocks. Determining the resource occupancy status of resource blocks within the same resource block group based on the target resource block, the method according to claim 3.
5. The first type of terminal device includes a terminal device corresponding to an extended mobile broadband scenario, and the second type of terminal device includes one or more of a terminal device corresponding to a function reduction scenario, a terminal device corresponding to a low-latency and high-reliability communication scenario, and a terminal device corresponding to a massive machine type communication scenario, the method according to claim 1.
6. A resource usage method applied to a terminal device, Receiving resource occupancy identifier information transmitted by a network device, the resource occupancy identifier information being generated by the network device based on resource setting information corresponding to a first type of terminal device and a second type of terminal device, and indicating the resource block occupancy status within a resource block group overlapping between the first type of terminal device and the second type of terminal device, Using resources based on the resource occupancy identifier information, a resource usage method.
7. The step of performing resource scheduling based on the resource occupancy identifier information is Analyzing the resource occupancy identifier information to obtain a target resource block, the target resource block being a resource block not occupied in a resource block group overlapping between the first type of terminal device and the second type of terminal device, Using resources based on the target resource block, the method according to claim 6.
8. A network device including a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection communication between the processor and the memory, wherein when the computer program is executed by the processor, the steps of the resource scheduling method according to any one of claims 1 to 5 are realized.
9. A terminal device including a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection communication between the processor and the memory, wherein when the computer program is executed by the processor, the steps of the resource usage method according to any one of claims 6 to 7 are realized.
10. A computer-readable storage medium in which one or more programs are stored, and when the one or more programs are executed by one or more processors, the steps of the resource scheduling method according to any one of claims 1 to 5 or the steps of the resource usage method according to any one of claims 6 to 7 are realized.
Citation Information
Patent Citations
Information transmission method and communication apparatus
WO2022027695A1