Resource allocation method, terminal and network side equipment

Abstract

The present application discloses a resource allocation method, a terminal, and a network-side device, and belongs to the field of communication technology. The method of the present application includes: determining the number of bits of frequency domain resource allocation FDRA in multicast downlink control information DCI according to predefined information or the first resource block RB number; determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number. The embodiment of the present application determines the number of bits of FDRA in the multicast DCI according to predefined information or the first RB number, and determines the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, thereby realizing the resource allocation of the multicast PDSCH.

Description

Technical Field

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

[0002] In Long Term Evolution (LTE), downlink resource allocation is performed on each carrier, and resource allocation is related to the carrier configuration. However, in the New Radio (NR) system, the User Equipment (UE) works on the UE-specific Band Width Part (BWP), and the downlink resource allocation type is configured for each BWP. The number of bits indicating the Frequency Domain Resource Assignment (FDRA) is related to the resource allocation type of the BWP, the Sub-Carrier Spacing (SCS) bandwidth, and the size of the resource block group (RBG size). When different UEs are configured with different BWPs, the number of bits required for FDRA may be different, and for the same FDRA value, the actual physical resources corresponding to different UEs may also be different. Therefore, how to indicate or determine the resource allocation of multicast PDSCH needs to be solved. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a resource allocation method, a terminal and a network-side device, which can solve the problem of how to indicate or determine the resource allocation of a multicast PDSCH.

[0004] In order to solve the above technical problems, this application is implemented as follows:

[0005] In a first aspect, a resource allocation method is provided, which is applied to a terminal and includes:

[0006] Determine the number of bits of frequency domain resource allocation FDRA in multicast downlink control information DCI according to predefined information or the number of first resource blocks RB;

[0007] According to the information corresponding to the FDRA of the number of bits, frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI is determined.

[0008] In a second aspect, a resource allocation device is provided, which is applied to a terminal and includes:

[0009] A first determination module is used to determine the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI according to predefined information or the number of the first resource block RB;

[0010] The second determination module is used to determine the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number.

[0011] In a third aspect, a resource allocation method is provided, which is applied to a network side device, including:

[0012] Determine the number of bits of frequency domain resource allocation FDRA in multicast downlink control information DCI according to predefined information or the number of first resource blocks RB;

[0013] According to the information corresponding to the FDRA of the number of bits, frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI is indicated.

[0014] In a fourth aspect, a resource allocation device is provided, which is applied to a network side device, including:

[0015] A third determination module is used to determine the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI according to the predefined information or the number of the first resource block RB;

[0016] The indication module is used to indicate the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number.

[0017] In a fifth aspect, a terminal is provided, comprising 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.

[0018] In the sixth aspect, a network side device is provided, 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 third aspect.

[0019] In the seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0020] In an eighth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the method described in the first aspect, or to implement the method described in the third aspect.

[0021] In an embodiment of the present application, the number of bits of FDRA in the multicast DCI is determined according to predefined information or the first RB number, and the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI is determined according to the information corresponding to the FDRA of the said number of bits, thereby realizing the resource allocation of the multicast PDSCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 is a structural diagram of a network system that can be applied to the embodiments of the present application;

[0023] Figure 2 A schematic diagram showing a flow chart of a resource allocation method according to an embodiment of the present application;

[0024] Figure 3 It shows one of the resource allocation schematic diagrams in the embodiment of the present application;

[0025] Figure 4 The second schematic diagram of resource allocation in the embodiment of the present application is shown;

[0026] Figure 5 The third schematic diagram of resource allocation in the embodiment of the present application is shown;

[0027] Figure 6 The fourth schematic diagram of resource allocation in the embodiment of the present application is shown;

[0028] Figure 7 A second flowchart of the resource allocation method according to an embodiment of the present application is shown;

[0029] Figure 8 One of the module schematic diagrams showing the resource allocation device according to an embodiment of the present application;

[0030] Fig. 9 A structural block diagram showing a communication device according to an embodiment of the present application;

[0031] Fig.10 A structural block diagram showing a terminal according to an embodiment of the present application;

[0032] Fig.11 A second schematic diagram showing a module of a resource allocation device according to an embodiment of the present application;

[0033] Fig.12 A structural block diagram showing a network side device according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0035] 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, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "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.

[0036] 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 systems and radio technologies mentioned above as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for illustrative purposes, and the NR terminology is 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 (6 th Generation, 6G) communication system.

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

[0038] In order to enable those skilled in the art to better understand the solutions of the embodiments of the present invention, the following description is first made.

[0039] In NR Rel-15, the downlink data channel supports two types of frequency domain resource allocation types: type 0 and type 1. Type 0 supports non-continuous resource allocation, and type 1 supports continuous resource allocation. If the resource allocation IE (resource Allocation IE) configured by the RRC of the PDSCH is a dynamic switch, the UE uses type 0 or type 1 according to the type indicated by the frequency domain resource (Frequency domain resource) in the DCI. Otherwise, the UE uses the type configured by the high-level resource Allocation IE, where the resource allocation type is configured according to each BWP. When allocating resources, they are allocated within the corresponding BWP, and the RB index is numbered within the BWP.

[0040] In frequency domain resource allocation type 0, the RBs in the BWP are allocated into multiple resource block groups (RBGs), each RBG group consists of P consecutive virtual RBs (VRBs), where the value of P is given by the RRC parameter rbg-Size and is related to the bandwidth. The total number of RBGs in the bandwidth can be obtained by the bandwidth and P, that is, DCI indicates the RBG allocated to the UE PDSCH through a bitmap in the frequency domain resource allocation information field. The number of bits in the bitmap is N. RBG , N RBG Indicates the total number of RBGs in the bandwidth, Indicates the size of BWP numbered i, that is, the number of RBs contained in BWPi.

[0041] In frequency domain resource allocation type 1, the value corresponding to the frequency domain allocation information field in the DCI is the resource indication value (RIV). The bit RIV value is used to indicate the starting RB number RB allocated to the UE PDSCH start And the length of the consecutively allocated VRBs L RBs The calculation formula of RIV is as follows:

