Resource scheduling method and apparatus

Abstract

This application provides a resource scheduling method and apparatus in which an extended Redcap (eRedCap) terminal reports to a network device the number of parallel unicast physical downlink shared channels (PDSCHs) supported by the eRedCap terminal in response to the eRedCap terminal having a first capability, or does not report to a network device the number of parallel unicast PDSCHs supported by the eRedCap terminal in response to the eRedCap terminal not having a first capability, wherein the first capability includes the ability of the eRedCap terminal to process parallel unicast PDSCHs. The proposed technology provided herein allows the eRedCap terminal to upload the number of parallel unicast PDSCHs it supports, and a base station to know the eRedCap terminal's processing capability for parallel unicast PDSCHs, thereby enabling rational scheduling of the eRedCap terminal's unicast PDSCHs.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and particularly to a resource scheduling method, apparatus, and system.

Background Art

[0002] To reduce the cost of Reduced Capability (RedCap) terminals, one feasible technical solution is to reduce the baseband bandwidth of the RedCap terminal data channel to 5 MHz. A RedCap terminal that supports such a reduction in baseband bandwidth is called an Enhanced Reduced Capability (eRedCap) terminal. In an eRedCap terminal, the number of resources with a 15 / 30 KHz Sub-Carrier Space (SCS) does not exceed 25 / 12 resource blocks (RBs). When performing a series of operations such as channel estimation, channel equalization, signal detection, and demodulation, the eRedCap terminal performs Physical Downlink Shared Channel (PDSCH) processing based on the number of 25 / 12 RBs of resources. When the number of received resources exceeds 25 / 12 RBs, the eRedCap terminal needs to process the received data in multiple portions, thereby introducing additional processing delays. Based on this, how to determine the number of PDSCH channels that an eRedCap terminal can process in parallel within a certain processing delay range is an urgent problem to be solved.

Summary of the Invention

Problems to be Solved by the Invention

[0003] Embodiments of this application provide a resource scheduling method, apparatus, and system, so that a base station can know the number of parallel unicast PDSCHs that an eRedCap terminal can process within a certain processing delay range, thereby enabling reasonable scheduling of the unicast PDSCH of the eRedCap terminal. [Means for solving the problem]

[0004] In a first aspect, an embodiment of the present application provides a resource scheduling method, the method being applied to an eRedCap terminal, In response to the eRedCap terminal having a first capability, the number of parallel unicast PDSCHs supported by the eRedCap terminal is reported to the network device. Or, The process includes the step of not reporting to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal in response that the eRedCap terminal does not have a first capability, The first capability described above includes the ability of the eRedCap terminal to process parallel unicast PDSCH.

[0005] In the implementation method, the step of reporting the number of parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: A step of reporting to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal, the step of determining that the number of RBs occupied by the first parallel unicast PDSCH is less than or equal to a first threshold.

[0006] In the implementation method, the step of reporting the number of first parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: A step of transmitting a first capability report field to the network device via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps include defining a new capability report field, obtaining a second capability report field, and transmitting the second capability report field to the network device via capability signaling, wherein the second capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0007] In the implementation method, the step of reporting the number of first parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: The method includes the step of reporting to the network device the number of first parallel unicast PDSCHs supported by the eRedCap terminal, in response that the processing delay of the parallel unicast PDSCHs of the eRedCap terminal is less than or equal to a preset first delay threshold.

[0008] In the implementation method, the step of reporting the number of parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: The step of reporting to a network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal, the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited by a first threshold.

[0009] In the implementation method, the step of reporting the number of second parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: A step of transmitting a first capability report field to the network device via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps include defining a new capability report field, obtaining a second capability report field, and transmitting the second capability report field to the network device via capability signaling, wherein the second capability report field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal, The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0010] In the implementation method, the step of reporting the number of second parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: The method includes the step of reporting to the network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal, in response that the processing delay of the parallel unicast PDSCH of the eRedCap terminal is less than or equal to a preset first delay threshold.

[0011] In the implementation method, the step of reporting the number of parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: In response to the processing delay of the parallel unicast PDSCH of the eRedCap terminal being less than or equal to a preset second delay threshold, the eRedCap terminal reports to the network device the number of third parallel unicast PDSCHs supported by the eRedCap terminal, the second delay threshold being greater than a preset first delay threshold, and the first delay threshold being the processing delay threshold for the parallel unicast PDSCH of a non-eRedCap terminal.

[0012] In the implementation method, the eRedCap terminal supports a number of parallel unicast PDSCHs, and the step of reporting the number of third parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: The number of targets is defined as the number of third parallel unicast PDSCHs supported by the eRedCap terminal, and the number of targets is reported to the network device. Or, The step includes taking the maximum number of third parallel unicast PDSCHs supported by the eRedCap terminal as the target number, and reporting the target number to the network device, The second delay threshold is different for each number of third parallel unicast PDSCHs.

[0013] In the implementation method, the step of reporting the number of third parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: A step of transmitting a first capability report field to the network device via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps include defining a new capability report field, obtaining a second capability report field, and transmitting the second capability report field to the network device via capability signaling, wherein the second capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal, The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0014] In a second aspect, embodiments of the present application further provide a resource scheduling method, the method being applied to a network device, receiving, by the eRedCap terminal, the number of parallel unicast PDSCHs supported by the eRedCap terminal, which is reported in response to the eRedCap terminal having a first capability; and scheduling, based on the number of parallel unicast PDSCHs supported by the eRedCap terminal, the unicast PDSCH resources of the eRedCap terminal, or, scheduling, based on the processing capability of a single unicast PDSCH of the eRedCap terminal, the unicast PDSCH resources of the eRedCap terminal, including the step, The first capability includes the capability of the eRedCap terminal to process parallel unicast PDSCHs.

[0015] In an implementation manner, the step of receiving, by the eRedCap terminal, the number of parallel unicast PDSCHs supported by the eRedCap terminal, which is reported in response to the eRedCap terminal having a first capability, is a step of receiving the number of first parallel unicast PDSCHs supported by the eRedCap terminal, where the number of RBs occupied by the supported first parallel unicast PDSCHs is not more than a first threshold, including the step.

[0016] In an implementation manner, the step of receiving the number of first parallel unicast PDSCHs supported by the eRedCap terminal is a step of receiving a first capability reporting field via capability signaling, where the first capability reporting field is an existing capability reporting field of the capability signaling, and the first capability reporting field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, or, Receiving a second capability reporting field via capability signaling, wherein the second capability reporting field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability reporting field is a new capability reporting field defined by the eRedCap terminal, The value set of the first capability reporting field is the same as or different from the value set of the second capability reporting field.

[0017] In an implementation manner, the number of the first parallel unicast PDSCHs is reported in response to the processing delay of the parallel unicast PDSCH of the eRedCap terminal being less than or equal to a preset first delay threshold by the eRedCap terminal.

[0018] In an implementation manner, the step of receiving, by the eRedCap terminal, the number of parallel unicast PDSCHs supported by the eRedCap terminal reported in response to the eRedCap terminal having a first capability includes: Receiving the number of second parallel unicast PDSCHs supported by the eRedCap terminal, wherein the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited by a first threshold.

[0019] In an implementation manner, the step of receiving the number of second parallel unicast PDSCHs supported by the eRedCap terminal includes: Receiving a first capability reporting field via capability signaling, wherein the first capability reporting field is an existing capability reporting field of the capability signaling, and the first capability reporting field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal, Or, The steps include receiving a second capability report field via capability signaling, wherein the second capability report field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal.

[0020] In the implementation method, the number of the second parallel unicast PDSCH is reported by the eRedCap terminal in response to the eRedCap terminal's processing delay of the parallel unicast PDSCH being less than or equal to a preset first delay threshold.

[0021] In the implementation, the step of receiving the number of parallel unicast PDSCHs supported by the eRedCap terminal, reported by the eRedCap terminal in response to the eRedCap terminal having a first capability, The step of receiving the number of third parallel unicast PDSCHs supported by the eRedCap terminal, the number of third parallel unicast PDSCHs being reported by the eRedCap terminal in response that the processing delay of the eRedCap terminal's parallel unicast PDSCHs is less than or equal to a preset second delay threshold, the second delay threshold being greater than a preset first delay threshold, and the first delay threshold being a threshold for the processing delay of a non-eRedCap terminal's parallel unicast PDSCHs.

[0022] In the implementation method, the eRedCap terminal supports a number of parallel unicast PDSCHs, and the step of receiving a third number of parallel unicast PDSCHs supported by the eRedCap terminal is: A step of receiving the number of targets of the eRedCap terminal, wherein the number of targets includes the number of each third parallel unicast PDSCH supported by the eRedCap terminal. Or, The step of receiving the number of targets of the eRedCap terminal, wherein the number of targets includes the maximum value of all third parallel unicast PDSCHs supported by the eRedCap terminal, The second delay threshold is different for each number of third parallel unicast PDSCHs.

[0023] In the implementation method, the step of receiving the number of third parallel unicast PDSCHs supported by the eRedCap terminal is: A step of receiving a first capability report field via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal. Or, The step of receiving a second capability report field via capability signaling, wherein the second capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal, The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0024] In a third aspect, the embodiment of the present application further provides a resource scheduling device, the device being installed in an eRedCap terminal, and the device is A response module for reporting to a network device the number of parallel unicast PDSCHs supported by the eRedCap terminal in response to the eRedCap terminal having a first capability, Or, The eRedCap terminal does not have a first capability, and in response to this, the eRedCap terminal does not report to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal, including a response module for not reporting the number of parallel unicast PDSCHs supported by the eRedCap terminal to the network device, The first capability described above includes the ability of the eRedCap terminal to process parallel unicast PDSCH.

[0025] In a fourth aspect, the embodiment of the present application further provides a resource scheduling device, the device being installed on a network device, the device is A receiving module for receiving the number of parallel unicast PDSCHs supported by an eRedCap terminal, reported by the eRedCap terminal in response to the eRedCap terminal having a first capability; and a scheduling module for scheduling the unicast PDSCH resources of the eRedCap terminal based on the number of parallel unicast PDSCHs supported by the eRedCap terminal. Or, Includes a scheduling module for scheduling unicast PDSCH resources of the eRedCap terminal based on the processing capacity of a single unicast PDSCH of the eRedCap terminal, The first capability described above includes the ability of the eRedCap terminal to process parallel unicast PDSCH.

[0026] In a fifth aspect, an embodiment of the present application provides a resource scheduling device comprising a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the device to perform the method according to the first or second aspect.

