Resource scheduling method, device and equipment

By acquiring downlink transmission configuration information, terminals and network-side devices can receive or send multicast downlink data based on this information, solving the problem of high base station scheduling complexity and achieving more efficient resource scheduling.

CN114071766BActive Publication Date: 2024-11-05VIVO MOBILE COMM CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202010780359.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-08-05
Publication Date
2024-11-05
Estimated Expiration
2040-08-05

AI Technical Summary

Technical Problem

In existing technologies, when a base station schedules a multicast PDSCH via a unicast PDCCH, the scheduling complexity is high, requiring the determination of information such as frequency domain resource allocation and time domain resource allocation based on the individual configuration of each UE.

Method used

A resource scheduling method is provided, which obtains downlink transmission configuration information for multicast downlink transmission. Terminal and network-side devices can receive or send downlink data based on the configuration information, thereby reducing scheduling complexity.

Benefits of technology

By configuring the same information for terminals receiving multicast downlink transmissions, the determination of configuration information for different terminals is reduced, thereby lowering the complexity of base station scheduling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114071766B_ABST
    Figure CN114071766B_ABST
Patent Text Reader

Abstract

The present application discloses a resource scheduling method, device and equipment, and relates to the field of communication technology. The method, applied to a terminal, comprises: obtaining downlink transmission configuration information, the downlink transmission configuration information is used for multicast downlink transmission; receiving downlink data according to the downlink transmission configuration information. The solution of the present application is used to solve the problem of high complexity of scheduling multicast PDSCH by unicast PDCCH in the prior art.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a resource scheduling method, device and equipment. Background Art

[0002] For Multicast and Broadcast Services (MBS), using multicast physical downlink shared channel (PDSCH) transmission is an effective means to improve the system spectrum efficiency. For multicast PDSCH in the new radio (NR), it can be scheduled through the unicast physical downlink control channel (PDCCH). When using unicast PDCCH scheduling, the base station schedules the same PDSCH through different PDCCHs, where the frequency domain resource allocation (FDRA) and time domain resource allocation (TDRA) of different PDCCHs need to indicate the same PDSCH time-frequency resources. In the prior art, for unicast PDCCH, the user equipment (UE) determines the number of FDRA bits and bit information according to the configuration of the UE-specific active bandwidth part (BWP).

[0003] Therefore, when scheduling, in order to enable the PDCCHs of different UEs to indicate the same PDSCH resources, the base station needs to determine the number of FDRA bits and / or FDRA bit information according to the active BWP configuration of each UE. Similarly, the TDRA list, modulation and coding scheme (MCS) table, etc. are also UE-specific. The base station needs to determine the bit information corresponding to each UE according to the different configurations of different UEs to schedule the same PDSCH, which increases the complexity of base station scheduling. Summary of the invention

[0004] The embodiments of the present application provide a resource scheduling method, apparatus and device, which can solve the problem of high complexity of scheduling multicast PDSCH by a base station through unicast PDCCH in the prior art.

[0005] In a first aspect, an embodiment of the present application provides a resource scheduling method, which is applied to a terminal, including:

[0006] Acquire downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission;

[0007] Downlink data is received according to the downlink transmission configuration information.

[0008] In a second aspect, an embodiment of the present application provides a resource scheduling method, which is applied to a network side device, including:

[0009] Sending downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission.

[0010] In a third aspect, an embodiment of the present application further provides a resource scheduling device, including:

[0011] An acquisition module, used to acquire downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission;

[0012] The processing module is used to receive downlink data according to the downlink transmission configuration information.

[0013] In a fourth aspect, an embodiment of the present application further provides a resource scheduling device, including:

[0014] The sending module is used to send downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission.

[0015] In the fifth aspect, an embodiment of the present application also provides a communication device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect or the second aspect.

[0016] In a sixth aspect, an embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0017] In the seventh aspect, an embodiment of the present application provides a chip, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect or the second aspect.

[0018] In an eighth aspect, an embodiment of the present application provides a program product, which is stored in a non-volatile storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect or the second aspect.

[0019] Thus, in the embodiment of the present application, after the downlink transmission configuration information is obtained, the reception of 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 can configure the same information for the terminal receiving the multicast downlink transmission, without having to determine the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 is a block diagram of a wireless communication system;

[0021] Figure 2 A schematic diagram of a process flow of a resource scheduling method applied to a terminal according to an embodiment of the present application;

[0022] Figure 3 This is one of the schematic diagrams of the first DCI structure in an embodiment of the present application;

[0023] Figure 4 This is a second schematic diagram of the first DCI structure of an embodiment of the present application;

[0024] Figure 5 A schematic diagram of a flow chart of a resource scheduling method applied to a network-side device according to an embodiment of the present application;

[0025] Figure 6 for Figure 2 A schematic diagram of the device structure corresponding to the method shown;

[0026] Figure 7 for Figure 5 A schematic diagram of the device structure corresponding to the method shown;

[0027] Figure 8 A schematic diagram of the structure of a communication device according to an embodiment of the present application;

[0028] Fig. 9 A schematic diagram of the structure of a terminal according to an embodiment of the present application;

[0029] Fig.10 A schematic diagram of the structure of a network side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0031] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here. In addition, the "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0032] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can 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 technology can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies. However, the following description describes a new radio (NR) system for example purposes, and NR terms are used in most of the following descriptions, although these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system.

[0033] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. 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 the specific type of the base station is not limited.

[0034] The resource scheduling method provided in the embodiment of the present application is described in detail below through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0035] The method of the embodiment of the present application is applied to user equipment, and user equipment (UE) can refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. The terminal device can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, or a wearable device.

[0036] like Figure 2 As shown, a resource scheduling method in an embodiment of the present application is applied to a terminal, including:

[0037] Step 201: Acquire downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission.

[0038] Here, the downlink transmission configuration information is used for multicast downlink transmission, that is, through the downlink transmission configuration information, the terminal will be able to receive the multicast physical downlink control channel PDSCH.

