Patent Description:
The present disclosure relates to the field of communication systems, and more particularly, to a user equipment (UE), a base station, and methods of communication of the same, which provides a good communication performance and high reliability.

In an unlicensed band, an unlicensed spectrum is a shared spectrum. Communication equipments in different communication systems can use the unlicensed spectrum as long as the unlicensed meets regulatory requirements set by countries or regions on a spectrum. There is no need to apply for a proprietary spectrum authorization from a government.

In order to allow various communication systems that use the unlicensed spectrum for wireless communication to coexist friendly in the spectrum, some countries or regions specify regulatory requirements that must be met to use the unlicensed spectrum. For example, a communication device follows a listen before talk (LBT) procedure, that is, the communication device needs to perform a channel sensing before transmitting a signal on a channel. When an LBT outcome illustrates that the channel is idle, the communication device can perform signal transmission, otherwise, the communication device cannot perform signal transmission. In order to ensure fairness, once a communication device successfully occupies the channel, a transmission duration cannot exceed a maximum channel occupancy time (MCOT).

On an unlicensed carrier, for a channel occupation time obtained by a base station, it may share the channel occupation time to a user equipment (UE) for transmitting an uplink signal or an uplink channel. In other words, when the base station shares its own channel occupancy time with the UE, the UE can use an LBT mode with higher priority than that used by the UE itself to obtain the channel, thereby obtaining the channel with greater probability.

In new radio-based access to unlicensed spectrum (NRU), a wideband operation can be configured and a configured active bandwidth part (BWP) can include resource block sets (RB sets). Physical uplink control channel (PUCCH) resource allocation in terms of an RB set and an interlace is not fully designed and is still an open issue.

In addition, in an NRU wideband operation, a BS (such as gNB) and a UE can operate in a wider band including RB sets. NR release <NUM> has defined a BWP concept, thus in a context of the NRU wideband operation, the UE can be configured with an active BWP including multiple RB sets. Multiple RB sets can be assigned by the gNB to the UE for uplink transmission, e.g. a physical uplink control channel (PUCCH) transmission. However, by regulation, priori to each transmission in the spectrum, a sender needs to perform the LBT procedure. This implies that for transmissions of multiple RB sets, multi-RB set-based LBT has to be performed. Because an outcome of the multi-RB-set based LBT cannot be ensured, the UE or the BS cannot predict the outcome of the LBT procedure. How to design an indication field to include a resource selection indication is still an open issue.

Therefore, there is a need for an apparatus and a method of communication of the same, which can solve issues in the prior art, provide a method of uplink resource allocation, and further provide an indication field to include a resource selection indication.

The document <CIT> provides a wireless communication system, which includes a communication module and a processor configured to control the communication module. When a time-frequency resource mapped to a demodulation-reference signal (DM-RS) of a data channel does not overlap with a time-frequency resource mapped to a different purpose from a transmission of the DM-RS, the processor is configured to receive the DM-RS in the time-frequency resource mapped to the transmission of the DM-RS and receive the data channel based on the DM-RS. In addition, when the time-frequency resource mapped to the transmission of the DM-RS of the data channel overlaps with the time-frequency resource mapped to the different purpose from the transmission of the DM-RS, the processor is configured not to expect the reception of the DM-RS in a resource element (RE) overlapping with the time-frequency resource mapped to the different purpose in the time-frequency resource mapped to the transmission of the DM-RS.

The document <CIT> provides a method of being allocated with a radio resource in a wireless communication system, the method performed by a user equipment includes: transmitting a first message to request the allocation of an semi-persistent signaling (SPS) resource for semi-persistently transmitting a specific uplink message to a base station before an uplink grant related to SPS is received from the base station; receiving a second message including information about the SPS resource allocated in response to the allocation request of the SPS resource, and transmitting the specific uplink message to the base station using an SPS resource identified using the received information, the first message includes at least one of first information indicating the timing or period in which the specific uplink message is generated and second information indicating the timing when the specific uplink message is transmitted.

The document <CIT> provides a terminal device including: a reception unit which receives an MIB that sets a first CORESET, receives an SIB1 that sets a second CORESET, receives first information that sets an initial UL BWP and second information that sets an additional UL BWP, and receives, in a common search space, a first DCI format that schedules a PUSCH, where an active UL BWP is one of the initial ULBWP and the additional UL BWP; and a transmission unit which, on the basis of a first field included in the first DCI format, identifies an allocated resource block set and transmits the PUSCH with the active UL BWP. A first value indicated by the first field is given on the basis of the size of the initial UL BWP, a first start position which is the start position for setting the allocated resource block, and the number of successively allocated first resource blocks, and the common search space is used for a random access procedure.

The document <CIT> provides a method of transmitting a signal by an apparatus in a wireless communication system. The method includes: obtaining N consecutive virtual resource block (VRB) indexes for an uplink signal in an unlicensed band, determining N physical resource block (PRB) indexes related to the N VRB indexes based on a mapping relationship between the VRB indexes and PRB indexes, and transmitting the uplink signal in resource blocks (RBs) related to the N PRB indexes in the unlicensed band.

<NPL>, discusses the FDRA filed of fallback DCI and non-fallback DCI.

<NPL>, discusses the agreements for interlaced PF2/<NUM>.

<NPL>, discusses interlace allocation for PUSCH and partial interlace allocation for PUSCH.

M<NPL>, discusses UL signals and channels in Section <NUM>.

An object of the present disclosure is to propose a user equipment (UE) and a base station (BS) and methods of communication of the same, which solve issues in the prior art, provide a method of uplink resource allocation, and further provide an indication field to include a resource selection indication.

In a first aspect of the present disclosure, a method of communication of a user equipment (UE) is provided according to claim <NUM> and further detailed in the dependent claims referring back to this claim.

In a second aspect of the present disclosure, a UE is provided according to claim <NUM> and further detailed in the dependent claims referring back to this claim.

In a third aspect of the present disclosure, a method of communication of a base station (BS) is provided according to claim <NUM> and further detailed in the dependent claims referring back to this claim.

In a fourth aspect of the present disclosure, a BS is provided according to claim <NUM> and further detailed in the dependent claims referring back to this claim.

In order to more clearly illustrate the embodiments of the present disclosure or related art, the following figures will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other figures according to these figures without paying the premise.

The invention made is disclosed in the embodiments referring to <FIG>, <FIG>, and <FIG>.