[0027] In a sixth aspect, an embodiment of the present application provides a resource scheduling device comprising a processor and an interface circuit, The interface circuit is used to receive code instructions and transmit them to the processor. The processor is used to execute the code instructions and perform the method according to the first or second embodiment.

[0028] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium in which instructions are stored, and when the instructions are executed, the method of the first or second aspect is realized. [Effects of the Invention]

[0029] The resource scheduling method and apparatus provided by embodiments of this application report to a network device the number of parallel unicast PDSCHs supported by the eRedCap terminal in response to the eRedCap terminal having a first capability, or not report to a network device the number of parallel unicast PDSCHs supported by the eRedCap terminal in response to the eRedCap terminal not having a first capability, wherein the first capability includes the ability of the eRedCap terminal to process parallel unicast PDSCHs. The proposed technology provided by embodiments of this application allows a base station to know the processing capability of the eRedCap terminal's parallel unicast PDSCHs by having the eRedCap terminal report the number of parallel unicast PDSCHs it can process, thereby enabling the base station to rationally schedule the unicast PDSCHs of the eRedCap terminal, and avoids resource waste and increased terminal energy consumption by preventing the eRedCap terminal from being unable to provide HARQ-ACK feedback when HARQ resources arrive, or only being able to provide NACK feedback, due to the need for the eRedCap terminal to divide received data into multiple processing steps and introduce additional delays. [Brief explanation of the drawing]

[0030] To more clearly illustrate the technical concepts in the embodiments or background art of this application, the drawings necessary for use in the embodiments or background art of this application are described below. [Figure 1] This is a schematic diagram of the communication system provided by the embodiment of this application. [Figure 2] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 3] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 4] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 5] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 6] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 7] This is a flowchart for reporting the number of first parallel unicast PDSCHs using a first capability reporting field provided in the embodiment of this application. [Figure 8] This is a flowchart for reporting the number of first parallel unicast PDSCHs using a second capability reporting field provided in the embodiment of this application. [Figure 9] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 10] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 11] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 12] This is a flowchart for reporting the number of second parallel unicast PDSCHs using a first capability reporting field provided in the embodiment of this application. [Figure 13] This is a flowchart for reporting the number of second parallel unicast PDSCHs using a second capability reporting field provided in the embodiment of this application. [Figure 14] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 15] This flowchart reports the number of third parallel unicast PDSCHs based on different delay thresholds provided by the embodiments of this application. [Figure 16] This is a flowchart for reporting the number of third parallel unicast PDSCHs using the first capability reporting field provided in the embodiment of this application. [Figure 17] This is a flowchart for reporting the number of third parallel unicast PDSCHs using a second capability reporting field provided in the embodiment of this application. [Figure 18] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 19] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 20] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 21] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 22] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 23] This is a flowchart of the resource scheduling method provided by the embodiment of this application. [Figure 24] This is a schematic diagram of the resource scheduling device provided by the embodiment of this application. [Figure 25] This is a schematic diagram of another resource scheduling device provided by an embodiment of this application. [Figure 26] This is a block diagram of a terminal device provided by the embodiment of this application. [Figure 27] This is a block diagram of a network device provided by an embodiment of this application. [Modes for carrying out the invention]

[0031] Herein, exemplary embodiments are described, and these examples are shown in the drawings. Where the following description relates to the drawings, unless otherwise stated, the same numbers in different drawings represent similar or identical elements. The embodiments described in the following exemplary embodiments do not represent all embodiments that are consistent with the embodiments of this application. Rather, they are merely examples of apparatuses and methods that are consistent with some aspects of the embodiments of this application.

[0032] The terms used in the embodiments of this application are used to describe specific embodiments and are not intended to limit the embodiments of this application. The singular forms “one kind,” “the said,” and “the” used in this application also include the plural form unless the context clearly indicates otherwise. The terms “and / or” used herein may refer to any or all possible combinations of one or more related enumeration items.

[0033] The embodiments of this application may use terms such as "first," "second," and "third" to describe various pieces of information, but this information should not be limited to these terms. These terms are merely used to distinguish the same type of information. For example, the first parameter may be called the second parameter, and similarly, the second parameter may be called the first parameter, as long as it does not deviate from the scope of the embodiments of this application. Depending on the context, the term "if" as used herein may be understood as "in the case of," "when," or "in response to a decision."

[0034] The embodiments of this application will be described in detail below. Examples of these embodiments are shown in the accompanying drawings, and the same or similar reference tables will be described in detail in the accompanying drawings from beginning to end. Where the following description relates to the drawings, unless otherwise stated, the same numbers in different drawings represent similar or identical elements. The embodiments described in the following exemplary embodiments do not represent all embodiments that are consistent with the embodiments of this application. Rather, they are merely examples of apparatuses and methods that are consistent with some aspects of the embodiments of this application.

[0035] The terms used in the embodiments of this application are used to describe specific embodiments and are not intended to limit the embodiments of this application. The singular forms “one kind,” “the said,” and “the” used in this application also include the plural form unless the context clearly indicates otherwise. The terms “and / or” used herein may refer to any or all possible combinations of one or more related enumeration items.

[0036] The embodiments of this application may use terms such as "first," "second," and "third" to describe various pieces of information, but this information should not be limited to these terms. These terms are merely used to distinguish the same type of information. For example, the first parameter may be called the second parameter, and similarly, the second parameter may be called the first parameter, as long as it does not deviate from the scope of the embodiments of this application. Depending on the context, the term "if" as used herein may be understood as "in the case of," "when," or "in response to a decision."

[0037] The embodiments of this application will be described in detail below. Examples of these embodiments are shown in the drawings, where the same or similar reference numerals from beginning to end represent the same or similar elements. The embodiments described below with reference to the attached drawings are illustrative for the purpose of illustrating this application and should not be understood as limitations thereof.

[0038] To better understand the resource scheduling method disclosed in the embodiments of this application, the following describes the communication system to which the embodiments of this application apply.

[0039] Referring to Figure 1, Figure 1 shows the architecture of a communication system provided by an embodiment of the present application. The communication system may include one network device and one terminal device, but is not limited to these. The terminal device communicates with the network device, and the number and configuration of devices shown in Figure 1 are merely examples and do not constitute limitations of the embodiment of the present application. In actual applications, two or more network devices and two or more terminal devices may be included. The communication system shown in Figure 1 is an example in which network device 101 and terminal device 102 are included.

[0040] For example, one terminal device can be an eRedCap terminal.

