PUSCH resource allocation method, device and electronic device

Abstract

The present application discloses a PUSCH resource allocation method, device and electronic device, which belongs to the field of communication technology. The PUSCH resource allocation method is applied to a terminal, and the method includes: obtaining downlink control information or a random access response uplink authorization message, the downlink control information or the random access response uplink authorization message explicitly indicating or implicitly indicating a resource block set allocated by the PUSCH; determining a resource block set allocated by the scheduled PUSCH according to the downlink control information or the random access response uplink authorization message. The technical solution of the present application enables the network side and the terminal to have consistent understanding of PUSCH allocation resources.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a PUSCH resource allocation method, device and electronic device. Background Art

[0002] In an unlicensed system, type 2 uplink resource allocation needs to indicate the resource block set (RB set) and interlace allocated to the terminal (User Equipment, UE), where the indication of the resource block set is related to the number of resource block sets contained in the BWP. For the downlink control information (Downlink Control Information, DCI) format 0_0 scrambled by the temporary radio network temporary identity (TC-RNTI) and the physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) scheduled by the random access response (RAR) uplink grant (UL grant), since the base station may not know whether the UE is in the radio resource control connected state (RRC_connected) or the radio resource control idle state (RRC_idle) when sending the corresponding command, it is impossible to determine whether the UE is currently working in the active uplink bandwidth part (UL BWP) or the initial BWP. Summary of the invention

[0003] The embodiments of the present application provide a PUSCH resource allocation method, device, and electronic device, which can ensure that the network side and the terminal have consistent understanding of PUSCH allocation resources.

[0004] In a first aspect, an embodiment of the present application provides a PUSCH resource allocation method, which is applied to a terminal, and the method includes:

[0005] Acquire downlink control information or a random access response uplink grant message, where the downlink control information or the random access response uplink grant message explicitly or implicitly indicates a resource block set allocated by a PUSCH;

[0006] A resource block set allocated to a scheduled PUSCH is determined according to the downlink control information or the random access response uplink grant message.

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

[0008] Downlink control information or a random access response uplink grant message is sent to the terminal, where the downlink control information or the random access response uplink grant message explicitly or implicitly indicates a resource block set allocated by the PUSCH.

[0009] In a third aspect, an embodiment of the present application provides a PUSCH resource allocation device, applied to a terminal, the device comprising:

[0010] An acquisition module, configured to acquire downlink control information or a random access response uplink grant message, wherein the downlink control information or the random access response uplink grant message explicitly or implicitly indicates a resource block set allocated by a PUSCH;

[0011] A processing module is used to determine a resource block set allocated to a scheduled PUSCH according to the downlink control information or the random access response uplink grant message.

[0012] In a fourth aspect, an embodiment of the present application further provides a PUSCH resource allocation device, which is applied to a network side device, and the device includes:

[0013] The sending module is used to send downlink control information or a random access response uplink grant message to the terminal, wherein the downlink control information or the random access response uplink grant message explicitly or implicitly indicates a resource block set allocated by the PUSCH.

[0014] In a fifth aspect, an embodiment of the present application further provides an electronic device, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction implements the steps of the method described above when executed by the processor.

[0015] In a sixth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and the program or instruction, when executed by a processor, implements the steps of the method described above.

[0016] In the seventh aspect, an embodiment of the present application provides a chip, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the methods described in the first and second aspects.

[0017] In an embodiment of the present application, the network side device can explicitly or implicitly indicate the resource block set allocated by PUSCH through downlink control information or a random access response uplink authorization message. After obtaining the downlink control information or the random access response uplink authorization message, the terminal can determine the resource block set allocated by the scheduled PUSCH according to the downlink control information or the random access response uplink authorization message, thereby ensuring the effectiveness of the communication system and avoiding the problem of inconsistent understanding of resource allocation between the network side device and the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0019] Figure 1 A schematic diagram showing a wireless communication system;

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

[0021] Figure 4 and Figure 5 Indicates the correspondence between the BWP and the resource block set in the embodiment of the present application;

[0022] Figure 6 and Figure 7 A schematic diagram showing the structure of a PUSCH resource allocation device according to an embodiment of the present application;

[0023] Figure 8 A terminal block diagram showing an embodiment of the present application;

[0024] Fig. 9 A block diagram of a network-side device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

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

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

[0027] The technology described herein is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used for various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA). UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system can implement radio technologies such as Global System for Mobile Communication (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS). LTE and more advanced LTE (such as LTE-A) are new UMTS versions that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).The techniques described herein may be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. However, the following description describes an NR system for example purposes and uses NR terminology in much of the following description, although the techniques may also be applicable to applications other than NR system applications.

[0028] The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the spirit and scope of the present disclosure. Various examples may appropriately omit, replace, or add various procedures or components. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

[0029] See also Figure 1 , Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 may also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal 11 may be a terminal side device such as a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (Personal Digital Assistant, PDA), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the above-mentioned base station can be a base station of 5G and later versions (for example: gNB, 5G NR NB, etc.), or a base station in other communication systems (for example: eNB, WLAN access point, or other access point, etc.), or a location server (for example: E-SMLC or LMF (Location Manager Function)), wherein the base station can be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the embodiment of the present application does not limit the specific type of the base station and the specific communication system.

[0030] In future communication systems, unlicensed bands can be used as a supplement to licensed bands to help operators expand services. Since unlicensed bands are shared by multiple radio access technologies (Radio Access Technology, RAT), such as Wi-Fi, radar, and LTE-based Licensed-Assisted Access (LTE-LAA), in some countries or regions, unlicensed bands must comply with regulatory regulations when used to ensure that all devices can share the resource fairly. Before sending information, the terminal or network-side device needs to perform channel idle estimation (Clear Channel Assess, CCA) and / or extended Clear Channel Assess (Extended Clear Channel Assess, eCCA) to listen to the channel, that is, perform energy detection (Energy Detection, ED). When the energy is lower than a certain threshold, the channel is judged to be empty before transmission can begin, that is, listen before talk (LBT). For example, Listen Before Talk (LBT), Maximum Channel Occupancy Time (MCOT), etc. The transmission node can be a base station, a terminal (UE), a Wi-Fi access point (AP), etc. After the transmission node starts transmitting, the channel time occupied cannot exceed MCOT.