<FIG> illustrates an interlaced structure for an uplink channel transmission. In new radio-based access to unlicensed spectrum (NRU) physical uplink control channel (PUCCH) interlace, in an unlicensed band in <NUM> Hz, a regulation imposes that if a transmitter wants to operate transmission in a channel, the transmission has to occupy at least <NUM>% of a channel bandwidth. With this restriction, NRU decided to adopt an interlaced structure for two uplink channel transmissions, they are PUCCH and physical uplink shared channel (PUSCH). Each interlace structure will have specific number of physical resource block (PRB). Between each consecutive PRB pairs, there is M PRB further apart. For example, in a <NUM> bandwidth and for <NUM> subcarrier spacing (SCS) case, <NUM> interlace has <NUM> or <NUM> PRBs and M=<NUM>.

In Release <NUM>, a PUSCH transmission is configured to use an interlace structure. Moreover, an active uplink bandwidth part contains more than one RB sets. When a downlink control information (DCI) schedules a PUSCH transmission, the DCI needs to indicate a selected interlace and a selected RB set. Moreover, for Msg3 transmission, it can be scheduled by a random access response (RAR) uplink grant. How to design an indication field to include a resource selection indication is still an open issue. Some embodiments of the present disclosure provide technical solutions to resolve this issue.

<FIG> illustrates that, in some embodiments, a user equipment (UE) <NUM> and a base station (BS) (e.g., gNB) <NUM> of communication in a communication network system <NUM> according to an embodiment of the present disclosure are provided. The communication network system <NUM> includes one or more UEs <NUM> of a cell and the BS <NUM>. The UE <NUM> includes a memory <NUM>, a transceiver <NUM>, and a processor <NUM> coupled to the memory <NUM>, the transceiver <NUM>. The base station <NUM> includes a memory <NUM>, a transceiver <NUM>, and a processor <NUM> coupled to the memory <NUM>, the transceiver <NUM>. The processor <NUM> or <NUM> is configured to implement proposed functions, procedures and/or methods described in this description. Layers of radio interface protocol may be implemented in the processor <NUM> or <NUM>. The memory <NUM> or <NUM> is operatively coupled with the processor <NUM> or <NUM> and stores a variety of first information to operate the processor <NUM> or <NUM>. The transceiver <NUM> or <NUM> is operatively coupled with the processor <NUM> or <NUM>, and the transceiver <NUM> or <NUM> transmits and/or receives a radio signal.

When the embodiments are implemented in software, the techniques described herein are implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules are stored in the memory <NUM> or <NUM> and executed by the processor <NUM> or <NUM>. The memory <NUM> or <NUM> are implemented within the processor <NUM> or <NUM> or external to the processor <NUM> or <NUM> in which case those are communicatively coupled to the processor <NUM> or <NUM> via various means as is known in the art.

In some embodiments, the processor <NUM> is configured to control the transceiver <NUM> to receive a first information, wherein the first information is relevant to an uplink resource allocation. This enables to provide a method of uplink resource allocation and further provide an indication field to include a resource selection indication.

In some embodiments, the processor <NUM> is configured to control the transceiver <NUM> to transmit a first information, wherein the first information is relevant to an uplink resource allocation. This provides a method of uplink resource allocation and further provides an indication field to include a resource selection indication.

<FIG> illustrates a method <NUM> of communication of a UE according to an embodiment of the present disclosure. In some embodiments, the method <NUM> includes: a block <NUM>, receiving, by a UE, a first information, wherein the first information is relevant to an uplink resource allocation. This provides a method of uplink resource allocation and further provides an indication field to include a resource selection indication.

<FIG> illustrates a method <NUM> of communication of a BS according to an embodiment of the present disclosure. In some embodiments, the method <NUM> includes: a block <NUM>, transmitting, by a BS, a first information, wherein the first information is relevant to an uplink resource allocation. This provides a method of uplink resource allocation and further provides an indication field to include a resource selection indication.

In some embodiments, the uplink resource allocation comprises one or more resource block (RB) sets for a PUSCH transmission in an active uplink bandwidth part (UL BWP), wherein the PUSCH is scheduled by the first information. In some embodiments, the active UL BWP is an initial UL BWP. In some embodiments, wherein the first information comprises at least one of the following: a DCI format 0_0 scrambled with a temporary cell radio network temporary identifier (TC-RNTI) or a cell radio network temporary identifier (C-RNTI) or a modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI) or a configured scheduling radio network temporary identifier (CS-RNTI), or an uplink grant in a random access response (RAR), where the RAR is transmitted in a physical downlink shared channel (PDSCH). In some embodiments, the DCI format 0_0 is transmitted in a physical downlink control channel (PDCCH) in a common search space. In some embodiments, the first information comprises an indication field for resource block (RB) set indication. In some embodiments, the indication field contains Y bits, where the value Y is related to at least one of the following: a number of RB sets in the initial UL BWP; or a number of RB sets in the active UL BWP. In some embodiments, the one or more RB sets are determined by the indication field. In some embodiments, the one or more RB sets comprise the RB set corresponding to a first set of RB set indices, wherein the first set of RB set indices are defined in an active UL BWP, and the first set of RB set indices comprising at least one RB set index. In some embodiments, the indication field indicates the first set of RB set indices.

In some embodiments, the indication field indicates a second set of RB set indices, wherein the second set of RB set indices comprising at least one RB set index. In some embodiments, the second set of RB set indices are defined in an initial UL BWP. In some embodiments, the first set of RB set indices are determined from the second set of RB set indices. In some embodiments, the RB sets corresponding to the first RB set indices in the active UL BWP are overlapped with the RB sets corresponding to the second RB set indices in the initial UL BWP. In some embodiments, the first set of RB set indices are equal to the second set of RB set indices. In some embodiments, the first set of RB set indices are equal to the second set of RB set indices with modulo operation. In some embodiments, the one or more RB set are determined from a reference RB set of an active downlink (DL) BWP. In some embodiments, the one or more RB set comprises one RB set that intersects with the reference RB set. In some embodiments, the reference RB set is the smallest RB set index of the RB sets in the active DL BWP in which the PDCCH or the PDSCH is located. In some embodiments, the one or more RB sets are a default RB set of the active UL BWP.

In a wireless communication system, a modulo operation specified by Equation <NUM> is used to represent a modulo N operation, e.g. mod(<NUM>,<NUM>)=<NUM>, mod(<NUM>,<NUM>)=<NUM>, mod(<NUM>,<NUM>)=<NUM>.

In some embodiments, the one or more RB sets comprise the RB set according to the smallest RB set index among the RB sets in the active UL BWP, wherein the RB sets in the active UL BWP intersect the RB sets of the active DL BWP, in which the PDCCH or the PDSCH is located. In some embodiments, the RB sets of the initial UL BWP are configured in a system information. In some embodiments, the system information comprises an information element ServingCellConfigCommonSIB, wherein the information element ServingCellConfigCommonSIB comprises a configuration relevant to an RB set configuration for the initial UL BWP. In some embodiments, the RB set configuration in the information element ServingCellConfigCommonSIB cannot be different from the RB set configuration in an information element ServingCellConfigCommon for a given serving cell, where the information element ServingCellConfigCommon is configured in a UE-specific radio resource control (RRC) information element. In some embodiments, the one or more RB sets are determined based on one or more RB sets in which a physical random access channel (PRACH) transmission is performed. In some embodiments, the RB set for the PUSCH transmission is the same RB set, in which the latest PRACH transmission is transmitted by the same UE before receiving the first information.