[0041] Furthermore, the technical inventions described in this application are applicable to various communication systems. For example, they may be applied to long-term evolution (LTE) systems, 5th generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0042] The network device in the embodiments of this application is an entity for transmitting and receiving signals on the network side. For example, the network device 101 may be an evolved NodeB (eNB), a transmission reception point (or transmit receive point, TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access point in a wireless fidelity (WiFi) system. The embodiments of this application do not limit the specific technology or specific device form used for the network device. The network device provided by the embodiments of this application may consist of a central unit (CU) and a distributed unit (DU), where the CU is also called a control unit, and by using a CU-DU structure, the protocol layer of the network device, such as a base station, can be separated, with some functions of the protocol layer being centrally controlled by the CU, and some or all of the remaining functions of the protocol layer being distributed in the DU, with the DU being centrally controlled by the CU.

[0043] In the embodiments of this application, the terminal device is an entity for transmitting and receiving signals on the user side, such as a mobile phone. The terminal device may also be called a terminal, mobile station (MS), mobile terminal (MT), etc. The terminal device may be an automobile equipped with communication functions, a smart car, a mobile phone, a wearable device, a tablet (Pad), a personal computer equipped with wireless transmission and reception functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. The embodiments of this application do not limit the specific technology or specific device form used for the terminal device.

[0044] In an eRedCap terminal supporting a 5MHz baseband bandwidth, the terminal's radio frequency bandwidth is 20MHz, allowing it to receive data exceeding 25 / 12 RBs and cache the received data using orthogonal frequency division multiplexing (OFDM). If two frequency-division multiplexing (FDM) unicast PDSCHs exceed 5MHz, the eRedCap terminal must process the received data in multiple parts, which introduces additional processing delays.

[0045] Based on this, embodiments of the present application provide a resource scheduling method and apparatus in which an eRedCap terminal reports the number of parallel unicast PDSCHs it can process, allowing a base station to know the processing capacity of the eRedCap terminal's parallel unicast PDSCHs, thereby enabling the base station to rationally schedule the unicast PDSCHs of the eRedCap terminal, and avoiding resource waste and increased terminal energy consumption by preventing the eRedCap terminal from being unable to provide HARQ-ACK feedback when HARQ resources arrive, or only being able to provide NACK feedback, due to the need for the eRedCap terminal to divide received data into multiple processing steps and introduce additional delays.

[0046] Referring to Figure 2, an embodiment of the present application provides a resource scheduling method. As shown in Figure 2, the method may include the following steps: Step 201: The eRedCap terminal sends the first piece of information to the network device.

[0047] In some implementations, the first information indicates the number of parallel unicast PDSCHs supported by the eRedCap terminal, for example, if the eRedCap terminal supports two parallel unicast PDSCHs, the first information is sent to the network device to inform the network device that the number of parallel unicast PDSCHs supported by the eRedCap terminal is two, so that the network device can schedule the unicast PDSCHs of the eRedCap terminal according to the processing capacity of the two parallel unicast PDSCHs.

[0048] In some implementations, the eRedCap terminal can determine whether or not it has the capability to process parallel unicast PDSCH. If the eRedCap terminal has the capability to process parallel unicast PDSCH, it sends the first information to the network device; if the eRedCap terminal does not have the capability to process parallel unicast PDSCH, it does not send the first information to the network device.

[0049] In some embodiments, the number of parallel unicast PDSCHs supported by the eRedCap terminal can be determined under certain limitations.

[0050] Specifically, in some embodiments, the eRedCap terminal can determine whether the number of RBs occupied by the parallel unicast PDSCHs supported by the eRedCap terminal is less than or equal to a preset first threshold. If the number of RBs occupied by the parallel unicast PDSCHs supported by the eRedCap terminal is less than or equal to the preset first threshold, the eRedCap terminal reports the number of unicast PDSCHs to the network device. Conversely, if the number of RBs occupied by the parallel unicast PDSCHs supported by the eRedCap terminal is greater than the preset first threshold, the eRedCap terminal does not report the number of unicast PDSCHs to the network device. For example, for an eRedCap terminal supporting a 5MHz baseband bandwidth, the number of parallel unicast PDSCH channels that can be processed is 2. Under a 15KHz SCS, the baseband bandwidth contains 25 RBs, i.e., the first threshold is 25 RBs. Therefore, the total number of RBs in the two unicast PDSCH channels of the eRedCap terminal must not exceed 25 RBs. However, under a 30KHz SCS, the baseband bandwidth contains 12 RBs, i.e., the first threshold is 12 RBs. Therefore, the total number of RBs in the two unicast PDSCH channels of the eRedCap terminal must not exceed 12 RBs.

[0051] In some embodiments, the eRedCap terminal can further determine whether the processing delay of the parallel unicast PDSCH of the eRedCap terminal is less than or equal to a preset second delay threshold, wherein the second delay threshold is greater than a preset first delay threshold, and the first delay threshold is the processing delay threshold of the parallel unicast PDSCH of a non-eRedCap terminal. If the processing delay of the parallel unicast PDSCH of the eRedCap terminal is less than or equal to the preset second delay threshold, the number of PDSCHs is reported to the network device. Conversely, if the processing delay of the parallel unicast PDSCH of the eRedCap terminal is greater than the preset second delay threshold, the number of PDSCHs is not reported to the network device. The non-eRedCap terminal may be a terminal that does not support a reduction in baseband bandwidth to 5 MHz, and more specifically, it may be a RedCap terminal that does not support a reduction in baseband bandwidth to 5 MHz. In actual applications, the non-eRedCap terminal may also be called a non-extendable capacity reduction terminal, and the embodiments of this application are not limited thereto.

[0052] Accordingly, in some embodiments, the number of parallel unicast PDSCHs supported by the eRedCap terminal can be further determined under the constraints of a first threshold and a second delay threshold.

[0053] In some embodiments, the eRedCap terminal may report the first information to the network device using an existing first capability reporting field in the capability signaling, and the network device may receive the first information using the first capability reporting field in the capability signaling. Alternatively, the eRedCap terminal may define a new second capability reporting field and report the first information to the network device via the second capability reporting field, and the network device may receive the first information using the second capability reporting field in the capability signaling. The new second capability reporting field may be a newly added capability reporting field in the capability signaling, i.e., the first capability reporting field is not an existing capability reporting field in the capability signaling.

[0054] Step 202: The network device receives the first information and schedules the unicast PDSCH of the eRedCap terminal based on the first information.

[0055] In some embodiments, the network device can determine, based on the first information received, the eRedCap terminal's ability to process parallel unicast PDSCHs, and in the scheduling process, schedule the parallel unicast PDSCHs supported by the eRedCap terminal based on the eRedCap terminal's parallel unicast PDSCH processing capability. For example, if the eRedCap terminal has the capability to process two parallel unicast PDSCHs, the two unicast PDSCHs of the eRedCap terminal can be scheduled simultaneously.

[0056] Correspondingly, in some embodiments, if the network device has not received the first information, the eRedCap terminal is deemed to be unable to process parallel unicast PDSCHs, and in this case, the network device can schedule one of the eRedCap terminal's unicast PDSCHs.

[0057] In summary, the resource scheduling method provided by the embodiment of this application allows the base station to know the processing capacity of the eRedCap terminal's parallel unicast PDSCHs by having the eRedCap terminal report the number of parallel unicast PDSCHs it can process, thereby enabling the base station to rationally schedule the unicast PDSCHs of the eRedCap terminal. Furthermore, it avoids resource waste and increased terminal energy consumption by preventing the eRedCap terminal from being unable to provide HARQ-ACK feedback when HARQ resources arrive, or only being able to provide NACK feedback, due to the need for the eRedCap terminal to divide received data into multiple processing steps and introduce additional delays.

[0058] Referring to Figure 3, an embodiment of the present application further provides a resource scheduling method, the method of which is applied to an eRedCap terminal. As shown in Figure 3, the method may include the following steps: Step 301: In response to the eRedCap terminal having a first capability, the number of parallel unicast PDSCHs supported by the eRedCap terminal is reported to the network device, wherein the first capability includes the ability of the eRedCap terminal to process parallel unicast PDSCHs.

[0059] In some embodiments, the eRedCap terminal transmits the number of parallel unicast PDSCHs supported by the eRedCap terminal to the network device, and the network device receives the number of parallel unicast PDSCHs supported by the eRedCap terminal.

[0060] In some embodiments, the eRedCap terminal can support two types of parallel unicast PDSCH processing capabilities, the first type of parallel unicast PDSCH processing capability supports processing X parallel unicast PDSCHs within a certain delay range without being limited by the number of RBs, and the second type of parallel unicast PDSCH processing capability supports processing Y parallel unicast PDSCHs within a certain delay range, being limited by the number of RBs, the set of values ​​for X can be represented as set#1, and the set of values ​​for Y can be represented as set#2, and set#1 and set#2 may be the same or different. Based on its implementation, the eRedCap terminal can selectively report these two types of capabilities, specifically, if both types of capabilities are implemented, i.e., if the eRedCap supports both types of capabilities simultaneously, both types of capabilities are reported; if the eRedCap supports only one of the capabilities, only the supported capability is reported; or if the eRedCap does not support either type of capability, neither is reported.

[0061] In some embodiments, the maximum number of parallel unicast PDSCHs supported by the eRedCap terminal may be smaller than the maximum number of parallel unicast PDSCHs supported by the non-eRedCap terminal. Specifically, if the set of values ​​for the number of parallel unicast PDSCHs supported by the eRedCap terminal is set#1 and the set of values ​​for the number of parallel unicast PDSCHs supported by the non-eRedCap terminal is set#3, then the maximum value in set#1 may be smaller than the maximum value in set#3. For example, if set#3 is {2, 4, 7}, then set#1 may be {2, 4} or {2}.

[0062] In some embodiments, the number of unicast PDSCHs can be determined under a certain resource limit, where the number of RBs occupied by the supported parallel unicast PDSCHs is less than or equal to a first threshold. For example, for an eRedCap terminal supporting a 5MHz baseband bandwidth, two parallel unicast PDSCH channels can be processed, and at 15KHz SCS, the number of RBs for the two parallel unicast PDSCH channels does not exceed 25 RBs, and at 30KHz SCS, the number of RBs for the two parallel unicast PDSCH channels does not exceed 12 RBs.

[0063] In the embodiments of this application, the number of RBs occupied by the supported parallel unicast PDSCH is not limited to the number of resources, for example, for an eRedCap terminal supporting a 5MHz baseband bandwidth, two parallel unicast PDSCH channels can be processed, and the number of RBs for the two parallel unicast PDSCH channels is not limited to 25 / 12 RBs.

[0064] In the embodiments of this application, the number of unicast PDSCHs is further reported as the number of parallel unicast PDSCHs that the eRedCap terminal can process, subject to certain delay limitations. For example, if the number of unicast PDSCHs is N, the number of unicast PDSCHs N is reported if the processing delay required for N parallel unicast PDSCHs is less than or equal to a preset delay threshold.

[0065] In embodiments of the present application, the eRedCap terminal may report the number of unicast PDSCHs to the network device using an existing first capability reporting field for capability signaling, or it may define a new second capability reporting field to report the number of unicast PDSCHs to the network device via the second capability reporting field. When reporting the number of parallel unicast PDSCHs supported by the eRedCap terminal using the second capability reporting field, the set of values ​​for the second capability reporting field may be the same as or different from the set of values ​​for the first capability reporting field.

[0066] In summary, the technology provided by the embodiments of this application allows the base station to know the processing capacity of the eRedCap terminal's parallel unicast PDSCHs by having the eRedCap terminal report the number of parallel unicast PDSCHs it can process, thereby enabling the base station to rationally schedule the unicast PDSCHs of the eRedCap terminal. Furthermore, it avoids resource waste and increased terminal energy consumption by preventing the eRedCap terminal from being unable to provide HARQ-ACK feedback when HARQ resources arrive, or only being able to provide NACK feedback, due to the need for the eRedCap terminal to divide received data into multiple processing steps and introduce additional delays.

[0067] In actual applications, if the eRedCap terminal does not have the capability to process parallel unicast PDSCHs, it may choose not to report the number of parallel unicast PDSCHs supported by the eRedCap terminal to the network device.

[0068] Based on this, embodiments of the present application further provide a resource scheduling method, which is applied to an eRedCap terminal. As shown in Figure 4, the method may include the following steps: Step 401: In response that the eRedCap terminal does not have the first capability, the number of parallel unicast PDSCHs supported by the eRedCap terminal is not reported to the network device.

[0069] Furthermore, the absence of the first capability in the eRedCap terminal may mean that all eRedCap terminals do not possess the first capability, i.e., that the eRedCap terminals do not support parallel unicast PDSCH.

[0070] In some embodiments, the number of parallel unicast PDSCHs supported by the eRedCap terminal is reported to the network device, and in response, the network device does not receive the number of parallel unicast PDSCHs supported by the eRedCap terminal.

[0071] In the embodiment of this application, the eRedCap terminal does not report its capabilities, and in this way, the base station schedules the eRedCap terminal's unicast PDSCH according to its processing capacity for a single unicast PDSCH. That is, the base station determines that the eRedCap terminal does not have the capacity to process parallel unicast PDSCHs and performs only single unicast PDSCH scheduling for the eRedCap terminal at the same time.

[0072] As described above, the resource scheduling method provided by the embodiment of this application allows the base station to rationally schedule the unicast PDSCH of the eRedCap terminal by knowing the processing capacity of the eRedCap terminal's parallel unicast PDSCH, avoiding the need for the eRedCap terminal to divide received data into multiple processing steps and introduce additional processing delays, and avoiding resource waste and increased terminal energy consumption by preventing the eRedCap terminal from being unable to provide HARQ-ACK feedback or only being able to provide NACK feedback when HARQ resources arrive.

[0073] Referring to Figure 5, the embodiments of this application further provide a resource scheduling method applied to an eRedCap terminal, which can be executed independently, in combination with any embodiment of this application or a possible implementation of any embodiment, or in combination with any technical proposal in the related art.

[0074] As shown in Figure 5, the resource scheduling method may include the following steps: Step 501: In response to the eRedCap terminal having a first capability, the number of first parallel unicast PDSCHs supported by the eRedCap terminal is reported to the network device, and the number of RBs occupied by the supported first parallel unicast PDSCHs is less than or equal to a first threshold.

[0075] In embodiments of this application, the first threshold may be the maximum number of RBs in a data channel supported by the eRedCap terminal baseband. For example, for an eRedCap terminal supporting a 5MHz baseband bandwidth, the number of parallel unicast PDSCH channels that can be processed is 2. Under a 15KHz SCS, the baseband bandwidth contains 25 RBs, i.e., the first threshold is 25 RBs, and therefore the total number of RBs in the two unicast PDSCH channels of the eRedCap terminal must not exceed 25 RBs. However, under a 30KHz SCS, the baseband bandwidth contains 12 RBs, i.e., the first threshold is 12 RBs, and therefore the total number of RBs in the two unicast PDSCH channels of the eRedCap terminal must not exceed 12 RBs.

[0076] Referring to Figure 6, embodiments of the present application further provide a resource scheduling method applied to an eRedCap terminal, which can be executed independently, in combination with any embodiment of the present application or a possible implementation of any embodiment, or in combination with any technical proposal in the related art.

[0077] As shown in Figure 6, the resource scheduling method may include the following steps: Step 601: In response to the eRedCap terminal's processing delay of the parallel unicast PDSCH being less than or equal to a preset first delay threshold, the eRedCap terminal reports to the network device the number of first parallel unicast PDSCHs supported by the eRedCap terminal.

[0078] In some embodiments, the eRedCap terminal can determine whether the processing delay of its own parallel unicast PDSCH is less than or equal to a preset second delay threshold. If the processing delay of the parallel unicast PDSCH supported by the eRedCap terminal is less than or equal to the preset second delay, the eRedCap terminal reports the number of parallel first parallel unicast PDSCHs it supports to the network device. Conversely, if the processing delay of the parallel unicast PDSCH supported by the eRedCap terminal is greater than the preset second delay, the eRedCap terminal does not report the number of parallel first parallel unicast PDSCHs it supports to the network device.

[0079] In the embodiments of this application, the first delay threshold is the processing delay of the parallel unicast PDSCH of the eRedCap terminal, and the eRedCap terminal can perform parallel processing using parallel unicast PDSCHs, can also perform serial processing, and it is sufficient that the processing can be completed within the time range of the first delay threshold, and the embodiments of this application are not limited thereto.

[0080] In the embodiments of this application, the first delay threshold may be a threshold defined by a protocol, or it may be a threshold set by the network device based on scheduling needs.

[0081] In the embodiments of this application, a first delay threshold is introduced, and the eRedCap terminal reports the number of parallel unicast PDSCHs it can process, allowing the base station to know the processing capacity of the eRedCap terminal's parallel unicast PDSCHs. This enables the base station to rationally schedule the eRedCap terminal's unicast PDSCHs, and by requiring the eRedCap terminal to divide the received data into multiple processing steps and introduce additional delays, the eRedCap terminal may be unable to provide HARQ-ACK feedback when HARQ resources arrive, or may only be able to provide NACK feedback, thus avoiding resource waste and increased terminal energy consumption.

[0082] In the embodiments of this application, the eRedCap terminal can report the number of the first parallel unicast PDSCHs using an existing first capability reporting field for capability signaling.

[0083] Based on this, with reference to Figure 7, an embodiment of the present application provides a method for reporting the number of the first parallel unicast PDSCH using a first capability reporting field, the method comprising the following steps: Step 701: In response to the eRedCap terminal having a first capability, it transmits a first capability report field to the network device via capability signaling, the first capability report field being an existing capability report field of the capability signaling, and the first capability report field including the number of first parallel unicast PDSCHs supported by the eRedCap terminal.

[0084] In the embodiments of this application, reporting the number of the first parallel unicast PDSCH using an existing first capability reporting field of the capability signaling adds a limit to the maximum number of resources for the eRedCap terminal to the definition of the first capability reporting field, i.e., the number of RBs occupied by the first parallel unicast PDSCHs supported to the definition of the first capability reporting field is less than or equal to a first threshold.

[0085] In the embodiments of this application, the eRedCap terminal may further report the number of the first parallel unicast PDSCHs based on a new second capability reporting field.

[0086] Based on this, with reference to Figure 8, an embodiment of the present application further provides a method for reporting the number of the first parallel unicast PDSCH using a second capability reporting field, the method comprising the following steps: Step 801: In response to the eRedCap terminal having a first capability, define a new capability report field and obtain a second capability report field, the second capability report field including the number of first parallel unicast PDSCHs supported by the eRedCap terminal. Step 802: Send the second capability report field to the network device via capability signaling.

[0087] Furthermore, the set of values ​​for the first capability report field may be the same as or different from the set of values ​​for the second capability report field. Specifically, the set of values ​​for the first capability report field may be the first set of values, for example, the set {2, 4, 7}, and the set of values ​​for the second capability field may be the second set of values, the first set of values ​​may be a pre-set set, and the second set of values ​​may be the same as the first set of values, and may also include other pre-set numerical values, i.e., numerical values ​​in a non-pre-set set. For example, if the pre-set set is {2, 4, 7}, the set of values ​​for the second capability report field may include numerical values ​​in the set {2, 4, 7}, and may also include numerical values ​​such as 3, 5, etc.

[0088] Referring to Figure 9, embodiments of the present application further provide a resource scheduling method applied to an eRedCap terminal, which can be run independently, in combination with any embodiment of the present application or a possible implementation of any embodiment, or in combination with any technical proposal in the related art.

[0089] As shown in Figure 9, the resource scheduling method may include the following steps: Step 901: In response to the eRedCap terminal having a first capability, the number of second parallel unicast PDSCHs supported by the eRedCap terminal is reported to the network device, and the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited to a first threshold.

[0090] In the embodiments of this application, the first threshold may be the maximum number of data channels RB supported by the eRedCap terminal baseband.

[0091] In actual applications, the number of RBs occupied by the second parallel unicast PDSCH supported by the eRedCap terminal can also be limited to the first threshold.

[0092] Based on this, with reference to Figure 10, an embodiment of the present application provides a resource scheduling method applied to an eRedCap terminal, and as shown in Figure 10, the method may include the following steps: Step 1001: Report the number of parallel unicast PDSCHs supported by the eRedCap terminal to the network device, and the number of resource blocks (RBs) occupied by the first parallel unicast PDSCH is less than or equal to a first threshold. Step 1002: The number of second parallel unicast PDSCHs supported by the eRedCap terminal is reported to the network device, and the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited by the first threshold.

[0093] In some embodiments, the eRedCap terminal can support two types of parallel unicast PDSCH processing capabilities, the first type of parallel unicast PDSCH processing capability is not limited by the number of RBs, and the second type of parallel unicast PDSCH processing capability is limited by the number of RBs. Based on its implementation, the eRedCap terminal can selectively report these two types of capabilities. Specifically, if both types of capabilities are implemented, i.e., the eRedCap supports both types of capabilities simultaneously, both types of capabilities are reported, i.e., steps 1001 and 1002 are executed simultaneously. Or, if the eRedCap supports only one of the capabilities, only the supported capability is reported, i.e., step 1001 or step 1002 is executed. Or, if the eRedCap does not support both types of capabilities, neither is reported, i.e., steps 1001 and 1002 are not executed.

[0094] In some embodiments, the first type of parallel unicast PDSCH processing capability supports processing X parallel unicast PDSCHs within a certain delay range, and the second type of parallel unicast PDSCH processing capability supports processing Y parallel unicast PDSCHs within a certain delay range, where the set of values ​​for X can be represented as set#1 and the set of values ​​for Y can be represented as set#2, and set#1 and set#2 may be the same or different.

[0095] Referring to Figure 11, embodiments of the present application further provide a resource scheduling method applied to an eRedCap terminal, which can be executed independently, in combination with any embodiment of the present application or a possible implementation of any embodiment, or in combination with any technical proposal in the related art.

[0096] As shown in Figure 11, the resource scheduling method may include the following steps: Step 1101: In response to the eRedCap terminal's processing delay of the parallel unicast PDSCH being less than or equal to a preset first delay threshold, the eRedCap terminal reports to the network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal.

[0097] In some embodiments, the eRedCap terminal can determine whether the processing delay of its own parallel unicast PDSCH is less than or equal to a preset first delay threshold. If the processing delay of the parallel unicast PDSCH supported by the eRedCap terminal is less than or equal to the preset first delay, the eRedCap terminal reports the number of parallel second parallel unicast PDSCHs it supports to the network device. Conversely, if the processing delay of the parallel unicast PDSCH supported by the eRedCap terminal is greater than the preset first delay, the eRedCap terminal does not report the number of parallel second parallel unicast PDSCHs it supports to the network device.

[0098] In the embodiments of this application, a first delay threshold is introduced, and the eRedCap terminal reports the number of parallel unicast PDSCHs it can process, allowing the base station to know the processing capacity of the eRedCap terminal's parallel unicast PDSCHs. This enables the base station to rationally schedule the eRedCap terminal's unicast PDSCHs, and by requiring the eRedCap terminal to divide the received data into multiple processing steps and introduce additional delays, the eRedCap terminal may be unable to provide HARQ-ACK feedback when HARQ resources arrive, or may only be able to provide NACK feedback, thus avoiding resource waste and increased terminal energy consumption.

[0099] In the embodiments of this application, the eRedCap terminal can report the number of the second parallel unicast PDSCHs using an existing first capability reporting field for capability signaling.

[0100] Based on this, with reference to Figure 12, an embodiment of the present application provides a method for reporting the number of the second parallel unicast PDSCH using a first capability reporting field, the method comprising the following steps: Step 1201: In response to the eRedCap terminal having a first capability, it transmits a first capability report field to the network device via capability signaling, the first capability report field being an existing capability report field of the capability signaling, and the first capability report field including the number of parallel second parallel unicast PDSCHs that the eRedCap terminal supports processing.

[0101] In the embodiments of this application, reporting the number of the second parallel unicast PDSCH using an existing first capability reporting field of the capability signaling allows for the addition of a limit on the maximum number of resources for the eRedCap terminal to the definition of the first capability reporting field, i.e., the number of RBs occupied by the second parallel unicast PDSCH, which is additionally supported in the definition of the first capability reporting field, is less than or equal to a first threshold.

[0102] In the embodiments of this application, the eRedCap terminal may further report the number of the second parallel unicast PDSCHs based on a new second capability reporting field.

[0103] Based on this, with reference to Figure 13, an embodiment of the present application further provides a method for reporting the number of the second parallel unicast PDSCH using a second capability reporting field, the method comprising the following steps: Step 1301: In response to the eRedCap terminal having a first capability, define a new capability report field and obtain a second capability report field, the second capability report field including the number of second parallel unicast PDSCHs supported by the eRedCap terminal. Step 1302: Send the second capability report field to the network device via capability signaling.

[0104] Furthermore, the set of values ​​for the first capability report field may be the same as or different from the set of values ​​for the second capability report field. Specifically, the set of values ​​for the first capability report field may be the first set of values, for example, the set {2, 4, 7}, and the set of values ​​for the second capability field may be the second set of values, the first set of values ​​may be a pre-set set, and the second set of values ​​may be the same as the first set of values, and may also include other pre-set numerical values, i.e., numerical values ​​in a non-pre-set set. For example, if the pre-set set is {2, 4, 7}, the set of values ​​for the second capability report field may include numerical values ​​in the set {2, 4, 7}, and may also include numerical values ​​such as 3, 5, etc.

[0105] Referring to Figure 14, embodiments of the present application further provide a resource scheduling method applied to an eRedCap terminal, which can be executed independently, in combination with any embodiment of the present application or a possible implementation of any embodiment, or in combination with any technical proposal in the related art.

[0106] As shown in Figure 14, the resource scheduling method may include the following steps: Step 1401: In response to the eRedCap terminal's processing delay of the parallel unicast PDSCH being less than or equal to a preset second delay threshold, the eRedCap terminal reports to the network device the number of parallel third parallel unicast PDSCHs it supports processing, wherein the second delay threshold is greater than a preset first delay threshold, and the first delay threshold is the processing delay threshold for the parallel unicast PDSCH of the non-eRedCap terminal.

[0107] In some embodiments, the eRedCap terminal can determine whether the processing delay of its own parallel unicast PDSCH is less than or equal to a preset first delay threshold. If the processing delay of the parallel unicast PDSCH supported by the eRedCap terminal is less than or equal to the preset first delay, the eRedCap terminal reports to the network device the number of parallel third parallel unicast PDSCHs it supports. Conversely, if the processing delay of the parallel unicast PDSCH supported by the eRedCap terminal is greater than the preset first delay, the eRedCap terminal reports to the network device the number of parallel third parallel unicast PDSCHs it supports.

[0108] In the embodiments of this application, a second delay threshold is introduced, and the eRedCap terminal reports the number of parallel unicast PDSCHs it can process, allowing the base station to know the processing capacity of the eRedCap terminal's parallel unicast PDSCHs, enabling the base station to rationally schedule the eRedCap terminal's unicast PDSCHs, and by requiring the eRedCap terminal to divide the received data into multiple processing steps and introduce additional delays, the eRedCap terminal may be unable to provide HARQ-ACK feedback when HARQ resources arrive, or may only be able to provide NACK feedback, thus avoiding resource waste and increased terminal energy consumption.

[0109] In the embodiments of this application, the eRedCap terminal can have different parallel processing capabilities, that is, the eRedCap terminal can support processing of different numbers of parallel unicast PDSCHs. A separate processing delay can be introduced for each different parallel processing capability, that is, the second delay threshold can include different delay thresholds, and the second delay threshold corresponding to a different number of third parallel unicast PDSCHs is different.

[0110] Based on this, with reference to Figure 15, an embodiment of the present application provides a method for reporting the number of third parallel unicast PDSCHs based on different delay thresholds, wherein the eRedCap terminal supports multiple numbers of parallel unicast PDSCHs, and each third number of parallel unicast PDSCHs has a different second delay threshold, the method comprising the following steps: Step 1501: The number of third parallel unicast PDSCHs supported by the eRedCap terminal is defined as the number of targets, and this number of targets is reported to the network device. Or, The maximum number of third parallel unicast PDSCHs supported by the eRedCap terminal is taken as the target number, and this target number is reported to the network device. The second delay threshold is different for each number of third parallel unicast PDSCHs.

[0111] In the embodiments of this application, first, the processing delay corresponding to the number of unicast PDSCHs supported by the eRedCap terminal is compared with a corresponding second delay threshold. If the processing delay for the number of unicast PDSCHs is smaller than the corresponding second delay threshold, the number of unicast PDSCHs is set to the number of third parallel unicast PDSCHs.

[0112] In the embodiments of this application, the number of each of the third parallel unicast PDSCHs is defined as the number of targets, and the number of targets is reported to the network device. The number of targets may be such that the eRedCap terminal reports only one third parallel unicast PDSCH at a time, or it may be such that the eRedCap terminal reports all third parallel unicast PDSCHs simultaneously.

[0113] Exemplary, for three different supported numbers of parallel unicast PDSCHs {2, 4, 7}, additional corresponding processing delay thresholds {X1, X2, X3} are introduced, where the processing delay threshold for 2 unicast PDSCHs is X1, the processing delay threshold for 4 unicast PDSCHs is X2, and the processing delay threshold for 7 unicast PDSCHs is X3. If the eRedCap terminal can satisfy X1 for processing 2 parallel channels, the eRedCap terminal can report the number 2; if the eRedCap terminal can satisfy X2 for processing 4 parallel channels, the eRedCap terminal can report the number 4; if the eRedCap terminal can satisfy X3 for processing 7 parallel channels, the eRedCap terminal can report the number 7. The eRedCap terminal can report only one number of unicast PDSCHs at a time, or it can report three numbers of unicast PDSCHs {2, 4, 7} simultaneously.

[0114] In the embodiments of this application, a common additional common processing delay can be introduced for different parallel processing capabilities, i.e., the second delay threshold is the same for different numbers of third parallel unicast PDSCHs. In practical applications, a common additional processing delay can be introduced, and the second delay threshold can be the sum of the additional processing delay and the first delay threshold.

[0115] In the embodiments of this application, the number of the third parallel unicast PDSCH can be determined from the number of parallel unicast PDSCHs supported by the eRedCap terminal based on the second delay threshold. Specifically, it can be determined that the eRedCap terminal satisfies the condition that the processing delay is less than or equal to the second delay threshold, and the maximum number of parallel unicast PDSCHs that can be supported can be determined, with the determined number being the number of the third parallel unicast PDSCH. The number of parallel unicast PDSCHs that can be processed is determined from the channel numerical set of the eRedCap terminal, and the channel numerical set of the eRedCap terminal may be a numerical set defined by a protocol, or a numerical set constructed based on the number of channels defined by the terminal-based protocol.

[0116] For example, if the set of channel numbers defined by the protocol is {2, 4, 7}, the eRedCap terminal supports three different numbers of parallel unicast PDSCHs {2, 4, 7}, introduces one additional processing delay Y1, and determines the maximum number of parallel unicast PDSCHs that the eRedCap terminal can support from {2, 4, 7} if the processing delay is less than or equal to Tprocessing, 1 + Y1, and sets this number as the number of third parallel unicast PDSCHs. For example, if the condition that the processing delay is less than Tprocessing, 1 + Y1 is met and the terminal can process up to four parallel channels, it reports the number of channels that can be processed in parallel as 4. Also, for example, if the eRedCap terminal defined by the protocol supports processing three parallel unicast PDSCHs and introduces an additional processing delay Y1, it is possible to determine the maximum number of parallel unicast PDSCHs that the eRedCap terminal can support from the set {2, 3, 4, 7}.

[0117] In the embodiments of this application, the eRedCap terminal can report the number of the first parallel unicast PDSCHs using an existing first capability reporting field for capability signaling.

[0118] Based on this, with reference to Figure 16, an embodiment of the present application provides a method for reporting the number of the third parallel unicast PDSCH using a first capability reporting field, the method comprising the following steps: Step 1601: In response to the eRedCap terminal having a first capability, it transmits a first capability report field to the network device via capability signaling, the first capability report field being an existing capability report field of the capability signaling, and the first capability report field including at least one third parallel unicast PDSCH supported by the eRedCap terminal.

[0119] In the embodiments of this application, the eRedCap terminal may further report the number of the at least one third parallel unicast PDSCH based on a new second capability reporting field.

[0120] Based on this, with reference to Figure 17, an embodiment of the present application further provides a method for reporting the number of the at least one third parallel unicast PDSCH using a second capability reporting field, the method comprising the following steps: Step 1701: In response to the eRedCap terminal having a first capability, define a new capability report field and obtain a second capability report field, the second capability report field including the number of at least one third parallel unicast PDSCH supported by the eRedCap terminal. Step 1702: Send the second capability report field to the network device via capability signaling.

[0121] Furthermore, the set of values ​​for the first capability report field may be the same as or different from the set of values ​​for the second capability report field. Specifically, the set of values ​​for the first capability report field may be the first set of values, for example, the set {2, 4, 7}, and the set of values ​​for the second capability field may be the second set of values, the first set of values ​​may be a pre-set set, and the second set of values ​​may be the same as the first set of values, and may also include other pre-set numerical values, i.e., numerical values ​​in a non-pre-set set. For example, if the pre-set set is {2, 4, 7}, the set of values ​​for the second capability report field may include numerical values ​​in the set {2, 4, 7}, and may also include numerical values ​​such as 3, 5, etc.

[0122] Referring to Figure 18, embodiments of this application further provide a different resource scheduling method applicable to network devices. As shown in Figure 18, the method may include the following steps: Step 1801: The eRedCap terminal receives the number of parallel unicast PDSCHs supported by the eRedCap terminal, reported in response to the eRedCap terminal having a first capability, the first capability including the ability of the eRedCap terminal to process parallel unicast PDSCHs.

[0123] In some embodiments, the eRedCap terminal can support two types of parallel unicast PDSCH processing capabilities, the first type of parallel unicast PDSCH processing capability supports processing X parallel unicast PDSCHs within a certain delay range without being limited by the number of RBs, and the second type of parallel unicast PDSCH processing capability supports processing Y parallel unicast PDSCHs within a certain delay range, being limited by the number of RBs. The network device can receive two types of capabilities reported simultaneously by the eRedCap, it can receive one capability supported by the eRedCap, or it can not receive any capability reported by the eRedCap.

[0124] In embodiments of the present application, the eRedCap terminal can report the number of unicast PDSCHs to the network device using an existing first capability reporting field for capability signaling, and correspondingly receive the first capability reporting field for network device utilization capability signaling, and can also define a new second capability reporting field for the eRedCap terminal and report the number of unicast PDSCHs to the network device via the second capability reporting field, and correspondingly receive the second capability reporting field via network device capability signaling. The set of values ​​for the second capability reporting field may be the same as or different from the set of values ​​for the first capability reporting field.

[0125] Step 1802: The unicast PDSCH resources of the eRedCap terminal are scheduled based on the number of parallel unicast PDSCHs supported by the eRedCap terminal.

[0126] In actual applications, the eRedCap terminal may also choose not to report the number of parallel unicast PDSCHs supported by the eRedCap terminal.

[0127] Based on this, with reference to Figure 19, embodiments of the present application further provide a resource scheduling method applicable to network devices. As shown in Figure 19, the method may include the following steps: Step 1901: In response to the eRedCap terminal not having the first capability, the unicast PDSCH resources of the eRedCap terminal are scheduled based on the processing capacity of a single unicast PDSCH of the eRedCap terminal.

[0128] Furthermore, the absence of the first capability in the eRedCap terminal may mean that all eRedCap terminals do not possess the first capability, i.e., that the eRedCap terminals do not support parallel unicast PDSCH.

[0129] Based on the above, the resource scheduling method provided by the embodiment of this application allows the communication base station to know the processing capacity of the eRedCap terminal's parallel unicast PDSCH, enabling the base station to rationally schedule the eRedCap terminal's unicast PDSCH, avoiding the need for the eRedCap terminal to divide received data into multiple processing steps and introduce additional processing delays, and avoiding resource waste and increased terminal energy consumption by preventing the eRedCap terminal from being unable to provide HARQ-ACK feedback when HARQ resources arrive, or only being able to provide NACK feedback.

[0130] Referring to Figure 20, embodiments of this application further provide a resource scheduling method applicable to network devices, the method may include the following steps: Step 2001: The number of first parallel unicast PDSCHs supported by the eRedCap terminal is received, and the number of RBs occupied by the supported first parallel unicast PDSCHs is less than or equal to a first threshold.

[0131] Step 2002: Based on the number of the first parallel unicast PDSCHs, the unicast PDSCH resources of the eRedCap terminal are scheduled.

[0132] A possible implementation of the embodiment of this application, the step of receiving the number of first parallel unicast PDSCHs supported by the eRedCap terminal, A step of receiving a first capability report field via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps may include receiving a second capability report field via capability signaling, wherein the second capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal. The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0133] A possible implementation of the embodiment of this application is such that the number of the first parallel unicast PDSCHs is reported by the eRedCap terminal in response to the processing delay of the parallel unicast PDSCHs of the eRedCap terminal being less than or equal to a preset first delay threshold.