[0042] if but otherwise,

[0043] in, Indicates the size of the BWP bandwidth, that is, the number of RBs contained in the BWP.

[0044] After receiving the DCI, the UE interprets the RIV in the DCI according to the bandwidth size of the BWP, that is, the number of RBs, and obtains the RB start and L RBs The frequency domain resource allocation type 1 of NR does not support arbitrary allocation of resource blocks but only supports continuous allocation in the frequency domain, thereby reducing the number of bits required to transmit the resource block allocation related information field.

[0045] After determining the virtual RBs allocated to the PDSCH, the UE also needs to determine the corresponding PRB resources based on the correspondence between VRBs and physical resource blocks (PRBs). For example, when the UE is configured with type 1 downlink resource allocation and interleaved VRB-to-PRB mapping, the UE will map the VRB to the PRB according to certain rules; if the UE is configured with type 0 downlink resource allocation, interleaved mapping of VRB to PRB is not supported, but VRB is directly mapped to PRB.

[0046] When the UE is configured with type 1 downlink resource allocation and interleaved VRB-to-PRB mapping, there is one bit in the DCI for scheduling PDSCH to indicate whether the UE performs VRB-to-PRB mapping.

[0047] Furthermore, in the broadcast multicast transmission of Long Term Evolution (LTE), the MBMS single frequency network (MBSFN) mode is supported for sending the Multimedia Broadcast Multicast Service (MBMS) and the single cell point-to-multipoint (SC-PTM) mode for multicast service sending. In the MBSFN mode, the Physical Multicast Channel (PMCH) is used to send in the MBSFN subframe. Among them, the control information is sent through the system information (such as SIB13) and the broadcast control channel (MCCH), and the data is sent through the broadcast traffic channel (MTCH). The control information (control channel parameters and traffic channel parameters, scheduling information, etc.) and data information of the MBMS service are all sent in a broadcast mode, so that both the idle state UE and the connected state UE can receive the MBMS service, and the MBMS data information is only sent in the MBSFN subframe. SC-PTM is a multicast transmission method standardized after the MBMS service. The biggest difference from the MBSFN method is that it is only scheduled and sent in a single cell, and the group radio network temporary identifier (group RNTI, g-RNTI) is used to schedule the service. It is sent through the PDSCH channel scheduled by the PDCCH. Among them, the control information is sent through the system information (such as SIB20) and the single cell broadcast control channel (Single Cell Multicast Control Channel, SC-MCCH), and the data is sent through the single cell broadcast traffic channel (Single Cell Multicast Traffic Channel, SC-MTCH). Among them, SC-MCCH is sent through the PDSCH scheduled by the single cell RNTI (Single Cell RNTI, SC-RNTI) PDCCH, and SC-MTCH is sent through the PDSCH scheduled by the G-RNTI PDCCH (Group RNTI, group RNTI). That is, the control channel parameters and service identification, cycle information, etc. are broadcast in the broadcast message. The scheduling information is notified by the PDCCH encrypted by g-RNTI, and the data part is sent in multicast mode, which is equivalent to the interested UE listening to g-RNTI to obtain data scheduling and then receiving it.

[0048] In LTE, a UE can receive multiple broadcast and multicast services at the same time. In the MBSFN mode, different services will have different MBSFN configurations, and the UE can distinguish different services through MBSFN. In SC-PTM, different services use different g-RNTIs, and the UE can distinguish different services through g-RNTI.

[0049] At present, NR technology has evolved through two versions, Rel-15 and Rel-16. In these two versions, broadcast / multicast features have not been supported. However, there are many important usage scenarios, such as public safety and mission critical, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, software delivery over wireless, group communications and IoT applications, etc., in which broadcast / multicast features can provide substantial improvements, especially in terms of system efficiency and user experience. Therefore, in the next Rel-17 version, NR will introduce broadcast / multicast features. At present, there is no relevant solution for indicating or determining the resource allocation of multicast PDSCH. Based on this, an embodiment of the present invention provides a resource allocation method that can solve the problem of how to indicate or determine the resource allocation of multicast PDSCH.

[0050] The resource allocation 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.

[0051] like Figure 2 As shown, an embodiment of the present application provides a resource allocation method, which is applied to a terminal, including:

[0052] Step 201: Determine the number of bits of frequency domain resource allocation FDRA in multicast downlink control information DCI according to predefined information or the number of first resource blocks RB.

[0053] In the embodiment of the present application, for resource allocation of type 0, the number of bits of FDRA is related to the number of RBGs included in the BWP, wherein the number of RBGs is related to the number of RBs and the RBG size. For resource allocation of DL type 1, it is related to the number of RBs included in the BWP. That is to say, for both types of resource allocation, the number of bits of FDRA is related to the number of RBs. Here, the number of bits of FDRA in the multicast DCI can be determined by the above-mentioned first number of RBs. The above-mentioned predefined information can be a predefined number of bits.

[0054] The embodiment of the present application can obtain information corresponding to the FDRA of the number of bits by determining the number of bits of FDRA in the above-mentioned multicast DCI, and further determine the frequency domain resource allocation of the PDSCH scheduled by the multicast DCI.

[0055] Step 202: Determine frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to information corresponding to the FDRA of the bit number.

[0056] Since the resource allocation indicated by FDRA is relative, for example, in resource allocation type 0, FDRA indicates the starting RB index and the number of continuously allocated RBs, and in resource allocation type 1, each bit of the bitmap corresponds to an RBG. Therefore, it is necessary to determine the reference point of FDRA allocation, that is, where the RBs are numbered and which RBs the RBGs correspond to. In the embodiment of the present application, the first RB, the second RB, the third RB, or the fourth RB is used to determine which RBs are specifically indicated by FDRA.

[0057] The frequency domain resources may be PRBs or VRBs. Specifically, for resource allocation type 0, the RBG allocated to the multicast PDSCH is determined by the bitmap of the FDRA of the bit number, and then the corresponding VRB and PRB are determined. For resource allocation type 1, the value RIV corresponding to the FDRA of the bit number is obtained, and the VRB or PRB resource allocated to the multicast PDSCH is determined by the RIV.