[0039] Here, compared with the one-to-one transmission in unicast transmission, i.e. one transmitting end and one receiving end, multicast downlink transmission refers to transmission in a one-to-many transmission mode, i.e. one transmitting end and multiple receiving ends, and can also be expressed as multicast transmission or broadcast transmission. It can be used to transmit, for example, broadcast-multicast services.

[0040] Step 202: Receive downlink data according to the downlink transmission configuration information.

[0041] In this step, after the downlink transmission configuration information is acquired in step 201, the terminal can receive the PDSCH according to the downlink transmission configuration information.

[0042] Thus, according to step 201 and step 202, the terminal using the resource scheduling method of the embodiment of the present application can complete the reception of 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 can configure the same information for the terminal receiving the multicast downlink transmission, without having to determine the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

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

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

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

[0046] Frequency domain resources;

[0047] Frequency domain resource allocation type;

[0048] Interleaving mapping indication of virtual resource blocks to physical resource blocks;

[0049] Resource block group size;

[0050] Time domain resource allocation information;

[0051] Modulation and coding schemes;

[0052] PDSCH aggregation factor;

[0053] PDSCH demodulation reference signal mapping type;

[0054] Maximum number of codewords scheduled by DCI;

[0055] Rate matching mode.

[0056] Here, frequency domain resources are used to indicate frequency domain resources used for multicast downlink transmission, which may be related information of BWP, or frequency domain resource configuration information, such as at least one of the starting common resource blocks (CRB) and the number of CRBs; or at least one of the starting physical resource blocks (PRB) and the number of PRBs. Frequency domain resource allocation type is used to indicate the frequency domain resource allocation type used for multicast downlink transmission, including at least one of downlink resource allocation type 0 (Resource Allocation Type0), downlink resource allocation type 1 (ResourceAllocation Type1) and dynamic switch (Dynamic Switch). Interleaving mapping indication of virtual resource block (VirtualResource Block, VRB) to physical resource block is used to indicate whether multicast downlink transmission performs interleaving mapping of VRB to PRB, and interleaving mapping indication of VRB to PRB can be configured by parameters such as Vrb-ToPRB-Interleaver. Resource block group (Resource Block Group, RBG) size is used to indicate the size of RBG used for multicast downlink transmission, and the RBG size can be configured by parameters such as RBG-Size. The time domain resource allocation information (TDRA) is used to indicate the TDRA of multicast downlink transmission, which can be configured through a list such as pdsch-TimeDomainAllocationList, and the table contains one or more available TDRAs. The modulation and coding scheme (MCS) can indicate the MCS of multicast downlink transmission, which can be configured through a table such as MCS-Table, and each table contains one or more available MCSs. The demodulation reference signal (DMRS) mapping type of PDSCH can indicate the DMRS mapping type of the scheduled PDSCH, such as type A (such as dmrs-DownlinkForPDSCH-MappingTypeA) or type B (such as dmrs-DownlinkForPDSCH-MappingTypeB). In addition, the downlink transmission configuration information can also include rate matching mode (such as rate Match Pattern), PDSCH aggregation factor corresponding to PDSCH, maximum number of codewords scheduled by DCI corresponding to DCI, and other information.

[0057] Among them, there may be certain associations between the various information of the downlink transmission configuration information. For example, when the frequency domain resource allocation type is Resource Allocation Type 1, the VRB to PRB interleaving mapping indication can be configured, such as vrb-ToPRB-Interleaver. Alternatively, when the frequency domain resource allocation type is configured as Resource Allocation Type 0, the VRB to PRB interleaving mapping indication does not need to be configured, but the RBG size is configured.

[0058] Of course, the downlink transmission configuration information in this embodiment includes one or more of the above-mentioned information items, and is not limited to the above-mentioned information, which will not be listed here.

[0059] Optionally, step 201 includes:

[0060] Get the downlink transmission configuration information sent by the network side device.

[0061] 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.

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

[0063] For example, predefined: multicast PDSCH supports PDSCH DMRS mapping type as PDSCH DMRS type A; the maximum number of codewords is 1; the MCS table uses a predefined table, such as table 'qam64'; the TDRA list uses a predefined table, such as using a default table; the PDSCH aggregation factor (pdsch-AggregationFactor) is equal to 1, that is, PDSCH repetition is not supported, etc. The corresponding downlink transmission configuration information configured by the network side device includes at least: frequency domain resources; frequency domain resource allocation type; VRB to PRB interleaving mapping indication; RBG size.

[0064] In addition, the network side device will send DCI to schedule PDSCH. Moreover, the DCI can be used to schedule multicast PDSCH or unicast PDSCH, that is, the DCI will carry scheduling information for multicast downlink data transmission, or carry scheduling information for unicast downlink data transmission.

[0065] Optionally, in an embodiment of the present application, DCI is transmitted by a network side device via a physical downlink control channel PDCCH, and the PDCCH may be a unicast PDCCH.

[0066] When the network side device generates DCI, it will determine the number of bits and bit information of each information field of the DCI such as FDRA, TDRA, MCS, VRB-to-PRB mapping, etc. according to the type of PDSCH it schedules, i.e., scheduling unicast PDSCH or multicast PDSCH, and the applicable configuration (which can be predefined or network side configuration). Of course, the information field can also be understood as a bit field.

[0067] In this embodiment, the information field of DCI includes but is not limited to at least one of the following: FDRA, TDRA, MCS, VRB-to-PRB mapping, and the maximum number of codewords scheduled by DCI. Specifically, for each information field, the network side device: FDRA, the number of bits and / or bit information can be determined by the configured frequency domain resources and frequency domain resource allocation type; TDRA, the number of bits and / or bit information can be determined by the configured TDRA list; VRB-to-PRB mapping, the number of bits and / or bit information can be determined by the configured frequency domain resource allocation type and / or whether the interleaved mapping of VRB to PRB is configured; the maximum number of codewords scheduled by DCI, when the configured maximum codeword is greater than 1, the maximum number of codewords scheduled by DCI of the DCI can include the MCS, New Data Indicator (NDI), and Redundancy Version (RV) indication of each transport block TB, such as TB 1: MCS, NDI, and RV, and TB 2: MCS, NDI, and RV.

