CN114071766A

CN114071766A - Resource scheduling method, device and equipment

Info

Publication number: CN114071766A
Application number: CN202010780359.0A
Authority: CN
Inventors: 李娜; 潘学明
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-08-05
Filing date: 2020-08-05
Publication date: 2022-02-18
Also published as: WO2022028464A1

Abstract

The application discloses a resource scheduling method, device and equipment, and relates to the technical field of communication. The method is applied to the terminal and comprises the following steps: acquiring downlink transmission configuration information, wherein the downlink transmission configuration information is used for multicast downlink transmission; and receiving downlink data according to the downlink transmission configuration information. The scheme of the application is used for solving the problem of high complexity of scheduling the multicast PDSCH by the base station through the unicast PDCCH in the prior art.

Description

Resource scheduling method, device and equipment

Technical Field

The present application belongs to the field of communications technologies, and in particular, to a resource scheduling method, apparatus, and device.

Background

For Multicast and Broadcast Services (MBS), transmission using a Multicast Physical Downlink Shared Channel (PDSCH) is a means for effectively improving the spectrum efficiency of the system. For a multicast PDSCH in a New Radio (NR), the multicast PDSCH may be scheduled through a unicast Physical Downlink Control Channel (PDCCH), and when using unicast PDCCH scheduling, a base station schedules the same PDSCH through different PDCCHs, where Frequency Domain Resource Allocation (FDRA) and Time Domain Resource Allocation (TDRA) of different PDCCHs need to indicate the same PDSCH Time-Frequency Resource. In the prior art, for a unicast PDCCH, a User Equipment (UE) determines the number of FDRA bits and bit information according to the configuration of a UE-specific active bandwidth Part (BWP).

Therefore, when the base station performs scheduling, in order to enable PDCCHs of different UEs to indicate the same PDSCH resource, the base station needs to determine the FDRA bit number and/or FDRA bit information according to active BWP allocation of each UE. Similarly, a TDRA list, a Modulation and Coding Scheme (MCS) table, and the like are also UE-specific, and the base station needs to determine bit information corresponding to each UE according to different configurations of different UEs to schedule the identical PDSCH, thereby increasing the complexity of scheduling by the base station.

Disclosure of Invention

The embodiment of the application provides a resource scheduling method, a resource scheduling device and resource scheduling equipment, which can solve the problem of high complexity of scheduling a multicast PDSCH by a base station through a unicast PDCCH in the prior art.

In a first aspect, an embodiment of the present application provides a resource scheduling method, which is applied to a terminal, and includes:

acquiring downlink transmission configuration information, wherein the downlink transmission configuration information is used for multicast downlink transmission;

and receiving downlink data according to the downlink transmission configuration information.

In a second aspect, an embodiment of the present application provides a resource scheduling method, which is applied to a network side device, and includes:

and sending downlink transmission configuration information, wherein the downlink transmission configuration information is used for multicast downlink transmission.

In a third aspect, an embodiment of the present application further provides a resource scheduling apparatus, including:

an obtaining module, configured to obtain downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission;

and the processing module is used for receiving downlink data according to the downlink transmission configuration information.

In a fourth aspect, an embodiment of the present application further provides a resource scheduling apparatus, including:

and the sending module is used for sending downlink transmission configuration information, and the downlink transmission configuration information is used for multicast downlink transmission.

In a fifth aspect, embodiments of the present application further provide a communication device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method according to the first aspect or the second aspect.

In a sixth aspect, the present application further provides a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect or the second aspect.

In a seventh aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect or the second aspect.

In an eighth aspect, the present application provides a program product stored on a non-volatile storage medium, the program product being executed by at least one processor to implement the steps of the method according to the first or second aspect.

In this way, in the embodiment of the present application, after the downlink transmission configuration information is acquired, the reception of the downlink data can be completed according to the downlink transmission configuration information. Here, since the downlink transmission configuration information is used for multicast downlink transmission, the network side device may configure the same information for the terminals receiving multicast downlink transmission, without determining the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

Drawings

FIG. 1 is a block diagram of a wireless communication system;

fig. 2 is a flowchart illustrating a resource scheduling method applied to a terminal according to an embodiment of the present application;

fig. 3 is one of schematic diagrams of a first DCI structure according to an embodiment of the present application;

fig. 4 is a second schematic diagram of a first DCI structure according to an embodiment of the present application;

fig. 5 is a flowchart illustrating a resource scheduling method applied to a network side device according to an embodiment of the present application;

FIG. 6 is a schematic diagram of an apparatus corresponding to the method shown in FIG. 2;

FIG. 7 is a schematic diagram of an apparatus corresponding to the method shown in FIG. 5;

fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a network-side device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.

The resource scheduling method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

The method of the embodiment of the present application is applied to a User Equipment (UE), which may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal device may also be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device.

As shown in fig. 2, a resource scheduling method according to an embodiment of the present application is applied to a terminal, and includes:

step 201, downlink transmission configuration information is obtained, and the downlink transmission configuration information is used for multicast downlink transmission.

Here, the downlink transmission configuration information is used for multicast downlink transmission, that is, the terminal can receive the multicast physical downlink control channel PDSCH through the downlink transmission configuration information.

Here, the multicast downlink transmission refers to transmission by a one-to-one transmission method, i.e., one originating terminal and one receiving terminal, as compared to unicast transmission, and may also refer to multicast transmission or broadcast transmission, i.e., transmission by one originating terminal and a plurality of receiving terminals. Which may be used to transmit, for example, broadcast multicast services.

Step 202, receiving downlink data according to the downlink transmission configuration information.

In this step, after acquiring the downlink transmission configuration information in step 201, the terminal can receive the PDSCH according to the downlink transmission configuration information.

Thus, according to step 201 and step 202, after acquiring the downlink transmission configuration information, the terminal applying the resource scheduling method according to the embodiment of the present application can complete receiving of downlink data according to the downlink transmission configuration information. Here, since the downlink transmission configuration information is used for multicast downlink transmission, the network side device may configure the same information for the terminals receiving multicast downlink transmission, without determining the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

