Method and device for resource planning

Abstract

FIELD: method and device for resource planning.SUBSTANCE: eRedCap terminal provides the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the eRedCap terminal has the first capability; or the eRedCap terminal does not provide the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the eRedCap terminal does not have the first capability, where the first capability is the capability of the eRedCap terminal to process parallel unicast PDSCH channels. The eRedCap terminal provides the number of supported parallel unicast PDSCH channels so that the base station can determine the eRedCap terminal's capability to handle parallel unicast PDSCH channels, enabling intelligent scheduling of unicast PDSCH channels for the eRedCap terminal.EFFECT: possibility of determining the number of PDSCH channels (physical downlink shared channels) that the eRedCap terminal (an advanced terminal with simplified capabilities) can process in parallel within a certain range of data processing delay.13 cl, 27 dwg

Description

Field of technology to which the present invention relates

[0001] The present invention relates to the field of communication technology, in particular, to a method and device for collecting data. Prior art of the present invention

[0002] In order to reduce the cost of RedCap terminals, one possible solution is to reduce the baseband bandwidth of the RedCap terminal's data link to 5 MHz. Such RedCap terminals that support the reduced baseband bandwidth are called enhanced RedCap terminals. For eRedCap terminals, the amount of resources at a subcarrier spacing (SCS) of 15 / 30 kHz does not exceed 25 / 12 resource blocks (RBs). When performing a number of operations such as channel estimation, channel equalization, signal detection, and demodulation, the eRedCap terminal processes the PDSCH (Physical Downlink Shared Channel) based on the amount of resources of 25 / 12 RBs; however, when the amount of received resources exceeds 25 / 12 RBs, the eRedCap terminal needs to process the received data multiple times, which results in additional processing delay.Based on this, an urgent problem that needs to be solved is to be able to determine the number of PDSCH channels that the eRedCap terminal can process in parallel within a certain range of data processing delay.Brief disclosure of the present invention.

[0003] Embodiments of the present invention provide a method, device, and system for resource scheduling so that a base station can determine the number of parallel unicast PDSCH channels that an eRedCap terminal can process within a certain processing delay range, thereby ensuring reasonable scheduling of unicast PDSCH channels for the eRedCap terminal.

[0004] According to a first aspect of the present invention, embodiments thereof provide a method for scheduling resources, wherein the method is applicable to an eRedCap terminal and comprises:

[0005] Grants the network device the number of parallel unicast PDSCH channels supported by the eRedCap terminal based on the eRedCap terminal's first capability;

[0006] or

[0007] Failure to provide the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal due to the fact that the eRedCap terminal does not have the first opportunity;

[0008] wherein the first capability includes the capability of the eRedCap terminal to handle parallel unicast PDSCH channels.

[0009] In one embodiment of the present invention, providing the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal includes:

[0010] providing the network device with the number of first parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of resource blocks (RBs) occupied by the first parallel unicast PDSCH channels is less than or equal to the first threshold value.

[0011] In one embodiment of the present invention, providing the network device with the number of first parallel unicast PDSCH channels supported by the eRedCap terminal comprises:

[0012] sending a first opportunity message field in the capability signaling information to the network device, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes the number of first parallel unicast PDSCH channels supported by the eRedCap terminal;

[0013] or

[0014] setting a new capability message field to receive a second capability message field, wherein the second capability message field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal; and sending the second capability message field in capability signaling information to the network device;

[0015] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0016] In one embodiment of the present invention, providing the network device with the number of first parallel unicast PDSCH channels supported by the eRedCap terminal comprises:

[0017] Provides the network device with the number of the first parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to the preset first delay threshold.

[0018] In one embodiment of the present invention, providing the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal includes:

[0019] providing the network device with the number of second parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RBs occupied by the second parallel unicast PDSCH channels supported by the eRedCap terminal is not limited by the first threshold.

[0020] In one embodiment of the present invention, providing the network device with the number of second parallel unicast PDSCH channels supported by the eRedCap terminal comprises:

[0021] sending to the network device a first capability message field in the capability signaling information, wherein the first capability message field is a predetermined capability message field in the capability signaling information, and the first capability message field includes a number of second parallel unicast PDSCH channels supported by the eRedCap terminal;

[0022] or

[0023] setting a new capability message field to obtain a second capability message field, wherein the second capability message field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal; and sending the second capability message field in capability signaling information to the network device;

[0024] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0025] In one embodiment of the present invention, providing to the network device the number of second parallel unicast PDSCH channels supported by the eRedCap terminal comprises:

[0026] Grants the network device the number of second parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a preset first delay threshold.

[0027] In one embodiment of the present invention, providing the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal includes:

[0028] providing the network device with the number of third parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by 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 a processing delay threshold of the parallel unicast PDSCH channels by a terminal that is not an eRedCap terminal.

[0029] In one embodiment of the present invention, the eRedCap terminal supports a plurality of values ​​of the number of third parallel unicast PDSCH channels, and providing the number of third parallel unicast PDSCH channels supported by the eRedCap terminal to the network device includes:

[0030] Provides the network device with target quantity values ​​that are all multiple quantities of the third parallel unicast PDSCHs supported by the eRedCap terminal;

[0031] or

[0032] Provides the network device with a target quantity that is the maximum value of the multiple values ​​of the quantity of third parallel unicast PDSCHs supported by the eRedCap terminal;

[0033] wherein multiple values ​​of the number of third parallel unicast PDSCH channels correspond to different second delay threshold values.

[0034] In one embodiment of the present invention, providing the network device with the number of third parallel unicast PDSCH channels supported by the eRedCap terminal comprises:

[0035] sending a first opportunity message field in the capability signaling information to the network device, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes the number of third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0036] or

[0037] defining a new capability message field for obtaining a second capability message field, wherein the second capability message field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal; and sending the second capability message field in capability signaling information to the network device;

[0038] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0039] According to a second aspect of the present invention, embodiments thereof provide a method for scheduling resources, wherein the method is applicable to a network device and comprises:

[0040] obtaining the number of concurrent unicast PDSCHs (Physical Downlink Shared Channels) supported by the eRedCap terminal (evolved lightweight terminal) transmitted by the eRedCap terminal based on the fact that the eRedCap terminal has the first opportunity; and scheduling the unicast PDSCH resources for the eRedCap terminal based on the number of concurrent unicast PDSCHs supported by the eRedCap terminal;

[0041] or

[0042] Scheduling unicast PDSCH resources for the eRedCap terminal based on the eRedCap terminal's ability to handle one unicast PDSCH channel;

[0043] wherein the first capability includes the capability of the eRedCap terminal to handle parallel unicast PDSCH channels.

[0044] In one embodiment of the present invention, obtaining the number of parallel unicast PDSCH channels supported by the eRedCap terminal transmitted by the eRedCap terminal upon the fact that the eRedCap terminal has the first opportunity includes:

[0045] obtaining the number of the first parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of resource blocks (RBs) occupied by the first parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to the first threshold value.

[0046] In one embodiment of the present invention, obtaining the number of first parallel unicast PDSCH channels supported by the eRedCap terminal includes:

[0047] receiving a first opportunity message field in the capability signaling information, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes the number of first parallel unicast PDSCH channels supported by the eRedCap terminal;

[0048] or

[0049] receiving a second opportunity message field in the capability signaling information, wherein the second opportunity message field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, and the second opportunity message field is a new capability message field set by the eRedCap terminal;

[0050] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0051] In one embodiment of the present invention, the number of first parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined first delay threshold.

[0052] In one embodiment of the present invention, obtaining the number of parallel unicast PDSCH channels supported by the eRedCap terminal provided by the eRedCap terminal based on the fact that the eRedCap terminal has the first opportunity comprises:

[0053] Obtaining the number of second parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of resource blocks (RBs) occupied by the second parallel unicast PDSCH channels supported by the eRedCap terminal is not limited by the first threshold.

[0054] In one embodiment of the present invention, obtaining the number of second parallel unicast PDSCH channels supported by the eRedCap terminal includes:

[0055] receiving a first capability message field in the capability signaling information, wherein the first capability message field is a predetermined capability message field in the capability signaling information, and the first capability message field includes a number of second parallel unicast PDSCH channels supported by the eRedCap terminal;

[0056] or

[0057] receiving a second opportunity message field in the capability signaling information, wherein the second opportunity message field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal, and the second opportunity message field is a new capability message field set by the eRedCap terminal.

[0058] In one embodiment of the present invention, the number of second parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined first delay threshold.

[0059] In one embodiment of the present invention, obtaining the number of parallel unicast PDSCH channels supported by the eRedCap terminal provided by the eRedCap terminal based on the fact that the eRedCap terminal has the first opportunity includes:

[0060] obtaining a number of third parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of third parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined second delay threshold, wherein the predetermined second delay threshold exceeds a predetermined first delay threshold, and the first delay threshold is a delay threshold for processing the parallel unicast PDSCH channels by a terminal that is not an eRedCap terminal.

[0061] In one embodiment of the present invention, the eRedCap terminal supports a plurality of values ​​of the number of third parallel unicast PDSCH channels, and obtaining the number of third parallel unicast PDSCH channels supported by the eRedCap terminal includes:

[0062] receiving target quantity values ​​from the eRedCap terminal, wherein these target quantities are all multiple quantities of the third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0063] or

[0064] receiving a target number from the eRedCap terminal, wherein the target number is a maximum value of a plurality of values ​​of the number of third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0065] wherein multiple values ​​of the number of third parallel unicast PDSCH channels correspond to different second delay threshold values.

[0066] In one embodiment of the present invention, obtaining the number of third parallel unicast PDSCH channels supported by the eRedCap terminal includes:

[0067] receiving a first opportunity message field in the capability signaling information, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes the number of third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0068] or

[0069] receiving a second opportunity message field of the capability signaling information, wherein the second opportunity message field includes the number of third parallel unicast PDSCH channels supported by the eRedCap terminal, and the second opportunity message field is a new capability message field set by the eRedCap terminal;

[0070] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0071] According to a third aspect of the present invention, embodiments thereof provide a resource scheduling device, wherein the device is located in an eRedCap terminal and includes:

[0072] a response module configured to provide the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the eRedCap terminal has the first capability;

[0073] or

[0074] a response module configured to not provide the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal due to the fact that the eRedCap terminal does not have the first option;

[0075] wherein the first capability includes the capability of the eRedCap terminal to handle parallel unicast PDSCH channels.

[0076] According to a fourth aspect of the present invention, embodiments thereof provide a resource scheduling device, wherein the device is located in a network device and includes:

[0077] a receiving module configured to obtain the number of parallel unicast PDSCH channels supported by the eRedCap terminal provided by the eRedCap terminal based on the fact that the eRedCap terminal has the first opportunity; and a scheduling module configured to schedule unicast PDSCH channel resources for the eRedCap terminal based on the number of parallel unicast PDSCH channels supported by the eRedCap terminal;

[0078] or

[0079] a scheduling module configured to schedule unicast PDSCH channel resources for an eRedCap terminal based on the eRedCap terminal's ability to process one unicast PDSCH channel;

[0080] wherein the first capability includes the capability of the eRedCap terminal to handle parallel unicast PDSCH channels.

[0081] According to a fifth aspect of the present invention, embodiments thereof provide a resource scheduling device, wherein the device includes 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, initiating the implementation by the proposed device of the method according to the first aspect or the second aspect of the present invention.