[0068] In this way, for the DCI carrying the scheduling information of multicast downlink data transmission, when the network side device generates the DCI, it will determine the number of bits and bit information of each information field in the DCI according to the type of the scheduled PDSCH, which is a multicast PDSCH, and the downlink transmission configuration information. In this way, the first information in the DCI will be the same, and it 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. Among them, the first information includes frequency domain resource allocation indication, time domain resource allocation indication, interleaving mapping indication of virtual resource blocks to physical resource blocks, modulation and coding scheme, etc.

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

[0070] receiving downlink control information DCI, where the DCI carries scheduling information for multicast downlink data transmission;

[0071] The multicast downlink data is received according to the downlink transmission configuration information and the DCI.

[0072] In this way, after receiving the DCI carrying the scheduling information of the multicast downlink data transmission, each UE in the terminal group can interpret the DCI based on the acquired downlink transmission configuration information to obtain the required scheduling information and complete the reception of the multicast downlink data.

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

[0074] The size of the DCI is determined according to the downlink transmission configuration information.

[0075] In this way, the terminal will determine the size of the DCI according to the downlink transmission configuration information. Specifically, the information field and the size of the information field of the DCI will be determined according to one or more information in the downlink transmission configuration information, thereby obtaining the size of the DCI.

[0076] For example, according to the frequency domain resources in the downlink transmission configuration information, the number of bits of the information field FDRA in the DCI can be determined; according to the TDRA list in the downlink transmission configuration information, the number of bits of the information field TDRA in the DCI can be determined; according to the frequency domain resource allocation type in the downlink transmission configuration information, the number of bits of the information field VRB-to-PRB mapping in the DCI can be determined, such as being determined as 0 bits or being determined as 1 bit; according to the maximum number of codewords scheduled by the DCI in the downlink transmission configuration information, when the configured maximum codeword is greater than 1, it can be determined that the maximum number of codewords in the DCI can include the MCS, NDI and RV of each TB, and so on.

[0077] Optionally, in the embodiment of the present application, step 202 includes:

[0078] Determine the size of the DCI according to the downlink transmission configuration information;

[0079] receiving the DCI, where the DCI carries scheduling information for unicast downlink data transmission;

[0080] According to the DCI, unicast downlink data is received.

[0081] Here, for the DCI carrying the scheduling information of unicast downlink data transmission, in addition to determining its size according to the configuration information corresponding to the unicast PDSCH, it can also be determined according to the downlink transmission configuration information. After receiving the DCI, the reception of unicast downlink data can be completed based on the DCI. Of course, the interpretation of the DCI is based on the configuration information corresponding to the unicast PDSCH.

[0082] Optionally, in this embodiment, the size of the DCI is equal to a target value, and the target value is:

[0083] the maximum of the first value and the second value; or

[0084] first value; or

[0085] Second value;

[0086] 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.

[0087] That is, for the second DCI for scheduling unicast PDSCH, according to the configuration information corresponding to the unicast PDSCH, the effective bit number size of the second DCI (i.e., the minimum number of bits required for scheduling unicast PDSCH, or the number of bits in the DCI format excluding the padding bits) is equal to the first value; for the first DCI for scheduling multicast PDSCH, according to the downlink transmission configuration information, the effective bit number size of the first DCI is equal to the second value. In this way, in one way, the size of the DCI sent by the network side device is equal to the maximum value of the first value and the second value; in one way, the size of the DCI sent by the network side device, i.e., the size of the DCI format corresponding to the first or second DCI, is equal to the first value; in another way, the size of the DCI sent by the network side device is equal to the second value. Considering that the total information size of the effective bit number of each information field in the DCI is less than the target value, in this embodiment, optionally, in the DCI, if the size of the scheduling information of the downlink data transmission is less than the target value, padding is performed at the target position; wherein the target position is within the information domain or outside the information domain. In this way, if the number of valid bits of scheduling information carried by the DCI sent by the network side device is less than the target value, the DCI needs to be padded to reach the target value. The target position of the padding can be within the information domain or outside the information domain. The padded bit value can be 0 or 1. The size of the information domain can be 0, that is, the DCI does not contain the information domain.

[0088] It can be understood that, for example, if the DCI is a DCI of a certain format, such as DCI 1-1, the DCI of this format can schedule both unicast downlink data transmission and multicast downlink data transmission. Specifically, the UE can determine whether the scheduling is unicast downlink data transmission or multicast downlink data transmission according to the indication information in the DCI, or according to the control resource set (Control Resource Set, CORESET) or search space (Searchspace, SS) where the DCI is located. Because the UE must determine its DCI size (i.e., target value) before receiving the DCI of this format, when determining the size of the DCI format, it can be determined as the DCI size determined by the configuration information corresponding to the multicast transmission (i.e., the second value), or the size determined by the configuration information corresponding to the unicast transmission (i.e., the first value), or the maximum value of the two. If the size of the DCI format is determined according to the configuration information corresponding to the unicast transmission, in one implementation manner, when configuring the downlink configuration information, the base station should make the DCI size required for scheduling the multicast downlink data determined according to this information not larger than the size of the DCI format.

[0089] Take the case where the target value is equal to the size of the second DCI (i.e., the DCI for scheduling the unicast PDSCH) as an example:

[0090] In this embodiment, the number of bits included in the DCI formats corresponding to the first DCI for scheduling multicast downlink transmission and the second DCI for scheduling unicast transmission is determined according to the second DCI.

[0091] Scenario 1: Filling outside the information domain.

