CN117460053A - Frequency domain resource allocation method, device and storage medium - Google Patents

Frequency domain resource allocation method, device and storage medium Download PDF

Info

Publication number
CN117460053A
CN117460053A CN202210837761.7A CN202210837761A CN117460053A CN 117460053 A CN117460053 A CN 117460053A CN 202210837761 A CN202210837761 A CN 202210837761A CN 117460053 A CN117460053 A CN 117460053A
Authority
CN
China
Prior art keywords
resource allocation
shared channel
waveform
physical uplink
uplink shared
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210837761.7A
Other languages
Chinese (zh)
Inventor
邢艳萍
沈姝伶
司倩倩
高雪娟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
Datang Mobile Communications Equipment Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Datang Mobile Communications Equipment Co Ltd filed Critical Datang Mobile Communications Equipment Co Ltd
Priority to CN202210837761.7A priority Critical patent/CN117460053A/en
Priority to PCT/CN2023/104635 priority patent/WO2024012262A1/en
Publication of CN117460053A publication Critical patent/CN117460053A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453Resources in frequency domain, e.g. a carrier in FDMA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/53Allocation or scheduling criteria for wireless resources based on regulatory allocation policies

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The embodiment of the application provides a frequency domain resource allocation method, a device and a storage medium, wherein the method comprises the following steps: determining the waveform of a physical uplink shared channel; and determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform. According to the frequency domain resource allocation method, the device and the storage medium, when the uplink waveform is dynamically changed, the terminal determines the waveform of the PUSCH, determines the frequency domain resource allocation of the PUSCH according to the waveform of the PUSCH, and supports the dynamic determination of the resource allocation type according to the waveform, so that the situation that the configuration is limited or the redundancy is indicated when the dynamic waveform is switched is solved.

Description