[0134] Referring to Figure 21, embodiments of this application further provide a resource scheduling method applicable to network devices, the method may include the following steps: Step 2101: The number of second parallel unicast PDSCHs supported by the eRedCap terminal is received, and the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited by the first threshold. Step 2102: Based on the number of the second parallel unicast PDSCHs, the unicast PDSCH resources of the eRedCap terminal are scheduled.

[0135] Referring to Figure 22, embodiments of this application further provide a resource scheduling method applicable to network devices, the method may include the following steps: Step 2201: The number of first parallel unicast PDSCHs supported by the eRedCap terminal is received, and the number of RBs occupied by the supported first parallel unicast PDSCHs is less than or equal to a first threshold. Step 2202: Receive the number of second parallel unicast PDSCHs supported by the eRedCap terminal, and the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited by the first threshold. Step 2203: The unicast PDSCH resources of the eRedCap terminal are scheduled based on the number of the first parallel unicast PDSCHs or the number of the second parallel unicast PDSCHs.

[0136] In some embodiments, the eRedCap terminal can support two types of parallel unicast PDSCH processing capabilities, the first type of parallel unicast PDSCH processing capability is not limited by the number of RBs, and the second type of parallel unicast PDSCH processing capability is limited by the number of RBs. The eRedCap terminal can selectively report these two types of capabilities based on its implementation. Specifically, if both types of capabilities are implemented, i.e., the eRedCap supports both types of capabilities simultaneously, both types of capabilities are reported, and the network device receives both types of capabilities, i.e., steps 2201 and 2202 are executed simultaneously. Or, if the eRedCap supports only one of the capabilities, only the supported capability is reported, and the network device receives only one capability, i.e., steps 2201 or 2202 are executed. Or, if the eRedCap does not support both types of capabilities, neither is reported, i.e., steps 1001 and 1002 are not executed, and the network device does not receive these two types of capabilities.