[0092] like Figure 3As shown, the first DCI and the second DCI are designed with 6 information fields, which are respectively used to indicate the type of PDSCH scheduled (i.e., unicast or multicast PDSCH) (for example, through the information field MBS PDSCH indicator) / or indicate the scrambling sequence initialization value of PDSCH (where unicast or multicast PDSCH corresponds to different scrambling sequence initialization values), frequency domain resource allocation information (Frequency Domain Resource Allocation, FDRA), TDRA, VRB to PRB interleaving mapping (VRB-To-PRB mapping), MCS, and others. Among them, MBS PDSCH indicator can be a 1-bit information field, MBS PDSCH indicator = 0, indicating that the scheduled PDSCH is unicast; MBS PDSCH indicator = 1, indicating that the scheduled PDSCH is multicast. The terminal parses each of the following information fields according to the type of PDSCH scheduled, that is, determines the number of bits and the indicated information of each information field. At this time, the first DCI schedules multicast PDSCH, and its length does not need to be the same as the corresponding information field in the second DCI, but only requires the overall number of bits of the two to be the same. in this way, Figure 3 The first DCI in the packet will be filled with 0 at the end, such as a zero padding area. When the terminal receives the first DCI, it does not need to interpret the zero padding at the end of the first DCI, or the zero padding at the end of the DCI does not indicate valid information.

[0093] Of course, the information field included in the first DCI may also be different from the information field included in the second DCI, for example, the second DCI includes the first information field, while the first DCI does not include the first information field. When the total information size of each information field in the first DCI is smaller than the size of the second DCI, 0 is also padded at the end.

[0094] Scenario 2: Fill in the information field.

[0095] like Figure 4As shown, the information fields of the first DCI are MBS PDSCH indicator, FDRA, TDRA, MCS and other. The information fields of the second DCI are MBS PDSCH indicator, FDRA, TDRA, VRB-To-PRB mapping, MCS and other. Among them, MBS PDSCH indicator can be a 1-bit information field, MBS PDSCH indicator = 0, indicating that the scheduled PDSCH is unicast; MBS PDSCH indicator = 1, indicating that the scheduled PDSCH is multicast. The terminal parses the following information fields according to the type of scheduled PDSCH. At this time, the first DCI schedules multicast PDSCH, and its information field and the length of the information field must be the same as those in the second DCI to achieve the same overall number of bits for the two. In this way, Figure 4 Since the FDRA of the first DCI only needs 8 bits, while the FDRA of the second DCI is 10 bits, invalid bits or zero padding can be filled in the FDRA of the first DCI. When the terminal receives the DCI format, it determines that it is the first DCI, that is, the multicast PDSCH is scheduled, and it needs to intercept 8 bits from the 10 bits corresponding to the FDRA position, and interpret that the FDRA of the first DCI is used to determine the frequency domain resource allocation of the multicast PDSCH, which can be intercepted in the MSB / LSB. In addition, Figure 4 If the first DCI in the information field does not include the VRB-To-PRB mapping field, but the second DCI includes it, then invalid bits or zero padding may be filled in the position corresponding to the VRB-To-PRB mapping of the second DCI, and invalid bits or zero padding may be filled in the tail of the information field. When the terminal receives the first DCI, it does not need to interpret these positions, or these positions do not indicate valid information.

[0096] You should know that Figure 3 , Figure 4 The information fields in the embodiment and the order of arrangement of the information fields are only examples in this embodiment. Of course, there are other implementations, which will not be described here. Figure 3 and Figure 4 In the DCI, the information field MBSPDSCH indicator is used to indicate whether the scheduled PDSCH is multicast or unicast. Of course, it can also be indicated in other implicit ways, such as the CORESET or SS where the DCI is located to determine whether the scheduled PDSCH is unicast or multicast.

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

[0098] Frequency domain resource allocation information;

[0099] Time domain resource allocation information;

[0100] Demodulation reference signal mapping type;

[0101] Modulation and coding schemes;

[0102] PDSCH aggregation factor;

[0103] Interleaving mapping of virtual resource blocks to physical resource blocks;

[0104] The number of codes contained in PDSCH;

[0105] Rate matching mode.

[0106] It should be known that when a terminal receives downlink data, i.e., data of a PDSCH, the scheduling information of the PDSCH may be indicated by the information in the information field of the DCI, may be jointly indicated by the configuration information of the PDSCH and the corresponding information field in the DCI, or may be independently indicated by the configuration information of the PDSCH. For example, to determine the FDRA for scheduling the PDSCH, the FDRA in the DCI and the resources in the frequency domain resources in the configuration information are required to determine the allocated physical resource blocks, and the DMRS mapping type of the PDSCH may be the DMRS mapping type in the configuration information, and so on.

[0107] Specifically, when DCI schedules unicast PDSCH, for example, DCI format 1-1, the terminal will determine the information field when the DCI schedules unicast PDSCH according to the configuration information corresponding to the unicast PDSCH:

[0108] For FDRA, the terminal needs to combine the configuration of active DL BWP in the configuration information corresponding to unicast PDSCH and the frequency domain resource allocation type to determine:

[0109] If the unicast PDSCH is configured with only resource allocation type 0, the number of bits of FDRA is N RBG , where N RBG Indicates the number of RBGs in the active DL BWP;

[0110] If unicast PDSCH is configured with only resource allocation type 1, the number of bits of FDRA is in Indicates the size of the active DL BWP;

[0111] If the unicast PDSCH is configured with type 0 and type 1 resource allocation, that is, Dynamic Switch, the number of bits of FDRA is

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

[0113] For TDRA, the terminal determines the time domain resources of the unicast PDSCH according to the TDRA table of the unicast PDSCH in the configuration information corresponding to the unicast PDSCH.

[0114] For MCS, the terminal determines the corresponding modulation order and target code rate according to the MCS table of the unicast PDSCH in the configuration information corresponding to the unicast PDSCH.

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

[0116] For FDRA, the terminal indicates resources within the frequency domain resources according to the frequency domain resources in the downlink transmission configuration information.

[0117] For VRB-to-PRB mapping, the mapping from VRB to PRB is determined according to the VRB to PRB mapping type in the downlink transmission configuration information.

[0118] For TDRA, the time domain resources of the DCI-scheduled multicast PDSCH are determined according to the TDRA list in the downlink transmission configuration information and the bit information of TDRA in the DCI.

[0119] For MCS, the modulation order and target code rate of the first DCI-scheduled multicast PDSCH are determined according to the MCS table in the downlink transmission configuration information and the bit information of the MCS in the DCI.

[0120] For the DMRS mapping type, the DMRS mapping type of the DCI-scheduled multicast PDSCH is determined according to the downlink transmission configuration information.

