Patent Description:
In Long Term Evolution (Long Term Evolution, LTE), downlink resource assignment is performed on each carrier, and resource assignment is related to a carrier configuration. However, in a New Radio (New Radio, NR) system, user equipment (User Equipment, UE) works on a UE-specific bandwidth part (Band Width Part, BWP), and a downlink resource assignment type is configured for each BWP. A quantity of bits that indicate frequency domain resource assignment (Frequency Domain Resource Assignment, FDRA) is related to a resource assignment type of the BWP, sub-carrier spacing (Sub-Carrier Spacing, SCS) bandwidth, and a resource block group size (RBG size). When different BWPs are configured for different UEs, a quantity of required FDRA bits may be different. In addition, for a same FDRA value, actual physical resources corresponding to different UEs may also be different. Therefore, how to indicate or determine resource assignment of a multicast PDSCH (Physical Downlink Shared Channel) needs to be resolved.

<CIT> provides some embodiments, which include methods for receiving, by a use equipment(UE) in a wireless network, assignment of frequency-domain resources of a communication channel. Such embodiments include receiving an indication of an active carrier bandwidth part (BWP) of a size NBWP,<NUM>sizefrequency-domain resource blocks (RBs).

<CIT> provides methods, user equipment (UE), and base stations for downlink control information (DCI) formats reception or transmission. A method of operating a UE to transmit a physical uplink shared channel (PUSCH) includes receiving a configuration for a number of bits for a field that indicates a parameter in a first downlink control information (DCI) format; and receiving a physical downlink control channel (PDCCH) that provides either the first DCI format scheduling the PUSCH or a second DCI format scheduling the PUSCH.

Terms "first" and "second" in the specification and claims of this application are used to distinguish between similar objects, and do not need to be used to describe a specific order or sequence. It should be understood that data used in this way may be interchangeable in an appropriate case, so that the embodiments of this application can be implemented in a sequence other than those shown or described herein, and objects distinguished by "first" and "second" are generally of a same type, and a quantity of objects is not limited. For example, there may be one or more first targets. In addition, in the specification and the claims, "and/or" represents at least one of connected objects, and the character "/" generally represents an "or" relationship between associated objects.

It should be noted that the technology described in this application is not limited to a Long Term Evolution (Long Time Evolution, LTE)/LTE-advanced (LTE-Advanced, LTE-A) system, and may also be used in various wireless communication systems, for example, Code Division Multiple Access (Code Division Multiple Access, CDMA), Time Division Multiple Access (Time Division Multiple Access, TDMA), Frequency Division Multiple Access (Frequency Division Multiple Access, FDMA), Orthogonal Frequency Division Multiple Access (Orthogonal Frequency Division Multiple Access, OFDMA), Single-carrier Frequency-Division Multiple Access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and another system. The terms "system" and "network" in the embodiments of this application are often used interchangeably. The described technology may be used in the foregoing system and radio technology, and may also be used in another system and radio technology. However, a New Radio (New Radio, NR) system is described below as an example, and the term NR is used in most of the descriptions, although these technologies can also be used in an application other than an application of the NR system, for example, a sixth (<NUM>th Generation, <NUM>) communication system.

<FIG> is a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal <NUM> and a network side device <NUM>. The terminal <NUM> may also be referred to as a terminal device or user equipment (User Equipment, UE). The terminal <NUM> may be a terminal side device such as a mobile phone, a tablet personal computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop 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), or a pedestrian terminal (PUE). The wearable device includes a band, a headset, eyeglasses, or the like. It should be noted that a specific type of the terminal <NUM> is not limited in this embodiment of this application. The network side device <NUM> may be a base station or a core network. The base station may be referred to as a NodeB, 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 NodeB, an evolved NodeB (eNB), a home NodeB, a home evolved NodeB, a WLAN access point, a WiFi node, a transmitting receiving point (Transmitting Receiving Point, TRP), or another suitable term in the field provided that a same technical effect is achieved. The base station is not limited to a specific technical term. It should be noted that, in this application, only a base station in an NR system is used as an example, but a specific type of the base station is not limited.

To enable a person skilled in the art to better understand the solutions of the embodiments of the present invention, the following descriptions are first provided.

In NR Rel-<NUM>, a downlink data channel supports two frequency domain resource assignment types: type (type) <NUM> and type <NUM>. The type <NUM> supports discontinuous resource assignment. The type <NUM> is continuous resource assignment. If a resource allocation IE (resource Allocation IE) configured for radio resource control (Radio Resource Control, RRC) of a PDSCH is dynamic switch (dynamic switch), UE uses type <NUM> or type <NUM> based on a type indicated by a frequency domain resource (Frequency domain resource) in DCI. Otherwise, the UE uses a type configured by a higher layer resource assignment IE, where a resource assignment type is configured according to each BWP. During resource assignment, a resource is assigned in a corresponding BWP, and an index of an RB is numbered in the BWP.

In a frequency domain resource assignment type <NUM>, RBs in the BWP are assigned to multiple resource block groups (resource block group, RBG). Each RBG group includes P consecutive virtual RBs (Virtual RB, VRB). A value of P is given by an RRC parameter RBG size and is related to bandwidth. A total quantity of RBGs in the bandwidth may be obtained by using the bandwidth and P, that is, <MAT>. DCI indicates, by using a bitmap (bitmap) of a frequency domain resource assignment information field, an RBG assigned to a UE PDSCH, a quantity of bits in the bitmap is NRBG, NRBG indicates a total quantity of RBGs in the bandwidth, and <MAT> indicates a size of a BWP numbered i, that is, a quantity of RBs included in a BWPi.