The downlink transmission configuration information is general information corresponding to a terminal group, and the terminal group is a terminal group to which the terminal belongs. The terminal group may include one or more UEs to which the downlink transmission configuration information is applicable. In this way, the downlink transmission configuration information is used to configure multicast resources of a group of UEs.

Optionally, the downlink transmission configuration information may be configured by a radio resource control RRC.

Optionally, in this embodiment of the present application, the downlink transmission configuration information includes at least one of the following:

frequency domain resources;

a frequency domain resource allocation type;

an interleaved mapping indication of virtual resource blocks to physical resource blocks;

resource block group size;

time domain resource allocation information;

a modulation and coding scheme;

a PDSCH aggregation factor;

a demodulation reference signal mapping type of the PDSCH;

maximum number of codewords for DCI scheduling;

rate matching mode.

Here, the frequency domain Resource is used to indicate a frequency domain Resource used for multicast downlink transmission, and may be BWP related information or frequency domain Resource configuration information, such as at least one of Common Resource Blocks (CRBs) and CRB number; or, at least one of a starting Physical Resource Block (PRB) and a number of PRBs is included. The frequency domain resource allocation type is used for indicating the frequency domain resource allocation type used by multicast downlink transmission, and comprises the following steps: at least one of a downlink Resource Allocation Type 0(Resource Allocation Type0), a downlink Resource Allocation Type 1(Resource Allocation Type1), and Dynamic switching (Dynamic Switch). The interleaving mapping indication from a Virtual Resource Block (VRB) to a physical Resource Block is used for indicating whether the interleaving mapping from the VRB to the PRB is performed for multicast downlink transmission, and the interleaving mapping indication from the VRB to the PRB may be configured by, for example, a VRB-ToPRB-Interleaver parameter. The Size of a Resource Block Group (RBG) is used to indicate the Size of an RBG used for multicast downlink transmission, and the Size of the RBG can be configured by, for example, an RBG-Size parameter. The Time Domain Resource Allocation information (TDRA) is used to indicate a TDRA for multicast downlink transmission, and may be configured by a list, such as a pdsch-Time Domain Allocation list, where the table includes one or more available TDRAs. The Modulation and Coding Scheme (MCS) may represent an MCS for multicast downlink transmission, and may specifically be configured by tables, such as MCS-Table, where each Table includes one or more available MCSs. A Demodulation Reference Signal (DMRS) mapping type of the PDSCH may represent a DMRS mapping type of the scheduled PDSCH, such as type a (e.g., DMRS-downlink forsch-mapping type a) or type B (e.g., DMRS-downlink forsch-mapping type B). In addition, the downlink transmission configuration information may further include information such as a rate matching Pattern (e.g., rate Match Pattern), a PDSCH aggregation factor corresponding to the PDSCH, and a maximum number of codewords corresponding to DCI scheduling of DCI.

For example, when the frequency domain Resource Allocation Type is Resource Allocation Type1, an interleaving mapping indication from VRBs to PRBs, such as VRB-ToPRB-Interleaver, may be configured. Alternatively, when the Allocation frequency domain Resource Allocation Type is Resource Allocation Type0, the size of the RBG is allocated without allocating the interleaving mapping indication of VRBs to PRBs.

Of course, the downlink configuration information in this embodiment includes one or more of the above items of information, and is not limited to the above information, and is not listed here.

Optionally, step 201 includes:

and acquiring downlink transmission configuration information sent by the network side equipment.

Thus, in this embodiment, the downlink transmission configuration information may be configured by the network side device and sent to the terminal. Optionally, the network side device may send the downlink transmission configuration information to each terminal of the terminal group to which the terminal belongs.

In addition, one or more items of the downlink transmission configuration information may also be predefined information, and then the terminal may receive downlink data according to the network side device configuration and/or the predefined information.

For example, predefined: the DMRS mapping type of the PDSCH supported by the multicast PDSCH is PDSCH DMRS type A; the maximum number of codewords is 1; the MCS table takes a predefined table, such as table 'qam 64'; the TDRA list adopts a predefined table, such as a default table; PDSCH aggregation factor (PDSCH-aggregation factor) equal to 1, i.e., PDSCH repetition is not supported, etc. And the downlink transmission configuration information configured by the corresponding network side equipment at least comprises: frequency domain resources; a frequency domain resource allocation type; an indication of the interleaving mapping of VRBs to PRBs; the RBG size.

In addition, the network side device may transmit DCI to schedule the PDSCH. Moreover, the DCI may be used to schedule a multicast PDSCH or a unicast PDSCH, that is, the DCI carries scheduling information for multicast downlink data transmission or scheduling information for unicast downlink data transmission.

Optionally, in an embodiment of the present application, the DCI is carried and transmitted by the network side device through a physical downlink control channel PDCCH, where the PDCCH may be a unicast PDCCH.

When the network side device generates the DCI, the network side device determines the bit number and bit information of each information field of the DCI, such as FDRA, TDRA, MCS, VRB-to-PRB mapping, according to the type of the PDSCH, i.e., whether the unicast PDSCH or the multicast PDSCH is scheduled, and according to an applicable configuration (which may be predefined or network side configuration). Of course, the information field can also be understood as a bit field.

In this embodiment, the information field of the DCI includes, but is not limited to, at least one of: FDRA, TDRA, MCS, VRB-to-PRB mapping, maximum number of codewords scheduled by DCI. Specifically, the network side device is configured to: FDRA, which can determine its bit number and/or bit information according to the configured frequency domain resource and frequency domain resource allocation type; the TDRA can determine the bit number and/or bit information thereof according to a configured TDRA list; the VRB-to-PRB mapping can determine the bit number and/or bit information thereof according to the configured frequency domain resource allocation type and/or whether to configure the interleaving mapping from the VRB to the PRB; when the configured maximum codeword is greater than 1, the maximum codeword of the DCI schedule may include an MCS of each transport block TB, a New Data Indicator (NDI), and a Redundancy Version (RV) Indicator, such as TB 1: MCS, NDI and RV, and TB 2: MCS, NDI, RV.