In some embodiments, the uplink resource allocation comprises one or more allocated resource block (RB) sets. In some embodiments, the allocated RB set comprises an initial uplink bandwidth part. In some embodiments, the one or more allocated RB sets are in an active uplink bandwidth part. In some embodiments, the one or more allocated RB sets are from a total RB sets in the active uplink bandwidth part. In some embodiments, the one or more allocated RB sets are one or more dedicated RB sets in the active uplink bandwidth part. For example, the dedicated RB sets are all RB sets of the active uplink bandwidth part. In some embodiments, the dedicated RB set is RB set index <NUM> or the first RB set in the active uplink bandwidth part. In some embodiments, the dedicated RB set is RB set index N-<NUM> or the last RB set (Nth RB set) in the active uplink bandwidth part, where N is the number of the RB sets in the active uplink bandwidth part. In some embodiments, the dedicated RB set corresponds to the active uplink bandwidth part and an initial uplink bandwidth part. In some embodiments, the dedicated RB set is the RB set in the active uplink bandwidth part that overlaps with the initial uplink bandwidth part, where the active uplink bandwidth part and the initial uplink bandwidth part have a same subcarrier spacing (SCS) and a same cyclic prefix (CP) length, and the active uplink bandwidth part comprises all RB sets of the initial uplink bandwidth part, or the active uplink bandwidth part is the initial uplink bandwidth part. For example, the active uplink bandwidth part includes all RB sets of the initial uplink bandwidth part.

In some embodiments, the dedicated RB set is pre-defined in a specification or pre-configured. In some embodiments, the first information corresponds to a first downlink control indicator (DCI) format. In some embodiments, the first DCI format is used to a schedule physical uplink shared channel (PUSCH) for a serving cell. The first DCI format is used to schedule the PUSCH for one serving cell. In some embodiments, the first DCI format is DCI format 0_0. In some embodiments, the DCI format 0_0 is in a common search space (CSS). In some embodiments, the DCI format 0_0 is in a UE-specific search space (USS). In some embodiments, the DCI format 0_0 is cyclic redundancy check (CRC) scrambled with a cell radio network temporary identifier (C-RNTI) or a configured scheduling radio network temporary identifier (CS-RNTI) or a modulation and coding scheme radio network temporary identifier (MCS-RNTI) or a temporary cell radio network temporary identifier (TC-RNTI). In some embodiments, the DCI format 0_0 comprises an indication field, and the indication field is frequency domain resource assignment. In some embodiments, a field of the frequency domain resource assignment has X bits, and X bits are used to indicate one or more interlaces. In some embodiments, X is equal to <NUM> when a subcarrier spacing is equal to <NUM>, or X is equal to <NUM> when the subcarrier spacing is equal to <NUM>. In some embodiments, a field of the frequency domain resource assignment has X plus Y bits, X bits are used to indicate one or more interlaces, and Y bits are used to indicate one or more RB sets. In some embodiments, most significant X bits are used to indicate interlace, and least significant Y bits are used to indicate one or more RB sets.

In some embodiments, <MAT> bits, where N is a number of the RB sets in the initial uplink bandwidth part. In some embodiments, the first information corresponds to a random access response (RAR) uplink grant. In some embodiments, the RAR uplink grant comprises a PUSCH frequency resource allocation field. In some embodiments, the PUSCH frequency resource allocation field has K bits, where K is an integer. In some embodiments, X bits are within K bits, and X bits are used to indicate one or more interlaces. In some embodiments, least significant X bits are used to indicate one or more interlaces. In some embodiments, X is equal to <NUM> when a subcarrier spacing is equal to <NUM>, or X is equal to <NUM> when the subcarrier spacing is equal to <NUM>. In some embodiments, Y bits are within K bits, and Y bits are used to indicate one or more RB sets. In some embodiments, least significant Y bits are used to indicate one or more RB sets. In some embodiments, K is equal to <NUM>. In some embodiments, the uplink resource allocation is an uplink resource allocation type <NUM>. In some embodiments, the uplink resource allocation type <NUM> is used when a higher layer parameter, useInterlacePUSCH-Common or useInterlacePUSCH-Dedicated, is set to enabled. In some embodiments, the uplink resource allocation further comprises one or more interlaces. In some embodiments, the uplink resource allocation is determined as an intersection of RBs of the one or more indicated interlaces, the indicated or determined RB sets, and an intra-cell guard band between the indicated or determined RB sets.

<FIG> illustrates that, in some embodiments, when the BS <NUM> (e.g. a gNB) schedules the UE <NUM> to transmit an uplink transmission in a PUSCH, the gNB <NUM> will indicate an uplink resource allocation for the PUSCH. The UE <NUM> obtains the uplink resource allocation via a first information. In some embodiments, the uplink resource allocation comprises one or more resource block (RB) sets. Moreover, the uplink resource allocation further comprises one or more interlaces. The UE <NUM> determines the uplink resource allocation as an intersection of RBs of the indicated interlaces, the indicated or determined RB sets, and an intra-cell guard band between the indicated or determined RB sets. In some embodiments, the first information is received by the UE <NUM> and it is used to determine the indicated interlaces and the RB sets. In some embodiments the RB sets are indicated by the first information. This solution is a simple solution but overhead needs to be added in the first information for RB set indication. In some other embodiments the RB sets are not indicated by the first information but there is correspondence between the first RB sets and the first information, so that the UE <NUM> derives the RB sets based on the first information. This solution is more complicated, but it reduces the indication overhead for signaling.

In some embodiments, the first information is DCI format 0_0. The DCI format 0_0 is used to schedule PUSCH transmission for a serving cell. The DCI format 0_0 comprises an indication field, frequency domain resource assignment (FDRA) field. When the DCI format 0_0 is CRC scrambled with TC-RNTI, the DCI format 0_0 is used to schedule message <NUM> (Msg3) retransmission and the DCI format 0_0 can be received in a common search space (CSS). In some embodiments, the FDRA field does not have dedicated bits for RB set indication.

In some embodiments, the first information is DCI format 0_0 with CRC scrambled with C-RNTI or CS-RNTI or MCS-RNTI, the DCI format 0_0 is used to schedule PUSCH transmission for connected UE and the DCI format 0_0 can be received in a common search space (CSS). The DCI format 0_0 comprises an indication field, frequency domain resource assignment (FDRA) field, and the FDRA field does not have dedicated bits for RB set indication when the DCI format 0_0 is received in the CSS.

In some embodiments, the first information is DCI format 0_0 with CRC scrambled with C-RNTI or CS-RNTI or MCS-RNTI, the DCI format 0_0 is used to schedule PUSCH transmission for connected UE and the DCI format 0_0 can be received in a UE-specific search space (USS). The FDRA field in DCI format 0_0 has dedicated bits for RB set indication when the DCI format 0_0 is received in the USS and the number of bits corresponds to the number of RB sets in active uplink bandwidth part. In some embodiments, the FDRA field does not have dedicated bits for RB set indication when the DCI format 0_0 is received in the USS.

In some embodiments, the first information is an uplink grant in random access response (RAR). It is used to schedule the initial transmission of Msg3. This information is received by initial access UE (idle UE) or connected UE. In RAR uplink grant, there is PUSCH FDRA field, and this field does not have dedicated bits for RB set indication. In some embodiments, when FDRA field in RAR uplink grant has dedicated bits for RB set indication, the UE determines the indicated RB sets from the FDRA field. In some embodiments, when the FDRA field in RAR uplink grant does not have dedicated bits for RB set indication, the UE determines the RB sets as the dedicated RB set in the active uplink bandwidth part. In some embodiments, the dedicated RB set is the first RB set in the active uplink bandwidth part. If the RB sets are indexed in the active uplink bandwidth part, the dedicated RB set is RB set index <NUM> or RB set <NUM>. In some embodiments, the dedicated RB set is the last RB set in the active uplink bandwidth part. If the RB sets are indexed in the active uplink bandwidth part, the dedicated RB set is RB set index N-<NUM> or RB set N-<NUM>, where N is the number of the RB sets in the active uplink bandwidth part.

<FIG> illustrates that a carrier bandwidth contains <NUM> RB sets and an initial UL BWP contains one RB set. <FIG> illustrates that, in an example, for a PUSCH transmission scheduled by an uplink grant (UL) in RAR or scheduled by a DCI format 0_0 with CRC scrambled with TC-RNTI, if the PUSCH is configured with interlaced transmission, the RB set in which the PUSCH is transmitted is indicated by PUSCH frequency domain resource allocation (FDRA) field in UL RAR or by FDRA field in the DCI format 0_0 scrambled by TC-RNTI. In what follows throughout all the examples, we use FDRA field to represent the PUSCH FDRA field in UL grant RAR or the FDRA field in DCI format 0_0 scrambled with TC-RNTI, unless indicated otherwise. In case for a UE, the active UL BWP is the initial UL BWP and it contains only one RB set, the allocated RB set for PUSCH transmission is the RB set of the active UL BWP and the UE will ignore the FDRA field indication.

Optionally, the UE may still read the RB set indication bits in FDRA field, but the UE does not expect that the base station indicates any RB sets outside the active UL BWP. As illustrated in <FIG>, where for an idle UE, its initial UL BWP contains only one RB set (RB set <NUM>). The UE does not expect that the base station indicates RB set other than RB set <NUM> in FDRA field.

PUSCH FDRA field contains Y bits, where <MAT> bits, and N is a number of the RB sets in the carrier bandwidth or N is a number of the RB sets in the initial UL BWP or N is a number of the RB sets in carrier bandwidth. The Y bits are the most significant bits in FDRA field or the least significant bits in FDRA field.

<FIG> illustrates that a carrier bandwidth contains <NUM> RB sets and an initial UL BWP contains <NUM> RB sets. <FIG> illustrates that, in an example for a UE, the active UL BWP is the initial UL BWP and it contains more than one RB set, as illustrated in <FIG>, for the PUSCH transmission scheduled by the uplink grant (UL) in RAR or scheduled by the DCI format 0_0 with CRC scrambled with TC-RNTI, the FDRA field includes Y bits for RB set allocation, where Y = <MAT> bits, and N is a number of the RB sets in the initial UL BWP. The UE should follow the RB set indication from PUSCH FDRA field to determine the allocated RB set. Optionally, the base station can only indicate one RB set, and in an example, if the base station indicates RB set <NUM>, the UE will transmit the PUSCH in the RBs intersecting between RB set <NUM> and initial UL BWP and the indicated interlace(s). Optionally, the base station can indicate more than one RB set, in <FIG>, if the base station indicates RB set <NUM> and RB set <NUM>, the UE determines the RBs for PUSCH transmission as the RBs intersecting between the RB set <NUM> and the RB set <NUM> and the initial UL BWP and the guard band between these two RB sets and the indicated interlace(s).

<FIG> illustrates that a carrier bandwidth contains <NUM> RB sets and an initial UL BWP contains <NUM> RB sets, an active UL BWP contains <NUM> RB sets; the active UL BWP includes all RB sets of the initial UL BWP. <FIG> illustrates that, in an example, for a UE, the active UL BWP is different from the initial UL BWP, and the active UL BWP includes all the RB sets of the initial UL BWP and the active UL BWP has the same subcarrier spacing and CP length as the initial UL BWP, as illustrated in <FIG>. Then, the FDRA field contains Y bits for RB set indication, <MAT> bits, and N is a number of the RB sets in the initial UL BWP. Moreover, the indicated RB set indices with Y bits are the RB set indices defined in the initial UL BWP which is not the RB set indices defined in the active UL BWP. To illustrate the difference, we can take <FIG> as an example, the active UL BWP includes all the RB sets of the initial UL BWP. Then, the FDRA field includes Y bits to indicate the one or two RB sets. If the FDRA field indicates RB set <NUM>, it should be understood that the PUSCH is transmitted in RB set of the active UL BWP that is overlapped with the indicated RB set <NUM> defined in the initial UL BWP. This is because the RB set <NUM> defined in the active UL BWP has a different location from the RB set <NUM> defined in the initial UL BWP. The reason of this difference is that the RB set index is ordered from the start of the BWP. Thus, if the initial UL BWP and the active UL BWP have different start points, this ambiguity may arise. Thus, the UE should first derive the RB set index from FDRA field, then derive the corresponding RB set index in the active UL BWP. In an example, it means that if the FDRA field indicates RB set <NUM>, the UE will understand that it is the RB set <NUM> location defined in the initial UL BWP and then the UE will derive the corresponding RB set index in the active UL BWP, i.e. determine the RB set in active UL BWP that is overlapped with the indicated RB set in the initial UL BWP, e.g. in <FIG> the RB set <NUM> in the initial UL BWP corresponds to RB set <NUM> in the active UL BWP. Thus, the actual determined RB set for PUSCH transmission is RB set <NUM> in active UL BWP. This operation is necessary, because the actual PUSCH is transmitted in active UL BWP not initial UL BWP. Optionally, to avoid this operation, the UE can directly transmit the PUSCH in the initial UL BWP, for this case, the above presented RB set index correspondence derivation for the indicated RB set index from the initial UL BWP to the active UL BWP is not needed. But this option requires the UE to transmit the PUSCH in the initial UL BWP, and thus, the UE needs to switch from the active UL BWP to the initial UL BWP.

<FIG> illustrates that a carrier bandwidth contains <NUM> RB sets and an initial UL BWP contains <NUM> RB set, an active UL BWP contains <NUM> RB sets; the active UL BWP does not include all RB sets of the initial UL BWP. <FIG> illustrates that, in an example, on the other hand, for a UE, when the active UL BWP does not include all the RB sets of the initial UL BWP or the active UL BWP has different subcarrier spacing or CP length from the initial UL BWP, or when the active UL BWP has the same subcarrier spacing and CP length as the initial UL BWP, but the active UL BWP does not include any RB set of the initial UL BWP, as illustrated in <FIG>, the FDRA field contains Y bits for RB set indication, <MAT> bits, and N is a number of the RB sets in the active UL BWP. The UE determines the allocated RB sets from the Y bits and the PUSCH is transmitted in the indicated RB set of the active UL BWP. As illustrated in <FIG>, the active UL BWP does not include all the RB sets of the initial UL BWP. In this case, the Y bits can indicate any RB sets configured in active UL BWP, i.e. either RB set <NUM> or RB set <NUM> or both RB set <NUM> and RB set <NUM> in active UL BWP.

<FIG> illustrates that a carrier bandwidth contains <NUM> RB sets and an initial UL BWP contains <NUM> RB sets, an active UL BWP contains <NUM> RB sets; the active UL BWP does not include all RB sets of the initial UL BWP. <FIG> illustrates that, the FDRA field contains Y bits for RB set indication, <MAT> bits, and N is a number of the RB sets in the initial UL BWP. But in this case, the indicated RB set index is directly determined as the RB set index defined in active UL BWP. As illustrated in <FIG>, if the Y bits indicate RB set <NUM>, it means the RB set <NUM> in active UL BWP. If the Y bits indicate RB set <NUM>, it means the RB set <NUM> in active UL BWP.

<FIG> illustrates that a carrier bandwidth contains <NUM> RB sets and an initial UL BWP contains <NUM> RB sets, an active UL BWP contains <NUM> RB sets; the active UL BWP does not include all RB sets of the initial UL BWP. <FIG> illustrates that, in some examples, for a UE, the active UL BWP is smaller than the initial UL BWP, i.e. the active UL BWP contains less RB sets than initial UL BWP, as illustrated in FIG, In this case, if the FDRA field contains Y bits to indicate RB set index, and the value of Y can be defined with alternative options.

In one option, the value of Y should be based on the minimum number of the RBs between the initial UL BWP and the active UL BWP. In <FIG>, there are <NUM> RB sets in the initial UL BWP and <NUM> RB sets in the active UL BWP, therefore <MAT> bits, and N is min{the number of the RB sets in the initial UL BWP, the number of the RB sets in the active UL BWP}, thus, N = min{<NUM>,<NUM> }=<NUM>. Then, the indicated RB set index is directly the RB set index defined in active UL BWP, e.g. if indicated RB set index is RB set <NUM>, it means that the PUSCH is transmitted in RB set <NUM> in active UL BWP.

Another option is that the value of Y bit is always based on the number of RB sets in the initial UL BWP, i.e. <MAT> bits, and N is a number of the RB sets in the initial UL BWP. Then the UE will determine the RB set index for PUSCH transmission in the active UL BWP as RB set index = mod(indicated RB set index , m), where m is the number of the RB sets in active UL BWP, and mod(x, m) denotes as the x modulo m operation. In an example of <FIG>, where the initial UL BWP contains <NUM> RB sets and the active UL BWP contains <NUM> RB sets, thus if the indicated RB set index is RB set <NUM>, it corresponds to RB set mod(<NUM>,<NUM>)=<NUM> in the active UL BWP. If the indicated RB set is <NUM>, it corresponds to RB set mod(<NUM>,<NUM>)=<NUM> in the active UL BWP. If the indicated RB set is <NUM>, it corresponds to RB set mod(<NUM>,<NUM>)=<NUM> in the active UL BWP. Optionally, the UE does not expect that the Y bits will indicate a RB set index that is larger than the maximum RB set index of the active UL BWP, or the UE does not expect that the Y bits indicate a number of the RB sets for PUSCH transmission that is larger than the total number of the RB sets of the active UL BWP.

Optionally, to avoid this modulo operation, the base station cannot configure an initial UL BWP containing more RB sets than active UL BWP. Although, this issue can be solved, this will introduce restriction for the base station configuration.

In some examples, when the active UL BWP has the same CP length and subcarrier spacing as initial UL BWP, but the active UL BWP partially overlaps with initial UL BWP, as illustrated in <FIG>, where the RB set <NUM> of the active UL BWP is overlapped with the RB set <NUM> of the initial UL BWP, but the active UL BWP does not include the RB set <NUM> and RB set <NUM> of the initial UL BWP. In this case, the PUSCH FDRA field contains Y bits for BR set indication, where <MAT> bits, and N is a number of the RB sets in the initial UL BWP. The UE will only determine the RB sets of the active UL BWP that are overlapped with the RB sets of the initial UL BWP. For example, in <FIG>, when Y bit indicates RB set <NUM>, the UE will determine that PUSCH is transmitted in the RB set <NUM> of the active UL BWP because they are overlapped. Optionally, the UE may ignore the RB set indication if the Y bits indicate one or more RB sets that are not fully overlapped with the active UL BWP, for example, in <FIG>, if the Y bits indicate RB set <NUM> and RB set <NUM>, since the RB set <NUM> of the initial active BWP does not overlap with the active UL BWP, the UE sees the scheduling is not a valid scheduling so that the UE does not transmit PUSCH.

In an example, the RB set determination for the PUSCH transmission is based on the RB set in which the PRACH transmission is performed. For example, the UE will determine that the RB set for the PUSCH transmission scheduled by UL RAR will be transmitted in the same RB set, in which the latest PRACH transmission is transmitted by the same UE.

As shown in <FIG>, a UE transmits a PRACH in an RB set to a base station (gNB). After the PRACH transmission, the UE receives an RAR UL grant scheduling a PUSCH transmission. The PUSCH transmission is in the same RB set of the previously transmitted the PRACH. Optionally, the UE receives a DCI format 0_0 scrambled by TC-RNTI scheduling a PUSCH transmission. The PUSCH is transmitted in the same RB set of the previously transmitted PRACH, or the PUSCH is transmitted in the same RB set of the previously transmitted PUSCH scheduled by the RAR UL grant. Optionally, the UE transmits a PUCCH in an RB set to the gNB, the PUCCH is transmitted in the same RB set as the previously transmitted PUSCH scheduled by the RAR UL grant or the PUCCH is transmitted in the same RB set as the previously transmitted PUSCH scheduled by the DCI format 0_0 scrambled by TC-RNTI, or the PUCCH is transmitted in the same RB set as the previously transmitted PRACH.

<FIG> illustrates that a detected PDCCH overlaps with RB set <NUM> of an active DL BWP, thus, the determined RB set in the active DL BWP is RB set <NUM>, the corresponding RB set in the active UL BWP is the RB set <NUM>. <FIG> illustrates that, in some examples, for a PUSCH transmission scheduled by DCI format 0_0 that is CRC scrambled with TC-RNTI or C-RNTI or MCS-C-RNTI or CS-RNTI, and the DCI format 0_0 is transmitted in PDCCH, which is detected by the UE in common search space (CSS). The DCI format 0_0 does not contain dedicated bits for RB set indication. The UE will determine the RB set for PUSCH by RB set in active DL BWP. When the UE detects a PDCCH in CSS that carries the DCI format 0_0 scrambled with TC-RNTI or C-RNTI or MCS-C-RNTI or CS-RNTI, the UE will first determine the RB sets that overlap with the detected PDCCH. If there is only one RB set that overlaps with the detected PDCCH, as illustrated in <FIG>, detected PDCCH overlaps with RB set <NUM> in the active DL BWP, then the RB set for PUSCH in the active UL BWP is the RB set that intersects with the determined RB set <NUM> in the active DL BWP, i.e. RB set <NUM> of the active UL BWP.

<FIG> illustrates that a detected PDCCH overlaps with RB set <NUM> and RB set <NUM> of an active DL BWP, thus, the selected RB set in the active DL BWP is RB set <NUM> (e.g. the smallest RB set index rule), the corresponding RB set in the active UL BWP is the RB set <NUM>. <FIG> illustrates that, in another example, if the detected PDCCH overlaps with more than one RB set, as illustrated in <FIG>, where the detected PDCCH overlaps with RB set <NUM> and RB set <NUM> of the active DL BWP. First, the UE determines the RB set in active DL BWP as the smallest RB set index or largest RB set index. If the take the rule of the smallest RB set index as example, the determined RB set index of the active DL BWP is the RB set <NUM>. Then, the UE determines the RB set of the active UL BWP as the intersecting RB set of the determined RB set <NUM> of the active DL BWP, i.e. the RB set <NUM> of the active UL BWP. Therefore, the mechanism is that when the detected PDCCH overlaps with more than one RB sets in the active DL BWP, the UE first selects one RB set among the overlapped RB sets, then the UE finds the corresponding RB set in active UL BWP that intersects with the selected RB set of the active DL BWP. The selected RB set of the active DL BWP among the overlapped RB sets can be the smallest RB set index or the largest RB set index.

<FIG> illustrates that a detected PDCCH overlaps with RB set <NUM> and RB set <NUM> of an active DL BWP, thus, the selected RB set in the active DL BWP is RB set <NUM> (e.g. the smallest RB set index rule), there is no RB set of the active UL BWP that intersects with RB set <NUM> of the active DL BWP, the UE uses a default RB set of the active UL BWP for PUSCH transmission. <FIG> illustrates that, in some examples, where part of the PDCCH resources are overlapped with RB set <NUM> and another part of the PDCCH resources are overlapped with RB set <NUM> of the active DL BWP, following the presented mechanism, the selected RB set of the active DL BWP does not intersect with any RB sets of the active UL BWP, as illustrated in <FIG>. Thus, the PUSCH is allocated in a default RB set index of the active UL BWP. The default RB set is specified in the specifications, for example the default is the first RB set of the active UL BWP, i.e. RB set <NUM>.

<FIG> illustrates that a detected PDCCH overlaps with RB set <NUM> and RB set <NUM> of an active DL BWP, thus, the intersecting RB set in the active UL BWP are RB set <NUM> and RB set <NUM>, the UE determines RB set <NUM> (e.g. smallest RB set index rule) as the RB set for PUSCH transmission. <FIG> illustrates that, optionally, the RB set determination mechanism is that if the detected PDCCH overlaps with more than one RB sets in the active DL BWP, the UE will determine all the RB sets of the active UL BWP that intersect with the more than one RB sets of the active DL BWP, then the UE selects the smallest RB set index or the largest RB set index from the RB sets of the active UL BWP. As illustrated in <FIG>, the detected PDCCH overlaps with RB set <NUM> and RB set <NUM> of the active DL BWP, then the UE determines all the RB sets of the active UL BWP that intersect with these two RB sets, so the UE determines RB set <NUM> and RB set <NUM>, then the UE selects the smallest RB set index (RB set <NUM>) or the largest RB set index (RB set <NUM>) as the RB set for the PUSCH transmission.

<FIG> illustrates that a detected PDCCH overlaps with RB set <NUM> and RB set <NUM> of an active DL BWP, thus, the intersecting RB set in the active UL BWP is only RB set <NUM> in the active UL BWP, thus, the UE determines RB set <NUM> for PUSCH transmission. <FIG> illustrates that, following this mechanism, in an example, a detected PDCCH overlaps with RB set <NUM> and RB set <NUM> of an active DL BWP, thus, the intersecting RB set in the active UL BWP is only RB set <NUM> in the active UL BWP, thus, the UE determines RB set <NUM> for PUSCH transmission. This shows the difference from the mechanism presented for an example of <FIG>.

For an idle UE, the UE needs to obtain the RB set configuration first in order to read the RB set indication from RAR UL grant. Otherwise, the UE does not understand the RB set locations. The RB set is firstly configured in carrier bandwidth and the carrier bandwidth is divided into one or more RB sets by intra-cell guard band. These guard band (GB) locations and lengths can be configured. If it is not configured, there can also be default values for the GB locations and lengths specified in the specifications. To obtain the RB set configuration, the base station can send intra-cell guard band configuration in the system information such as system information block (SIB). Optionally, the system information contains an information element ServingCellConfigCommonSIB, which further contains parameters intraCellGuardBandUL-r16 and intraCellGuardBandDL-r16 for uplink carrier RB set configuration and downlink carrier RB set configuration, respectively. Once the carrier RB set is configured, the RB set in UL BWP can be derived from the intersection between the configured carrier RB set and configured initial UL BWP. Optionally, in some cases, the carrier RB set can be derived from a default RB set configuration with default guard band length and locations specified in the specification.

Optionally, for an active UE, the intra-cell guard band can also be configured in an information element ServingCellConfigCommon. Since there is already the intra-cell guard band in the system information, therefore, the UE does not expect that for the same serving cell the intra-cell guard band configuration in ServingCellConfigCommon is different from that of in ServingCellConfigCommonSIB. Optionally, there is one exception that the base station can configure different intra-cell guard band configuration in ServingCellConfigCommon and in ServingCellConfigCommonSIB. The exception is that if the active UL BWP does not include any RB set of the initial UL BWP.

In some embodiments, the dedicated RB sets are all the RB sets of the active uplink bandwidth part. In some embodiments, the dedicated RB set is the initial uplink bandwidth part. In some embodiments, the dedicated RB set corresponds to the initial uplink bandwidth part and active uplink bandwidth part. It means that the dedicated RB set is determined by the initial uplink bandwidth part and the active uplink bandwidth part. If the active uplink bandwidth part and the initial uplink bandwidth part have same SCS and same CP length and the active uplink bandwidth part includes all RB sets of the initial uplink bandwidth part, or the active uplink bandwidth part is the initial uplink bandwidth part, the dedicated RB set is the initial uplink bandwidth part. Otherwise, the dedicated RB set is the first RB set in the active UL BWP or the last RB set in the active UL BWP; or the number of RBs equals to the number of RBs in the initial uplink bandwidth part, starting from the first RB of the active uplink bandwidth part.

In some embodiments, the uplink resource allocation is type <NUM>. In uplink resource allocation of type <NUM>, the resource block assignment information indicates, to a UE, a set of up to interlace indices, and/or a set of up to N RB sets, where N is the number of RB sets in the active bandwidth part. When a higher layer parameter, useInterlacePUSCH-Common or useInterlacePUSCH-Dedicated, is set to enabled in which case uplink resource allocation type <NUM> is used.

In some embodiments, when the DCI format 0_0 is CRC scrambled with TC-RNTI, the DCI format 0_0 is used to schedule message <NUM> (Msg3) retransmission. Since the Msg3 can be sent by both initial access UE (a. idle UE), i.e. a UE not yet connected to a network, and a connected UE (i.e. a UE already connected the network). At a stage of scheduling Msg3, the network does not know if this Msg3 is sent by the connected UE or the initial access UE. Thus, the FDRA field does not contain an explicit RB set indication. This is because, to be able to provide an RB set indication, the network needs to know the number of RB sets in the active uplink bandwidth part for a UE. For an initial access UE, if it receives DCI format 0_0 with CRC scrambled with TC-RNTI, the FDRA field only has X bits, where X=<NUM> for a subcarrier spacing=<NUM>; or X=<NUM> for the subcarrier space=<NUM>. The X bits are used to indicate interlace indices. And the UE will determine the RB set as the initial uplink bandwidth part. The uplink resource allocation is then determined as an intersection of the RBs of the indicated interlaces and the initial uplink bandwidth part. Note that the initial uplink bandwidth part can be considered containing only one RB set. Therefore, there is no intra-cell guard band between two RB sets. This solution can be used as a solution <NUM>. This solution does not provide an explicit RB set indication and provides an implicit RB set indication by indicating interlace indices by the FDRA field having X bits. The advantages of this solution include small DCI overhead, high reliability, and more suitable for scheduling PUSCH in CSS. Because it requires high reliability. Moreover, the solution is unified for both idle UE and connected UE, which does not depend on specific UE configuration. Thus, this solution is very suitable for Msg3 retransmission.

<FIG> illustrates an active uplink bandwidth part (UL BWP) and an initial UL BWP. For a connected UE, if it receives the DCI format 0_0 with CRC scrambled with TC-RNTI, the FDRA field only has X bits, where X=<NUM> for the subcarrier spacing=<NUM>; or X=<NUM> for the subcarrier space=<NUM>. The X bits are used to indicate interlace indices. And the UE will determine the RB set as following. If the active UL BWP and the initial UL BWP have same SCS and same CP length and the active UL BWP includes all RB sets of the initial UL BWP as illustrated in <FIG>, the RB set is the RB set in the active UL BWP that overlaps with the initial UL initial UL BWP. <FIG> illustrates that, in the active UL BWP, there are two RB sets, i.e. RB set <NUM> and RB set <NUM>. The active UL BWP includes all the RB sets of initial UL BWP. Moreover, it is assumed that the active UL BWP and the initial UL BWP have the same subcarrier spacing and CP length. In this case, the determined RB set in the active UL BWP is the one that overlaps with the initial UL BWP, which in <FIG> is RB set <NUM>. This solution can be used as a solution <NUM>. This solution does provide an explicit RB set indication and provides an implicit RB set indication by indicating interlace indices by the FDRA field having X bits. The advantages of this solution include small DCI overhead, high reliability, and more suitable for scheduling PUSCH with DCI format 0_0 in CSS. Because it requires high reliability.

In another example, if the active UL BWP is the initial UL BWP, it is similar to the idle UE case that is mentioned above. Thus, the solution <NUM> can be applied.

<FIG> illustrates an active uplink bandwidth part (UL BWP) and an initial UL BWP. In some embodiments, if the active UL BWP does not include all the RB sets of the initial UL BWP (as illustrated in <FIG>), or the active uplink bandwidth part and the initial uplink bandwidth part do not have the same SCS or CP length, the UE will determine the RB set as a dedicated RB set in the active UL BWP. This dedicated RB set can be the first RB set, i.e. RB set <NUM> or the last RB set. The last RB set in an example as illustrated in <FIG> is RB set <NUM>. This solution can be used as a solution <NUM>. This solution does not provide an explicit RB set. The advantages of this solution include that the active uplink bandwidth part configuration is less restricted in terms of size or SCS or CP length and is suitable for scheduling PUSCH with DCI format 0_0 in both CSS and USS.

In some embodiments, if only one RB set is considered as the dedicated RB set will restrict a throughput, an alternative way is to consider all the RB sets in the active UL BWP as the dedicated RB set. This solution can be used as a solution <NUM>. This solution does not provide an explicit RB set. The advantages of this solution include that a scheduling received by the UE is to target high throughput service as more RB sets are to be used and more suitable for scheduling PUSCH with DCI format 0_0 in USS. But this solution can be also applied for DCI format 0_0 in CSS.

Optionally, selecting an RB set or selecting all RB sets can be configured by the network, for example, can be configured by RRC or configured by system information.

For UE receiving DCI format 0_0 in CSS and the DCI format 0_0 is CRC scrambled with C-RNTI or CS-RNTI or MCS-RNTI, in the DCI format 0_0, the FDRA field is more suitable to not include dedicated bits for RB set indication. The advantages of this solution include followings. This is to align a DCI size for all PDCCH monitoring in the CSS that is not dependent of RRC configuration (the number of RB sets in active UL BWP is a RRC configuration and it varies from UE to UE). In this case, solution <NUM> or <NUM> or <NUM> or <NUM> can be applied, for UE to determine the RB set in which the uplink transmission is performed.

For UE receiving DCI format 0_0 in the USS and the DCI format 0_0 is CRC scrambled with C-RNTI or CS-RNTI or MCS-RNTI, in the DCI format 0_0, the FDRA field should include dedicated bits for RB set indication. The field contains Y bits, where <MAT> where ┌ ┐ is a ceiling operation meaning the smallest integer equal to or greater than <MAT>, and N is the number of the RB sets in the active UL BWP. These Y bits are used to indicate the one or more RB sets in the active UL BWP. The indicated RB sets are for uplink transmission, which takes into account also the intra-cell guard band (GB) between the indicated RB sets and the indicated interlaces, i.e. the uplink resource allocation is determined as an intersection of RBs of the one or more indicated interlaces, the indicated or determined RB sets, and an intra-cell guard band between the indicated or determined RB sets. The advantages of this solution include that flexible control is provided, a BS can control throughout at any time, and Y bits can be least significant Y bits or most significant Y bits in the FDRA field. The UE shall determine the uplink resource allocation as an intersection of the RBs of the indicated interlaces, the indicated or determined RB sets, and the intra-cell guard band between the indicated or determined RB sets.

In some embodiments, the DCI size for DCI format 0_0 in the USS needs to be aligned with the DCI size for DCI format 0_0 in the CSS. This is for the reason of reducing the UE PDCCH monitoring complexity. In this case, the FDRA field of DCI format 0_0 in the USS does not have dedicated bits for RB set indication. Thus, the above-mentioned solution <NUM> or <NUM> or <NUM> or <NUM> can be applied, for UE to determine the RB set for uplink resource allocation. Preferably, solution <NUM> is more suitable, because its advantages are suitable for applications with large throughput.

In another example, when UE receives an UL grant scheduled by RAR, the first information is an uplink grant by random access response (RAR). It is used to schedule the initial transmission of Msg3. This information can be received by initial access UE (idle UE) or a connected UE. In RAR uplink grant, there is PUSCH FDRA field, and this field does not have dedicated bits for RB set indication. Thus, the solution <NUM> or <NUM> or <NUM> or <NUM> can be applied for UE to determine the RB set for uplink resource allocation. Advantages of this example include that high reliability is provided and RAR is suitable for low throughout applications.

Commercial interests for some embodiments are as follows. providing a method of uplink resource allocation. providing an indication field to include a resource selection indication. providing a good communication performance. providing a high reliability. Some embodiments of the present disclosure are used by <NUM>-NR chipset vendors, V2X communication system development vendors, automakers including cars, trains, trucks, buses, bicycles, moto-bikes, helmets, and etc., drones (unmanned aerial vehicles), smartphone makers, communication devices for public safety use, AR/VR device maker for example gaming, conference/seminar, education purposes. Some embodiments of the present disclosure are a combination of "techniques/processes" that can be adopted in 3GPP specification to create an end product. Some embodiments of the present disclosure could be adopted in the <NUM> NR unlicensed band communications. Some embodiments of the present disclosure propose technical mechanisms.

<FIG> is a block diagram of an example system <NUM> for wireless communication. Example described herein may be implemented into the system using any suitably configured hardware and/or software. <FIG> illustrates the system <NUM> including a radio frequency (RF) circuitry <NUM>, a baseband circuitry <NUM>, an application circuitry <NUM>, a memory/storage <NUM>, a display <NUM>, a camera <NUM>, a sensor <NUM>, and an input/output (I/O) interface <NUM>, coupled with each other at least as illustrated. The application circuitry <NUM> may include a circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors, such as graphics processors, application processors. The processors is coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.

The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. The baseband circuitry may provide for communication compatible with one or more radio technologies. For example, the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Examples in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

In various examples not being part of the present invention, the baseband circuitry <NUM> may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency. The RF circuitry <NUM> may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various examples, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various examples, the RF circuitry <NUM> may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

In various examples, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and/or the application circuitry. As used herein, "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some examples, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some examples, some or all of the constituent components of the baseband circuitry, the application circuitry, and/or the memory/storage may be implemented together on a system on a chip (SOC). The memory/storage <NUM> may be used to load and store data and/or instructions, for example, for system. The memory/storage for one example may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM)), and/or non-volatile memory, such as flash memory.

In various examples, the I/O interface <NUM> may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface. In various examples, the sensor <NUM> may include one or more sensing devices to determine environmental states and/or location first information related to the system. In some examples, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.

In various examples, the display <NUM> may include a display, such as a liquid crystal display and a touch screen display. In various examples, the system <NUM> may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, a AR/VR glasses, etc. In various examples, system may have more or less components, and/or different architectures. Where appropriate, methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

A person having ordinary skill in the art understands that each of the units, algorithm, and steps described and disclosed in the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the state of application and design requirement for a technical plan. A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he/she can refer to the working processes of the system, device, and unit as above-mentioned since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed.

It is understood that the disclosed system, device, and method in the present disclosure can be realized with other ways.

If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other kinds of media capable of storing program codes.

Claim 1:
A method (<NUM>) of communication of a user equipment, UE, comprising:
receiving (<NUM>), by the UE, a first information from a base station, BS, wherein the first information includes information relevant to an uplink resource allocation, the information relevant to the uplink resource allocation comprises a plurality of resource block, RB, sets for physical uplink transmission, and the information relevant to the uplink resource allocation comprises one or more interlace structures in one or more RB sets, and
wherein the first information is of a downlink control indicator, DCI format 0_0 used for scheduling physical uplink shared channel, PUSCH, the DCI format 0_0 comprises a field of a frequency domain resource assignment,
wherein
the field of the frequency domain resource assignment has X plus Y bits, most significant X bits are used to indicate one or more interlace structures, and least significant Y bits are used to indicate one or more RB sets, X and Y being integers greater than or equal to <NUM>, and each of the one or more interlace structures being used for physical uplink control channel, PUCCH, transmission and PUSCH transmission and has a specific number of physical resource block, PRB,
wherein the information relevant to the uplink resource allocation is an uplink resource allocation type <NUM>, and the uplink resource allocation type <NUM> is used when a higher layer parameter, useInterlacePUSCH-Common or useInterlacePUSCH-Dedicated, is set to enabled, and
wherein the uplink resource allocation is determined as an intersection of RBs of the one or more indicated interlaces, the indicated or determined RB sets and an intra-cell guard band between the indicated or determined RB sets.