In a frequency domain resource assignment type <NUM>, a value corresponding to a frequency domain assignment information field in the DCI is a resource indication value (resource indication Value, RIV), and a <MAT> bit RIV value is used to indicate a number RBstart of a start RB assigned to a UE PDSCH and a length LRBs of consecutively assigned VRBs. A calculation formula of the RIV is as follows:.

If <MAT>; otherwise, <MAT>, where <MAT> represents a bandwidth size of a BWP, that is, a quantity of RBs included in the BWP.

After receiving the DCI, the UE interprets the RIV in the DCI based on the bandwidth size of the BWP, that is, a quantity of RBs, to obtain values of RBstart and LRBs. The frequency domain resource assignment type <NUM> of NR does not support random assignment of resource blocks but only supports continuous frequency domain resource, thereby reducing a quantity of bits required by a transmission resource block to assign a related information field.

After determining a virtual RB assigned to the PDSCH, the UE further needs to determine a corresponding PRE resource based on a correspondence between a VRB and a physical resource block (physical RB, PRB). For example, when the UE is configured with downlink resource assignment of the type <NUM> and interleaved VRB-to-PRB mapping, the UE maps the VRB to the PRB according to a specific rule. If the UE is configured with downlink resource assignment of the type <NUM>, the UE does not support interleaved VRB-to-PRB mapping, but directly maps the VRB to the PRB.

When the UE is configured with downlink resource assignment of the type <NUM> and interleaved VRB-to-PRB mapping, a bit in the DCI for scheduling the PDSCH indicates whether the UE performs VRB-to-PRB mapping.

Further, in Long Term Evolution (Long Term Evolution, LTE) broadcast/multicast transmission, an MBMS single frequency network (Multimedia Broadcast multicast service Single Frequency Network, MB SFN) manner is supported to send a multimedia broadcast multicast service (Multimedia Broadcast Multicast Service, MBMS) service and a multicast service in a single-cell point-to-multipoint (Single-Cell Point-to-Multipoint, SC-PTM) manner. In the MBSFN manner, sending is performed in an MBSFN subframe by using a physical multicast channel (Physical Multicast Channel, PMCH). Control information is sent by using system information (for example, a SIB <NUM>) and a broadcast control channel (Multicast Control Channel, MCCH), and data is sent by using a broadcast traffic channel (Multicast Traffic Channel, MTCH). Both control information (a control channel parameter, a service channel parameter, scheduling information, and the like) and data information of an MBMS service are sent in a broadcast manner, so that idle-state UE and connected-state UE can receive the MBMS service, and the MBMS data information is sent only in an MBSFN subframe. SC-PTM is a multicast sending manner standardized after an MBMS service. A largest difference from the MBSFN manner is that scheduling and sending are performed only in a single cell, and service scheduling is performed by using a group radio network temporary identifier (group RNTI, g-RNTI). Sending is performed by using a PDSCH channel scheduled by using a PDCCH (Physical Downlink Control Channel, physical downlink control channel). Control information is sent by using system information (for example, a SIB <NUM>) and a single cell multicast control channel (Single Cell Multicast Control Channel, SC- MCCH), and data is sent by using a single cell multicast traffic channel (Single Cell Multicast Traffic Channel, SC-MTCH). The SC-MCCH is sent by using a PDSCH scheduled by a single cell RNTI (Single Cell RNTI, SC-RNTI) PDCCH, and the SC-MTCH is sent by using a PDSCH scheduled by a G-RNTI PDCCH (Group RNTI, group RNTI). In other words, an empty channel parameter, an identifier of a service, periodic information, and the like are broadcast in a broadcast message. Scheduling information is notified by a PDCCH scrambled by the g-RNTI, and a data part is sent in a multicast manner, which is equivalent to that UE of interest listens to the g-RNTI to obtain data scheduling and then perform receiving.

UE in LTE may receive multiple broadcast/multicast services together. In the MBSFN manner, different services may have different MBSFN configurations. The UE may distinguish different services by using MBSFNs. In the SC-PTM, different services use different g-RNTIs, and the UE may distinguish different services by using the g-RNTIs.

Currently, an NR technology has undergone evolution of two versions: Rel-<NUM> and Rel-<NUM>. In the two versions, a broadcast/multicast (broadcast/multicast) feature is not supported. However, there are many important use scenarios, such as public safety and mission critical (public safety and mission critical), V2X applications (V2X applications), transparent IPv4/IPv6 multicast delivery (transparent IPv4/IPv6 multicast delivery), IPTV, software delivery over wireless (software delivery over wireless), and group communication and Internet of Things applications (group communications and IoT applications). The broadcast/multicast feature can provide substantial improvement, especially in system efficiency and user experience. Therefore, in a next Rel-<NUM> release, a broadcast/multicast feature is to be introduced into the NR. Currently, there is no related solution to how to indicate or determine resource assignment of a multicast PDSCH. Based on this, an embodiment of the present invention provides a resource assignment method, which can resolve a problem of how to indicate or determine resource assignment of the multicast PDSCH.