In this way, for DCI carrying scheduling information for multicast downlink data transmission, when generating DCI, the network side device determines the bit number and bit information of each information field in the DCI according to the downlink transmission configuration information, where the type of the scheduled PDSCH is the multicast PDSCH. Thus, the first information in the DCI is the same, and does not need to be determined separately according to the respective configuration information of each terminal, which reduces the complexity of scheduling the multicast PDSCH. The first information comprises a frequency domain resource allocation indication, a time domain resource allocation indication, an interleaving mapping indication from a virtual resource block to a physical resource block, a modulation and coding scheme and the like.

Therefore, in the embodiment of the present application, optionally, step 202 includes:

receiving downlink control information DCI, wherein the DCI carries scheduling information of multicast downlink data transmission;

and receiving multicast downlink data according to the downlink transmission configuration information and the DCI.

In this way, after each UE in the terminal group receives DCI carrying scheduling information for multicast downlink data transmission, the UE can decode the DCI based on the acquired downlink transmission configuration information to obtain required scheduling information, thereby completing reception of multicast downlink data.

Optionally, in an embodiment of the present application, step 202 further includes:

and determining the size of the DCI according to the downlink transmission configuration information.

Thus, the terminal determines the DCI size (DCI size) according to the downlink transmission configuration information. Specifically, the information field and the size of the information field of the DCI are determined according to one or more items of information in the downlink transmission configuration information, so as to obtain the size of the DCI.

For example, according to the frequency domain resource in the downlink transmission configuration information, the bit number of the information domain FDRA in the DCI can be determined; according to a TDRA list in the downlink transmission configuration information, the bit number of an information domain TDRA in DCI can be determined; according to the frequency domain resource allocation type in the downlink transmission configuration information, the bit number of VRB-to-PRB mapping in the information domain in the DCI can be determined, and if the bit number is determined to be 0 bit or 1 bit; according to the maximum code word number of the DCI scheduling in the downlink transmission configuration information, in the case that the configured maximum code word is greater than 1, it may be determined that the MCS, the NDI, and the RV of each TB may be included in the maximum code word number in the DCI, and so on.

Optionally, in this embodiment of the present application, step 202 includes:

determining the size of DCI according to the downlink transmission configuration information;

receiving the DCI, wherein the DCI carries scheduling information of unicast downlink data transmission;

and receiving unicast downlink data according to the DCI.

Here, the DCI carrying the scheduling information for unicast downlink data transmission may be determined according to the downlink transmission configuration information, in addition to the size of the DCI according to the configuration information corresponding to the unicast PDSCH. After receiving the DCI, the unicast downlink data can be received based on the DCI. Needless to say, the DCI is interpreted based on the configuration information corresponding to the unicast PDSCH.

Optionally, in this embodiment, the size of the DCI is equal to a target value, where the target value is:

a maximum of the first value and the second value; or

A first value; or

A second value;

the first value is the size of the DCI determined according to the configuration information corresponding to the unicast PDSCH, and the second value is the size of the DCI determined according to the downlink transmission configuration information.

That is, for the second DCI for scheduling the unicast PDSCH, the size of the effective bit number of the second DCI (i.e., the minimum bit number required for scheduling the unicast PDSCH, or the bit number except for the padding bit in the DCI format) may be equal to the first value according to the configuration information corresponding to the unicast PDSCH; and for the first DCI for scheduling the multicast PDSCH, according to the downlink transmission configuration information, the size of the effective bit number of the first DCI is equal to a second value. Thus, in one mode, the size of the DCI transmitted by the network side device is equal to the maximum value of the first value and the second value; in one mode, the size of DCI transmitted by a network side device, that is, the size of a DCI format corresponding to a first or second DCI, is equal to a first value; in another mode, the size of the DCI transmitted by the network side device is equal to the second value. Considering the fact that the size of the total information of the effective bit numbers of each information field in the DCI is smaller than the target value, in this embodiment, optionally, if the size of the scheduling information for downlink data transmission in the DCI is smaller than the target value, padding is performed at the target position; and the target position is in an information domain or out of the information domain. In this way, if the effective bit number of the scheduling information carried by the DCI transmitted by the network side device is smaller than the target value, the DCI needs to be padded to reach the target value. The target position of the filling can be in the information domain or out of the information domain. The bit value to be filled may be 0or 1. Wherein the size of the information field may be 0, i.e., the information field is not included in the DCI.

It can be understood that, for example, the DCI is a DCI of a certain format, such as DCI 1-1, where the DCI of the format may schedule unicast downlink data transmission or multicast downlink data transmission, and specifically, the UE may determine whether to schedule unicast downlink data transmission or multicast downlink data transmission according to indication information in the DCI, or according to a Control Resource Set (core Set) or a Search Space (SS) where the DCI is located. Since the UE must determine its DCI size (i.e., the target value) before receiving the DCI of the format, when determining the size of the DCI format, it may determine the DCI size determined for multicast transmission corresponding to the configuration information (i.e., the second value), or the size determined for unicast transmission corresponding to the configuration information (i.e., the first value), or the maximum value of the two. If the DCI format size is determined according to the configuration information corresponding to unicast transmission, in one embodiment, when the base station configures the downlink configuration information, the base station should make the DCI size required for scheduling multicast downlink data determined according to the information not larger than the DCI format size.

Taking the target value equal to the size of the second DCI (i.e., the DCI scheduling the unicast PDSCH) as an example:

in this embodiment, the number of bits included in a DCI format corresponding to a first DCI for scheduling multicast downlink transmission and a second DCI for scheduling unicast transmission is determined according to the second DCI.