[0058] The resource allocation method of an embodiment of the present application determines the number of bits of FDRA in the multicast DCI according to predefined information or the first RB number, and determines the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, thereby realizing the resource allocation of the multicast PDSCH.

[0059] Further, according to the predefined information, determining the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI includes:

[0060] The number of bits of the FDRA is determined by a predefined number of bits.

[0061] That is to say, in the embodiment of the present application, the number of bits of FDRA in the multicast DCI can be predefined.

[0062] Further, the first number of RBs is a predefined number of RBs;

[0063] Alternatively, the first number of RBs is the number of RBs corresponding to the target CORESET, the target CORESET is the CORESET with index number 0, or the target CORESET is the CORESET where the multicast DCI is located. The number of RBs corresponding to the target CORESET can also be expressed as the size of the bandwidth corresponding to the target CORESET;

[0064] Alternatively, the first number of RBs is the number of RBs contained in the carrier, which may also be expressed as the size of the bandwidth corresponding to the carrier; or, the first number of RBs is the number of RBs contained in the carrier corresponding to a specific subcarrier spacing;

[0065] Alternatively, the first number of RBs is the number of RBs included in the target BWP, and can also be expressed as the size of the bandwidth corresponding to the target BWP. The target BWP is the initial downlink BWP, or the target BWP is the BWP configured by the network side device for multicast PDSCH transmission.

[0066] Further, as a first optional implementation manner, determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the number of bits includes:

[0067] Determine frequency domain resource allocation of the multicast PDSCH within the target BWP according to information corresponding to the FDRA of the number of bits and the first RB;

[0068] The first RB is the RB with the lowest number in the target BWP, the target BWP is an initial downlink BWP, or the target BWP is a BWP configured by a network-side device for multicast PDSCH transmission.

[0069] Specifically, when the first number of RBs is the BWP configured by the network side device for multicast PDSCH transmission, the frequency domain resource allocation of the multicast PDSCH in the BWP configured by the network side device for multicast PDSCH transmission is determined. That is, when the target BWP is the BWP configured by the network side device for multicast PDSCH transmission, the number of bits of FDRA is determined by the number of RBs included in the BWP configured by the network side device for multicast PDSCH transmission.

[0070] When the target BWP is the initial downlink BWP, the number of bits of FDRA can be determined by the predefined number of bits, the number of RBs contained in the carrier, the number of RBs contained in the initial downlink BWP, the number of RBs corresponding to CORESET0, or the number of RBs corresponding to the CORESET where the multicast DCI is located.

[0071] Here, as a first optional implementation method, the number of bits of FDRA is determined according to the size of the initial downlink BWP, and the frequency domain resource allocation of the multicast PDSCH is determined according to the information corresponding to the FDRA of the bit number and the first RB, and the first RB is the RB with the lowest number in the initial downlink BWP. Optionally, the frequency domain resource allocation of the multicast PDSCH may include RBs other than the initial downlink BWP. Here, the transmission parameters of the multicast PDSCH may also be configured or predefined, such as resource allocation type, VRB to PRB mapping, RBG size, etc.

[0072] like Figure 3 As shown, the base station configures the BWP for multicast PDSCH transmission through high-level signaling, where the high-level signaling can be BWP for GPDSCH, which can be common signaling (such as configured through SIB) or UE-specific signaling (such as the base station configures each UE that receives multicast PDSCH). The configuration of BWP may include the frequency domain position and subcarrier space (SCS) of BWP. Optionally, the base station can also configure relevant parameters for multicast PDSCH transmission, such as configuring resource allocation type, VRB to PRB interleaving, RBG size, etc. through the parameter gPDSCH-config. After the UE receives the multicast DCI, it determines the frequency domain resource allocation of the PDSCH scheduled by the DCI according to the FDRA indication in the DCI. The number of bits of FDRA depends on the configuration of the BWP corresponding to the multicast PDSCH. The UE determines the allocated RB within the BWP corresponding to the multicast PDSCH, that is, the RB numbering is performed within the BWP corresponding to the multicast PDSCH.

[0073] Assuming that the frequency domain resource allocation type of the multicast PDSCH is type 0, the RBs in the BWP corresponding to the multicast PDSCH are allocated to multiple RBGs. Each RBG group consists of P consecutive virtual RBs, where the value of P is configured or predefined by the base station. The total number of RBGs in the bandwidth can be obtained by the bandwidth and P. The DCI indicates the RBGs allocated to the UE PDSCH through the FDRA bitmap, and the number of bits in the bitmap is N. RBG Each bit in the bitmap corresponds to each RBG one by one. When the value of the bit is 1, it means that the RBG corresponding to the bit is allocated to the UE.

[0074] Assuming that the frequency domain resource allocation type of the multicast PDSCH is type 1, the UE determines the starting RB number indicated by the FDRA based on the number of RBs in the BWP corresponding to the PDSCH. start And the length of the consecutively allocated VRBs L RBs , and the RB allocation is performed within the BWP corresponding to the PDSCH, that is, the RB numbering starts from the RB with the lowest number in the BWP corresponding to the PDSCH. In addition, the first optional implementation method may also include the following scenario: the first RB is the RB with the lowest number in the target BWP, and the target BWP is the initial downlink BWP. That is, the frequency domain resource allocation of the multicast PDSCH is determined according to the RB with the lowest number in the initial downlink BWP.

[0075] Further, as a second optional implementation manner, determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the number of bits includes:

[0076] Determine frequency domain resource allocation for the multicast PDSCH according to information corresponding to the FDRA of the number of bits and the second RB;

[0077] The second RB is the RB with the lowest number among the RBs corresponding to the target CORESET, the target CORESET is the CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located.

[0078] In this implementation, for the frequency domain resource allocation of multicast PDSCH, the RB numbering starts from the lowest RB of the target CORESET, and the physical resources allocated by the multicast PDSCH are determined by mapping VRB to PRB. The UE determines the allocated VRB n according to the FDRA indication in the DCI. In the mapping of VRB to PRB, for the multicast PDSCH transmission scheduled by the multicast DCI, VRB n is mapped to PRBm, where, Indicates the lowest numbered PRB in the corresponding target CORESET, or the lowest numbered PRB in the RB where the multicast DCI corresponds to the PDCCH.