A resource assignment method provided in embodiments of this application is described in detail below with reference to the accompanying drawings by using specific embodiments and application scenarios thereof.

As shown in <FIG>, an embodiment of this application provides a resource assignment method. The resource assignment method is applied to a terminal and includes:.

Step <NUM>: Determine a quantity of frequency domain resource assignment FDRA bits in multicast downlink control information DCI based on predefined information or a first quantity of resource blocks RBs.

In this embodiment of this application, for resource assignment of a type <NUM>, a quantity of bits in FDRA is related to a quantity of RBGs included in a BWP, and the quantity of RBGs is related to a quantity of RBs and an RBG size. DL resource assignment of a type <NUM> is related to a quantity of RBs included in the BWP. In other words, in the two types of resource assignment, the quantity of bits in FDRA is related to the quantity of RBs. Herein, the quantity of bits in FDRA in the multicast DCI may be determined by using the foregoing first quantity of RBs. The foregoing predefined information may be a predefined quantity of bits.

In this embodiment of this application, the quantity of bits in FDRA in the multicast DCI is determined, so that information corresponding to the quantity of bits in FDRA can be obtained, and further, frequency domain resource assignment of a PDSCH scheduled by the multicast DCI can be determined.

Step <NUM>: Determine, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI.

Resource assignment indicated by the FDRA is relative. For example, in a resource assignment type <NUM>, the FDRA indicates a start RB index and a quantity of consecutively assigned RBs, and in a resource assignment type <NUM>, each bit in a bitmap corresponds to one RBG. Therefore, a reference point assigned in the FDRA needs to be determined, that is, a position at which RBs start to be numbered and RBs corresponding to RBGs. In this embodiment of this application, RBs specifically indicated by the FDRA are determined by using a first RB, a second RB, a third RB, or a fourth RB.

The foregoing frequency domain resource may be a PRB or a VRB. Specifically, for the resource assignment type <NUM>, an RBG assigned to the multicast PDSCH is determined by using a bitmap of the FDRA of the quantity of bits, to determine a corresponding VRB and a corresponding PRB. For the resource assignment type <NUM>, a value RIV corresponding to the FDRA of the quantity of bits is obtained, and a VRB or PRB resource assigned to the multicast PDSCH is determined by using the RIV.

In the resource assignment method in this embodiment of this application, the quantity of FDRA bits in the multicast DCI is determined based on the predefined information or the first quantity of RBs, and the frequency domain resource assignment of the multicast PDSCH scheduled by the multicast DCI is determined based on the information corresponding to the FDRA of the quantity of bits, so that resource assignment of the multicast PDSCH is implemented.

Further, the determining a quantity of frequency domain resource assignment FDRA bits in multicast downlink control information DCI based on predefined information includes:
determining the quantity of FDRA bits by using a predefined quantity of bits.

In other words, in this embodiment of this application, the quantity of FDRA bits in the multicast DCI may be predefined.

Further, the first quantity of RBs is a predefined quantity of RBs.

Alternatively, the first quantity of RBs is a quantity of RBs corresponding to a target CORESET, and the target CORESET is a CORESET whose index number is <NUM>, or the target CORESET is a CORESET in which the multicast DCI is located. The quantity of RBs corresponding to the target CORESET may also be represented as a size of bandwidth corresponding to the target CORESET.

Alternatively, the first quantity of RBs is a quantity of RBs included in a carrier, or may be represented as a size of bandwidth corresponding to the carrier. Alternatively, the first quantity of RBs is a quantity of RBs included in a carrier corresponding to a special subcarrier spacing.

Alternatively, the first quantity of RBs is a quantity of RBs included in a target BWP, or may be represented as a size of bandwidth corresponding to the target BWP, and 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.

Further, in a first optional implementation, the determining, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI includes:.

Specifically, in a case that the first quantity of RBs is the BWP that is configured by the network side device and that is used for multicast PDSCH transmission, frequency domain resource assignment of the multicast PDSCH in a BWP configured by the network side device for multicast PDSCH transmission is determined. In other words, in a case that the target BWP is a BWP configured by the network side device for multicast PDSCH transmission, the quantity of FDRA bits is determined by using a quantity of RBs included in the BWP configured by the network side device for multicast PDSCH transmission.

In a case that the target BWP is an initial downlink BWP, the quantity of FDRA bits may be determined by using the predefined quantity of bits, a quantity of RBs included in the carrier, a quantity of RBs included in the initial downlink BWP, a quantity of RBs corresponding to a CORESET <NUM>, or a quantity of RBs corresponding to a CORESET in which the multicast DCI is located.

Herein, in a first optional implementation, the bit quantity in the FDRA is determined based on a size of the initial downlink BWP, and frequency domain resource assignment of the multicast PDSCH is determined based on the information corresponding to the FDRA of the quantity of bits and the first RB, where the first RB is an RB with a smallest number in initial downlink BWPs. Optionally, frequency domain resource assignment of the multicast PDSCH may include an RB other than the initial downlink BWP. Herein, a transmission parameter of the multicast PDSCH may also be configured or predefined, for example, a resource assignment type, VRB-to-PRB mapping, and an RBG size.