Scene one, filling outside the information domain.

As shown in fig. 3, the design information fields of the first DCI and the second DCI are both 6, and are sequentially an indication (for example, through an information field MBS PDSCH indicator) for indicating the type of the scheduled PDSCH (i.e., a unicast or multicast PDSCH) or a scrambling sequence initialization value for indicating the PDSCH (where the unicast or multicast PDSCH corresponds To different scrambling sequence initialization values), Frequency Domain Resource Allocation information (FDRA), TDRA, and interleaving mapping (VRB-To-PRB mapping) of VRB To PRB, MCS, and others (other). Wherein, the MBS PDSCH indicator can be a 1bit information domain, and the MBS PDSCH indicator is 0, which indicates that the dispatched PDSCH is a unicast PDSCH; MBS PDSCH indicator 1 indicates that multicast PDSCH is scheduled. And the terminal respectively analyzes the next information fields according to the type of the scheduled PDSCH, namely determining the bit number and the indicated information of each information field. In this case, the first DCI schedules the multicast PDSCH, and the length of the corresponding information field in the second DCI does not need to be the same, but the total number of bits of both is only required to be the same. Thus, the first DCI in fig. 3 is padded with 0 at the tail, such as a Zero padding (Zero padding) region. And when the terminal receives the first DCI, the terminal does not need to interpret Zero padding at the tail part of the first DCI or the Zero padding at the tail part of the DCI does not indicate effective information.

Of course, the information field included in the first DCI may be different from the information field included in the second DCI, for example, the second DCI includes the first information field, and the first DCI does not include the first information field. In the case where the size of the total information of the information fields in the first DCI is smaller than that of the second DCI, 0 is padded in the tail portion as well.

And scene two, filling in the information domain.

As shown in fig. 4, the information field of the first DCI is MBS PDSCH indicator, FDRA, TDRA, MCS and other in this order. The information field of the second DCI is MBS PDSCH indicator, FDRA, TDRA, VRB-To-PRB mapping, MCS and other in sequence. Wherein, the MBS PDSCH indicator can be a 1bit information domain, and the MBS PDSCH indicator is 0, which indicates that the dispatched PDSCH is a unicast PDSCH; MBS PDSCH indicator 1 indicates that multicast PDSCH is scheduled. And the terminal respectively analyzes the next information domains according to the type of the scheduled PDSCH. In this case, the first DCI schedules the multicast PDSCH, and it is necessary that the length of the information field and the length of the information field in the second DCI are the same, so that the total number of bits is the same for both. As such, the FDRA of the first DCI in fig. 4 only needs 8 bits, and the FDRA of the second DCI is 10 bits, the FDRA of the first DCI may be filled with Invalid bits (invaid bits) or Zero padding. And when the terminal receives the DCI format, the terminal determines that the first DCI, that is, the scheduled multicast PDSCH, needs to intercept 8 bits from 10 bits at the corresponding position of the FDRA, and the FDRA that reads the first DCI is used to determine the frequency domain resource allocation of the multicast PDSCH, which may be intercepted in MSB/LSB. In addition, the first DCI in fig. 4 does not include the VRB-To-PRB mapping field, and the second DCI includes the VRB-To-PRB mapping field, it is also possible To fill invaid bits or Zero padding at a position corresponding To the VRB-To-PRB mapping of the second DCI, and fill invaid bits or Zero padding at the tail of the information field. When the terminal receives the first DCI, the positions do not need to be interpreted or do not indicate effective information.

It should be understood that the information fields in fig. 3 and fig. 4 and the arrangement order of the information fields are only examples in this embodiment, and other implementations are certainly possible and will not be described herein again. In fig. 3 and 4, the DCI indicates whether the scheduled PDSCH is multicast PDSCH or unicast PDSCH through the MBS PDSCH indicator, but may also indicate in other implicit manners, such as core set or SS where the DCI is located, to determine whether the scheduled PDSCH is unicast or multicast.

Optionally, in an embodiment of the present application, the scheduling information of the DCI includes at least one of:

frequency domain resource allocation information;

time domain resource allocation information;

demodulating a reference signal mapping type;

a modulation and coding scheme;

a PDSCH aggregation factor;

interleaving and mapping from the virtual resource block to the physical resource block;

the number of codes included in the PDSCH;

rate matching mode.

It should be noted that the terminal receives downlink data, that is, data of the PDSCH, and the scheduling information of the PDSCH may be indicated by information in an information field in the DCI, may be indicated by configuration information of the PDSCH in combination with corresponding information field information in the DCI, or may be indicated by configuration information of the PDSCH independently. For example, determining the FDRA for scheduling the PDSCH requires determining the allocated physical resource block from the FDRA in the DCI and from resources in frequency domain resources in the configuration information, and the DMRS mapping type of the PDSCH may be the DMRS mapping type in the configuration information, and so on.

Specifically, the DCI schedules the unicast PDSCH, for example, DCI format 1-1, and the terminal determines, according to the configuration information corresponding to the unicast PDSCH, an information field in the case where the DCI schedules the unicast PDSCH:

for FDRA, the terminal needs to determine, in combination with the active DL BWP configuration and the frequency domain resource allocation type in the configuration information corresponding to the unicast PDSCH:

if the unicast PDSCH is only configured with the resource allocation type0, the bit number of the FDRA is N_RBGIn which N is_RBGRepresenting the number of RBGs in active DL BWP;

if the unicast PDSCH is only configured with the resource allocation type1, the bit number of the FDRA is

Wherein

Represents the size of active DL BWP;

if the unicast PDSCH is configured with type0 and type1 resource allocation, i.e. Dynamic Switch, the bit number of the FDRA is

For VRB-to-PRB mapping (0or 1bit), if the unicast PDSCH is only configured with resource allocation type0, or is not configured with interleaved VRB-to-PRB mapping, then 0 bit; otherwise 1 bit.