[0082] According to a sixth aspect of the present invention, embodiments thereof provide a resource scheduling device, including: a processor and an interface circuit;

[0083] wherein the interface circuit is configured to receive code commands and transmit code commands to the processor, and

[0084] the processor is configured to execute code instructions for the purpose of implementing the method according to the first aspect or the second aspect of the present invention.

[0085] According to a seventh aspect of the present invention, embodiments thereof provide a machine-readable storage medium on which instructions are stored, the execution of which initiates the implementation of the method according to the first aspect of the present invention or initiates the implementation of the method according to the second aspect of the present invention.

[0086] The resource scheduling method and device according to the embodiments of the present invention provide the possibility of providing the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the eRedCap terminal has the first opportunity; or the possibility of not providing the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the eRedCap terminal does not have the first opportunity, wherein the first opportunity includes the possibility of processing the parallel unicast PDSCH channels by the eRedCap terminal.The solutions implemented in the embodiments of the present invention allow the base station to determine the ability of the eRedCap terminal to process parallel unicast PDSCH channels by providing the eRedCap terminal with the number of parallel unicast PDSCH channels that it is capable of processing, which allows the base station to intelligently schedule unicast PDSCH channels for the eRedCap terminal, eliminates the need for the eRedCap terminal to repeatedly re-process the received data and introduce additional delay, which could lead to the eRedCap terminal not performing a timely HARQ-ACK feedback (acknowledgment within the hybrid automatic repeat request for data) upon receipt of HARQ resources or only performing a NACK feedback (negative acknowledgment that the data was received with errors or not received at all), which would entail a waste of resources and an increase in the energy consumption of the terminal.Brief description of the drawings.

[0087] In order to more clearly illustrate the technical solutions implemented in the embodiments of the present invention or in the prior art, drawings necessary for the embodiments of the present invention or in the prior art are briefly described below.

[0088] Fig. 1 is a schematic diagram showing a communication system according to one embodiment of the present invention;

[0089] Fig. 2 is a flow chart illustrating a resource scheduling method according to one embodiment of the present invention;

[0090] Fig. 3 is a flow chart illustrating a resource scheduling method according to one embodiment of the present invention;

[0091] Fig. 4 is a flow chart illustrating a resource scheduling method according to one embodiment of the present invention;

[0092] Fig. 5 is a flow chart illustrating a resource scheduling method according to one embodiment of the present invention;

[0093] Fig. 6 is a flow chart illustrating a resource scheduling method according to one embodiment of the present invention;

[0094] Fig. 7 is a block diagram of providing a number of first parallel unicast PDSCH channels using a first opportunity message field according to one embodiment of the present invention;

[0095] Fig. 8 is a block diagram of providing a number of first parallel unicast PDSCH channels using a second opportunity message field according to one embodiment of the present invention;

[0096] Fig. 9 is a flowchart illustrating a resource scheduling method according to one embodiment of the present invention;

[0097] Fig. 10 is a flow chart illustrating a resource scheduling method according to one embodiment of the present invention;

[0098] Fig. 11 is a flow chart illustrating a resource scheduling method according to one embodiment of the present invention;

[0099] Fig. 12 is a block diagram of providing a number of second parallel unicast PDSCH channels using a first opportunity message field according to one embodiment of the present invention;

[0100] Fig. 13 is a block diagram of providing a number of second parallel unicast PDSCH channels using a second opportunity message field according to one embodiment of the present invention;

[0101] Fig. 14 is a flowchart illustrating a resource scheduling method according to one embodiment of the present invention;

[0102] Fig. 15 is a block diagram of providing a number of third parallel unicast PDSCH channels based on different delay thresholds according to one embodiment of the present invention;

[0103] Fig. 16 is a block diagram of providing a number of third parallel unicast PDSCH channels using a first opportunity message field according to one embodiment of the present invention;

[0104] Fig. 17 is a block diagram of providing a number of third parallel unicast PDSCH channels using a second opportunity message field according to one embodiment of the present invention;

[0105] Fig. 18 is a flowchart illustrating a resource scheduling method according to one embodiment of the present invention;

[0106] Fig. 19 is a flowchart illustrating a resource scheduling method according to one embodiment of the present invention;

[0107] Fig. 20 is a flowchart illustrating a resource scheduling method according to one embodiment of the present invention;

[0108] Fig. 21 is a flow chart illustrating a resource scheduling method according to one embodiment of the present invention;

[0109] Fig. 22 is a flowchart illustrating a resource scheduling method according to one embodiment of the present invention;

[0110] Fig. 23 is a flowchart illustrating a resource scheduling method according to one embodiment of the present invention;

[0111] Fig. 24 is a schematic diagram of the structure of a resource scheduling device according to one embodiment of the present invention;

[0112] Fig. 25 is a schematic diagram of the structure of another resource scheduling device according to one embodiment of the present invention;

[0113] Fig. 26 shows a block diagram of a terminal according to one embodiment of the present invention; and

[0114] Fig. 27 shows a block diagram of a network device according to one embodiment of the present invention. Detailed disclosure of the present invention

[0115] The present document will describe in detail illustrative embodiments of the claimed invention, examples of which are illustrated in the accompanying drawings. When reference is made to the drawings in the following description, the same numbers in different drawings designate the same or similar elements, unless otherwise indicated. The embodiment examples described within the framework of the disclosure of illustrative embodiments of the present invention do not represent all embodiment examples corresponding to the embodiments of the present invention. Rather, they serve only as examples of the implementation of devices and methods corresponding to certain aspects of the embodiments of the present invention, as detailed in the appended claims.

[0116] The terms used in the disclosure of embodiments of the present invention are intended solely to describe particular embodiments thereof and do not in any way limit the embodiments of the claimed invention. The singular forms indicated by the indefinite and definite articles used in the description of embodiments of the present invention, as well as in the appended claims, are intended to also cover the plural forms, unless the context clearly dictates otherwise. It should also be understood that, as used herein, the term "and / or" refers to and includes any possible combinations of one or more associated listed elements.

[0117] It should be understood that although terms such as "first," "second," "third," etc. may be used in the disclosure of embodiments of the present invention to describe various types of information, this information should not be limited to these terms. These terms are used only to distinguish between similar types of information. For example, without departing from the scope of the embodiments of the present invention, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" or "when" used herein may be interpreted as "during," "upon," or "upon determining that."

[0118] Embodiments of the present invention are described in detail below. Examples of the implementation of these embodiments are illustrated in the accompanying drawings, where the same or similar reference numerals designate the same or similar elements. When reference is made to the drawings in the following description, the same numerals in different drawings designate the same or similar elements, unless otherwise specified. The implementation examples described within the framework of the disclosure of illustrative embodiments of the present invention do not represent all implementation examples corresponding to the embodiments of the present invention. Rather, they serve only as examples of the implementation of devices and methods corresponding to certain aspects of the embodiments of the present invention, as detailed in the appended claims.

[0119] The terms used in the disclosure of embodiments of the present invention are intended solely to describe particular embodiments thereof and do not limit the embodiments of the claimed invention in any way. The singular forms indicated by the indefinite and definite articles used in the description of embodiments of the present invention, as well as in the appended claims, are intended to cover the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that, as used herein, the term "and / or" refers to and includes any possible combinations of one or more associated listed elements.

[0120] It should be understood that although terms such as "first," "second," "third," etc. may be used in the disclosure of embodiments of the present invention to describe various types of information, this information should not be limited to these terms. These terms are used only to distinguish between similar types of information. For example, without departing from the scope of the embodiments of the present invention, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" or "when" used herein may be interpreted as "during," "upon," or "upon determining that."

[0121] Embodiments of the claimed invention are described in detail below, examples of which are shown in the drawings, where the same or similar elements are designated by the same or similar reference numerals. The embodiments of the present invention described below in connection with the drawings are illustrative in nature and are intended to clarify the essence of the claimed invention, and they should not be construed as limiting the present invention.

[0122] In order to better understand the resource scheduling method disclosed in the description of embodiments of the present invention, a communication system applicable to embodiments of the claimed invention will first be described below.

[0123] Referring to Fig. 1, a communication system according to one embodiment of the present invention is schematically shown. This communication system may include, among other things, one network device and one terminal, wherein the terminal communicates with the network device. The number and shape of the devices shown in Fig. 1 are presented solely for illustration purposes and in no way limit the present invention. In practice, two or more network devices and two or more terminals may be provided. The communication system shown in Fig. 1 includes one network device 101 and one terminal 102.

[0124] For example, the terminal can be the eRedCap terminal.

[0125] It should be noted that the technical solutions implemented in the embodiments of the present invention can be applied to various communication systems, such as: LTE (Long Term Evolution) systems, 5G (fifth generation mobile communication systems), 5G NR (fifth generation New Radio) systems or other promising new mobile communication systems, etc.

[0126] A network device according to the embodiments of the present invention is a structural unit on the network side for transmitting or receiving signals. For example, the network device 101 may be an enhanced base station (eNB) in a 4G network, a transmit / receive point (TRP), a next-generation NodeB (gNB) in a NR (New Radio) system, a base station in other advanced mobile communication systems, or an access node in a Wi-Fi wireless communication system (a wireless Internet access technology according to the IEEE 802.1 1x standard), etc. The embodiments of the present invention do not limit the network device to a specific technology and a specific shape. The network device according to the embodiments of the present invention may be composed of a central unit (CU) and a distributed unit (DU), where the CU may also be referred to as a control unit.The CU-DU structure allows the protocol layers of a network device such as a base station to be separated, with the functions of some protocol layers being located in the CU for centralized management, and the functions of the remaining or all protocol layers being distributed in the DU, which is centrally managed by the CU.

[0127] A terminal according to the embodiments of the present invention is a structural unit located at the user's end, such as a mobile phone, and which is designed to receive transmitted signals. A terminal may also be referred to as a terminal device, a mobile station (MS), a mobile terminal (MT), and the like.The terminal may be a car with a data exchange function, an intelligent car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal for controlling industrial processes, a wireless terminal in automatic driving systems, a wireless terminal for remote surgery, a wireless terminal in an intelligent network, a wireless terminal in transport security systems, a wireless terminal for smart city systems, a wireless terminal for smart home systems, etc. Embodiments of the present invention do not limit the terminal to a specific technology and a specific form.

[0128] Since the eRedCap terminal, which supports a baseband bandwidth of 5 MHz, has a radio frequency range of 20 MHz, it can receive data exceeding 25 / 12 RB blocks and cache the received data after processing by the OFDM (orthogonal frequency division multiplexing) method. If two unicast PDSCH channels with frequency division multiplexing (FDM) are outside the 5 MHz bandwidth, the eRedCap terminal must process the received data multiple times, which results in additional processing delay.

[0129] Based on this, embodiments of the present invention provide a resource scheduling method and device that enable a base station to determine whether an eRedCap terminal can process parallel unicast PDSCH channels by providing the eRedCap terminal with the number of parallel unicast PDSCH channels that it is capable of processing, which enables the base station to intelligently schedule unicast PDSCH channels for the eRedCap terminal, eliminating the need for the eRedCap terminal to repeatedly re-process received data and introduce additional delay, which could result in the eRedCap terminal not performing the HARQ-ACK feedback in time when HARQ resources are received, or only performing the NACK feedback, which would entail wasting resources and increasing the power consumption of the terminal.

[0130] One embodiment of the present invention, which is illustrated in Fig. 2, provides a method for scheduling resources. As shown in Fig. 2, this method may include performing the steps described below.

