DETAILED ACTION
Claims 1-22 are presented for examination.
Claims 1 and 11 are amended.
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 .
Response to Arguments
Applicant’s arguments with respect to claim 1 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
In response to the applicant’s argument, that by virtue of their dependence from amended claim 1, claims 2-10 are allowable, the examiner respectfully disagrees. No new arguments were presented for dependent claims other than their dependency to independent claim 1. Therefore for at least the reasons above presented for claim 1, the dependent claims 2-20 are rejected.
Regarding the rejection of claim 11, claim 11 recites the same limitations as set forth in claim 1, the response to claim 1 is also applicable to claim 11, and thus please refer to the response to claim 1 above.
In response to the applicant’s argument, that by virtue of their dependence from amended claim 11, claims 12-22 are allowable, the examiner respectfully disagrees. No new arguments were presented for dependent claims other than their dependency to independent claim 11. Therefore for at least the reasons above presented for claim 11, the dependent claims 12-22 are rejected.
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.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 1, 5-10 are rejected under 35 U.S.C. 103 as being unpatentable over Babaei (US 20220279456 A1); hereinafter Babaei, in view of Kim (US 12382465 B2); hereinafter Kim; further in view of MolavianJazi (US 20220053522 A1); hereinafter MolavianJazi; further in view of Kwon (US 20160302177 A1); hereinafter Kwon.
Regarding claim 1, Babaei teaches a method, performed by user equipment (UE), of physical uplink control channel (PUCCH) switching secondary cell (sSCell) switching, the method comprising:
transmitting UE capability information to a next generation node B (gNB) during an initial registration procedure ([0262] In an example, the wireless device may transmit the one or more capability messages in response to transitioning from an RRC idle/inactive state to an RRC connected state.), the UE capability information indicating whether the UE supports PUCCH cell switching (Fig. 37 and [0256] the wireless device may transmit one or more capability messages comprising one or more capability information elements (IEs) associated with uplink control channel (e.g., PUCCH) cell switching. For example, the one or more capability IEs may indicate whether the wireless device is capable of (e.g., supports) uplink control channel (e.g., PUCCH) cell switching (e.g., PUCCH cell switching);
receiving radio resource control (RRC) configuration including a PhysicalCellGroupConfig information element, the PhysicalCellGroupConfig information element including a sequence of pucch-sSCell information elements to configure multiple cells as PUCCH sSCells ([0167] the wireless device may receive one or more messages (e.g., one or more RRC messages) comprising configuration parameters associated with PUCCH carrier switching. The configuration parameters, associated with PUCCH carrier switching, may be for one or more PUCCH carriers/cells in a PUCCH group. Also, [0253] the wireless device may receive a configuration parameter (e.g., a pucch-sSCellPattern parameter) of a switching pattern);
receiving a medium access control (MAC) control element (CE) message for activation of a PUCCH sSCell for PUCCH transmission ([0108] The base station may activate or deactivate configured SCells using a SCell Activation/Deactivation MAC CE).
activating the PUCCH sSCell to use the PUCCH sSCell in addition to a configured PUCCH SCell for PUCCH transmission responsive to the MAC CE ([0171] In an example, the configured SCell(s) may be activated and deactivated based on receiving the SCell Activation/Deactivation MAC CE. [0100] The primary PUCCH group may comprise the PCell 1110 and one or more first SCells. First UCI corresponding to the PCell and the one or more first SCells of the primary PUCCH group may be transmitted by the PUCCH of the PCell. The first UCI may be, for example, HARQ feedback for downlink transmissions via downlink CCs of the PCell and the one or more first SCells. The secondary PUCCH group may comprise a PUCCH SCell and one or more second SCells. Second UCI corresponding to the PUCCH SCell and the one or more second SCells of the secondary PUCCH group may be transmitted by the PUCCH of the PUCCH SCell. The second UCI may be, for example, HARQ feedback for downlink transmissions via downlink CCs of the PUCCH SCell and the one or more second SCells. [0173] In an example, if firstActiveDownlinkBWP-Id is not set to dormant BWP: the wireless device may activate the SCell according to a timing for MAC CE activation and according to the timing direct SCell activation; i.e. apply normal SCell operation including: SRS transmissions on the SCell; CSI reporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoring for the SCell; PUCCH transmissions on the SCell, if configured.;
receiving a deactivation MAC CE message to deactivate the PUCCH sSCell from PUCCH transmission ([0178] In an example, an SCell Activation/Deactivation MAC CE is received deactivating the SCell); and
deactivating the PUCCH sSCell for PUCCH transmission and using an RRC configured cell for PUCCH transmission ([0180] In an example, if the SCell is deactivated: the wireless device may not transmit SRS on the SCell; not report CSI for the SCell; not transmit on UL-SCH on the SCell; not transmit on RACH on the SCell; not monitor the PDCCH on the SCell; not monitor the PDCCH for the SCell; and not transmit PUCCH on the SCell. [0201] The wireless device may receive a command (e.g., a cell activation/deactivation MAC CE) indicating deactivation of the second cell. The wireless device may receive the command before the first timing. In an example, the first timing may be after deactivation of the second cell and/or after reception of the command indicating deactivation of the second cell. In response to receiving the command and/or in response to determining to deactivate the second cell and/or in response to deactivation of the second cell, the wireless device may determine that the first cell/carrier is the PUCCH cell/carrier during the first timing. In response to receiving the command and/or in response to determining to deactivate the second cell and/or in response to deactivation of the second cell, the wireless device may determine that the first cell/carrier (RRC configured cell), and not the second cell/carrier configured by the timing pattern, is the PUCCH cell/carrier in the first timing.).
Babaei does not explicitly teach the MAC CE message comprising a MAC sub header including a logical channel identification (LCID) field and an extended LCID (eLCID) field, the MAC CE message further including a five-bit PUCCH sSCell identification (ID) of an SCell index to be used for the PUCCH sSCell; the five-bit PUCCH sSCell ID to accommodate a maximum thirty-two cell carrier aggregation (CA); the RRC configuration parameters can configure up to thirty-two cells.
However, Kim, in the same field of endeavor of wireless communications, teaches the MAC CE message comprising a MAC sub header including a logical channel identification (LCID) field and an extended LCID (eLCID) field (Col. 5, lines 28-37 FIG. 2I illustrates Table showing mapping information of a logical channel identifier for each data (e.g., data (MAC SDU or RLC PDU) of uplink shared channel (UL-SCH) or MAC CE) when a first logical channel Identity (LCID) or a second extended logical channel identity (eLCID) of a MAC subheader which is available for application of a data transmission method of a MAC layer is used, according to an embodiment of the disclosure.).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the MAC-CE message of Babaei to include a MAC sub header including the LCID and eLCID fields of Kim. The motivation to do so would have been to provide a method to transmit and/or receive data in a MAC layer (Kim; Col. 148, lines 25-28).
Kim does not teach the MAC CE message further including a five-bit PUCCH sSCell identification (ID) of an SCell index to be used for the PUCCH sSCell; the five-bit PUCCH sSCell ID to accommodate a maximum thirty-two cell carrier aggregation (CA); the RRC configuration parameters can configure up to thirty-two cells.
However, MolavianJazi, in the same field of endeavor of PUCCH carrier switching teaches the MAC CE message further including a five-bit PUCCH sSCell identification (ID) of an SCell index to be used for the PUCCH sSCell ([0667] FIG. 55 illustrates an example MAC-CE command 5500 for activation/deactivation of SP-CSI reporting on PUCCH according to embodiments of the present disclosure. An embodiment of the MAC-CE command 5500 shown in FIG. 55 is for illustration only. [0668] For example, the MAC-CE includes an index for an active PUCCH cell. [0547] In one embodiment, for a UE configured (to operate) with two or more PUCCH cells for at least one serving cell, the UE can receive a network signaling and/or an indication from higher layers for change of an active PUCCH cell for a given serving cell, herein referred to as an indication for switching of an active PUCCH cell. According to this embodiment, an indication for switching of an active PUCCH cell for a given serving cell can include one or more “PUCCH group switching” (PGS) field(s). [0550] According to this example, a PUCCH cell indicator (PCI) included in the PGS field in this case can be e.g. 5 bits to provide a “full/absolute” serving cell index for the new active PUCCH serving cell. [0424] In one embodiment of EA-1-2, contents of an indication for switching of an active PUCCH cell are provided. In one embodiment, for a UE configured (to operate) with two or more PUCCH cells for at least one serving cell, the UE can receive a network signaling and/or an indication from higher layers for change of an active PUCCH cell for a given serving cell, herein referred to as an indication for switching of an active PUCCH cell. According to this embodiment, an indication for switching of an active PUCCH cell for a given serving cell can include one or more “PUCCH group switching” (PGS) field(s), wherein each PGS field includes at least one or more of a PUCCH cell indicator (PCI), and an indication for a BWP in the new active PUCCH cell, and an indication for a serving cell for which the new active PUCCH cell applies.), the five-bit PUCCH sSCell ID to accommodate a maximum thirty-two cell carrier aggregation (CA) ([0295] According to this example, a scheduled cell index can be absent in an indication for switching of active scheduling cell(s). In another example, a scheduling cell indicator (SCI) parameter can have a bit-width of, for example, up to 5 bits or less to indicate an “absolute” cell index (e.g., out of the up to 32 configured serving cells for a UE). [0417] The present disclosure provides enhancements for PUCCH groups in a CA (carrier aggregation) operation to enable dynamic and flexible mechanisms for offloading of uplink control overhead corresponding to different serving cells among the PUCCH cells/groups). [0528] As illustrated in FIG. 32, a UE receives a configuration for operation with at least two serving cells, at step 3210, i.e., carrier aggregation operation. [0529] Herein, the two configured PUCCH serving cells are included among the at least two serving cells. For example, when the UE is configured with two serving cells and the two serving cells are a PCell and a PUCCH-SCell, then the two serving cells are the same as the two PUCCH serving cells. In another example, when the UE is configured with three serving cells including a PCell, a PUCCH-SCell, and another SCell without PUCCH configuration, and if both PCell and PUCCH-SCell are configured as PUCCH serving cells for the SCell without PUCCH configuration, then the serving cell is different from the PUCCH serving cells and the entire set of serving cells is different from (e.g., a super-set of) the set of PUCCH serving cell. As such, a serving cell can belong to two/multiple PUCCH groups.)
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the MAC-CE message of Babaei to include a five-bit PUCCH sSCell identification (ID) of an SCell index of MolavianJazi. The motivation to do so would have been to overcome the shortcomings of semi-statically configured associations between serving cells and PUCCH cell(s) as described in paragraph [0511], by allowing/supporting multiple (two or more) PUCCH cells for a given serving cell or a given serving cell group, along with an “active” PUCCH cell on which the UE transmits a UCI, wherein the active PUCCH cell can dynamically change over time based on network indication and/or UE determination. (MolavianJazi; [0511] [0512]).
MolavianJazi does not teach the RRC configuration parameters can configure up to thirty-two cells.
However, Kwon in the same field of endeavor of wireless communications teaches the RRC configuration parameters can configure up to thirty-two cells ([0009] a Radio Resource Control (RRC) message including cell configuration information for the UE, the cell configuration information for the UE including configuration information of a maximum of 32 serving cells).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the RRC configuration parameters of Babaei to include configuration information of a maximum of 32 serving cells of Kwon. The motivation to do so would have been to provide a method of activating/deactivating an SCell that is capable of configuring a PUCCH, and a method of indicating activation/deactivation with respect to increasing SCells under carrier aggregation. Also, to support a communication environment that evolves from an existing CA environment (system) that supports 5 CCs to a system that supports 5 or more CCs, and to provide support for a communication system that supports increasing CCs that are greater than or equal to 8 bits, by taking into consideration the structure of a MAC message of 8 bits. (Kwon; [0007] [0052]).
Regarding claim 5, Babaei teaches the sequence of pucch-sSCell information elements includes a first pucch sSCell information element for a primary PUCCH group, and a secondary pucch-sSCell information element is for a secondary PUCCH group ([0111] as shown in FIG. 11B, the base station may configure a UE with a primary PUCCH group 1114 and a secondary PUCCH group 1116).
Regarding claim 6, Babaei teaches the sequence of pucch-sSCell information elements is a first sequence of pucch-sSCell information elements for a master cell group, and in which a second sequence of pucch-sSCell information elements is for a secondary cell group ([0172] In case of dual/multi connectivity, the plurality of cells may comprise a first cell group (e.g., a master cell group (MCG)) provided by a first base station (e.g., a master base station) and a secondary cell group (e.g., a secondary cell group (SCG)) provided by a secondary base station).
Regarding claim 7, Babaei teaches selecting an RRC configured PUCCH cell for a first transmission and selecting the PUCCH sSCell for a second transmission (Fig. 26 and 27 and [0177] The wireless device may transmit a physical uplink control channel, via the first cell of the PUCCH group, with a first power level determined based on the first TPC command. The wireless device may switch a PUCCH cell/carrier from the first cell of the cell group to the second cell of the cell group. The switching the PUCCH cell/carrier from the first cell to the second cell may be based on one or more processes described above (e.g., based on an indication in a DCI and/or one or more rules to determine a PUCCH cell/carrier in a PUCCH group and/or a PUCCH cell timing pattern for determining a PUCCH cell/carrier in a PUCCH group). The wireless device then transmits the 2nd PUCCH via the 2nd cell of the PUCCH group as shown in Fig. 26).
Regarding claim 8, Babaei teaches the selecting is based on a predetermined periodic cell switch pattern ([0171] In an example, the switching between a first cell, in the first plurality of cells of the plurality of cells in the PUCCH group, to a second cell in the first plurality of cells may be based on a timing pattern of applicable PUCCH cells).
Regarding claim 9, Babaei teaches in which the selecting is based on a downlink control information (DCI) indicator ([0169] the switching between a first cell, in the first plurality of cells of the plurality of cells in the PUCCH group, to a second cell in the first plurality of cells may be based on a dynamic indication in a DCI).
Regarding claim 10, Babaei teaches the activation is performed after a time delay that is based on subcarrier spacing and physical downlink shared channel-to-hybrid automatic repeat request feedback (PDSCH-to- HARQ_feedback) timing indicator (Fig. 17 The term activation is interpreted as the actual switch from one cell to another. [0164] The UE switches cells, if necessary, after a time delay based on the PDSCH-to-HARQ feedback timing indicator and may also be based on the periodic cell switching pattern for PUCCH transmissions. [0259] The switching pattern may be based on a numerology (e.g., subcarrier spacing (SCS)) of the primary cell. a bit of the pattern may correspond to a slot for a reference SCS configuration (e.g., provided by a configuration parameter, e.g., by tdd-UL-DL-ConfigurationCommon) for the PCell with a value of ‘0’ or a value of ‘1’ indicating, respectively, the first cell or the second cell (e.g., PUCCH-sSCell) as the cell for PUCCH transmissions during the slot of the reference SCS configuration).
Claim Rejections - 35 USC § 103
Claim 4 is rejected under 35 U.S.C. 103 as being unpatentable over Babaei in view of Kim; further in view of MolavianJazi and Kwon as applied to claim 1 above, hereinafter Babaei-Kim- MolavianJazi-Kwon; further in view of Cheng (US 20220330155 A1); hereinafter Cheng.
Regarding claim 4, Babaei-Kim- MolavianJazi-Kwon teaches the method of claim 1, but does not teach MAC CE further includes a PUCCH group identification (ID) indicating whether a dynamic switch of PUCCH MAC CE is for a primary PUCCH group or for a secondary PUCCH group.
Cheng in the same field of endeavor of wireless communications and secondary cell dormancy teaches MAC CE further includes a PUCCH group identification (ID) indicating whether a dynamic switch of PUCCH MAC CE is for a primary PUCCH group or for a secondary PUCCH group ([0086] In some aspects, the RAR message may use a particular format to provide the timing alignment indicator. For example, as shown by reference numbers 703-2 and 703-3, BS 110 may use a legacy RAR MAC CE or a dedicated RAR MAC CE (e.g., which may include a reserved bit, N, (used as PUCCH group ID) to indicate whether the timing advance command is of a primary PUCCH group or a secondary PUCCH group of a secondary cell group)).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the MAC-CE message of Babaei-Kim- MolavianJazi-Kwon to include the PUCCH group ID of Cheng to indicate whether a dynamic switch of PUCCH MAC CE is for a primary PUCCH group or for a secondary PUCCH group. The motivation to do so would have been to provide a dormancy profile to define a dormancy state or dormancy behavior for a bandwidth part associated with a secondary cell. (Cheng, [0074]).
Claim Rejections - 35 USC § 103
Claims 2 and 3 are rejected under 35 U.S.C. 103 as being unpatentable over Babaei in view of Kim; further in view of MolavianJazi and Kwon I as applied to claim 1 above, hereinafter Babaei-Kim- MolavianJazi-Kwon; further in view of Babaei (US 20230102290 A1); hereinafter Babaei2.
Regarding claim 2, Babaei-Kim- MolavianJazi-Kwon teaches claim 1, but does not teach switching the PUCCH sSCell from a first cell to a second cell by deactivation of the first cell identified in a first MAC CE message and activation of the second cell identified in a second MAC CE message.
In the same field of endeavor of PUCCH cell switching, Babaei2 teaches switching the PUCCH sSCell from a first cell to a second cell by deactivation of the first cell identified in a first MAC CE message and activation of the second cell identified in a second MAC CE message ([0036] For example, the wireless device may receive a first command (e.g., a first SCell Activation/Deactivation MAC CE) indicating deactivation of the second cell. In response to receiving the first command, the wireless device may deactivate the second cell and the second cell may be deactivated in the first transmission timing based on the first command. In response to the second cell being deactivated in the first transmission timing, the wireless device may transmit the first UCI via the first cell in the first transmission timing. In an example, the timing pattern may further indicate that the second cell is the cell configured for PUCCH transmission in a second transmission timing. The wireless device may receive a second command (e.g., a second SCell Activation/Deactivation MAC CE) indicating activation of the second cell. In response to receiving the second command, the wireless device may activate the second cell and the second cell may be activated in the second transmission timing based on the second command).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the teachings of Babaei-Kim- MolavianJazi-Kwon with the teachings of Babaei2 to include the details of PUCCH cell switching with respect to the MAC CE Activation/Deactivation messages. The motivation to do so would have been to enhance processes associated with PUCCH Cell Switching in a PUCCH group and activation/deactivation status of candidate PUCCH cells in the PUCCH group (Babaei2, [0043]).
Regarding claim 3, Babaei teaches the deactivation is performed after a time delay that is based on subcarrier spacing and physical downlink shared channel-to-hybrid automatic repeat requestfeedback (PDSCH-to- HARQ_feedback) timing indicator (Fig. 17 [0164] The term deactivation is interpreted as the actual switch from one cell to another. The UE switches cells, if necessary, after a time delay based on the PDSCH-to-HARQ feedback timing indicator and may also be based on the periodic cell switching pattern for PUCCH transmissions. [0259] The switching pattern may be based on a numerology (e.g., subcarrier spacing (SCS)) of the primary cell. A bit of the pattern may correspond to a slot for a reference SCS configuration (e.g., provided by a configuration parameter, e.g., by tdd-UL-DL-ConfigurationCommon) for the PCell with a value of ‘0’ or a value of ‘1’ indicating, respectively, the first cell or the second cell (e.g., PUCCH-sSCell) as the cell for PUCCH transmissions during the slot of the reference SCS configuration).
Claim Rejections - 35 USC § 103
Claims 11-17 and 21 are rejected under 35 U.S.C. 103 as being unpatentable over Babaei (US 20220279456 A1); hereinafter Babaei, in view of MolavianJazi (US 20220053522 A1); hereinafter MolavianJazi; further in view of Kwon (US 20160302177 A1); hereinafter Kwon.
Regarding claim 11, Babaei teaches a method, performed by a next generation node B (gNB), of physical uplink control channel (PUCCH) switching secondary cell (sSCell) switching, the method comprising: receiving user equipment (UE) information from a UE during an initial registration procedure ([0262] In an example, the wireless device may transmit the one or more capability messages in response to transitioning from an RRC idle/inactive state to an RRC connected state), the UE capability information indicating whether the UE supports PUCCH cell switching ((Fig. 37 and [0256] the wireless device may transmit one or more capability messages comprising one or more capability information elements (IEs) associated with uplink control channel (e.g., PUCCH) cell switching. For example, the one or more capability IEs may indicate whether the wireless device is capable of (e.g., supports) uplink control channel (e.g., PUCCH) cell switching (e.g., PUCCH cell switching); determining whether the UE supports PUCCH cell switching ([0250] receiving configuration parameters for PUCCH cell switching (e.g., configuration parameters of the second cell (PUCCH switching secondary cell) and/or the second index for determining a second TPC command associated with the second cell) may be in response to transmitting the one or more capability messages and the one or more capability IEs indicating that the wireless device is capable of (e.g., supports) the uplink control channel (e.g., PUCCH) cell switching. Receiving configuration parameters for PUCCH cell switching from the gNB shows that the gNB determined the UE could support PUCCH cell switching); transmitting a radio resource control (RRC) configuration including a PhysicalCellGroupConfig information element, the PhysicalCellGroupConfig information element including a sequence of pucch-sSCell information elements to configure multiple cells as PUCCH sSCells ([0167] the wireless device may receive one or more messages (e.g., one or more RRC messages) comprising configuration parameters associated with PUCCH carrier switching. The configuration parameters, associated with PUCCH carrier switching, may be for one or more PUCCH carriers/cells in a PUCCH group. Also, [0253] the wireless device may receive a configuration parameter (e.g., a pucch-sSCellPattern parameter) of a switching pattern); selecting a PUCCH sSCell from among the configured PUCCH sSCells based on one or more triggering criteria, the one or more triggering criteria including pathloss, PUCCH resource location in a resource grid, cross fronthaul deployment type, selected antenna port, configured PUCCH sSCell switch pattern defining switching pattern between primary cell (PCell)/primary secondary cell (PSCell)/PUCCH secondary cell (SCell) and PUCCH switching secondary cell (PUCCH sSCell) (PCell/PSCell/PUCCH SCell and PUCCH sSCell), or type of spectrum used ([0168] The wireless device may determine a cell from the first plurality of cells as an applicable cell for PUCCH transmission and/or may switch PUCCH carrier/cell based at least one of: …a timing pattern for applicable cell used for transmission of PUCCH. [0253] For example, the configuration parameter may provide/indicate a periodic cell switching pattern for PUCCH transmissions (configured PUCCH sSCell switch pattern). The wireless device may determine, based on the switching pattern indicated by the first configuration parameter, whether the first cell or the second cell is the cell for uplink control channel transmission in/during the transmission timing of the uplink control information. For example, if the transmission timing of the uplink control information is within the first timings, indicated by the switching pattern, the wireless device may determine the first cell as the cell for uplink control channel transmission in/during the transmission timing (selecting a PUCCH sSCell from among the configured PUCCH sSCells). For example, if the transmission timing of the uplink control information is within the second timings, indicated by the switching pattern, the wireless device may determine the second cell as the cell for uplink control channel transmission in/during the transmission timing. [0111] A base station may configure a UE with multiple PUCCH groups wherein a PUCCH group comprises one or more cells. For example, as shown in FIG. 11B, the base station may configure a UE with a primary PUCCH group 1114 and a secondary PUCCH group 1116. The primary PUCCH group may comprise the PCell 1110 and one or more first SCells. The secondary PUCCH group may comprise a PUCCH SCell and one or more second SCells.); and triggering a MAC CE message for activation of the selected PUCCH sSCell for PUCCH transmission ([0108] The base station may activate or deactivate configured SCells using a SCell Activation/Deactivation MAC CE).
Babaei does not teach the MAC CE message including a five-bit PUCCH sSCell identification (ID) of an SCell index to be used for the PUCCH sSCell; the five-bit PUCCH sSCell ID to accommodate a maximum thirty-two cell carrier aggregation (CA); the RRC configuration parameters can configure up to thirty-two cells.
However, MolavianJazi, in the same field of endeavor of PUCCH carrier switching teaches the MAC CE message further including a five-bit PUCCH sSCell identification (ID) of an SCell index to be used for the PUCCH sSCell ([0667] FIG. 55 illustrates an example MAC-CE command 5500 for activation/deactivation of SP-CSI reporting on PUCCH according to embodiments of the present disclosure. An embodiment of the MAC-CE command 5500 shown in FIG. 55 is for illustration only. [0668] For example, the MAC-CE includes an index for an active PUCCH cell. [0547] In one embodiment, for a UE configured (to operate) with two or more PUCCH cells for at least one serving cell, the UE can receive a network signaling and/or an indication from higher layers for change of an active PUCCH cell for a given serving cell, herein referred to as an indication for switching of an active PUCCH cell. According to this embodiment, an indication for switching of an active PUCCH cell for a given serving cell can include one or more “PUCCH group switching” (PGS) field(s). [0550] According to this example, a PUCCH cell indicator (PCI) included in the PGS field in this case can be e.g. 5 bits to provide a “full/absolute” serving cell index for the new active PUCCH serving cell. [0424] In one embodiment of EA-1-2, contents of an indication for switching of an active PUCCH cell are provided. In one embodiment, for a UE configured (to operate) with two or more PUCCH cells for at least one serving cell, the UE can receive a network signaling and/or an indication from higher layers for change of an active PUCCH cell for a given serving cell, herein referred to as an indication for switching of an active PUCCH cell. According to this embodiment, an indication for switching of an active PUCCH cell for a given serving cell can include one or more “PUCCH group switching” (PGS) field(s), wherein each PGS field includes at least one or more of a PUCCH cell indicator (PCI), and an indication for a BWP in the new active PUCCH cell, and an indication for a serving cell for which the new active PUCCH cell applies.), the five-bit PUCCH sSCell ID to accommodate a maximum thirty-two cell carrier aggregation (CA) ([0295] According to this example, a scheduled cell index can be absent in an indication for switching of active scheduling cell(s). In another example, a scheduling cell indicator (SCI) parameter can have a bit-width of, for example, up to 5 bits or less to indicate an “absolute” cell index (e.g., out of the up to 32 configured serving cells for a UE). [0417] The present disclosure provides enhancements for PUCCH groups in a CA (carrier aggregation) operation to enable dynamic and flexible mechanisms for offloading of uplink control overhead corresponding to different serving cells among the PUCCH cells/groups). [0528] As illustrated in FIG. 32, a UE receives a configuration for operation with at least two serving cells, at step 3210, i.e., carrier aggregation operation. [0529] Herein, the two configured PUCCH serving cells are included among the at least two serving cells. For example, when the UE is configured with two serving cells and the two serving cells are a PCell and a PUCCH-SCell, then the two serving cells are the same as the two PUCCH serving cells. In another example, when the UE is configured with three serving cells including a PCell, a PUCCH-SCell, and another SCell without PUCCH configuration, and if both PCell and PUCCH-SCell are configured as PUCCH serving cells for the SCell without PUCCH configuration, then the serving cell is different from the PUCCH serving cells and the entire set of serving cells is different from (e.g., a super-set of) the set of PUCCH serving cell. As such, a serving cell can belong to two/multiple PUCCH groups.)
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the MAC-CE message of Babaei to include a five-bit PUCCH sSCell identification (ID) of an SCell index of MolavianJazi. The motivation to do so would have been to overcome the shortcomings of semi-statically configured associations between serving cells and PUCCH cell(s) as described in paragraph [0511], by allowing/supporting multiple (two or more) PUCCH cells for a given serving cell or a given serving cell group, along with an “active” PUCCH cell on which the UE transmits a UCI, wherein the active PUCCH cell can dynamically change over time based on network indication and/or UE determination. (MolavianJazi; [0511] [0512]).
MolavianJazi does not teach the RRC configuration parameters can configure up to thirty-two cells.
However, Kwon in the same field of endeavor of wireless communications teaches the RRC configuration parameters can configure up to thirty-two cells ([0009] a Radio Resource Control (RRC) message including cell configuration information for the UE, the cell configuration information for the UE including configuration information of a maximum of 32 serving cells).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the RRC configuration parameters of Babaei to include configuration information of a maximum of 32 serving cells of Kwon. The motivation to do so would have been to provide a method of activating/deactivating an SCell that is capable of configuring a PUCCH, and a method of indicating activation/deactivation with respect to increasing SCells under carrier aggregation. Also, to support a communication environment that evolves from an existing CA environment (system) that supports 5 CCs to a system that supports 5 or more CCs, and to provide support for a communication system that supports increasing CCs that are greater than or equal to 8 bits, by taking into consideration the structure of a MAC message of 8 bits. (Kwon; [0007] [0052]).
Regarding claim 12, Babaei teaches the PUCCH sSCell is for a frequency division duplex (FDD) system ([0167] In an example, the first secondary cell may be a FDD cell).
Regarding claim 13, Babaei teaches the PUCCH sSCell is for a time division duplex (TDD) system ([0162] A wireless device may switch PUCCH carrier/cell, for example to avoid delay for HARQ feedback transmission if a PUCCH carrier/cell of a PUCCH group is a TDD cell).
Regarding claim 14, Babaei teaches the sequence of pucch-sSCell information elements includes a first pucch-sSCell information element for a primary PUCCH group, and a second pucch-sSCell information element is for a secondary PUCCH group ([0111] as shown in FIG. 11B, the base station may configure a UE with a primary PUCCH group 1114 and a secondary PUCCH group 1116).
Regarding claim 15, Babaei teaches the sequence of pucch-sSCell information elements is a first sequence of pucch-sSCell information elements for a master cell group, and in which a second sequence of pucch-sSCell information elements is for a secondary cell group ([0172] In case of dual/multi connectivity, the plurality of cells may comprise a first cell group (e.g., a master cell group (MCG)) provided by a first base station (e.g., a master base station) and a secondary cell group (e.g., a secondary cell group (SCG)) provided by a secondary base station.
Regarding claim 16, Babaei teaches the PhysicalCellGroupConfig information element configures the UE for PUCCH cell switching that is statically configured based on a predetermined periodic cell switch pattern ([0253] the wireless device may receive a configuration parameter (e.g., a pucch-sSCellPattern parameter). The configuration parameter may provide/indicate a periodic cell switching pattern for PUCCH transmissions).
Regarding claim 17, Babaei teaches the PhysicalCellGroupConfig information element configures the UE for PUCCH cell switching that is dynamically configured based on downlink control information (DCI) indicator ([0169] the switching between a first cell, in the first plurality of cells of the plurality of cells in the PUCCH group, to a second cell in the first plurality of cells may be based on a dynamic indication in a DCI).
Regarding claim 21, Babaei teaches in response to the activation or deactivation performed after a time delay that is based on subcarrier spacing and physical downlink shared channel-to-hybrid automatic repeat requesetfeedback (PDSCH-to-HARQ_feedback) timing indicator, and monitoring PUCCH on both RRC configured cells and the PUCCH sSCells (Fig. 17 [0164] The term activation/deactivation is interpreted as the actual switch from one cell to another. The UE switches cells, if necessary, after a time delay based on the PDSCH-to-HARQfeedback timing indicator and may also be based on the periodic cell switching pattern for PUCCH transmissions. [0259] The switching pattern may be based on a numerology (e.g., subcarrier spacing (SCS)) of the primary cell. A bit of the pattern may correspond to a slot for a reference SCS configuration (e.g., provided by a configuration parameter, e.g., by tdd-UL-DL-ConfigurationCommon) for the PCell with a value of ‘0’ or a value of ‘1’ indicating, respectively, the first cell or the second cell (e.g., PUCCH-sSCell) as the cell for PUCCH transmissions during the slot of the reference SCS configuration. After which the PUCCH is transmitted by the UE as shown in Fig. 17).
Claim Rejections - 35 USC § 103
Claim 18 is rejected under 35 U.S.C. 103 as being unpatentable over Babaei in view of MolavianJazi further in view of Kwon, as in claim 11, hereinafter Babaei-MolavianJazi-Kwon; further in view of KITTICHOKECHAI (WO 2022086414 A2); hereinafter KITTICHOKECHAI; further in view of Cheng (US 20220330155 A1); hereinafter Cheng, further in view of 3GPP TS 38.321 V17.5.0 (2023-06); hereinafter TS 38.321.
Regarding claim 18, Babaei-MolavianJazi-Kwon teaches the method of claim 11 but does not teach wherein the MAC CE message comprises: a MAC sub header including a logical channel identification (LCID) field and an extended LCID (eLCID) field; and MAC CE data including an activation/deactivation (A/D) bit, PUCCH group identification (ID), a serving cell ID, a PUCCH-sSCell ID, a bandwidth part (BWP) ID, a supplementary uplink (SUL) bit, and a multi-cell configuration (MC) bit.
However, KITTICHOKECHAI, in the same field of endeavor of PUCCH carrier switching teaches wherein the MAC CE message comprises: a MAC sub header including a logical channel identification (LCID) field and an extended LCID (eLCID) field ([00154] Table 3 shows an example of a new eLCID for this new MAC CE); and MAC CE data including a serving cell ID ([00150] The Serving Cell ID field indicates the identity of the PDSCH serving cell for which the MAC CE applies. The length of the field is 5 bits), a PUCCH-sSCell ID ([00151] The PUCCH Cell Indicator field indicates the UL serving cell where the HARQ-ACK for the PDSCH on the Serving Cell are carried. In some embodiments, "PUCCH Cell Indicator" is 1-bit, where value '0' indicates PCell, value '1' indicates SpCell of this cell group or a PUCCH SCell. In other embodiments, "PUCCH Cell Indicator" is 2-bit, and up to 4 PUCCH cells can be indicated.).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the MAC-CE message of Babaei-MolavianJazi-Kwon to include the MAC CE data fields of KITTICHOKECHAI. The motivation to do so would have been to allow to switch PUCCH carrier in a PUCCH group on which HARQ feeback is transmitted. The embodiments allow for example, the HARQ feedback to be provided on UL carrier in a PUCCH group and not necessarily only on the default PUCCH carriers such as PCell or PUCCH-SCell of the corresponding PUCCH group. This can be useful, e.g., for URLLC, to reduce the overall DL transmission latency which involves HARQ-ACK retransmission because the UE can switch to a PUCCH carrier which provides lower latency. (KITTICHOKECHAI; [0013]).
KITTICHOKECHAI does not teach MAC CE data including an activation/deactivation (A/D) bit, PUCCH group identification (ID), a bandwidth part (BWP) ID, a supplementary uplink (SUL) bit, and a multi-cell configuration (MC) bit.
However, Cheng in the same field of endeavor of wireless communications and secondary cell dormancy, teaches MAC CE data including a PUCCH group identification (ID) ([0086] as shown by reference numbers 703-2 and 703-3, BS 110 may use a legacy RAR MAC CE or a dedicated RAR MAC CE (e.g., which may include a reserved bit, N, (used as PUCCH group ID) to indicate whether the timing advance command is of a primary PUCCH group or a secondary PUCCH group of a secondary cell group)).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the MAC-CE message of Babaei-MolavianJazi-Kwon and KITTICHOKECHAI to include the PUCCH group ID of Cheng. The motivation to do so would have been to provide a dormancy profile to define a dormancy state or dormancy behavior for a bandwidth part associated with a secondary cell. (Cheng, [0074]).
Cheng does not explicitly teach the MAC CE message comprising MAC CE data including an activation/deactivation (A/D) bit, a bandwidth part (BWP) ID, a supplementary uplink (SUL) bit, and a multi-cell configuration (MC) bit.
However, TS 38.321, in the same field of endeavor of wireless communications, teaches the MAC CE message comprising a MAC sub header including a logical channel identification (LCID) field and an extended LCID (eLCID) field (Section 6.2.1, The MAC subheader consists of the following fields: LCID and eLCID); and MAC CE data including an activation/deactivation (A/D) bit (Fig. 6.1.3.18-1, Section 6.1.3.18, Si: If, in PUCCH-Config in which the PUCCH Resource ID is configured, there is a PUCCH Spatial Relation Info with PUCCH-SpatialRelationInfoId as specified in TS 38.331 [5], configured for the uplink bandwidth part indicated by BWP ID field, Si indicates the activation status of PUCCH Spatial Relation Info with PUCCH-SpatialRelationInfoId equal to i + 1, otherwise MAC entity shall ignore this field. The Si field is set to 1 to indicate PUCCH Spatial Relation Info with PUCCH-SpatialRelationInfoId equal to i + 1 shall be activated. The Si field is set to 0 to indicate PUCCH Spatial Relation Info with PUCCH-SpatialRelationInfoId equal to i + 1 shall be deactivated. Only a single PUCCH Spatial Relation Info can be active for a PUCCH Resource at a time), a bandwidth part (BWP) ID ((Fig. 6.1.3.25-1, Section 6.1.3.25, BWP ID: This field indicates a UL BWP for which the MAC CE applies as the codepoint of the DCI bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits), a supplementary uplink (SUL) bit (Fig. 6.1.3.26-1, Section 6.1.3.26, SUL: This field indicates whether the MAC CE applies to the NUL carrier or SUL carrier configuration. This field is set to 1 to indicate that it applies to the SUL carrier configuration, and it is set to 0 to indicate that it applies to the NUL carrier configuration), and a multi-cell configuration (MC) bit (Fig. 6.1.3.26-1, Section 6.1.3.26, C: This field indicates whether the octets containing Resource Serving Cell ID field(s) and Resource BWP ID field(s) are present. If this field is set to 1, Resource Serving Cell ID field(s) and Resource BWP ID field(s) are present (multi-cell configuration), otherwise they are not present so MAC entity shall ignore Resource Serving Cell ID field(s) and Resource BWP ID field(s)).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the MAC-CE message of Babaei-MolavianJazi-Kwon, KITTICHOKECHAI and Cheng to include a MAC sub header including the LCID and eLCID fields of TS 38.321 and the data including an activation/deactivation (A/D) bit, a supplementary uplink (SUL) bit, and a multi-cell configuration (MC) bit. The motivation to do so would have been to include other pertinent parameters in the MAC CE for flexible configuration.
Claim Rejections - 35 USC § 103
Claims 19, 20 and 22 are rejected under 35 U.S.C. 103 as being unpatentable over Babaei in view of MolavianJazi, Kwon, KITTICHOKECHAI, Cheng and 3GPP TS 38.321 V17.5.0 (2023-06); hereinafter Babaei-MolavianJazi-Kwon-KITTICHOKECHAI-Cheng-3GPP TS 38.321;, as applied to claim 18 above, and further in view of Babaei (US 20230102290 A1); hereinafter Babaei2.
Regarding claim 19, Babaei-MolavianJazi-Kwon-KITTICHOKECHAI-Cheng-3GPP TS 38.321 teaches claim 18, but they do not explicitly teach the MAC CE message is a first MAC CE message, and the method further comprising switching the selected PUCCH sSCell by deactivation of a first cell identified in the first MAC CE message, and activation of a second cell identified in a second MAC CE message.
In the same field of endeavor of PUCCH cell switching, Babaei2 teaches the MAC CE message is a first MAC CE message, and the method further comprising switching the selected PUCCH sSCell by deactivation of a first cell identified in the first MAC CE message, and activation of a second cell identified in a second MAC CE message ([0336] For example, the wireless device may receive a first command (e.g., a first SCell Activation/Deactivation MAC CE) indicating deactivation of the second cell. In response to receiving the first command, the wireless device may deactivate the second cell and the second cell may be deactivated in the first transmission timing based on the first command. In response to the second cell being deactivated in the first transmission timing, the wireless device may transmit the first UCI via the first cell in the first transmission timing. In an example, the timing pattern may further indicate that the second cell is the cell configured for PUCCH transmission in a second transmission timing. The wireless device may receive a second command (e.g., a second SCell Activation/Deactivation MAC CE) indicating activation of the second cell. In response to receiving the second command, the wireless device may activate the second cell and the second cell may be activated in the second transmission timing based on the second command).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the teachings of Babaei-MolavianJazi-Kwon-KITTICHOKECHAI-Cheng-3GPP TS 38.321 with the teachings of Babaei2 to include the details of PUCCH cell switching with respect to the MAC CE Activation/Deactivation messages. The motivation to do so would have been to enhance processes associated with PUCCH Cell Switching in a PUCCH group and activation/deactivation status of candidate PUCCH cells in the PUCCH group (Babaei2 [0043]).
Regarding claim 20, Babaei-MolavianJazi-Kwon-KITTICHOKECHAI-Cheng-3GPP TS 38.321 teaches claim 18, but they do not explicitly teach deactivating the PUCCH sSCell in response to none of the cells qualifying as the PUCCH sSCell based on one or more triggering criteria.
In the same field of endeavor of PUCCH cell switching, Babaei2 teaches deactivating the PUCCH sSCell in response to none of the cells qualifying as the PUCCH sSCell based on one or more triggering criteria ([0229] In an example embodiment, the plurality of cells in a PUCCH group may be deactivated while (e.g., based on) the candidate PUCCH cells of the PUCCH group are deactivated. For example, the network (base station) may transmit commands (e.g., one or more MAC CEs) indicating deactivation of all of the cells of the PUCCH group based on/while the candidate PUCCH cells of the PUCCH group are deactivated).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the teachings of Babaei-MolavianJazi-Kwon-KITTICHOKECHAI-Cheng-3GPP TS 38.321 with the teachings of Babaei2 to deactivate the PUCCH sSCell in response to none of the cells qualifying as the PUCCH sSCell based on one or more triggering criteria. The motivation to do so would have been to enhance processes associated with PUCCH Cell Switching in a PUCCH group and activation/deactivation status of candidate PUCCH cells in the PUCCH group (Babaei2 [0043]).
Regarding claim 22, Babaei-MolavianJazi-Kwon-KITTICHOKECHAI-Cheng-3GPP TS 38.321 teaches claim 18, but they do not explicitly teach triggering a deactivation MAC CE message to deactivate the PUCCH sSCell preparatory to a cell release.
In the same field of endeavor of PUCCH cell switching, Babaei2 teaches triggering a deactivation MAC CE message to deactivate the PUCCH sSCell preparatory to a cell release ([0189] In an example, at handover or connection resume from RRC_INACTIVE: the SCells may be activated or deactivated).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the teachings of Babaei-MolavianJazi-Kwon-KITTICHOKECHAI-Cheng-3GPP TS 38.321 with the teachings of Babaei2 to include triggering a deactivation MAC CE message to deactivate the PUCCH sSCell preparatory to a cell release. The motivation to do so would have been to enhance processes associated with PUCCH Cell Switching in a PUCCH group and activation/deactivation status of candidate PUCCH cells in the PUCCH group (Babaei2 [0043]).
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to NANCY SIXTO whose telephone number is (571)272-3295. The examiner can normally be reached Mon - Friday 9AM-5PM EST.
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, Gary Mui can be reached at 571-270-1420. 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.
/NANCY SIXTO/Examiner, Art Unit 2465
/GARY MUI/Supervisory Patent Examiner, Art Unit 2465
Prosecution Insights