And for the TDRA, the terminal determines the time domain resource of the unicast PDSCH according to the TDRA table of the unicast PDSCH in the configuration information corresponding to the unicast PDSCH.

For the MCS, the terminal determines a corresponding modulation order (modulation order) and a target code rate (target code rate) according to an MCS table of the unicast PDSCH in the configuration information corresponding to the unicast PDSCH.

Specifically, the DCI schedules the multicast PDSCH, for example, DCI format 1-1, and the terminal determines the information field when the DCI schedules the multicast PDSCH according to the downlink transmission configuration information:

for the FDRA, the terminal indicates the resources in the frequency domain resources according to the frequency domain resources in the downlink transmission configuration information.

And for VRB-to-PRB mapping, determining the mapping from the VRB to the PRB according to the mapping type from the VRB to the PRB in the downlink transmission configuration information.

And for the TDRA, determining DCI scheduling multicast PDSCH time domain resources according to the TDRA list in the downlink transmission configuration information and the bit information of the TDRA in the DCI.

And for the MCS, determining a modulation order and a target code rate of the first DCI scheduling multicast PDSCH according to the MCS table in the downlink transmission configuration information and the bit information of the MCS in the DCI.

And for the DMRS mapping type, determining the DMRS mapping type of the multicast PDSCH scheduled by the DCI according to the downlink transmission configuration information.

And determining the number of codes included in the multicast PDSCH scheduled by the DCI according to the downlink transmission configuration information and the bit information of the maximum number of codes in the DCI.

For DMRS mapping type: and directly determining the DMRS mapping type of the PDSCH according to the DMRS mapping type in the downlink transmission configuration information.

Of course, similar determination is also performed for other items of information in the scheduling information, and this is not listed here.

As can be seen from the above, the method of the embodiment of the present application is applied to a scenario where a network side device schedules a terminal group to receive a multicast PDSCH, and each terminal in the terminal group determines scheduling information for scheduling the multicast PDSCH by obtaining downlink transmission configuration information. For example, the frequency domain Resource of the downlink configuration information is a first Resource or a first BWP, and the frequency domain Resource Allocation Type is Resource Allocation Type 1. In the DCI received by the terminal a, the target frequency domain resource indicated by the FDRA is within the first resource or the first BWP, and therefore, the following calculation formula is used according to the RIV:

the terminal can be according to

Interpreting Resource Indication Value (RIV) in DCI to obtain RB for scheduling PDSCH_startAnd the number L of RB allocated consecutively_RBs. Wherein

Is the bandwidth of the first resource or the first BWP, i.e. represents the number of RBs contained in the first resource or the first BWP; RB (radio B)_startIndicates the number of RBs of which the first RB of the PDSCH is offset from the first resource or the first RB of the first BWP. Wherein L is_RBsShould not be greater than the number of RBs contained by the first resource or the first BWP.

To sum up, the method according to the embodiment of the present application can complete receiving downlink data according to the downlink transmission configuration information after acquiring the downlink transmission configuration information. Here, since the downlink transmission configuration information is used for multicast downlink transmission, the network side device may configure the same information for the terminals receiving multicast downlink transmission, without determining the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

As shown in fig. 5, a resource scheduling method according to an embodiment of the present application is applied to a network side device, and includes:

step 501, sending downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission.

Here, the downlink transmission configuration information sent by the network side device is used for multicast downlink transmission so that the terminal receives downlink data based on the downlink transmission configuration information.

Thus, through step 501, the network side device informs the terminal of the downlink transmission configuration information for receiving the multicast downlink transmission, and in the case of scheduling the multicast PDSCH, the network side device may configure the same information for the terminal receiving the multicast downlink transmission without determining the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

For the terminal group, the network side device may send the downlink transmission configuration information to each terminal of the terminal group. The terminal group may include one or more UEs to which the downlink transmission configuration information is applicable. In this way, the downlink transmission configuration information is used to configure multicast resources of a group of UEs.

Optionally, the downlink transmission configuration information includes at least one of:

frequency domain resources;

a frequency domain resource allocation type;

resource block group size;

time domain resource allocation information;

a modulation and coding scheme;

a PDSCH aggregation factor;

a demodulation reference signal mapping type of the PDSCH;

maximum number of codewords for DCI scheduling;

rate matching mode.

Here, the frequency domain resource is used to indicate a frequency domain resource used for multicast downlink transmission, and may be related information of BWP, or frequency domain resource configuration information, such as at least one of a starting CRB and a number of CRBs; still alternatively, at least one of a starting PRB and a number of PRBs is included. The frequency domain resource allocation type is used for indicating the frequency domain resource allocation type used by multicast downlink transmission, and comprises the following steps: at least one of a downlink Resource Allocation Type 0(Resource Allocation Type0), a downlink Resource Allocation Type 1(Resource Allocation Type1), and a Dynamic Switch. The interleaving mapping indication of the VRB to the PRB is used for indicating whether the interleaving mapping of the VRB to the PRB is performed for the multicast downlink transmission, and the interleaving mapping indication of the VRB to the PRB can be configured by a VRB-ToPRB-Interleaver parameter, for example. The RBG Size is used to indicate the Size of the RBG used for multicast downlink transmission, and the RBG Size can be configured by using an RBG-Size parameter, for example. The TDRA is used to indicate a TDRA for multicast downlink transmission, and may be configured by a list, such as a pdsch-timedomainnalockationlist, where the list includes one or more available TDRAs. The MCS may represent an MCS for multicast downlink transmission, and may be configured by tables, such as an MCS-Table, where each Table includes one or more available MCSs. The DMRS mapping type of the PDSCH may represent a DMRS mapping type of a scheduled PDSCH, such as type a (DMRS-downlinkforsdsch-mapping type a) or type B (DMRS-downlinkforsch-mapping type B). In addition, the downlink transmission configuration information may further include information such as a rate matching Pattern (rate Match Pattern), a PDSCH aggregation factor corresponding to the PDSCH, and a maximum codeword number for DCI scheduling corresponding to the DCI.