[0137] In some embodiments, the first type of parallel unicast PDSCH processing capability supports processing X parallel unicast PDSCHs within a certain delay range, and the second type of parallel unicast PDSCH processing capability supports processing Y parallel unicast PDSCHs within a certain delay range, where the set of values ​​for X can be represented as set#1 and the set of values ​​for Y can be represented as set#2, and set#1 and set#2 may be the same or different.

[0138] A possible implementation of the embodiment of this application, the step of receiving the number of second parallel unicast PDSCHs supported by the eRedCap terminal, A step of receiving a first capability report field via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal. Or, The step of receiving a second capability report field via capability signaling, wherein the second capability report field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal.

[0139] A possible implementation of the embodiment of this application is such that the number of the second parallel unicast PDSCH is reported by the eRedCap terminal in response to the processing delay of the parallel unicast PDSCH of the eRedCap terminal being less than or equal to a preset first delay threshold.

[0140] Referring to Figure 23, embodiments of this application further provide a resource scheduling method applicable to network devices, the method may include the following steps: Step 2301: The number of third parallel unicast PDSCHs supported by the eRedCap terminal is received, and the number of third parallel unicast PDSCHs is reported by the eRedCap terminal in response that the processing delay of the eRedCap terminal's parallel unicast PDSCHs is less than or equal to a preset second delay threshold, the second delay threshold being greater than a preset first delay threshold, and the first delay threshold being the processing delay threshold for the parallel unicast PDSCHs of a non-eRedCap terminal. Step 2302: The unicast PDSCH resources of the eRedCap terminal are scheduled based on the number of at least one third parallel unicast PDSCH.