[0121] For the number of codes included in the PDSCH, the number of codes included in the multicast PDSCH scheduled by the DCI is determined according to the downlink transmission configuration information and the bit information of the maximum number of codes in the DCI.

[0122] For DMRS mapping type: directly determine the DMRS mapping type of PDSCH according to the DMRS mapping type in the downlink transmission configuration information.

[0123] Of course, other items of information in the scheduling information are determined in a similar manner and are not listed here one by one.

[0124] It can be seen from the above content that the method of the embodiment of the present application is applied to the scenario where the network side device schedules the terminal group to receive the multicast PDSCH. Each terminal in the terminal group determines the scheduling information of the multicast PDSCH by obtaining the downlink transmission configuration information. For example, the frequency domain resource of the downlink transmission configuration information is the first resource or the first BWP, and the frequency domain resource allocation type is Resource Allocation Type1. In the DCI received by terminal A, the target frequency domain resource indicated by FDRA is within the first resource or the first BWP. Therefore, according to the following calculation formula of RIV:

[0125]

[0126] The terminal can Interpret the resource indication value (RIV) in the DCI to obtain the RB for scheduling PDSCH start and the number of consecutively allocated RBs L RBs .in is the bandwidth of the first resource or the first BWP, that is, the number of RBs included in the first resource or the first BWP; RB start Indicates the number of RBs that the first RB of the PDSCH is offset from the first RB of the first resource or the first BWP. RBs It should not be greater than the number of RBs included in the first resource or the first BWP.

[0127] In summary, the method of the embodiment of the present application can complete the reception of 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 can configure the same information for the terminal receiving the multicast downlink transmission, without having to determine the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

[0128] like Figure 5 As shown, a resource scheduling method in an embodiment of the present application is applied to a network side device, including:

[0129] Step 501: Send downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission.

[0130] 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.

[0131] In this way, through step 501, the network side device informs the terminal of the downlink transmission configuration information for receiving multicast downlink transmission. In the case of scheduling multicast PDSCH, the network side device can configure the same information for the terminal receiving multicast downlink transmission, without having to determine the indication information in the DCI separately for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

[0132] Wherein, for a 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, and the downlink transmission configuration information is applicable to the one or more UEs. In this way, the downlink transmission configuration information is used to configure multicast resources of a group of UEs.

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

[0134] Frequency domain resources;

[0135] Frequency domain resource allocation type;

[0136] Interleaving mapping indication of virtual resource blocks to physical resource blocks;

[0137] Resource block group size;

[0138] Time domain resource allocation information;

[0139] Modulation and coding schemes;

[0140] PDSCH aggregation factor;

[0141] PDSCH demodulation reference signal mapping type;

[0142] Maximum number of codewords scheduled by DCI;

[0143] Rate matching mode.

[0144] Here, the frequency domain resources are used to indicate the frequency domain resources used for multicast downlink transmission, which can be related information of BWP, or frequency domain resource configuration information, such as at least one of the starting CRB and the number of CRBs; or at least one of the starting PRB and the number of PRBs. The frequency domain resource allocation type is used to indicate the frequency domain resource allocation type used for multicast downlink transmission, including: at least one of downlink resource allocation type 0 (Resource Allocation Type0), downlink resource allocation type 1 (Resource Allocation Type1) and Dynamic Switch. The VRB to PRB interleaving mapping indication is used to indicate whether the multicast downlink transmission performs VRB to PRB interleaving mapping, and the VRB to PRB interleaving mapping indication can be configured through parameters such as Vrb-ToPRB-Interleaver. The RBG size is used to indicate the size of the RBG used for multicast downlink transmission, and the RBG size can be configured through parameters such as RBG-Size. TDRA is used to indicate the TDRA for multicast downlink transmission, which can be configured through a list, such as pdsch-TimeDomainAllocationList, and the table contains one or more available TDRAs. MCS can represent the MCS of multicast downlink transmission, which can be configured through a table, such as MCS-Table, each table containing one or more available MCSs. The DMRS mapping type of PDSCH can represent the DMRS mapping type of the scheduled PDSCH, such as type A (dmrs-DownlinkForPDSCH-MappingTypeA) or type B (dmrs-DownlinkForPDSCH-MappingTypeB). In addition, the downlink transmission configuration information can also include rate matching mode (rate MatchPattern), PDSCH aggregation factor corresponding to PDSCH, maximum number of DCI scheduled codewords corresponding to DCI, and other information.

[0145] Among them, there may be certain associations between the various information of the downlink transmission configuration information. For example, when the frequency domain resource allocation type is Resource Allocation Type 1, the VRB to PRB interleaving mapping indication can be configured, such as vrb-ToPRB-Interleaver. Alternatively, when the frequency domain resource allocation type is configured as Resource Allocation Type 0, the VRB to PRB interleaving mapping indication does not need to be configured, but the RBG size is configured.

[0146] Of course, the downlink transmission configuration information in this embodiment includes one or more of the above-mentioned information items, and is not limited to the above-mentioned information, which will not be listed here.

[0147] Optionally, in the embodiment of the present application, it also includes:

[0148] Sending a DCI, where the DCI carries scheduling information for multicast downlink data transmission, or where the DCI carries scheduling information for unicast downlink data transmission.

[0149] That is, the DCI may be used to schedule the multicast PDSCH or the unicast PDSCH.

[0150] Optionally, in an embodiment of the present application, DCI is transmitted by a network side device via a PDCCH, and the PDCCH may be a unicast PDCCH.

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

[0152] The size of the DCI is determined according to the downlink transmission configuration information.

[0153] Optionally, the size of the DCI is equal to a target value, and the target value is:

[0154] the maximum of the first value and the second value; or

[0155] first value; or

[0156] Second value;

[0157] 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.

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

[0159] Considering that the total information size of each information field in the DCI may be smaller than the target value, in this embodiment, 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; wherein the target position is within the information domain or outside the information domain. In this way, if the size of the scheduling information carried by the DCI sent 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 for padding may be within the information domain or outside the information domain. The padded bit value may be 0 or 1. The size of the information domain may be 0, that is, the information domain is not included in the DCI.