[0031] At the same time, the CCA frequency domain granularity on 5GHz is 20MHz, and it is strictly implemented according to the prescribed (Regulation) channel planning.

[0032] In the unlicensed spectrum, in order to meet the OCB (Occupied Channel Bandwidth) and to increase the transmit power while meeting the PSD (power spectral density), a resource allocation based on an interlace structure, namely type 2 UL resource allocation, is designed. The frequency domain resources are divided into different interlaces, and resource allocation is performed in units of interlaces. The number of interlaces contained in a bandwidth part (Bandwidth part, BWP) is only related to the subcarrier spacing. For example, when the subcarrier spacing is 15kHz, the number of interlaces M is 10 (that is, the spacing between two adjacent physical resource blocks (Physical Resource Block, PRB) in an interlace), and the number of PRBs contained in each interlace is related to the bandwidth. For example, when the bandwidth is 20MHz, the total number of PRBs in the bandwidth is 106, and each interlace contains 10 / 11 PRBs. When the subcarrier spacing is 30kHz, the number of interlaces M is 5. The number of PRBs contained in each interlace is related to the bandwidth. For example, when the bandwidth is 20MHz, the total number of PRBs in the bandwidth is 51, and each interlace contains 10 / 11 PRBs. Table 1 shows the maximum transmission bandwidth configuration (Maximum transmission bandwidth configuration NRB), where SCS is the subcarrier spacing and NRB is the total number of PRBs in the bandwidth.

[0033] Table 1

[0034]

[0035]

[0036] In order to indicate the interlace allocated to the UE, when allocating resources, when the subcarrier spacing is 30kHz, a 5-bit bitmap can be used to indicate which interlaces are allocated to the UE; when the subcarrier spacing is 15kHz, a 6-bit resource indicator value (RIV) can be used to indicate which interlaces are allocated to the UE.

[0037] As mentioned above, in the unlicensed spectrum (NRU), the channel is listened before transmission (Listen Before Talk, LBT). Since the frequency domain granularity of CCA (LBT) on 5GHz is 20MHz, the resource allocation in NRU needs to be performed in units of the frequency domain granularity of LBT, such as 20MHz, 40MHz, 60MHz, and 80MHz. When the BWP bandwidth is greater than one LBT bandwidth, when scheduling the physical uplink shared channel (PUSCH) transmission, the base station can schedule the PUSCH to be transmitted on part of the BWP, that is, by indicating the allocated LBT bandwidth (or resource block set (RB set), one RB set corresponds to one LBT bandwidth) to schedule PUSCH to be transmitted on all or part of the BWP. The UE determines the PRB resources allocated to the PUSCH based on the indicated interlace, RB set, and intra-carrier guard band (RRC configuration or protocol provisions).

[0038] After the UE sends the physical random access channel (PRACH), the UE will detect the downlink control information (DCI) format 1_0 scrambled by the user identity (RA-RANTI) used for the random access process within a time window. If the UE detects the DCI format 1_0 scrambled by RA-RANTI and the corresponding transport block (TB) transmitted by the physical downlink shared channel (PDSCH) within the time window, the UE will pass the TB to the upper layer, and the upper layer will parse the TB. Each PRACH is associated with a random access preamble identifier (RAPID). If the upper layer identifies the RAPID in the random access response (RAR) information of the TB, the upper layer indicates an uplink grant (UL grant) to the physical layer. The UL grant is called RAR UL grant in the physical layer.

[0039] One RAR UL grant schedules one PUSCH transmission. Table 2 shows the contents of the RAR UL grant, starting from the most significant bit (MSB) to the least significant bit (LSB).

[0040] Table 2

[0041]

[0042] In the relevant communication protocol, the RAR UL grant contains 14 bits to indicate the frequency domain resource allocation. For an active UL BWP, if the RAR UL grant schedules a PUSCH transmission, the UE determines the frequency domain resources allocated to the PUSCH in the active UL BWP in the following manner:

[0043] (1) If the active UL BWP and the initial UL BWP have the same SCS and the same cyclic prefix (CP) length, and the active UL BWP contains all RBs of the initial UL BWP, or the active UL BWP is the initial UL BWP, the initial UL BWP is used;

[0044] (2) Otherwise, the numbering starts from the first RB of the acitve UL BWP, and the maximum number of RBs allocated in the frequency domain is equal to the number of RBs in the initial UL BWP.

[0045] The RAR UL grant in the NRU contains 12 bits to indicate the frequency domain resource allocation, wherein the X bit (if the SCS of the active BWP is 15 kHz, X=6; if the SCS of the active BWP is 30 kHz, X=5) is used to indicate the allocated interlace.

[0046] In NRU type2 uplink resource allocation, PUSCH resource allocation not only needs to indicate the allocated interlace, but also needs to determine the allocated RB set. For TC-RNTI scrambled DCI 0_0 and RAR UL grant-scheduled PUSCH, how to determine its resource allocation needs to be solved.

[0047] The embodiment of the present application provides a physical uplink shared channel PUSCH resource allocation method, which is applied to a terminal, such as Figure 2 As shown, the method includes:

[0048] Step 101: obtaining downlink control information or a random access response uplink grant message, wherein the downlink control information or the random access response uplink grant message explicitly or implicitly indicates a resource block set allocated by a PUSCH;

[0049] Step 102: Determine a resource block set allocated for a scheduled PUSCH according to the downlink control information or the random access response uplink grant message.

[0050] In an embodiment of the present application, the network side device can explicitly or implicitly indicate the resource block set allocated by PUSCH through downlink control information or a random access response uplink authorization message. After obtaining the downlink control information or the random access response uplink authorization message, the terminal can determine the resource block set allocated by the scheduled PUSCH according to the downlink control information or the random access response uplink authorization message, thereby ensuring the effectiveness of the communication system and avoiding the problem of inconsistent understanding of resource allocation between the network side device and the terminal.

[0051] Among them, the explicit indication is that the downlink control information or the random access response uplink authorization message includes indication information for indicating the resource block set allocated to the PUSCH; the implicit indication is that the downlink control information or the random access response uplink authorization message does not include indication information for indicating the resource block set allocated to the PUSCH, and the resource block set allocated to the PUSCH scheduled by the downlink control information or the random access response uplink authorization message is determined according to the implicit method.

[0052] In some embodiments, the acquiring of downlink control information or random access response uplink grant message includes any one of the following:

[0053] Acquire downlink control information in a common search space, where the downlink control information includes Y bits of PUSCH resource allocation indication information;

[0054] The random access response uplink grant message (RAR UL grant) is obtained, where the random access response uplink grant message includes Y bits of PUSCH resource allocation indication information.

[0055] The Y-bit PUSCH resource allocation indication information refers to indication information used to indicate the allocation of a PUSCH resource block set.

[0056] The random access response uplink authorization message in the embodiment of the present application is not necessarily sent directly from the network side device (such as a base station) to the physical layer of the terminal device, but can also be sent indirectly, such as by high-level analysis of the terminal to parse the information received from the network side device and then pass the uplink authorization message to the physical layer.

[0057] In some embodiments, the size of Y satisfies any of the following:

[0058] The size of Y is determined by the number of resource block sets included in the activated uplink bandwidth part or the initial uplink bandwidth part;

[0059] The size of Y is fixed, such as 4;

[0060] The size of Y is determined according to the bandwidth of the scheduled carrier or the number of resource blocks included, for example, according to the formula log 2 (n(n+1) / 2), where n represents the number of RB sets contained in the carrier.

[0061] In an embodiment of the present application, the downlink control information may include Y bits of PUSCH resource allocation indication information, and the downlink control information may be specifically DCI 0_0 in the common search space, which is used for uplink PUSCH scheduling of the cell; or the downlink control information may not include PUSCH resource allocation indication information; or the random access response uplink authorization message may include Y bits of PUSCH resource allocation indication information.

[0062] In some embodiments, if the downlink control information is encrypted using a temporary radio network temporary identifier TC-RNTI, the terminal ignores the Y-bit PUSCH resource allocation indication information in the downlink control information; or the terminal does not expect the network side device to instruct the terminal to allocate more than one resource block set.

[0063] The terminal ignores the Y-bit PUSCH resource allocation indication information in the downlink control information, indicating that there are Y bits when determining the DCI size and the size of each field, but the Y bits are not used to indicate any valid information or are not used to indicate the RB set allocation of the PUSCH.

[0064] In some embodiments, when the terminal receives DCI 0_0 encrypted with TC-RNTI, if the activated uplink bandwidth part has the same subcarrier spacing and cyclic prefix length as the initial uplink bandwidth part, and the activated uplink bandwidth part includes all resource blocks of the initial uplink bandwidth part, the terminal ignores the Y-bit PUSCH resource allocation indication information in the downlink control information; otherwise, the terminal determines the allocated RB set according to the Y-bit PUSCH resource allocation indication information in the downlink control information.

[0065] The downlink control information may be scrambled using TC-RNTI.

[0066] The size of Y is determined by the number of resource block sets included in the activated uplink bandwidth part or the initial uplink bandwidth part.

[0067] In some embodiments, if the downlink control information does not include PUSCH resource allocation indication information or the terminal ignores the PUSCH resource allocation indication information in the downlink control information, the terminal determines the resource block set allocated to the PUSCH scheduled by the downlink control information according to any one of the following:

[0068] If the activated uplink bandwidth part has the same subcarrier spacing and cyclic prefix length as the initial uplink bandwidth part, and the activated uplink bandwidth part includes all resource blocks of the initial uplink bandwidth part, the resource block set allocated by the PUSCH is the first resource block set corresponding to the initial uplink bandwidth part, otherwise the resource block set allocated by the PUSCH is the first resource block set (such as RB set 0) of the activated uplink bandwidth part;

[0069] If the second resource block set of the activated uplink bandwidth part and the third resource block set where the downlink control information in the activated downlink bandwidth part is located have an intersection, the resource block set allocated by the PUSCH is the intersection, otherwise the resource block set allocated by the PUSCH is the first resource block set (such as RB set 0) of the activated uplink bandwidth part;

[0070] If the activated uplink bandwidth part has the same subcarrier spacing and cyclic prefix length as the initial uplink bandwidth part, and the activated uplink bandwidth part contains all resource blocks of the initial uplink bandwidth part, the resource block set allocated by the PUSCH is the first resource block set corresponding to the initial uplink bandwidth part; otherwise, the resource block set allocated by the PUSCH is the intersection part; if the intersection part does not exist, the resource block set allocated by the PUSCH is the first resource block set (such as RBset 0) of the activated uplink bandwidth part.

[0071] In some embodiments, if the second resource block set of the activated uplink bandwidth part and the third resource block set where the downlink control information in the activated downlink bandwidth part is located have an intersection, then the resource block set allocated by the PUSCH is the intersection and includes any one of the following items:

[0072] If the second resource block set of the activated uplink bandwidth part and the third resource block set where the first resource element group REG of the downlink control information in the activated downlink bandwidth part is located have an intersection, then the resource block set allocated by the PUSCH is the intersection; otherwise, that is, if the second resource block set of the activated uplink bandwidth part and the third resource block set where the first resource element group REG of the downlink control information in the activated downlink bandwidth part is located do not have the intersection, the resource block set allocated by the PUSCH is the first resource block set (such as RB set 0) of the activated uplink bandwidth part;

[0073] If the second resource block set of the activated uplink bandwidth part and the third resource block set where the downlink control information in the activated downlink bandwidth part is located have an intersection, the resource block set allocated by the PUSCH is the first resource block set (such as RB set 0) of the intersection.

[0074] In some embodiments, if the downlink control information includes Y bits of PUSCH resource allocation indication information, the Y bits of PUSCH resource allocation indication information are indicated on the entire carrier, that is, the size of the Y bits is determined according to the bandwidth of the carrier or the number of RB sets included or is fixed, such as 4, and the index of the starting resource block set of the resource block set indicated by the Y bit information is the number of the resource block set in the carrier, that is, the starting RB set, the RB set number, etc. are all performed within the carrier.

[0075] In an embodiment of the present application, the UE may determine the RB set allocated by the PUSCH and the corresponding VRB n according to the PUSCH resource allocation indication information of Y bits in DCI 0_0; if Y depends on the carrier bandwidth or the number of RB sets, the RB set allocated by the PUSCH may be the intersection RB set of the RB set allocated by the PUSCH resource allocation indication information of Y bits and the RB set of the initial (initial) and / or activated (active) BWP; or the RB set allocated by the PUSCH may be the first RB set of the intersection RB set of the RB set allocated by the PUSCH resource allocation indication information of Y bits and the RB set of the initial (initial) and / or activated (active) BWP.

[0076] In some embodiments, the UE may determine the RB set allocated by the PUSCH according to the PUSCH resource allocation indication information of Y bits in the DCI 0_0 of the common search space. If Y depends on the carrier bandwidth or the number of RB sets, if the RNTI corresponding to the DCI 0_0 of the common search space is C-RNTI, MCS-C-RNTI or CS-RNTI, the RB set allocated by the PUSCH may be the RB set allocated indicated by the PUSCH resource allocation indication information of Y bits; if the RNTI corresponding to the DCI 0_0 of the common search space is TC-RNTI, the RB set allocated by the PUSCH may be the intersection RB set of the RB set allocated indicated by the PUSCH resource allocation indication information of Y bits and the RB set of the initial and / or active BWP; or the RB set allocated by the PUSCH may be the first RB set of the intersection RB set of the RB set allocated indicated by the PUSCH resource allocation indication information of Y bits and the RB set of the initial and / or active BWP.

[0077] In some embodiments, the UE may determine the RB set allocated by the PUSCH based on the PUSCH resource allocation indication information of the Y bits in the DCI 0_0 of the common search space. If Y depends on the carrier bandwidth or the number of RB sets, for the PUSCH scheduled by the DCI 0_0 of the common search space, the PUSCH resource allocation indication information of the Y bits is indicated on the entire carrier, that is, the size of the Y bits is determined or fixed based on the bandwidth of the carrier or the number of RB sets included, such as 4, and the index of the starting resource block set of the resource block set indicated by the Y bit information is the number of the resource block set in the carrier.

[0078] In some embodiments, the UE may determine the RB set allocated by the PUSCH based on the PUSCH resource allocation indication information of the Y bits in the DCI 0_0 of the common search space. If Y depends on the carrier bandwidth or the number of RB sets, if the RNTI corresponding to the DCI 0_0 of the common search space is C-RNTI, MCS-C-RNTI or CS-RNTI, the RB set indicated by Y is indicated within the activeUL BWP, that is, the starting RB set index indicated by Y is an offset relative to the first RB set of the active UL BWP; if the RNTI corresponding to the DCI 0_0 of the common search space is TC-RNTI, the PUSCH resource allocation indication information of the Y bits is indicated on the entire carrier, that is, the size of the Y bits is determined or fixed according to the bandwidth of the carrier or the number of RB sets contained, such as 4, and the index of the starting resource block set of the resource block set indicated by the Y bit information is the number of the resource block set within the carrier.

[0079] In some embodiments, the method further includes determining a physical resource block PRB corresponding to a virtual resource block VRB, and in the mapping of VRB to PRB, for a PUSCH scheduled by downlink control information encrypted by TC-RNTI, if the activated uplink bandwidth part has the same subcarrier spacing and cyclic prefix length as the initial uplink bandwidth part, and the activated uplink bandwidth part includes all resource blocks of the initial uplink bandwidth part, then VRB n is mapped to PRB Where n is a natural number, Indicates the starting resource block index of the initial uplink bandwidth part. ), Indicates the starting resource block index of the allocated RB set in active uplink bandwidth part j starting at ).

[0080] In some embodiments, if the random access response uplink grant message includes Y bits of the PUSCH resource allocation indication information, the terminal may not expect the network side device to instruct the terminal to allocate more than one resource block set.

[0081] In some embodiments, if the random access response uplink authorization message includes Y bits of the PUSCH resource allocation indication information, the Y bits of the PUSCH resource allocation indication information are indicated on the entire carrier, that is, the size of the Y bits is determined according to the bandwidth of the carrier or the number of RB sets included or is fixed, such as 4, and the index of the starting resource block set of the resource block set indicated by the Y bit information is the number within the carrier, that is, the starting RB set, the RB set number, etc. are all performed within the carrier.

[0082] In an embodiment of the present application, the UE can determine the RB set allocated by PUSCH based on the Y-bit PUSCH resource allocation indication information in the RAR UL grant; the allocated RB set can be the intersection RB set of the allocated RB set indicated by the Y-bit PUSCH resource allocation indication information and the RB set of the initial (initial) and / or activated (active) BWP, or the RB set allocated by PUSCH can be the first RB set of the intersection RB set of the allocated RB set indicated by the Y-bit PUSCH resource allocation indication information and the RB set of the initial (initial) and / or activated (active) BWP.