[0079] like Figure 4 As shown, assuming that the target CORESET is the CORESET where the multicast DCI is located, after the UE receives the multicast DCI, it determines the frequency domain resource allocation of the PDSCH scheduled by the DCI according to the FDRA in the DCI. Assuming that the resource allocation type of the multicast PDSCH is type 1, the value corresponding to the FDRA in the DCI is RIV, which is used to indicate the starting RB number RB allocated to the UE PDSCH startAnd the length of the consecutively allocated VRBs L RBs The calculation formula of RIV is the same as the calculation formula of RIV described above. After receiving DCI, UE interprets RIV in DCI according to the size of BWP to obtain RB start and L RBs Here, the size of BWP, that is, the number of RBs, is determined by any of the following:

[0080] Predefined number of RBs;

[0081] The number of RBs contained in the carrier;

[0082] The number of RBs included in the initial BWP;

[0083] The number of RBs contained in the BWP bandwidth configured by high-level signaling.

[0084] In the resource allocation of multicast PDSCH, the RB numbering starts from the lowest RB in the CORESET where the multicast DCI is located, that is, the lowest RB in the CORESET where the DCI is located is numbered 0, and RB start The value indicates the index of the starting RB, which means that the starting RB is the RB numbered from the lowest RB in the CORESET where the DCI is located. start RB. L RBs The value of indicates the number of RBs allocated continuously starting from the starting RB.

[0085] Or, if Figure 5 As shown in the figure, in the resource allocation of multicast PDSCH, the RB numbering starts from the lowest RB in the RB where the DCI corresponding PDCCH is located, that is, the lowest RB in the RB where the DCI corresponding PDCCH is located is numbered 0, and the RB start The value indicates the index of the starting RB, which means that the starting RB is the RB numbered from the lowest RB in the RB where the DCI corresponding PDCCH is located. start RB. L RBs The value of indicates the number of RBs allocated continuously starting from the starting RB.

[0086] Optionally, in this implementation, the resource allocation type, VRB to PRB mapping, RBG size, etc. of the multicast PDSCH can be predefined or configured by high-level signaling. For example, the PDSCH scheduled by multicast DCI only supports type 0 resource allocation and does not support interleaved VRB to PRB mapping.

[0087] Optionally, in this implementation, the terminal determines the number of bits of FDRA based on the number of RBs included in the carrier bandwidth, the number of RBs included in the initial downlink bandwidth, the number of RBs corresponding to CORESET0, a predefined number of bits, or the number of RBs corresponding to the CORESET where the multicast DCI is located.

[0088] Further, as a third optional implementation, determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the number of bits includes:

[0089] Determine frequency domain resource allocation of the multicast PDSCH within the carrier according to information corresponding to the FDRA of the number of bits and the third RB;

[0090] The third RB is the RB with the lowest number in the carrier (ie, common RB 0).

[0091] like Figure 6 As shown in the figure, after the UE receives the multicast DCI, it determines the frequency domain resource allocation of the PDSCH scheduled by the DCI according to the FDRA indication in the DCI. Assuming that the resource allocation type of the multicast PDSCH is type 1, the value corresponding to the FDRA in the DCI is RIV, which is used to indicate the starting RB number RB allocated to the UE PDSCH start And the length of the consecutively allocated VRBs L RBs The calculation formula of RIV is the same as the calculation formula of RIV described above. After receiving DCI, UE interprets RIV in DCI according to the size of BWP to obtain RB start and L RBs Here, the size of the BWP may be determined according to the bandwidth size of the carrier or the corresponding carrier bandwidth size under a specific subcarrier spacing or according to the size of the initial downlink BWP.

[0092] In the resource allocation of multicast PDSCH, the RBs are numbered starting from the lowest RB (point A) of the carrier, that is, the lowest RB of the carrier is numbered 0. start The value indicates the index of the starting RB, which means that the starting RB is the RB numbered from the lowest RB of the carrier. start RB. L RBs The value of indicates the number of RBs allocated continuously starting from the starting RB.

[0093] Optionally, in this method, for each UE receiving the multicast PDSCH, the PRBs allocated by the multicast PDSCH should be included in the active downlink BWP (active DL BWP) of the UE, that is, the UE does not expect any PRB allocated by the multicast PDSCH to be outside its active BWP.

[0094] Optionally, in this implementation, the terminal determines the number of bits of FDRA based on the number of RBs included in the carrier bandwidth, the number of RBs included in the initial downlink bandwidth, the number of RBs corresponding to CORESET0, a predefined number of bits, or the number of RBs corresponding to the CORESET where the multicast DCI is located.

[0095] Further, as a fourth optional implementation, determining, according to information corresponding to the FDRA of the number of bits, frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI includes:

[0096] Determine frequency domain resource allocation of the multicast PDSCH within the carrier according to information corresponding to the FDRA of the number of bits and the fourth RB;

[0097] The fourth RB is configured by the base station, such as the base station configures the fourth RB as common RB 0, or the RB with the lowest number in the initial BWP, or the RB with the lowest number in the CORSET where the DCI is located. Further, before determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, the method also includes:

[0098] Get predefined resource allocation types;

[0099] Alternatively, the resource allocation type is obtained through high-layer signaling.

[0100] Here, the resource allocation type may be type 0 or type 1 or may be dynamically indicated type 0 or type 1.

[0101] Further, before determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, the method further includes:

[0102] Get the size of the predefined resource block group RBG;

[0103] Alternatively, the size of the RBG is obtained through high-layer signaling.

[0104] Specifically, when the resource allocation type is type 0, the size of the RBG is obtained.

[0105] In addition, in the embodiments of the present application, the time domain resource allocation is described as follows.