For example, when the frequency domain Resource Allocation Type is Resource Allocation Type1, an interleaving mapping indication from a VRB to a PRB may be configured, such as VRB-ToPRB-Interleaver. Alternatively, when the Allocation frequency domain Resource Allocation Type is Resource Allocation Type0, the size of the RBG is allocated without allocating the interleaving mapping indication of VRBs to PRBs.

Optionally, in an embodiment of the present application, the method further includes:

and sending DCI, wherein the DCI carries scheduling information of multicast downlink data transmission, or the DCI carries scheduling information of unicast downlink data transmission.

I.e., the DCI may be used to schedule a multicast PDSCH or a unicast PDSCH.

Optionally, in an embodiment of the present application, the DCI is carried and transmitted by the network side device through a PDCCH, where the PDCCH may be a unicast PDCCH.

Optionally, before sending the first physical downlink control channel PDCCH, the method further includes:

Optionally, the size of the DCI is equal to a target value, where the target value is:

a maximum of the first value and the second value; or

A first value; or

A second value;

That is, for the second DCI for scheduling the unicast PDSCH, the size of the second DCI is equal to the first value according to the configuration information corresponding to the unicast PDSCH; and for the first DCI for scheduling the multicast PDSCH, the size of the first DCI is equal to a second value according to the downlink transmission configuration information. In this way, in one mode, the size sent by the network side device is equal to the maximum value of the first value and the second value; in one mode, the size of DCI transmitted by a network side device is equal to a first value; in another mode, the size of the DCI transmitted by the network side device is equal to the second value.

Considering that the size of the total information of each information field in the DCI is smaller than the target value, in this embodiment, optionally, if the size of the scheduling information for downlink data transmission in the DCI is smaller than the target value, padding is performed at the target position; and the target position is in an information domain or out of the information domain. Thus, if the size of the scheduling information carried by the DCI transmitted by the network side device is smaller than the target value, the DCI needs to be padded to reach the target value. The target position of the filling can be in the information domain or out of the information domain. The bit value to be filled may be 0or 1. Here, the size of the information field may be 0, that is, the information field is not included in the DCI.

Optionally, in this embodiment, the information field of the DCI includes, but is not limited to, at least one of the following: FDRA, TDRA, MCS, VRB-to-PRB mapping, maximum number of codewords scheduled by DCI. The DCI is generated by a network side device, and when the network side device generates the DCI, the network side device determines the bit number and bit information of each information field in the DCI, such as FDRA, TDRA, MCS, VRB-to-PRB mapping, and the like, according to an applicable configuration (which may be predefined or network side configuration) according to the type of a scheduling PDSCH of the DCI, that is, whether a unicast PDSCH or a multicast PDSCH is scheduled. Thus, the terminal determines the information fields of the DCI with the applicable configuration for the DCI scheduled PDSCH type. For the multicast PDSCH, the network side equipment generates DCI with the same first information for the terminal group aiming at the configurations, and does not need to respectively determine according to the respective configuration information of each terminal, so that the complexity of scheduling the multicast PDSCH is reduced.

Thus, if the DCI transmitted by the network side device is the DCI for scheduling the multicast PDSCH, the network side device determines each information domain of the DCI according to the downlink transmission configuration information; if the DCI transmitted by the network side device is for scheduling the unicast PDSCH, the DCI needs to be determined according to the unicast PDSCH configuration information.

Specifically, the network side device is configured to: FDRA, whose bit number and/or bit information can be determined by the configured frequency domain resource and frequency domain resource allocation type; the TDRA can determine the bit number and/or bit information thereof according to a configured TDRA list; the VRB-to-PRB mapping can determine the bit number and/or bit information thereof according to the configured frequency domain resource allocation type and/or whether to configure the interleaving mapping from the VRB to the PRB; when the configured maximum codeword is greater than 1, the MCS, NDI, RV indication of each TB may be included in the maximum codeword of the DCI schedule, such as TB 1: MCS, NDI and RV, and TB 2: MCS, NDI, RV.

Optionally, the scheduling information of the DCI includes at least one of:

frequency domain resource allocation information;

time domain resource allocation information;

demodulating a reference signal mapping type;

a modulation and coding scheme;

a PDSCH aggregation factor;

the number of codes included in the PDSCH;

rate matching mode.

It should be noted that the scheduling information of the PDSCH may be indicated by information in the information field of the DCI, may be indicated by the configuration information of the PDSCH jointly with corresponding information field information in the DCI, or may be indicated by the configuration information of the PDSCH independently. For example, determining the FDRA for scheduling the PDSCH requires determining the allocated physical resource block from the FDRA in the DCI and the resources in the frequency domain resources in the downlink transmission configuration information, and the DMRS mapping type of the PDSCH may be the DMRS mapping type in the downlink transmission configuration information, or the like.

To sum up, in the method of the embodiment of the present application, the network side device informs the terminal of the downlink transmission configuration information for receiving the multicast downlink transmission, and in the case of scheduling the multicast PDSCH, the network side device may configure the same information for the terminal receiving the multicast downlink transmission without determining the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the scheduling complexity.

It should be noted that the method is used in cooperation with the method for scheduling resources for a terminal, and the implementation manner of the embodiment of the method for scheduling resources for a terminal is suitable for the method and can achieve the same technical effect.

It should be further noted that, in the resource scheduling method provided in the embodiment of the present application, the execution main body may be a resource scheduling apparatus, or a control module in the resource scheduling apparatus for executing the resource loading scheduling method. In the embodiment of the present application, a resource scheduling apparatus is taken as an example to execute a method for scheduling a loaded resource, and the method for scheduling a resource provided in the embodiment of the present application is described.

As shown in fig. 6, a resource scheduling apparatus according to an embodiment of the present application includes:

an obtaining module 610, configured to obtain downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission;

and a processing module 620, configured to receive downlink data according to the downlink transmission configuration information.