[0083] In some embodiments, the method further includes determining a physical resource block PRB corresponding to a virtual resource block VRB, and in the mapping of VRB to PRB, for a PUSCH scheduled by a random access response uplink grant message, if the activated uplink bandwidth part has the same subcarrier spacing and cyclic prefix length as the initial uplink bandwidth part, and the activated uplink bandwidth part includes all resource blocks of the initial uplink bandwidth part, then VRB n is mapped to PRB Where n is a natural number, Indicates the starting resource block index of the initial uplink bandwidth part. ), Indicates the starting resource block index of the PUSCH allocated RB set in active uplink bandwidth part j starting at ).

[0084] In some embodiments, for the PUSCH scheduled by the DCI 0_0 or RAR UL grant scrambled by the TC-RNTI, if the resource block set allocated by the PUSCH is the first resource block set corresponding to the initial uplink bandwidth part, or the activated uplink bandwidth part has the same subcarrier spacing and cyclic prefix length as the initial uplink bandwidth part and the activated uplink bandwidth part includes all resource blocks of the initial uplink bandwidth part,

[0085] The terminal determines the resource blocks allocated by the PUSCH using an intra-cell guard band corresponding to the initial uplink bandwidth portion.

[0086] The embodiment of the present application also provides a physical uplink shared channel PUSCH resource allocation method, which is applied to a network side device, such as Figure 3 As shown, the method includes:

[0087] Step 201: Send downlink control information or a random access response uplink grant message to a terminal, wherein the downlink control information or the random access response uplink grant message explicitly or implicitly indicates a resource block set allocated by a PUSCH.

[0088] In an embodiment of the present application, the network side device can explicitly or implicitly indicate the resource block set allocated by PUSCH through downlink control information or a random access response uplink authorization message. After obtaining the downlink control information or the random access response uplink authorization message, the terminal can determine the resource block set allocated by the scheduled PUSCH according to the downlink control information or the random access response uplink authorization message, thereby ensuring the effectiveness of the communication system and avoiding the problem of inconsistent understanding of resource allocation between the network side device and the terminal.

[0089] Among them, the explicit indication is that the downlink control information or the random access response uplink authorization message includes indication information for indicating the resource block set allocated to the PUSCH; the implicit indication is that the downlink control information or the random access response uplink authorization message does not include indication information for indicating the resource block set allocated to the PUSCH, but the resource block set allocated to the PUSCH scheduled by the downlink control information or the random access response uplink authorization message can still be determined according to the implicit method.

[0090] In some embodiments, the downlink control information includes Y bits of PUSCH resource allocation indication information; or

[0091] The random access response uplink grant message includes Y bits of PUSCH resource allocation indication information.

[0092] The random access response uplink authorization message in the embodiment of the present application is not necessarily sent directly from the network side device (such as a base station) to the physical layer of the terminal device, but can also be sent indirectly, such as by high-level analysis of the terminal to parse the information received from the network side device and then pass the uplink authorization message to the physical layer.

[0093] In some embodiments, the size of Y satisfies any of the following:

[0094] The size of Y is determined by the number of resource block sets included in the activated uplink bandwidth part or the initial uplink bandwidth part;

[0095] The size of Y is fixed;

[0096] The size of Y is determined according to the bandwidth of the scheduled carrier or the number of resource block sets included.

[0097] In an embodiment of the present application, the downlink control information may include Y bits of PUSCH resource allocation indication information, and the downlink control information may be specifically DCI 0_0 in the common search space, which is used for uplink PUSCH scheduling of the cell; or the downlink control information may not include PUSCH resource allocation indication information; or the random access response uplink authorization message may include Y bits of PUSCH resource allocation indication information.

[0098] In some embodiments, if the downlink control information includes Y bits of PUSCH resource allocation indication information, the index of the starting resource block set of the resource block set indicated by the Y bits of the PUSCH resource allocation indication information is the number in the carrier, that is, the starting RB set, that is, the number of the RB set is performed in the carrier;

[0099] If the random access response uplink grant message includes Y bits of the PUSCH resource allocation indication information, the index of the starting resource block set of the resource block set indicated by the Y bits of the PUSCH resource allocation indication information is the number within the carrier, that is, the RB set numbering is performed within the carrier.

[0100] The downlink control information may be scrambled using TC-RNTI.

[0101] In an embodiment of the present application, the UE can determine the RB set allocated by the PUSCH and the corresponding VRB n according to the PUSCH resource allocation indication information of Y bits in DCI 0_0; if Y depends on the number of RB sets of the carrier, the allocated RB set can be the intersection RB set of the RB set allocated by the PUSCH resource allocation indication information of Y bits and the RB set of the initial and / or active BWP; in addition, if Y depends on the number of RB sets of the carrier, the VRB can also be the intersection RB set of the RB set allocated by the PUSCH resource allocation indication information of Y bits and the RB set of the initial and / or active BWP.

[0102] In an embodiment of the present application, the UE can determine the RB set allocated by PUSCH based on the Y-bit PUSCH resource allocation indication information in the RAR UL grant; the allocated RB set can be the intersection RB set of the allocated RB set indicated by the Y-bit PUSCH resource allocation indication information and the RB set of the initial (initial) and / or activated (active) BWP; or the RB set allocated by PUSCH can be the first RB set of the intersection RB set of the allocated RB set indicated by the Y-bit PUSCH resource allocation indication information and the RB set of the initial (initial) and / or activated (active) BWP.

[0103] The technical solution of the present invention is further described below in conjunction with the accompanying drawings and specific embodiments:

[0104] Embodiment 1

[0105] For type 2 uplink resource allocation, the UE determines the RB allocated in the frequency domain according to the allocated interlace, RB set and intra-cell guard band, where the intra-cell guard band of the initial UL BWP is specified by the protocol or configured by the system message, and the intra-cell guard band of the active UL BWP is configured by the radio resource control (RRC) message. For the PUSCH scheduled by the TC-RNTI scrambled DCI 0_0, or the RAR UL grant, since the network side equipment (such as the base station) cannot distinguish whether the UE is in the RRC connected state or the idle state when sending the corresponding scheduling signaling, it is impossible to distinguish whether the UE is working in the active UL BWP or the initial UL BWP, and thus it is impossible to distinguish the number of intra-cell guard bands and on which PRBs the UE transmits the PUSCH. Therefore, it is necessary to solve the problem of inconsistent understanding between the base station and the UE.