Frequency domain resource allocation method, device and storage medium
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method and apparatus for allocating frequency domain resources, and a storage medium.
Background
The new air interface (NR) uplink supports two waveforms, cyclic prefix orthogonal frequency division multiplexing (Cyclic Prefix Orthogonal Frequency Division Multiplexing, CP-OFDM) and discrete fourier transform spread orthogonal frequency division multiplexing (Discrete Fourier Transform spread Orthogonal Frequency Division Multiplexing, DFT-s-OFDM), respectively. For a particular physical uplink shared channel (Physical Uplink Shared Channel, PUSCH), the uplink waveform used is semi-statically configured.
The NR uplink supports two resource allocation types, namely a resource allocation type 0 and a resource allocation type 1.CP-OFDM may use resource allocation type 0 and resource allocation type 1, whereas DFT-s-OFDM may only use resource allocation type 1.
At present, under dynamic waveform switching, the resource allocation type 0 is not suitable for the DFT-s-OFDM waveform, and the problems of configuration limitation or indication redundancy can be brought.
Disclosure of Invention
The embodiment of the application provides a frequency domain resource allocation method, a frequency domain resource allocation device and a storage medium, which are used for solving the defect that the configuration is limited or the redundancy is indicated when a dynamic waveform is switched, realizing the dynamic determination of the resource allocation type according to the waveform, and solving the problem that the configuration is limited or the redundancy is indicated when the dynamic waveform is switched.
In a first aspect, an embodiment of the present application provides a frequency domain resource allocation method, which is applied to a terminal, and includes:
determining the waveform of a physical uplink shared channel;
and determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform.
In some embodiments, the determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform includes:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
Determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0;
wherein the resource block groups allocated to the physical uplink shared channel according to the resource allocation type 0 are contiguous in the frequency domain.
In some embodiments, after determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0, the method further includes:
determining a target number under the condition that the total number of the resource blocks in the resource block group set does not meet a preset condition; the target number is the maximum value meeting the preset condition, and the target number is smaller than the total number;
the target number is the number of resource blocks allocated to the physical uplink shared channel;
the preset conditions are as follows:
wherein,alpha is the number of resource blocks 2 ,α 3 ,α 5 Is a non-negative integer.
In some embodiments, the target number of resource blocks is the lowest or highest frequency target number of resource blocks in the set of resource block groups.
In some embodiments, the determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform includes:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is a resource allocation type 1;
Determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 1;
under the condition that the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
and determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0.
In some embodiments, the determining the waveform of the physical uplink shared channel includes:
receiving downlink control information for scheduling or activating the physical uplink shared channel;
and determining the waveform of the physical uplink shared channel based on the downlink control information.
In some embodiments, the determining the waveform of the physical uplink shared channel based on the downlink control information includes:
and determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information.
In some embodiments, the determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information includes:
and determining the waveform of the physical uplink shared channel based on the most significant bit of the frequency domain resource allocation domain in the downlink control information.
In some embodiments, the determining the waveform of the physical uplink shared channel based on the downlink control information includes:
and determining the waveform of the physical uplink shared channel based on the domains except the frequency domain resource allocation domain in the downlink control information.
In some embodiments, the determining the waveform of the physical uplink shared channel includes:
receiving a MAC-CE message;
and determining the waveform of the physical uplink shared channel based on the indication of the MAC-CE message.
In some embodiments, further comprising:
and determining the frequency domain resource allocation of the physical uplink shared channel based on a high order zero padding or low order bit mode under the condition that the bit number of the frequency domain resource allocation domain in the downlink control information is inconsistent with the bit number of the frequency domain resource allocation domain determined based on the resource allocation type.
In some embodiments, further comprising:
and determining the waveform of the physical uplink shared channel based on the frequency resource allocation domain in the downlink control information, wherein the bit number of the frequency resource allocation domain in the downlink control information does not comprise bits for indicating the waveform of the physical uplink shared channel.
In a second aspect, an embodiment of the present application provides a method for allocating frequency domain resources, which is applied to a network device, and includes:
Transmitting indication information;
the indication information is used for determining a waveform of a physical uplink shared channel, and the waveform is used for determining frequency domain resource allocation of the physical uplink shared channel.
In some embodiments, the sending the indication information includes:
transmitting downlink control information for scheduling or activating the physical uplink shared channel; the downlink control information is used for determining the waveform of the physical uplink shared channel.
In some embodiments, the sending the indication information includes:
transmitting a MAC-CE message; the MAC-CE message is used to determine a waveform of the physical uplink shared channel.
In a third aspect, embodiments of the present application further provide a terminal, including a memory, a transceiver, and a processor:
a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:
determining the waveform of a physical uplink shared channel;
and determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform.
In some embodiments, the determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform includes:
Under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0;
wherein the resource block groups allocated to the physical uplink shared channel according to the resource allocation type 0 are contiguous in the frequency domain.
In some embodiments, after determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0, the method further includes:
determining a target number under the condition that the total number of the resource blocks in the resource block group set does not meet a preset condition; the target number is the maximum value meeting the preset condition, and the target number is smaller than the total number;
the target number is the number of resource blocks allocated to the physical uplink shared channel;
the preset conditions are as follows:
wherein,alpha is the number of resource blocks 2 ,α 3 ,α 5 Is a non-negative integer.
In some embodiments, the target number of resource blocks is the lowest or highest frequency target number of resource blocks in the set of resource block groups.
In some embodiments, the determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform includes:
Under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is a resource allocation type 1;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 1;
under the condition that the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
and determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0.
In some embodiments, the determining the waveform of the physical uplink shared channel includes:
receiving downlink control information for scheduling or activating the physical uplink shared channel;
and determining the waveform of the physical uplink shared channel based on the downlink control information.
In some embodiments, the determining the waveform of the physical uplink shared channel based on the downlink control information includes:
and determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information.
In some embodiments, the determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information includes:
And determining the waveform of the physical uplink shared channel based on the most significant bit of the frequency domain resource allocation domain in the downlink control information.
In some embodiments, the determining the waveform of the physical uplink shared channel based on the downlink control information includes:
and determining the waveform of the physical uplink shared channel based on the domains except the frequency domain resource allocation domain in the downlink control information.
In some embodiments, the determining the waveform of the physical uplink shared channel includes:
receiving a MAC-CE message;
and determining the waveform of the physical uplink shared channel based on the indication of the MAC-CE message.
In some embodiments, further comprising:
and determining the frequency domain resource allocation of the physical uplink shared channel based on a high order zero padding or low order bit mode under the condition that the bit number of the frequency domain resource allocation domain in the downlink control information is inconsistent with the bit number of the frequency domain resource allocation domain determined based on the resource allocation type.
In some embodiments, further comprising:
and determining the waveform of the physical uplink shared channel based on the frequency resource allocation domain in the downlink control information, wherein the bit number of the frequency resource allocation domain in the downlink control information does not comprise bits for indicating the waveform of the physical uplink shared channel.
In a fourth aspect, embodiments of the present application further provide a network device, including a memory, a transceiver, and a processor:
a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:
transmitting indication information;
the indication information is used for determining a waveform of a physical uplink shared channel, and the waveform is used for determining frequency domain resource allocation of the physical uplink shared channel.
In some embodiments, the sending the indication information includes:
transmitting downlink control information for scheduling or activating the physical uplink shared channel; the downlink control information is used for determining the waveform of the physical uplink shared channel.
In some embodiments, the sending the indication information includes:
transmitting a MAC-CE message; the MAC-CE message is used to determine a waveform of the physical uplink shared channel.
In a fifth aspect, embodiments of the present application further provide a frequency domain resource allocation apparatus, including:
the determining module is used for determining the waveform of the physical uplink shared channel;
and the allocation module is used for determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform.
Optionally, the allocation module is specifically configured to:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0;
wherein the resource block groups allocated to the physical uplink shared channel according to the resource allocation type 0 are contiguous in the frequency domain.
Optionally, the frequency domain resource allocation device further includes:
a second determining module, configured to determine a target number if the total number of resource blocks in the resource block group set does not meet a preset condition; the target number is the maximum value meeting the preset condition, and the target number is smaller than the total number;
the target number is the number of resource blocks allocated to the physical uplink shared channel;
the preset conditions are as follows:
wherein,alpha is the number of resource blocks 2 ,α 3 ,α 5 Is a non-negative integer.
Optionally, the target number of resource blocks is the lowest or highest frequency target number of resource blocks in the set of resource blocks.
Optionally, the allocation module is specifically configured to:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is a resource allocation type 1;
Determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 1;
under the condition that the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
and determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0.
Optionally, the determining module is specifically configured to:
receiving downlink control information for scheduling or activating the physical uplink shared channel;
and determining the waveform of the physical uplink shared channel based on the downlink control information.
Optionally, the frequency domain resource allocation device further includes:
and a third determining module, configured to determine a waveform of the physical uplink shared channel based on a frequency domain resource allocation domain in the downlink control information.
Optionally, the frequency domain resource allocation device further includes:
and a fourth determining module, configured to determine a waveform of the physical uplink shared channel based on a most significant bit of a frequency domain resource allocation domain in the downlink control information.
Optionally, the frequency domain resource allocation device further includes:
and a fifth determining module, configured to determine a waveform of the physical uplink shared channel based on a domain other than the frequency domain resource allocation domain in the downlink control information.
Optionally, the determining module is further specifically configured to:
receiving a MAC-CE message;
and determining the waveform of the physical uplink shared channel based on the indication of the MAC-CE message.
Optionally, in the case that the number of bits in the frequency domain resource allocation domain in the downlink control information is inconsistent with the number of bits in the frequency domain resource allocation domain determined based on the resource allocation type, determining the frequency domain resource allocation of the physical uplink shared channel based on a high order zero padding or low order bit.
Optionally, in the case of determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information, the number of bits in the frequency domain resource allocation domain in the downlink control information does not include bits for indicating the waveform of the physical uplink shared channel.
In a sixth aspect, embodiments of the present application further provide a frequency domain resource allocation apparatus, including:
the sending module is used for sending the indication information;
the indication information is used for determining a waveform of a physical uplink shared channel, and the waveform is used for determining frequency domain resource allocation of the physical uplink shared channel.
Optionally, the sending module is specifically configured to:
transmitting downlink control information for scheduling or activating the physical uplink shared channel; the downlink control information is used for determining the waveform of the physical uplink shared channel.
Optionally, the sending module is specifically configured to:
transmitting a MAC-CE message; the MAC-CE message is used to determine a waveform of the physical uplink shared channel.
In a seventh aspect, embodiments of the present application further provide a processor-readable storage medium storing a computer program for causing the processor to perform the frequency domain resource allocation method according to the first or second aspect as described above.
In an eighth aspect, embodiments of the present application further provide a computer readable storage medium storing a computer program for causing a computer to execute the frequency domain resource allocation method according to the first aspect or the second aspect.
In a ninth aspect, embodiments of the present application further provide a communication device readable storage medium, where the communication device readable storage medium stores a computer program for causing a communication device to perform the frequency domain resource allocation method according to the first aspect or the second aspect.
In a tenth aspect, embodiments of the present application further provide a chip product readable storage medium storing a computer program for causing a chip product to perform the frequency domain resource allocation method according to the first aspect or the second aspect as described above.
According to the frequency domain resource allocation method, the frequency domain resource allocation device and the storage medium, when the uplink waveform dynamically changes, the terminal determines the waveform of the PUSCH, determines the frequency domain resource allocation of the PUSCH according to the waveform of the PUSCH, and supports the dynamic determination of the resource allocation type according to the waveform, so that the situation that the configuration is limited or the redundancy is indicated when the dynamic waveform is switched is solved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief description will be given below of the drawings that are needed in the embodiments or the prior art descriptions, and it is obvious that the drawings in the following description are some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of a frequency domain resource allocation method according to an embodiment of the present application;
fig. 2 is a second flowchart of a frequency domain resource allocation method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a terminal provided in an embodiment of the present application;
fig. 4 is a schematic structural diagram of a network device according to an embodiment of the present application;
Fig. 5 is one of schematic structural diagrams of a frequency domain resource allocation apparatus according to an embodiment of the present application;
fig. 6 is a second schematic structural diagram of a frequency domain resource allocation device according to an embodiment of the present application.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In order to clearly describe the technical solutions of the embodiments of the present application, in each embodiment of the present application, if "first," "second," and the like words are used to distinguish identical items or similar items having substantially identical functions and actions, those skilled in the art will understand that the "first," "second," and the like words do not limit the number and execution order.
In the embodiment of the application, the term "and/or" describes the association relationship of the association objects, which means that three relationships may exist, for example, a and/or B may be represented: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
The term "plurality" in the embodiments of the present application means two or more, and other adjectives are similar thereto.
The NR uplink supports two waveforms, CP-OFDM and DFT-s-OFDM, respectively. For a particular PUSCH, the uplink waveform used is semi-statically configured.
The NR uplink supports two resource allocation types, namely a resource allocation type 0 and a resource allocation type 1. Wherein, the resource allocation type 0 takes the resource block group (Resource Block Group, RBG) as a unit to allocate resources, which can support continuous resource allocation and discontinuous resource allocation; the Resource allocation type 1 can only support continuous Resource allocation, and the base station indicates the joint coding of the initial Resource Blocks (RBs) and the number of RBs. CP-OFDM may use resource allocation type 0 and resource allocation type 1, whereas DFT-s-OFDM may only use resource allocation type 1.
The downlink control information (Downlink Control Information, DCI) format of the scheduled PUSCH includes a frequency domain resource allocation (Frequency domain resource assignment, FDRA) domain, and the number of bits in the FDRA domain is related to the resource allocation type.
Specifically, the FDRA field of DCI format 0_0 is fixed according to resource allocation type 1, and the number of bits of the FDRA field in DCI format 0_1 and DCI format 0_2 is related to the resource allocation type configured by the higher layer.
For example, the number of bits of the FDRA field in DCI format 0_1 is as follows:
if only the resource allocation type 0 is configured, the number of bits of the FDRA field is N RBG ,N RBG For the number of RBGs included in the Bandwidth Part (BWP), FDRA fieldsThe bitmap (bitmap) manner indicates the set of RBGs allocated for PUSCH.
If only resource allocation type 1 is configured, the number of bits of the FDRA field is:
wherein,the number of RBs included in the uplink BWP.
The FDRA field indicates a resource indicator value (Resource Indication Value, RIV) obtained by joint coding of the initial RB and the RB number.
If a dynamic resource allocation type handoff is configured, the number of bits of the FDRA domain is:
wherein,for the number of RBs contained in the uplink BWP, N RBG Is the number of RBGs included in the upstream BWP.
The most significant bit (Most Significant Bit, MSB) of the FDRA domain is used to dynamically indicate the resource allocation type, and further determine the frequency domain resource allocation of the PUSCH according to the indicated resource allocation type according to the resource allocation type 0 or type 1.
Since the resource allocation type determines the number of bits of the FDRA information field in the DCI, the resource allocation type needs to be preconfigured even if the uplink waveform dynamically changes. If one uniform resource allocation type is configured to be applicable to two waveforms along the prior art, the resource allocation type 0 cannot be configured to be a fixed resource allocation type 0 because the resource allocation type 0 is not applicable to the DFT-s-OFDM waveform in the prior art; if the resource allocation type is dynamic switching, the dynamic resource allocation indication is redundant for the DFT-s-OFDM waveform.
Fig. 1 is a schematic flow chart of a frequency domain resource allocation method provided in the embodiment of the present application, as shown in fig. 1, where an execution body of the frequency domain resource allocation method may be a terminal, for example, a mobile phone or the like. The method comprises the following steps:
step 101, determining the waveform of a physical uplink shared channel;
step 102, determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform.
In step 101, a waveform of a physical uplink shared channel is determined.
Alternatively, in the case of dynamic switching of the waveform of the PUSCH, the network device may transmit the indication information to the terminal. For example, the DCI for scheduling or activating PUSCH may be a media access Control layer (Media Access Control, MAC) Control Element (CE) message.
The terminal may determine the PUSCH waveform according to the indication information sent by the network device.
For example, in case of waveform dynamic switching of PUSCH, a terminal may receive DCI for scheduling or activating PUSCH, and the DCI may include an FDRA domain, a modulation and coding scheme (Modulation and Coding Scheme, MCS) domain, or a newly defined domain.
The terminal may determine the PUSCH waveform according to the indication of the FDRA domain in the DCI, e.g., the terminal may determine the PUSCH waveform according to the MSB of the FDRA domain, which may be 0 or 1, and the two states may correspond to DFT-s-OFDM and CP-OFDM, respectively.
The terminal may also determine the PUSCH waveform according to other indications in the DCI, except for the FDRA domain, for example, may be an indication of other information domains in the DCI, such as an MCS domain, a newly defined domain.
The terminal may also receive the MAC-CE message sent by the network device, and determine the PUSCH waveform according to the indication of the MAC-CE message, which is not limited herein.
In step 102, a frequency domain resource allocation of the physical uplink shared channel is determined based on the waveform.
And the terminal determines the frequency domain resource allocation of the PUSCH according to the waveform of the PUSCH.
For example, when determining that the waveform of the PUSCH is DFT-s-OFDM, the terminal determines that the frequency domain resource allocation type of the PUSCH is the resource allocation type 1, and determines the frequency domain resource allocation of the PUSCH according to the resource allocation type 1.
When the terminal determines that the waveform of the PUSCH is CP-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 0, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0.
Or when the terminal determines that the waveform of the PUSCH is DFT-s-OFDM, determining that the frequency domain resource allocation type of the PUSCH is resource allocation type 0, and when determining the resource allocation of the PUSCH according to the resource allocation type 0, the RBGs allocated to the PUSCH are continuous in the frequency domain.
When the terminal determines that the waveform of the PUSCH is CP-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 0, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0.
Or when the terminal determines that the waveform of the PUSCH is DFT-s-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 1, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 1.
When the terminal determines that the waveform of the PUSCH is CP-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 1, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 1.
That is, the terminal may dynamically determine the resource allocation type of the PUSCH according to the waveform of the PUSCH, thereby determining the frequency domain resource allocation of the PUSCH.
According to the frequency domain resource allocation method, when the uplink waveform dynamically changes, the terminal determines the waveform of the PUSCH, and determines the frequency domain resource allocation of the PUSCH according to the waveform of the PUSCH, so that the resource allocation type is dynamically determined according to the waveform, and the situation that the configuration is limited or the redundancy is indicated when the dynamic waveform is switched is solved.
In some embodiments, the determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform includes:
Under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0;
wherein the resource block groups allocated to the physical uplink shared channel according to the resource allocation type 0 are contiguous in the frequency domain.
The resource allocation type 0 performs resource allocation in units of RBGs, and can support discontinuous resource allocation and continuous resource allocation. Each RBG can include one or more RBs.
When the terminal determines that the waveform of the PUSCH is DFT-s-OFDM, the frequency domain resource allocation type of the PUSCH is determined to be the resource allocation type 0, and when the resource allocation of the PUSCH is determined according to the resource allocation type 0, RBGs allocated to the PUSCH are continuous in the frequency domain.
For example, an indication may be added to the FDRA domain in the DCI, so that when the terminal determines that the waveform of the PUSCH is DFT-s-OFDM, it determines that the frequency domain resource allocation type of the PUSCH is the resource allocation type 0, and determines that the frequency domain resource allocation of the PUSCH according to the resource allocation type 0, the RBGs allocated to the PUSCH are continuous in the frequency domain.
According to the frequency domain resource allocation method provided by the embodiment of the application, when the terminal determines that the waveform of the PUSCH is DFT-s-OFDM, RBGs allocated to the PUSCH according to the resource allocation type 0 are continuous in the frequency domain, so that the DFT-s-OFDM waveform is supported to use the resource allocation type 0, the resource allocation type is supported to be dynamically determined according to the waveform, the situation that the configuration is limited or redundancy is indicated during dynamic waveform switching is further solved, and the flexibility of frequency domain resource allocation is improved.
In some embodiments, after determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0, the method further includes:
determining a target number under the condition that the total number of the resource blocks in the resource block group set does not meet a preset condition; the target number is the maximum value meeting the preset condition, and the target number is smaller than the total number;
the target number is the number of resource blocks allocated to the physical uplink shared channel;
the preset conditions are as follows:
wherein,alpha is the number of resource blocks 2 ,α 3 ,α 5 Is a non-negative integer.
Optionally, when the waveform of the PUSCH is DFT-s-OFDM, the number of RBs allocated to the PUSCH needs to satisfy the following preset condition:
wherein,alpha is the number of resource blocks 2 ,α 3 ,α 5 Is a non-negative integer.
When determining that the waveform of the PUSCH is DFT-s-OFDM, if the total number of RBs in the RBG set allocated to the PUSCH according to the resource allocation type 0 does not meet the preset condition, determining the target number from the total number, where the target number of RBs is the RBs allocated to the PUSCH.
The target number may be obtained by determining all values satisfying the preset condition in the total number and selecting one maximum value from all the determined values. The target number is the number of RBs allocated to PUSCH.
In some embodiments, the target number of resource blocks is the lowest or highest frequency target number of resource blocks in the set of resource block groups.
The target number of RBs allocated to PUSCH is the lowest or highest frequency target number of RBs in the RGB set.
For example, the number of bits of FDRA field in DCI is determined to be N RBG ,N RBG Is the number of RBGs included in the upstream BWP.
The terminal determines the waveform of the PUSCH according to other indications except the FDRA domain in the DCI, for example, the waveform may be other information domains in the DCI, for example, an MCS domain or a newly defined domain, etc.
The terminal may also determine the PUSCH waveform, such as a MAC-CE message, according to an indication other than DCI, which is not limited herein.
1. When the terminal determines that the waveform of the PUSCH is DFT-s-OFDM, the RBG set allocated by the FDRA domain is determined according to the resource allocation type 0, and the RBG set is continuous on the frequency domain.
Optionally, if the number of RBs corresponding to the RBG set does not satisfy (alpha 2, alpha 3, alpha 5 are non-negative integers).
Determining that the frequency domain resource allocation of the PUSCH is as the number of the RBG set within the allocation meets the requirement2 ,α 3 ,α 5 Is a non-negative integer) maximum number RB, said +.>The RBs are the lowest or highest frequency of the RBG sets>And RB.
For example, the FDRA domain indicates that the allocated RBG sets are RBG0 to RBG13, wherein RBG0 includes one PRB and the other RBGs include 4 PRBs, and RBG0 to RBG13 correspond to consecutive 53 PRBs from PRB0 to PRB52. The above formula is satisfied and a maximum value of less than 53 is 50. The frequency domain resource allocation of PUSCH is 50 PRBs with the lowest or highest frequency among PRB0 to PRB52, i.e., PRB0 to PRB49 or PRB3 to PRB52.
2. When the terminal determines that the waveform of the PUSCH is the CP-OFDM, the terminal determines the frequency domain resource allocation of the PUSCH according to the resource allocation type 0. Specifically, the FDRA domain indicates the set of RBGs allocated for PUSCH.
For another example, the number of bits of the FDRA field in DCI is determined to be N RBG +1,N RBG Is the number of RBGs included in the upstream BWP.
The terminal determines the waveform of the PUSCH according to the MSB in the FDRA domain in the DCI, and the two states of the MSB correspond to DFT-s-OFDM and CP-OFDM respectively.
1. When the terminal determines that the waveform of the PUSCH is DFT-s-OFDM, the RBG set allocated by the FDRA domain is determined according to the resource allocation type 0, and the RBG set is continuous in the frequency domain.
Optionally, if the number of RBs corresponding to the RBG set does not satisfy (alpha 2, alpha 3, alpha 5 are non-negative integers).
Determining that the frequency domain resource allocation of the PUSCH is as the number of the RBG set within the allocation meets the requirement2 ,α 3 ,α 5 Is a non-negative integer) maximum number RB, said +.>The RBs are the lowest or highest frequency of the RBG sets>And RB.
2. And when the waveform of the PUSCH is determined to be the CP-OFDM, determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0. Specifically, the FDRA domain indicates the set of RBGs allocated for PUSCH.
In order to meet the requirement of the number of RBs of the DFT-s-OFDM waveform, the frequency domain resource allocation method further determines a subset in the allocated RBG set to serve as the frequency domain resource allocation of the PUSCH, so that the resource allocation type 0 used by the DFT-s-OFDM waveform is realized, the resource allocation type is dynamically determined according to the waveform, the situation that configuration is limited or redundancy is indicated during dynamic waveform switching is further solved, and the flexibility of frequency domain resource allocation is improved.
In some embodiments, the determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform includes:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is a resource allocation type 1;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 1;
under the condition that the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
and determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0.
When the terminal determines that the waveform of the PUSCH is DFT-s-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 1, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 1.
When the terminal determines that the waveform of the PUSCH is CP-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 0, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0.
For example, the number of bits of the FDRA field in DCI is determined to be max (N1, N2) +1. Where N1 and N2 are the number of bits determined according to the resource allocation type 1 and the resource allocation type 0, respectively.
The number of bits of the FDRA field in DCI format 0_1 is:
wherein,for the number of RBs contained in the uplink BWP, N RBG Is the number of RBGs included in the upstream BWP.
The number of bits of the FDRA field in DCI format 0_2 is:
wherein,for the number of RBs contained in the uplink BWP, < + >>N is the initial position of the uplink BWP RBG For the number of RBGs included in the uplink BWP, K1 is DCI format 0_2 resource allocation type 1 granularity.
The MSB in the FDRA domain indicates the waveform of PUSCH and/or the resource allocation type of PUSCH, for example:
1. the two states of the MSB of the FDRA domain may correspond to DFT-s-OFDM and CP-OFDM, respectively.
1.1, when the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 1, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 1.
For DCI format 0_1, low of fdra domain The bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
For DCI format 0_2, low of fdra domainBit indication is obtained by joint coding of initial RB and RB number allocated for PUSCHRIV。
1.2, when the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 0, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0.
For DCI format 0_1 and DCI format 0_2, low N of fdra domain RBG The bits indicate the set of RBGs allocated for PUSCH.
2. The two states of the MSB in the FDRA domain may correspond to resource allocation type 0 and resource allocation type 1, respectively.
2.1 when the resource allocation type is 1, the waveform of the PUSCH is DFT-s-OFDM.
For DCI format 0_1, low of fdra domain The bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
For DCI format 0_2, low of fdra domainThe bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
2.2 when the resource allocation type is 0, the waveform of the PUSCH is CP-OFDM.
For DCI format 0_1 and DCI format 0_2, low N of fdra domain RBG The bits indicate the set of RBGs allocated for PUSCH.
3. The two states of the MSB in the FDRA domain may correspond to the CP-OFDM waveform and the resource allocation type 0, and the DFT-s-OFDM waveform and the resource allocation type 1, respectively.
3.1, when corresponding DFT-s-OFDM waveform and resource allocation type 1:
for DCI format 0_1, low of fdra domain The bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
For DCI format 0_2, low of fdra domainThe bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
3.2, when the corresponding CP-OFDM waveform and resource allocation type 0:
For DCI format 0_1 and DCI format 0_2, low N of fdra domain RBG The bits indicate the set of RBGs allocated for PUSCH.
According to the frequency domain resource allocation method provided by the embodiment of the application, the resource allocation type is determined according to the waveform of the PUSCH, when the waveform is DFT-s-OFDM, the resource allocation type of the PUSCH is fixed to be 1, when the waveform is CP-OFDM, the resource allocation type of the PUSCH is fixed to be 0, and the situations of limited configuration or redundant indication during dynamic waveform switching are solved.
In some embodiments, the determining the waveform of the physical uplink shared channel includes:
receiving downlink control information for scheduling or activating the physical uplink shared channel;
and determining the waveform of the physical uplink shared channel based on the downlink control information.
Alternatively, the terminal may receive DCI for scheduling or activating PUSCH transmitted by the network device, where the DCI may include an FDRA domain, an MCS domain, a newly defined domain, and the like.
The terminal may determine the waveform of PUSCH according to the indication of the FDRA domain, the MCS domain, or the newly defined domain in the DCI.
In some embodiments, the determining the waveform of the physical uplink shared channel based on the downlink control information includes:
and determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information.
Alternatively, the terminal may determine the waveform of PUSCH from the FDRA domain in DCI.
Further, the determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information includes:
and determining the waveform of the physical uplink shared channel based on the most significant bit of the frequency domain resource allocation domain in the downlink control information.
The MSB of the FDRA field may be 0 or 1, and the two states may correspond to the two waveforms DFT-s-OFDM and CP-OFDM, respectively.
The terminal can determine the waveform of the PUSCH according to the indication of the MSB of the FDRA domain in the DCI.
According to the frequency domain resource allocation method provided by the embodiment of the application, the MSB of the FDRA domain can be used for dynamically indicating the waveform, so that the terminal can determine the waveform of the PUSCH according to the MSB of the FDRA domain.
In some embodiments, the determining the waveform of the physical uplink shared channel based on the downlink control information includes:
and determining the waveform of the physical uplink shared channel based on the domains except the frequency domain resource allocation domain in the downlink control information.
Alternatively, the terminal may determine the PUSCH waveform according to the indication of the other fields in the DCI, except the FDRA field, for example, may be other information fields in the DCI, such as an MCS field or a newly defined field, which is not limited herein.
In some embodiments, the determining the waveform of the physical uplink shared channel includes:
receiving a MAC-CE message;
and determining the waveform of the physical uplink shared channel based on the indication of the MAC-CE message.
Alternatively, the terminal may also determine the waveform of PUSCH according to an indication other than DCI. For example, the terminal may receive a MAC-CE message transmitted by the network device and determine the PUSCH waveform according to an indication of the MAC-CE message.
In some embodiments, further comprising:
and determining the frequency domain resource allocation of the physical uplink shared channel based on a high order zero padding or low order bit mode under the condition that the bit number of the frequency domain resource allocation domain in the downlink control information is inconsistent with the bit number of the frequency domain resource allocation domain determined based on the resource allocation type.
Alternatively, in case that the number of bits of the FDRA in the DCI does not coincide with the number of bits of the FDRA determined based on the resource allocation type, the frequency domain resource allocation of the PUSCH may be determined according to a high order zero padding or a low order bit manner.
For example, when the number of bits of the FDRA domain in the DCI is determined to be min (N1, N2), where N1 and N2 are the number of bits determined according to the resource allocation type 1 and the resource allocation type 0, respectively.
The number of bits of the FDRA field in DCI format 0_1 is:
wherein,for the number of RBs contained in the uplink BWP, N RBG Is the number of RBGs included in the upstream BWP.
The number of bits of the FDRA field in DCI format 0_2 is:
/>
wherein the method comprises the steps ofFor the number of RBs contained in the uplink BWP, < + >>N is the initial position of the uplink BWP RBG For the number of RBGs included in the uplink BWP, K1 is DCI format 0_2 resource allocation type 1 granularity.
The waveform of the PUSCH is determined according to other indications in the DCI except the FDRA domain, and may be, for example, other information domains in the DCI, such as an MCS domain or a newly defined domain, etc.
The PUSCH waveform may be determined according to an instruction other than DCI, and may be an instruction such as a MAC-CE message, for example, which is not limited herein.
1. When the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 1, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 1.
For DCI format 0_1, if the number of bits of the FDRA domain is greater thanLow ∈of the FDRA domain>Bit indication is RIV obtained by joint coding of initial RB and RB number distributed for PUSCH;
if the number of bits of the FDRA field is smaller thanThen the FDRA domain is high-order zero-padded to +.>Bit(s)>The bit indicates RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH, or RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH directly uses the value of the FDRA domain.
For DCI format 0_2, if the number of bits of the FDRA domain is greater thanLow ∈of the FDRA domain>Bit indication is RIV obtained by joint coding of initial RB and RB number distributed for PUSCH;
if the number of bits of the FDRA field is smaller thanThen the FDRA domain is high-order zero-padded to +.>Bit(s)>The bit indicates RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH, or RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH directly uses the value of the FDRA domain.
2. When the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 0, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0.
For DCI format 0_1 and DCI format 0_2, if the number of bits of the FDRA domain is greater than N RBG Low N of FDRA domain RBG Bit indicates RBG set allocated for PUSCH;
if the number of bits of the FDRA field is less than N RBG Then carry out high order zero padding to N on the FDRA domain RBG Bits, N RBG The bits indicate the set of RBGs allocated for PUSCH.
According to the frequency domain resource allocation method provided by the embodiment of the application, under the condition that the bit number of FDRA in DCI is inconsistent with the bit number of FDRA determined based on the resource allocation type, the frequency domain resource allocation of the PUSCH can be determined in a high-order zero padding or low-order bit filling mode.
In some embodiments, further comprising:
and determining the waveform of the physical uplink shared channel based on the frequency resource allocation domain in the downlink control information, wherein the bit number of the frequency resource allocation domain in the downlink control information does not comprise bits for indicating the waveform of the physical uplink shared channel.
Optionally, when determining the PUSCH waveform based on the indication of the FDRA domain in the DCI, and the number of bits of the FDRA domain in the DCI is inconsistent with the number of bits of the FDRA domain determined based on the resource allocation type, and determining the frequency domain resource allocation of the PUSCH by using a high order zero padding or a low order bit, the number of bits of the FDRA domain is a number of bits excluding the waveform for indicating the PUSCH.
Fig. 2 is a second flowchart of a frequency domain resource allocation method according to the embodiment of the present application, as shown in fig. 2, where an execution body of the frequency domain resource allocation method may be a network device, for example, a base station. The method comprises the following steps:
step 201, sending indication information;
the indication information is used for determining a waveform of a physical uplink shared channel, and the waveform is used for determining frequency domain resource allocation of the physical uplink shared channel.
In some embodiments, the sending the indication information includes:
transmitting downlink control information for scheduling or activating the physical uplink shared channel; the downlink control information is used for determining the waveform of the physical uplink shared channel.
In some embodiments, the sending the indication information includes:
transmitting a MAC-CE message; the MAC-CE message is used to determine a waveform of the physical uplink shared channel.
Specifically, the frequency domain resource allocation method provided in the embodiments of the present application may refer to the embodiment of the frequency domain resource allocation method in which the execution body is a terminal, and may achieve the same technical effects, and the same parts and beneficial effects as those of the embodiment of the corresponding method in the embodiments are not described in detail herein.
The frequency domain resource allocation method provided by the embodiment of the present application is described in detail below with reference to specific embodiments.
Embodiment one:
the bit number of the FDRA domain in the DCI is determined to be max (N1, N2) +1, wherein N1 and N2 are respectively determined according to the resource allocation type 1 and the resource allocation type 0.
The number of bits of the FDRA field in DCI format 0_1 is:
wherein,for the number of RBs contained in the uplink BWP, N RBG Is the number of RBGs included in the upstream BWP.
The number of bits of the FDRA field in DCI format 0_2 is:
wherein,for the number of RBs contained in the uplink BWP, < + >>N is the initial position of the uplink BWP RBG For the number of RBGs included in the uplink BWP, K1 is DCI format 0_2 resource allocation type 1 granularity.
The MSB in the FDRA domain may indicate the waveform of PUSCH and/or the resource allocation type of PUSCH:
1. the two states of the MSB of the FDRA field correspond to DFT-s-OFDM and CP-OFDM, respectively.
1.1, when the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 1, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 1.
For DCI format 0_1, low of fdra domain The bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
For DCI format 0_2, low of fdra domainThe bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
1.2, when the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 0, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0.
For DCI format 0_1 and DCI format 0_2, low N of fdra domain RBG The bits indicate the set of RBGs allocated for PUSCH.
2. The two states of the MSB in the FDRA domain correspond to resource allocation type 0 and resource allocation type 1, respectively.
2.1 when the resource allocation type is 1, the waveform of the PUSCH is DFT-s-OFDM, and for DCI format 0_1, the fdra domain is low The bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
For DCI format 0_2, low of fdra domainThe bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
2.2 when the resource allocation type is 0, the PUSCH waveform is CP-OFDM,
for DCI format 0_1 and DCI format 0_2, low N of fdra domain RBG The bits indicate the set of RBGs allocated for PUSCH.
3. The two states of the MSB in the FDRA domain correspond to the CP-OFDM waveform and the resource allocation type 0, and the DFT-s-OFDM waveform and the resource allocation type 1, respectively.
3.1 when the corresponding DFT-s-OFDM waveform and resource allocation type 1,
for DCI format 0_1, low of fdra domain The bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
For DCI format 0_2, low of fdra domainThe bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
3.2 when the corresponding CP-OFDM waveform and resource allocation type 0,
for DCI format 0_1 and DCI format 0_2, low N of fdra domain RBG The bits indicate the set of RBGs allocated for PUSCH.
Embodiment two:
Determining the number of bits of FDRA field in DCI as N RBG ,N RBG Is the number of RBGs included in the upstream BWP.
The waveform of the PUSCH is determined according to other indications in the DCI except the FDRA domain, and may be, for example, other information domains in the DCI, such as an MCS domain or a newly defined domain, etc.
The PUSCH waveform may be determined according to an instruction other than DCI, and may be an instruction such as a MAC-CE message, for example, which is not limited herein.
1. When the waveform is DFT-s-OFDM, RBG sets allocated by the FDRA domain are determined according to the resource allocation type 0, and the RBG sets are continuous in the frequency domain.
Optionally, if the number of RBs corresponding to the RBG set does not satisfy (alpha 2, alpha 3, alpha 5 are non-negative integers), determining that the frequency domain resource allocation of the PUSCH is as the number of the RBG set within the allocation meets the requirement2 ,α 3 ,α 5 Non-negative integer) is providedMaximum number RB, & lt->The RBs are the lowest or highest frequency of the RBG sets>And RB.
For example, the FDRA domain indicates that the allocated RBG sets are RBG0 to RBG13, wherein RBG0 includes one PRB and the other RBGs include 4 PRBs, and RBG0 to RBG13 correspond to consecutive 53 PRBs from PRB0 to PRB52. The above formula is satisfied and a maximum value of less than 53 is 50. The frequency domain resource allocation of PUSCH is 50 PRBs with the lowest or highest frequency among PRB0 to PRB52, i.e., PRB0 to PRB49 or PRB3 to PRB52.
2. When the waveform is CP-OFDM, determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0.
Specifically, the FDRA domain indicates the set of RBGs allocated for PUSCH.
Embodiment III:
determining the number of bits of FDRA field in DCI as N RBG +1,N RBG Is the number of RBGs included in the upstream BWP.
The MSB in the FDRA domain is used to indicate the waveform of the PUSCH, and the two states correspond to DFT-s-OFDM and CP-OFDM, respectively.
1. When the waveform is DFT-s-OFDM, a set of RBGs allocated by the FDRA domain is determined according to the resource allocation type 0, the set of RBGs being contiguous in the frequency domain. Optionally, determining that the frequency domain resource allocation of the PUSCH is as the number of the RBG set within the allocation meets the requirement2 ,α 3 ,α 5 Is a non-negative integer) of the maximum number RBThe RBs are the lowest or highest frequency of the RBG sets>And RB.
For example, the FDRA domain indicates that the allocated RBG sets are RBG0 to RBG13, wherein RBG0 includes one PRB and the other RBGs include 4 PRBs, and RBG0 to RBG13 correspond to consecutive 53 PRBs from PRB0 to PRB52. The above formula is satisfied and a maximum value of less than 53 is 50. The frequency domain resource allocation of PUSCH is 50 PRBs with the lowest or highest frequency among PRB0 to PRB52, i.e., PRB0 to PRB49 or PRB3 to PRB52.
2. When the waveform is CP-OFDM, determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0. Specifically, the FDRA domain indicates the set of RBGs allocated for PUSCH.
Embodiment four:
the bit number of the FDRA field in the DCI is determined to be N1+1, wherein N1 is the bit number determined according to the resource allocation type 1.
The number of bits of the FDRA field in DCI format 0_1 is:
wherein,the number of RBs included in the uplink BWP.
The number of bits of the FDRA field in DCI format 0_2 is:
wherein,for the number of RBs contained in the uplink BWP, < + >>For the position of the start of the uplink BWP, K1 is DCI format 0_2 resource allocation type 1 granularity.
The MSB in the FDRA domain is used to indicate the waveform of the PUSCH, and the two states correspond to DFT-s-OFDM and CP-OFDM, respectively.
The bits of the FDRA field other than the MSB are determined as the RIV obtained by joint coding of the initial RB and the RB number of the PUSCH allocation.
Fifth embodiment:
the bit number of the FDRA field in the DCI is determined to be max (N1, N2), wherein N1 and N2 are the bit numbers determined according to the resource allocation type 1 and the resource allocation type 0 respectively.
The number of bits of the FDRA field in DCI format 0_1 is:
wherein,for the number of RBs contained in the uplink BWP, N RBG Is the number of RBGs included in the upstream BWP.
The number of bits of the FDRA field in DCI format 0_2 is:
wherein the method comprises the steps ofFor the number of RBs contained in the uplink BWP, < + >>N is the initial position of the uplink BWP RBG For the number of RBGs included in the uplink BWP, K1 is DCI format 0_2 resource allocation type 1 granularity.
The waveform of the PUSCH is determined according to other indications in the DCI except the FDRA domain, and may be, for example, other information domains in the DCI, such as an MCS domain or a newly defined domain, etc.
The PUSCH waveform may be determined according to an instruction other than DCI, and may be an instruction such as a MAC-CE message, for example, which is not limited herein.
1. When the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 1, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 1.
For DCI format 0_1, low of fdra domain The bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
For DCI format 0_2, low of fdra domainThe bit indicates the RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH.
2. When the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 0, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0.
For DCI format 0_1 and DCI format 0_2, low N of fdra domain RBG The bits indicate the set of RBGs allocated for PUSCH.
Example six:
the bit number of the FDRA field in the DCI is determined to be min (N1, N2), wherein N1 and N2 are the bit numbers determined according to the resource allocation type 1 and the resource allocation type 0 respectively.
The number of bits of the FDRA field in DCI format 0_1 is:
wherein,for the number of RBs contained in the uplink BWP, N RBG Is the number of RBGs included in the upstream BWP.
The number of bits of the FDRA field in DCI format 0_2 is:
wherein the method comprises the steps ofFor the number of RBs contained in the uplink BWP, < + >>N is the initial position of the uplink BWP RBG For the number of RBGs included in the uplink BWP, K1 is DCI format 0_2 resource allocation type 1 granularity.
The waveform of the PUSCH is determined according to other indications in the DCI except the FDRA domain, and may be, for example, other information domains in the DCI, such as an MCS domain or a newly defined domain, etc.
The PUSCH waveform may be determined according to an instruction other than DCI, and may be an instruction such as a MAC-CE message, for example, which is not limited herein.
1. When the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 1, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 1.
For DCI format 0_1, if the number of bits of the FDRA domain is greater thanLow ∈of the FDRA domain>Bit indication is RIV obtained by joint coding of initial RB and RB number distributed for PUSCH;
if the number of bits of the FDRA field is smaller thanThen the FDRA domain is high-order zero-padded to +.>Bit(s)>The bit indicates RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH, or RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH directly uses the value of the FDRA domain.
For DCI format 0_2, if the number of bits of the FDRA domain is greater thanLow ∈of FDRA Domain>Bit indication is RIV obtained by joint coding of initial RB and RB number distributed for PUSCH;
if the number of bits of the FDRA field is smaller thanThen the FDRA domain is high-order zero-padded to +.>Bit(s)>The bit indicates RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH, or RIV obtained by joint coding of the initial RB and the RB number allocated for the PUSCH directly uses the value of the FDRA domain.
2. When the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the PUSCH is the resource allocation type 0, and determining the frequency domain resource allocation of the PUSCH according to the resource allocation type 0.
For DCI format 0_1 and DCI format 0_2, if the number of bits of the FDRA domain is greater than N RBG Low N of FDRA domain RBG Bit indicates RBG set allocated for PUSCH;
if the number of bits of the FDRA field is less than N RBG Then carry out high order zero padding to N on the FDRA domain RBG Bits, N RBG The bits indicate the set of RBGs allocated for PUSCH.
The PUSCH in all the above embodiments may be a PUSCH dynamically scheduled by DCI, or may be a configuration grant PUSCH activated by DCI.
All embodiments are directed to PUSCH, but for other uplink and downlink physical channels, dynamic waveform switching is also applicable if supported.
The above embodiments may be used alone or in combination.
For example, embodiment one may be used alone.
The number of bits of the FDRA domain is fixed in the manner of embodiment one when dynamic waveform switching is enabled, and the MSBs of the FDRA domain are used to indicate the waveform and/or the resource allocation type.
The first, third and fourth embodiments may be used in combination.
For example, it is assumed that the resource allocation type configured at the network side is applicable to both CP-OFDM and DFT-s-OFDM, and the configured resource allocation type is a resource allocation type 0, a resource allocation type 1, or dynamic handover. Then, when the resource allocation type is dynamic handover, embodiment one is adopted; when the resource allocation type is the resource allocation type 0, adopting the third embodiment; when the resource allocation type is the resource allocation type 1, the fourth embodiment is adopted.
Or, the default DFT-s-OFDM is fixed and adopts the resource allocation type 1, the resource allocation type of the CP-OFDM waveform is configured by a network side, and when the resource allocation type of the CP-OFDM waveform is configured as the resource allocation type 0, the first embodiment is adopted; the fourth embodiment is adopted when the resource allocation type of the CP-OFDM waveform is configured as the resource allocation type 1.
Or, the network side configures the resource allocation types for the CP-OFDM waveform and the DFT-s-OFDM waveform respectively, and when dynamic switching is configured for any one waveform or the resource allocation type 0 and the resource allocation type 1 are configured for the CP-OFDM waveform and the DFT-s-OFDM waveform respectively, embodiment one is adopted; when the resource allocation type 0 is configured for both the CP-OFDM waveform and the DFT-s-OFDM waveform, the third embodiment is adopted; the fourth embodiment is adopted when the resource allocation type 1 is configured for both the CP-OFDM waveform and the DFT-s-OFDM waveform.
The second embodiment and the fifth or sixth embodiment may be used in combination.
For example, it is assumed that the resource allocation type configured at the network side is applicable to both CP-OFDM and DFT-s-OFDM, and the configured resource allocation type is a resource allocation type 0, a resource allocation type 1, or dynamic handover. Adopting the fifth embodiment or the sixth embodiment when the resource allocation type is dynamic switching; when the resource allocation type is the resource allocation type 0, adopting the second embodiment; when the resource allocation type is the resource allocation type 1, the FDRA domain adopts the existing mechanism.
The first embodiment and the second embodiment may be used in combination.
For example, it is assumed that the resource allocation type configured at the network side is applicable to both CP-OFDM and DFT-s-OFDM, and the configured resource allocation type is a resource allocation type 0, a resource allocation type 1, or dynamic handover. Then, when the resource allocation type is dynamic handover, embodiment one is adopted; when the resource allocation type is the resource allocation type 0, adopting the second embodiment; when the resource allocation type is the resource allocation type 1, the FDRA domain adopts the existing mechanism.
The frequency domain resource allocation method provided by the embodiment of the application can support the DFT-s-OFDM waveform to use the resource allocation type 0 and support the dynamic determination of the resource allocation type according to the waveform, thereby solving the problems of limited configuration or redundant indication during dynamic waveform switching.
Fig. 3 is a schematic structural diagram of a terminal according to an embodiment of the present application, as shown in fig. 3, where the terminal includes a memory 320, a transceiver 300, and a processor 310, where:
a memory 320 for storing a computer program; a transceiver 300 for transceiving data under the control of the processor 310; a processor 310 for reading the computer program in the memory 320 and performing the following operations: determining the waveform of a physical uplink shared channel; and determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform.
Specifically, the transceiver 300 is used to receive and transmit data under the control of the processor 310.
Wherein in fig. 3, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 310 and various circuits of memory represented by memory 320, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 300 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over transmission media, including transmission media including wireless channels, wired channels, optical cables, and the like. The user interface 330 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 310 is responsible for managing the bus architecture and general processing, and the memory 320 may store data used by the processor 310 in performing operations.
Alternatively, the processor 310 may be a central processing unit (Central Processing Unit, CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a Field programmable gate array (Field-Programmable Gate Array, FPGA), or a complex programmable logic device (Complex Programmable Logic Device, CPLD), and the processor may also employ a multi-core architecture.
The processor is configured to execute any of the methods provided in the embodiments of the present application by invoking a computer program stored in a memory in accordance with the obtained executable instructions. The processor and the memory may also be physically separate.
Optionally, as another embodiment, the processor 310 is further configured to:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0;
wherein the resource block groups allocated to the physical uplink shared channel according to the resource allocation type 0 are contiguous in the frequency domain.
Optionally, as another embodiment, the processor 310 is further configured to:
determining a target number under the condition that the total number of the resource blocks in the resource block group set does not meet a preset condition; the target number is the maximum value meeting the preset condition, and the target number is smaller than the total number;
the target number is the number of resource blocks allocated to the physical uplink shared channel;
the preset conditions are as follows:
wherein,alpha is the number of resource blocks 2 ,α 3 ,α 5 Is a non-negative integer.
Optionally, as another embodiment, the target number of resource blocks is the lowest or highest frequency target number of resource blocks in the set of resource block groups.
Optionally, as another embodiment, the processor 310 is further configured to: under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is a resource allocation type 1;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 1;
under the condition that the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
and determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0.
Optionally, as another embodiment, the processor 310 is further configured to:
receiving downlink control information for scheduling or activating the physical uplink shared channel;
and determining the waveform of the physical uplink shared channel based on the downlink control information.
Optionally, as another embodiment, the processor 310 is further configured to:
and determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information.
Optionally, as another embodiment, the processor 310 is further configured to:
and determining the waveform of the physical uplink shared channel based on the most significant bit of the frequency domain resource allocation domain in the downlink control information.
Optionally, as another embodiment, the processor 310 is further configured to:
and determining the waveform of the physical uplink shared channel based on the domains except the frequency domain resource allocation domain in the downlink control information.
Optionally, as another embodiment, the processor 310 is further configured to:
receiving a MAC-CE message;
and determining the waveform of the physical uplink shared channel based on the indication of the MAC-CE message.
Optionally, as another embodiment, the processor 310 is further configured to:
and determining the frequency domain resource allocation of the physical uplink shared channel based on a high order zero padding or low order bit mode under the condition that the bit number of the frequency domain resource allocation domain in the downlink control information is inconsistent with the bit number of the frequency domain resource allocation domain determined based on the resource allocation type.
Optionally, as another embodiment, the processor 310 is further configured to:
and determining the waveform of the physical uplink shared channel based on the frequency resource allocation domain in the downlink control information, wherein the bit number of the frequency resource allocation domain in the downlink control information does not comprise bits for indicating the waveform of the physical uplink shared channel.
It should be noted that, the terminal provided by the embodiment of the present invention can implement all the method steps implemented by the method embodiment in which the execution body is a terminal, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those of the method embodiment in the embodiment are omitted herein.
Fig. 4 is a schematic structural diagram of a network device according to an embodiment of the present application, as shown in fig. 4, where the network device includes a memory 420, a transceiver 400, and a processor 410, where:
a memory 420 for storing a computer program; a transceiver 400 for transceiving data under the control of the processor 410; a processor 410 for reading the computer program in the memory 420 and performing the following operations:
transmitting indication information;
the indication information is used for determining a waveform of a physical uplink shared channel, and the waveform is used for determining frequency domain resource allocation of the physical uplink shared channel.
Specifically, the transceiver 400 is configured to receive and transmit data under the control of the processor 410.
Wherein in fig. 4, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 410 and various circuits of memory represented by memory 420, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 400 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium, including wireless channels, wired channels, optical cables, etc. The processor 410 is responsible for managing the bus architecture and general processing, and the memory 420 may store data used by the processor 410 in performing operations.
The processor 410 may be a central processing unit (Central Processing Unit, CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a Field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device, CPLD), or may employ a multi-core architecture.
Optionally, as another embodiment, the processor 410 is further configured to:
transmitting downlink control information for scheduling or activating the physical uplink shared channel; the downlink control information is used for determining the waveform of the physical uplink shared channel.
Optionally, as another embodiment, the processor 410 is further configured to:
transmitting a MAC-CE message; the MAC-CE message is used to determine a waveform of the physical uplink shared channel.
Fig. 5 is a schematic structural diagram of a frequency domain resource allocation apparatus according to an embodiment of the present application, where the apparatus includes:
a determining module 501, configured to determine a waveform of a physical uplink shared channel;
an allocation module 502, configured to determine frequency domain resource allocation of the physical uplink shared channel based on the waveform.
Optionally, the allocation module 502 is specifically configured to:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0;
wherein the resource block groups allocated to the physical uplink shared channel according to the resource allocation type 0 are contiguous in the frequency domain.
Optionally, the frequency domain resource allocation device further includes:
a second determining module, configured to determine a target number if the total number of resource blocks in the resource block group set does not meet a preset condition; the target number is the maximum value meeting the preset condition, and the target number is smaller than the total number;
the target number is the number of resource blocks allocated to the physical uplink shared channel;
the preset conditions are as follows:
wherein,alpha is the number of resource blocks 2 ,α 3 ,α 5 Is a non-negative integer.
Optionally, the target number of resource blocks is the lowest or highest frequency target number of resource blocks in the set of resource blocks.
Optionally, the allocation module 502 is specifically configured to:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is a resource allocation type 1;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 1;
under the condition that the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
and determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0.
Optionally, the determining module 501 is specifically configured to:
receiving downlink control information for scheduling or activating the physical uplink shared channel;
and determining the waveform of the physical uplink shared channel based on the downlink control information.
Optionally, the frequency domain resource allocation device further includes:
and a third determining module, configured to determine a waveform of the physical uplink shared channel based on a frequency domain resource allocation domain in the downlink control information.
Optionally, the frequency domain resource allocation device further includes:
and a fourth determining module, configured to determine a waveform of the physical uplink shared channel based on a most significant bit of a frequency domain resource allocation domain in the downlink control information.
Optionally, the frequency domain resource allocation device further includes:
and a fifth determining module, configured to determine a waveform of the physical uplink shared channel based on a domain other than the frequency domain resource allocation domain in the downlink control information.
Optionally, the determining module 501 is further specifically configured to:
receiving a MAC-CE message;
and determining the waveform of the physical uplink shared channel based on the indication of the MAC-CE message.
Optionally, in the case that the number of bits in the frequency domain resource allocation domain in the downlink control information is inconsistent with the number of bits in the frequency domain resource allocation domain determined based on the resource allocation type, determining the frequency domain resource allocation of the physical uplink shared channel based on a high order zero padding or low order bit.
Optionally, in the case of determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information, the number of bits in the frequency domain resource allocation domain in the downlink control information does not include bits for indicating the waveform of the physical uplink shared channel.
It should be noted that, the device provided in this embodiment of the present invention can implement all the method steps implemented by the method embodiment in which the execution body is a terminal, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those of the method embodiment in this embodiment are omitted.
Fig. 6 is a second schematic structural diagram of a frequency domain resource allocation apparatus according to an embodiment of the present application, where the apparatus includes:
a sending module 601, configured to send indication information;
the indication information is used for determining a waveform of a physical uplink shared channel, and the waveform is used for determining frequency domain resource allocation of the physical uplink shared channel.
Optionally, the sending module 601 is specifically configured to:
transmitting downlink control information for scheduling or activating the physical uplink shared channel; the downlink control information is used for determining the waveform of the physical uplink shared channel.
Optionally, the sending module 601 is specifically configured to:
transmitting a MAC-CE message; the MAC-CE message is used to determine a waveform of the physical uplink shared channel.
It should be noted that, the above device provided in this embodiment of the present invention can implement all the method steps implemented by the method embodiment in which the execution body is a network device, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those of the method embodiment in this embodiment are omitted.
It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a processor-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution, in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In another aspect, embodiments of the present application further provide a processor readable storage medium storing a computer program, where the computer program is configured to cause the processor to perform the method provided in the foregoing embodiments, where the method includes: determining the waveform of a physical uplink shared channel; and determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform.
The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), semiconductor storage (e.g., ROM, EPROM, EEPROM, nonvolatile storage (NAND FLASH), solid State Disk (SSD)), and the like.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims (33)