Optionally, the processing module includes:

the first receiving submodule is used for receiving downlink control information DCI, and the DCI carries scheduling information of multicast downlink data transmission;

and the second receiving submodule is used for receiving the multicast downlink data according to the downlink transmission configuration information and the DCI.

Optionally, the processing module includes:

and the first determining submodule is used for determining the size of the DCI according to the downlink transmission configuration information.

Optionally, the processing module includes:

the second determining submodule is used for determining the size of the DCI according to the downlink transmission configuration information;

a third receiving submodule, configured to receive the DCI, where the DCI carries scheduling information for unicast downlink data transmission;

and the fourth receiving submodule is used for receiving the unicast downlink data according to the DCI.

Optionally, the downlink transmission configuration information includes at least one of the following:

frequency domain resources;

a frequency domain resource allocation type;

resource block group size;

time domain resource allocation information;

a modulation and coding scheme;

a PDSCH aggregation factor;

a demodulation reference signal mapping type of the PDSCH;

maximum number of codewords for DCI scheduling;

rate matching mode.

Optionally, the obtaining module is further configured to:

a maximum of the first value and the second value; or

A first value; or

A second value;

Optionally, in the DCI, if the size of the scheduling information for downlink data transmission is smaller than the target value, padding is performed at the target position; and the target position is in an information domain or out of the information domain.

Optionally, the scheduling information of the DCI includes at least one of:

frequency domain resource allocation information;

time domain resource allocation information;

demodulating a reference signal mapping type;

a modulation and coding scheme;

a PDSCH aggregation factor;

the number of codes included in the PDSCH;

rate matching mode.

The device in the embodiment of the application can complete the reception of the downlink data according to the downlink transmission configuration information after acquiring the downlink transmission configuration information. Here, since the downlink transmission configuration information is used for multicast downlink transmission, the network side device may configure the same information for the terminals receiving multicast downlink transmission, without determining the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

The apparatus is an apparatus to which the method applied to the terminal is applied, and the implementation manner of the embodiment of the resource scheduling method applied to the terminal is applied to the apparatus, and the same technical effect can be achieved.

The resource scheduling apparatus in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine or a self-service machine, and the like, and the embodiments of the present application are not particularly limited.

The resource scheduling apparatus in the embodiment of the present application may be an apparatus having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The resource scheduling apparatus provided in this embodiment of the present application can implement each process implemented by the terminal in the method embodiment of fig. 2, and is not described here again to avoid repetition.

As shown in fig. 7, a resource scheduling apparatus according to an embodiment of the present application includes:

a sending module 710, configured to send downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission.

frequency domain resources;

a frequency domain resource allocation type;

resource block group size;

time domain resource allocation information;

a modulation and coding scheme;

a PDSCH aggregation factor;

a demodulation reference signal mapping type of the PDSCH;

maximum number of codewords for DCI scheduling;

rate matching mode.

Optionally, the apparatus further comprises:

and the control information sending module is used for sending DCI, wherein the DCI carries scheduling information of multicast downlink data transmission or the DCI carries scheduling information of unicast downlink data transmission.

Optionally, the apparatus further comprises:

and the determining module is used for determining the size of the DCI according to the downlink transmission configuration information.

a maximum of the first value and the second value; or

A first value; or

A second value;

Optionally, the scheduling information of the DCI includes at least one of:

frequency domain resource allocation information;

time domain resource allocation information;

demodulating a reference signal mapping type;

a modulation and coding scheme;

a PDSCH aggregation factor;

the number of codes included in the PDSCH;

rate matching mode.

The device of the embodiment of the application informs the terminal of the downlink transmission configuration information for receiving the multicast downlink transmission, and the network side equipment can configure the same information for the terminal receiving the multicast downlink transmission under the condition of scheduling the multicast PDSCH, so that the indication information in DCI does not need to be respectively determined according to the respective configuration information of different terminals, and the scheduling complexity is reduced.

It should be noted that, the apparatus is an apparatus to which the method applied to the network side device is applied, and the implementation manner of the embodiment of the resource scheduling method applied to the network side device is applied to the apparatus, and the same technical effect can be achieved.

The resource scheduling apparatus in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a network side device.

The resource scheduling apparatus in this embodiment of the present application may be an apparatus having an operating system, and the operating system is not specifically limited in this embodiment of the present application.

The resource scheduling apparatus provided in this embodiment of the present application can implement each process implemented by the network side device in the embodiment of the method in fig. 5, and is not described here again to avoid repetition.

Optionally, as shown in fig. 8, an embodiment of the present application further provides a communication device, which includes a processor 801, a memory 802, and a program or instruction stored on the memory 802 and executable on the processor 801, for example, when the communication device 800 is a terminal, the program or instruction is executed by the processor 801 to implement the processes of the embodiment of the resource scheduling method applied to the terminal, and the same technical effect can be achieved. When the communication device 800 is a network-side device, the program or the instructions are executed by the processor 801 to implement the processes of the resource scheduling method embodiment applied to the network-side device, and the same technical effects can be achieved.

Fig. 9 is a schematic hardware structure diagram of a terminal implementing various embodiments of the present application.

The terminal 900 includes but is not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909, and a processor 910.

Those skilled in the art will appreciate that the terminal 900 may further include a power source (e.g., a battery) for supplying power to various components, and the power source may be logically connected to the processor 910 through a power management system, so as to manage charging, discharging, and power consumption management functions through the power management system. The terminal structure shown in fig. 9 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.

It should be understood that, in the embodiment of the present application, the input Unit 904 may include a Graphics Processing Unit (GPU) 9041 and a microphone 9042, and the Graphics Processing Unit 9041 processes image data of a still picture or a video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 907 includes a touch panel 9071 and other input devices 9072. A touch panel 9071 also referred to as a touch screen. The touch panel 9071 may include two parts, a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In this embodiment of the application, the radio frequency unit 901 receives downlink data from a network side device and then processes the downlink data to the processor 910; in addition, the uplink data is sent to the network side equipment. Generally, the radio frequency unit 901 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