[0106] Therefore, in this embodiment, when the active UL BWP includes all RBs of the initial UL BWP and the active ULBWP and the initial UL BWP have the same SCS and CP length, and the RB set allocated by PUSCH is the initial UL BWP, the UE always determines the RB allocated by PUSCH according to the intra-cell guard band corresponding to the initial UL BWP.

[0107] Embodiment 2:

[0108] For type 2 uplink resource allocation, the UE needs to determine the RBs allocated in the frequency domain based on the allocated interlace, RB set, and intra-cellguard band. When indicating the allocated RB set, such as Figure 4 As shown in FIG. 1 , if a BWP includes multiple RB sets, the PUSCH resource allocation indication information containing Y bits in the DCI indicates which RB sets are allocated, that is, Y indicates the resource indication value (RIV), Y = log 2 (n(n+1) / 2), where n represents the number of RB sets configured on the BWP, and Y indicates the starting RB set and the number of RB sets, as follows:

[0109]

[0110] The resource indicator value corresponds to the starting RB set (RBsetSTART ) and the number of consecutively allocated resource block sets L RBset (L RBset ≥1). The resource indicator value can be obtained by the following methods;

[0111] if So

[0112]

[0113] otherwise,

[0114]

[0115] However, the instructions of RB set are all carried out within a BWP, that is, RBset START is the offset of RB set 0 relative to BWP, L RBset It indicates the number of consecutive RB sets allocated, for example, RBset START =0,L RBset =2, it means that two RB sets starting from the 0th in the BWP, namely RB set 0 and RB set 1, are allocated.

[0116] However, if the base station sends the RAR UL grant and the TC-RNTI scrambled DCI 0_0, it may not be able to distinguish which UE it is, and therefore cannot know which active UL BWP it corresponds to. Figure 5 As shown in the figure, on a carrier containing 4 RB sets, UE 1's BWP1 corresponds to the first 2 RB sets of the carrier, and each RB set is numbered RB set 0 and RB set 1 in BWP 1; UE 2's BWP2 corresponds to the last 3 RB sets of the carrier, and each RB set is numbered RB set 0, RBset 1, and RB set 2 in BWP 1. When RIV is indicated in the RAR UL grant RBset =0, corresponding to RBset START =0,L RBset =1, UE1 will think that the allocation is the first RB set in BWP 1, that is, RB set 0 in the figure, and UE2 will think that the allocation is the first RB set in BWP 2, that is, RB set 1 in the figure. In this way, the base station cannot know on which RB set the UE will transmit PUSCH. Therefore, a certain method is needed to avoid the blind detection problem of the base station.

[0117] In this embodiment, the RAR UL grant includes Y bits of PUSCH resource allocation indication information, where Y indicates the RB set allocated on the entire carrier, that is, the UE RBset Determined RBset START The offset relative to the first RB set of the carrier. For example, when RIV is indicated in the RAR UL grant RBset =1, corresponding to RBset START =1,L RBset =1, then UE 1 and UE2 both understand that the allocation is RB set 1 on the carrier, thus avoiding the blind detection problem of the base station.

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

[0119] The PUSCH resource allocation device of the embodiment of the present application is applied to the terminal 300, such as Figure 6 As shown, the device comprises:

[0120] An acquisition module 310 is configured to acquire downlink control information or a random access response uplink grant message, wherein the downlink control information or the random access response uplink grant message explicitly or implicitly indicates a resource block set allocated by a PUSCH;

[0121] The processing module 320 is configured to determine a resource block set allocated to the scheduled PUSCH according to the downlink control information or the random access response uplink grant message.

[0122] In some embodiments, the processing module 320 is specifically configured to perform any of the following:

[0123] Acquire downlink control information in a common search space, where the downlink control information includes Y bits of PUSCH resource allocation indication information;

[0124] The random access response uplink grant message is obtained, where the random access response uplink grant message includes Y bits of PUSCH resource allocation indication information.

[0125] In some embodiments, the size of Y satisfies any of the following:

[0126] The size of Y is determined by the number of resource block sets included in the activated uplink bandwidth part or the initial uplink bandwidth part;

[0127] The size of Y is fixed;

[0128] The size of Y is determined according to the bandwidth of the scheduled carrier or the number of resource block sets included.

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

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

[0131] The PUSCH resource allocation device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the PUSCH resource allocation method in the method embodiment are not described here to avoid repetition.

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

[0133] The PUSCH resource allocation device of the embodiment of the present application is applied to a network side device 400, such as Figure 7 As shown, the device comprises:

[0134] The sending module 410 is configured to send downlink control information or a random access response uplink grant message to the terminal, wherein the downlink control information or the random access response uplink grant message explicitly or implicitly indicates a resource block set allocated by the PUSCH.

[0135] In some embodiments, the downlink control information includes Y bits of PUSCH resource allocation indication information; or

[0136] The random access response uplink grant message includes Y bits of PUSCH resource allocation indication information.

[0137] In some embodiments, the size of Y satisfies any of the following:

[0138] The size of Y is determined by the number of resource block sets included in the activated uplink bandwidth part or the initial uplink bandwidth part;

[0139] The size of Y is fixed;

[0140] The size of Y is determined according to the bandwidth of the scheduled carrier or the number of resource block sets included.

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

[0142] The PUSCH resource allocation device provided in the embodiment of the present application can achieve Figure 3 The various processes implemented by the PUSCH resource allocation method in the method embodiment are not described here to avoid repetition.