[0131] Stage 201: The eRedCap terminal sends the first information to the network device.

[0132] In some embodiments, the first information indicates the number of parallel unicast PDSCH channels supported by the eRedCap terminal. For example, when the eRedCap terminal supports two parallel unicast PDSCH channels, it sends the first information to the network device, informing the network device that the number of parallel unicast PDSCH channels supported by the eRedCap terminal is two, so that the network device can schedule unicast PDSCH channels for the eRedCap terminal based on the terminal's ability to handle two parallel unicast PDSCH channels.

[0133] In some implementation examples, the eRedCap terminal may determine whether it has the capability to process parallel unicast PDSCH channels. If the eRedCap terminal has the capability to process parallel unicast PDSCH channels, it sends the first information to the network device; if the eRedCap terminal does not have the capability to process parallel unicast PDSCH channels, it does not send the first information to the network device.

[0134] In some embodiments of the present invention, the number of parallel unicast PDSCH channels supported by the eRedCap terminal may be determined under certain restrictions.

[0135] In particular, in some embodiments of the present invention, the eRedCap terminal can determine whether the number of RBs occupied by the parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to a predetermined first threshold. If the number of RBs occupied by the parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to the predetermined first threshold, the eRedCap terminal reports the number of unicast PDSCH channels to the network device; accordingly, if the number of RBs occupied by the parallel unicast PDSCH channels supported by the eRedCap terminal exceeds the predetermined first threshold, the eRedCap terminal does not report the number of unicast PDSCH channels to the network device.For example, for an eRedCap terminal supporting a 5 MHz baseband bandwidth, the number of parallel unicast PDSCH channels that can be processed is two. With an SCS of 15 kHz, the baseband bandwidth includes 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 cannot exceed 25. With an SCS of 30 kHz, the baseband bandwidth includes 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 cannot exceed 12.

[0136] In some embodiments of the present invention, the eRedCap terminal may also determine whether the delay in processing parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined second delay threshold, wherein the second delay threshold exceeds a predetermined first delay threshold, and the first delay threshold is a delay threshold for processing parallel unicast PDSCH channels by a terminal that is not an eRedCap terminal.If the processing delay of parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to the predefined second delay threshold, the eRedCap terminal reports the number of PDSCH channels to the network device; accordingly, if the processing delay of parallel unicast PDSCH channels by the eRedCap terminal exceeds the predefined second delay threshold, the eRedCap terminal does not report the number of PDSCH channels to the network device. A non-eRedCap terminal may be a terminal that does not support the reduction of the baseband bandwidth to 5 MHz. In particular, this may be a RedCap terminal that does not support the reduction of the baseband bandwidth to 5 MHz.In practice, a terminal that is not an eRedCap terminal may also be referred to as a non-enhanced terminal with simplified capabilities, which is not limiting in the embodiments of the present invention.

[0137] Accordingly, in some embodiments of the present invention, the number of parallel unicast PDSCH channels supported by the eRedCap terminal may also be determined under certain constraints associated with a first threshold value and a second delay threshold value.

[0138] In some embodiments of the present invention, the eRedCap terminal may use the first capability message field already provided in the capability signaling information to provide the first information to the network device; accordingly, the network device obtains the first information using the first capability message field in the capability signaling information. The eRedCap terminal may also define a new second capability message field and provide the first information to the network device through the second capability message field; accordingly, the network device obtains the first information using the second capability message field in the capability signaling information. The new second capability message field may be a capability message field newly added to the capability signaling information, i.e.The first capability message field is not a predefined capability message field in the capability signaling information.

[0139] Stage 202: The network device receives the first information and schedules unicast PDSCHs for the eRedCap terminal based on the first information.

[0140] In some embodiments of the present invention, the network device may determine the capability of the eRedCap terminal to process parallel unicast PDSCH channels based on the received first information; and thus, in the scheduling process, it may schedule the parallel unicast PDSCH channels supported by the eRedCap terminal based on the capability of the eRedCap terminal to process parallel unicast PDSCH channels. For example, if the eRedCap terminal has the capability to process two parallel unicast PDSCH channels, the network device may simultaneously schedule two unicast PDSCH channels for the eRedCap terminal.

[0141] Accordingly, in some embodiments of the present invention, if the network device does not receive the first information, it considers that the eRedCap terminal is unable to process parallel unicast PDSCH channels. In this case, the network device may schedule one unicast PDSCH channel for the eRedCap terminal.

[0142] In summary, the resource determination method according to the embodiments of the present invention allows the base station to determine the ability of the eRedCap terminal to process parallel unicast PDSCH channels by providing the eRedCap terminal with the number of parallel unicast PDSCH channels that it is capable of processing, which allows the base station to intelligently schedule unicast PDSCH channels for the eRedCap terminal, eliminating the need for the eRedCap terminal to repeatedly re-process the received data and introduce an additional delay, which could lead to the eRedCap terminal not performing the HARQ-ACK feedback in time when the HARQ resources arrive or only performing the NACK feedback, which would entail a waste of resources and an increase in the power consumption of the terminal.

[0143] One embodiment of the present invention, which is illustrated in Fig. 3, provides a resource scheduling method that is applicable to the eRedCap terminal. As shown in Fig. 3, this method may include performing the step described below.

[0144] Stage 301: Grant the network device the number of concurrent unicast PDSCHs supported by the eRedCap terminal based on the eRedCap terminal having the first capability; wherein the first capability includes the capability of the eRedCap terminal to handle concurrent unicast PDSCHs.

[0145] In some embodiments of the present invention, the eRedCap terminal sends to the network device the number of parallel unicast PDSCH channels supported by the eRedCap terminal; accordingly, the network device receives the number of parallel unicast PDSCH channels supported by the eRedCap terminal.

[0146] In some embodiments of the present invention, the eRedCap terminal may support two types of parallel PDSCH processing capabilities. The first parallel PDSCH processing capability is not limited by the number of RBs and supports processing X parallel PDSCH unicast channels within a certain delay range. The second parallel PDSCH processing capability is limited by the number of RBs and supports processing Y parallel PDSCH unicast channels within a certain delay range. The set of X values ​​may be denoted as set#1, and the set of Y values ​​may be denoted as set#2. Set#1 and set#2 may be the same or different. The eRedCap terminal, depending on its implementation options, may selectively report these two capabilities. In particular, if both capabilities can be provided, i.e.If the eRedCap terminal supports both capabilities, both capabilities are reported; or, if the eRedCap terminal supports only one capability, only the supported capability is reported; or, if the eRedCap terminal supports neither capability, neither capability is reported.

[0147] In some embodiments of the present invention, the maximum value of the number of parallel unicast PDSCH channels supported by the eRedCap terminal may be less than the maximum value of the number of parallel unicast PDSCH channels supported by a terminal that is not an eRedCap terminal. Specifically, the set of values ​​of the number of parallel unicast PDSCH channels supported by the eRedCap terminal is set#1, and the set of values ​​of the number of parallel unicast PDSCH channels supported by a terminal that is not an eRedCap terminal is set#3. Thus, the maximum value in set#1 is less than the maximum value in set#3. For example, if set#3 includes the values ​​{2,4,7}, then set#1 may be {2,4} or {2}.

[0148] In some embodiments of the present invention, the number of unicast PDSCH channels may be determined under the constraint that the number of RBs occupied by the supported parallel unicast PDSCH channels is within a certain resource limit. In particular, the number of unicast PDSCH channels may be determined under the condition that the number of RBs occupied by the supported parallel unicast PDSCH channels is less than or equal to the first threshold. For example, the eRedCap terminal supporting a baseband bandwidth of 5 MHz can process two parallel unicast PDSCH channels. At an SCS of 15 kHz, the number of RBs of the two parallel unicast PDSCH channels does not exceed 25. At an SCS of 30 kHz, the number of RBs of the two parallel unicast PDSCH channels does not exceed 12.

[0149] In this embodiment of the present invention, the number of RBs occupied by the supported parallel unicast PDSCH channels may also not be limited by the number of resources. For example, an eRedCap terminal supporting a baseband bandwidth of 5 MHz can process two parallel unicast PDSCH channels, and the number of RBs of the two parallel unicast PDSCH channels is not limited to 25 / 12.

[0150] In this embodiment of the present invention, the number of unicast PDSCH channels may also represent the number of parallel unicast PDSCH channels that can be processed by the eRedCap terminal under a certain delay limitation. For example, if the number of unicast PDSCH channels is N, and the processing delay required to process N-orth number of parallel unicast PDSCH channels is less than or equal to a predetermined threshold, then the N-th number of unicast PDSCH channels are reported.

[0151] In this embodiment of the present invention, the eRedCap terminal may use the first opportunity message field already provided in the capability signaling information to inform the network device of the number of unicast PDSCH channels; or it may define a new second opportunity message field to inform the network device of the number of unicast PDSCH channels through the second opportunity message field. When using the second opportunity message field to inform of the number of concurrent unicast PDSCH channels supported by the eRedCap terminal, the set of values ​​in the second opportunity message field may be the same as or different from the set of values ​​in the first opportunity message field.

[0152] To summarize, the solutions implemented in the embodiments of the present invention allow the base station to determine the ability of the eRedCap terminal to process parallel unicast PDSCH channels by providing the eRedCap terminal with the number of parallel unicast PDSCH channels that it is capable of processing, which allows the base station to intelligently schedule unicast PDSCH channels for the eRedCap terminal, eliminating the need for the eRedCap terminal to repeatedly re-process the received data and introduce an additional delay, which could lead to the eRedCap terminal not performing the HARQ-ACK feedback in time when HARQ resources arrive or only performing the NACK feedback, which would entail a waste of resources and an increase in the power consumption of the terminal.

[0153] In practice, when the eRedCap terminal does not have the capability of handling concurrent unicast PDSCH channels, it may also not inform the network device of the number of concurrent unicast PDSCH channels supported by the eRedCap terminal.

[0154] ​​Based on this, one embodiment of the present invention provides a resource scheduling method applicable to the eRedCap terminal. As shown in Fig. 4, this method includes performing the step described below.

[0155] Stage 401: The network device failed to provide the number of concurrent unicast PDSCHs supported by the eRedCap terminal due to the eRedCap terminal not having the first opportunity.

[0156] It should be noted that the lack of the first capability in an eRedCap terminal may mean that all eRedCap terminals do not have the first capability, i.e., eRedCap terminals do not support parallel unicast PDSCH channels.

[0157] In some embodiments of the present invention, the eRedCap terminal does not report to the network device the number of parallel unicast PDSCH channels supported by the eRedCap terminal; accordingly, the network device does not obtain the number of parallel unicast PDSCH channels supported by the eRedCap terminal.

[0158] In this embodiment of the present invention, the eRedCap terminal does not report its capabilities. Therefore, the base station side schedules unicast PDSCH channels for the eRedCap terminal based on the capability of processing one unicast PDSCH channel. That is, the base station side determines that the eRedCap terminal does not have the capability of processing concurrent unicast PDSCH channels, and concurrently schedules only one unicast PDSCH channel for the eRedCap terminal.