[0160] Optionally, in this embodiment, the information field of DCI includes but is not limited to at least one of the following: FDRA, TDRA, MCS, VRB-to-PRB mapping, and the maximum number of codewords scheduled by DCI. DCI is generated by a network-side device. When generating DCI, the network-side device will determine the number of bits and bit information of each information field such as FDRA, TDRA, MCS, VRB-to-PRB mapping in the DCI according to the type of PDSCH scheduled by DCI, that is, whether to schedule unicast PDSCH or multicast PDSCH, according to the applicable configuration (which may be predefined or network-side configuration). In this way, the terminal will select an applicable configuration to determine the various information fields of the DCI based on the type of PDSCH scheduled by DCI. For multicast PDSCH, the network-side device will generate DCI with the same first information for the terminal group based on these configurations, and there is no need to determine it separately according to the respective configuration information of each terminal, thereby reducing the complexity of scheduling multicast PDSCH.

[0161] In this way, if the DCI sent by the network side device is used to schedule multicast PDSCH, the network side device determines the information fields of the DCI based on the downlink transmission configuration information; if the DCI sent by the network side device is used to schedule unicast PDSCH, it needs to be determined based on the unicast PDSCH configuration information.

[0162] Specifically, the network side device, for each information domain: FDRA, the number of bits and / or bit information can be determined by the configured frequency domain resources and frequency domain resource allocation type; TDRA, the number of bits and / or bit information can be determined by the configured TDRA list; VRB-to-PRB mapping, the number of bits and / or bit information can be determined by the configured frequency domain resource allocation type and / or whether VRB to PRB interleaved mapping is configured; the maximum number of codewords scheduled by DCI, when the configured maximum codeword is greater than 1, the maximum number of codewords scheduled by the DCI of the DCI can include MCS, NDI, and RV indications for each TB, such as TB 1: MCS, NDI, and RV, and TB 2: MCS, NDI, and RV.

[0163] Optionally, the scheduling information of the DCI includes at least one of the following:

[0164] Frequency domain resource allocation information;

[0165] Time domain resource allocation information;

[0166] Demodulation reference signal mapping type;

[0167] Modulation and coding schemes;

[0168] PDSCH aggregation factor;

[0169] Interleaving mapping of virtual resource blocks to physical resource blocks;

[0170] The number of codes contained in PDSCH;

[0171] Rate matching mode.

[0172] It should be known that the scheduling information of PDSCH can be indicated by the information in the information field of the DCI, can be indicated jointly by the configuration information of PDSCH and the corresponding information field information in DCI, or can be indicated independently by the configuration information of PDSCH. For example, to determine the FDRA of the scheduled PDSCH, the resources in the frequency domain resources in the FDRA in the DCI and the downlink transmission configuration information are required to determine the allocated physical resource blocks, and the DMRS mapping type of PDSCH can be the DMRS mapping type in the downlink transmission configuration information, etc.

[0173] To summarize, 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 multicast downlink transmission. In the case of scheduling multicast PDSCH, the network side device can configure the same information for the terminal receiving multicast downlink transmission, without having to determine the indication information in the DCI separately for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

[0174] It should be noted that this method is implemented in conjunction with the above-mentioned method applied to the terminal to achieve resource scheduling. The implementation method of the embodiment of the above-mentioned resource scheduling method applied to the terminal is applicable to this method and can also achieve the same technical effect.

[0175] It should also be noted that the resource scheduling method provided in the embodiment of the present application can be executed by a resource scheduling device or a control module in the resource scheduling device for executing the loading resource scheduling method. In the embodiment of the present application, the resource scheduling method provided in the embodiment of the present application is described by taking the resource scheduling device executing the loading resource scheduling method as an example.

[0176] like Figure 6 As shown, a resource scheduling device in an embodiment of the present application includes:

[0177] An acquisition module 610 is used to acquire downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission;

[0178] The processing module 620 is configured to receive downlink data according to the downlink transmission configuration information.

[0179] Optionally, the processing module includes:

[0180] A first receiving submodule, configured to receive downlink control information DCI, where the DCI carries scheduling information for multicast downlink data transmission;

[0181] The second receiving submodule is used to receive multicast downlink data according to the downlink transmission configuration information and the DCI.

[0182] Optionally, the processing module includes:

[0183] The first determination submodule is used to determine the size of the DCI according to the downlink transmission configuration information.

[0184] Optionally, the processing module includes:

[0185] A second determination submodule is used to determine the size of the DCI according to the downlink transmission configuration information;

[0186] A third receiving submodule, configured to receive the DCI, where the DCI carries scheduling information for unicast downlink data transmission;

[0187] The fourth receiving submodule is used to receive unicast downlink data according to the DCI.

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

[0189] Frequency domain resources;

[0190] Frequency domain resource allocation type;

[0191] Interleaving mapping indication of virtual resource blocks to physical resource blocks;

[0192] Resource block group size;

[0193] Time domain resource allocation information;

[0194] Modulation and coding schemes;

[0195] PDSCH aggregation factor;

[0196] PDSCH demodulation reference signal mapping type;

[0197] Maximum number of codewords scheduled by DCI;

[0198] Rate matching mode.

[0199] Optionally, the acquisition module is further used for:

[0200] Get the downlink transmission configuration information sent by the network side device.

[0201] Optionally, the size of the DCI is equal to a target value, and the target value is:

[0202] the maximum of the first value and the second value; or

[0203] first value; or

[0204] Second value;

[0205] 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.

[0206] 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; wherein the target position is within the information domain or outside the information domain.

[0207] Optionally, the scheduling information of the DCI includes at least one of the following:

[0208] Frequency domain resource allocation information;

[0209] Time domain resource allocation information;

[0210] Demodulation reference signal mapping type;

[0211] Modulation and coding schemes;

[0212] PDSCH aggregation factor;

[0213] Interleaving mapping of virtual resource blocks to physical resource blocks;

[0214] The number of codes contained in PDSCH;

[0215] Rate matching mode.

[0216] After acquiring the downlink transmission configuration information, the device of the embodiment of the present application can complete the reception 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 can configure the same information for the terminal receiving the multicast downlink transmission, without having to determine the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

[0217] It should be noted that the device is a device that applies the above-mentioned method applied to the terminal, and the implementation method of the embodiment of the above-mentioned resource scheduling method applied to the terminal is applicable to the device and can also achieve the same technical effect.

[0218] The resource scheduling device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and the non-mobile electronic device can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0219] The resource scheduling device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0220] The resource scheduling device provided in the embodiment of the present application can achieve Figure 2 To avoid repetition, the various processes implemented by the terminal in the method embodiment will not be described again here.

[0221] like Figure 7 As shown, a resource scheduling device in an embodiment of the present application includes:

[0222] The sending module 710 is used to send downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission.

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

[0224] Frequency domain resources;

[0225] Frequency domain resource allocation type;

[0226] Interleaving mapping indication of virtual resource blocks to physical resource blocks;

[0227] Resource block group size;

[0228] Time domain resource allocation information;

[0229] Modulation and coding schemes;

[0230] PDSCH aggregation factor;

[0231] PDSCH demodulation reference signal mapping type;

[0232] Maximum number of codewords scheduled by DCI;

[0233] Rate matching mode.

[0234] Optionally, the device further comprises:

[0235] The control information sending module is used to send DCI, where the DCI carries scheduling information for multicast downlink data transmission, or the DCI carries scheduling information for unicast downlink data transmission.

[0236] Optionally, the device further comprises:

[0237] The determination module is used to determine the size of the DCI according to the downlink transmission configuration information.

[0238] Optionally, the size of the DCI is equal to a target value, and the target value is:

[0239] the maximum of the first value and the second value; or

[0240] first value; or

[0241] Second value;

[0242] 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.

[0243] Optionally, the scheduling information of the DCI includes at least one of the following:

[0244] Frequency domain resource allocation information;

[0245] Time domain resource allocation information;

[0246] Demodulation reference signal mapping type;

[0247] Modulation and coding schemes;

[0248] PDSCH aggregation factor;

[0249] Interleaving mapping of virtual resource blocks to physical resource blocks;

[0250] The number of codes contained in PDSCH;

[0251] Rate matching mode.

[0252] The apparatus of the embodiment of the present application informs the terminal of the downlink transmission configuration information for receiving multicast downlink transmission. In the case of scheduling multicast PDSCH, the network side device can configure the same information for the terminal receiving multicast downlink transmission, without having to determine the indication information in the DCI separately for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

[0253] It should be noted that the device is a device that applies the above-mentioned method applied to the network side device. The implementation method of the embodiment of the above-mentioned resource scheduling method applied to the network side device is applicable to the device and can achieve the same technical effect.

[0254] The resource scheduling device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a network side device.

[0255] The resource scheduling device in the embodiment of the present application may be a device having an operating system, and the operating system is not specifically limited in the embodiment of the present application.

[0256] The resource scheduling device provided in the embodiment of the present application can achieve Figure 5 To avoid repetition, the various processes implemented by the network-side device in the method embodiment will not be described here.

[0257] Optional, such as Figure 8 As shown, the embodiment of the present application also provides a communication device, including a processor 801, a memory 802, and a program or instruction stored in 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 various processes of the resource scheduling method embodiment 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 instruction is executed by the processor 801 to implement the various processes of the resource scheduling method embodiment applied to the network side device, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0258] Fig. 9A schematic diagram of the hardware structure of a terminal for implementing various embodiments of the present application.

[0259] 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.

[0260] Those skilled in the art will appreciate that the terminal 900 may also include a power source (such as 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, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig. 9 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0261] It should be understood that in the embodiment of the present application, the input unit 904 may include a graphics processor (Graphics Processing Unit, GPU) 9041 and a microphone 9042, and the graphics processor 9041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture 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, etc. The user input unit 907 includes a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called 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 (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0262] In the embodiment of the present application, the radio frequency unit 901 receives downlink data from the network side device and sends it to the processor 910 for processing; in addition, the uplink data is sent to the network side device. 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, etc.

[0263] The memory 909 can be used to store software programs or instructions and various data. The memory 909 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 909 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices.

[0264] The processor 910 may include one or more processing units; optionally, the processor 910 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 910.

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

[0266] The processor 910 is configured to receive downlink data according to the downlink transmission configuration information.

[0267] After acquiring the downlink transmission configuration information, the terminal can complete the reception 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 can configure the same information for the terminal receiving the multicast downlink transmission, without having to determine the indication information in the DCI for the respective configuration information of different terminals, thereby reducing the complexity of scheduling.

[0268] Specifically, the embodiment of the present application also provides a network side device. Fig.10As shown, the network device 1000 includes: an antenna 1001, a radio frequency device 1002, and a baseband device 1003. The antenna 1001 is connected to the radio frequency device 1002. In the uplink direction, the radio frequency device 1002 receives information through the antenna 1001 and sends the received information to the baseband device 1003 for processing. In the downlink direction, the baseband device 1003 processes the information to be sent and sends it to the radio frequency device 1002, and the radio frequency device 1002 processes the received information and sends it out through the antenna 1001.

[0269] The frequency band processing device may be located in the baseband device 1003 . The method performed by the network-side device in the above embodiment may be implemented in the baseband device 1003 . The baseband device 1003 includes a processor 1004 and a memory 1005 .

[0270] The baseband device 1003 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.10 As shown, one of the chips is, for example, a processor 1004, which is connected to a memory 1005 to call a program in the memory 1005 to execute the network device operations shown in the above method embodiment.

[0271] The baseband device 1003 may further include a network interface 1006 for exchanging information with the radio frequency device 1002 . The interface may be, for example, a common public radio interface (CPRI).

[0272] Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 1005 and executable on the processor 1004, and the processor 1004 calls the instructions or programs in the memory 1005 to execute Figure 7 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0273] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the program or instruction implements the above-mentioned resource scheduling method applied to the terminal, or implements the various processes of the above-mentioned resource scheduling method embodiment applied to the network side device, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0274] The processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0275] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the above-mentioned resource scheduling method applied to the terminal, or to implement the various processes of the above-mentioned resource scheduling method embodiment applied to the network side device, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0276] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0277] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0278] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0279] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A resource scheduling method, applied to a terminal, characterized in that: include: Acquire downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission; receiving downlink data according to the downlink transmission configuration information; The step of receiving downlink data according to the downlink transmission configuration information includes: receiving downlink control information DCI, where the DCI is used to schedule a multicast physical downlink shared channel PDSCH or a unicast PDSCH; In a case where the DCI carries scheduling information for multicast downlink data transmission, receiving the multicast downlink data according to the downlink transmission configuration information and the DCI; In a case where the DCI carries scheduling information for unicast downlink data transmission, receiving unicast downlink data according to the DCI and configuration information corresponding to the unicast PDSCH; The size of the DCI is equal to a target value, and the target value is: a first value, wherein the first value is the size of the DCI determined according to configuration information corresponding to the unicast PDSCH; and the DCI is a unicast DCI.

2. The method according to claim 1, characterized in that The downlink transmission configuration information includes at least one of the following: Frequency domain resources; Frequency domain resource allocation type; Interleaving mapping indication of virtual resource blocks to physical resource blocks; Resource block group size; Time domain resource allocation information; Modulation and coding schemes; Physical downlink shared channel PDSCH aggregation factor; PDSCH demodulation reference signal mapping type; Maximum number of codewords scheduled by DCI; Rate matching mode.

3. The method according to claim 1, characterized in that The obtaining of downlink transmission configuration information includes: Get the downlink transmission configuration information sent by the network side device.

4. The method according to claim 1, characterized in that: In the DCI, if the size of the scheduling information of the downlink data transmission is smaller than the target value, padding is performed at the target position; wherein the target position is within the information domain or outside the information domain.

5. The method according to claim 1, characterized in that: The scheduling information of the DCI includes at least one of the following: Frequency domain resource allocation information; Time domain resource allocation information; Demodulation reference signal mapping type; Modulation and coding schemes; PDSCH aggregation factor; Interleaving mapping of virtual resource blocks to physical resource blocks; The number of codes contained in PDSCH; Rate matching mode.

6. A resource scheduling method, applied to a network side device, characterized in that: include: Sending downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission; The method further comprises: Sending a DCI, where the DCI is used to schedule a multicast PDSCH or a unicast PDSCH, and the DCI carries scheduling information for multicast downlink data transmission, or the DCI carries scheduling information for unicast downlink data transmission; The size of the DCI is equal to a target value, and the target value is: a first value, wherein the first value is the size of the DCI determined according to configuration information corresponding to the unicast PDSCH; and the DCI is a unicast DCI.

7. The method according to claim 6, characterized in that The downlink transmission configuration information includes at least one of the following: Frequency domain resources; Frequency domain resource allocation type; Interleaving mapping indication of virtual resource blocks to physical resource blocks; Resource block group size; Time domain resource allocation information; Modulation and coding schemes; PDSCH aggregation factor; PDSCH demodulation reference signal mapping type; Maximum number of codewords scheduled by DCI; Rate matching mode.

8. The method according to claim 6, characterized in that The scheduling information of the DCI includes at least one of the following: Frequency domain resource allocation information; Time domain resource allocation information; Demodulation reference signal mapping type; Modulation and coding schemes; PDSCH aggregation factor; Interleaving mapping of virtual resource blocks to physical resource blocks; The number of codes contained in PDSCH; Rate matching mode.

9. A resource scheduling device, characterized in that: include: An acquisition module, used to acquire downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission; A processing module, configured to receive downlink data according to the downlink transmission configuration information; The processing module comprises: A first receiving submodule, configured to receive a DCI, where the DCI is used to schedule a multicast physical downlink shared channel PDSCH or a unicast PDSCH; A second receiving submodule, configured to receive multicast downlink data according to the downlink transmission configuration information and the DCI when the DCI carries scheduling information for multicast downlink data transmission; A fourth receiving submodule, configured to receive unicast downlink data according to the configuration information corresponding to the DCI and the unicast PDSCH when the DCI carries scheduling information for unicast downlink data transmission; The size of the DCI is equal to a target value, and the target value is: a first value, wherein the first value is the size of the DCI determined according to configuration information corresponding to the unicast PDSCH; and the DCI is a unicast DCI.

10. The device according to claim 9, characterized in that The downlink transmission configuration information includes at least one of the following: Frequency domain resources; Frequency domain resource allocation type; Interleaving mapping indication of virtual resource blocks to physical resource blocks; Resource block group size; Time domain resource allocation information; Modulation and coding schemes; PDSCH aggregation factor; PDSCH demodulation reference signal mapping type; Maximum number of codewords scheduled by DCI; Rate matching mode.

11. A resource scheduling device, characterized in that: include: A sending module, used for sending downlink transmission configuration information, where the downlink transmission configuration information is used for multicast downlink transmission; The device also includes: A control information sending module, used to send DCI, where the DCI is used to schedule multicast PDSCH or unicast PDSCH, and the DCI carries scheduling information for multicast downlink data transmission, or the DCI carries scheduling information for unicast downlink data transmission; The size of the DCI is equal to a target value, and the target value is: a first value; wherein the first value is the size of the DCI determined according to configuration information corresponding to the unicast PDSCH; and the DCI is a unicast DCI.

12. A communication device, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the resource scheduling method as described in any one of claims 1 to 5, or implements the steps of the resource scheduling method as described in any one of claims 6 to 8.

13. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the resource scheduling method as described in any one of claims 1 to 5, or implements the steps of the resource scheduling method as described in any one of claims 6 to 8.

Citation Information

Patent Citations

  • Dm-rs transmission method for broadcast data in next-generation communication system and apparatus therefor

    CN109845179A

  • Block transmission method, downlink transmission method, NRS receiving method, UE, base station and medium

    CN110830184A

  • Multicast transmission method and apparatus, and computer storage medium

    US20190281418A1

  • Multicast or broadcast ethernet traffic transmissions over a radio access network

    US20200112941A1