[0106] For the g-RNTI scrambled DCI-scheduled PDSCH, its time domain resource allocation TDRA value m indicates the m+1 row in the corresponding resource allocation table, where the corresponding resource allocation table is a predefined table, or a table configured by high-level signaling, where the high-level signaling can be common or UE-specific. For example, it is configured through SIB or UE-specific (such as the base station configures each UE that receives multicast PDSCH). For example, the PDSCH time domain allocation table (pdsch-Time Domain Allocation List) is configured through the parameter gPDSCH-config.

[0107] The resource allocation method of the embodiment of the present application determines the number of bits of FDRA in the multicast DCI according to predefined information or the first RB number, and determines the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, thereby realizing the resource allocation of the multicast PDSCH and improving the effectiveness of the communication system.

[0108] like Figure 7 As shown, the embodiment of the present application also provides a resource allocation method, which is applied to a network side device, including:

[0109] Step 701: Determine the number of bits of frequency domain resource allocation FDRA in multicast downlink control information DCI according to predefined information or the number of first resource blocks RB.

[0110] In the embodiment of the present application, for resource allocation of type 0, the number of bits of FDRA is related to the number of RBGs included in the BWP, wherein the number of RBGs is related to the number of RBs and the RBG size. For resource allocation of DL type 1, it is related to the number of RBs included in the BWP. That is to say, for both types of resource allocation, the number of bits of FDRA is related to the number of RBs. Here, the number of bits of FDRA in the multicast DCI can be indicated by the first number of RBs. The above-mentioned predefined information can be a predefined number of bits.

[0111] The embodiment of the present application indicates the number of bits of FDRA in the multicast DCI, so that the terminal can obtain the information corresponding to the FDRA of the number of bits, and further determine the frequency domain resource allocation of the PDSCH scheduled by the multicast DCI.

[0112] Step 702: Indicate frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number.

[0113] The frequency domain resource may be a PRB or a VRB. Specifically, for resource allocation type 0, the RBG allocated to the multicast PDSCH is indicated by a bitmap of the FDRA of the bit number. For resource allocation type 1, the VRB or PRB resource allocated to the multicast PDSCH is indicated by a value RIV corresponding to the FDRA of the bit number.

[0114] The resource allocation method of an embodiment of the present application indicates the number of bits of FDRA in the multicast DCI according to predefined information or the first RB number, and indicates the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, thereby realizing the resource allocation of the multicast PDSCH.

[0115] Further, according to the predefined information, indicating the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI includes:

[0116] The number of bits of the FDRA is determined by a predefined number of bits.

[0117] Further, the first number of RBs is a predefined number of RBs;

[0118] Alternatively, the first number of RBs is the number of RBs corresponding to the target CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located. The number of RBs corresponding to the target CORESET may also be expressed as the size of the bandwidth corresponding to the target CORESET;

[0119] Alternatively, the first number of RBs is the number of RBs included in the carrier, and may also be expressed as the size of the bandwidth corresponding to the carrier;

[0120] Alternatively, the first number of RBs is the number of RBs included in the target BWP, and can also be expressed as the size of the bandwidth corresponding to the target BWP. The target BWP is the initial downlink BWP, or the target BWP is the BWP configured by the network side device for multicast PDSCH transmission.

[0121] Further, according to the information corresponding to the FDRA of the number of bits, indicating the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI, including:

[0122] Indicating frequency domain resource allocation of the multicast PDSCH within the target BWP according to information corresponding to the FDRA of the number of bits and the first RB;

[0123] The first RB is the RB with the lowest number in the target BWP, the target BWP is an initial downlink BWP, or the target BWP is a BWP configured by a network-side device for multicast PDSCH transmission.

[0124] Further, according to the information corresponding to the FDRA of the number of bits, indicating the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI, including:

[0125] Indicating frequency domain resource allocation of the multicast PDSCH according to the information corresponding to the FDRA of the number of bits and the second RB;

[0126] The second RB is the RB with the lowest number among the RBs corresponding to the target CORESET, the target CORESET is the CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located.

[0127] Further, according to the information corresponding to the FDRA of the number of bits, indicating the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI, including:

[0128] Indicating frequency domain resource allocation of the multicast PDSCH within the carrier according to information corresponding to the FDRA of the number of bits and the third RB;

[0129] The third RB is the RB with the lowest number in the carrier.

[0130] Furthermore, the method further comprises:

[0131] The resource allocation type is indicated through pre-defined or higher-layer signaling.

[0132] Furthermore, the method further comprises:

[0133] The size of the resource block group RBG is indicated through pre-definition or higher-layer signaling.

[0134] It should be noted that the resource allocation method applied to the network side device is a method corresponding to the above-mentioned resource allocation method applied to the terminal side, and will not be described in detail here.

[0135] The resource allocation method of an embodiment of the present application determines the number of bits of FDRA in the multicast DCI according to predefined information or the first RB number, and indicates the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, thereby realizing the resource allocation of the multicast PDSCH.

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

[0137] like Figure 8 As shown, the embodiment of the present application further provides a resource allocation device 800, which is applied to a terminal, including:

[0138] The first determination module 801 is used to determine the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI according to predefined information or the number of first resource blocks RB;

[0139] The second determining module 802 is configured to determine frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to information corresponding to the FDRA of the bit number.

[0140] In the resource allocation device of the embodiment of the present application, the first determination module is used to determine the number of bits of the FDRA through a predefined number of bits.

[0141] In the resource allocation device of the embodiment of the present application, the first number of RBs is a predefined number of RBs;

[0142] Alternatively, the first number of RBs is the number of RBs corresponding to a target CORESET, the target CORESET is a CORESET with an index number of 0, or the target CORESET is a CORESET where the multicast DCI is located;

[0143] Alternatively, the first number of RBs is the number of RBs included in the carrier;

[0144] Alternatively, the first number of RBs is the number of RBs included in the target BWP, the target BWP is an initial downlink BWP, or the target BWP is a BWP configured by a network-side device for multicast PDSCH transmission.

[0145] In the resource allocation device of the embodiment of the present application, the second determination module is used to determine the frequency domain resource allocation of the multicast PDSCH within the target BWP according to the information corresponding to the FDRA of the number of bits and the first RB;