[0159] In summary, the resource determination method according to the embodiments of the present invention allows the base station to determine the ability of the eRedCap terminal to process parallel unicast PDSCH channels by providing the eRedCap terminal with the number of parallel unicast PDSCH channels that it is capable of processing, which allows the base station to intelligently schedule unicast PDSCH channels for the eRedCap terminal, eliminating the need for the eRedCap terminal to repeatedly re-process the received data and introduce an additional delay, which could lead to the eRedCap terminal not performing the HARQ-ACK feedback in time when the HARQ resources arrive or only performing the NACK feedback, which would entail a waste of resources and an increase in the power consumption of the terminal.

[0160] One embodiment of the present invention, which is illustrated in Fig. 5, further provides a resource scheduling method applicable to the eRedCap terminal. This resource scheduling method can be implemented separately, or in combination with any other embodiment of the claimed invention or a possible example of its implementation, or in combination with any technical solution of the prior art.

[0161] As shown in Fig. 5, the resource planning method may include performing the step described below.

[0162] Stage 501: Grant the network device the number of RBs occupied by the first parallel unicast PDSCHs supported by the eRedCap terminal based on the fact that the eRedCap terminal has the first opportunity, and the number of RBs occupied by the first parallel unicast PDSCHs is less than or equal to the first threshold.

[0163] In this embodiment of the present invention, the first threshold value may be the maximum number of RBs supported by the baseband of the eRedCap terminal for the data channel. For example, for an eRedCap terminal supporting a baseband bandwidth of 5 MHz, the number of parallel unicast PDSCHs that can be processed is 2. At an SCS of 15 kHz, the baseband bandwidth includes 25 RBs, i.e., the first threshold value is 25 RBs. Therefore, the total number of RBs in two unicast PDSCHs of the eRedCap terminal cannot exceed 25. At an SCS of 30 kHz, the baseband bandwidth includes 12 RBs, i.e., the first threshold value is 12 RBs. Therefore, the total number of RBs in two unicast PDSCHs of the eRedCap terminal cannot exceed 12.

[0164] One embodiment of the present invention, which is illustrated in Fig. 6, further provides a resource scheduling method applicable to the eRedCap terminal. This resource scheduling method can be implemented separately, or in combination with any other embodiment of the claimed invention or a possible example of its implementation, or in combination with any technical solution of the prior art.

[0165] As shown in Fig. 6, the resource planning method may include performing the step described below.

[0166] Stage 601: Grant the network device the number of the first parallel unicast PDSCHs supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCHs of the eRedCap terminal is less than or equal to a preset first delay threshold.

[0167] In some embodiments of the present invention, the eRedCap terminal may determine whether the processing delay of the parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to a predetermined second delay threshold. If the processing delay of the parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to the predetermined second delay threshold, the eRedCap terminal notifies the network device of the number of the first parallel unicast PDSCH channels that it can process; accordingly, if the processing delay of the parallel unicast PDSCH channels supported by the eRedCap terminal exceeds the predetermined second delay threshold, the eRedCap terminal does not notify the network device of the number of the first parallel unicast PDSCH channels that it can process.

[0168] In this embodiment of the present invention, the first delay threshold value represents the delay of processing parallel unicast PDSCH channels by the eRedCap terminal. The eRedCap terminal may use parallel unicast PDSCH channels for parallel or serial processing, provided that this processing can be completed within the time range of the first delay threshold value, which is not limiting in the embodiments of the present invention.

[0169] In this embodiment of the present invention, the first delay threshold may be a threshold value agreed upon by the protocol or a threshold value configured by the network device in accordance with scheduling requirements.

[0170] In this embodiment of the present invention, it is provided that by introducing the first delay threshold and providing the number of parallel unicast PDSCH channels that the eRedCap terminal is capable of processing, the base station can determine the ability of the eRedCap terminal to process parallel unicast PDSCH channels, which allows the base station to intelligently schedule unicast PDSCH channels for the eRedCap terminal, eliminating the need for the eRedCap terminal to repeatedly re-process the received data and introduce an additional delay, which could lead to the eRedCap terminal not performing the HARQ-ACK feedback in time when HARQ resources arrive or only performing the NACK feedback, which would entail a waste of resources and an increase in the power consumption of the terminal.

[0171] In this embodiment of the present invention, the eRedCap terminal may use the first capability message field already provided in the capability signaling information to provide the network device with the number of first parallel unicast PDSCH channels.

[0172] Based on this, one embodiment of the present invention, which is illustrated in Fig. 7, proposes a method for providing the number of first parallel unicast PDSCH channels using a first opportunity message field. This method includes performing the step described below.

[0173] Stage 701: Sending a first opportunity message field to the network device through the capability signaling information upon the fact that the eRedCap terminal has the first opportunity, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes the number of the first parallel unicast PDSCHs supported by the eRedCap terminal.

[0174] In this embodiment of the present invention, it is provided that, when using the first opportunity message field already provided in the capability signaling information and intended to provide the number of first parallel unicast PDSCH channels, a limitation on the maximum number of resources for the eRedCap terminal may be added to the definition of the first opportunity message field, that is, the definition of the first opportunity message field may be supplemented with a condition that the number of RBs occupied by the first parallel unicast PDSCH channels is less than or equal to a first threshold value.

[0175] In this embodiment of the present invention, the eRedCap terminal may also provide the number of first parallel unicast PDSCH channels based on a new second opportunity message field.

[0176] Based on this, one embodiment of the present invention, which is illustrated in Fig. 8, further proposes a method for providing a number of first parallel unicast PDSCH channels using a second opportunity message field. This method includes performing the steps described below.

[0177] Stage 801: Set a new capability message field to obtain a second capability message field based on whether the eRedCap terminal has the first capability, and the second capability message field includes the number of the first parallel unicast PDSCHs supported by the eRedCap terminal.

[0178] Stage 802: Send the second capability message field to the network device through capability signaling information.

[0179] It should be noted that the value set in the first opportunity message field may be the same as or different from the value set in the second opportunity message field. Specifically, the value set in the first opportunity message field may be a first value set, such as {2,4,7}. The value set in the second opportunity message field may be the second value set. The first value set is a preconfigured value set. The second value set may be the same as the first value set or may include other preconfigured values, i.e., values ​​that are not in the preconfigured value set. For example, if the preconfigured set is {2,4,7}, the value set in the second opportunity message field may include values ​​from {2,4,7}, or it may include values ​​such as 3, 5, etc.

[0180] One embodiment of the present invention, which is illustrated in Fig. 9, further provides a resource scheduling method applicable to the eRedCap terminal. This resource scheduling method can be implemented separately, or in combination with any other embodiment of the claimed invention or a possible example of its implementation, or in combination with any technical solution of the prior art.

[0181] As shown in Fig. 9, the resource scheduling method may include performing the step described below.

[0182] Stage 901: Grant the network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal based on the fact that the eRedCap terminal has the first capability, and the number of RBs occupied by the second parallel unicast PDSCHs supported by the eRedCap terminal is not limited by the first threshold.

[0183] In this embodiment of the present invention, the first threshold value may be the maximum number of RB blocks supported by the baseband of the eRedCap terminal for the data transmission channel.

[0184] In practice, the number of RBs occupied by the second parallel unicast PDSCHs supported by the eRedCap terminal may also be limited by the first threshold.

[0185] Based on this, one embodiment of the present invention, which is illustrated in Fig. 10, provides a resource scheduling method applicable to the eRedCap terminal. As shown in Fig. 10, this method includes performing the steps described below.

[0186] Stage 1001: Granting to the network device the number of first parallel unicast PDSCHs supported by the eRedCap terminal, wherein the number of resource blocks (RBs) occupied by the first parallel unicast PDSCHs is less than or equal to the first threshold.

[0187] Stage 1002: Grant the number of second parallel unicast PDSCHs supported by the eRedCap terminal to the network device, wherein the number of RBs occupied by the second parallel unicast PDSCHs supported by the eRedCap terminal is not limited to the first threshold.

[0188] In some embodiments of the present invention, the eRedCap terminal may support two types of parallel unicast PDSCH processing capabilities. The first parallel unicast PDSCH processing capability is not limited by the number of RBs. The second parallel unicast PDSCH processing capability is limited by the number of RBs. The eRedCap terminal, depending on its implementation, may selectively report these two capabilities. In particular, if both capabilities can be provided, i.e., the eRedCap terminal supports both capabilities, then both capabilities are reported, i.e., both step 1001 and step 1002 are performed; or, if the eRedCap terminal supports only one capability, then only the supported capability is reported, i.e., either step 1001 or step 1002 is performed; or, if the eRedCap terminal does not support either capability, neither of them is reported, i.e.,neither stage 1001 nor stage 1002 is performed.

[0189] In some embodiments of the present invention, a first capability for processing parallel unicast PDSCH channels supports processing X number of parallel unicast PDSCH channels within a certain delay range. A second capability for processing parallel unicast PDSCH channels supports processing Y number of parallel unicast PDSCH channels within a certain delay range. The set of values ​​X may be designated as set#1, and the set of values ​​Y may be designated as set#2, wherein the sets of values ​​set#1 and set#2 may be the same or different.

[0190] One embodiment of the present invention, which is illustrated in Fig. 11, further provides a resource scheduling method applicable to the eRedCap terminal. This resource scheduling method can be implemented separately, or in combination with any other embodiment of the claimed invention or a possible example of its implementation, or in combination with any technical solution of the prior art.

[0191] As shown in Fig. 11, this resource scheduling method may involve performing the step described below.

[0192] Stage 1101: Grant the network device the number of second parallel unicast PDSCHs supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCHs of the eRedCap terminal is less than or equal to a predetermined first delay threshold.

[0193] In some embodiments of the present invention, the eRedCap terminal may determine whether the processing delay of the parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to a predetermined first delay threshold. If the processing delay of the parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to the predetermined first delay threshold, the eRedCap terminal notifies the network device of the number of the second parallel unicast PDSCH channels that it can process; accordingly, if the processing delay of the parallel unicast PDSCH channels supported by the eRedCap terminal exceeds the predetermined first delay threshold, the eRedCap terminal does not notify the network device of the number of the second parallel unicast PDSCH channels that it can process.

[0194] In this embodiment of the present invention, it is provided that by introducing the first delay threshold and providing the number of parallel unicast PDSCH channels that the eRedCap terminal is capable of processing, the base station can determine the ability of the eRedCap terminal to process parallel unicast PDSCH channels, which allows the base station to intelligently schedule unicast PDSCH channels for the eRedCap terminal, eliminating the need for the eRedCap terminal to repeatedly re-process the received data and introduce an additional delay, which could lead to the eRedCap terminal not performing the HARQ-ACK feedback in time when HARQ resources arrive or only performing the NACK feedback, which would entail a waste of resources and an increase in the power consumption of the terminal.

[0195] In this embodiment of the present invention, the eRedCap terminal may use the first capability message field already provided in the capability signaling information to provide the number of second parallel unicast PDSCH channels.

[0196] Based on this, one embodiment of the present invention, which is illustrated in Fig. 12, proposes a method for providing a number of second parallel unicast PDSCH channels using a second opportunity message field. This method includes performing the step described below.

[0197] Stage 1201: Sending a first capability message field to the network device through the capability signaling information upon the fact that the eRedCap terminal has the first capability, wherein the first capability message field is a predetermined capability message field in the capability signaling information, and the first capability message field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal.

[0198] In this embodiment of the present invention, it is provided that, when using the first opportunity message field already provided in the capability signaling information and intended to provide the number of second parallel unicast PDSCH channels, a limitation on the maximum number of resources for the eRedCap terminal may be added to the definition of the first opportunity message field, that is, the definition of the first opportunity message field may be supplemented with a condition that the number of RBs occupied by the second parallel unicast PDSCH channels is less than or equal to a first threshold value.

[0199] In this embodiment of the present invention, the eRedCap terminal may also provide the number of second parallel unicast PDSCH channels based on a new second opportunity message field.

[0200] Based on this, one embodiment of the present invention, which is illustrated in Fig. 13, further proposes a method for providing a number of second parallel unicast PDSCH channels using a second opportunity message field. This method includes performing the steps described below.

[0201] Stage 1301: Set a new capability message field to obtain a second capability message field based on whether the eRedCap terminal has the first capability, and the second capability message field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal.

[0202] Stage 1302: Send the second capability message field to the network device through capability signaling information.

[0203] It should be noted that the value set in the first opportunity message field may be the same as or different from the value set in the second opportunity message field. Specifically, the value set in the first opportunity message field may be a first value set, such as {2,4,7}. The value set in the second opportunity message field may be the second value set. The first value set is a preconfigured value set. The second value set may be the same as the first value set or may include other preconfigured values, i.e., values ​​that are not in the preconfigured value set. For example, if the preconfigured set is {2,4,7}, the value set in the second opportunity message field may include values ​​from {2,4,7}, or it may include values ​​such as 3, 5, etc.

[0204] One embodiment of the present invention, which is illustrated in Fig. 14, further provides a resource scheduling method applicable to the eRedCap terminal. This resource scheduling method can be implemented separately, or in combination with any other embodiment of the claimed invention or a possible example of its implementation, or in combination with any technical solution of the prior art.

[0205] As shown in Fig. 14, this resource planning method involves performing the step described below.

[0206] Stage 1401: Granting to the network device the number of third parallel unicast PDSCH channels supported by the eRedCap terminal, based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined second delay threshold; wherein the second delay threshold is greater than a predetermined first delay threshold, and the first delay threshold is a processing delay threshold of the parallel unicast PDSCH channels by a terminal that is not an eRedCap terminal.

[0207] In some embodiments of the present invention, the eRedCap terminal may determine whether the processing delay of the parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to a predetermined first delay threshold. If the processing delay of the parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to the predetermined first delay threshold, the eRedCap terminal notifies the network device of the number of the third parallel unicast PDSCH channels that it can process; accordingly, if the processing delay of the parallel unicast PDSCH channels supported by the eRedCap terminal exceeds the predetermined first delay threshold, the eRedCap terminal does not notify the network device of the number of the third parallel unicast PDSCH channels that it can process.

[0208] In this embodiment of the present invention, it is provided that by introducing the second delay threshold and providing the number of parallel unicast PDSCH channels that the eRedCap terminal is capable of processing, the base station can determine the ability of the eRedCap terminal to process parallel unicast PDSCH channels, which allows the base station to intelligently schedule unicast PDSCH channels for the eRedCap terminal, eliminating the need for the eRedCap terminal to repeatedly re-process the received data and introduce an additional delay, which could lead to the eRedCap terminal not performing the HARQ-ACK feedback in time when HARQ resources arrive or only performing the NACK feedback, which would entail a waste of resources and an increase in the power consumption of the terminal.

[0209] In this embodiment of the present invention, the eRedCap terminal may have different parallel processing capabilities, i.e., the eRedCap terminal may support processing different numbers of parallel unicast PDSCH channels. Separate processing delays may be introduced for different parallel processing capabilities, i.e., the second delay threshold may include different delay thresholds, wherein different second delay thresholds correspond to different numbers of third parallel unicast PDSCH channels.

[0210] Based on this, one embodiment of the present invention, which is illustrated in Fig. 15, is proposed to provide a method for providing a number of third parallel unicast PDSCH channels based on different delay thresholds. The eRedCap terminal supports a plurality of numbers of third parallel unicast PDSCH channels, and the plurality of numbers of third parallel unicast PDSCH channels correspond to different second delay thresholds. This method includes performing the step described below.

[0211] Stage 1501: Provide the network device with target quantity values ​​that are all multiple quantities of the third parallel unicast PDSCHs supported by the eRedCap terminal;

[0212] or

[0213] providing the network device with a target quantity that is the maximum value of multiple values ​​of the quantity of third parallel unicast PDSCHs supported by the eRedCap terminal;

[0214] wherein multiple values ​​of the number of third parallel unicast PDSCH channels correspond to different second delay threshold values.

[0215] In this embodiment of the present invention, the processing delay corresponding to each number of unicast PDSCH channels supported by the eRedCap terminal is first compared with the corresponding second delay threshold. If the processing delay of the number of unicast PDSCH channels is less than or equal to the corresponding second delay threshold, then this number of PDSCH channels is adopted as the number of third parallel unicast PDSCH channels.

[0216] In this embodiment of the present invention, providing the network device with each number of third parallel unicast PDSCH channels as target number values ​​may mean that the eRedCap terminal notifies only one number of third parallel unicast PDSCH channels at a time, or the eRedCap terminal notifies all the numbers of third parallel unicast PDSCH channels at the same time.

[0217] For example, for three different supported values ​​of the number of concurrent PDSCH unicast channels, such as {2, 4, 7}, additional corresponding processing delay thresholds are introduced, namely {X1, X2, X3}, where the processing delay threshold for two PDSCH unicast channels is XI, for four PDSCH unicast channels it is X2, and for seven PDSCH unicast channels it is X3. If the processing delay of two concurrent channels by the eRedCap terminal can correspond to XI, the eRedCap terminal can provide the number of 2. If the processing delay of four concurrent channels by the eRedCap terminal can correspond to X2, the eRedCap terminal can provide the number of 4. If the processing delay of seven concurrent channels by the eRedCap terminal can correspond to X3, the eRedCap terminal can provide the number of 7.The eRedCap terminal can provide only one number of unicast PDSCH channels at a time, or can provide all three values ​​of the number of unicast PDSCH channels, namely {2,4,7}, at the same time.

[0218] In this embodiment of the present invention, it is envisaged that an additional overall processing delay may also be introduced for different parallel processing capabilities, i.e., different values ​​of the number of third parallel unicast channels correspond to the same delay threshold. In practice, this means that an overall additional processing delay may be introduced, and the sum of the additional processing delay and the first delay threshold may be taken as the second delay threshold.

[0219] In this embodiment of the present invention, the number of third parallel unicast PDSCH channels can be allocated from a plurality of the numbers of parallel unicast PDSCH channels supported by the eRedCap terminal based on the second delay threshold. Specifically, the maximum number of parallel unicast PDSCH channels that can be supported by the eRedCap terminal can be determined under the condition that the processing delay is less than or equal to the second delay threshold, and the set number is adopted as the number of third parallel unicast PDSCH channels. The number of parallel unicast PDSCH channels that can be processed can be allocated from a set of channel numbers of the eRedCap terminal.It should be noted that the set of channel number values ​​of the eRedCap terminal may be a set of values ​​agreed upon by the protocol or a set of values ​​configured by the terminal in accordance with the channel number values ​​agreed upon by the protocol.

[0220] For example, if the set of channel number values ​​agreed upon by the protocol is {2,4,7}, the eRedCap terminal supports three different values ​​of the number of parallel unicast PDSCH channels, namely {2,4,7}. In this case, an additional processing delay Y1 is introduced. From the set {2,4,7}, the maximum number of parallel unicast PDSCH channels that can be supported by the eRedCap terminal is allocated, provided that the processing delay is less than or equal to T_processing, 1 + Y1. This number is adopted as the number of the third parallel unicast PDSCH channels. For example, provided that the processing delay is less than T_processing, 1 + Y1, if the terminal can process up to four parallel channels, it represents the value 4 for the number.In another example, if the protocol specifies that the eRedCap terminal supports the processing of three parallel unicast PDSCH channels, then by introducing an additional processing delay Y1, the maximum number of parallel unicast PDSCH channels that can be supported by the eRedCap terminal can also be allocated from the set {2,3,4,7}.

[0221] In this embodiment of the present invention, the eRedCap terminal may use the first capability message field already provided in the capability signaling information to provide the number of first parallel unicast PDSCH channels.

[0222] Based on this, one embodiment of the present invention, which is illustrated in Fig. 16, proposes a method for providing a number of third parallel unicast PDSCH channels using a first opportunity message field. This method includes performing the step described below.

[0223] Stage 1601: Sending a first capability message field to the network device through the capability signaling information upon the fact that the eRedCap terminal has the first capability, wherein the first capability message field is a predetermined capability message field in the capability signaling information, and the first capability message field includes at least one number of third parallel unicast PDSCHs supported by the eRedCap terminal.

[0224] In this embodiment of the present invention, the eRedCap terminal may also provide at least one number of third parallel unicast PDSCH channels based on a new second opportunity message field.

[0225] Based on this, one embodiment of the present invention, which is illustrated in Fig. 17, further provides a method for providing at least one number of third parallel unicast PDSCH channels using a second opportunity message field. This method includes performing the steps described below.

[0226] Stage 1701: Setting a new capability message field to obtain a second capability message field based on the fact that the eRedCap terminal has the first capability, wherein the second capability message field includes at least one number of third parallel unicast PDSCHs supported by the eRedCap terminal; and

[0227] Stage 1702: Send the second capability message field to the network device through capability signaling information.

[0228] It should be noted that the value set in the first opportunity message field may be the same as or different from the value set in the second opportunity message field. Specifically, the value set in the first opportunity message field may be a first value set, such as {2,4,7}. The value set in the second opportunity message field may be the second value set. The first value set is a preconfigured value set. The second value set may be the same as the first value set or may include other preconfigured values, i.e., values ​​that are not in the preconfigured value set. For example, if the preconfigured set is {2,4,7}, the value set in the second opportunity message field may include values ​​from {2,4,7}, or it may include values ​​such as 3, 5, etc.

[0229] One embodiment of the present invention, which is illustrated in Fig. 18, further provides a resource scheduling method applicable to a network device. As shown in Fig. 18, this resource scheduling method may include performing the step described below.

[0230] Stage 1801: Obtain the number of parallel unicast PDSCH channels supported by the eRedCap terminal provided by the eRedCap terminal based on the fact that the eRedCap terminal has the first capability, where the first capability includes the capability of the eRedCap terminal to handle parallel unicast PDSCH channels.

[0231] In some embodiments of the present invention, the eRedCap terminal may support two types of parallel unicast PDSCH channel processing capabilities. The first parallel unicast PDSCH channel processing capability is not limited to the number of RBs supporting the processing of X parallel unicast PDSCH channels within a certain delay range. The second parallel unicast PDSCH channel processing capability is limited to the number of RBs supporting the processing of Y parallel unicast PDSCH channels within a certain delay range. The network device may accept both capabilities simultaneously provided by the eRedCap terminal, or accept one capability supported by the eRedCap terminal, or accept neither capability provided by the eRedCap terminal.

[0232] In this embodiment of the present invention, the eRedCap terminal can use the first opportunity message field already provided in the capability signaling information to provide the network device with the number of unicast PDSCH channels; accordingly, the network device obtains the message field using the capability signaling information. The eRedCap terminal can also define a new second opportunity message field and provide the network device with the number of unicast PDSCH channels through the second opportunity message field; accordingly, the network device obtains the second opportunity message field through the capability signaling information. The set of values ​​in the second opportunity message field may be the same as or different from the set of values ​​in the first opportunity message field.

