DETAILED ACTION
This office action is a response to the Request for Reconsideration-After Non-Final Rejection filed on 06/25/2026.
Notice of 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 .
Claim Status:
Claims 1-20 are pending
Claims 1-20 remain rejected.
Claim Interpretation
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked.
As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph:
(A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function;
(B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and
(C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function.
Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function.
Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function.
Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier.
Claim 20 recites limitations that use words like “means” (or “step”) or similar terms with functional language and do invoke 35 U.S.C. 112(f):
Claim 20; recites the limitations, “…means for obtaining a configuration of a control channel or a data channel in a cell, … means for receiving or transmitting information in at least one of the control channel or the data channel based on the configuration,” in Lines [2-3] and [9-10] respectively.
Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
After a careful analysis, as disclosed above, and a careful review of the specification the following limitations in claim 2:
(i) “means for obtaining” and “means for receiving”: Fig. 22, #2204, Para. [0150] discloses, “…the apparatus 2202, and in particular the one or more cellular baseband processors 2204, includes means for obtaining a configuration of a control channel or a data channel in a cell, …and means for receiving or transmitting information in at least one of the control channel or the data channel based on the configuration.”
If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph.
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 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 of this title, 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 1-15 and 17-20 are rejected under 35 U.S.C. 103 as being unpatentable over TSAI et al. (US 20230371039 A1), hereinafter referenced as Tsai, in view of Do et al. (US 20230066568 A1), hereinafter referenced as Do.
Regarding claims 1 and 19-20, Tsai teaches an apparatus for wireless communication, comprising: one or more memories; and one or more processors each communicatively coupled with at least one of the one or more memories, the one or more processors, individually or in any combination (Para. [0004]-Tsai discloses methods, systems, and devices that may assist in operation of DL control channel. Para. [0090]-Tsai discloses method for the single-to-multiple scheduling DCI format. Figs. 19F-19G, Para. [0198]-Tsai discloses WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad/indicators 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. Para. [0177]-Tsai discloses core network entities may be logical entities that are implemented in the form of computer-executable instructions (software) stored in a memory of, and executing on a processor of, an apparatus configured for wireless or network communications or a computer system), operable to cause the apparatus to:
obtain a configuration of a control channel or a data channel in a cell (Para. [0135]-Tsai discloses when UE 102 monitor PDCCH in a monitoring span (X, Y) (e.g., X=8 slots, Y=4 slots), UE only monitor PDCCH within Y slots. The starting slot can be signalled by higher layer (e.g., PDCCH config in RRC). For example, PDCCH configuration can signal the (starting) slot number n in a SFN and the span length Y (e.g., Y≤X/2) ... since common CORESET configuration and search space are shared by multiple UEs in a serving cell, so accordingly, network need to take care alignment with UEs for this configuration like PDCCH control region for RAR/paging/system information),
the cell including a plurality of … frequency bands associated with different numerologies (Para. [0050]-Tsai discloses methods for DCI design for NR from 52.6 GHz and above {set of frequency bands, including non-contiguity} (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses for SCS/numerologies ... SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above {Corresponding to frequency bands} ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs. Para. [0042]-Tsai discloses SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0134]-Tsai discloses non-contiguous (time-domain) transmission of PDSCH/PUSCH can be supported. ),
the control channel or the data channel being allocated in: one or more of the non-contiguous frequency bands associated with a single numerology of the different numerologies, or one or more of the non-contiguous frequency bands associated with each numerology of the different numerologies (Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}.
Para. [0087]-Tsai discloses if the allocation length of PRB for a PDSCH in one of the separate FDRA field in DCI is equal to zero, then UE 102 can assume that corresponding PDSCH is not scheduled. FDRA can support Type 0, Type 1, and dynamic switch (switch between Type 0 and 1). Para. [0079]-Tsai discloses FDRA: This field can be separated for each scheduled PDSCH. DCI can use separated FDRA field for each scheduled PDSCH frequency-domain resource, or DCI can use a single FDRA field for scheduling multiple PDSCHs frequency-domain resources based on a look-up table. The entries in the look-up table can be configured by higher layer (e.g., RRC). (See also Para. [0090). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs. Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell); and
receive or transmit information in at least one of the control channel or the data channel based on the configuration (Fig. 19A, Para. [0145]-Tsai discloses the base station 114a may be configured to transmit or receive wireless signals within a particular geographic region, which may be referred to as a cell ... the base station 114b may be configured to transmit or receive wired or wireless signals within a particular geographic region, which may be referred to as a cell ... for methods, systems, and devices of downlink control channel for NR from 52.6 GHz and above. Para. [0057]-Tsai discloses PDCCH for paging PDSCH is disclosed, system Information (SI) PDSCH can be adopted with the cross-slot scheduling when the SCS/numerologies are greater than a value e.g., SCS=480 KHz /μ=5. The value of K.sub.0 can be referred from a pre-defined table (e.g., a new set of default tables for TDRA) in the specification or via higher layer (RRC) configuration. For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs (e.g., for paging or RMSI PDSCH reception).
Tsai fails to explicitly teach non-contiguous frequency bands.
However, Do teaches obtain a configuration of a control channel or a data channel in a cell (Para. [0193]-Do discloses the base station may be any radio node configured to allocate the radio resources for the radio communication. Para. [0168]-Do discloses the term base station may be used interchangeably with the term cell. Para. [0083-0084]-Do discloses B-value for common channels and dedicated channels can be signaled to UEs in dedicated signaling when it is applicable. Furthermore, the B-value for PDSCH and PUSCH can also be dynamically specified in the associated scheduling DCIs or in some MAC CEs ..., the allocation 302 defines a DM-RS pattern, e.g., for PDSCH and/or PUSCH),
the cell including a plurality of non-contiguous frequency bands associated with different numerologies (Para. [0181]-Do discloses the first frequency band and the second frequency band may be noncontiguous in a frequency domain. For example, the first frequency band and the second frequency band may belong to different operating frequency bands. Para. [0179]-Do discloses numerology of the first frequency band may be different from a numerology of the second frequency band. For example, a SCS of the OSs in the first frequency band may less than a SCS of the OSs in the second frequency band. Alternatively or in addition, a length of the OSs in the first frequency band may greater than a length of the OSs in the second frequency band. Para. [0165-0181]-Do discloses the same base station and/or the radio communication may use different SCSs at different times ... the term base station may be used interchangeably with the term cell ... the same base station and/or the radio communication may use different lengths of the OSs (e.g., different numerologies) at different times ... the radio communication uses a first frequency band and a second frequency band).
Tsai and Do are both considered to be analogous to the claimed invention because they are in the same field of radio communication network, dealing with allocating and applying the allocation of radio resources.
Therefore, it would have been obvious to someone of ordinary skill in the art before the effective filing date of the claimed invention to have modified the Tsai to incorporate the teachings of Do on frequency bands, with a motivation for non-contiguous bands, and guarantee operation of DL control channel for NR from 52.6 GHz and above, (Tsai, Para. [0004]).
Regarding claim 2, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical downlink control channel (PDCCH), the configuration indicates to monitor the PDCCH in the one or more of the non-contiguous frequency bands associated with the single numerology of the different numerologies (Para. [0048]-Tsai discloses monitoring PDCCH for NR from 52.6 to 71 GHz band {set of frequency bands, including non-contiguity}. Para. [0039]-Tsai discloses PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS {Numerology} configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0042]-Tsai discloses non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs. (See also Para. [0120]). Para. [0134]-Tsai discloses non-contiguous (time-domain) transmission of PDSCH/PUSCH can be supported), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: monitor the PDCCH in the one or more of the non-contiguous frequency bands associated with the single numerology (Para. [0048]-Tsai discloses monitoring PDCCH for NR from 52.6 to 71 GHz band {set of frequency bands, including non-contiguity}. Para. [0039]-Tsai discloses PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS {Numerology} configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0042]-Tsai discloses non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs. (See also Para. [0120]). Para. [0134]-Tsai discloses non-contiguous (time-domain) transmission of PDSCH/PUSCH can be supported).
Regarding claim 3, Tsai teaches the apparatus of claim 2,
Tsai further teaches the configuration indicates a quantity of blind decoding attempts (Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability. Para. [0054]-Tsai discloses gNB 114 may config the UEs to monitor only the compact DCI format 1_x instead of DCI format 0_0/1_0 and 0_1/1_1 so that the total number of blind decodes won't increase for a UE) and
a quantity of non-overlapped control channel elements (CCEs) for PDCCH monitoring in a time period for the cell (Para. [0043]-Tsai discloses the UE can be configured by the gNB to monitor PDCCH for the maximum number of PDCCH candidates and nonoverlapping CCEs defined per slot. Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability),
the quantity of blind decoding attempts and the quantity of non-overlapped CCEs respectively being capped by a limit associated with the single numerology for the PDCCH (Para. [0054]-Tsai discloses gNB 114 may config the UEs to monitor only the compact DCI format 1_x instead of DCI format 0_0/1_0 and 0_1/1_1 so that the total number of blind decodes won't increase for a UE. Para. [0043]-Tsai discloses the UE can be configured by the gNB to monitor PDCCH for the maximum number of PDCCH candidates and nonoverlapping CCEs defined per slot. Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability. Figs. 1 and 10A, Para. [0120]-Tsai discloses UE 102 can be configured by gNB 114 to monitor PDCCH for the maximum number of PDCCH candidates (M.sub.PDCCH.sup.max,span,μ) and nonoverlapping CCEs (C.sub.PDCCH.sup.max,span,μ) defined per span).
Regarding claim 4, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical downlink control channel (PDCCH), the configuration indicates to monitor the PDCCH in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies (Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0042]-Tsai discloses non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: monitor the PDCCH in the one or more of the non-contiguous frequency bands associated with the single numerology during a time period (Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0042]-Tsai discloses non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs. (See also Para. [0120])).
Regarding claim 5, Tsai teaches the apparatus of claim 4,
Tsai further teaches the configuration indicates a quantity of blind decoding attempts (Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability. Para. [0054]-Tsai discloses gNB 114 may config the UEs to monitor only the compact DCI format 1_x instead of DCI format 0_0/1_0 and 0_1/1_1 so that the total number of blind decodes won't increase for a UE) and
a quantity of non-overlapped control channel elements (CCEs) for PDCCH monitoring in the time period for the cell (Para. [0043]-Tsai discloses the UE can be configured by the gNB to monitor PDCCH for the maximum number of PDCCH candidates and nonoverlapping CCEs defined per slot. Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability),
the quantity of blind decoding attempts and the quantity of non-overlapped CCEs for the PDCCH respectively being capped by a limit associated with the single numerology during the time period (Para. [0054]-Tsai discloses gNB 114 may config the UEs to monitor only the compact DCI format 1_x instead of DCI format 0_0/1_0 and 0_1/1_1 so that the total number of blind decodes won't increase for a UE. Para. [0043]-Tsai discloses the UE can be configured by the gNB to monitor PDCCH for the maximum number of PDCCH candidates and nonoverlapping CCEs defined per slot. Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability. Figs. 1 and 10A, Para. [0120]-Tsai discloses UE 102 can be configured by gNB 114 to monitor PDCCH for the maximum number of PDCCH candidates (M.sub.PDCCH.sup.max,span,μ) and nonoverlapping CCEs (C.sub.PDCCH.sup.max,span,μ) defined per span).
Regarding claim 6, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical downlink control channel (PDCCH), the configuration indicates to monitor for the PDCCH in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies (Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0042]-Tsai discloses non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: monitor the PDCCH in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies during a time period (Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0042]-Tsai discloses non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs),
control channel elements (CCEs) of the PDCCH are respectively mapped in resources associated with the single numerology (Figs. 1 and 10A, Para. [0120]-Tsai discloses UE 102 can be configured by gNB 114 to monitor PDCCH for the maximum number of PDCCH candidates (M.sub.PDCCH.sup.max,span,μ) and nonoverlapping CCEs (C.sub.PDCCH.sup.max,span,μ) defined per span … UE 102 and gNB 114 can map PDCCH candidates in each PDCCH monitoring span as the following mapping rules in legacy NR specification: (1) common search space (CSS) sets are mapped before UE specific search space (USS) sets; (2) USS sets are mapped in ascending order of the search space (SS) set indices, and if the number of PDCCH candidates/CCEs exceeds UE 102 processing limits, etc).
Regarding claim 7, Tsai teaches the apparatus of claim 6,
Tsai further teaches the configuration indicates a quantity of blind decoding attempts (Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability. Para. [0054]-Tsai discloses gNB 114 may config the UEs to monitor only the compact DCI format 1_x instead of DCI format 0_0/1_0 and 0_1/1_1 so that the total number of blind decodes won't increase for a UE) and
a quantity of non-overlapped CCEs for PDCCH monitoring in the time period for the cell for the each numerology of the different numerologies (Para. [0043]-Tsai discloses the UE can be configured by the gNB to monitor PDCCH for the maximum number of PDCCH candidates and nonoverlapping CCEs defined per slot. Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability),
the quantity of blind decoding attempts and the quantity of non-overlapped CCEs for the PDCCH respectively being capped by a limit associated with the each of the different numerologies during the time period (Para. [0054]-Tsai discloses gNB 114 may config the UEs to monitor only the compact DCI format 1_x instead of DCI format 0_0/1_0 and 0_1/1_1 so that the total number of blind decodes won't increase for a UE. Para. [0043]-Tsai discloses the UE can be configured by the gNB to monitor PDCCH for the maximum number of PDCCH candidates and nonoverlapping CCEs defined per slot. Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}).
Regarding claim 8, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical downlink control channel (PDCCH), the configuration indicates to monitor for the PDCCH in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies (Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0042]-Tsai discloses non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: monitor the PDCCH in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies during a time period (Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0042]-Tsai discloses non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs),
control channel elements (CCEs) of the PDCCH are respectively mapped in resources associated with a set of the each numerologies (Para. [0042]-Tsai discloses maximum number M.sub.PDCCH.sup.max,span,μ of monitored PDCCH candidates per span (X=7, Y=3) for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {44, 36} and the maximum number C.sub.PDCCH.sup.max,span,μ of non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above).
Regarding claim 9, Tsai teaches the apparatus of claim 8,
Tsai further teaches the configuration indicates a quantity of blind decoding attempts (Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability. Para. [0054]-Tsai discloses gNB 114 may config the UEs to monitor only the compact DCI format 1_x instead of DCI format 0_0/1_0 and 0_1/1_1 so that the total number of blind decodes won't increase for a UE) and
a quantity of non-overlapped CCEs for PDCCH monitoring in the time period for the cell for the set of the each numerologies (Para. [0043]-Tsai discloses the UE can be configured by the gNB to monitor PDCCH for the maximum number of PDCCH candidates and nonoverlapping CCEs defined per slot. Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability),
the quantity of blind decoding attempts and the quantity of non-overlapped CCEs for the PDCCH respectively being capped by a limit associated with a reference numerology of the set of the each numerologies during the time period (Para. [0054]-Tsai discloses gNB 114 may config the UEs to monitor only the compact DCI format 1_x instead of DCI format 0_0/1_0 and 0_1/1_1 so that the total number of blind decodes won't increase for a UE. Para. [0043]-Tsai discloses the UE can be configured by the gNB to monitor PDCCH for the maximum number of PDCCH candidates and nonoverlapping CCEs defined per slot. Para. [0039]-Tsai discloses depending on the configuration, the number of PDCCH candidates may be limited by the number of blind decoding attempts, or by the number of CCE that require channel estimates. In NR, number of monitored PDCCH candidates and non-overlapped CCEs per slot is the UE capability. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}).
Regarding claim 10, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical uplink control channel (PUCCH) (Para. [0062-0079]-Tsai discloses control information in DCI bit field (or DCI field) may be separated or shared field. For shared field, the n PDSCHs can share the same valued indicated by DCI field. For separated field, n separate values are indicated to then PDSCHs ... Control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH), and
the configuration indicates a plurality of PUCCH resources respectively including one or more time-frequency resources associated with the single numerology of the different numerologies (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0090]-Tsai discloses single-to-multiple scheduling DCI format (e.g., format 1_z) to avoid overgrowth is that the control information can be divided into two parts. The first part of the control information is the critical demodulation information such as the time-frequency resource allocation information (e.g., FDRA, TDRA, rate matching parameter, etc.) and shared field like carrier indicator, BWP ID. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}),
the PUCCH resources being respectively allocated in the one or more of the non-contiguous frequency bands associated with the single numerology (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}).
Regarding claim 11, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical uplink control channel (PUCCH) (Para. [0062-0079]-Tsai discloses control information in DCI bit field (or DCI field) may be separated or shared field. For shared field, the n PDSCHs can share the same valued indicated by DCI field. For separated field, n separate values are indicated to then PDSCHs ... Control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH),
the configuration indicates a plurality of PUCCH resources respectively including one or more time-frequency resources associated with the single numerology of the different numerologies (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0090]-Tsai discloses single-to-multiple scheduling DCI format (e.g., format 1_z) to avoid overgrowth is that the control information can be divided into two parts. The first part of the control information is the critical demodulation information such as the time-frequency resource allocation information (e.g., FDRA, TDRA, rate matching parameter, etc.) and shared field like carrier indicator, BWP ID. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}),
the PUCCH resources being respectively allocated in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: transmit in one of the PUCCH resources allocated in the one or more of the non-contiguous frequency bands associated with the single numerology during a time period (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}).
Regarding claim 12, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical uplink control channel (PUCCH) (Para. [0062-0079]-Tsai discloses control information in DCI bit field (or DCI field) may be separated or shared field. For shared field, the n PDSCHs can share the same valued indicated by DCI field. For separated field, n separate values are indicated to then PDSCHs ... Control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH),
the configuration indicates a plurality of PUCCH resources respectively including one or more time-frequency resources associated with the single numerology of the different numerologies (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0090]-Tsai discloses single-to-multiple scheduling DCI format (e.g., format 1_z) to avoid overgrowth is that the control information can be divided into two parts. The first part of the control information is the critical demodulation information such as the time-frequency resource allocation information (e.g., FDRA, TDRA, rate matching parameter, etc.) and shared field like carrier indicator, BWP ID. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}),
the PUCCH resources being respectively allocated in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: transmit in multiple ones of the PUCCH resources allocated in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies simultaneously during a single time period (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}).
Regarding claim 13, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical uplink control channel (PUCCH) (Para. [0062-0079]-Tsai discloses control information in DCI bit field (or DCI field) may be separated or shared field. For shared field, the n PDSCHs can share the same valued indicated by DCI field. For separated field, n separate values are indicated to then PDSCHs ... Control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH),
the configuration indicates a plurality of PUCCH resources respectively including one or more time-frequency resources associated with the each numerology of the different numerologies (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0090]-Tsai discloses single-to-multiple scheduling DCI format (e.g., format 1_z) to avoid overgrowth is that the control information can be divided into two parts. The first part of the control information is the critical demodulation information such as the time-frequency resource allocation information (e.g., FDRA, TDRA, rate matching parameter, etc.) and shared field like carrier indicator, BWP ID. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}),
one of the PUCCH resources being respectively allocated in the one or more of the non-contiguous frequency bands associated with the each numerology during different time periods (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}).
Regarding claim 14, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical uplink control channel (PUCCH) (Para. [0062-0079]-Tsai discloses control information in DCI bit field (or DCI field) may be separated or shared field. For shared field, the n PDSCHs can share the same valued indicated by DCI field. For separated field, n separate values are indicated to then PDSCHs ... Control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH),
the configuration indicates a plurality of PUCCH resources respectively including one or more time-frequency resources associated with the each numerology of the different numerologies (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0090]-Tsai discloses single-to-multiple scheduling DCI format (e.g., format 1_z) to avoid overgrowth is that the control information can be divided into two parts. The first part of the control information is the critical demodulation information such as the time-frequency resource allocation information (e.g., FDRA, TDRA, rate matching parameter, etc.) and shared field like carrier indicator, BWP ID. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}),
one of the PUCCH resources being respectively allocated in the one or more of the non-contiguous frequency bands associated with the each numerology during a same time period (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}).
Regarding claim 15, Tsai teaches the apparatus of claim 1,
Tsai further teaches the data channel is a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) (Fig. 10B, Para. [0019]-Tsai discloses PDCCH monitoring methods for supporting NR from 52.6 GHz and above in which there may be a single DCI schedule multiple (e.g., two) PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s)), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: receive downlink control information (DCI) scheduling the PDSCH or the PUSCH in the one or more of the non-contiguous frequency bands associated with the single numerology of the different numerologies (Para. [0116]-Tsai discloses UE 102 can receive a single DCI scheduling multiple PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s). Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz)),
at least one field of the DCI being configured for the single numerology (Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz)); and
receive the PDSCH or transmit the PUSCH in the one or more of the non-contiguous frequency bands associated with the single numerology of the different numerologies (Para. [0116]-Tsai discloses UE 102 can receive a single DCI scheduling multiple PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s). Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}),
different PDSCHs or different PUSCHs are respectively allocated in the one or more of the non-contiguous frequency bands associated with the different numerologies during different time periods (Para. [0116]-Tsai discloses UE 102 can receive a single DCI scheduling multiple PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s). Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}).
Regarding claim 17, Tsai teaches the apparatus of claim 1,
Tsai further teaches the control channel is a physical uplink control channel (PUCCH) (Para. [0062-0079]-Tsai discloses control information in DCI bit field (or DCI field) may be separated or shared field. For shared field, the n PDSCHs can share the same valued indicated by DCI field. For separated field, n separate values are indicated to then PDSCHs ... Control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH) and
the data channel is a physical uplink shared channel (PUSCH) (Para. [0046]-Tsai discloses DCI format 0_2, open loop power control (OLPC) set indication field with from 0 to 2 bits, priority indicator field with 0 or 1 bit, invalid symbol pattern indicator field with 0 or 1 bit are new fields added to be compatible with new standards of PUSCH transmission. Fig. 10B, Para. [0019]-Tsai discloses PDCCH monitoring methods for supporting NR from 52.6 GHz and above in which there may be a single DCI schedule multiple (e.g., two) PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s)), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: transmit the PUCCH in the one or more of the non-contiguous frequency bands associated with one or multiple of the different numerologies (Para. [0064-0072]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0090]-Tsai discloses single-to-multiple scheduling DCI format (e.g., format 1_z) to avoid overgrowth is that the control information can be divided into two parts. The first part of the control information is the critical demodulation information such as the time-frequency resource allocation information (e.g., FDRA, TDRA, rate matching parameter, etc.) and shared field like carrier indicator, BWP ID. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}); and
transmit the PUSCH, concurrently with the PUCCH, in a different one or more of the non-contiguous frequency bands associated with one or multiple of the different numerologies (Para. [0046]-Tsai discloses DCI format 0_2, open loop power control (OLPC) set indication field with from 0 to 2 bits, priority indicator field with 0 or 1 bit, invalid symbol pattern indicator field with 0 or 1 bit are new fields added to be compatible with new standards of PUSCH transmission. Para. [0116]-Tsai discloses UE 102 can receive a single DCI scheduling multiple PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s). Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}).
Regarding claim 18, Tsai teaches the apparatus of claim 1,
Tsai further teaches the data channel is a physical uplink shared channel (PUSCH) (Para. [0046]-Tsai discloses DCI format 0_2, open loop power control (OLPC) set indication field with from 0 to 2 bits, priority indicator field with 0 or 1 bit, invalid symbol pattern indicator field with 0 or 1 bit are new fields added to be compatible with new standards of PUSCH transmission) and
the control channel is a physical uplink control channel (PUCCH) concurrent in time with the PUSCH (Para. [0062-0079]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: transmit the PUSCH in one or more of the non-contiguous frequency bands associated with one or multiple of the different numerologies (Para. [0046]-Tsai discloses DCI format 0_2, open loop power control (OLPC) set indication field with from 0 to 2 bits, priority indicator field with 0 or 1 bit, invalid symbol pattern indicator field with 0 or 1 bit are new fields added to be compatible with new standards of PUSCH transmission. Para. [0116]-Tsai discloses UE 102 can receive a single DCI scheduling multiple PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s). Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}),
the PUCCH being multiplexed on the PUSCH in either: the one or more of the non-contiguous frequency bands associated with a reference numerology of the different numerologies, or the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies (Para. [0053]-Tsai discloses UEs can be multiplexed in frequency domain resource within a OFDM symbol, the transport block (TB) can be occupied most of resource elements (REs) in a OFDM symbol. Para. [0062-0079]-Tsai discloses control information in DCI field may include shared fields ... PUCCH resource indicator: Scheduled PDSCHs can share a same PUCCH resource ... TPC command for scheduled PUCCH. Para. [0046]-Tsai discloses DCI format 0_2, open loop power control (OLPC) set indication field with from 0 to 2 bits, priority indicator field with 0 or 1 bit, invalid symbol pattern indicator field with 0 or 1 bit are new fields added to be compatible with new standards of PUSCH transmission).
Claim 16 are rejected under 35 U.S.C. 103 as being unpatentable over TSAI et al. (US 20230371039 A1), hereinafter referenced as Tsai, in view of Do et al. (US 20230066568 A1), hereinafter referenced as Do, and further in view of WANG et al. (US 20180132269 A1), hereinafter referenced as Do.
Regarding claim 16, Tsai teaches the apparatus of claim 1,
Tsai further teaches the data channel is a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) (Fig. 10B, Para. [0019]-Tsai discloses PDCCH monitoring methods for supporting NR from 52.6 GHz and above in which there may be a single DCI schedule multiple (e.g., two) PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s)), and
the one or more processors, individually or in any combination, are operable to cause the apparatus to: receive downlink control information (DCI) scheduling the PDSCH or the PUSCH in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies (Para. [0116]-Tsai discloses UE 102 can receive a single DCI scheduling multiple PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s). Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz)); and
receive the PDSCH or transmit the PUSCH in the one or more of the non-contiguous frequency bands associated with the each numerology of the different numerologies (Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz)),
individual … blocks in the PDSCH or the PUSCH are respectively allocated in the one or more of the non-contiguous frequency bands associated with the single numerology (Tables 2, 4 and 6, Para. [0053]-Tsai discloses bit field in DCI format 1_0/1_1 can be further reduced such as the frequency domain resource assignment (FDRA) ..., PDSCH-to-HARQ-timing-indicator, etc. can be reduced for new compact DCI format 1_x design for NR from 52.6 GHz to 71 GHz {set of frequency bands, including non-contiguity}. Para. [0087]-Tsai discloses allocation length of PRB for a PDSCH in one of the separate FDRA field in DCI. Para. [0079]-Tsai discloses FDRA: This field can be separated for each scheduled PDSCH. DCI can use separated FDRA field for each scheduled PDSCH frequency-domain resource. Para. [0116]-Tsai discloses UE 102 can receive a single DCI scheduling multiple PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s). Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}).
Tsai fails to explicitly teach code block.
However, Wang teaches individual code blocks in the PDSCH or the PUSCH are respectively allocated in the one or more of the non-contiguous frequency bands associated with the single numerology (Fig. 4, Para. [0074-0075]-Wang discloses UE 404 may map the ACK/NACK feedback frequency first ..., the subcarriers for ACK/NACK feedback may be non-contiguous in frequency. The UE 404 may puncture the PUSCH with the ACK/NACK feedback—e.g., at least a portion of a set of RBs corresponding to the PUSCH may be used to carry bits conveying the ACK/NACK feedback … one or more of the first code blocks of the PUSCH data may be heavily punctured by the ACK/NACK feedback and RI … the subcarriers for ACK/NACK feedback or RI may be non-contiguous in frequency. The UE 404 may puncture the PUSCH data with at least one of the ACK/NACK feedback and RI. Para. [0139]-Wang discloses the subcarriers for CQI may be non-contiguous in frequency, e.g., even or odd subcarriers).
Wang is considered to be analogous because it is in the same field of communication systems, dealing with user equipment configured for mapping uplink control information.
Therefore, it would have been obvious to someone of ordinary skill in the art before the effective filing date of the claimed invention to have modified the Tsai in view of Do to incorporate the teachings of Wang on code blocks, with a motivation for allocations in non-contiguous frequency bands, and guarantee operation of DL control channel for NR from 52.6 GHz and above, (Tsai, Para. [0004]).
Response to Arguments
Applicant's Arguments/Remarks, filed on 06/25/2026, with respect to the 35 USC § 102 rejection of claims 1-20 have been fully considered. Applicant’s arguments are not persuasive.
In the remarks, on page 12, Lines [5-7], Applicant argues that, “…not one of these paragraphs mentions the term "noncontiguous" or any analogous term, let alone a single cell that includes "a plurality of noncontiguous frequency bands."” Examiner respectfully disagrees for the following reasons:
In Para. [0050]-Tsai discloses NR from 52.6 GHz and above {Corresponding to set of frequency bands, including non-contiguous frequency bands} (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses for SCS/numerologies ... SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above {Corresponding to frequency bands} ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs. Para. [0042]-Tsai discloses SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0134]-Tsai discloses non-contiguous (time-domain) transmission of PDSCH/PUSCH can be supported. ….
In the remarks, on page 12, Lines [17-19], Applicant argues that, “…Paragraphs 38, 39, 42, 50, 57, and 107 of Tsai fail to teach or otherwise suggest "the cell including a plurality of non-contiguous frequency bands associated with different numerologies," of claim 1.”
However, Do et al. (US 20230066568 A1) explicitly teach the cell including a plurality of non-contiguous frequency bands associated with different numerologies (Para. [0181]-Do discloses the first frequency band and the second frequency band may be noncontiguous in a frequency domain. For example, the first frequency band and the second frequency band may belong to different operating frequency bands. Para. [0179]-Do discloses numerology of the first frequency band may be different from a numerology of the second frequency band. For example, a SCS of the OSs in the first frequency band may less than a SCS of the OSs in the second frequency band. Alternatively or in addition, a length of the OSs in the first frequency band may greater than a length of the OSs in the second frequency band. Para. [0165-0181]-Do discloses the same base station and/or the radio communication may use different SCSs at different times ... the term base station may be used interchangeably with the term cell ... the same base station and/or the radio communication may use different lengths of the OSs (e.g., different numerologies) at different times ... the radio communication uses a first frequency band and a second frequency band).
In the remarks, on page 15, Lines [1-6], Applicant argues that, “…the rejection of claim 2 still fails ... It does not disclose a configuration indicating that PDCCH monitoring should occur across "non-contiguous frequency bands associated with a single numerology," as recited in claim 2.”
However, TSAI teaches the control channel is a physical downlink control channel (PDCCH), the configuration indicates to monitor the PDCCH in the one or more of the non-contiguous frequency bands associated with the single numerology of the different numerologies (Para. [0048]-Tsai discloses monitoring PDCCH for NR from 52.6 to 71 GHz band {set of frequency bands, including non-contiguity}. Para. [0039]-Tsai discloses PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS {Numerology} configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Table 3, Para. [0089]-Tsai discloses design for the single-to-multiple scheduling DCI format (e.g., DCI format l_y) for NR from 52.6 {GHz band} and above ... Frequency domain resource assignment (FDRA) {Shared or Separated}. Para. [0050]-Tsai discloses DCI format 0_x and 1_x or PDCCH repetition for NR from 52.6 GHz and above (CORESET and/or SS configuration in a BWP). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}. Para. [0042]-Tsai discloses non-overlapped CCEs per span for a DL BWP with SCS configuration μ∈{0, 1} for a single serving cell can be {56, 56}, respectively. The per monitoring span (X, Y) supports SCS/numerologies 15 KHz/μ=0 and 30 KHz/μ=1 only. Para. [0107]-Tsai discloses numerology for the BWP in SCell may be different from the BWP used in the scheduled cell (e.g., PCell or PSCell). Para. [0057]-Tsai discloses SCSs/numerologies may be introduced for NR from 52.6 GHz and above ... For NR from 52.6 GHz and above, UE can know the “cross-slot” scheduling scheme for certain BWPs. (See also Para. [0120]). Para. [0134]-Tsai discloses non-contiguous (time-domain) transmission of PDSCH/PUSCH can be supported).
In the remarks, on page 16, Lines [12-15], Applicant argues that, “…as recited in claim 16, the "individual code blocks in the PDSCH or the PUSCH" relate to code blocks within a single channel (i.e., the PDSCH or the PUSCH). In contrast, the paragraphs cited by the Office Action all discuss multiple separate channels (i.e., "multiple PDSCHs").”
However, Tsai teaches blocks in the PDSCH or the PUSCH are respectively allocated in the one or more of the non-contiguous frequency bands associated with the single numerology (Tables 2, 4 and 6, Para. [0053]-Tsai discloses bit field in DCI format 1_0/1_1 can be further reduced such as the frequency domain resource assignment (FDRA) ..., PDSCH-to-HARQ-timing-indicator, etc. can be reduced for new compact DCI format 1_x design for NR from 52.6 GHz to 71 GHz {set of frequency bands, including non-contiguity}. Para. [0087]-Tsai discloses allocation length of PRB for a PDSCH in one of the separate FDRA field in DCI. Para. [0079]-Tsai discloses FDRA: This field can be separated for each scheduled PDSCH. DCI can use separated FDRA field for each scheduled PDSCH frequency-domain resource. Para. [0116]-Tsai discloses UE 102 can receive a single DCI scheduling multiple PDSCHs. Para. [0048]-Tsai discloses single DCI which schedules multiple PDSCH(s) can reduce the BD efforts for monitoring PDCCH for NR from 52.6 to 71 GHz band. In Rel-16, a single DCI can schedule two PDSCH(s). Para. [0114]-Tsai discloses single DCI scheduling multiple different PDSCHs from a serving cell with multiple TRP transmission. In addition, ... the gap symbol is required for the higher SCS (e.g., 960 KHz). Para. [0038-0039]-Tsai discloses UE can be configured with up to 10 SS sets each for up to 4 BWPs in a serving cell ... PDCCH minimum processing times is confined in units of symbols for SCS/numerologies ... PDCCH maximum number M.sub.PDCCH.sup.max,slot,μ of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell can be {44, 36, 22, 20}); while,
WANG et al. (US 20180132269 A1) teaches blocks in the PDSCH or the PUSCH are respectively allocated in the one or more of the non-contiguous frequency bands associated with the single numerology (Fig. 4, Para. [0074]-Wang discloses UE 404 may map the ACK/NACK feedback frequency first ... , the subcarriers for ACK/NACK feedback may be non-contiguous in frequency. The UE 404 may puncture the PUSCH with the ACK/NACK feedback—e.g., at least a portion of a set of RBs corresponding to the PUSCH may be used to carry bits conveying the ACK/NACK feedback … one or more of the first code blocks of the PUSCH data may be heavily punctured by the ACK/NACK feedback and RI).
Conclusion
Listed below are the prior arts made of record and not relied upon but are considered pertinent to applicant`s disclosure.
Tamiazzo et al. (US 20130162374 A1)-discloses nodes in the filter are connected both to resonant elements (a.k.a. resonators) and non-resonant elements (including elements having inductances and/or capacitances that do not resonate in a predetermined frequency band of interest). The resonant frequencies of the resonant elements may be adjusted, in order to adjust the location of the center frequency and/or the width of the passband of the filter. The characteristics of the resonant and non-resonant elements are selected such that the poles of the filter, when plotted on the complex plane, move substantially along the imaginary axis when the resonant frequencies are adjusted, without substantial movement along the real axis. The resulting bandpass filter has substantially constant losses and substantially constant absolute selectivity over a relatively wide range of bandwidths…. …Fig. 1-5
Yi Yunjung (US 20210092008 A1)-discloses method and apparatus for configuring a data subband set in a wireless communication system is provided. A user equipment (UE) configures at least one data subband set within a carrier, and communicating with a base station by using the at least one data subband set. Each of the at least one data subband set consists of at least one data subband, and each of the at least one data subband consists of a set of consecutive physical resource blocks (PRBs). Each of the at least one data subband set may be configured per numerology. The at least one data subband may correspond to at least one bandwidth part (BWP)…. …Fig. 1-5
Bagheri et al. (US 20200322929 A1)-discloses configuration of a first search space for monitoring control channel candidates over a first set of symbols can be received. A configuration of an alternative set of search spaces containing at least a second search space for monitoring control channel candidates over a second set of symbols can be received. A DCI scheduling an uplink transmission over a third set of symbols can be received. A determination can be made as to whether the uplink transmission overlaps with the first set of symbols. Control channel candidates in the first search space can be monitored when the uplink transmission does not overlap with the first set of symbols. Control channel candidates can be monitored in the second search space instead of the first search space when the uplink transmission overlaps with the first set of symbols.… …Fig. 1-5
WANG et al. (US 20250219772 A1)-discloses ata scheduling methods and apparatus are described. One example method includes receiving N pieces of initial scheduling information by a communication apparatus from N network devices. The communication apparatus sends coordinated transmission scheduling information and first indication information, and performs data transmission with M network devices on a time-frequency resource for coordinated transmission. One of the N pieces of initial scheduling information is from one of the N network devices. The N network devices are in one-to-one correspondence with the N pieces of initial scheduling information. The coordinated transmission scheduling information is determined by the terminal device based on the N pieces of initial scheduling information. The first indication information indicates information about the N network devices, where N is an integer greater than 1, M is an integer greater than or equal to N, and the M network devices include the N network devices…. …Fig. 1-5
BIAN et al. (US 20250227680 A1)-discloses data sending method, a data receiving method, a communication node, and a storage medium. The sending method comprises: determining a target physical resource block (PRB) index according to a first parameter, wherein the first parameter comprises at least one of the following: a reference PRB index, a time slot index, a PRB offset, the number of PRBs comprised in a first frequency resource, a second frequency resource position update duration, and an indication of the second frequency resource; determining a second frequency resource according to the target PRB index; and sending data within the second frequency resource…. …Fig. 1-5
Any inquiry concerning this communication or earlier communications from the examiner should be directed to OLADIRAN GIDEON OLALEYE whose telephone number is (571)272-5377. The examiner can normally be reached Monday - Friday: 07:30am - 05:30pm.
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 SPE, NICHOLAS A. JENSEN can be reached on (571) 270-5443. 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.
/OLADIRAN GIDEON OLALEYE/Examiner, Art Unit 2472
Prosecution Insights