[0146] The first RB is the RB with the lowest number in the target BWP, the target BWP is an initial downlink BWP, or the target BWP is a BWP configured by a network-side device for multicast PDSCH transmission.

[0147] In the resource allocation device of the embodiment of the present application, the second determination module is used to determine the frequency domain resource allocation of the multicast PDSCH according to the information corresponding to the FDRA of the number of bits and the second RB;

[0148] The second RB is the RB with the lowest number among the RBs corresponding to the target CORESET, the target CORESET is the CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located.

[0149] In the resource allocation device of the embodiment of the present application, the second determination module is used to determine the frequency domain resource allocation of the multicast PDSCH within the carrier according to the information corresponding to the FDRA of the number of bits and the third RB;

[0150] The third RB is the RB with the lowest number in the carrier.

[0151] The resource allocation device in the embodiment of the present application further includes:

[0152] The first acquisition module is used for obtaining a predefined resource allocation type before the second determination module determines the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number; or obtaining the resource allocation type through high-level signaling.

[0153] The resource allocation device in the embodiment of the present application further includes:

[0154] The second acquisition module is used for the second determination module to obtain the size of the predefined resource block group RBG before determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number; or, to obtain the size of the RBG through high-level signaling.

[0155] The resource allocation device of the embodiment of the present application determines the number of bits of FDRA in the multicast DCI according to predefined information or the first RB number, and determines the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, thereby realizing the resource allocation of the multicast PDSCH.

[0156] The resource allocation device in the embodiment of the present application may be a device, or a component, integrated circuit, or chip in a terminal. The device may be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include but is not limited to the types of terminals 11 listed above, and the non-mobile terminal may 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 are not specifically limited in the embodiment of the present application.

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

[0158] The resource allocation device provided in the embodiment of the present application can achieve Figures 1 to 6 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0159] Optional, such as Fig. 9 As shown, the embodiment of the present application also provides a communication device 900, including a processor 901, a memory 902, and a program or instruction stored in the memory 902 and executable on the processor 901. For example, when the communication device 900 is a terminal, the program or instruction is executed by the processor 901 to implement the various processes of the resource allocation method embodiment applied to the terminal, and the same technical effect can be achieved. When the communication device 900 is a network side device, the program or instruction is executed by the processor 901 to implement the various processes of the resource allocation method embodiment applied to the network device side, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0160] Fig.10 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0161] The terminal 100 includes but is not limited to components such as a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110.

[0162] Those skilled in the art will appreciate that the terminal 100 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 110 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.10 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.

[0163] It should be understood that in the embodiment of the present application, the input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Other input devices 1072 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.

[0164] In the embodiment of the present application, the radio frequency unit 101 receives downlink data from the network side device and sends it to the processor 110 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 101 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0165] The memory 109 can be used to store software programs or instructions and various data. The memory 109 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 109 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 device.

[0166] The processor 110 may include one or more processing units; optionally, the processor 110 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 110.

[0167] The processor 110 is configured to determine the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI according to the predefined information or the number of the first resource block RB;

[0168] According to the information corresponding to the FDRA of the number of bits, frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI is determined.

[0169] The terminal of the embodiment of the present application determines the number of bits of FDRA in the multicast DCI according to predefined information or the first RB number, and determines the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, thereby realizing the resource allocation of the multicast PDSCH.

[0170] Optionally, the processor 110 is further configured to determine the number of bits of the FDRA by using a predefined number of bits.

[0171] Optionally, the first number of RBs is a predefined number of RBs;

[0172] Alternatively, the first number of RBs is the number of RBs corresponding to a target CORESET, the target CORESET is a CORESET with an index number of 0, or the target CORESET is a CORESET where the multicast DCI is located;

[0173] Alternatively, the first number of RBs is the number of RBs included in the carrier;

[0174] Alternatively, the first number of RBs is the number of RBs included in the target BWP, the target BWP is an initial downlink BWP, or the target BWP is a BWP configured by a network-side device for multicast PDSCH transmission.

[0175] Optionally, the processor 110 is further configured to determine frequency domain resource allocation of the multicast PDSCH within the target BWP according to the information corresponding to the FDRA of the number of bits and the first RB;

[0176] The first RB is the RB with the lowest number in the target BWP, the target BWP is an initial downlink BWP, or the target BWP is a BWP configured by a network-side device for multicast PDSCH transmission.

[0177] Optionally, the processor 110 is further configured to determine frequency domain resource allocation of the multicast PDSCH according to information corresponding to the FDRA of the number of bits and the second RB;

[0178] The second RB is the RB with the lowest number among the RBs corresponding to the target CORESET, the target CORESET is the CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located.

[0179] Optionally, the processor 110 is further configured to determine frequency domain resource allocation of the multicast PDSCH within the carrier according to the information corresponding to the FDRA of the number of bits and the third RB;

[0180] The third RB is the RB with the lowest number in the carrier.

[0181] Optionally, the processor 110 is further configured to obtain a predefined resource allocation type;

[0182] Alternatively, the resource allocation type is obtained through high-layer signaling.

[0183] Optionally, the processor 110 is further configured to obtain a size of a predefined resource block group RBG; or, obtain the size of the RBG through high-layer signaling.

[0184] The terminal of the embodiment of the present application determines the number of bits of FDRA in the multicast DCI according to predefined information or the first RB number, and determines the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, thereby realizing the resource allocation of the multicast PDSCH.

[0185] like Fig.11 As shown, the embodiment of the present application further provides a resource allocation device 1100, which is applied to a network side device, including:

[0186] The third determination module 1101 is used to determine the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI according to the predefined information or the number of the first resource block RB;

[0187] The indication module 1102 is used to indicate the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number.

[0188] In the resource allocation device of the embodiment of the present application, the third determination module is used to determine the number of bits of the FDRA through a predefined number of bits.

[0189] In the resource allocation device of the embodiment of the present application, the first number of RBs is a predefined number of RBs;

[0190] Alternatively, the first number of RBs is the number of RBs corresponding to a target CORESET, the target CORESET is a CORESET with an index number of 0, or the target CORESET is a CORESET where the multicast DCI is located;

[0191] Alternatively, the first number of RBs is the number of RBs included in the carrier;