[0233] Stage 1802: Schedule unicast PDSCH resources for the eRedCap terminal based on the number of concurrent unicast PDSCH channels supported by the eRedCap terminal.

[0234] In practice, the eRedCap terminal may not provide the number of parallel unicast PDSCH channels supported by the eRedCap terminal.

[0235] Based on this, one embodiment of the present invention, which is illustrated in Fig. 19, further provides a resource scheduling method applicable to a network device. As shown in Fig. 19, this method includes performing the step described below.

[0236] Stage 1901: Schedule unicast PDSCH resources for the eRedCap terminal based on the eRedCap terminal's ability to handle one unicast PDSCH due to the eRedCap terminal's lack of the first capability.

[0237] It should be noted that the lack of the first capability in an eRedCap terminal may mean that all eRedCap terminals do not have the first capability, i.e., eRedCap terminals do not support parallel unicast PDSCH channels.

[0238] In summary, the resource determination method according to the embodiments of the present invention allows the base station to determine whether the eRedCap terminal can process parallel unicast PDSCH channels, which allows the base station to intelligently schedule unicast PDSCH channels for the eRedCap terminal, eliminating the need for the eRedCap terminal to repeatedly re-process the received data and introduce an additional delay, which could lead to the eRedCap terminal not performing the HARQ-ACK feedback in time when the HARQ resources arrive, or only performing the NACK feedback, which would entail a waste of resources and an increase in the power consumption of the terminal.

[0239] One embodiment of the present invention, which is illustrated in Fig. 20, further provides a resource scheduling method applicable to a network device. This method includes performing the steps described below.

[0240] Stage 2001: Obtaining the number of first parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RBs occupied by the first parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to the first threshold.

[0241] Stage 2002: Schedule unicast PDSCH resources for the eRedCap terminal based on the number of first parallel unicast PDSCH channels.

[0242] As one possible example of implementing this embodiment of the present invention, obtaining the number of first parallel unicast PDSCH channels supported by the eRedCap terminal may include:

[0243] receiving a first opportunity message field in the capability signaling information, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes the number of first parallel unicast PDSCH channels supported by the eRedCap terminal;

[0244] or

[0245] receiving a second opportunity message field in the capability signaling information, wherein the second opportunity message field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, and the second opportunity message field is a new capability message field set by the eRedCap terminal;

[0246] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0247] As one possible example of implementing this embodiment of the present invention, the number of first parallel unicast PDSCH channels is provided to the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels of the eRedCap terminal is less than or equal to a predetermined first delay threshold.

[0248] One embodiment of the present invention, which is illustrated in Fig. 21, further provides a resource scheduling method applicable to a network device. This method includes performing the steps described below.

[0249] Stage 2101: Obtaining the number of second parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RBs occupied by the second parallel unicast PDSCH channels supported by the eRedCap terminal is not limited by the first threshold;

[0250] Stage 2102: Schedule unicast PDSCH resources for the eRedCap terminal based on the number of second parallel unicast PDSCH channels.

[0251] One embodiment of the present invention, which is illustrated in Fig. 22, further provides a resource scheduling method applicable to a network device. This method includes performing the steps described below.

[0252] Stage 2201: Obtaining the number of first parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RBs occupied by the first parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to the first threshold value;

[0253] Stage 2202: Obtaining the number of second parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RBs occupied by the second parallel unicast PDSCH channels supported by the eRedCap terminal is not limited by the first threshold;

[0254] Stage 2203: Schedule PDSCH unicast channel resources for the eRedCap terminal based on the number of first parallel PDSCH unicast channels or the number of second parallel PDSCH unicast channels.

[0255] In some embodiments of the present invention, the eRedCap terminal may support two types of parallel unicast PDSCH processing capabilities. The first parallel unicast PDSCH processing capability is not limited by the number of RBs. The second parallel unicast PDSCH processing capability is limited by the number of RBs. The eRedCap terminal, depending on its implementation, may selectively report these two capabilities. In particular, if both capabilities can be provided, i.e., the eRedCap terminal supports both capabilities, then both capabilities are reported; accordingly, the network device obtains both capabilities, i.e., both step 2201 and step 2202 are performed. Alternatively, if the eRedCap terminal supports only one capability, then only the supported capability is reported; accordingly, the network device obtains one capability, i.e.,Either step 2201 or step 2202 is performed. Another alternative is that if the eRedCap terminal does not support either capability, then neither capability is reported; therefore, the network device does not receive either capability.

[0256] In some embodiments of the present invention, the first capability for processing parallel unicast PDSCH channels supports processing X number of parallel unicast PDSCH channels within a certain delay range. The second capability for processing parallel unicast PDSCH channels supports processing Y number of parallel unicast PDSCH channels within a certain delay range. The set of values ​​X may be designated as set#1, and the set of values ​​Y may be designated as set#2, where the sets of values ​​set#1 and set#2 may be the same or different.

[0257] As one possible example of implementing this embodiment of the present invention, obtaining the number of second parallel unicast PDSCH channels supported by the eRedCap terminal may include:

[0258] receiving a first capability message field in the capability signaling information, wherein the first capability message field is a predetermined capability message field in the capability signaling information, and the first capability message field includes a number of second parallel unicast PDSCH channels supported by the eRedCap terminal;

[0259] or

[0260] receiving a second opportunity message field in the capability signaling information, wherein the second opportunity message field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal, and the second opportunity message field is a new capability message field set by the eRedCap terminal.

[0261] As one possible example of implementing this embodiment of the present invention, the number of second parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels of the eRedCap terminal is less than or equal to a predetermined first delay threshold value.

[0262] One embodiment of the present invention, which is illustrated in Fig. 23, further provides a resource scheduling method applicable to a network device. This method includes performing the steps described below.

[0263] Stage 2301: Obtaining the number of third parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of third parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined second delay threshold; wherein the second delay threshold is greater than a predetermined first delay threshold, and the first delay threshold is a delay threshold for processing the parallel unicast PDSCH channels by a terminal that is not an eRedCap terminal.

[0264] Stage 2302: Scheduling unicast PDSCH resources for the eRedCap terminal based on at least one number of third parallel unicast PDSCH channels.

[0265] As one possible example of implementing this embodiment of the present invention, obtaining the number of third parallel unicast PDSCH channels supported by the eRedCap terminal includes:

[0266] receiving target quantity values ​​from the eRedCap terminal, wherein the target quantity values ​​are all multiple quantity values ​​of the third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0267] or

[0268] receiving a target number from the eRedCap terminal, wherein the target number is a maximum value of a plurality of values ​​of the number of third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0269] wherein multiple values ​​of the number of third parallel unicast PDSCH channels correspond to different second delay threshold values.

[0270] As one possible example of implementing this embodiment of the present invention, obtaining the number of third parallel unicast PDSCH channels supported by the eRedCap terminal includes:

[0271] receiving a first opportunity message field in the capability signaling information, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes a number of third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0272] or

[0273] receiving a second opportunity message field in the capability signaling information, wherein the second opportunity message field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal, and the second opportunity message field is a new capability message field set by the eRedCap terminal;

[0274] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0275] The present invention further provides a resource scheduling device corresponding to the resource scheduling methods according to the embodiments of the claimed invention illustrated in Figs. 3-17. Since the resource scheduling device according to the embodiments of the present invention corresponds to the resource scheduling methods according to the embodiments of the present invention illustrated in Figs. 3-17, the implementation examples of the resource scheduling methods are also applicable to the resource scheduling device according to the embodiments of the present invention, and therefore, the description thereof is not repeated hereinafter.

[0276] Fig. 24 shows a schematic diagram of the structure of a resource scheduling device according to one embodiment of the present invention, and the device is located in the eRedCap terminal. As shown in Fig. 24, the proposed device includes:

[0277] a response module 2401 configured to provide the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the eRedCap terminal has the first opportunity;

[0278] or

[0279] response module 2401, configured to not provide the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal due to the fact that the eRedCap terminal does not have the first option;

[0280] wherein the first capability includes the capability of the eRedCap terminal to handle parallel unicast PDSCH channels.

[0281] As one possible example of implementing this embodiment of the present invention, the response module 2401 is configured, in particular, with the ability to:

[0282] providing the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of resource blocks (RBs) occupied by the first parallel unicast PDSCH channels is less than or equal to the first threshold value.

[0283] As one possible example of implementing this embodiment of the present invention, the response module 2401 is configured, in particular, with the ability to:

[0284] sending a first opportunity message field in the capability signaling information to the network device, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes the number of first parallel unicast PDSCH channels supported by the eRedCap terminal;

[0285] or

[0286] setting a new capability message field to obtain a second capability message field, wherein the second capability message field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal; and sending the second capability message field in capability signaling information to the network device;

[0287] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0288] As one possible example of implementing this embodiment of the present invention, the response module 2401 is configured, in particular, with the ability to:

[0289] Provides the network device with the number of the first parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a preset first delay threshold.

[0290] As one possible example of implementing this embodiment of the present invention, the response module 2401 is configured, in particular, with the ability to:

[0291] providing the network device with the number of second parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RB blocks occupied by the second parallel unicast PDSCH channels is not limited by the first threshold value.

[0292] As one possible example of implementing this embodiment of the present invention, the response module 2401 is configured, in particular, with the ability to:

[0293] sending a first capability message field in the capability signaling information to the network device, wherein the first capability message field is a predetermined capability message field in the capability signaling information, and the first capability message field includes a number of second parallel unicast PDSCH channels supported by the eRedCap terminal;

[0294] or

[0295] setting a new capability message field to obtain a second capability message field, wherein the second capability message field includes the number of second parallel unicast PDSCHs supported by the eRedCap terminal; and sending the second capability message field in capability signaling information to the network device;

[0296] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0297] As one possible example of implementing this embodiment of the present invention, the response module 2401 is configured, in particular, with the ability to:

[0298] providing the network device with the number of second parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a preset first delay threshold.

[0299] As one possible example of implementing this embodiment of the present invention, the response module 2401 is configured, in particular, with the ability to:

[0300] providing the network device with the number of third parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by 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 a processing delay threshold of the parallel unicast PDSCH channels by a terminal that is not an eRedCap terminal.

[0301] As one possible example of implementing this embodiment of the present invention, the eRedCap terminal supports multiple values ​​of the number of third parallel unicast PDSCH channels, and the response module 2401 is configured, in particular, to:

[0302] providing the network device with target quantity values, wherein the target quantity values ​​are all multiple quantity values ​​of the third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0303] or

[0304] providing the network device with a target quantity that is the maximum value of a plurality of the quantities of the third parallel unicast PDSCHs supported by the eRedCap terminal;

[0305] wherein multiple values ​​of the number of third parallel unicast PDSCH channels correspond to different second delay threshold values.

[0306] As one possible example of implementing this embodiment of the present invention, the response module 2401 is configured, in particular, with the ability to:

[0307] sending a first opportunity message field in the capability signaling information to the network device, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes the number of third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0308] or

[0309] setting a new capability message field to obtain a second capability message field, wherein the second capability message field includes the number of third parallel unicast PDSCHs supported by the eRedCap terminal; and sending the second capability message field in capability signaling information to the network device;

[0310] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0311] Fig. 25 shows a schematic diagram of the structure of a resource scheduling device according to one embodiment of the present invention, wherein the device is located in a network device. As shown in Fig. 25, the proposed device includes:

[0312] a receiving module 2501, configured to obtain the number of parallel unicast PDSCH channels supported by the eRedCap terminal provided by the eRedCap terminal based on the fact that the eRedCap terminal has the first opportunity; and a scheduling module 2502, configured to schedule unicast PDSCH channel resources for the eRedCap terminal based on the number of parallel unicast PDSCH channels supported by the eRedCap terminal;

[0313] or

[0314] a scheduling module 2502 configured to schedule unicast PDSCH resources for an eRedCap terminal based on the eRedCap terminal's ability to process one unicast PDSCH;

[0315] wherein the first capability includes the capability of the eRedCap terminal to handle parallel unicast PDSCH channels.

[0316] As one possible example of implementing this embodiment of the present invention, the receiving module 2501 is configured, in particular, with the possibility of:

[0317] obtaining the number of the first parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RB blocks occupied by the first parallel unicast PDSCH channels is less than or equal to the first threshold value.

[0318] As one possible example of implementing this embodiment of the present invention, the receiving module 2501 is configured, in particular, with the possibility of:

[0319] receiving a first opportunity message field in the capability signaling information, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes the number of first parallel unicast PDSCH channels supported by the eRedCap terminal;

[0320] or

[0321] receiving a second opportunity message field in the capability signaling information, wherein the second opportunity message field includes the number of first parallel unicast PDSCHs supported by the eRedCap terminal, and the second opportunity message field is a new capability message field set by the eRedCap terminal;

[0322] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0323] As one possible example of implementing this embodiment of the present invention, the number of first parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined first delay threshold.

[0324] As one possible example of implementing this embodiment of the present invention, the receiving module 2501 is configured, in particular, with the ability to:

[0325] obtain the number of second parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RBs occupied by the second parallel unicast PDSCH channels supported by the eRedCap terminal is not limited by the first threshold value.

[0326] As one possible example of implementing this embodiment of the present invention, the receiving module 2501 is configured, in particular, with the possibility of:

[0327] receiving a first capability message field in the capability signaling information, wherein the first capability message field is a predetermined capability message field in the capability signaling information, and the first capability message field includes a number of second parallel unicast PDSCH channels supported by the RedCap terminal;

[0328] or

[0329] receiving a second opportunity message field in the capability signaling information, wherein the second opportunity message field includes the number of second parallel unicast PDSCHs supported by the RedCap terminal, and the second opportunity message field is a new capability message field set by the eRedCap terminal.

[0330] As one possible example of implementing this embodiment of the present invention, the number of second parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined first delay threshold.

[0331] As one possible example of implementing this embodiment of the present invention, the receiving module 2501 is configured, in particular, with the possibility of:

[0332] obtaining a number of third parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of third parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined second delay threshold, wherein the second delay threshold value exceeds a predetermined first delay threshold value, and the first delay threshold value is a delay threshold value of processing the parallel unicast PDSCH channels by a terminal that is not an eRedCap terminal.

[0333] As one possible example of implementing this embodiment of the present invention, the receiving module 2501 is configured, in particular, with the possibility of:

[0334] receiving target quantity values ​​from the eRedCap terminal, wherein these target quantities are all multiple quantities of the third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0335] or

[0336] receiving a target number from the eRedCap terminal, wherein the target number is a maximum value of a plurality of values ​​of the number of third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0337] wherein multiple values ​​of the number of third parallel unicast PDSCH channels correspond to different second delay threshold values.

[0338] As one possible example of implementing this embodiment of the present invention, the receiving module 2501 is configured, in particular, with the possibility of:

[0339] receiving a first opportunity message field in the capability signaling information, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field includes a number of third parallel unicast PDSCH channels supported by the eRedCap terminal;

[0340] or

[0341] receiving a second opportunity message field of the capability signaling information, wherein the second opportunity message field includes the number of third parallel unicast PDSCH channels supported by the eRedCap terminal, and the second opportunity message field is a new capability message field set by the eRedCap terminal;

[0342] In this case, the set of values ​​in the first opportunity message field may be the same as or different from the set of values ​​in the second opportunity message field.

[0343] To implement the above-described embodiments of the present invention, the claimed invention further proposes a resource scheduling device, wherein this device includes 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, initiating the implementation by the proposed device of the method described in connection with any of Figs. 2-23.

[0344] In order to implement the above-described embodiments of the present invention, the claimed invention further provides another resource scheduling device including a processor and an interface circuit;

[0345] wherein the interface circuit is configured to receive code commands and transmit code commands to the processor, and

[0346] the processor is configured to execute code instructions for the purpose of implementing the method described in connection with any of Figs. 2-23.

[0347] To implement the above-described embodiments of the present invention, the claimed invention further proposes a machine-readable data carrier on which commands are stored, the execution of which initiates the implementation of the method described in connection with any of Figs. 2-23.

[0348] Fig. 26 shows a structural diagram of a terminal according to one embodiment of the present invention. For example, terminal 2600 may be a mobile phone, a computer, a digital broadcasting terminal, a message transceiver, a game console, a tablet, a medical device, a training device, a personal digital assistant, or another similar device.

[0349] As shown in Fig. 26, the terminal 2600 may include at least one of the following components: a data processing component 2602, a memory 2604, a power supply component 2606, a multimedia component 2608, an audio component 2610, an input / output (I / O) interface 2612, a sensor component 2614, and a communication component 2616.

[0350] Data processing component 2602 typically controls all actions of terminal 2600, such as operations related to data display, telephone calls, data exchange, camera operation, and recording. Data processing component 2602 may include at least one processor 2620 that executes instructions for performing all or some stages of the methods described above. Moreover, data processing component 2602 may include at least one module that facilitates interaction between data processing component 2602 and other components. For example, data processing component 2602 may include a multimedia module that facilitates interaction between multimedia component 2608 and data processing component 2602.

[0351] The memory 2604 is configured to store various types of data that support the operation of the terminal 2600. Examples of such data include commands for any applications or methods implemented on the terminal 2600, contact information, phone book data, messages, images, videos, and other similar data. The memory 2604 can be implemented using volatile or non-volatile memory devices of any type 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 or optical disk.

[0352] Power component 2606 supplies power to various components of terminal 2600. Power component 2606 may include a power management system, at least one power source, and any other elements associated with generating, managing, and distributing power for terminal 2600.

[0353] The multimedia component 2608 includes a screen, which is an output interface that communicates between the terminal 2600 and the user. In some embodiments of the present invention, 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 touch display for receiving input signals transmitted by the user. The touch panel includes one or more touch sensors for reading touches and finger movements on the touch panel in various directions. The touch sensors can not only read the action boundary of a touch or finger movement on the touch panel, but also read the wake-up time period and pressure associated with a touch or finger movement on the touch panel.In some embodiments of the present invention, the multimedia component 2608 includes a front-facing camera and / or a rear-facing camera. When the terminal 2600 is in an operating mode, such as in photo or video mode, the front-facing camera and / or rear-facing camera can receive external multimedia data. Each of the front-facing and rear-facing cameras may have a fixed optical lens system or have adjustable focal length and optical zoom capabilities.

[0354] The audio component 2610 is configured to emit and / or receive audio signals. For example, the audio component 2610 includes a microphone (MIC) configured to receive an external audio signal when the terminal 2600 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can then be stored in the memory 2604 or transmitted via the communication component 2616. In some embodiments of the present invention, the audio component 2610 further includes a speaker for emitting audio signals.

[0355] The input / output (I / O) interface 2612 provides mutual communication between the data processing component 2602 and peripheral interface modules such as a keyboard, a mouse wheel, buttons, and the like. These buttons may include, but are not limited to, a return button, a volume control button, a start button, and a lock button.

[0356] The sensor component 2614 includes one or more sensors for providing an assessment of the state of various aspects of the terminal 2600. For example, the sensor component 2614 can detect the open / closed state of the terminal 2600, the relative location of the components (for example, the display and the numeric keypad of the terminal 2600), a change in the position of the terminal 2600 or any of its components, the presence or absence of contact of the user with the terminal 2600, the orientation or acceleration / deceleration of the terminal 2600 and a change in the temperature of the terminal 2600. The sensor component 2614 can include a proximity sensor configured to detect nearby objects without any physical contact with them.The sensor component 2614 may also include a light-sensitive sensor, such as a CMOS (complementary metal-oxide-semiconductor) or CCD (charge-coupled device) image sensor, which is used in image processing applications. In some embodiments of the present invention, the sensor component 2614 may also include an accelerometer, a gyroscope, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0357] The communication component 2616 is configured to facilitate communication, both wirelessly and by wire, between the terminal 2600 and other devices. The terminal 2600 can access a wireless network using a communication standard such as Wi-Fi (wireless Internet access technology according to the IEEE 802.1 lx standard), 2G (second generation communication standard), 3G (third generation communication standard), or a combination thereof. In one of the exemplary embodiments of the present invention, the communication component 2616 receives a broadcast signal or broadcast information from an external broadcast control system via a broadcast channel. In one of the exemplary embodiments of the present invention, the communication component 2616 further includes an NFC (near field communication) module that facilitates communication over short distances.For example, an NFC module can be implemented based on RFID (radio frequency identification) technology, IrDA (Infrared Data Association) technology, UWB (ultra wideband) technology, BT (Bluetooth wireless communication technology) technology, and other technologies.

[0358] In exemplary embodiments of the present invention, the terminal 2600 may be implemented using one or more components such as an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), an FPGA, a controller, a microcontroller, a microprocessor, or another electronic component to implement the method illustrated in Fig. 2-23.

[0359] Fig. 27 shows a block diagram of a network device according to one embodiment of the present invention. As shown in Fig. 27, the network device 2700 includes a data processing component 2722, which further comprises at least one processor and memory resources represented by a memory 2732 for storing instructions executed by the data processing component 2722, for example, application programs. The application programs stored in the memory 2732 may include one or more modules, each of which corresponds to a certain set of instructions. In addition, the data processing component 2722 is configured to execute instructions for implementing any method applicable to the network device and described above, for example, the method described within the framework of the disclosure of the embodiments of the present invention illustrated in Figs. 3-17.

[0360] The network device 2700 may also include a power component 2726 configured to control the power of the network device 2700; a wired or wireless network interface 2750 configured to connect the network device 2700 to the network; and an input / output (I / O) interface 2758. The network device 2700 may operate on an operating system stored in the memory 2732, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0361] Illustrative embodiments of the present invention also provide a non-volatile computer-readable storage medium, such as memory 2604, containing instructions that can be executed by processor 2620 of terminal 2600 for implementing the method illustrated in Fig. 2-23. For example, the non-volatile computer-readable storage medium may be read-only memory (ROM), random access memory (RAM), compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, or other similar device.

[0362] Those skilled in the art will understand that the various logical blocks and steps illustrated in the embodiments of the present invention may be implemented using electronic hardware, computer software, or a combination of both. Whether these functions are implemented in hardware or software depends on the specific application and the overall design requirements of the entire system. Those skilled in the art may employ various methods to implement these functions in each specific application, but decisions regarding such implementation should not be construed as extending beyond the scope of the present invention.