1. The frequency domain resource allocation method is characterized by being applied to a terminal and comprising the following steps:
determining the waveform of a physical uplink shared channel;
and determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform.
2. The method of frequency domain resource allocation according to claim 1, wherein said determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform comprises:
Under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0;
wherein the resource block groups allocated to the physical uplink shared channel according to the resource allocation type 0 are contiguous in the frequency domain.
3. The method for allocating frequency domain resources according to claim 2, wherein after determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0, further comprising:
determining a target number under the condition that the total number of the resource blocks in the resource block group set does not meet a preset condition; the target number is the maximum value meeting the preset condition, and the target number is smaller than the total number;
the target number is the number of resource blocks allocated to the physical uplink shared channel;
the preset conditions are as follows:
wherein,alpha is the number of resource blocks 2 ,α 3 ,α 5 Is a non-negative integer.
4. The method of frequency domain resource allocation according to claim 3, wherein the target number of resource blocks is a target number of resource blocks with a lowest or highest frequency in the set of resource blocks.
5. The method of frequency domain resource allocation according to claim 1, wherein said determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform comprises:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is a resource allocation type 1;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 1;
under the condition that the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
and determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0.
6. The method of allocating frequency domain resources according to claim 1, wherein the determining a waveform of a physical uplink shared channel comprises:
receiving downlink control information for scheduling or activating the physical uplink shared channel;
and determining the waveform of the physical uplink shared channel based on the downlink control information.
7. The method of frequency domain resource allocation according to claim 6, wherein the determining the waveform of the physical uplink shared channel based on the downlink control information comprises:
And determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information.
8. The method of allocating frequency domain resources according to claim 7, wherein determining a waveform of a physical uplink shared channel based on a frequency domain resource allocation domain in the downlink control information comprises:
and determining the waveform of the physical uplink shared channel based on the most significant bit of the frequency domain resource allocation domain in the downlink control information.
9. The method of frequency domain resource allocation according to claim 6, wherein the determining the waveform of the physical uplink shared channel based on the downlink control information comprises:
and determining the waveform of the physical uplink shared channel based on the domains except the frequency domain resource allocation domain in the downlink control information.
10. The method of allocating frequency domain resources according to claim 1, wherein the determining a waveform of a physical uplink shared channel comprises:
receiving a MAC-CE message;
and determining the waveform of the physical uplink shared channel based on the indication of the MAC-CE message.
11. The frequency domain resource allocation method according to claim 2 or 5, further comprising:
And determining the frequency domain resource allocation of the physical uplink shared channel based on a high order zero padding or low order bit mode under the condition that the bit number of the frequency domain resource allocation domain in the downlink control information is inconsistent with the bit number of the frequency domain resource allocation domain determined based on the resource allocation type.
12. The frequency domain resource allocation method according to claim 11, further comprising:
and determining the waveform of the physical uplink shared channel based on the frequency resource allocation domain in the downlink control information, wherein the bit number of the frequency resource allocation domain in the downlink control information does not comprise bits for indicating the waveform of the physical uplink shared channel.
13. A method for allocating frequency domain resources, which is applied to a network device, comprising:
transmitting indication information;
the indication information is used for determining a waveform of a physical uplink shared channel, and the waveform is used for determining frequency domain resource allocation of the physical uplink shared channel.
14. The frequency domain resource allocation method according to claim 13, wherein the transmitting the indication information comprises:
transmitting downlink control information for scheduling or activating the physical uplink shared channel; the downlink control information is used for determining the waveform of the physical uplink shared channel.
15. The frequency domain resource allocation method according to claim 13, wherein the transmitting the indication information comprises:
transmitting a MAC-CE message; the MAC-CE message is used to determine a waveform of the physical uplink shared channel.
16. A terminal comprising a memory, a transceiver, and a processor:
a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:
determining the waveform of a physical uplink shared channel;
and determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform.
17. The terminal of claim 16, wherein the determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform comprises:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0;
wherein the resource block groups allocated to the physical uplink shared channel according to the resource allocation type 0 are contiguous in the frequency domain.
18. The terminal of claim 17, wherein after determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0, further comprising:
determining a target number under the condition that the total number of the resource blocks in the resource block group set does not meet a preset condition; the target number is the maximum value meeting the preset condition, and the target number is smaller than the total number;
the target number is the number of resource blocks allocated to the physical uplink shared channel;
the preset conditions are as follows:
wherein,alpha is the number of resource blocks 2 ,α 3 ,α 5 Is a non-negative integer.
19. The terminal of claim 18, wherein the target number of resource blocks is a lowest or highest frequency target number of resource blocks in the set of resource blocks.
20. The terminal of claim 16, wherein the determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform comprises:
under the condition that the waveform is DFT-s-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is a resource allocation type 1;
determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 1;
Under the condition that the waveform is CP-OFDM, determining that the frequency domain resource allocation type of the physical uplink shared channel is resource allocation type 0;
and determining the frequency domain resource allocation of the physical uplink shared channel according to the resource allocation type 0.
21. The terminal of claim 16, wherein the determining the waveform of the physical uplink shared channel comprises:
receiving downlink control information for scheduling or activating the physical uplink shared channel;
and determining the waveform of the physical uplink shared channel based on the downlink control information.
22. The terminal of claim 21, wherein the determining the waveform of the physical uplink shared channel based on the downlink control information comprises:
and determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information.
23. The terminal of claim 22, wherein the determining the waveform of the physical uplink shared channel based on the frequency domain resource allocation domain in the downlink control information comprises:
and determining the waveform of the physical uplink shared channel based on the most significant bit of the frequency domain resource allocation domain in the downlink control information.
24. The terminal of claim 21, wherein the determining the waveform of the physical uplink shared channel based on the downlink control information comprises:
and determining the waveform of the physical uplink shared channel based on the domains except the frequency domain resource allocation domain in the downlink control information.
25. The terminal of claim 16, wherein the determining the waveform of the physical uplink shared channel comprises:
receiving a MAC-CE message;
and determining the waveform of the physical uplink shared channel based on the indication of the MAC-CE message.
26. The terminal according to claim 17 or 20, further comprising:
and determining the frequency domain resource allocation of the physical uplink shared channel based on a high order zero padding or low order bit mode under the condition that the bit number of the frequency domain resource allocation domain in the downlink control information is inconsistent with the bit number of the frequency domain resource allocation domain determined based on the resource allocation type.
27. The terminal of claim 26, further comprising:
and determining the waveform of the physical uplink shared channel based on the frequency resource allocation domain in the downlink control information, wherein the bit number of the frequency resource allocation domain in the downlink control information does not comprise bits for indicating the waveform of the physical uplink shared channel.
28. A network device comprising a memory, a transceiver, and a processor:
a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:
transmitting indication information;
the indication information is used for determining a waveform of a physical uplink shared channel, and the waveform is used for determining frequency domain resource allocation of the physical uplink shared channel.
29. The network device of claim 28, wherein the transmitting the indication information comprises:
transmitting downlink control information for scheduling or activating the physical uplink shared channel; the downlink control information is used for determining the waveform of the physical uplink shared channel.
30. The network device of claim 28, wherein the transmitting the indication information comprises:
transmitting a MAC-CE message; the MAC-CE message is used to determine a waveform of the physical uplink shared channel.
31. A frequency domain resource allocation apparatus, comprising:
the determining module is used for determining the waveform of the physical uplink shared channel;
And the allocation module is used for determining the frequency domain resource allocation of the physical uplink shared channel based on the waveform.
32. A frequency domain resource allocation apparatus, comprising:
the sending module is used for sending the indication information;
the indication information is used for determining a waveform of a physical uplink shared channel, and the waveform is used for determining frequency domain resource allocation of the physical uplink shared channel.
33. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing the processor to perform the frequency domain resource allocation method of any one of claims 1 to 15.
CN202210837761.7A 2022-07-15 2022-07-15 Frequency domain resource allocation method, device and storage medium Pending CN117460053A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202210837761.7A CN117460053A (en) 2022-07-15 2022-07-15 Frequency domain resource allocation method, device and storage medium
PCT/CN2023/104635 WO2024012262A1 (en) 2022-07-15 2023-06-30 Frequency domain resource allocation method and apparatus, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210837761.7A CN117460053A (en) 2022-07-15 2022-07-15 Frequency domain resource allocation method, device and storage medium