Memory 909 can be used to store software programs or instructions as well as various data. The memory 909 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 909 may include a high-speed random access Memory, and may also include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable PROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 910 may include one or more processing units; alternatively, the processor 910 may integrate an application processor, which mainly handles operating systems, user interfaces, and applications or instructions, etc., and a modem processor, which mainly handles wireless communications, such as a baseband processor. It is to be appreciated that the modem processor described above may not be integrated into processor 910.

The radio frequency unit 901 is configured to obtain downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission;

the processor 910 is configured to receive downlink data according to the downlink transmission configuration information.

After the terminal acquires the downlink transmission configuration information, the terminal can complete the reception of the downlink data according to the downlink transmission configuration information. Here, since the downlink transmission configuration information is used for multicast downlink transmission, the network side device may configure the same information for the terminals receiving multicast downlink transmission, without determining the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 10, the network device 1000 includes: antenna 1001, rf device 1002, and baseband device 1003. The antenna 1001 is connected to the radio frequency device 1002. In the uplink direction, rf device 1002 receives information via antenna 1001 and transmits the received information to baseband device 1003 for processing. In the downlink direction, the baseband device 1003 processes information to be transmitted and transmits the information to the rf device 1002, and the rf device 1002 processes the received information and transmits the processed information through the antenna 1001.

The above band processing means may be located in the baseband means 1003, and the method executed by the network side device in the above embodiment may be implemented in the baseband means 1003, where the baseband means 1003 includes a processor 1004 and a memory 1005.

The baseband device 1003 may include, for example, at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 10, where one chip, for example, a processor 1004, is connected to a memory 1005 and calls a program in the memory 1005 to perform the network device operations shown in the above method embodiments.

The baseband device 1003 may further include a network interface 1006, for exchanging information with the radio frequency device 1002, and the interface is, for example, a Common Public Radio Interface (CPRI).

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 1005 and executable on the processor 1004 are called by the processor 1004 to execute the method executed by each module shown in fig. 7, and achieve the same technical effect, and are not described herein for avoiding repetition.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the method for resource scheduling applied to a terminal or the processes in the embodiment of the method for resource scheduling applied to a network side device are implemented, and the same technical effects can be achieved, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to execute a program or an instruction to implement the foregoing resource scheduling method applied to the terminal, or to implement each process of the foregoing resource scheduling method embodiment applied to the network side device, and the same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A resource scheduling method is applied to a terminal, and is characterized by comprising the following steps:

2. The method of claim 1, wherein receiving downlink data according to the downlink transmission configuration information comprises,

3. The method of claim 2, wherein the receiving downlink data according to the downlink transmission configuration information further comprises:

4. The method of claim 1, wherein the receiving downlink data according to the downlink transmission configuration information comprises:

and receiving unicast downlink data according to the DCI.

5. The method of claim 1, wherein the downlink configuration information comprises at least one of:

frequency domain resources;

a frequency domain resource allocation type;

resource block group size;

time domain resource allocation information;

a modulation and coding scheme;

physical Downlink Shared Channel (PDSCH) aggregation factors;

a demodulation reference signal mapping type of the PDSCH;

maximum number of codewords for DCI scheduling;

rate matching mode.

6. The method of claim 1, wherein the obtaining the downlink transmission configuration information comprises:

7. The method of any of claims 2 to 4, wherein the DCI size is equal to a target value, the target value being:

a maximum of the first value and the second value; or

A first value; or

A second value;

8. The method of claim 7, wherein in the DCI, if a size of scheduling information for downlink data transmission is smaller than the target value, padding is performed at a target location; and the target position is in an information domain or out of the information domain.

9. The method of claim 2 or 4, wherein the scheduling information of the DCI comprises at least one of:

frequency domain resource allocation information;

time domain resource allocation information;

demodulating a reference signal mapping type;

a modulation and coding scheme;

a PDSCH aggregation factor;

the number of codes included in the PDSCH;

rate matching mode.

10. A resource scheduling method is applied to network side equipment, and is characterized by comprising the following steps:

11. The method of claim 10, wherein the downlink configuration information comprises at least one of:

frequency domain resources;

a frequency domain resource allocation type;

resource block group size;

time domain resource allocation information;

a modulation and coding scheme;

a PDSCH aggregation factor;

a demodulation reference signal mapping type of the PDSCH;

maximum number of codewords for DCI scheduling;

rate matching mode.

12. The method of claim 10, further comprising:

13. The method of claim 12, wherein prior to the sending the DCI, further comprising:

14. The method of claim 12 or 13, wherein the DCI size is equal to a target value, the target value being:

a maximum of the first value and the second value; or

A first value; or

A second value;

15. The method of claim 12, wherein the scheduling information of the DCI comprises at least one of:

frequency domain resource allocation information;

time domain resource allocation information;

demodulating a reference signal mapping type;

a modulation and coding scheme;

a PDSCH aggregation factor;

the number of codes included in the PDSCH;

rate matching mode.

16. A resource scheduling apparatus, comprising:

17. The apparatus of claim 16, wherein the downlink configuration information comprises at least one of:

frequency domain resources;

a frequency domain resource allocation type;

resource block group size;

time domain resource allocation information;

a modulation and coding scheme;

a PDSCH aggregation factor;

a demodulation reference signal mapping type of the PDSCH;

maximum number of codewords for DCI scheduling;

rate matching mode.

18. A resource scheduling apparatus, comprising:

19. A communications device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the resource scheduling method of any one of claims 1 to 9 or the steps of implementing the resource scheduling method of any one of claims 10 to 15.

20. A readable storage medium, on which a program or instructions are stored, which, when executed by a processor, implement the resource scheduling method of any one of claims 1 to 9 or the steps of the resource scheduling method of any one of claims 10 to 15.