[0141] A possible implementation of the embodiment of this application, the step of receiving the number of third parallel unicast PDSCHs supported by the eRedCap terminal, A step of receiving the number of targets of the eRedCap terminal, wherein the number of targets includes the number of each third parallel unicast PDSCH supported by the eRedCap terminal. Or, The step of receiving the number of targets of the eRedCap terminal, wherein the number of targets includes the maximum value of all third parallel unicast PDSCHs supported by the eRedCap terminal, The second delay threshold is different for each number of third parallel unicast PDSCHs.

[0142] A possible implementation of the embodiment of this application, the step of receiving the number of third parallel unicast PDSCHs supported by the eRedCap terminal, A step of receiving a first capability report field via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal. Or, The step of receiving a second capability report field via capability signaling, wherein the second capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal, The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0143] Corresponding to the resource scheduling method provided by the embodiments in Figures 3 to 17 described above, this application further provides a resource scheduling device. Since the resource scheduling device provided by the embodiments of this application corresponds to the resource scheduling method provided by the embodiments in Figures 3 to 17 described above, the implementation of the resource scheduling method is applied to the resource scheduling device provided by the embodiments of this application, and the embodiments of this application will not be described in detail.

[0144] Figure 24 is a schematic diagram of a resource scheduling device provided by an embodiment of this application, the device being installed in an eRedCap terminal. As shown in Figure 19, the device includes a response module, The response module 2401 is used to report to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal in response to the eRedCap terminal having a first capability. Or, The response module 2401 is used in response to the eRedCap terminal not having a first capability, by not reporting to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal. The first capability described above includes the ability of the eRedCap terminal to process parallel unicast PDSCH.

[0145] A possible implementation of the embodiment of this application is, specifically, the response module 2401, This is used to report to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal, wherein the number of resource blocks (RBs) occupied by the first parallel unicast PDSCH is less than or equal to a first threshold.

[0146] A possible implementation of the embodiment of this application is, specifically, the response module 2401, Used to transmit a first capability report field to the network device via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal. Or, A new capability reporting field is defined and used to obtain a second capability reporting field, the second capability reporting field including the number of first parallel unicast PDSCHs supported by the eRedCap terminal, and is used to transmit the second capability reporting field to the network device via capability signaling. The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0147] A possible implementation of the embodiment of this application is, specifically, the response module 2401, In response to the processing delay of the parallel unicast PDSCH of the eRedCap terminal being less than or equal to a preset first delay threshold, this is used to report the number of first parallel unicast PDSCHs supported by the eRedCap terminal to the network device.

[0148] A possible implementation of the embodiment of this application is, specifically, the response module 2401, This is used to report to the network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal, and the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited by the first threshold.

[0149] A possible implementation of the embodiment of this application is, specifically, the response module 2401, A first capability report field is transmitted to the network device via capability signaling, the first capability report field being an existing capability report field of the capability signaling, and the first capability report field including the number of second parallel unicast PDSCHs supported by the eRedCap terminal. Or, A new capability reporting field is defined to obtain a second capability reporting field, the second capability reporting field including the number of second parallel unicast PDSCHs supported by the eRedCap terminal, and is used to transmit the second capability reporting field to the network device via capability signaling. The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0150] A possible implementation of the embodiment of this application is, specifically, the response module 2401, In response to the processing delay of the parallel unicast PDSCH of the eRedCap terminal being less than or equal to a preset first delay threshold, this is used to report to the network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal.

[0151] A possible implementation of the embodiment of this application is, specifically, the response module 2401, In response to the processing delay of the parallel unicast PDSCH of the eRedCap terminal being less than or equal to a preset second delay threshold, the number of third parallel unicast PDSCHs supported by the eRedCap terminal is reported to the network device, wherein the second delay threshold is greater than a preset first delay threshold, and the first delay threshold is the processing delay threshold for parallel unicast PDSCHs of non-eRedCap terminals.

[0152] A possible implementation of the embodiment of this application is such that the eRedCap terminal supports a number of parallel unicast PDSCHs, and the response module 2401 specifically, The number of third parallel unicast PDSCHs supported by the eRedCap terminal is defined as the number of targets, and this number of targets is reported to the network device. Or, The maximum number of third parallel unicast PDSCHs supported by the eRedCap terminal is defined as the target number, and this target number is used to report the target number to the network device. The second delay threshold is different for each number of third parallel unicast PDSCHs.

[0153] A possible implementation of the embodiment of this application is, specifically, the response module 2401, A first capability report field is transmitted to the network device via capability signaling, the first capability report field being an existing capability report field of the capability signaling, and the first capability report field including the number of third parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps include defining a new capability report field, obtaining a second capability report field, and transmitting the second capability report field to the network device via capability signaling, wherein the second capability report field is used to include the number of third parallel unicast PDSCHs supported by the eRedCap terminal. The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0154] Figure 25 is a schematic diagram of a resource scheduling device provided by an embodiment of the present application, the device being installed in a network device. As shown in Figure 20, the device includes a receiving module 2501 and a scheduling module 2502, The receiving module 2501 is used to receive the number of parallel unicast PDSCHs supported by the eRedCap terminal, reported by the eRedCap terminal in response to the eRedCap terminal having a first capability; the scheduling module 2502 is used to schedule the unicast PDSCH resources of the eRedCap terminal based on the number of parallel unicast PDSCHs supported by the eRedCap terminal. Or, The scheduling module 2502 is used to schedule the unicast PDSCH resources of the eRedCap terminal based on the processing capacity of a single unicast PDSCH of the eRedCap terminal. The first capability described above includes the ability of the eRedCap terminal to process parallel unicast PDSCH.