As shown in <FIG>, a base station configures, by using higher layer signaling, a BWP used for multicast PDSCH transmission, where the higher layer signaling may be a BWP for GPDSCH, may be common (common) signaling (for example, configured by using a SIB) or UE-specific signaling (for example, is configured by the base station for each UE that receives the multicast PDSCH). A configuration of the BWP may include a frequency domain location of the BWP and a subcarrier spacing (subcarrier space, SCS). Optionally, the base station may further configure parameters related to multicast PDSCH transmission, for example, configure a resource assignment type, VRB-to-PRB interleaving, and an RBG size by using a parameter gPDSCH-config. After receiving the multicast DCI, the UE determines, based on an FDRA indication in the DCI, the frequency domain resource assignment of the PDSCH scheduled by the DCI. The quantity of FDRA bits depends on a configuration of a BWP corresponding to the multicast PDSCH. The UE determines an assigned RB in the BWP corresponding to the multicast PDSCH, that is, RBs are numbered in the BWP corresponding to the multicast PDSCH.

Assuming that a frequency domain resource assignment type of the multicast PDSCH is a type <NUM>, RBs in the BWP corresponding to the multicast PDSCH are assigned as multiple RBGs, and each RBG group includes P consecutive virtual RBs. A value of P is configured or predefined by the base station. A total quantity of RBGs in bandwidth may be obtained by using bandwidth and P. The DCI indicates, by using a bitmap (bitmap) of the FDRA, an RBG assigned to a UE PDSCH, and a quantity of bits in the bitmap is NRBG. Each bit in the bitmap is in a one-to-one correspondence with each RBG. When a value of the bit is <NUM>, it indicates that an RBG corresponding to the bit is assigned to the UE.

Assuming that a frequency domain resource assignment type of the multicast PDSCH is a type <NUM>, the UE determines, based on the quantity of RBs in the BWP corresponding to the PDSCH, a start RB number RBstart indicated by the FDRA and a length LRBs of consecutively assigned VRBs, and RBs are assigned in the BWP corresponding to the PDSCH, that is, RBs start to be numbered from an RB with a smallest number in the BWP corresponding to the PDSCH. In addition, the first optional implementation may further include the following scenario: The first RB is an RB with a largest number in the target BWP, and the target BWP is an initial downlink BWP. In other words, the frequency domain resource assignment of the multicast PDSCH is determined based on an RB with a smallest number in the initial downlink BWP.

Further, in a second optional implementation, the determining, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI includes:.

In this implementation, for frequency resource assignment of the multicast PDSCH, RBs start to be numbered from a lowest RB in the target CORESET, and a physical resource assigned to the multicast PDSCH is determined by using VRB-to-PRB mapping. The UE determined an assigned VRB n according to an FDRA indication in the DCI. In VRB-to-PRB mapping, for multicast PDSCH transmission scheduled by the multicast DCI, the VRB n is mapped to a PRB m, where <MAT>, and <MAT> represents a corresponding PRB with a smallest number in the target CORESET, or is a PRB with a smallest number in an RB in which a PDCCH corresponding to the multicast DCI is located.

As shown in <FIG>, it is assumed that the target CORESET is a CORESET in which the multicast DCI is located. After receiving the multicast DCI, the UE determines, based on the FDRA in the DCI, the frequency domain resource assignment of the PDSCH scheduled by the DCI. It is assumed that a resource assignment type of the multicast PDSCH is the type <NUM>, and a value corresponding to the FDRA in the DCI is an RIV, which is used to indicate a number RBstart of a start RB assigned to the UE PDSCH and a length LRBs of consecutively assigned VRBs. A calculation formula of the RIV is the same as the foregoing calculation formula of the RIV. After receiving the DCI, the UE interprets the RIV in the DCI based on a size of the BWP, to obtain values of RBstart and LRBs. Herein, the size of the BWP, that is, the quantity of RBs, is determined based on any one of the following:.

In resource assignment of the multicast PDSCH, RBs start to be numbered from a lowest RB in a CORESET in which the multicast DCI is located; in other words, a number of the RB with the smallest number in a CORESET in which the DCI is located is <NUM>, and a value of RBstart represents an index of a start RB, that is, indicates that the start RB is an (RBstart)th RB that starts to be numbered from the lowest RB in the CORESET in which the DCI is located. A value of LRBs indicates a quantity of RBs consecutively assigned from the start RB.

Alternatively, as shown in <FIG>, in resource assignment of the multicast PDSCH, RBs start to be numbered from a lowest RB in a PDCCH in which the DCI is located; in other words, a number of the RB with the smallest number in the PDCCH corresponding to the DCI is <NUM>, and a value of RBstart represents an index of a start RB, that is, indicates that the start RB is an (RBstart)th RB that starts to be numbered from a lowest RB in an RB in which the PDCCH corresponding to the DCI is located. A value of LRBs indicates a quantity of RBs consecutively assigned from the start RB.

Optionally, in this implementation, a resource assignment type of the multicast PDSCH, VRB-to-PRB mapping, an RBG size, and the like may be predefined or configured by using higher layer signaling. For example, the PDSCH scheduled by the multicast DCI only supports resource assignment of the type <NUM>, and does not support interleaved VRB-to-PRB mapping.

Optionally, in this implementation, the terminal determines the quantity of FDRA bits based on the quantity of RBs included in the bandwidth of the carrier, the quantity of RBs included in the initial downlink bandwidth, the quantity of RBs corresponding to the CORESET <NUM>, the predefined quantity of bits, or the quantity of RBs corresponding to the CORESET in which the multicast DCI is located.

Further, in a third optional implementation, the determining, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI includes:.

As shown in <FIG>, after receiving the multicast DCI, the UE determines, according to an FDRA indication in the DCI, the frequency domain resource assignment of the PDSCH scheduled by the DCI. It is assumed that a resource assignment type of the multicast PDSCH is the type <NUM>, and a value corresponding to the FDRA in the DCI is an RIV, which is used to indicate a number RBstart of a start RB assigned to the UE PDSCH and a length LRBs of consecutively assigned VRBs. A calculation formula of the RIV is the same as the foregoing calculation formula of the RIV. After receiving the DCI, the UE interprets the RIV in the DCI based on a size of the BWP, to obtain values of RBstart and LRBs. Herein, a size of the BWP may be determined based on a bandwidth size of a carrier, a carrier bandwidth size corresponding to a special subcarrier spacing, a size of an initial downlink BWP, or the like.

In resource assignment of the multicast PDSCH, RBs start to be numbered from a lowest RB (point A) of a carrier (carrier), in other words, a number of the lower RB in the carrier is <NUM>. If a value of RBstart, it indicates that the start RB is an (RBstart)th RB that starts to be numbered from the lowest RB in the carrier. A value of LRBs indicates a quantity of RBs consecutively assigned from the start RB.

Optionally, in this method, for each UE that receives the multicast PDSCH, a PRB assigned by the multicast PDSCH should be included in an active downlink BWP (active DL BWP) of the UE; in other words, the UE does not expect any PRB assigned by the multicast PDSCH to be outside an active BWP of the UE.

Further, in a fourth optional implementation, the determining, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI includes:
determining frequency domain resource assignment of the multicast PDSCH in a carrier based on the information corresponding to the FDRA of the quantity of bits and a fourth RB; where.

The fourth RB is configured by a base station. For example, the base station configures that the fourth RB is a common RB <NUM> (common RB <NUM>), or is an RB with a lowest number in an initial BWP, or is an RB with a smallest number in a CORSET in which DCI is located. Further, before the determining, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI, the method further includes:.

Herein, a resource assignment type may be the type <NUM>, the type <NUM>, or a dynamically indicated type <NUM> or type <NUM>.

Further, before the determining, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI, the method further includes:.

Specifically, in a case that the resource assignment type is the type <NUM>, an RBG size is obtained.

In addition, in this embodiment of this application, time domain resource assignment is described as follows:
For a PDSCH scheduled by DCI scrambled by a g-RNTI, a time domain resource assignment TDRA value m indicates an (m+<NUM>)th row in a corresponding resource assignment table, where the corresponding resource assignment table is a predefined table or a table configured by using higher layer signaling, and the higher layer signaling may be common or UE-specific, for example, is configured by using a SIB or is UE-specific (for example, is configured by the base station for each UE that receives the multicast PDSCH). For example, a PDSCH time domain allocation table (pdsch-Time Domain Allocation List) is configured by using a parameter gPDSCH-config.

In the resource assignment method in this embodiment of this application, the quantity of FDRA bits in the multicast DCI is determined based on the predefined information or the first quantity of RBs, and the frequency domain resource assignment of the multicast PDSCH scheduled by the multicast DCI is determined based on the information corresponding to the FDRA of the quantity of bits, so that resource assignment of the multicast PDSCH is implemented, and validity of a communication system is improved.

As shown in <FIG>, an embodiment of this application further provides a resource assignment method. The resource assignment method is applied to a network side device and includes:.

Step <NUM>: Determine a quantity of bits of frequency domain resource assignment FDRA in multicast downlink control information DCI based on predefined information or a first quantity of resource blocks RBs.

In this embodiment of this application, for resource assignment of a type <NUM>, a quantity of bits in FDRA is related to a quantity of RBGs included in a BWP, and the quantity of RBGs is related to a quantity of RBs and an RBG size. DL resource assignment of a type <NUM> is related to a quantity of RBs included in the BWP. In other words, in the two types of resource assignment, the quantity of bits in FDRA is related to the quantity of RBs. Herein, the quantity of bits in FDRA in the multicast DCI may be indicated by using the foregoing first quantity of RBs. The foregoing predefined information may be a predefined quantity of bits.

In this embodiment of this application, the quantity of bits in FDRA in the multicast DCI is indicated, so that a terminal can obtain information corresponding to the quantity of bits in FDRA, and further, frequency domain resource assignment of a PDSCH scheduled by the multicast DCI can be determined.

Step <NUM>: Indicate, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI.

The foregoing frequency domain resource may be a PRB or a VRB. Specifically, for a resource assignment type <NUM>, an RBG assigned to the multicast PDSCH is indicated by using a bitmap of the FDRA of the quantity of bits. For a resource assignment type <NUM>, a VRB or PRB resource assigned to the multicast PDSCH is determined by using a value RIV corresponding to the FDRA of the quantity of bits.

In the resource assignment method in this embodiment of this application, the quantity of FDRA bits in the multicast DCI is indicated based on the predefined information or the first quantity of RBs, and the frequency domain resource assignment of the multicast PDSCH scheduled by the multicast DCI is indicated based on the information corresponding to the FDRA of the quantity of bits, so that resource assignment of the multicast PDSCH is implemented.

Further, the indicating a quantity of frequency domain resource assignment FDRA bits in multicast downlink control information DCI based on predefined information includes:
determining the quantity of FDRA bits by using a predefined quantity of bits.

Alternatively, the first quantity of RBs is a quantity of RBs included in a carrier, or may be represented as a size of bandwidth corresponding to the carrier.

Further, the indicating, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI includes:.

Further, the method further includes:
indicating a resource assignment type through predefining or by using higher layer signaling.

Further, the method further includes:
indicating a resource block group RBG size through predefining or by using higher layer signaling.

It should be noted that the resource assignment method applied to the network side device is a method corresponding to the foregoing resource assignment method applied to a terminal side, and details are not described herein again.

In the resource assignment method in this embodiment of this application, the quantity of FDRA bits in the multicast DCI is determined based on the predefined information or the first quantity of RBs, and the frequency domain resource assignment of the multicast PDSCH scheduled by the multicast DCI is indicated based on the information corresponding to the FDRA of the quantity of bits, so that resource assignment of the multicast PDSCH is implemented.

It should be noted that, the resource assignment method provided in this embodiment of this application may be performed by a resource assignment apparatus or a control module that is in the resource assignment apparatus and that is configured to perform the resource assignment method. In the embodiments of this application, the resource assignment apparatus provided in the embodiments of this application is described by using an example in which the resource assignment apparatus performs the resource assignment method.

As shown in <FIG>, an embodiment of this application further provides a resource assignment apparatus <NUM>. The resource assignment apparatus is applied to a terminal and includes:.

In the resource assignment apparatus in this embodiment of this application, the first determining module is configured to determine the quantity of FDRA bits by using a predefined quantity of bits.

In the resource assignment apparatus in this embodiment of this application, the first quantity of RBs is a predefined quantity of RBs; or.

In the resource assignment apparatus in this embodiment of this application, the second determining module is configured to determine frequency domain resource assignment of the multicast PDSCH in a target BWP based on information corresponding to FDRA of the quantity of bits and a first RB; where
the first RB is an RB with a smallest number in the target BWP, and 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.

In the resource assignment apparatus in this embodiment of this application, the second determining module is configured to determine frequency domain resource assignment of the multicast PDSCH based on information corresponding to FDRA of the quantity of bits and a second RB; where
the second RB is an RB with a smallest number in RBs corresponding to a target CORESET, and the target CORESET is a CORESET whose index number is <NUM>, or the target CORESET is a CORESET in which the multicast DCI is located.

In the resource assignment apparatus in this embodiment of this application, the second determining module is configured to determine frequency domain resource assignment of the multicast PDSCH in a carrier based on information corresponding to FDRA of the quantity of bits and a third RB; where
the third RB is an RB with a smallest number in the carrier.

The resource assignment apparatus in this embodiment of this application further includes:
a first obtaining module, configured to: before the second determining module determines, based on the information corresponding to the FDRA of the quantity of bits, the frequency domain resource assignment of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI, obtain a predefined resource assignment type or obtain a resource assignment type by using higher layer signaling.

The resource assignment apparatus in this embodiment of this application further includes:
a second obtaining module, configured to: before the second determining module determines, based on the information corresponding to the FDRA of the quantity of bits, the frequency domain resource assignment of the multicast physical downlink shared channel PDSCH scheduled by the multicast DCI, obtain a predefined resource block group RBG size or obtain an RBG size by using higher layer signaling.

In the resource assignment apparatus in this embodiment of this application, the quantity of FDRA bits in the multicast DCI is determined based on the predefined information or the first quantity of RBs, and the frequency domain resource assignment of the multicast PDSCH scheduled by the multicast DCI is determined based on the information corresponding to the FDRA of the quantity of bits, so that resource assignment of the multicast PDSCH is implemented.

The resource assignment apparatus in this embodiment of this application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal. The apparatus may be a mobile terminal, or may be a non-mobile terminal. For example, the mobile terminal may include but is not limited to the foregoing listed types of terminals <NUM>. 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. This is not specifically limited in this embodiment of this application.

The resource assignment apparatus in this embodiment of this application may be an apparatus with an operating system. The operating system may be an Android (Android) operating system, may be an iOS operating system, or may be another possible operating system. This is not specifically limited in this embodiment of this application.

The resource assignment apparatus provided in this embodiment of this application can implement processes implemented in the method embodiments of <FIG>, and a same technical effect is achieved. To avoid repetition, details are not described herein again.

Optionally, as shown in <FIG>, an embodiment of this application further provides a communication device <NUM>, including a processor <NUM>, a memory <NUM>, a program or an instruction that is stored in the memory <NUM> and that can run on the processor <NUM>. For example, when the communication device <NUM> is a terminal, the program or the instruction is executed by the processor <NUM> to implement processes of the embodiment of the foregoing resource assignment method applied to the terminal, and a same technical effect can be achieved. When the communication device <NUM> is a network side device, when the program or the instruction is executed by the processor <NUM>, processes of the embodiment of the foregoing resource assignment method applied to the network side device are implemented, and a same technical effect can be achieved. To avoid repetition, details are not described herein again.

<FIG> is a schematic diagram of a hardware structure of a terminal according to an embodiment of this application.

The terminal <NUM> includes but is not limited to components such as a radio frequency unit <NUM>, a network module <NUM>, an audio output unit <NUM>, an input unit <NUM>, a sensor <NUM>, a display unit <NUM>, a user input unit <NUM>, an interface unit <NUM>, a memory <NUM>, and a processor <NUM>.

It may be understood by a person skilled in the art that the terminal <NUM> may further include a power supply (such as a battery) that supplies power to each component. The power supply may be logically connected to the processor <NUM> by using a power management system, to implement functions such as charging, discharging, and power consumption management by using the power management system. A structure of the terminal shown in <FIG> does not constitute a limitation on the terminal device, and may include more or fewer parts than those shown in the figure, or combine some parts, or have different part arrangements.

It should be understood that, in this embodiment of this application, the input unit <NUM> may include a graphics processing unit (Graphics Processing Unit, GPU) <NUM> and a microphone <NUM>. The graphics processing unit <NUM> processes image data of a static picture or a video obtained by an image capture apparatus (such as a camera) in a video capture mode or an image capture mode. The display unit <NUM> may include a display panel <NUM>, and the display panel <NUM> may be configured in a form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit <NUM> includes a touch panel <NUM> and another input device <NUM>. The touch panel <NUM> is also referred to as a touchscreen. The touch panel <NUM> may include two parts: a touch detection apparatus and a touch controller. The another input device <NUM> may include but is not limited to one or more of a physical keyboard, a function key (such as a volume control key or an on/off key), a trackball, a mouse, a joystick, and the like.

In this embodiment of this application, after receiving downlink data from a network side device, the radio frequency unit <NUM> sends the downlink data to the processor <NUM> for processing, and sends uplink data to the network side device. Generally, the radio frequency unit <NUM> includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory <NUM> may be configured to store a software program or an instruction and various data. The memory <NUM> may mainly include a storage program or instruction area and a storage data area, where the storage program or instruction area may store an operating system, an application program or an instruction required by at least one function (such as a sound play function or an image play function), and the like. In addition, the memory <NUM> may include a high-speed random access memory, and may further include a non-volatile memory. The non-volatile memory may 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 magnetic disk storage device, a flash memory device, or another non-volatile solid-state storage device.

The processor <NUM> may include one or more processing units. Optionally, the processor <NUM> may be integrated with an application processor and a modem processor. The application processor mainly processes an operating system, a user interface, an application program or an instruction, and the like, and the modem processor mainly processes wireless communication, for example, a baseband processor. It may be understood that the modem processor may also not be integrated into the processor <NUM>.

The processor <NUM> is configured to: determine a quantity of frequency domain resource assignment FDRA bits in multicast downlink control information DCI based on predefined information or a first quantity of resource blocks RBs; and
determine, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel PDSCH scheduled by the multicast DCI.

In the terminal in this embodiment of this application, the quantity of FDRA bits in the multicast DCI is determined based on the predefined information or the first quantity of RBs, and the frequency domain resource assignment of the multicast PDSCH scheduled by the multicast DCI is determined based on the information corresponding to the FDRA of the quantity of bits, so that resource assignment of the multicast PDSCH is implemented.

Optionally, the processor <NUM> is further configured to determine the quantity of FDRA bits by using a predefined quantity of bits.

Optionally, the first quantity of RBs is a predefined quantity of RBs; or.

Optionally, the processor <NUM> is further configured to determine frequency domain resource assignment of the multicast PDSCH in a target BWP based on the information corresponding to the FDRA of the quantity of bits and a first RB; where
the first RB is an RB with a smallest number in the target BWP, and 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.

Optionally, the processor <NUM> is further configured to determine frequency domain resource assignment of the multicast PDSCH based on the information corresponding to the FDRA of the quantity of bits and a second RB; where
the second RB is an RB with a smallest number in RBs corresponding to a target CORESET, and the target CORESET is a CORESET whose index number is <NUM>, or the target CORESET is a CORESET in which the multicast DCI is located.

Optionally, the processor <NUM> is further configured to determine frequency domain resource assignment of the multicast PDSCH in a carrier based on the information corresponding to the FDRA of the quantity of bits and a third RB; where
the third RB is an RB with a smallest number in the carrier.

Optionally, the processor <NUM> is further configured to obtain a predefined resource assignment type; or
obtain a resource assignment type by using higher layer signaling.

Optionally, the processor <NUM> is further configured to obtain a predefined resource block group RBG size, or obtain an RBG size by using higher layer signaling.

As shown in <FIG>, an embodiment of this application further provides a resource assignment apparatus <NUM>. The resource assignment apparatus is applied to a network side device and includes:.

In the resource assignment apparatus in this embodiment of this application, the third determining module is configured to determine the quantity of FDRA bits by using a predefined quantity of bits.

In the resource assignment apparatus in this embodiment of this application, the indication module is configured to indicate frequency domain resource assignment of the multicast PDSCH in a target BWP based on information corresponding to FDRA of the quantity of bits and a first RB; where
the first RB is an RB with a smallest number in the target BWP, and 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.

In the resource assignment apparatus in this embodiment of this application, the indication module is configured to indicate frequency domain resource assignment of the multicast PDSCH based on information corresponding to FDRA of the quantity of bits and a second RB; where
the second RB is an RB with a smallest number in RBs corresponding to a target CORESET, and the target CORESET is a CORESET whose index number is <NUM>, or the target CORESET is a CORESET in which the multicast DCI is located.

In the resource assignment apparatus in this embodiment of this application, the indication module is configured to indicate frequency domain resource assignment of the multicast PDSCH in a carrier based on information corresponding to FDRA of the quantity of bits and a third RB; where
the third RB is an RB with a smallest number in the carrier.

The resource assignment apparatus in this embodiment of this application further includes:
a third indication module, configured to indicate a resource assignment type through predefining or by using higher layer signaling.

The resource assignment apparatus in this embodiment of this application further includes:
a third indication module, configured to indicate a type of a resource block group RBG through predefining or by using higher layer signaling.

The resource assignment apparatus provided in this embodiment of this application can implement processes implemented in the embodiment of the resource assignment method, and a same technical effect is achieved. To avoid repetition, details are not described herein again.

In the resource assignment apparatus in this embodiment of this application, the quantity of FDRA bits in the multicast DCI is determined based on the predefined information or the first quantity of RBs, and the frequency domain resource assignment of the multicast PDSCH scheduled by the multicast DCI is indicated based on the information corresponding to the FDRA of the quantity of bits, so that resource assignment of the multicast PDSCH is implemented.

Specifically, an embodiment of this application further provides a network side device. As shown in <FIG>, the network side device <NUM> includes an antenna <NUM>, a radio frequency apparatus <NUM>, and a baseband apparatus <NUM>. The antenna <NUM> is connected to the radio frequency apparatus <NUM>. In an uplink direction, the radio frequency apparatus <NUM> receives information by using the antenna <NUM>, and sends the received information to the baseband apparatus <NUM> for processing. In a downlink direction, the baseband apparatus <NUM> processes to-be-sent information, and sends the to-be-sent information to the radio frequency apparatus <NUM>. After processing the received information, the radio frequency apparatus <NUM> sends the information by using the antenna <NUM>.

The foregoing band processing apparatus may be located in the baseband apparatus <NUM>. In the foregoing embodiment, a method performed by the network side device may be implemented in the baseband apparatus <NUM>. The baseband apparatus <NUM> includes a processor <NUM> and a memory <NUM>.

For example, the baseband apparatus <NUM> may include at least one baseband board. Multiple chips are disposed on the baseband board. As shown in <FIG>, one chip is, for example, the processor <NUM>, and is connected to the memory <NUM>, to invoke a program in the memory <NUM> to perform an operation of the network side device shown in the foregoing method embodiment.

The baseband apparatus <NUM> may further include a network interface <NUM>, configured to exchange information with the radio frequency apparatus <NUM>, where the interface is, for example, a common public radio interface (common public radio interface, CPRI for short).

Specifically, the network side device in this embodiment of the present invention further includes an instruction or a program that is stored in the memory <NUM> and that can run on the processor <NUM>. The processor <NUM> invokes the instruction or the program in the memory <NUM> to perform the method performed by the modules shown in <FIG>, and a same technical effect is achieved. To avoid repetition, details are not described herein.

An embodiment of this application further provides a readable storage medium. A program or an instruction is stored in the readable storage medium. When the program or the instruction is executed by a processor, the processes of the embodiments of the foregoing resource assignment method can be implemented, and a same technical effect can be achieved. To avoid repetition, details are not described herein.

The processor is a processor in the terminal in the foregoing embodiment. The readable storage medium includes a computer-readable storage medium such as a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, an optical disc, or the like.

An embodiment of this application further provides a chip. The chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction of a network side device to implement the processes of the embodiments of the foregoing resource assignment method, and a same technical effect can be achieved. To avoid repetition, details are not described herein again.

It should be understood that the chip mentioned in this embodiment of this application may also be referred to as a system-level chip, a system chip, a chip system, or a system on a chip.

It should be noted that in this specification, the term "include", "including", or any other variant is intended to cover non-exclusive inclusion, so that a process, method, article, or apparatus that includes a series of elements includes not only those elements but also other elements that are not explicitly listed, or includes elements inherent to such a process, method, article, or apparatus. In the absence of more restrictions, an element defined by the statement "including a. " does not exclude another same element in a process, method, article, or apparatus that includes the element. In addition, it should be noted that a scope of the method and the apparatus in the embodiments of this application is not limited to: performing a function in a sequence shown or discussed, and may further include: performing a function in a basically simultaneous manner or in a reverse sequence based on an involved function. For example, the described method may be performed in a different order, and various steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.

Claim 1:
A resource assignment method performed by a terminal, comprising:
determining a quantity of frequency domain resource assignment, FDRA, bits in multicast downlink control information, DCI based on a first quantity of resource blocks, RBs (<NUM>); and
determining, based on information corresponding to FDRA of the quantity of bits, frequency domain resource assignment of a multicast physical downlink shared channel, PDSCH scheduled by the multicast DCI (<NUM>); characterized in that,
the first quantity of RBs is a quantity of RBs corresponding to a target CORESET and the target CORESET is a CORESET whose index number is <NUM>, or the target CORESET is a CORESET in which the multicast DCI is located; or
the first quantity of RBs is a quantity of RBs comprised in an initial downlink BWP; or
the first quantity of RBs is a quantity of RBs comprised in a BWP configured by a network side device for multicast PDSCH transmission.