[0143] Optionally, an embodiment of the present application also provides an electronic device, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, the various processes of the embodiment of the above-mentioned PUSCH resource allocation method are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0144] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0145] The electronic device of this embodiment may be a terminal. Figure 8In order to implement the hardware structure diagram of a terminal in each embodiment of the present application, the terminal 50 includes but is not limited to: a radio frequency unit 51, a network module 52, an audio output unit 53, an input unit 54, a sensor 55, a display unit 56, a user input unit 57, an interface unit 58, a memory 59, a processor 510, and a power supply 511. Those skilled in the art can understand that Figure 8 The terminal structure shown in the figure does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. In the embodiments of the present application, the terminal includes but is not limited to a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted terminal, a wearable device, and a pedometer.

[0146] It should be understood that in the embodiment of the present application, the radio frequency unit 51 can be used for receiving and sending signals during information transmission or calls. Specifically, after receiving downlink data from the base station, it is sent to the processor 510 for processing; in addition, uplink data is sent to the base station. Generally, the radio frequency unit 51 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. In addition, the radio frequency unit 51 can also communicate with the network and other devices through a wireless communication system.

[0147] The memory 59 can be used to store software programs and various data. The memory 59 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 59 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0148] The processor 510 is the control center of the terminal. It uses various interfaces and lines to connect various parts of the entire terminal. It executes various functions of the terminal and processes data by running or executing software programs and / or modules stored in the memory 59, and calling data stored in the memory 59, so as to monitor the terminal as a whole. The processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 510.

[0149] The terminal 50 may also include a power supply 511 (such as a battery) for supplying power to various components. Preferably, the power supply 511 may be logically connected to the processor 510 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system.

[0150] In addition, the terminal 50 includes some functional modules not shown, which will not be described in detail here.

[0151] The electronic device of this embodiment may also be a network side device. Fig. 9 As shown, the network side device 600 includes: an antenna 61, a radio frequency device 62, and a baseband device 63. The antenna 61 is connected to the radio frequency device 62. In the uplink direction, the radio frequency device 62 receives information through the antenna 61 and sends the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes the information to be sent and sends it to the radio frequency device 62. The radio frequency device 62 processes the received information and sends it out through the antenna 61.

[0152] The frequency band processing device may be located in a baseband device 63 . The method performed by the network-side device in the above embodiment may be implemented in the baseband device 63 . The baseband device 63 includes a processor 64 and a memory 65 .

[0153] The baseband device 63 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig. 9 As shown, one of the chips is, for example, a processor 64, which is connected to a memory 65 to call a program in the memory 65 to execute the network-side device operations shown in the above method embodiment.

[0154] The baseband device 63 may further include a network interface 66 for exchanging information with the radio frequency device 62 . The interface may be, for example, a common public radio interface (CPRI).

[0155] The processor here can be a processor or a collective name for multiple processing elements. For example, the processor can be a CPU, an ASIC, or one or more integrated circuits configured to implement the method executed by the above network-side device, such as one or more microprocessors DSP, or one or more field programmable gate arrays FPGA, etc. The storage element can be a memory or a collective name for multiple storage elements.

[0156] The memory 65 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DRRAM). The memory 65 described in the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0157] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the embodiment of the above-mentioned PUSCH resource allocation method are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0159] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement each process of the embodiment of the above-mentioned PUSCH resource allocation method, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

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

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

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

Claims

1. A method for allocating physical uplink shared channel (PUSCH) resources. It is characterized in that Applied to a terminal, the method comprises: Acquire downlink control information, where the downlink control information implicitly indicates a resource block set allocated by a PUSCH; Determine a resource block set allocated to a scheduled PUSCH according to the downlink control information; The terminal determines a resource block set allocated to the PUSCH scheduled by the downlink control information according to the following method: If the second resource block set of the activated uplink bandwidth part and the third resource block set where the first resource element group REG of the downlink control information in the activated downlink bandwidth part is located have an intersection, the resource block set allocated by the PUSCH is the first resource block set of the intersection.

2. The PUSCH resource allocation method according to claim 1, It is characterized in that The downlink control information indicates a resource block set allocated to the PUSCH; and obtaining the downlink control information includes: Downlink control information in a common search space is obtained, where the downlink control information includes Y bits of PUSCH resource allocation indication information.

3. The PUSCH resource allocation method according to claim 2, It is characterized in that The size of Y satisfies any of the following: The size of Y is determined by the number of resource block sets included in the activated uplink bandwidth part or the initial uplink bandwidth part; The size of Y is fixed; The size of Y is determined according to the bandwidth of the scheduled carrier or the number of resource block sets included.

4. The PUSCH resource allocation method according to claim 2, It is characterized in that If the downlink control information is scrambled using a temporary radio network temporary identifier TC-RNTI, the terminal ignores the Y-bit PUSCH resource allocation indication information in the downlink control information; or the terminal does not expect the network side device to instruct the terminal to allocate more than one resource block set.

5. The PUSCH resource allocation method according to claim 2, It is characterized in that The index of the starting resource block set of the resource block set indicated by the Y-bit PUSCH resource allocation indication information is a number within a carrier.

6. The PUSCH resource allocation method according to claim 5, It is characterized in that The downlink control information is scrambled using TC-RNTI.

7. The PUSCH resource allocation method according to claim 1, It is characterized in that The downlink control information is DCI in a common search space, and the downlink control information does not include indication information of PUSCH resource block set allocation.

8. The PUSCH resource allocation method according to claim 7, It is characterized in that The downlink control information is specifically DCI 0_0 in the common search space.

9. The PUSCH resource allocation method according to claim 1, It is characterized in that The downlink control information is scrambled using C-RNTI, MCS-C-RNTI or CS-RNTI.