[0192] Alternatively, the first number of RBs is the number of RBs included in the target BWP, the target BWP is an initial downlink BWP, or the target BWP is a BWP configured by a network-side device for multicast PDSCH transmission.

[0193] In the resource allocation device of the embodiment of the present application, the indication module is used to indicate the frequency domain resource allocation of the multicast PDSCH within the target BWP according to the information corresponding to the FDRA of the bit number and the first RB;

[0194] The first RB is the RB with the lowest number in the target BWP, the target BWP is an initial downlink BWP, or the target BWP is a BWP configured by a network-side device for multicast PDSCH transmission.

[0195] In the resource allocation device of the embodiment of the present application, the indication module is used to indicate the frequency domain resource allocation of the multicast PDSCH according to the information corresponding to the FDRA of the number of bits and the second RB;

[0196] The second RB is the RB with the lowest number among the RBs corresponding to the target CORESET, the target CORESET is the CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located.

[0197] In the resource allocation device of the embodiment of the present application, the indication module is used to indicate the frequency domain resource allocation of the multicast PDSCH within the carrier according to the information corresponding to the FDRA of the number of bits and the third RB;

[0198] The third RB is the RB with the lowest number in the carrier.

[0199] The resource allocation device in the embodiment of the present application further includes:

[0200] The third indication module is used to indicate the resource allocation type through predefined or high-level signaling.

[0201] The resource allocation device in the embodiment of the present application further includes:

[0202] The third indication module is used to indicate the size of the resource block group RBG through predefined or high-layer signaling.

[0203] The resource allocation device provided in the embodiment of the present application can implement each process implemented in the embodiment of the resource allocation method applied to the network side device and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0204] The resource allocation device of the embodiment of the present application determines the number of bits of FDRA in the multicast DCI according to predefined information or the first RB number, and indicates the frequency domain resource allocation of the multicast PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number, thereby realizing the resource allocation of the multicast PDSCH.

[0205] Specifically, the embodiment of the present application also provides a network side device. Fig.12 As shown, the network device 1200 includes: an antenna 121, a radio frequency device 122, and a baseband device 123. The antenna 121 is connected to the radio frequency device 122. In the uplink direction, the radio frequency device 122 receives information through the antenna 121 and sends the received information to the baseband device 123 for processing. In the downlink direction, the baseband device 123 processes the information to be sent and sends it to the radio frequency device 122, and the radio frequency device 122 processes the received information and sends it out through the antenna 121.

[0206] The frequency band processing device may be located in the baseband device 123 . The method executed by the network-side device in the above embodiment may be implemented in the baseband device 123 . The baseband device 123 includes a processor 124 and a memory 125 .

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

[0208] The baseband device 123 may further include a network interface 126 for exchanging information with the radio frequency device 122 . The interface may be, for example, a common public radio interface (CPRI).

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

[0210] 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, each process of the above-mentioned resource allocation method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0211] The processor is the processor in the terminal 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.

[0212] 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 network-side device programs or instructions to implement the various processes of the above-mentioned resource allocation method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

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

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

[0216] 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 allocation method, applied to a terminal, characterized in that: include: Determine the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI according to the first number of resource blocks RB; wherein the first number of RBs is the number of RBs corresponding to the target CORESET, and the target CORESET is the CORESET with an index number of 0; or, the first number of RBs is the number of RBs included in the initial downlink BWP, or, is the number of RBs included in the BWP configured by the network side device for multicast PDSCH transmission; Determine frequency domain resource allocation of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to information corresponding to the FDRA of the number of bits; Among them, determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the number of bits includes: According to the information corresponding to the FDRA of the bit number and the first RB, determine the frequency domain resource allocation of the multicast PDSCH within the BWP configured by the network side device for multicast PDSCH transmission; wherein the first RB is the RB with the lowest number in the BWP configured by the network side device for multicast PDSCH transmission.

2. The resource allocation method according to claim 1, characterized in that: The frequency domain resource allocation type corresponding to the multicast DCI is type1, and the method further includes: According to the number of RBs in the frequency domain corresponding to the multicast PDSCH, determine the starting RB number RB indicated by FDRA start And the length of the consecutively allocated VRBs L RBs .

3. The resource allocation method according to claim 1, characterized in that: Determining frequency domain resource allocation of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to information corresponding to the FDRA of the number of bits, including: Determine frequency domain resource allocation for the multicast PDSCH according to information corresponding to the FDRA of the number of bits and the second RB; The second RB is the RB with the lowest number among the RBs corresponding to the target CORESET, the target CORESET is the CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located.

4. The resource allocation method according to claim 1, characterized in that: Determining frequency domain resource allocation of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to information corresponding to the FDRA of the number of bits, including: Determine frequency domain resource allocation of the multicast PDSCH within the carrier according to information corresponding to the FDRA of the number of bits and the third RB; The third RB is the RB with the lowest number in the carrier.

5. The resource allocation method according to claim 1, characterized in that: Before determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the number of bits, the method further includes: Get predefined resource allocation types; Alternatively, the resource allocation type is obtained through high-layer signaling.

6. The resource allocation method according to claim 1, characterized in that: Before determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the number of bits, the method further includes: Get the size of the predefined resource block group RBG; Alternatively, the size of the RBG is obtained through high-layer signaling.

7. A resource allocation method, applied to a network side device, characterized in that: include: Determine the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI according to the first number of resource blocks RB; wherein the first number of RBs is the number of RBs corresponding to the target CORESET, and the target CORESET is the CORESET with an index number of 0; or, the first number of RBs is the number of RBs included in the initial downlink BWP, or, is the number of RBs included in the BWP configured by the network side device for multicast PDSCH transmission; Indicating frequency domain resource allocation of a multicast physical downlink shared channel PDSCH scheduled by a multicast DCI according to information corresponding to the FDRA of the number of bits; Among them, according to the information corresponding to the FDRA of the number of bits, indicating the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI, including: According to the information corresponding to the FDRA of the bit number and the first RB, the frequency domain resource allocation of the multicast PDSCH within the BWP configured by the network side device for multicast PDSCH transmission is indicated; wherein the first RB is the RB with the lowest number in the BWP configured by the network side device for multicast PDSCH transmission.