[0363] The embodiments of the present invention disclosed above may be implemented in whole or in part using software, hardware, firmware, or a combination thereof. When implemented using software, they may be implemented in whole or in part as a computer program product. The computer program product includes one or more computer programs. When loaded and executed on a computer, the processes or functions according to the embodiments of the present invention are generated in whole or in part. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. The computer programs may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another.For example, computer programs may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired communication line (e.g., coaxial cable, fiber optics, digital subscriber line (DSL)) or wireless communication line (e.g., using infrared, wireless, microwave, and other devices). A computer-readable storage medium may be any accessible medium that can be accessed by a computer or a data storage device, such as a server, data center, or the like, that incorporates one or more accessible media. Suitable storage media may include magnetic media (e.g., floppy disks, hard drives, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)), etc.

[0364] Those skilled in the art should understand that the numerals such as "first", "second", etc. provided in this document are used solely for the convenience of description and do not limit the scope of embodiments of the claimed invention, nor do they indicate the order of occurrence.

[0365] The term "at least one" in the context of this document may also mean "one or more," and the term "more than one" refers to two, three, four or more elements, which is not limiting in this document. In the embodiments of the claimed invention, the terms "first," "second," "third," "A," "B," "C," "D," and other similar terms describing a technical feature are used to distinguish between technical features of the same type. However, the technical features described using the terms "first," "second," "third," "A," "B," "C," and "D" do not indicate any order or sequence of dimensions.

[0366] The correspondences shown in the tables in this document can be configured or preset. The information values ​​in each table are examples only and can be configured for other values, but are not intended to be limiting in this document. When configuring the correspondence between configuration information and parameters, it is not necessary to configure all the correspondences shown in the tables. For example, in the tables presented in this document, the correspondences shown in some terms may not be configured. In addition, appropriate adjustments, such as splitting, merging, etc., can be made based on these tables.The parameter names in the headers of these tables may also be represented as other names understood by the resource scheduler, and the values ​​or representations of the parameters may also be represented as other values ​​or representations understood by the resource scheduler. Other data structures may also be used in the implementation of these tables, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, pyramid structures, hash tables, or hash maps.

[0367] The term "preset" as used in this document may be interpreted as "set," "preset," "stored," "pre-stored," "pre-agreed," "pre-configured," "fixed," or "pre-recorded."

[0368] Those skilled in the art will understand that the various logical blocks and steps in the exemplary implementations described within the disclosure of embodiments of the claimed invention herein may be implemented using electronic hardware or a combination of electronic hardware and computer software. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. To implement these functions in each specific application, those skilled in the art may use various methods, but such implementation should not be construed as going beyond the scope of legal protection of the present invention.

[0369] For convenience and brevity of presentation, specific work processes in the above-described systems, devices and units can be correlated with the corresponding processes in the embodiments of the method disclosed above, and their description is not repeated further in the text.

[0370] The above are only specific embodiments of the present invention, and the scope of legal protection for the claimed invention is not limited by them. Within the technical scope disclosed herein, any person skilled in the art can easily develop various modifications or substitutions that are within the scope of legal protection for the claimed invention. Therefore, the scope of legal protection for the present invention should be determined by the scope of legal protection for its claims.

Claims

1. A resource planning method implemented by the eRedCap terminal (an advanced terminal with simplified capabilities) and providing for: providing the network device with the number of parallel unicast PDSCH (Physical Downlink Shared Channels) supported by the eRedCap terminal, upon the eRedCap terminal having the first capability; or failure to provide the network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal due to the lack of the first capability of the eRedCap terminal; where the first capability is the ability of the eRedCap terminal to process parallel unicast PDSCH channels; whereby the provision of a network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal provides for: providing the network device with the number of first parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of resource blocks (RBs) occupied by the first parallel unicast PDSCH channels is less than or equal to a first threshold value; wherein providing the network device with the number of first parallel unicast PDSCH channels supported by the eRedCap terminal comprises: sending a first opportunity message field in the capability signaling information to the network device, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field contains a number of first parallel unicast PDSCH channels supported by the eRedCap terminal; or setting a new capability message field to receive a second capability message field, wherein the second capability message field contains a number of first parallel unicast PDSCH channels supported by the eRedCap terminal; and sending the second capability message field as part of capability signaling information to the network device; wherein the set of values ​​in the first opportunity message field is the same as or different from the set of values ​​in the second opportunity message field.

2. The method according to claim 1, wherein providing to the network device the number of first parallel unicast PDSCH channels supported by the eRedCap terminal comprises: providing the network device with the number of the first parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined first delay threshold; or Providing a network device with the number of parallel unicast PDSCH channels supported by the eRedCap terminal provides for: providing the network device with a number of second parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RB blocks occupied by the second parallel unicast PDSCH channels supported by the eRedCap terminal is not limited by the first threshold value.

3. The method according to claim 2, wherein providing to the network device the number of second parallel unicast PDSCH channels supported by the eRedCap terminal comprises: sending to the network device a first capability message field in the capability signaling information, wherein the first capability message field is a predetermined capability message field in the capability signaling information, and the first capability message field contains a number of second parallel unicast PDSCH channels supported by the eRedCap terminal; or specifying a new capability message field to receive a second capability message field, wherein the second capability message field contains the number of second parallel unicast PDSCH channels supported by the eRedCap terminal; And sending a second capability message field as part of the capability signaling information to a network device.

4. The method according to claim 2, wherein providing to the network device the number of second parallel unicast PDSCH channels supported by the eRedCap terminal comprises: providing the network device with a number of second parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined first delay threshold.

5. The method according to claim 1, wherein providing to the network device the number of parallel unicast PDSCH channels supported by the eRedCap terminal comprises: providing the network device with the number of third parallel unicast PDSCH channels supported by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined second delay threshold, wherein the second delay threshold value is greater than a predetermined first delay threshold value, and the first delay threshold value is a delay threshold value for processing the parallel unicast PDSCH channels by a terminal that is not an eRedCap terminal; wherein the eRedCap terminal supports a plurality of values ​​of the number of third parallel unicast PDSCH channels, and providing the network device with the number of third parallel unicast PDSCH channels supported by the eRedCap terminal includes: providing the network device with target values ​​of the number that are all of the plural values ​​of the number of third parallel unicast PDSCH channels supported by the eRedCap terminal; or providing to the network device a target number that is the maximum value of a plurality of numbers of third parallel unicast PDSCH channels supported by the eRedCap terminal; wherein multiple values ​​of the number of third parallel unicast PDSCH channels correspond to different second delay threshold values.

6. The method according to claim 5, wherein providing to the network device the number of third parallel unicast PDSCH channels supported by the eRedCap terminal comprises: sending a first opportunity message field in the capability signaling information to the network device, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field contains a number of third parallel unicast PDSCH channels supported by the eRedCap terminal; or defining a new capability message field to receive a second capability message field, wherein the second capability message field contains a number of third parallel unicast PDSCH channels supported by the eRedCap terminal; and sending the second capability message field as part of capability signaling information to the network device.

7. A method of resource planning implemented by a network device and providing for: obtaining the number of parallel unicast PDSCHs (Physical Downlink Shared Channels) supported by the eRedCap terminal (an enhanced lightweight terminal) transmitted by the eRedCap terminal based on the first capability of the eRedCap terminal; and scheduling unicast PDSCH resources for the eRedCap terminal based on the number of parallel unicast PDSCHs supported by the eRedCap terminal; or scheduling of unicast PDSCH channel resources for the eRedCap terminal based on the ability of the eRedCap terminal to process one unicast PDSCH channel; the first possibility is the ability of the eRedCap terminal to process parallel unicast channels; whereby obtaining the number of parallel unicast PDSCH channels supported by the eRedCap terminal, transmitted by the eRedCap terminal upon the availability of the first opportunity by the eRedCap terminal, provides for: obtaining a number of first parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of resource blocks (RBs) occupied by the first parallel unicast PDSCH channels supported by the eRedCap terminal is less than or equal to a first threshold value; whereby obtaining the number of first parallel unicast PDSCH channels supported by the eRedCap terminal provides for: receiving a first opportunity message field in the capability signaling information, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field contains a number of first parallel unicast PDSCH channels supported by the eRedCap terminal; or receiving a second opportunity message field as part of the capability signaling information, wherein the second opportunity message field comprises a number of first parallel unicast PDSCH channels supported by the eRedCap terminal, and the second opportunity message field is a new capability message field specified by the eRedCap terminal; wherein the set of values ​​in the first opportunity message field is the same as or different from the set of values ​​in the second opportunity message field.

8. The method according to claim 7, wherein the number of first parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined first delay threshold; or Obtaining the number of parallel unicast PDSCH channels supported by the eRedCap terminal, provided by the eRedCap terminal upon the availability of the first opportunity by the eRedCap terminal, involves: obtaining the number of second parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of RB blocks occupied by the second parallel unicast PDSCH channels supported by the eRedCap terminal is not limited by the first threshold value.

9. The method according to claim 8, wherein obtaining the number of second parallel unicast PDSCH channels supported by the eRedCap terminal comprises: receiving a first capability message field in the capability signaling information, wherein the first capability message field is a predetermined capability message field in the capability signaling information, and the first capability message field contains a number of second parallel unicast PDSCH channels supported by the eRedCap terminal; or receiving a second opportunity message field as part of the capability signaling information, wherein the second opportunity message field contains a number of second parallel unicast PDSCH channels supported by the eRedCap terminal, and the second opportunity message field is a new capability message field specified by the eRedCap terminal.

10. The method according to claim 8, wherein the number of second parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined first delay threshold.

11. The method according to item 7, in which obtaining the number of parallel unicast PDSCH channels supported by the eRedCap terminal, provided by the eRedCap terminal based on the fact that the eRedCap terminal has the first opportunity, comprises: obtaining a number of third parallel unicast PDSCH channels supported by the eRedCap terminal, wherein the number of third parallel unicast PDSCH channels is provided by the eRedCap terminal based on the fact that the processing delay of the parallel unicast PDSCH channels by the eRedCap terminal is less than or equal to a predetermined second delay threshold, wherein the predetermined second delay threshold is greater than a predetermined first delay threshold, and the first delay threshold is a delay threshold for processing the parallel unicast PDSCH channels by a terminal that is not an eRedCap terminal; wherein the eRedCap terminal supports multiple values ​​of the number of third parallel unicast PDSCH channels, and obtaining the number of third parallel unicast PDSCH channels supported by the eRedCap terminal involves: receiving target quantity values ​​from the eRedCap terminal, wherein the target values ​​represent all multiple quantities of third parallel unicast PDSCH channels supported by the eRedCap terminal; or receiving a target number from the eRedCap terminal, wherein the target number is a maximum value of a plurality of values ​​of the number of third parallel unicast PDSCH channels supported by the eRedCap terminal; wherein multiple values ​​of the number of third parallel unicast PDSCH channels correspond to different second delay threshold values; or Obtaining the number of third parallel unicast PDSCH channels supported by the eRedCap terminal involves: receiving a first opportunity message field in the capability signaling information, wherein the first opportunity message field is a predetermined capability message field in the capability signaling information, and the first opportunity message field contains a number of third parallel unicast PDSCH channels supported by the eRedCap terminal; or receiving a second opportunity message field as part of the capability signaling information, wherein the second opportunity message field contains a number of third parallel unicast PDSCH channels supported by the eRedCap terminal, and the second opportunity message field is a new capability message field specified by the eRedCap terminal.

12. A resource scheduling device comprising a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program stored in the memory, initiating the implementation by the proposed device of the method according to any of the preceding paragraphs. 1-6.

13. A resource scheduling device comprising a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program stored in the memory, initiating the implementation by the proposed device of the method according to any of the preceding paragraphs. 7-11.

Images