10. The PUSCH resource allocation method according to claim 2, It is characterized in that The resource block set allocated by the PUSCH is an intersection of the resource block set allocated by the PUSCH resource allocation indication information and the resource block set of the activated uplink bandwidth part and / or the initial uplink bandwidth part; Or the resource block set allocated by the PUSCH is the first resource block set of the intersection of the resource block set allocated by the PUSCH resource allocation indication information and the resource block set of the activated uplink bandwidth part and / or the initial uplink bandwidth part.

11. The PUSCH resource allocation method according to claim 1, It is characterized in that The method further includes determining a physical resource block PRB corresponding to the virtual resource block VRB, wherein the determining the physical resource block PRB corresponding to the VRB includes: For PUSCH scheduled by TC-RNTI scrambled downlink control information, if the activated uplink bandwidth part has the same subcarrier spacing and cyclic prefix length as the initial uplink bandwidth part, and the activated uplink bandwidth part contains all resource blocks of the initial uplink bandwidth part, VRB n is mapped to PRB Where n is a natural number, Indicates the starting resource block index of the initial uplink bandwidth part, Indicates the starting resource block index of the resource block set allocated to PUSCH.

12. The PUSCH resource allocation method according to claim 2, It is characterized in that If the resource block set allocated by the PUSCH is the first resource block set corresponding to the initial uplink bandwidth part, or the activated uplink bandwidth part has the same subcarrier spacing and cyclic prefix length as the initial uplink bandwidth part and the activated uplink bandwidth part includes all resource blocks of the initial uplink bandwidth part, The terminal determines the resource block allocated by the PUSCH using the intra-cell protection frequency band corresponding to the initial uplink bandwidth part.

13. A method for allocating physical uplink shared channel PUSCH resources, It is characterized in that Applied to a network side device, the method includes: Sending downlink control information to the terminal, where the downlink control information implicitly indicates a resource block set allocated by the PUSCH; The resource block set allocated to the PUSCH scheduled by the downlink control information is determined by the terminal according to the following method: If the second resource block set of the activated uplink bandwidth part and the third resource block set where the first resource element group REG of the downlink control information in the activated downlink bandwidth part is located have an intersection, the resource block set allocated by the PUSCH is the first resource block set of the intersection.

14. The PUSCH resource allocation method according to claim 13, It is characterized in that The downlink control information indicates a resource block set for PUSCH allocation; the downlink control information includes Y bits of PUSCH resource allocation indication information.

15. The PUSCH resource allocation method according to claim 14, It is characterized in that The size of Y satisfies any of the following: The size of Y is determined by the number of resource block sets included in the activated uplink bandwidth part or the initial uplink bandwidth part; The size of Y is fixed; The size of Y is determined according to the bandwidth of the scheduled carrier or the number of resource block sets included.

16. The PUSCH resource allocation method according to claim 14, It is characterized in that The index of the starting resource block set of the resource block set indicated by the Y-bit PUSCH resource allocation indication information is a number within a carrier.

17. The PUSCH resource allocation method according to claim 16, It is characterized in that The downlink control information is scrambled using TC-RNTI.

18. The PUSCH resource allocation method according to claim 14, It is characterized in that The resource block set allocated by the PUSCH is an intersection of the resource block set allocated by the PUSCH resource allocation indication information and the resource block set of the activated uplink bandwidth part and / or the initial uplink bandwidth part; Or the resource block set allocated by the PUSCH is the first resource block set of the intersection of the resource block set allocated by the PUSCH resource allocation indication information and the resource block set of the activated uplink bandwidth part and / or the initial uplink bandwidth part.

19. A physical uplink shared channel PUSCH resource allocation device, It is characterized in that Applied to a terminal, the device comprises: An acquisition module, used for acquiring downlink control information, wherein the downlink control information implicitly indicates a resource block set allocated by a PUSCH; a processing module, used for determining a resource block set allocated by a scheduled PUSCH according to the downlink control information; The terminal determines a resource block set allocated to a PUSCH scheduled by downlink control information according to the following method: If the second resource block set of the activated uplink bandwidth part and the third resource block set where the first resource element group REG of the downlink control information in the activated downlink bandwidth part is located have an intersection, the resource block set allocated by the PUSCH is the first resource block set of the intersection.

20. The PUSCH resource allocation device according to claim 19, It is characterized in that The downlink control information indicates a resource block set allocated to the PUSCH; and the processing module is specifically configured to execute: Downlink control information in a common search space is obtained, where the downlink control information includes Y bits of PUSCH resource allocation indication information.

21. The PUSCH resource allocation device according to claim 20, It is characterized in that The size of Y satisfies any of the following: The size of Y is determined by the number of resource block sets included in the activated uplink bandwidth part or the initial uplink bandwidth part; The size of Y is fixed; The size of Y is determined according to the bandwidth of the scheduled carrier or the number of resource block sets included.

22. A physical uplink shared channel PUSCH resource allocation device, It is characterized in that Applied to a network side device, the device comprises: A sending module, configured to send downlink control information to a terminal, wherein the downlink control information explicitly or implicitly indicates a resource block set allocated by a PUSCH; The resource block set allocated to the PUSCH scheduled by the downlink control information is determined by the terminal according to the following method: If the second resource block set of the activated uplink bandwidth part and the third resource block set where the first resource element group REG of the downlink control information in the activated downlink bandwidth part is located have an intersection, the resource block set allocated by the PUSCH is the first resource block set of the intersection.

23. The PUSCH resource allocation device according to claim 22, It is characterized in that The downlink control information indicates a resource block set for PUSCH allocation; the downlink control information includes Y bits of PUSCH resource allocation indication information.

24. The PUSCH resource allocation device according to claim 23, It is characterized in that The size of Y satisfies any of the following: The size of Y is determined by the number of resource block sets included in the activated uplink bandwidth part or the initial uplink bandwidth part; The size of Y is fixed; The size of Y is determined according to the bandwidth of the scheduled carrier or the number of resource block sets included.

25. An electronic device, It is characterized in that The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method according to any one of claims 1 to 18.

26. A readable storage medium, It is characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 18 are implemented.

Images