Publications (1)

Publication Number Publication Date
CN117460053A true CN117460053A (en) 2024-01-26

Family

ID=89535463

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210837761.7A Pending CN117460053A (en) 2022-07-15 2022-07-15 Frequency domain resource allocation method, device and storage medium

Country Status (2)

Country Link
CN (1) CN117460053A (en)
WO (1) WO2024012262A1 (en)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2730446C1 (en) * 2017-03-17 2020-08-21 ЭлДжи ЭЛЕКТРОНИКС ИНК. Method and device for receiving terminal data in wireless communication system
CN109600845A (en) * 2017-09-30 2019-04-09 华为技术有限公司 A kind of resource regulating method, the network equipment and communication equipment
US11916843B2 (en) * 2020-08-11 2024-02-27 Qualcomm Incorporated Techniques for triggering CSI report on PUSCH based on downlink grant signaling

Also Published As

Publication number Publication date
WO2024012262A1 (en) 2024-01-18

Similar Documents

Publication Publication Date Title
KR102481800B1 (en) Method and apparatus for data transmission in new radio cellular network
CN109600835B (en) Method for determining resource allocation and indicating resource allocation, terminal and network side equipment
EP3334228B1 (en) Resource allocation method and device
JP7483053B2 (en) Frequency domain resource allocation method and device
TWI687116B (en) Resource configuration method and device, and computer storage medium
CN110324897B (en) Frequency domain resource allocation indication information sending method and device, frequency domain resource allocation indication information receiving method and device, storage medium, base station and user terminal
CN113747588B (en) Information transmission method and device
WO2021223703A1 (en) Frequency domain resource allocation method and device
CN110677371B (en) Communication method and device
CN109803412B (en) Resource mapping method, resource determining method, network side equipment and user terminal
CN114125860A (en) Method and device for allocating NR PDCCH (physical Downlink control channel) resources under spectrum sharing
WO2019029306A1 (en) Method, device, and system for transmitting downlink control information
CN109495965B (en) Resource indicating and determining method and device
CN110731109B (en) Resource indication method, equipment and computer storage medium
CN117460053A (en) Frequency domain resource allocation method, device and storage medium
CN115022968A (en) Resource allocation indicating method, resource allocation obtaining method, base station and user terminal
WO2020143721A1 (en) Resource assignment method and device and computer-readable storage medium
CN108633058B (en) Resource allocation method, base station and UE
CN113498183A (en) Method and device for indicating frequency domain resources
CN113271669A (en) Control information transmission method and device
CN114930758A (en) Multiple transmit and receive point (multiple TRP) enhancement
WO2023168564A1 (en) Transmissions across multiple time-domain resources in wireless communication networks
WO2023179114A1 (en) Reference signal transmission method, apparatus and storage medium
CN116506946A (en) Resource allocation method and device, terminal and network side equipment
CN111867079A (en) Resource allocation method, device and computer readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination