DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Priority
Receipt is acknowledged of certified copies of papers required by 37 CFR 1.55.
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 04/03/2024 has been fully considered by examiner and made of record.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 1-5, 7, 10-11, and 20 are rejected under 35 U.S.C. 102(a)(1) & 102(a)(2) as being anticipated by Bhamri et al (US 2022/0014333).
Regarding Claim 1, Bhamri teaches a method by a terminal (Fig. 5, Fig. 8), the method comprising: receiving, by the terminal from a base station (Fig. 6), a first radio resource control (RRC) message ([0142], receiver 420 of the user equipment 410 receives a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling),
wherein the first RRC message comprises: a first set of parameters related to uplink transmission ([0142], PUSCH config IE is applicable to a particular bandwidth part. The PUSCH config IE is received from the base station 460 serving the particular bandwidth part. For example, the reception operation may be performed by the PUSCH config IE receiver 520-a of FIG. 5); a second set of parameters related to uplink transmission ([0143], the processor 430 of the user equipment 410 configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The RRC configured table comprises rows, each with a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions. For example, this configuration operation may be performed by the table configuring processing circuitry 530-a of FIG. 5); and
one or more third sets of parameters related to configured grant ([0144], the receiver 420 of the user equipment 410 receives a configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the configured table. For example, this reception operation may be performed by the configured grant config IE receiver 520-c of FIG. 5); and
performing, by the terminal and based on the first set of parameters and based on the second set of parameters ([0145], processor 430 of the user equipment 410 determines allocated resources for the plurality of PUSCH transmissions based on: (i) a value of a time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and (ii) the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table. For example, this determination operation may be performed by the allocated resources determining processing circuitry 530-b of FIG. 5), uplink transmission for control information on unused configured grant ([0148], the transmitter 420 of the user equipment 410 transmits a PUSCH transmission using the respectively determined allocated resources. For example, this transmission operation may be performed by the PUSCH transmitter 520-f of FIG. 5),
wherein the control information consists of two or more bits ([0146-0147], transmitter 420 of the user equipment 410 selects transport blocks of data to be carried in the plurality of PUSCH transmissions. For example, this selection operation may be performed by the transport blocks selecting transmitter 520-d of FIG. 5, transport blocks of data are selected based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions),
wherein the control information is: transmitted in a first period ([0260], Fig. 8, For determining the allocated time-domain resources for the first PUSCH transmission (#1), the processor 430 reverts to the first set of parameters in the indexed row with row index 3 of the RRC configured table, [0262], from the value K.sub.2, the processor 430 infers that allocated time-domain resources for the first PUSCH transmission are included in the slot with slot number k+2. Additionally, from the values S and L the processor 430 infers that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols);
not transmitted in a second period ([0268], For the subsequent PUSCH transmission #3, the second parameter with value D, meaning a difference over the preceding PUSCH transmission, indicates that a new transport block of data is to be selected which is different from that of the preceding PUSCH transmission #2. In other words, the second parameters define the repetition or difference for a subsequent PUSCH transmission with respect to the preceding PUSCH transmission); and
transmitted in a third period ([0265], the allocated time-domain resources for the subsequent PUSCH transmission #2 and #3 are included in the slots with slot numbers k+2 and k+3, respectively. Additionally two values S′ and two values L′ are comprised indicating that the allocated resources for subsequent PUSCH transmission #2 and #3 start in the respective slot with slot number k+2 and k+3 at the symbol with symbol numbers 6 and 1, respectively. The respective resource allocations in time domain are also shown),
wherein the first period is a period during when a first timer is running, wherein the first timer starts based on the first set of parameters ([0094], the processor 430 may determine the allocated time-domain resource for a first PUSCH transmission based on: (i) index of a slot carrying the received DCI, and (ii) the value K.sub.2 indicating the slot offsets, and (iii) the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table. This implies that the processor 430 has previously determined that the value indicating the PUSCH mapping type indicates a type B mapping (only when the PUSCH transmission is permitted to start at any symbol within a slot, then it is necessary to base the determination on the value SLIV),
wherein the second period is a period that occurs periodically based on the second set of parameters ([0268], For the subsequent PSUCH transmission #2, the second parameter with value R, meaning a repetition of the preceding PUSCH transmission, indicates that the same transport block of data is to be selected which is repeating that of the preceding PUSCH transmission #1, [0098], the processor 430 checks (see, e.g., step 750—FIG. 7) a second parameter which indicates to the user equipment 410 whether the subsequent PUSCH transmissions are either different (or separate) PUSCH transmissions or whether they are repeated PUSCH transmissions, [0109], the processor 430, for the at least one subsequent PUSCH transmission, reverts to the row with row index m+1 of the RRC configured table, and determines that the allocated resources, for the first repetition of the first PUSCH transmission, are included in a slot with number k+K.sub.2+1 (where 1 is a pre-defined constant fixed by standardization), and have a start and length in terms of symbols of this slot corresponding to the same value SLIV), and
wherein the third period is a period that is neither the first period nor the second period ([0116], for the third set of values, a value SLIV′ indicating another start and length indicator may be (indirectly) inferred by the processor 430 from modified SLIV parameters comprised in the PUSCH time domain resource allocation list IE. A modified SLIV parameter is provided, for example, with twice, three times, . . . the number of bits (e.g., 14 bits instead of 7 bits, or also 21 bits instead of 7 bits, or so on). Thereby, this modified SLIV parameter may be used by the processor 430 to (indirectly) infer, when configuring the table, the value SLIV included in the first set of values, and the value SLIV′, included in the third set of values of the RRC configured table).
Regarding Claim 2, Bhamri teaches the method of claim 1, wherein the first set of parameters comprises: a parameter indicating a length of the first timer; and a parameter indicating a cycle of the first period, and wherein the second set of parameters comprises: a parameter indicating a length of the second period; and a parameter indicating a cycle of the second period ([0130], a mechanism is disclosed which facilitates alleviating the uplink scheduling constraints resulting from one uplink grant per TTI. For this purpose, the RRC configure table permits the user equipment 410, despite having received only a single DCI with an uplink grant, to transmit plural PUSCH transmission, be it in the form of different (or separate) PUSCH transmissions, or be it in the form of repeated PUSCH transmissions, [0044], TTI determines the timing granularity for scheduling assignment. One TTI is the time interval in which given signals is mapped to the physical layer. Conventionally, the TTI length can vary from 14-symbols (slot-based scheduling) to 2-symbols (non-slot based scheduling). Downlink and uplink transmissions are specified to be organized into frames (10 ms duration) consisting of 10 subframes (1 ms duration). In slot-based transmission, a subframe, in return, is divided into slots, the number of slots being defined by the numerology/subcarrier spacing and the specified values range between 10 slots for a subcarrier spacing of 15 kHz to 320 slots for a subcarrier spacing of 240 kHz. The number of OFDM symbols per slot is 14 for normal cyclic prefix and 12 for extended cyclic prefix (see section 4.1 (general frame structure), 4.2 (Numerologies), 4.3.1 (frames and subframes) and 4.3.2 (slots) of the 3GPP TS 38.211 V15.4.0, incorporated herein by reference). However, assignment of time resources for transmission may also be non-slot based. In particular, the TTIs in non slot-based assignment may correspond to mini-slots rather than slots. E.g., one or more mini-slots may be assign to a requested transmission of data/control signaling. In non slot-based assignment, the minimum length of a TTI may conventionally be 2 OFDM symbols).
Regarding Claim 3, Bhamri teaches the method of claim 1, wherein the one or more third sets of parameters related to configured grant is specific to an uplink bandwidth part ([0184], due to the fact that the radio spectrum configuration pertains to the same particular bandwidth part to which also the PUSCH config IE is applicable, the user equipment 410 can implicitly establish a relationship between an unlicensed mode of operation and a necessity (or requirement) for an enhanced reliability of the PUSCH transmissions on the particular bandwidth part).
Regarding Claim 4, Bhamri teaches the method of claim 1, wherein each of the one or more third sets of parameters comprises a first subset of parameters related to a frequency resource ([0468], the PUSCH time domain resource allocation list IE additionally comprises at least one of: a parameter indicating whether the transport block size is calculated for each PUSCH transmission separately, or whether a combined transport block size is calculated for all PSUCH transmissions, including the initial PUSCH transmission and the at least one repetition thereof, a parameter indicating whether frequency hopping is applied for each PUSCH transmission separately, or whether continuous frequency hopping is applied for all PUSCH transmissions, including the initial PUSCH transmission and the at least one repetition thereof, and a parameter indicating whether or not demodulation reference symbols, DMRS, are present in all or each individual one of the at least one repetition of the initial PUSCH transmission).
Regarding Claim 5, Bhamri teaches the method of claim 4, wherein two or more configured grants are configured based on a set of parameters in case that the set of parameters further comprises a second subset of parameters related to a time resource ([0092], time-domain resources to be used by the user equipment 410 for the plural PUSCH transmissions have been previously allocated by the base station 460. In this context, the processor 430 accordingly determines which of the previously allocated resource it shall use for the plural PUSCH transmissions. For easy reference, the plural PUSCH transmissions may be understood to include a first PUSCH transmission and at least one subsequent PUSCH transmission which are all being scheduled by a single DCI, [0178-0179], the processor 430 infers from same received second parameter, whether or not it is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmission, the separate (e.g., new) parameter comprised in the Phy-Parameter IE may be termed “pusch-MultipleTrasmissions” and may be of format “ENUMERATED{repeatTB, differentTB].” This parameter may only be considered when a single DCI is configured to schedule plural PUSCH transmissions as in the focus of the present disclosure. If the single DCI is not configured to schedule multiple PUSCH transmissions, then this parameter is not considered by the user equipment 410. Such distinction can be either applied to all DCIs or can be restricted to particular DCIs).
Regarding Claim 7, Bhamri teaches the method of claim 4, wherein a single configured grant is configured based on a set of parameters in case that the set of parameters does not comprise a second subset of parameters related to a time resource ([0178-0179], the processor 430 infers from same received second parameter, whether or not it is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmission, the separate (e.g., new) parameter comprised in the Phy-Parameter IE may be termed “pusch-MultipleTrasmissions” and may be of format “ENUMERATED{repeatTB, differentTB].” This parameter may only be considered when a single DCI is configured to schedule plural PUSCH transmissions as in the focus of the present disclosure. If the single DCI is not configured to schedule multiple PUSCH transmissions, then this parameter is not considered by the user equipment 410. Such distinction can be either applied to all DCIs or can be restricted to particular DCIs).
Regarding Claim 10, Bhamri teaches the method of claim 5, wherein a number of the two or more configured grants is determined based on the second subset of parameters ([0212], With this understanding, the RRC configured table comprises not only values from the first set of values which are specifying allocated time-domain resources for the first PUSCH transmission. Rather the RRC configured table comprises a third set of values including values K.sub.2′ and/or SLIV′ which are specifying allocated time-domain resources for the at least one subsequent PUSCH transmission(s). In addition, the third set of values includes a value indicating the number of the at least one subsequent PUSCH transmission(s) further complements the RRC configured table in that it permits a more flexible determination as to which of the specified allocated time-domain resource are to be used for subsequent PUSCH transmissions).
Regarding Claim 11, Bhamri teaches the method of claim 5, wherein a time resource of each of the two or more configured grants is determined based on the second subset of parameters ([0210-0211], at least one of the third set of values, comprised in the indexed row of the RRC configured table, is at least one of a value K.sub.2′ indicating another slot offset for at least one subsequent PUSCH transmission(s), a value SLIV′ indicating another start and length indicator value for the at least one subsequent PUSCH transmission(s), and/or a value indicating the number of the at least one subsequent PUSCH transmission(s). In particular, the other start and length indicator value SLIV′ comprises: a value S′ indicating a symbol number specifying the start of the allocated time-domain resources for the at least one subsequent PUSCH transmission(s), and a value L′ indicating a number of symbols specifying the length of the allocated time-domain resources for the at least one subsequent PUSCH transmission(s)).
Regarding Claim 20, Bhamri teaches a terminal comprising: a transceiver, a memory, and a controller coupled to the transceiver and the memory ([0008-0009]), wherein the controller is configured to cause the terminal to: receive, from a base station (Fig. 6), a first radio resource control (RRC) message ([0142], receiver 420 of the user equipment 410 receives a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling),
wherein the first RRC message comprises: a first set of parameters related to uplink transmission ([0142], PUSCH config IE is applicable to a particular bandwidth part. The PUSCH config IE is received from the base station 460 serving the particular bandwidth part. For example, the reception operation may be performed by the PUSCH config IE receiver 520-a of FIG. 5);
a second set of parameters related to uplink transmission ([0143], the processor 430 of the user equipment 410 configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The RRC configured table comprises rows, each with a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions. For example, this configuration operation may be performed by the table configuring processing circuitry 530-a of FIG. 5); and
one or more third sets of parameters related to configured grant ([0144], the receiver 420 of the user equipment 410 receives a configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the configured table. For example, this reception operation may be performed by the configured grant config IE receiver 520-c of FIG. 5); and
perform, based on the first set of parameters and based on the second set of parameters ([0145], processor 430 of the user equipment 410 determines allocated resources for the plurality of PUSCH transmissions based on: (i) a value of a time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and (ii) the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table. For example, this determination operation may be performed by the allocated resources determining processing circuitry 530-b of FIG. 5), uplink transmission for control information on unused configured grant ([0148], the transmitter 420 of the user equipment 410 transmits a PUSCH transmission using the respectively determined allocated resources. For example, this transmission operation may be performed by the PUSCH transmitter 520-f of FIG. 5),
wherein the control information consists of two or more bits ([0146-0147], transmitter 420 of the user equipment 410 selects transport blocks of data to be carried in the plurality of PUSCH transmissions. For example, this selection operation may be performed by the transport blocks selecting transmitter 520-d of FIG. 5, transport blocks of data are selected based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions),
wherein the control information is: transmitted in a first period ([0260], Fig. 8, For determining the allocated time-domain resources for the first PUSCH transmission (#1), the processor 430 reverts to the first set of parameters in the indexed row with row index 3 of the RRC configured table, [0262], from the value K.sub.2, the processor 430 infers that allocated time-domain resources for the first PUSCH transmission are included in the slot with slot number k+2. Additionally, from the values S and L the processor 430 infers that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols);
not transmitted in a second period ([0268], For the subsequent PUSCH transmission #3, the second parameter with value D, meaning a difference over the preceding PUSCH transmission, indicates that a new transport block of data is to be selected which is different from that of the preceding PUSCH transmission #2. In other words, the second parameters define the repetition or difference for a subsequent PUSCH transmission with respect to the preceding PUSCH transmission); and
transmitted in a third period ([0265], the allocated time-domain resources for the subsequent PUSCH transmission #2 and #3 are included in the slots with slot numbers k+2 and k+3, respectively. Additionally two values S′ and two values L′ are comprised indicating that the allocated resources for subsequent PUSCH transmission #2 and #3 start in the respective slot with slot number k+2 and k+3 at the symbol with symbol numbers 6 and 1, respectively. The respective resource allocations in time domain are also shown),
wherein the first period is a period during when a first timer is running, wherein the first timer starts based on the first set of parameters ([0094], the processor 430 may determine the allocated time-domain resource for a first PUSCH transmission based on: (i) index of a slot carrying the received DCI, and (ii) the value K.sub.2 indicating the slot offsets, and (iii) the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table. This implies that the processor 430 has previously determined that the value indicating the PUSCH mapping type indicates a type B mapping (only when the PUSCH transmission is permitted to start at any symbol within a slot, then it is necessary to base the determination on the value SLIV),
wherein the second period is a period that occurs periodically based on the second set of parameters ([0268], For the subsequent PSUCH transmission #2, the second parameter with value R, meaning a repetition of the preceding PUSCH transmission, indicates that the same transport block of data is to be selected which is repeating that of the preceding PUSCH transmission #1, [0098], the processor 430 checks (see, e.g., step 750—FIG. 7) a second parameter which indicates to the user equipment 410 whether the subsequent PUSCH transmissions are either different (or separate) PUSCH transmissions or whether they are repeated PUSCH transmissions, [0109], the processor 430, for the at least one subsequent PUSCH transmission, reverts to the row with row index m+1 of the RRC configured table, and determines that the allocated resources, for the first repetition of the first PUSCH transmission, are included in a slot with number k+K.sub.2+1 (where 1 is a pre-defined constant fixed by standardization), and have a start and length in terms of symbols of this slot corresponding to the same value SLIV), and
wherein the third period is a period that is neither the first period nor the second period ([0116], for the third set of values, a value SLIV′ indicating another start and length indicator may be (indirectly) inferred by the processor 430 from modified SLIV parameters comprised in the PUSCH time domain resource allocation list IE. A modified SLIV parameter is provided, for example, with twice, three times, . . . the number of bits (e.g., 14 bits instead of 7 bits, or also 21 bits instead of 7 bits, or so on). Thereby, this modified SLIV parameter may be used by the processor 430 to (indirectly) infer, when configuring the table, the value SLIV included in the first set of values, and the value SLIV′, included in the third set of values of the RRC configured table).
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 6, 8-9, and 12-19 are rejected under 35 U.S.C. 103 as being unpatentable over Bhamri et al (US 2022/0014333), in view of Zhou et al (US 2020/0260486).
Regarding Claim 6, Bhamri teaches the invention of Claim 5 above, except the following, which in the same field of endeavor, Zhou teaches wherein the two or more configured grants occur periodically ([0398], RRC signaling may indicate (e.g., for Type 1 configured grants) the time domain resource allocation e.g., periodicity, offset in the frame, start symbol and length of PUSCH and K-repetition of the configured grant resource. In an example for Type 2 configured grant, RRC may indicate periodicity and K-repetition in time domain. The other time domain related parameters may be given through DCI activation scrambled with a corresponding RNTI for configured grants (e.g., CS-RNTI). In an example, some enhancements may be used in different application scenario such as URLLC. For example, the granularity of time domain allocation may be based on slot instead of OFDM symbol. In an example, the K-repetition may be reinterpreted as number of configured resource within a period).
It would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to incorporate the periodic configured grants each determined based on a number of included parameters, as taught in Zhou, in the system of Bhamri, in order to improve network coverage and transmission efficiency of the wireless network. (See Zhou [0329])
Regarding Claim 8, Bhamri teaches the invention of Claim 7 above, except the following, which in the same field of endeavor, Zhou teaches wherein the configured grant occurs periodically ([0398], RRC signaling may indicate (e.g., for Type 1 configured grants) the time domain resource allocation e.g., periodicity, offset in the frame, start symbol and length of PUSCH and K-repetition of the configured grant resource. In an example for Type 2 configured grant, RRC may indicate periodicity and K-repetition in time domain. The other time domain related parameters may be given through DCI activation scrambled with a corresponding RNTI for configured grants (e.g., CS-RNTI). In an example, some enhancements may be used in different application scenario such as URLLC. For example, the granularity of time domain allocation may be based on slot instead of OFDM symbol. In an example, the K-repetition may be reinterpreted as number of configured resource within a period).
It would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to incorporate the periodic configured grants each determined based on a number of included parameters, as taught in Zhou, in the system of Bhamri, in order to improve network coverage and transmission efficiency of the wireless network. (See Zhou [0329])
Regarding Claim 9, Bhamri teaches the invention of Claim 4 above, except the following, which in the same field of endeavor, Zhou teaches wherein the first subset of parameters comprises: a first parameter related to a frequency resource ([0548], the first configuration parameters may comprise bandwidth part configuration parameters. The bandwidth part configuration parameters may indicate a plurality of bandwidth parts of the unlicensed cell. In an example, configuration parameters of a bandwidth part of a cell may indicate a numerology corresponding to the bandwidth part. In an example, configuration parameters of a bandwidth part of a cell may indicate frequency domain location and bandwidth of the bandwidth part. In an example, configuration parameters of a bandwidth part of a cell may indicate a numerology and/or frequency domain location and bandwidth and/or subcarrier spacing of the bandwidth part and/or a cyclic prefix (e.g., normal or extended cyclic prefix));
a second parameter related to a number of Hybrid Automatic Retransmission request (HARQ) processes ([0550], second configuration parameters may indicate a plurality of HARQ processes for configured grants. The wireless device may select a HARQ process from the plurality of HARQ process for transmission of one or more transport via resources of a configured grant of the configured grants. The second configuration parameters may indicate (e.g., the second configuration parameters or the second configuration parameters along with an activation DCI) radio resources of the configured grants on the unlicensed cell. The second configuration parameters may indicate one or more power control parameters and/or time domain resource allocation (e.g., periodicity and/or offset (e.g., with respect to a first SFN) and/or a bitmap indicating slots/symbols/subframes of the configured grants) and/or one or more repetition parameters (e.g., a number of repetitions), etc);
a third parameter related to Modulation and Coding Scheme (MCS) table ([0542], a configuration parameter mcs-Table may indicate the MCS table the UE may use for PUSCH with transform precoding); and a fourth parameter related to periodicity ([0550]).
It would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to incorporate the periodic configured grants each determined based on a number of included parameters, as taught in Zhou, in the system of Bhamri, in order to improve network coverage and transmission efficiency of the wireless network. (See Zhou [0329])
Regarding Claim 12, Bhamri teaches the invention of Claim 5 above, except the following, which in the same field of endeavor, Zhou teaches wherein: all of the two or more configured grants are configured in a same frequency resource determined based on the first subset of parameters; and each of the two or more configured grants is configured in a time resource that is different from each other and that is determined based on the second subset of parameters ([0405-0407], a wireless device may be configured with multiple transmission occasions over the pre-configured time-domain resource within a CG period. In an example, before the beginning of the pre-configured period, the wireless device may perform the LBT procedure towards accessing the first transmission occasion/burst starting position. If the LBT is successful, the UE may start transmitting one or more PUSCHs up to the end of the CG resource within the pre-configured period. In an example, if the LBT fails, the UE may not defer the channel access for the remaining period. The wireless device may resume its channel access attempt by performing LBT towards accessing the second transmission occasion, and so on. In an example, transmission start time of multiple UEs configured with the same time-domain resources and either same or orthogonal frequency interlaces on a given unlicensed channel may be aligned. In an example, base station may align uplink transmission with configured grant using an Alignment Signal (e.g., a group common DCI)).
It would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to incorporate the periodic configured grants each determined based on a number of included parameters, as taught in Zhou, in the system of Bhamri, in order to improve network coverage and transmission efficiency of the wireless network. (See Zhou [0329])
Regarding Claim 13, Bhamri, modified by Zhou, teaches the invention of Claim 9 above, Zhou further teaches wherein: frequency resources indicated by the first parameter is applied to two or more configured grants in case that the set of parameters comprises the second subset of parameters ([0541], a configuration parameter frequenctDomainAllocation may indicate frequency domain resource allocation. In an example, a intraSlot value of a configuration parameter frequencyHopping enables ‘Intra-slot frequency hopping’ and a value interSlot enables ‘Inter-slot frequency hopping’. If the field is absent, frequency hopping is not configured. In an example, a configuration parameter frequencyHoppingOggset enables intra-slot frequency hopping with the given frequency hopping offset. Frequency hopping offset may be used when frequency hopping is enabled, [0543], a configuration parameter repK indicates the number of repetitions of K. In an example, a configuration parameter resourceAllocation indicates configuration of resource allocation type 0 and resource allocation type 1. For Type 1 UL data transmission without grant, “resourceAllocation” may be resourceAllocationType0 or resourceAllocationType1. In an example, a configuration parameter rrc-ConfiguredUplinkGrant may indicate configuration for “configured grant” transmission with fully RRC-configured UL grant (Type1). If this field is absent the UE uses UL grant configured by DCI addressed to CS-RNTI (Type2). Type 1 configured grant may be configured for UL or SUL, but not for both simultaneously).
It would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to incorporate the periodic configured grants each determined based on a number of included parameters, as taught in Zhou, in the system of Bhamri, in order to improve network coverage and transmission efficiency of the wireless network. (See Zhou [0329])
Regarding Claim 14, Bhamri, modified by Zhou, teaches the invention of Claim 13 above, Zhou further teaches wherein: frequency resources indicated by the first parameter is applied to a single configured grant in case that the set of parameters does not comprise the second subset of parameters ([0541], a configuration parameter frequenctDomainAllocation may indicate frequency domain resource allocation. In an example, a intraSlot value of a configuration parameter frequencyHopping enables ‘Intra-slot frequency hopping’ and a value interSlot enables ‘Inter-slot frequency hopping’. If the field is absent, frequency hopping is not configured. In an example, a configuration parameter frequencyHoppingOggset enables intra-slot frequency hopping with the given frequency hopping offset. Frequency hopping offset may be used when frequency hopping is enabled, [0543], a configuration parameter repK indicates the number of repetitions of K. In an example, a configuration parameter resourceAllocation indicates configuration of resource allocation type 0 and resource allocation type 1. For Type 1 UL data transmission without grant, “resourceAllocation” may be resourceAllocationType0 or resourceAllocationType1. In an example, a configuration parameter rrc-ConfiguredUplinkGrant may indicate configuration for “configured grant” transmission with fully RRC-configured UL grant (Type1). If this field is absent the UE uses UL grant configured by DCI addressed to CS-RNTI (Type2). Type 1 configured grant may be configured for UL or SUL, but not for both simultaneously).
It would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to incorporate the periodic configured grants each determined based on a number of included parameters, as taught in Zhou, in the system of Bhamri, in order to improve network coverage and transmission efficiency of the wireless network. (See Zhou [0329])
Regarding Claim 15, Bhamri, modified by Zhou, teaches the invention of Claim 9 above, Bhamri further teaches wherein: the third parameter is applied to two or more configured grants in case that the set of parameters comprises the second subset of parameters ([0178-0179], the processor 430 infers from same received second parameter, whether or not it is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmission, the separate (e.g., new) parameter comprised in the Phy-Parameter IE may be termed “pusch-MultipleTrasmissions” and may be of format “ENUMERATED{repeatTB, differentTB].” This parameter may only be considered when a single DCI is configured to schedule plural PUSCH transmissions as in the focus of the present disclosure. If the single DCI is not configured to schedule multiple PUSCH transmissions, then this parameter is not considered by the user equipment 410. Such distinction can be either applied to all DCIs or can be restricted to particular DCIs).
Regarding Claim 16, Bhamri, modified by Zhou, teaches the invention of Claim 15 above, Bhamri further teaches wherein: the third parameter is applied to a single configured grant in case that the set of parameters does not comprise the second subset of parameters ([0178-0179], the processor 430 infers from same received second parameter, whether or not it is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmission, the separate (e.g., new) parameter comprised in the Phy-Parameter IE may be termed “pusch-MultipleTrasmissions” and may be of format “ENUMERATED{repeatTB, differentTB].” This parameter may only be considered when a single DCI is configured to schedule plural PUSCH transmissions as in the focus of the present disclosure. If the single DCI is not configured to schedule multiple PUSCH transmissions, then this parameter is not considered by the user equipment 410. Such distinction can be either applied to all DCIs or can be restricted to particular DCIs).
Regarding Claim 17, Bhamri, modified by Zhou, teaches the invention of Claim 9 above, Bhamri further teaches wherein the fourth parameter is applied to a single configured grant in case that the set of parameters does not comprise the second subset of parameters ([0178-0179], the processor 430 infers from same received second parameter, whether or not it is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmission, the separate (e.g., new) parameter comprised in the Phy-Parameter IE may be termed “pusch-MultipleTrasmissions” and may be of format “ENUMERATED{repeatTB, differentTB].” This parameter may only be considered when a single DCI is configured to schedule plural PUSCH transmissions as in the focus of the present disclosure. If the single DCI is not configured to schedule multiple PUSCH transmissions, then this parameter is not considered by the user equipment 410. Such distinction can be either applied to all DCIs or can be restricted to particular DCIs).
Regarding Claim 18, Bhamri teaches the invention of Claim 1 above, except the following, which in the same field of endeavor, Zhou teaches wherein the specific parameter is related to a resource for transmission of the control information ([0481], at least a first portion of the one or more uplink control information corresponding to the one or more CBGs of the TB may be transmitted/multiplexed with the one or more CBGs of the TB and transmitted via an uplink data channel (e.g., PUSCH). In an example, at least a second portion of the one or more uplink control information corresponding to the one or more CBGs of the TB may be via an uplink control channel (e.g., PUCCH). The uplink control channel may be transmitted in a same transmission time/TTI as a transmission time of the one or more CBGs (e.g., a time occasion of the configured grant). In an example, the uplink control channel may be transmitted at a later time than the transmission time of the one or more CBGs (e.g., a time occasion of the configured grant)).
It would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to incorporate the periodic configured grants each determined based on a number of included parameters, as taught in Zhou, in the system of Bhamri, in order to improve network coverage and transmission efficiency of the wireless network. (See Zhou [0329])
Regarding Claim 19, Bhamri teaches the invention of Claim 1 above, except the following, which in the same field of endeavor, Zhou teaches wherein a number of bits in the control information is determined based on the specific set of parameters ([0533], UCI multiplexing in PUSCH may be performed. In an example, UCI multiplexing in PUSCH may be performed when UCI and PUSCH transmissions coincide in time. In an example, UCI multiplexing in PUSCH may be due to transmission of a UL-SCH transport block or due to triggering of A-CSI transmission without UL-SCH transport block. In an example, UCI (e.g. UCI carrying HARQ-ACK feedback with small payload, e.g., 1 or 2 bits) may be multiplexed by puncturing PUSCH. In an example, UCI may be multiplexed by rate matching PUSCH. In an example for puncturing, a TB may be mapped to radio resources and one or more resources elements may be punctured for transmission of the UCI. In an example, for rate matching, the UCI and data may be jointly coded and mapped to the radio resources).
It would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to incorporate the periodic configured grants each determined based on a number of included parameters, as taught in Zhou, in the system of Bhamri, in order to improve network coverage and transmission efficiency of the wireless network. (See Zhou [0329])
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure: Li et al (US 2022/0078823) discloses The second higher layer parameter may be the configuration identifier of the Type-1 configured PUSCH, different configuration identifiers are used to correspond to different transmission parameters, and there is a correspondence between the configuration identifier and the value of the priority. For example, if the configuration identifier belongs to a first set, a second priority is 1; or if the configuration identifier belongs to a second set, the second priority is 2. For another example, the second higher layer parameter may be the MCS table of the Type-1 configured PUSCH. When the MCS table is a low-spectral-efficiency table (that is, spectral efficiency corresponding to a lowest MCS index in the table is the lowest among all tables), a second priority is 1; or when the MCS table is not a low-spectral-efficiency table, the second priority is 2. For another example, when the transmission periodicity of the Type-1 configured PUSCH is less than or equal to a first threshold, a second priority is 1; or when the transmission periodicity of the Type-1 configured PUSCH is greater than the first threshold, the second priority is 2. The first threshold is predefined or is configured by a higher layer. For still another example, when the time domain length of the Type-1 configured PUSCH is less than or equal to a second threshold, a second priority is 1; or when the time domain length of the Type-1 configured PUSCH is greater than the second threshold, the first priority is 2. The second threshold is predefined or is configured by a higher layer. ([0422]);
Jeon et al (US 2018/0368157) discloses FIG. 26 is an example diagram of a first timer (e.g., a HARQ RTT timer) and a second timer (e.g., a drx uplink retransmission timer). A base station may transmit, to a wireless device, at least one RRC message comprising one or more configuration parameters of a configured periodic grant of a first type (e.g., GF UL transmission). The one or more configuration parameters may indicate resources of the configured periodic grant of the first type. The one or more configuration parameters may indicate a first value of the first timer and a second value of the second timer. An DRX operation may be triggered in the wireless device. The wireless device may have data to transmit during the DRX operation. The wireless device may transmit the data via the resources of the configured periodic grant of the first type. For example, the wireless device may transmit the data via the resources of the configured periodic grant of the first type in response to the data of a logical channel being detected as associated with the configured periodic grant. The wireless device may start the first timer in response to transmitting the data via the resources of the configured periodic grant of the first type. In response to expiry of the first timer, the wireless device may start the second timer. The wireless device may start to monitor a downlink control channel in response to starting the second timer. The wireless device may have second data to transmit via the resources of the configured periodic grant of the first type when the second timer is running. The wireless device may stop the second timer in response to transmitting the second data via the resources of the configured periodic grant of the first type. The wireless device may start the first timer in response to transmitting the second data.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MARGARET G WEBB whose telephone number is (571)270-7803. The examiner can normally be reached M-F 9:00-6:00 PM.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Charles Appiah can be reached at (571) 272-7904. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/MARGARET G WEBB/Primary Examiner, Art Unit 2641