[0155] A possible implementation of the embodiment of this application is as follows: The receiving module 2501 is specifically: This is used to receive the number of first parallel unicast PDSCHs supported by the eRedCap terminal, and the number of RBs occupied by the supported first parallel unicast PDSCHs is less than or equal to a first threshold.

[0156] A possible implementation of the embodiment of this application is as follows: The receiving module 2501 is specifically: A first capability report field is received via capability signaling, the first capability report field being an existing capability report field of the capability signaling, and the first capability report field including the number of first parallel unicast PDSCHs supported by the eRedCap terminal. Or, Used to receive a second capability report field via capability signaling, the second capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal. The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0157] A possible implementation of the embodiment of this application is such that the number of the first parallel unicast PDSCHs is reported by the eRedCap terminal in response to the processing delay of the parallel unicast PDSCHs of the eRedCap terminal being less than or equal to a preset first delay threshold.

[0158] A possible implementation of the embodiment of this application is as follows: The receiving module 2501 is specifically: The number of second parallel unicast PDSCHs supported by the eRedCap terminal is used to receive the number of RBs occupied by the supported second parallel unicast PDSCHs, and the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited by the first threshold.

[0159] A possible implementation of the embodiment of this application is as follows: The receiving module 2501 is specifically: A first capability report field is received via capability signaling, the first capability report field being an existing capability report field of the capability signaling, and the first capability report field including the number of second parallel unicast PDSCHs supported by the eRedCap terminal. Or, Used to receive a second capability report field via capability signaling, the second capability report field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal.

[0160] A possible implementation of the embodiment of this application is such that the number of the second parallel unicast PDSCH is reported by the eRedCap terminal in response to the processing delay of the parallel unicast PDSCH of the eRedCap terminal being less than or equal to a preset first delay threshold.

[0161] A possible implementation of the embodiment of this application is as follows: The receiving module 2501 is specifically: This is used to receive the number of third parallel unicast PDSCHs supported by the eRedCap terminal, the number of third parallel unicast PDSCHs being reported by the eRedCap terminal in response that the processing delay of the eRedCap terminal's parallel unicast PDSCHs is less than or equal to a preset second delay threshold, the second delay threshold being greater than a preset first delay threshold, the first delay threshold being the processing delay threshold for parallel unicast PDSCHs of non-eRedCap terminals.

[0162] A possible implementation of the embodiment of this application is as follows: The receiving module 2501 is specifically: The number of targets of the eRedCap terminal is received, and the number of targets includes the number of each third parallel unicast PDSCH supported by the eRedCap terminal. Or, Used to receive the number of targets of the eRedCap terminal, the number of targets includes the maximum of the number of third parallel unicast PDSCHs supported by the eRedCap terminal, The second delay threshold is different for each number of third parallel unicast PDSCHs.

[0163] A possible implementation of the embodiment of this application is as follows: The receiving module 2501 is specifically: A first capability report field is received via capability signaling, the first capability report field being an existing capability report field of the capability signaling, and the first capability report field including the number of third parallel unicast PDSCHs supported by the eRedCap terminal. Or, Used to receive a second capability report field via capability signaling, the second capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal. The set of values ​​for the first capability report field is either the same as or different from the set of values ​​for the second capability report field.

[0164] To realize the above-described embodiment, this application further provides a resource scheduling device comprising a processor and memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the device to perform the method described in Figures 2 to 23.

[0165] To realize the above embodiment, this application further provides another resource scheduling device, including a processor and an interface circuit, The interface circuit is used to receive code instructions and transmit them to the processor. The aforementioned processor is used to execute the code instructions and carry out the method described in Figures 2 to 23.

[0166] To realize the above-described embodiment, this application provides a computer-readable storage medium in which instructions are stored, and when the instructions are executed, the method described in Figures 2 to 23 is realized.

[0167] Figure 26 is a block diagram of a terminal device provided by an embodiment of this application. For example, the terminal device 2600 may be a mobile phone, a computer, digital broadcasting user equipment, a message transmission and reception device, a game console, a tablet terminal, a medical device, a fitness device, or a personal digital assistant.

[0168] Referring to Figure 26, the terminal device 2600 may include one or more of the following: processing component 2602, memory 2604, power supply component 2606, multimedia component 2608, audio component 2610, input / output (I / O) interface 2612, sensor component 2614, and communication component 2616.

[0169] The processing component 2602 typically controls the overall operation of the terminal device 2600, including operations related to display, telephone calling, data communication, camera operation, and recording. The processing component 2602 may include one or more processors 2620 for executing instructions to complete all or some of the steps of the above method. In addition, the processing component 2602 may include one or more modules to facilitate interaction with other components. For example, the processing component 2602 may include a multimedia module to facilitate interaction between the multimedia component 2608 and the processing component 2602.

[0170] Memory 2604 is configured to store various types of data, such as instructions for any application programs or methods operated on the terminal device 2600, contact data, phonebook data, messages, photos, and videos, in order to support operations on the terminal device 2600. Memory 2604 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, optical disk, etc.

[0171] The power component 2606 provides power for various components of the terminal device 2600. The power component 2606 may include a power management system, at least one power supply, and components related to generating, managing, and allocating power for other terminal devices 2600.

[0172] The multimedia component 2608 includes a screen that provides an output interface between the terminal device 2600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensors detect not only the boundary of a touch or slide operation, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 2608 includes one front camera and / or a rear camera. When the terminal device 2600 is in an operating mode such as shooting mode or video mode, the front camera and / or rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or may have a focal length and optical zoom capability.

[0173] The audio component 2610 is configured to output and / or input audio signals. For example, the audio component 2610 includes one microphone (MIC), and when the terminal device 2600 is in an operating mode such as calling mode, recording mode, and voice recognition mode, the microphone is configured to receive external audio signals. The received audio signals can be further stored in memory 2604 or transmitted via communication component 2616. In some embodiments, the audio component 2610 further includes one speaker for outputting audio signals.

[0174] The I / O interface 2612 provides an interface between the processing component 2602 and a peripheral interface module, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to, a home button, volume buttons, a start button, and a lock button.

[0175] The sensor component 2614 includes at least one or more sensors to provide various forms of state evaluation for the terminal device 2600. For example, the sensor component 2614 can detect the on / off state of the terminal device 2600, the relative positioning of components, for example, the display and keypad of the terminal device 2600, and the sensor component 2614 can also detect changes in the position of the terminal device 2600 or its components, whether or not a user is in contact with the terminal device 2600, the orientation or acceleration / deceleration of the terminal device 2600, and temperature changes of the terminal device 2600. The sensor component 2614 may also include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. The sensor component 2614 may further include an optical sensor, such as a CMOS or CCD image sensor for use in imaging applications. In some embodiments, the sensor component 2614 may further include an accelerometer, gyroscope, magnetic sensor, pressure sensor, or temperature sensor.

[0176] The communication component 2616 is configured to facilitate wired or wireless communication between the terminal device 2600 and other devices. The terminal device 2600 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 2616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 2616 further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT)® technology, and other technologies.

[0177] In exemplary embodiments, the terminal device 2600 may be implemented by at least one dedicated integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing unit (DSPD), a programmable logic device (PLD), a field-programmable gate array (FPGA), a controller, a microcontroller, a microprocessor, or other electronic components to perform the methods shown in Figures 2 to 23 above.

[0178] Figure 27 is a block diagram of a network device provided by an embodiment of the present application. As shown in Figure 27, the network device 2700 includes a processing component 2722, further including at least one processor and memory resources, including memory 2732, which are used to store instructions executable by the processing component 2722, such as application programs. The application programs stored in memory 2732 may include one or more modules, each corresponding to a set of instructions. The processing component 2722 is configured to execute instructions, thereby performing any method applicable to the base station of the above method, for example, at least one of the methods described in any of the Figures 3 to 17.

[0179] The network device 2700 may further include a power component 2726 configured to perform power management for the network device 2700, a wired or wireless network interface 2750 configured to connect the network device 2700 to a network, and an input / output (I / O) interface 2758. The network device 2700 can operate an operating system stored in memory 2732, such as Windows Server™, Mac OS X™, Unix™, Linux™®, FreeBSD™, or a similar system.

[0180] In exemplary embodiments, a non-temporary computer-readable storage medium containing instructions is further provided, for example, a memory 804 containing instructions, which can be executed by a processor 2620 of a terminal device 2600 to complete the method shown in Figures 2 to 23 above. For example, the non-temporary computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, tape, floppy disk, or optical data storage device.

[0181] As those skilled in the art will see, the various illustrative logical blocks and steps enumerated in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the overall system. Those skilled in the art can implement the functions in various ways for each specific application, but such implementations should not be understood as exceeding the scope of protection of the embodiments of this application.

[0182] In the embodiments described above, all or part of them can be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of them can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer programs are loaded and executed on a computer, all or part of the flows or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. The computer programs can be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer programs can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, radio, microwave, etc.). The computer-readable storage medium may be any available media accessible to a computer, or a data storage device such as a server or data center that includes one or more available media integrations. The usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

[0183] As those skilled in the art will understand, the various numerical designations such as "1st," "2nd," etc., in this application are classifications made for the purpose of facilitating explanation and do not limit the scope of the embodiments of this application, but also represent priority.

[0184] In this application, “at least one” may also be described as “one or more,” where “more” may be two, three, four or more, and is not limited to this application. In the embodiments of this application, for a single technical feature, technical features of that type are distinguished by “first,” “second,” “third,” “A,” “B,” “C,” and “D,” and there is no priority or size order among the technical features described by “first,” “second,” “third,” “A,” “B,” “C,” and “D.”

[0185] The correspondences shown in each table in this application may be set in advance or defined in advance. The possible values ​​of the information in each table are merely examples and may be set to other values, and are not limited in this application. When setting the correspondence between information and each parameter, it is not necessary to set all the correspondences shown in each table. For example, in the tables of this application, the correspondences shown in some rows may not be set. Also, appropriate modifications and adjustments such as splitting and joining may be made to the above tables. The names of the parameters shown in the themes of each table above may also be called by other names that are understandable to the communication device, and the possible values ​​or representation methods of those parameters may also be other possible values ​​or representation methods that are understandable to the communication device. When the above tables are implemented, other data structures such as arrays, queues, containers, stacks, linked lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables may be used.

[0186] In this application, "predefinition" may be understood as definition, predefinition, memory, pre-storage, pre-specification, pre-setting, curing, or pre-firing.

[0187] As those skilled in the art will understand, the units and algorithmic steps described in each example disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are performed in hardware or in software depends on the specific application of the proposed technology and the design constraints. Those skilled in the art may implement the described functions in different ways for each specific application, but such implementations should not be considered beyond the scope of this application.

[0188] For the convenience and simplification of the explanation, and so that those skilled in the art can clearly understand, the specific working processes of the systems, apparatus, and units described above are omitted here, and should be referred to by the corresponding processes in the embodiments of the methods described above.

[0189] The above describes only specific embodiments of this application, and the scope of protection of this application is not limited thereto. Any changes or substitutions that a person skilled in the art could easily conceive of, as long as they do not deviate from the technical scope disclosed in this application, should be included in the scope of protection of this application. Therefore, the scope of protection of this application must be in accordance with the claims described above.

Claims

1. A resource scheduling method applicable to an extended reduced capacity (eRedCap) terminal, In response to the eRedCap terminal having a first capability, the eRedCap terminal reports to the network device the number of parallel unicast physical downlink shared channels (PDSCH) supported by the eRedCap terminal. Or, The step of not reporting to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal in response that the eRedCap terminal does not have a first capability, The first capability includes the ability of the eRedCap terminal to process parallel unicast PDSCH, A resource scheduling method characterized by the following features.

2. The step of reporting to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal is: A step of reporting to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal, the step of determining that the number of resource blocks (RBs) occupied by the first parallel unicast PDSCH is less than or equal to a first threshold, The resource scheduling method according to feature 1.

3. The step of reporting to the network device the number of first parallel unicast PDSCHs supported by the eRedCap terminal is: A step of transmitting a first capability report field to the network device via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps include defining a new capability report field, obtaining a second capability report field, and transmitting the second capability report field to the network device via capability signaling, wherein the second capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, The set of values ​​for the first capability reporting field is the same as or different from the set of values ​​for the second capability reporting field. The resource scheduling method according to feature 2.

4. The step of reporting to the network device the number of first parallel unicast PDSCHs supported by the eRedCap terminal is: The process includes the step of reporting to the network device the number of first parallel unicast PDSCHs supported by the eRedCap terminal, in response that the processing delay of the parallel unicast PDSCH of the eRedCap terminal is less than or equal to a preset first delay threshold. The resource scheduling method according to claim 2 or 3, characterized by the features described above.

5. The step of reporting to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal is: The step includes reporting to a network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal, wherein the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited by a first threshold. The resource scheduling method according to any one of the features 1 to 3.

6. The step of reporting to the network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal is: A step of transmitting a first capability report field to the network device via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps include defining a new capability report field, obtaining a second capability report field, and transmitting the second capability report field to the network device via capability signaling, wherein the second capability report field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal, The set of values ​​for the first capability reporting field is the same as or different from the set of values ​​for the second capability reporting field. The resource scheduling method according to feature 5.

7. The step of reporting to the network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal is: The process includes the step of reporting to the network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal, in response that the processing delay of the parallel unicast PDSCH of the eRedCap terminal is less than or equal to a preset first delay threshold. The resource scheduling method according to feature 5.

8. The step of reporting to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal is: A step of reporting to the network device the number of third parallel unicast PDSCHs supported by the eRedCap terminal, in response that the processing delay of the parallel unicast PDSCH of the eRedCap terminal is less than or equal to a preset second delay threshold, wherein the second delay threshold is greater than a preset first delay threshold, and the first delay threshold is the processing delay threshold of the parallel unicast PDSCH of a non-eRedCap terminal. The resource scheduling method according to feature 1.

9. The eRedCap terminal supports a number of parallel unicast PDSCHs, and the step of reporting the number of third parallel unicast PDSCHs supported by the eRedCap terminal to the network device is: The number of targets is defined as the number of third parallel unicast PDSCHs supported by the eRedCap terminal, and the number of targets is reported to the network device. Or, The step includes taking the maximum number of third parallel unicast PDSCHs supported by the eRedCap terminal as the target number, and reporting the target number to the network device, The second delay threshold corresponding to the number of third parallel unicast PDSCHs is different. The resource scheduling method according to claim 8.

10. The step of reporting to the network device the number of third parallel unicast PDSCHs supported by the eRedCap terminal is: A step of transmitting a first capability report field to the network device via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps include defining a new capability report field, obtaining a second capability report field, and transmitting the second capability report field to the network device via capability signaling, wherein the second capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal, The set of values ​​for the first capability reporting field is the same as or different from the set of values ​​for the second capability reporting field. The resource scheduling method according to claim 8 or 9, characterized in that it is as follows:

11. A resource scheduling method applied to network devices, The steps of receiving the number of parallel unicast PDSCHs supported by the eRedCap terminal, reported by the eRedCap terminal in response to the eRedCap terminal having a first capability, and scheduling the unicast PDSCH resources of the eRedCap terminal based on the number of parallel unicast PDSCHs supported by the eRedCap terminal. Or, The step includes scheduling the unicast PDSCH resources of the eRedCap terminal based on the processing capacity of a single unicast PDSCH of the eRedCap terminal, The first capability includes the ability of the eRedCap terminal to process parallel unicast PDSCH, A resource scheduling method characterized by the following features.

12. The step of receiving the number of parallel unicast PDSCHs supported by the eRedCap terminal, reported by the eRedCap terminal in response to the eRedCap terminal having a first capability, The process includes receiving the number of first parallel unicast PDSCHs supported by the eRedCap terminal, wherein the number of RBs occupied by the supported first parallel unicast PDSCHs is less than or equal to a first threshold. The resource scheduling method according to claim 11.

13. The step of receiving the number of first parallel unicast PDSCHs supported by the eRedCap terminal is: A step of receiving a first capability report field via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps include receiving a second capability report field via capability signaling, wherein the second capability report field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal, The set of values ​​for the first capability reporting field is the same as or different from the set of values ​​for the second capability reporting field. The resource scheduling method according to feature 12.

14. The number of the first parallel unicast PDSCH is reported by the eRedCap terminal in response to the eRedCap terminal's processing delay of the parallel unicast PDSCH being less than or equal to a preset first delay threshold. The resource scheduling method according to claim 12 or 13, characterized by the features described herein.

15. The step of receiving the number of parallel unicast PDSCHs supported by the eRedCap terminal, reported by the eRedCap terminal in response to the eRedCap terminal having a first capability, The step of receiving the number of second parallel unicast PDSCHs supported by the eRedCap terminal, the number of RBs occupied by the supported second parallel unicast PDSCHs is not limited by a first threshold, The resource scheduling method according to any one of claims 11 to 13.

16. The step of receiving the number of second parallel unicast PDSCHs supported by the eRedCap terminal is: A step of receiving a first capability report field via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes a number of second parallel unicast PDSCHs supported by the eRedCap terminal. Or, The step of receiving a second capability report field via capability signaling, wherein the second capability report field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal. The resource scheduling method according to claim 15.

17. The number of the second parallel unicast PDSCH is reported by the eRedCap terminal in response to the eRedCap terminal's processing delay of the parallel unicast PDSCH being less than or equal to a preset first delay threshold. The resource scheduling method according to claim 15.

18. The step of receiving the number of parallel unicast PDSCHs supported by the eRedCap terminal, reported by the eRedCap terminal in response to the eRedCap terminal having a first capability, The step of receiving the number of third parallel unicast PDSCHs supported by the eRedCap terminal, the number of third parallel unicast PDSCHs being reported by the eRedCap terminal in response that the processing delay of the eRedCap terminal's parallel unicast PDSCHs is less than or equal to a preset second delay threshold, the second delay threshold being greater than a preset first delay threshold, and the first delay threshold being the processing delay threshold for non-eRedCap terminal parallel unicast PDSCHs. The resource scheduling method according to claim 11.

19. The eRedCap terminal supports a number of parallel unicast PDSCHs, The step of receiving the number of third parallel unicast PDSCHs supported by the eRedCap terminal is: A step of receiving the number of targets of the eRedCap terminal, wherein the number of targets includes the number of each third parallel unicast PDSCH supported by the eRedCap terminal. Or, The step of receiving the number of targets of the eRedCap terminal, wherein the number of targets includes the maximum value of all third parallel unicast PDSCHs supported by the eRedCap terminal, The second delay threshold corresponding to the number of third parallel unicast PDSCHs is different. The resource scheduling method according to claim 18.

20. The step of receiving the number of third parallel unicast PDSCHs supported by the eRedCap terminal is: A step of receiving a first capability report field via capability signaling, wherein the first capability report field is an existing capability report field of the capability signaling, and the first capability report field includes a number of third parallel unicast PDSCHs supported by the eRedCap terminal. Or, The steps include receiving a second capability report field via capability signaling, wherein the second capability report field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal, and the second capability report field is a new capability report field defined by the eRedCap terminal, The set of values ​​for the first capability reporting field is the same as or different from the set of values ​​for the second capability reporting field. The resource scheduling method according to claim 18 or 19, characterized in that it is the same as described above.

21. A resource scheduling device, A response module for reporting to a network device the number of parallel unicast PDSCHs supported by the eRedCap terminal in response to the eRedCap terminal having a first capability, Or, The eRedCap terminal does not have a first capability, and in response to this, the eRedCap terminal does not report to the network device the number of parallel unicast PDSCHs supported by the eRedCap terminal, including a response module for not reporting the number of parallel unicast PDSCHs supported by the eRedCap terminal to the network device, The first capability includes the ability of the eRedCap terminal to process parallel unicast PDSCH, A resource scheduling device characterized by the following features.

22. A resource scheduling device, A receiving module for receiving the number of parallel unicast PDSCHs supported by the eRedCap terminal, reported by the eRedCap terminal in response to the eRedCap terminal having a first capability; and a scheduling module for scheduling the unicast PDSCH resources of the eRedCap terminal based on the number of parallel unicast PDSCHs supported by the eRedCap terminal. Or, Includes a scheduling module for scheduling the unicast PDSCH resources of the eRedCap terminal based on the processing capacity of a single unicast PDSCH of the eRedCap terminal, The first capability includes the ability of the eRedCap terminal to process parallel unicast PDSCH, A resource scheduling device characterized by the following features.

23. A resource scheduling device, A device comprising a processor and memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the device to perform the method according to any one of claims 1 to 10 or the method according to any one of claims 11 to 20. A resource scheduling device characterized by the following features.

24. A resource scheduling device, It includes a processor and interface circuitry, The interface circuit is used to receive code instructions and transmit them to the processor. The processor is used to execute the code instructions to carry out the method according to any one of claims 1 to 10, or the method according to any one of claims 11 to 20. A resource scheduling device characterized by the following features.

25. A computer-readable storage medium in which instructions are stored, When the aforementioned instruction is executed, the method according to any one of claims 1 to 10, or the method according to any one of claims 11 to 20, is realized. A computer-readable storage medium characterized by the following features.

Images