8. The resource allocation method according to claim 7, characterized in that: The frequency domain resource allocation type corresponding to the multicast DCI is type1, and the number of RBs in the frequency domain position corresponding to the multicast PDSCH is used to determine the starting RB number RB indicated by FDRA start And the length of the consecutively allocated VRBs L RBs .

9. The resource allocation method according to claim 7, characterized in that: Indicating frequency domain resource allocation of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to information corresponding to the FDRA of the number of bits, including: Indicating frequency domain resource allocation of the multicast PDSCH according to the information corresponding to the FDRA of the number of bits and the second RB; The second RB is the RB with the lowest number among the RBs corresponding to the target CORESET, the target CORESET is the CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located.

10. The resource allocation method according to claim 7, characterized in that: Indicating frequency domain resource allocation of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to information corresponding to the FDRA of the number of bits, including: Indicating frequency domain resource allocation of the multicast PDSCH within the carrier according to information corresponding to the FDRA of the number of bits and the third RB; The third RB is the RB with the lowest number in the carrier.

11. The resource allocation method according to claim 7, characterized in that: The method further comprises: The resource allocation type is indicated through pre-defined or higher-layer signaling.

12. The resource allocation method according to claim 7, characterized in that: The method further comprises: The size of the resource block group RBG is indicated through pre-definition or higher-layer signaling.

13. A resource allocation device, applied to a terminal, characterized in that: include: A first determination module is used to determine the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI according to the first resource block RB number; wherein the first RB number is the number of RBs included in the initial downlink BWP, or the number of RBs included in the BWP configured by the network side device for multicast PDSCH transmission; A second determination module is used to determine the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the number of bits; The second determination module is used to determine the frequency domain resource allocation of the multicast PDSCH within the BWP configured by the network side device for multicast PDSCH transmission based on the information corresponding to the FDRA of the bit number and the first RB; wherein the first RB is the RB with the lowest number in the BWP configured by the network side device for multicast PDSCH transmission.

14. The resource allocation device according to claim 13, characterized in that: The frequency domain resource allocation type corresponding to the multicast DCI is type1, and the first determination module is used to determine the starting RB number RB indicated by the FDRA according to the number of RBs in the frequency domain position corresponding to the multicast PDSCH start And the length of the consecutively allocated VRBs L RBs .

15. The resource allocation device according to claim 13, characterized in that: The second determination module is used to determine the frequency domain resource allocation of the multicast PDSCH according to the information corresponding to the FDRA of the number of bits and the second RB; The second RB is the RB with the lowest number among the RBs corresponding to the target CORESET, the target CORESET is the CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located.

16. The resource allocation device according to claim 13, characterized in that: The second determination module is used to determine the frequency domain resource allocation of the multicast PDSCH within the carrier according to the information corresponding to the FDRA of the number of bits and the third RB; The third RB is the RB with the lowest number in the carrier.

17. The resource allocation device according to claim 13, characterized in that: Also includes: The first acquisition module is used for obtaining a predefined resource allocation type before the second determination module determines the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number; or obtaining the resource allocation type through high-level signaling.

18. The resource allocation device according to claim 13, characterized in that: Also includes: The second acquisition module is used for the second determination module to obtain the size of the predefined resource block group RBG before determining the frequency domain resource allocation of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI according to the information corresponding to the FDRA of the bit number; or, to obtain the size of the RBG through high-level signaling.

19. A terminal, 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 steps of the resource allocation method according to any one of claims 1 to 6.

20. A resource allocation device, applied to a network side device, characterized in that: include: The third determination module is used to determine the number of bits of the frequency domain resource allocation FDRA in the multicast downlink control information DCI according to the first resource block RB number; wherein the first RB number is the number of RBs corresponding to the target CORESET, and the target CORESET is the CORESET with an index number of 0; or, the first RB number is the number of RBs included in the initial downlink BWP, or, is the number of RBs included in the BWP configured by the network side device for multicast PDSCH transmission; An indication module, used to indicate frequency domain resource allocation of a multicast physical downlink shared channel PDSCH scheduled by a multicast DCI according to information corresponding to the FDRA of the bit number; Among them, the indication module is used to indicate the frequency domain resource allocation of the multicast PDSCH within the BWP configured by the network side device for multicast PDSCH transmission according to the information corresponding to the FDRA of the bit number and the first RB; wherein the first RB is the RB with the lowest number in the BWP configured by the network side device for multicast PDSCH transmission.

21. The resource allocation device according to claim 20, characterized in that: The frequency domain resource allocation type corresponding to the multicast DCI is type1, and the number of RBs in the frequency domain position corresponding to the multicast PDSCH is used to determine the starting RB number RB indicated by FDRA start And the length of the consecutively allocated VRBs L RBs .

22. The resource allocation device according to claim 20, characterized in that: The indication module is used to indicate the frequency domain resource allocation of the multicast PDSCH according to the information corresponding to the FDRA of the bit number and the second RB; The second RB is the RB with the lowest number among the RBs corresponding to the target CORESET, the target CORESET is the CORESET with an index number of 0, or the target CORESET is the CORESET where the multicast DCI is located.

23. The resource allocation device according to claim 20, characterized in that: The indication module is used to indicate the frequency domain resource allocation of the multicast PDSCH within the carrier according to the information corresponding to the FDRA of the bit number and the third RB; The third RB is the RB with the lowest number in the carrier.

24. The resource allocation device according to claim 20, characterized in that: Also includes: The third indication module is used to indicate the resource allocation type through predefined or high-level signaling.

25. The resource allocation device according to claim 20, characterized in that: Also includes: The fourth indication module is used to indicate the size of the resource block group RBG through predefined or high-layer signaling.

26. A network side device, characterized in that: It 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 steps of the resource allocation method as claimed in any one of claims 7 to 12.

27. 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 a processor, it implements the resource allocation method according to any one of claims 1 to 6, or implements the steps of the resource allocation method according to any one of claims 7 to 12.

Images